I just installed the LiquidSmooth Jellybean 2.0 Beta Rom. I have encountered 2 issues.
1) Voice Search does not work. It seems to listen forever and never do anything.
2) Google Music does not sync.
I tried to post on the specific forum but I can't since I'm a new user. I would really just like to see if others are experiencing the same issues, and if so alert the LiquidSmooth guys. These are by no means show stopper bugs. All in all, its a very impressive Rom.
Related
Since rooting my gnex and trying out the various roms, I've noticed some issues with certain ICS and Jellybean roms. It usually only affects the play store and Facebook and maybe some other apps here and there. The issue is persistent on wifi and 4g and I've got no idea what the cause is.
When I select an app to download in the store it normally takes 2+ minutes or more to actually start the download. Same thing with Facebook, like trying to view pictures on posts. I've encountered these problems on aokp build 40 and milestone 6, slim ics 4.2, and all jellybean roms. Its annoying enough to make me go to a known reliable rom. If anyone has any clues or things to try I am all ears. Thanks.
Sent from my Galaxy Nexus using xda premium
Yesterday, I flashed CM10.0.0 stable release via "ROM Manger Premium" app by ClockWorkMod from Play store after rooting my T-mobile Galaxy S3 along with app provided Gapps package. Everything works great and I was really liking this ROM and considered this as my primary ROM. However, the excitement was short lived when I called my girlfriend using skype and viber. I had very low volume issue on viber(according to my girlfriend) and weird sound(according to my girlfriend) issue on skype on my girlfriend's side of the call. Those problems went away when I hung up the call, reflashed my stock TouchWiz 4.0.4 on my phone and immediately called her back. I was wondering if any other people has or had the same problem and is there a fix on that issue? Thanks in advance.
sincerely,
DroidNoob74
Hi,
This is a member of the Viber R&D Team.
It sounds like the typical Custom ROM issue - some custom ROMs alter the microphone definitions of your phone, causing Viber not to recognize the phone's microphone properly. That is the reason that Viber cannot transmit your sound to the other side. We discussed this issue in detail with our users in this thread on XDA Forums: http://forum.xda-developers.com/showthread.php?p=25865775#post25865775
Please note that in that thread, a workaround was suggested *by a user* that seemed to have solved the problem for Galaxy S+S2 users.
Let us know if you have any questions.
Thanks,
Viber
I have a d2tmo GS3 and been running CM10 nightlys. It is alright but I sometimes have BT trouble between the phone and the car and so I am looking to see if there is another ROM that will work better for me.
I am mainly looking for a relatively vanilla JB ROM. Don't need or care to much about fancy stuff. Its ok if it has extra features as long as they don't cause problems. More than anything else, I want a stable ROM that works correctly.
There are two problems I am having with BT.
The first is that the phone does not always auto connect for music with my car. It used to also have trouble connecting for phone, but a recent nightly build seems to have fixed that.
The second is that when it does connect, it automatically starts playing a random file (it did this with the stock ROM as well). For some reason my Nexus S didn't do this with either ICS or JB vanilla Android. My understanding is that this is cause the phone is getting an autoplay signal from the car. I am hoping there is an Android version that can be set to ignore this request.
Frosty.
aviphysics said:
I have a d2tmo GS3 and been running CM10 nightlys. It is alright but I sometimes have BT trouble between the phone and the car and so I am looking to see if there is another ROM that will work better for me.
I am mainly looking for a relatively vanilla JB ROM. Don't need or care to much about fancy stuff. Its ok if it has extra features as long as they don't cause problems. More than anything else, I want a stable ROM that works correctly.
There are two problems I am having with BT.
The first is that the phone does not always auto connect for music with my car. It used to also have trouble connecting for phone, but a recent nightly build seems to have fixed that.
The second is that when it does connect, it automatically starts playing a random file (it did this with the stock ROM as well). For some reason my Nexus S didn't do this with either ICS or JB vanilla Android. My understanding is that this is cause the phone is getting an autoplay signal from the car. I am hoping there is an Android version that can be set to ignore this request.
Click to expand...
Click to collapse
I'm actually having the same problem with auto-connect I have a thread going as well. I am running wicked JB which is TW based so close to stok and thats my only problem so far
Just to be clear, when I say "vanilla JB" I mean JB like google intended, not neccesarilty GS3 stock rom.
psykhotic said:
Frosty.
Click to expand...
Click to collapse
Does Frosty allow your phone to ignore BT autoplay requests?
Wicked
Sent from my SGH-T999 using xda premium
Frosty or Wicked. Both have been very stable for me.
Frosty is incredible give it a shot.
Anyone noticing they are having a problem with creating a station on pandora? When ever I do it I get a quick flash to the add station section then nothing happens. No keyboard pops up. Its like I never clicked the create station button. It just goes right back to my station list.
Im on the AT&T GS3. Rooted. Android 4.2.1 CyanogenMod 10.1 Jan 16 build. Stock kernal. I haven't updated because of ongoing bluetooth problems (A2DP).
Any help would be greatly appreciated.
-JZ
Yes i have that problem also and i think a few others too. I had it while running jellybam and have it on rootbox so i'm not sure what the source of the problem is.
I think its due to Pandora not being fully updated to 4.2.1.
This problem doesn't happen with Pandora 4.0. I downgraded, and am having less issues.
Just did it on Pandora v4.1.2. No problems here. Running latest AOKP and KT747.
Using the SynergyROM for AT&T, we all seem to be getting the "+" sign prefixed to all of our incoming calls. This is a huge PIA to an otherwise very well done ROM. I recall having this problem months ago with a different ROM, but I can't for the life of me remember which one it was and what the fix ended up being. Can anyone remember any of the other ROMs they have seen this issue with? I know Task650s build had this problem, but it seems it's fixed in his ROM now.
Would love to know the answer to this as well. I tried SynergyROM and liked it quite a bit but this among some other annoyances pushed me to finding other ROMs.
I had this issue with one of Task's first 4.2.1 builds. Been fixed for a long time there.
I used a combination of contactscleanup and prefixer in the interim to handle the +.
It was one of the stock builds that had this problem, just wish I could remember which one.
I am also having this issue. I am on AT&T, GalaxyMod RLS16 ROM, KT Kernel(2/7 version). Android version 4.1.1.
The "+" sign is causing problems for me when my allowed contacts are not ringing through to me when the phone is in Call Block mode (I keep it this way while I am at work).
If anyone has any suggestions has a solution that I may have missed while searching, it would be appreciated if you would share. Thanks!