Database Users

How do I edit gps.conf

I read in the SD-development thread about editing the
"GPS1_CLEANUP_ENABLED=1
HD2 have high current drainage(60mA) in the 0812 build. I noticed in /etc/gps.conf GPS1_CLEANUP_ENABLED was set to 0. After changing the value to 1. Current usage was back to normal 8mA"
I'm currently running the AmericanAndroid SD build and would like to change this value to 1. How do I access this? Using the phone, I went into file manager/etc and found the gps.conf file but how do I edit it? When I plug the phone to my laptop I can only view files from my SD card.
Thanks in advance, and sorry if this is a noob question.

Can anyone help?
During standy the battery drain is a consistent 60-70mA. Nothing is running, background data turned off, no wi-fi, no GPS, no sync.

rice-CHRISpies said:
I read in the SD-development thread about editing the
"GPS1_CLEANUP_ENABLED=1
HD2 have high current drainage(60mA) in the 0812 build. I noticed in /etc/gps.conf GPS1_CLEANUP_ENABLED was set to 0. After changing the value to 1. Current usage was back to normal 8mA"
I'm currently running the AmericanAndroid SD build and would like to change this value to 1. How do I access this? Using the phone, I went into file manager/etc and found the gps.conf file but how do I edit it? When I plug the phone to my laptop I can only view files from my SD card.
Thanks in advance, and sorry if this is a noob question.
Click to expand...
Click to collapse
You need to use a file explorer with root privileges. You can d/l ES File Explorer (or something like it) from the market for free.
When you run it, you'll be prompted to give it root (SU, or superuser) permissions. There's a checkbox in the menu, for you to do this anyway.
Most importantly - since the file system is read only - you'll have to also check the box directly underneath it in the root settings section of the menu to 'Mount File System'. This will make the files writable, so you can save your edits.
In general, you can keep the 'Root Explorer' box checked at all times, but it's not a bad practice to uncheck the Mount File System box when you're done so as to ensure against file changes.
gps.conf is located in the etc directory of the system. The line you want to edit is at the end of the file. When you make your change... don't forget to press the menu button and then press SAVE.
another user had similar problems - so you can take a quick look here...
http://forum.xda-developers.com/showpost.php?p=16735406&postcount=15225
Rob

thanx.works for me.

ke2v85 said:
thanx.works for me.
Click to expand...
Click to collapse
"Speaking of thanks, use the thanks button. Use it every time you get an answer, even if it's a one you don't like"
http://www.youtube.com/watch?v=JmvCpR45LKA&t=1m33s
I pressed it for you this time, next time you do it.

S Memo Crashing on a Particular Memo

When I try to load a memo I've done a lot of artwork in, the memo loads and even gets exported into an image. However, when I try to edit it, I get the following error:
The application S Memo (process com.sec.android.widgetapp.diotek.smemo) has stopped unexpectedly. Please try again.
[Force Close]
Click to expand...
Click to collapse
All other memos I've made are operating fine.
Has my memo got corrupted? Does anyone know how to get it back to normal? The image I'm exporting to is fine and I know I can finish off the picture from there... but it's not the same

Try this to solve the problem:
1. Find /data/system/packages.xml with Root Explorer.
2. Make a backup of packages.xml right away in the same folder in case we mess anything up any need to restore it later
3. Copy packages.xml onto the root of your internal or external storage
4. Plug your device into your computer and copy packages.xml from the root of your storage over to your computer
5. Open the packages.xml on your computer with your editor of choice - I use Wordpad
6. Search for the string. The lines should look something like this:
<package name="com.sec.android.widgetapp.diotek.smemo" codePath="/system/app/SMemo.apk" nativeLibraryPath="/data/data/com.sec.android.widgetapp.diotek.smemo/lib" flags="1" ft="135586718b0" it="133696737a0" ut="135586718b0" version="1" userId="10044">
7. then, you need to put/add this: enabled="1" at the last line before the ">" sign. The lines should look something like this:
<package name="com.sec.android.widgetapp.diotek.smemo" codePath="/system/app/SMemo.apk" nativeLibraryPath="/data/data/com.sec.android.widgetapp.diotek.smemo/lib" flags="1" ft="135586718b0" it="133696737a0" ut="135586718b0" version="1" userId="10044" enabled="1">

Did it work I am having the same problem?

I updated my firmware to the latest open Europe one and the problem stop! So the best to solve this problem is to.flash a new firmware!
Pure vida guys!
Sent from my GT-N7000 using xda premium
Sent from my GT-N7000 using xda premium

[Q] rooted NST - how to add images to internal wallpaper folder?

I'd like to change the wallpaper on the root u-tube home screen, but I don't see how one can access the internal folders. I'd like to be use adb push but I don't know the path for the 'Picture', or 'Wallpaper gallery Home' that are possible locations for adding the images.

You do mean the desktop wallpaper?
I'm boring. I just changed the default wallpaper to solid white.
In /system/framework/framework-res.apk
Replace /res/drawable-mdpi/default_wallpaper.png
To answer your original question: I don't know.

Thanks for the information; however being a complete beginner that does help me get a little bit closer to what I'd like to do but there is still much that I don't really understand. How do I access that location? And should I add my new image to the subfolder with a totally differently name, or should I rename the my image to that of the default.png and replace the old image?
If I adb push to the nook my image renamed to match the old wallpaper image, will that work?

still trying to replace home image in rooted Nook ST
I have a question for someone who knows more than I about android systems. Thanks to Thank Meter 78 who pointed out the file I need to change in order to replace the home image is in
/system/framework/framework-res.apk
and that I need to replace in that apk
/res/drawable-mdpi/default_wallpaper.png
Will the following procedure work properly without screwing up my newly rooted Nook?
Using Root Explorer I copied the 'framework-res.apk', and saved it to my Nook sd card. Then copied that apk file to my windows xp computer and changed the extension to 'zip' and unzipped it. The png file thus is available for replacement by another image of identical size and name.
Will it be correct for me to rename the modified .zip extenson file containing a new default_wallpaper.png file back to its original .apk extension, copy/paste it to the sd card, insert the sd card into the Nook, and the using Root Explorer to copy the apk file and paste it back to the drawable-mdpi folder where it will replace the nook apk (being sure that I change the r/o to r/w permission for the folder, and change it back after the replacement)?
Could there be adverse effects of the replacement?

My friends all call me Renate...
Yes, that procedure works, correcting for your typo.
Unzip, replace PNG, zip, copy back to /system/framework/framework-res.apk
You don't need to set it back to r/o. It's better/easier to just reboot, preferably with ADB.
You should always backup at reasonable intervals and before major changes.
Heck, I've bricked my Nook a dozen times.

Thanks Renate!

Ok, the actual answer is:
The gallery uses the mediastore images database.
The crawler can't find anything even if it's right under its nose.
The databases are stored in /data/data/com.android.providers.media/databases
There's internal.db and another db for each unique SD card inserted.
The crawler is equally lame finding MP3's also.
That's why both Music and Gallery say "no media".

Renate NST said:
Ok, the actual answer is:
The gallery uses the mediastore images database.
The crawler can't find anything even if it's right under its nose.
The databases are stored in /data/data/com.android.providers.media/databases
There's internal.db and another db for each unique SD card inserted.
The crawler is equally lame finding MP3's also.
That's why both Music and Gallery say "no media".
Click to expand...
Click to collapse
1) I thought the original question was about u-tube (I guess "Youtube" ;-))
2) ad gallery - I was always wondering how to make it see the JPGs I had as screensavers... Would you have any ideas how to fix this (i.e. make the crawler work)? Or maybe the other way round, how often is the crawler running? Would battery be improved if it was turned off/killed?

The Media Scanner service is what scans.
Normally it is activated on insertion of an SD card.
It does not run continuously.
It ignores directories with file in it called ".nomedia"
The MediaScannerConnection can be used to request scanning of a single file.
Level 8 API (we're 7) can request scanning of multiple files.
It seems to turn its nose up at files and not put them in its database.

ajislav said:
2) ad gallery - I was always wondering how to make it see the JPGs I had as screensavers... Would you have any ideas how to fix this (i.e. make the crawler work)? Or maybe the other way round, how often is the crawler running? Would battery be improved if it was turned off/killed?
Click to expand...
Click to collapse
Are you asking about having your own pics as screensavers?
I did that by connecting my NST to the PC, and creating a folder (one word name) under screensavers/ and copying the pics into that folder. It then shows up in the screensavers menu, and you can select it. The location from within the nook is /media/screensavers
--

The emulator's MediaScanner works fine, the Nook's appears broken.
You can manually enter images into the MediaStore:
(This requires sqlite3 installed or pull the database and do it on your desktop.)
Code:
sqlite3 /data/data/com.android.providers.media/databases/internal.db
insert into images (_data, mime_type) values('/media/myphoto.png', 'image/png');
.q
Call up Gallery.
You will see a blank thumbnail because one has not been generated yet.
Click on that.

Renate NST said:
The emulator's MediaScanner works fine, the Nook's appears broken.
You can manually enter images into the MediaStore:
(This requires sqlite3 installed or pull the database and do it on your desktop.)
Code:
sqlite3 /data/data/com.android.providers.media/databases/internal.db
insert into images (_data, mime_type) values('/media/myphoto.png', 'image/png');
.q
Call up Gallery.
You will see a blank thumbnail because one has not been generated yet.
Click on that.
Click to expand...
Click to collapse
Isn't their any way to repair the nooks MediaScanner? like, re-install it, clear the app data, copy another one in from another android 2.1 device? I don't understand why it isn't working, or why it can't be fixed. I've tried backing up the app and re-installing it, deleting the external db's, running media scan apps. Disabling it, re-enabling it...

Which is the best and easiest way to modify build.prop ?

Hi guys,
I would like to modify the build.prop file to introduce the following content.
ro.media.enc.jpeg.quality=100
I tried to do that using Explorer but my G2 stucked at the logo screen. Here below the steps that I followed.
1. Download of Explorer -> htt ps://play.google.com/store/apps/details?id=com.speedsoftware.explorer (remove the space between T and P)
2. App root permissions
3. Copy of the build.prop into another folder
4. Modify of the copied build.prop
5. Save of the modified build.prop
6. Copy/Paste of the modified build.prop into /system folder and confirm the substitution
7. Reboot
Help me plz

Radeon89 said:
Hi guys,
I would like to modify the build.prop file to introduce the following content.
ro.media.enc.jpeg.quality=100
I tried to do that using Explorer but my G2 stucked at the logo screen. Here below the steps that I followed.
1. Download of Explorer -> htt ps://play.google.com/store/apps/details?id=com.speedsoftware.explorer (remove the space between T and P)
2. App root permissions
3. Copy of the build.prop into another folder
4. Modify of the copied build.prop
5. Save of the modified build.prop
6. Copy/Paste of the modified build.prop into /system folder and confirm the substitution
7. Reboot
Help me plz
Click to expand...
Click to collapse
Modify the build.prop in its original original location itself and then save it & reboot, don't copy build.prop to other folder then modify it and then re-paste in it's original location you'll stuck with a bootloop, just modify it in it's original location. Btw next time before making a thread do make sure where should it belong this is a [Q] Question thread so should have been in QA, help & troubleshooting section, next time be sure to know where you have to make a new thread.

My apologies for the wrong section. I'm new sorry.
However, I forget to write that what you just suggested (modify it directly without make a copy) it's the first thing that I tried but with no success.
After I pressed the button save, Explorer app prompts an advise saying that an error occured and that the changes have not been applied.
And now? :crying:

Radeon89 said:
My apologies for the wrong section. I'm new sorry.
However, I forget to write that what you just suggested (modify it directly without make a copy) it's the first thing that I tried but with no success.
After I pressed the button save, Explorer app prompts an advise saying that an error occured and that the changes have not been applied.
And now? :crying:
Click to expand...
Click to collapse
In system > build.prop (original location) is the device mounted to R/W?

Hi,
First, this line "ro.media.enc.jpeg.quality=100" does nothing...
After that if you change the location of a file, when you move it again you need to set the correct permissions like the original files, other than that you can encounter a bootloop.
Like RuchRha said modifie the file directly, no need to move it...
And if I were you I'll make a Nandroid backup before playing with file system...

These are the file permissions that I see into the file properties.
rw- r-- r--
Is this what you was asking me?

Radeon89 said:
These are the file permissions that I see into the file properties.
rw- r-- r--
Is this what you was asking me?
Click to expand...
Click to collapse
If you can see an option of Mount R/W instead click on it and it should change/show you Mount R/O instead of showing mount R/W, when the time when system is not mounted to R/W and you try to edit buildprop and save it, it shows error n doesn't gets saved.

Radeon89 said:
These are the file permissions that I see into the file properties.
rw- r-- r--
Is this what you was asking me?
Click to expand...
Click to collapse
Nope,
Read Only system:
Read/Write:
You need to mount the system as R/W.
EDIT: too late...

To the best of my uderstanding the free version does not permit such kind of change.
Is there any free app that I can use?

Radeon89 said:
To the best of my uderstanding the free version does not permit such kind of change.
Is there any free app that I can use?
Click to expand...
Click to collapse
you can use BuildProp Editor.Is free in playstore:good:

Titanium Backup cannot backup to micro sd

Hi all,
For the past month or so, Titanium Backup cannot backup anything to my external sd any more and reports "Insufficient storage space". When I look at the folder location under TiBu preferences, it says "folder is not writable", however when I check the permissions with Root Explorer, it says it is writable, and everything else can really write to it anyway (e.g. google music can write there just fine).
If I switch the backup location to internal storage, it works fine but that defeats the purpose, I want to use my external microsd.
I've already tried uninstalling/re-installing, updating my SuperSU, rebooting the phone etc.
Any ideas?

Hi. . Your can try "Helium" as even the free version supports backup and restore from sd card.. here's the link:
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
Good luck
Sent from my GT-I9505 using Tapatalk

fincan said:
Hi all,
For the past month or so, Titanium Backup cannot backup anything to my external sd any more and reports "Insufficient storage space". When I look at the folder location under TiBu preferences, it says "folder is not writable", however when I check the permissions with Root Explorer, it says it is writable, and everything else can really write to it anyway (e.g. google music can write there just fine).
If I switch the backup location to internal storage, it works fine but that defeats the purpose, I want to use my external microsd.
I've already tried uninstalling/re-installing, updating my SuperSU, rebooting the phone etc.
Any ideas?
Click to expand...
Click to collapse
Could be related to the update to 4.3 which changed permissions for writing to the external SD Card.
Check this thread out.
http://forum.xda-developers.com/showthread.php?t=2436494

dratsablive said:
Could be related to the update to 4.3 which changed permissions for writing to the external SD Card.
Check this thread out.
http://forum.xda-developers.com/showthread.php?t=2436494
Click to expand...
Click to collapse
You are right. I rolled back my platform.xml thinking that the sd card issue has been fixed in 4.4, changing it back did the trick. Thanks

fincan said:
You are right. I rolled back my platform.xml thinking that the sd card issue has been fixed in 4.4, changing it back did the trick. Thanks
Click to expand...
Click to collapse
Your welcome!

fincan said:
You are right. I rolled back my platform.xml thinking that the sd card issue has been fixed in 4.4, changing it back did the trick. Thanks
Click to expand...
Click to collapse
I updated to Kitkat 4.4 and am rooted. Im having the exact same issue with Titanium. It tells me the target dir is full and that it cant write/access the SD card. I changed permission of the SD Card with Root explorer but it doesnt stay.
How do I "roll back" platform.xml? I have no idea how to fix this. Never had any issue like this before in all my years of swapping roms and upgrading android builds.

Alpine- said:
I updated to Kitkat 4.4 and am rooted. Im having the exact same issue with Titanium. It tells me the target dir is full and that it cant write/access the SD card. I changed permission of the SD Card with Root explorer but it doesnt stay.
How do I "roll back" platform.xml? I have no idea how to fix this. Never had any issue like this before in all my years of swapping roms and upgrading android builds.
Click to expand...
Click to collapse
You have to edit yoour platform.xml file so Titanium Backup works again. Since you are already rooted, you can refer to this post for what to edit, where the file is etc.:
http://forum.xda-developers.com/showthread.php?p=44370296

fincan said:
You have to edit yoour platform.xml file so Titanium Backup works again. Since you are already rooted, you can refer to this post for what to edit, where the file is etc.:
http://forum.xda-developers.com/showthread.php?p=44370296
Click to expand...
Click to collapse
Thanks, I found an identicle How-To here: http://www.androidauthority.com/galaxy-s4-gpe-android-4-3-sd-card-fix-254960/
They are the same, both work. This one is a little easier to follow. I'm shocked this bug mad it over from 4.3 and into 4.4.2 official builds. All is well now though.

Titanium Backup with insuffiecient storage space - 1 problem , 3 solutions
To summarize, I have come across three solutions to this problem. In fact, it´s four solutions now, since one additional method was pointed out by Vandevandel (see number two below).
1.
Change the backup-location to /storage/emulated/legacy/TitaniumBackup
Just open Titanium and go to Settings/Preferences/Backup folder location
Change to: /storage/emulated/legacy/TitaniumBackup
2.
There is an elegant way of giving TitaniumBackup write access to the external sdcard, without having to forfeit security (as in method 3 below).
Since the time of Android 4.3, Google uses a very clean security-solution by giving apps that request write access to external SD, permission only to their own folder - not to the entire card!
In order to get TitaniumBackup to work without compromising security, you can simply create a folder on the external sdcard,using the following folder-structure: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/
If you already have existing backups, move them with a file-explorer from their current place to: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/
Lastly, go tothe preferences of TitaniumBackup, choose "Backup folder location" and choose the above specified folder.
Finish.
Very clean and safe.
3.
There is a solution for gaining write access to the external sdcard (/mnt/sdcard2). The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. This permission was not required for access to the external sdcard prior to Android 3.2, but for security reasons this is the case now.
If you're rooted and want to make the ext. sdcard writable to all apps, please try the following:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
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 your tablet.
Original:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
</permission>
New:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Done.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that accesses either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
This may also fix problems with other apps that have issues writing to the ext. sdcard, but please be aware that in terms of security, solution two (see above) is preferable.
4.
If you had Titanium Backup installed on a previous ROM, doing a non-wipe install could stop the process of Titanium Backup. You might receive a pop-up notification that Titanium Backup has stopped working. Reinstalling the app might lead to an insufficient storage space error — when an app is uninstalled or modified, it leaves a .odex residue file which causes the error. So all you have to do is delete the .odex file of Titanium Backup.
Here’s how:
Using any file explorer like Root Explorer or ES File Explorer, go to /data/app , find and delete ”com.kermidas.TitaniumBackup-1.odex“. Now you can install Titanium Backup again!
If there is no such file in your folder, that´s OK. But please don´t delete any .apk file!
Good luck!
--------------------------------------------------------------------------------
If you find this post useful, pls feel free to click "Thanks".
Have a nice day

Parinibbana said:
To summarize, I have come across three solutions to this problem.
1.
Change the backup-location to /storage...
Open Titanium and go to Settings/Preferences/Backup folder location
Change to: /storage/emulated/legacy/TitaniumBackup
2.
If you had Titanium Backup installed on a previous ROM, doing a non-wipe install could stop the process of Titanium Backup. You might receive a pop-up notification that Titanium Backup has stopped working. Reinstalling the app might lead to an insufficient storage space error — when an app is uninstalled or modified, it leaves a .odex residue file which causes the error. So all you have to do is delete the .odex file of Titanium Backup.
Here’s how:
Using any file explorer like Root Explorer or ES File Explorer, go to /data/app , find and delete ”com.kermidas.TitaniumBackup-1.odex“. Now you can install Titanium Backup again!
If there is no such file in your folder, that´s OK. But please don´t delete any .apk file!
3.
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
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 your tablet.
Original:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
</permission>
New:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Done.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that accesses either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
This may also fix other apps that have issues writing to the card.
--------------------------------------------------------------------------------
If you find this post useful, pls feel free to click on "Thanks".
Have a nice day
Click to expand...
Click to collapse
thanks

idrak3 said:
thanks
Click to expand...
Click to collapse
You're welcome.

I rooted yesterday my galaxy s4 and had the same problem with the titanium backup pro. Thank you so much dude!:good:

Much appreciated, had this issue on my new S5 and this was a simple enough solution. Thanks.

Step 3 worked for me after just upgrading to my Note2 to DN3 v5 and having this Titanium Backup Pro issue on app reinstall - many thanks!

Install Easy Fix
fincan said:
Hi all,
For the past month or so, Titanium Backup cannot backup anything to my external sd any more and reports "Insufficient storage space". When I look at the folder location under TiBu preferences, it says "folder is not writable", however when I check the permissions with Root Explorer, it says it is writable, and everything else can really write to it anyway (e.g. google music can write there just fine).
If I switch the backup location to internal storage, it works fine but that defeats the purpose, I want to use my external microsd.
I've already tried uninstalling/re-installing, updating my SuperSU, rebooting the phone etc.
Any ideas?
Click to expand...
Click to collapse
Just install this 300kb app and run it. it will fix the issue. worked perfectly for me
https://play.google.com/store/apps/details?id=nextapp.sdfix

That app didn't work for me :' (
Sent from my SM-G900P using Tapatalk

tbudke said:
That app didn't work for me :' (
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Are you rooted ?
Sent from my SM-G900V using Tapatalk

Titanium Backup Fix for Folder is not writable
fincan said:
Hi all,
For the past month or so, Titanium Backup cannot backup anything to my external sd any more and reports "Insufficient storage space". When I look at the folder location under TiBu preferences, it says "folder is not writable", however when I check the permissions with Root Explorer, it says it is writable, and everything else can really write to it anyway (e.g. google music can write there just fine).
If I switch the backup location to internal storage, it works fine but that defeats the purpose, I want to use my external microsd.
I've already tried uninstalling/re-installing, updating my SuperSU, rebooting the phone etc.
Any ideas?
Click to expand...
Click to collapse
Install NEXTAPP SDFIX and run it will fix

Another thing to look out for:
Sometimes, I've seen a file/folder get created in the TB backup folder called .write_test
What actually creates this and why is still a mystery to me.
If this exists, TB will refuse to write to that folder, and will give the "insufficient storage" error.
Delete it through Root Explorer, and you should be good to go.

Parinibbana said:
To summarize, I have come across three solutions to this problem.
Click to expand...
Click to collapse
#3 worked for me after -- (dummy me) I remembered to reboot.