I want to run a custom ROM, but I keep running into bugs that are a no go for me. One in particular being the sound distortion bug that seems to be in every ROM I've tried. Anyone know if there are any without such problems?
I have the Verizon HTC One M8 currently running stock rooted with an unlocked bootloader.
Seems the sound distortion bug only effects cm based Roms. Try the stock Roms on here.
From what I understand nothing but a sense ROM will not have the bug based on HTC not releasing something and the CM teams having to reverse engineer. In thinking it's the kernel, but don't quote me on that.
Related
Hi
Not sure where to post this. Want as much exposure as i can get for a fast fix.
Basically, I have tried two custom roms:
AOKP JB rom
Paranoid Android
I would have stuck with any of these, but the AOKP rom would switch from Loudspeaker to normal during a phonecall. And the Paranoid Android has too many bugs in it that I cant run it without getting annoyed with the force closes etc.
Im now looking for either:
A FULLY WORKING CUSTOM ROM
or
AN OFFICIAL HTC ONE V STOCK ROM
hope you can point me to the right direction?
Thanks,
Words fails me. I am so disgusted I have ran out of expletives so I won't bother repeating them here. Seriously...voice dialer is STILL not working! This update was specifically designed to fix this bug and it is still not working. I just can't understand what is so hard about putting back in functionality that was working before in ICS and was necessary.
This is the sort of thing that gets people to switch over irrevocably to apple. This has been going on for like a year now. It is starting to feel like it is being done on purpose for God knows what reason. Does it work for anyone else?
android 4.2.2
i535VRBLK3
AOKP
What update? This phone is officially on 4.1.1 . You are not guaranteed anything by running custom software.
BattsNotIncld said:
What update? This phone is officially on 4.1.1 . You are not guaranteed anything by running custom software.
Click to expand...
Click to collapse
Fair enough. Although I never said I was guaranteed anything and apparently we are also not guaranteed to have important functionality (aka voice dialer) to work from one official release to the next. It worked fine when I had ICS it just broke when I was upgraded to JB. I would prefer not to have to root my phone to get it work, but if I waited for the official channels then I will likely have to wait until I get my next phone for a fix.
Both Google and AOKP mentioned that bluetooth issues were fixed with 4.2.2 and I was inquiring whether this worked for others as it did not work for me. Neither 4.1.1, nor 4.1.2 nor 4.2.1 nor 4.2.2 nor any of the other little hacks others have tried have worked and I know others on the official release of 4.2.2 for Nexus had similar problems so I was hoping someone might have run across a solution.
I know I sounded snarky, but I am just really frustrated.
So I do not know if this will help you but I had pacman rom and the dialer wasn't working so I reflashed, no wiping and it fixed it.
Also there is always the option of going back to the stable TW roms. Which is what I did. You can't be mad for things not running smooth when you're running custom roms that make no claims of stability.
Via my S3 CleanRom 5.6
CM-Freak said:
So I do not know if this will help you but I had pacman rom and the dialer wasn't working so I reflashed, no wiping and it fixed it.
Also there is always the option of going back to the stable TW roms. Which is what I did. You can't be mad for things not running smooth when you're running custom roms that make no claims of stability.
Via my S3 CleanRom 5.6
Click to expand...
Click to collapse
Thanks for the info, it was definitely worth a try. Alas the pacman rom did not do the trick. I had the official JB TW update and that is what broke my phone in the first place and I am not really interested in going back to ICS since I got the new phone so I can get Jelly Bean. I have also tried CleamROM and the the latest CM, AOKP and liquidSmooth 4.2.2 along with the just released gapps-jb-130301-signed.zip. No dice.
I'll keep banging away and let everyone know if I find a solution with other ROMs or tweaks.
I am not mad about custom ROMs not working properly I am mad about the official release breaking critical functionality for me.
I tried PK and PA ROMs in addition to aready mentioned. Voice dial does not work in any of them. I also tried Ktoonsez kernel - no dice. I think it's a major JB problem and there won't be any working ROM until Google fixes the issue. I just stopped trying :crying: ...
I would like to put KitKat on my phone and I have not done the OTA 4.3 update, so my baseband has not been updated. Whenever I try to figure out how to put KitKat on my phone, I find threads that say something like the following.
Don't update to 4.3 or you'll never get a custom boot image
OK, we figured out how to root 4.3, but you still shouldn't do it
All KITKAT roms are based on AOSP or their derivitives, which you need to update to 4.3 to get
But don't update to 4.3 because it isn't worth it, I mean, the camera sucks on AOSP
Here is a list of 25 KITKAT roms, each more awesome than the last!
Here is a 4.3 update without the baseband, if you haven't updated, use this, it is the best of both worlds
We wont be updating the above rom, because we are so excited about these KITKAT roms!
Hey I just updated to AOSP (CM, AOKP, etc) KITKAT and it is lame, how do I get TW back?
Does that sound about right? If I want KITKAT I should just stop wanting KITKAT and that will solve all my problems?
If you take the 4.3 update you will be stuck on 4.3 (or until Verizon decides to upgrade). It can be rooted and now you can flash other 4.3 ROMs with safestrap, but you will never be able to run a custom recovery/kernel. So even if you wanted to try AOSP you wouldn't be able to. I don't know who told you you have to upgrade to 4.3 to try AOSP but that is completely off base, in fact it's the complete opposite!
What are you currently running? Is your bootloader unlocked? If you are curious about AOSP I would definitely give it a try. In my experience TW ROMS tend to be more stable and have every bit of hardware working (camera, bluetooth, etc). AOSP ROMS are quicker, smoother, have newer features and are more easily customized. It's really a matter of preference.
If you really want to try KK and be on the bleeding edge you should. Kit Kat ROMs run very well on this phone. If something like a 100% working camera or bluetooth is extremely important to you I would stay on TW. However, devs are constantly working on the ROMs and working out these kinks.
BattsNotIncld said:
If you take the 4.3 update you will be stuck on 4.3 (or until Verizon decides to upgrade). It can be rooted and now you can flash other 4.3 ROMs with safestrap, but you will never be able to run a custom recovery/kernel. So even if you wanted to try AOSP you wouldn't be able to. I don't know who told you you have to upgrade to 4.3 to try AOSP but that is completely off base, in fact it's the complete opposite!
What are you currently running? Is your bootloader unlocked? If you are curious about AOSP I would definitely give it a try. In my experience TW ROMS tend to be more stable and have every bit of hardware working (camera, bluetooth, etc). AOSP ROMS are quicker, smoother, have newer features and are more easily customized. It's really a matter of preference.
If you really want to try KK and be on the bleeding edge you should. Kit Kat ROMs run very well on this phone. If something like a 100% working camera or bluetooth is extremely important to you I would stay on TW. However, devs are constantly working on the ROMs and working out these kinks.
Click to expand...
Click to collapse
OK, thanks for the info.
How do I know which baseband a rom is for? I found the TouchWiz 4.3 Download List. Does that basically mean that, if it isn't on that list, it is probably for the old baseband?
I tried flashing some Gummy nightlies and Carbon - both failed. On TWRP, the only message I get is "install failed"
I know troubleshooting that is a different thread, but I'm not sure where to start to figure it out.
ragendem said:
OK, thanks for the info.
How do I know which baseband a rom is for? I found the TouchWiz 4.3 Download List. Does that basically mean that, if it isn't on that list, it is probably for the old baseband?
I tried flashing some Gummy nightlies and Carbon - both failed. On TWRP, the only message I get is "install failed"
I know troubleshooting that is a different thread, but I'm not sure where to start to figure it out.
Click to expand...
Click to collapse
Update your recovery.
That thread is what will work on the Verizon 4.3 update. You're fine flashing anything because you never took it, just follow the directions in each rom thread. You could flash those roms as well.
Sent from my HTC6525LVW using Tapatalk
Hello, I am using Nightlies for Paranoid 4.4 on Motorola Moto G rom, but I think this problem exsist on other roms. The problem is when I try to change volume in music player its verry delayed. Sometimes when I press volume up button once, it goes not by one, but all the way to max volume. Tried different roms, still same problem. So maybe someone had same problem and know how to fix it? thanks
UP
I have the same problem, there is also a delay while pausing the music.
Best to report it in the associated ROM thread.
This is a CM bug, the most part of ROMs is based on CM sources, because of this the Paranoid has this bug
Itachitops said:
This is a CM bug, the most part of ROMs is based on CM sources, because of this the Paranoid has this bug
Click to expand...
Click to collapse
From what I read on google, other phones also have this bug, even with stock roms after update to 4.4.4.
Hey guys, you who used stock 5.1 and custom ROMS that are having the latest Android version (5.1.1): what differences do you notice?
As we all know 5.1.1 is the latest version which fixes the memory leak, and Moto is still a version behind on 5.1.1: stock only is Android 5.1.
How would you compare stock to the latest Android version with the latest bugfixes and memory leak fix?
Would it be possible that Moto backported 5.1.1 fixes to stock 5.1?
Can a moderator edit "bases ROM's" to "5.1.1-based custom ROMS? I made a typo
Sparubens said:
Hey guys, you who used stock 5.1 and custom ROMS that are having the latest Android version (5.1.1): what differences do you notice?
As we all know 5.1.1 is the latest version which fixes the memory leak, and Moto is still a version behind on 5.1.1: stock only is Android 5.1.
How would you compare stock to the latest Android version with the latest bugfixes and memory leak fix?
Would it be possible that Moto backported 5.1.1 fixes to stock 5.1?
Click to expand...
Click to collapse
It is more a question of CM12.1 vs Stock ROM.
With the Stock Motorola Lollipop you have (at least in theory) a bug free ROM, it will work in every situation and scenarios.
Where with a custom ROM you will have more experimental features, a more tunable kernel and settings (that can either improve or break a ROM) and, to be honest, more support as they update almost every week where Motorola go very slow.
Pupet_Master said:
It is more a question of CM12.1 vs Stock ROM.
With the Stock Motorola Lollipop you have (at least in theory) a bug free ROM, it will work in every situation and scenarios.
Where with a custom ROM you will have more experimental features, a more tunable kernel and settings (that can either improve or break a ROM) and, to be honest, more support as they update almost every week where Motorola go very slow.
Click to expand...
Click to collapse
Yeah that's true. I was just wondering if the 5.1 version still has the memory leak which was resolved in 5.1.1. Also, CM12 based roms don't support notification tickers anymore, not even through Xposed so that's a bit pity too. But they do have features you can't find in stock or Xposed.
Just wondering which ROM gives the best performance, CM12 or optimized stock or just plain AOSP without any tweaks.
Sparubens said:
Yeah that's true. I was just wondering if the 5.1 version still has the memory leak which was resolved in 5.1.1. Also, CM12 based roms don't support notification tickers anymore, not even through Xposed so that's a bit pity too. But they do have features you can't find in stock or Xposed.
Just wondering which ROM gives the best performance, CM12 or optimized stock or just plain AOSP without any tweaks.
Click to expand...
Click to collapse
I can't say if Motorola fix the Memory issue or not. I can say too that some CM12.1 ROMs did have memory issues even at 5.1.1 but i think all are gone now.
About performance, a custom ROM for sure will bring you that. I'm not a big fan of motorola "optimizations" for our devices, in fact i would say they don't do at all.
It all depends really, you could get stock 5.1 with moggy kernel v12 which is very smooth being a linaro based kernel with other optimizations as well. (I was running that earlier today)
But you could also get a custom ROM such as blisspop. Which is very very poorly developed on our device.
A ROM that the developer uses as a daily driver is likely to be better than stock. However you'll find ROMs such as BlissPop where the developer does not run the ROM on our device and merely syncs with latest sources and uploads the builds without testing them first.
Those ROMs are likely to provide worse performance and definitely less stability than stock. Unless of course you flash a custom kernel over it, but then you've just got a sugar coated turd. And nobody wants a turd.
Sent from my XT1045 running CM 12.1 7/23 build with Optimus Kernel R38 using XDA Free mobile app
Travisholt92 said:
It all depends really, you could get stock 5.1 with moggy kernel v12 which is very smooth being a linaro based kernel with other optimizations as well. (I was running that earlier today)
But you could also get a custom ROM such as blisspop. Which is very very poorly developed on our device.
A ROM that the developer uses as a daily driver is likely to be better than stock. However you'll find ROMs such as BlissPop where the developer does not run the ROM on our device and merely syncs with latest sources and uploads the builds without testing them first.
Those ROMs are likely to provide worse performance and definitely less stability than stock. Unless of course you flash a custom kernel over it, but then you've just got a sugar coated turd. And nobody wants a turd.
Sent from my XT1045 running CM 12.1 7/23 build with Optimus Kernel R38 using XDA Free mobile app
Click to expand...
Click to collapse
YEs that is true, also there are some ROMs that are much more experimental then stable.
So a research would be need.
That being said, stock is always the safest bet but a nice custom ROM will be superior if he find one.
I'm personally very happy with Euphoria and the R35 version of the Optimus Kernel.
But you (@Sparubens ) would need to flash all the roms to find the one who fit you better, stock and non stock
It's worth considering the difference in Battery-life of Stock Firmware / ROMs in comparison to non-Stock custom ROMs. That could be an interesting thread.
Pupet_Master said:
YEs that is true, also there are some ROMs that are much more experimental then stable.
So a research would be need.
That being said, stock is always the safest bet but a nice custom ROM will be superior if he find one.
I'm personally very happy with Euphoria and the R35 version of the Optimus Kernel.
But you (@Sparubens ) would need to flash all the roms to find the one who fit you better, stock and non stock
Click to expand...
Click to collapse
I did flash almost every ROM here but there always seems to be an issue:
-CM12.1 is stable and fast, but doesn't have 4 tiles per row option in QS Settings and doesn't support notification ticker anymore (Xposed), SaberMod is smooth (Beeto) but there's a bug where you can't access SuperSU without dialing a code
- SlimROM wasn't a good experience when trying it to use as daily driver, sluggish and bad multitasking
- CM12.1 based ROMS like CrDroid and Euphoria I do really like, have some bugs like screen pinning causing reboot (CrDroid) and also no real Xposed support for CrDroid and Euphoria doesn't register all touches on the keyboard and makes my phone a bit hot, otherwise I would be very happy to have it as a daily driver, AICP was running okayish but there's been a bug for over a month that when opening the data quick menu, the percentage is misaligned, and it still hasn't been fixed.
- Stock 5.1 is nice, but it's a version behind 5.1.1 so that's not very nice either. Also heavily lacking in options, but I can use Xposed. Also there are 2 carrier labels on the lockscreen which makes no sense at all..
Also, in custom ROMS the torch doesn't seem to be functioning fully, the light density is not at it fullest. Sadly there seem to be some quirks with every ROM.
I'm ready to make compromises and have a ROM as daily driver which doesn't support notification ticker (basically all of them atm) but then there's also the torch issue sadly which pushes me more back to stock. But then again, nobody knows if stock still has the memory leak and opinions have been very different from person to person about stock 5.1.
Some interesting opinions over here, keep 'em coming!
@lost101 I personally think that there's no custom ROM that can match the battery life of stock, it has been impressive, surely on Lollipop.
Sparubens said:
Also, in custom ROMS the torch doesn't seem to be functioning fully, the light density is not at it fullest.
Click to expand...
Click to collapse
A solution for this problem seems not to be far away
http://forum.xda-developers.com/showpost.php?p=62028617&postcount=155
Sparubens said:
I did flash almost every ROM here but there always seems to be an issue:
-CM12.1 is stable and fast, but doesn't have 4 tiles per row option in QS Settings and doesn't support notification ticker anymore (Xposed), SaberMod is smooth (Beeto) but there's a bug where you can't access SuperSU without dialing a code
- SlimROM wasn't a good experience when trying it to use as daily driver, sluggish and bad multitasking
- CM12.1 based ROMS like CrDroid and Euphoria I do really like, have some bugs like screen pinning causing reboot (CrDroid) and also no real Xposed support for CrDroid and Euphoria doesn't register all touches on the keyboard and makes my phone a bit hot, otherwise I would be very happy to have it as a daily driver, AICP was running okayish but there's been a bug for over a month that when opening the data quick menu, the percentage is misaligned, and it still hasn't been fixed.
- Stock 5.1 is nice, but it's a version behind 5.1.1 so that's not very nice either. Also heavily lacking in options, but I can use Xposed. Also there are 2 carrier labels on the lockscreen which makes no sense at all..
Also, in custom ROMS the torch doesn't seem to be functioning fully, the light density is not at it fullest. Sadly there seem to be some quirks with every ROM.
I'm ready to make compromises and have a ROM as daily driver which doesn't support notification ticker (basically all of them atm) but then there's also the torch issue sadly which pushes me more back to stock. But then again, nobody knows if stock still has the memory leak and opinions have been very different from person to person about stock 5.1.
Some interesting opinions over here, keep 'em coming!
@lost101 I personally think that there's no custom ROM that can match the battery life of stock, it has been impressive, surely on Lollipop.
Click to expand...
Click to collapse
That's why we have a lot of roms outthere, everyone can choose what match better with everyone, if you want something without issues choose stock, but don't have the optimizations options, if you prefer the options, choose the one you consider is better, but always have to sacrifice something
Enviado desde mi peregrine mediante Tapatalk