Database Develop

Touch Screen Issues

I have a stock N1, updated to Froyo. So every now and then, ever since I got the phone, the screen just stops responding when waking it up. Sometimes, the screen doesn't turn on at all, but the soft buttons light up. And the only way I've found to fix the problem is to either restart the phone, or connect it to my USB.
Was wondering if it's a hardware or software issue?

same thing happening to me aswell...seems to be only since Froyo flash. Really crappy when you are trying to show off the phone and you have to reboot first. Im gonna mess around a bit tonight and see if I figure anything out...Im also not getting any trackball notifications... I think its software related, for now.

I can say it's not Froyo since I've had this problem before the update, unfortunately.

mailliw320 said:
I can say it's not Froyo since I've had this problem before the update, unfortunately.
Click to expand...
Click to collapse
Ok some weird stuff going on for sure..
With CM 5.0.6 every couple days I would the keyboard would "uncalibrate", but the screen would never freeze up.
Since installing Froyo I am getting the freezing and unresponsive screen at least once a day.
Lets hope my it is not my screen getting worse. Ill have to flash back to CM 5.0.6 and see if I still get freezing.
Bye bye Froyo, see you in a couple days!!

So...anyone else with this issue pre-Froyo?

ive never had my nexus freeze, then i flashed froyo and that day it froze for about a minute, now it has done the hard sleep thing and it does it more times per day each subsequent day.
I know that we have an early "test" version of froyo so this stuff isnt grave, but since there seem to be groups of people experiencing different issues, i also wonder if its possible that specific apps can cause problems unrelated to the app since they arent really ready for froyo...is that possible and does anyone know of apps to beware of? not so much apps that dont work but apps that cause other problems?
Edit: my phone is stock by the way

i used to have a lot of problems when i switched from landscape to portrait mode with the calibrations but since ive put on 2.2 that problem is long gone and i have no other issues...

I had shocking touchscreen issues on 5.0.6, to the point where the phone was unusable and I had to reboot or pull the battery. Turning the screen off and on using power button would work occasionally but not always. Unfortunately I am still having the occasional problem on froyo. I had some mates trying to troubleshoot for me and took a few logs, the recurring error was (CM 5.0.6):
I/InputDevice( 117): Dropping bad point #1: newY=176 closestDy=3401 maxDy=2779
I haven't taken a log while on froyo

Thanks for the input, fellas. Sounds like it's a more apparent issue in this test release of Froyo. I've had the issue since before flashing the update, with stock 2.1, but it's sounding like it's software related and nothing actually wrong with my phone. Guess I won't bother contacting HTC haha

Nexus One Restarting Randomly! Help!

Hey guys,
I was hoping someone here could help me out. I just got my Nexus one Today, and I am charging it as we speak. But anyways I was playing around with it while it charges and it randomly crashes and restarts on me. I already did the auto update over the air to FROYO, but it is still doing the same thing. Also it seems to do it mainly in apps that use the gps, for example the compass app will do it every time.
It took me a month to get this phone to me in Costa Rica, and it would be way outside my available time and budget to get it replaced. So I hope it is a software problem, maybe some way to do a swipe or something.
PS: I already tried wiping it from the settings options, but it didn't help. Also I would like to root this phone, but I am to afraid now as I don't know if there is a hardware problem with it.
Thanks for you help, it is much appreciated!

I think random reboots are standard on the nexus. Mines stock and I've had the problem since I got it. But it only happens every couple days or so so im not too worried. How often is yours rebooting?

No this is every 5min.
But I think I figured it out. First off I realized it only happened with sim card in. Then I realized it only happened when I forced the WCDMA, which I need for 3g in Costa Rica. Then I realized that if I enabled roaming, even though I am not, and Left WCDMA on forced, it also stoped. So that is what I did, and it has been going for 30min now. Fingers crossed.
I am still going to get the official Froyo and place it on the sd card then wipe in recovery and update. Just for safety.
So yeah Looks like software issue. Which is really good for me! If it keeps working I am going to root it soon, can't stand that white notification bar

[SOLVED] All of a sudden I get horrible battery drain.

I am running the stock V10c ROM with 0405 Baseband and root.
Until recently I had little to complain about, but since last Saturday my phone has a horrible battery drain.
It turns off within 6 hours after I unplugged it even tho I did not use it and it was sitting calm in my pocket. This happend for the third time now since Saturday.
I was suspecting the recently installed Vlingo or Google+ Apps, but after removing them I still have the same issue. I recalibrated the battery yesterday but the Phone turned off again today.
I recharged it just now and it got incredibly hot like it has never been before.... this is very strange.
Anyone else experiencing something similar?
Have there been any recently updated Apps that are said to cause battery problems (Google Maps got a recent Update...)?
Any suggestions?
(I hope that damn OTA update comes soon and fixes this otherwise I'll have to update it manually or will have to install a custom ROM.)
EDIT
I flashed MoDaCo's MCR Fr19 and the Problem is gone.
I guess a factory reset would have solved my problem as well, but since I had all the work with backing up and restoring anyway I have chosen to go with a nice custom ROM.
Everything works like a charm again!

I used to get horrible battery drain, and generally the battery stats would have a mind of their own and change at random..... sometimes a phone restart would fix this, sometimes not. This was the biggest problem I had with the phone, but by no means the only problem.
I was always on stock, but since flashing the newest Modaco ROM (FR19) I've not had a single problem, the phone actually works as the piece of high-tech gadgetry I expected it to in the beginning. It's been nearly 2 weeks since switching to a custom ROM, and finally I'm loving this phone. I was reluctant to do it earlier as I waiting for the official LG updates, but after all their tardiness I decided enough was enough and went Modaco.
My advice: if you're unhappy with the phone as it is, try at the very least 1 custom ROM (both Modaco and Cyanogen are popular) and see if it improves your experience.

I have this problem too sometime
Only solution is to turn off the phone and turn and everything become normal
But after sime day if use same happens again. I suspect there is a program start to run in bg non stop
Btw i am in fear edition 12.2
Sent from my LG-P990 using XDA App

Ermmm.... correct me if im wrong, but to my knowledge v10c roms uses 622 RIL.. which has a 622 basebnd too.. why are still on 405 baseband? I really recommend 622 baseband as its the least power hungry baseband I've used since 405, but then again, some other factors might affect ur battery too.. but alot of ppl give positive comments on 622 baseband
.. shld give it a try.
Sent from my LG-P990 using XDA Premium App

Thanks for your replies!
@Crofteh
I am generally a big fan of custom ROMs and always used one on my last android phone, but I liked the stock LG ROM enough to keep it until Gingerbread would arrive. I hoped to test official LG GB without wiping and then upgrade to a GB build of MoDaCo or CM.
That is what I thought, but who knows how long LG will still need for GB.
@Netuser
Thanks, I also suspect some App to uselessly run non stop as the phone feels warm near the camera, which indicated SoC load.
@tablights
I have the unbranded German version which came with a V10b ROM and a baseband number I forgot. After updating via the LG PC tool it changed to V10c and 0405 Baseband. Since that there was no official Baseband update for my phone. As far as I know, the German Vodafone branded phones got the 622 Baseband in last weeks update.
I will try to manually update to V10e via KDZ updater since it apparently does not wipe in the procedure.
Should the issue still persist I'll give MDC r19 a try.

I think the best bet to avoid the heating problem is to remove the micro SD card. Or try another one not greater than 8G. Don't use 16G or 32G - less costly for you if it burns out.

How is that related to the SD card? My 16GB card worked flawlessly all the time.

Same here
Hi,
I had exactly the same Problem, Phone got incredibly hot, was always warm even in airplane mode and died after 5h in stand-by. I tried all Basebands, different ROMs, reseted the battery stats several times, tried charging and uncharging several times. I logged the battery usage and got it down to maybe 20mA which should give me something like 75h in standby, still the phone shut off after 5-6h. I didn't use a SD-Card so it had nothing to do with that and it didn't change with different Software so i'm sorry to report: it may be a hardware problem. Either the battery broke or the handset itself didn't survive the temperature and is now draining (you could try another battery).
I sent my in and DHL lost the packet so no more Info from my side
btw, i also had the german version bought at Amazon.
Good luck finding the Problem !

I hope it won't be necessary to send it in. At the moment I am trying to rule out all possible causes. I signed out from the google labs project that lets you download parts of maps, since I activated that shortly before the problems begun and I could imagine that constantly downloading maps could cause high battery drain.
I have no time to do a custom ROM install including all backup and restore stuff atm as I am busy writing my diploma thesis for the next two weeks. But I will try that if nothing else helps. If that does not help, I will send it back.
Did you get an replacement or a refund?
If you got a replacement, does it have any issues like backlight bleeding ?
If you got a refund, did they pay the price you bought it for or the price it costs now? Cause there is a steep difference in price from then to now.

Juice Defender?
I had the problem and the problem is solved after I install juice defender.

I'm still in the process of getting a refund.
I think they will pay what i payed. But it is exhausting getting them to do anything and while i do that I'm back to my good old and terribly slow G1

Good luck with that!
Would be nice if you could let me know how this was resolved so that I can decide what is the best way to go should things not get better.
Thanks!

Still having text messaging problems

Ok well I had a post before that I was having problems texting after update and root. well we thought it was the phone so verizon sent me a new one. I can receive perfectly fine but I cant send even on the new phone. I got the phone yesterday afternoon got it all set up on gingerbread rooted it then flashed with gingervolt v 1.2. Everything was working great last night then first thing this am bam no texting again. I got the v7 tot file and re flashed and it seems to be working again. For how long who knows but I am hoping someone may have a little info. Verizon has a ticket on it but something tells me it wont go anywhere.

jfl14609 said:
Ok well I had a post before that I was having problems texting after update and root. well we thought it was the phone so verizon sent me a new one. I can receive perfectly fine but I cant send even on the new phone. I got the phone yesterday afternoon got it all set up on gingerbread rooted it then flashed with gingervolt v 1.2. Everything was working great last night then first thing this am bam no texting again. I got the v7 tot file and re flashed and it seems to be working again. For how long who knows but I am hoping someone may have a little info. Verizon has a ticket on it but something tells me it wont go anywhere.
Click to expand...
Click to collapse
Are you using any 3rd party programs for texting or just stock?
I've had this problem before but only with a single person, my uncle, who uses AT&T (Only person with AT&T I text. AT&T has horrible service in my area so almost no one has them here) To make it so he'd receive my texts, I would have to completely delete my text thread and send a new message. He's the only person I've had problems with and deleting the thread fixes it every time.
Perhaps Re-flashing is working because in the process it is deleting your thread? Hope this helps!

I wish it were that simple when it goes it goes and i cant text anyone

So I am guessing no one has this issue with rooting or gingervolt? I am just curious because I love the speed and stability of gingervolt but I have been afraid that its somehow the cause. Now using the tot file v7 restores it to stock right so if it were a problem with the root or gv 1.2 this would get rid of it because its 100% stock right?

http://forum.xda-developers.com/showthread.php?t=1331603
Your previous post (For other users)
I've been lurking the gingerbread mod forums a lot and this is the first I've heard of this specific problem. Though that doesn't mean someone else isn't having the same problem.
You only get stuck when going into Gingervolt, but V7 seems to work for you? Have you tried staying in V7 w/o gingervolt for a few days just to see if the problem comes back or not?

Been on just straight v7 and it did it again man this is getting frustrating

I've had this problem on and off with the phone ever since i got it (so stock v4, R1.5, GV1.2). For me, it occasionally sits with the outgoing arrow moving, as if it were trying to send in area with no service. The workaround that i've used has been going to airplane mode which sometimes works, or more frequently, eating a reboot. Sometimes this results in them receiving duplicate texts. when i complained to Verizon they claimed it was common...

pendragon11 said:
I've had this problem on and off with the phone ever since i got it (so stock v4, R1.5, GV1.2). For me, it occasionally sits with the outgoing arrow moving, as if it were trying to send in area with no service. The workaround that i've used has been going to airplane mode which sometimes works, or more frequently, eating a reboot. Sometimes this results in them receiving duplicate texts. when i complained to Verizon they claimed it was common...
Click to expand...
Click to collapse
I used to have this issue, but it either resolved itself or something I did fixed it, but I have no idea what that something might have been.
I'm currently waiting on a replacement phone due to my USB connection no longer working, so we'll see if this problem makes a comeback. If you see me on IRC feel free to hit me up...I have some vague ideas as to what I might have changed that eliminated the issue, that's not a service guarantee though.

Looks as though its time to change forums. Verizon is switching me to a droid charge cant wait to see how this goes

Do any ROMs fix the shutdown problem?

I tried to search but alas Tapatalk isn't very good at that.
I bought a Captivate via eBay. Before I press to return it, is there a fix or ROM that fixes the dreaded random shutoffs? I tried resets and the GB Serenity ROM but alas I'm still encountering it...rather frequently. Every hour or less it'll shut off. So, other than the battery draining Captivate Keep Alive app...is there a real solution?

barring anything physical with your phone .. I have not had any sleep deaths or random reboots since switching to Fusion-CM-ICS-beta. It used to be a chronic issue with my phone.

Thanks for the fast reply Garyth. I'll give it a go.

I've heard the aosp roms seem to help the problem (this includes the ICS roms). They use different drivers than Samsung roms.

So far, so good. Data is consistently faster as well. Thanks again!

Hmm. Still getting random yet pervasive shut downs.

I believe this was a known hardware issue as well. There is a thread around somewhere will effected build numbers.

I saw that thread and don't believe mine is in the range. I'll be calling the seller tomorrow anyway.

Not sure if you are in the same boat as me, since the IMEI of my phone does fall into that catergory of the "recalled" phones, but since it was out of warranty by the time I saw that post, they wouldn't exchange it at the store.
At any rate, here's what I've gone thru:
Back in the Froyo times, I "think" CM7 fixed the issue, but I was too fidgety at the time so I was always trying new roms so I don't remember 100% if that was true or not.
I read somewhere that this could be caused by the battery shifting around due to temp changes as it charge/discharges, and that you should put some electrical tape or whatever to make sure your batt. made good contact. Didn't work for me at all.
So finally what fixed the problem was Captivate Keep Alive app, it's in the market.
First I tried it with two ICS roms: ICSSGS and Fusion, with Platypus and IcyGlitch kernels. The app work fine with a setting of 85%, but I was getting "charge death" as well, which I've never had before.
So now I've rolled back to KK4 (Serenity ROM) with the latest Corn kernel, and for some reason I have to set the app to 80% charge but works.
There'll be definitely an increase in battery drain, but for me it hasn't been that bad.

I used to have that problem when I first got my cappy, had froyo KB1 on it, and it would randomly shut down. Eventually when I got into hacking the android, when I finally updated to newer bootloaders, the problem went away. Though I can't recommend flashing bootloaders, since you can hard brick your phone if unsuccessful. Just saying that's what seemed to solve the problem for me.

mrhaley30705 said:
I've heard the aosp roms seem to help the problem (this includes the ICS roms). They use different drivers than Samsung roms.
Click to expand...
Click to collapse
Can anyone confirm this?
crt60 said:
I used to have that problem when I first got my cappy, had froyo KB1 on it, and it would randomly shut down. Eventually when I got into hacking the android, when I finally updated to newer bootloaders, the problem went away. Though I can't recommend flashing bootloaders, since you can hard brick your phone if unsuccessful. Just saying that's what seemed to solve the problem for me.
Click to expand...
Click to collapse
But what bootloader fix that to you?

Mine only rebooted randomly once when on eclair. Haven't had a problem in gb or ics.
Posted from my ICS'd Captivate

That would help if eclair wasn't completely useless.
Sent from my Samsung Captivate running Team ICSSGS 4.0.3

I tried Captivate Keep Alive. Even it didn't work. A replacement phone is on its way. The IMEI was actually affected, but I didn't realize at first because I only looked at the last digits. Apparently was a really early build. The seller photographed the new IMEI before shipping it out so I could verify.

I have Dark Knight's 4.0.4 ROM since 2 weeks ago.
At the moment, and I hope it remains 0 reboots.
Just wanna share with you, is up to you to try it....
http://forum.xda-developers.com/showthread.php?t=1501615
By the way, with this ROM also I got the best Quandrant Benchamark score (2400) without overcloking...

I'll keep that in mind but I got a replacement that works really well. I ended up getting it from another seller though.