Tried firefox for android beta2 today and it freezed my phone, so I uninstall it only to realise that it locked 13MB of my internal memory permanently probably due to bad uninstall. Tried to reinstall it so that I can uninstall it again but it didn't allow me to install again saying that I don't have enough memory (though i still have ~45 MB free internal memory).
Anyone knows where does firefox install to? I couldn't find it in any of the app directory (not in data\app or system\app, nothing in dalvik cache and data\data as well). having 14MB memory locked is really a paint considering how small our milestone memory is.
Please help.
Thanks
en0203 said:
Tried firefox for android beta2 today and it freezed my phone, so I uninstall it only to realise that it locked 13MB of my internal memory permanently probably due to bad uninstall. Tried to reinstall it so that I can uninstall it again but it didn't allow me to install again saying that I don't have enough memory (though i still have ~45 MB free internal memory).
Anyone knows where does firefox install to? I couldn't find it in any of the app directory (not in data\app or system\app, nothing in dalvik cache and data\data as well). having 14MB memory locked is really a paint considering how small our milestone memory is.
Please help.
Thanks
Click to expand...
Click to collapse
bump. please can someone help. thanks
en0203 said:
bump. please can someone help. thanks
Click to expand...
Click to collapse
1.Do you have a recent nandroid backup? that would be a simple fix?
2. What rom and kernel are you using?
3. Is your phone rooted? Probably yes...All the apps go to /system/app, unless you have apps2sd installed
4. If it's not there and it's not in "manage applications" then probably it's a an error of your rom showing erroneous available space.
Hi,
Thanks for your reply.
1) I am using XT720, we don't have nandroid backup tools yet
2) Stock EU rom and kernel for XT720
3) yes, rooted. I am sure it's not in /system/app (mine has got apps2sd)
4) I guess I'll probably need to reflash the rom to get rid of it then. a bit troublesome but no choice I guess.
Something about the firefox is that if you install it you'll find that the space taken up by the firefox is much bigger than the .apk+dalvik cache+data in the normal app installation path. some portion gets installed into somewhere else which nobody knows where. My friend with a Nexus one try to move it to sd but it simply won't move the whole thing because part of it does not install to the /app.
Anyway, thanks for the help. I'll wait another day or two before I flash it to stock again.
Many thanks
en0203 said:
Hi,
Thanks for your reply.
1) I am using XT720, we don't have nandroid backup tools yet
2) Stock EU rom and kernel for XT720
3) yes, rooted. I am sure it's not in /system/app (mine has got apps2sd)
4) I guess I'll probably need to reflash the rom to get rid of it then. a bit troublesome but no choice I guess.
Something about the firefox is that if you install it you'll find that the space taken up by the firefox is much bigger than the .apk+dalvik cache+data in the normal app installation path. some portion gets installed into somewhere else which nobody knows where. My friend with a Nexus one try to move it to sd but it simply won't move the whole thing because part of it does not install to the /app.
Anyway, thanks for the help. I'll wait another day or two before I flash it to stock again.
Many thanks
Click to expand...
Click to collapse
Can you go into recovery? ADB commands actually work as root there.
You also said you have app2sd - I'm guessing the ext version. You can browse around the ext partition if you have something that can read it (like Ubuntu) and delete it from the card as well.
- Look into your /cache partition and delete every download*.apk
- Look into /data/app and look if there is still an apk left
- Look into /data/data and see if a Firefox-folder is located there - delete it!
You can do all this with RootExplorer
Then you should be fixed
Milestone isn't supported. I think I read it somewhere on the mozilla site. There's some known issue logged somewhere
Sent from my Milestone using XDA App
Check if there is any "*.tmp" files under /data/app ?
I was locked some memory due to unsuccessful install of "Pocket Legends", and found out that the apks were stored in both "/cache/downloadfile.apk" and "/data/app/vmxyzxyz.tmp".
A Noobs Guide to Getting Started with a Custom Rom on the Nook Color
So you heard about the nook color. How it's a cheap e-reader that can be pushed to the limit and you are wondering how you can enable this power for yourself. Well you came to the right place!
Table of Contents
1. Why you should NOT use Honeycomb
2. SD or Internal instal
a. SD install
b. internal install
3. Restoring to Stock
4. Other Cool Stuff
5.Issues
6. Conclusion
7. Changelog (Last update 1/10/12)
1. Why you should NOT use Honeycomb
So you've heard about how the Nook Color can run Honeycomb and you are thinking that you want to try it. I mean why not? It's a tablet OS and the Nook is supposed to be turned into a tablet right? Well here's how it is. Honeycomb unlike other versions of Android is not an open source release. That means that developers cannot see how it works and have to reverse engineer basically the entire thing. This leaves you will something that barley runt because of countless missing drivers and many bugs from the SDK simulator. Honeycomb is a very painful and unstable experience. Do not use it. Wait for the next version of Android codename Ice Cream Sandwich to come out. For now use CM7. To check on the progress of CM9 (AKA ICS) check out this thread where you can find the first alpha builds.
2. SD or Internal install
The first decision you need to make is if you want to install CM7 (Android) over your current stock firmware or to run from an SD card.
a. SD Install
The benefit of running from an SD card is that you get to keep your Nook's current stock rom along side your Android install. The downside is that Android will run terribly if you do not use the correct SD card.
When running from an SD card use ONLY a SANDISK CLASS 2 or 4!
Take a look at this thread here for why you need to use a Sandisk:
Instructions for installing to an SD card
b. Internal Install
I recommend you do an internal install just because it is more stable and a lot easier to troubleshoot and upgrade to a newer CM version. If you ever need to return to stock it is very easy (see part 3).
To install to your internal memory follow this guide
Remember if you have a newer Nook that came with stock version 1.2 or above you may want to follow the repartitioning instructions here to have more space available to save files.
3. Restoring to Stock
So something happened and you need to return to stock. You need to make a warranty claim, register you device with BN, or whatever.
Here is what you need to do
When you are done you will have a complete stock Nook to do whatever you want with.
4. Other Cool Stuff
Watch Hulu with a hacked flash app
Make your Nook more Honeycomb like with TransformerBread
5. Issues
Help Facebook keeps force closing!!!!!
Solutions:
1. Use Facebook 1.6 or lower
2. Use tetherGPS lite
3. Use a third party app
Use this thread for help
N64oid won't work!!!!
Starting with N64oid 2.0 and above the new .32 Nook kernel used in CM7 does not work with N64oid.
Solutions:
Use a version of N64oid before 2.0
Use an older version of CM7 without the .32 kernel
Use this thread for help:
6. Conclusion
I hope this guide helped you out. If you think there is anything I should add or you have any questions feel free to comment.
7. Changelog
1/14/11
Restoring to stock guide updated for 1.4.1 zip that will work for people with new touchscreens.
1/10/12
New Guide for restoring to Stock that uses 1.3 and the new clockwork to work on the newer blue dot Nooks.
Removed 1.2 zip as it is no longer needed
Removed "Guide" from Changelog
Changed "Guide Changes" to Changelog in Table of Contents
Added link to CM9 dev thread
12/23/11
Added 1.2 restore zip link
Added Conclusion to table of contents
Good work, kookid,
Comment on 2.b. about re-partition. It is an option, not a must so saying "you need to follow ...." might confuse others.
votinh said:
Good work, kookid,
Comment on 2.b. about re-partition. It is an option, not a must so saying "you need to follow ...." might confuse others.
Click to expand...
Click to collapse
Oh good point. Will change.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Good overview for newcomers.
Will return here when I get my NC in November.
Two thumbs up, maybe this should get stickied.
What about overclocking/undervolting kernels?
OrganizedFellow said:
What about overclocking/undervolting kernels?
Click to expand...
Click to collapse
Overclock/undervolt is included in the CM7.1 kernel.
Overclocking is built in to the CM settings. To undervolt you need to use the Nook Tweaks app.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Reverting to the factory original ROM can be done much easier than the link provided. I would post the link but I have not yet posted enough to provide a link.
BASIC! said:
Reverting to the factory original ROM can be done much easier than the link provided. I would post the link but I have not yet posted enough to provide a link.
Click to expand...
Click to collapse
Could you at least post the name of the thread? I'm always looking for better ways to do things.
---------------------------------
Sent from my LG Optimus V using Tapatalk
BASIC! said:
Reverting to the factory original ROM can be done much easier than the link provided. I would post the link but I have not yet posted enough to provide a link.
Click to expand...
Click to collapse
Link provided by koolkid was for 1.0.1 but I think it was the standard procedure for any other version.
I'm eager to learn a new, better way.
I just substitute the full 1.3 .zip for the CM7 and gaaps .zips when booting with the original install image and it works fine. I recommend everyone who installs CM7 to the eMMC save their original install SD card for future needs and buy a 2nd one for use with CM7. The 1.3 .zip now seems to be missing from the drop box site though so someone will need to repost it. It was linked in this thread: http://forum.xda-developers.com/showthread.php?t=914690&page=29
Thanks for a very useful thread ... even though I already have mine running on CM7 since last month, really grateful for the info regarding the Facebook FC.
I'm still very much a noob at this.
One suggestion for more info regarding an issue which many noobs like me may have: How to expand the partition to use the rest of the SD card. On my 16Gb card, it now has four partitions: Boot, 2x unallocated, and Storage. Using EASUS PartitionMaster, how do I expand the fourth partition ? Do I have to delete the two unallocated ? Any further info regarding this would be very much appreciated !!
If I use App2SD, which partition would those programs go to ? Seeing that I already booted from SD, the Apps are already on the SD, right ? No need to "move to SD" ?
Thanks ahead for the schooling !!
vn33 said:
Thanks for a very useful thread ... even though I already have mine running on CM7 since last month, really grateful for the info regarding the Facebook FC.
I'm still very much a noob at this.
One suggestion for more info regarding an issue which many noobs like me may have: How to expand the partition to use the rest of the SD card. On my 16Gb card, it now has four partitions: Boot, 2x unallocated, and Storage. Using EASUS PartitionMaster, how do I expand the fourth partition ? Do I have to delete the two unallocated ? Any further info regarding this would be very much appreciated !!
If I use App2SD, which partition would those programs go to ? Seeing that I already booted from SD, the Apps are already on the SD, right ? No need to "move to SD" ?
Thanks ahead for the schooling !!
Click to expand...
Click to collapse
For your first question: just right click the 4th partition, select resize and then make sure everything is selected.
For your 2nd question: I'm not exactly sure as I do not use an SD install. Maybe someone else with more SD booting experience can help but what I am thinking is that all of your apps are on the 2nd or 3rd partition but when you use app2SD they get moved to the 4th partition.
---------------------------------
Sent from my LG Optimus V using Tapatalk
votinh said:
Link provided by koolkid was for 1.0.1 but I think it was the standard procedure for any other version.
I'm eager to learn a new, better way.
Click to expand...
Click to collapse
I found a link that I could post:
http://forum.xda-developers.com/showthread.php?t=1054027
The simple complete wipe is near the bottom of the first post.
BASIC! said:
I found a link that I could post:
http://forum.xda-developers.com/showthread.php?t=1054027
The simple complete wipe is near the bottom of the first post.
Click to expand...
Click to collapse
Unfortunately you cannot use the 8 failed boot method if you replace the stock recovery which most do when installing CM. That is why I used the method I did with this guide. It works no matter what is on your internal memory.
---------------------------------
Sent from my LG Optimus V using Tapatalk
BASIC! said:
I found a link that I could post:
http://forum.xda-developers.com/showthread.php?t=1054027
The simple complete wipe is near the bottom of the first post.
Click to expand...
Click to collapse
I'm probably slow but your provided link is for rooting the 1.2/1.3 NC using ManualNooter. It has nothing to do with reverse back to stock ROM.
And, the complete wipe near the bottom of the first post, again, has nothing to do with reversing if currently running custom ROM on eMMC.
A mod should definitely sticky this...most helpful thread I've read in the general forum yet.
Thank you so much
I just got a refurbished Nook Color and after hours of searching and reading I came across your post. This guide is a like a mother-load of good links and clear instructions. Thank you for taking the time to put it together. It has really helped me understand what was needed to get my NC up and running.
This is a really helpful guide for beginner.
I want to ask some thing about the whole workflow. I've used other Android phones to play with rooting and flashing new roms, but NC is quite new to me. So still need to make sure about something.
In this guide, there is nothing about rooting. And when I use CM7 from a SD card, I don't have to do that and already got the su in terminal. So I suppose if I just flash CM onto the eMMC, I'll get root access anyway. I don't have to root it right now in its stock system, right?
-Updated the Restoring to stock guide to use a 1.3 and the newest clockwork it's on Android Central for now but I might move it over here if I get some time.
zhourj said:
This is a really helpful guide for beginner.
I want to ask some thing about the whole workflow. I've used other Android phones to play with rooting and flashing new roms, but NC is quite new to me. So still need to make sure about something.
In this guide, there is nothing about rooting. And when I use CM7 from a SD card, I don't have to do that and already got the su in terminal. So I suppose if I just flash CM onto the eMMC, I'll get root access anyway. I don't have to root it right now in its stock system, right?
Click to expand...
Click to collapse
Nope, no need to root if you are going to flash CM7 because of the ability to boot a custom recovery from an SD card.
Hi.
I have issues here.
I would install market and Astro filemanager.
But I got info that they already was installed.
I cannot see them in the Application->Manage applications
It tells me, that " you don't have any third party apps installed".
I had the idea, that the GT540 is rooted, but obvciously not, as I cannot install apk's using the adb command.
Beside this, I also have this:
process com.android.vending issue.
What can I do?
aalested said:
Hi.
I have issues here.
I would install market and Astro filemanager.
But I got info that they already was installed.
I cannot see them in the Application->Manage applications
It tells me, that " you don't have any third party apps installed".
I had the idea, that the GT540 is rooted, but obvciously not, as I cannot install apk's using the adb command.
Beside this, I also have this:
process com.android.vending issue.
What can I do?
Click to expand...
Click to collapse
You've missed the forum, this should be in General or Themes and Apps forum.
You haven't stated what ROM are you using.
Are you trying to install Astro via Play Store or from apk on sd card?
com.android.vending is a Google Play Store app, has it updated itself or is still Market?
darko94 said:
You've missed the forum, this should be in General or Themes and Apps forum.
You haven't stated what ROM are you using.
Are you trying to install Astro via Play Store or from apk on sd card?
com.android.vending is a Google Play Store app, has it updated itself or is still Market?
Click to expand...
Click to collapse
Sorry for posting a wrong place :-(
I'm not sure what ROM I'm using. It's the dafault one, as it has not been modified, but Don't know. How to see it?.
It's an LG GT540 I use.
Iwould install it from apk on SD card, but due to a reason I don't know, I cannot get adb to work.
It tells me, that device not found.
I have formatted the SD card with FAT32, and now I cannot see the system path.
Bot worth to mention, I'm a newcomer here on Android :crying:
aalested said:
Sorry for posting a wrong place :-(
I'm not sure what ROM I'm using. It's the dafault one, as it has not been modified, but Don't know. How to see it?.
It's an LG GT540 I use.
Iwould install it from apk on SD card, but due to a reason I don't know, I cannot get adb to work.
It tells me, that device not found.
I have formatted the SD card with FAT32, and now I cannot see the system path.
Bot worth to mention, I'm a newcomer here on Android :crying:
Click to expand...
Click to collapse
On android 2.1 adb work only on recovery mode just make a hardreset and everything will be just fine
Don't worry about the wrong forum thing we all learn!
hardspace said:
On android 2.1 adb work only on recovery mode just make a hardreset and everything will be just fine
Click to expand...
Click to collapse
How to set the phone in recovery mode ?.
I have made a hard reset many times.
Code:
VOLUME UP + HOME + SEARCH
It was after such a stunt, that the following occured :angel:
And what is the next to be done now ?.
If it's too much to discuss here, it will be ok, if one will help me direct
-Grift- said:
Don't worry about the wrong forum thing we all learn!
Click to expand...
Click to collapse
Thank you for those nice words
I have learned it, yes!
aalested said:
How to set the phone in recovery mode ?.
I have made a hard reset many times.
Code:
VOLUME UP + HOME + SEARCH
It was after such a stunt, that the following occured :angel:
And what is the next to be done now ?.
If it's too much to discuss here, it will be ok, if one will help me direct
Click to expand...
Click to collapse
For recovery and fastboot look here: http://forum.xda-developers.com/showthread.php?t=1224747
I'm not sure what puzzled me, but now all is working.
I did an factory reset -one of an enormeus lot-, and after all worked again.
Now I can go to Market and do all what I want.
Thanks for the link to recovery and fastboot.
Will save the link for future use.
So for now, thanks for all your comments and great infos.
They are much appreciated
Hi All,
Day by day, another MIUI quirk/challenge... Things that were easy and possible under other phones and stock Android versions seem ever so more challenging under MIUI....
So, I purchased a nice 128GB SD Card to go with the built in storage. Mainly for moving data around, so don't loose it...
However due to Android 4.4 and beyond, Google make it difficult to write access this. However other File Managers and Android versions in past, I've managed to re-enable this. However with this phone, so far I have not found to a way to unlock it yet??
The usual app (FX Explorer) doesn't work, says I can't unlook the root of the SD Card, only individual folders... which it then complains, isn't the root.... (yeah, I know that... you wouldn't let me unlock the root of SD).
I try MIUI Storage settings, but that has nothing in there to unlock it....
I then install Google Files, as strangley a guide says that'll work... it doesn't....
There was then a guide with the stock Xiaomi File Manager to unlock write access to SD Card, yet the options in the guide don't exist in this version. And can't see how allowing access to my Contacts in File Manager and then clearing the settings would fix it anyway?
So now running out of idea's to allow access to SD Card... T'was so simple on other Android devices.....
Cheers, Lister
Update: Seems I am not alone, many have this bug and looks not to be fixed.... or consistently fixed. Very hit and miss....
https://www.reddit.com/r/miui/comments/joxuhi
The plot thickens.... or not, so it seems !!!
So under Developer Settings, there is an options to "Force Write Access to External SD for all Apps" so I have enabled this and it has done..... diddly squat !!!
What's the point of providing an SD Card slot, with no write access...??
Lister
Hi All,
Has anyone had any luck getting an Ext SD Card to be writable between apps....?? As all the usual methods that I know of, and apps (FX) that have worked in the past, don't work.
The OS built in settings don't work, and the hidden Developer Settings to force write access don't work....
So at this point, I am racking my brians why Xiaomi even bothered to include an SD Card slot, as currently its pointless and redundant !!!
I'm having to copy it from the Internal memory, onto PC, then from PC back onto Exteral.... and it's slow as hell and doesn't always work... It's a brand new SanDisk MicroSD purchased from large retail store... So not like its some iffy thing off eBay.
Cheers, Lister
Thats, lets say, weird. i never had that problem, try finding something in the developer options?
if nothing worked, then root your phone i guess
Yeah it's very weird, I've never faced this issue on any of my other phones in the past.... Which have mainly been Samsung's.... S2, S5 and Note 1.... All old and trusty models, had no issues with those phones over the years, they were like TANKS.... just kept on working.
However this phone, I am encountering issue, after issue.... things that worked like stock/standard under normal Android are not working on MIUI.... I can't even get Ringtones to work, just have the 3x ringtones it comes with with no option to add more....
SD Card won't allow me to write at the root of the card, it says create a folder from the root of the card and then make the folder writable. I do that, then the OS complains this isn't standard practice and that I should allow the whole card.... which was what I was trying to do, when it tells me "for my own privacy" not write at the root level... Argghhhhhhhhhhhhhhh !!!!! lol
I am trying not root the phone itself at the moment, as this is the most moddern and recent phone ever purchased and trying to run it as stock with banking apps.... But if pushed, I may try rooting and try masking root at a later date....
But for now, if there is any official non-root ways of making the SD Card work, would be grateful...
Cheers, Lister
Lister Of Smeg said:
Yeah it's very weird, I've never faced this issue on any of my other phones in the past.... Which have mainly been Samsung's.... S2, S5 and Note 1.... All old and trusty models, had no issues with those phones over the years, they were like TANKS.... just kept on working.
However this phone, I am encountering issue, after issue.... things that worked like stock/standard under normal Android are not working on MIUI.... I can't even get Ringtones to work, just have the 3x ringtones it comes with with no option to add more....
SD Card won't allow me to write at the root of the card, it says create a folder from the root of the card and then make the folder writable. I do that, then the OS complains this isn't standard practice and that I should allow the whole card.... which was what I was trying to do, when it tells me "for my own privacy" not write at the root level... Argghhhhhhhhhhhhhhh !!!!! lol
I am trying not root the phone itself at the moment, as this is the most moddern and recent phone ever purchased and trying to run it as stock with banking apps.... But if pushed, I may try rooting and try masking root at a later date....
But for now, if there is any official non-root ways of making the SD Card work, would be grateful...
Cheers, Lister
Click to expand...
Click to collapse
Yeah the root of the sd card is not allowed a lot of phones, i have a lumia 530 (windows phone) and don't have full access, but my huawei p smart 2019 has root of the sd
Hi All,
Just gets better and better..... NOT !!!
Xiaomi why the fook have you included an SD Card reader to your phones, and Google why do you allow the user to VIEW but NOT use additional storage? Might as well remove the SD Card slot and add a 3rd SIM slot.
Then rebrand Android OS to Google-iOS, and continue to lock this sh*t down !!! Utterly pointless....
Google Issue Tracker
issuetracker.google.com
So it seems this is a known issue since Android 11, getting worse in 12 and dread to think by time of 13. So many unhappy and angry users out there over Googles latest changes... So Google lock their DocsUI storage down to secure their devices, thus users are installing unknown apks to try and re-enable it or ROOT their phones to regain the feature back. Therefore reversing what Google are trying enforce... lol
Pity I purchased a 128GB SD for this phone, might as well slamed in a 2GB for all the use it'll get...
Lister
Hi All,
<< Credit, where credit is due... as no other solution all over the web worked... other than below >>
Thanks to @xetc , with regards to this post... Ext SD Card write access has been resolved and can now make use of my 128gb Micro SD Card again... Yaaaaaaay....
Fault: If you're running Android 11, or higher. You will now find you cannot write/make use of your External MicroSD Card as Google have now blocked this. Android 10 is not as restricted, and Android 9 or below is not affected by this issue.
Solution: Download and use FX Explorer v8.0.3.0
To re-summarize steps...
1) If you already have FX Explorer installed, remove it.
2) Then download specifically FX Explorer v8.0.3.0 from your usual source.
3) Then click the top right corner, and select [Enable Write Access] at the bottom of the menu and follow prompts.
4) Once completed, reboot your phone.
5) Now test, to make sure you can write between internal to external, if all good, proceed to update.
6) Now grab the latest version of FX Explorer, once updated, re-check that you still have write access.
Happy days....
Lister
hmm
Lister Of Smeg said:
Hi All,
<< Credit, where credit is due... as no other solution all over the web worked... other than below >>
Thanks to @xetc , with regards to this post... Ext SD Card write access has been resolved and can now make use of my 128gb Micro SD Card again... Yaaaaaaay....
Fault: If you're running Android 11, or higher. You will now find you cannot write/make use of your External MicroSD Card as Google have now blocked this. Android 10 is not as restricted, and Android 9 or below is not affected by this issue.
Solution: Download and use FX Explorer v8.0.3.0
To re-summarize steps...
1) If you already have FX Explorer installed, remove it.
2) Then download specifically FX Explorer v8.0.3.0 from your usual source.
3) Then click the top right corner, and select [Enable Write Access] at the bottom of the menu and follow prompts.
4) Once completed, reboot your phone.
5) Now test, to make sure you can write between internal to external, if all good, proceed to update.
6) Now grab the latest version of FX Explorer, once updated, re-check that you still have write access.
Happy days....
Lister
Click to expand...
Click to collapse
Btw, on 4), I didn't need a reboot on A10, just enabled write access, then updated. Your mileage may vary, though, with A11+.
Lister Of Smeg said:
Hi All,
Day by day, another MIUI quirk/challenge... Things that were easy and possible under other phones and stock Android versions seem ever so more challenging under MIUI....
So, I purchased a nice 128GB SD Card to go with the built in storage. Mainly for moving data around, so don't loose it...
However due to Android 4.4 and beyond, Google make it difficult to write access this. However other File Managers and Android versions in past, I've managed to re-enable this. However with this phone, so far I have not found to a way to unlock it yet??
The usual app (FX Explorer) doesn't work, says I can't unlook the root of the SD Card, only individual folders... which it then complains, isn't the root.... (yeah, I know that... you wouldn't let me unlock the root of SD).
I try MIUI Storage settings, but that has nothing in there to unlock it....
I then install Google Files, as strangley a guide says that'll work... it doesn't....
There was then a guide with the stock Xiaomi File Manager to unlock write access to SD Card, yet the options in the guide don't exist in this version. And can't see how allowing access to my Contacts in File Manager and then clearing the settings would fix it anyway?
So now running out of idea's to allow access to SD Card... T'was so simple on other Android devices.....
Cheers, Lister
Click to expand...
Click to collapse
I changed my SD card to another version and my problems were fixed... I don't know if it will help others bud I now associate the problem with my SanDisk as it is not working in my other Redmi
Be aware that when swapping cards, even if you had previously granted card write access, you'll get into the same problem again with the new card. Is it related it to FX not relying on system file transfer app to handle permission, but doing it on its own, instead?
Equally, bookmark links, which are linked to the card's individual path (/####-####/), once you swap card, won't work anymore, either.
Unfortunately, seems none of these and other reported issues seem will ever be fixed, so maybe it's time to move on...
Btw, wonder if this still works...?: NextApp SDFix
Lister Of Smeg said:
Hi All,
<< Credit, where credit is due... as no other solution all over the web worked... other than below >>
Thanks to @xetc , with regards to this post... Ext SD Card write access has been resolved and can now make use of my 128gb Micro SD Card again... Yaaaaaaay....
Fault: If you're running Android 11, or higher. You will now find you cannot write/make use of your External MicroSD Card as Google have now blocked this. Android 10 is not as restricted, and Android 9 or below is not affected by this issue.
Solution: Download and use FX Explorer v8.0.3.0
To re-summarize steps...
1) If you already have FX Explorer installed, remove it.
2) Then download specifically FX Explorer v8.0.3.0 from your usual source.
3) Then click the top right corner, and select [Enable Write Access] at the bottom of the menu and follow prompts.
4) Once completed, reboot your phone.
5) Now test, to make sure you can write between internal to external, if all good, proceed to update.
6) Now grab the latest version of FX Explorer, once updated, re-check that you still have write access.
Happy days....
Lister
Click to expand...
Click to collapse
thank you also @xetc for reporting the fix first. I was experiencing this on my secondary phone with LineageOS 17.1/ Android 10.
@tliebeck can you revisit the v. 8.0.3.0 code and re-implement the way you enabled media card write access in that version back into the current version? Obviously something got twisted (and has been ever since v. 8.0.3.0 +)
Above all, thank you for your app !!
Not sure why to use FX Explorer. I use Total Commander and it works to the ext SD card fine. (NOTE: Be aware that if you update to the 3.33 version or higher, you will lose the ability to install apps manually from the SD card. Blame Google! You can solve this by signing it with your favorite app (like apk-signer) so Play won't keep telling you there is an update to the program.
Lister Of Smeg said:
Hi All,
<< Credit, where credit is due... as no other solution all over the web worked... other than below >>
Thanks to @xetc , with regards to this post... Ext SD Card write access has been resolved and can now make use of my 128gb Micro SD Card again... Yaaaaaaay....
Fault: If you're running Android 11, or higher. You will now find you cannot write/make use of your External MicroSD Card as Google have now blocked this. Android 10 is not as restricted, and Android 9 or below is not affected by this issue.
Solution: Download and use FX Explorer v8.0.3.0
To re-summarize steps...
1) If you already have FX Explorer installed, remove it.
2) Then download specifically FX Explorer v8.0.3.0 from your usual source.
3) Then click the top right corner, and select [Enable Write Access] at the bottom of the menu and follow prompts.
4) Once completed, reboot your phone.
5) Now test, to make sure you can write between internal to external, if all good, proceed to update.
6) Now grab the latest version of FX Explorer, once updated, re-check that you still have write access.
Happy days....
Lister
Click to expand...
Click to collapse
The old 8.0.3.0 from December 2020 is now a 7-day trial app, and step #3 does not produce any "enable write access" from the top right hamburger menu. I enabled root/developer access in its settings but no difference.
EDIT: though I see no "enable write access" anywhere the app, I can read and write to it, and send files from it to Drive, the last 2 things fail on my RN11. Both are on custom ROMs on A13. So, this has to be a developer's issue in the ROM, OR something with the card itself. I will keep testing to see what I can find.
i.e. this no longer works (NOTE: this might just be an SD card issue. I am able to write to and send files from an external SD on a different ROM on a different A13 phone - Redmi Note 10 Pro - without any permissions stalls at all using Total Commander 3.31, for example.)
xetc said:
Be aware that when swapping cards, even if you had previously granted card write access, you'll get into the same problem again with the new card. Is it related it to FX not relying on system file transfer app to handle permission, but doing it on its own, instead?
Equally, bookmark links, which are linked to the card's individual path (/####-####/), once you swap card, won't work anymore, either.
Unfortunately, seems none of these and other reported issues seem will ever be fixed, so maybe it's time to move on...
Btw, wonder if this still works...?: NextApp SDFix
Click to expand...
Click to collapse
Nope. It produces an error. "Platform permission file is invalid. no groups specified in WRITE_EXTERNAL_STORAGE"
Sheist! said:
The old 8.0.3.0 from December 2020 is now a 7-day trial app, and step #3 does not produce any "enable write access" from the top right hamburger menu. I enabled root/developer access in its settings but no difference.
i.e. this no longer works (NOTE: this might just be an SD card issue. I am able to write to and send files from an external SD on a different ROM on a different A13 phone - Redmi Note 10 Pro - without any permissions stalls at all using Total Commander 3.31, for example.)
Click to expand...
Click to collapse
Hi @Sheist! ,
All versions/editions of FX Explorer are considered a Trial edition when first installed... You can enable full features for a 7 - 14x day trial to which it reverts back to limited features. You only miss out on the bonus, networking/app management and few extra controls/filesystem features.... All the core Explorer features are still there...
This method was correct and accurate at the time of testing, which I believe I was on Android 11, as I don't think A12 was around at the time. Since upgraded to A12 afterwards it has still kept write access to the SD Card enabled after the hack.
I've not tried this method on A13 yet, as I am still on stock rom. However, each release of Android, from version 10 upwards keep tweaking SD Card usage, and restricts access to it more and more... So A13 could well have issues, don't know.
Personally, when I tried Total Commander back on A11, I couldn't get it to work at all (despite reading a guide somewhere) saying to use this. I tried all the various apps out there, one even suggested using the MiExplorer. No method worked at all, apart from that very specific release of FX Explorer, and when tried worked like a charm. As it always has done since Android 4.4x when Google first started messing around with SD Cards. I believe Android developers were asked to remove such features from their File Manager apps, hence why after 8.0.3.0 this feature disappeared.
There was a method briefly, using Googles own "Files" app, known as packagename "My Documents" or something like that... This feature only worked on Android 11, and had limited access when enabled. However as this is often a system app, and without root... Trying to disable, debloat, replace this app... this method also was fiddly and didn't work.... the only sucess that worked for me was what was mentioned above.
I tried practically everything, and was at the point of giving up and annoyed I wasted money on a 128GB SD card not to be used... until I stumbled on the above. Relieved it worked, and thought if it helps others in similar position, share the info... as I read pages and pages (forums/Googles own documentation) on how its disabled, how it no longer works, workarounds that didnt work... I believe it should still work for A11, and poss A12 roms (does via upgrade), however not personally tested on A13.
Cheers, Lister
Lister Of Smeg said:
Hi @Sheist! ,
All versions/editions of FX Explorer are considered a Trial edition when first installed... You can enable full features for a 7 - 14x day trial to which it reverts back to limited features. You only miss out on the bonus, networking/app management and few extra controls/filesystem features.... All the core Explorer features are still there...
This method was correct and accurate at the time of testing, which I believe I was on Android 11, as I don't think A12 was around at the time. Since upgraded to A12 afterwards it has still kept write access to the SD Card enabled after the hack.
I've not tried this method on A13 yet, as I am still on stock rom. However, each release of Android, from version 10 upwards keep tweaking SD Card usage, and restricts access to it more and more... So A13 could well have issues, don't know.
Personally, when I tried Total Commander back on A11, I couldn't get it to work at all (despite reading a guide somewhere) saying to use this. I tried all the various apps out there, one even suggested using the MiExplorer. No method worked at all, apart from that very specific release of FX Explorer, and when tried worked like a charm. As it always has done since Android 4.4x when Google first started messing around with SD Cards. I believe Android developers were asked to remove such features from their File Manager apps, hence why after 8.0.3.0 this feature disappeared.
There was a method briefly, using Googles own "Files" app, known as packagename "My Documents" or something like that... This feature only worked on Android 11, and had limited access when enabled. However as this is often a system app, and without root... Trying to disable, debloat, replace this app... this method also was fiddly and didn't work.... the only sucess that worked for me was what was mentioned above.
I tried practically everything, and was at the point of giving up and annoyed I wasted money on a 128GB SD card not to be used... until I stumbled on the above. Relieved it worked, and thought if it helps others in similar position, share the info... as I read pages and pages (forums/Googles own documentation) on how its disabled, how it no longer works, workarounds that didnt work... I believe it should still work for A11, and poss A12 roms (does via upgrade), however not personally tested on A13.
Cheers, Lister
Click to expand...
Click to collapse
The problem is I have other apps that need to write to the SD and at this point they started failing. I don't suspect A13, as CherishOS does not have this issue on RN10P, OR the SD card I am using on that RN10P phone is error-free. My card would not read in the crDroid recovery in my RN11 UNTIL I formatted it in Windows with NTFS. Even formatting in the phone in exFat gives an exFat error in the incorporated crDroid recovery! This is probably still some issue with my card or its formatting, as I don't see noise on this issue from other users. My external SD was working fine for my write/copy-to apps on A13 until I fixed the issue getting it to read in crDroid recovery, which oddly I don't even need anymore! (successfully installed TWRP to ramdisk now). I need to reformat back to exFat and see where I am. If good, then I will reply again.
Lister Of Smeg said:
Hi @Sheist! ,
All versions/editions of FX Explorer are considered a Trial edition when first installed... You can enable full features for a 7 - 14x day trial to which it reverts back to limited features. You only miss out on the bonus, networking/app management and few extra controls/filesystem features.... All the core Explorer features are still there...
This method was correct and accurate at the time of testing, which I believe I was on Android 11, as I don't think A12 was around at the time. Since upgraded to A12 afterwards it has still kept write access to the SD Card enabled after the hack.
I've not tried this method on A13 yet, as I am still on stock rom. However, each release of Android, from version 10 upwards keep tweaking SD Card usage, and restricts access to it more and more... So A13 could well have issues, don't know.
Personally, when I tried Total Commander back on A11, I couldn't get it to work at all (despite reading a guide somewhere) saying to use this. I tried all the various apps out there, one even suggested using the MiExplorer. No method worked at all, apart from that very specific release of FX Explorer, and when tried worked like a charm. As it always has done since Android 4.4x when Google first started messing around with SD Cards. I believe Android developers were asked to remove such features from their File Manager apps, hence why after 8.0.3.0 this feature disappeared.
There was a method briefly, using Googles own "Files" app, known as packagename "My Documents" or something like that... This feature only worked on Android 11, and had limited access when enabled. However as this is often a system app, and without root... Trying to disable, debloat, replace this app... this method also was fiddly and didn't work.... the only sucess that worked for me was what was mentioned above.
I tried practically everything, and was at the point of giving up and annoyed I wasted money on a 128GB SD card not to be used... until I stumbled on the above. Relieved it worked, and thought if it helps others in similar position, share the info... as I read pages and pages (forums/Googles own documentation) on how its disabled, how it no longer works, workarounds that didnt work... I believe it should still work for A11, and poss A12 roms (does via upgrade), however not personally tested on A13.
Cheers, Lister
Click to expand...
Click to collapse
I reformatted in the phone again (exFat) and all apps work fine again to/from the external SD card. I am on TWRP so I don't care about the installed crDroid recovery issue anymore. (A13, crDroid 9.3, TWRP 3.7.0_12-0)