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: ...
Related
I got my new black verizon s3 yesterday and i love it, buttery smooth. I was coming from a HTC Thunderbolt. I had rooted my thunderbolt, however since rooting that phone, i noticed that data connectivity didnt seem to be as stable as the non rooted version of that phone.
Here is my question, do you guys recommend rooting this S3 phone? Has it effected the data connectivity (dropped signals, etc)? Some advice and direction for this new S3 user would be helpful from some of you all who have been S3 users for a while. Thank you!
I would recommend rooting since there is a lot of support for the device. Data should be fine but there have been some problems either user related mistakes or bugs in a ROM. Those problems are fixable. Most of the ROMs are stable even the 4.2 ROMs.
i rooted and i think its worth it. it is easy to do and pretty low risk. I did mainly because i wanted to under clock and get better battery life. I haven't noticed any issues regarding loss of data or anything. i run into some issues at times because i try different kernals and roms that are not 100% in their stable phase. But the act of rooting itself isn't going to cause you any issues.
thanks guys, i am going to root the phone tonight after work. i browsed thru the rooting instructions for the jellybean update software (which i got when i activated my phone). I just didnt want to run into unstable data connections like i had with my thunderbolt.
Can you guys recommend any good 4.1 Roms as well as 4.2 roms? Also what is the difference between android 4.1 & 4.2?
It depends on the ROM as all 4.2 ROMs as of now are AOSP ROMs while the 4.1 ROMs are either TW based or AOSP based.
TW is ok... better then Sense IMO, however I like the stock ASOP feel. I will give a 4.2 rom a try. can you recommend a popular, 100% working 4.2 ROM? I looked in the dev section and there are so many Roms to choose from........ 24 hours of having my S3 and i LOVE it! so buttery smooth!
Blackbean 7 Is the most stable of the bunch as of now.
Ok. If you are going to root and Rom there are some things you need to know.
Your going to want to unlock your boot loader. And make an imei backup incase you lose it during a flash.
Search those up and get them done and your good to go
Via my Google Galaxy S3 running magic beans
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
thanks guys, i rooted the phone with no problems last night. got root and unlocked bootloader. I wanted to try out CM10 so I fla**** it this morning. So far so good. really like 4.2
bsdesign0000 said:
thanks guys, i rooted the phone with no problems last night. got root and unlocked bootloader. I wanted to try out CM10 so I fla**** it this morning. So far so good. really like 4.2
Click to expand...
Click to collapse
Do you mean Cm 10.1? Because if you flashed cm10 you're still on 4.1. Cm10 has a stable release while cm10.1 is still on nightlies. I've been running 10.1 nightlies for about a month and have only noticed very minor issues. So minor I can't even remember what they are.
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.
Question #1: GPS
I have the Samsung Galaxy S 4G which has been long rooted and I've installed a few roms now on it. Recently I upgraded to Revolt 4+ which is my first attempt to find a Jelly Bean ROM that will work for me. Well, I love it. Only problem is that it seems it doesn't have GPS? Google Maps work but Navigation doesn't follow me which I'm guessing means it's using internet to "find" me. There's no GPS flashing icons nor are there any settings for GPS. Is there anyway to get it working or is it just not working for this ROM?
Question #2: Aries?!
Many of the roms mention "Aries's common bugs" but google searching it gives me nothing. Where can I find information about Aries?
Question #3: The latest fully-working ROM?
There are soooo many ROMs to choose from for the SGS4G that I don't know what to look for. I found and have been using THIS page but not sure how outdated/accurate it is. Anybody know the best/most recommended ROM right now that has all the main parts working? GPS, WIFI...etc? I know wifi calling always has issues but not important.
:good: to anybody who is able to help with any of the above!
Hi.
#1 All JB ROMs (meaning 4.1.2 and above) have Aries kernel.
it is faster than Herrig kernel used before, and should be more stable, but, no developer was able to make GPS work with it. so, there's currently no JB ROM with a working GPS.
#2 If you want a working GPS you will need ICS (4.0.3/4.0.4) ROM :
CM9/AOKP/Slim/MIUI/Ultragen etc.
I'm a MIUI freak so I can say I love HebMIUI which is an upgraded MIUI version I came up with. you can try it (see my signature) or any of the others I mentioned.
Slight addendum to #1. Not entirely true. Some of the earlier JB ROMs were still Herring. The various 4.2 Wifi-bugs were on Herring. Any ROM where they tell you to do the 4.1.2 JB if you wanted Wifi, it's a Herring kernel. For that matter, I believe we've only had compiled 4.2.2 and above Aries here. So if the ROM is 4.1.2 JB, it's Herring. If it's 4.2.2 without working Wifi, it's probably Herring. If it's 4.2.2 with Wifi or 4.3, it's probably Aries.
Agree on ICS/GB for GPS though. HebMIUI or Ultragen 1.01 (DO NOT USE ULTRAGEN 1.00 AND POST BUG REPORTS) are probably your best ICS options.
THANK YOU both for clearing up alot of stuff for me. Thank you x2 for itzik2sh for recommending HebMIUI. I have it installed and I love it sofar. Hopefully somebody figures out JB GPS eventually.
I'll still check back here if anybody else has anything else to throw in.
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
Hi, it's been almost a year since I last installed a new ROM on my rooted/unlocked S3, and to make a long story short, I'm trying to figure out how to flash to a TW based rom (I'm on a 4.3 version of PACman ROM right now). Not having kept up with anything for the past year, I'm surprised at how complicated everything seems now, so I'm hoping someone can offer any pointers on how to avoid screwing anything up.
I've used ASOP/CM based ROMs for almost the entire time I've had the phone and as good as they are, I'm just having problems with almost daily reboots now, so I want to see if a TW based ROM will be better.
I'm on VRBLK3 baseband if that matters.
I'm ok losing all my data as I have everything important (SMS, whatsapp texts, etc) backed up.
Thanks for any help.
bruins22 said:
Hi, it's been almost a year since I last installed a new ROM on my rooted/unlocked S3, and to make a long story short, I'm trying to figure out how to flash to a TW based rom (I'm on a 4.3 version of PACman ROM right now). Not having kept up with anything for the past year, I'm surprised at how complicated everything seems now, so I'm hoping someone can offer any pointers on how to avoid screwing anything up.
I've used ASOP/CM based ROMs for almost the entire time I've had the phone and as good as they are, I'm just having problems with almost daily reboots now, so I want to see if a TW based ROM will be better.
I'm on VRBLK3 baseband if that matters.
I'm ok losing all my data as I have everything important (SMS, whatsapp texts, etc) backed up.
Thanks for any help.
Click to expand...
Click to collapse
If you like TW rom then I suggest you try
Alliancerom http://forum.xda-developers.com/showthread.php?t=1973982
It's TW rom with a lot of customization, just follow the instruction in the OP page.
buhohitr said:
If you like TW rom then I suggest you try
Alliancerom http://forum.xda-developers.com/showthread.php?t=1973982
It's TW rom with a lot of customization, just follow the instruction in the OP page.
Click to expand...
Click to collapse
Great, thanks for the help. Can I upgrade my modem to the latest version as well?
bruins22 said:
Great, thanks for the help. Can I upgrade my modem to the latest version as well?
Click to expand...
Click to collapse
You could but don't go pass VRUBMF1 modem. VRUBMF1 is where you should upgrade to.