Solved: "double tap here to learn how to use always on display" - Samsung Galaxy J7 (2017) Questions & Answers

Hello,
Long story short, I flashed a stock firmware and I had two problems faced me, and thank God I got the solution by luck and decided to share them with anyone who might find them useful.
First problem that my device is 32gb and after flashing it showed storage capacity of 16 GB only.
Solution: just wiped data in recovery and then flashed another stock firmware of another country.
Second problem which gave me aloooooooot of headache is an annoying message on the always on display says
"double tap here to learn how to use always on display"
And it I tapped over every pixel of the screen and wiped data/cache of aod app over and over again and did factory reset and even flashed another stock firmware and still IT DIDN'T GO AWAY!!!!!!!!!!
Solution which worked for me:
The current version of aod app available for my device is 4.2.xx or something like that.
So I downloaded from internet aod app -still by Samsung- but higher version 5.x.x and installed it but the aod screen stopped working at all.
Then I uninstalled this update and installed the next higher version of my current version 4.3.xx and once I installed it just vanished the message thank God!!
Anyway, I'm an amateur and sure these problems are nothing to you, but I felt I had to share that with you.
Stay safe ?

Related

Too many issues so few roms

3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?

[Q] "Dream Manager Service" keeps waking the screen up, how do I disable it?

[Q] "Dream Manager Service" keeps waking the screen up, how do I disable it?
I've looked for other posts on this issue, but none helped me very much. I have a Samsung S5 (international, sim-free), I recently flashed Phoenix Rom, version 6.3, build BOC7. Was on Omega Rom BOB7 previously. I'm also on BOB7 bootloader and modem. Don't know if it's relevant, but I'll mention it anyway. I don't have a PC, so it's difficult for me to use Odin, it's something I have to arrange days in advance. That's why I haven't updated bootloader or modem to BOC7 yet. And before anyone tells me to just go back to Omega Rom, Phoenix Rom is my absolute favourite Rom, it was my daily driver on KitKat, and I just discovered today that it had been updated to Lollipop, so I flashed it immediately.
Using Wakelock Detector immediately after booting, I find Android System, specifically "Dream Manager Service" the only thing which has woken the screen. So that seems to be the culprit, but I don't know how to kill it. It was never an issue before. Basic Daydreams (a Samsung process) is frozen via Titanium Backup. I don't use any other sort of daydream app or service.
It is clearly an issue with Phoenix Rom, but it didn't start until a few hours after I'd flashed it. So in the meantime something has happened, but I don't know what, and before I go through the hassle of reflashing it, I'd like to see how I could disable it. Things I've tried:
- Turning off ambient display - was not on when the problem started, I've tried turning it on and off, but doesn't help. I don't use it or want it, so I don't mind killing it somehow.
- Booting into safe mode. This helped, the problem did not appear when in safe mode. As far as I know though, it just doesn't allow "Dream Manager Service" to run. Not so helpful for finding out how to disable it.
- Revoking permission to "keep screen on" in App Ops for Android System. It seems to just ignore this, which seems to make the whole permission management thing a bit pointless.
When the screen does turn on, it looks different. The wallpaper is not displayed, and it's all in black and white.
Does anyone know why "Dream Manager Service" is doing this? And more importantly, how I can stop it? If you need any more information from me, just ask.
EDIT: Found reason: Ambient Display in Phoenix v6.3 was causing this bug, even after I turned it off. Downgraded back to 6.0, will skip 6.3 and wait for fix, hope it will be an option in the Aroma Installer next time.
Thank you! I found this information useful 2 years later in my Galaxy S7 running Ambasadii Nougat 7.0.

{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.

Flashlight being used by another app. Camera doesn't work

After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
TommyQuid said:
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
Click to expand...
Click to collapse
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
kanesglove said:
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
Click to expand...
Click to collapse
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
kanesglove said:
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
Click to expand...
Click to collapse
you guys offer little information at all so this is why no one helps you. Maybe tell what firmware version you flashed what root version you did etc. There is a big difference between bootloader revB/11 and the others
Holy ****. Did I just get constructive suggestions from jrkruse?! Dude if you told me I could fix my phone by sucking a fart out of a wallaby's ass I'd do it cuz the advice came from you, and if there's one thing I know it's that you know your ****. You're ****in' awesome. I feel so special now. Ok sorry about that...
Well, I'm not too sure about the OP but I can tell you about the phone I have that seems to have the same issue.
My S7 Edge is a SM-G935V on android 7.0 on update 4BQK2. Prior to rooting I put everything to stock then I did a NAND erase and repartition. No issues with any of that.
I rooted my phone from this post
G935V Root Method. No Lag! No Heat!
G935V Root Method. No Lag! No Heat!
I AM NOT RESPONSIBLE FOR ANY OF YOUR ISSUES! ALL I CAN DO IS RECOMMEND A GOOD PSYCHOLOGIST! Hey guys. Stumbled on this by accident. I HAVE ABSOLUTELY NO IDEA WHY IT WORKS, BUT IT DOES. THE METHOD HAS BEEN TESTED BY ME AND A FEW OTHER PEOPLE HERE...
forum.xda-developers.com
which directs to your older method for gaining root privileges.
[DISCONTINUED] ROOT Method For Nougat
DISCONTINUED New Thread Found Here This Root Method For S7 Nougat Nougat_S7_Root_2_82_All_Carriers_V2.zip Includes Fingerprint Fix [Latest Verison] Nougat_S7_Root_2_81_All_Carriers_V2.zip Includes Fingerprint Fix Nougat_S7_Root_2_79_All.zip...
forum.xda-developers.com
I also flashed Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.
Then I flashed the BL file in the BL slot from the G935U firmware with odin checking "Phone Bootloader Update". I used the BL file from G935UUES4BRA1 since it's the closest update for the U brand to the firmware this phone is on (G935VVRU4BQK2)
I'm aware that there are newer methods for gaining root access but I chose this method cuz I used it back in 2017-2018, I had read all the posts in the thread, and I knew it worked.
I currently have 3 S7 Edge phones all on the same firmware and build and are all rooted with the same combo method I just explained. The other 2 phones also have xposed installed and they both work well.. expect mine says weird stuff instead of the callers information. I think it only does it if they're a contact but in the notification tab it says an example like this 5556661234;verstat=No-TN-Validation. No clue how to fix that.
The phone that is having the same issue as the OP still had access to the private/secure folder when it was rooted; which I thought was weird cuz mine doesn't and from what I understood private mode gets disabled if the phone's rooted. Maybe it only gets disabled if you install xposed? I don't know. My son had the phone with the issue and it was his first smart phone and he dropped it a few times (with a case) so I was thinking it's an effect from something he downloaded from the play store (he's 20 now but pretty still very ignorant with android). Now I'm not sure if it's a software or hardware issue since the problem persisted after the NAND erase.
Something to note about my sons old phone also is that it has 2 thin pink lines running down one side of the screen (defective/dead pixels) and when the screen turns off it it flashes once before actually turning off. One time over the phone I tried troubleshooting the issue with him and he ended up being able to use his camera immediately after rebooting the phone though once he exited the camera app it wouldn't open again. We were trying a bunch of things, force closing any app I thought would be related to the issue. Not sure what allowed it work when it did, but even now right after a reboot the camera app still crashes.
This was long ago, I've since lost the phone. But, I was on the A bootloader and on OREO rooted using @/billa's method using an ENGboot file. I tried everything possible to get the camera to work including flashing back to stock but nothing helped. I just gave up finally. @kanesglove maybe try safely updating the firmware. Hope it helps

Categories

Resources