Related
Engadget just posted a story on the two major issues of signal loss and rebooting during calls.
Maybe with this Google will start to fix the problem? I sure hope so, as both are now affecting me more than ever.
http://www.engadget.com/2011/02/15/nexus-s-suffering-from-random-data-loss-reboots/
Didn't Ry guy posted that a fix is coming and they already found the problem? Its been more than 2 weeks now..
They must also fix
1)Choppy browser with and without flash.....
2)Random freeze of the gingerbread launcher...
slateac said:
Didn't Ry guy posted that a fix is coming and they already found the problem? Its been more than 2 weeks now..
Click to expand...
Click to collapse
I think it was posted that the reboot fix was coming, but not the loss of data.
Maybe I am just a lucky one, but I have had Nexus S since release and have only had a "random reboot" once; and no data signal loss issue AFAIK like Engadget has described. I have owned three Nexus Ss.
There are other issues, though, making it clear 2.3 is not bug free.
fchipm said:
Engadget just posted a story on the two major issues of signal loss and rebooting during calls.
Maybe with this Google will start to fix the problem? I sure hope so, as both are now affecting me more than ever.
http://www.engadget.com/2011/02/15/nexus-s-suffering-from-random-data-loss-reboots/
Click to expand...
Click to collapse
and they didn't even give us XDA credits
Perhaps 2.4 is coming sooner than planned and the fixes will be implemented in that? Just a wild guess.
The article was updated. Now saying that Google fixed the issues and an OTA is coming soon.
Sent from my Nexus S using XDA App
i'm hoping they fix the quirky back button as well. that thing is driving me crazy!
I recommended the nexus s to my girlfriend, but seeing all these issues are making me regret it :\ there are no fixes/workarounds?
Sent from my SPH-D700 using XDA App
aaaaaand... 10char
Update: Huzzah! Just got a note from Google saying: "All of the issues described in the post are resolved and will be fixed with an OTA that will go out soon." Feel free to start mashing that "system updates" menu item.
Click to expand...
Click to collapse
that was fast.
Weird. I haven't had a single one of the issues described in any form. However, the browser issues do make me angry.
Glad there is a hotfix on the way (for the issues mentioned, that is, not necessarily the browser issues)!
The only issue that regularly bothers me is the vanishing ringtone one. It's not exactly critical from a utilitarian standpoint, but I think it's stupid that I should have to root and move files around my phone in order to set a custom ringtone. Still, I'm far too happy with pretty much everything else to switch.
I think one major sticking point with the Nexus S is that we have a fairly lengthy list of at least semi-common issues, but in several cases it's not clear whether those are hardware- or software-related. This is troublesome because the latter may be reasonably expected to get fixed in OTAs, while the former will probably only ever be resolved through workarounds, if at all.
I would be very pleased if Google were more transparent about what it's working on, or at least aware of, even if they (understandably) don't want to commit to fix dates. As a user, just knowing the basic nature of these problems and that they are being acknowledged would go a long way towards improving customer satisfaction in my book.
SooSpecial said:
The article was updated. Now saying that Google fixed the issues and an OTA is coming soon.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i read that there will be an ota update, but (maybe its a noob question) if your rooted will you still receive the update, and if so will it unroot the phone??
Fix the GPS!!!!!
Fix the keyboard: http://www.youtube.com/watch?v=RUZdvr6Pdjk
Discussed more in depth at this thread: http://forum.xda-developers.com/showthread.php?t=932838&page=13
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.
UPDATED:
released.
ROM thread
so, I've built a buggy cm14 that's good enough to look at and play a little with the features that do work, and watch the eye candy and all.
it has wifi and bluetooth and SMS messaging.
Otherwise broken telephony.
only some of the sound works. no camera, nfc, location.
the idea is a poll.
I figure people like to click buttons, so the poll suits that.
I'm amazed at your skills. And I have learned a lot from reading this thread. More importantly, my VM 816 is still functional.
Sent from my 710C using Tapatalk
I think you can release it whatever people use or not , but 816 is my only 4G phone.I will test it till the Calling Services worked
Ed128 said:
I'm amazed at your skills. And I have learned a lot from reading this thread. More importantly, my VM 816 is still functional.
Sent from my 710C using Tapatalk
Click to expand...
Click to collapse
A lot of what I do is googling errors, borrowing commits from other cm devices with similar chipsets, (and commenting out lines that throw errors in the build until I figure out workarounds... not the most kosher of methods.)
It's fun, but I often lean heavily on stuff that's already been done by others. Grarak put up really nice device trees to work from on this device for example, and my first tweaks at it were just after it had faded from cm nightlies. Made it comparatively easy next to my Optimus or Evo3d.
frank9184 said:
I think you can release it whatever people use or not , but 816 is my only 4G phone.I will test it till the Calling Services worked
Click to expand...
Click to collapse
Odds are the basic call services will be online way before 4G. Especially since my 4G service is still broken and has ben for quite a while. I'll hassle Virgin Mobile about a replacement sim card soon; research and talking with a Ting rep both imply that would fix my issue.
bigsupersquid said:
so, I've built a buggy cm14 that's good enough to look at and play a little with the features that do work, and watch the eye candy and all.
it has wifi and bluetooth, possibly nfc, probably no location, totally broken telephony.
only some of the sound works. no camera.
the idea is a poll.
I figure people like to click buttons, so the poll suits that.
Read this post and you see that clicking the thanks button counts more than voting...
Click to expand...
Click to collapse
I think you should upload the zip. Legacy devices are getting cm 14. Why we are late?
Tim Cook said:
I think you should upload the zip. Legacy devices are getting cm 14. Why we are late?
Click to expand...
Click to collapse
Well, htc certainly won't be releasing N for my a5_chl (Virgin Mobile variant) since they wouldn't even let M out the door for it.
you can partly name lack of manufacturer support.
And I get tired of complaints about nonworking items from people who don't read the OP, so I'm waiting for adequate interest to post it (big upload on poor isp, couple hours.)
Plus there's inability to test dug/dwg and that's twice the upload bandwidth. But few source changes to build for them, and some dual sim owners would enjoy buggy N too.
Several reasons that N isn't out in the wild yet for the a5. But I'll probably set it free to roam soon.
Question about CM14
When you let it roam, I'm ready to try it out. But I have two questions. First, I am delighted with CM13. It was the first time I ever flashed a phone and it is working nearly perfect. A hiccup or two but nothing I cannot handle. It has extended the useful life of my VM 816 A5 and saved me from buying another phone. Here's two questions for CM14 whenever it becomes available. Can I just backup my existing files with TWRP, Wipe and flash CM14? Then, the real question is if I don't like it, can I completely restore what I have now with RESTORE? The last thing I want is to ruin CM13. Thanks for helping this newby.
Ed128 said:
When you let it roam, I'm ready to try it out. But I have two questions. First, I am delighted with CM13. It was the first time I ever flashed a phone and it is working nearly perfect. A hiccup or two but nothing I cannot handle. It has extended the useful life of my VM 816 A5 and saved me from buying another phone. Here's two questions for CM14 whenever it becomes available. Can I just backup my existing files with TWRP, Wipe and flash CM14? Then, the real question is if I don't like it, can I completely restore what I have now with RESTORE? The last thing I want is to ruin CM13. Thanks for helping this newby.
Click to expand...
Click to collapse
yes, and yes. I restore cm13 over messed up cm14 regularly.
Still fighting with ril. location not working at all in spite of the switch working. and nfc probably will work once I get the firmware moved to wherever it's looking. but all the sound seems to be working now.
Ed128 said:
When you let it roam, I'm ready to try it out. But I have two questions. First, I am delighted with CM13. It was the first time I ever flashed a phone and it is working nearly perfect. A hiccup or two but nothing I cannot handle. It has extended the useful life of my VM 816 A5 and saved me from buying another phone. Here's two questions for CM14 whenever it becomes available. Can I just backup my existing files with TWRP, Wipe and flash CM14? Then, the real question is if I don't like it, can I completely restore what I have now with RESTORE? The last thing I want is to ruin CM13. Thanks for helping this newby.
Click to expand...
Click to collapse
Yes you can just Backup and Restore your previous ROM. Just be careful, wipe system and dalvik cache and cache. CM13 has some problems but mostly everything works on 816.
ajones23 said:
Yes you can just Backup and Restore your previous ROM. Just be careful, wipe system and dalvik cache and cache. CM13 has some problems but mostly everything works on 816.
Click to expand...
Click to collapse
ninja'd you this time.
I've been able to dirty flash 14 over 13, but previously installed apps get denied permissions and stuff like that.
bigsupersquid said:
ninja'd you this time.
I've been able to dirty flash 14 over 13, but previously installed apps get denied permissions and stuff like that.
Click to expand...
Click to collapse
Yup you got me, I usually don't dirty flash always clean flash. Since I use Root Essentials as partition of sdcard. When ever you get it to work,I'll be a tester. Let me know.
That's something I can deal with. Just don't want to go too far past my limited "expertise". And, not trying to hurry things. I'm a happy CM13 customer.
Sent from my 710C using Tapatalk
Ed128 said:
That's something I can deal with. Just don't want to go too far past my limited "expertise". And, not trying to hurry things. I'm a happy CM13 customer.
Click to expand...
Click to collapse
If you need help,just ask,I'm always on and off.
bigsupersquid said:
so, I've built a buggy cm14 that's good enough to look at and play a little with the features that do work, and watch the eye candy and all.
it has wifi and bluetooth, possibly nfc, probably no location, totally broken telephony.
only some of the sound works. no camera.
the idea is a poll.
I figure people like to click buttons, so the poll suits that.
Read this post and you see that clicking the thanks button counts more than voting...
Click to expand...
Click to collapse
Love your work!!!
D816w
what could be the estimated date for the first beta? hunger to flash this CM14.....
Naxym said:
what could be the estimated date for the first beta? hunger to flash this CM14.....
Click to expand...
Click to collapse
Its really not a good idea to ask for ETAs. Specially when not many things work.
Naxym said:
what could be the estimated date for the first beta? hunger to flash this CM14.....
Click to expand...
Click to collapse
ajones23 said:
Its really not a good idea to ask for ETAs. Specially when not many things work.
Click to expand...
Click to collapse
It's ok in this thread, since that's kind of what it's about.
If I can stabilize the radio glitches enough that all the telephony stops force-closing constantly I'll release an alpha, there isn't tons of interest but there seems to be enough.
After all, if I were in your shoes I'd want a release to check out.
bigsupersquid said:
It's ok in this thread, since that's kind of what it's about.
If I can stabilize the radio glitches enough that all the telephony stops force-closing constantly I'll release an alpha, there isn't tons of interest but there seems to be enough.
After all, if I were in your shoes I'd want a release to check out.
Click to expand...
Click to collapse
I sorta may get a flashing bug if you put up a alpha. I just thought I would put my 2 cents in about ETAs. Not a good thing sometimes.
ajones23 said:
I sorta may get a flashing bug if you put up a alpha. I just thought I would put my 2 cents in about ETAs. Not a good thing sometimes.
Click to expand...
Click to collapse
A lot of developers get uppity about ETAs.
I imagine with hot new devices and hundreds of posts a week it would get really old.
I usually just warn people that I have too much on my 'real-world' plate for my own taste and that my hobby work (this) ends up on the bottom of my get-er-done list.
Plus I like to put up it's-almost-ready posts and then take forever to upload:angel: and similar annoying delayed releases. Like I rebuilt for the OV a little while ago, posted about it, and never debugged or released it at all.
Bad dev :cyclops:
I put this thread out in general 816 to encourage comments and questions.
Once the alpha is out I'll open a thread in Original Dev (and post a link to it here) since cm14 is definitely original right now.
About to flash another test build!
Test has sms but no phone.
No Bluetooth.
Close to being uploadable.
assuming the next build isn't in any worse shape than this one (should have working BT, and I'm really hoping for at least 3g data and maybe phone service) then I'll try pushing the zip to AFH. If my landline internet stays connected long enough to get it upstream...
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 guys, long story short I've appropriated Axon 7 I originally got for my girl to use since she didn't quite like it, and honestly right now I need to upgrade from my unrootable slug of BB Priv.
As usual, way too many choices when it comes to roms, and the whole Oreo overhang is making it hard to try and narrow it down to just one. I haven't done anything custom for years, so is there a way to back up and restore all the apps and settings to save doing all of that between each new FW flash? That would save a ton of time and help me decide on a rom to start using daily.
That aside, should I pick from the already and well established 7.1.1 roms or try/wait for the 8's? On that note, what's with MiFavor 4.2 vs 5?
Skv012a said:
Hey guys, long story short I've appropriated Axon 7 I originally got for my girl to use since she didn't quite like it, and honestly right now I need to upgrade from my unrootable slug of BB Priv.
As usual, way too many choices when it comes to roms, and the whole Oreo overhang is making it hard to try and narrow it down to just one. I haven't done anything custom for years, so is there a way to back up and restore all the apps and settings to save doing all of that between each new FW flash? That would save a ton of time and help me decide on a rom to start using daily.
That aside, should I pick from the already and well established 7.1.1 roms or try/wait for the 8's? On that note, what's with MiFavor 4.2 vs 5?
Click to expand...
Click to collapse
Just unlock and root, all following the guides. Use TWRP 3.2.1-0.
You can dualboot ROMs as long as the primary ROM is stock MiFavor. It's a little bit more complicated with Oreo ROMs but it's doable. Otherwise just try with titanium backup maybe, people still use that thing
Skv012a said:
Hey guys, long story short I've appropriated Axon 7 I originally got for my girl to use since she didn't quite like it, and honestly right now I need to upgrade from my unrootable slug of BB Priv.
As usual, way too many choices when it comes to roms, and the whole Oreo overhang is making it hard to try and narrow it down to just one. I haven't done anything custom for years, so is there a way to back up and restore all the apps and settings to save doing all of that between each new FW flash? That would save a ton of time and help me decide on a rom to start using daily.
That aside, should I pick from the already and well established 7.1.1 roms or try/wait for the 8's? On that note, what's with MiFavor 4.2 vs 5?
Click to expand...
Click to collapse
Why not get it up to date as possible and leave it stock?
I decided to keep mine stock, still has a locked bootloader. Today I did an ADB de-bloat. Relented on my "not touching it" stance a tiny bit, lol. It is nice to have excess apps removed though. A factory reset would probably bring it all back anyway.
I started on this because I could tether data from my personal SIM but not my work SIM. ADB allowed me to fix that and then I got carried away
Will still be able to do an official Oreo update this way, if it comes.
RobboW said:
Why not get it up to date as possible and leave it stock?
I decided to keep mine stock, still has a locked bootloader. Today I did an ADB de-bloat. Relented on my "not touching it" stance a tiny bit, lol. It is nice to have excess apps removed though. A factory reset would probably bring it all back anyway.
I started on this because I could tether data from my personal SIM but not my work SIM. ADB allowed me to fix that and then I got carried away
Will still be able to do an official Oreo update this way, if it comes.
Click to expand...
Click to collapse
Seeing how ZTE is basically screwed outta US market for/now, I think betas + our devs will be the only way. I wouldn't mind 7.1.1 had it option for camera to be on lock button double-click, but alas. And de-bloat IMO is an absolute must.
Skv012a said:
Seeing how ZTE is basically screwed outta US market for/now, I think betas + our devs will be the only way. I wouldn't mind 7.1.1 had it option for camera to be on lock button double-click, but alas. And de-bloat IMO is an absolute must.
Click to expand...
Click to collapse
On MiFavor there's a much better thing imo: assign a fingerprint to the camera. Just use a finger that you won't ever confuse while unlocking it normally and you're done
Choose an username... said:
On MiFavor there's a much better thing imo: assign a fingerprint to the camera. Just use a finger that you won't ever confuse while unlocking it normally and you're done
Click to expand...
Click to collapse
So print can open camera + unlock the locker or?
In fingerprint settings you can assign different functions per print.
In fingerprint settings you can assign different functions per print and also set it to take picture. I have a finger set to turn on the torch when it's locked.
Skv012a said:
So print can open camera + unlock the locker or?
Click to expand...
Click to collapse
Yes ofc
you had no idea about that one did you
Everyone always instantly wants a custom ROM but there's nothing wrong with stock. People just don't give it a go. It is a very well equipped phone once on Nougat. Even if we don't get Oreo I will leave mine on stock ROM unless it lasts well and need to go custom to get security updates etc.
RobboW said:
Everyone always instantly wants a custom ROM but there's nothing wrong with stock. People just don't give it a go. It is a very well equipped phone once on Nougat. Even if we don't get Oreo I will leave mine on stock ROM unless it lasts well and need to go custom to get security updates etc.
Click to expand...
Click to collapse
I generally agree, but, there's no camera2, no double click for camera, and even these 2 misc features actually make or break a phone for me. If even Blackberry had the camera shortcut, with its potato of a camera otherwise, I don't see why ZTE decided to take it out entirely. Add a disclaimer and made it a toggleable option, not remove it entirely because of stupid people who put their phones into pockets with screen facing inwards.
Choose an username... said:
Yes ofc
you had no idea about that one did you
Click to expand...
Click to collapse
Well, I personally never lock my phone because it annoys the hell out of me and my phone doesn't leave my side, ever, and on top of that A7 seems to hate my prints, so this is hardly a viable option for me. And, using the print sensor as a shutter, once and only once you're in the camera is pointless for me. double power button brings up the camera on top of whatever else you have going on, lock/screen off or not, to let you take that quick snap and that's exactly what I loved in 6.0.1 and onwards.