Best KitKat 4.4 ROM for HTC one?


Recommended Posts

Hallo people.

 

I have been using a sense 4.3 ROM on my HTC one for a while and thought it's probably time to update to kitkat, I'm wanting a ROM (Play edition) that's as stock as possible but any sort of speed/performance tweaks would be welcome too.

 

Not really font of asop roms because they never include beats audio support, same goes to CM roms too.

 

 

The only thing I'm going to miss other than that is the Sense camera, it's so much better than the stock android one! Doesn't even support slow mo, total waste of space. Don't know if there's any way to bring that over to android 4.4. I know there used to be but I don't think so now.

 

So, thanks for the help anyways!

Link to comment
Share on other sites

Kind of hard to say regardless of what phone you have.  Each ROM offers something different in ways of performance, features...and so on.

 

CyanogenMod is always a solid choice depending if it is available for your phone.  Otherwise, its trial/error testing different ROMs and finding on you like. I normally look at what the thread is rated on XDA and then read a few pages of the thread to see what kind of problems there are.

 

Anyway, I would go to http://forum.xda-developers.com/htc-one and check out the Development forums.

Link to comment
Share on other sites

Kind of hard to say regardless of what phone you have.  Each ROM offers something different in ways of performance, features...and so on.

 

CyanogenMod is always a solid choice depending if it is available for your phone.  Otherwise, its trial/error testing different ROMs and finding on you like. I normally look at what the thread is rated on XDA and then read a few pages of the thread to see what kind of problems there are.

 

Anyway, I would go to http://forum.xda-developers.com/htc-one and check out the Development forums.

Thing is, I'd be happy with stock GP edition, didn't seem to work 100% though. I know it's only a small thing but the transparent toolbar went solid when you were in any apps, isn't it supposed to remain transparent? At least in apps like Google Maps where there's full screen content?

Link to comment
Share on other sites

Thing is, I'd be happy with stock GP edition, didn't seem to work 100% though. I know it's only a small thing but the transparent toolbar went solid when you were in any apps, isn't it supposed to remain transparent? At least in apps like Google Maps where there's full screen content?

Nope, not even on the Nexus 5. I've had no problems at all with the Google Play edition conversion on my HTC One. It is designed specifically for that phone, after all, so it should work 100%. That is as compared to something like CyanogenMod that's a third party thing.

 

There are two types of ROMs out there. There are ROMs based off stock HTC software, and there are ROMs based off AOSP code adapted for the device. In the case of the HTC One, it has a fairly AOSP ROM in the Google Play edition, so you could say there are GPe based ROMs as well.

 

If you want/need Beats and the HTC camera, you must be on an HTC based ROM. The code for these features is in the HTC code, so going with CM or GPe will lose those features. It's not just something that people have forgotten to add. There are alternatives though for AOSP based ROMs like various sound mods available on XDA and camera apps like Focal that add more features over AOSP if you go that route.

 

The HTC One confuses things a little bit more in the fact that the GPe ROMs actually still uses HTCs kernel and have some of the underlying Sense code in the kernel. This allows them to use some features like the IR sensor and if I recall correctly it enabled better USB OTG for me, but I can't remember the details there. So GPe ROMs give you the feel of AOSP, but better support for the device than ROMs like CM.

 

For me, nothing compares to GPe. On my N5 I'm running CM now because it is true AOSP and therefore nothing is really missing from CM. For the HTC One I run GPe because it's the best of both worlds and gets updates quickly. In fact, I just pulled mine out this morning and it's bugging me to update to 4.4.2.

Link to comment
Share on other sites

  • 2 weeks later...

Nope, not even on the Nexus 5. I've had no problems at all with the Google Play edition conversion on my HTC One. It is designed specifically for that phone, after all, so it should work 100%. That is as compared to something like CyanogenMod that's a third party thing.

 

There are two types of ROMs out there. There are ROMs based off stock HTC software, and there are ROMs based off AOSP code adapted for the device. In the case of the HTC One, it has a fairly AOSP ROM in the Google Play edition, so you could say there are GPe based ROMs as well.

 

If you want/need Beats and the HTC camera, you must be on an HTC based ROM. The code for these features is in the HTC code, so going with CM or GPe will lose those features. It's not just something that people have forgotten to add. There are alternatives though for AOSP based ROMs like various sound mods available on XDA and camera apps like Focal that add more features over AOSP if you go that route.

 

The HTC One confuses things a little bit more in the fact that the GPe ROMs actually still uses HTCs kernel and have some of the underlying Sense code in the kernel. This allows them to use some features like the IR sensor and if I recall correctly it enabled better USB OTG for me, but I can't remember the details there. So GPe ROMs give you the feel of AOSP, but better support for the device than ROMs like CM.

 

For me, nothing compares to GPe. On my N5 I'm running CM now because it is true AOSP and therefore nothing is really missing from CM. For the HTC One I run GPe because it's the best of both worlds and gets updates quickly. In fact, I just pulled mine out this morning and it's bugging me to update to 4.4.2.

 

Well I tried google play edition for about a day and as you can imagine, I was taking a lot of photos over the holiday period. Stock android camera looks like crap! Glad I made a nandroid backup, it's a shame that no one has figured out how to get the relevant framework files from the sense version of the rom just to pull over the camera app because both the quality and features are much better than stock android's camera.

Link to comment
Share on other sites

Oh, yeah, I think the camera isn't as good on AOSP, but I really don't use my camera much for quality, so I never really noticed. I know the Google Play Edition kernel is about the same as the Sense kernel so it already has the inner workings. I wonder if it would be at all possible to strip down the framework to a minimum on the software side just to get the camera working. Though, I suppose if it were realistic, someone would have already done it.

Link to comment
Share on other sites

I've been using the Cyanogen 11 nightlies for like a week now, no real problems with it, I don't taken many pictures, but the few I've taken have looked just fine, and nothing running it through Auto Awesome or Snapseed can't fix, not that I've actually had to fix any yet

Link to comment
Share on other sites

The thing is Cyanogenmod, or CM, will never be as good as pure Google AOSP or HTC with their software. The AOSP camera is rubbish unuless its a Nexus device, and the camera on CM is just as bad.

 

I would suggest you head over to XDA and check out the GPE roms if you want a pure Google experience with no HTC bloat (i call it bloat, some may call it features).

 

I personally stay away from Cyanogenmod, even more so now that they are a LLC and are closing source on much of their work, which defeats the whole open source community IMO.

 

Take a loot at ParanoidAndroid, also known as AOSPA they have a kitkat rom available for your device at this XDA thread http://bit.ly/1eCR610

 

Here is a stock GPE edition that is rooted http://bit.ly/JEh1Mr and here is one more GPE edition with some tweaks http://bit.ly/1egkKJ4

 

Here is my honest opinion as someone who has made custom roms for the OGEVO4g, the d2spr, along with the nexus 5 aka hammerhead. I recommend running stock GPE or Google roms and use something like Xposed (a free app) that allows you to add in different customizations. Usually this is the best option on a stock rom, that way you keep FULL functionality, which isnt the case with most custom AOSP roms and even CM roms, certain aspects of your phone just wont work or are buggy. With xposed you keep the fully working stock rom and just modifiy it to your liking, I really enjoy the Xposed add-on gravitybox.

Link to comment
Share on other sites

I just recently switched back to Android and I've been running CyanogenMod 10.2 on my One X. I prefer CyanogenMod to AOSP just because of the added customization you can do in CM as opposed to bone-stock AOSP.

Link to comment
Share on other sites

I've been using the Cyanogen 11 nightlies for like a week now, no real problems with it, I don't taken many pictures, but the few I've taken have looked just fine, and nothing running it through Auto Awesome or Snapseed can't fix, not that I've actually had to fix any yet

 

I have been running C11 on my LG G2 for a few months.  Works great and pics are pretty good as well.  I have taken some good pics with it.

Link to comment
Share on other sites

If you don't like the AOSP camera app, search for a replacement in the play store. There isn't much you can't customise on Android.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.