I can't seem to locate the directory folder that the new firefox app downloads to. anyone?
Nevermind, it goes right to the sdcard, no folder. I didn't see the files because the downloads failed...
can't seem to get the download folder to change.
I went into:
about:config
created a new string: browser.download.dir
set the value to: /mnt/extSdCard/Downloads/
Restarted Firefox
But still the downloads go into the sdcard/downloads
I've also tried:
/extSdCard/Downloads/
/sdcard/
/extSdCard/
/mnt/sdcard
none of these have any effect.
Any ideas?
Bump:beer:
Sent from my SGH-I747M using Tapatalk 2
Im also looking for changing my dl directory. It have work once for me when modifying the "browser.download.folderList" after creating the browser.download.dir string. But after reboot of firefox the next dl will go back again to the sdcard.
Wonder if anyone else could tell how to do it
creating a new string is a good step for changing your dl directory. But you should also add this step to make it work.
Modify the value of "browser.download.folderList" from 1 to 2
Thats it!!
Click to expand...
Click to collapse
When editing your old posts, try not to delete the original information that could have been useful to others.
People won't have known what value to put into the string.
Sent from my SGH-I747M using Tapatalk 2
I hate managing folders so now I use directory bind which allows me to bind two folders together. Basically you create another downloads folder on your external sd card and use directory bind to "bind" them. Checkbox to transfer contents and your downloads (source) folder will be dumped into the empty folder you've created automatically (destination must be empty when checking the box). When altering files in either downloads folder, the changes appear in both. When you look at storage, the original source folder is not calculated into your used internal storage amount even though every other app sees files in there (since that would defeat the purpose). I use it for my downloads, camera and several apps and game folders not designed to be pushed to SD. Instead of continuously resetting app download destinations, I sit back and relax knowing every app downloads to the proper place (minus the rogues who think they deserve their own folder lol). When flashing a new ROM, simply unbind everything first and disable autostart, backup with titanium backup, after restore, you should be good (depending on your new version of android in which case you may need to adjust some settings). If setting up from scratch again, assuming your working folder structure is still in tact, you can bind again without ticking the box (since the files are in their proper place and a transfer is no longer necessary).
You can get it here, it looks like it hasn't been updated in a while, but I've tested it from Android 4.0 through 4.2.2 and it's perfect (settings adjustments will likely be required): http://forum.xda-developers.com/showthread.php?t=1410262
Hi everyone, was a solution found to that still issue? I tried to move the default download folder to the ext SD card with settings into about:config, I changed as well the "browser.download.folderList" value to 2 and add a "browser.download.defaultFolder" string, but everything failed, please does someone know what to do? Or is there another setting menu or mod/Exposed module to achieve this..?
Thanks in advance for the help!
May I Taste said:
Hi everyone, was a solution found to that still issue? I tried to move the default download folder to the ext SD card with settings into about:config, I changed as well the "browser.download.folderList" value to 2 and add a "browser.download.defaultFolder" string, but everything failed, please does someone know what to do? Or is there another setting menu or mod/Exposed module to achieve this..?
Thanks in advance for the help!
Click to expand...
Click to collapse
Use this config (I am assuming you're on 4.4 and have used SDFixer)
SeraphSephiroth said:
Use this config (I am assuming you're on 4.4 and have used SDFixer)
Click to expand...
Click to collapse
Hi, thanks for your help, but it still don't work for me. What I don't understand is that the path can be whether
/storage/sdcard1/Download
or
/ext_card/Download
Maybe you know why? I'm running CM11 nightlies (4.4.4) on Xperia Z2
May I Taste said:
Hi, thanks for your help, but it still don't work for me. What I don't understand is that the path can be whether
/storage/sdcard1/Download
or
/ext_card/Download
Maybe you know why? I'm running CM11 nightlies (4.4.4) on Xperia Z2
Click to expand...
Click to collapse
With a r/w sd? Use a root explorer to find the path to the r/w sd
I'm very busy and sorry not to say anything for long but thank you much for your answer and help.
My path is correctly pointing the SD, I checked carefully the settings and got no success. Then suddenly Firefox began to write on ext sd, but still this is only sometimes! I tried to see if the files type or size had something to do with that behavior but it seems to be just erratic..
It actually seems that it's the "Flash Video Downloader" module who sends files into the internal storage regardless of the browser settings..
Related
Hey everyone, I have successfully made a few ROMS for myself (using the DSIXDA HTC Android ROM kitchen v 1.00). I am making a ROM for the HTC Evo.
I know how to do most of it, I have managed so far:
To add my own ringtones
To add my own notification sounds
To set the default ringtone, notification, and change the default wallpaper
Add a theme to my ROM
But there is a few questions I have. I have Googled, looked around on here, and done what I can to find the answers but I am so far unsuccessful.
My first question: Ok, I know that the default wallpapers reside in the system/customize/resource directory. I have attempted to replace the wallpaper (and small preview) wallpapers with my own custom ones. I tried using Paint.net for Windows to resize to the same dimensions as the default wallpaper. For example, to replace htc_wallpaper_01.jpg, I edited a 960x800 wallpaper to have the same size and name (everything the same) and changed htc_wallpaper_small_01 with a matching 80x60 smaller version of the new graphic. I have found sometimes it works, but if I do a few using the method mentioned above, the ROM fails to load up. Can someone help and explain why?
Question 2: I am trying to place the removed apps automatically on the SD Card. I made a "sdcard" folder in the root directory of my ROM. I tried editing the update.zip to include copy_dir PACKAGE:sdcard /sdcard and when I do a check for errors I get none, yet when I try and install the ROM it gives me the "E:syntax error in update script" meaning I am not doing it right. I tried doing it the same way Fresh did it and it also threw me the same error.
So can anyone please tell me how to do this? I know I am close with both and I have tried dissecting other ROMS to see how they did it but I cannot figure it out.
First question:
It could be many possibilities. Maybe not enough room on system, file names not matching, etc...
Try each png on seperate flashes to find the culprit.
*The best way to find out for sure is to use "adb logcat" on boot. This tells you all your errors the OS has.*
Second question:
Im not understanding what your trying to do?
Root of a rom is /
sdcard is mounted to a folder on /
If you want to store the apk on sdcard then,
the proper code to install in /sdcard from update.zip:
Code:
copy_dir PACKAGE:sdcard SDCARD:
If this is not what your asking please explain to me what your asking.
RichieDaze said:
First question:
It could be many possibilities. Maybe not enough room on system, file names not matching, etc...
Try each png on seperate flashes to find the culprit.
*The best way to find out for sure is to use "adb logcat" on boot. This tells you all your errors the OS has.*
Second question:
Im not understanding what your trying to do?
Root of a rom is /
sdcard is mounted to a folder on /
If you want to store the apk on sdcard then,
the proper code to install in /sdcard from update.zip:
Code:
copy_dir PACKAGE:sdcard SDCARD:
If this is not what your asking please explain to me what your asking.
Click to expand...
Click to collapse
Thank you RichieDaze for the response.
You mentioned png., but all the ROMS I have seen have the wallpaper in .jpg format. I was just wondering if there was a certain size they have to be (I mimic the exact size of the default ones).
I think I got this part worked out by doing exactly that, installing 1 at a time until I find the culprit.
For question 2: Thanks to using the DSIXDA kitchen, I cannot use updater.script, which seems to be the way ROM makers like Calkulin, Hero_over, and other have used to set their removed apps to automatically copy on to the SD card when you install the ROM.
I have to use update.script instead, and when I try and do it using that I run into an error.
What I am trying to is remove the usual bloat from the ROM, but copy the removed apps so that users can have the option of installing them if they use any of them.
You are answering my question and are on the right track to helping me. I will try to add that (the way you wrote it out) and see what happens to my update.script.
Thank you very much for your help, greatly appreciated and please let me know if there is some other way to do this if you are aware of any or if someone is using update.script instead of updater.script.
Here is the correct way to use root explorer for manually replacing system files:
1. Mount the system as r/w (read/write) per the top right corner. Navigate to the file that you plan to replace (e.g., system/framework/framework.jar).
2. Copy (not move) the file and paste it somewhere on your SD card (internal or external, doesn't matter - as long as you can locate it in case you need to put it back). Rename the file you just pasted, but very subtly. For example, when renaming framework.jar, I would only throw something in front of the file name, such as "Backup - framework.jar", so I can easily distinguish it from the new file if I put them in the same spot.
3. NANDROID BACKUP!
4. Download/put on your sd card (whatever you do) the new file that you want to replace the old one with.
5. Move the new file to /system (not in a subfolder yet). Here you will change the permissions, which is crucial to avoid FCs and problems. In root explorer, you would long press the file, press permissions, and set them to whatever the old file's permissions are. This may require going to verify what they are before starting this step. For example, in a lot of cases, the permissions will be RW-R-R. In Root Explorer, this would mean checking the first two boxes on the first line and only the first box on the next two lines. In any situation, confirm that the permissions you see after you've changed them (right below the file name) match exactly what you're replacing.
6. Ensure that your new file is correctly named to exactly what it is replacing (case actually matters) and double check the permissions.
7. Move your new file to the folder, root explorer will ask if you want to replace the file. Confirm.
8. Back out of root explorer and immediately reboot.
No force closes, no problems .
It may seem like a lot to someone who doesn't do it often but for me, I actually do this method faster than any other and fly through it every time. I got tired of seeing people explain ways to use Root Explorer which result in bootloops, FCs, etc. without fail. So, I decided to put an end to it.
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Audiochild said:
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Toggle "Mount R/W" button at the top.
Audiochild said:
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Sounds like you need to mount \system as read-write. There is a button in the upper right corner of root explorer to mount
Sent from my SGH-I777 using XDA App
Thanks wonner and kbilly70! That was the issue
Awsome. Bookmarked!
thanks for the awesome guide. worked great for me!
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
kZard said:
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
Click to expand...
Click to collapse
Those are only for flashing purposes. Not needed if you're not flashing it. You only need to pull everything besides that folder and place them appropriately.
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Edgarhighman said:
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Click to expand...
Click to collapse
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Simba501 said:
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Click to expand...
Click to collapse
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Edgarhighman said:
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Click to expand...
Click to collapse
If the apk is compatible, it will work. At no point should you get an "application not installed" prompt, unless you attempted to manually install it at some point. If it wouldn't work, it just wouldn't appear in the app drawer: no prompt.
I guess this should be mentioned in the OP, but some times, clearing data of the application may be necessary after finishing. Usually a force stop at the most will allow you to see changes (which is why the steps include a reboot). You've piqued my interest. Post the files of question and I'll see if they work on my device. There was a similar issue someone else was having; I told him to redownload the apk and that was the problem. Some kind of botched file/download.
Sent from my Galaxy S II (i777)
can you edit or create new folders in the /sys directory?
mikoal said:
can you edit or create new folders in the /sys directory?
Click to expand...
Click to collapse
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Simba501 said:
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
dsmboost said:
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
Click to expand...
Click to collapse
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Simba501 said:
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
Ah okay, I was referring to ES file explorer, which can modify other files in that directory.
thanks to you both!
Hi, I'm having a strange problem with the folders on TouchWiz. After I've filled some apps into a folder which i created, say 4 apps in total for example, and they are arranged in the order 1,2,3,4 (from left to right). But after i reboot the phone, The apps in the folders rearrange themselves in the opposite order 4,3,2,1 (from left to right). In short, the apps in the folders rearrange themselves in the reverse order everytime i reboot my phone. Any idea on how to fix this issue? Any help will be greatly appreciated.
SGS-II said:
Hi, I'm having a strange problem with the folders on TouchWiz. After I've filled some apps into a particular folder which i created, say 4 apps in total for example, and they are arranged in the order 1,2,3,4 (from left to right). But after i reboot the phone, The apps in the folders rearrange themselves in the opposite order 4,3,2,1 (from left to right). In short, the apps in the folders rearrange themselves in the reverse order everytime i reboot my phone. Any idea on how to fix this issue? Any help will be greatly appreciated.
Click to expand...
Click to collapse
I'm sure u can see an order there or?
So f.ex. before reboot it's sorted by time from input (newest to old)
After reboot it's sorted by f.ex. name? PLS check this first.
CHEERS
What is f.ex. ? Folder extension?
What I mean is that I've created this folder called "News" then i started to drag apps into the folder, Pulse followed by Time Mobile followed by Engadget. So now the apps are in that order in that "News" folder. Then i reboot my phone, and the apps inside the folder are now arranged in the order Engadget followed by Time Mobile followed by Pulse. In short, the apps reverse their arrangement WITHIN the folder everytime i reboot the phone. And yes, the order of apps is sorted by time from input into the folder. Before reboot, oldest to newest. After reboot, newest to oldest. The order gets reversed with every reboot of the phone.
The folders themselves don't have auto rearrange problem, same goes for the apps outside the folders. They remain in the same position before and after reboot.
I hope I've made myself clearer now.
Bump. Anyone has any solution?
SGS-II said:
Bump. Anyone has any solution?
Click to expand...
Click to collapse
f.ex. : for example
hmm so for me listen logical.
News folder: news to old
Sure while creating it, it's in other way.
So Maybe u find an app which helps to create folder,
but stock folder can't be changed especially if they are created from app?!
CHEERS
Hannibal226 said:
f.ex. : for example
hmm so for me listen logical.
News folder: news to old
Sure while creating it, it's in other way.
So Maybe u find an app which helps to create folder,
but stock folder can't be changed especially if they are created from app?!
CHEERS
Click to expand...
Click to collapse
No offense but i don't understand a thing you typed.
I am using stock ROM so my folders are created using the stock folders app which comes together with the standard default TouchWiz launcher.
This is how i create folders: (Application Tray > Menu > Edit > Drag icons into "Add folder")
Folders can be renamed. After the folder is created (by default it will be named as "Folder 1") you can just open up the folder and at the top of the folder which says "Folder 1" you tap and hold it for about 2 seconds and the system will prompt you to rename the folder.
Please try Menu > Save after changing apps or folder location.
Sent from my GT-I9100 using xda premium
dragon135 said:
Please try Menu > Save after changing apps or folder location.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks it worked for me. Not sure if it's because of your method or the firmware version (i recently upgraded from 2.3.3 to 2.3.6) but anyway it's fine now.
So I repartitioned my media and storage drives yesterday, and although I did have a few problems (post #156-158) I finally managed to repartition and proceeded mounting the drives in 1.4.1 rooted B&N. Also checked if they worked via usb to computer which they did. I then decided that I wanted to try cm7 today and installed it flawlessly. Only problem is that now my newly resized 10GB internal media partition don't show up. So tried installing the;
[CM7][GB] Soft-mod RibbonICS ROM by veronica, but still no change.
In the storage settings i've tried to mount the
Additional storage/mnt/sdcard/_internalSD but doesen't work and thats probably also just the folder I created myself as instructed in the soft-mod.
So yeah I'm wondering if I can only use the extended media part in stock rooted B&N or if its got to do with the problems I had with the process. Or mayb I just need to mount the media drive somewhere?
Please help
Went into adb-shell in CWM and checked via the p command if the media drive was there which is was
(looked like this: 10 1611MB 11.6GB 9989MB fat32 media msftres)...so it really should work.....shouldn't it?
Edit: actually the above is not entirely correct: I have found my media partition in the file browser now but its just not really accessible it seems. Is it just not mounted or what?
Included in the soft-mod for cm7 is also an application called multi-mount sd lite which should help with this but it force-closes on me even after i fix permissions need help with this..
nook tablet cm7 can not access internall sd
Hi
I loaded cm7 onto my nook tablet 16g internal SD using your latest Zip and it worked like a charm. Thank everybody.
only problem I have is that I can't access the internal SD from my windows computer. It accesses the external one fine but not the internal one.
can download app into internal via web and brows around it.
It doesn't seem to be mounted for external USB access.
Can anyone help with this?
Thanks Martyn
There's a typo in two lines of the build.prop. Described here: http://forum.xda-developers.com/showthread.php?t=1540272&referrerid=4611244
But the link to the corrected build.prop there doesn't work! There's a good link further down the thread...but I attached mine here if you want to use it.
Just download to the root of your removable sdcard and install it from CWM. Or extract it and copy it to /system with your favorite file explorer to overwrite the "typo" version.
EDIT: by "mine" I mean my copy of Celtic's.
OOPS!
Sorry. My reply above was to kingtechmartyn, not the OP domiel...didn't mean to hijack the thread.
Very sorry.
There's a typo in two lines of the build.prop. Described here: http://forum.xda-developers.com/showthread.php?t=1540272&referrerid=4611244<br />
<br />
But the link to the corrected build.prop there doesn't work! There's a good link further down the thread...but I attached mine here if you want to use it.<br />
Just download to the root of your removable sdcard and install it from CWM. Or extract it and copy it to /system with your favorite file explorer to overwrite the "typo" version.<br />
<br />
EDIT: by "mine" I mean my copy of Celtic's.
Click to expand...
Click to collapse
Just remember when changing build.prop to always make a backup of the original so if you want to revert you can.
Sent from my Nook Tablet using xda premium
I don't know if its specific to root explorer or not, but whenever I modify a build.prop that I have navigated to via root explorer, it automatically adds a .bak extension to the original build.prop file.
for an edit of build.prop, be sure to use the correct edit tool which places a 'line feed' at the eol and not a 'carriage return and line feed'.
hth.
Cubanluke88 said:
I don't know if its specific to root explorer or not, but whenever I modify a build.prop that I have navigated to via root explorer, it automatically adds a .bak extension to the original build.prop file.
Click to expand...
Click to collapse
Normal
Cubanluke88 said:
I don't know if its specific to root explorer or not, but whenever I modify a build.prop that I have navigated to via root explorer, it automatically adds a .bak extension to the original build.prop file.
Click to expand...
Click to collapse
you are right, normally a backup is automatically created. But, I have seen a lot of requests since November when we started messing with this device of people making mistakes and not having a backup. So it is always a good idea to copy and then save to the sd card just in case.
Sent from my Nook Tablet using xda premium
Well to be quite honest, before you make any sort of system modifications, you should always make a nandroid backup.
Having a backup of the build.prop or whatever file is nice because it allows you to quickly revert. But a nandroid backup protects you from when the damn thing decides to temp brick.
build prop differences
Also be aware that the build prop typo correction from the Team B CM 7 release (and I believe the RC2 release from a different source I cannot remember) is different from the mods Veronica released - she has developed her own build prop to handle the internal storage. I also had problems with the included Multi Mount SD Card Lite included in her mod and purchased the full version for $.99 which corrected the problems. Also note that there is an underline before _InternalSD in the full release of her mod which is different from just the small mod that handles the Internal over External SD card. Make sure you are being consistent with the folder name you create with the mod version you have installed.
Cubanluke88 said:
Well to be quite honest, before you make any sort of system modifications, you should always make a nandroid backup.
Having a backup of the build.prop or whatever file is nice because it allows you to quickly revert. But a nandroid backup protects you from when the damn thing decides to temp brick.
Click to expand...
Click to collapse
exactly, if more people would do this there might be fewer issues due to being able to restore if there is a oops moment.
Sent from my Nook Tablet using xda premium
Hi Bernardicus
Thanks heaps you are a champion!
I don't even know how to get terminal into su yet so you zip was a god send.
Now I have to work out how to enlarge the 1g of memory, i must admit it's very fulfilling modifying my Nook, looking forward to be proficient enough to return the favors from you all.
RhinoNelson said:
Also be aware that the build prop typo correction from the Team B CM 7 release (and I believe the RC2 release from a different source I cannot remember) is different from the mods Veronica released - she has developed her own build prop to handle the internal storage. I also had problems with the included Multi Mount SD Card Lite included in her mod and purchased the full version for $.99 which corrected the problems. Also note that there is an underline before _InternalSD in the full release of her mod which is different from just the small mod that handles the Internal over External SD card. Make sure you are being consistent with the folder name you create with the mod version you have installed.
Click to expand...
Click to collapse
Absolutely correct. I'm running her ribbon ics mod now on top of the Team B CM7 ROM (and loving it). She also modded the vold.fstab in /system/etc to reflect those changes in build.prop. I ended up replacing her vold.fstab with the Team B version and editing her build.prop to reflect the corrected "typos" in the Team B build.prop. (I know, I de-modded the mod, but for some reason, using the multi mount widget to do something that the OS should handle made the hairs on the back of my neck stand up!)
I'm spending more time modifying this thing that actually using it! But it has been fun.
bernardicus said:
Absolutely correct. I'm running her ribbon ics mod now on top of the Team B CM7 ROM (and loving it). She also modded the vold.fstab in /system/etc to reflect those changes in build.prop. I ended up replacing her vold.fstab with the Team B version and editing her build.prop to reflect the corrected "typos" in the Team B build.prop. (I know, I de-modded the mod, but for some reason, using the multi mount widget to do something that the OS should handle made the hairs on the back of my neck stand up!)
I'm spending more time modifying this thing that actually using it! But it has been fun.
Click to expand...
Click to collapse
I'm running Veronica's NT_CM7_Ribbon_ICS_v2.1 and I have the same problem. I replaced her vold.fstab with the Team B version and edited her build.prop. Now I can mount the Internal SD on my computer. Thanks for the help.
HELP!!
When i was running the RGUI ROM (JB) there was a fix zip to use in CWM to fix the 'Media' drain in the battery.
This worked wonders! So i just tried to flash it to my device again, except now i'm running the 'Anonorom' ROM.
It worked. Or flashed without error anyway.
The problem now is that since the reboot, the 'Fonts' have failed to be picked by my apps.
This is most noticibly with UCCW. The widget i created for the homescreen uses about 5 different fonts and its defaulted to 1 default font.
When i open the widget to change the fonts back, it tells me theres only 1 font available; "Default" and that if i want to add more then to put them in 'sd:\fonts'.
I've gone back to my file manager and checked this location and there are LOADS of fonts in there still, so its not as if they've been deleted.
Clearly this is the work of the fix_mediaDrain.zip, which i now obviously regret flashing. And WHO KNOWS what other errors i will now encounter!
So my question is, other than reflashing the ROM (which would be a pain because i've also flashed the JKay framework and other things like that, and amanaged to get the phone to my liking) does ANYONE know of a kind of UNDO fix for this fix_mediaDrain.zip that i can flash.
Obviously i dont even know if it exists,im just praying, but if anyone has any ideas i would greatly appriociate it.
I'm guessing the media scanner has been stopped, or a .nomedia file has been placed in the fonts folder.
So first check if there is a file called .nomedia in this folder and if so, delete it and reboot.
If not, then get rescan media root from play and try to enable media scanner and reboot.
Report back please
slaphead20 said:
first check if there is a file called .nomedia in this folder and if so, delete it and reboot.
If not, then get rescan media root from play and try to enable media scanner and reboot.
Report back please
Click to expand...
Click to collapse
Firstly, thanks for your reply..
I've checked the location for a '.nomedia' file and no it does not exist.
I even checked 'Root Explorer' incase the file was hiddenin my regular file manager. Still nothing.
I downloaded the 'Rescan Media Root' app, which looked successful, but didnt fix my issue.
I tried a different app called 'media Rescan Lite', but that too did not fix the issue.
It's not looking good for me is it?
well the obvious path note really is to post in the Rom thread/contact dev and find out what the file does and how it can be reverted, let me know if you don't have enough posts and I will post link to your dilemma for you
slaphead20 said:
well the obvious path note really is to post in the Rom thread/contact dev and find out what the file does and how it can be reverted
Click to expand...
Click to collapse
I have contacted the developer of this fix to ask what it does exactly and if theres any way to undo the fix.
I have also added a post to the thread where this fix was first suggested to me in the past, incase anyone there might be able to shed some light on it..
I will post my findings once i ear back from anyone incase anyone else ever has this problem...
Thanks again.
SOLVED!!
I have managed to fix this problem!
This is going to sound RIDICULOUS but.....
I renamed the 'Fonts' folder on my sdcard slightly.
I say 'renamed', but all i did was make the filename all lowercase, creating "fonts" instead of "Fonts".
Then, IMMEDIATLY, the fonts on my widget wer back to normal..!
How very odd that this was changed by the 'fix_mediaDrain.zip' throgh CWM + reboot.
AndyGalaxy said:
I have managed to fix this problem!
This is going to sound RIDICULOUS but.....
I renamed the 'Fonts' folder on my sdcard slightly.
I say 'renamed', but all i did was make the filename all lowercase, creating "fonts" instead of "Fonts".
Then, IMMEDIATLY, the fonts on my widget wer back to normal..!
How very odd that this was changed by the 'fix_mediaDrain.zip' throgh CWM + reboot.
Click to expand...
Click to collapse
well solved :thumbup: