Develop Bugs

[Q] SD Card Not Being Used

So, a month ago I installed the Play Edition ROM on my S4. However, I've noticed that since then, no apps are using the SD Card. After Googling, I found the fix is supposed to be altering the platform.xml file so include <group gid = 'media_rw" /> under the WRITE_EXTERNAL_STORAGE permission. However, when I looked, it was already there. Looks like the ROM author already fixed that before I flashed it.
But still, no data is going to the SD card. It's there, and I can access it and manually move files over with Root Browser, but none of my apps are putting anything on there. Any ideas?

[Q] SD Card Fix Issue With P600

Hi,
I hope someone has suggestions on the following issue. I've searched threads, but haven't found this specifically.
I need the ability to R/W with multiple programs to my SD card. Due to work and also teaching concerns, I need to access directories of ebooks, articles and databases that are large and in the past were synced from the cloud to my device. Obviously KitKat makes an issue of this.
I recently obtained a Samsung Galaxy Note 10.1 2014 P600. Refurbished by the manufacturer. This has only a one-month warranty so rooting wasn't a concern.
1. I rooted the device using CF Autoroot. Rooting was confirmed by Root Checker.
2. I ran SDFix. No joy. Access to the SD card was sporadic - for example - music on the card would only play 2 seconds of each song.
3. Using Titanium Backup, I froze all Knox-related programs (this was more than the list of 6 I think. I can provide a list later.) Later, I also backed-up and deleted the programs.
Access to the SD card was still sporadic. After a reboot, I might have access for a few minutes, and then restricted access again.
4. I then tried Xposed Framework and the "Handle External Storage" module (see the 3rd method in this article http://technofaq.org/posts/2014/04/fixing-external-sd-card-write-issue-on-android-kitkat/). This worked but still had issues - I had drive access but from time to time it would disappear - it would seem to randomly unmount.
5. But, I decide to keep trying and in the process went to create a folder with File Explorer. FX gave me a message about KitKat - and asked if I wanted to configure it to try to write to the SD card under KitKat. I said yes - and suddenly I cannot access the drive at all.
Android Version 4.4.2
Kernel Version 3.4.39-1462259
Build Number: KOT49H.P600UECNK1
SE for Android Status Enforcing SEPF_SM-P600_4.4.2_0032
The SD card is a Sandisk 128GB.
I haven't tried flashing another ROM because I also need S-Pen and Chromecast functionality - so I just didn't want to fool with it.
1. Does anyone have any suggestions to get SD card RW access?
2. If "No" to the above, what is a good stock ROM with S-Pen and Chromecast functionality that has already addressed the SD issue that I can flash (and where is it located)?
Thank you all for your help.

Have you tried manually editing /system/etc/permissions/platform.xml?
Find this section:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
And change it to this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
[B][COLOR=Blue]<group gid="media_rw" />[/COLOR][/B]
</permission>
Check permissions on platform.xml after editing and fix if needed. Reboot.

blindmanpb said:
Have you tried manually editing /system/etc/permissions/platform.xml?
Click to expand...
Click to collapse
[SNIP]
Yes - I checked SDFix after running it, and platform.xml had already been correctly edited. Thanks for the suggestion though.

Have you tested this SD card in other devices, and other SD cards in this device?

Caveman6 said:
Hi,
I hope someone has suggestions on the following issue. I've searched threads, but haven't found this specifically.
I need the ability to R/W with multiple programs to my SD card. Due to work and also teaching concerns, I need to access directories of ebooks, articles and databases that are large and in the past were synced from the cloud to my device. Obviously KitKat makes an issue of this.
I recently obtained a Samsung Galaxy Note 10.1 2014 P600. Refurbished by the manufacturer. This has only a one-month warranty so rooting wasn't a concern.
1. I rooted the device using CF Autoroot. Rooting was confirmed by Root Checker.
2. I ran SDFix. No joy. Access to the SD card was sporadic - for example - music on the card would only play 2 seconds of each song.
Edit: This ROM would be a good fit for you it has all of the stock features plus some also the ability to read and write to the SD card. http://forum.xda-developers.com/showthread.php?t=2793898
3. Using Titanium Backup, I froze all Knox-related programs (this was more than the list of 6 I think. I can provide a list later.) Later, I also backed-up and deleted the programs.
Access to the SD card was still sporadic. After a reboot, I might have access for a few minutes, and then restricted access again.
4. I then tried Xposed Framework and the "Handle External Storage" module (see the 3rd method in this article http://technofaq.org/posts/2014/04/fixing-external-sd-card-write-issue-on-android-kitkat/). This worked but still had issues - I had drive access but from time to time it would disappear - it would seem to randomly unmount.
5. But, I decide to keep trying and in the process went to create a folder with File Explorer. FX gave me a message about KitKat - and asked if I wanted to configure it to try to write to the SD card under KitKat. I said yes - and suddenly I cannot access the drive at all.
Android Version 4.4.2
Kernel Version 3.4.39-1462259
Build Number: KOT49H.P600UECNK1
SE for Android Status Enforcing SEPF_SM-P600_4.4.2_0032
The SD card is a Sandisk 128GB.
I haven't tried flashing another ROM because I also need S-Pen and Chromecast functionality - so I just didn't want to fool with it.
1. Does anyone have any suggestions to get SD card RW access?
2. If "No" to the above, what is a good stock ROM with S-Pen and Chromecast functionality that has already addressed the SD issue that I can flash (and where is it located)?
Thank you all for your help.
Click to expand...
Click to collapse
Take a look at this thread http://forum.xda-developers.com/showthread.php?t=2741914. It looks like 128Gb SD card only works with 4.3
Edit: Try this ROM it should have RW to SD card. Along with S-Pen and Chromecast ability because it is stock based.
http://forum.xda-developers.com/showthread.php?t=2793898
Sent from my SM-P600 using XDA Free mobile app

Thank you for the prior comments. Due to work and the holidays I wasn't able to reply prior to now.
It turns out the issue was my attempt at using a 128GB card- the Samsung Note 10.1 2014 can apparently only handle up to a 64GB card.
Out of curiosity, has anyone found a way to root and reset KNOX to 0?

Orion116 said:
Take a look at this thread http://forum.xda-developers.com/showthread.php?t=2741914. It looks like 128Gb SD card only works with 4.3
Edit: Try this ROM it should have RW to SD card. Along with S-Pen and Chromecast ability because it is stock based.
http://forum.xda-developers.com/showthread.php?t=2793898
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
128GB cards do not work with 4.3. I have 4.3 and have tested four different Sandisk 128gb cards in fat32 and Exfat and no luck. Only 64gb works with 4.3 and this was confirmed with Best Buy demo units as well (pre 4.4 update of the demos course).

Caveman6 said:
Thank you for the prior comments. Due to work and the holidays I wasn't able to reply prior to now.
It turns out the issue was my attempt at using a 128GB card- the Samsung Note 10.1 2014 can apparently only handle up to a 64GB card.
Out of curiosity, has anyone found a way to root and reset KNOX to 0?
Click to expand...
Click to collapse
from what I know and read once knox is tripped you cant reset it. I think you can root without tripping it but just cant reset it.

It's a one-way trip!
mikep2323 said:
from what I know and read once knox is tripped you cant reset it. I think you can root without tripping it but just cant reset it.
Click to expand...
Click to collapse
Right! The problem is that "tripping" knox actually changes the hardware. It burns out a fusible link which, of course, can't be un-burnt.

Caveman6 said:
Thank you for the prior comments. Due to work and the holidays I wasn't able to reply prior to now.
It turns out the issue was my attempt at using a 128GB card- the Samsung Note 10.1 2014 can apparently only handle up to a 64GB card.
Out of curiosity, has anyone found a way to root and reset KNOX to 0?
Click to expand...
Click to collapse
Good news! The issue I was having was with the SPECIFIC 128 GB card. I tried a PNY 128GB card instead, and it is working perfectly.

[Q] Lost access to SD card after Lollipop upgrade

Upgraded from KK to Lollipop recently. Running fine, rooted, and with sleek kernel.
I left my 64gb SD card in while doing this and now I cannot access it.
The OS sees it and can erase it, but that's about it. When I try to mount it, it fails (with no error message).
Any suggestions on how to resolve please?

techinv said:
Upgraded from KK to Lollipop recently. Running fine, rooted, and with sleek kernel.
I left my 64gb SD card in while doing this and now I cannot access it.
The OS sees it and can erase it, but that's about it. When I try to mount it, it fails (with no error message).
Any suggestions on how to resolve please?
Click to expand...
Click to collapse
No problem. You need to add a line to the /etc/permissions/platform.XML.
It is the media line. Use Root Browser, open the file, write in the third line designated, save, enjoy
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
---------- Post added at 05:20 PM ---------- Previous post was at 05:03 PM ----------
sleekmason said:
No problem. You need to add a line to the /etc/permissions/platform.XML.
It is the media line. Use Root Browser, open the file, write in the third line designated, save, enjoy
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Click to expand...
Click to collapse
oh, and glad to see you using my kernel! I updated for sound control today as well. Flash new kernel in recovery.

sleekmason said:
No problem. You need to add a line to the /etc/permissions/platform.XML.
It is the media line. Use Root Browser, open the file, write in the third line designated, save, enjoy
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
---------- Post added at 05:20 PM ---------- Previous post was at 05:03 PM ----------
oh, and glad to see you using my kernel! I updated for sound control today as well. Flash new kernel in recovery.
Click to expand...
Click to collapse
Thanks very much sleek, for the answer and the update on the kernel. Downloading now!

sleekmason said:
No problem. You need to add a line to the /etc/permissions/platform.XML.
It is the media line. Use Root Browser, open the file, write in the third line designated, save, enjoy
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Sleek, my platform.xml already has those lines exactly as listed above for the WRITE_EXTERNAL_STORAGE permission. If it matters, the READ_EXTERNAL_STORAGE only has <group gid="sdcard_r" />
Click to expand...
Click to collapse

techinv said:
sleekmason said:
No problem. You need to add a line to the /etc/permissions/platform.XML.
It is the media line. Use Root Browser, open the file, write in the third line designated, save, enjoy
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Sleek, my platform.xml already has those lines exactly as listed above for the WRITE_EXTERNAL_STORAGE permission. If it matters, the READ_EXTERNAL_STORAGE only has <group gid="sdcard_r" />
Click to expand...
Click to collapse
Huh, I was having the same problem and the above fixed it just fine. But, why would you already have that line if you switched to Lollipop..? Strange. What file Explorer do you use?
---------- Post added at 08:49 PM ---------- Previous post was at 08:43 PM ----------
techinv said:
sleekmason said:
No problem. You need to add a line to the /etc/permissions/platform.XML.
It is the media line. Use Root Browser, open the file, write in the third line designated, save, enjoy
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Sleek, my platform.xml already has those lines exactly as listed above for the WRITE_EXTERNAL_STORAGE permission. If it matters, the READ_EXTERNAL_STORAGE only has <group gid="sdcard_r" />
Click to expand...
Click to collapse
is your card a SanDisk? There have been problems with SanDisk 64 cards.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

sleekmason said:
techinv said:
Huh, I was having the same problem and the above fixed it just fine. But, why would you already have that line if you switched to Lollipop..? Strange. What file Explorer do you use?
Not sure why the lines are there, but they are definitely there. I did notice that there was a platform.XML.bak in the same directory. I'm not sure what differences are there between the 2 files. I'm using ES File Explorer with root explorer functionality turned on.
---------- Post added at 08:49 PM ---------- Previous post was at 08:43 PM ----------
techinv said:
is your card a SanDisk? There have been problems with SanDisk 64 cards.
Click to expand...
Click to collapse
Yep, it is a SanDisk 64, but I've been using it with this tablet for almost a year without any problems.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

techinv said:
sleekmason said:
techinv said:
Huh, I was having the same problem and the above fixed it just fine. But, why would you already have that line if you switched to Lollipop..? Strange. What file Explorer do you use?
Not sure why the lines are there, but they are definitely there. I did notice that there was a platform.XML.bak in the same directory. I'm not sure what differences are there between the 2 files. I'm using ES File Explorer with root explorer functionality turned on.
---------- Post added at 08:49 PM ---------- Previous post was at 08:43 PM ----------
Yep, it is a SanDisk 64, but I've been using it with this tablet for almost a year without any problems.
Click to expand...
Click to collapse
Give Root Browser a shot. I switched over to Root Browser after problems with ES.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

sleekmason said:
techinv said:
sleekmason said:
Give Root Browser a shot. I switched over to Root Browser after problems with ES.
Click to expand...
Click to collapse
Installed root browser, checked the file, but I don't see any differences so here is what I tried anyway.
Made a bogus edit to the file and saved it, rebooted, no change.
Booted into recovery, wiped the micro_sd card, rebooted, no change.
Erased the card through, settings -> storage, no change.
The OS cannot mount the card. It seems like it tries to when I touch the command (I see an icon for about a half second in the status bar), but it fails and there is no error message that I can see.
I'm beginning to think that this card is toasted and that maybe I should buy another one (but not SanDisk).....
Click to expand...
Click to collapse
Click to expand...
Click to collapse

techinv said:
sleekmason said:
techinv said:
Installed root browser, checked the file, but I don't see any differences so here is what I tried anyway.
Made a bogus edit to the file and saved it, rebooted, no change.
Booted into recovery, wiped the micro_sd card, rebooted, no change.
Erased the card through, settings -> storage, no change.
The OS cannot mount the card. It seems like it tries to when I touch the command (I see an icon for about a half second in the status bar), but it fails and there is no error message that I can see.
I'm beginning to think that this card is toasted and that maybe I should buy another one (but not SanDisk).....
Click to expand...
Click to collapse
Do you have one just to check With? Maybe in your phone or camera?
Click to expand...
Click to collapse
Click to expand...
Click to collapse

sleekmason said:
techinv said:
sleekmason said:
Do you have one just to check With? Maybe in your phone or camera?
Click to expand...
Click to collapse
Good idea, will look and see what I can find. Getting late here so will do more with this tomorrow.
Thanks again for the suggestions.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Found a 32gb SanDisk card and it worked right away in my G Pad, so I guess that confirms that the 64gb one stopped working somewhere during the upgrade to Lollipop. Sort of sucks, but at least I know.....

LG G Pad SD Card problems
Hi, I am having the same issue with SD Cards (3 - 2-64gb and 1-16gb). I just purchased two G Pad 8.3's, one for my son and one for me. I also purchased two Samsung EVO Micro SDXC 64GB cards to use with the Tablets. I immediately updated the OS from 4.2.2 to 4.4.2 KK and everything seemed fine. I did have one problem that I attributed to the SD Card, my Tablet popped up a msg stating that the SD Card was not accessible and I need to Format it. I tried to Format from within the Tablet and it didn't work, I still couldn't mount it or access it. So I removed it and put it in a little card reader and ran a Complete Format in exFat32 and it worked because I then installed it in the Tablet and it was visible and accessible, so I removed it and tried it in the second Tablet and it seemed fine, for a couple hours. I added some music and videos from my PC and again it seemed fine. But somewhere along the line the SD card is kicked out of the format and becomes Un-Formatted. So I am thinking all you need do is remove the card from the Tablet and do a Full Format on a PC, Windows 7 defaults to exFat32 for the 64GB SDXC card and Fat32 for the 16gb SDHC card and they then appear to be perfectly normal. I don't think the Cards are permanently ruined, even though the Tablet will not access the card until a re-format. What I need to know is why are TWO new Tablets BOTH doing this to TWO NEW SDXC Cards and one SDHC 16gb card that I have had for a long time which has been reliable and Stable until now. Are there other instances of this taking place using KitKat? Is it possible that the Tablets are BOTH Defective? or is it something in the OS that is corrupting the cards, but still allowing me to reformat outside of the Tablet in a card reader? Any Feedback would be appreciated. And it sounds like your card is still serviceable if you do a full format outside of the Tablet, Oh and I am not sure but it seems like the problems begin AFTER the Tablet shuts down and reboots although I am not positive about that. Again, any help is welcome, I need to either resolve this soon or I have to return the Tablets before the window for returning them expires. Sorry for the length of this post.... Dan

I think your problem is related to what base your firmware is. There have been many sdcard problems with official stock 4.4.2 firmware. Try going back to 4.2.2.

Arrrghgh!! I was havoing the same problem after installing the new recovery.
THE ANSWER IS.... while in recovery, goto mount, and mount the damn sdcard!!! Took me a few to figure it out. Jeez.

You must also make sure your sdcard is formatted as fat32 and not exfat. If you format the sdcard in CWM, then it should be the correct format and you will have much less trouble with strange unmounts.
Exfat will appear to work, but it will give you problems.

Locking method?
I can't post links yet, so here is my entire post from androidcentral:
Galaxy S5 - Tmobile - SD 16gb
My SD card was working fine shortly after the upgrade to Lollipop until I did the first restart: the card was no longer recognized. I thought the problem could be with the card, so I backed it up using my laptop (yes, it was readable from the laptop) and did a full format in FAT32. Still no luck. Then, out of nothing, I decided to unlock the phone using the backup password instead of my finger print: immediately I saw in the top of the phone the message "preparing SD card" and it was recognized by the phone. I repeated the test: restarted the phone and unlocked it using the finger print: SD card not available. Then locked the phone and unlocked it using the backup password: the card was recognized. Since then I'm not using any locking method for my phone (will try other methods later).
Has anyone gone through something similar?

[Q] Lollipop - Titanium backup ext_sd error

Hope I'm not repeating a question here. I couldn't find anything in this forum. I just finished updating my international m8 to lollipop ota. After installing titanium backup from the market, I noticed my previous backup on ext_sd are reported as not writable by titanium. I was under the impression that the new android L would rectify this Kitkat issue. Is there any work around for this issue yet? Thanks.

So I found a test version of titanium backup for Lollipop http://bit.ly/1v0njNa. Unfortunately I'm getting Documents crashes when I selected the extsd after switching to documentprovider storage. So I'm still unable to assign the backup directory to my external sd. Any input would be appreciated. Thanks!

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
Thread link forum.xda-developers.com/showthread.php?t=2617921
Working ok.

Thanks for the reply. I did use that solution when I was on 4.4 but lollipop has a different documentprovider solution now. I finally figured out what was happening. The issue isn't with titanium backup up but with how documentprovider was accessing my ext_sd. For some reason the documents will crash if I left ext_sd unnamed. I ended resolving the issue by naming my sdcard and it's been working as expected. Weird little bug in lollipop... In addition to the DNS issue.

Thanks for that solution. I had the same issue.
After naming the SD card using my laptop, the HTC Documents application no longer crashed and I can allow write access to the application (ES fileexplorer in my case.).
I guess it is an HTC bug, the documentsprovider shows the label/name of the ext SD card on the button to be pressed to allow access, and apparently it can't handle an empty SD card name.

SdFix or not SdFix?

Hi,
my H815 is freshly and happily rooted, and i wonder if i have to install SdFix or not.
Do we have to do this on Lillipop?
on Google Play, SdFix says "for kitkat" and don't mention Lollipop.
What do you think?
Thanx for answers

I had to use it for some apps, so I say YES. Lollipop has the same regulations for the external SD like KitKat, so the apps have the same problems.

misteurz said:
Hi,
my H815 is freshly and happily rooted, and i wonder if i have to install SdFix or not.
Do we have to do this on Lillipop?
on Google Play, SdFix says "for kitkat" and don't mention Lollipop.
What do you think?
Thanx for answers
Click to expand...
Click to collapse
I use it as well and it works - I can now save TB backup directly on my external SD :good:

clandes said:
I use it as well and it works - I can now save TB backup directly on my external SD :good:
Click to expand...
Click to collapse
+1

there was this thread some time ago by @TecknoFreak that explained how to fix that by editing the /system/etc/permissions/platform.xml file by hand, no need for an app http://forum.xda-developers.com/showthread.php?t=2524277. he posted this in another thread but i cant remember now where i saw it
having said that, i cant remember if i used TB saving my backups to external before or after i made the change to my xml using the steps from the thread but i am pretty sure it was before. also the LG camera can write to ext_sd so dont know for sure this is needed. plus i just did a reflash of @MicroMod777 xTreme rom so it reset that file and i can still write to my ext_sd with TB and camera
oops...i take back part of this, i just now noticed the notification i got from TB that said my backup failed cause i did not have enough space to write the backup to, but the camera still saves to external
so i must have done the xml edit before i did TB, either way, i dont think you need an app for this. sure it might make it easier, but editing the file is not too bad to tackle either

I downloaded SDFix from Google Play (pretty sure it's the same one I used when KitKat first came out) and it reported that the app wasn't necessary.
EU H815 rooted with the recently released Low Effort Exploit (and not by unlocking the bootloader via LG's Dev site).
TiBu was one of the first apps I installed after rooting earlier this week, and it never had a problem backing up to my ext. SD card.

Midnight_Rider said:
there was this thread some time ago by @TecknoFreak that explained how to fix that by editing the /system/etc/permissions/platform.xml file by hand, no need for an app http://forum.xda-developers.com/showthread.php?t=2524277. he posted this in another thread but i cant remember now where i saw it
having said that, i cant remember if i used TB saving my backups to external before or after i made the change to my xml using the steps from the thread but i am pretty sure it was before. also the LG camera can write to ext_sd so dont know for sure this is needed. plus i just did a reflash of @MicroMod777 xTreme rom so it reset that file and i can still write to my ext_sd with TB and camera
oops...i take back part of this, i just now noticed the notification i got from TB that said my backup failed cause i did not have enough space to write the backup to, but the camera still saves to external
so i must have done the xml edit before i did TB, either way, i dont think you need an app for this. sure it might make it easier, but editing the file is not too bad to tackle either
Click to expand...
Click to collapse
My edits should work just fine for TB backing up on external. I did the same edits to my H811 and works great. I was getting the same error as well and it got fixed after those edits that is just one line missing.
I rather change a line or 2 before installing an app to my phone but that is just me.

Specifically for TitaniumBackup, you just need to go to preferences and when selecting your backup folder, change the storage provider to DocumentProvider storage (Click above the DETECT button) and then navigate to your folder.
Works fine without any fixes.

Charsher47 said:
Specifically for TitaniumBackup, you just need to go to preferences and when selecting your backup folder, change the storage provider to DocumentProvider storage (Click above the DETECT button) and then navigate to your folder.
Works fine without any fixes.
Click to expand...
Click to collapse
Don't get the option to 'protect' backups though if you go this route. Only if you use the default setting with edited platform.xml file.

TecknoFreak said:
My edits should work just fine for TB backing up on external. I did the same edits to my H811 and works great. I was getting the same error as well and it got fixed after those edits that is just one line missing.
I rather change a line or 2 before installing an app to my phone but that is just me.
Click to expand...
Click to collapse
Same here, and this worked perfectly fine on my H815 (SEA version). Now I can actually let GoneMadMusicPlayer edit tags in my music collection.
Thanks :good: