Related
Hey all,
I'm thinking of buying a Mate 7 and switching over from my Moto X Pure. Mainly for the size, metal body, and the battery. Right now I can get it for ~$330 on Amazon. The only thing that's held me back is the software. I've read the stock software is very annoying with constant notifications about apps using up too much RAM/battery. But all these reviews were from the phone's release, I haven't been able to find much information since it's been updated to Marshmallow. I typically like very light ROMs like CM but I see there hasn't been a whole lot of development for this phone other than the KangVIP ROM which seems to have a lot of issues. So I guess my question is how do you all like the stock Marshmallow ROM and is it still good on battery life?
Also I've seen a lot of threads about how to downgrade the software to earlier versions of Android, is this just to install an earlier version of Cyanogenmod? I've not been able to find a "why" in all the threads I've seen on the subject. I've found plenty of Chinese phones that are ~6" with a big battery and metal body but LTE bands are always an issue. This is the only phone I've come across that seems to have everything, other than my concerns about the software. I'm also thinking of holding out and seeing if the Asus Zenfone 3 and the LeTV Max Pro end up having U.S. LTE bands.
Anyway, any thoughts or opinions would be greatly appreciated!
It's getting old now, still a really nice phone but I'd be looking at newer devices at this point. People regress to earlier versions of Android as the MM beta releases often dissapoint. I stuck with the latest release of Lollipop as I have some limited functionality with Xposed, got ViPER4Android working etc, it's smooth and stable. Battery is great. It's hard to describe just how much freedom that allows you compared to other devices. My Oppo Find 7 is a nice phone too, but it just doesn't last long enough and being used to the Mate 7, that annoys me greatly. I do find that the oppo at 5.5" is better to handle and fits a pocket easier. That extra half inch really is noticeable on the Mate. It is one device that does feel a little special though. Once it's optimised and personalised, it's gorgeous.
As for ROMs, not going to happen any time soon. I'm happy with stock, rooted and modded. Doesn't worry me apart from limiting lifespan, but if development did take off, I would be happy.
Huawei just don't understand the international market yet and if they did, and fostered good relations and supported development, they would be able to become #1 I think, but at this point their thinking is still very Chinese.
RobboW said:
It's getting old now, still a really nice phone but I'd be looking at newer devices at this point. People regress to earlier versions of Android as the MM beta releases often dissapoint. I stuck with the latest release of Lollipop as I have some limited functionality with Xposed, got ViPER4Android working etc, it's smooth and stable. Battery is great. It's hard to describe just how much freedom that allows you compared to other devices. My Oppo Find 7 is a nice phone too, but it just doesn't last long enough and being used to the Mate 7, that annoys me greatly. I do find that the oppo at 5.5" is better to handle and fits a pocket easier. That extra half inch really is noticeable on the Mate. It is one device that does feel a little special though. Once it's optimised and personalised, it's gorgeous.
As for ROMs, not going to happen any time soon. I'm happy with stock, rooted and modded. Doesn't worry me apart from limiting lifespan, but if development did take off, I would be happy.
Huawei just don't understand the international market yet and if they did, and fostered good relations and supported development, they would be able to become #1 I think, but at this point their thinking is still very Chinese.
Click to expand...
Click to collapse
Thanks for the quick reply RobboW! I've always had phones that had a lot of development so I've kind of taken it for granted. A couple years ago I wouldn't have even considered a phone without a lot of development but my ROM addiction has really subsided and I only recently put a custom ROM on my Moto X. Honestly I don't do much customization anymore, the thing that made me apprehensive about the Mate 7 was all the "battery saving" shenanigans. If there's some way to disable those while still keeping good battery life (which definitely should be possibly with the 4100 mAh battery) then I'll be happy with the ROM, provided there's no lag. I don't do any kind of gaming or anything, just browsing the web, videos, texts, and emails, but I can't stand any kind of lag.
Thanks again for your help, it's been a grueling process trying to find a phone that meets all my criteria for a reasonable price. The Mate 7's hardware hits it perfectly, so if I can live with the software I still think it's a good deal.
It sounds like your user case is much like mine then. The Mate 7 (get 32Gb version and insert a 128Gb uSD) should serve you well. Update it from kitkat to lollipop for UI smoothness, unlock bootloader, install TWRP recovery, root and do a little debloat, although there's really not much bloat, install Viper if sound is your thing. You will need a different launcher and icon pack to get away from Huawei launcher which is terrible.
For the notifications, it has a notification manager so you can customise that to your liking. Mine doesn't bombard me with warnings. The battery is awesome, just go to power saving settings, ignore the savings and set it to normal. It still easily goes a day with heavy use.
My son liked mine and wanted to update his galaxy S4 so got a Mate 7 32Gb and I did all these things to his. He has wifi and BT on all day, facebook messenger always on etc and it never has a battery problem. He is still gobsmacked by it. Says it's better in every way to the S4 other than maybe the lack of ir blaster (which he doesn't care about) and amoled screen in the S4 but the Mate 7 screen is really nice anyway. I actually like the IPS panel better than amoled as I think amoled is gharish, too colourful, just not realistic and the IPS seems much nicer, more realistic for photos and video. It's actually a warmish tint, unlike my oppo which has a very stark, cold tint and is harder on my eyes.
You can adjust the screen and I set it to it's coldest but it's still warmer than the oppo.
I've been toying with the idea to go back to using the Mate 7 as my daily phone instead of the oppo. I was going to use the Mate 7 as a tool, like a small tablet because it will be the database and interface (BT) between an electrical test tag machine and a label printer. The camera is really good at macro focus and reads barcodes very well.
I didn't want to talk it up to someone expecting a 6P and lot's of custom roms, but for the price they can be bought for now, and your user case, it will make a great daily driver. Just be very sure it works on the correct bands you need there in the US. It works great here in Australia.
Edit: I'm having an issue with my Oppo where sometimes I can't view an email when others work ok. The Mate 7 doesn't have the issue and I've been going through settings looking for differences as the two phones are set up almost the same. Cannot find the problem so I have my SIM in the Mate again (Titanium Backup is so handy for transfering sms and call data) and will try to get a custom ROM in the Oppo.
The Mate works great. No desire for a ROM in that unless I update to MM when/if I can get a stable final release that is originally OTA.
Well I went ahead and bit the bullet and I'm going for it. I'll probably need to be pointed in the right direction once it arrives as far as which ROM to install and how I go about downgrading it if I need to. Thanks again for your help! I'm excited to check it out.
@RobboW has said pretty much all there is that's worth mentioning about the device. If you're after stellar battery life and a solid daily driver you can't go wrong, but don't expect the flexibility of devices that are more open to customization.
I've updated to the official MM release and have yet to encounter any of the issues people complained about in the beta releases. While the LP release is fantastic (and Viper actually works on it, which I miss), the MM build offers even better responsiveness and an overall better-rounded software experience, although that's not saying I wouldn't flash something entirely different in a heartbeat (if only I could....).
The camera is also not very great. On paper it's decent, but photos almost always come out blurry (as there's no OIS) and washed out. A but of tinkering on Snapseed can make a big difference though, but don't expect anything too great.
If you already bought it I'd suggest that you immediately install a 3rd party launcher of your choice to avoid the stock launcher (which really is horrendous), and then root if that's your sort of thing.
Enjoy!
Scruffykid said:
The camera is also not very great. On paper it's decent, but photos almost always come out blurry (as there's no OIS) and washed out. A but of tinkering on Snapseed can make a big difference though, but don't expect anything too great.
Enjoy!
Click to expand...
Click to collapse
Scruffy, set the saturation in the camera app settings a notch higher. You can also set the brightness down a little if needed. I actually find the camera pretty good. It's not a flagship camera but it's also not a cheap one.
I've got my SIM back in my Oppo today, got OmniROM set up pretty nice now. So much better than ColorOS from Oppo. The B331 LP Mate 7 ROM is quite nice for a stock ROM IMO and I'm still happy to keep it. If the Oppo is stable on OmniROM, maybe I'll look at updating the Mate 7 to MM, but not if I can't have Xposed and ViPER4Android......
I'm on Marshmallow on the Oppo now and it's a PIA with some things. File explorers have issues with access, notifications are more intrusive, but it is a nice OS other than that. I actually found Lollipop easier to use.
---------- Post added at 10:54 AM ---------- Previous post was at 10:47 AM ----------
Prozart said:
Well I went ahead and bit the bullet and I'm going for it. I'll probably need to be pointed in the right direction once it arrives as far as which ROM to install and how I go about downgrading it if I need to. Thanks again for your help! I'm excited to check it out.
Click to expand...
Click to collapse
It will ship with Kitkat so you boot and see which firmware version it's on and what OTA update it wants to install when it goes online, but don't install it straight away, come back to the forum with the information and then the correct update tree can be looked at.
Don't leave it on Kitkat, IMO, you either use B331 Lollipop or a Marshmallow ROM. Nothing earlier. Some of the MM ROMS do need an earlier Lollipop version to update from, but sometimes you can flash the ROM anyway, as long as the phone is compatible with it.
RobboW said:
Scruffy, set the saturation in the camera app settings a notch higher. You can also set the brightness down a little if needed. I actually find the camera pretty good. It's not a flagship camera but it's also not a cheap one.
Click to expand...
Click to collapse
I can't seem to find the settings you're mentioning in my camera settings. Perhaps it was removed on the MM builds? Anyway I think simply installing 3rd party camera software should make a big difference. As you and I both said, most of what's wrong with the camera is software.
Haven't tried MM on my Mate 7 so couldn't speculate, but from Google Play, give Open Camera a try, it's free. See if pics match the viewing angle you expected.
For a paid app, Camera FV-5 is very good. It's supposed to mimmick a DSLR.
Edit:
Just installed Open Camera (by Mark Harmon) on both phones. Works well. Two things I like are the availability of grid lines and a level indicator. Makes quite a difference when doing landscape photography. I live in a seaside town and getting horizon level is so important with shots including ocean. If it had panorama mode I'd be a happy chappy!
I haven't been bothered with camera apps on my Mate 7 as it has a good camera on KK and LP and I had no need to look for better. The Oppo Find 7 is another matter. Oppo camera was good with ColorOS, but now on OmniROM, I needed to look at camera apps, but had already found the others with my previous phone as it was a THL W200 and stock software was pretty crap.
RobboW said:
It will ship with Kitkat so you boot and see which firmware version it's on and what OTA update it wants to install when it goes online, but don't install it straight away, come back to the forum with the information and then the correct update tree can be looked at.
Don't leave it on Kitkat, IMO, you either use B331 Lollipop or a Marshmallow ROM. Nothing earlier. Some of the MM ROMS do need an earlier Lollipop version to update from, but sometimes you can flash the ROM anyway, as long as the phone is compatible with it.
Click to expand...
Click to collapse
Alright so it arrived today with KK 4.4.2 build number 120SP04. I went to the updater and it said no updates are available. I don't have a SIM card in it so I don't know if that makes a difference. I didn't realize it didn't have a nano sim slot so I'll have to go to my carrier to get a micro. In the mean time, what are my upgrade paths to a good Lollipop or Marshmallow? I'm in North America and on the main page I only saw update packages for India, Europe, and China I believe. Would I just go with the European ones?
Prozart said:
Alright so it arrived today with KK 4.4.2 build number 120SP04. I went to the updater and it said no updates are available. I don't have a SIM card in it so I don't know if that makes a difference. I didn't realize it didn't have a nano sim slot so I'll have to go to my carrier to get a micro. In the mean time, what are my upgrade paths to a good Lollipop or Marshmallow? I'm in North America and on the main page I only saw update packages for India, Europe, and China I believe. Would I just go with the European ones?
Click to expand...
Click to collapse
Will you be using an SD card? Slot 2 takes either an SD or a nano SIM, not both at once though.
That's the same ROM my phone came on. It's the standard international ROM for a non carrier locked TL10 goldie.
It will update to B130 OTA
From B130 I flashed mine to B331 Lollipop (newest lollipop). Just a download of ROM and place in dload folder and point the updater to it, then it does it from within the OS. It won't go past B130 on an OTA.
If you want MM, that needs to be loked at as there are stacks of vesions. I'm inclined to think if it can be flashed up to MM from B331 it's reasonably new. That's my aim. I won't go to an older LP to get up to a buggy old beta MM.
Here's the download link where I got my stable Lollipop.
http://www.carbontesla.com/2016/01/download-ascend-mate-7-full-b331-lollipop-firmware-europe/
It seems to me that Huawei are still slowly releasing updates so I would rather sit on a stable LP and wait for the last MM rather than join the unhappy bunch of early flashers who have bugs or bricks.
B331 LP works well and can get some limited use of Xposed and full use of Viper4android.
You need to keep stock recovery to flash an update but unlocked bootloader is fine, so I'd look to unlock the bootloader after it gets B130 update.
It will have a choppy UI on KitKat, it's normal. Lollipop fixes that.
I reckon you'll last maybe 5 minutes trying to use the Huawei launcher. Don't fight that, just install another, lol. Have to go into settings and choose default launcher in the app management section.
RobboW said:
Will you be using an SD card? Slot 2 takes either an SD or a nano SIM, not both at once though.
That's the same ROM my phone came on. It's the standard international ROM for a non carrier locked TL10 goldie.
It will update to B130 OTA
From B130 I flashed mine to B331 Lollipop (newest lollipop). Just a download of ROM and place in dload folder and point the updater to it, then it does it from within the OS. It won't go past B130 on an OTA.
If you want MM, that needs to be loked at as there are stacks of vesions. I'm inclined to think if it can be flashed up to MM from B331 it's reasonably new. That's my aim. I won't go to an older LP to get up to a buggy old beta MM.
Here's the download link where I got my stable Lollipop.
http://www.carbontesla.com/2016/01/download-ascend-mate-7-full-b331-lollipop-firmware-europe/
It seems to me that Huawei are still slowly releasing updates so I would rather sit on a stable LP and wait for the last MM rather than join the unhappy bunch of early flashers who have bugs or bricks.
B331 LP works well and can get some limited use of Xposed and full use of Viper4android.
You need to keep stock recovery to flash an update but unlocked bootloader is fine, so I'd look to unlock the bootloader after it gets B130 update.
It will have a choppy UI on KitKat, it's normal. Lollipop fixes that.
I reckon you'll last maybe 5 minutes trying to use the Huawei launcher. Don't fight that, just install another, lol. Have to go into settings and choose default launcher in the app management section.
Click to expand...
Click to collapse
Awesome, thanks for your help! Since its saying "no updates available" should I manually update it to B130 and then to the link you provided for B331?
And yeah I've already got a launcher I've been using and like, I'm already sick of the stock launcher, lol. Also, strangely, the play store force closes after a few seconds of opening. I'm not too worried about it as I'll very soon be flashing different firmware, but still strange. Also, this is the MT7 L09 version, should I still update B130>B331?
And as far as Marshmallow is concerned I'm inclined to take your path with a stable Lollipop until they get MM all worked out.
Prozart said:
Awesome, thanks for your help! Since its saying "no updates available" should I manually update it to B130 and then to the link you provided for B331?
And yeah I've already got a launcher I've been using and like, I'm already sick of the stock launcher, lol. Also, strangely, the play store force closes after a few seconds of opening. I'm not too worried about it as I'll very soon be flashing different firmware, but still strange. Also, this is the MT7 L09 version, should I still update B130>B331?
And as far as Marshmallow is concerned I'm inclined to take your path with a stable Lollipop until they get MM all worked out.
Click to expand...
Click to collapse
L09, well that changes everything. You can go to B522 MM on that already. Update to B331, see how you like it. You can update to B522 from there anyway.
Google Play FC will be it trying to update itself whilst you're using it.
Check your ROM matches the number of the update. There are update notes included with it. If it doesn't match, it will fail to flash once most of the way through it. This is the CUST folder and is ROM specific for different areas of the world. It's where most naive users brick their phone.
For instance, mine is C900B331 and the original would have been C900B120SP04
That C900 is most important.
What many don't realise is that the number of the ROM doesn't always mean newer. It could be for a different region and that region has a different sequence of ROM designations.
RobboW said:
L09, well that changes everything. You can go to B522 MM on that already. Update to B331, see how you like it. You can update to B522 from there anyway.
Google Play FC will be it trying to update itself whilst you're using it.
Check your ROM matches the number of the update. There are update notes included with it. If it doesn't match, it will fail to flash once most of the way through it. This is the CUST folder and is ROM specific for different areas of the world. It's where most naive users brick their phone.
For instance, mine is C900B331 and the original would have been C900B120SP04
That C900 is most important.
What many don't realise is that the number of the ROM doesn't always mean newer. It could be for a different region and that region has a different sequence of ROM designations.
Click to expand...
Click to collapse
Thanks to you I successfully updated to B331. I got my launcher installed and now I just need to change the DPI as everything is huge, lol. So now I need to unlock bootloader and root it. But so far everything is smooth, no problems yet.
Edit: Quick question. I went into the APN settings and accidentally clicked on preferred network type. Before I went in there it was set to LTE (and I was successfully connected to LTE) but that wasn't an option to click on when I went into the settings. It's only showing me these three and so I'm not getting LTE anymore. Any ideas?
Check dual card settings for default 4G slot.
Edit: Why am I suggesting that for an L09, lol.
Have you done anything to upset the settings for APN?
Have a look in power saving settings to see if anything there cuts it back to 3G to save juice.
4G really sucks battery compared to 3G.
RobboW said:
Check dual card settings for default 4G slot.
Edit: Why am I suggesting that for an L09, lol.
Have you done anything to upset the settings for APN?
Have a look in power saving settings to see if anything there cuts it back to 3G to save juice.
4G really sucks battery compared to 3G.
Click to expand...
Click to collapse
I can't find anything i n the power settings regarding network modes, I believe the only thing I've changed is putting the power plan on Normal and turning off Power-intensive prompt.
Also on the keyboard, the keys aren't vibrating. I went into the keyboard settings and made sure it was turned on. Also tried toggling it off and on with no success. Are there any other vibration settings hidden somewhere that I'm missing?
I wonder if a factory reset is in order. Just to count out any leftovers. I do wonder though, if there is something funny about the bands the carriers allow to work in the US. I often see comments from US XDA members about bands. Like the US is really different than the rest of the world or something.
RobboW said:
I wonder if a factory reset is in order. Just to count out any leftovers. I do wonder though, if there is something funny about the bands the carriers allow to work in the US. I often see comments from US XDA members about bands. Like the US is really different than the rest of the world or something.
Click to expand...
Click to collapse
Yeah I may try that when I get home tonight. I need to unlock bootloader and root anyway so that'll wipe it. It's just so weird cause I had LTE up until the point when I went into settings and clicked on WDCMA or whatever and now there's no option to get back to LTE. It's also not connecting via bluetooth to my car. It had no problems connecting to my Moto 360, I don't know what would be different about my car. But it's not detecting it at all. Perhaps a factory reset would help solve that.
I spent about an hour last night reading up on unlocking the bootloader. I tried emailing Huawei and they directed me to log in to my Huawei account and I'd be able to get the code after 14 days. Is there any other way to do this? I mean I can survive a couple weeks without root, but it's not optimal, lol.
Don't root it yet and don't flash recovery.
Unlock the bootloader first. Read the following thread where I show the trick for getting your code easy and free.
http://forum.xda-developers.com/mate-7/general/bootloader-unlock-longer-anymore-t3296725
I've put mine back to stock B331 as much as possible tonight and flashed stock recovery then dirty flashed B331 back over it. About to factory reset it then attempt flashing Marshmallow.
Edit:
Reset went ok.
Edit:
Started the update, got to 96% and failed (CUST FAIL) and rebooted, sat on the start screen for quite a while and then booted. It's on C900B522 Marshmallow but I'm not sure what impact the cust fail has, but it seems to run fine. The dual card management settings are there so it is running as the TL10 that it is, although in settings it's calling itself a JAZZ.
RobboW said:
Don't root it yet and don't flash recovery.
Unlock the bootloader first. Read the following thread where I show the trick for getting your code easy and free.
http://forum.xda-developers.com/mate-7/general/bootloader-unlock-longer-anymore-t3296725
I've put mine back to stock B331 as much as possible tonight and flashed stock recovery then dirty flashed B331 back over it. About to factory reset it then attempt flashing Marshmallow.
Edit:
Reset went ok.
Edit:
Started the update, got to 96% and failed (CUST FAIL) and rebooted, sat on the start screen for quite a while and then booted. It's on C900B522 Marshmallow but I'm not sure what impact the cust fail has, but it seems to run fine. The dual card management settings are there so it is running as the TL10 that it is, although in settings it's calling itself a JAZZ.
Click to expand...
Click to collapse
I upgraded to 522 and so far it seems to be working well. Having some problems with Google Play Services (says it needs to update but the option isn't available in the play store) but otherwise seems great. Got LTE back and I've connected via Bluetooth to my car. I'm thinking about upgrading to 560 tonight. So I'm trying to follow your instructions on unlocking the bootloader but I don't understand where I need to go to type in the IMEI. I went to the website and logged in but then it takes me to this page (which doesn't seem to have an English version) and I have no idea where to go from there.
Am I missing a post? All I can find is the posts for the 930F/FD.
I'm trying to get a handle on this whole 60% battery issue before it gets pushed to me. I know about the app that disables it for you, but honestly I'd rather have Root for ultimate say.
If there's not a ROM for the Sprint version, why not? (other than no one has made one)
I'm sorry if this has been covered in an older post.
Raccoonbuddy85 said:
Am I missing a post? All I can find is the posts for the 930F/FD.
I'm trying to get a handle on this whole 60% battery issue before it gets pushed to me. I know about the app that disables it for you, but honestly I'd rather have Root for ultimate say.
If there's not a ROM for the Sprint version, why not? (other than no one has made one)
I'm sorry if this has been covered in an older post.
Click to expand...
Click to collapse
(THIS IS NOT MINE BUT FROM ANOTHER MEMBER)
Yeah. I have a fix. Download this .tar and put each part in the right box. Turn on OEM unlock and Debugging and flash with the latest version of Odin3_v3.12.4_4 . My phone now charges to 100% and the stupid recall nag screen is gone. The phone is 100% stock and unrooted still. You're welcome. Don't forget to hit that thanks button.
https://www.androidfilehost.com/?fid=457095661767101384
patrick_1 said:
(THIS IS NOT MINE BUT FROM ANOTHER MEMBER)
Yeah. I have a fix. Download this .tar and put each part in the right box. Turn on OEM unlock and Debugging and flash with the latest version of Odin3_v3.12.4_4 . My phone now charges to 100% and the stupid recall nag screen is gone. The phone is 100% stock and unrooted still. You're welcome. Don't forget to hit that thanks button.
https://www.androidfilehost.com/?fid=457095661767101384
Click to expand...
Click to collapse
I am going to give this a shot, does it get rid of all the warnings too, I just hope I can get back to 100% battery. Does this wipe my data or does it save it? Thanks
Sniper_Ghost said:
I am going to give this a shot, does it get rid of all the warnings too, I just hope I can get back to 100% battery. Does this wipe my data or does it save it? Thanks
Click to expand...
Click to collapse
According to the OP this wipes data.
let the world know if it works please. Don't want to lose my Sammy pay unless it's a somewhat permanent fix
thelungmeister said:
let the world know if it works please. Don't want to lose my Sammy pay unless it's a somewhat permanent fix
Click to expand...
Click to collapse
I will post if it works or not, I wish there was a way to revert to the factory firmware and not wipe the data. So I assume a simple restore really does not restore it to factory another words the updates are still there not the firmware it shipped with? I have to back up my phone and then I am going to give it a shot, if I get a fail message I hope someone here can help me figure out why and how to fix it.
Sniper_Ghost said:
I will post if it works or not, I wish there was a way to revert to the factory firmware and not wipe the data. So I assume a simple restore really does not restore it to factory another words the updates are still there not the firmware it shipped with? I have to back up my phone and then I am going to give it a shot, if I get a fail message I hope someone here can help me figure out why and how to fix it.
Click to expand...
Click to collapse
My guess is the updates applied will stick. The method I mentioned previously works, I know it's a headache to restore data but it's worth it in the end.
Sorry guys, I've flashed this three times and the Samsung patch still over rides and in installs the 60% limit. Only solution is to root and I've not found anything that works yet.
Sent from my SM-P607T using Tapatalk
Bad news
Well we better get a custom rom quick because Samsung told me today that they will release an update that prevents the phones from being turned on as well as carriers are going to block note 7s from connecting to their network. We have to make our voices heard becaise today its the note 7, tomorrow who knows, I will never buy samsung again after being treated this way.
PS Disable samsung cloud because they are using it to drain your battery...
Admon420 said:
Well we better get a custom rom quick because Samsung told me today that they will release an update that prevents the phones from being turned on as well as carriers are going to block note 7s from connecting to their network. We have to make our voices heard becaise today its the note 7, tomorrow who knows, I will never buy samsung again after being treated this way.
PS Disable samsung cloud because they are using it to drain your battery...
Click to expand...
Click to collapse
How dare they try so hard to prevent death/injury to you and your loved ones and damage to your property...
It's not like any of that would tarnish their image, right? Wait...
Yeah any lithium ion battery has the possibility to blow up, i dont care that you are a senior member, if you don't have anything useful to add the post, then get out...
We are looking for solutions so get off the soapbox, my Note 7 is at just as much risk as your phone.
To the OP, we really need a custom rom and root quick cuz it wont be long until we are blocked from the networks.
Admon420 said:
Yeah any lithium ion battery has the possibility to blow up, i dont care that you are a senior member, if you don't have anything useful to add the post, then get out...
We are looking for solutions so get off the soapbox, my Note 7 is at just as much risk as your phone.
To the OP, we really need a custom rom and root quick cuz it wont be long until we are blocked from the networks.
Click to expand...
Click to collapse
True that, however we will be powerless against the IMEI block, that's a cell tower thing, something we don't have control over.
I was successful in reverting to a previous update before the 60% one. I also found a previous version of the package blocker described in some of the posts I've read. All of which you can find via Google (Android central) or XDA.
Phone automatically tried updating, so I skipped ahead as fast as possible to turn on airplane mode. I then installed the already downloaded disabler, disabled the recommended packages and turned on the radio again.
(Note: Ensure that you de-encrypt your files before starting the process, I forgot to and lost some files.)
jag5001 said:
Sorry guys, I've flashed this three times and the Samsung patch still over rides and in installs the 60% limit. Only solution is to root and I've not found anything that works yet.
Sent from my SM-P607T using Tapatalk
Click to expand...
Click to collapse
Can someone point me to the easiest free way to Root the Note 7, its a Sprint Note 7 so I can get rid of the 60% thing. Does Root allow you to stop the 60% battery limit? Does it allow you to stop all the dang warnings? I would appreciate it. I keep getting different threads about how to Root the Sprint Note 7 so if someone can post a link to the best thread on how to do this the easiest without messing it up. I really appreciate it, thank you in advance.
Rick
Sniper_Ghost said:
Can someone point me to the easiest free way to Root the Note 7, its a Sprint Note 7 so I can get rid of the 60% thing. Does Root allow you to stop the 60% battery limit? Does it allow you to stop all the dang warnings? I would appreciate it. I keep getting different threads about how to Root the Sprint Note 7 so if someone can post a link to the best thread on how to do this the easiest without messing it up. I really appreciate it, thank you in advance.
Rick
Click to expand...
Click to collapse
Unfortunately, there isn't a root option for us 930P users. There was something that we *could* have used, however that got patched a couple updates ago and we can't go any further back than the one that patched it (to my understanding).
If we have root access and the XPOSED module, then there certainly will be something we can do about it if you do a quick search in the play store... of course like the package disabler, Samsung will come hard at those apps too... Im lucky enough to not ever had to deal with the 60 percent update, hopefully I'm lucky enough that someone will release a rooted PHE or unlock key for the bootloader.
How was it you were able to get the nag gone? soon as i finished flashing it shows the nag; and the battery update notice, which I don't know which service to disable using a different disabler when i click on debloat, it doesn't block update, unlike disabler pro :\
android386 said:
How was it you were able to get the nag gone? soon as i finished flashing it shows the nag; and the battery update notice, which I don't know which service to disable using a different disabler when i click on debloat, it doesn't block update, unlike disabler pro :\
Click to expand...
Click to collapse
These are a few of the ones that I disabled...
Raccoonbuddy85 said:
android386 said:
How was it you were able to get the nag gone? soon as i finished flashing it shows the nag; and the battery update notice, which I don't know which service to disable using a different disabler when i click on debloat, it doesn't block update, unlike disabler pro :
Click to expand...
Click to collapse
These are a few of the ones that I disabled...
Click to expand...
Click to collapse
You won't be able to get 100% of the nag screen gone, but I was able to get it down to just the little one when charging.
Raccoonbuddy85 said:
You won't be able to get 100% of the nag screen gone, but I was able to get it down to just the little one when charging.
Click to expand...
Click to collapse
I have no nag at all just under settings the number 1 and when i click on it it says system update available...100% green battery....no annoyance even when charging ..i downgraded and stopped 3 things only
Hi,
I'm thinking about buying this phone at this moment (Black Friday). My question is : is it worth buying considering this model has been received 2 major updates? I think Samsung update policy is to release only 2 big updates for their models. This model was launched with Nougat, now is running with Oreo and, presumably, will end with Pie. Is this correct?
Thanks
Wrong one major update 7.1 to 8.0 I believe it will get 9.0 but not sure.
Personal I pass on the ab but I got the ab+ version.
It been a very good phone.
mchlbenner said:
Wrong one major update 7.1 to 8.0 I believe it will get 9.0 but not sure.
Personal I pass on the ab but I got the ab+ version.
It been a very good phone.
Click to expand...
Click to collapse
According to many websites, it's very very likely this phone will have Pie. But the question is if that version will be the last one (not eligible for Android Q). It's well-known that Samsung do not care mid/low range models regarding upgrades (other than security patches).
Another question: does this phone still have the annoying FRP Lock protection? I would like to root the phone, but this protection is a pain in the ass. My old Galaxy Grand prime still has it.
Thanks again
If you want to root it you will lose the warranty... but then you can install a costume rom P,Q,etc...
Robert978 said:
If you want to root it you will lose the warranty... but then you can install a costume rom P,Q,etc...
Click to expand...
Click to collapse
I think if I flash the stock ROM with Odin I will recover the warranty, right? I have already rooted my old Galaxy. The problem is the root access when the FRP Lock protection is still present.
When you root the phone, if you have configured any Google account (needed for Play Store), the phone does not boot when is rebooted (the bootloader detects an 'unofficial' firmware installed). In order to bypass it (and reboot your phone when is needed), you need to remove all your Google accounts first and therefore this is a PITA. So my question (to rooted users) is if this protection is still present, and if so, if there is a way to get rid of it.
Thanks.
Robert978 said:
If you want to root it you will lose the warranty... but then you can install a costume rom P,Q,etc...
Click to expand...
Click to collapse
Hi,
I'm reading about rooting in this forum and I have realized that this model is not easy to root, specially if you already are in Oreo (very likely if I buy now the phone). I have found several threads about this question but it's not clear what is the 'best guide'. Also I have found the following tutorial HERE.
Can you elaborate a bit?
Thanks
Boblo said:
Hi,
I'm reading about rooting in this forum and I have realized that this model is not easy to root, specially if you already are in Oreo (very likely if I buy now the phone). I have found several threads about this question but it's not clear what is the 'best guide'. Also I have found the following tutorial HERE.
Can you elaborate a bit?
Thanks
Click to expand...
Click to collapse
There's already a pretty good guide here on how to install a custom recovery and root this phone made by @corsicanu. I followed it just about a week ago when my phone was 5 days old and I had no problem whatsoever. I had OREO 8.0 and I was super scared about my phone being locked since I had never listened to that before. This phone is really worth it. Size, display and performance is 10/10 for me. On the contrary, the main camera is below average. I have yet to found a good version of the gcam since all I have tried are not working properly. My last device was a Xiaomi MI A2, but it only lasted two weeks. The reasons to replace the MI A2 are bad display outdoors, too big of a phone, super bad adio quality (headphone wise) plus no headphone jack, low lasting battery and no NFC. I swear to you there are very low options that are as packed as this galaxy a8 2018. It cost me 290€ on a retail store so I'm super happy.
catalem said:
There's already a pretty good guide here on how to install a custom recovery and root this phone made by @corsicanu. I followed it just about a week ago when my phone was 5 days old and I had no problem whatsoever. I had OREO 8.0 and I was super scared about my phone being locked since I had never listened to that before. This phone is really worth it. Size, display and performance is 10/10 for me. On the contrary, the main camera is below average. I have yet to found a good version of the gcam since all I have tried are not working properly. My last device was a Xiaomi MI A2, but it only lasted two weeks. The reasons to replace the MI A2 are bad display outdoors, too big of a phone, super bad adio quality (headphone wise) plus no headphone jack, low lasting battery and no NFC. I swear to you there are very low options that are as packed as this galaxy a8 2018. It cost me 290€ on a retail store so I'm super happy.
Click to expand...
Click to collapse
Thanks. Is THIS GUIDE? And is your system stable with no important bugs?
Other than that... unlike older Galaxy models I cannot recover my warranty when the device is rooted, right? I have read that the warranty bit is changed, the bootloader detects an 'unofficial' firmware and there is no way to avoid this.
Regards
Boblo said:
Thanks. Is THIS GUIDE? And is your system stable with no important bugs?
Other than that... unlike older Galaxy models I cannot recover my warranty when the device is rooted, right? I have read that the warranty bit is changed, the bootloader detects an 'unofficial' firmware and there is no way to avoid this.
Regards
Click to expand...
Click to collapse
It is indeed. Flashing and rooting your device does not make it less stable. My galaxy a8 is working like a charm. I don't have my phone rooted but I have had it and the only problem for me is I have always a notificacion shown saying device is in danger, you must restart. Unlike some other devices, samsung smartphones are not able to be reverted. Once you trip knox, there's no going back. Even if you flash back an original ROM with ODIN, the phone will still known its been modified.
catalem said:
It is indeed. Flashing and rooting your device does not make it less stable. My galaxy a8 is working like a charm. I don't have my phone rooted but I have had it and the only problem for me is I have always a notificacion shown saying device is in danger, you must restart. Unlike some other devices, samsung smartphones are not able to be reverted. Once you trip knox, there's no going back. Even if you flash back an original ROM with ODIN, the phone will still known its been modified.
Click to expand...
Click to collapse
Thanks again. Where did you see that warning? Is it annoying? Can you hide it?
And a last question: I suppose you know the FRP Lock protection. With this guide, is the FRP Lock protection gone forever?
On a side note, I still have my old Galaxy Grand Prime (2015 model) rooted, with TWRP 3 installed and the Knox counter has the value 0x0 (not tripped). So it seems new models like the A8 have a reinforced protection against hacking...
I want to open this thread about Nokia 7 Plus TA-1055 single sim (for those have this model variant like me), to discuss about it and about problems with custom boot/system/anything else flashing/installation, which works on another model variant (TA-1046 and TA-1062) instead.
Pie gsi gives "no SIM" bug on single sim variant of the the TA-1055
- Oreo GSI (I tried them personally) have a weird call bug. It's very impossible to call someone!!
- Custom kernel have some problems with TA-1055 model, instead of other variants
I'm running pixel experience gsi on my ta-1055. No Sim bug is fixed by popping the Sim out and back in. Super stable build. Way better battery life and so much faster. After every reboot/update you must pop the Sim out and back in and it works. I think it has to do with the fact that it's looking for sim2 first and can't find it because it doesn't exist.
Micahvdm said:
I'm running pixel experience gsi on my ta-1055. No Sim bug is fixed by popping the Sim out and back in. Super stable build. Way better battery life and so much faster. After every reboot/update you must pop the Sim out and back in and it works. I think it has to do with the fact that it's looking for sim2 first and can't find it because it doesn't exist.
Click to expand...
Click to collapse
It's works, thx
I have TA-1055 too. Does anybody received the february patch? I tried to install with my sd card the recovery always says that: expected 00WW_3_22C (SP04)
What is that mean?
terjekd said:
I have TA-1055 too. Does anybody received the february patch? I tried to install with my sd card the recovery always says that: expected 00WW_3_22C (SP04)
What is that mean?
Click to expand...
Click to collapse
Maybe because ta1055 is on version 3.39
Rubens95 said:
Maybe because ta1055 is on version 3.39
Click to expand...
Click to collapse
What is that mean?
terjekd said:
What is that mean?
Click to expand...
Click to collapse
in November Nokia7Plus have official 2 OTA branch, one in line 3.22* which is only with security patches and second line 3.39* which also have some apps updates...
then if for you sideload say "expected 00WW_3_22C (SP04" then you can try OTA 3.22* on instaled higher branch 3.39*...
now you can check what exact version you have installed (in Settings/System/AboutPhone is two version show, one in BuildNumber (me PieFeb is 00WW_3_39B_SP03) and one in AndroidVersion/BuildNumber (me show [email protected]@_3_39H)), and download right OTA files from 3.39YOURVERSION to 3.39NextVersion (and repeat until you finish on Februrary) here: https://forum.xda-developers.com/nokia-7-plus/development/ota-nokia-7-plus-ota-links-t3818774
(WARNING ignore 3.51X this is unofficial)
k3dar7 said:
in November Nokia7Plus have official 2 OTA branch, one in line 3.22* which is only with security patches and second line 3.39* which also have some apps updates...
then if for you sideload say "expected 00WW_3_22C (SP04" then you can try OTA 3.22* on instaled higher branch 3.39*...
now you can check what exact version you have installed (in Settings/System/AboutPhone is two version show, one in BuildNumber (me PieFeb is 00WW_3_39B_SP03) and one in AndroidVersion/BuildNumber (me show [email protected]@_3_39H)), and download right OTA files from 3.39YOURVERSION to 3.39NextVersion (and repeat until you finish on Februrary) here: https://forum.xda-developers.com/nokia-7-plus/development/ota-nokia-7-plus-ota-links-t3818774
(WARNING ignore 3.51X this is unofficial)
Click to expand...
Click to collapse
Thank you very much for your help!!
*disclaimer: Thanks for the help, but unfortunately nothing worked in the end,
Interesting. But I don't understand how this whole thing could even work. I am on 3.22H january security level. For starters, I can't install anything older than January updates. Also, 3.39 february update is out of the question again, as it's for 3.39, doesn't work with 3.22.
And the phone won't let me sideload anything older, saying "expected version: ...3.22H".
That's it, can't install older updates, can't roll back to oreo either. End of the line. Volume up, power button, then power button and volume up, apply update, connect usb, type in this type in that, check logs, switch fastboot slots, still wrong timestamp. It's 2 AM, wasted 2 hours of my life with "tutorials", combing through endless list of unorganized update files. This is my first android phone, and this is exactly what I expected unfortunately. 3.22H it is then. Wish windows phone was still a thing, I miss my Lumia so much.
Is timely updates too much to ask? Do I have to debug and flash my phone myself? Getting real tired of BS like this
sheppards1984 said:
It's 2 AM, wasted 2 hours of my life with "tutorials", combing through endless list of unorganized update files. This is my first android phone, and this is exactly what I expected unfortunately. 3.22H it is then. Wish windows phone was still a thing, I miss my Lumia so much.
Is timely updates too much to ask? Do I have to debug and flash my phone myself? Getting real tired of BS like this
Click to expand...
Click to collapse
Well, actually no one is forcing you to do updates on your own, so stop blaming anybody except yourself for wasting time. I'm not satisfied with the quality of updates too, but complaining so hard on XDA has no effect since HMD is not reading even their our forum for this phone.
I'm atm stuck at January patch 3.22, but do I care? No. Why? Security updates are something that keeps me calm not getting since they are almost useless. And as people report 3.39 nor 3.51 don't have any significant fixes which would really drive me crazy not having (maybe except for nav and notification bar coloring fix). I already perceived that HMD is a pile of crap and I don't expect them to do anything.
Once its get really bad with the stock rom experience I'll unlock the bootloader and flash some custom rom (i.e Pixel Experience), as they are getting better over time.
Sure, I'm not blaming anyone but myself, in fact I thank everybody for their effort...
But still I, bought this phone to just use it, not waste time and effort making it up to date, as they've advertised, then what? They split update paths... Anyway, I gave it a shot, I failed, moving on
I have an att variant that is unlocked. I've been using it with straight talk and would like to flash it to an "unlocked" variant instead of att. I don't want to root it. I have rooted previous galaxy phones but not ones that I don't want to trip knox so I can keep using samsung pay and stuff.
My main reason for doing this is after updating to one ui 4.1 it messed with my device and I'm unhappy with the results. Such as no data icon most times, but data still works. I can't get internet on devices with hotspot, which I could before the update no problem. I had to use a different APN to get data working again after the update as well, which I'm guessing is a major issue with the hotspot.
Any help would be much appreciated. Thank You
The unlocked variant likely isn't much different.
I have 2 N10+'s, one a N975U, and a N975U1.
Both have plenty of bloatware. The AT&T bloatware is easily package blocked.
The debloat list for both is near identical... disappointing and a bit surprising.
I take it you're on Android 12, roll back to 11. 10 would be better but the updated bootloader version likely won't allow it.
blackhawk said:
The unlocked variant likely isn't much different.
I have 2 N10+'s, one a N975U, and a N975U1.
Both have plenty of bloatware. The AT&T bloatware is easily package blocked.
The debloat list for both is near identical... disappointing and a bit surprising.
I take it you're on Android 12, roll back to 11. 10 would be better but the updated bootloader version likely won't allow it.
Click to expand...
Click to collapse
Am I able to use verizon fw on an unlocked att variant? thats the straight talk sim card I use anyways. Im just trying to get my mobile hotspot working again after the latest one ui update.
Don't know. Roll it back to the version that was working if you can.
I don't let my N10+'s update, ever.
blackhawk said:
Don't know. Roll it back to the version that was working if you can.
I don't let my N10+'s update, ever.
Click to expand...
Click to collapse
I'd like to do that but not sure which fw I had before this update
akp2369 said:
I'd like to do that but not sure which fw I had before this update
Click to expand...
Click to collapse
A Samsung Experience center at a Best Buy can reflash it. Might be easier.
blackhawk said:
Don't know. Roll it back to the version that was working if you can.
I don't let my N10+'s update, ever.
Click to expand...
Click to collapse
Could you point me in the direction of how to roll back Note 20 Ultra updates? The new updates broke my short cut maker app that let me change/choose bands and now it doesn't have permissions to access those secret settings.
kody2112 said:
Could you point me in the direction of how to roll back Note 20 Ultra updates? The new updates broke my short cut maker app that let me change/choose bands and now it doesn't have permissions to access those secret settings.
Click to expand...
Click to collapse
If you're on Android 12 I think you can go back to 11 by reflashing the same version it had before.
Others have done it here so I think it's doable.
As long as the boot loader hasn't been upgraded too. I never had to reflash any of my Androids, I avoid it if at all possible.
I have 2 N10+'s, one running on 9, the other 10, I prefer Pie though. Unfortunately the one running on 10 can't be reflashed to 9 because of the boot loader version It's not that bad though... I guess.