Hi all,
I've a Max 3 running Miui 10.01.0 Android 8.1.0 with the paid version of Nova.
I keep getting notifications for email, texts, alarms ect resetting to defaults and i can't work out why?
I'm not rebooting the phone, I'm not installing anything that would mess with other apps.
I'll set a tone for say Whatsapp or incoming texts and it works, but then a few days later it'll go back to the system default and I'll start me miss messages. When I check systems settings for the app, the one for sounds has switched itself back to off??
Can anyone suggest what's going on?
Thanks
I had that exact issue on oreo miui...I don't have any issues now with notifications on miui pie but I never figured out why this happened.
I tried many things..even after a clean flash with nothing installed this happened so it was not due to magisk or anything.
Now I have problem mounting partitions.
It started with the system partition, now /data is RW but the same thing happens.
Even if it says RW the folder I made and files I copied are gone after a reboot.
I will test if mounting /data in the terminal with, "mount -o remount,rw /data" when I have time
Last time I flashed the xiaomi eu pie I made a text file named test in /data and rebooted after each app or config I made to see if the file was still there.
First it was resolved by not installing the latest nfs magisk module.
Second time now I skipped this and the file remained until now...during this time I've just used the phone, haven't done any configurations.
I can't figure out why this issue reappears again and again on miui stock rom.
Related
Hi guys,
I could not find the exact same problem anywhere else, so here we go:
I have been running on [STOPPED][ROM ICS 15 Jul] slim rom for Desire [based on Sandvold .15 & K900 build 40] successfully for some months with only slight problems. One of those being an occasional (hot) reboot out of the blue. Recently, without any particular trigger, I encountered a bootloop on one such occasion. When I removed the SD card, I was able to boot, but obviously had no data and apps did not start, so I had to reset some things.
Since then, I made a lot of full wipes in 4ext recovery, formatted and re-partitioned my SD card, even tried out another SD card, and installed several different ICS ROMs, e.g. Sandvold or AOKP. The systems always work in the beginning - I can boot and set up my stuff. At some point afterwards, I get into a bootloop again on the next reboot I make. I can always enter recovery without problems, though.
[edit: Additionally, removing the SD card now does not help anymore: bootloops seem definite]
I have not been able to completely narrow down a possible trigger. However, I noticed that without setting up my Google Account, I seem to be able to keep the phone running & booting for days. If I do enter google data, I at some point get the bootloop, whether I check the "sync/save my phone via google" or not (though not immediately after entering the account - it seems to take some time - some corrupt data to be synched perhaps?). Obviously, I am not keen on starting a new google account and losing all my apps and data, and running the phone without google at all is, let's just say, limited. I do not really see how a bootloop can be caused by some data that is coming in via google, but it comes up with an annoying certainty.
One last thing: the 4ext app currently pops up a news window regarding bootloops on some users' devices, but their recommended solution is to check in superuser whether the su binary is up-to-date. Unfortunately, it seems to be (3.1.1).
So if anybody out there has seen something like this or some suggestions as to narrow down the problem, I would much appreciate it!
Thanks in advance and best wishes from Germany!
This might be related to the google play store updating to the latest version. It is known to cause a boot loop on every restart for some ICS ROMs. Try this if it helps: http://forum.xda-developers.com/show...ostcount=16742
Thanks so much for pointing me in this direction!
Although your link seems to be broken, it gave me the correct idea on what to search for.
I followed steps that are discussed in http://forum.xda-developers.com/showthread.php?t=1944766 as well as http://forum.xda-developers.com/showthread.php?t=1355660&page=1661 and seem to be finally bootloop-free again even after setting up all my stuff!
For people who might need to follow the procedure, I did the following things:
Full Wipe
Install Sandvold ROM
Download modded Play Store APK file called: Vending-3.8.15.noupdate.norestrictions
Rename APK to "Vending.apk" and push to sdcard
Mount data, system, sdcard in Recovery
Enter "adb shell"
cd /system/app
rm Vending.apk
cd /data/app (might also be /data/data or something)
rm -r com.android.vending
rm -r com.android.vending.updater
cp /sdcard/Vending.apk /system/app/
(Dalvik wipe if ROM is not a fresh install)
Boot Up
Glad it worked for you. I followed almost the same steps myself. Unfortunately this happened to me while I was travelling and I was stranded with a brick for a week.
P.S: No idea why the link got eaten up...
Hello guys,
I've just flashed the Paranoid Android ROM by WOH (http://forum.xda-developers.com/showthread.php?t=1912187&page=111) and I really like it.
However, I'm having some kind of issue with the PA engine settings.
The problem goes like this:
1. When I set the global UI settings, I'm asked to reboot, but the settings are back to defaults after the reboot.
2. When I edit the preferences for a particular app, I'm only able to make it work by setting and applying the needed values followed by using the launch button, which finally makes the changes effective. These changes are, however, also reset after rebooting the phone.
I did some searching and found this hint (http://www.paranoid-rom.com/forum/guides-references/256-hint-pa-prefs-does-not-save-changes) which seems to deal with this problem, but haven't had any luck with it. In the terminal, when trying to run the commands, I get an error saying my file system is mounted read only. So I tried modifying the file perimissions in the ES file manager (which also didn't work on some occasions, but sometimes it did), then running the terminal commands successfully, but without any effect on the PA preferences bahaviour after rebooting.
I ended up editing those files manually and removing the backup file (which, I thought, was overwriting the preferences file, reverting the settings to defaults). The ES file manager also behaved very oddly when trying to manipulate those files, once I was not allowed to delete those files, than they disappeared on their own, same goes for renaming.
Finally, I think, the problem is being caused by the properties file being overwritten with the defaults on every boot. So far I've been unable to determine the cause of this behaviour, so I hope perhaps some of you have come across this problem and know the solution. Thanks in advance for that.
Anybody having trouble mounting /System in 5.0.1? es explorer can't write to it and when I use terminal emulator to mount it's still no go. ?
I use ScriptManager. It has the auto mount system partition as needed feature working for Samsung SELinux but it occasionally has an issue mounting as ro after writing. Just reboot. The prompt will keep popping up with "Not recommended" and something else like continue or default or recommended, can't recall. But with stock kernel, the only choice is "Not recommended" and reboot when done. No problem writing. Can't even use advanced mode to mount system as ro when it fails. Just reboot.
I just sent an update to the developer yesterday. He had sent me a development apk last Christmas to get the icon sizing issue corrected; mismatched to text on the Note 4, resizing the text makes the icons tiny. He fixed that in development but hasn't released it yet.
Are you talking about mounting system in a root file browser app? If so, use root explorer. It never fails.
tx_dbs_tx said:
Are you talking about mounting system in a root file browser app? If so, use root explorer. It never fails.
Click to expand...
Click to collapse
Yes. Got file Explorer going but still can't get any of the reboot menu apps to go with your stock L roms. Stock tar yes... I dunno.
jhill110 said:
Yes. Got file Explorer going but still can't get any of the reboot menu apps to go with your stock L roms. Stock tar yes... I dunno.
Click to expand...
Click to collapse
Do u want me to upload the 4 way reboot mod for my deodexed rom? I have that done already.
Edit: Here you go. Pushh this android.policy.jar to system/framework. You might get a freeze & reboot but once you hot swap it if the system freezes then recovers, just copy & paste it one more time then set permissions & reboot again.
tx_dbs_tx said:
Do u want me to upload the 4 way reboot mod for my deodexed rom? I have that done already.
Edit: Here you go. Pushh this android.policy.jar to system/framework. You might get a freeze & reboot but once you hot swap it if the system freezes then recovers, just copy & paste it one more time then set permissions & reboot again.
Click to expand...
Click to collapse
Thanks tx, your my hero! Still scratching my head tho... Running your rom completely from scratch... Total wipe of everything. Thanks again.
Edit: Awesome menu. Took one reboot and went through the "android is upgrading" for 15 minutes but it's working great.
Thanks again! :thumbup:
samep said:
I use ScriptManager. It has the auto mount system partition as needed feature working for Samsung SELinux but it occasionally has an issue mounting as ro after writing. Just reboot. The prompt will keep popping up with "Not recommended" and something else like continue or default or recommended, can't recall. But with stock kernel, the only choice is "Not recommended" and reboot when done. No problem writing. Can't even use advanced mode to mount system as ro when it fails. Just reboot.
I just sent an update to the developer yesterday. He had sent me a development apk last Christmas to get the icon sizing issue corrected; mismatched to text on the Note 4, resizing the text makes the icons tiny. He fixed that in development but hasn't released it yet.
Click to expand...
Click to collapse
May be off topic but I wanted to update the status of this app. The developer is focusing on lollipop issues and updated the application a couple of times recently. I appreciate the fact he's responded to the issues that were present with Samsung stock kernel and icon to text proportionality with Note 4. It keeps getting better; squashing bugs and adding features. I have the pro version so long term support is a wonderful thing regarding a purchase.
Here is my issue I cannot create folders or delete anything on the internal sdcard.
Background info: I just got this gs3 its on boost mobile. I am on NJ3 I used CF-auto-root method to get root. Everything went fine updated Supersu installed a bunch of apps including Titanium Backup and made backups of all apps on the phone. Everything finished fine. I have not deleted any apps yet nor have I installed a custom record very or any ROMs its still!l stock. I have a 64gb sdcard installed which is new and empty so I wanted to put my backups on it but could not. While looking for a fix I noticed that even the default INTERNAL sdcard had a red folder on top with "cannot write to this location" . so now I cannot use TB. It gives an "insufficient storage" message and fails
I then went to ES File Explorer and tried to make a folder on the internal card and could not, also tried to delete and could not !! I have Googled this problem and come up with a number of solutions but most are very old threads. Can anyone give me some help fixing this? The phone seems to otherwise work but I fear it will only get worse with time.
edit I can install apps though even now.
Oh I left out that I did recieve an update for Security policy update. Which I understand has something to do with SElinux. I also found a fix for what appears to be my problem related to this it is;
SU
restorecon -FR /data/media/0
I decided to try it but get a message that -F is invalid
syntax is restorecon (--nRrv-- )
From what I can google the version of restorecon I have on my phone does not include that switch!!! Just my luck, can anyone help me figure out if I can change the binary to an updated one so I can use this?
Well I am disappointed 45 views and not one reply, oh well.
I eventually bit the bullet and did a factory reset from the settings menu, it cleared up the issue and I still had root!! Google reinstalled all my apps and SuperSu disabled Knox for me. I also unchecked auto update for security updates so that Samsung does not send another one to me without my knowledge. also disabled autoupdate for Samsung apps.
know everything is golden again.
Repost from Sprint forum area, since this main area is much more active...
I have some weirdness going on with my LS990, still running the original ZV4 with Xposed and TWRP. I've never had any problems, until now, with anything on this phone, it's been fantastic and that's why I leave it on Kit Kat.
Starting yesterday, whenever I try to open the stock File Manager, I get the following error dialog:
------------
Note
Cannot read files. File Manager will be closed. Please check Media Storage enable settings and try again.
OK <--button
------------
Sometimes the dialog is in the foreground and I can close it with OK, but File Manager never opens. Sometimes the dialog appears behind my launcher icons and everything is unresponsive until I kill the running process using my nav bar shortcut from G3 Tweaksbox.
Also, I was trying to take a screenshot to include with this post, but it gives an error (Cannot take screenshot. Try again.) when trying to save it, plus the notification just stays on "Saving Screenshot" and is unable to be swiped away. [UPDATE: Noticed the screenshots do get saved in the proper Pictures/Screenshots folder, but the notification remains "stuck"]
I have also noticed my gallery is now empty, yet I can still access all of my pics from third-party file managers. Plus, when I open the camera and take a picture, it doesn't show in the little Gallery bubble at the bottom of the screen - in fact, the bubble doesn't even work, but yet the picture is saved properly.
Has anyone seen behavior like this before? The only thing I have changed on the phone is flashing the new TWRP 3.0.0.0 yesterday, using the image feature in my previously installed TWRP 2.8.7.0. I've updated TWRP plenty of times and there has never been an issue, but one difference I did notice this time was it asked if I wanted to keep System read-only or the default swipe to make read-write, which is what I did since I have Xposed and it modifies the System anyways.
Hopefully someone out there has an idea how to fix this, I really don't want to start all over, at least not until Sprint releases MM for the G3. The strange thing is, everything else is working just fine. My phone is fully functional except for the quirks mentioned above, root is still there and Xposed is functioning properly. I did do a Safe Mode boot to see if I could eliminate any root apps, but the issues were still there even after a safe boot.
Try sd card write fix on the market just for kicks u mighta lost permissions to the ext sd try switching save point to internal and see if they save
Unfortunately, I'm not using a microSD card, everything is saved to the internal memory. I thought it might be something with permissions, was thinking about trying the "fix permissions" option in TWRP but I'm not sure if that would make things worse. I've already tried a cache and Dalvik wipe, but that didn't fix anything. Even in Safe Mode, nothing changes.
I've searched online and haven't seen anyone else with this issue, it's very strange. I wish Sprint would hurry up and drop the MM update so I would have the perfect excuse to flash back to stock.