Related
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
fedreta said:
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
Click to expand...
Click to collapse
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
**Menos** said:
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
Click to expand...
Click to collapse
I've never tried flashing a ROM before, my device is already unlocked/rooted. What do you do exactly to flash Cyanogenmod?
Just installed Cyanogenmod and saw that the problem is not solved. I fear starting to appear that the problem is hardware. Now have to wait for an update from Google.
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Tony_YYZ said:
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Click to expand...
Click to collapse
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update. All the nexus devices start their lives like this, one of the few annoying things about being a nexus fanboy, you get to enjoy the bugs before anyone else gets to.
http://www.engadget.com/2013/08/13/2013-nexus-7-multitouch-bug/
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Tony_YYZ said:
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Click to expand...
Click to collapse
Yeah I remember this too, something about the kernel supplying not enough voltage to the touchscreen in an attempt to improve battery life. This has to be a kernel bug.
Try flashing a different kernel as that is what bridges hardware and software.
Aren't all kernels based on stock?
Sent from my Nexus 7 using xda premium
uprightbass360 said:
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
sfhub said:
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
Click to expand...
Click to collapse
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation. I think that judging by past examples anyone who has bought a nexus device at launch has either knowingly or unknowingly already agreed to be a guinea pig. In the end I am one of the last people to say that someone shouldn't return a defective piece of hardware, but it seems a lot of the issues people are having are being misdiagnosed as hardware issues when in fact they can (and most likely will) be fixed by an OTA.
I can dare to say that the issue is present in Android 4.3 affecting any device running it even Custom Roms I'm on CyanogenMod 10.2 on my d2spr (S3 Sprint) and the issue is present there too. Also that causes reboots too. I could be wrong too.
Sent from my SPH-L710 using Tapatalk 4
Team SXTP
Also the jss build is giving problems in the nexus 4 thread
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...
uprightbass360 said:
Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
uprightbass360 said:
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation.
Click to expand...
Click to collapse
No problem with repeating what they are saying, but you seem to have commited them to more than they are saying in their personal comments, not those as official reps.
IMO everyone should get accurate information so they can evaluate for themselves whether it is worth the risk to keep it or just to return the unit.
Personally I think the random reboots and GPS can be addressed in software and the multi-touch is probably 50/50 something that can be worked around in software, but everyone has their own tolerance levels for these kind of issues and "are looking into it or are working on it" and "going to be fixed" are quite different levels of commitment.
I'm sorry but what issues are you having because I exchanged my first n7 because I was having multitouch stuttering and issues with unresponsiveness which made the device unusable. The new device is okay.
Android 5.1.1 Experience and Discussion
OTA 5.1.1 Link https://android.googleapis.com/pack...gned-volantis-LMY47X-from-LRX22L.5cb0c625.zip
Factory Images 5.1.1 https://dl.google.com/dl/android/aosp/volantis-lmy47x-factory-3efdc8d4.tgz
marcomsousa said:
Android 5.1.1 Experience and Discussion
OTA 5.1.1 Link https://android.googleapis.com/pack...gned-volantis-LMY47X-from-LRX22L.5cb0c625.zip
Factory Images 5.1.1 https://dl.google.com/dl/android/aosp/volantis-lmy47x-factory-3efdc8d4.tgz
Click to expand...
Click to collapse
Wish these were also available for the LTE model
[/COLOR]
Zylograth said:
Wish these were also available for the LTE model
Click to expand...
Click to collapse
Want to trade?
*WARNING* RE-enable OEM Bootloader Unlocking after Update!!!
Just a heads up and REMINDER to go into Developer Options and turn OEM Unlocking back on after the OTA update because it had turned mine back off after sideloading.
I wish I had my laptop set up so I could remote in from work right now and begin downloading the image.
I take it Root is still working?
bjacks12 said:
I wish I had my laptop set up so I could remote in from work right now and begin downloading the image.
Click to expand...
Click to collapse
I've been thinking off using one of my phones as a hotspot for my laptop...Just not thinking it will be quite fast enough and stable enough to download and get a good MD5. My company watches everything.
techiedj said:
Just a heads up and REMINDER to go into Developer Options and turn OEM Unlocking back on after the OTA update because it had turned mine back off after sideloading.
Click to expand...
Click to collapse
Why not just get it over with and UNLOCK it? Once you are unlocked, the state of that checkbox is irrelevant.
techiedj said:
Just a heads up and REMINDER to go into Developer Options and turn OEM Unlocking back on after the OTA update because it had turned mine back off after sideloading.
Click to expand...
Click to collapse
Why is that important? Will I brick my device if I don't? Please explain for an absolute newbie!
Thank you!!!
s0101 said:
Why is that important? Will I brick my device if I don't? Please explain for an absolute newbie!
Thank you!!!
Click to expand...
Click to collapse
If you don't unlock, and leave your bootloader unlocked it can. If you have the check box checked then the bootloader remains locked. So if you get caught with a bad flash or anything else that causes a bootloop there is no way to gain access to the bootloader and run fastboot.
Not off to a great start. I've had my 3rd crash triggered simply by browsing to the reddit nexus 9 board. Now it appears to be on a forced cache erase after the consecutive crashes.
From this we can safely say nobody in Google pays any attention the forum moaning otherwise they might have noticed this issue.
Anyone get an OTA for the LTE version yet? They haven't posted the factory images which scares me a little that LTE might get left behind. The 5.0.2 links went up for both at the same time.
stuken said:
Not off to a great start. I've had my 3rd crash triggered simply by browsing to the reddit nexus 9 board. Now it appears to be on a forced cache erase after the consecutive crashes.
From this we can safely say nobody in Google pays any attention the forum moaning otherwise they might have noticed this issue.
Click to expand...
Click to collapse
Mine's still running really warm and it's losing power over USB just by being on. I'm watching the battery drain simply from the screen idling on Google Now. Come the **** on Google, heat and battery drain should have been primary concerns.
Edit: Fortunately though, it seems like the entire device is running buttery smooth, which is literally a first on stock Android for me. Even my Nexus 6 hiccups without a custom ROM and that has the S805 and 1 more GB of memory.
Still no OTA for LTE on 5.01 -> 5.02 ...
What the hell is Google doing... firstly releasing almost beta Lollipop that on our Nexus have serious issues.. after waiting and being the last device to be updated still no upgrade to LTE which is more expensive and deserves at least same support.
If our model is left behind, I will surely not buy a Nexus device ever again.
atomikpt said:
Still no OTA for LTE on 5.01 -> 5.02 ...
What the hell is Google doing... firstly releasing almost beta Lollipop that on our Nexus have serious issues.. after waiting and being the last device to be updated still no upgrade to LTE which is more expensive and deserves at least same support.
If our model is left behind, I will surely not buy a Nexus device ever again.
Click to expand...
Click to collapse
LTE takes time. I wouldn't worry about it. I bet factory images are up within a day or two. I'm an LTE owner too, so I'm in the same boat. I'm just happy it actually started rolling out, as it started to look like it wasn't happening. This is a much bigger update than 5.0.1 -> 5.0.2
Updated this morning. So far so good
So far, it's definitely an improvement on performance but it remains to be seen with this is another cache-wipe factor or something. One of the first-impression fixes is that the light sensor seems to actually work now, while it was almost useless before.
I noticed the stock kernel is now on 2,5GHz high and that both cores are allways on, which i am not sure if it was happening on 5.0.x. I remember Franco noticing it on Nexus 6 5.1 too, so i guess it's a common practice by google to not turn cores off anymore.
Well so far so good. I never had major issues before. OTA side loaded fine. Did a factory reset to set up fresh. Now that everything is set up I'm just waiting for it to charge completely. It did get warm installing and updating everything, but no issues so far. Everything went smoothly.
There's a new apk named 'Who Am I?' That is disabled by default in this update. Turns out it's a widget that literally shows you the time and what your name is. Maybe it's for people with dementia or short term memory.
The way things have been going, most of us might have needed that widget by the time this update got to us if we'd waited much longer.
So, I just got myself a brand new Nexus 6P today, and I'm in love. However, after unlocking the bootloader, connecting to my Wifi network (haven't gotten to test others yet) seems to cause my device to slow down and lock up. This happens on both the stock rom and on cyanogenmod. Has anybody else experienced this, or know how to fix it without RMAing my phone?
Pyrokineticdew said:
So, I just got myself a brand new Nexus 6P today, and I'm in love. However, after unlocking the bootloader, connecting to my Wifi network (haven't gotten to test others yet) seems to cause my device to slow down and lock up. This happens on both the stock rom and on cyanogenmod. Has anybody else experienced this, or know how to fix it without RMAing my phone?
Click to expand...
Click to collapse
I never faced any such problem, ever. Which Android version and build number are you currently running on your 6P?
Also did you try re-locking and then checking if it works fine?
DJBhardwaj said:
I never faced any such problem, ever. Which Android version and build number are you currently running on your 6P?
Also did you try re-locking and then checking if it works fine?
Click to expand...
Click to collapse
I'm on Android 6.0.1 and my build number is rather large because I'm on cyanogenmod right now, you can see a screenshot of my about page if you go to imgur slash 1b8VtH7 and yes, it did persist when I re-locked it
EDIT: If you want, I can make a video of the behavior so you can see it for yourself.
Pyrokineticdew said:
I'm on Android 6.0.1 and my build number is rather large because I'm on cyanogenmod right now, you can see a screenshot of my about page if you go to imgur slash 1b8VtH7 and yes, it did persist when I re-locked it
EDIT: If you want, I can make a video of the behavior so you can see it for yourself.
Click to expand...
Click to collapse
I could see in the screenshot that your radio version is latest, so my doubts are clear, and everything is fine there. To rule out the software aspect completely, you could give a try to a factory reset by flashing the factory image.
If that doesn't work, I would advise you to re-lock bootloader, and take your phone to the service centre.
Yeah, I was gonna give re-flashing stock a try in the morning. As far as bringing it to a service center, I've got no idea what to do, since I bought the phone through Amazon. Hopefully there should be some sort of RMA procedure available through them
Pyrokineticdew said:
Yeah, I was gonna give re-flashing stock a try in the morning. As far as bringing it to a service center, I've got no idea what to do, since I bought the phone through Amazon. Hopefully there should be some sort of RMA procedure available through them
Click to expand...
Click to collapse
Good luck. :good:
Even I brought my Nexus 6P through Amazon India. I had an issue with a misplaced volume key, so what I did was, I restored stock, relocked and took the phone to the nearest Huawei service centre. Took the phone, box, and all accessories, and also a copy of invoice from Amazon itself.
DJBhardwaj said:
Good luck. :good:
Even I brought my Nexus 6P through Amazon India. I had an issue with a misplaced volume key, so what I did was, I restored stock, relocked and took the phone to the nearest Huawei service centre. Took the phone, box, and all accessories, and also a copy of invoice from Amazon itself.
Click to expand...
Click to collapse
Well, I got antsy and just reflashed a bunch of different versions and roms; it's all the same, but now it's actually saying there's a problem instead of just hanging; gotta send it in -_- Oh well, at least I know when it finally gets here (again) I'll have an awesome phone.
Pyrokineticdew said:
Well, I got antsy and just reflashed a bunch of different versions and roms; it's all the same, but now it's actually saying there's a problem instead of just hanging; gotta send it in -_- Oh well, at least I know when it finally gets here (again) I'll have an awesome phone.
Click to expand...
Click to collapse
Good luck with it. :good:
Hello guys.
I live in South Korea and just had contact with customer service.
They said once my warranty is now passed, they might not be able to provide me a free repair, but google will soon release an update that is supposed to fix the BLOD(Boot Loop Of Death), so I'd better wait for it.
I don't know if it will work, but for me, and people having a phone which can't even get to recovery but only bootloader, who seem to have nothing to lose, this update will worth the wait.
Let's hope that's true and we can get our 6P back to life.
Didnt Google mentioned BLOD is a hardware issue earlier?
Aswin08 said:
Didnt Google mentioned BLOD is a hardware issue earlier?
Click to expand...
Click to collapse
Yeah. There's a news that Google said it's hardware problem, but Huawei did say the upcoming update will fix it.
IDK which one is truth.. just hoping simply updating software will fix it.
frostydawn said:
Yeah. There's a news that Google said it's hardware problem, but Huawei did say the upcoming update will fix it.
IDK which one is truth.. just hoping simply updating software will fix it.
Click to expand...
Click to collapse
If it's a software issue why does it happen with Marshmallow, Nougat and custom ROMs? I don't think Huawei is being honest.
jhs39 said:
If it's a software issue why does it happen with Marshmallow, Nougat and custom ROMs? I don't think Huawei is being honest.
Click to expand...
Click to collapse
Oh it didn't occured to me..
I also have some doubt that it's a software-related problem, because downgrading to MM doesn't even work.
Well, maybe they are fixing bugs that they haven't found before, or also maybe, the defective OS has triggered something..
I'm not sure that update will fix my phone, but for now, this is my last hope.
frostydawn said:
Oh it didn't occured to me..
I also have some doubt that it's a software-related problem, because downgrading to MM doesn't even work.
Well, maybe they are fixing bugs that they haven't found before, or also maybe, the defective OS has triggered something..
I'm not sure that update will fix my phone, but for now, this is my last hope.
Click to expand...
Click to collapse
Good luck but I honestly wouldn't get my hopes up too high. But you aren't the first person Huawei told this to. Hopefully there is something to it besides them trying to brush people off. I personally think people should file a class action suit against Huawai since the phone appears to be defective and it should last for more than a year given its premium price. I've never had a phone from HTC, LG or Samsung break, no matter how long I kept using them. I've never even heard of another phone that has all the issues the 6P does.
jhs39 said:
Good luck but I honestly wouldn't get my hopes up too high. But you aren't the first person Huawei told this to. Hopefully there is something to it besides them trying to brush people off. I personally think people should file a class action suit against Huawai since the phone appears to be defective and it should last for more than a year given its premium price. I've never had a phone from HTC, LG or Samsung break, no matter how long I kept using them. I've never even heard of another phone that has all the issues the 6P does.
Click to expand...
Click to collapse
Yeah I'm suspecting if there's an inherent hardware defects, and if that's the case, I think they should provide us a proper support like LG providing refund of Nexus 5x in US.
But, I'm not an expert and don't know what caused boot loop.
As I saw another person who may live in another country of mine, heard from Huawei that update will fix the problem, there may be something google is preparing for.
For now, there best thing I can do, is wait android 7.1.2 beta image.
If it won't work, that's a problem of then.
p.s. luckily I have unlocked bootloader, but considering boot looping devices can update their software only through unlocked bootloader, what should normal people having locked bootloader should do?
frostydawn said:
Yeah I'm suspecting if there's an inherent hardware defects, and if that's the case, I think they should provide us a proper support like LG providing refund of Nexus 5x in US.
But, I'm not an expert and don't know what caused boot loop.
As I saw another person who may live in another country of mine, heard from Huawei that update will fix the problem, there may be something google is preparing for.
For now, there best thing I can do, is wait android 7.1.2 beta image.
If it won't work, that's a problem of then.
p.s. luckily I have unlocked bootloader, but considering looping devices can update their software only through unlocked bootloader, what should normal people having locked bootloader should do?
Click to expand...
Click to collapse
Exactly, with those people have warranty expired and locked bootloader as well will have to throw it away?
Blod, I assume thats bootloader something something. Wish everyone would just write ..... Nevermind.
dontbeweakvato said:
Blod, I assume thats bootloader something something. Wish everyone would just write ..... Nevermind.
Click to expand...
Click to collapse
Battery life of death...
dontbeweakvato said:
Blod, I assume thats bootloader something something. Wish everyone would just write ..... Nevermind.
Click to expand...
Click to collapse
Sorry for not writing post in a way everyone can understand easily and using only abbreviation.
BLOD means Boot Loop Of Death
tigsandmitch said:
Battery life of death...
Click to expand...
Click to collapse
*Boot Loop of death
Hardware Issue
frostydawn said:
I don't know if it will work, but for me, and people having a phone which can't even get to recovery but only bootloader, who seem to have nothing to lose, this update will worth the wait. Let's hope that's true and we can get our 6P back to life.
Click to expand...
Click to collapse
If you have exhausted your warranty options, it's time to put the phone down and move on.
v12xke said:
If you have exhausted your warranty options, it's time to put the phone down and move on.
Click to expand...
Click to collapse
Maybe you're right.
I'm not sure if the update will fix my phone, and whether they meant 7.1.2 beta or officially update.
I also have a bad feeling that my phone won't back, but if this phone doesn't return, I have no choice but keep using my old-fashioned Nexus 5.
If the beta update doesn't fix it, maybe I'll just give up or give it a second chance for official update.. but for now, I can see some hope because Huawei said it to me.
There's some news about what I tried, but there ain't good things.
First, I downloaded N4F26O update(https://developers.google.com/android/images), which was uploaded in 2 days ago(Yeah, I only thought about 7.1.2 beta, abd didn't think about this) and installed it.
It didn't work.
So I contacted with Huawei and Google's consumer care center.
Huawei said, to talk about softwares, I should contact with Google.
Google said, they didn't receive any plan of the update which is supposed to fix boot loop. I got confused, since a days ago, Huawei once did say there will be that update.
They also said, if I have a secondary phone, I'd better use that phone and see if the update will be released and fix my phone.
So... I didn't gain anything. Google and Huawei both said they can't assure the update will fix the bootloop, and the only clear solution is to change its motherboard.
Well, I won't give up, at least unti thel 7.1.2 beta's release, but I'm tired and for now, have nothing to do.
I'll just wait for the 7.1.2 beta.
I'll just keep waiting...
If you feel compelled to support, and bring attention to this issue.
https://www.change.org/p/google-inc...utm_source=share_petition&utm_medium=copylink
frostydawn said:
There's some news about what I tried, but there ain't good things... I'll just keep waiting...
Click to expand...
Click to collapse
Since you have nothing to lose, why not try this while you are waiting. I would direct any questions you have about this method to the dev.
v12xke said:
Since you have nothing to lose, why not try this while you are waiting. I would direct any questions you have about this method to the dev.
Click to expand...
Click to collapse
But that's seems to be for devices that's stuck in EDL mode.
I still can access bootloader, so thank you for your advice, but that seems to not work.
I'm afraid that you'll have to let this go.. Huawei is know for telling customers BS on the phone. Even the warranty repair center sucks. They downgrade people their phones and say that the battery issue is now resolved. It really is a shame, but they don't give a rat's *ss about you or any other customer who has already paid for the product.
Hey XDA,
Am a new user and i need some advice on the new Andriod O.
In the past I had the Andriod 7.1.1 and my got the BLOD. I sent the phone back to and got another one with Andriod 7.0.
I never upgraded the version because i didnt know if it was safe and now seeing that Andriod O is out. Am just wondering if its safe to upgrade?
Am considering to unlock the Bootloader and USB Debugging just in the event something goes wrong i guess i can always install a new ROM or something.
As i really dont want to be hurt again
Any advice for a newbie?
Thanks in advance.
Capt_JuMbO said:
Hey XDA,
Am a new user and i need some advice on the new Andriod O.
In the past I had the Andriod 7.1.1 and my got the BLOD. I sent the phone back to and got another one with Andriod 7.0.
I never upgraded the version because i didnt know if it was safe and now seeing that Andriod O is out. Am just wondering if its safe to upgrade?
Am considering to unlock the Bootloader and USB Debugging just in the event something goes wrong i guess i can always install a new ROM or something.
As i really dont want to be hurt again
Any advice for a newbie?
Thanks in advance.
Click to expand...
Click to collapse
The android version isn't what causes the BLOD but a degraded battery is what causes it. It is completely safe to update to O.
DEVILOPS 007 said:
The android version isn't what causes the BLOD but a degraded battery is what causes it. It is completely safe to update to O.
Click to expand...
Click to collapse
Okay when i called Hauwei support they told me it was a problem with 7.1.1 thats why i never updated.
So does that mean that the BLOD can come back? Or was it due to an inferior battery used on some devices ?
Capt_JuMbO said:
Okay when i called Hauwei support they told me it was a problem with 7.1.1 thats why i never updated.
So does that mean that the BLOD can come back? Or was it due to an inferior battery used on some devices ?
Click to expand...
Click to collapse
It depends on how well you look after your battery. This issue is mostly present on the Nexus 6p as AFAIK but it can happen on any device. Just try to look after your battery by charging to the max of 80% and try not to go under 30% too often. What Huawei told you assuming you understood them correctly was BS and likely a way for them to put the blame on Google and not their hardware. Degraded batteries cause bootloops. If you already had the issue once then it will likely come back so you should definitely change the battery if you can't get Huawei to send you a new one.
DEVILOPS 007 said:
It depends on how well you look after your battery. This issue is mostly present on the Nexus 6p as AFAIK but it can happen on any device. Just try to look after your battery by charging to the max of 80% and try not to go under 30% too often. What Huawei told you assuming you understood them correctly was BS and likely a way for them to put the blame on Google and not their hardware. Degraded batteries cause bootloops. If you already had the issue once then it will likely come back so you should definitely change the battery if you can't get Huawei to send you a new one.
Click to expand...
Click to collapse
I guess what Hauwei was saying was BS but google didnt offer any help just said to contact them.
I try honestly try to look after the battery, i normally let it charge to 100% at night and take it off before i sleep. I dont leave it on the charger ever or longer than i need. Then charge it again around 20-15% back to full.
If i was to charging at 30% to 80%, i dont think would give me alot of time and would have to charge more often. Wouldn't that harm the battery more?
DEVILOPS 007 said:
Degraded batteries cause bootloops. If you already had the issue once then it will likely come back so you should definitely change the battery if you can't get Huawei to send you a new one.
Click to expand...
Click to collapse
This is the second phone they sent me, so it doesnt have any more warranty. Am hopeful it can last and would have to replace anything. :fingers-crossed: Are there any sources for good battery replacement ?
Capt_JuMbO said:
This is the second phone they sent me, so it doesnt have any more warranty. Am hopeful it can last and would have to replace anything. :fingers-crossed: Are there any sources for good battery replacement ?
Click to expand...
Click to collapse
Your first thought was the correct one. Start by unlocking your bootloader and then update to 8.0 and enjoy your phone. If/when you ever have a battery issue there are plenty of places to have it replaced at a reasonable price. Android software version was never the cause (or cure) to a bootlooping phone, so you got some bad information there.