Related
Hello All,
Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).
**Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **
1. Using a root-enabled file manager, navigate to /system/etc/permissions
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...
4. Save the changes to the file.
5. Restart.
Attached is a copy of my platform.xml.
Note : Another Playstore application avaliable to fix this issue : https://play.google.com/store/apps/details?id=nextapp.sdfix.
Edited on request of @webmastir
try it yesterday 4 times and every time I had a Bluetooth error.
The only way I was able to use Kitkat with my note was using a custom ROM. Do not understand, what are custom rom builders do other way, but it work for me...
And more. Even with custom rom, the external sd is showed the "different" way, when in 4.3 , For example, in Total commander, there is no SD2. and some other software, do not define microsd as SD card. Just another folder in fail system...
zpjotr said:
try it yesterday 4 times and every time I had a Bluetooth error.
The only way I was able to use Kitkat with my note was using a custom ROM. Do not understand, what are custom rom builders do other way, but it work for me...
And more. Even with custom rom, the external sd is showed the "different" way, when in 4.3 , For example, in Total commander, there is no SD2. and some other software, do not define microsd as SD card. Just another folder in fail system...
Click to expand...
Click to collapse
Well, the architecture is the same and permission manisfest is used with all roms, sammy developers forgot to add a group I guess or did it on purpose, who knows.. but this worked like a charm for me after I flashed kitkat and felt handicapped.
Maybe you have messed up with some permission or something if you're getting the bluetooth error.
Try to do a clean flash again and then edit the file. If clean flash is not possibe pm me ur email. I will send you my xml and try to replace it with yours to see if that fixes your problem.
Sent from my SM-N9005 using xda app-developers app
this method isnt working for me I already modified the file but still cant make the programs to access the sd card, worst than that my internal storage is "write protected"... Im starting to think to get rid of this phone it has been nothing but problems since the beggining: Region Lock, Knox crap and now the SD... whats next?
carlomagno78 said:
this method isnt working for me I already modified the file but still cant make the programs to access the sd card, worst than that my internal storage is "write protected"... Im starting to think to get rid of this phone it has been nothing but problems since the beggining: Region Lock, Knox crap and now the SD... whats next?
Click to expand...
Click to collapse
Can you add a screen of the platform.xml? Perhaps you may have wrongly entered the permission gid.. And you need to restart the phone after editing the file.
mateenf said:
Can you add a screen of the platform.xml? Perhaps you may have wrongly entered the permission gid.. And you need to restart the phone after editing the file.
Click to expand...
Click to collapse
Sure here it is.
I made it by flashing the zip file, am not able to copy or edit files in the internal memory because "write protection"
carlomagno78 said:
Sure here it is.
I made it by flashing the zip file, am not able to copy or edit files in the internal memory because "write protection"
Click to expand...
Click to collapse
I'd strongly recommend to do a full wipe and factory reset if you're having a custom recovery. Ive read fee forums outside XDA that many a times flashable zips have cause a problem to platform.xml.
If you dont have a custom recovery then you may need to flash the firmware again and then edit the file.
Sent from my SM-N9005 using xda app-developers app
mateenf said:
Well, the architecture is the same and permission manisfest is used with all roms, sammy developers forgot to add a group I guess or did it on purpose, who knows.. but this worked like a charm for me after I flashed kitkat and felt handicapped.
Maybe you have messed up with some permission or something if you're getting the bluetooth error.
Try to do a clean flash again and then edit the file. If clean flash is not possibe pm me ur email. I will send you my xml and try to replace it with yours to see if that fixes your problem.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
thank you for proposed help. But I'm to tired of setting up phone after all weekend "fun" with rom flashed (all together 5-6 times with full wipe)
I'm almost sure, I wasn't messing with anything else - I did it more then 4 times, and Bluetooth was working until I edit platform.xml
now, I start to think, it's possible the ownership and permissions were changed after editing (I was using total commander and did not check it after saving the file).
But, I'm not the only one - there someone having same issue:
http://forum.xda-developers.com/showpost.php?p=49530438&postcount=3
P.S. I wasn't modifying /mnt/media_rw
some application don't have permission to write extSdCard
I made this mod but some application don't have permission to write ExtSdCard.
these application in my case are: dolphin wont download files, tomtom navigator doesn't work but moving tomtom folder in internal sdcard it works.
Is there anybody that have same issue?
mateenf said:
Hello All,
Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).
**Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **
1. Using a root-enabled file manager, navigate to /system/etc/permissions
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart.
Attached is a copy of my platform.xml.
Click to expand...
Click to collapse
Hey, I'm having the same issue, it's affecting my titanium backups. I tried the very same method above over the weekend based on instructions from another thread, but still no success.
Sent from my SM-N9005 using XDA Premium 4 mobile app
---------- Post added at 06:40 PM ---------- Previous post was at 06:27 PM ----------
Hey, your permissions are correct, previously I granted sdcard_rw rights, but not media_rw as mentioned in your discussion. Since the changes to show
"
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
"
I'm able to write and titanium backup is running smoothly.
Thanks and Cheers!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Thanks guy, work great for me on stock rom rooted NA6 kitkat
liva said:
Thanks guy, work great for me on stock rom rooted NA6 kitkat
Click to expand...
Click to collapse
Welcome Glad was able to help
Sent from my Nexus 5 using xda app-developers app
mateenf said:
Hello All,
Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).
**Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **
1. Using a root-enabled file manager, navigate to /system/etc/permissions
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart.
Attached is a copy of my platform.xml.
Click to expand...
Click to collapse
Thanks for the best additional thing to bring stuck with KitKat.
sent from my iPhone 6s 64gb 5.7inch Super Oled screen and spen
Will there be a solution for non rooted stock rom?
liomajor said:
Will there be a solution for non rooted stock rom?
Click to expand...
Click to collapse
That will have to wait for Samsung to push the OTA update.
Sent from my Nexus 5 using xda app-developers app
Today's rollout for OMN, SIM, MTL and ATL have the same missing media_rw.
If you are not on root (!!!knox 0x1!!!), i suggest NOT to update to 4.4.2
or a lot programs you paid for might not work properly if they need
access to ExtSdCard.
Dunno if its a bug or changed permissions to use ExtSdCard.
Currently only programs with system access like stock Filemanager are working.
mateenf said:
That will have to wait for Samsung to push the OTA update.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I don't think there will be a fix. This is a kitkat feature where app that need access to external sd need to ask for permission. So it's up to each app developer to update their app with this permission.
Sent from my SM-N9005 using XDA Premium 4 mobile app
antt00 said:
I don't think there will be a fix. This is a kitkat feature where app that need access to external sd need to ask for permission. So it's up to each app developer to update their app with this permission.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1
Sent from my Nexus 5 using xda app-developers app
Can confirm that it is working on my SM-N900W8.
Thank you.
Editing permission.xml worked on exynos version.
Sent from my SM-N900 using Tapatalk
Guys, please help me. I'm really, really pissed now for this Samsung BS!
I upgraded my Note 3 to NB4 (France) and of course, I could not able to access my external SD Card. There was a fix for the platform.xml, I followed the instruction to the T (note that I was successful in doing the same when I first upgraded to KitKat) but it still could not be detected, nor read.
Please if anyone knows the solution to this, please let me know.
Thanks.
It actually works using solid explorer to edit the platform.xml. And yeah. You have to be rooted to do so.
gidzdlcrz said:
It actually works using solid explorer to edit the platform.xml. And yeah. You have to be rooted to do so.
Click to expand...
Click to collapse
Still didn't work. I used Solid Explorer and am rooted.
After adding this:
<group gid="media_rw" /> to the WRITE_EXTERNAL_STORAGE,
like so:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Do I have to set the platform.xml's permission to rw-r-r? I did that but still not working.
You may need to reflash a new one.
gidzdlcrz said:
You may need to reflash a new one.
Click to expand...
Click to collapse
Reflash a new what? Platform.xml? I backed up the original file for safekeeping.
I mean. Flash a new clean firmware. It happened to me before. That solves my prob.
I lost count of how many times I've flashed this French firmware just because of this issue, and still no luck.
Sent from my SM-N9005 using Tapatalk
Try Root Explorer and grant root access for it.
After edidting the platform file reboot your phone.
BN3
Sent from my SM-N9005 using Tapatalk
mdfpido said:
Guys, please help me. I'm really, really pissed now for this Samsung BS!
Thanks.
Click to expand...
Click to collapse
Just a little blame correction, it's not Samsung, it's Google.
Give a credit where credit is due.
I read somewhere Samsung fixed this google mess in NB5.
Dahdoul said:
Try Root Explorer and grant root access for it.
After edidting the platform file reboot your phone.
BN3
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Try this....
http://forum.xda-developers.com/showthread.php?p=50837230
Sent via Hondata F.PRO + N3 NOS
Got a new s7 international so it's unlocked and now rooted. I was looking around for a way to avoid all those requests for permission to write to the external SD card (I don't want to format the card for use only in the phone). I found a page that recommends this:
edit platform.xml
Find <permission name=”android.permission.WRITE_EXTERNAL_STORAGE” > and add one new line:
<group gid=”media_rw” />
I'm finding it hard to believe this will work and I've never heard it before. Can anyone tell me if this would do anything, good bad or indifferent?
If you give me a link to the source I may be able to determine if this is reliable information.
Using CM12.1 on my SGH-T999
Ok, so I think I was prepared for something like this, but it seems that this is too much for me:
(I don't want to bother any of you, so you can skip the story and go to the summary down there)
I have a very normal Samsung Galaxy Grand Neo, GT-I9060L (the "L" stands for latin, as I'm chilean). Since with an older phone (Galaxy Y) I had some... issues, this time I wanted to play safe and decided to not root it. Ok, so no problem since 2014... until now. This morning I went to the Google's Android Device Manager website, and noticed that, where the buttons "Lock" and "Erase" should have been, there was something like "Setup Lock & Erase". I didn't do that before? So I clicked it, and it sent a notification to my phone, requiring the activation of "Android Device Manager" as a "Device Administrator". Ok, I read and accepted. The problem then began. I mean, the phone rebooted immediately, and it got stuck in the "SAMSUNG" splash screen, with a little vibration every few seconds (usually it's once, and then it shows the lock screen). Damn! As I had enabled USB Debugging, I thought that I could do something to at least backup the data there. Well, executing `adb devices`, and trying different states of the phone (I can get it to recovery mode, and ODIN mode, but not to safe boot), the only things that I could get to were "offline" (Linux) or "unauthorized" (OS X) under Recovery Mode (there wasn't anything to do, as any command lead me to an "error: device offline."), and "sideload" under Recovery Mode > apply update from ADB, which I think is one of the two only ways to try a firmware update (I don't know if that would solve anything), but I don't know if it would delete any data. Going to the main boot loop and trying `adb wait-for-device` didn't work (it just goes offline), so there isn't a way to get the phone to a normal state of "device" in adb (in other words: i cannot start the daemon on the phone, I suppose). Another thing I could do is to install Kies and try that "Firmware Upgrade and Initialization" thing, but I'm afraid that it could also mean to wipe the data there. I don't want to do so.
I'm sorry, I always write that long (in every language...), but at least there are more details with all of it.
So, summary:
– Grand Neo stuck at the SAMSUNG boot screen, right after setting Android Device Manager as a Device Administrator.
– USB Debugging is enabled, the phone is not rooted, and the firmware is the official, I mean, never touched.
– Some time ago I dumped the ".pit" file and also got the firmware (I9060LUBUANG1) from samsung-updates, just in case.
– I can get the phone to Recovery and ODIN modes, and so I just could do `adb sideload <file>` with some <file> (zip?).
– Can't even wipe the cache partition. I think it's game over with that one.
– I could try reinstalling the firmware with Kies, but don't know (as it doesn't recognize the phone) if I could do a backup.
– I don't want to wipe, erase, nor delete any data in the phone. It's the last resource for me.
Could I get some help with this? What should I do? ADB sideload? Kies? Something about Heimdall? I use OS X, but I've got a Pi, so there shouldn't be any problems with software (also, I've got a super-slow-netbook with Win XP hidden somewhere... I wish I could install Win 10 in Boot Camp inside this MBP Mid 2009). Thank you if you get to read this, and try to understand and help me with this.
Also, I'm sorry if this doesn't belong here (or anywhere...), but I couldn't post this on the Grand Neo forum (and it confuses me: is that forum for I9060i Grand Neo Plus as it states or for every I9060?).
Hi !
Please refer to this forum
https://forum.xda-developers.com/t/galaxy-grand-neo
Good luck !
Thaanks i solved it!!
xanthrax said:
Hi !
Please refer to this forum
https://forum.xda-developers.com/t/galaxy-grand-neo
Good luck !
Click to expand...
Click to collapse
Oh, simply thank you! Thanks to you I solved it! I owe you my phone's warranty!! (now voided, but whatever!)
[((Solution: DELETE THAT FILE `/data/system/device_policies.xml` through any recovery that lets you delete such file))]
You know something? I looked there before, but after your post I decided to go further (on my own!) into that forums, did some research about some things... and decided to flash a recovery. And I researched that it wouldn't do anything to the partitions I didn't want to lose, because the recovery has its own partition. Well, looking into the Grand Neo forum, I chose the TWRP recovery over the CWM one, because the latter was way older. And as I don't have Win, I used Heimdall with my Pi (Raspbian), but when I started I had some problems with the connection to the device. I discovered that the problem that I had with this version of the Heimdall package (1.4.0) had been already solved with the commit #329 on GitHub, so I tried compiling from source, and it successfully worked.
Then, I got amazed because, on recovery, I could get root access to every file, and also the device was detected over ADB as "recovery", and could do everything. Gladfully, I copied every file in the internal storage and the external SD Card to my Mac, then formatted the SD, then made backups of the Data and System partitions. Later, I discovered the difference between the Data, System, Internal Storage, Micro SD Card, Cache, Dalvik Cache, and Recovery partitions.
So if anyone out there wants a bit of info (at least about my phone), the System partition works like the Mac's System folder, containing things that almost never get modified by the end user, unless you flash some image to that partition (a custom or stock ROM, ideally), or delete accidentally causing broken things. The Data partition is mounted in /data, and contains (almost) everything that gets modified over the time. It also contains mount points for the Internal Storage, at /data/media/0 (there are several mount points for this over all the drive, and it's quite confusing), and I don't know exactly, but I think for Dalvik Cache and the Cache. The Micro SD Card partition is almost independent from everything else, but it also has several mount points along the Internal Storage one. the Cache is, well... the cache, and is mounted at /cache. The recovery partition is what I touched, and I think it explains itself a lot if you've used a Mac (pressing command+R at startup). The Dalvik Cache is quite interesting. I think it's mounted at /data/dalvik-cache, but I'm not sure. Well, it apparently has "optimized" versions of your apks stored in /data/app.
When I thought that wiping the Dalvik Cache would solve something, I discovered that the phone almost booted properly, but came back to the boot loop after the process of "optimizing" all of my 157 apps, with the difference that the device got recognized this time (only when booting after wiping the Dalvik!) by the ADB as a "device". Well played, at least. I went back to TWRP and made a backup of the Data, so now I can come back to that error whenever I want.
As I could get back in time, I decided to look for that little thing that was preventing my phone from booting. First, I dumped over 15 MB of logs, by ADB, the Recovery and the Shell. Now I can see that everything relates to some "policies" (more on that later). Then, I wiped the /data partition, as I had a backup. And I saw the phone booting to that "Welcome to your new Android!" thing. Thanks, the problem wasn't on the system! It was the Data! And, to confirm myself, I went to the settings, and activated that Google Device Administrator Thing again. Boom! Bootloop. It got wiped again by me, just to go there and do some "testing". I was going to see exactly what changed with that option, so went to that menu, and just before "pressing the button" (!), I went to recovery, and got every regular folder and regular file (because any symlink and stuff just made the copy fail) copied from /data to my computer. Then, I booted the phone, changed the setting, powered it off, and copied the /data again. In bash I made a `diff -r`, and also listed (from the original /data that I wanted to recover) every file there (this time of any kind) and on my computer sorted them all by date, to see the last files touched. Well, the diff resulted on various things, like a new line on the file /data/data/com.android.settings/shared_prefs/com.android.settings_preferences.xml:
Code:
<boolean name="pref_device_provision" value="true" />
It wasn't so important, as I deleted it and rebooted and nope, the bootloop continued. Backup restored again.
Then, something more interesting on the file /data/data/com.google.android.gsf/shared_prefs/update.xml: some name "provisioned" changed its value from zero to a UNIX timestamp in milliseconds. I didn't do anything on that because it wasn't so important, a timestamp. There was a ton of files with such timestamps, and also some new files from certain background apps, and the diff also showed up several xml files differing because the sorting. Dismissed all that and kept looking, and...
THERE IT WAS:
Code:
Only in /Users/Benja/Desktop/pos/data/system: device_policies.xml
(for the record: there was a "pre" and a "pos" folder, one for each /data)
I HATE IT. Out of rage, I looked at the file:
Code:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<policies>
<admin name="com.google.android.gms/com.google.android.gms.mdm.receivers.MdmDeviceAdminReceiver">
<policies flags="28" />
<allow-storage-card value="true" />
<simplepassword-enabled value="true" />
<allow-wifi value="true" />
<allow-text-messaging value="true" />
<allow-popimap-email value="true" />
<allow-browser value="true" />
<allow-internet-sharing value="true" />
<allow-bluetooth-mode value="2" />
<allow-Desktop-Sync value="true" />
<allow-IrDA value="true" />
<require-StorageCard-Encryption value="false" />
<allow-list-thirdparty value="" />
<block-list-InRom value="" />
<allow-unsignedapp value="true" />
<allow-unsignedinstallationpkg value="true" />
</admin>
</policies>
THAT FILE WAS CAUSING ALL OF THIS. There was also a backup of that file, that had nothing else than the xml header and an empty `<policies />`. But well, that file appeared also in the list of the most recently touched files (it took a while to do that list, because I couldn't figure out a better way than listing /data recursively and with full dates with the `-re` options (looked up for those at the help there, because the options were different and `find` didn't have printf) and parsing it with awk (stackoverflow #1767384), then on my Mac did the rest of the date parsing and sorting with date and cut and date again).
I DELETED THAT FILE `/data/system/device_policies.xml` (and obviously made a backup, even though I'll never want to bootloop it again, lol). Then rebooted and... finally I was able to see again my Little Prince lock background: Il tomba doucement comme tombe un arbre.
Now I'm restoring the files that I got from the Internal and External Storages. Then everything will continue as usual. Thank you so much for referring me to that forum again.
Also, after all of this, I googled the file and magically found this russian website (to prevent spamming, I cannot post a href): http://juick.com/PoZitron/2801749
That site (through the Google Translator (irony)) had just the info that I'd want to have read before (in russian, lol).
Well, as the site points, всегда делайте бэкапы!
Thanks again, and good luck to everyone else with problems out there.
Hi !
I`m glad you solved it , thanks for letting us know
Cheers !
thread closed
I've noticed many complaints about this. While I have left some comments in various threads with my original (root) suggestion, people don't seem to be finding them, or perhaps they just don't have root.
I have since figured out a non-root way to solve the problem.
WARNING
If you rely on encrypted cloud backups, there's a report that this willl break them.
Simple non-root solution
You don't need root but you do need to be a developer. Open Settings -> About and click on the build number 7 times. Connect your computer to your phone via USB cable. Install adb if you don't already have it (https://developer.android.com/studio/releases/platform-tools.html).
Download https://yasmar.net/xda/com.android.settings.intelligence.ab and run this command.
Code:
adb restore com.android.settings.intelligence.ab
The phone will prompt you. Click the restore button. There's no password.
Root solution and explanation
My original solution was to hand-edit /data/data/com.android.settings.intelligence/shared_prefs/suggestions.xml file to dismiss the suggestions. As noted, this requires root.
You can see my modified file here: https://yasmar.net/xda/suggestions.xml
The important part is all the _is_dismissed keys, which I manually set to true.
This file is also present in the adb backup above, which is why restoring it will remove the suggestions.
I came up with the adb restore solution while searching for a way to modify shared prefs without root. Specifically, this page: https://medium.com/swlh/back-me-up-hacking-android-apps-without-root-44d7789dc232. However, since I had already modified my prefs on the device, I didn't actually need to unpack/modify/repack the adb backup.
Updates
18/08/2020 - Added Google Wallet to the list of dismissed suggestions.
I am rooted and I changed all the false values to true but I have a problem after doing this my app suggestions are not working that were previously working I am using which switch and launcher but the the app suggestions are not working the one which come on top of the app drawer
a1291762 said:
I've noticed many complaints about this. While I have left some comments in various threads with my original (root) suggestion, people don't seem to be finding them, or perhaps they just don't have root.
I have since figured out a non-root way to solve the problem.
Simple non-root solution
You don't need root but you do need to be a developer. Open Settings -> About and click on the build number 7 times. Connect your computer to your phone via USB cable. Install adb if you don't already have it (https://developer.android.com/studio/releases/platform-tools.html).
Download https://yasmar.net/xda/com.android.settings.intelligence.ab and run this command.
Root solution and explanation
My original solution was to hand-edit /data/data/com.android.settings.intelligence/shared_prefs/suggestions.xml file to dismiss the suggestions. As noted, this requires root.
You can see my modified file here: https://yasmar.net/xda/suggestions.xml
The important part is all the _is_dismissed keys, which I manually set to true.
This file is also present in the adb backup above, which is why restoring it will remove the suggestions.
I came up with the adb restore solution while searching for a way to modify shared prefs without root. Specifically, this page: https://medium.com/swlh/back-me-up-hacking-android-apps-without-root-44d7789dc232. However, since I had already modified my prefs on the device, I didn't actually need to unpack/modify/repack the adb backup.
Click to expand...
Click to collapse
Do i need to reboot to bootloader, for applying the non-root step ?
gusbalaa said:
Do i need to reboot to bootloader, for applying the non-root step ?
Click to expand...
Click to collapse
Edit:my bad
No
Just while your phone is running. If you've got the settings app open you can watch the suggestions disappear
Done Fixed Thanks
Any way to get rid of these?
I already try,
But got pop up asking password, my devices doesn't using password only using PIN Number. Should i enter the PIN ?
gusbalaa said:
I already try,
But got pop up asking password
Click to expand...
Click to collapse
Just click the restore button. There's no password on the backup.
Aadil Gillani said:
Any way to get rid of these?
Click to expand...
Click to collapse
These are transient... so they aren't recorded anywhere in an XML file.
My phone has a caret to the right so I can expand or collapse these.
If you want them completely gone, you can disable the com.android.settings.intelligence app, but that will also remove the search bar.
Code:
adb shell pm disable-user --user 0 com.android.settings.intelligence
Works perfectly!
Thank you very much!
works perfect thanks! made a zip so ill can flash it easily on each update!
EDIT : finally I got a new one arrived, while all are set to false
Pay faster with google
Save payment info to your Google account for easier online checkout
Click to expand...
Click to collapse
can someone explain step by step? pls im so anoyed by those settings sugestion on android 10.
TNX
Antho02 said:
finally I got a new one arrived, while all are set to false
Click to expand...
Click to collapse
I don't have Google pay, which may be why I never saw that one.
Are you able to share your adb backup or suggestions.xml?
a1291762 said:
I don't have Google pay, which may be why I never saw that one.
Are you able to share your adb backup or suggestions.xml?
Click to expand...
Click to collapse
yeah i dont have google pay too. its more like the payment attached to playstore purchases, but already got paypal attached, and sue this suggestions isnt even clikable :good:
my xml :
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<boolean name="com.android.settings/com.android.settings.Settings$NightDisplaySuggestionActivity_is_dismissed" value="true" />
<long name="com.android.settings/com.android.settings.wallpaper.WallpaperSuggestionActivity_setup_time" value="1587334165402" />
<long name="com.android.settings/com.android.settings.wallpaper.StyleSuggestionActivity_setup_time" value="1587334165403" />
<boolean name="com.android.settings/com.android.settings.password.ScreenLockSuggestionActivity_is_dismissed" value="true" />
<long name="com.android.settings/com.android.settings.biometrics.fingerprint.FingerprintEnrollSuggestionActivity_setup_time" value="1587334165391" />
<boolean name="com.android.settings/com.android.settings.wallpaper.StyleSuggestionActivity_is_dismissed" value="true" />
<long name="com.android.settings/com.android.settings.Settings$NightDisplaySuggestionActivity_setup_time" value="1587334165403" />
<long name="com.android.settings/com.android.settings.notification.ZenSuggestionActivity_setup_time" value="1587334165401" />
<long name="com.android.settings/com.android.settings.password.ScreenLockSuggestionActivity_setup_time" value="1587334165393" />
<long name="com.google.android.gms/com.google.android.gms.wallet.setupwizard.PaymentsSetupWizardActivity_setup_time" value="1588549233979" />
<boolean name="com.android.settings/com.android.settings.wifi.calling.WifiCallingSuggestionActivity_is_dismissed" value="true" />
<boolean name="com.android.settings/com.android.settings.biometrics.fingerprint.FingerprintEnrollSuggestionActivity_is_dismissed" value="true" />
<long name="com.android.settings.suggested.category.HIGH_PRIORITY_setup_time" value="1587334165359" />
<boolean name="com.android.emergency/com.android.emergency.edit.EditInfoSuggestion_is_dismissed" value="true" />
<long name="com.android.emergency/com.android.emergency.edit.EditInfoSuggestion_setup_time" value="1587334165401" />
<long name="com.android.settings.suggested.category.FIRST_IMPRESSION_setup_time" value="1587334165368" />
<boolean name="com.android.settings/com.android.settings.notification.ZenSuggestionActivity_is_dismissed" value="true" />
<boolean name="com.android.settings/com.android.settings.wallpaper.WallpaperSuggestionActivity_is_dismissed" value="true" />
<boolean name="com.google.android.gms/com.google.android.gms.wallet.setupwizard.PaymentsSetupWizardActivity_is_dismissed" value="true" />
<long name="com.android.settings.suggested.category.DEFERRED_SETUP_setup_time" value="1587334165240" />
<long name="com.android.settings/com.android.settings.wifi.calling.WifiCallingSuggestionActivity_setup_time" value="1587334165403" />
</map>
Click to expand...
Click to collapse
First method (adb/root):
adb shell pm disable-user --user 0 com.android.settings.intelligence
Pros: Ability to collapse suggestions Cons: You will disable search option
Second method (root):
1. Backup /data/data/com.android.settings.intelligence/shared_prefs/suggestions.xml
2. Edit the end of strings suggestions.xml with value="digits", to value="false", save and reboot
Pros: I am happy! Cons: None
At first time I changed just first four strings and I am happy... Night vision suggestion gone, Pixel gone...
Antho02 said:
yeah i dont have google pay too. its more like the payment attached to playstore purchases, but already got paypal attached, and sue this suggestions isnt even clikable :good:
my xml :
Click to expand...
Click to collapse
Thanks. I have updated the download file. I ... guess it works
a1291762 said:
Thanks. I have updated the download file. I ... guess it works
Click to expand...
Click to collapse
i tried things yesterday too and it finally gone.
a question for you @a1291762 , could you tell me the group and owner for suggestions.xml , its app_10047 / uid 10047 (settings app) for me and i wonder if its same uid for everyone, if so ill can send you a twrp flahable zip if you want
Antho02 said:
i tried things yesterday too and it finally gone.
a question for you @a1291762 , could you tell me the group and owner for suggestions.xml , its app_10047 / uid 10047 (settings app) for me and i wonder if its same uid for everyone, if so ill can send you a twrp flahable zip if you want
Click to expand...
Click to collapse
Using adb and su, I see u0_a2/10002. I never even thought about file permissions... But maybe adb restore corrects them?
I don't need a flashable zip.
a1291762 said:
Using adb and su, I see u0_a2/10002. I never even thought about file permissions... But maybe adb restore corrects them?
I don't need a flashable zip.
Click to expand...
Click to collapse
not for you, i meant if you wanted add it to your thread as another method