OK guys thanks for the efforts of team EOS and rlasalle15 we now have another working AOSP ROM. Along with every AOSP ROM some will want soft keys over hardware keys so I compiled a .zip to do this.
Step 1: Flash this file View attachment 1859121
Step 2: Go to etc/init.d/99keyoff/ change from rw-rw-r to rwx-rwx-r to disable key backlight.
Please flash through TWRP. There is no brick risk with this!
Thanks to:
wewooo (based off his original file for CM10.1)
VoluntaryMan (He was the last one to post the manual way to get this)
Just curious, what did you modify in weewoo's zip?
Sent from my LG-LS970 using xda app-developers app
I had to make changes to the build. Prop so that it would work on team eos. His was designed with shellnut2's CM10.1 Build
Sent from my LG-LS970 using xda premium
neemot said:
I had to make changes to the build. Prop so that it would work on team eos. His was designed with shellnut2's CM10.1 Build
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Sorry to ask, but how do I change the permission to RWX,RWX,R--? what app do i have to use? Im on cm10.1 btw using wewoo flashable zip
Hitsugaya111 said:
Sorry to ask, but how do I change the permission to RWX,RWX,R--? what app do i have to use? Im on cm10.1 btw using wewoo flashable zip
Click to expand...
Click to collapse
Use a root file explorer and navigate to where the file is placed. I use root explorer. Hold the file and a popup with options come up. Hit permissions then check execute on the right for the first 2.
Sent from my LG-LS970 using xda app-developers app
Is there anyway to completely disable hard keys? So if my fat fingers touch them they won't work?
Take the file in the zip named keypad_8064.kl and put it in system/use/keylayout/. Overwrite the existing one. Reboot.
Sent from my LG-LS970 using xda app-developers app
neemot said:
OK guys thanks for the efforts of team EOS and rlasalle15 we now have another working AOSP ROM. Along with every AOSP ROM some will want soft keys over hardware keys so I compiled a .zip to do this.
Step 1: Flash this file View attachment 1859121
Step 2: Go to etc/init.d/99keyoff/ change from rw-rw-r to rwx-rwx-r to disable key backlight.
Please flash through TWRP. There is no brick risk with this!
Thanks to:
wewooo (based off his original file for CM10.1)
VoluntaryMan (He was the last one to post the manual way to get this)
Click to expand...
Click to collapse
By the way, this isn't the most optimal way to add the keys. In your zip, you're flashing a new build.prop basically messing up the build.prop if they had any tweaks. You should be running a .sh within the updater script that writes this line to build.prop
If you open the lifeless rom, you'll see it done there with a lot of build.prop tweaks.
so have a file like this in the root of the zip called softkeys.sh with the following written inside.
#!/sbin/sh
echo "#qemu.hw.mainkeys=0" >> /system/build.prop
And then alter the updater script to have the following
package_extract_file("softkeys.sh", "/tmp/softkeys.sh");
set_perm(0, 0, 0777, "/tmp/softkeys.sh");
run_program("/tmp/softkeys.sh");
Related
So after desperatley wanting this mod to work on my captivate glide at any cost, i went after it myself. It looked easy at first but turned out to consume a lot of hours figuring out how to compile decompile and understand basics of smali.
What it does ?
As in the title, pressing the volume buttons a little longer (400 ms) will make the stock music player skip to next track (up vol) or previous track (down vol). This only works while the screen is off and phone locked which is basically the purpose . Right now will work on deodexed ROMs only, meaning pepole having "android.policy.odex" file in the system/framewrok folder would not be able to use this mod.
Caution : The mod if goes wrong can/will make your phone stuck at the boot animation unless the mod is removed. Copy both the files so you can restore your original file back in case it doesn't work for you.
How to Install
1) Make sure you are rooted. and boot into CWMR.
2) Flash LongPressVol.zip - Installs the mod and takes backup
3) Wipe Dalvik and Cache partition
4) Reboot and "Upgrading android" screen should show up.
You are done and now test it and let me know if it works for you. Enjoy!!!
Restore original/Remove Mod :
1) Boot into CWMR.
2) Flash LongPressVolRemove.zip - Restores your original android.policy.jar file
3) Wipe Dalvik and Cache partition
4) Reboot
Tested to be working fine on following ROMs
Nardholio's NardROM 0.4
Thegreatergood's LiteROM .4
Credits : Ported with help from the guide posted by jakubklos -> http://forum.xda-developers.com/showthread.php?t=1770564
Next update :
CWM flashable zip (will need some time to learn how to do that - Done
Post the Diff and the code to make it easier for other roms to include it if the android.policy.jar changes. - In progress
Awesome, been missing this mod since leaving my DHD
CWM Flashables worked great..... But since I'm using the stock rom which has not been deoxed it did not work.
It booted though didn't notice any adverse affects
Not to put you on the spot but do you think you could use the UCLH2 .jar and make a version that will use odex. not sure if anything would have to be done to the odex file but I have included the non odexed android.policy.jar files if you wouldn't mind taking a stab at it. If you could just modify the .jar file I'll test it. I would be forever in your debt!
Sent from my SGH-I927 using xda premium
Force closes PowerAMP and Nova Launcher.
Tested on ICS Leak.
Just delete the odex file and clear cache and you should be fine. You don't have to deodex the whole ROM.
or for extra points you can reodex, which theoretically will boost speeds a bit (although I'm experiencing wonderful speeds on my ROM). Redodexing is pretty easy (just Google it) and doesn't require him to do his mod again.
Cool thanks for the tip!
Sent from my SGH-I927 using xda premium
ludacris1 said:
Force closes PowerAMP and Nova Launcher.
Tested on ICS Leak.
Click to expand...
Click to collapse
Strange works for me. Nova didn't quit at all throughout my testing. I tried Poweramp trial and works fine as well. Did you clear dalvik and cache after flashing in the Mod ?
Nardholio said:
Just delete the odex file and clear cache and you should be fine. You don't have to deodex the whole ROM.
or for extra points you can reodex, which theoretically will boost speeds a bit (although I'm experiencing wonderful speeds on my ROM). Redodexing is pretty easy (just Google it) and doesn't require him to do his mod again.
Click to expand...
Click to collapse
Tried with no success stuck at boot screen. Thanks for the hint I'll try re odexing it and see if that will work next.
I like all the bloat that the stock has except the att apps, I would love to try your ROM but I would prefer a completely stock version of it with little modification and fixes. I have tried to do it myself with no success and simple don't have the patience for it. As my computer would end up at the muzzle end of a AR15. I really don't want to waste ammo or buy a new computer just yet. LOL ^o^
I'm very happy with the stock rom after applying the keyboard, tethering fix, and sdcard swap. It will be perfect when I get this working on it. And if its true that having it odexed is faster, I don't know but it is very smooth and battery is awesome.
Sent from my SGH-I927 using xda premium
enewman17 said:
Awesome, been missing this mod since leaving my DHD
CWM Flashables worked great..... But since I'm using the stock rom which has not been deoxed it did not work.
It booted though didn't notice any adverse affects
Not to put you on the spot but do you think you could use the UCLH2 .jar and make a version that will use odex. not sure if anything would have to be done to the odex file but I have included the non odexed android.policy.jar files if you wouldn't mind taking a stab at it. If you could just modify the .jar file I'll test it. I would be forever in your debt!
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
As evident from your last post, it does not work for you on UCLH2. As i said in my OP that i've not tested it on LH2 and it might not work as the android.policy.jar may be different. It should work on the UCLG9 and the ROM's based on it for sure.
I'll see later what i can do for the LH2. Can you post me a link of your whole system/framework folder, so i can download the same ? I'll maybe try later in the day to see the difference.
Thanks you, much appreciated! http://db.tt/0PnPOv4p
Sent from my Transformer TF101 using XDA Premium HD app
enewman17 said:
Thanks you, much appreciated! http://db.tt/0PnPOv4p
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
Deodexed your files and compared the PhoneWindowManager.smali file with mine, they are binary equals. So technically this mod should work for you. As your ROM is odexed, you need to manually delete the android.policy.odex and android.policy.jar file and then copy the android.policy.jar file from the zip attached to the OP. Remember to clear dalvik and cache partition as the last step before rebooting your phone. As Nardholio suggested this should work and you don't need to deodex the whole ROM.
Updated OP with the name of the ROM's tested to be working fine with this mod. Will try some more and keep adding.
Sent from my SGH-I927
Nardholio said:
Just delete the odex file and clear cache and you should be fine. You don't have to deodex the whole ROM.
or for extra points you can reodex, which theoretically will boost speeds a bit (although I'm experiencing wonderful speeds on my ROM). Redodexing is pretty easy (just Google it) and doesn't require him to do his mod again.
Click to expand...
Click to collapse
Do not delete the odex file... in an odex ROM all the code, java and smali are located in the odex class until you deodex which pulls the classes out and compresses them into a classes.dex into the particular apk and/ or jar file. So, if you delete the odex file the jar or apk is useless as you just deleted all the java and smali code it uses to communicate with the DVM..
Sent from my SGH-I897 using xda premium
dman3285 said:
Do not delete the odex file... in an odex ROM all the code, java and smali are located in the odex class until you deodex which pulls the classes out and compresses them into a classes.dex into the particular apk and/ or jar file. So, if you delete the odex file the jar or apk is useless as you just deleted all the java and email code it uses to communicate with the DVM..
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Deodexing is all clear and i know the procedure, but can you let me know some link or tutorial to follow to odex it back again ? I think it needs the whole rom and needs some more files like framework etc. to be odexed again ?
Note: still learning and long way to go
In my trying to learn all of this too, seems you can re-odex a rom. But everything I found has to be done on the phone it self with terminal and a odex wrapper script. Haven't found a way of doing it on a computer yet.
Sent from my SGH-I927 using xda premium
enewman17 said:
In my trying to learn all of this too, seems you can re-odex a rom. But everything I found has to be done on the phone it self with terminal and a odex wrapper script. Haven't found a way of doing it on a computer yet.
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
I've read some tutorials as well, but lemme know if you find a easier way to do this. I'm almost certain that the odex files are specific to a specific rom, but i can be wrong as well. That's the reason i believe that the generic mods are only for the deodexed ROMs.
enewman17 said:
Awesome, been missing this mod since leaving my DHD
CWM Flashables worked great..... But since I'm using the stock rom which has not been deoxed it did not work.
It booted though didn't notice any adverse affects
Not to put you on the spot but do you think you could use the UCLH2 .jar and make a version that will use odex. not sure if anything would have to be done to the odex file but I have included the non odexed android.policy.jar files if you wouldn't mind taking a stab at it. If you could just modify the .jar file I'll test it. I would be forever in your debt!
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
I don't realize there was a Dial Home Device on earth, I though it was never found
*stargatefan*
TheHow7zer said:
I don't realize there was a Dial Home Device on earth, I though it was never found
*stargatefan*
Click to expand...
Click to collapse
Lol love stargate
Sent from my Desire HD using xda premium
---------- Post added at 07:13 PM ---------- Previous post was at 06:47 PM ----------
ninthsense said:
I've read some tutorials as well, but lemme know if you find a easier way to do this. I'm almost certain that the odex files are specific to a specific rom, but i can be wrong as well. That's the reason i believe that the generic mods are only for the deodexed ROMs.
Click to expand...
Click to collapse
Yes the odex file is specific per app so if any changes were made, the odex file which contains most of the data for each app would also have to reflect those changes. As the changes you made were part of .smali which is part of the dex file. So on a stock rom the odex file is loaded into the Dalvik machine during boot. This is why when flashed on a odexed rom the mod does not take, because the non modded odex file was already loaded. I gave up as I'm happy using literom4 with your mod.
Edit: Ok here is why it has to be done using the phone, all has to do with BOOTCLASSPATH http://classictomatoe.net/dexo-universal-odex-tool/
If you wanted to make this mod for folks still using the stock rom. All that needs to be done is decompile the .odex file using baksmali make the changes to the necessary files and then smali ?I think? don't quote me on that.
Can you share the how to four this? I'm setting up a rom and would like to add this
Sent from my SGH-I927 using xda app-developers app
kick buttowski said:
Can you share the how to four this? I'm setting up a rom and would like to add this
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Would you use the new uclj3 ? Send me the androidpolicy jar from your rom and hopefully it should be the same. I've not upgraded to .8 literom yet so not sure if it will work as .8 is based on the newer uclj3 released by samsung.
Sent from my SGH-I927
ninthsense said:
Would you use the new uclj3 ? Send me the androidpolicy jar from your rom and hopefully it should be the same. I've not upgraded to .8 literom yet so not sure if it will work as .8 is based on the newer uclj3 released by samsung.
Sent from my SGH-I927
Click to expand...
Click to collapse
Here ya go
As the title says this MOD will remove your emergency call button in the pattern lockscreen.
I´ve modified the Pattern Lockscreen this way the button diasppears. So no more unwanted emergency calls while you have your phone in your pocket.
Just remember. Noone else will be able to call with your phone in case of emergency unless he/she knows how to unlock your phone.
Since there are various custom ROMs with a modified framework and since the framework in Arcos CM9 may differ in each release, I decided to write a little HOWTO.
First you need is my modified pattern lockscreen xml file you can download here:
Rapidshare or Dropbox
Extract it and copy the framework-res.apk from your phone or your flashable ROM to your PC.
Open the framework-res.apk with 7zip and navigate to the res\layout folder there.
Copy and paste my keyguard_screen_unlock_portrait.xml into this folder to replace the current xml file there.
Close 7zip and move the modified framework-res.apk to your sdcard.
Move it to the system folder in your phone and set the permissions to rw-r-r.
Use Root Explorer for the following step!
After the permissions were set correctly, move it to the framework folder and reboot your phone.
That´s all.
Below is a flashable Zip for Arcos beta3.
Rapidshare
Dropbox Mirror
yow honey!
you rock!
-salute!
By only for the vanilla cm9 by arco, do you mean that it won't work on the roms based on it like biohazard?
Sent from my GT-I8150 using xda app-developers app
Gary122 said:
By only for the vanilla cm9 by arco, do you mean that it won't work on the roms based on it like biohazard?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Well. The modification is inside the vanilla framework and this mod is flashing the modified vanilla framework, so can´t tell. But as long as the framework isn´t modified there, it will. Unfortunally a lot of custom ROMs are using modified frameworks. These would need to be modified as well.
honeyx said:
Well. The modification is inside the vanilla framework and this mod is flashing the modified vanilla framework, so can´t tell. But as long as the framework isn´t modified there, it will. Unfortunally a lot of custom ROMs are using modified frameworks. These would need to be modified as well.
Click to expand...
Click to collapse
I tried it on my biohazard it works! Thanks bro.
Sent from my GT-I8150 using xda app-developers app
I want to know how hard it is to make your own custom ROM. How much time will it take me and is there a good and clear guide?
Thanks
Sent from my Galaxy Nexus using xda app-developers app
First, you should read the sticky that talks about setting up and compiling aosp. It's in General. You'll need Linux.
sent from my Google Galaxy Nexus
What results are you trying to achieve by doing your own Rom?
It really isn't hard once you're set up for it. You'll need Linux which isn't a big deal cause its free just make sure if you don't straight boot to Linux you give your VM enough space to sync a repo
Sent from my Galaxy Nexus using xda premium
Thanks everybody. I am quite a noob. Anyone knows a clear guide?
Sent from my Galaxy Nexus using xda app-developers app
Creating ROM from OTA is really easy, I don't like ROMs which is built from sources so I don't never use AOSP ROMs..
Creating Rom OTA (the easy way):
Make Custom nandroid backup via Nexus toolkit: System folder and boot files "system.img" & "boot.img"
then add system.img and boot.img to .zip file and then you have to use Ubuntu to install Dsixda's Android kitchen and then add the .ZIP file to Original_update folder.
Then open menu.sh via terminal and then choose:
"1. Set up working folder from ROM"
when it asks something then always write yes, except then if it asks do you wan't to delete recovery bla bla bla...
and when it asks about the update script then select the default one "amend bla bla bla (1)"
Now it is ready to begin modifying it..
select (0) and then (11) and de-odex ROM then add init.d support, add busybox and root permissions, extract boot.img and ipen default.prop from boot_extracted folder and change the ro.secure line from 0 to 1, then it is insecured.. build boot.img from the extracted files..
then (99) build ROM..
or download apktools and modify apps, e.g. enabling rotation from default android launcher or from lockscreen..
etc.
It's easy.. but building ROM from sources is harder and requires enough good PC with 64-bit CPU..
DDd
manumanfred said:
and ipen default.prop from boot_extracted folder and change the ro.secure line from 0 to 1, then it is insecured..
Click to expand...
Click to collapse
Wrong, ro.secure=0 IS already insecure.. And another tip: ccache.
Lol... This is a Nexus, why don't you like to build from source? That's a joke, right? Seems to me that you are holding it wrong.
sent from my Google Galaxy Nexus
manumanfred said:
Creating ROM from OTA is really easy, I don't like ROMs which is built from sources so I don't never use AOSP ROMs..
Creating Rom OTA (the easy way):
Make Custom nandroid backup via Nexus toolkit: System folder and boot files "system.img" & "boot.img"
then add system.img and boot.img to .zip file and then you have to use Ubuntu to install Dsixda's Android kitchen and then add the .ZIP file to Original_update folder.
Then open menu.sh via terminal and then choose:
"1. Set up working folder from ROM"
when it asks something then always write yes, except then if it asks do you wan't to delete recovery bla bla bla...
and when it asks about the update script then select the default one "amend bla bla bla (1)"
Now it is ready to begin modifying it..
select (0) and then (11) and de-odex ROM then add init.d support, add busybox and root permissions, extract boot.img and ipen default.prop from boot_extracted folder and change the ro.secure line from 0 to 1, then it is insecured.. build boot.img from the extracted files..
then (99) build ROM..
or download apktools and modify apps, e.g. enabling rotation from default android launcher or from lockscreen..
etc.
It's easy.. but building ROM from sources is harder and requires enough good PC with 64-bit CPU..
DDd
Click to expand...
Click to collapse
Isn't that just modifying my current ROM with my own name?
bk201doesntexist said:
Wrong, ro.secure=0 IS already insecure.. And another tip: ccache.
Lol... This is a Nexus, why don't you like to build from source? That's a joke, right? Seems to me that you are holding it wrong.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
Building from source is a lot harder, or isn't it?
Sent from my Galaxy Nexus using xda app-developers app
It's not hard to build from source, it just takes a LONG time! Then you've gotta learn how to add mods from Gerrit code, etc. and it can be annoying.
Making a ROM using dsixda's kitchen is easier as you're using the stock image as a base so it'll work but you've then got more of a task getting new code in as you've gotta decompile it all, edit it and then recompile
mrgnex said:
Isn't that just modifying my current ROM with my own name?
Building from source is a lot harder, or isn't it?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yep, then you make own ROM from the stock ROM..
Building ROM from source is different thing and harder..
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
bk201doesntexist said:
Wrong, ro.secure=0 IS already insecure.. And another tip: ccache.
Lol... This is a Nexus, why don't you like to build from source? That's a joke, right? Seems to me that you are holding it wrong.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
oh yeah, sorry: from 1 to 0!
I don't like AOSP ROMs, except CM ROMs but I don't want to use CM ROM on my Nexus.
Ummm. Any ROM you compile is from source. It doesn't take a long time. My dual core 2.4 GH laptop will do it in a couple hours. There are several tutorials online. If you're willing to learn it's not that hard. Compiling aosp or cm is pretty much the same process.
CM File manager [Universal] Download is right Here!!!
Sorry about that forgot put link up, enjoy.
Where is the link?
Sent from the scary door.....
Just an FYI OP you didn't post a link (i don't know if you meant to or not)
For anyone wishing to accomplish this yourselves, download the newest nightly build of CM, pull the apk from /system/app, and install it.
Sent from my SGH-I747 using xda app-developers app
drinfernoo said:
For anyone wishing to accomplish this yourselves, download the newest nightly build of CM, pull the apk from /system/app, and install it.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Maybe mention they should use 7zip to do this, don't have to but works nice
xxsicknessxx said:
Maybe mention they should use 7zip to do this, don't have to but works nice
Click to expand...
Click to collapse
They don't have to. If anyone feels like they have to do this, they should probably know how to open a zip file, and since CM packages it's releases in zips, Windows, Mac, and Linux can open them natively, or they could use any manner of zip utility like 7Zip, WinZip, WinRAR, or even an Android one like AndroZip, if they wanted to do it right on their phone.
Another good resource is the DIY Aroma installer, (search, don't have a link handy) which you can use to build a flashable zip of any apk(s) you want.
Sent from my SGH-I747 using xda app-developers app
does any one know how to add apps to a rom while porting and after that does i have to edit some think in build.prop please help me i want to port a rom for lg p690 and want some apps in it so please help me
guys if u found my question useful then thank me
It depends on some apps. Some are tied to system folders and some aren't.
Which ones are you trying to add?
And no need for build.prop edits
Sent from my HTC One X using xda premium
just download the .apk and with Esexplorer mount system as r\w and copt the apk to ^^system root/app^^ touch and hold copied apk and change permission and tick all apply and REBOOT!
WALLAH!!!!!!!!:victory:
i want to add you tube and camera.apks so what to do
J.E.abhishek kumar said:
i want to add you tube and camera.apks so what to do
Click to expand...
Click to collapse
just put them in your rom's /system/app folder
then can i flash my rom after pasting the apks
I want to change the kernel in Miui v5 How to do it?
the boot.img in rom zip is kernel so u can try to change it .just put the boot.img of any rom like for cm to cm and aokp toaokp.etc built for your device and had not tried it yet so try it on your wn risk and reply what happened
waleed78636 said:
just download the .apk and with Esexplorer mount system as r\w and copt the apk to ^^system root/app^^ touch and hold copied apk and change permission and tick all apply and REBOOT!
WALLAH!!!!!!!!:victory:
Click to expand...
Click to collapse
Wallah bro?
J.E.abhishek kumar said:
then can i flash my rom after pasting the apks
Click to expand...
Click to collapse
It depends if your roms format is correctly. Deleting something that is required by the system bootloops the rom.
What are you pasting them with?
i want learn too
Sent from my YP-G70 using xda app-developers app
J.E.abhishek kumar said:
does any one know how to add apps to a rom while porting and after that does i have to edit some think in build.prop please help me i want to port a rom for lg p690 and want some apps in it so please help me
guys if u found my question useful then thank me
Click to expand...
Click to collapse
You shouldn't be porting ROMs if you don't know this..
just drag your app to flashable zip rom
Sent from my SCH-i509 using xda premium
J.E.abhishek kumar said:
does any one know how to add apps to a rom while porting and after that does i have to edit some think in build.prop please help me i want to port a rom for lg p690 and want some apps in it so please help me
guys if u found my question useful then thank me
Click to expand...
Click to collapse
Just put the .apk file in the app folder and compress it but some application also need lib files with them
So make sure you also put them in lib folder
Sent from my HTC Explorer using xda premium
Tell me how framework edit? For add app while porting ROM??
Sent from my AD683G using xda app-developers app