[GUIDE] Getting some old features back in Virtuous Sense ROMS - G2 and Desire Z Android Development

GUIDE: Getting some old features back
INTRO: For those who dislike some of the changes/features made to roms as they are developed and are asking how to get them back, here is a how to. It is usually a simple matter of pushing the old files from previous builds into your current rom. Keep in mind that the devs are building a rom as they see fit. As with any rom that you don't build yourself, there will always be things you want to change.
-If there is a bug, post it in the thread.
-If there is a change that you personally want, then do it yourself. Don't expect the dev, and everyone else who uses the rom, to accommodate your specific needs/wants. You may not have noticed, but you aren't the only one using the rom!
NOTE: This guide and code are meant for the virtuous sense rom, but the concept is universal. For example, if you are using some rom and the new version is posted with, say the amazon mp3 apk removed, and you want it back, refrain from cluttering up the dev's thread with a request to have it back. This is both selfish and a waste of posting space. If you are to the point of installing custom roms, you should first be able to type basic adb/terminal emulator commands to copy/delete files. In this case you would extract the amazon mp3 apk from an old .zip and push/install it into your current one. Now wasn't that easier than waiting and hoping that someone will do it for you?
NOW TO THE GUIDE:
Auto brightness mod - To revert from the auto brightness 'mod', which is far too sensitive, to the original, simply pull the services.jar and framework-res.apk from a rom before the patch, and push them to your framework folder. I've attached them to the second post for ease.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/framework/services.jar
adb shell rm /system/framework/framework-res.apk
adb push [directory of saved file]\services.jar /system/framework
adb push [directory of saved file]\framework-res.apk /system/framework
Reboot
-------------------
Keyboard mapping - The www/com key has been changed to a tab, which is good, as it was non-functional before. However the user keys have been changed too. I've modified a file which keeps the www/com key as TAB but also keeps the user keys as user assignable keys. Also attached to second post.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/usr/keylayout/vision-keypad.kl
adb push [directory of saved file]\vision-keypad.kl /system/usr/keylayout
Reboot
-------------------
Rosie auto-rotate - If you want to keep it so that rosie will only be in portrait mode with the keyboard closed, but dont want to turn off auto-rotate throughout all apps, just push the old rosie. Also attached to second post.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/app/com.htc.launcher.apk
adb push [directory of saved file]\com.htc.launcher.apk /system/app
Reboot

Attachments:
You need to rename "services.jar.zip" back to "services.jar" and "vision-keypad.kl.zip" back to "vision-keypad.kl". This is because the forum wont let you upload .kl and .jar extensions as attachments.

Thanks so much for this. I'll definitely be pushing the auto-brightness mod back, and I may do the keyboard, too (might let others do that one first, or see if rmk40/eViL release an update with that first).

Thanks for this!
Sent from my HTC Vision using Tapatalk

Couldn't make the quick key to work.. maybe I might be doing it wrong but I couldn't make it work.. ill keep trying
sent from t-mobile g2 using HTC sense

android602 said:
Couldn't make the quick key to work.. maybe I might be doing it wrong but I couldn't make it work.. ill keep trying
sent from t-mobile g2 using HTC sense
Click to expand...
Click to collapse
What version of virtuous are you running? Did you rename it and remove the .zip from the end?
I'm using that exact file w/ no issues

calendar/lockscreen
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this

felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
Lockscreen - no.
Calendar - maybe, haven't tried. However I did find these 2 threads by typing in the words "htc calendar" in the search box (which means you didn't search very hard )
http://forum.xda-developers.com/showthread.php?t=795222
http://forum.xda-developers.com/showthread.php?t=723761]
They may help you.

Good idea with this thread. It's impossible for us to please everyone and this is absolutely the most constructive way to deal with everyone's personal preferences. There is one key consideration for everyone. If we make other changes to the frameworks which you DO want, pushing files from this thread which have not been updated with said features will eliminate those changes as well. Point is, the concept here is good but it needs to be maintained.
Also, the intention with Virtuous is to provide options. The ROM isn't finalized so ROM Manager isn't populated with all the variants it will eventually have. Case in point, we had to re-base on the new Egypt RUU and are in the process of re-applying all our changes. If we had a variety of options, we would have to redo all of those as well. Once we're in a more "final" state, you'll start to see a lot more choices officially supported with the ROM.
The keyboard mod you have here will probably just become part of Virtuous 0.8.0, by the way. I had not realized our replacement eliminated the quick key customizations (oversight).

Chances are I'm not doing it right, as I'm only about 2% oriented in using ADB, but after following the code, pushing the files, etc, the phone boots up with perpetual errors and crashes. (Phone cannot be launched, etc.)
The process in which I did it was:
Wipe the G2, install v0.7.0, update to 0.7.4, remain in recovery and use adb and followed the code you provided above. (Everything says it works, in terms of mounting, pushing, etc.)
I've also tried it where I reboot after updating, let the phone launch fully, then go back to recovery to push the mod files. Same errors occur.
The only two mods I was interested in were the auto-brightness one and the orientation one.
Any idea what I did wrong?

felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
You could possibly try pushing the lockscreen apk from SuperVillainZ.
NANDROID 1ST THOUGH!!!!!
Sent from my HTC Vision using XDA App

fox-orian said:
Chances are I'm not doing it right, as I'm only about 2% oriented in using ADB, but after following the code, pushing the files, etc, the phone boots up with perpetual errors and crashes. (Phone cannot be launched, etc.)
The process in which I did it was:
Wipe the G2, install v0.7.0, update to 0.7.4, remain in recovery and use adb and followed the code you provided above. (Everything says it works, in terms of mounting, pushing, etc.)
I've also tried it where I reboot after updating, let the phone launch fully, then go back to recovery to push the mod files. Same errors occur.
The only two mods I was interested in were the auto-brightness one and the orientation one.
Any idea what I did wrong?
Click to expand...
Click to collapse
Well from what you are saying, it sounds like the methods are correct. Did you make sure to remove the ".zip" from the end of the services.jar.zip file?

Can this be modified to restore ".com/www" to G2's?

the1wingedangel said:
Well from what you are saying, it sounds like the methods are correct. Did you make sure to remove the ".zip" from the end of the services.jar.zip file?
Click to expand...
Click to collapse
Yup, and I have "always show extension" enabled in folder options, so I definitely got rid of the .zip.
Maybe I'll fiddle with it a little more, see if I missed something.

All right, here's the error I get after removing the files for the brightness mod, and pushing the ones you attached in:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly."
Basically the launcher is completely inaccessible, the phone remains perpetually in the settings screen because I suppose it's the only thing that it can load without the launcher. It also can't get a signal except for wi-fi, "Mobile Networks" in the settings remains unchecked, and it can't be turned on. Hahaha pretty severe for a rather simple mod.
Here's a full step-by-step of exactly what I did:
Wipe User Data, Wipe Cache
Install virtuous v0.7.0, then v0.7.4 from zip
Remain in Recovery
Open command prompt Change directory to ADB (c:\AndroidSDK\tools)
Entered the following codes one at a time:
- adb shell mount /system (mounts)
- adb shell rm /system/framework/services.jar (file removed)
- adb shell rm /system/framework/framework-res.apk (file removed)
- adb push C:\services.jar /system/framework (success 0.250s)
- adb push C:\framework-res.apk /system/framework (success 1.80s)
(I just have the files on C temporarily for the ease of it.)
Reboot
Then the errors hit once I unlock the screen.
Heheh, I can't really think of any other way to approach it. Hmmmm.

Any idea what I'd need to put back for video codecs? I'm running CM 6.1 but it doesn't run streaming videos from the NHL Gamecenter unlike the stock rom. I'm assuming its a codec issue and was wondering what I'd want to replace.

fox-orian said:
All right, here's the error I get after removing the files for the brightness mod, and pushing the ones you attached in:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly."
Basically the launcher is completely inaccessible, the phone remains perpetually in the settings screen because I suppose it's the only thing that it can load without the launcher. It also can't get a signal except for wi-fi, "Mobile Networks" in the settings remains unchecked, and it can't be turned on. Hahaha pretty severe for a rather simple mod.
Here's a full step-by-step of exactly what I did:
Wipe User Data, Wipe Cache
Install virtuous v0.7.0, then v0.7.4 from zip
Remain in Recovery
Open command prompt Change directory to ADB (c:\AndroidSDK\tools)
Entered the following codes one at a time:
- adb shell mount /system (mounts)
- adb shell rm /system/framework/services.jar (file removed)
- adb shell rm /system/framework/framework-res.apk (file removed)
- adb push C:\services.jar /system/framework (success 0.250s)
- adb push C:\framework-res.apk /system/framework (success 1.80s)
(I just have the files on C temporarily for the ease of it.)
Reboot
Then the errors hit once I unlock the screen.
Heheh, I can't really think of any other way to approach it. Hmmmm.
Click to expand...
Click to collapse
Weird, I have no idea why that won't work for you. Anyway, there is another way around it. Just open up your patch.zip (from 0.7.0 to 0.7.4), go to the framework folder, and remove the services.jar and framework-res.apk from it. Then go about the wipe/install of both zips like normal. That way the patch zip will no longer replace those two files. Anything that you don't want changed in a patch zip can just removed from it.
Snap Jackel Pop said:
Any idea what I'd need to put back for video codecs? I'm running CM 6.1 but it doesn't run streaming videos from the NHL Gamecenter unlike the stock rom. I'm assuming its a codec issue and was wondering what I'd want to replace.
Click to expand...
Click to collapse
Sorry cant help on that one, I haven't run a CM rom since like 1 or 2.0 haha. You may try to see if others are having that problem, or if it is a known issue with the 6.1 and streaming videos. Is it only that site? Maybe a flash player version problem?
rmk40 said:
Good idea with this thread. It's impossible for us to please everyone and this is absolutely the most constructive way to deal with everyone's personal preferences. There is one key consideration for everyone. If we make other changes to the frameworks which you DO want, pushing files from this thread which have not been updated with said features will eliminate those changes as well. Point is, the concept here is good but it needs to be maintained.
Also, the intention with Virtuous is to provide options. The ROM isn't finalized so ROM Manager isn't populated with all the variants it will eventually have. Case in point, we had to re-base on the new Egypt RUU and are in the process of re-applying all our changes. If we had a variety of options, we would have to redo all of those as well. Once we're in a more "final" state, you'll start to see a lot more choices officially supported with the ROM.
The keyboard mod you have here will probably just become part of Virtuous 0.8.0, by the way. I had not realized our replacement eliminated the quick key customizations (oversight).
Click to expand...
Click to collapse
Yea, I assumed it would be out-dated soon anyway, as changes are made to your roms. I'll adjust it to keep up if the need is there though. It was just a couple of the more simple alterations that I made, and after seeing so many people cluttering up your thread with posts about them, I decided to post this.
Mostly, though, I just wanted to remind people that many simple issues/personal needs (like an app being removed from a rom, or a small change to one or two apps) can be solved with a little bit of thought and some adb knowledge - both of which should be present if you are working with a rooted phone in the first place!

the1wingedangel said:
many simple issues/personal needs can be solved with a little bit of thought and some adb knowledge - both of which should be present if you are working with a rooted phone in the first place!
Click to expand...
Click to collapse
I really cant emphasise this enough!
Sent from my sweet G2

Do you know if there is anyone to return the power down message. I remember before there being and option to restart the phone, hibernate, power off, or reboot into recovery. I liked having that. Is there anyway to return this feature?
Sent from my sweet G2

felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
ddotpatel said:
You could possibly try pushing the lockscreen apk from SuperVillainZ.
NANDROID 1ST THOUGH!!!!!
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
by chance, did anyone try this? if not, I will try it in a few...

Related

New Clock Widget Switcher 50+ clocks and no ADB required.

Updated: Sept 8 2009 Now over 50 clocks some in 2 sizes. Have fun with the new clocks and the new Candy.
--Linuxrebel--
I'm one of those who loves Eye Candy, but hates windows. So despite some excellent work done by xidominicanoix I couldn't use the work. So with xidominicanoix's permission to use the collection I've written a shell script that can run on your SD card and installs the new clocks in quick order.
NOTE: This is for rooted phones only. I've tested it pretty heavily on my G1 but your mileage is not guaranteed. If you are not comfortable in a Linux/Unix shell you might be best off with the tool here.
I claim only that it worked on my phone, (and that it looks cool to me )
Directions for use (Copy of the directions are also in the README file):
+++++++++++++++++++++++++++++++++++++++++
This is a quick and easy way to change the clocks on your phone without the hassle of using windows adb, etc.
Unfortunately for those who aren't rooted, this will not work. Root is required to be able to use
this script and change the clock. There are lots of tutorials on how to root phones, so go forth and google to find your answers.
Usage:
+++++++++++++++++++++++++++++++++++++++++
1. Connect your phone to your main computer and copy the file clocks.tgz to your sdcard
2. Disconnect the phone, as the rest will not need your computer to complete.
3. Open a term window (I like connectbot your preference may vary)
4. su
5. cd /sdcard
6. tar -vzxf clocks.tgz (this will open the tar gzip file)
7. cd Clocks
8. sh setclock.sh backup (This will backup your existing clock)
9. sh setclock.sh [name of the clock you want to use]
You can remove the clocks.tgz file anytime you want once it is opened it's no longer used. If you run backup a second time it restores the originally backed up clock.
NOTES:
Images of the various clocks are in the the directory called Images. The Image viewer on the G1 picks them up (may need to force it to re-read) and I'd imagine that the other phones work the same, so you can see what it is you are going to get that way. The Directory name will match the name of the picture to make life better. To add a clock to this script all you need to do is make a directory under Clocks, with the AlarmClock.apk file in it, and then run the script to have it 'installed' the same as all the others.
Again thanks to xidominicanoix for gathering together permission to use all of these clocks, and giving me the idea to do it this way. (Since I couldn't use his bloody windows tools )
--Linuxrebel--
You can download the tarball at the following link:
http://www.4shared.com/file/131059734/7781f9a1/clocks.html
md5sum 7c1253ba43d6b21194b56c489b9fb7e6 clocks.tgz
Seems I forgot about the Windows side of the world. All I have at home are *nix systems (Linux, Mac and BSD), so if you are not on a *nix or Cygwin enabled system a zip file
http://www.4shared.com/file/132469430/9f73a1ba/clocks.html
md5sum f5cdb6cd3c4ad983ab30123b1acce3f7 clocks.zip
good work man ... now Mac and Linux users can all enjoy
xidominicanoix said:
good work man ... now Mac and Linux users can all enjoy
Click to expand...
Click to collapse
And noobs who can't get it work like me
Thank you both for your hard work on this.
Adam17 said:
And noobs who can't get it work like me
Thank you both for your hard work on this.
Click to expand...
Click to collapse
Are you having hard time with xidominicanoix's version or mine? If mine let me know what the problem is. If xidominicanoix's I'm going to be as in the dark as anyone could be.
Yeah I am having problems with his, just can't seem to get it working for me.
Edit: So we have to go back into term everytime we want to change it? Or am I missing the easier way to do it?
Adam17 said:
Yeah I am having problems with his, just can't seem to get it working for me.
Edit: So we have to go back into term everytime we want to change it? Or am I missing the easier way to do it?
Click to expand...
Click to collapse
Good bad or ugly, yes you do need to go back to term. UNLESS a miracle happens and I instantly figure out how to to Android style programming I'm an admin not a programmer.
Np, I can deal with term a helluva a lot easier than I can with adb.
works great..takes a few seconds after initial set up to bang into terminal the commands to change the clock. I have had issues with ADB where I seem to lose adb connection for unknown reasons and phone doesnt connect so this method for me is alot easier.
thanks!
works great .. .thanks ... it shows up on my home screen but does not show up in my open home home screen :/ is there a way I could make it work in open home?
wow so easy and straight from the phone
thanks for this!!
hello .... it's not working for me..
when i get to step:
8. sh setclock.sh backup (This will backup your existing clock)
my g1 says cp: cannot stat '//system/app/AlarmClock.apk': No such file or directory
hmmmmmmmmmmm
what to do
i HAve Cm 4.0.2
and the oreo red n blk theme
bboy_201 said:
hello .... it's not working for me..
when i get to step:
8. sh setclock.sh backup (This will backup your existing clock)
my g1 says cp: cannot stat '//system/app/AlarmClock.apk': No such file or directory
hmmmmmmmmmmm
what to do
i HAve Cm 4.0.2
and the oreo red n blk theme
Click to expand...
Click to collapse
Looking into it.
EDIT: I did the only thing I can imagine is that a theme you are using has moved the AlarmClock.apk package and I've no idea where.
I'm stumped
linuxrebel said:
Looking into it.
Click to expand...
Click to collapse
The normal location of the clock is /system/app (or //system/app, same place extra /)
Is it perhaps possible that the theme you are using moves the AlarmClock.apk? If you can give me a link to the theme (I'm more than a little tired at the moment and having really lousy luck with search.) I'll see if I can figure out what the author of that did, or if it is even the problem.
Worked perfect I love it thank you very much!
i iused the other verion of doing this from the link provided in the top of the 1st post......
http://forum.xda-developers.com/showthread.php?t=538189&page=12
that worked for me!!!!!!!!!!!!
edit:
found it out myself
And what about even more easiest switching. Try this one http://www.mediafire.com/?whgtmmt5uui. Unpack copy folder to sd card then run just once clock_install.sh via GScript Lite app. For switch clock open terminal and write clock.
I'm running on CM 4.0.4 and when I input the setclock.sh clock name it works and everything works perfect except that I never can get the clock widget its always the same watch as before any help?
AndroidFiend said:
I'm running on CM 4.0.4 and when I input the setclock.sh clock name it works and everything works perfect except that I never can get the clock widget its always the same watch as before any help?
Click to expand...
Click to collapse
I am running CM 4.04 too on my MT3G and everything works. I now have TedLight clock on my phone. The only problem I have is that I wanted Clock5, but my keyboard or emulator refuse to use digits. What am I doing wrong? Is there a way to type digits or it is just my phone is not cooperating?
Thanks.
Would anybody mind posting some highlights?

*OUTDATED* ROM porting for kaiser/vogue [Linux] NOOB friendly!

THIS IS NOW OUTDATED!!
It uses the old sqsh method WITH a rootfs. So if you're using the NoMoRootfs method, this won't work. Please use the already complete builds in the Kaiser/Vogue threads as they are working the best at this moment.
DISCLAIMER:
I take no responsibility for anything that may happen to your phone/computer. Use at your own risk.
PURPOSE:
This is for informational/testing purposes. And for people to stop asking, "can somebody port X rom!!! PLZ!!!"
PREFACE:
I made this as a quick tool to port ROMs from the Dream/Sapphire forums to work with our phones. It's a very quick and dirty script I threw together using bash, so there's probably some problems with it. This tool is simply designed to make a copy of the Dream/Sapphire ROM. Once you get the setup, it's really easy and you'll be porting like crazy.
I did this all on Ubuntu 9.10 so things might not work properly if you're using another distro.
THANKS:
All credit goes to the people that made this possible, in no particular order...
dzo, vilord, mssmison, zen, enatefox, pmos, jamezelle, craig0r, cyanogen, and so many more. If I forgot you, I'm sorry, but you know if you helped in some way.
THE SETUP:
1) Download this file
2) Extract the folder to your desktop. Then copy and paste the following code into the terminal:
Code:
sudo mv -f $HOME/Desktop/Android/genext2fs /bin/genext2fs; sudo chmod 755 /bin/genext2fs; sudo dpkg -P squashfs-tools; sudo dpkg -i $HOME/Desktop/Android/squashfs-tools_3.3-7_i386.deb; sudo rm -r $HOME/Desktop/Android/squashfs-tools_3.3-7_i386.deb; sudo chmod 777 $HOME/Desktop/Android/*.build.script
3) Now go into synaptic package manager, search for squashfs-tools, select it and under Package, check Lock Version so that way it won't try to update.
4) Now cruise over to the Dream android development forum or the Sapphire android development forum and download the ROM you would like to port. Place the zip file in the Android folder. (no need to rename)
5) Place any .apk's you would like built into the system in the Apps folder.
ADVANCED SETUP:
If you would like to tweak the system before building, open the script in a text editor and you'll find a line to uncomment that will halt the script until you are ready.
HOW TO RUN:
Either run the script from a terminal
Code:
./$HOME/Desktop/Android/HERO.build.script
or
./$HOME/Desktop/Android/Donut.Build.script
Or double click and Run in Terminal
You will get a prompt for your password to use the sudo command. THIS IS NOT SAVED ANYWHERE OR MAGICALLY SENT TO ME. It is just to get the system.sqsh setup for you to use.
You will now see a Donut/Hero folder inside the Android folder. Inside that will be a nice little system.sqsh with the date ready to boot!
*Rename to system.sqsh when you put on your SD card*
Grab the latest basefiles from vogue-android and you're good to go.
~~~~~~ To get an output of what's happening run in a terminal as described above but add " > build.txt" and you'll see a txt file in the Android folder. ~~~~~~~
CHANGING SYSTEMS:
If you want to port a new rom, replace the .zip.
UPDATES:
1) Download the updates from HERE
2) Extract to the Android folder overwriting if necessary.
3) Copy and paste the following code into a terminal:
Code:
sudo chmod 777 $HOME/Desktop/Android/*.script
CLEANUP:
If you follow the advanced setup and/or accidentally closed the terminal before the build finishes, run the cleanup script. This will unmount everything that might be mounted and delete all folders that are made during the process.
DOWNLOADS:
If you're too lazy or just want a quick link:
Main "Android porting" folder
Updates
Input, testers, bugs, and tweaks to the scripts are appreciated!
FAQ:
Why does my system.sqsh not work?
Most likely cause is that you're not using the correct version of squashfs-tools. You'll have to find version 3.X for the distro you're using. Version 4.X will NOT work!!!
When I try to boot a system.sqsh I just made I keep getting something about android power wake locks. WTF?
You're probably trying to port an eclair or cyan ROM. These don't work at the current state. Hopefully soon I'll get these working.
Will update more when they arise.
CHANGELOG:
11-27-09:
-Created a cleanup script in case the terminal is closed during the build process.
-Bug fixes in Donut and Hero scripts
11-24-09:
-Added an Apps folder for apk's you want built into the system.
-Bug fixes in scripts
11-22-09:
-Combined everything needed into a zip file
-WAY easier to setup
11-20-09:
-Added feedback to make more user friendly
-Append time to system.sqsh
loserskater said:
Input, testers, bugs, and tweaks to the scripts are appreciated!
Click to expand...
Click to collapse
Will try today... Downloading
Tried and working. Had to change the script for it work with ubuntu version that i use. Thanks this is really great
garynsa said:
Will try today... Downloading
Tried and working. Had to change the script for it work with ubuntu version that i use. Thanks this is really great
Click to expand...
Click to collapse
What did you change?
Glad to see it's working.
loserskater said:
What did you change?
Glad to see it's working.
Click to expand...
Click to collapse
hI
For some reason I cannot use -a in the genext2fs command. Had to remove that..
One of the Donut is working. Couldnt get the Cyanogen build working . Struggling with hero build also.
Will try again in the next couple of days and post results.
Thanks
garynsa said:
hI
For some reason I cannot use -a in the genext2fs command. Had to remove that..
One of the Donut is working. Couldnt get the Cyanogen build working . Struggling with hero build also.
Will try again in the next couple of days and post results.
Thanks
Click to expand...
Click to collapse
Make sure you use the genext2fs that I referenced.
That one works with -a and might take care of some issues. try that and see if it works.
Updated script to now move system to a Hero or Donut folder.
Working on the cyanogen build now...
EDIT: Here's a cyanogen script that gets it to boot, but sits at a black screen. I haven't had much time to test it so it might boot further than that if you leave it. If somebody wants to test this out or tweak it in some way go for it.
It uses the donut.sqsh in the Android folder so you shouldn't have to do anything with it except make it executable.
EDIT 2: Still working on cyan builds... that script didn't work.
great job i like to see stuff like this to motivate people!!! also note this will work with any donut or hero build from the sapphire forum
jamezelle said:
great job i like to see stuff like this to motivate people!!! also note this will work with any donut or hero build from the sapphire forum
Click to expand...
Click to collapse
Good point, forgot to mention that. Updated first post.
I'm hoping it will help people start to learn to tweak system's. But I have a slight feeling wer're going to start seeing a lot of "MLIGN/DWANG/etc's Android Rom" threads from random people.
Hi
Was able to port the DWANGs build using your script. Thanks a lot for making life this simple. Howev3er, hero build is still not working. Tried your genesxt2fs. Is it possible to get the links to correct base hero version to use? I tried magic and normal version. It keeps giving me black screen and doesnt completely boot. I think the base hero version is not the right one i am using
Thanks
OK, I think I figured out the problem. The apps folders weren't copying over from the data folder to the system folder correctly. Testing now, and will update first post with new scripts.
EDIT: Finally got the Hero builds working correctly. You should still be able to use any hero.sqsh.
loserskater said:
OK, I think I figured out the problem. The apps folders weren't copying over from the data folder to the system folder correctly. Testing now, and will update first post with new scripts.
EDIT: Finally got the Hero builds working correctly. You should still be able to use any hero.sqsh.
Click to expand...
Click to collapse
Hi
The new script is great.. I was able to get the hero to boot I still have 2 check a few thing willl post later in the night with more
Thanks a lot
garynsa said:
Hi
The new script is great.. I was able to get the hero to boot I still have 2 check a few thing willl post later in the night with more
Thanks a lot
Click to expand...
Click to collapse
Glad to see its working. Thanks for the feedback!
Most things working
Hi
was able to get the hero ported and a few things worked
1. Calls
2. SMS
3. Wifi (getting ips)
4. Working with partition rootfs (speed quite great with this)
Not working
1. Camera
2. GPS
I am using he ION build to build the hero roms (based on the inputs of Zen). May be I need to use another hero rom for the camera to work? I recommend that the links to the recommended build to be used as template (donut, hero...) be updated on the first thread to make it easy for others to have a single starting platform
garynsa said:
Hi
was able to get the hero ported and a few things worked
1. Calls
2. SMS
3. Wifi (getting ips)
4. Working with partition rootfs (speed quite great with this)
using u
Not working
1. Camera
2. GPS
I am using he ION build to build the hero roms (based on the inputs of Zen). May be I need to use another hero rom for the camera to work? I recommend that the links to the recommended build to be used as template (donut, hero...) be updated on the first thread to make it easy for others to have a single starting platform
Click to expand...
Click to collapse
If using a hero.sqsh doesnt fix the problem it sounds like it might be the rootfs (probably not copying over correctly). Ill take a look at it when I get home and update the first post with hero/donut.sqsh's.
Im also thinking about combing the 2 into just one script and youll be able to just type which build you want when you run it. What do you think? Or is the 2 seperate scripts more convenient?
loserskater said:
If using a hero.sqsh doesnt fix the problem it sounds like it might be the rootfs (probably not copying over correctly). Ill take a look at it when I get home and update the first post with hero/donut.sqsh's.
Im also thinking about combing the 2 into just one script and youll be able to just type which build you want when you run it. What do you think? Or is the 2 seperate scripts more convenient?
Click to expand...
Click to collapse
Personally i prefer the separate scripts mainly because each requires a different base templates. However if you prefer to combine them may be have sub-folders within the main so that the work happen for each port within the sub-folder.
Few suggestions if you like (please ignore if not correct.. being a non-programmer of linux I can be a bit off )
1. Let the folder names be requested at start and use them
2. If possible to put in a log of the run to check if there were issue or not (because i use double-click to run the script sometimes there is a problem that i face if i dont watch the window. for now i have put some waits to check the errors. Had this issue while testing to port one)
If I can help (except on coding as I dont know it.. generally change the script just enough to work... )
Queries/questions
1. Is there a way to test the build on the comp itslef rather than to keep booting on the phone (takes a lot of time and the phone is not usable all that time...)
Thanks for all the work
garynsa said:
Personally i prefer the separate scripts mainly because each requires a different base templates. However if you prefer to combine them may be have sub-folders within the main so that the work happen for each port within the sub-folder.
Few suggestions if you like (please ignore if not correct.. being a non-programmer of linux I can be a bit off )
1. Let the folder names be requested at start and use them
2. If possible to put in a log of the run to check if there were issue or not (because i use double-click to run the script sometimes there is a problem that i face if i dont watch the window. for now i have put some waits to check the errors. Had this issue while testing to port one)
If I can help (except on coding as I dont know it.. generally change the script just enough to work... )
Queries/questions
1. Is there a way to test the build on the comp itslef rather than to keep booting on the phone (takes a lot of time and the phone is not usable all that time...)
Thanks for all the work
Click to expand...
Click to collapse
I'll try to make the script more user friendly with prompts if something doesn't happen correctly. And also work on naming folders.
But first I want to figure out the camera/gps issues...
There isn't a way to boot it on the comp that I know of. I'll upload blank data.img's for each build so that they'll boot faster but other than that I think moving to SD Card and booting is the only way. But once all these bugs get sorted out, you won't have to do it as often!
EDIT: Which folders would you like to name? Just where the system.sqsh gets stored?
loserskater said:
I'll try to make the script more user friendly with prompts if something doesn't happen correctly. And also work on naming folders.
But first I want to figure out the camera/gps issues...
There isn't a way to boot it on the comp that I know of. I'll upload blank data.img's for each build so that they'll boot faster but other than that I think moving to SD Card and booting is the only way. But once all these bugs get sorted out, you won't have to do it as often!
EDIT: Which folders would you like to name? Just where the system.sqsh gets stored?
Click to expand...
Click to collapse
Hi
Thanks for the answers. For me it should be both (but the starting folder is main. Other can be a sub-folder like u have now to be renamed as choice)
garynsa said:
Hi
Thanks for the answers. For me it should be both (but the starting folder is main. Other can be a sub-folder like u have now to be renamed as choice)
Click to expand...
Click to collapse
Are you referring to the Android folder? Or just a folder where everything is kept when it runs?
loserskater said:
Are you referring to the Android folder? Or just a folder where everything is kept when it runs?
Click to expand...
Click to collapse
Android folder... but its not a big deal as one can easily change it while startign the script

[23/Jan/2012][NST][1.1] Current book cover screensaver + custom shutdown image

UPDATE 23/01/2012:
Added support for content on sd-card (BETA). Further details on this post.
UPDATE 03/01/2012:
WARNING: some users reported troubles starting custom launcher and application after installation of this mod; a full backup before installation of this mod is strongly suggested!
UPDATE 27/12/2011:
Added custom shutdwown image mod.
UPDATE 18/12/2011:
Complete refactoring of Hack; now it's based on firmware 1.1.
Older firmware (1.0 and 1.0.1 no more supported).
Hi all,
i made a modification on Nook Simple Touch to use, as screensaver, the cover of the current reading book (i.e. the last book opened in the stock reader application).
Of course, it's necessary that the book has a cover (i.e. the cover is shown in the library application); on contrary, the default screensaver will be displayed (i.e. "authors").
Usage:
to activate the "current reading book cover screensaver: go to settings / screen / screensaver and select the new option, called "Current reading book image";
to set the custom shutdown image: copy an image called "shutdown.png" inside folder "screensavers" of Nook internal drive, when the Nook is connected with USB; the image "shutdownLowBattery.png" is displayed in case the Nook turns off due to low battery.
If the images are not found, the default ones are used.
Thanks to:
XorZone for it's really useful modification "Edit n/reading now/side btns/RecentApps+ActivityPicker+ForceOrient";
WARNING: as usual, modifying system files you may risk to brick your Nook, unless you know what you are doing. You are strongly advised to make a full backup before proceeding. I don't take any responsibility if you decide to apply this mod.
WARNING-2: this modification could only be appied on firmware 1.1 .
Installation:
download and unpack one of the attached files:
screensaver-hack-110-xor.zip in case you are using XorZone mod to improve button mappings etc..;
screensaver-hack-110.zip otherwise (i.e.: you are just using plain firmware from B&N);
verify that the archive you downloaded contains these 4 files:
android.policy.jar [needed only for "current book cover screensaver"];
services.jar [needed only for "current book cover screensaver"];
Settings.apk [needed only for "current book cover screensaver"];
framework.jar [needed only for "custom shutdown image"];
please consider that if you want to apply just one of the 2 modification included, you may limit the execution of next steps just to the relevant files as listed above;
(optional) make backup of original files, in case of problems with the modded ones (in case you revert to original files, remember to set the permissions of the original files, and delete the dalvik-cache)
remount system partition r/w
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
copy the downloaded files to Nook
Code:
adb push android.policy.jar /system/framework
adb push services.jar /system/framework
adb push framework.jar /system/framework
adb push Settings.apk /system/app
change the permission
Code:
adb shell chmod 644 /system/framework/android.policy.jar
adb shell chmod 644 /system/framework/services.jar
adb shell chmod 644 /system/framework/framework.jar
adb shell chmod 644 /system/app/Settings.apk
delete dalvik-cache
Code:
adb shell rm /data/dalvik-cache/[email protected]@[email protected]
adb shell rm /data/dalvik-cache/[email protected]@[email protected]
adb shell rm /data/dalvik-cache/[email protected]@[email protected]
adb shell rm /data/dalvik-cache/[email protected]@[email protected]
delete packages.xml [needed only for "current book cover screensaver"] (it will be regenerated at next boot; optionally make a backup also of this file, in case of troubles)
Code:
adb shell rm /data/system/packages.xml
(optional) due to packages.xml regeneration, it's possible (in my case it occurred) that now when you turn on the NST, the demo mode starts automatically; in any case, it's turned off as soon as you click any button, so it doesn't make any harm; but, if you want, you can simply delete the apk to get rid of it:
Code:
adb shell rm /system/app/DemoMode.apk
reboot your Nook
Code:
adb reboot
Thanks to user persichini, it's also available an alternative installation guide using RootExplorer directly from Nook (i.e. no need of ADB commands): in any case, please take into account that the same considerations about the relevance of modified files (in case you only want to install either "current book cover screensaver" or "custom shutdown image").
In case of issue, please provide the logcat log. You can redirect the log to a file (logcat.log) with the ADB command (launch it when Nook is booting to have all useful info):
Code:
adb logcat > logcat.log
Hit Ctrl+C to stop logging.
Hope you will enjoy it!
PS: as soon as i will have time, i will post sources, so you can build the mod by yourself (meanwhile, if you need them, just decompile and compare to original files of firmware 1.1 )
PS2: attached to this message you can also find 2 nice possible shutdown / lowBattery images.
I know you said that it's not compatible with v1.0.1, but is there a reason why you don't have v1.0.1 firmware on your nook? It's been out since July/August and works just as (un)well with the rooting scripts out there.
nickveldrin said:
I know you said that it's not compatible with v1.0.1, but is there a reason why you don't have v1.0.1 firmware on your nook? It's been out since July/August and works just as (un)well with the rooting scripts out there.
Click to expand...
Click to collapse
mostly, just because i'm lazy! and on changelog it's just mentioned that 1.0.1 hav some improvement on wifi, that i don't use at all.
In any case, this doesn't matter for my mod, since i downloaded the manual upgrade file from B&N, so that it would be easy to apply the mod to 1.0.1. I just need to find some time. I hope i will do it during the week-end.
Regards
traycold said:
mostly, just because i'm lazy! and on changelog it's just mentioned that 1.0.1 hav some improvement on wifi, that i don't use at all.
In any case, this doesn't matter for my mod, since i downloaded the manual upgrade file from B&N, so that it would be easy to apply the mod to 1.0.1. I just need to find some time. I hope i will do it during the week-end.
Regards
Click to expand...
Click to collapse
Okay thank you! I will look forward to the 1.0.1 release.
Another option is to use Cool Reader 3. It has Nook Simple Touch features (e.g.: type of refresh - full, fast; you can map the physical buttons) and, starting with cr3.0.51-20, it automatically creates one folder (currentbook) in screensavers and saves the current book's cover in that directory (deleting all others when the current book is changing). You can then choose that directory in the standard screensaver option of your Nook.
Not to mention other nice touches not present in the standard reader (showing the clock and the battery percentage or bars while reading a book, very customizable).
Yeah, problem encountered when I try reading or going into settings.. here's the log:
http://pastebin.com/fGGJVnGQ
I'm using 1.0.0
EDIT: Restored the backuped files, reader's back online, settings still not working :[
This particular error appears when I'm trying to launch the settings panel:
Code:
No Activity found to handle Intent { act=android.settings.SETTINGS flg=0x14400000 }
Touching the wifi icon doesn't open up any popup, it just fast reboots the nook
koltzu said:
Yeah, problem encountered when I try reading or going into settings.. here's the log:
http://pastebin.com/fGGJVnGQ
I'm using 1.0.0
EDIT: Restored the backuped files, reader's back online, settings still not working :[
Touching the wifi icon doesn't open up any popup, it just fast reboots the nook
Click to expand...
Click to collapse
hi,
sorry for your issue.
Actually, i also had some issue just opening the wifi-tab of the settings. I didn't found it before simply because i don't use wifi at all, so normally i don't have any reason to open it!
To solve this issue, you just need to update the file settings.apk, following the instruction on post 1. I updated the file "Settings.apk" in the firtst post.
In your case, if you reverted to original file, then there is no trace left of my modification, so i really don't understand what may occur. It could be useful to get a complete logcat trace since boot. To do so, launch the logcat command, as soon as the Nook is booting (tipically, as soon as the Nook drive appears on Windows): this way, you don't miss the first log lines that could help understanding your issue.
Additional advices: check that, after reverting to original files, you set the right permissions; wipe dalvik-cache:
Code:
adb shell rm /data/dalvik-cache/*.*
Thanks for the answer, I did as you told and the settings started working [by using your apk] but the reader died again. Replaced it again by using my files and the reader started working while the settings menu stopped working.
I seem to be unable to do a logcat while booting [can't connect through cable for some reason].
I blame all of these problems on my own previous tinkering with my nook.
Luckily I have a backup that I've done before rooting the nook. I'll just restore it and try again on a 'clean' and newly rooted Android system as soon as I get my hand on a microSD card.
If I bang into any more problems after restoring, I'll let you know
Any update on this? Possibly getting it to work on the (yes just released) v1.1 update?
I'm interested to see if this has been worked on anymore? Is there any plans for bring this to V1.1? I would love to use this on my nook.
persichini said:
I'm interested to see if this has been worked on anymore? Is there any plans for bring this to V1.1? I would love to use this on my nook.
Click to expand...
Click to collapse
hi, i will try and find the time to make the updates for firmware 1.1 as soon as possible (possible, this week-end).
Regards
traycold said:
hi, i will try and find the time to make the updates for firmware 1.1 as soon as possible (possible, this week-end).
Regards
Click to expand...
Click to collapse
Hey tray - thanks a lot!
But many of us here have already installed modified versions of android.policy.jar and services.jar...it's not possible to release a patcher, right? Can't ask for too much, and don't mean to be belittling your contributions...
And, btw, I'm seeing all these different patches here...does anybody have a primer on patching these jars? Or at least some intro? I'd google it but I'm not quite sure what to search for...
traycold said:
hi, i will try and find the time to make the updates for firmware 1.1 as soon as possible (possible, this week-end).
Regards
Click to expand...
Click to collapse
That would be awesome if you did bring it to 1.1. I under stand developers have lives outside of development thank you for your time.
traycold said:
hi, i will try and find the time to make the updates for firmware 1.1 as soon as possible (possible, this week-end).
Regards
Click to expand...
Click to collapse
Since you are going to patch Reader.apk, how hard would it be to modify it so that it can be launched from standard drawer as any other app?
It would be great to be able to add a big icon (e.g. with Desktop VisualizeR) to the home page that opens the book your currently reading...
traycold said:
hi, i will try and find the time to make the updates for firmware 1.1 as soon as possible (possible, this week-end).
Regards
Click to expand...
Click to collapse
Hey trey- instead of releasing a jar file, which many of us have modified, what about just giving us whatever you modify in the smalis, and then we go ahead and apply the patch ourselves?
You could also take the stock 1.0.0 files and make the patches yourself.
LOL, right, if I knew just what the heck I was looking for...
LastSilmaril said:
LOL, right, if I knew just what the heck I was looking for...
Click to expand...
Click to collapse
You don't need to know! Decompile the original files, decompile the files from this thread (apktool). Make a diff of the to decompiled folders (diff -crB folder_with_decompiled_stock_files folder_with_decompiled_files_from_this_thread > diff.patch ). Now you know what has been changed and you can try to use the patch with the 1.1 files.
mali100 said:
You don't need to know! Decompile the original files, decompile the files from this thread (apktool). Make a diff of the to decompiled folders (diff -crB folder_with_decompiled_stock_files folder_with_decompiled_files_from_this_thread > diff.patch ). Now you know what has been changed and you can try to use the patch with the 1.1 files.
Click to expand...
Click to collapse
Thanks...I've never had to really use diff for anything before so I never really thought about it. I'll try it out, but likely not today - I need a break from Nook testing/hackery already (see my dhcp thread...)
bump.........

[Q] Anyone know how to perm disable cap lights on lg nitro?

i have a few apps that can disable them but the changes are reset every reboot none of them can make changes stick. i've heard of a few file editing ways to make it stick but most of those say they only work for specific phones and haven't found one for lg nitro yet. my problem is i had to replace a digitizer and the new lights on the new one are too bright and offcentered so i just want the lights off because everything else is working and i dont need the lights anyways. Thanks for any help.
if you're using stock ICS rom, there is an option to disable it in settings and it stays on reboot.
for other roms, try this app, not sure if it works.
https://play.google.com/store/apps/details?id=com.deskangel.kblight&hl=en
ightsrti purpose
arda99 said:
if you're using stock ICS rom, there is an option to disable it in settings and it stays on reboot.
for other roms, try this app, not sure if it works.
https://play.google.com/store/apps/details?id=com.deskangel.kblight&hl=en
Click to expand...
Click to collapse
i have that app its one of the only ones that will turn the lights off, but it doens't stick on boot and after boot i have uncheck recheck the option every time, it is right not he only solution but its not convenient, looking for something more perm. i'm running CM10.0.0 with apex launcher.
by the way thanks for the fast response, it's ironic because i lost my stock rom because of a faulty flash of CWM recovery, my backup rom is the stock AT&T ROM, do you know if this rom has the option? it's gingerbread i think. I'm also wondering if flashing to that rom, disabling the lights, then flashing CM10 again would solve the problem. but i asume when flashing cm10 i would lose the solution and the lights would come back on after booting into cm10 the first time. Any more help on a perm solution would be appreciated. i know there are perm soltuions for other phones but i hvaen't found one that works with p930 yet, i've even seen some for optimus 2x and G but they won't work on LTE, even rootdim doesn't work i've already contacted the developer and told him i can help him with compatibily if he needs anything from my phone to help update rootdim for p930 incase other people are having this problem as well., the problem is mostly that LTE screen is incredibly good and bright, and i dont want to wreck the clarity with my aftermarket digitizers overlight bright cap button lights blaring into my eyes and ruining the beauty of the HD screen on this thing. I mean after all how many of us need lights to tell us where our back/home/menu buttons are... i mean i googled this problem and there are hundreds of people trying to disable them on almost any phone you can think of, with varying success.
KronicSkillz said:
i have that app its one of the only ones that will turn the lights off, but it doens't stick on boot and after boot i have uncheck recheck the option every time, it is right not he only solution but its not convenient, looking for something more perm. i'm running CM10.0.0 with apex launcher.
by the way thanks for the fast response, it's ironic because i lost my stock rom because of a faulty flash of CWM recovery, my backup rom is the stock AT&T ROM, do you know if this rom has the option? it's gingerbread i think. I'm also wondering if flashing to that rom, disabling the lights, then flashing CM10 again would solve the problem. but i asume when flashing cm10 i would lose the solution and the lights would come back on after booting into cm10 the first time. Any more help on a perm solution would be appreciated. i know there are perm soltuions for other phones but i hvaen't found one that works with p930 yet, i've even seen some for optimus 2x and G but they won't work on LTE, even rootdim doesn't work i've already contacted the developer and told him i can help him with compatibily if he needs anything from my phone to help update rootdim for p930 incase other people are having this problem as well., the problem is mostly that LTE screen is incredibly good and bright, and i dont want to wreck the clarity with my aftermarket digitizers overlight bright cap button lights blaring into my eyes and ruining the beauty of the HD screen on this thing. I mean after all how many of us need lights to tell us where our back/home/menu buttons are... i mean i googled this problem and there are hundreds of people trying to disable them on almost any phone you can think of, with varying success.
Click to expand...
Click to collapse
and im not as stupid as i might sound by my rambling way of speaking lol. i was able to get all the mods onto my phone and repair a smashed digitizer by myself (which requires taking the entire phone about and motherboard out of the phone and putting it back together) i just hated english class and it now shows
you can try this one:
http://forum.xda-developers.com/showpost.php?p=30698163&postcount=2
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
the exact path of "max_brightness" might vary and if so,
Code:
find /sys -name max_brightness
Try these commands via rooted adb shell or terminal emulator, if it works then modify init.d to set it on every reboot.
arda99 said:
you can try this one:
http://forum.xda-developers.com/showpost.php?p=30698163&postcount=2
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
the exact path of "max_brightness" might vary and if so,
Code:
find /sys -name max_brightness
Try these commands via rooted adb shell or terminal emulator, if it works then modify init.d to set it on every reboot.
Click to expand...
Click to collapse
how would i go about modifying the init.d to add this, when i executed the command line the lights turn off as desired =P thanks for your help thus far i just haven't modify'd that file before and it's a system file i can see so i'd rather not go trial and error, thanks again so far if you could give me a step by step to add the modifications that would be optimal.
*edit* i gave u a thanks for atleast teaching me where the file is
is it just a text file i open and add the code to? if so does it matter where i add the code (top/bottom)
ok nevermind, i navigated to it out of curiousity and i see that its a folder and obviously not a text file... however im still not sure what to do from here do i drop a text file with that code in it or something ? if so what do i name the file ? if not do i add the code to one of the two files here? the two files i see here are 00banner and 90userinit
after stopping to think i would assume that the userinit file would make most sense, if i remember correctly i actually think i can put it anywhere im just being careful and double checking. two things i'm a little hazy on, can i just add it to the end of the userinit file, if so do those commands require ; at the end of them? because everything else in this file except the loop counter has ;
thanks in advance, i also have another question, i read somewhere on these forums that the system/ folder gets reflashed at every boot, if this is true wont that overwrite this file? if that is true if i was to create a custom file and add it, would that get deleted whent he system is reflashed? does it delete the entire directory and rewrite it or just readd the files because if it was copying over the old files i think that would mean i should actually create a new file called something like dislights. just to verify if this is the case would a file with this text in it suffice.
chmod 666 /sys/class/leds/button-backlight/max_brightness
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 444 /sys/class/leds/button-backlight/max_brightness
or do i need some type of header and footer or semicolons at the end like this
{
chmod 666 /sys/class/leds/button-backlight/max_brightness;
echo 0 > /sys/class/leds/button-backlight/max_brightness;
chmod 444 /sys/class/leds/button-backlight/max_brightness;
}
sorry for all the questions im just paranoid about altering system dir when im not 100% sure what im doing.
Download and extract the attachment, put it in /system/etc/init.d, and set permission to rwxr-xr-x, you might need es explorer(enable root options) or root explorer to do so.
thanks for reply, just performed that operation, rebooting fingers crossed.
confirmed works. !!!! yay thanks man i'm going to give you another official forum thank you after im done writing this.
*note* from what i have been reading over the passed few hours, some phones my need to have the init.d activated to work on bootup automatically. the following link will provide a solution for almost all phones (even unrooted) to apply this solution. Although you need root permission to actually write files to the init.d and change permissions. thanks to everyone who contributed to this solution.
edit : adding link i forgot lol
http://forum.xda-developers.com/showthread.php?t=1710980
glad to know it works for you.
init.d is usually missing on stock roms but available on most, if not all 3rd party roms.

[ROOT HD 10] Enable advanced power menu (global actions) + my other framework mods!

*****ONLY WORKS FOR FIREOS 5.6.2.0 OR LOWER*****
The title says it all. I've activated the stock global actions power menu. The options need tweaking a bit still, but this was too good to wait.
For the moment, without an Xposed module, the stock options are: Airplane Mode, Settings, Lock Now, and volume. With Gravitybox, you can add power (might be stock. I noticed this after gravitybox was installed), restart (which leads to soft reboot, reboot, recovery reboot and boot loader reboot).
How?
One minor edit to the framework was all it took. The menu was disabled, the value set to 0. Change the value to 1, and you get the menu. Simply long press the power button for a couple of seconds and it will pop up.
I have been trying for so long to get this to work. I looked at the configuration dozens of times and didn't figure out what it meant until today. This needs a bit more work and can probably be added to my settings.apk, but that's for another day.
Requirements:
Rooted HD 10 on FireOS ***5.6.1.0 or 5.6.2.0****
Windows PC with ADB
Installation:
1. Download and install adbd insecure.
2. Download and place the attached framework-res.apk in your ADB folder and plug your tablet into your PC.
3. Open adbd insecure and check the top box to make adb insecure. Open an adb window and type the following, hitting enter at the end of each line:
Code:
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
4. Long press power button. Score. :highfive:
P.S. This framework also contains all previous modifications. References:
How to guide: Enable 'ok Google' to work from ANY screen
[ROOT] [HD 10 2017] FireTabletSettings.apk Rewritten [August 22, 2018]
[FIRMWARE] [STOCK] Pre-rooted, optimized, stock firmware for HD 10 Suez [APRIL 2019]
[Root] [HD 10 Suez] Remove parental control applications/restrictions [May 2019]
[TEST] [Flash Zip] [HD 10] [ROOT] All-in-1: The ultimate hacks, tricks & mods zip
[Root] [App] [All tablets] Disable & replace lock screen - set custom wallpaper
NO ROOT REQUIRED: Working Screen Mirroring
UPDATE (for 5.6.1.0):
June 1, 2019
- Increased default system volumes from -6 db to 8
- Set preference for 5ghz wifi to false. Setting this to true only allows 5ghz connections. 2ghz are ignored if set to true.
- Fixed typo in time server I found in the system logs.
- Extend network attributes (I don't know if these actually work but doesn't hurt either way)
- Wpa_supplicant_scan_interval by default is set to 15000.... milliseconds. Raised value to 150000000. This may have been the cause of disconnects on a constant level.
- preferences prefer dual pane set to true
- Bar separating notifications from system messages was narrow (set to true). Set it to false.
- Low battery warning is now 10% instead of 25%. Extreme low battery warning (almost dead battery) set at 5%
DragonFire1024 said:
The title says it all. I've activated the stock global actions power menu. The options need tweaking a bit still, but this was too good to wait.
For the moment, without an Xposed module, the stock options are: Airplane Mode, Settings, Lock Now, and volume. With Gravitybox, you can add power (might be stock. I noticed this after gravitybox was installed), restart (which leads to soft reboot, reboot, recovery reboot and boot loader reboot).
How?
One minor edit to the framework was all it took. The menu was disabled, the value set to 0. Change the value to 1, and you get the menu. Simply long press the power button for a couple of seconds and it will pop up.
I have been trying for so long to get this to work. I looked at the configuration dozens of times and didn't figure out what it meant until today. This needs a bit more work and can probably be added to my settings.apk, but that's for another day.a
Requirements:
Rooted HD 10 on FireOS ***5.6.1.0*** (5.6.2.0 comes soon. Possibly 5.3.x.x)
Windows PC with ADB
Installation:
1. Download and install adbd insecure.
2. Download and place the attached framework-res.apk in your ADB folder and plug your tablet into your PC.
3. Open adbd insecure and check the top box to make adb insecure. Open an adb window and type the following, hitting enter at the end of each line:
Code:
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
4. Long press power button. Score. :highfive:
Click to expand...
Click to collapse
I have updated to the latest, 5.6.3.0 (erroneously called 5.3.6.4). I guess it is risky to do this until someone tries it and says it works? I've been using retyre's prerooted installs for the last couple of releases. So if this screws things up, I would have to adb sideload and root again, which I'd like to avoid.
Ignoring that issue, can the file just be copied into the correct folder with a file manager since I'm already rooted?
sga999 said:
The title says it all. I've activated the stock global actions power menu. The options need tweaking a bit still, but this was too good to wait.
For the moment, without an Xposed module, the stock options are: Airplane Mode, Settings, Lock Now, and volume. With Gravitybox, you can add power (might be stock. I noticed this after gravitybox was installed), restart (which leads to soft reboot, reboot, recovery reboot and boot loader reboot).
How?
One minor edit to the framework was all it took. The menu was disabled, the value set to 0. Change the value to 1, and you get the menu. Simply long press the power button for a couple of seconds and it will pop up.
I have been trying for so long to get this to work. I looked at the configuration dozens of times and didn't figure out what it meant until today. This needs a bit more work and can probably be added to my settings.apk, but that's for another day.a
Requirements:
Rooted HD 10 on FireOS ***5.6.1.0*** (5.6.2.0 comes soon. Possibly 5.3.x.x)
Windows PC with ADB
Installation:
1. Download and install adbd insecure.
2. Download and place the attached framework-res.apk in your ADB folder and plug your tablet into your PC.
3. Open adbd insecure and check the top box to make adb insecure. Open an adb window and type the following, hitting enter at the end of each line:
I have updated to the latest, 5.6.3.0 (erroneously called 5.3.6.4). I guess it is risky to do this until someone tries it and says it works? I've been using retyre's prerooted installs for the last couple of releases. So if this screws things up, I would have to adb sideload and root again, which I'd like to avoid.
Ignoring that issue, can the file just be copied into the correct folder with a file manager since I'm already rooted?
Click to expand...
Click to collapse
There was one report of it working a week or two ago. No one has said anything since. If it doesn't work, worst case is you need to flash back to 5.6.x.x
DragonFire1024 said:
There was one report of it working a week or two ago. No one has said anything since. If it doesn't work, worst case is you need to flash back to 5.6.x.x
Click to expand...
Click to collapse
1. If it fails, and I'm unable to boot, I will have to redo the sideload of the bin file. Then I have to reroot. As I said, I've just been using the prerooted version for the last couple of releases which means I don't have to go through extra steps to root. Since I am rooted, I just use Flashfire to flash the new prerooted version by retyre.
2. I was asking about copying the framework file that you put out there. If I ignore the problems of it possibly messing up my system, and I just want to try it anyway, why is it necessary to use Adb insecure and the PC? Since I'm rooted, can't your framework file just be copied to the correct folder?
3. Finally, can you tell me exactly what you changed in the framework? In your other thread about modifying the framework, you give some good instructions on how to decompile and recompile. I might want to try that instead of using the version that you have created here (since I'm on 5.6.3.0). Is it really just one boolean that needs to be changed?
sga999 said:
1. If it fails, and I'm unable to boot, I will have to redo the sideload of the bin file. Then I have to reroot. As I said, I've just been using the prerooted version for the last couple of releases which means I don't have to go through extra steps to root. Since I am rooted, I just use Flashfire to flash the new prerooted version by retyre.
2. I was asking about copying the framework file that you put out there. If I ignore the problems of it possibly messing up my system, and I just want to try it anyway, why is it necessary to use Adb insecure and the PC? Since I'm rooted, can't your framework file just be copied to the correct folder?
3. Finally, can you tell me exactly what you changed in the framework? In your other thread about modifying the framework, you give some good instructions on how to decompile and recompile. I might want to try that instead of using the version that you have created here (since I'm on 5.6.3.0). Is it really just one boolean that needs to be changed?
Click to expand...
Click to collapse
1. Yes
2. With a root explorer yes.
3. For this? An integer was all. Everything else? That's too much to type. Honestly I spend hours and days reading them testing and mostly failing. I can't tell you the amount of bookmarks i have, maybe close to 500 or more. A lot of times I have to mix together old tricks. you spend most time reading than anything.
DragonFire1024 said:
1. Yes
2. With a root explorer yes.
3. For this? An integer was all. Everything else? That's too much to type. Honestly I spend hours and days reading them testing and mostly failing. I can't tell you the amount of bookmarks i have, maybe close to 500 or more. A lot of times I have to mix together old tricks. you spend most time reading than anything.
Click to expand...
Click to collapse
I don't understand your answer to 3. I'm just interested in what you changed in the framework-res to get the advanced power menu. You said it's just an integer. If I decompile framework-res.apk, where is the integer that must be changed? When you said "everything else", maybe you mean all your changes in the thread about hacks, tricks, and mods? I'm not asking about those. I'm only asking about the advanced power menu that you are talking about in this thread.
sga999 said:
I don't understand your answer to 3. I'm just interested in what you changed in the framework-res to get the advanced power menu. You said it's just an integer. If I decompile framework-res.apk, where is the integer that must be changed? When you said "everything else", maybe you mean all your changes in the thread about hacks, tricks, and mods? I'm not asking about those. I'm only asking about the advanced power menu that you are talking about in this thread.
Click to expand...
Click to collapse
If you decompile it, it would be in res/values/integers. The config would be (paraphrasing) 'long_press_on_power'. Since in this AOSP framework the global actions are active, you have a choice of values of 0 or 1. 0 being no action, 1 being the action. It's a few lines away from 'long_press_on_home' which is supposed to be between 0 and 3. 2 would activate the voice assist. But for some reason I haven't figured out, setting that value does nothing one way or the other but gravitybox fixes it.
You can change around the global action menu too I saw, but didn't have time to experiment with that yesterday.
@DragonFire1024
Nice hack! Like your new power menu - always wanted something like that!
Now, given that it'd be such a burden to update this for every FireOS version, any chance you'd take a stab at putting this together as an Xposed module? Other rooted Fire tablets could use it too.
I recall sometime in the past there were modules designed for FireOS - if you find that on XDA, you could start from that one.
DragonFire1024 said:
If you decompile it, it would be in res/values/integers. The config would be (paraphrasing) 'long_press_on_power'. Since in this AOSP framework the global actions are active, you have a choice of values of 0 or 1. 0 being no action, 1 being the action. It's a few lines away from 'long_press_on_home' which is supposed to be between 0 and 3. 2 would activate the voice assist. But for some reason I haven't figured out, setting that value does nothing one way or the other but gravitybox fixes it.
You can change around the global action menu too I saw, but didn't have time to experiment with that yesterday.
Click to expand...
Click to collapse
Here's what is in my integers.xml file for 5.6.3.0. Are you saying I need to change 2 to 1 in the first one? And no changes to the others?
<integer name="config_longPressOnPowerBehavior">2</integer>
<integer name="config_shortPressOnPowerBehavior">1</integer>
<integer name="config_doublePressOnPowerBehavior">0</integer>
<integer name="config_triplePressOnPowerBehavior">0</integer>
@DragonFire1024, Have you edited smalis? It is for do it in the framework-res.apk of another tablet.
sga999 said:
Here's what is in my integers.xml file for 5.6.3.0. Are you saying I need to change 2 to 1 in the first one? And no changes to the others?
<integer name="config_longPressOnPowerBehavior">2</integer>
<integer name="config_shortPressOnPowerBehavior">1</integer>
<integer name="config_doublePressOnPowerBehavior">0</integer>
<integer name="config_triplePressOnPowerBehavior">0</integer>
Click to expand...
Click to collapse
Correct. First config set to 1 and leave the others as is, unless you want to test them out.
Rortiz2 said:
@DragonFire1024, Have you edited smalis? It is for do it in the framework-res.apk of another tablet.
Click to expand...
Click to collapse
I have not. I rarely touch that at least not Amazon smali. It doesn't translate well at all. And haven't really had to so far. And the framework is odexed...well the .jar in system/framework is, so they don't have smalis.
bibikalka said:
@DragonFire1024
Nice hack! Like your new power menu - always wanted something like that!
Now, given that it'd be such a burden to update this for every FireOS version, any chance you'd take a stab at putting this together as an Xposed module? Other rooted Fire tablets could use it too.
I recall sometime in the past there were modules designed for FireOS - if you find that on XDA, you could start from that one.
Click to expand...
Click to collapse
I was thinking about that however if gravity box works to bring out the rest (reboot etc) I imagine other power menu modules will also work now.
DragonFire1024 said:
I was thinking about that however if gravity box works to bring out the rest (reboot etc) I imagine other power menu modules will also work now.
Click to expand...
Click to collapse
Gravity box might work - AFTER your framework-res.apk replacement (which needs updating after each OS version). As is, for me Gravity does not bring anything out beyond the stock "Power off" option. It seems a module could simply patch framework with the correct flag, and then Gravity will do its thing. Same logic would apply to other features that Amazon might have chosen to disable.
bibikalka said:
Gravity box might work - AFTER your framework-res.apk replacement (which needs updating after each OS version). As is, for me Gravity does not bring anything out beyond the stock "Power off" option. It seems a module could simply patch framework with the correct flag, and then Gravity will do its thing. Same logic would apply to other features that Amazon might have chosen to disable.
Click to expand...
Click to collapse
Install framework in OP then you need to enable the advanced power menu in gravitybox, power tweaks. Then long press power button, tap restart, then you get your options for reboot.
Rortiz2 said:
@DragonFire1024, Have you edited smalis? It is for do it in the framework-res.apk of another tablet.
Click to expand...
Click to collapse
Also for the most part Amazon just moved configurations around maybe changed a few characters or couple of words. But for the most part a significant portion if not almost all of the Android source for this version was left inside these files. There are very few things I actually had to rebuild. The battery stats is one of those things. Other things are more difficult and require other pieces of software, for example specific apks. That took quite a lot of time to hunt down working versions of certain apks. Remember we are working with what is considered a stone age OS version. So we have to literally search for needles and haystacks just to find the one tiny thing that makes it all work... Well at least some of it
Gosh, I tried for a long time to decompile/recompile framework-res.apk (5.6.3.0)...no luck! I'm using your instructions in post 2 in the 7 wallpaper thread as a guideline. I can decompile successfully. Then, even without making any changes at all, recompile does not work. I won't bother to put the error display here unless you're interested. (systemui.apk fails on the recompile also, but in a different way). A "regular application" will decompile and recompile just fine.
So I have no idea what's wrong. I do have xposed/gravitybox installed, and I wonder if that causes the problem (but it sounds like have those also?). Or some change to 5.6.3.0 that you did not encounter with prior releases. I'm wondering if you can upload your framework-res.apk somewhere so that I can try that. At least that would narrow it down to the new release or my error.
There are lots of posts about this kind of problem, but they mostly talk about wrong paths, etc. That is definitely not my issue.
I had downloaded the most recent apktool, 2.3.4. Just for fun, I just tried 2.2.0. There are 4 warnings, but otherwise, it worked. I haven't tried to install the new framework, so I can't be sure all is okay, but it's certainly a good sign. I will also try more recent versions of apktool, i.e. ones between 2.2.0 and 2.3.4, and see where it went wrong.
EDIT: 2.3.2 and earlier are good, 2.3.3 and 2.3.4 are bad.
---------- Post added at 04:58 PM ---------- Previous post was at 04:55 PM ----------
If it ain't one thing, it's another! After changing the integer, I'm trying to drag and drop with 7zip from the new apk to the old, as you described in your other thread. For resources.arsc, it works as you said, i.e. it asks if I'm sure I want to copy. But for the res folder, it doesn't ask me anything and just starts extracting into the old. I cancel it before it can complete.
Do you recall doing something different for the res folder? I could be on a different 7zip version than you, of course. I've used 7zip, but I'm not that familiar with it.
EDIT2: I don't think a notification is done if my edit gets combined with my prior post. I tried both reply and quick reply, and both ended up combining. Can someone tell me how to make it do a new post? Or maybe I'm wrong and another notification occurs, in which case, ignore this!
sga999 said:
I had downloaded the most recent apktool, 2.3.4. Just for fun, I just tried 2.2.0. There are 4 warnings, but otherwise, it worked. I haven't tired to install the new framework, so I can't be sure all is okay, but it's certainly a good sign. I will also try more recent versions of apktool, i.e. ones between 2.2.0 and 2.3.4, and see where it went wrong.
EDIT: 2.3.2 and earlier are good, 2.3.3 and 2.3.4 are bad.
---------- Post added at 04:58 PM ---------- Previous post was at 04:55 PM ----------
If it ain't one thing, it's another! After changing the integer, I'm trying to drag and drop with 7zip from the new apk to the old, as you described in your other thread. For resources.arsc, it works as you said, i.e. it asks if I'm sure I want to copy. But for the res folder, it doesn't ask me anything and just starts extracting into the old. I cancel it before it can complete.
Do you recall doing something different for the res folder? I could be on a different 7zip version than you, of course. I've used 7zip, but I'm not that familiar with it.
EDIT2: I don't think a notification is done if my edit gets combined with my prior post. I tried both reply and quick reply, and both ended up combining. Can someone tell me how to make it do a new post? Or maybe I'm wrong and another notification occurs, in which case, ignore this!
Click to expand...
Click to collapse
Lol it's going to take a bit to get used to everything. I actually had messed around with apktool when I first started all this and got so frustrated I just stopped trying. 6 months after that I tried again and it took me a week or so before I successfully compiled and installed a system apk. My initial goal was to use this method to try and trick a non rooted tablet into thinking it was installing an update to a system app. Though it worked on rooted devices, I could never get it to work for non rooted ones. Don't give up,keep trying and re check everything, especially make sure your PATH to the proper tools is correct. I'll look at the latest fireOS framework tomorrow.
P.S. without any further modifications, I tested APM+ Xposed module and it works too. You can add and remove all the optioions plus add different ones depending on the module. No further tweaking needed on my end.
Okay, when dragging and dropping res, it does finally ask if I really want to copy AFTER it takes quite a while "extracting". I was confusing extracting with unzipping or unpacking...or some other term that would imply it was changing the format. I'm still not sure if it's doing it properly, but I'll keep trying. And I'd still like to know how to make these combined posts cause a notification, and if not, how can I force it to.

Categories

Resources