Database Develop

[Q] Nexus One restarts frequently

Hi all,
I've had a problem with my Nexus One ever since I got it.
Whether I use a custom ROM or the stock one, the phone restarts itself 4-5 times a day. However, this only happens when I'm in Bahrain.
I've used my phone in Cyprus and in UK without a problem. I am completely stumped :/
If it helps, I'm currently using CM 6.1.0-RC1 on the following networks:
Bahrain: STC / VIVA
Cyprus: CytaVoda
UK: O2
Thanks

Noone have any idea what the problem might be?
Any suggestion is welcome

It happens to me too.and someone suggest to me to decrease my cpu speed(from setcpu). But i never tried it. I updated to CM 6.1 RC2. and the problem dissapear
Sent from my Nexus One using XDA App

Yeah happened to me only once, I was play around with SetCPU and overclocked it way too much. Hasn't happened again since.

Do you have to pull the battery for it to boot after it restarts? That was the case in my situation and it was a hardware issue.
Sent from my Nexus One using XDA App

ive seen and heard of certain cell towers that this will happen with. i had a problem with a certain tower when i was using my g1. i called tmobile and explained the situation then they reset the tower and all was good after. corrupt data being sent from them that your phone reacts to(or something like that.

It has happened to me few times, most likely it's caused by kernel.
some people report improved stability after flashed an over-volted kernel (Wildmonks provides customized over-volted kernel)
so you might want to give the over-volted kernels a try

In my case I had a perfectly working Nexus one but I cracked a screen. I paid $55 to HTC and I got a replacement. Now every replacement I get from HTC reboots on any application which used to make my phone warm. CPU test, Tower games, etc... They all cause phone to reboot within 5 minutes. I think it is overheating...
Waiting for 3rd replacement from HTC...

How many people got the same problem after reclaim a new 2X from LG (reboots problem)

As I see, I guess there are approximately 5% of the total amount of Optimus 2X that got problem about freezing screen and reboot itself.
No one can solve this problem unless go back to LG and claim new one.
But, no one can make sure that the new one will not have the same problem again.
Now I am sending my 2X back to LG and wait them to send a new 2X back to me.
I am so worried if I get the new mobile with problem again.
So, I would like to know anybody who already claim the mobile from LG and still got the problem. I would like to know the statistics of the user.

If your guess is right, you will get a good unit with a 95% probability.
Sounds good, no?

Confirmed here in Netherlands people indeed got back a new phone with same issues.....

I got the g2x...and can confirm that my phone is not defective...works great..
Sent from my LG-P999 using XDA App

I work for a phone compagny and so far i think 5% can be true. But that was before the updates. After the updates nobody (at least with me) came back with complains
Sent from my Optimus 2X using XDA Premium App

i'm still using stock rom with v10b..never face the reboot issues
p/s this phone is really great!!

thank all guys, if I got a good phone at the beginning, I would not feel like this.
I'm in Thailand and I bought this phone on May 7, 2011 for 20,900 baht (~680 USD)
When Samsung Galaxy S2 is released, the price down to 15,900 baht (~520 USD) within a month.
The point is I got a problem phone. That means I can't use phone well along 1 month.
Feeling like I throw away 160 USD to LG for free.

for almost a month i didn't have problems but in the recent time it started to behave strange... today i had my second reboot...
i'm not getting some sms messages at all... however the sender got's message that it was sent... sometimes they call me, but my phone doesn't make any sign of it, but at the other end it is ringing...
kinda strange behaviour, not I am the only one with these calling and sms bugs...
the charging is also crap, somtimes i just charge it, and the charging indicator is tuck at some value, and the phone is really hot... then i restart it, and the value just jumps higher, and a temperature of the phone gets ok...
the charging problem seems a hardware issue... i'm thinking on sending it back... but I don't know what else to buy... this one has all the features i need, sgs2 and sensation are too expensive for me... so i'm hoping that lg will do something in the summer... otherwise i'm sending it back :S

My phone started rebooting recently. Yesterday it rebooted twice and tonight it shut down causing me to miss the alarm.
Before this it went 2 months without any reboots.
Wtf?

Installed anything recently?
Flash 10.3 update maybe?

I just heard an information from Thai webboard.
He said that the warranty of 2X can let the user claim it for only one time.
That means you cannot claim it again if the new one got problem again.
Suck LG

I have no issues either so I can't imagine having these reboots is like.

They said the same thing for the VIP service here in Netherlands. Max 3 swaps, But some people already did swap #4
Sent from my LG-P990 using XDA App

The price of this model is around 480-550 USD in Ebay... I should try to sell it for a while ago..

xmoo said:
They said the same thing for the VIP service here in Netherlands. Max 3 swaps, But some people already did swap #4
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
Max 3 swaps.. So then you're just stuck with a faulty product forever?
I think it's time for Kassa.

Try to format your external SD. Upgrade to Fr18Rom. If the problem cannot fix. Return the phone to LG. It‘s hardware issue.
Sent from my LG-P990 using XDA App

arbrad said:
Try to format your external SD. Upgrade to Fr18Rom. If the problem cannot fix. Return the phone to LG. It‘s hardware issue.
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
if the issue can be fixed that easy..... most of people in this webboard would change it long time ago....
take a look here
http://forum.xda-developers.com/showthread.php?t=1041546
I am sure that
- ROM cannot solve this problem
- It MIGHT be Hardware problem, but no clue can confirm this (most of people still believe it's software problem)

I think some buggy apps and buggy kernel let your phone reboot or sleep dead.

[Q] Help! Random Reboots on New Note

Hi,
Got a Note in the UK just last week, brand new, and within two days I flashed it to the German stock ICS update. I can't say that I noticed issues in the first few days, but that could be because I didn't get a lot of time with it.
Since then, however, now that it is all set up and configured, I'm noticing random spontaneous reboots during sleep on the device, anything between every 2 to 6 hours, no warning, just the phone suddenly flashing into life with the model splash screen, followed by startup animation.
Reading around I've followed all kinds of anecdotal cures... I've removed Apex Launcher and Widget Locker, and returned to TWLauncher and stock dialer. I've moved all my apps from external SD to phone internal and deleted App2SDpro. I've cancelled all automatic syncs. I'm not rooted and don't have any iffy software on it.
Does anyone please have any ideas on this?

No ideas?

Since the update mine does exactly the same thing. Sometimes it reboots after every hour or so but then sometimes it happens every 5 hours. Its completely random and has started happening since the ICS update.

Hmmm. I'm wondering if I should do another full install, or if this is a bug that will be absent in the official UK version of the new OS/firmware update.
I wonder if it is somehow specific to UK users?
It annoys the pants off me, because it will happen, then I'll delete a load of software and restart manually, then it will behave sometimes (like today) for 11-12 hours. And then it does it again. And again. I've had 12 hours between reboots from yesterday to today, and then today I've had three in four hours, including one after just an 11 minute interval, while the phone was on standby.
Is there anything that can be a 'variable' on an 'international' Note which might be an incompatibility in one territory but not another?
Sim? Network? Wifi?

I'm in UK, and was on German Ics official until today . Started experiencing fcs on random apps, from what I've read elsewhere that can be the start of a superbrick. I would highly recommend flashing back to stable GB immediately.
Sent from my GT-N7000 using xda premium

Well... We may be seeing an improvement.
When I installed German ICS on my UK Note I did it as an upgrade. So yesterday afternoon I put the note to sleep and then rebooted into hard reset. I got myself a nice clean system and after lots of restoring files and reinstalling apps, I now have a Note that spent all night charging and hasn't restarted itself since 6am. It still could... But hasn't yet.
Something else odd I noticed...
When I first installed ICS (without tweaks, messing, only on stock ROM) and came to install SwiftKeyX for Phone it refused, allowing me only to install the tablet version... This depressed me a little because the skin I use is nicer on the phone version than tablet. Oddly, this time, after the reinstall, the note would only install the phone version of SwiftKeyX, and not the tablet.
Not sure what changed and why, but I can only imagine that something was broke and is now fixed...
Time will tell. I think battery might be a little better now too. And I use JuiceDefender.
If I get a full 24 hours without reboots I might dare to try App2SD again and move some apps to card storage.
So far so good.

Arse. 19 hours later and the reformed Note spoiled itself with a random reboot during sleep.
Back to the drawing board.
So is this a hardware or software fault. Its so new that I could do with knowing... I can insist it be swapped. But am I going to get the same again? Has anyone been able to trap this erroneous reboot in logs or anything? Do we know what it is?
Are there just a few of us, or many? Former would suggest hardware, latter could be software.

I'm having this issue too. We need help here
Sent from my GT-N7000 using Tapatalk 2

Mine hasn't rebooted all night while on charge. I would also like to know if there are any logs that can pin point the issue
Sent from my GT-N7000 using xda premium

I would suggest turn it off (be sure, it is turned off)
Remove the battery
Leave it this way for an hour
Insert the battery
Perhaps it would be good idea to go back to your area GB also (following drKetan guides).
I had the same anectodal thing happening with my new note just when i purchased it. After 1..2 days it went grazy. Then it blacked totally out. But just by chance it woke up after resting without battery for a day.
Personally, I think, the cache should be cleaned - BUT i definitely will not recommend a wipe cache in LPY (though it worked with me - but then again, it COULD NOT work with you - and the loss... what a loss it would be). (worked with me - that means it did not brick my phone when i upgraded few days ago and that did not have anything to do with my troubles when I purchased the note (few months ago)).

I'm discouraged that there are either so few people suffering this that we're simply 'on our own' with it, or so many people who have it but have learned to accept it.
It seems preposterous to not have attention to such a big fault.
And I realised that I've seen this before, and have the sneaky feeling that it is a dirty little secret of Android....
I bought an ASUS Transformer last June. It had this issue from day one on Honeycomb. Random reboots at unpredictable times, at least two per day. Over the last 9 months it went back to ASUS three times and each time they 'fixed' something totally unrelated to the problem before eventually telling me that they had no replacement units to give me and were authorising a full buy back - a refund.
I had anecdotal indications that it only occurred when I had an SD card installed. That was my growing suspicion, but I now no longer have a unit to test it.
Other Galaxy range users have been reporting random or looped reboots, and have pinned blame on using an sd card, especially in conjunction with App2SD.
I have an HTC Flyer with an SD card installed, running App2SD, and have no random reboot problems. Its as solid as a rock on stock Honeycomb.
Similarly, though, some users have reported that their Galaxy phone model has random reboots relating to having a sim card installed...
You see where this is going. Its getting to the place where we're accepting that the only way our expensive device works is if we disable key functionality and surrender our expectations of its advertised features doing the job they were intended to.
It is scandalous that this device should malfunction as a result of using the advertised features, and that no fix would be found nor explanation offered.
I now have an SD in the unit, but have not moved apps with App2SD. I have established that the reboots occur with all three of my SD cards of varying sizes, soit is not caused by a corrupt or faulty SD... If it is caused by an SD at all, it is 'all' SD's. Since so many users have the Note with SD's installed, and they run perfectly, I can't believe there is an issue with SD cards, although I did wonder if the manufacturers are now phasing out SD slots in their devices because 'cloud computing' is all the rage, or rather because this volatility caused by SD in the now unfixable evolving Android code means that they are minimising their embarrassment by simply dispensing with the faulty variable.
I have also begun setting static IP's for all my stored wlan's in case this is a DHCP issue caused during momentary wakes from sleep for polling or sync. If only we had an app that could store, like a seismograph, a persistent record of device events which trigger the reboot and then capture the reboot events also. Closest I've found uses ram to store the events log and then blanks the log on reboot starting from the reboot instead of maintaining the record prior to the reboot.
Getting close to wits end with this, and now deeply regretting my purchase.
Nothing like this on my Xperia Arc S.
Even an iPhone is better than this!

opsakas said:
I would suggest turn it off (be sure, it is turned off)
Remove the battery
Leave it this way for an hour
Insert the battery
Perhaps it would be good idea to go back to your area GB also (following drKetan guides).
I had the same anectodal thing happening with my new note just when i purchased it. After 1..2 days it went grazy. Then it blacked totally out. But just by chance it woke up after resting without battery for a day.
Personally, I think, the cache should be cleaned - BUT i definitely will not recommend a wipe cache in LPY (though it worked with me - but then again, it COULD NOT work with you - and the loss... what a loss it would be). (worked with me - that means it did not brick my phone when i upgraded few days ago and that did not have anything to do with my troubles when I purchased the note (few months ago)).
Click to expand...
Click to collapse
Can you direct me to that guide?
And is it likely that it is the DE ICS release that just doesn't like UK devices? Why would that be so?

Looks like i'm going to get stuck with this problem until I move on to a next phone. What a waste
Sent from my GT-N7000 using Tapatalk 2

Maybe you should have waited for a stable release built using the UK or wwe equivalent rom? You didn't even give the stock more than a couple of days, what was the rush?!
Sent from my GT-N7000 using xda premium

Maybe, yes.
Naivete, perhaps.
I'll tell you exactly why.
I had an Xperia Arc S on ICS which I loved. I was tempted by the Note. I bought one expecting a Samsung flavored ICS experience, and got tossed back to GB. I basically had 7 days to return the Note or learn to like it, and during that period DE f/w was released and I had to know...
Note was rebooted using static ip's and is nowraring to go...
So far so good @ 18 hours

BashyUK said:
Maybe you should have waited for a stable release built using the UK or wwe equivalent rom? You didn't even give the stock more than a couple of days, what was the rush?!
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Did you even read my other posts? Problem started when i was still in gb.
Sent from my GT-N7000 using Tapatalk 2

Still going... No reboots. And excellent battery performance to boot.

l0rd_almighty said:
Did you even read my other posts? Problem started when i was still in gb.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
But if that was when your phone was still new why didn't you just return it for a replacement rather than root and flash a phone that wasn't stable in the first place? For all you know it may be a hardware issue and likely so as I've not heard any apart from you and the op mention it.
Anyway, your phone, your call what you do with it but it makes no sense to me to blame the manufacturer and model when you've not even followed basic steps to deal with an issue.
Sent from my GT-N7000 using xda premium

The first note I had in December 2011 rebooted at random. It was a hardware issue. It only started after owning it for 3 weeks, stock GB. Not roiled or modified in anyway. I had it replaced.
G
Sent from my GT-N7000 using Tapatalk 2

BashyUK said:
But if that was when your phone was still new why didn't you just return it for a replacement rather than root and flash a phone that wasn't stable in the first place? For all you know it may be a hardware issue and likely so as I've not heard any apart from you and the op mention it.
Anyway, your phone, your call what you do with it but it makes no sense to me to blame the manufacturer and model when you've not even followed basic steps to deal with an issue.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Basic steps i didn't follow? Enlighten me... I never mentioned that this happened when my phone was new. I said this started when i was still in GB. Notice the difference? If you can't help us figure out what's causing this just go troll on somebody else's thread.
Sent from my GT-N7000 using Tapatalk 2

[Q] Sprint HTC One - Won't Boot - Won't Charge

The story is I was having a lot of general problems with my Sprint HTC One. I was using it with CyanogenMod 10.1 and I noticed it was getting VERY warm. I then noticed that the battery was at 21%, I had hardly used it all day. It would normally have been around 94% percent. So I was shocked. Then I noticed that is would make weird clicking and "eek" noises when I would browse the Operating system. It would make an especially annoying noise when I would turn on the LED Camera light. I also noticed that the battery would drop about 1 percent ever 30 seconds.
I immediately shut it off and plugged it into my charger (AC). I opened up ClockworkMod and wiped my cache and dalvik cache and then did a factory reset from ClockworkMod. The problems still occured. I then tried flashing an Earlier version of CyanogenMod 10.1. The problem still occured. So I let my battery charge up to 50% (it took a especially long to charge, it would actually lose a charge while charging at times) and then used RUU tool to flash it to Complete Stock. That got rid of the weird noises caused during the operating system use. But the battery continued to run hot and take especially long to charge (somtimes the battery level actually was dropping). I then installed an app to control the frequency of the CPU. It was set to always run at 1.7GHz. So I fixed that and made the minimum Frequency the lowest option and the Max Frequency 1.7GHz. That solved the charging problem.
I left it to charge over night and by the morning it was at 100%, so I unplugged it and turned it off. I thought I had solved everything. I left the phone alone for about 4 hours and when I checked on it, it would not boot whatsoever. I could not not even get into the Bootloader! Then I plugged it back into the charger to find out that the Orange charging indicator LED would NOT light up! So for now, it is just sitting in the charger without the charging indicator light lit up.
I would also like to mention that I am not the original owner. I bought this phone used. It does not have the normal Sticker on the back of the phone to indicate the Serial Number etc. And since I am not the original owner, I do not believe I qualify for a replacement warranty. Any help at all would be greatly appreciated. Thank you for your time.

this has been happening to alot of people
which of the nightlies did you flash?

flex360 said:
this has been happening to alot of people
which of the nightlies did you flash?
Click to expand...
Click to collapse
It was either the cm-10.1-20130731-NIGHTLY-m7spr (2013-07-31) build or the cm-10.1-20130730-NIGHTLY-m7spr (2013-07-30) build

Might need to go to sprint for a replacement
Sent from my HTCONE using Tapatalk 4 Beta

krazyflipj said:
Might need to go to sprint for a replacement
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
Am I able to get a replacement even though I'm not the original owner?

ammuica said:
Am I able to get a replacement even though I'm not the original owner?
Click to expand...
Click to collapse
If you are under service they should. Phone is still under manufacturer warranty. If you don't have insurance, worst case scenario you pay $50 for a refurb/new phone. Of course that's if they can't repair
Sent from my HTCONE using Tapatalk 4 Beta

krazyflipj said:
If you are under service they should. Phone is still under manufacturer warranty. If you don't have insurance, worst case scenario you pay $50 for a refurb/new phone. Of course that's if they can't repair
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
It is not under service. I Bought it with the plan of not using it on a contract because I cannot afford a data plan, but I would still like to use an android smartphone.

Yeah just got and get a replacement for 50$ I was not the orginal owner and they got the serial number off they're system I got a refurbished one I think but it was in like brand new condition but now it seems the brick problem is still around
Sent from my HTCONE using Tapatalk 4 Beta

Alex1123 said:
Yeah just got and get a replacement for 50$ I was not the orginal owner and they got the serial number off they're system I got a refurbished one I think but it was in like brand new condition but now it seems the brick problem is still around
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
But will they still replace it if I'm not using it with a plan? I bought it from someone else and I never re-activated it.

I've called sprint and since I don't have the phone under my account and since it is not activated, they will not repair it. So a replacement/repair is out of the question. So is there anyway I can fix this myself? I'm familiar with flashing and all that stuff, so any of that stuff is just fine.

There is no way you can repair this yourself.
And eek! This problem's back? What? You were using the latest nightly too?
And since you have no warranty (pretty sure its non transferable), you should look up JTAG services. $60. It may not be as clean as you'd like, though. Besides, HTC repair service wouldn't fix your device for free because, even though the device is bricked, they can see your tampered boot loader. They charged me $200. I probably won't root again.
This has happened to at least a dozen people, but all if them were before July 3rd. This is kind of disturbing.

sauprankul said:
There is no way you can repair this yourself.
And eek! This problem's back? What? You were using the latest nightly too?
And since you have no warranty (pretty sure its non transferable), you should look up JTAG services. $60. It may not be as clean as you'd like, though. Besides, HTC repair service wouldn't fix your device for free because, even though the device is bricked, they can see your tampered boot loader. They charged me $200. I probably won't root again.
This has happened to at least a dozen people, but all if them were before July 3rd. This is kind of disturbing.
Click to expand...
Click to collapse
Hey, it's always worth a try. I always used the latest nightly. I updated whenever they pushed a new update. I had it running CyanogenMod 10.1 Nightly for over a month without a single problem. I've been using it on my Galaxy Nexus for over a year. This is the first time it's ever given me a problem.
I'll look into the JTAG, but if anyone else has any ideas I'm up to try anything. The bright light while holding Volume Down + Power didn't work for me.

OP.... wow. Just wow.
So you have the device's processor spinning at 1.7 GHz constantly, and you are wondering why it is warm? You are also running a custom OS with a myriad of bugs and issues, and you are wondering why now your device isn't working properly.
Unbelievable. You shouldn't be playing around with its powerful hardware if you have absolutely no clue what you are doing, don't you think?
Sent from my SM-N900T

Admiral Sir Manley Power said:
OP.... wow. Just wow.
So you have the device's processor spinning at 1.7 GHz constantly, and you are wondering why it is warm? You are also running a custom OS with a myriad of bugs and issues, and you are wondering why now your device isn't working properly.
Unbelievable. You shouldn't be playing around with its powerful hardware if you have absolutely no clue what you are doing, don't you think?
Sent from my SM-N900T
Click to expand...
Click to collapse
I did know what I was doing. I was running a stock build flashed by RUU. So I assumed that it would have a decent frequency management (that should be a safe assumption). I know what I'm doing when it comes to android's. I'm not stupid enough to have the CPU running at the full 1.7 GHz. Immediately after it started getting warm again that was the first thing I checked. Normally I underclock my devices. I usually have my Galaxy Nexus run at 700 MHz. I've also been using Nightly builds for my Nexus for over a year and I've found it to be stable enough to decide to flash it on my HTC One. And until 2 nights ago, It was perfectly stable.
I've done no fault on my own. I personally blaim HTC for pumping out a ROM that let it run at 1.7GHz 24/7, even unrooted.

Also to include, while I was running CM 10.1 I had my CPU set to a minimum of ~300MHz (forget exact frequency) and a maximum of 1.7GHz. I'm not stupid enough to set it to run at 1.7GHz 24/7 for any reason whatsoever. I was shocked when I saw that it had been running at 1.7GHz 24/7 (had only been running for an hour in sleep mode at that point before I fixed it).

Admiral Sir Manley Power said:
OP.... wow. Just wow.
So you have the device's processor spinning at 1.7 GHz constantly, and you are wondering why it is warm? You are also running a custom OS with a myriad of bugs and issues, and you are wondering why now your device isn't working properly.
Unbelievable. You shouldn't be playing around with its powerful hardware if you have absolutely no clue what you are doing, don't you think?
Sent from my SM-N900T
Click to expand...
Click to collapse
?
10.1 is very close to stable...
Except, you know, the bricking issue.
Where does it say the device was maxed out on purpose? Stock CM is supposed be pretty good at CPU management.
So now we know what is causing the bricks. The CPU is literally self destructing. We should have deck look into it.

I'm considering selling it to technollo.com . With a promo code, they will pay $70. I only payed $230, so I might as well just cut my losses.

ammuica said:
I'm considering selling it to technollo.com . With a promo code, they will pay $70. I only payed $230, so I might as well just cut my losses.
Click to expand...
Click to collapse
Really sucks man.
Again, just goes to show. If you can't afford to lose/fix your device, then you shouldn't be rooting it and stuff. HTC makes no guarantees that the phone will be able to run AOSP ROMs. The devs just do their best. Phones are getting more and more complicated, and it gonna get harder and harder to make stable ROMs for them.
Looks like this is your only option... maybe you can go and get yourslef an N5 when it comes out as a replacement?

sauprankul said:
Really sucks man.
Again, just goes to show. If you can't afford to lose/fix your device, then you shouldn't be rooting it and stuff. HTC makes no guarantees that the phone will be able to run AOSP ROMs. The devs just do their best. Phones are getting more and more complicated, and it gonna get harder and harder to make stable ROMs for them.
Looks like this is your only option... maybe you can go and get yourslef an N5 when it comes out as a replacement?
Click to expand...
Click to collapse
Well I think it's worth the risk. Usually I can fix nearly any software issue possible. However, this is a hardware issue. I love modifying my devices and I won't stop anytime soon. My Personal computer currently has full liquid loop (GPU + CPU) that I setup and maintain that I am proud of. Sometimes things just go wrong. That's no reason to give up. For now I'll just continue to use my Galaxy Nexus until I find it necessary to upgrade.
However if anyone would be interested in purchasing this HTC One from me, just message me and we could try to work something out.

ammuica said:
Well I think it's worth the risk. Usually I can fix nearly any software issue possible. However, this is a hardware issue. I love modifying my devices and I won't stop anytime soon. My Personal computer currently has full liquid loop (GPU + CPU) that I setup and maintain that I am proud of. Sometimes things just go wrong. That's no reason to give up. For now I'll just continue to use my Galaxy Nexus until I find it necessary to upgrade.
However if anyone would be interested in purchasing this HTC One from me, just message me and we could try to work something out.
Click to expand...
Click to collapse
I never asked you to stop rooting. It was just a PSA saying one should only root if one can afford to lose or fix one's device.
English is stupid.

What can I do to prevent half screen problem?

On most roms I am to get the half screen problem, and I was wondering if there is something I can do to prevent it.

According to T-Mobile it is a know problem. Got my replacement on order. I had the problem happen before I even rooted the phone. Seems to have gotten worse over time for me though and that's why I called to have it replaced. If your having the problem I totally recommend the same to you. I will say after trying chroma I think it has gotten more frequent even after loading up my light rom backup. I can't blame it on anything other then bad hardware though cause like I said it happened before I rooted a week into having the phone.

Hardware issue, replace it
Sent from my Nexus 6 using XDA Free mobile app

Yeah I had the issue before I rooted as well. Lol I had called tmobile for the replacement 5 min before reading this and they are sending me a replacement device. Thanks for responding though!

When to you guys called it in, do you get the normal "factory reset" troubleshooting, or do they know that this issue is random and just send a replacement? I get the issue with certain kernels, and not with others and am wondering if I should call it in.
Sent from my Nexus 6 using XDA Free mobile app