Hi everybody, this is my first thread here.
I'm currently on stock 4.1.1 after getting s-off and supercid but then soft bricking trying to update hboot (I think I restarted my phone while it was updating) . Little bit put off trying to load a custom ROM for now (having to reconnect gmail accounts, redownload apps etc) but I'd obviously make the exception for 4.4.
I've seen a few unofficial CM11 builds are already out there in some form or another but my question is will there be an official CM11 for the HOS? If not what will be the closest thing to it? Someone that knows more about CM11 (in general), will it be long until they have a fully functional 4.4 ROM with all features working?
Thanks!
Cyanogenmod will finish cm 10.2 before moving on to 11
fatboyslimerr said:
Hi everybody, this is my first thread here.
I'm currently on stock 4.1.1 after getting s-off and supercid but then soft bricking trying to update hboot (I think I restarted my phone while it was updating) . Little bit put off trying to load a custom ROM for now (having to reconnect gmail accounts, redownload apps etc) but I'd obviously make the exception for 4.4.
I've seen a few unofficial CM11 builds are already out there in some form or another but my question is will there be an official CM11 for the HOS? If not what will be the closest thing to it? Someone that knows more about CM11 (in general), will it be long until they have a fully functional 4.4 ROM with all features working?
Thanks!
Click to expand...
Click to collapse
Its MOST likely, sense we are still part of the HTC "One" line. But Cyanogenmod Developers have stated that just because Google optimized android 4.4 for older devices that they still wouldn't go back and support them. But our device is a monster, and its never old to me! One thing I can tell you is the HTC Evo 4G wont be seeing official builds:laugh:
CM11 is already running faster and most stable than CM10.2, so i would imagine we'll start getting official releases at some point
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 am getting the itch to put on a custom ROM of my GS3, but I have a Fitbit One and would like for it to continue to update over the phone. I've tried CM10.1, but it appears that there is a problem with the BT4.0 and the phone doesn't want to try to connect to the fitbit. I'm not close to a computer much currently to update the fitbit.
TL: DR- Is there a working ROM where the BT4.0/BLE is working somewhat properly?
Thanks in advance.
I'm looking for the same thing. I switched back to a Stock variant to get BT4 working and the Stock ROM is total garbage after using Cyanogen Mod. I don't want to have to choose one or the other!
There is not a single ROM out there at the moment that has Bluetooth 4.0 working. Google has not released or included a lib file for it to work. Sure our devices have the hardware but the software has no clue how to utilize it. Maybe next version of android will have it.
The 4.1.2 Omega ROM was working for me. The ROM will need to be based off of Samsung's official as it will need their hacked Bluetooth stack - they worked directly wth Fitbit to get it up and running. I've since upgraded to the Omega 4.2.2 AOKP ROM and it no longer works (which I expected).
BLE
The only ROM that i've found with working BT4/BLE is the one by beanstown.. i do confirm it working just fine for my fitbit flex.
http://forum.xda-developers.com/showthread.php?t=1973982
I have a fitbit as well and I am trying to figure out what it would take to get it working with CyanogenMod. I flashed an unofficial 10.2 (4.3) and still no luck with the fitbit.
try the 4.3 version of CM in teh development section? I thought this was an added or fixed feature in teh newest version of android. not too sure though.
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
I've done a fair bit of rooting and flashing in the past, but got lazy
On my Galaxy S2, I used the simpler Cyanogenmod one click installer package, which rooted my phone and flashed CM10.1 / v4.3
A week ago I updated to CM11 / v4.4 using system update, and now I'm in hell, the cyanogenmod website lists CM11 for the GS2 as a present release snapshot, and it's riddled with problems
I need a daily driver, not an experiment and I really need to go back to my old 4.3 ROM
I understand that there's no way to do that via system update
So my question is,
Can I simply run the cyanogenmod one click installer again and get CM10.1 (which the installer still installs)
Or would that cause problems?
Thanks in advance
Cheers