Related
I had problems which corrupted the title bar of my Ameo (UK, T-Mobile) after about 8 - 10 hours. I can't exactly pin down what caused it, but when I disabled Batti and removed it from my Startup folder the problems totally disappeared.
I'm using WM6 Project Black 2.0 as downloaded.
Has anyone else experienced such problems?
Yes, I am on Tmobile in the UK, and am running the project black 2.0 rom.
I have to reset my phone each morning to get it working on this rom, and at about 4-6pm i get a corrupted title bar which requires another reset.
I havent looked into the problem yet, but will try removing Batti and see what happens
I also suffer from very heavy battery drain with this rom, I took my phone off charge at 10am this morning, and it is now down to 10% and giving me warnings about charging it, I have tried running it right down till it turns off after 10 seconds, then charged it up overnight without turning it on, but this didnt help at all
I do still like the new rom, and wont be going back to WM5, but these 2 problems are a little annoying on a daily basis
Let me know if disabling Batti from start up fixes the issue of the title bar. I experience a similar issue and am working on isolating it myself. It doesn't happen daily on mine but too often nevertheless. I finally have time to troubleshoot so I'll try to post my results as soon as i find some. I'm going to test Batti first based on this info and see if that fixes the issue. I also noticed that sometimes when the bar does that, some other areas of the screen freak out and sometimes the device locks up. We'll see. Thnx for the post.
Hey all... first for the record, I'm a longtime lurker here but not many posts, but I'm also "answerman" over at PPCGeeks and HowardForums, probably close to 1000 posts at those sites so I am definitely not new to this world...
Looking to see if anyone else has had this issue: I went from the stock Alltel WM6 ROM to the 3.27 radio and the progression of DCD's ROMs from 2.0.0 to 2.1.0 to 2.2.1... and every one has the same issue for me: when I leave my 6800 plugged into the wall charger overnight, the next morning it is locked up solid and I have to soft reset to get it back.
I'm guessing this has less to do with DCD's ROM and more to do with the radio, but I am just looking for clarification. Anyone else seeing this?
I don't have much installed... the next step would be to hard reset and see if the problem arises with no programs installed, but I haven't gotten to that yet... all I have installed besides Odyssey Mobile are HTC X-Button 1.5, VistaHide battery meter, AIM (which I haven't even opened yet), Total Commander, Opera Mobile 8.65, and nandHP FreeCell. And I have it checking 4 email accounts via IMAP once an hour. It's fine during the day, the problem arises only when I leave it plugged in overnight.
Otherwise, DCD's ROMs have been fantastic... fast, reliable (other than the above issue) and GPS has worked flawlessly from day 1 for me... I use Odyssey Mobile (nav program that came with my Holux GPSlim 236) and I get a lock within about 60 seconds of starting up Odyssey, no need to "jumpstart" the GPS.
26 views and no responses... apparently I am in the minority...
I'd even like to hear "No, I have not had this problem" from someone... that would be useful...
answerman said:
26 views and no responses... apparently I am in the minority...
I'd even like to hear "No, I have not had this problem" from someone... that would be useful...
Click to expand...
Click to collapse
No, I haven't had that problem. I'm on Verizon though so it might make a difference.
I'm also on Verizon and leave my phone in a charging cradle all night with no problems.
i have the problem, but it seems only if i leave IM+ running overnight, if nothing is running it seems to last fine
Had that problem when I used S2U2.
ok, that would seem to rule out the radio then... that was the answer I was looking for...
I am going to leave it off the charger tonight and see if it happens that way...
[I have a AT&T tilt and more often than not, it is locked up solid in the mornings, whenever i leave it on charging overnight.
Well, the plot thickens... since it had a pretty good charge, I left it unplugged overnight and it was fine this morning after 8 hours of nonuse... so it's not a "lockup during idle" thing. Definitely seems to be related to being plugged in.
Next step is to try a different charger, I guess... weird, because this was never a problem until I reflashed the radio and DCD's ROM, and this is the original OEM charger I'm using so there shouldn't be anything wonky there.
I had this issue with DCD 2.0.0 and 2.1.0, but since 2.2.0 came out, the problem has gone away. I'm now running 2.2.4 and still no problems yet. It only seems to happen if the screen turns off. If you uncheck that setting in the power management, you could avoid the issue.
tavella said:
I had this issue with DCD 2.0.0 and 2.1.0, but since 2.2.0 came out, the problem has gone away. I'm now running 2.2.4 and still no problems yet. It only seems to happen if the screen turns off. If you uncheck that setting in the power management, you could avoid the issue.
Click to expand...
Click to collapse
Isn't the current version 2.2.3?
Edit: Just saw the 2.2.4 version for Sprint. My bad.
Yeah, well I tried that... kinda...
I have my power management settings set to never turn the screen off when it is on external power, and usually I manually put it in standby (screen off) when I charge it, but a couple nights ago I tried leaving the screen on all night and it still did the same thing... so...
tavella said:
I had this issue with DCD 2.0.0 and 2.1.0, but since 2.2.0 came out, the problem has gone away. I'm now running 2.2.4 and still no problems yet. It only seems to happen if the screen turns off. If you uncheck that setting in the power management, you could avoid the issue.
Click to expand...
Click to collapse
i have the issue even when the screen is one (i did have the backlight turning off, that would seem an odd thing to lock it up though)
Isn't the current version 2.2.3?
Click to expand...
Click to collapse
dcd posted a 2.2.4 test for sprint, its in the second post in his thread
i'm still running dcd 2.1.0 here on verizon. i only had the unit lock up overnight once... the first night after reflashing. i had left a wmirc session open and running -- the next morning the unit was locked up solid and needed a soft reset to fix.
since then, i haven't had it do anything wonky while charging overnight at all, but i usually close all apps when it's done for the night and set down to charge.
could still be a radio issue with data connections causing these crashes... not sure. given all the seemingly known issues with radio v3.27, i can't wait for an update to the radio already...
scootle74 said:
could still be a radio issue with data connections causing these crashes... not sure. given all the seemingly known issues with radio v3.27, i can't wait for an update to the radio already...
Click to expand...
Click to collapse
See, that was what I was wondering... the only thing that should be running when it's charging overnight (I'm pretty anal about closing apps when I am not using them) is Messaging to check my email accounts...there are 3 that get checked every 15 minutes via IMAP... I will try disabling the auto send/receive and see if that makes a difference.
I installed 2.2.4 and went to break, came back and my device was locked again. It's hooked to my pc via USB. Not sure if those details help or not. Running Vista Ultimate x64. This didn't appear to happen with 2.2.1 or 2.2.2. Could just be coincidental. Overall, great ROM!
i am having the same, my phone is password protected in the morning when left charging overnight. I am currently using DCD 2.5 but it was also happening using PPCkitchens newest build. After doing a little research it seems to mostly be happening to the Alltel 6800s.
mine usually locks up once or twice during the day, and only when it is in a timed-out/sleep state. I have to push the reset button/hole thing to bring it back, but I have never woken up to it being frozen, but that could be because of my power settings.
Set your screen/power to always stay on when plugged in on external power, but still to time out/off after 1minutes on battery power. You should set it to that, because I let mine charge all night and never wake up with it frozen.
also, when mine does freeze, during the day, the service light is still blinking green, like it still has a signal...i dont get it. you would think that would stop too when it froze. hmm.
it happens to me a few times...seems to happen after a new rom update...but mostly goes away after a few days..i noticed it alot after 3.2.0
i leave it charging and i thinks it just in standby until i push the power button...but its frozen and got to soft reset
i posted about it on this page http://forum.xda-developers.com/showthread.php?t=402920&page=38
My issue is not that the phone is frozen but is actually locked with a password and I have not set any passwords or lock on my phone. I have tried the epst unlock code, and my phone number but it still will not unlock unless I soft reset.
Hey guys, hope you can help with an issue I'm having with my Eris. A while back I dropped it in a parking lot and the screen broke. I upgraded to a Droid, but I got the screen fixed so my wife could have the phone. Everything seems to be working great, except for one problem. When you make a call, the screen goes to sleep as soon as you press the call button. When this happens, none of the buttons wake the screen up or end the call. The phone will wake up for around a second if you cover the light sensor, then uncover it, letting you end the call and then the phone is back to normal. I tried using Shakeawake and Screebl, neither worked.
I tried several different ROMs to see if it was just a weird quirk, but that didn't help. Currently running Jcase's Plain Jane with a mild overclock (710). Is there a way I can prevent the screen from sleeping? Seems easier than trying to get it to wake up. Seems like I remember a ROM that didn't sleep during calls, Espresso maybe?
If anyone can help or point me in the right direction, I'd appreciate it. Gladtm see the Eris community still going strong, things had gotten a little ugly when I left. Sorry if my post ran a little long.
Sent from my Droid using XDA App
Case?
Do you have a protective case on the phone? I had the same problem with my Eris after putting a case on it. The case interfered with the sensor on the top left of the phone.
There are a couple of things to try that I can think of off of the top of my head. One, under Settings > Call Settings > there should be a box to check to keep the screen on longer during the call. The other is to try pushing the trackball in and at the same time volume down. Surely not the most convenient way, but more so than not being able to not hang up a call or whatever. I honestly had this issue and a couple of other small problems that I ended up getting a refurb. One other thing that you could try before that is doing a nandroid back up and installing a Froyo based rom. I feel that it might be a 2.1 issue for some phones. I'm not sure why, but computers/phones can be finicky sometimes. Hope this helps!
it has to be a hardware issue since it started after the phone was dropped and across several different roms. i would see vzw about getting a refurb replacement. unroot it, put it back to stock and get a new one.
I did the same thing, dropped my eris off of the moving truck, and cracked the screen, I had been looking for something to fix that issue for quite a while, recently I installed Tazz Froyo v.4 and enabled the Settings => Call Settings => Keep Screen Awake function, ever since I have enabled that it hasn't locked up on me yet *knock on wood* Good Luck
Thanks for the replies everybody. I'll try the track ball trick, then installing Froyo tonight and see if that helps. I hadn't even looked at Froyo ROMs since I came back to XDA; when I left there was only one and it really couldn't even be called functional at the time. Glad the Eris is getting Froyo goodness too.
I do agree its probably a hardware issue, especially since when my screen was broken everything still worked fine, just couldn't see the display very well and it was ugly as sin. But looking at when this happens, I think if I can keep the phone from ever telling the screen to sleep, it would probably solve the problem.
If all else fails I'll try to get a refurb. Thanks again, and if anyone thinks of anything else, post it up.
Sent from my Droid using XDA App
Forgot to mention, the really weird thing is it only does it every other call. Thought that was pretty strange.
Sent from my Droid using XDA App
So i just upgraded to Tazz V5 and it started freezing again, from my research the problem that's causing the screen to lock up is the proximity sensor, when you cracked your screen it messed that up, my hunch is that in Tazz V4 that the proximity sensor isn't supported, so as a byproduct it doesn't turn the screen off for us Just my observation, let me know what you guys think
I am from Hong Kong, using vibrant.
I found that my vibrant will get easily hanged/not responding, occasionally.
No matter which rom I flashed, stock, roms from eugene. (Applied/not Applied lagfix)
When my vibrant is not responding, the back of vibrant near the camara or next to the camara, will get hot and hotter.
After a long press of the power button, for a hard reboot of the vibrant, the vibrant will be fine again. However, the situation repeat.
So, I want to figure out that is there anybody encountering the same situation.
Thanks.
I have not had this exact problem, but I have had mine randomly go black. It's done it 3 times in the 4 days I have had it. When it goes black, you can't turn it on, power does nothing, and you have to pull the battery to start it again. I have never let it sit long enough to see if it gets hot.
I have heard mixed thoughts, some people claim it's hardware problem, some say its a firmware problem =/
I've seen my screen turn black with just the key backlights remain on. The device becomes and remains hot to the touch as if working very hard (drawing heavily on the battery and CPU) but it never responds again. Holding down the power button for a full five seconds resets it.
In my case, I typically see this happen while I'm trying to use Google Navigate (GPS) while also running Pandora (streaming radio) in the background. Often it works, but often it doesn't, especially on days with warm weather. I've monitored battery temperatures around 114 degrees F after rebooting.
I suspect it is related to the problems with the GPS (fixed to use supl.google.com) and very much hope it will be fixed with the promised OTA upgrade. Although I may have seen it a few times (very few times) without GPS. My other suspicion turns toward a process called mmcqd which seems to run heavily at times. Perhaps the lagfix will help with this "Multimedia Card Queue Daemon" process. ::shrug::
Just offering this as notes to compare. I'm curious if others see the problem with GPS disabled? Or if you notice the mmcqd process maxing your CPU?
I've noticed that when using GPS, only when the GPS gets confused.. say for instance that I'm driving, get out of my car with a Navi program still running and walk inside of a building/house.. bam, phone is dead with the buttons lit.. I've decided to not bother with GPS.
If you're having those types of issues try avoiding background sync with the forever sluggish stock eMail app, and don't load up the internal memory with a lot of junk.
having the same prob... cant find the solution .. do u have any?
This happens to me on my stock vibrant everytime I try to use the maps program. On the off chance I get it to start working, as soon as it shifts orientation to landscape mode the whole thing will lock up. Usually I have to remove the battery to get it to reset. As was said, it appears to be caused by the faulty gps, so I usually just leave mine off.
However, I haven't noticed it happening while doing anything else and I'm hoping the upcoming ota update fixes these issues. (Don't want to bother with rooting stuff until I'm on stock 2.2)
The solution is to install the leaked update that we should be getting officially very soon. No freezing, no serious lag (installing apps will lag almost any Android device), no black screen freeze ups, much improved GPS, I'm lovin' it.
I installed Cyanogen Mod7 on samsung vibrant, after reboot the set not started, only samsung logo shows but not booted further, plz give the solution.
heygrl said:
The solution is to install the leaked update that we should be getting officially very soon. No freezing, no serious lag (installing apps will lag almost any Android device), no black screen freeze ups, much improved GPS, I'm lovin' it.
Click to expand...
Click to collapse
Hey, did u get the update or solution?
I've been using Android phones since the first Droid in November, 2009. My most recent phone (before my Thunderbolt) was a Droid Incredible. I loved the incredible but upgraded to the TB on the last day of unlimited data so I could lock it in for 2 more years.
However, there are some anomalies, aka problems, with the Thunderbolt that I didn't experience on the Incredible. I'm hoping you can help me decide if this is because of a faulty phone or I have to live with these.
1. GPS. I leave the GPS on all the time. I know, it's a battery hit, but I use it enough to just leave it on. However, on the Thunderbolt, after I've picked a destination in Google Maps, I often get a message at the bottom of the map stating: "Waiting for GPS". Yesterday I drove over 20 miles before it locked into GPS. This happens frequently. On the Incredible I never saw "Waiting for GPS" ever. Not once. Do I have to live with this? Is this the nature of the beast? Or do I have a faulty unit?
2. Data connection. Often when I try to do something data-wise such as the browser, etc. I get a message stating there's no data connection. I look at the notification bar and see that there are 3 or 4 bars in my signal strength area but no data information. There's no 3G, 1X or 4G indicator. Nothing. That area has just vanished from the notification bar. I've tried turning data on/off, I've tried going into and out of airplane mode, nothing turns data back on. I eventually have to hold the power button down and tap on "reset." That does the trick and I'll have data once it's reset. Again, is this normal or is there a setting somewhere where I can coax data into coming on. Or is this a faulty unit?
3. Screen dimming oddness. I have the car holder. I like it a lot. When I put it in the car holder I see the little lightning bolt over the battery indicator indicating it's charging. I have set the settings option to keep the screen on when it's plugged in so I can see the maps while driving. However, after a period of time the screen goes dim. It doesn't turn off, just dim. Touching the screen brings it to full brightness. However, that's dangerous while driving.
When this happens I notice that the lightning bolt doesn't appear over the battery any more. It's as if the charger stopped charging and I am running on battery. However, that can't be the case since the battery never drains. Even after 5 hours of driving the battery doesn't go down. It just doesn't have a lighting bolt and the screen will go dim. I can dismount and remount the phone in the car holder and the lightning bolt will reappear. As long as the lightning bolt is there the screen won't dim. But after a while the lightning bolt goes away and the screen will dim again. This is very annoying.
Any help on these issues would be greatly appreciated.
Here are details on my phone. Stock Android, not rooted. Android 2.2.1 Build: 1.13.605.7
Thanks in advance
The GPS is sadly a known issue but a fix can be found here. I use OMFGB and have flawless GPS even w/o the fix.
Your issue with data is kinda odd. Perhaps you can try flashing a newer radio. A list of Radio's and ROM's that are compatible with them is here
I am also unsure about your Car Dock issue since I dont use that feature. The above link for radio's and ROMs might fix that issue as well.
I dont recall having any weird issues like that when I had my 1st Thunderbolt, a side from call quality problems and bad battery.
I ended up taking it back and got an Incredible 2. never had any problems with the Inc 2 but did not that the battery was only a little bit better then the Thunderbolt's(during heavy usage) & since I did like the bigger size of the TB I ended up trading with someone on these forums and now I have a T B again. Same battery issues & same call quality issues.
I think once Verizon gives the $400 deposit back after the 1st year im just going to buy somwtjing new.
I had I similar issue with the data connection disappearing all of a sudden. This started to happen after I flushed MR2 OTA radio. I have since tried MR2 leaked and R2 gingerbread radios and both did not have this problem. Good luck!
Sent from my HTC ThunderBolt using Tapatalk
Thanks for the quick responses. Currently, since this is a corporate phone, I don't intend to root or change roms. Any other ideas?
The new gingeritis roms and he new gb radio are both from the new gb base that's supposed to be released for the TB soon. I would try them, you might be on an old radio and kernel that's just not working for your phone, try the new ones and see if that helps. If not, it might be a hardware problem, cuz I have none of those issues on the new radio and gingeritis 3d, or the old radio and stock rom, or any other rom for that matter.
Sent from my TBolt using my f**king thumbs...
Woohoo! The GPS Status program corrected my GPS issue. Thanks a bunch for that tip.
Now, how about the data issue or the dimming issue. Any thoughts on those two items?
TabGuy said:
I've been using Android phones since the first Droid in November, 2009. My most recent phone (before my Thunderbolt) was a Droid Incredible. I loved the incredible but upgraded to the TB on the last day of unlimited data so I could lock it in for 2 more years.
However, there are some anomalies, aka problems, with the Thunderbolt that I didn't experience on the Incredible. I'm hoping you can help me decide if this is because of a faulty phone or I have to live with these.
1. GPS. I leave the GPS on all the time. I know, it's a battery hit, but I use it enough to just leave it on. However, on the Thunderbolt, after I've picked a destination in Google Maps, I often get a message at the bottom of the map stating: "Waiting for GPS". Yesterday I drove over 20 miles before it locked into GPS. This happens frequently. On the Incredible I never saw "Waiting for GPS" ever. Not once. Do I have to live with this? Is this the nature of the beast? Or do I have a faulty unit?
2. Data connection. Often when I try to do something data-wise such as the browser, etc. I get a message stating there's no data connection. I look at the notification bar and see that there are 3 or 4 bars in my signal strength area but no data information. There's no 3G, 1X or 4G indicator. Nothing. That area has just vanished from the notification bar. I've tried turning data on/off, I've tried going into and out of airplane mode, nothing turns data back on. I eventually have to hold the power button down and tap on "reset." That does the trick and I'll have data once it's reset. Again, is this normal or is there a setting somewhere where I can coax data into coming on. Or is this a faulty unit?
3. Screen dimming oddness. I have the car holder. I like it a lot. When I put it in the car holder I see the little lightning bolt over the battery indicator indicating it's charging. I have set the settings option to keep the screen on when it's plugged in so I can see the maps while driving. However, after a period of time the screen goes dim. It doesn't turn off, just dim. Touching the screen brings it to full brightness. However, that's dangerous while driving.
When this happens I notice that the lightning bolt doesn't appear over the battery any more. It's as if the charger stopped charging and I am running on battery. However, that can't be the case since the battery never drains. Even after 5 hours of driving the battery doesn't go down. It just doesn't have a lighting bolt and the screen will go dim. I can dismount and remount the phone in the car holder and the lightning bolt will reappear. As long as the lightning bolt is there the screen won't dim. But after a while the lightning bolt goes away and the screen will dim again. This is very annoying.
Any help on these issues would be greatly appreciated.
Here are details on my phone. Stock Android, not rooted. Android 2.2.1 Build: 1.13.605.7
Thanks in advance
Click to expand...
Click to collapse
I have had these problems on stock, rooted, and custom ROMs, esp the data signal disappearing and also the screen dimming while using google maps. Not sure what the problem is. Make sure you leave wifi on when using gps also, this will help it get locks faster.
nrfitchett4 said:
I have had these problems on stock, rooted, and custom ROMs, esp the data signal disappearing and also the screen dimming while using google maps. Not sure what the problem is. Make sure you leave wifi on when using gps also, this will help it get locks faster.
Click to expand...
Click to collapse
I actually have wifi hotspot turned on when I travel so I can use my Galaxy Tab on the Internet. So, leaving wifi on isn't a real option. However, the tips above seemed to have fixed the GPS lock.