Related
Hey,
I've tried almost all 2.2.1 ROMs now, frost, darky, atriarc, loki yet on none of these ROMs could I get the aGPS to work. It works flawlessly on 2.2 ROMs otherwise... What could be wrong?
I've tried faster fix, gingerbread.zip and sgps.zip from the forums, etc. already..
Sent from Bionix on Vibrant
then go back to 2.2... i don't see much change between 2.2 and 2.2.1 since we had voodoo on 2.2
but w/e
My gps was perfect when I was on Frost, after flashing sgps. Have you tried the hardware fix?
adyscorpius said:
Hey,
I've tried almost all 2.2.1 ROMs now, frost, darky, atriarc, loki yet on none of these ROMs could I get the aGPS to work. It works flawlessly on 2.2 ROMs otherwise... What could be wrong?
I've tried faster fix, gingerbread.zip and sgps.zip from the forums, etc. already..
Sent from Bionix on Vibrant
Click to expand...
Click to collapse
I have Simply Honey 2.5 with GPS fix plus there is another forum here:
http://forum.xda-developers.com/showthread.php?t=878970
This one has made my GPS best its ever been and probably best it will ever be considering it is Samsung..
Well, I did that immediately when I noticed that the 2.2.1 ROM isn't locking on... I had just replaced back the FFC mod camera and then I was planning to run 2.2.1 so that I can benefit from its camera firmware. So I thought maybe I screwed up the contact.
But that didn't happen. Once i flashed 2.2 back, i got a GPS lock in 15-17 seconds on every cold start.
Installed the sGPS.zip and Gingerbread.zip too, alternatively, and together, also done an ODIN and then fresh install, but none of it helps... Tried fasterfix too for India...
Anyone else facing this problem ???
Hey guys could anyone help me out, I received a refurbished phone from Verizon 5 days ago and it keeps rebooting. I managed to root my phone using "BAMF GingerREMIX v2.0 Beta #6", Radio: 1.39.00.0430. The most I can use my phone is for about 10 min. unless I leave plugged into a charger. Can anyone help me out???
Are you sure your battery is any good?
Yeah my battery is good, i got a brand new one and its still acting up..
Change the radio to the mr2 radio. Seems the most stable of the gb radios. That might help
Sent from my thunderbolt
This happened to me as well as soon as the screen went off. Rebooted. If I kept playing with it it was fine.
Had to go back to Froyo roms because of it. Happened with MR2 and 2.5 radios.
Sometimes when I mess with the kernel settings a lot this will happen. Try flashing a new kernel or even the same one and see what happens.
Mine has started doing the same thing after receiving refurbished from VZW. My old one never rebooted with same setups. Something quirky going on with it. I can flash back to stock and stops. Its not the rom or kernel i'm using because i have tried all combinations that used to work flawless on old device.
So after updating to the 1.2BL and installing illuminate 1.5 i had noticed that my tab would not wake up after going to sleep. I had to hold down power and fully restart the device in order to get it going again.
I assumed it was because of illuminate so i wiped data/cache/dalvik and reinstalled with no luck. So i decided to wipe everything including system, repartition and then reinstall....still no luck. After updating to 1.6 and 2.0 with the same problem i figured I'd try bottle of smoke..... Well the same issue remains.
The tablet goes to sleep, and then will not wake up again with out a restart.
I had zero problems when i was on 1.1 and running other roms including stock, tnt lite, vegan tab and CM7/CM7 nightlies.
Installing a wifi lock app stops the device from sleeping and fixes the problem. However that isn't a permanent fix. I'm not sure if the problem is related to the 1.2 bootloader or Honeycomb.
Is anyone else having the same issue? Any ideas on a fix?
edit: also adjusting overclock settings doesn't make a difference
I am not sure on how to fix this, but since the Honeycomb ROMs are still in Alpha (which means they are still in development) it is most likely the ROM, or it may be just your specific G-Tablet reacting weirdly. I would suggest, if its that big of a problem, to switch to a new/different ROM and wait until they have Honeycomb stabilized. Hope this helped
(actually responding here as I got PM'd as well) I don't really know this ROM too heavily since it's not mine, but even the HC alphas have differences as far as the kernels in use are concerned. It could just be a "known issue", but you might be better off posting to the modders dev thread or PM'ing him to be sure. I haven't heard of this issue, but again I don't scan his thread heavily.
What I can tell you is that sleep of death (SOD) issues have occurred on Froyo ROMs for a long time. It's one of the things that custom kernels attempt to minimize.
Thanks for the response mate. I actually switched from illuminate over to bottle of smoke because I thought the rom may be the issue. But I'm still having the same problem
Sent from my DROIDX using Tapatalk
SOD is one thing I can't replicate on BoS, at least with my minimal testing. It was a big problem for me on the 4349 stock kernel - so much so that I started using custom kernels on TNT Lite (first) and then later on Mountain Laurel.
roebeet said:
SOD is one thing I can't replicate on BoS, at least with my minimal testing. It was a big problem for me on the 4349 stock kernel - so much so that I started using custom kernels on TNT Lite (first) and then later on Mountain Laurel.
Click to expand...
Click to collapse
yeh i haven't heard of anyone else having the same issue. At least not with honeycomb roms. I'll see if i can pull some logs to see if i can see anything from that
interesting update on this.
I nvflashed back to bootloader 1.1 with the stock tap n tap software.
Wifi turned off, and the tab wakes from sleep just fine like it should.
I flashed the latest RC1 CM7 rom for BL 1.1, and the tab will not wake from sleep like it was doing before. Unless the wifi is forced on, the tab will have to be hard reset when the screen is turned off.
I flashed Vegantab (froyo) and once again. No problems. The gtab wakes just fine.
The biggest thing is that i was using the old BL1.1 CM7 nightly builds before switching to honeycomb and i never had any problems with those.
So it seems there is something in the honeycomb and latest CM7 roms that is causing the sleep of death problem
Assuming this isn't a software bug, try boosting the min CPU frequency.
rajeevvp said:
Assuming this isn't a software bug, try boosting the min CPU frequency.
Click to expand...
Click to collapse
yeh i tried messing with all that stuff before with no luck.
I'm actually selling the tablet anyway. I've got vegantab running on it. Which isn't ideal but it's the only rom where ALL features of the device work fine, and it doesn't die when the screen is off
SOD Illuminate
Hi,
I did have the same problem over and over again whenever I replace CM7 or Vegancomb. It is just for the 2.3.4 roms with 1.2 bl. Froyo to HC, I never have them. The cure is to nvflash 4349 then reflash any Froyo rom or HC on it. For this matter, I dont like 2.3.3 or 2.3.4 versions. If you use CM7 or Vegan, it is a must to go back to 4349 first before going to diferent roms. This is one of your instructions Roebeet. By doing so, you will never have problems. I notice this first when I flashed CCv6 from Vegan and then, I got curious why. Then I repeated the same with other roms, it dd the same. Be careful with the 2.3.3 and 2.3.4. Ooops, 5274 and HC By the way yield CWM looping.
I'm using Aura right now, and randomly my phone these past few days have been defaulting to speakerphone on when I place a call or pick up a call. It's very very irritating. I'm not sure what's going on as I haven't downloaded any new apps or anything that would affect the speakerphone. Anyone have any ideas or have come across this issue? I would like to not have to reflash everything again, but that's just me...
That's weird im running Alien Rom and it just recently started doing that to me as well.
Sent from my [email protected] Atrix - OC 1.1ghz
chriscerv90 said:
That's weird im running Alien Rom and it just recently started doing that to me as well.
Sent from my [email protected] Atrix - OC 1.1ghz
Click to expand...
Click to collapse
see: http://forum.xda-developers.com/showthread.php?t=1242704
so.. ROMs are Alien, Aura, πCrust
I'm using faux123 kernel 0.1.7
Do you guys have GO SMS Pro? I recently got an update today which states in the chance log that it fixes this problem! Hope that helps.
chriscerv90 said:
That's weird im running Alien Rom and it just recently started doing that to me as well.
Sent from my [email protected] Atrix - OC 1.1ghz
Click to expand...
Click to collapse
Do you use GO SMS Pro? Someone in another thread said it might be that issue...but I don't know.
I know there are several posting about Vibrants shutting down on its own even when it is fully charged, but, most of the posting are about rooted phones. I am experiencing the same problem but with a stock Vibrant upgraded to 2.2 Froyo. Is there a fix for this problem? I just experienced this problem twice today already and I'm hoping stock Vibrant owners might have a solution.
I have also had spontaneous shutdowns and reboots using CM. I tried two different ICS builds for a while (Onecosmic's and CM9 Kang) and it didn't happen with either of them, so maybe something about ICS fixes this. I'm waiting for CM permissions management to appear in an ICS build, then switching over for good.
cashmundy said:
I have also had spontaneous shutdowns and reboots using CM. I tried two different ICS builds for a while (Onecosmic's and CM9 Kang) and it didn't happen with either of them, so maybe something about ICS fixes this. I'm waiting for CM permissions management to appear in an ICS build, then switching over for good.
Click to expand...
Click to collapse
I'm pretty sure in the OP the guy is looking for help from people on a stock vibrant, unrooted on 2.2...
As far as the random shutdowns go, I would try to factory reset the phone and let the phone sit for about 5-10 minutes after doing so before reinstalling apps and whatnot.
Sent from my T959 using XDA App
dustinkh said:
I'm pretty sure in the OP the guy is looking for help from people on a stock vibrant, unrooted on 2.2...
As far as the random shutdowns go, I would try to factory reset the phone and let the phone sit for about 5-10 minutes after doing so before reinstalling apps and whatnot.
Sent from my T959 using XDA App
Click to expand...
Click to collapse
I have put my phone back to JFD via Odin quite a few times, let alone resets, so I wouldn't expect much from that. There will apparently never be a stock ICS for the Vibrant. If the underlying problem is indeed fixed in ICS, the OP may want to make the leap to a good rom at some point.
My GF's phone was on stock 2.2 Froyo and shutdown incidentally, it actually just cut power, black screen suddently. Tried two battery and did the same, reflash to VJI6 and JFD and didn't help at all, but after flashing to Bionix 1.3.1 somehow the problem is gone, weird though
Spontaneous halts and reboots indicate a bug in the kernel or drivers. I don't know what bionic uses. ICS kernels are from the 3.x series of Linux, and are incompatible with older roms. Changing ketnel amd/or radio driver might be a way of attacking the problem short of changing roms. I've changed radios with CM7 but still get the halt/reboots.
A spontaneous shutdowm could also be cause by the battery making bad contact.. try smacking or dropping the phone and see if it happens
sent from the xda app on my android smartphone.