Related
I shall take no credit for any of this. Smartsreenath first put me onto the idea, and pretty much anyone if this forum could've managed it. I just had the time to do it all.
Woo! Snakehult, being a genius, has made a clever little zip that uses proper scripts to just change the required value, instead of the whole file. So! Instead of me making an insane number of zips every time ROMs are updated use these instead. Cheers Snakehult!
Attached is a zip file with a whole lot of flashable zips in it. Don't flash the zip you download, extract that one somewhere and look inside
How to use:
Download the attached zip file, and extract it to somewhere on your computer. Inside the zip are a bunch of folders, each folder named after a ROM for the HTC Legend. Navigate into the folder that shares the name of whatever ROM you are using and inside you will find 6 zip files. These zips are flashable. The the zips are names thus: xxx.zip, where xxx is a number. The lower the number, the higher the apparent resolution. Choose a zip, copy it to your SD card and flash it like any other zip. To revert back to how it was simply flash the "160.zip". This just flashes a completely un-modified version of build.prop for your ROM. Make sure you only use the zips form the correct folder for your ROM, or funny things *might* happen.
More info:
By editing the build.prop file it is possible to increase the dpi of an Android device. This essentially scales everything down, so you can fit more on the screen. This is especially nice for browsing the market and the internet; as well as improving, in my opinion, the overall Android experience. The lower the number in the name of the zip, the higher the apparent resolution. It's worth noting that this does *not* change the actual resolution of the Legend; it's still a HVGA device. So you still can't install apps designed for bigger, more powerful phones, like the HTC Desire or Nexus One. This is a somewhat flawed way of achieving this effect, and can have some ugly side effects:
Some apps simply don't scale
HTC-IME mod ends up screwed
Games *can* be rendered unplayable, but not always. Often the menu is the worst affected part.
A work around to fix a number of issues is to disable the built in compatibility mode of Android, and if I knew a way to do this through a zip, rest assured that I would. It'd save me having to explain how to do it. Alas, I don't know how, so here's how:
In your ROM look for an app called "Spare parts". If it's not there look for it in the market. If you open that app and scroll down to the bottom you will find a checkbox option for "Compatibility mode". Ensure that this is *un-checked*, then reboot. Most issues will be resolved. As I learn more about Android I shall keep an eye out for a way to force apps to scale correctly, and if I ever find one I'll update these.
I have also tried values higher than usual, just for kicks. I don't expect them to be useful, nor will I make actual zip files for them, but I went all the way up to 200; and it felt like I was using an HTC wildfire: everything was really quite cramped.
My personal favourite setup is as follows:
CM 6.1, with a 768MHz overclock
My "lcd-density" (this MOD) set to 130
Launcher Pro Plus with 5 icon rows
Below is a paste of what was the first post (when I was just trying to fix a ****-up on my part), and is now here for reference. It has all of the original build.prop files attached.
Attached is a .zip file, which you will need to extract somewhere. It's not for flashing. Within this zip are several folders, each containing a "build.prop". You'll notice that each folder is named after a ROM: Azure, NeonMOD etc. The "Based-on-stock" folder should cover these ROMs:
[ROM] Based on Official WWE_2.03.405.3 ROM + A2SD [Rev 03 - released]
[ROM] UPDATED Almost Stock Legend HTC WWE 2.03.405.3 Radio 7. 08.35.21
You'll need to use ADB to push these files, as I haven't had time to make flash-able zip's for them yet
Instructions:
1. Extract the zip to a suitable directory, and locate the appropriate build.prop
2. Copy the build.prop to your AndroroidSDK/tools folder
3. Reboot your phone into ClockworkMOD recovery and navigate the the "Partitions menu", then click "mount /system"
4. Connect your phone to the PC and start CMD/a terminal window in your AndroidSDK/tools folder
5. Run the command "adb devices" to ensure that the ADB server is running, and that the PC has detected your device correctly
6. Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
This will put your resolution back to default, but should fix everything else too. If you still want a higher resolution then follow the guides in posts 1 and 2 of the other thread. This one.
If you can't use ADB for whatever reason you'll just have to wait it out until myself or someone else create proper, flash-able, fixes. I have done this to try and quickly rectify the issue; assuming, of course, that most people in this forum can use ADB
I will make proper zips, but it's getting late for me...
Click to expand...
Click to collapse
hi
here is a zip for neonmod 0.21 with 135lcd, flashed it on my legend today with rom manager
Wow do we have a lot of ROMs...
Anyhoo, I am currently working on appropriate flashable zips for each ROM, and each ROM will have the following versions:
110
120
130
140
150
160 (original)
I'm doin' 'em as fast as I can..
EDIT:
Current thoughts:
All build by Ali Ba have nice, short build.prop files. The current record for the longest one it held by MyTouch Legend...
TheGrammarFreak said:
Wow do we have a lot of ROMs...
Anyhoo, I am currently working an appropriate flashable zips for each ROM
Click to expand...
Click to collapse
Awesome!
All our lovely ROMs are actively being used, and its great.
Thx for all hard work!
No worries, I hope I haven't missed one
Now to sign 50 60 zip files...
EDIT:
DONE! All finished. I really hope they work. I can't test them all, but there is no reason why they won't work. Lemme know either way.
nice job
thanks bro
nice
spare parts is also in neonmod
xennr3 said:
nice
spare parts is also in neonmod
Click to expand...
Click to collapse
Cool, and you can turn compatibility mode off?
TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
sure
1234
TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
thanks for your work! i just tried 130 dpi and it seems really good.. i'll try also others zip asap!
yes with compatibility mode off all softwares i tried work really well!
xennr3 said:
sure
1234
Click to expand...
Click to collapse
Cool, thanks for the info. I'll update the OP when I'm home
Sent from my Legend using XDA App
Wow, really cool mod Love it!
Good job!
Cool, glad you like it
Just flashed 130 for SpeedLegend and it worked like a charm
HTC_IME works here (this isnt the mod)
images dont look so good anymore and stuff, but alright
works fine
edit; TBH I find the 140 to be 'more' compatible overall, and show a better picture (ive tried all the flashables)
thats besides the orgnal setting btw, it gives the best picture by far.
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
SimDroid said:
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
Click to expand...
Click to collapse
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
i glad to hear that someone like you got the idea from my thread........good work ...........and nice job.....you will get all help from me and from my friends
FOLLOW ME http://smartsreenath.blogspot.com/
TheGrammarFreak said:
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
yeah, that is for 5 rows on a screen, but you still can't have 5 icons on a row... That's what I want. I tried ADWLauncher again, but it feels so god damn slow.
Ummm, I have 5x5 icons on my desktop with the stock ADW launcher. Just check out "Settings > ADW > Screen prefs > Desktop cols/Desktop rows"
Ok so this started out as a small project to make my day to day phone functions easier and quicker but I thought I might share it incase anyone thought my AdbTool was helpful or just nice to have.
Functions so far:
1. Check for device
2. Push or Pull a File
3. Install .apk
4. Reboot
5. Root your Droid X
6. Change bootanimation
7. Push framework (specifically for framework)
8. issue whatever adb command you need to with out the extra typing
9. Set project
10. Error log
11. Clean up folder
There are more functions to come in the future so let me know if you like this script and what you wanna see added. There is no install just unzip and open the .bat file.
This sounds great! Though I'm on Linux machine, so I don't think ill be able to use it :/
Sent from my DROIDX using XDA App
No sorry, I should have specified. It is a Windows script... Just wait though, because Sunday I will be getting a desktop that is already running linux. If you really want I will take the time to make a script to run for linux?
Sent from my DROIDX using XDA App
rooting the dx doesnt work for me :/
Huh... what is happening when you enter that option? Sorry for the long time for me to post I missed the email alert.
Sent from my DROIDX using XDA App
I'm assuming this doesnt allow root for 2.3.3 ota correct?
since all I see is rageagainstthecage in the files
This looks like a really useful program! I might do some work this weekend on it and see if I can get it working for the DROID 2 and port it over to UNIX machines.
If I set it up for unix I will add an SBF option too.
Woa just realized this is a really old thread
ljbaumer said:
This looks like a really useful program! I might do some work this weekend on it and see if I can get it working for the DROID 2 and port it over to UNIX machines.
If I set it up for unix I will add an SBF option too.
Woa just realized this is a really old thread
Click to expand...
Click to collapse
Yeah, this thread is quite old (almost a year) and I am sure the program/script needs to be updated to work.
It is a good idea though (if it can be updated)
D.
I'd like to make a request for a Mount and UnMount command.
fyi....you spelled Folders wrong in the main menu "Floders"
.
I can make the program for yall. Yall just need something for shell or a gui for windows?
whatever's easier for you, either would be appreciated it
i have adb properly installed by doing adb devices in cmd it shows my dx
but when i use your tool it says it cannot find the path specific
I had a patched version of libflashplayer.so that worked fairly well with Hulu on VEGAn 5.1.1 but when I upgraded what I think was the same .so no longer worked.
So here's what you want to do:
1) Install Flash 10.2 off the market or however else you do it.
2) Get this: http://www.2shared.com/file/hW5sepYW/libflashplayer.html
3) Use your favorite method (adb, root explorer, etc.) to make a backup copy of /data/data/com.adobe.flashplayer/lib/libflashplayer.so (I named mine libflashplayer.so.bak)
4) Put the file you downloaded in step 2 over the original (that's /data/data/com.adobe.flashplayer/lib/libflashplayer.so)
5) You need to make sure the browser restarts. If you are adept, go to Settings, Applications and force close the browser. If that worries you, reboot the tablet (nuclear option).
6) Make sure the browser is set to report itself as a desktop (Depends on your browser).
Notes: If you are running Ad Free, Hulu will complain and make you wait 30-60 seconds while it complains.
If it looks like it is working but the screen is black or frozen, touch the video. The click sensitivity is ridiculously high so when you try to adjust anything or press play or full screen it will often see the press twice and just go back to pause.
Works fine with pershoot's latest kernel and VEGAn Ginger even full screen. I'm using Opera Mobile. Haven't tried others, but if they load flash should be ok.
Good luck!
Update: The "Long boot problem" winds up erasing this fix on each reboot! Until that gets figured out here's a work around:
Get Script Manager from the market. Create a script that runs as root at boot time.
Script manager already puts in the first line you need so the whole script looks like this:
#!/system/bin/sh
cp /mnt/sdcard2/libflashplayer-patched.so /data/data/com.adobe.flashplayer/lib/libflashplayer.so
Use your favorite method to put the patched so file on /mnt/sdcard2 (or where ever you want to put it). If the boot thing gets fixed you should not need this anymore.
It is wise to test the script by simply running it before rebooting. You should not get any errors. If you do, fix them before you reboot.
Awesome, thanks! I tried everything and the closest I could get was picture but no sound. This worked perfect, using stock browser. Thanks again!
For some reason, it used to work to just change AND to WIN but now you have to jimmy the version number as well, apparently.
Okay following instructions exactly....downloaded new file and using rootexplorer to rename old file (bak) and replacing with downloaded file....
When I reboot my tablet the library file is resetting back to default....the original file is put back in place and the new downloaded file and backup file (bak) are nowhere to be found.....
I'm on VeganGinger using pershoots new oc kernel.....
Any ideas?
Hmm... same thing here! I just rarely reboot because it takes so long.
So this is probably related to the boot time issue. I figured out that the boot time is long because it unpacks the native libs for everything at boot time which I don't think it should be doing. So that explains that.
Could make a new APK but it would have to be signed. What I will probably do is keep my patched copy somewhere else and do a Script Manager script at boot time to do a copy:
cp /mnt/sdcard2/libflashplayer-patched.so /data/data/com.adobe.flashplayer/lib/libflashplayer.so
(all on one line)
A hack, for sure though.
That does the trick, it looks like. You can get Script Manager on the market. Gscript would work but it can't auto run on boot as far as I know. This makes me more certain that VEGAn 5.1.1 was NOT unpacking the APKs on boot
Script manager already puts in the first line you need so the whole script looks like this:
#!/system/bin/sh
cp /mnt/sdcard2/libflashplayer-patched.so /data/data/com.adobe.flashplayer/lib/libflashplayer.so
Use your favorite method to put the patched so file on /mnt/sdcard2 (or where ever you want to put it). If the boot thing gets fixed you should not need this anymore.
The other thing I use ScriptManager for is to bind mount sdcard2 in the /mnt/sdcard/sdcard2 directory so programs that only look in /sdcard can find things in my sdcard2 folders.
Fantastic ...thanks wd!
I'll give it a try...thanks for figuring out a work around so quickly ...
QUESTION .....so I create a the new script with Script Manager and place it where? Sorry ...have done the rooting, ROMs, kernels, etc. but scripts are new territory for me...thnx.
UPDATE.....Okay....created script to match your example...placed libflashplayer-patched.so on sdcard2...not sure where created script should be placed....checked "run at boot"...placed new script file on sdcard2, but Hulu did not work after rebooting so I'm guessing script needs to be in another location to run.....
script manager puts them in its folder. what happens if you run it from script manager? I am sure it needs root checked.
first time using Script Manager so I selected "New Script" and then gave it a file name "Hulu"...then copied the script language into that file and then Run...
came back with errors:
cp: can't stat '/data/data/com.adobe.flashplayer/lib/libflashplayer.so/mnt':not a directory
cp: can't stat '/data/data/com.adobe.flashplayer/lib/libflashplayer.so/libflashplayer-patched.so': Not a directory
Those paths are not right. Missing space I think.
Here is what I have:
Code:
#!/system/bin/sh
cp /mnt/sdcard2/libflashplayer-patched.so /data/data/com.adobe.flashplayer/lib/libflashplayer.so
yep...too many spaces..fixed that..
now when I do a quick run in Script Manager I get the following error:
cp: can't create 'data/data/com.adobe.flashplayer/lib/libflashplayer.so': File exists
do you have run as root checked?
wd5gnr said:
do you have run as root checked?
Click to expand...
Click to collapse
Bingo....I had Run on Boot, but not Run as Root....
Unfortunately after running and going to Hulu...on the main page I am getting a messages saying: "Hulu requires Flash Player 10.0.32 or higher. Please download and install the latest version of Flash Player before continuing."
I have the latest Flash 10.2 available for Android....user agent is set to desktop on browser....strange...
10.2.59.1 is what I get at www.playerversion.com. Is it possible you have the wrong one in the data directory?
is that the libflashplayer-patched.so file? I'm using the one from the download link in your original post..
if that's not it let me know....thanks for your help..sorry you're having to walk me through this....
WHEN I GO TO PLAYERVERSION.COM ON MY TABLET IT SAYS I DON'T HAVE FLASH PLAYER INSTALLED. Could the replacement libflashplayer.so file be incorrect?
Its working for me. You do have Flash 10.2 installed from market first right? I'm sure you do or it wouldn't be getting overwritten.
Here's what I'd suggest.
Remove and reinstall 10.2 plain. Turn off the boot script. Reboot.
Open some flash site like the player test site with your browser of choice (I use Opera Mobile). Observe that it tells you that you are on 10.2. something.
Now turn the boot script back on. If you force close the browser, just run the script. If you prefer, just reboot. Now go back to the same site and observe that you have Flash running and it is now the patched version #. If not, Hulu isn't going to work.
Once that's working, try Hulu again.
No worries. Would be good to know that it works somewhere else ;-)
Works great!
Thanks. Works great on the stock browser. Still get the "your operating system not supported usung Opera Mobile" tho. Just downloaded latest version of opera and it no longer let's you choose type of system, so I imagine that is the problem.
Is that Opera Mobile or Opera Mini?
Okay...Hulu now up and running...
When I looked at the script and realized what it was actually doing I realized that I shouldn't have been actually naming the patched file as "-patched" as that was why after the script ran Flash no longer showed up...
I renamed to match the libflashplayer.so file it was replacing...also moved file and script reference to "sdcard" rather than "sdcard2" to see if that made a difference...now working fine on Hulu....
Thanks for the fix and walking a noob thru using scripts!
wd5gnr said:
Is that Opera Mobile or Opera Mini?
Click to expand...
Click to collapse
I think it's Opera Mini that only gives you the option of turning on or off "mobile" version of browser...tried it out earlier....
I thought I'd offer my solution to disabling the hard key vibrations on the Atrix since other people might find this useful. This method differs from the other solutions in that it doesn't tamper with your Silent Mode vibrations (like StreakVibrations does) and it's code based, so it shouldn't tamper with any themes you have installed (like the framework-res.apk method). It is firmware dependent though since it's a code modification.
You'll need an android.policy.jar modified for your firmware.
What I'm doing is I'm modifying the method called performHapticFeedbackLw, and telling it to skip triggering the vibrate pattern for all effects (there are 5) except for keyboard taps. Long press vibe, virtual key vibe, safe mode disabled vibe, and safe mode enabled vibe will no longer trigger... Incidentally, does anyone know what safe mode on this phone refers to?
To use the file, you need to be on Bell, Telstra, GingerBlur, Gladiatrix or stock ATT 1.8.3 firmware, and be deodexed. Can you copy the file to your phone without being deodexed? I don't know. I'm a programmer, but an Android newbie so just to be safe it's best if you're deodexed.
Before you try anything, obviously make sure you are backed up. At least copy your existing android.policy.jar so that you can restore it if necessary.
All you need to do is either:
a) Run the novibes.bat script packaged in the zip. There are a couple prerequisites:
1. Make sure to set your USB connection to "None" on your phone.
2. On your phone, go to Settings > Applications > Development and make sure USB debugging is turned on.
3. Plug your phone into your PC and let it install any necessary drivers.
4. Then you can run novibes.bat.
or
b) Follow the steps outlined below to do it manually:
1. Replace /system/framework/android.policy.jar with the one that I've attached.
2. Make sure the permissions of the file are set to rw-r--r-- (thanks for reminding me, Meloy and for correcting, natboy!). The easiest way is to use Root Explorer, long press the file, choose permissions, and set owner: read/write, group:read, others:read. Otherwise, use Terminal and type "chmod 644 /system/framework/android.policy.jar" without the quotations.
3. Reboot.
For those not on stock Bell, I'd be willing to modify your android.policy.jar and post it here if you provide somewhere for me to download it, and specify what firmware it comes from. It's quite quick to do once you're set up so I don't mind. Alternatively, make the change yourself:
1. Download baksmali and smali (both .jars and scripts, total 4 files).
2. Copy /system/framework/ from your phone to your computer.
3. Copy all the files from step 1 to the framework directory from step 2 on your computer.
4. Unzip android.policy.jar and copy its classes.dex file to the framework directory on your computer.
5. From the command line, navigate to the framework directory and run "./baksmali classes.dex". It will create a directory named "out".
6. Open "out/com/android/internal/policy/impl/PhoneWindowManager.smali" in a text editor.
7. Search for a method called "performHapticFeedbackLw". Go to near the bottom of that method, and you will see the Dalvik bytecode representation of a switch statement:
Code:
.sparse-switch
0x0 -> :sswitch_27 #This is for long press vibe
0x1 -> :sswitch_35 #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :sswitch_3b #This is for safemode disabled vibe
0x2711 -> :sswitch_3e #This is for safemode enabled vibe
.end sparse-switch
8. Here's an example of how you might want it to change. Basically you want to replace the original goto labels with one that causes the method to step out without triggering a vibe, and that notifies the calling method there was no vibe by returning false. The label to use is called ":cond_1d":
Code:
.sparse-switch
0x0 -> :cond_1d #This is for long press vibe
0x1 -> :cond_1d #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :cond_1d #This is for safemode disabled vibe
0x2711 -> :cond_1d #This is for safemode enabled vibe
.end sparse-switch
9. From the command line in the framework directory, run "./smali -o classes.dex out". You now have a new classes.dex that has your modification.
10. Zip up the classes.dex with the META-INF directory from your original android.policy.jar. Rename the zip to android.policy.jar.
11. Copy the new file to your phone and reboot.
12. At this point you should be done.
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
n1ckr0th said:
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
bearsfan172 said:
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
Click to expand...
Click to collapse
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
n1ckr0th said:
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
Click to expand...
Click to collapse
Yes, this would work perfectly fine on ATT. You can either follow the instructions I provided, or if you like you can post /system/framework/android.policy.jar from your phone somewhere and pm me the link so I can download it and I'll do it for you. Also mention what firmware you're on. I just don't want to download hundreds of MB of firmwares which is why I didn't set one up for all the ATT firmwares.
That other method requires editing a file that is guaranteed to change with any theme you install. That means anytime you change themes you'll need to edit that .apk yourself, or wait for someone to bring the change over. android.policy.jar is unlikely to change for themes.
Ok, I've posted a version for ATT 1.8.3 that was given to me by n1ckr0th.
n1ckr0th, let me know whether it works fine or not. There should be no problem, it looked just like the other 2 versions I modified.
Incidentally, he's using GingerBlur 3.5 so anyone on stock be careful (ie. copy your original file to somewhere else on your phone). It shouldn't matter at all because from what I see, there aren't any resources to modify in android.policy.jar so GingerBlur's should be the same as stock. At any rate, it won't brick your phone if you put the wrong one on. I put Telstra's on my phone by accident and it just messed up the the graphics on screen (maybe because the addresses were all wrong for my phone). You can still use adb, or sshdroid to copy and replace with your original android.policy.jar.
please delete
meloy said:
Don't use this on AT&T 1.83!
After the replace and reboot my phone was really laggy and some applications doesn't start anymore (camera, contacs for example). After i have replaced it with the original file i have still the same problem.
My phone config:
- SBF 1.83
- rooted (GingerBreak 1.20)
- sideloading enabled (GladEnabler)
- GladiAtrix 3 b0.2 ROM
- LauncherPRO
- GingerBread Theme only
Click to expand...
Click to collapse
What? That can't be right, if you still have the same problem after copying the original file, that means that you must have done something wrong. It's a single file change, provided you returned the file to the original, it will be back to the way it was. How did you copy the file? And also, are you deodexed? As mentioned in the original post, you have to be deodexed, because I don't know the results of using it on a non-deodexed system. Your posted config makes it sound like you might not be.
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
meloy said:
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
Click to expand...
Click to collapse
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
maledyris said:
Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
meloy said:
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
Click to expand...
Click to collapse
Interesting, that never occurred to me. I usually go into terminal and type in reboot to reboot my phone. I think I'll add that to my phone too...
maledyris said:
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
n1ckr0th said:
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
Click to expand...
Click to collapse
Hmm, how far does it get? Do you at least get to the boot animation? I notice that it may sit at the boot animation for a really long time after changing a file sometimes. Probably updating the cache or something. It's odd that it wouldn't work for you considering it's your file and it worked for meloy. How did you copy the file over?
If you try again, delete the original file, so you can be sure it's no longer there, then try the copy again.
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
I have no problems with this mod. It works all fine.
Been waiting on this mod. Streakvibrations has me missing my notification vibes. Thank you
It gave me a red light on boot, stuck at Motorola logo for infinity. I booted into recovery and reflashed gb 3.5 to fix it. Ill try your idea of deleting it then moving the new one.
Sent from my MB860 using XDA App
EDIT: still didnt boot, had to flash again..
I'm getting the flashing red light and rebooting as well. I can't get into CWM though, going to have to flash a SBF. Only think I can think of is maybe the Dalvik cache needs to be wiped before rebooting?
Edit: I'm on an AT&T phone and used GB to deodex as well.. maybe it's not catching all the files..
lurchbyrep said:
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
Click to expand...
Click to collapse
Are you on stock 1.83? Now that we know that android.policy.jar has some mods built into it for Gingerblur pseudo rom, the att 1.83 file I posted probably isn't ideal for stock users.
If you're on stock, maybe you could post your android.policy.jar somewhere and pm me the link to download. Then I could put together a pure stock att one when I get home.
Sent from my MB860 using XDA App
requires Root (Superuser/Busybox), and a kernel that supports "init.d" scripts (script files that are stored in /system/etc/init.d/).
The script also has a partner called V6 supercharger they go pretty well together heres a link to the V6 supercharger by zeppelinrox
this script is so easy to use but users might have problems using it so here is a easy install for you all to use i have converted it to run on non samsung phones by renaming the file and removing processes connected to the stock samsung apps
Have Clockwork recovery installed
Download the update.zip from the bottom of the post
Reboot into recovery and install the update.zip
Now for the really easy part
Using Root Explorer navigate to ect/init.d and select mount RW now scroll down to the "97loopy_smoothness_tweak" file and open it in the text editor within root explorer and you will see the 3 main sections to the script they are called
At the start of the script you will see this
Code:
USER_LAUNCHER=""
you need to add the launcher you currently use so that it gets locked in
Resident system apps
Other system apps
Other apps
in the 3 sections you will see lines one code that look the same which are
Code:
if [ $PROCESS_1 -eq "0" ]; then PNAME="com.android.phone"; NICELEVEL=-20; if [ `pidof $PNAME` ]; then renice $NICELEVEL `pidof $PNAME`; PROCESS_1=1; P_CHECK=`expr $P_CHECK + 1`; fi; fi;
All you do to add a app you want to keep in memory for as long as possible is to edit the script and change these values for e.g the stock dialer to go contacts
Code:
PNAME="com.android.phone";
to
Code:
PNAME="com.japps.contactpro";
that will keep Go Contacts EX locked in the background so everytime you wish to use the GC EX dialer you wont have to wait for it redrawing before using it.
To find the process names goto the data/data folder and all the folders you see in there are the process names used by the apps e.g. the com.android.vending folder is the process name for the vending.apk aka market app.
Just to let users no this script will not auto start the apps on reboot and once you first select the app you have added to the script after reboot you will have to wait for the app to redraw the app again into the memory slot once it has done that the app will remain in a cache type(hidden) form until you run the app again then it will return to ram in the foreground.
lpy of XDA said:
What this script hopes to achieve:
- Entering your PIN with minimal/no delay/lag
- Minimising delay with lock screen pattern/unlock (not the time it takes to wakeup, but the touchscreen response lag)
- Having smoother notifications on the status bar, and smoother pulldown menu response
- Minimising Launcher lag while Media Scanner is running (can scroll through screens without heavy pauses)
- Minimising lag when scrolling through the market while icons are still loading
- Installing/Uninstalling apps while continuing other tasks
- Minimising/eliminating intermittent lag spikes in gaming
- No delay in being able to answer phone calls
... you get the idea
Click to expand...
Click to collapse
Thanks goes to the creator lpy @XDA
tweak source:
http://forum.xda-developers.com/showthread.php?t=1137554
Download:
http://www.mediafire.com/?g4fte3m87t3ukui
Install via CWM as update.zip ???
Have you tested this? I'm doing backup right now, and I might, but I'm looking at the script, and it says it's for Galaxy S. There's also a part on one of the first lines where you have to specify your launcher. Also, I don't think the scripts it our init.d even begin with "S_..", but rather with a two digit number, e.g. "06swapon".
EDIT: I edited the file to point to my launcher "com.fede.launcher", and touched nothing else. Named it "18smooth" or something of the sort, and put it in /system/etc/inid.d. The system failed to boot(never got past the second "LG" screen. Maybe it's the rom I'm using, but this is not working so far. I hope your promised tutorial is of use.
nutterbg said:
Have you tested this? I'm doing backup right now, and I might, but I'm looking at the script, and it says it's for Galaxy S. There's also a part on one of the first lines where you have to specify your launcher. Also, I don't think the scripts it our init.d even begin with "S_..", but rather with a two digit number, e.g. "06swapon".
EDIT: I edited the file to point to my launcher "com.fede.launcher", and touched nothing else. Named it "18smooth" or something of the sort, and put it in /system/etc/inid.d. The system failed to boot(never got past the second "LG" screen. Maybe it's the rom I'm using, but this is not working so far. I hope your promised tutorial is of use.
Click to expand...
Click to collapse
yes i have tested it and it works i will be uploading a modded one for the update.zip but if you install it just rename it to 97smoothnees, it asks for the launcher you currently are using e.g. adw launcher but if you have any worries wait until tomorrow for the tut
I think this is helping with battery management because my battery seems to be going down slower
Sent from my GT540 using XDA Premium App
Let's hope I'm wrong. Looking forward to that tutorial.
Downloaded it, and flash'd it in cwm on my girlfriends gt540. In her opinion, it makes a noticeable difference.
Sent from my Nexus S using XDA Premium App
Oki, so I install this script and I must say that it's working. ;-)
Tut added hopefully you can all understand it
Hmm, I don't know why but I don't have "97loopy_smoothness_tweak" in folder.
pRo_lama said:
Hmm, I don't know why but I don't have "97loopy_smoothness_tweak" in folder.
Click to expand...
Click to collapse
let me have a quick check to see whats going on
eoghan2t7 said:
Have Clockwork recovery installed
Download the update.zip from the bottom of the post
Reboot into recovery and install the update.zip
Click to expand...
Click to collapse
I did this and when i'm trying to do next i can't find the file in etc/init.d folder
pRo_lama said:
I did this and when i'm trying to do next i can't find the file in etc/init.d folder
Click to expand...
Click to collapse
i just tried the update.zip again there and it installed fine for me what clockwork version are you using?
but you can extract the zip file and manually add the file to the init.d folder and give it these perrmissions
xxx
xxx
xxx
I have 4.0.1.4.
When I apply script, reboot phone then on screen with PIN I don't have any delay.
pRo_lama said:
I have 4.0.1.4.
When I apply script, reboot phone then on screen with PIN I don't have any delay.
Click to expand...
Click to collapse
try adding it manually to see what happens.
So I must manualy add the file into system and then continue with tutorial ???
yes you coy the script to the ect/init.d folder then continue with the tut
ok, i'm going to try it ;-)
Can't download please mirror on another hoster.
Sent from my GT540 using XDA Premium App
Should this method not eat battery rather than conserving it? As apps run in background correct me if m wrong....
Sent from my GT540 using XDA App