Database Info

Thunderbolt w/power plugged-in boots to recovery

This issue seems to go waaaay back. "An issue with CWR" is all I've found....
Anyone know of a fix? Searched and searched. Can't post on the TB dev forum yet...
thanks!
sk

Its not really a very big deal. All you have to do when that happens is push the power button once more and it will just boot up

skeeter123 said:
This issue seems to go waaaay back. "An issue with CWR" is all I've found....
Anyone know of a fix? Searched and searched. Can't post on the TB dev forum yet...
thanks!
sk
Click to expand...
Click to collapse
If you searched you would of found five threads on the TB forum alone about this
Its a HTC built thing in most HTC phones as a safeguard. What happens if you break the volume rocker? Well your screwed into getting into recovery ... Wait! U can force it into recovery by doing that
Sent from my ADR6400L using XDA Premium App

superchilpil said:
If you searched you would of found five threads on the TB forum alone about this
Its a HTC built thing in most HTC phones as a safeguard. What happens if you break the volume rocker? Well your screwed into getting into recovery ... Wait! U can force it into recovery by doing that
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Search, I did. As I said I did. Answers I did not find.
I should have been more specific. I want to charge the TB with power off...
...and my phone is rooted. Perhaps it's not a bug w/ CWR after all... just a lovely safeguard...
...sk

See here:
http://forum.xda-developers.com/showthread.php?t=1000546
Assuming you are rooted, since it doesn't happen on un-rooted Thunderbolts. As previously stated, hopefully it's just a matter of time and code to resolve it.
Yes, this was recycled from one of the other threads.

tekthrawn said:
See here:
http://forum.xda-developers.com/showthread.php?t=1000546
Assuming you are rooted, since it doesn't happen on un-rooted Thunderbolts. As previously stated, hopefully it's just a matter of time and code to resolve it.
Yes, this was recycled from one of the other threads.
Click to expand...
Click to collapse
Ahhh. It's all in the search terms. I had originally spotted it in that very thread....then started searching under "bump charge" or some combo that didn't bring thread up. Various iterations of CWR, etc.......head.....feeling.......thick....today..
Thanks much for lead...

...and using fastboot will prevent going into recovery.

This bug/issue has been fixed:
http://forum.xda-developers.com/showpost.php?p=12834785&postcount=86

How to install init to fix froyo freeze ?

hello xda members
i have install froyo fx06 bundle here
my problem is sometimes the phone freeze. i read the entire post to find the solution to fixed that. then i found the only solution is to install init at here . can someone make a tutorial how to install that. i mean the step by step tutorial.

Have you any idea as to how to use ADB or terminal? If you do, then you are pretty much done, with the exception of executing those commands in that post. If not, you'll have to wait till it gets committed like the rest of us Or just wait till someone that does know, comes across your thread! That thread is mainly there for people who know how to do this already.

R^7Z said:
Have you any idea as to how to use ADB or terminal? If you do, then you are pretty much done, with the exception of executing those commands in that post. If not, you'll have to wait till it gets committed like the rest of us Or just wait till someone that does know, comes across your thread! That thread is mainly there for people who know how to do this already.
Click to expand...
Click to collapse
i don't know how to use ADB or terminal. actually this is my first time heard that. hehe

Some say it isn't that difficult while others have a difficult time trying to understand English, much less speak/type it(like myself ). If you feel up to it, you can start by reading HERE. Unless someone else has this simplified elsewhere. If that were the case and I knew of it, I woldn't be pointing you in this direction.

Thank you for trying to help me.

today i have install [RIL + ROOTFS] on my device after found this thread http://forum.xda-developers.com/showthread.php?t=950383
but the problem still same. i have read that [RIL + ROOTFS] is to fixed freeze because 3g problem i think. but i think my problem is not about 3g.
my problem i think is about my device sometimes not showing display, it happen if i put my phone in standby mode then when i want to on back it will not show the display. but i can tell that my phone is working and not freeze, only it have blank screen.
please help me..!!

hotsmusic said:
today i have install [RIL + ROOTFS] on my device after found this thread http://forum.xda-developers.com/showthread.php?t=950383
but the problem still same. i have read that [RIL + ROOTFS] is to fixed freeze because 3g problem i think. but i think my problem is not about 3g.
my problem i think is about my device sometimes not showing display, it happen if i put my phone in standby mode then when i want to on back it will not show the display. but i can tell that my phone is working and not freeze, only it have blank screen.
please help me..!!
Click to expand...
Click to collapse
and i think it's not because flax cable because this problem only happen when i use froyo fx06.

Honestly, I've never had any real problems with FroYo freezing on boot. Just the SoD issue due to partial panel collapse. Supposedly, that (modified rootfs) only fixes the freezing on boot issue. Unfortunately, there is no way I can reproduce the issue you are experiencing on my end to help troubleshoot. Some blame it on the operator/service provider and others think it's the build itself. As for me, well I'm not sure what to think because it doesn't seem to affect me much. Have you tried Gingerbread yet? Might be something to play around with till the issue gets fixed.

R^7Z said:
Honestly, I've never had any real problems with FroYo freezing on boot. Just the SoD issue due to partial panel collapse. Supposedly, that (modified rootfs) only fixes the freezing on boot issue. Unfortunately, there is no way I can reproduce the issue you are experiencing on my end to help troubleshoot. Some blame it on the operator/service provider and others think it's the build itself. As for me, well I'm not sure what to think because it doesn't seem to affect me much. Have you tried Gingerbread yet? Might be something to play around with till the issue gets fixed.
Click to expand...
Click to collapse
Thank you for trying to help me. actually i have try to set my phone in airplane mode to test if the problem because operator/service provider , but the problem still the same. it's not freeze because i still can fell it vibrate when i touch the screen only the display not show up.
about gingerbread. i have read that gingerbread is android 2.3 and froyo is 2.2 right? but why many people like to use froyo then gingerbread? if gingerbread have any problem. sorry if i asking to many question.

I'm not 100% on this but I think it has something to do with the fact that the porting is still in alpha phase for our devices. If anything, this can be looked at as good or bad. Good, that we have gotten this far and it seems our devices are pretty much stable. Bad, that this might be as good as it gets for a while. You have to weight the options of a faster port(in terms of stability) but less complete(in terms of functionality) or a more complete port but not quite as fast. I remember when we first got FroYo, it seemed like a complete mess. It took till the third release (FRX03) for stability to take place(noticable) because the devs were trying to figure out what caused the instability. When it's all said and done, the end user experience is all that most are looking for. When this is the case, it's difficult to say what should be done. Wait till it becomes more stable or try to come up with work arounds. Troubleshooting can get you so far until you require more understanding of what affects what. Hopefully, I have bored you out of your mind and that this makes things clearer as to what you can do to help!

thank you for your kind to help me. i have change to gingerbread but it have same problem like froyo. then i tried to hard reset then reinstall froyo and change the kernel. now it working great without problem except camera not working . maybe because i change the kernel htc-msm-linux-20110214_200559-package.tar . but it's ok for me. i will wait till new release.

You must have the similar issues some others have (on foreign carriers/other than USA based) Now, I'm not saying this is the problem just that others that have a similar issue, are on those carriers. There have been updated kernel packages that include the camera fix but I would suggest a little more reading into what you need to do, to ensure that you aren't causing the issue you are experiencing now.

Is It Me Or Is Everyone Nitpicking About This Phone?

There isn't a day that goes by that people dont complain about this phone. It seems that every since the bleeding issue has been addressed people have been finding the tiniest things to get mad about. Some things can be fixed through software fixes/roms and some things you just simply return the device for if you can't fix it yourself. Some things are just your imagination lol. The device in my opinion is doing good to be out for almost a month. Maybe I'm just tired of hearing people let the negative outweigh the positive. Honestly if you didn't want the issues you should have waited a couple months after the launch. This is the first phone I bought on the day it launched. I expected issues...nothing is perfect but with these roms coming out its starting to become a perfect device in my eyes. Once Faux123 cooks us a kernel there shouldn't be any complaints left.
Sent from my LG-P999 using XDA Premium App

Totally agree

Yes, what is even more annoying is that each "issue" has two dozen threads dedicated to it. Making it impossible for anyone to make any headway.
How about a single "battery issues and solutions" thread?
A single "LCD bleed" thread.
A single "random reboot" thread.
Can you imagine how much better this forum would be? Maybe the mods could merge threads and do this, but it's probably too far gone at this point to implement some organization.
Currently, every time someone has one of those issues, they start a whole new f-ing thread.

mapin0518 said:
Yes, what is even more annoying is that each "issue" has two dozen threads dedicated to it. Making it impossible for anyone to make any headway.
How about a single "battery issues and solutions" thread?
A single "LCD bleed" thread.
A single "random reboot" thread.
Can you imagine how much better this forum would be? Maybe the mods could merge threads and do this, but it's probably too far gone at this point to implement some organization.
Currently, every time someone has one of those issues, they start a whole new f-ing thread.
Click to expand...
Click to collapse
Agreed. So expect more to come.
Sent from my LG-P999 using XDA Premium App

mapin0518 said:
Yes, what is even more annoying is that each "issue" has two dozen threads dedicated to it. Making it impossible for anyone to make any headway.
How about a single "battery issues and solutions" thread?
A single "LCD bleed" thread.
A single "random reboot" thread.
Can you imagine how much better this forum would be? Maybe the mods could merge threads and do this, but it's probably too far gone at this point to implement some organization.
Currently, every time someone has one of those issues, they start a whole new f-ing thread.
Click to expand...
Click to collapse
Man... ain't that the truth
Sent from my LG-P999 using XDA App

Agree. I for one have not a single issue except wifi fighting with data sometimes..
Gps rocks
Camera rocks even though before clicking this thread I saw " camera sucks thread"
Video camera rocks
Screen is awesome (dont bring up backlight)
Good memory
Fast ass phone
Sturdy hardware
good looking
Already a leaked gingerbread build within 2 weeks
Cm roms
This phone is the **** meng..

smashpunks said:
Agree. I for one have not a single issue except wifi fighting with data sometimes..
Gps rocks
Camera rocks even though before clicking this thread I saw " camera sucks thread"
Video camera rocks
Screen is awesome (dont bring up backlight)
Good memory
Fast ass phone
Sturdy hardware
good looking
Already a leaked gingerbread build within 2 weeks
Cm roms
This phone is the **** meng..
Click to expand...
Click to collapse
I disable data when I turn wifi on. It only fights it sometimes when I leave both on.
Sent from my LG-P999 using XDA Premium App

I'm running the new eagleblood rom based off gingerbread this phone is faster than before. Backlight was a issue till I found one with minimal to none. Everything has a fix. Stop complaining and fix it. Your on XDA.
Sent from my LG-P999 using XDA Premium App

charlieb620 said:
I'm running the new eagleblood rom based off gingerbread this phone is faster than before. Backlight was a issue till I found one with minimal to none. Everything has a fix. Stop complaining and fix it. Your on XDA.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Op - I know at one point you were planning on returning the g2x and wait for sensation. Glad that you have got one that doesn't have that much bleeding and you are happy with it
For me personally this device rocks in all aspects except for the slight lcd bleeding I have. Any other software issues will be addressed by our awesome devs. I just hope LG address this lcd bleeding.
Sent from my LG-P999 using XDA Premium App

+1 everyone being WAY too picky.
100% of the people are under a FULL REFUND period still. Rather than b*tch and whine, return the thing and get something else. Why cause so much stress you have to whine on an online forum about it instead of just returning the thing for 100% your money back? Sounds like gluttony for punishment to me; would rather waste 5-10min complaining than rectify the situation and be done with it by getting something else. Tmobile has plenty of other good android phones.
The blacklight bleed is not that big an issue. Anyone running their backlight at 100% all of the time to complain about it has bigger issues like going 4 hours on a charge. No one should need to set the backlight at 100% for anything besides trying to kill your battery for some reason.
And if LG does fix the issue EVERYONE has a 1 year warranty on the phone despite the return period to swap it for a "fixed" one. There is absolutely nothing that warrants the dozens of threads about it blocking other meaningful discussions.

kirdroid said:
Op - I know at one point you were planning on returning the g2x and wait for sensation. Glad that you have got one that doesn't have that much bleeding and you are happy with it
For me personally this device rocks in all aspects except for the slight lcd bleeding I have. Any other software issues will be addressed by our awesome devs. I just hope LG address this lcd bleeding.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Yea I was to the point of no return. I just kept bothering tmobile until I felt as though I got a device that was satisfsctory. My friend works for them so when he gets his sensation from training class ill mess around with it to see if its worth the hype.
Sent from my LG-P999 using XDA Premium App

klmsu19 said:
+1 everyone being WAY too picky.
100% of the people are under a FULL REFUND period still. Rather than b*tch and whine, return the thing and get something else. Why cause so much stress you have to whine on an online forum about it instead of just returning the thing for 100% your money back? Sounds like gluttony for punishment to me; would rather waste 5-10min complaining than rectify the situation and be done with it by getting something else. Tmobile has plenty of other good android phones.
The blacklight bleed is not that big an issue. Anyone running their backlight at 100% all of the time to complain about it has bigger issues like going 4 hours on a charge. No one should need to set the backlight at 100% for anything besides trying to kill your battery for some reason.
And if LG does fix the issue EVERYONE has a 1 year warranty on the phone despite the return period to swap it for a "fixed" one. There is absolutely nothing that warrants the dozens of threads about it blocking other meaningful discussions.
Click to expand...
Click to collapse
I still have 16 days left so my decision is still on the air. Phone still looks new. Right now I'm keeping it, but anything can happen. Who knows more roms may come out. I'm happy with it. I bought times of accessories so if do go somewhere else the accessories will be up for grabs.
Sent from my LG-P999 using XDA Premium App

So far this has been the best Android device I have ever used and I have used many. Luckily I do not have a single problem with this phone. My WiFi works great and never fights with data. I get 30mbs download speeds and 10mbs upload speeds while on WiFi. I get 7mbs download and 2mbs upload on 4G. My GPS locks within 3 seconds and is accurate to 5 feet. I am running the stock software with the pre-dexopt patch using Launcher Pro and this phone flies through everything. It plays every game at high frame rates and Flash runs buttery smooth. I never thought I would use a Android phone that didn't lag but this phone hasn't lagged once. I can honestly say that I am extremely happy and in my opinion this is the best device available in the US right now. The only device that will dethrone it is the SGII which I will be getting and give the G2X to my wife. For those who think the Sensation will be better than the G2x.....HAHAHAHAHAHAH

jrwingate6 said:
So far this has been the best Android device I have ever used and I have used many. Luckily I do not have a single problem with this phone. My WiFi works great and never fights with data. I get 30mbs download speeds and 10mbs upload speeds while on WiFi. I get 7mbs download and 2mbs upload on 4G. My GPS locks within 3 seconds and is accurate to 5 feet. I am running the stock software with the pre-dexopt patch using Launcher Pro and this phone flies through everything. It plays every game at high frame rates and Flash runs buttery smooth. I never thought I would use a Android phone that didn't lag but this phone hasn't lagged once. I can honestly say that I am extremely happy and in my opinion this is the best device available in the US right now. The only device that will dethrone it is the SGII which I will be getting and give the G2X to my wife. For those who think the Sensation will be better than the G2x.....HAHAHAHAHAHAH
Click to expand...
Click to collapse
This phone is far superior to my G1. As long as it just runs with no errors, I'm good.

.....or it could be that many of the first release devices had major issues and people have come to rely on the excellent folks here at XDA to help them. I know that many also moved from the HD2 to a full time android device and there has been growing pains.
I had a POS one, swapped it and am very happy now.
Thanks again to all great people here at XDA that have helped me make the adjustment from WM.
Reading is the key!

Just my personal opinion, but it does seem like they rushed out the 2.2 build. I worked as a sales rep for T-Mobile (today was my last day), so I had to see the dark side of the user experience more since people would come to me with troubleshooting issues. It just doesn't have the polish that I would expect from a 2.2 ROM. Most times it would fly, but occasionally it would hang when switching apps, be slow to respond, and sometimes outright crash for no reason. That said, almost all the stability issues I've had were fixed when I flashed the Gingerbread leak, and I didn't even wipe before flashing (I was naughty).
Seems to me like they intended to ship it with 2.3 but ran short on time. Instead they took the ROM they had for the O2x, got rid of their UI changes and hobbled it onto the G2x with the intention of updating it quickly. For that reason, I told the customers that came into my store with stability issues to wait for the update, but if it doesn't come before their return period is up (30 days here in California) to go ahead and return it. I fully expect that update to come before June 20th.

mapin0518 said:
Yes, what is even more annoying is that each "issue" has two dozen threads dedicated to it. Making it impossible for anyone to make any headway.
How about a single "battery issues and solutions" thread?
A single "LCD bleed" thread.
A single "random reboot" thread.
Can you imagine how much better this forum would be? Maybe the mods could merge threads and do this, but it's probably too far gone at this point to implement some organization.
Currently, every time someone has one of those issues, they start a whole new f-ing thread.
Click to expand...
Click to collapse
more than a dozen! lol. It's ridiculous.. especially when someone is in a direct thread like rooting.. "How do I root?" Ugh.. read the stupid OP of the thread you are in!!! "uh, I'm getting an error." - "Follow the directions in the OP" - "Great thanks! It worked!"
maldlkasdkfsjadfal;dfjwpoijfo

Rant
here's the kicker... You see, I'm a NEW android/smartphone user. This is my first smartphone. I came from using a razr just for phone calls, for the last 4+ yrs.
I thought the g2x is the next best thing to sliced bread. I love it. I got mine on the day it was launched, the first run of phones.. It has slight screen bleed.. so what. I would have never noticed it unless someone said something. I thought about returning the phone to get a different one because "heck, everyone else was complaining"... and I was like.. why would I do that? The phone works fine.. nothing wrong with it... and I'll probably get one that has more probs.
So I kept the phone. Battery life? As someone else said... on every single other forum where a new phone comes out... that's the #1 talked about topic. "Battery life sucks! Battery life sucks!" Now after talking to a few folks, do I see there is a problem for a few people.. absolutely. If you're phone has apps frozen, nothing running, you set it down on the table.. pick it up a cpl hours later and it has dropped 25%... ya, major problem. A few guys are seeing a drop down to a dead battery in 8hrs, with almost zero usage. A phone call or 2 and litearlly a few txt msgs. There is somethihng seriously wrong. BUT there are others that are using their phone all day long.. txting all day.. screwing battery usage with using ATK 30x a day, etc.. and they are complaining about battery life of 8hrs when they are using their phone like a computer. Stupid.
I have talked to multiple guys about their battery usage... they started off complaining... Then as we discussed in PMs... they admitted.. "Ya I guess I do use the phone a lot. I'm literally texting all day long." WTF!?!? Duhhhhhhhhhh
lol... I seriously believe that around 75% of the battery complaints are idiots using the crap out of their phone... and wondering what is going on...
/rant

I totally agree...way too much complaining. And I LOVE that we now have a thread for complaining about the complaint threads. I know, I'm twisty...but I love it.

I agree. I was just looking at the pictures posted in one of those other threads of the screen bleed. They are all mostly like mine. One, with a sqiggly line, did look really bad. But really, I do not see the bleed in everyday use. At all.( Edit: And I am a 100% brightness sorta guy) Someone was griping about how they can't see it in use, but boy when 2,3 comes out and that bar turns black....oh boy am I gonna be mad!! Wow.
Mine activated early yesterday morning. I am amazed at this thing...
I may totally regret saying this, but other than the screen bleed "issue", this thing has been perfect for me. Just lucky I guess.
No reboots, wifi seems to work perfect, great data speeds and clear crisp calls. So far. My call reception was awful on Metropcs.
Again I may regret saying this. I have seen a couple of posts where people say they started having issues after a week or so.
Am I the only one having a problem free experience?

[Q] touchscreen problems?? anyone?

sometimes when i unlock the lockscreen it doesnt work, i have to lock it and unlock it again to get it working (this usually happen when im playing games or when i just unlock it...
i searched and i didnt find a thread of this
is this also happening to someone else or is just to me??
im using TB fusion 1,2,0,1

renehd2 said:
sometimes when i unlock the lockscreen it doesnt work, i have to lock it and unlock it again to get it working (this usually happen when im playing games or when i just unlock it...
i searched and i didnt find a thread of this
is this also happening to someone else or is just to me??
im using TB fusion 1,2,0,1
Click to expand...
Click to collapse
You may need to try BROWSING the sections, too. It's been asked a million times.
Non-rom specific touchscreen driver issue it is suspected.
Some people experience it, some don't.
I, for one, haven't, but many people have.

well when you put the topic of the thread it gives you some similar options to your problem and no one of the options was even close to my request so thats why i did it.. can you give the link where was asked the same question as me please?
thank you

Bumb...........!!

Will the touchscreen driver also make parts of the screen non responsive randomly? I am having that happen to me and wondering if I should try and exchange it.
Running Cm7 nightly in case thatd help

I've had this problem on multiple roms.

I've had this issue on multiple roms as well it's not horrible at all though just have to touch it a second time. the weird thing is I can pretty much predict it for example when scrolling through my apps in tibu it gets stuck at the same spot every time. and also the xda app on the first scroll. it's been discussed many times but I'll throw it out there again. NOT A ROM ISSUE, HTC ISSUE. MANY PHONES ARE AFFECTED. don't stress over it
Sent from my Inspire 4G using XDA Premium App

[Q] [CM10 Nightlies] gpslocationprovider wakelock on 10/18 Nightly

Hi All,
I am putting this here in the Q&A section because I don't have any posts yet and I can't put it in the dev section. I'm running CM10 nightlies on the Samsung Galaxy S2 Skyrocket and I'm currently on 10/18. What I've noticed today, and I haven't found any information on it yet.
This morning I used my maps and GPS to get around town a bit and then came to work. When I looked at BBS a few hours later I noticed a kernel wakelock on PowerManagement. After some investigation, I learned I needed to look into partial wakelocks and found a corresponding wakelock on the GPSLocationprovider which I imagine is from my use this morning.
From what I've read so far, this has been an issue in other CM10 nightlies for other devices but I'm not sure if it has been reported yet for this one. I know to fix it, I can do a reboot but just curious if it is being looked at.
Thanks and apologies if it is listed elsewhere - i did search and couldn't find it.

andygens said:
This morning I used my maps and GPS to get around town a bit and then came to work. When I looked at BBS a few hours later I noticed a kernel wakelock on PowerManagement. After some investigation, I learned I needed to look into partial wakelocks and found a corresponding wakelock on the GPSLocationprovider which I imagine is from my use this morning.
Click to expand...
Click to collapse
I have the same thing, although it doesn't seem to be burning through the battery like actually having GPS on. If it helps, I do have tasker automatically shut off GPS when the screen is off so I'm not sure why it would be running in the background.

andygens said:
Hi All,
I am putting this here in the Q&A section because I don't have any posts yet and I can't put it in the dev section. I'm running CM10 nightlies on the Samsung Galaxy S2 Skyrocket and I'm currently on 10/18. What I've noticed today, and I haven't found any information on it yet.
This morning I used my maps and GPS to get around town a bit and then came to work. When I looked at BBS a few hours later I noticed a kernel wakelock on PowerManagement. After some investigation, I learned I needed to look into partial wakelocks and found a corresponding wakelock on the GPSLocationprovider which I imagine is from my use this morning.
From what I've read so far, this has been an issue in other CM10 nightlies for other devices but I'm not sure if it has been reported yet for this one. I know to fix it, I can do a reboot but just curious if it is being looked at.
Thanks and apologies if it is listed elsewhere - i did search and couldn't find it.
Click to expand...
Click to collapse
Check the better battery stats thread there is a way to fix that and this has already been answered please use search
Sent from my SGH-I727 using xda premium

crashpsycho said:
Check the better battery stats thread there is a way to fix that and this has already been answered please use search
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
I have read most of that thread and have been unable to find a solution which works for me.
Based upon my reading in other device threads, some people get this wakelock if they use GPS for anything and then attempt to turn it off. For example, if you turn on GPS, use a maps application for a short while, close the maps application and turn off GPS, the wakelock is born. Even if you kill any active maps services, it will still be there.
I am under the impression that a flavor of this issue can be caused by location aware apps such as Google Maps and Facebook, but the issue where it is constantly active for hours on end, is perhaps an inherent issue in the 4.0.x and 4.1.x, kernels. I have found many people complaining of this issue on many different flavors of roms (ICS / JB) and hardware (HTC, Samsung, LG).
One user's solution was to never turn GPS off, but will continue to look for a better solution.

Its Google now, turn it off and see if it Persists in bbs
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

First there is a thread in general section devoted to wakelocks. Please search.
Second never post in dev section unless you are dropping a ROM kernel or mod.
Sent from my SGH-I727 using Tapatalk 2

Even without Google Now enabled I can recreate this wakelock without fail. GPS on, use GPS, GPS off, wakelock materializes.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 09:14 PM ---------- Previous post was at 09:13 PM ----------
Unfortunately there does not seem to be any info about this particular phenomena in the threads that I have found.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Sorry to resurrect an old thread. Has anyone who has had this issue resolved it?
Like promiseoc, I can get the wakelock every time I use the gps, and shut it off later. So far, I've tried the fix in bbs using Gemini Manager and disabling latitude and all location services. I'm also not signed into google now. I use Latitude occasionally, but make sure to shut it off when not in use.
So far, I've had this problem on each of the AOSP-based roms I've tried (CM10, Liquid, and Slim). Great roms, all of them, but any other suggestions on what else I can try?

jedah said:
Sorry to resurrect an old thread. Has anyone who has had this issue resolved it?
Like promiseoc, I can get the wakelock every time I use the gps, and shut it off later. So far, I've tried the fix in bbs using Gemini Manager and disabling latitude and all location services. I'm also not signed into google now. I use Latitude occasionally, but make sure to shut it off when not in use.
So far, I've had this problem on each of the AOSP-based roms I've tried (CM10, Liquid, and Slim). Great roms, all of them, but any other suggestions on what else I can try?
Click to expand...
Click to collapse
I guess we are just supposed to keep GPS on and forget about it. I don't like to because of paranoia but it seems like that's the fix. Happens across a library of devices.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

promiseofcake said:
I guess we are just supposed to keep GPS on and forget about it. I don't like to because of paranoia but it seems like that's the fix. Happens across a library of devices.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Oh well. If that's the only solution, so be it. I was always under the belief that drained battery, but then again I've never tested how much it does. May not be a big deal. Thanks.

The wakelock goes away if you reboot and I think it also does if you plug your phone into a charger even briefly. Of course, ensure it is not a charger that causes the vbus_wakelock.

phoneturf said:
The wakelock goes away if you reboot and I think it also does if you plug your phone into a charger even briefly. Of course, ensure it is not a charger that causes the vbus_wakelock.
Click to expand...
Click to collapse
Goes away with reboot but then you lose battery whilst media scanner runs. I now leave GPS on and forget about it. That is interesting about the charger, I will have to check it out.

promiseofcake said:
Goes away with reboot but then you lose battery whilst media scanner runs. I now leave GPS on and forget about it. That is interesting about the charger, I will have to check it out.
Click to expand...
Click to collapse
Any word if this will be worked on in the new update?

If you leave GPS enabled it's a non-issue.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Sorry to revive, but I have this even with GPS always disabled.
Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S