• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root sd mount read only

its not even like its a big deal you can probably use a different app lol i just want to know whats going on haha.

When you unistalled and reinstalled how did you do it? Tib?
 
damn you went all out lol i actually deleted it and got another app. and so far its running smooth. now just gotta change my kernal. downloaded a new rom and its eating battery like no tomorrow
 
Sure the easy solution is use a diff or a diff rom but the easy solution is usually not the most entertaining or rewarding lol.
 
I'm having a similar issue with my evo and google nav. After opening up nav, i'll get a notification that my sd card is read only. If i tap the notification, sometimes it fixes the problem, other times it stays read only. After closing nav, it goes back to normal. What rom are you using? I'm on calkulin's evio 1.8 based rom.
 
im running koni's elite 3. just switched to it then the errors started. it was easier just to ditch the widget and get another one.
 
I got the error again just a bit ago. I guess it's not a big deal as the error goes away after the app closes, but it would be nice to know why.
 
You're welcome for the amusement lol. I actually have two emails from the dev if you prefer his widget we may get it...?
 
I got bored...here is response 1

I've never seen this issue either.
The only time I've seen a SD card goes in read only mode is when there are errors on the card.
So I can imagine a few reasons for this issue:
- The file has reached the file size limit on a FAT16/32 file system, would require history logging every 10 seconds or so for a few month, unlikely though!?
- The file itself is corrupted and each time the app tries to write to it, the OS notices the issue

Here are a few questions that might help understand what's happening:
- Did he purchased the pro version, and might still be running both app logging in the same file!? Note that I do run both on the same file without problems...
- Did he changed the logging rate, 5 minutes is the default and works very well. One minute is the minimum that's actually useful on most ROMs (except CyanonGenMod ROMs which provides mA updates every 10 seconds or so I've heard).
- Is he using a Custom ROM?
- Has he been using the app for long, what's the history file size?
- Without widget, when he starts the app, does the SD card goes read-only too?

In any case, your member could first try to delete the history file if it resolves the issue, next is to backup the SD, format it and start again.
If neither of those works out he can change the location of the file to be on internal storage (NB: history logging should not be set under 1 minute and I recommend leaving 5 minutes in any case!)
To be on the safe side, he/she could also start by clearing the app data, hence starts with clean default settings (logging every 5 minutes)
One last resort is to disable the history logging completely... Only live monitoring will remain active, but the app will not write to the SD card any more.

Note that I suppose each attempt will require re-mounting the SD card in read/write mode...
Note also that the app is written in Java using standard file writer objects, hence nothing special about the file logging
 
and second response...

uninstalling/reinstalling doesn't clear the app data! I've read it somewhere and experienced it too... very weird too!
Note also that history file never gets cleared, it's not part of the app data, it's stored on the SD card only and remain there until manually deleted, so if the file is corrupted/too big/etc, re-installing the app, clearing app data will not do any good.
I've had a few issues with this 'fix permissions', it doesn't seem to always work... At some point a custom ROM kept telling me the UUID was wrongly set and could cause instability... So had to reinstall my ROM from scratch.
Based on your feedback, I can only think about a corrupted history file... Maybe caused by a very low logging rate (which is a very bad idea on the long run).
Also his SD card could be 'broken/damaged' in some ways, where a reformat could (or not) fix it.
Running the app alone should result in the same situation, because when the app starts, it will start logging (if enabled), if not, this might have nothing to do with the app, but relates to the widget framework itself (very very unlikely)...

Did he use some SD tweaks available on the market, to speed up read-times for example?
 
basically i would install his app, see if it does it. then try clearing the data in titanium. if that doesnt work i would delete the history file, should have created a file on your sd card you can look for to delete the log.
 
You must log in or register to reply here.
Back
Top Bottom