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.
Related
Hey guys, bit of a weekend brain teaser for you guys...
My rotation function just stopped working completely a day or two ago. I dont know if its worth mentioning but I actually never use auto-rotation (I just personally dont like/need it much). However, certain programs; Youtube, games, have usually served their proper rotation function when in use.
I've been running SC 2.9.2 with jt's ec10 kernel for quite some time now without any flaws. No changes were made to the phone before the issue.
Kinda sucks not being able to watch Youtube in full screen...
Any ideas?
Interesting. Mine stopped working a couple of days ago as well, also using SC 2.9.2. I'm using jt's 4/7 kernel. I've tried reinstalling both the rom and kernel with no success. In addition to the rotation my compass also does not work, so both the accelerometer and magnetometer have failed. It happened while using Google Nav in walking mode, where the phone froze and became unresponsive. After about 10 minutes of no response I pulled the battery and afterward noticed the problem. I'm planning to revert to stock to see if it helps tonight.
whereas im relieved to know that someone else is on the same boat, i really hope that it doesnt come.down to doing a full back to stock wipe :/
it would be nice to know what caused the malfunction...
Sent from my SCH-I500 using XDA App
Mine's working again after going back to EB01 briefly before going to EC01. I was planning to try out EC01 anyway and the brief revert to EB01 is part of the procedure.
I have had VirusRom installed for about a week now. Overall I love it.
Here is my problem though. When I am making a call the screen will lock. I have to push the power button to bring back up the screen in order to hang up the call.
Shouldn't the proximity sensor know when I pull it away from my face so I can hang up the call? It did before I went to this rom, was still using stock rom at that point.
Anyone know of a way to fix this problem? I have tried to post this question on the VirusRom forum, Since I think it is a bug with the rom, but am not allowed. It says you need 10 posts to be able to do that, Still I get that too even though I am over ten posts. Oh well on that though.
This could be a deal breaker for me and VirusRom. As it is quite frustrating to me. If anyone has any thoughts on how to get around this I would be thankful.
It's due to the kernel Virus installed in teh rom. It's one of Ziggy's first kernels and it has a bug that prevents the screen from turning on after/during a call as you describe.
Fix: Install a new kernel.
There are several on here to use, or you can search PPCGeeks / Ziggy to find his new kernels, which he has now fixed the proximity sensor issue.
Thanks for the answer. I downloaded kernal manager from the market. Any specific recommendations for a kernel? Adrynalyne's seem to be the most stable, but maybe I should stick with a stock kernal.
You can't go wrong with one of Adry's kernels. You should start with one those.
Sent from my BAMF'd T-Bolt
I had the same problem. I installed the new radio which was supposed to fix it and it did. But Im having trouble with the data connection, so I flashed back to the stock radio.
Ziggy's new kernal upgrade has fixed this issue. Id suggest downloading that. It works great and super crisp and fast over the version that came with the ROM and the proximity issue is fixed, been testing it for myself and all is good.
Check the VirusRom thread for info.
Ok, So I flashed one of Adrynalyne's kernals and now I don't have 3g or 4g. Just 1x. So do I flash another kernal, maybe the stock one, and the problem is solved? That will put it back the way it was right?
nope that did not work, I flashed Adrynalyne's stock rom and still just 1x. What have I done? What do I need to do to put it back? SInce I keep rom backups everytime I flash a ROM, I am going to flash back to the previous version that did have 3g and 4g working. I hope that works. The kernal is part of the ROM, correct?
Now this is getting frustrating. Flashed back to the previous working virus rom the one I had before the kernel update, and it still is only 1x. Wouldn't the kernel be part of the rom? Why did this not work? What can I do now?
Ok, since the rom is not the problem3g/4g problem, I reflashed the kernal to ziggy's updated kernal. And that did not solve the proximity sensor problem. I still have to unlock the screen to hangup the phone. Kind of strange I think, since that was supposed to be one of the fixes in the kernal.
Any thoughts on this?
Use Adrynalyne's kernel
http://forum.xda-developers.com/showthread.php?t=1024338
I use the 4.3 and it runs perfectly fine and the prox sensor works, his are in Kernel Manager also so it will be an easy fix.
oscar615 said:
Ok, since the rom is not the problem3g/4g problem, I reflashed the kernal to ziggy's updated kernal. And that did not solve the proximity sensor problem. I still have to unlock the screen to hangup the phone. Kind of strange I think, since that was supposed to be one of the fixes in the kernal.
Any thoughts on this?
Click to expand...
Click to collapse
verizon 3g might still be down?
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.
I know there's plenty of GPS problems with this phone, but after reading that GPS works in both the roms i've tried, i think im doing something wrong. This is where i'm at:
After using both of these roms on 2 different vibrants, i can't figure out for the life of me why i cant get the GPS to do anything at all on these roms.
I've used ODIN to go back to stock, and then tried flashing the roms but with no luck.
I dont have any clue how to use Angry GPS either, so i haven't messed with that at all. If i need to change some settings within the app, please enlighten me.
Thanks for anyone who helps me with this problem. The only Rom i know of that i have 100% working GPS is with Team Whiskey's Bionix-V 1.3.1.
Anyone? I dont want to be pushy, i just wanna figure out the problem.
And on a side note, i know i posted in the wrong section.
GPS works but it is also a work in progress as no one knows what is really going on with GPS in the Vibrant. The ROM seems to have little effect on weather the GPS works but the "kernel" that underlies it is where the effort is being placed for a fix. While the GPS works on all the kernels it eventually stops working after some time. It is believed to be an issue with how Android starts and stops different services to save power.
Most users have reported great GPS using Kiss 2.2 kernel in combination with either of the Team-Passion Roms (Passion, Euphoria). The most recent kernel is Kiss 8.2. Get it here:http://team-passion.com/index.php/downloads/galaxy-vibrant
For info on each kernel see here: http://team-passion.com/index.php/forum/2-about-team-passion/283-test-kernels
Keep in mind that the developers in my opinion have been working on these ROMS and Kernels like it was their full time job. And they are determined to make GPS work consistently so give them some encouragement to hopefully keep them motivated as they are likely our only hope.
Passion is a faster more responsive but Euphoria has more customizations baked in. The kernels are interchangeable between these ROMs but they have different performance characteristics.
GPS working after deep sleep on Euphoria
After going through 10 ROMs and 20 Kernals I think I may have a semi working GPS. Running Euphoria RC2.1 with stock KB5 modem and gingerbread bootloaders. Installed these gps fixes
http://forum.xda-developers.com/showthread.php?t=1550327
Ran ultimate cleaning script then flashed Glitch then the subzero kernel in the same recovery session
CM9-vibrantmtd-Glitch-V14-B6.zip
cwm-subZero-vibrant-1.1VC_build61-CFS_BLN.zip
Lock immediately after boot with angry gps and phone has deep slept multiple times and gps picks up after granted after 50 seconds
I really appreciate the help guys, the Kiss 8.2 kernel fixed the problem in the Euphoria 2.1 ROM. I get locks within 10 seconds, and also better battery life.
So now as far as im concerned, this is the best combo there is.
droidtomtom said:
Most users have reported great GPS using Kiss 2.2 kernel in combination with either of the Team-Passion Roms (Passion, Euphoria). The most recent kernel is Kiss 8.2. Get it here:http://team-passion.com/index.php/downloads/galaxy-vibrant.
Click to expand...
Click to collapse
8.2 did the trick for me. Locked up in under 20 seconds, and I'm inside my house (by a window) Don't know about deep sleep recovery, but I'll let you know.
You really need to change to Chimera v2.2
Im just curious if anybody out there is running the stock version of Honeycomb and NOT having any gps lock problems?
No problems here. Don't use the GPS extensively but I've not noticed a problem when I use it with either GB or HC.
I use Sygic a ton! Like around 3 times a week and I have not had any problems on HC
Sent from my PG41200 using XDA
So your not running anything special?
Not rooted, or different kernal flashed. Stock version of HC?
jacobbones said:
Im just curious if anybody out there is running the stock version of Honeycomb and NOT having any gps lock problems?
Click to expand...
Click to collapse
there is a patch on GPS from crypted,
http://forum.xda-developers.com/showthread.php?t=1267899
used it and check your gps with gps-status.
Hope this help,
I saw that patch.
Looks like I will try and do that next day off.
Gotta root my tablet first though
When running CypherROM I had no problems with GPS lock.
I'm trying the de-sensed ROM now, and haven't tried GPS yet.
No, nothing special. Just the HC I got when i updated. No special Rom or anything.
Sent from my PG41200 using XDA
This has been hashed over and over. There must be 10 similar thread on this forum so not sure why people see the need to open yet another one, but.
Nothing actually fully fixes the GPS issue in HTC honeycomb, same for all the custom HC variants. It appears to have a problem that repeatedly resets the GPS after a period of time. For some applications, it will still work if you are in a location that allows a fast lock again or for applications that need a one time fix. There is something buried deep in the driver or kernel that is playing havoc with the GPS.
STILL NOT FIXED ON ANY VARIANT OF HC.