HI guys,
Need your help with something, i updated my GN to 4.2 yesterday was on stock android 4.1.2 with unlocked bootloader and unrooted, i installed the 4.2 update after i was notified by the phone about the update everything went well no hiccups no stops and restarting of the phone or anything. Everything appeared to work well until i got home in the evening and tried to bluetooth some stuff from my wife's S1 to my GN. When the phone tries to recieve the bluetooth toggle comes on and off about ten times and the phone acts all crazy asking if yuo want to accept file or not and a message box appears about sending google a report that comes up and goes comes up and goes. Is there any recommendation on how i could possibly fix this.
Edit: Also i can send files through bluetooth, i can't receieve. Also restarting the phone or taking out the battery for a minute didn't help
Thanks
Same problem here
viveksn said:
Same problem here
Click to expand...
Click to collapse
What I did was use the galaxy nexus toolkit and flashed 4.1 back on my phone and did the update again - so far so good with no issues
Related
Hello,
i've been experiencing troubles making calls since upgraded to 4.2, tried 4.1.2, hangs up immediately call log says 0 seconds.
there is a topic about it at google issues, but i thought if i'll bring it here it will get some more attention. it seems that removing the SIM and re-inserting it, fix it, but after restart, problem restore.
only few service provider seems to suffer from this issue.
here is the topic: code.google .com/p/android/issues/detail?id=39904
thank you!
Taufik15 said:
Hello,
i've been experiencing troubles making calls since upgraded to 4.2, tried 4.1.2, hangs up immediately call log says 0 seconds.
there is a topic about it at google issues, but i thought if i'll bring it here it will get some more attention. it seems that removing the SIM and re-inserting it, fix it, but after restart, problem restore.
only few service provider seems to suffer from this issue.
here is the topic: code.google .com/p/android/issues/detail?id=39904
thank you!
Click to expand...
Click to collapse
Try factory reset and pull the battery for a few minutes then put it back
Sent from my Galaxy Nexus using Tapatalk 2
Sorry for the delay,
I tried this and same issue appearing..
any other suggestions?
Bump....
Download a stock ROM from Google Developer, and flash the new ROM.
^^^xdabilly said it.
I just did this recently myself having gone 4.0.3 to 4.1 to 4.2 via ROM wipes and flashes only. My phone doesn't misbehave anymore since I completely wiped it and flashed Google's official image and then went on about rooting from there and now back to Purity ROM.
Hey everyone,
So two night ago I received a notification on my GS3 saying a new update was out.
When I tried installing the update it rebooted into recovery and failed at 24%....weird. I was running Rogers stock rom and recovery at the time so this shouldn't have happened, and I would like to know why for future reference.
I also tried updating via samsung kies. But when I tried this, it said my device wasn't compatible to update via kies????
So I ended up download the LK4 update off sammobile website and installed it using odin.
Anyways, I now have the new update installed. I've noticed two weird things:
1. When I go to about phone in settings and go into software update, it shows a screen "checking for software updates..." and doesn't go away unless I press back or home button. Why can't I search for new updates????
2. My google now voice isn't working. It recognizes what I say to it but when it gives the flashcard response, it doesn't talk back like it normally does. I have it set to English US, and yes my media volume is up at full volume.
Anyways I'm a little frustrated at this point. I can't figure out how to fix these problems so any help would be greatly appreciated. Thanks
So I just rooted my Samsung sgh t-989 the tmobile one. I put TWRP 2.5 and have Cygenmod 10.1 running. I was all excited because I have notdone this kind of stuff since middle school.
But The problem is my Bluetooth is "disabled" When i try to turn it on it just goes right off, I have no idea where to start to fix this problem. I already tried google and searching the forums but no solutions.
Which date of cm10.1 did you flash? You need to give more details. Flash a custom kernel? What's your radio you're using?
Denta87 said:
So I just rooted my Samsung sgh t-989 the tmobile one. I put TWRP 2.5 and have Cygenmod 10.1 running. I was all excited because I have notdone this kind of stuff since middle school.
But The problem is my Bluetooth is "disabled" When i try to turn it on it just goes right off, I have no idea where to start to fix this problem. I already tried google and searching the forums but no solutions.
Click to expand...
Click to collapse
I've had exactly the same problem, using the CM 10.1 RC5a.
Bluetooth will do as you described - be disabled, when clicked on, will jump to off again.
Restarting always fixes it momentarily.
If BT is on, and successfully connects to my car, and I'm able to place a call, first no one can hear me, the call is dropped, and BT shuts off to remain permanently disabled til I reboot the system.
After a reboot, its usually ok for a couple hours.
Lots of other users are having the same problem....
Denta87 said:
So I just rooted my Samsung sgh t-989 the tmobile one. I put TWRP 2.5 and have Cygenmod 10.1 running. I was all excited because I have notdone this kind of stuff since middle school.
But The problem is my Bluetooth is "disabled" When i try to turn it on it just goes right off, I have no idea where to start to fix this problem. I already tried google and searching the forums but no solutions.
Click to expand...
Click to collapse
Also, flashing this fix now, will report back:
http://forum.xda-developers.com/showthread.php?t=2174100
I wiped dalvik/cache, flashed the BT fix, fix permissions, then rebooted.
Just CM 10.1 RC5a, UVMC6 radio, I upgraded firmware using the UVMC6.aio.tar.md5 file made by Mikeyman
Hope it works - really tired of having to reboot every time i want to make a call over BT car audio...
HISTORY oforoub
aaronchili said:
Also, flashing this fix now, will report back:
http://forum.xda-developers.com/showthread.php?t=2174100
I wiped dalvik/cache, flashed the BT fix, fix permissions, then rebooted.
Just CM 10.1 RC5a, UVMC6 radio, I upgraded firmware using the UVMC6.aio.tar.md5 file made by Mikeyman
Hope it works - really tired of having to reboot every time i want to make a call over BT car audio...
Click to expand...
Click to collapse
36 hours on this and no BT crashes!
Faster connection to car audio, and call stability is much better.
Also remember after reboot to delete all devices, and re-add them.
I've got an unrooted, completely stock, unlocked Galaxy Nexus. A few weeks ago, I updated it to 4.3 when prompted by the usual notification ("System update downloaded: Touch to install"), and the update went fine.
However, since then I keep getting the same notification again, and pressing it seems to reinstall 4.3. The notification then reappears after a week or so. I know the update isn't failing, as I can see in the settings that it's running 4.3.
Does anyone know why it might be doing this, and how I can stop it?!
6chrisp said:
I've got an unrooted, completely stock, unlocked Galaxy Nexus. A few weeks ago, I updated it to 4.3 when prompted by the usual notification ("System update downloaded: Touch to install"), and the update went fine.
However, since then I keep getting the same notification again, and pressing it seems to reinstall 4.3. The notification then reappears after a week or so. I know the update isn't failing, as I can see in the settings that it's running 4.3.
Does anyone know why it might be doing this, and how I can stop it?!
Click to expand...
Click to collapse
I have the same problem
Probable solution
I found a solution in this thread
http://forum.xda-developers.com/showthread.php?t=2413535&page=11
looking for some suggestions as to what I can to to correct these issues. I have a 210R that I screwed up probably flashed something I should not have... to restore I went to sam mobil and downloaded the latest firmware ( T210RUEU0COB1), installed using Oden and restored the Tab. since I have done this (and yes I redownloaded the firmware and reinstalled to make sure it was a good file and installation) the tab now will boot up fine, but will come up with the error messages Process com.androis.systemui has stopped and often com.sec.android.flashbarservice has stopped as well clicking ok will sometimes let me continue, other times will simply reboot. If it lets me continue whatever app I am using will quickly stop as well and the tab reboots. in addition to this the WiFi barely recieves any signal unless I am almost on top of the router. it is currently stock. Any suggestions or help will be greatly appreciated.
Having the same problems minus wifi issues
jdsatyr said:
looking for some suggestions as to what I can to to correct these issues. I have a 210R that I screwed up probably flashed something I should not have... to restore I went to sam mobil and downloaded the latest firmware ( T210RUEU0COB1), installed using Oden and restored the Tab. since I have done this (and yes I redownloaded the firmware and reinstalled to make sure it was a good file and installation) the tab now will boot up fine, but will come up with the error messages Process com.androis.systemui has stopped and often com.sec.android.flashbarservice has stopped as well clicking ok will sometimes let me continue, other times will simply reboot. If it lets me continue whatever app I am using will quickly stop as well and the tab reboots. in addition to this the WiFi barely recieves any signal unless I am almost on top of the router. it is currently stock. Any suggestions or help will be greatly appreciated.
Click to expand...
Click to collapse
Dude my tablet is in the same state I use. The many reboots. All apps/process stopping for no reason. Funny thing is this started happening to me after I received an OTA update for 4.4.2 and flashed it. So basically the official update released by samsung messed up my phone. Somebody please respond with suggestions/solutions.
Sigh.... guess I'll just use it as a paperweight ..