Database Develop

[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

So what's the deal with the camera red tint?

I have 3 HTC Ones (all sprint) in my possession at the moment. Mine has the red tint problem. The other 2 (wife's + wife's insurance replacement.. she just broke the screen ($first time ever using phone insurance, thank god we had it$)) both seem to be fine - no red issue.
All 3 phones started with 1.31.651.2, both mine and the broken screen phone have been updated to 3.04.651.2 The new replacement is still 1.31.651.2. We've had these phones for just about 2 weeks (embarrassing, we weren't even a week into enjoying these before she dropped it..). Anywho..
I did some camera experimenting tonight to find out a few things, here are the results:
Camera issue exists with both 1.31 and 3.04. I saw some posts about people thinking the update had something to do with it, but I don't think so. The phone w/ red had it both pre and post 3.04. The normal phone has been normal both pre and post 3.04. The 3rd phone is still on 1.31.. I've left it alone as a sort-of control phone.
Heat doesn't matter (maybe if you melted things tho.. ). My phone would exhibit red regardless of waking 'cold' fresh from sleep or after heavy usage where it would really start to warm the hand. Both the normal phone and the control phone would be fine following the same pattern.
ISO 100 doesn't fix things, it just lowers the ISO enough that the camera software? stops trying to add gain/noise to the signal. Taking [roughly] the same picture between all 3 cameras at iso 100, the red one is still noticeably red tinged when compared to the other 2 phones, they're all just much darker so it's less noticeable esp if you didn't have anything to compare to.
Full wiping/resetting (incl media/data) doesn't make a difference.
Unrelated to the camera and this is kind of a nitpick, updating to 3.04 really slowed the UI down. It's still extremely fast, but it's kine of like things run at 30fps now where as 1.31 everything was 60fps. The best repeatable example is scrolling when unlocking the phone. 1.31 is silky 60fps smooth, 3.04 is crossfire/sli microstuttery. Reset/wipe doesn't make a difference.
Attaching a few boring pics.. excuse the boringness The 2 normal phone pics are pretty much the same so I've only uploaded 1 to compare w/ the red phone. Have a bunch more, but these pretty much typify what is going on.
So is this a hardware defect? What's the best way to deal with it? I don't mind shipping it to HTC and go w/o for a bit to get it addressed, but I do want to make sure it's dealt with. I'd also be pretty steamed to get either a refurb or used phone in return, because we bought these new less than 2 weeks ago (Costco).
Even though we are technically still in the 14day return window, I'm pretty sure we can't return the phones and try to switch to another Sprint offering because of insurance being used already (sigh), but that's fine - we do like the phones and want to keep them.
How do I get this fixed?
Thanks!
*edit* Contacting HTC via http://www.htc.com/us/contact/email/ just gave me a 403 Forbidden error, so this is already starting off in a bad light (pun?).
*edit2* Resubmit and got through, I'll keep this thread updated as I find out more. (I haven't been able to find any concrete info regarding all of this, so maybe this will come in handy for someone in a similar situation at some point)

pbassjunk said:
I have 3 HTC Ones (all sprint) in my possession at the moment. Mine has the red tint problem. The other 2 (wife's + wife's insurance replacement.. she just broke the screen ($first time ever using phone insurance, thank god we had it$)) both seem to be fine - no red issue.
All 3 phones started with 1.31.651.2, both mine and the broken screen phone have been updated to 3.04.651.2 The new replacement is still 1.31.651.2. We've had these phones for just about 2 weeks (embarrassing, we weren't even a week into enjoying these before she dropped it..). Anywho..
I did some camera experimenting tonight to find out a few things, here are the results:
Camera issue exists with both 1.31 and 3.04. I saw some posts about people thinking the update had something to do with it, but I don't think so. The phone w/ red had it both pre and post 3.04. The normal phone has been normal both pre and post 3.04. The 3rd phone is still on 1.31.. I've left it alone as a sort-of control phone.
Heat doesn't matter (maybe if you melted things tho.. ). My phone would exhibit red regardless of waking 'cold' fresh from sleep or after heavy usage where it would really start to warm the hand. Both the normal phone and the control phone would be fine following the same pattern.
ISO 100 doesn't fix things, it just lowers the ISO enough that the camera software? stops trying to add gain/noise to the signal. Taking [roughly] the same picture between all 3 cameras at iso 100, the red one is still noticeably red tinged when compared to the other 2 phones, they're all just much darker so it's less noticeable esp if you didn't have anything to compare to.
Full wiping/resetting (incl media/data) doesn't make a difference.
Unrelated to the camera and this is kind of a nitpick, updating to 3.04 really slowed the UI down. It's still extremely fast, but it's kine of like things run at 30fps now where as 1.31 everything was 60fps. The best repeatable example is scrolling when unlocking the phone. 1.31 is silky 60fps smooth, 3.04 is crossfire/sli microstuttery. Reset/wipe doesn't make a difference.
Attaching a few boring pics.. excuse the boringness The 2 normal phone pics are pretty much the same so I've only uploaded 1 to compare w/ the red phone. Have a bunch more, but these pretty much typify what is going on.
So is this a hardware defect? What's the best way to deal with it? I don't mind shipping it to HTC and go w/o for a bit to get it addressed, but I do want to make sure it's dealt with. I'd also be pretty steamed to get either a refurb or used phone in return, because we bought these new less than 2 weeks ago (Costco).
Even though we are technically still in the 14day return window, I'm pretty sure we can't return the phones and try to switch to another Sprint offering because of insurance being used already (sigh), but that's fine - we do like the phones and want to keep them.
How do I get this fixed?
Thanks!
*edit* Contacting HTC via http://www.htc.com/us/contact/email/ just gave me a 403 Forbidden error, so this is already starting off in a bad light (pun?).
*edit2* Resubmit and got through, I'll keep this thread updated as I find out more. (I haven't been able to find any concrete info regarding all of this, so maybe this will come in handy for someone in a similar situation at some point)
Click to expand...
Click to collapse
I don't have that problem
Sent from my HTCONE using Tapatalk

@pbassjunk check this thread out.
http://forum.xda-developers.com/showthread.php?t=2317507

Yeah I have this problem as well. Had it since I got the phone (before 4.3 update). I just try to not take pictures in low light even though that's what the camera is for. Hopefully it's a software problem and they fix it but I'm pretty sure it's a hardware problem
Sent from my HTC One using XDA Premium

4.3 update fixed that. If you still have it after 4.3, your device is defective.
Sent from my HTCONE using Tapatalk

So anyone else get Lollipop OTA?

I like my root and don't want to be the Guinea pig, but see the OTA is here. Have to do some research so I don't brick my G2...again
BTW I just added a screenshot of my system info.

al2fast said:
I like my root and don't want to be the Guinea pig, but see the OTA is here. Have to do some research so I don't brick my G2...again
BTW I just added a screenshot of my system info.
Click to expand...
Click to collapse
I'm downloading the update right now! I unrooted my phone yesterday but was unaware I had to revert to stock firmware to update, so I had to do that first . For some reason it looks a little different from my old software's gui but I'm happy I'm getting the update!

Let us know how it goes! I'm quite happy with my g2, except for the GPS that needs a clear sky view to be accurate. Don't want to break a good thing!

al2fast said:
Let us know how it goes! I'm quite happy with my g2, except for the GPS that needs a clear sky view to be accurate. Don't want to break a good thing!
Click to expand...
Click to collapse
Well after performing all the previous updates for my g2, I finally installed 5.0, and now my g2 won't boot up so I have to install the stock firmware again LOL

Yeah so I went through the whole updating thing a second time and the same thing happened. I learned that my phone tried updating to 5.0 one time and failed. The second time I tried to install it, after it finishes updating, after reboot it should go into optimizing apps and such before loading the screen, but it's just stuck at the lg screen.

sk8ergun234 said:
Well after performing all the previous updates for my g2, I finally installed 5.0, and now my g2 won't boot up so I have to install the stock firmware again LOL
Click to expand...
Click to collapse
And LG reps admitted on the phone with me and a Verizon rep that the GPS would be fixed with the Lollipop update. Ha. It did not work. Big surprise. I have yet to deal with a company who cares less about their customers (and I drive a *gasp* Volkswagen!)!
Sent from my VS980 4G

Likely a hardware issue, the last two Assurion re-furbs have had great GPS performance. Quick locks and 3m accuracy even indoors and solid navigation in both portrait and landscape orientation when docked on the dash. This one just got the lollipop OTA last night and GPS is still strong.
Sent from my VS980 4G using Tapatalk

My GPS got worse and worse on this refurb (screen had dead spots on last one). Anyway, I tightened the screws under the back cover and it now works better than it ever did. (Motorola GPS seemed better to me, well, usually. Maybe all my screws keep coming loose--this is first time I've tried to tighten them--and it worked).

Should I upgrade or is it my phone?

My phone is only 3-4 months old and it's starting to overheat and lose battery fairly quick 5-6 hours usage max. I want to try rooting on stock, but I don't want to have to manually flash monthly security updates.. I'm just kind of over all of that now. I went to FAA and am no longer a flashaholic like I was in my early 20's. I also, don't have the time for it, and the random hiccups or break downs when I need my phone to work 100% of the time.
I don't understand why this is happening. The phone is in like new condition. I could easily list and sell it as like new, because I've kept it in a case, never let it near water or dropped it. I subconsciously know to put my keys in the opposite pocket as my phone (very good habit to get into I must add). So I think I could get a lot for this phone on Amazon looking at the prices it's being sold $350 now (I paid $300 for it months ago, but it's discontinued, and people do still want this). I would list it for $325. My seller feedback is 100% with 9 other smartphones sold with feedback stating I sell my products exactly as described, so when I list, they usually sell within 24 hours.
I don't want to sell, but would A. Would it be smart since I can basically get my money back and upgrade without losing much (if any) money after fees? B.) Do you think there's a fix, or is my phone going bust? C.) With the phone being 3-4 months old, should I just get Motorola to replace it? I heard they give 64GB new replacements for the cloud whites for Amazon customers. Then I could sell that and actually buy a 6P for not much more, and have a 6 mos old phone as opposed to a 1.5 old model.
Thoughts?

nikeman513 said:
). So I think I could get a lot for this phone on Amazon looking at the prices it's being sold $350 now (I paid $300 for it months ago, but it's discontinued, and people do still want this). I would list it for $325. My seller feedback is 100% with 9 other smartphones sold with feedback stating I sell my products exactly as described, so when I list, they usually sell within 24 hours.
Thoughts?
Click to expand...
Click to collapse
What does your seller feedback have to do with upgrading your phone, or whether it is defective?
Why does it matter that other phones sell within 24 hours? If your Samsung Galaxy S5 took 25 hours to sell, does that mean your Nexus 6 doesn't have an overheating problem?
I would recommend doing a factory reset to make sure that it isn't some malfunctioning apps that are causing this, before you send it in to Moto, or sell it for more than you paid (which is somehow relevant to the issue at hand).

We have no idea if your N6 is defective. That's up to you to decide and RMA with Motorola if you want. Motorola may send you a brand new or refurbished phone.

andy_n_ said:
What does your seller feedback have to do with upgrading your phone, or whether it is defective?
Why does it matter that other phones sell within 24 hours? If your Samsung Galaxy S5 took 25 hours to sell, does that mean your Nexus 6 doesn't have an overheating problem?
I would recommend doing a factory reset to make sure that it isn't some malfunctioning apps that are causing this, before you send it in to Moto, or sell it for more than you paid (which is somehow relevant to the issue at hand).
Click to expand...
Click to collapse
I'm just stating I could sell it if I had to and get what I paid for it, if buying a new phone is a better decision. Idk if this a common problem with the Nexus 6 or not. Everything is pretty much bone stock. I don't want Touchwiz or any bloated phone. I'd rather get another Nexus, but I am worried about the SD810. Is the SD810 in the 6P better than it is in the OP2 and LG phones? I prefer no bloatware. I'm very minimal with my apps.

seabro01 said:
We have no idea if your N6 is defective. That's up to you to decide and RMA with Motorola if you want. Motorola may send you a brand new or refurbished phone.
Click to expand...
Click to collapse
What would cause it to start lagging and getting so hot that I have to turn it off for 15-20 minutes for doing nothing, but reading or taking calls. I keep the brightness almost all the way down 99% of the time to keep the phone from getting burn in too. I've done everything I can to baby this phone for the day I do decide to resell it, but I've never had a phone just start going crazy except when I had custom ROMs on it, but it's stock now. I've tried wiping cache. I still haven't done a FDR, but I did those for people when I worked in wireless in college, and that was always a last ditch effort that never really solved a problem like this.
Not trying to be funny or weird, but I don't watch porn or visit weird websites. It's always news, check Facebook on their webpage, and Google now. Gmail attachments from co-workers and family and friends. So I don't think I could have a virus. Can a chip or RAM just go bad one day?

nikeman513 said:
What would cause it to start lagging and getting so hot that I have to turn it off for 15-20 minutes for doing nothing, but reading or taking calls. I keep the brightness almost all the way down 99% of the time to keep the phone from getting burn in too. I've done everything I can to baby this phone for the day I do decide to resell it, but I've never had a phone just start going crazy except when I had custom ROMs on it, but it's stock now. I've tried wiping cache. I still haven't done a FDR, but I did those for people when I worked in wireless in college, and that was always a last ditch effort that never really solved a problem like this.
Not trying to be funny or weird, but I don't watch porn or visit weird websites. It's always news, check Facebook on their webpage, and Google now. Gmail attachments from co-workers and family and friends. So I don't think I could have a virus. Can a chip or RAM just go bad one day?
Click to expand...
Click to collapse
It could be a wide variety of things. From apps (which clearly it isn't, given the provided information) to hardware. Whether it's a defective battery that's getting hot under very minimal loads or during charging, or whether it's a dying chip/something shorting out which is generating much more heat than it should. Download System Monitor Lite on Google Play and see what temperatures your CPU and battery are running on, and at what frequencies/loads it ramps up at. If the temps ramp up even when there's no CPU usage, then it's probably hardware and Motorola/Google (depending on the origin of device) will do their best to satisfy you within a week. If your CPU usage is constantly hitting high numbers you should probably factory reset your device.
Hope this gets you a step further, unlike other comments..

humzaahmed155 said:
It could be a wide variety of things. From apps (which clearly it isn't, given the provided information) to hardware. Whether it's a defective battery that's getting hot under very minimal loads or during charging, or whether it's a dying chip/something shorting out which is generating much more heat than it should. Download System Monitor Lite on Google Play and see what temperatures your CPU and battery are running on, and at what frequencies/loads it ramps up at. If the temps ramp up even when there's no CPU usage, then it's probably hardware and Motorola/Google (depending on the origin of device) will do their best to satisfy you within a week. If your CPU usage is constantly hitting high numbers you should probably factory reset your device.
Hope this gets you a step further, unlike other comments..
Click to expand...
Click to collapse
Thank you for the useful information. I'm going to check that out the next couple hours and if it seems to have odd frequency's, I'll go ahead and FDR it and give it another day. Then if it has the problem still, I'll go ahead and do a warranty claim. I just would hate to be without a phone for however long they will make me be without one, but it's getting pretty severe. Thanks again.

nikeman513 said:
Thank you for the useful information. I'm going to check that out the next couple hours and if it seems to have odd frequency's, I'll go ahead and FDR it and give it another day. Then if it has the problem still, I'll go ahead and do a warranty claim. I just would hate to be without a phone for however long they will make me be without one, but it's getting pretty severe. Thanks again.
Click to expand...
Click to collapse
A few weeks ago my Google now app updated and my phone had severe battery drain and got warmer than usual (Google now was at around 25% in battery usage). So I decided to FDR and then install a nandroid backup I had and problem solved. So imho apps can cause the symptoms you describe.

Thread cleaned. Please keep your comments/replies wholly objective - and CORDIAL. Thanks.

Is this phone even selling?

Hi!
So, I've been a long time moto user, used the old G4 plus for more than 4 years (great phone!!!) and it served me well till I dropped it in the toilet (don't ask:laugh, which is how I'm here.
Now this phone is a few months old, yet this forum is almost empty! Very unlike the G4 plus xda forums when it first released, which a few months in was filled with discussions, tips, guides and roms.
I wonder if motorola/Lenovo's abysmal track record since the iconic G3, and then the G4 has a part in this? I mean the one fusion plus is a great phone on paper, and I've loved it so far, but the lack of discussions and developer participation here on XDA can only mean it's not selling enough to pull in the elite crowd.
Is a shame too, I'm not competent enough to find ways to root my phone by myself, nor make/port roms for it. Coming to XDA has always helped me do that because of its great user base. The fact that this forum isn't where it should be for a phone this great is IMO largely Lenovo's fault in taking its user's for granted since the G4, making people weary of buying it's products even when they did finally put out a decent product in the one fusion plus.
Pity.

No

I hate to be this guy, but theres a good reason its not selling, and if its not the reason, at very least its a blessing. Ive had this phone for over a year now and its been the WORST phone I have ever had in my LIFE. The phone runs fine for a few weeks, then suddenly it becomes super slow. Facebook Messenger and Reddit will start randomly having problems loading messages and posts. Several websites including google discover app will start failing to show images. They just wont appear. Videos on many websites and youtube app will start to stutter or "Lag". I have NO idea what could have been causing this. I originally thought maybe it was a virus so I downloaded a couple virus scanners and checked and boom: Nothing. So, I factory reset and it worked for about a week and the same abnormal behavior started again. I then asked my sister, who has the same phone (who talked me into getting this phone) and shes having literally the same problems to a T. We dont know if its because of some update completely broke the phones ROM/OS or what, but the phone is an unstable broken mess right now. Nothing fixes it.
Also, that "Amazing" "Innovative" popup camera on both our phones occasionally gets stuck. You will open it to take a selfie and it simply wont go back down. The motor stops responding. Sometimes you literally have to FORCE it to go down which likely isnt good for the gears/motor. Its become so bad ive became afraid to take selfies.
I have used many Motorola/Lenovo phones and this phone is quite possibly one of the worst phones they've ever made. Let this be a warning to you if you consider buying this garbage. I didn't intend for this comment to end up basically being a review, but here we are. I was angry so I decided to write this comment and it became a review. I have been struggling lately which is why I haven't simply bought a different phone. Likely once I do get paid soon, I will be buying a different phone and I likely wont be buying a motorola again based on their quality. I literally upgraded from a Moto Z2 Force to the Moto One Fusion Plus and the moto z2 force had a ton of problems and the screen was literally peeling (look it up, its a known defect).
TLDR: Garbage phone. Constant freezes and crashes. Avoid.

cameroncr95 said:
I hate to be this guy, but theres a good reason its not selling, and if its not the reason, at very least its a blessing. Ive had this phone for over a year now and its been the WORST phone I have ever had in my LIFE. The phone runs fine for a few weeks, then suddenly it becomes super slow. Facebook Messenger and Reddit will start randomly having problems loading messages and posts. Several websites including google discover app will start failing to show images. They just wont appear. Videos on many websites and youtube app will start to stutter or "Lag". I have NO idea what could have been causing this. I originally thought maybe it was a virus so I downloaded a couple virus scanners and checked and boom: Nothing. So, I factory reset and it worked for about a week and the same abnormal behavior started again. I then asked my sister, who has the same phone (who talked me into getting this phone) and shes having literally the same problems to a T. We dont know if its because of some update completely broke the phones ROM/OS or what, but the phone is an unstable broken mess right now. Nothing fixes it.
Also, that "Amazing" "Innovative" popup camera on both our phones occasionally gets stuck. You will open it to take a selfie and it simply wont go back down. The motor stops responding. Sometimes you literally have to FORCE it to go down which likely isnt good for the gears/motor. Its become so bad ive became afraid to take selfies.
I have used many Motorola/Lenovo phones and this phone is quite possibly one of the worst phones they've ever made. Let this be a warning to you if you consider buying this garbage. I didn't intend for this comment to end up basically being a review, but here we are. I was angry so I decided to write this comment and it became a review. I have been struggling lately which is why I haven't simply bought a different phone. Likely once I do get paid soon, I will be buying a different phone and I likely wont be buying a motorola again based on their quality. I literally upgraded from a Moto Z2 Force to the Moto One Fusion Plus and the moto z2 force had a ton of problems and the screen was literally peeling (look it up, its a known defect).
TLDR: Garbage phone. Constant freezes and crashes. Avoid.
Click to expand...
Click to collapse
I can add that the resolution doesn't even fit the screen, it's literally watching a tv with zoom mode on. Worst decision i made too, now i'm stuck with it