First g2x rebooted constantly. Froze up on charger. Required battery pull.
New g2x hasn't rebooted yet. Same SIM card.
My guess is that if yours reboots you got a dud and should exchange it.
strung said:
First g2x rebooted constantly. Froze up on charger. Required battery pull.
New g2x hasn't rebooted yet. Same SIM card.
My guess is that if yours reboots you got a dud and should exchange it.
Click to expand...
Click to collapse
http://www.petitiononline.com/LGO2XPrb/petition.html
strung said:
First g2x rebooted constantly. Froze up on charger. Required battery pull.
New g2x hasn't rebooted yet. Same SIM card.
My guess is that if yours reboots you got a dud and should exchange it.
Click to expand...
Click to collapse
The same happened to me. First phone suffered from reboots.
My replacement is fine but I still haven't root it, so I blamed it on the root process.
Is yours rooted?
To counter your point..
Original G2X - rebooted a lot but then removing apps, software changes have made it more stable. Usually go 3+ days without a reboot
Replacement G2X (sent back) - rebooted just like my first one so i didn't even bother removing apps. SAME BATTERY AS ORIGINAL!
I also think it's mainly the battery which is what you're seeing by getting a replacement. I think some batteries don't charge properly so there are times when the voltage drops too much to sustain the phone causing a lock/reboot. I've been monitoring my phone and the more I think about it the more I realize most of my reboots happen after I had taken it off the charger at 100%. I can use it without charging it and it never reboots. Also battery monitor widgets,etc. cause reboots which all comes back to a bad battery or horrible battery driver which CM devs have already said existed.
After months of being in denial about the same problem which has plagued the O2X since launch, a couple of weeks ago LG Europe acknowledged the problem publicly and said it was software.
http://translate.google.com/transla...alligevel-problemer-med-optimus-2x,lid.15324/
Here's the post on the O2X forum that discusses the problem in gory detail. Interestingly, it says the Atrix is having a similar issue which could certainly point to the processor.
http://forum.xda-developers.com/showthread.php?t=1041546
The rebooting is a software issue. The only time my phone rebooted was when I installed an app (Fring). After I uninstalled it, no issues.
Sent from my LG-P999 using XDA App
sstang2006 said:
The same happened to me. First phone suffered from reboots.
My replacement is fine but I still haven't root it, so I blamed it on the root process.
Is yours rooted?
Click to expand...
Click to collapse
Neither were rooted. Also, rooting in and of itself is incidental; it would not affect the issue as rooting does not change any of the kernel files.
mobilehavoc said:
I also think it's mainly the battery which is what you're seeing by getting a replacement. I think some batteries don't charge properly so there are times when the voltage drops too much to sustain the phone causing a lock/reboot. I've been monitoring my phone and the more I think about it the more I realize most of my reboots happen after I had taken it off the charger at 100%. I can use it without charging it and it never reboots. Also battery monitor widgets,etc. cause reboots which all comes back to a bad battery or horrible battery driver which CM devs have already said existed.
Click to expand...
Click to collapse
Very interesting. This corresponds to what I experienced, and I think you may be on to something here.
kangxi said:
The rebooting is a software issue. The only time my phone rebooted was when I installed an app (Fring). After I uninstalled it, no issues.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess I have been one of the lucky ones. I bought my phone on the 22nd and have never had a reboot or lock up happen. Also my lcd bleeding is pretty minimal. Im still exchanging my phone for a new one because the little black piece of plastic that covers the camera just fell off one day plus I have a dead pixel on the screen that driving me nuts.
sstang2006 said:
The same happened to me. First phone suffered from reboots.
My replacement is fine but I still haven't root it, so I blamed it on the root process.
Is yours rooted?
Click to expand...
Click to collapse
It is not the root process. I thought the same thing the first night after I rooted. The phone would not stay on for more than 5 minutes. The store rep did not believe me and tried his sim card and sure enough after five minutes sitting on the counter it turned off and only by pulling the battery was he able to get is re-started. Some of the phones are screwed up. Swap it. My new one is running great except for the battery life.
strung said:
Neither were rooted. Also, rooting in and of itself is incidental; it would not affect the issue as rooting does not change any of the kernel files.
Click to expand...
Click to collapse
good to know
Are you serious with your response to my comment? That was unnecessary as I was being serious and many people can say the same.
Sent from my LG-P999 using XDA App
kangxi said:
Are you serious with your response to my comment? That was unnecessary as I was being serious and many people can say the same.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Oh. Sorry. It just seems that on a lot of threads where people post about problems they are having, you jump in say you don't have any issues and to uninstall something like Fring that works fine on every other phone, so I thought you were trolling.
sstang2006 said:
The same happened to me. First phone suffered from reboots.
My replacement is fine but I still haven't root it, so I blamed it on the root process.
Is yours rooted?
Click to expand...
Click to collapse
Although I often manually reboot the phone. I haven't seen one single auto-reboot or freeze, before or after root. So I don't think root is the cause of auto-reboot.
All bloatware are there and running, sometimes I manually close CarHome and TeleNav after reboot, sometimes I forget to do so.
From what I've seen, auto-reboot does look like a hardware problem. To be more specific, those devices are defective.
rhinology said:
Although I often manually reboot the phone. I haven't seen one single auto-reboot or freeze, before or after root. So I don't think root is the cause of auto-reboot.
All bloatware are there and running, sometimes I manually close CarHome and TeleNav after reboot, sometimes I forget to do so.
From what I've seen, auto-reboot does look like a hardware problem. To be more specific, those devices are defective.
Click to expand...
Click to collapse
Just jinxed myself. Right after I replied to this thread I saw first freeze. After pulling battery and putting it back I saw "System Checking..." upon booting, and many force closes after boot was completed.
strung said:
Oh. Sorry. It just seems that on a lot of threads where people post about problems they are having, you jump in say you don't have any issues and to uninstall something like Fring that works fine on every other phone, so I thought you were trolling.
Click to expand...
Click to collapse
Just offering what worked for me. If that's not the case then just return your phone. You can keep getting a new one or listen. There's nothing wrong with the phone that a software update probably wouldn't fix.
Sent from my LG-P999 using XDA App
I think its HW. If its SW it doesn't explain why one phone would reboot and a replacement would not.
almostinsane said:
I think its HW. If its SW it doesn't explain why one phone would reboot and a replacement would not.
Click to expand...
Click to collapse
+1
Someone explain how the first phone reboots and the replacement does not ( same apps, same usage).
sstang2006 said:
+1
Someone explain how the first phone reboots and the replacement does not ( same apps, same usage).
Click to expand...
Click to collapse
My 2nd phone has no auto shutdown yet, but I am using new sim card. My ex G2X was using the old sim card.
My week old today G2x, 4/11/11 build, has never rebooted by itself. The only problems I'm having are flaky behavior switching wifi calling on and off automatically and some back light bleed.
As for how one phone reboots and others don't, it could be software or not. In order to really know for sure you would have to be absolutely certain you had the exact same apps installed in the exact same order, be in the same location at the same time and under the same conditions and loads.
nraudigy2 said:
My 2nd phone has no auto shutdown yet, but I am using new sim card. My ex G2X was using the old sim card.
Click to expand...
Click to collapse
That could be the cause, since my previous phone suffered from reboots and I was using the old SIM. I started using the new SIM since day one with this phone and still no reboots..
Related
I know theres a poll on issues etc and rebooting is mentioned, but I feel it was too early to poll and people could have voted and had a reboot after...
So question is..... has your phone rebooted? Or just fine?
Also if you could mention how long you had it that would be great....
I just want to know exactly who is having reboots and who hasn't..
Not once on its own.
Sent from my LG-P999 using XDA Premium App
None so far.
None so far.
Zero.
Sent from my LG-P999 using XDA App
LOTS of reboots
I have had about 20 in two weeks. I am CURRENTLY getting CONTINUOUS reboots.
It had the LG logo and thinking bar, underneath it said "System checking". Now it has rebooted non-stop (6 times so far as I'm typing).
New phone should arrive on my doorstep within the next hour or so... fingers crossed.
once that I know of. No idea why. It just rebooted while on my desk idle.
In the one week I had the phone (preroot), never. Even after rooting it, never.
Haven't had any issues with mine.
Had 3 reboots in 5 days on my old phone. Nothing yet on new one so far. It has been 3 days. I noticed my old phone was alot hotter than this one. Possibly a hardware issue after all.
Guys, try to turn off gps, I did that and I have 0 reboot and 0 shut down today, I had a lot of reboots and phone turning off by itself before that. I'll see what happens when I charge it tonight and I'll let u guys know.
Sent from my LG-P999 using XDA App
Theres got to be something thats causing it.
results don't look so good..
Hmmm prerooted I had maybe one and some freezing and lag..
rooted no reboots except running eaglesblood rom and experimental kernel with pauls lag apparentky too much going on there. .
If your phone is rebooting constantly don't even waste your time return it for a new unit. The att galaxy s had the same prob and everyone waited for a fix only to find out it was hardware related....if your in the 14 day window don't even waste your time and end up with a refurb
Sent from my LG-P999 using XDA App
I bought my g2x a day after launch. For a few days, I didn't experience any reboots. After that they starting happening but not too often. Eventually (by yesterday), it was happening more often. Somewhere in that time frame I did a factory reset to try to improve battery life.
I called tmobile support yesterday and they made do another factory reset and not install any apps. It has been 16 hours without a reboot but that doesn't prove anything, really. First, it doesn't necessarily happen every day. Second, without any non-default apps installed, it may not be taxing the device enough. Third, even if it is an app's fault, it may not be directly the apps fault. Am I supposed to run no apps if that turns out to be the problem?
They will be calling back at three and I'm going to try to push them for a replacement. I'm also having reception issues and the battery could certainly last longer.
None here, gps is not turned off
Sent from my LG-P999 using XDA Premium App
I am on my 5th G2X... with a build date of 4/3/2011 and I have not had a reboot as of yet with GPS turned on. This has also been the best phone out of all those 5, I have a week left and if I experience problems I will be taking it back. As somoene said dont waste your time your better off returning it then waiting for a fix.
Berat said:
I am on my 5th G2X... with a build date of 4/3/2011 and I have not had a reboot as of yet with GPS turned on. This has also been the best phone out of all those 5, I have a week left and if I experience problems I will be taking it back. As somoene said dont waste your time your better off returning it then waiting for a fix.
Click to expand...
Click to collapse
Any advice on what to tell them so they'll take it back? The tmobile phone tech wants me to prove that it isn't an app...
none so far got it on May 3rd..
oldbustedjorn said:
Any advice on what to tell them so they'll take it back? The tmobile phone tech wants me to prove that it isn't an app...
Click to expand...
Click to collapse
I just took it to the store, told them the problems I was having mentioned the reboots, screen bleed, and data connection issues. Told them I was within the 14days and that Customer Care told me to come to the store and try and get a working phone. I wouldnt talk about the reboots as it may not happen in store if you have screen bleed its easier that way cause you can prove that.
Did you buy it in store, online or over the phone?
I sure as hell will. Wondering who here is ready to return if their phone reboots after update. T mobile will be so swamped if it doesn't fix it, and mine recently has started rebooting randomly, not too often. Just wondering if everyone here will return, if so, t mobile will have quite the ride with this one unless they do a recall.
Sent from my LG-P999 using XDA App
unique77 said:
I sure as hell will. Wondering who here is ready to return if their phone reboots after update. T mobile will be so swamped if it doesn't fix it, and mine recently has started rebooting randomly, not too often. Just wondering if everyone here will return, if so, t mobile will have quite the ride with this one unless they do a recall.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I would for sure.
Yep. Although there isn't much left in the t-mo lineup that is tempting.
liquidblue1985 said:
Although there isn't much left in the t-mo lineup that is tempting.
Click to expand...
Click to collapse
My sentiments exactly.
I don't think LG is going to let it happened. It's something in the software that is conflicting with the hardware. I'm on customs ROM (CM7) and have not seen it rebooted once.
I will sell the phone if I will see new 2.3 gonna be slow than 2.2
(Im ready to buy Samsung Galaxy S II)
If the update or a battery swap doesn't fix my reboots,i would like to return it but I'm already past my 30 days.
Sent from my LG-P999 using XDA App
I would make them exchange it. How can they not if you tell them it interrupts calls with a reboot. Also someone else said in the topic about the o2x gingerbread delay that the g2x was pulled and he's getting a sensation. Not sure if that's true or not.
Sent from my LG-P999 using XDA App
shilent said:
If the update or a battery swap doesn't fix my reboots,i would like to return it but I'm already past my 30 days.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Doesn't it have an LG manufacturers warranty for 1 year?
Maybe just go through LG for a replacement.
Hoggles said:
Doesn't it have an LG manufacturers warranty for 1 year?
Maybe just go through LG for a replacement.
Click to expand...
Click to collapse
Would I get a refurbished?
Sent from my LG-P999 using XDA App
shilent said:
Would I get a refurbished?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
That I don't know. Most likely...
When you ask, "will you return it?" you realize that T-Mobile will not take it back for a refund outside the 14 or 30 day "buyers remorse" periods.
If you are outside that period, returning it for a refund or exchange for another phone of a different model is not an option.
And since the phone has not been available for nearly 30 days now, I dont see how ANYONE could still be within their buyers remorse period.
I was on the phone with an executive from T-Mobile today (not a customer service specialist, retention specialist or tech specialist... a real executive) and there is nothing that ANYONE of lower position at T-Mobile can do.
And as an FYI, the issue is happening with pre-rooted and un-modded phones AND rooted and custom rom phones. I have one of each sitting on my desk right now and both of them have the same issues.
If I jump off this ship the I won't get to see this phone mature.
It is such an awesome device and at least with me the reboots are not bad at all. Just like any other phone I had, nothing new nothing major.
This is going to be an awesome phone ones it matures.
Sent from my G2x
There's always the Sensation. I played with one at my Wal-Mart today and it is very light and small. I was shocked, tbh. I have very small hands, for a guy and it is quite comfortable. The only thing holding me back from pulling the trigger is that new return policy and the chance of a Nexus Two? Three? coming this Christmas.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will not jump to the Sensation unless they build a ROM that is without Sense. Sense is fun to play with but it's horrendous as a daily driver.
The Slide 4g or whatever does have me intrigued though. I just loves me some keyboard.
There is no way in hell I am getting another one of these. No way. They can't tell me when the update is coming and each phone has these different crazy personalities!
Mine did two completely new and screwy things today. Completely different than the wifi issues and shutting off type reboots, and screen bleed that this forth phone has been doing already.
First, today when I was at the local Walmart trying to see a Sensation, I took my phone out of my pocket and it was stuck in this loop. The notification screen looked like it was pulled half way down. It was spinning around between landscape and portrait, landscape and portrait over and over about once a second. Kind of looked like a slow motion propeller just goin' round and round. Landscape, portrait, landscape, portrait. Bizzarre. Had to pull the battery.... nothing else would work.
Then tonight, my battery was in the red zone. So I change batteries. I have to enter my code on my sim card before I can use my phone. It took forever to get to that sim screen, then I could not input anything. Finally held down the power off button, the power off screen shows but I cannot input hereeither..,,,,battery pull. Arggghhh!
Then I turn it on, and it takes forever....I mean two full minutes, then shows an error message.....
" Sorry!
The application com.lge omadmclient (process com. lge omadmclient) has stopped unexpectedly. Please try again"
With a "Force close" button
When I pushed the force close, it showed another error screen
"Sorry
The application Launcher pro (process android.process. a core) has stopped unecpectedly. Please try again."
This one had two choices.."Force close" and "Make report"
When I pushed FC, it went right to the former error screen.
Could not get out of this loop. Until I did a battery pull. Power off did not work.
This happened three times. Three times. Finally did an on/volume reset. Arggghhh!
More Weirdness.....
No....I don't want another. Thanks.
hiko36 said:
I will not jump to the Sensation unless they build a ROM that is without Sense. Sense is fun to play with but it's horrendous as a daily driver.
The Slide 4g or whatever does have me intrigued though. I just loves me some keyboard.
Click to expand...
Click to collapse
+1 I love sense for the eyes but sense bogs down the phone too much. I want my phone to be snappy as possible but it does look like a nice device.. Although I dont think it makes sense to jump ship for it. I think by late fall(which is only a few months a way ) something better will be out and I'll upgrade then The mytouch 4g slide does look interesting as well(I had the mt4g and loved it) Wonder how thick it will be. I really dont have any reboot issues with my g2x. I do have some screen bleed but I'm going to try to fix that I actually have 2 g2x's that's why I dont mind trying to open one up just to fix the screen bleed. The other got sent back to "LG" (really Steller Wireless) for major major screen bleed/screen separation. I hope that one comes back perfect but I'm not holding my breath. But I want to try to fix the one with minimal screen bleed myself
Oh I am going to stick this out to the buyer end... It is a beast... It had me at hello...
Sent from my butt using XDA Premium App
hell yeah...
Hi,
Was using my HTC Sensation the other day, all was working fine I was sending a text message when the phone suddenly went of. I tried to turn it back on but nothing happened, took the battery out and put it back in, tried again and nothing. Couldn't get into bootloader either. Thought it might be the battery so bought a new one but it doesn't work with that one either! When I plug it into my PC Windows sees it as QHSUSB_DLOAD but adb can't see it. Is this a hardware failure? Can it be fixed? So frustrating because if I send it back to HTC they'll see that it's rooted and they won't be happy >.<
If anyone can shed any light on what I should do that'd be great
Thanks in anticipation
lifeisfaked said:
Hi,
Was using my HTC Sensation the other day, all was working fine I was sending a text message when the phone suddenly went of. I tried to turn it back on but nothing happened, took the battery out and put it back in, tried again and nothing. Couldn't get into bootloader either. Thought it might be the battery so bought a new one but it doesn't work with that one either! When I plug it into my PC Windows sees it as QHSUSB_DLOAD but adb can't see it. Is this a hardware failure? Can it be fixed? So frustrating because if I send it back to HTC they'll see that it's rooted and they won't be happy >.<
If anyone can shed any light on what I should do that'd be great
Thanks in anticipation
Click to expand...
Click to collapse
Hi,
Look HERE
malybru said:
Hi,
Look HERE
Click to expand...
Click to collapse
Thanks for your reply, I've looked into this and it seems this only applies to devices bricked when trying to S-ON or when flashing hboot, mine just died when I was using it. I've contacted HTC and they are going to repair it for me - fingers crossed they don't notice it's rooted!
You we're only sending a text message and the phone bricked? That's so strange? Keep us posted and let us know how it goes with HTC repair. Did you install anything before you started the text message? Any mod, or anything? I wonder how it suddenly bricked? Or I wonder if it's a sort of hardware failure? I wish you the best and do hope they repair the device without any problems. Let us know how it goes. Best wishes
realsis said:
You we're only sending a text message and the phone bricked? That's so strange? Keep us posted and let us know how it goes with HTC repair. Did you install anything before you started the text message? Any mod, or anything? I wonder how it suddenly bricked? Or I wonder if it's a sort of hardware failure? I wish you the best and do hope they repair the device without any problems. Let us know how it goes. Best wishes
Click to expand...
Click to collapse
I was running JBMIUI with Sultan kernel. I was getting wifi problems with the latest build of that kernel so was in correspondence with the developer and was trying an older version of it which was a bit dodgy, maybe it killed a component I dunno! I have read into this QHUSB_DLOAD issue and from what I've heard the device is so bricked that they wont be able to tell it was rooted. Thanks, I really hope so too! Will keep you posted,
Regards,
Luke
lifeisfaked said:
I was running JBMIUI with Sultan kernel. I was getting wifi problems with the latest build of that kernel so was in correspondence with the developer and was trying an older version of it which was a bit dodgy, maybe it killed a component I dunno! I have read into this h issue and from what I've heard the device is so bricked that they wont be able to tell it was rooted. Thanks, I really hope so too! Will keep you posted,
Regards,
Luke
Click to expand...
Click to collapse
I don't see how that could've killed a component . Right now your Sensation is in download mode (all kernels, including mine, put the phone into download mode upon kernel panic). Maybe when your battery died a lot of bad luck happened because when a kernel panic happens the phone should've rebooted after 5 seconds (that's the default timeout for my kernel). Also, all previous and current versions of my kernels are stable and shouldn't cause components to randomly die. Have you looked at this video: http://www.youtube.com/watch?v=db5f3If-2Jw?
android1234567 said:
I don't see how that could've killed a component . Right now your Sensation is in download mode (all kernels, including mine, put the phone into download mode upon kernel panic). Maybe when your battery died a lot of bad luck happened because when a kernel panic happens the phone should've rebooted after 5 seconds (that's the default timeout for my kernel). Also, all previous and current versions of my kernels are stable and shouldn't cause components to randomly die. Have you looked at this video: http://www.youtube.com/watch?v=db5f3If-2Jw?
Click to expand...
Click to collapse
Sorry I didn't mean to cause offence by saying it was dodgy - the only thing that made me say that was the bug that meant that sometimes on r5 the CPU1 would not switch on and you had to reflash the kernel. Damnit, I probably should have had a go at the HTC Unbricking Project before I sent it off to HTC, This I do regret but I sort of panicked and thought the best option was to send it to HTC and hope they fix it. If they spot that it's been rooted they either charge you for the repair or send it back to you and charge £25 in courier costs. If they find it's rooted should I just pay them to fix it or do you think I have a good chance being able to fix it myself with the HTC Unbricking Project? The only reason I didn't embark upon the HTC Unbricking Project was that it explicitly said in the OP that it ONLY worked for devices bricked by switching s-on or flashing hboot, neither of which I was doing when my phone died. With hindsight though I probably should have still given it a try :/
You should do try try the unbrick project as I said earlier before paying HTC as u can pay them even after trying the project.
Sent from my htc using Tapatalk 2
lifeisfaked said:
Sorry I didn't mean to cause offence by saying it was dodgy - the only thing that made me say that was the bug that meant that sometimes on r5 the CPU1 would not switch on and you had to reflash the kernel. Damnit, I probably should have had a go at the HTC Unbricking Project before I sent it off to HTC, This I do regret but I sort of panicked and thought the best option was to send it to HTC and hope they fix it. If they spot that it's been rooted they either charge you for the repair or send it back to you and charge £25 in courier costs. If they find it's rooted should I just pay them to fix it or do you think I have a good chance being able to fix it myself with the HTC Unbricking Project? The only reason I didn't embark upon the HTC Unbricking Project was that it explicitly said in the OP that it ONLY worked for devices bricked by switching s-on or flashing hboot, neither of which I was doing when my phone died. With hindsight though I probably should have still given it a try :/
Click to expand...
Click to collapse
If there's a chance then you should always take it. If it didn't work then you probably could've bricked it more (maybe pull out the cable while the unbricker was doing something important) to make sure that HTC would never be able to find out that it's rooted. Also, that CPU1 bug only happened when you tried changing CPU governors from the default governor, performance (it happened because the default CPU governor was performance). To fix that you only had to reboot, not reflash the kernel . Good luck
android1234567 said:
If there's a chance then you should always take it. If it didn't work then you probably could've bricked it more (maybe pull out the cable while the unbricker was doing something important) to make sure that HTC would never be able to find out that it's rooted. Also, that CPU1 bug only happened when you tried changing CPU governors from the default governor, performance (it happened because the default CPU governor was performance). To fix that you only had to reboot, not reflash the kernel . Good luck
Click to expand...
Click to collapse
Hehe I think I'm more of a noob than I realise also I don't think it was just the kernel that went into panic mode - I freaked out and just wanted to have my phone back! I'm missing it so much haha let's just hope HTC fix it for free!
I am very lucky
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
They have replaced the mainboard and haven't charged me a penny good old HTC eh? Thanks for your support guys
lifeisfaked said:
I am very lucky
They have replaced the mainboard and haven't charged me a penny good old HTC eh? Thanks for your support guys
Click to expand...
Click to collapse
Congrats
Lol. I had the same yesterday. I was playing Asphalt 7 and HTC crashed. (I had a lot of crashes but basically it was able to turn on after 3-5 minutes http://forum.xda-developers.com/showthread.php?p=35937286) I'm trying to boot it up but my PC recognized it also as QSUSB_DLOAD.
Have they changed motherboard in your device a while ago? Cause they have for me and since that last repair I have these problems.
lifeisfaked said:
I am very lucky
They have replaced the mainboard and haven't charged me a penny good old HTC eh? Thanks for your support guys
Click to expand...
Click to collapse
Told u people at HTC are dumb A$$ lol
Sent from my htc using Tapatalk 2
so... seems like i have the same/nearly same problem.
i just sent a sms and my phone rebooted ---> stuck
so i thought i am restoring a backup i did yesterday... went into recovery..wiped dalvik and cache and wiped the rest. While wiping my phone rebooted again (no clue why). now i can sometimes boot into bootloader but everytime i try to go into recovery my phone reboots again.
windows installed qhsusb driver but nothing else..cant see it.. and i cant do anything else..my phone reboots when booting into recovery and thats it... what can i do? there must be something i can do, i can atleast reaching bootloader every 3. time i am trying too.
I used ViperS 1.6
Firmware 3.32
S-Off JuopunutBear unlocked
Any Idea?
EDIT: now i cant even get into bootloader..screen turns on but stays black guys help me please
Gudio142 said:
Lol. I had the same yesterday. I was playing Asphalt 7 and HTC crashed. (I had a lot of crashes but basically it was able to turn on after 3-5 minutes http://forum.xda-developers.com/showthread.php?p=35937286) I'm trying to boot it up but my PC recognized it also as QSUSB_DLOAD.
Have they changed motherboard in your device a while ago? Cause they have for me and since that last repair I have these problems.
Click to expand...
Click to collapse
This is the first time I've sent it to repair. I would try using the HTC Unbrick Project (see previous posts) and if that doesn't work I'd say you're pretty safe to send it to HTC. I would guess there's a been a hardware failure - especially if the device was having to work hard running a game. In which case they won't find out it's been rooted so you shouldn't have to pay.
Mydy said:
so... seems like i have the same/nearly same problem.
i just sent a sms and my phone rebooted ---> stuck
so i thought i am restoring a backup i did yesterday... went into recovery..wiped dalvik and cache and wiped the rest. While wiping my phone rebooted again (no clue why). now i can sometimes boot into bootloader but everytime i try to go into recovery my phone reboots again.
windows installed qhsusb driver but nothing else..cant see it.. and i cant do anything else..my phone reboots when booting into recovery and thats it... what can i do? there must be something i can do, i can atleast reaching bootloader every 3. time i am trying too.
I used ViperS 1.6
Firmware 3.32
S-Off JuopunutBear unlocked
Any Idea?
EDIT: now i cant even get into bootloader..screen turns on but stays black guys help me please
Click to expand...
Click to collapse
This is weird that you can get the screen to come on but not get anywhere - on mine it was completely dead - the power button did nothing, pressing power on and vol down did nothing either. What happens when you try to charge it? I couldn't even get a orange charging light. Again this sounds like a faulty component, but I'm no expert on this.
As for trying to fix it yourself I don't think either of you have much chance - if it's still in warranty (mine had 2 years warranty, not sure if that is a UK thing only but considering this phone was only released May 2011 everyone's should still be in warranty) I'd say send it back to HTC. But try the HTC Unbricking project just for peace of mind so you know you can't fix it - I'd say that's your only chance
yeah..its really wierd.at first i could at least go into the bootloader (but not into recovery)...now its just turning on.
i see that the black screen gets a bit brighter (so screen seems on) but it only shows a black screen.
Looks like i need to use my warranty. Hope it isnt a problem that i rooted, but its maybe better that they dont know that :/
Cant afford repair or a new phone. Sucks to be a broke student
I tried HTC Unbricking Project. It couldn't detect my device I had 1-2 crashes per day since last repair, I guess htc did something wrong while replacing the motherboard.
First time I sent them because I had similar problem and now the same happened. Anyways I'm waiting for postman and gonna wait 3-4 weeks again to repair this phone...
Hope they will find damaged component.
Mydy said:
yeah..its really wierd.at first i could at least go into the bootloader (but not into recovery)...now its just turning on.
i see that the black screen gets a bit brighter (so screen seems on) but it only shows a black screen.
Looks like i need to use my warranty. Hope it isnt a problem that i rooted, but its maybe better that they dont know that :/
Cant afford repair or a new phone. Sucks to be a broke student
Click to expand...
Click to collapse
Take out the battery and let the phone sit without its battery for 1 night. When you wake up, try and see if it works.
android1234567 said:
Take out the battery and let the phone sit without its battery for 1 night. When you wake up, try and see if it works.
Click to expand...
Click to collapse
Will try. Thanks for the suggestion
Not enjoying my Nexus 5 too much and going back to Nexus 4.
Nexus 5 is set up the exact same way as Nexus 4 but issues.
Bluetooth randomly disconnects.
Phone randomly reboots itself (every couple of hours or so).
HD Widgets on home screen take up to a minute to display on first logon.
None of these issues on Nexus 4.
:crying:
Anyone else getting similar issues?
<edit>
After spending many hours trying to resolve this I have concluded it is a hardware fault.
Main issues were related.
Also HD widget is fine so long as not on default home screen. If it is then it takes while to fully load.
The bluetooth randomly disconnecting (when used with car system) was the device rebooting itself and not a bluetooth issue.
A couple of new issues appeared:
1. Rebooted when I was logged in even after all active apps had been uninstalled (previously it had only rebooted when screen was sleeping).
2. A couple of times now it as shut down completely and refused to start again.
Booting to recovery worked and then booted normally afterwards.
I have factory reset it and still doing the same thing (random reboots mostly when screen is sleeping).
I have found others having the same issues (including one in this forum)
Returning to Google to replace.
</edit>
<edit 2>
Replacement Phone Delivered in less than 30 hours. Thank you Google and Parcel Force.
All apps restored though Titanium Backup and all tested and working well.
Now my Nexus 5 is working properly I am loving it. Fantastic Phone.
</edit 2>
nope, my device is pretty much perfect
HD Widgets not loading quickly is the developer's fault, but the phone's...and if you are getting random reboots, something you've installed is mucking up the system
wait for apps to be 4.4 optimised before complaining about the phone
Sent from my Nexus 5 using xda app-developers app
Flakie said:
Not enjoying my Nexus 5 too much and going back to Nexus 4.
Nexus 5 is set up the exact same way as Nexus 4 but issues.
Bluetooth randomly disconnects.
Phone randomly reboots itself (every couple of hours or so).
HD Widgets on home screen take up to a minute to display on first logon.
None of these issues on Nexus 4.
:crying:
Anyone else getting similar issues?
Click to expand...
Click to collapse
Just shut down altogether.
Only been booted 10 minutes.
Going to remove HD widgets from home screen to test.
n7of9 said:
nope, my device is pretty much perfect
HD Widgets not loading quickly is the developer's fault, but the phone's...and if you are getting random reboots, something you've installed is mucking up the system
wait for apps to be 4.4 optimised before complaining about the phone
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
What???
This is forum and I am writing down my experiences.
I can put down what I want.
And you know it is not the phones fault how? Maybe I have a faulty one?
Now I love nexus and android but fanboy crap like that really annoys me.
When in doubt....factory reset(or clean flash if this is a custom ROM). There are tons of apps on the Play Store that would seem to do no harm but could cause all of these issues.
I dont think that was fanboy crap....seemed like spot on advice....
Flakie said:
What???
This is forum and I am writing down my experiences.
I can put down what I want.
And you know it is not the phones fault how? Maybe I have a faulty one?
Now I love nexus and android but fanboy crap like that really annoys me.
Click to expand...
Click to collapse
Fanboy crap or not, the point is valid. If you're having random reboots it is caused by software 99% of the time. Go through the list of apps you've installed and begin uninstalling them one at a time, waiting to see if you're getting reboots in between. Good luck.
Go back to stock with no apps for a day and see if the problem continues. If it does then maybe it's the phone. If not, it was an app. New software always has issues either in itself or working with other apps. Why do people expect it to be perfect?
comminus said:
Fanboy crap or not, the point is valid. If you're having random reboots it is caused by software 99% of the time. Go through the list of apps you've installed and begin uninstalling them one at a time, waiting to see if you're getting reboots in between. Good luck.
Click to expand...
Click to collapse
Yes, thanks, I am aware of how to debug a system be it a PC or a phone.
Blanket statements are no help at all.
I asked if anyone else had similar issues.
Maybe they do and they suspect an app.
I suspected HD widgets but it shut down completely with them disabled.
As sure as you are it is software it could just as likely be hardware.
Seems most likely to do it when it goes to sleep or screen is off.
Flakie said:
Yes, thanks, I am aware of how to debug a system be it a PC or a phone.
Blanket statements are no help at all.
I asked if anyone else had similar issues.
Maybe they do and they suspect an app.
I suspected HD widgets but it shut down completely with them disabled.
As sure as you are it is software it could just as likely be hardware.
Seems most likely to do it when it goes to sleep or screen is off.
Click to expand...
Click to collapse
No need to toss attitude around. If you're aware how to debug, then get it done and tell us what the issue was - you'll probably save someone else who finds this thread from going through the same process.
brianfields33 said:
Go back to stock with no apps for a day and see if the problem continues. If it does then maybe it's the phone. If not, it was an app. New software always has issues either in itself or working with other apps. Why do people expect it to be perfect?
Click to expand...
Click to collapse
Who said I expect t to be perfect.
Jeesh.
Yes I am planning to do that which is why I have gone back to my Nexus 4.
I am trying to get a useful thread going for others who may have issues similar.
If anyone has any comments that may be useful they will be welcomed, but please no pointless posts or fanboy trash.
comminus said:
No need to toss attitude around. If you're aware how to debug, then get it done and tell us what the issue was - you'll probably save someone else who finds this thread from going through the same process.
Click to expand...
Click to collapse
I AM!
No attitude being tossed around by me.
Just some of the posters here who have nothing better to do so are posting rubbish.
I posted a thread to help with the process.
People making blanket statement that it must be an app. IT is NOT the phone is crap.
It helps no-one and makes them look stupid and wastes time.
Flakie said:
I AM!
No attitude being tossed around by me.
Just some of the posters here who have nothing better to do so are posting rubbish.
I posted a thread to help with the process.
People making blanket statement that it must be an app. IT is NOT the phone is crap.
It helps no-one and makes them look stupid and wastes time.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am using HD Widgets (with clock and weather and a second widget with switches) and had not a single unwanted reboot or other issues with my phone and I am playing around since monday morning.
Helpful or not - you decide...
Flakie said:
Just shut down altogether.
Only been booted 10 minutes.
Going to remove HD widgets from home screen to test.
Click to expand...
Click to collapse
Seem to be when the screen is off that it reboots.
I have display set to sleep after 10 minutes of activity.
I have set security et to automatically lock after 5 minutes of sleep.
I have it set so the power button does *not* instantly lock.
If I click power button to shut off screen it auto reboots within 3 minutes of doing so.
So it does not appear that it is the sleep process that is causing the reboot.
Going to time this.
DЯΦ[email protected]П said:
I am using HD Widgets (with clock and weather and a second widget with switches) and had not a single unwanted reboot or other issues with my phone and I am playing around since monday morning.
Helpful or not - you decide...
Click to expand...
Click to collapse
Very helpful. Thanks.
Exactly as I was using it.
As an aside, do you have them on the home screen.
If so have you noticed any delay in them appearing when logging in (egg timer)?
I have the clock and weather widget on my homescreen (not lockscreen) and after a reboot it takes a little time to initialize as on my Desire HD before (but much faster now). After turning on the screen, it's just there as it should be. Btw: using Nova Launcher, because I like it and bought it.
Flakie said:
Who said I expect t to be perfect.
Jeesh.
Yes I am planning to do that which is why I have gone back to my Nexus 4.
I am trying to get a useful thread going for others who may have issues similar.
If anyone has any comments that may be useful they will be welcomed, but please no pointless posts or fanboy trash.
Click to expand...
Click to collapse
You may not like their suggestion but that doesn't make it invalid. If you REALLY want to get to the bottom of whether this is hardware or software do a factory reset and leave it stock for a few hours. Question answered.
I've only had one issue, hangout force closed within 15 mins of the phone being on. Nothing since.
Sent from my Nexus 5 using xda app-developers app
HughesNet said:
You may not like their suggestion but that doesn't make it invalid. If you REALLY want to get to the bottom of whether this is hardware or software do a factory reset and leave it stock for a few hours. Question answered.
Click to expand...
Click to collapse
It is not that I do not like the suggestion.
I am prepared for the long haul to find the solution and I will find it.
But Jumping to assumptions that is is the software and stating that is is something I installed that is mucking up the system is of no help.
Then to state I should wait until apps are 4.4 optimised before I complain adds further insult.
This si close to fanboy talk and pisses me off.
I am factual and do not assume anything.
If someone has nothing of value to say then keep it zipped. Simple.
Obviously Samsung weren't happy with their efforts to launch this device with a broken email app. They've gone one step further and broken all push notification support in 4.4.
No longer do I receive email notifications, app notifications, or pretty much anything else.
I have to unlock the phone before I'm told that I had an important meeting an hour ago which had a reminder set 30 mind before. Nor will I receive those stupidly funny pictures of cats with bread crusts on their heads on time.
But it's OK, because calls and texts still work just fine. Who needs important emails as long as you have that text telling you to pick up milk the second it comes through.
There must be laws somewhere to protect us against this stuff. Samsung are shocking.
I would suggest doing a factory reset. I have none of these issues. I have multiple email accounts and calendar reminders that never fail to go off unless the battery is dead. Both the first 4.4.2 and the current build (which is much cleaner in general performance btw).
Sent from my SM-N900T using Tapatalk
arcanexvi said:
I would suggest doing a factory reset. I have none of these issues. I have multiple email accounts and calendar reminders that never fail to go off unless the battery is dead. Both the first 4.4.2 and the current build (which is much cleaner in general performance btw).
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I've done 5 factory resets in the last 2 weeks.
Notifications SOMETIMES work for the first 2 days, before they stop altogether.
Doesn't matter if I have a clean start with no apps installed, having all the bloatware disabled, etc. It always breaks.
I've tried just using the normal battery cover as opposed to the Samsung Flip cover, makes no difference at all.
I've also noticed that Cell Standby is top of battery usage regardless of what I do. Tested different batteries, sim cards, forcing 2G/3G instead of LTE, etc, also with no luck. The battery reporting is also way off too. 100% to 50% drains stupidly slow, then after 50% it craters to 0% within hours. Again, doesnt matter which battery I use (all official batteries btw). Wiped everything via recovery, nothing works.
Am I just one of the victims of 4.4.2? Because I'm starting to think the phone itself is broken.
Also worth mentioning that its only a few weeks old, so 4.3 hasnt been tested, and now obviously I can't go back due to the bootloader update.
My note 2 runs beautifully on both 4.3 and 4.4
I would take your reset one step further and flash the current firmware via Odin. The factory flash you have might be corrupt. Not likely but it wouldn't be the first time I've seen it.
Sent from my SM-N900T using Tapatalk
Whatever your situation is it's your situation. I've been on 4.4 since a leak was released in January and haven't had any of the issues you're describing. The Gear is dependent on device notifications for its feed so its forum would be lit up like a Christmas tree if what you're describing were common. I can't imagine it's h/w related because there's no specific component that would touch the things affecting you. From what you said, I'm assuming your device is receiving whatever's supposed to trigger the notification but you're not being alerted when it arrives/occurs. That sounds like an app conflict or problem in settings.
BarryH_GEG said:
Whatever your situation is it's your situation. I've been on 4.4 since a leak was released in January and haven't had any of the issues you're describing. The Gear is dependent on device notifications for its feed so its forum would be lit up like a Christmas tree if what you're describing were common. I can't imagine it's h/w related because there's no specific component that would touch the things affecting you. From what you said, I'm assuming your device is receiving whatever's supposed to trigger the notification but you're not being alerted when it arrives/occurs. That sounds like an app conflict or problem in settings.
Click to expand...
Click to collapse
Strangely enough, notifications work fine when paired with the Galaxy Gear I got free with it. I just rarely use it due to the nature of my workplace.
I probably should have added, the notifications only come through a few seconds after the phone is unlocked. You can visibly see the phone begin to access the network via the icon, and once it downloads, notifications pop.
And worth mentioning that this happens regardless of wifi access point, and on both 2G/3G and on LTE.
arcanexvi said:
I would take your reset one step further and flash the current firmware via Odin. The factory flash you have might be corrupt. Not likely but it wouldn't be the first time I've seen it.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I'll give that a go thanks.
I know you say it's unlikely, but I've tried for hours to find people that have the same issues as me, with no luck. Here's hoping it's just one of those rare cases.
http://forum.xda-developers.com/showthread.php?t=2760935
I posted the firmware a week or so ago. That's the build that was just released.
Sent from my SM-N900T using Tapatalk
Mine doesn't do this. In fact mine is the opposite, it checks my email more often than what I set it to, kind of annoying.
Sent from my SM-N9005 using XDA Free mobile app
arcanexvi said:
http://forum.xda-developers.com/showthread.php?t=2760935
I posted the firmware a week or so ago. That's the build that was just released.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Thanks but I'm running the international version.
Decided to bite the bullet and use the latest NE3/NE4 update from Asia, as a few people have reported it to be fine for the n9005 model it was intended for. I can always flash back later.
Will update in due course if anything helps my situation.
I had the same problem with WhatsApp notification
And I figured out that was happening because I hibernated google play store app
Just a quick message to say that the NE3 build seems to have fixed my cell standby issue, but ofcourse this is more than likely down to the full odin flash.
Hopefully it stays that way. Will test notifications during my work day tomorrow.
Yet another thing I forgot to add. Notifications have always worked properly when there is music playing to an external device. I assume this is down to the fact that the phone is always awake, and not in deep sleep like it normally is.
Android system and Android OS are both firmly back at the top of my battery usage as per the 4.4.2 norm. Strangely though I can't get the screen usage up at all.
weird. I have had 0 problems with NE3. Are you sure that you didn't greenify \ deactivate \appops stuff you shouldn't ?
i would love to have cell standby up on top as opposed to Android OS \ Android system though i did see a big leap in standby battery life comming to NE3 from ND3 and they were still on top.
istrikerx said:
Strangely enough, notifications work fine when paired with the Galaxy Gear I got free with it. I just rarely use it due to the nature of my workplace.
I probably should have added, the notifications only come through a few seconds after the phone is unlocked. You can visibly see the phone begin to access the network via the icon, and once it downloads, notifications pop.
And worth mentioning that this happens regardless of wifi access point, and on both 2G/3G and on LTE.
Click to expand...
Click to collapse
Sounds like background data is off.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my leanKernel 2.5.1 powered stock 4.4.2 (NE6) SM-N900T
fookea said:
weird. I have had 0 problems with NE3. Are you sure that you didn't greenify \ deactivate \appops stuff you shouldn't ?
i would love to have cell standby up on top as opposed to Android OS \ Android system though i did see a big leap in standby battery life comming to NE3 from ND3 and they were still on top.
Click to expand...
Click to collapse
NE3 seems to be significantly better than the ND6 build I was originally on. I can't judge battery life as ND6 was completely broken where tracking battery health, charge, etc was concerned. But I will say that it seems much more accurate.
So far notifications are working flawlessly while I have my flip cover installed. Hopefully it lasts.