I want to edit the build prop
i want to
1. Force launcher into memory
Code:
ro.HOME_APP_ADJ=1
(What do i replace the HOME_APP if im using GOLauncher EX?)
8. Disable debugging notify icon on statusbar
Code:
persist.adb.notify=0
9. Increase overall touch responsiveness
Code:
debug.performance.tuning=1
video.accelerate.hw=1
But i dont know where to add them and they dont register,maybe they do register but i need to reboot?
http://forum.xda-developers.com/showthread.php?t=1227269
Anyone tried Editing their props? Can you confirm if it works for you?
Cat_On_Droid said:
I want to edit the build prop
i want to
1. Force launcher into memory
Code:
ro.HOME_APP_ADJ=1
(What do i replace the HOME_APP if im using GOLauncher EX?)
8. Disable debugging notify icon on statusbar
Code:
persist.adb.notify=0
9. Increase overall touch responsiveness
Code:
debug.performance.tuning=1
video.accelerate.hw=1
But i dont know where to add them and they dont register,maybe they do register but i need to reboot?
http://forum.xda-developers.com/showthread.php?t=1227269
Anyone tried Editing their props? Can you confirm if it works for you?
Click to expand...
Click to collapse
If you upload your build.prop here cat, i will add them lines and post it back
*edit*
Oh wait you already did it? yeah you must reboot. You dont add the launcher, Its a generic rule, It will apply to any launcher present. Just add the lines to the bottom of the build.prop
Alright i rebooted and it does work.
But just to be sure ,how can i check if my HomeLauncher is in Memory ?
Oh and i saw some nice stuff with init.D but am not sure how to apply them do i create a folder? i put the header required but the folder went !!POOF!! It didnt appear there
Cat_On_Droid said:
Alright i rebooted and it does work.
But just to be sure ,how can i check if my HomeLauncher is in Memory ?
Oh and i saw some nice stuff with init.D but am not sure how to apply them do i create a folder? i put the header required but the folder went !!POOF!! It didnt appear there
Click to expand...
Click to collapse
Do something that requires alot of memory, Go watch a youtube video in the stock browers leave it open and go play a game too, when you press home, if the launcher dosen't need to restart it's working
Any scripts in init.d are executed on boot. As long as the scripts are written correctly. You dont put them in folders or they wont work
AndroHero said:
Do something that requires alot of memory, Go watch a youtube video in the stock browers leave it open and go play a game too, when you press home, if the launcher dosen't need to restart it's working
Any scripts in init.d are executed on boot. As long as the scripts are written correctly. You dont put them in folders or they wont work
Click to expand...
Click to collapse
So how do i make the Scripts?
echo "500" > /proc/sys/vm/dirty_expire_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_centisecs
i want this ^
but how i didnt try but is this how you do it ;
go RootExplorer
press newfolder (i forget the other options @[email protected])
make the header and put the code
i dont think its the right way =(
Cat_On_Droid said:
So how do i make the Scripts?
echo "500" > /proc/sys/vm/dirty_expire_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_centisecs
i want this ^
but how i didnt try but is this how you do it ;
go RootExplorer
press newfolder (i forget the other options @[email protected])
make the header and put the code
i dont think its the right way =(
Click to expand...
Click to collapse
what does it say the header has to be?
Init.d
(needs ROM with init.d access and busybox, open empty file, insert header #!/system/bin/sh and put these there, save in /system/etc/init.d and name it something like 77tweaks)
I tried to do it for you, here's the script. Its inside the .zip. You can push it with ADB.
You may have to chmod 777 it too
thnx for the script,but how can i make my own,there are other cool stuff like NET connection fix or something similar
btw ; can i just get the file to my Plays SD,and then move and paste to init.D ? will it work the same?
Cat_On_Droid said:
thnx for the script,but how can i make my own,there are other cool stuff like NET connection fix or something similar
btw ; can i just get the file to my Plays SD,and then move and paste to init.D ? will it work the same?
Click to expand...
Click to collapse
open the scipt in wordpad, look how it is written, write the scripts the same way
if you copy it with root explorer, make sure you give it the right permissions:
rwx-rwx-rwx
Alrighty ,im all set.TY
Cat_On_Droid said:
Alrighty ,im all set.TY
Click to expand...
Click to collapse
Last week you was a noob Now your writing init.d scripts
AndroHero said:
Last week you was a noob Now your writing init.d scripts
Click to expand...
Click to collapse
xD
Related
I was wondering if anyone thought about integrating a theme switcher with modified firmwares. I wonder if its possible without having to reboot to install a different skin.
possible!!
i wud thnk its possible bcuz its the same concept as the jf updater!! it wud just bring up a list of themes to choose from and u pic 1 thn it just does the auto reboot and the name change!! in theory it makes since but im not tht good of a dev. so i cud b wrong!! just gotta wait n c i guess!!
acejoker25000 said:
i wud thnk its possible bcuz its the same concept as the jf updater!! it wud just bring up a list of themes to choose from and u pic 1 thn it just does the auto reboot and the name change!! in theory it makes since but im not tht good of a dev. so i cud b wrong!! just gotta wait n c i guess!!
Click to expand...
Click to collapse
Ouch...my head. Your keyboard seems to be missing some letters.
For the OP, you would need to reboot to apply the update.zip, I don't believe it can be applied without the phone rebooting, even if an application was to do the "switching" for you.
it would be like winterboard in the iphone/ipod touch restart every time you change themes. But i dont mind if an app could do the hole process for me
why not?!?
why is it not possible without a reboot?
as far as i know the themes are only images overwriting the original images...
now only some one has to try it ^^
i found the "framework-res.apk" on my phone (ADP1) in /system/framework
now just cp "NEW-Themed-framework-res.apk" to /system/framework
and restart the home app...
or the app that uses these images .. i dont know when there are loaded ... if they are loaded already on boot we need a reboot!
is anyone brave enough to just force cp the theme file
shouldn't do any harm its linux so what ....
lad
ps probably i will -.-
sounds great in theory, and i like the last post about it being linux so who cares, we can always fix it. but personally i would prefer an app similar to the JFupdater app. the main problem with that is that someone (not me) would have to make sure that the server the app reads from always has the most updated themes, and with our devs posting 10 new themes a day and only getting more since RandumAccess has posted 10 himself in the last two days it would get to be quite a headache. i like both ideas, the app seems like the better one, but please let up know if you get the force cp to work, it might get us on our way
ok
dont try it !!!!!
i did it thru the terminal app and after copying i pressed the home button to see i f anything happend...
well yes ... it rebooted ... and it stuck at booting ...
fixing my phone now ....
JUST DONT TRY IT! ....
Doesent it work like openHome and Bettercut ?
just relink the icons with an app?
I liked a themes icons here but hated what they did with the bars so I just copied the /system/app/ apks to mine and it worked without a reboot. I guess you could just make a program that copies apks around but I'm thinking having themes stored in /data/themes and symlinking the apks would work better. What do you guys think?
DeadBody79 said:
Doesent it work like openHome and Bettercut ?
just relink the icons with an app?
Click to expand...
Click to collapse
i thought so...too
thats why i tried to overwrite them ... but it seems that ii's more complex...
but mabye if we place symlink / hardlinks into the theme package..
and link to a location with the new image (so we can change this image)
something like /data/framework/framework-res.apk/res/drawable
ok i played a little with symlinks and hardlinks
what we need are symlinks with an absolute path
we can copy (with cp -d ) these into the package...
i'll try that ...but it may take a while since i never singed a package...
lad
What if you used scripts to rewrite the data and auto save apply the theme then forclose or cause a light reset? I'm assuming the system would have to be completely rebooted for the textures to take effect!?
ok
i have a problem with signing ...(i am runing linux!)
i did everything according to http://developer.android.com/guide/publishing/app-signing.html
signing on the computer works and even the verification says "jar verified" on every apk that is in my package..
just when i want to update on my dream it says :
verifying update package...
E: No signature (58 files)
E: Verification failed
....
how can i find these unsigned files...?
edit:
ohh and you have to compress the zip via : zip -yr newZip.zip dir
to keep the symlinks
lad
The auto sign programs wont work on linux because that makes it much easier to sign the .apk files and the update.zip. I used to do it manually and it takes way more time than using the sign.bat.
ok
signing problem solved ...
i tried to sign with my private key and not with the "public-update.zip-key"
so i managed to update with the symlink .... and it didn't boot
i checked everything again ... the symlink is now a text file (no wonder android didn't like that....)
... but why?
first i thought that th proses of unzip is destroying the symlink ... but on my com the symlink are always kept
then i noticed when signing a new zip is made and that broke the symlink ....
for signing the update.zip and framework.apk i'm using :
java -jar signapk.jar publickey.x509.pem privatekey.pk8 <themeDir>update.zip <themeDir>newUpdate.zip
(well sort of...)
i will now try to "hack" the signing into my own zip
or does anyone know how to sign it without destroying the symlink?
lad
-.-.....
what i did ...
i copied the symlink into the drawable folder of framework...
i made a zip of framework ... i signed that zip
then i unziped it to copy the symlink again (this time into the just unziped folder)
then i touched (with touch) the symlink and made the timestamp the same as the signed zip
then i ziped that folder .... (it is now signed and has the symlink)
now i only needed to zip and sign the whole update.zip ....
(i unpacked both to see if the symlink was still there... it was!)
i copyed it on he android ... and updated succesful
...but then it didn't boot ..... -.-
now what...?
any ideas?
lad
ps i will try to symlink the whole framework-res.apk .....
edit: pps use at own risk
script for Resigning(use it as a nautilus script):
Code:
#!/bin/bash
#
#use as nautilus script
##########################################
#change to the dir where u have the "signapk.jar", "testkey.x509.pem" and t"estkey.pk8"
##########################################
androidModDir=/home/lad/projekt/android/AndroidMod
java -jar $androidModDir/signapk.jar $androidModDir/testkey.x509.pem $androidModDir/testkey.pk8 "$*" "$*".signed
exit 0
script for Verifying"dirty" (use it as a nautilus script):
Code:
#!/bin/bash
#
#use as nautilus script
export i=`jarsigner -verify "$*"`
zenity --info --title "JarVerifier" --text "Well the outcome is:\n $i"
exit 0
I understand every bit of what you're trying to do. As of right now its obvious that a complete reboot to install the update.zip may be needed to install each skin, but I wonder if you can just do a reboot without an update to rewrite over the previous files then the new files would load a different skin. It shouldn't be so hard since the G1 is like any other cpu or OS platform right!? Keep trying you're getting close to it "Lad!" I'm sure there are more people out there in the world that are willing to give you a helping hand in the process of making this all work out. =)
Idea
What if you just created something that asks which theme you want to use. It then opens something like a file manager with a theme directory list
/themes
-->/theme1
-->/theme2
-->/etc
you choose the theme you want. It asks if you want to backup your current update.zip and then copies the update.zip from the theme folder selected to /sdcard and then reboots and applies the update.
Is that possible. Or even if it just reboots and then you press the power + home key when it restarts and then !!! you have applied the new theme. This would allow you to add/remove themes as you see fit.
OK, here you go
Here is a script for gscript to automate theme switching!
http://forum.xda-developers.com/showthread.php?t=486486
Code:
echo "boot-recovery
--update_package=SDCARD:themes/aero/update.zip" > /cache/recovery/command
reboot recovery
I have all my themes located in /sdcard/themes and a folder with the name. So all you have to do is write scripts for each theme and just place a shortcut on the desktop. With bettercut you could make the icon very representative of the theme.
beagz said:
Here is a script for gscript to automate theme switching!
http://forum.xda-developers.com/showthread.php?t=486486
Code:
echo "boot-recovery
--update_package=SDCARD:themes/aero/update.zip" > /cache/recovery/command
reboot recovery
I have all my themes located in /sdcard/themes and a folder with the name. So all you have to do is write scripts for each theme and just place a shortcut on the desktop. With bettercut you could make the icon very representative of the theme.
Click to expand...
Click to collapse
Here is the original post to this thread.
flip0406 said:
I was wondering if anyone thought about integrating a theme switcher with modified firmwares. I wonder if its possible without having to reboot to install a different skin.
Click to expand...
Click to collapse
I guess we'll have to keep searching and testing things until we can get it all together...........
well, I thought this would help until someone can find a way without doing a reboot.
Until then, this was the easiest method I could find.
I am just about to release my new barebones build with a lot of new features but one thing is killing me. I cannot get superuser to work anymore with the latest build and the latest kernel. Rogue tools won't overclock without SU working and that just totall kills the speed of my build =(. The build is based off scoot's release 5 and I am using the latest kernel with and without the module update SU is unaffected. Everything else works though.
What have you changed from the build i sent you that might effect it? Does it work for you with the original build? Things to check are the sysinit.rc, make sure it calls userinit.sh on startup, and also check your userinit.sh in the /bin directory and make sure the su fix is still present in the file Otherwise, try opening the super user app and downloading the latest su binary file, if it fails to install then you most likely have partition permission issues.
I did edit userinit to enable the odex script. I am gonna check that now.
Ok I am pretty sure that was it. how do I add this line to userinit to have it be proper then? /system/bin/odex.sh
aceoyame said:
Ok I am pretty sure that was it. how do I add this line to userinit to have it be proper then? /system/bin/odex.sh
Click to expand...
Click to collapse
You'd need to put it in sysinit.rc like this :
service odex /system/bin/odex.sh
So put that line right at the end then? Or is there a special format it has to go in. Sorry, I have just never had to edit this particular file before lol.
aceoyame said:
So put that line right at the end then? Or is there a special format it has to go in. Sorry, I have just never had to edit this particular file before lol.
Click to expand...
Click to collapse
At the end is fine, you will see some similar lines in there, you may want to add some options such as :
console
user root
oneshot
I don't know what the structure of the odex script is so i don't know which options you will need to get it to run properly but these are the most likely, just experiment and see
I've always put it at the end, after the su fix just as "/system/bin/odex.sh" and nothing else. What does service do? will it run it continuously or just with different permissions?
I would say its more likely that something's gone wrong while you edited userinit.sh, and now it can't be executed.
did you edit it in windows? you may have /n/r line endings now instead of /n
if you did it in linux it may be a permissions problem
fixed! I used the userinit from my old barebones. Something changed in the update. The two looked totally different.
Guys I looked around and didnt find anything regarding our phones and this script so I decided to post it here. If I missed it and there is a thread about it, forgive me.
Recently the developer updated his script so it can run on ICS too. Is anyone running the script?? Would it be useful for our phones?
http://forum.xda-developers.com/showthread.php?p=16635544#post16635544
atsavlis said:
Recently the developer updated his script so it can run on ICS too. Is anyone running the script?? Would it be useful for our phones?
Click to expand...
Click to collapse
Nope.
and
Probably not much use at all. Zeppelinrox originally created it for phones with low amounts of memory (originated on the milestone which has 256mb and would constantly kill the launcher etc), I'm not sure if anythings changed now in the script, but we have heaps of memory, and I just don't see the point.
That's weird... this device has the most supercharged services.jar downloads...
http://android.mimic.ca/
Hmmmm, interesting... Hopefully someone who has an idea can shine some light for us. There must be a reason the script developer created a section specifically for ICS??
atsavlis said:
Hmmmm, interesting... Hopefully someone who has an idea can shine some light for us. There must be a reason the script developer created a section specifically for ICS??
Click to expand...
Click to collapse
Shhhh! He's behind you ........
I think this could potentially be a problem with DroidTheory's SHO script in this AXIOM XBREAD.
I don't know but I guess zeppelin can find out for us? :O
It did wonders for my Samsung Captivate.
I'm currently running it on the latest AOKP build, but it was one of the first things I installed. So I don't really have a feel for what the Nexus is like without it.
TwinkyOfHope said:
It did wonders for my Samsung Captivate.
I'm currently running it on the latest AOKP build, but it was one of the first things I installed. So I don't really have a feel for what the Nexus is like without it.
Click to expand...
Click to collapse
What options are you using?
TwinkyOfHope said:
It did wonders for my Samsung Captivate.
I'm currently running it on the latest AOKP build, but it was one of the first things I installed. So I don't really have a feel for what the Nexus is like without it.
Click to expand...
Click to collapse
Could you give us a quick rundown of what you did?? Specifically did you do that whole process about ODEX/DEODEX roms??
Make sure you have terminal emulator before replacing your services.Jar!
First use root browser to copy your services.Jar to your sdcard it is in the /system/framework folder.
Then go to http://android.mimic.ca and upload your services.Jar file.
Afterwards, I downloaded the modified services.Jar because the flashable cwm option didn't work for me.
I copied the modified services.Jar to /system then changed its permissions to the same permissions of the other .jar files in the /system/framework folder.
Then move the services.Jar with changed permissions to the /system/framework folder.
Once you have done that, open up terminal emulator.
Type this out, and press enter when said:
Su enter
Cd /system/framework enter
Chown 0.0 services.Jar enter
Chmod 644 services.Jar enter
Then reboot!
Start Up script manager.
Browse to the supercharger v6 pdf and click on it. Press su to run the script with superuser permissions.
The script will load and is mostly self explanatory. It will take you through the options when you first run it. I put the text scrolling on fast and disable the animation and integrate when it asks.
When you get back to the main menu, I usually use option 10. It calculates what minfree values to use based on the ram of the phone.
After all this, reboot once more and run the script again to see if you are 100% supercharged!
EDIT: if you run into bootloops by moving your services.Jar incorrectly, then just reflash your rom without wiping.
Sent from my Galaxy Nexus using XDA
Option 10 asks us to input our own Ram value, is this correct?? If so, what did you set it to?
atsavlis said:
Option 10 asks us to input our own Ram value, is this correct?? If so, what did you set it to?
Click to expand...
Click to collapse
Option 10 shouldn't ask you to input anything else. It should use the minfree calculator and set itself. Are you using update9 RC7? If it still isn't working for you, then try option 8 which should be the 768 settings
Sent from my Galaxy Nexus using XDA
i followed everything but when i run the first line of code i get
sh: cd/system/framework: not found
not sure if its because of the binary
You're missing a space.
zeppelinrox said:
You're missing a space.
Click to expand...
Click to collapse
thanks i just noticed that. funny thing is when i was on liquids rom they had a cwm zip file to flash for that rom and was able to bypass the cd /system/framework, enter, chown 0.0 services.jar, enter, chmod 644 services.jar, enter stuff. i am not sure if the stuff carried over but it let me run it on aokp31 release without it and it runs smoothly. phone is exactly the way i want it super snappy
Any use of the script on stock jelly bean?
Sent from my Galaxy Nexus
Force enable lockscreen rotation
Code:
setprop lockscreen.rot_override true
Force disable lockscreen rotation
Code:
setprop lockscreen.rot_override false
On devices that already can rotate, this does nothing.
Code should work on all AOSP ROMs with lockscreens that don't rotate, unless the code there has been modified.
Resets on reboot though I think
Great find. Thanks!
Thanks man, I have a DIY dock for mine and the fact I had to enter my PIN sideways everytime I unlock my device driving me insane.
Can this code be used on the fly? I'm using a app at the moment (called Rotate) which can enable, disable lockscreen rotation. however this is heavy on memory and I want to simply do this with a script in Tasker.
---------- Post added at 04:58 PM ---------- Previous post was at 04:37 PM ----------
Just ran this from terminal emulator as root and it worked! Awesome - but it is lost on reboot so I need to be able to run this as a script in tasker - scripting looks tricky in Tasker though. Open to ideas!
I have enabled rotation by modifying bools.xml file and now I get to know that JB 4.2 has different rotation texts to enable rotation!
How about Launcher?
privatesam said:
Just ran this from terminal emulator as root and it worked! Awesome - but it is lost on reboot so I need to be able to run this as a script in tasker - scripting looks tricky in Tasker though. Open to ideas!
Click to expand...
Click to collapse
If you run it from a terminal emulator, it's temporary. If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
manumanfred said:
I have enabled rotation by modifying bools.xml file and now I get to know that JB 4.2 has different rotation texts to enable rotation!
How about Launcher?
Click to expand...
Click to collapse
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Awesome. This worked for me on 4.1.2 as well. Thanks!
Really useful in the car since I don't have the official car dock. No more unlocking sideways!
Cilraaz said:
If you run it from a terminal emulator, it's temporary. If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Click to expand...
Click to collapse
I know that, that's why I have modified bools.xml file to enable rotation on launcher + lockscreen.
I think JB 4.2.x have also the changed code for launcher rotation...
manumanfred said:
I know that, that's why I have modified bools.xml file to enable rotation on launcher + lockscreen.
I think JB 4.2.x have also the changed code for launcher rotation...
Click to expand...
Click to collapse
Does anyone have an answer to whether they have changed the code in 4.2? I can't find a bools.xml file anywhere - and no one seems to point at it. Also, no one says exactly where the suggested code should sit in the build.prop file - at the end, in the 'build' section, at the front? And it doesn't work on android 4.2.2 as far as I can tell although the terminal emulator temporary method works. And while you're firguring that out - can you tell me a way (without an app) to get the screen to stay awake after rebooting? Why won't that option remain set in Developer Options?
dosent work for me
xaueious said:
Force enable lockscreen rotation
Code:
setprop lockscreen.rot_override true
Force disable lockscreen rotation
Code:
setprop lockscreen.rot_override false
On devices that already can rotate, this does nothing.
Code should work on all AOSP ROMs with lockscreens that don't rotate, unless the code there has been modified.
Resets on reboot though I think
Click to expand...
Click to collapse
I tried this command in the terminal and no error message came.i.e it got executed properly Then when i see the lock-screen it is always in portrait mode.
Cant manage to get it to landscape mode. My auto rotation is on.
I am on 4.2.2 and using NOVA launcher. Xperia S OPENSEMC ROM.
Any idea y i am not able to rotate my lockscreen ??
siddharthisback said:
I tried this command in the terminal and no error message came.i.e it got executed properly Then when i see the lock-screen it is always in portrait mode.
Cant manage to get it to landscape mode. My auto rotation is on.
I am on 4.2.2 and using NOVA launcher. Xperia S OPENSEMC ROM.
Any idea y i am not able to rotate my lockscreen ??
Click to expand...
Click to collapse
Run Terminal as root, type "su" (no quotes), then enter, then the command.
Cilraaz said:
... If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
Click to expand...
Click to collapse
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
dark0shark said:
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
Click to expand...
Click to collapse
Thank you for this. I wasn't sure if there was a specific spot in build.prop where I had to insert the line. The temporary fix in Terminal Emulator worked for me, but now it sticks after boot! I was sick of having to unlock my device sideways when it was in my car mount. The only weird thing is that it smooshes my wallpaper instead of switching to the landscape orientation, but I can live with that.
laur3n.newm4n said:
... I was sick of having to unlock my device sideways when it was in my car mount.
Click to expand...
Click to collapse
Yes, the car mount in heads up position with the cables (USB-power and 3,5 audio jack) to the bottom were exactly my reason to add this option permanently, too. The position of this environment variable in the configuration file build.prop does not matter, it is just common sense to add additional lines at the end, so you can find them easily.
dark0shark said:
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
Click to expand...
Click to collapse
Thank you for outlining this -- it helped me remember what to do!
and kaferei
Jeffreycat said:
Thank you for outlining this -- it helped me remember what to do!
Click to expand...
Click to collapse
Indeed -- very helpful and worked for me as well!
basic build.prop editing to enable pie on sgh-i747m
Shibang said:
Indeed -- very helpful and worked for me as well!
Click to expand...
Click to collapse
Thanks for providing the info on this basic build prop prop editing !
Ive been reading CyanogenMod 10.1 – A Complete Hands-On Review & Guide
by Haroon Q Raja and really wanted to enable Pie,etc on my rooted Samsung SGH I747m. With your help I was able to edit my build prop as was suggested by a comment I picked up on to:
ro.product.manufacturer=LGE
ro.product.model=Nexus 4
This didnt make any difference. Is there something else that needs to be changed?
Samsung G3 SGH-I747M Rogers
Cilraaz said:
...
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Click to expand...
Click to collapse
Redscorpian said:
Does anyone have an answer to whether they have changed the code in 4.2? I can't find a bools.xml file anywhere - and no one seems to point at it. Also, no one says exactly where the suggested code should sit in the build.prop file - at the end, in the 'build' section, at the front? And it doesn't work on android 4.2.2 as far as I can tell although the terminal emulator temporary method works. And while you're firguring that out - can you tell me a way (without an app) to get the screen to stay awake after rebooting? Why won't that option remain set in Developer Options?
Click to expand...
Click to collapse
No one can tell?
Some users who flashed the leaked JWR66N on their N4's report there is no full app rotation anymore in the Camera app, just the icons. So another change to feel optimistic about 4.3.
madd0g said:
Some users who flashed the leaked JWR66N on their N4's report there is no full app rotation anymore in the Camera app, just the icons. So another change to feel optimistic about 4.3.
Click to expand...
Click to collapse
Speaking of the camera, I played around with a iPad yesterday at the local store, i felt that Apple's shutter button have a better placement as compared to Google's. The shutter button is placed by the right side of the app, falls just nice of my thumb.
Beamed from my Grouper
I have tried many of stock HTC Flashlight APKs on my WFS+CM9+MIUIv4, but none of them worked. Then I digged the error log using logcat and fixed the issue. It was simply due to permissions. Change the permissions of the file /sys/class/leds/flashlight/brightness to 666, if the flashlight works fine, then you may need to create a /etc/init.d script to set permission each time device boots.
Create a file in /etc/init.d with following line
chmod 666 /sys/class/leds/flashlight/brightness
Click to expand...
Click to collapse
ENJOY!!! HIT THANKS AND LET HELP OTHERS!!!
painkalshafeer said:
I have tried many of stock HTC Flashlight APKs on my WFS+CM9+MIUIv4, but none of them worked. Then I digged the error log using logcat and fixed the issue. It was simply due to permissions. Change the permissions of the file /sys/class/leds/flashlight/brightness to 666, if the flashlight works fine, then you may need to create a /etc/init.d script to set permission each time device boots.
Create a file in /etc/init.d with following line
ENJOY!!! HIT THANKS AND LET HELP OTHERS!!!
Click to expand...
Click to collapse
A really good find...... Good for people who still want some sense stuff in custom roms
I personally never used the HTC application, but will try this sometime
ill try nextime.. busy for work right now, anyway tnx!
I would like to ask something, a little offtopic, but I'm sorry. Could the same be applied for Link2SD? In the custom rom that I use (gb_2.3.7) every time I reboot it doesn't show the apps and I have to recreate mount scripts and "quick reboot". So if I write something relevant on the android emulator to give permission would it be solved..?
Again, sorry for the offtopic.
polfrank said:
I would like to ask something, a little offtopic, but I'm sorry. Could the same be applied for Link2SD? In the custom rom that I use (gb_2.3.7) every time I reboot it doesn't show the apps and I have to recreate mount scripts and "quick reboot". So if I write something relevant on the android emulator to give permission would it be solved..?
Again, sorry for the offtopic.
Click to expand...
Click to collapse
Any script put in /etc/init.d will be executed at boot time.
Still stick with GB??? even JB 4.2 is arrived for our WFS :good: