Develop Bugs

For thouse, who run stock 5.0.x-5.1.x, why to risk the device?

I have some thumb rule, never update to the newest firmware, and reed the comments. Also at home I have a router, that the manufacture update the firmware from time to time, but I used to run one firmware before the last one. It just an example, but since all the Lollipop, people complain, so why bother? Can't you wait for a while, till Google resolve all the issues? Do you consider Kitkat was perfect then? Or does Lollipop runs perfect on Nexus 6 & 9? I'm starting to think, it intentionally, like iOS 7 on iCrap 4, on iOS 6 it was fine, just think of it, maybe Google do it intentionally, to make us buy a new device? Or they just do a bad optimization job for older devices, and put all effort toward new devices? Any thoughts? I know we all nexus user, are a free beta testers, but if running latest firmware, means it brick out devices, it's hard to thrust Google like that, so I think it's better to stay on Kitkat till better times.
Sent from my hammerhead using Tapatalk

The people who's tablets work fine (the vast majority I'd guess) don't complain. You only here from the people who have problems.
I've been on lollipop since the preview and it's been great. I'll be flashing 5.1.1 the second it's out. Kitkat is dead to me, and very ugly looking back. It certainly was not perfect.
If my device gets the brick people are talking about it would suck but I really, really doubt it has anything to do with the firmware. Some hardware failure most likely. No reason to stay on an old release.

5.0.2 was horrible. While I disregard majority of users complaining of battery life, some of them weren't spewing nonsense.
5.1 is an improvement. I'm one of the guys who do not post every complaint or dissatisfaction I encounter with the Nexus 7. I know what the problem is, I know where to ask for help to pinpoint the cause, now it's my turn to make a decision, stay on Lollipop? or revert to KitKat? Or remove the cause, in other words the app itself.
Back to the OP, there is no risk updating to 5.x. Your device won't magically break. If you like to play it safe, maybe it's better for you to wait for user feedback and ignore the OTA.

OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?

I wouldn't take an ota myself. Not because of "the brick," I think thats a hardware problem, I feel it's a cleaner update with fastboot and if something fails I'll know what.
And you can (and should) make full nandroid backups in a custom recovery (cwm, twrp etc.).
But to the poster aboves comment it just goes to show you people are having different experiences. 5.0.2 was fantastic for me, great battery life, best it's ever been actually (still as good on 5.1 ~8 hours screen time over two days.)
The memory leak was/is a problem. Oh no I had to reboot once a week. Huge headache. On 5.1 I'm at 270 hours uptime and system ram's at 479. It is creeping up slooowly but better than 5.0.2
I guess it depends what you do with the tablet and especially what apps you have installed. I use my **** pretty heavily though so I don't know why I'v had no problems.

donisan969 said:
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
Click to expand...
Click to collapse
Hard bricks have been reported from both OTA and ADB updates, but very seldom from users of custom ROMs... Most likely cause is eMMC failure due to faulty hardware, though the issue is present on nexus 4 and 5 as well... Possibly faulty bootloader software too.

^Bootloader faults could be possible.. that has pretty low level access. I don't know low enough to corrupt the chip. I don't know. Asus/google probably does but guaranteed you'll never hear a word from them.
I hope it's not something like the infamous s2 brickbug. Then you're just playing russian roulette. Maybe entropy can help lol.
What emmc chips are the 4 and 5 using? I'll have to look.

I'm not sure this is true but if you use Greenify I think the memory is kept in check better, although it requires root. I still see the occasional launcher redraw but not nearly as bad as it was in 5.0. I was on 5.0.2 for several weeks and wouldn't have updated if I hadn't read about the hardware failures.

Well if you don't update your tab, than you don't need a Nexus, buy some cheap chinese tabs for 70-100$, almost all of them are on kitkat, most of them vanila android, no updates, and they all work fine.
This is Nexus.It's a developers tab, for testig, trying, people who like the freshest system on their device, who like clean android....if something's not working, there's always an image of the old system or a bunch of ROMs to test and use...

I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk

donisan969 said:
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
Click to expand...
Click to collapse
Device OEM is irrelevant in that regard, the quality of internal components is really the crux of understanding hardware failure IMO. of the major android OEMs, all of them have in the past put forth devices that were predisposed to early hardware failure, mostly due to choices of components used during the manufacturing process. Hardware revisions on individual devices of the same model is also a valid form of comparison.

P8000 unusual problem.

Hello.
11.11.2015 i recived a notification on phone that Elephone had released a new update to improve system functioning ect.
Keep in mind this is a stock p8000. nothing done with it.
I downloaded update, installed and it said phone will reboot.
After that phone is stuck in bootloader and simply wont boot.
Ive tried wiping cache and factory reset but PHONE WONT turn on.
So question is. What the hell do i do now?

There's like five threads about the same problem, so nothing really unusual about this excerpt for the lack of quality control from Elephone which apparently releases broken OTA:s and phones with old or modified base roms. ?
This thread should be merged with other ones.

Have anyone found a solution?
pitrus- said:
There's like five threads about the same problem, so nothing really unusual about this excerpt for the lack of quality control from Elephone which apparently releases broken OTA:s and phones with old or modified base roms.
This thread should be merged with other ones.
Click to expand...
Click to collapse
Have anyone found a solution to the problem then?
Or is my only choice to open a dispute with PayPal?

The Boards are full of Threads and solutions about this problem !
Why aren't you looking around a bit ?
How about the first post in Q&A section ???
http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203

StormiZMo said:
Have anyone found a solution to the problem then?
Or is my only choice to open a dispute with PayPal?
Click to expand...
Click to collapse
manually flash the stock rom .. i faced the same ****.. i followed the below steps and my elephone working fine
http://bbs.elephone.hk/thread-9229-1-1.html
hope this will work...

Fixed
As it turns out i managed to fix the problem.
Manually flashed a new rom and now the phone works fine. Tho im not installing the new update again.
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
People without the necessary skills on this subject would have to return or get the money refunded because THE only way to fix this is flashing a new rom..
Thanks for the help people!!

StormiZMo said:
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
Click to expand...
Click to collapse
LOL, fired for what? it worked on most devices.
you get what you pay for! how are elephone selling a phone with decent specification for that price? they cut corners everywhere.
quality being 1 and skilled staff is the other.
with the given resources, their staff did they best they could with the test hardware they had.

StormiZMo said:
As it turns out i managed to fix the problem.
Manually flashed a new rom and now the phone works fine. Tho im not installing the new update again.
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
People without the necessary skills on this subject would have to return or get the money refunded because THE only way to fix this is flashing a new rom..
Thanks for the help people!!
Click to expand...
Click to collapse
Also, most China phones don't even get updates, or even more exclusive, source code releases like this one. My guess is that there's likely only a one man show in charge of software development for this model, so give them some slack will you. [emoji1]

mine went off to after the OTA so i had to flash manually and like my friend said there trying, unlike most china phone company's so even though mine failed my father's and my friend's p8000 got there OTA np

It seems like the first 5000 batch delivered had no notification led,they seem to put in different hardware thats available.So end up with a hotch podge of slightly different devices.
So fingers crossed that a update works.Thankfully Elephone allows ,enables development.

It also looks like OTA update fails on rooted phones, which is not so different than what happens to most Android phones. When I used a Samsung phone long ago, OTA update notifications wouldn't even show up if you had rooted your phone, and on other phones I remember having a similar issue after I applied an OTA update with the phone rooted

Nougat Beta Completed - Official update due in January to S7 and S7 Edge

Samsung apparently has sent out a final notification to all those enrolled in the Nougat Beta that there will be no more updates and that the beta ends officially on December 30th and that they will attempt to push out the official update to everyone in January. Hope this means they were able to quash all major bugs.
http://www.androidcentral.com/galaxy-s7-and-s7-edge-receive-nougat-update-january
And it is officially Android 7.1.1, at least for those in the US.

Hopefully we get it soon, I would love some Nougat. At this point I prefer to not have to root my phone to get updates because it's a hassle without being able to unlock the bootloader. I was rooted for awhile and IMHO stock runs butter unless you spend hours customizing it. I love debloating but I would prefer a fully unlocked/rooted phone to a partial solution.
I don't have high hopes for when we get this updated because of verizon but we eventually will, about 2 years after everyone else

JerseyDubbin said:
Hopefully we get it soon, I would love some Nougat. At this point I prefer to not have to root my phone to get updates because it's a hassle without being able to unlock the bootloader. I was rooted for awhile and IMHO stock runs butter unless you spend hours customizing it. I love debloating but I would prefer a fully unlocked/rooted phone to a partial solution.
I don't have high hopes for when we get this updated because of verizon but we eventually will, about 2 years after everyone else
Click to expand...
Click to collapse
I haven't been rooted for over a year. I was on an LG G3 before my S7 and so far, I haven't found a real need to root. Before, I rooted because I used TiBu to backup my apps, but with the G3, they had their own backup utility that worked just like TiBu, but it's only for LG devices.
But with how Google Play uploads settings now, that appears to work just fine for me as well, so at this point, I have no reason to root. Plus, I really love Samsung Pay so I don't want to lose that.

This is the first device I have owned that I have never rooted. No need to. Faster than anything I have ever owned and mine never slows down for my usage. It's the first device that I feel works as intended. I also wasted a few years of my life with this stuff and just don't have the motivation anymore. Especially without an unlocked bootloader and custom recovery, I'd never.

JediDru said:
This is the first device I have owned that I have never rooted. No need to. Faster than anything I have ever owned and mine never slows down for my usage. It's the first device that I feel works as intended. I also wasted a few years of my life with this stuff and just don't have the motivation anymore. Especially without an unlocked bootloader and custom recovery, I'd never.
Click to expand...
Click to collapse
Agree completely. The root process works well etc but I had to go through xposed and do a lot of tweaks to get it running well for really no gain over what I had stock.

JediDru said:
This is the first device I have owned that I have never rooted. No need to. Faster than anything I have ever owned and mine never slows down for my usage. It's the first device that I feel works as intended. I also wasted a few years of my life with this stuff and just don't have the motivation anymore. Especially without an unlocked bootloader and custom recovery, I'd never.
Click to expand...
Click to collapse
I completely agree. The G3 was the first phone I ended up not rooting. I did at first because I was just in that mode of, get a new phone, root, flash a custom ROM. But as I started getting used to a lot of the features, and found that the battery life wasn't bad, coupled with running Greenify in non-root mode, I could make the battery last 1.5 days. So, over the last year of the two years I owned it, I didn't root.
With the S7, no need to root. This is smoothest phone I've had yet. The quality of the phone itself is excellent. So, this phone will not be rooted.

It appears the official Nougat OTA is being pushed out, with beta testers getting it first.
Anyone on here that has gotten the Nougat OTA notification yet? I'm holding off on accepting until I know better on how it performs, etc.
http://www.androidcentral.com/stabl...ing-galaxy-s7-and-s7-edge-starting-beta-users

iBolski said:
It appears the official Nougat OTA is being pushed out, with beta testers getting it first.
Anyone on here that has gotten the Nougat OTA notification yet? I'm holding off on accepting until I know better on how it performs, etc.
http://www.androidcentral.com/stabl...ing-galaxy-s7-and-s7-edge-starting-beta-users
Click to expand...
Click to collapse
Nothing on my end yet.
Sent from my SM-G930V using XDA-Developers Legacy app

was there ever a second beta OTA sent out to Verizon testers? I didn't get into the beta but side loaded the only 7.0 beta build OTA that was floating around and my build number is NRD90M.G930VVRU4ZPK4. Was there an update to after that? Trying to figure out if the Nougate beta -> final OTA (assuming someone pulls it) will work on my phone or if I'll need to find the intermediary beta OTAs or else wipe clean and start from scratch.

sklarskyj said:
was there ever a second beta OTA sent out to Verizon testers? I didn't get into the beta but side loaded the only 7.0 beta build OTA that was floating around and my build number is NRD90M.G930VVRU4ZPK4. Was there an update to after that? Trying to figure out if the Nougate beta -> final OTA (assuming someone pulls it) will work on my phone or if I'll need to find the intermediary beta OTAs or else wipe clean and start from scratch.
Click to expand...
Click to collapse
I believe there were only two betas for VZW phones and then they cancelled the beta testing for VZW-based phones. Not sure why. Kind of sucks. Probably Big Red had something to do with it.

j0hnh0lmes said:
Nothing on my end yet.
Sent from my SM-G930V using XDA-Developers Legacy app
Click to expand...
Click to collapse
Same here, tried rebooting and checking again a few times and still nothing.
Oh well

I spoke to Verizon about this and they dont know when the update will be out.

SoerenHelmer said:
I spoke to Verizon about this and they dont know when the update will be out.
Click to expand...
Click to collapse
Of course they don't. They have to add crapware, disable a bunch of stuff and add backdoors.
Sent from my SM-G930V using XDA-Developers Legacy app

SoerenHelmer said:
I spoke to Verizon about this and they dont know when the update will be out.
Click to expand...
Click to collapse
That's their usual response.

I've read US-Based carriers have no ETA yet. Grr.

iBolski said:
I've read US-Based carriers have no ETA yet. Grr.
Click to expand...
Click to collapse
I swear searching around the interwebs for information on release dates has at least as much mis-information as looking for information on the election candidates during the election. So much trash.
But I haven't found anyone stating they heard definite dates. I'm thinking it will be late January at this point maybe early Feb before it hits our phones.

i have given up speculating anything that involves verizon. nothing would surprise me.

Take it where its coming from but it looks like some US non-beta testers are starting to see the update. "Unlocked" phones only but still....
http://www.theverge.com/2017/1/19/14321980/samsung-galaxy-s7-edge-android-nougat-update

I have an official unlocked US model, but nothing yet. I expect to see the update by the weekend. Crossing fingers.

lickwid said:
I have an official unlocked US model, but nothing yet. I expect to see the update by the weekend. Crossing fingers.
Click to expand...
Click to collapse
I believe unlocked models should be getting it before us on Verizon. But, there was a story out that stated OTAs for some reason have stopped being pushed out and Samsung has acknowledged this and is looking into why it happened.
http://www.droidviews.com/samsung-galaxy-s7-android-nougat-problems-firmware-delivery-stops/
Whether the "bug" is in the firmware itself or with the update process that sends out the notifications is not mentioned.

Does LOS has ARB Protection

As some of you know google has implemented Anti-RollBack protection to Oreo that was optional but I have just learned that Pie has mandatory ARB protection. I'm curious if Lineage OS has this feature implemented in any way because I have a Xiaomi device which will eventually get a MIUI 10 update with ARB Protection. I totally don't want ARB. If any of you have the answer please comment down below :fingers-crossed:

I have within the past 6 months had to go back to an earlier build for various reasons and have had no issues doing so. However, I don't actively follow Los development plans or know if at some point it will become part of the base build they get from Google, which I would hazard a guess it will. From my reading though it is possible to go back just that you end up seeing error messages which hopefully can be resolved in some way. But now that I think about it I haven't gone to an earlier build in 2 months so maybe it has changed. I'm on an op2 so I doubt pie would come around for it. Good luck in any case.
Sent from my ONE A2005 using Tapatalk

General Honor Magic4 Pro + Android 13 = Broken

Just updated my Magic4 Pro to Android 13, Magic OS 7.1, Build number: 7.1.0.136 and I cannot switch between apps; the functionality is simply broken.
I've got a video demonstrating it on Twitter...would therefore suggest not upgrading until this is (and potentially other bugs) fixed.
UPDATE:
I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.

Was it à regular updates from Honor ?

TotallydubbedHD said:
Just updated my Magic4 Pro to Android 13, Magic OS 7.1, Build number: 7.1.0.136 and I cannot switch between apps; the functionality is simply broken.
I've got a video demonstrating it on Twitter...would therefore suggest not upgrading until this is (and potentially other bugs) fixed.
Click to expand...
Click to collapse
I suggest you to perform a hard reset. I don't meet this issue. It's very strange!!!

marcox92 said:
Was it à regular updates from Honor ?
Click to expand...
Click to collapse
Yes it's a regular and official update.

Curious, didn't receive the update

nico97470 said:
I suggest you to perform a hard reset. I don't meet this issue. It's very strange!!!
Click to expand...
Click to collapse
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.

marcox92 said:
Curious, didn't receive the update
Click to expand...
Click to collapse
You should tape in the three points upper in right in the app Honor Club( system update). Trying versions.

TotallydubbedHD said:
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
Click to expand...
Click to collapse
I'm going to perform a hard reset because of draining battery and others bugs. I was before a beta tester. This update, too soon!!! Honor should have waited!!! I'm angry !

nico97470 said:
I'm going to perform a hard reset because of draining battery and others bugs. I was before a beta tester. This update, too soon!!! Honor should have waited!!! I'm angry !
Click to expand...
Click to collapse
Agreed.

Doing a reset will solve it, I have not done it and it works fine, I have been lucky.

TotallydubbedHD said:
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
Click to expand...
Click to collapse
Unfortunately you might just have to do a backup and do it when it comes to android in general not just honor platform updates tend to break things and only way to fix those bugs is to reset simple as that you can complain left and right but that's just how it is happens on ios mac os and Windows as well

wolfaas12345 said:
Unfortunately you might just have to do a backup and do it when it comes to android in general not just honor platform updates tend to break things and only way to fix those bugs is to reset simple as that you can complain left and right but that's just how it is happens on ios mac os and Windows as well
Click to expand...
Click to collapse
I used to flash ROMs and kernels weekly on my SGS1, but I can't ever recall one breaking basing navigation functionalities.
With that said, I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.

It was very relieving to find this thread and make my phone usable again. It was horrible experience trying to use the phone without an ability to switch apps.

Ja5ka said:
It was very relieving to find this thread and make my phone usable again. It was horrible experience trying to use the phone without an ability to switch apps.
Click to expand...
Click to collapse
Sorry to hear that but glad I could help!

TotallydubbedHD said:
I used to flash ROMs and kernels weekly on my SGS1, but I can't ever recall one breaking basing navigation functionalities.
With that said, I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
Click to expand...
Click to collapse
"It didn't happen before so it can't happen now" great logic also that was super long time ago lmao back in SGS1 days we only had 1 navigation type so it either fully worked or didn't there were no variables these days we have 2-3 so obvs stuff can break plus don't forget with a clean install there are 0 variables that's why bugs, if they happen, are caught by honor or whoever makes the update with apps and custom settings thrown in there's thousands of variables that can make stuff go haywire

wolfaas12345 said:
"It didn't happen before so it can't happen now" great logic also that was super long time ago lmao back in SGS1 days we only had 1 navigation type so it either fully worked or didn't there were no variables these days we have 2-3 so obvs stuff can break plus don't forget with a clean install there are 0 variables that's why bugs, if they happen, are caught by honor or whoever makes the update with apps and custom settings thrown in there's thousands of variables that can make stuff go haywire
Click to expand...
Click to collapse
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.

TotallydubbedHD said:
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
Click to expand...
Click to collapse
No its garbage logic in fact yes its been in dev for 13 years it has also been adding features for 13 years changin things for 13 years for same 13 years its also been supporting over 20k+ devices and working on them bugs are about normal with majority phones we dont see a lot cuz devs squash them before they push the update but variables that i mentioned prevent devs from covering all scenarios so shenanigans happen my problem was not with bug itself my problem is people like you talking crap because they refuse to wipe or expect flawless experience every time nothing is perfect especially software

TotallydubbedHD said:
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
Click to expand...
Click to collapse
I think you are an expert. Do you think it is possible to install Google Services Framework on Magic5pro? I have one but dunno how to do so. Thank you for your sharing.