Related
Does anyone else have a problem with holding down the power button?
When I hold down the button my Nexus only registers it as pressing it and letting go and usually just turns off the screen. It's quite frustrating when I need to turn off my N1 or set airplane mode, and usually takes half a dozen tries before it actually registers as holding down the button and not just pressing it.
I fear it may be a hardware issue and I will have to return it.
I got the same issue. Not sure if it is soft- or hardware related. Also having problem with waking up. Works well with the track ball so I guess it's the hardware.
I'm really dreading having to send this back to HTC. Everything else on this device has been working normally, but I also have an unlocked bootloader. I'm reluctant to trade it in.
andythefan said:
I'm really dreading having to send this back to HTC. Everything else on this device has been working normally, but I also have an unlocked bootloader. I'm reluctant to trade it in.
Click to expand...
Click to collapse
Mine is doing the same thing.
Here's a good test.
Do a nandroid backup, and then flash back to the stock ROM. I haven't done this yet, and am planning to do so this weekend.
If you flash back to stock and the power button works normally, well there you go.
If not, it's a hardware issue.
I will say that I've been using a Desire2Nexus port ROM and it definitely happens more with this ROM than the CM-based ROMs, but that could also be due to the laggy/sluggishness of SenseUI.
I was seeing the same problem in both ROMs of recent generation though. So my gut tells me it's a hardware issue. Flashing to stock and testing it out will be a dead giveaway, though.
HTC has historically been pretty good about replacing known hardware malfunctions. I also bought SquareTrade coverage just in case, though, so I will be getting my money back one way or another.
maxawesome said:
Mine is doing the same thing.
Here's a good test.
Do a nandroid backup, and then flash back to the stock ROM. I haven't done this yet, and am planning to do so this weekend.
If you flash back to stock and the power button works normally, well there you go.
If not, it's a hardware issue.
Click to expand...
Click to collapse
I've wiped and flashed the last stable CM version. The issue persists. Also, it happens when I'm in recovery as well, so I'm afraid it may be a hardware related issue.
Can I still send this in for replacement if the bootloader is unlocked? When I be charged repairs in that regard?
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts
so, i've been using xda for a while now and i would like to start thanking all the contributors and the nice android community there is.
today i'm posting my 1st post and it's not for good reasons...
i got my sgs [i9000 international] on september and i have to say it has been nothing but problems.
it was working ok but then came along the 1st issue - unable to receive text messages. it would just stop to receive them and i would have to place the sim card on another phone receive the 50 sms or so i was supposed to have been receiving and then place the sim card back on the sgs and it would be fine for 5 days or so and the problem would begin again and i must say walking around with 2 mobile phones is just stupid when i only need 1...
in order to solve this and some other lags the phone had i decided to update to 2.2. in portugal there's no official update in kies (at least for me...) so i decided to go custom rom. i went with doc's rom BUJP8 V9.0.1 non-wipe and then voodoo's lag fix and i finally had the mobile phone i always wanted. then came along another issue - unable to receive phone calls (it doesn't receive sms and phone calls, what kind of a mobile phone is this?!). when someone is calling me, the phone lights up, it says there's no network available, it regains the signal and i don't even know who called!
now, i don't know what to do, i have a sgs that just doesn't work and i don't know what i'm supposed to do. this thing cost me a lot of money and i just don't want to waste it, all i really want is a proper mobile phone, i want the sgs!
i would appreciate any help, tell me if i've done something wrong, what i can do to have this working.
thanks in advance
~galaxydroids
ps: sorry for the english, as i've said i'm from lisbon, portugal
the attachment shows the sgs info after the custom rom flash
Sounds really weird indeed.
Have you tried hard-reseting your phone?
Does it still do the same after a hard-reset?
Maybe there is something wrong with the phones hardware it you keep loosing signal, where other phones works perfectly.
I would say, try putting in stock ROM (2.1 for Portugal?) and see it the problems still occur. If they do, maybe you should send it in for repair.
so i was kind of avoiding the hard reset but went for it.
now the phone is...well... isn't. it did everything, rebooted and now the two led buttons are lighted up and the phone randomly vibrates. that's it. it's been like this for quite some time now. is this supposed to happen?
Mine started to do that after a reboot also I just reinstalled the rom and its working for now.
Sent from my GT-P1000 using Tapatalk
how did you reinstall the rom? i can't even connect it to the computer...
Using download mode, I guess...
yeah well i can't get into download or recovery mode, neither one of them, i've tried all the combos with the keys...
if i'm unable to get into download mode how can i use odin?
my guess is that your problem might be due to your carrier... I don't know over there in portugal, but I've always heard vodafone isn't very good....
I have same phone, international version, bought on sept. mine came from handtec.co.uk...
if your phone is like mine, you should be able to enter download mode, just hold down the volume down key + home key + power key.. in that order, you should see your phone boot to download mode.
Hope it helps
I have a samsung captivate. It is a early model, I got it the day they became available. The phone will not always answer an incoming call. the green answer button comes up but will not swipe. Anyone else have this problem? Will froyo cure this?
Youre gonna need to add some more info....
are you on stock 2.1?
if you did flash a custom Rom which one and which kernel/ modem are you using?
Did you do a restore with titanium? (this is where I had problems when I flashed)
captivate wont answer incoming calls Sometimes
yes complete stock, no mods whatsoever
I had a problem like this when I first got my Captivate as well. My problem was that it wouldn't swipe all the way across the screen. This got very frustrating while driving. The solution, surprisingly, was to make sure my hands weren't completely dry. Without traction on the screen my phone didn't register my fingers.
I don't know if that'll help but there are also other dialers out there on the market that you can try legitimately without rooting or flashing a different ROM (if you're trying to avoid doing those things).
I would do a flash back to stock and do a master clear to rule out any software issues. You can do this without having to root. You just wont be able to back up your apps and system config.
Sent from my SAMSUNG-SGH-I897 using XDA App
It is and always has been completly stock.
Are you rooted? I had this problem every now and then... not very often.. I figured it was due to one of the apps I was running in the background, that was sucking up all the RAM and the phone became unresponsive. I backed up my apps, and flashed stock and then restored only the ones I absolutely wanted... I am sorry, I dont remember which app it was, just know that it was a background process that was collecting some kind of stats! Hope that helps!
By the way how long ago did this start happening?
rskeeters said:
I have a samsung captivate. It is a early model, I got it the day they became available. The phone will not always answer an incoming call. the green answer button comes up but will not swipe. Anyone else have this problem? Will froyo cure this?
Click to expand...
Click to collapse
i had a similar problem even tho i had a custom rom my incoming calls didnt come in at all.i had to Reflash my rom.. idk how similar this situation is but i agree with the other guys.. try reflashing stock
phone is not rooted. I cant tell you how long it has been happening but it appears to be more frequent as of late. The one thing I can ad, when it does it, it may do it several times in a row
Thank you guys for helping the newb.. I appreciat the input!
I occasionally get the same problem on my SGS even before rooting
Sent from my GT-I9000 using Tapatalk
The time it took you to go back and forth on this forum, you could have flashed back to stock and master clear to troubleshoot. The problem isn't going to fix itself.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks for all the HELPFUL input
I will try flashing stock
This may be a common sense answer but usually when it doesnt swipe all the way accross for me its because of to much grease ( or sweat) on my hands or on the screen like after lengthy phone calls or if my hands are dirty or something. Try cleaning the screen well, and washing your hands and such. Always fixed for me.
by swipe do you mean it doesnt move at ALL or it goes half way or you cant get it all the way to the other side to answer?
Yeah, i know that when i first turn on my phone and try swiping, nothing will happen, it will just stay green and not respond. After leaving my phone on for a couple of minutes, it usually corrects itself.
This is also a common problem for stock users wanting to use a lockscreen replacement (i.e. widgetlocker).
If you try using widgetlocker without any lagfix, you can get phone call screens you can't interact with for a few seconds.
I have had a similar issue both stock and rommed. I find a lot of time it does have something to do with friction on the screen but also if I have low signal it will happen as well. My phone will actually freeze up to the point of having to remove the battery, this same thing happened on my old Samsung Blackjack II.
Sent from my SAMSUNG-SGH-I897 using XDA App
Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign
^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.
I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.
A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.