Related
http://forum.xda-developers.com/archive/index.php/t-644769.html << I got my idea from there.
If you update the
Code:
/data/data/com.android.providers.settings/databases/settings.db
file so that "install_non_market_apps" = 1 instead of 0, you will be able to install non-market apps off of your sdcard or wherever.
This works for me at least, but you'll have to root first.
I ended up editing the file with the SQLite Manager firefox add-on.
But, since that took me a really long time, I'll just upload the edited settings.db for you. (don't forget to make the extention .db instead of .db.txt)
Now, as far as I know, this won't mess anything up... BUT, I'd feel a lot better if someone who knows more about Android would provide some feedback before anyone else tries this. [It works for me, but I'm not sure if any other user-specific settings are kept in that file that I don't know about!]
But, at least for me, I no longer need to use adb to install apks that aren't from the Android Market.
I hope this is useful to someone...
EDIT::
You will lose your settings if you use the attached settings.db.txt file. Your best bet is to pull the file off your phone, edit it with something that understands sqlite3's database format, and then push it back. It's just better that way.
Further EDIT:: As someone pointed out later in this thread, this file unbeknownst to me when I shared it, actually has a unique ID by which phones can be identified on the android market, etc. While this isn't a huge deal, it can lead to some rather strange behavior... my phone for example has started attempting to download apps from the android market all by itself.
So--- if you want to side-load apps, change the variable in the database like I explained above.
Sorry, completely new to android but where would you put this file so it would allow side-loading?
You'd have to replace
Code:
/data/data/com.android.providers.settings/databases/settings.db
with it. You'll have to have your phone rooted first though. Then you'll have to transfer the file to your phone with adb, and you'll then copy it over the existing settings.db file.
Honestly, it might not even be worth the trouble now that attn1 is just doing the whole ROMs.
But make sure you take off the .txt.
This works. Thanks.
For some reason, i'm getting a permissons error regardless that i successfuly rooted my phone...o_o
justince said:
For some reason, i'm getting a permissons error regardless that i successfuly rooted my phone...o_o
Click to expand...
Click to collapse
did you boot the phone and do adb remount with debugging enabled?
USB debugging? Yeah.
What i did was i used the other method to sideload root explorer, took the settings.db.txt, deleted the .txt part and replaced it via root explorer, and now i can sideload whenever...however, when i try to delete any of the att bloatware, its read only o_o fawking att
Can anyone confirm any other way to remove bloatware without flashing the rom?
justince said:
USB debugging? Yeah.
What i did was i used the other method to sideload root explorer, took the settings.db.txt, deleted the .txt part and replaced it via root explorer, and now i can sideload whenever...however, when i try to delete any of the att bloatware, its read only o_o fawking att
Can anyone confirm any other way to remove bloatware without flashing the rom?
Click to expand...
Click to collapse
That's why made the ROM without all that -er- stuff.
attn1 said:
That's why made the ROM without all that -er- stuff.
Click to expand...
Click to collapse
Attn's Rom is ****ing great. many thanks btw
a little help please
a bit confused..
how do i type in this code "/data/data/com.android.providers.settings/databases/settings.db"?
adb /data/data/com.android.providers.settings/databases/settings.db
or something else because that doesnt work.
fluffyarmada said:
I'm not sure if any other user-specific settings are kept in that file that I don't know about!
Click to expand...
Click to collapse
The only issue I see (as an Android newcomer, but with a development background) is that the settings.db contains an android_id that is supposed to be unique (it gets generated when you boot the phone the first time after a reset). So anyone installing your settings.db is going to have the same ID.
I'm sure it won't be an issue for most people but I wonder if there'd be a collision in any apps that are designed to communicate between Android devices? For this reason I'll be tweaking my own settings.db once the phone arrives later today.
Big thanks for posting this though!
Thanks for that, I honestly had no idea. I'm very new to Android. And this was a kludge.
fluffyarmada said:
http://forum.xda-developers.com/archive/index.php/t-644769.html << I got my idea from there.
If you update the
Code:
/data/data/com.android.providers.settings/databases/settings.db
file so that "install_non_market_apps" = 1 instead of 0, you will be able to install non-market apps off of your sdcard or wherever.
This works for me at least, but you'll have to root first.
I ended up editing the file with the SQLite Manager firefox add-on.
But, since that took me a really long time, I'll just upload the edited settings.db for you. (don't forget to make the extention .db instead of .db.txt)
Now, as far as I know, this won't mess anything up... BUT, I'd feel a lot better if someone who knows more about Android would provide some feedback before anyone else tries this. [It works for me, but I'm not sure if any other user-specific settings are kept in that file that I don't know about!]
But, at least for me, I no longer need to use adb to install apks that aren't from the Android Market.
I hope this is useful to someone...
EDIT::
You will lose your settings if you use the attached settings.db.txt file. Your best bet is to pull the file off your phone, edit it with something that understands sqlite3's database format, and then push it back. It's just better that way.
Further EDIT:: As someone pointed out later in this thread, this file unbeknownst to me when I shared it, actually has a unique ID by which phones can be identified on the android market, etc. While this isn't a huge deal, it can lead to some rather strange behavior... my phone for example has started attempting to download apps from the android market all by itself.
So--- if you want to side-load apps, change the variable in the database like I explained above.
Click to expand...
Click to collapse
NOTE: You MUST have root access in order for this to work
sqlite3 is included in the Android SDK tools, so this would be the best way:
COMMON
Enable USB debugging (settings > applications > development > USB Debugging)
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Linux/OS X
echo "update secure set value = 1 where name = 'install_non_market_apps';"|./sqlite3 settings.db
WINDOWS
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
COMMON
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Reboot phone and sideloading works. (thanks fluffyarmada)
I wonder if this might be why google voice fails to install properly for some...
Sent from my HTC Liberty using XDA App
Cobus said:
I wonder if this might be why google voice fails to install properly for some...
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
It is possible. The Google apps all use the android_id, afaik.
Although, I do remember I was never able to get the settings menu to setup the voicemail forwarding... I always had to use the weird GSM code. (The weird number with a bunch of * and # that you have to type in if you follow google's directions.)
judicious said:
a bit confused..
how do i type in this code "/data/data/com.android.providers.settings/databases/settings.db"?
adb /data/data/com.android.providers.settings/databases/settings.db
or something else because that doesnt work.
Click to expand...
Click to collapse
After you've rooted your phone, download the new settings.db into the same folder as where your adb program is. Then type:
adb push /data/data/com.android.providers.settings/databases/settings.db
in that folder while your phone is connect via usb.
I'm not sure if you have to restart your phone into recovery or not. Can someone check on this?
tiga2001 said:
After you've rooted your phone, download the new settings.db into the same folder as where your adb program is. Then type:
adb push /data/data/com.android.providers.settings/databases/settings.db
in that folder while your phone is connect via usb.
I'm not sure if you have to restart your phone into recovery or not. Can someone check on this?
Click to expand...
Click to collapse
Well, it's
Code:
$ adb push /path/to/file/on/computer/settings.db /path/to/file/on/phone/settings.db
So, if your settings.db is in your tools folder, then you can do
Code:
$ adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
what happen to the file download? i cant find it..
judicious said:
what happen to the file download? i cant find it..
Click to expand...
Click to collapse
Please follow the instructions posted by attn1 on reply number 13 to this thread.
I removed the settings.db, because it actually has a bunch of extra settings I didn't know about like a handset specific android_id variable... that caused me a bit of trouble...
But, follow the instructions on reply #13 on this thread, and you'll be able to fix it yourself.
Sorry for the inconvenience.
so if we already used the file, is there anyway to revert it back to default and then change the settings via the method outlined above? or.. if we failed to make a copy of our original settings.db file.. basically am i SOL?
EDIT: nevermind, just rebooted into Clockwork and wiped the phone.
Hello,
Related to this post :
http://forum.xda-developers.com/showthread.php?p=39762775#post39762775
I have the following problem with an Xperia J:
Initial Problem:
- The mobile belongs to my cousin, she updated it with the Sony update center to the latest version (JB 4.1.2) and there: problem with the wifi when the sim.
- I got the mobile, and downgrade to the 4.0.4 version, I've tried 4 different versions:
-> ST26i_11.0.A.3.18_Global
-> ST26i_11.0.A.7.5_CE
-> ST26i_11.0.A.3.28_WE
-> St26i_4.0.4_11.0.A.3.28_CE3
I had always the problem with the wifi when the sim plugged.
Finally I've tried also the UNOFFICIAL CM 10, with no success
- I found a solution with the apk wifix manager witch worked with the 28 WE version of the firmware.
But I've continued to search an other solution, and I've remarked that when I flash the rom I always get the Warn: "This file is ignored : simlock.ta "
After some research I get an advice by a member of XDA to rename the file as "preset.ta", AND THERE, it works no warning ... BUT the sim is blocked (not locked) and I have always the message (invalid card).
I've tried to re-flash the firmware many times, to re-lock the bootloader (with appropriate ftf proposed in this forum ), Tried to use the sony update service .. But I have always the same problem (INVALID CARD)
I've also tried to format everything with CWM (system,card,cache) and made a sdcard partition, and NO way.
In addition:
- I can't enter to the fastboot mode, the led doesn't turn on blue no more, it works when I've started to work with, and it was important to install CM10, now I can't retry the CM installation.
- I've rooted the device, but I can't edit the build.prop (with root explorer neither with a terminal ide with vi editor, even if I do a "su" command and then "whoami", I didn't show : root).
- I've tried several sim cards, and they work with other devices (as xperia P and xperia U).
So, can any body help me with that please?!
Note : I'm in the middle east zone, some suggestions in the web talk about re-installing the official O2 rom, but I've searched this ROM with no success.
RevoOSyr said:
- I've rooted the device, but I can't edit the build.prop (with root explorer neither with a terminal ide with vi editor, even if I do a "su" command and then "whoami", I didn't show : root).
Click to expand...
Click to collapse
What are the build.prop permissions? Of course "Root is god", but you can set flag in kernel, that makes root follow his own rules, i.e. if you want to write to a file, it must be writable. If it isn't, you must change the permissions and then write to it.
build.prop afaik is rw-r--r-- so you must make it rw-rw-rw to write anything.
chmod go+w build.prop
or
chmod 666 build.prop
to restore:
chmod go-w build.prop
or
chmod 644
In reality with the version CE3, we have a line in the file build.prob witch lock the APN and I would to comment the line, it's not needed now, because I haven't this line in the other version.
I've tried to make a chmod but I wasn't able to do it.
Regards,
0x4721 said:
What are the build.prop permissions? Of course "Root is god", but you can set flag in kernel, that makes root follow his own rules, i.e. if you want to write to a file, it must be writable. If it isn't, you must change the permissions and then write to it.
build.prop afaik is rw-r--r-- so you must make it rw-rw-rw to write anything.
chmod go+w build.prop
or
chmod 666 build.prop
to restore:
chmod go-w build.prop
or
chmod 644
Click to expand...
Click to collapse
It's OK for the root problem, it was a problem with the rooting procedure here:
http://forum.xda-developers.com/showthread.php?t=2033114
in reality I had an error (can't mount /system in rw), I've reinstalled busybox and it's ok, I've tried to change some parameters in the build.prop (such : hide some language) and it works.
But still having a problem with the (INVALID CARD)
Any help?!
Thanks.
Other precision:
When I go to : *#*#7378423#*#*
Then: Service info > Configuration > Rooting Status : Bootloader unlock allowed says no
And the SIM LOCK seems to be incorrect.
I think that I've locked the bootloader somewhere, because I've unlockd the booloader 2 days ago when I've installed CM10, and everything was OK!!!
ThnkX
Other problem, in the SIM LOCK menu I have : x everywhere with the counter set to 0
After research in the web, that means that even it could not be unlocked by code!
it's strange that there's no way to fix that ...
No body has an idea about the solution for this problem?! even a payant one!
Thanks
Return to sony service
I didn't find any solution to this problem, so I've sent the device to sony service, and they didn't fix the problem yet.
The lesson of the story, you have to be very carefull when you do something (as lashing your mobile)
You have to know exactly what you do. And never to try insecure operations.
Im in the same situation... any news?
nacxo said:
Im in the same situation... any news?
Click to expand...
Click to collapse
did you have TA BACK UP?
How can I change how a game server detects your device? The reason why is because I want to start over in restaurant story but they keep your data tied to your device. So I need to change the device information they're receiving. It seems possible by changing something in the build.prop but I don't know what to change. I have successfully done this before on a different device but I don't remember what I changed to make it work. I've done some experimentation and made a backup of build.prop and tried changing ro.build.display.id, and ro.build.id and rebooted and it didn't work. Then I went on a tweaking spree and changed ro.build.description, ro.build.fingerprint, and ro.build.version.codename - doing very minor changes - and rebooted and my device wouldn't boot up. It would just sit on the boot animation and not finish and I had to restore in recovery. Does anyone know what I must change to make it work?
joshua5683 said:
How can I change how a game server detects your device? The reason why is because I want to start over in restaurant story but they keep your data tied to your device. So I need to change the device information they're receiving. It seems possible by changing something in the build.prop but I don't know what to change. I have successfully done this before on a different device but I don't remember what I changed to make it work. I've done some experimentation and made a backup of build.prop and tried changing ro.build.display.id, and ro.build.id and rebooted and it didn't work. Then I went on a tweaking spree and changed ro.build.description, ro.build.fingerprint, and ro.build.version.codename - doing very minor changes - and rebooted and my device wouldn't boot up. It would just sit on the boot animation and not finish and I had to restore in recovery. Does anyone know what I must change to make it work?
Click to expand...
Click to collapse
Are you sure it is tied to your device or tied to your account (Gmail)? Anyways I think you need to change the ro.product.device in the Build.prop.
mapatton82 said:
Are you sure it is tied to your device or tied to your account (Gmail)? Anyways I think you need to change the ro.product.device in the Build.prop.
Click to expand...
Click to collapse
Yeah it's tied to the device. Unless they changed it, but I doubt it. Thanks I think I tried that but nevermind, I decided I actually don't want to use the app anymore. Thanks anyways
I made a thread for Rooted AT&T 2.20 about enabling factory tethering. I found out that using this same .db file on 3.18 was not working for me. So I went back and re-edited the telephony.db that came with 3.18 and it seems to work again. I have uploaded the 3.18 version of telephony.db to enable factory hotspot sharing again. I have CleanROM 6 R2 installed and this seems to work well on it. Should work on stock rooted phones as well.
To Install
1. Extract telephony.db into the same folder as your adb.exe
2. Run these commands (they create a backup as well as push the edited database):
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/data/data/com.android.providers.telephony/databases/telephony.db of=/sdcard/telephony.db.bak
>adb push telephony.db /sdcard/telephony.db
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/telephony.db of=/data/data/com.android.providers.telephony/databases/telephony.db
[email protected]:/ # reboot
After reboot everything should work fine.
this is awesome, but you got my hopes up with the "rooted 3.18" title. you may want to move that bit to the end of the title. will definitely use this if my phone is ever unlocked again :\
Ha I got all excited too. And I may be wrong, but shouldn't this be in the development section?
lightpost712 said:
I made a thread for Rooted AT&T 2.20 about enabling factory tethering. I found out that using this same .db file on 3.18 was not working for me. So I went back and re-edited the telephony.db that came with 3.18 and it seems to work again. I have uploaded the 3.18 version of telephony.db to enable factory hotspot sharing again. I have CleanROM 6 R2 installed and this seems to work well on it. Should work on stock rooted phones as well.
To Install
1. Extract telephony.db into the same folder as your adb.exe
2. Run these commands (they create a backup as well as push the edited database):
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/data/data/com.android.providers.telephony/databases/telephony.db of=/sdcard/telephony.db.bak
>adb push telephony.db /sdcard/telephony.db
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/telephony.db of=/data/data/com.android.providers.telephony/databases/telephony.db
[email protected]:/ # reboot
After reboot everything should work fine.
Click to expand...
Click to collapse
I downloaded file, but seems zip file is empty... I am using Peazip
diekastro said:
I downloaded file, but seems zip file is empty... I am using Peazip
Click to expand...
Click to collapse
I just re-downloaded it and the file is there. Try using a different unzipping program.
lightpost712 said:
I just re-downloaded it and the file is there. Try using a different unzipping program.
Click to expand...
Click to collapse
I tried again with windows pack and winzip... Both shows empty file.
I disabled Eset Enpoint, and I downloaded it 3 times.
However, I am using stock rom and I have the SQLite Editor. What changes did you do? Do you just have to change file 12 'broadband' to 'pta'?
Thanks
diekastro said:
I tried again with windows pack and winzip... Both shows empty file.
I disabled Eset Enpoint, and I downloaded it 3 times.
However, I am using stock rom and I have the SQLite Editor. What changes did you do? Do you just have to change file 12 'broadband' to 'pta'?
Thanks
Click to expand...
Click to collapse
I don't remember which line exactly off the top of my head. I am reattaching the zip file see if that works if that fails then I will go in a compare the standard .db with the new one. It was a simple one line change just don't remember which line it was. Trial and error is how I found it.
Thank you
lightpost712 said:
I don't remember which line exactly off the top of my head. I am reattaching the zip file see if that works if that fails then I will go in a compare the standard .db with the new one. It was a simple one line change just don't remember which line it was. Trial and error is how I found it.
Click to expand...
Click to collapse
I guess you did it using SQLite editor, it works for me.
Make a backup of telephony.db
Your internet APN should be configured (Settings - Mobile data - Access Point names)
1)Open Telephony.db (flange files: data/data/com.android.providers.telephony/databases)
2)Select 'carriers'
3)Search second row, then select Edit field
4)Change ID field with a number non used in this db (ex: in my case the last row is "42" so I used "43") - Save
5)Repeat the 3 and 4 steps, but using row 12.
6)Search the last line (or line with your carrier internet APN)
7)Select the row and Edit Field.
8)Change the ID field to "2". - Save
9)Chose the second row, then Clone Record and change ID field to '12' - Save
Just need to change a lot of things
Row number 2 -> Edit field
1)Change name to ATT Phone
2)Type to "default"
2)Insert_by field to "internal".
3)State to "readonly"
Row number 12 -> Edit field
1)Change name to Entiltlement
2)Type to "entitle"
2)Insert_by field to "internal".
3)State to "hidden"
My phone: HTC One X AT&T 3.18 unlocked and root. Stock rom
Worked great for me with a rooted, s-off HTC First and ST (ATT) SIM. Thank you!
diekastro said:
I guess you did it using SQLite editor, it works for me.
Make a backup of telephony.db
Your internet APN should be configured (Settings - Mobile data - Access Point names)
1)Open Telephony.db (flange files: data/data/com.android.providers.telephony/databases)
2)Select 'carriers'
3)Search second row, then select Edit field
4)Change ID field with a number non used in this db (ex: in my case the last row is "42" so I used "43") - Save
5)Repeat the 3 and 4 steps, but using row 12.
6)Search the last line (or line with your carrier internet APN)
7)Select the row and Edit Field.
8)Change the ID field to "2". - Save
9)Chose the second row, then Clone Record and change ID field to '12' - Save
Just need to change a lot of things
Row number 2 -> Edit field
1)Change name to ATT Phone
2)Type to "default"
2)Insert_by field to "internal".
3)State to "readonly"
Row number 12 -> Edit field
1)Change name to Entiltlement
2)Type to "entitle"
2)Insert_by field to "internal".
3)State to "hidden"
My phone: HTC One X AT&T 3.18 unlocked and root. Stock rom
Click to expand...
Click to collapse
I did all this it worked, it stopped saying "there's temporary network problem that stop the enablement of your... yari yari yari"
but it is not showing tethering status icon at the notification drawer however, it is saying limited service if i connected it with my computer..
somebody gotta help me out pls
BEST REGARDS
brilliant_smart said:
I did all this it worked, it stopped saying "there's temporary network problem that stop the enablement of your... yari yari yari"
but it is not showing tethering status icon at the notification drawer however, it is saying limited service if i connected it with my computer..
somebody gotta help me out pls
BEST REGARDS
Click to expand...
Click to collapse
The AT&T ROMs are a real pain in the butt in regards to tethering and WiFi hotspot. As you are already bootloader unlocked and rooted, I would suggest just flashing any non-AT&T base ROM, and the tethering functions should work properly. Especially if you are not on AT&T, and your carrier does not limit tethering in any way (it looks like you are not located in the US?).
In my opinion, there is nothing "good" about being on the AT&T ROM. Many functions are intentionally broken or hidden, with nothing useful added. So going to a non-AT&T based ROM is "win" all around.
brilliant_smart said:
I did all this it worked, it stopped saying "there's temporary network problem that stop the enablement of your... yari yari yari"
but it is not showing tethering status icon at the notification drawer however, it is saying limited service if i connected it with my computer..
somebody gotta help me out pls
BEST REGARDS
Click to expand...
Click to collapse
Maybe Its late for answer, but did you restar your phone after edit the file?
diekastro said:
Maybe Its late for answer, but did you restar your phone after edit the file?
Click to expand...
Click to collapse
No offense to the OP, but I would suggest not wasting any more time with this method (its been 6 months after all). As I already mentioned in Post #11 above, just flash any custom or stock rooted ROM that is not AT&T base (Sense base - I don't follow AOSP ROMs enough to know how well WiFI hotspot works on those), and WiFi hotspot will work fine.
You are right
redpoint73 said:
No offense to the OP, but I would suggest not wasting any more time with this method (its been 6 months after all). As I already mentioned in Post #11 above, just flash any custom or stock rooted ROM that is not AT&T base (Sense base - I don't follow AOSP ROMs enough to know how well WiFI hotspot works on those), and WiFi hotspot will work fine.
Click to expand...
Click to collapse
yes, really I flashed with T-mobile Sense 5 ROM five months ago, and its better option.
As there are again and again discussions concerning the minfree settings in CM12 roms, I decided to open this thread. If a moderator thinks, this is the wrong place for this thread, just move it, to where it belongs.
Obviously, since the last builds of CM12, the settings for minfrees cause some trouble. After a clean install of any rom, the minfree settings in trickstermod and in fauxclock are completely empty. In fauxclock the settings for OOM (out of memory) Score as well. Some people entered them manually, but I'm afraid, this won't help.
To really solve this, you have to do the following steps: open your file explorer, go to sys/module/lowmemorykiller/parameters. There you will find 5 files. Two of them do not have correct permissions. The first one, called adj, is for the OOM Scores. The other one, called minfree, is, you won't guess it, for the minfrees. :fingers-crossed:
As you see, both of them have only write permissions, but no read permissions. So I guess, the system will ignore these settings completely. I checked this, using cool tool from play store, very nice tool to show for example the actual free ram in your status bar. And in deed, the ram went down to 25MB, after I had opened a handful apps, and then my phone stopped working. I only could do a reboot.
Now the solution, which is quite easy: change the permissions into rw-rw-rw (666), and maybe change the group under owners into root (I'm not sure, if this is necessary, but it does make no problems, so why not).
Et voilà - if you now open trickstermod or fauxclock again, you will see the preset parameters. As you can see also, the minfrees there are really high. In another thread, there have been suggested the following settings, which are a good standard:
trickstermod 48/60/72/84/96/120
fauxclock 12288/15360/18432/21504/24576/30720
Important: In fauxclock, the minfree settings are not made in MB. You have to enter the so called "pages" for minfrees, which I can't explain exactly, what this is. In general, if you want to change minfrees in fauxclock, just take the settings in MB, you want to, and multiply by 256. This will give you the correct values.
BTW I don't think, it's a good idea, to change the OOM Scores, as long as you do not know exactly, what you're doing.
So, hopefully I could help a bit and clear some things up. But the final question to the CM devs remains:
is this a bug or is this a feature?
With me, those files were already chmod 666, owner root. I use latest liquidsmooth rom. What i did, prior reading your post, was that i set minfree in trickster, from my presets, than immedatly switched to faux, parameters were there, pressed apply, switched set on boot and rebooted. After that minfree r sticking in faux and trickster. Guess that my actions leaded to what you have described. Anyway, your way is much more convinient - at least one app less to use
I don't get it... The directory you mentioned is empty on my one s as well as on my nexus 10 both with cm12.
However my settings stick since I use fauxclock.
One more thing I don't get is in fauxclock. It says "kilobyte" explicitly in the minfree settings although you said (and it stems to be) this strange pages value....
mariachi62 said:
I don't get it... The directory you mentioned is empty on my one s as well as on my nexus 10 both with cm12.
However my settings stick since I use fauxclock.
One more thing I don't get is in fauxclock. It says "kilobyte" explicitly in the minfree settings although you said (and it stems to be) this strange pages value....
Click to expand...
Click to collapse
You have to use your file manager with root permissions. Depending on which file manager you use, this can be done differently. The inbuilt CM12 file manager can be given root permissions in settings, in Root explorer for example you have to mount the directory as r/w.
An yes, you are right, fauxclock says, the settings are in kilobyte, but this is not correct. If you succeed to open the minfree file with your file manager, you will find there exactly the values, you have entered in fauxclock.
Damnit, you're right. Solid explorer doesn't show the content of the directory.... I use it a long time and always had the feeling solid explorer shows me all files...
Cm file manager works, thanks!
mariachi62 said:
Damnit, you're right. Solid explorer doesn't show the content of the directory.... I use it a long time and always had the feeling solid explorer shows me all files...
Cm file manager works, thanks!
Click to expand...
Click to collapse
It does work with solid explorer as well. The point is, there is no option, to set root permissions manually in solid explorer. So the trick is to create a situation, where solid explorer will ask for root access. For example: long press any folder in your system root, tap properties, tap change (attributes) and now press OK, without changing anything. You will be asked for root access.
Now everything should be fine!
got a problem.
parameter file is empty.
using unofficial cm12 on htc one s with icecode kernel
waver1967 said:
got a problem.
parameter file is empty.
using unofficial cm12 on htc one s with icecode kernel
Click to expand...
Click to collapse
problem solved
For solid explorer, just try to open /data and it will ask for root permissions. I do it every time I flash my phone.
Thanks a lot man! I wasn't aware of the skewed minfree files. Was setting them in Trickster and wondering why the apps keep shutting down on me when multitasking. Great work
oll0 said:
Thanks a lot man! I wasn't aware of the skewed minfree files. Was setting them in Trickster and wondering why the apps keep shutting down on me when multitasking. Great work
Click to expand...
Click to collapse
They will still close even so...just not so obvious
Rapier said:
They will still close even so...just not so obvious
Click to expand...
Click to collapse
Uh yes obviously. However they were actually closing the instant i opened another app. Couldnt even keep two apps open at the same time, that was pretty bad.
oll0 said:
Uh yes obviously. However they were actually closing the instant i opened another app. Couldnt even keep two apps open at the same time, that was pretty bad.
Click to expand...
Click to collapse
Yes, I know what you mean. Was the same for me. Having better minfree settings that stick after a reboot helped but didn't solved the issue completely. But at least now phone is usable. I put my hopes in that Google patch they'll release with 5.0.3
Sent from nowhere over the air...
deleted
Thanks for this thread, I changed the permission with "chmod 666" using adb shell, but after a reboot, the files were back to write-only mode, is it normal ? How do you make it permanent ?
Sylvain_44 said:
Thanks for this thread, I changed the permission with "chmod 666" using adb shell, but after a reboot, the files were back to write-only mode, is it normal ? How do you make it permanent ?
Click to expand...
Click to collapse
If it's reverting, I guess the only way would be through an script that runs at boot time. But it's strange, the permissions should stick once set...
Sylvain_44 said:
Thanks for this thread, I changed the permission with "chmod 666" using adb shell, but after a reboot, the files were back to write-only mode, is it normal ? How do you make it permanent ?
Click to expand...
Click to collapse
I used a file explorer with root permissions like root explorer or ES file explorer. My permissions are actually rw-rw-rw, both for adj and minfree file. I guess, this is 666? And they stick after a reboot. But honestly I am not quite sure, if I changed something else. IIRC, I might have changed the permissions for system/etc/init.d/90userinit to rwxr-xr-x. Maybe you want to check this, too.
Well, they don't stick because init.rc sets them to chmod 0220 on boot. That makes me wonder if maybe it was supposed to be like this? I wanted to change it but I don't want to screw anything up. There is a dedicated section for low memory killer in init.rc and only things there are chmod 0220 for those two files and chown for them - so basically the things that we are fixing in this thread. A bug or a feature?
jakubmi9 said:
Well, they don't stick because init.rc sets them to chmod 0220 on boot. That makes me wonder if maybe it was supposed to be like this? I wanted to change it but I don't want to screw anything up. There is a dedicated section for low memory killer in init.rc and only things there are chmod 0220 for those two files and chown for them - so basically the things that we are fixing in this thread. A bug or a feature?
Click to expand...
Click to collapse
Thanks for this hint! Indeed, this might be the other thing, that I had changed. In CM11 roms, the described permissions in init.rc are 664 - both for adj and minfree file. I am not quite sure, if this helps, but it's worth an attempt. You can change the permissions in init.rc to 644, reboot and see, if the permissions for adj and minfree are sticky now. I just did this ,and everything is fine -so you can try without risk, I guess. But I must say, I hadn't the problem before, that the permissions for adj and minfree were reset after reboot. Could be related to the changes in init.rc, but I am not sure.
A weird thing: I made a backup and tried anyway yesterday but after a reboot my init.rc restores itself to normal. I tried another time: Modified the values and saved. After reopening it's still there and it stays there but only until I reboot the phone. After reboot the permissions are not set correctly and init.rc restores itself to original state. Is there something I do not know about modifying init.rc? Because that is the first time I try to do something with it.