Database Users

A Lollipop made of Bugs !!!

Hello Everyone !
I updated my Nexus 4 to Android Lollipop 3 days ago and soon after I realized that it was a mistake and now I am stuck! I am facing all kinds of problems with it. Below is a list.
1. Pulse notification light is dead! Its not working for anything (missed calls, messages, app notifications etc...). Before the update it was working fine. I have checked all settings related to notifications. Pulse notification light option is on.
2. Sometimes I am not able to change the use Picture. It gives me the option to pick an image then crop and then it does nothing!
3. Many apps are crashing and have torn up UI after launch. I have attached a screenshot of PlayerPro UI
4. Many times I get an error pop up saying 'Android UI is not responding' which is weird because I don't have many applications installed or running.
I have tried resetting my device to its factory settings 3 times since the Lollipop update but I don't see any improvements. This is probably the worst Android Update released by Google since the evolution of Android. I never had problems when I updated to Kitkat but now, it has become my worst nightmare.
Is anyone else facing the same problems with Lollipop? Is there a way to go back to Kitkat, if yes then will I be receiving OTA updates in future? My device is not Rooted.
Thanks.

t3chn0vamp said:
Hello Everyone !
I updated my Nexus 4 to Android Lollipop 3 days ago and soon after I realized that it was a mistake and now I am stuck! I am facing all kinds of problems with it. Below is a list.
1. Pulse notification light is dead! Its not working for anything (missed calls, messages, app notifications etc...). Before the update it was working fine. I have checked all settings related to notifications. Pulse notification light option is on.
2. Sometimes I am not able to change the use Picture. It gives me the option to pick an image then crop and then it does nothing!
3. Many apps are crashing and have torn up UI after launch. I have attached a screenshot of PlayerPro UI
4. Many times I get an error pop up saying 'Android UI is not responding' which is weird because I don't have many applications installed or running.
I have tried resetting my device to its factory settings 3 times since the Lollipop update but I don't see any improvements. This is probably the worst Android Update released by Google since the evolution of Android. I never had problems when I updated to Kitkat but now, it has become my worst nightmare.
Is anyone else facing the same problems with Lollipop? Is there a way to go back to Kitkat, if yes then will I be receiving OTA updates in future? My device is not Rooted.
Thanks.
Click to expand...
Click to collapse
relax bro,**** happens
i'm running lrx21t (sideloaded) and haven't (luckily) experienced any major issue.
but from what i've heard,many weird issues have arisen,more so on nex5
but this is to be expected with an overhaul of this magnitude..
hang in,google should take care of it in MR1
to downgrade,sideload factory image of kitkat 4.4.4 occam available at the google dev site
u dont need root,just an unlocked bootloader and adb n sdk tools
complete guide can be found in other threads and multiple other sites
also there are videos on youtube specifically detailing the procedure
PLEASE NOTE UNLOCKING BOOTLOADER CAUSES SYTEM WIPE-u wil lose all your data
always back-up before flashing/sideloading any file
if u r stock,u should get ota
i'm not responsible if u brick ur phone due to any procedure...ur phone,ur decision
hit thanks if this helps u

apv25 said:
relax bro,**** happens
i'm running lrx21t (sideloaded) and haven't (luckily) experienced any major issue.
but from what i've heard,many weird issues have arisen,more so on nex5
but this is to be expected with an overhaul of this magnitude..
hang in,google should take care of it in MR1
to downgrade,sideload factory image of kitkat 4.4.4 occam available at the google dev site
u dont need root,just an unlocked bootloader and adb n sdk tools
complete guide can be found in other threads and multiple other sites
also there are videos on youtube specifically detailing the procedure
PLEASE NOTE UNLOCKING BOOTLOADER CAUSES SYTEM WIPE-u wil lose all your data
always back-up before flashing/sideloading any file
if u r stock,u should get ota
i'm not responsible if u brick ur phone due to any procedure...ur phone,ur decision
hit thanks if this helps u
Click to expand...
Click to collapse
Thanks bro. Seems like sideloading kitkat is the only option I have right now. :/

{Singapore} LG G3 For Singaporean User

As you guys know, MM has started rolling out to the International Model D855!
I've been on MM for 3 days and quite satisfied with the update! Rom's seems faster and snappier, no more micro lag, juice seems to be better than LP tho... What you guys think? To all Lions, Share your thoughts and comments here! Cheers All!!!

Having problem flashing MM?
Use this method:
Reboot to twrp
2. Full wipe (data, internal card, system, cache, delvik cache, format data) All zip move to external card for a clean flash
3. Flash V2 zip - robalm's thread
4. Flash boot zip - autoprime's thread
5. Flash https://mega.nz/#!gxtwVBwZ!41S8Woy2y...HhK4gcGooK7OIo permissive zip (most important part don't forget to flash this)
6. Flash betasupersu 2.52 https://mega.nz/#!F8E02RyC!XeJhx4QZH...bVd14ccRYHbNKg ( no other version worked only this version worked)
7. Flash sharpening mod 3.5 and reboot system
To me this method works 100%
I've tried on 5 of my friend's G3 and all without fail!
4G ,Titanium and ext card works flawlessly

Reserved

Singaporean user here, so far it's been fantastic on stock marshmallow. With 21c modem there's no problem when it comes to connectivity (I'm on Singtel and I get 4G just like on Lollipop). Battery life much better than lollipop (average about 3.5-4h SOT compared to 2.5-3h on lollipop).
Here's a features review I did for the new stock MM

oceangreen said:
As you guys know, MM has started rolling out to the International Model D855!
I've been on MM for 3 days and quite satisfied with the update! Rom's seems faster and snappier, no more micro lag, juice seems to be better than LP tho... What you guys think? To all Lions, Share your thoughts and comments here! Cheers All!!!
Click to expand...
Click to collapse
Sorry to ask but really all International Model D855 got MM update or only Poland ? Please confirm.

OTA in Poland for D855 only

krk2krk said:
Sorry to ask but really all International Model D855 got MM update or only Poland ? Please confirm.
Click to expand...
Click to collapse
currently only Poland has update via OTA or LG PC Suite. However, there are zip files and KDZ files available that you can flash on any D855.

oceangreen said:
Having problem flashing MM?
5. Flash https://mega.nz/#!gxtwVBwZ!41S8Woy2y...HhK4gcGooK7OIo permissive zip (most important part don't forget to flash this)
6. Flash betasupersu 2.52 https://mega.nz/#!F8E02RyC!XeJhx4QZH...bVd14ccRYHbNKg ( no other version worked only this version worked)
7. Flash sharpening mod 3.5 and reboot system
Click to expand...
Click to collapse
Hi oceangreen,
Saw this thread late. Black screen, Red & Blue LED flashing problem after following autoprime's thread.
Some questions:
Step 5 - autoprime didn't have this! However, your Megasync link requires decryption key? Can u provide?
Step 6 - Is this the same as autoprime's SuperSU 2.52?
Step 7 - Is this the correct link to the sharpening mod 3.5 (http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648)? autoprime did not provide this! If I have no issues with the sharpening issue, can I skip this?
Thks in advance.

Is this still MM if use 21c modem ?

Preter said:
Hi oceangreen,
Saw this thread late. Black screen, Red & Blue LED flashing problem after following autoprime's thread.
Some questions:
Step 5 - autoprime didn't have this! However, your Megasync link requires decryption key? Can u provide?
Step 6 - Is this the same as autoprime's SuperSU 2.52?
Step 7 - Is this the correct link to the sharpening mod 3.5 (http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648)? autoprime did not provide this! If I have no issues with the sharpening issue, can I skip this?
Thks in advance.
Click to expand...
Click to collapse
This thread really need updating - or at least a sticky note to say that the better thread to use is http://forum.xda-developers.com/lg-g3/development/stock-t2961073/page252
Answer to some of my own questions:
Here are the mega links without requiring key
https://mega.nz/#!gwFhDAIb!ElPjTOntE...nGotozKUyypoAU
https://mega.nz/#!M5tkgDoR!eWGHs5O29...7uP6fiW-8pOwbw
you don't need sharpening mod if you use v2.52 see http://forum.xda-developers.com/lg-g...ables-t3282012. with this method it's simple & root sticks
The SuperSU 2.52 is the same based on the hash files.

fOxunO said:
Is this still MM if use 21c modem ?
Click to expand...
Click to collapse
yes, modem only affects cellular and things like that. The rom is still MM

Does it have volte with sg telco

Followed the flashing guide to the letter - this V2 rom is great - but for only about 3 days.
After around the 3 day mark, the error message will flash "SIM card removed The mobile network will be unavailable until you restart with a valid SIM card inserted."
The phone will reboot within 10 seconds (even if you go to airplane mode immediately). It rebooted repeatedly first time it happened.
Did a complete nuke wipe, flashed again. Same thing - at the 3 day mark - the Singtel SIM will show the same error and reboot. After that, SIM not usable at all. All telco signals (Singtel) will be gone. No phone, SMS, let alone data of any sort.
Think it is the problem with the modem.
http://forum.xda-developers.com/lg-g3/development/stock-t2961073
(Download v2 (modem from v21c) -> https://mega.nz/#!OIlwGLKS!LlcNIImHK...EzSt_ikHlWj3yY)
Tried flashing 21A, 21B, autoprime's hybrid modem. Doesn't work. Anybody else encountered similar problems?
Flashed on TWRP 2.8.7 from Stock Kit Kat 4.4.2.

Preter said:
Followed the flashing guide to the letter - this V2 rom is great - but for only about 3 days.
After around the 3 day mark, the error message will flash "SIM card removed The mobile network will be unavailable until you restart with a valid SIM card inserted."
The phone will reboot within 10 seconds (even if you go to airplane mode immediately). It rebooted repeatedly first time it happened.
Did a complete nuke wipe, flashed again. Same thing - at the 3 day mark - the Singtel SIM will show the same error and reboot. After that, SIM not usable at all. All telco signals (Singtel) will be gone. No phone, SMS, let alone data of any sort.
Think it is the problem with the modem.
http://forum.xda-developers.com/lg-g3/development/stock-t2961073
(Download v2 (modem from v21c) -> https://mega.nz/#!OIlwGLKS!LlcNIImHK...EzSt_ikHlWj3yY)
Tried flashing 21A, 21B, autoprime's hybrid modem. Doesn't work. Anybody else encountered similar problems?
Flashed on TWRP 2.8.7 from Stock Kit Kat 4.4.2.
Click to expand...
Click to collapse
I have the same problem as you. except, I did not do the update and it happened out of the blue today. Been restarting my phone and if I am lucky, sometimes I get connected to the network for about an hour before the error comes on again.

matthewmax09 said:
I have the same problem as you. except, I did not do the update and it happened out of the blue today. Been restarting my phone and if I am lucky, sometimes I get connected to the network for about an hour before the error comes on again.
Click to expand...
Click to collapse
Hi Matthew,
Saw your PM. Just to confirm that you have the same problem.
​Error message - "The mobile network will be unavailable until you restart with a valid SIM card inserted"
​- Bar counts up to 100% before phone reboots automatically
This is apparently a very serious problem with Android going back a few years and a few Android OS versions (KK I believe). It happens with various phone models ranging from:
LG G4
https://www.reddit.com/r/lgg4/comments/43p26p/sim_card_removed/
Nexus - Google doesn't give a F*CK
http://androidforums.com/threads/sim-card-problems.467384/
Motorola, Nexus, Samsung Galaxy etc.
https://code.google.com/p/android/issues/detail?id=66964
Google apparently doesn't give a rat's ass about it. As such it is very difficult to pin-point the problem. I have flashed & re-flashed robalm's V2 ROM at least 4 times, each time with a complete (nuke) wipe of everything including the Internal SD card. It definitely happens on the default modem (21C supposedly) that comes with it. Different modems have not helped. If you find one that works, let me know.
It cannot be a SIM card problem. Cos I've never ever taken it out since the day I got the phone. Once the problem happened, I've tried re-seating it, wiping the electrical contacts with microfibre cloth etc. Singtel shop customer service checked all the APN and network settings and confirmed it is correct, asked me to try the SIM card in other phones. Done that, nothing wrong with the SIM..
Googling further, some folks discovered that it is due to Google Apps (Play Store, Maps, G+, Gmail, Play Books/Games/Movies/Music/Services etc. etc.), which are system apps (as part of the ROM package), causing the problem after they are updated via Google Play Store. Don't we all update apps to the latest version, no?
I tried uninstalling all the updates for all of them (Settings>>Apps>>) and replacing them with the factory updates that came with the ROM. I usually freeze all the crap money sucking subscription based or in-app purchasing Google Apps that I don't use anyway. However, whether frozen or not, it still happens. Although not freezing any of them does seem more likely to cause the problem to become even more severe - like going into constant reboots as opposed to intermittent ones. When that happens, you have to go to airplane mode BEFORE the countdown completes and reboot happens. At least when it restarts, it won't hunt for the missing cellular signal and triggering another reboot. This then allows you to freeze the suckers more agressively.
It worked for a few days - I thought I had narrowed the problem down to Google Play Store, Play Framework and Play Services. But yesterday or so it has come back again with a vengeance. Freezing Google Play Store does not help by the way - besides what's the point if you can't use Play Store?
Problem is, disabling the auto-update functions on Google Play Store using:
(Play Store>>Settings>>General>>Auto-update apps>>check "Do not auto-update apps")
doesn't stop Google Play Store and Google Play services from auto-updating themselves! F*ck Google! You cannot prevent it no matter what.
Worse, everytime it auto-updates itself (or if you uninstall updates) - note that it will switch to the default setting of "Auto-update apps over Wi-Fi only" again. So you have to be fast in going to Settings in Google Play each time you reboot and open Play Store.
Some netizens have suggested ADB command line means to cripple the auto-updating. But to me that is not the freaking point. It's about trying to isolate and find the problem.
You end up uninstalling updates for Play Store several times a day but when you find that the cellular signal is gone (no bars), you realise that it has sneakily updated to 6.0.5.
But even when I uninstall all updates for Play Store. It can still happen. Maybe less frequently.
No cellular signal is bad enough. The worst aspect is the rebooting. I tried restoring my beloved KK 4.4.2 Nandroid backup but apparently I'll have to find a compatible modem again as TWRP 2.8.0 (or my previous version before upgrading to TWRP 2.8.7 for this Marshmallow) didn't manage to back it up (even though I tick everything).
Still doing trial and error to try isolating the problem. The Google apps clue seems the more likely cause, but I can't say I can discern a definite pattern yet.
It could be a bug in Marshmallow 6.0. Maybe 6.1 will solve it. Maybe its the damn Polish ROM/modem.
In the meantime, I can only say - Do not flash this ROM! Without any cellular signal, the phone is not a phone. The constantly rebooting makes it useless!

Preter said:
Hi Matthew,
Saw your PM. Just to confirm that you have the same problem.
​Error message - "The mobile network will be unavailable until you restart with a valid SIM card inserted"
​- Bar counts up to 100% before phone reboots automatically
This is apparently a very serious problem with Android going back a few years and a few Android OS versions (KK I believe). It happens with various phone models ranging from:
LG G4
https://www.reddit.com/r/lgg4/comments/43p26p/sim_card_removed/
Nexus - Google doesn't give a F*CK
http://androidforums.com/threads/sim-card-problems.467384/
Motorola, Nexus, Samsung Galaxy etc.
https://code.google.com/p/android/issues/detail?id=66964
Google apparently doesn't give a rat's ass about it. As such it is very difficult to pin-point the problem. I have flashed & re-flashed robalm's V2 ROM at least 4 times, each time with a complete (nuke) wipe of everything including the Internal SD card. It definitely happens on the default modem (21C supposedly) that comes with it. Different modems have not helped. If you find one that works, let me know.
It cannot be a SIM card problem. Cos I've never ever taken it out since the day I got the phone. Once the problem happened, I've tried re-seating it, wiping the electrical contacts with microfibre cloth etc. Singtel shop customer service checked all the APN and network settings and confirmed it is correct, asked me to try the SIM card in other phones. Done that, nothing wrong with the SIM..
Googling further, some folks discovered that it is due to Google Apps (Play Store, Maps, G+, Gmail, Play Books/Games/Movies/Music/Services etc. etc.), which are system apps (as part of the ROM package), causing the problem after they are updated via Google Play Store. Don't we all update apps to the latest version, no?
I tried uninstalling all the updates for all of them (Settings>>Apps>>) and replacing them with the factory updates that came with the ROM. I usually freeze all the crap money sucking subscription based or in-app purchasing Google Apps that I don't use anyway. However, whether frozen or not, it still happens. Although not freezing any of them does seem more likely to cause the problem to become even more severe - like going into constant reboots as opposed to intermittent ones. When that happens, you have to go to airplane mode BEFORE the countdown completes and reboot happens. At least when it restarts, it won't hunt for the missing cellular signal and triggering another reboot. This then allows you to freeze the suckers more agressively.
It worked for a few days - I thought I had narrowed the problem down to Google Play Store, Play Framework and Play Services. But yesterday or so it has come back again with a vengeance. Freezing Google Play Store does not help by the way - besides what's the point if you can't use Play Store?
Problem is, disabling the auto-update functions on Google Play Store using:
(Play Store>>Settings>>General>>Auto-update apps>>check "Do not auto-update apps")
doesn't stop Google Play Store and Google Play services from auto-updating themselves! F*ck Google! You cannot prevent it no matter what.
Worse, everytime it auto-updates itself (or if you uninstall updates) - note that it will switch to the default setting of "Auto-update apps over Wi-Fi only" again. So you have to be fast in going to Settings in Google Play each time you reboot and open Play Store.
Some netizens have suggested ADB command line means to cripple the auto-updating. But to me that is not the freaking point. It's about trying to isolate and find the problem.
You end up uninstalling updates for Play Store several times a day but when you find that the cellular signal is gone (no bars), you realise that it has sneakily updated to 6.0.5.
But even when I uninstall all updates for Play Store. It can still happen. Maybe less frequently.
No cellular signal is bad enough. The worst aspect is the rebooting. I tried restoring my beloved KK 4.4.2 Nandroid backup but apparently I'll have to find a compatible modem again as TWRP 2.8.0 (or my previous version before upgrading to TWRP 2.8.7 for this Marshmallow) didn't manage to back it up (even though I tick everything).
Still doing trial and error to try isolating the problem. The Google apps clue seems the more likely cause, but I can't say I can discern a definite pattern yet.
It could be a bug in Marshmallow 6.0. Maybe 6.1 will solve it. Maybe its the damn Polish ROM/modem.
In the meantime, I can only say - Do not flash this ROM! Without any cellular signal, the phone is not a phone. The constantly rebooting makes it useless!
Click to expand...
Click to collapse
Yes! correct. we have the same problem. I don't think it is a glitch on mm 6.0 because i was on lollipop 5.0 when the problem occurred and I have only flashed 5.0 roms and modems. can you try the candySiX rom and see how it fairs in your phone? CandySix Rom thread link
I tried it on my phone and was able to connect to tower until I started installing Whatsapp which cause the sucker to break and reboot. But that was in a span of 15 mins. I read that it could also be a GPS problem so I disabled GPS but the phone was still broken. From my understanding, your trail and error seems to point to the play store updating itself that causes the phone to break correct? so why not cripple it using ADB and as for the updating of apps, it be done manually through sideload. because i don't think that there will be many apps that need to be frequently updated right? and even so if we do not update the app, it does not mean that the app will lose its functionality??

matthewmax09 said:
Yes! correct. we have the same problem. I don't think it is a glitch on mm 6.0 because i was on lollipop 5.0 when the problem occurred and I have only flashed 5.0 roms and modems. can you try the candySiX rom and see how it fairs in your phone? CandySix Rom thread link
I tried it on my phone and was able to connect to tower until I started installing Whatsapp which cause the sucker to break and reboot. But that was in a span of 15 mins. I read that it could also be a GPS problem so I disabled GPS but the phone was still broken. From my understanding, your trail and error seems to point to the play store updating itself that causes the phone to break correct? so why not cripple it using ADB and as for the updating of apps, it be done manually through sideload. because i don't think that there will be many apps that need to be frequently updated right? and even so if we do not update the app, it does not mean that the app will lose its functionality??
Click to expand...
Click to collapse
Dude –punctuation please …
I wish it was that simple. I've used Android Firewall (AFSWall+) to BLOCK all internet connections for Google Play Store and Google Play Services. The sneaky bastards at Google can still somehow update the factory Google Play Store from to 6.0.5! Upon that happening, all cellular network connection WILL DEFINITELY be lost. It may or may not reboot after that.
The problem is definitely related to Google Play (Store & Services). But it is not limited to it. Even when it has not updated itself, the error message can still show up and the phone can still reboot randomly with the error message. That is why I don’t think using ADB to disable updates solves anything.
Google is definitely doing something very intrusive with their Play Store apps – (why should and) how the hell apps (even if system apps) can be allowed to affect the functions of SIM card and cellular network reception to this extent is beyond me. Big brother is really upon us.
Not keen on trying custom ROMs anymore since my S2 days. Especially when stock Marshmallow already cause so many problems. Maybe this needs to be posted in the other international LG G3 threads.

Flash tool crashed
oceangreen said:
As you guys know, MM has started rolling out to the International Model D855!
I've been on MM for 3 days and quite satisfied with the update! Rom's seems faster and snappier, no more micro lag, juice seems to be better than LP tho... What you guys think? To all Lions, Share your thoughts and comments here! Cheers All!!!
Click to expand...
Click to collapse
Heyy trying to flash MM but lg flash tool 2014 keeps on crashing on win 10. want to retain data so am not using TWRP. What tool are u using and software version?

Good Sharing... thus far my screen not so often give me a blank screen issue after upgrade to MM Global

Hi guys ( @Preter @matthewmax09 )
my friend's SEA device started to giving your "The mobile network will be unavailable until you restart with a valid SIM card inserted" error too.
did you solved this problem? can anyone tell a solution for this?
thanks.

New EU firmware! (EU1.1.124b)

So, it just popped up while my phone was idle, without anyone calling it in here first, YotaPhone finally decided to give us EU users the RU124 firmware! It looks from the changelog to be the exact EU equivalent to its RU counterpart, including YotaTravel, the return of the YotaStore and other stuff. It's been so long that I don't even remember, but I should be fine flashing this and then reflashing SuperSU and Xposed without losing anything, correct?

If you have stock recovery it will install fine. If not you should be able to grab the update zip from /cache and side load. Then reflash what you want.
Sent from my iPhone using Tapatalk

Yep I'm still on the stock recovery (I just boot TWRP every time I need it). Gotcha, then I'm just dumping my Titanium Backup folder onto my PC as a precaution, and then I'll update and report back on SU\Xposed.

Looks like whatever Yota pushed at 117MB was the wrong thing - a failed update attempt and a reboot later, it's now 0.94 GB. Seems like it's the correct size in ftp://fw.ydevices.com/YotaPhone2/Firmwares/EU/ so now it should work.

Update from RU1.1.112 to RU1.1.124 issue
https://r.tapatalk.com/shareLink?ur...share_tid=3436224&share_fid=3793&share_type=t
Sent from my iPhone using Tapatalk

Just as expected the 0.94 GB update file worked, I reflashed SuperSU and Xposed and the phone is working great on 1.124b.

What version were you coming from?
Sent from my iPhone using Tapatalk

EU1.87. I wanted to go to the RU version but never could get a KitKat RU firmware to boot on my device, so I just gave up and went back to the latest EU firmware.

Ah OK that makes sense. Glad you got it working.
Sent from my iPhone using Tapatalk

Go mine today (1.1.44HK)
Updated to EU 1.1.124b with official yotaflasher.
No Su nor any hack.
So far no bug, it's a great device.

Hi there!
I'm waiting for my yotaphone 2 from this new wave from chinese shops. I ordered the International version. Is it safe to flash the EU version firmware over the "international" version?
And please, can anyone provide an alternative downolad link for the yota flasher?
The one from offcial website:
https://yotaphone.com/us-en/ypflasher/
is a corrupted zip file.
Thanks!
Edit:
I could get it from here:
ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/

Seems there's a bug.
Almost each time i try to unlock phone (with power button) from EDP the pin keyboard isn't showing up, i must tap all over the EDP screen, way it's relocking then i can have the keyboard again.

Solved by using gesture instead of pincode

satsuki_yatoshi said:
Solved by using gesture instead of pincode
Click to expand...
Click to collapse
Gutted they removed the Instagram Cover instead of fixing it!

Rarelyamson said:
Gutted they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
Instagram restricted access to its API, so none of 3rd party apps now work properly. Thats why Instagram Cover was removed.

Hello
I deployed this great update a few days ago, and it clearly brings numerous improvements and fixes.
One visibly new bug annoys me a lot anyway, and that's why I am posting :
When I type a SMS on the EPD, lots of freezes occur. And today, I found a simple pattern. I type a word, and then I back-delete one or a few letters of it. Then I add new letters, and that frequently freezes the EPD for a long moment.
It's not 100%, lots of times it freezes under these conditions, few other times it does not.
I setup 3 languages to choose from (thanks to the update !) and the auto correction is ON.
Does someone else experience the same issue ? Any workaround or fix ?
Thanks

Appens to me 2 times, each time i needed to look/unlook the edp screen to solve

My problem is that with the latest update I need to restart my phone until it starts charging. Otherwise it will not charge ... does this happen to anybody else? Probably I should try to reset ...

no charge bug here

No charge bug here neither. Quite the opposite in fact, I would even say that autonomy obviously improved since this update.
And I confirm I have the same bug with the PIN keyboard not showing up on the EPD when using the Powa button. It happens very often after using the other screen, but unlocking by tapping twice is an easy and efficient workaround.
Surprising obvious bugs anyway, I hope the Yotagods watch us and intend to fix them.

A previous downgrade attempt has scarred me from trying to downgrade again

Back in December while i was still on 6.0.1 but on the latest monthly update at the time, I have known for awhile that there was a high android system battery drain after the february 2016 monthly update so I wanted to downgrade back to February. But when I was in the process of downgrading, I got an error on odin and it failed. After I restarted my phone I got a message saying "an error has occurred while updating the device software. Use emergency recovery function in the smart switch pc software" so at that time i was freaking out a bit and I went searching around and people said around may of 2016 samsung updated the bootloader so you couldn't downgrade to an earlier month that had the older bootloader.
I just want to know if samsung has updated their bootloader since 7.0 being on the latest bootloader. I'm currently on August security patch and want to go back to March.

I was using, if I'm not mistaken, the Android 7.0 July patch and I wanted to do an experiment. So, I downloaded version 6.0.1 and flashed using Odin.
Everything went through smoothly!
Just a curiosity, why do you want to go back to March? There are no benefits rolling back to an older patch, unless you want to test something.
Also, people say everywhere that their batteries are X with Y update and then, with Z, it got worse (or better). It actually depends on your usage, what apps you have installed, how you use your phone, etc etc etc.
Ah! My S7 Edge is the Exynos version.
Regards

angourakis said:
I was using, if I'm not mistaken, the Android 7.0 July patch and I wanted to do an experiment. So, I downloaded version 6.0.1 and flashed using Odin.
Everything went through smoothly!
Just a curiosity, why do you want to go back to March? There are no benefits rolling back to an older patch, unless you want to test something.
Also, people say everywhere that their batteries are X with Y update and then, with Z, it got worse (or better). It actually depends on your usage, what apps you have installed, how you use your phone, etc etc etc.
Ah! My S7 Edge is the Exynos version.
Regards
Click to expand...
Click to collapse
I've had a serious kernel battery drain and i've tried whatever I could to fix it. It just started out of nowhere and I can't think of any apps that would cause it to continue and so my battery life has been horrible and it doesn't even go into doze half of the time and I also has forcedoze enabled.
If you were able to go back to 6.0.1 without having an error in odin, then what did i do wrong? I put all the right files in the right place.

orlans21 said:
I've had a serious kernel battery drain and i've tried whatever I could to fix it. It just started out of nowhere and I can't think of any apps that would cause it to continue and so my battery life has been horrible and it doesn't even go into doze half of the time and I also has forcedoze enabled.
Click to expand...
Click to collapse
What model is your phone? What country?
Battery drain, doze not starting... it's normally caused by apps.
Post a screenshot from Settings -> Device Maintenance -> Battery -> Battery Usage

angourakis said:
What model is your phone? What country?
Battery drain, doze not starting... it's normally caused by apps.
Post a screenshot from Settings -> Device Maintenance -> Battery -> Battery Usage
Click to expand...
Click to collapse
sm-g935w8 (canada) right now im currently backing up apps and other stuff in smart switch so it is charging but im getting like close to 3 hours of SOT when I used to get 6 hours back on 6.0.1 february and 4 hours on the first 7.0 (march)
Android OS has a high stay awake.

orlans21 said:
sm-g935w8 (canada) right now im currently backing up apps and other stuff in smart switch so it is charging but im getting like close to 3 hours of SOT when I used to get 6 hours back on 6.0.1 february and 4 hours on the first 7.0 (march)
Android OS has a high stay awake.
Click to expand...
Click to collapse
Ohhh Canadaaa \o/
What I would suggest is to start from scratch, without restoring any backup.
If you want, you can download the current and older versions from here: https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935W8/
I'm also on August security patch and I consistently get 7h+ SOT but I disable preloaded apps, (especially Facebook), use the resolution in HD and a black theme to get the benefits of the AMOLED screen.
When using Odin, make sure you put everything on the right place and use CSC file instead of HOME_CSC. It will delete all your data!

angourakis said:
Ohhh Canadaaa \o/
What I would suggest is to start from scratch, without restoring any backup.
If you want, you can download the current and older versions from here: https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935W8/
I'm also on August security patch and I consistently get 7h+ SOT but I disable preloaded apps, (especially Facebook), use the resolution in HD and a black theme to get the benefits of the AMOLED screen.
When using Odin, make sure you put everything on the right place and use CSC file instead of HOME_CSC. It will delete all your data!
Click to expand...
Click to collapse
I also have apps disabled or at least HAD them disabled..i've might have enabled them except the ones i know for sure i dont need like facebook, chrome and those microsoft apps...you get the idea. I use HD resolution and keep it on black or dark theme. I use substratum and have whatever apps are supported themed to black.
Also why not home_csc if im starting from scratch?

orlans21 said:
I also have apps disabled or at least HAD them disabled..i've might have enabled them except the ones i know for sure i dont need like facebook, chrome and those microsoft apps...you get the idea. I use HD resolution and keep it on black or dark theme. I use substratum and have whatever apps are supported themed to black.
Also why not home_csc if im starting from scratch?
Click to expand...
Click to collapse
HOME_CSC will not wipe /data, CSC will. I may be crazy, but I erase things the maximum I can, so: I factory reset before updating to a new version, I use the CSC file to flash via Odin and I factory reset after I've updated. Then I log in to my Google account and start installing my apps from Play Store.
Of course I don't do it monthly (because security patches make no drastic changes). I only do it when there's a huge update (like Android 6.0 to 7.0) or when I feel the phone becomes sluggish (because I've installed and uninstalled lots of apps, for example).
When I had my Nexus 6, I also used fastboot commands and TWRP to garantee it's 100% clean (yep, you can now shout * crazy dudeeee *)

angourakis said:
HOME_CSC will not wipe /data, CSC will. I may be crazy, but I erase things the maximum I can, so: I factory reset before updating to a new version, I use the CSC file to flash via Odin and I factory reset after I've updated. Then I log in to my Google account and start installing my apps from Play Store.
Of course I don't do it monthly (because security patches make no drastic changes). I only do it when there's a huge update (like Android 6.0 to 7.0) or when I feel the phone becomes sluggish (because I've installed and uninstalled lots of apps, for example).
When I had my Nexus 6, I also used fastboot commands and TWRP to garantee it's 100% clean (yep, you can now shout * crazy dudeeee *)
Click to expand...
Click to collapse
I used to restore all my apps that way too but the last factory reset i did I just restored backup but this time ill do it that way. So now then i gotta take screenshots of where all my apps are placed on my home screen

So I attempted it and it is a success!

September 2019 Security update for Mi A2 is now available

69.5MB in size so no major changes are to be expected...

Downloaded it just now...no major changes...no bugs encountered...

Weird noise while switching camera modes seems to have gone

Patched boot of last update ?

parkpark9999 said:
Patched boot of last update ?
Click to expand...
Click to collapse
Stock and patched (Magisk 19.3) images of /boot partition:
Note: I recommend to
- copy stock image to /downloads,
- patch it with Magisk (thus a copy of stock image will be saved in /data for further "Uninstallation of Magisk")
- copy patched image to PC (or take the one attached)
- boot patched image via fastboot
- make "Direct installation" in Magisk
This method will enable you to "Uninstall Magisk" by <Restore partitions> command when preparing to download next OTA

Darshan28 said:
Weird noise while switching camera modes seems to have gone
Click to expand...
Click to collapse
Yes i can confirm that.
Is seems THat WI-Fi Is more stable now also.

ki69 said:
Yes i can confirm that.
Is seems THat WI-Fi Is more stable now also.
Click to expand...
Click to collapse
No, the sound is still there but a lot quieter (tested with a sound meter )

WARNING: Caused my phone to get stuck in a bootloop during update.
I'm not rooted and haven't unlocked bootloader. Trying to find a solution.
Edit: after a bunch of tries and some time charging, it finally booted and displayed a "Couldn't update" error. I'm back to august patch with a working phone. I guess I'll wait for more people to report on this update.
A question: In case my phone gets stuck in a bootloop for good when updating, should leaving the "OEM Unlocking" option enabled be enough to save it and allow me to flash a fresh iso?
I mean, only leave the option enabled, but not actually unlocking the bootloader (I don't want to reset the phone unless necessary).

Wifi has indeed improved a lot! I have now connection to the WiFi with the September update where it did not even find the network with the August update. Big improvement here! It now shows the same behaviour as an Galaxy S7, which is really good with WiFi. Major thing... Thanks Xiaomi!
Edit: it looks like this was only accidentally. On other places WiFi is still far more worse than on other devices. Where other devices find multiple WiFi networks with decent speeds, the Mi A2 find no network at all. If it finds finally one, then the speeds are dramatic. I ditch the phone and I'll go for the S10.

JassyNL said:
Wifi has indeed improved a lot! I have now connection to the WiFi with the September update where it did not even find the network with the August update. Big improvement here! It now shows the same behaviour as an Galaxy S7, which is really good with WiFi. Major thing... Thanks Xiaomi!
Click to expand...
Click to collapse
I'm not sure but seems the range became reduced. Need to test again.

WiFi speeds seem to have increased, camera noise is gone for me. So far no complaints

danannnn said:
WARNING: Caused my phone to get stuck in a bootloop during update.
I'm not rooted and haven't unlocked bootloader. Trying to find a solution....
Click to expand...
Click to collapse
Used to happen with many previous OTA updates to many people. Why should this update be fully safe? That's why experienced stock MiA2 users recommend to keep bootloader and critical unlocked.
danannnn said:
Edit: after a bunch of tries and some time charging, it finally booted and displayed a "Couldn't update" error. I'm back to august patch with a working phone.
Click to expand...
Click to collapse
Good that this method worked for you.... usually works but needs great patience and dedication.
danannnn said:
A question: In case my phone gets stuck in a bootloop for good when updating, should leaving the "OEM Unlocking" option enabled be enough to save it and allow me to flash a fresh iso?
I mean, only leave the option enabled, but not actually unlocking the bootloader (I don't want to reset the phone unless necessary).
Click to expand...
Click to collapse
Yes, enough, but please consider following:
- now with working phone you can save most of your user data to PC (and to Google), then unlock and then restore data;
- when you will be forced to unlock phone in bootloop, you won't be able to save/restore user data
- after unlocking you will have ability to make TWRP backup of your /data partition

Audio is definitely louder.

Aerobatic said:
Stock and patched (Magisk 19.3) images of /boot partition:
Note: I recommend to
- copy stock image to /downloads,
- patch it with Magisk (thus a copy of stock image will be saved in /data for further "Uninstallation of Magisk")
- copy patched image to PC (or take the one attached)
- boot patched image via fastboot
- make "Direct installation" in Magisk
This method will enable you to "Uninstall Magisk" by <Restore partitions> command when preparing to download next OTA
Click to expand...
Click to collapse
Sorry for the question, i'm on 10.0.13.0, can i boot the 10.0.14.0 patched and update, because i uninstalled magisk and all of the modules and the update fails, says it couldn't update.

Anyone thinks that the screen takes quite a while to light up after the fingerprint is recognised?

tatitar said:
Sorry for the question, i'm on 10.0.13.0, can i boot the 10.0.14.0 patched and update, because i uninstalled magisk and all of the modules and the update fails, says it couldn't update.
Click to expand...
Click to collapse
To answer your question, no, you can't update by doing that.
It is highly probable that your system partition have been remounted rw (read/write). For Android to successfully update, it is important for any of the root apps to never remount system as rw.
To check if this is the cause, check Matlog (an app for logcat) after the error when performing the update. Filter "update engine" and check a message in regards to system mounting.
If this is correct, then, to be successful in updating to the September security level, you will need to flash the August's system partition from a fastboot package, and then try the update once again
---------- Post added at 04:28 AM ---------- Previous post was at 04:23 AM ----------
LeChevalierR said:
Anyone thinks that the screen takes quite a while to light up after the fingerprint is recognised?
Click to expand...
Click to collapse
I see that this have a chance to occur when a person updates to a newer patch level. This is based on the messages i have seen in this forum board though it is unknown if it really the cause.
I read that deleting your fingerprints and add them back as new "fixes" this issue. I recommend you to try it out first

Aerobatic said:
...
Click to expand...
Click to collapse
Thanks for the all the explanations.
I guess I'll just keep "OEM Unlocking" enabled for now if its enough to save me from disaster. I don't mind losing my phone data, I consider it transient anyway. I'm just too lazy to set it all up again unless I really need to.
After making sure OEM Unlocking was enabled, that I got fastboot all set up and working, etc., I went ahead and attempted to update again, this time with no issues.

New bug encountered? I was watching a video from YouTube I opened through a WhatsApp link and all of a sudden my back button was there but home and recent apps buttons disappeared and they didn't come back until I reset my phone!

My screen makes some weird noises when it register touch, like squeking or static noise behind the screen, it is hard to explain. It start to hear when touchscreen register touch and it last about 2-3 seconds, then it stop, and when i touch it again the sound is back and so on. It's very annoying

I can do confirm that the camera sound is gone, although I can still hear it if I concentrate enough. It might be what is used to sound before so I can't really tell.
WiFi is definitely improved and it now searches for available networks faster
Overall system speed is improved specially with those awkward keyboard lags in the previous update.
Also LTE Signal got better I can tell
.
.
But I do have a little doubt about the battery life cause my phone had about 14% of charge last night which I forgot to plug in the charger and it was dead in the morning which has never happened before. It usually had at least 5% when that happened before. Still am not sure if that's the real deal so I'm gonna just wait some more to see battery performance.
But the update itself seems stable and bugless enough so it's definitely recommended to install it especially if you're dealing with camera sound...
P.S. : No camera2API nor ARCore