Related
I'm not sure on which phones this will work.
Motorola Milestone is for certain. Probably other Motorolas as well.
If you have the file /system/bin/mot_boot_mode, then this should work just fine.
Edit: Works on DroidX, Atrix, Bionic, Defy... (I guess it really does have a chance of working if you have mot_boot_mode
Do this at your own risk
What you need:
1. GScript Lite or Script Manager
2. Rooted Phone. For Milestoners, you can use Universal Androot (not in market ?)
3. Busybox Installer
You don't need to have a vulnerable recovery applied.
Why you want it: People on custom roms take it for granted that they can run custom scripts from the /system/etc/init.d folder.
Overclocking, tweaking memory settings, kernel tweaks, etc.
Those on Stock ROMS usually have to resort to 3rd party apps (eg. Milestone Overclock, Auto Memory Manager) that take up memory to do stuff that custom roms do automatically and easily - with boot up scripts.
It's possible for Stock ROMS to get this ability via open recovery but most users may find it overwhelming and confusing as to where to even start.
I have also been working on GScripts to get my SuperCharging / Bulletproof Launcher tweaks to work on all phones without need of 3rd party software.
I found that the easiest way would be with a startup script placed in the /system/etc/init.d - the same way that custom roms do it.
Since alot of users would be uncomfortable with getting it working via open recovery, I converted the open recovery script to work in GScript!
Booya!
Instructions: 1. Extract the attached zip file into the root of your sdcard. The files should then be inside the folder /sdcard/gscript
................... 2. Run GScript Lite
................... 3. Press menu > Add script > Load file button
................... 4. Select "!Autostarts - Enable init.d on Stock ROMS.sh"
................... 5. Leave "Needs SU?" checked and press the Save button.
................... 6. It now shows up in the list of GScripts.
................... Note: GScript will save it internally within it's settings.
................... 7. Run the script by simply selecting it in GScript... and...
................... 8. Get tweaking!
All thanks go to those who put Androidian OpenRecovery together! ie. Skrilax_CZ, Azhad and 89luca89!!
Good job, Joe. I'll test and let you know.
btw, the values that we discussed a few days back work better for me on stock. First 3 from your script and last 3 default values.
Cool beans
zeppelinrox said:
What you need:
1. GScript Lite
2. Rooted Phone. For Milestoners, you can use Universal Androot (not in market ?)
3. Busybox Installer - Have it install the latest BusyBox (v1.19). This ensures GScript doesn't spit out ugly stderr: messages.
You don't need to have a vulnerable recovery applied.
Why you want it: People on custom roms take it for granted that they can run custom scripts from the /system/etc/init.d folder.
Overclocking, tweaking memory settings, kernel tweaks, etc.
Those on Stock ROMS usually have to resort to 3rd party apps (eg. Milestone Overclock, Auto Memory Manager) that take up memory to do stuff that custom roms do automatically and easily - with boot up scripts.
It's possible for Stock ROMS to get this ability via open recovery but most users may find it overwhelming and confusing as to where to even start.
I have also been working on GScripts to get my SuperCharging / Bulletproof Launcher tweaks to work on all phones without need of 3rd party software.
I found that the easiest way would be with a startup script placed in the /system/etc/init.d - the same way that custom roms do it.
Since alot of users would be uncomfortable with getting it working via open recovery, I converted the open recovery script to work in GScript!
Booya!
Instructions: 1. Extract the attached zip file into the root of your sdcard. The files should then be inside the folder /sdcard/gscript
................... 2. Run GScript Lite
................... 3. Press menu > Add script > Load file button
................... 4. Select "!Autostarts - Enable init.d on Stock ROMS.sh"
................... 5. Leave "Needs SU?" checked and press the Save button.
................... 6. It now shows up in the list of GScripts.
................... Note: GScript will save it internally within it's settings.
................... 7. Run the script by simply selecting it in GScript... and...
................... 8. Get tweaking!
All thanks go to those who put Androidian OpenRecovery together! ie. Skrilax_CZ, Azhad and 89luca89!!
Click to expand...
Click to collapse
Hi, good evening.
Excellent work... But I cant see
gscript-All_ROMS-SuperCharge+BulletProof_Pack_v4.zip
It isnt a link.
Thanks. Best regards
Marcos
Hey Zep, will these work on 2.1 eclair? I am running 2.1 for a change. Had enough of the half cooked Froyo and GB roms.
I'm not sure.
Did you flash a custom eclair or stock?
I'd love to get it to work with stock eclair though.
If you have a 10overclock, where is it?
Actually, a good test is if you were able to overclock with AOR's froyo menu after running this gscript
zeppelinrox said:
I'm not sure.
Did you flash a custom eclair or stock?
I'd love to get it to work with stock eclair though.
If you have a 10overclock, where is it?
Actually, a good test is if you were able to overclock with AOR's froyo menu after running this gscript
Click to expand...
Click to collapse
I am currently overclocked using milestone overclock app. There is no 10overclock file in /system/etc/init.d folder. I will try overclocking using AOR after loading modules.
Sent from my Milestone using Tapatalk
In AOR, the eclair overclocking uses the /system/bin/boot_script folder as opposed to the usual /system/etc/init.d folder.
If I do a google search for "eclair /system/bin/boot_script" there aren't that many results.
If I do a google search for "eclair /system/etc/init.d" there are twice as many hits.
So this should work on stock eclair without vulnerability patch
Applying this to a rooted, stock 2.2.1 milestone makes the M logo bootloop... ive tried it twice. Followed the steps exactly..
And I think it may have bricked my phone :S Now it won't turn on anymore...
So buysbox is installed right?
I actually developed the script working with stock telus 2.2.1 so it works.
I had a problem flashing the sbf 2.2 upgrade and was stuck on the M logo.
From recovery menu, I had wiped caches/reset to factory defaults and it booted up.
What have you tried so far?
zeppelinrox said:
So buysbox is installed right?
I actually developed the script working with stock telus 2.2.1 so it works.
I had a problem flashing the sbf 2.2 upgrade and was stuck on the M logo.
From recovery menu, I had wiped caches/reset to factory defaults and it booted up.
What have you tried so far?
Click to expand...
Click to collapse
I can't do anything really. It won't turn on, not even into recovery. No M logo, the screen doesn't even light up, and when I try to charge, the charge light doesn't turn on, and it doesn't charge, and isn't recognized by my comp. Initially it went into a boot loop, but then I restored via nandroid, but then I tried again, and I left the phone for a couple mins, then when I got back, it was really warm and wouldn't turn on or charge. I have a feeling something burnt out. I'm gunna bring it to telus today and try and get a new one.
For charging it, use the wall charger.
Does anything happen if you take the battery out and plug it in?
Normally, you would get a big battery icon with a question mark.
Then put the battery in and it changes to whatever the battery level is.
zeppelinrox said:
For charging it, use the wall charger.
Does anything happen if you take the battery out and plug it in?
Normally, you would get a big battery icon with a question mark.
Then put the battery in and it changes to whatever the battery level is.
Click to expand...
Click to collapse
I don't have my wall charger with me, but I've made some progress I think..
Now when I plug it into usb without the battery, the light goes on, and I can insert the battery without it shutting off. But it still won't turn on , and when I plug it in with the battery in it, the light doesn't come on. I've been trying that battery bypass thing, and my comp is definitely responding to it being plugged in, but only for a second or two.
If you don't have much battery left, you're not gonna get too far.
It'll just keep draining more n more.
Howabout a car charger to charge it in the meantime?
zeppelinrox said:
If you don't have much battery left, you're not gonna get too far.
It'll just keep draining more n more.
Howabout a car charger to charge it in the meantime?
Click to expand...
Click to collapse
I brought it to telus. The battery is fine, theres juice. They tried charging it with a regular wall charger, but still no luck, so in it goes for repairs.
ah ok.
Hopefully it won't take too long to get it back
zeppelinrox said:
ah ok.
Hopefully it won't take too long to get it back
Click to expand...
Click to collapse
They said 2 months is the max, and I'm stuck with a stupid moto backflip.. gunna try and switch it out tho.. btw, your scripts worked awesome in openrecovery when I was using cm7. That bulletproof launcher was perfect
heh.. thanks
So if you had openrecovery going with vulnerable recovery, why did you use the gscript method?
Just curious, it's the same thing really.
But with openrecovery available you would have more options for trying to get it going again.
zeppelinrox said:
heh.. thanks
So if you had openrecovery going with vulnerable recovery, why did you use the gscript method?
Just curious, it's the same thing really.
But with openrecovery available you would have more options for trying to get it going again.
Click to expand...
Click to collapse
I tried that actually, but the overclocks didn't work, and neither did the bulletproof launcher. They worked on custom roms, but not stock.
I see.
In aor's froyo menu there is the enable autostarts which does the exact same as this gscript since I merely copied it lol.
The only advantage of the gscript is that you don't need vr patched and no aor.
Of course both would then allow the overclocking and other stuff on stock roms.
Sent from my Milestone using Tapatalk
First thanks to kamma and his thread HERE. This fixed was 100% inspired by his attempt, i only had the benefit of having access to some files he didnt. This thread is based off his, but with the files from 2.3.3 which did not have the jumping issue.
I have NOT tested extensively, but in my limited experience(and that of a few others) this does fix the problem.
Code:
[color=#FF0000]USE THIS SCRIPT AT YOUR OWN RISK[/color]
This is just a proof-of-concept fix. I dont guarantee any improvement, because i have not much time to test it.
I simply replace battery libs and apps extracted from [color=#FF0000]ATT 2.2.3*[/color].
How to:
1. Download [color=#FF0000]CMW_Jug6_batfix.zip*[/color] (bellow in Attached Files)
2. Copy it to sdcard or sdcard-ext
3. Reboot into CWM recovery
5. Click "install zip from sdcard"
6. Choose zip from sdcard
7. Pick the [color=#FF0000]CMW_Jug6_batfix.zip*[/color]
8. Install
9. Reboot
V2 - Removed BatteryManager.apk & BatteryReport.apk as they are not needed
Gonna flash this now and reboot frenzy!
Brilliant, will try immediately! Does it matter if you switch between roms, do you have to re-apply then?
Will test, thanks Jug.
Guess I would need to deodex it for a deodexrom?
Vangelis13 said:
Brilliant, will try immediately! Does it matter if you switch between roms, do you have to re-apply then?
Click to expand...
Click to collapse
Yes as you go between roms you would need to reapply, that is until(if its working 100%) its added to the roms themeselves.
Ronaldo_9 said:
Will test, thanks Jug.
Guess I would need to deodex it for a deodexrom?
Click to expand...
Click to collapse
it has both, but if you want u can remove the 2 .odex files from the zip.
Its not as easy as just removing the odex files.... lol... it has to be actually "deodexed" there is a difference. I will do this if you don't know how...
jug6ernaut said:
Yes as you go between roms you would need to reapply, that is until(if its working 100%) its added to the roms themeselves.
it has both, but if you want u can remove the 2 .odex files from the zip.
Click to expand...
Click to collapse
Sent from my Cyanbreaded Gingered Atrix!
installing now....will report tomorow
sublimejosh2000 said:
Its not as easy as just removing the odex files.... lol... it has to be actually "deodexed" there is a difference. I will do this if you don't know how...
Sent from my Cyanbreaded Gingered Atrix!
Click to expand...
Click to collapse
I recommend this.
Sent from my MB860 using XDA App
Installed at 85% battery life, was thinking it was actually closer to 95% at the time I ran this as I hadn't done much since it was fully charged. Didn't wipe battery stats or anything, it started back up at 84%. Did a few things to see how quickly it would drop, when it came down to 81%, I rebooted and wiped battery stats and davlk cache. Took a while on reboot after those wipes, started up at 80%. Still think it should have been higher than the 85% it started at, so I'm charging up to 100% and running Battery Calibration app. Will edit this post when I get the results, but it's not bouncing around like it was before. Awesome work Jug6!
Edit: Charged it to full charge, wouldn't charge past 98%, so I ran the battery calibration app, restarted, and on restart is said 99% and full charged. It was recommended in the app to fully discharge battery and then fully recharge without interruption. Will try to drain it quickly -> Pandora!
sublimejosh2000 said:
Its not as easy as just removing the odex files.... lol... it has to be actually "deodexed" there is a difference. I will do this if you don't know how...
Sent from my Cyanbreaded Gingered Atrix!
Click to expand...
Click to collapse
I would appreciate it, I won't b able to until around 4cst. Granted I'm running this on an deobexed rom.
/me admits his knowledge of compatibility between deobexed/obexed is very lacking lol
Sent from my MB860 using Tapatalk
Will try it out if enough people give good feedback, lol.
Deodexing... From what I understand so far
jug6ernaut said:
I would appreciate it, I won't b able to until around 4cst. Granted I'm running this on an deobexed rom.
/me admits his knowledge of compatibility between deobexed/obexed is very lacking lol
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
I think I would need some of the 2.3.3 framework to do it though..
Basically,
Each .apk has a "classes.dex" file in it.. when a .apk or .jar for that matter has an .odex file associated with it. whish is the case with the Atrix and other phones too... what has happened is that the "Classes.dex" file has been taken out of the .apk/.jar file and placed in a .odex form. this way it is device spacific and cannot be moddified or replaced using generic .apk/.jar files .. i.e. customized ...
he reason it is "working" for you, is because your phone is the spacific device these files were made for... so it isn't crapping out. At least, i think this is the reason...
In order to run a deodex on these file though, I would need some of the reference files that they are dependant on in order to run the script to do so. hat is the "Boot class file paths" that you see below...
I am glad to see these are seeming to fix the problem though. I will see what I can do, but I am getting errors running the script:
Code:
D:\Atrix\Baksmali>java -jar baksmali-1.2.6.jar -x Ba
Error occured while loading boot class path files. A
org.jf.dexlib.Util.ExceptionWithContext: Cannot loca
.odex
at org.jf.dexlib.Code.Analysis.ClassPath.loa
a:237)
at org.jf.dexlib.Code.Analysis.ClassPath.ini
5)
at org.jf.dexlib.Code.Analysis.ClassPath.Ini
ssPath.java:110)
at org.jf.baksmali.baksmali.disassembleDexFi
at org.jf.baksmali.main.main(main.java:278)
ok tried this out on kens gb rom, started at 96, played a game got it down to 93, rebooted into cwm, wiped dav and batt stats, rebooted, was still at 93. so im letting it get down to 85 or so and see if it keeps. this may be the fix for this. i thank you so much for it working this good jug, and hope it is implemented soon.
i just have one thing to say to jug::
: " ooooh ITS THE JUGGANAUT *****"
i have cherry 0.5b, i go in recovery with 83%, i flash this zip, no wipecache no wipe stats no wipe and when i reboot i have 83%, it's work well, and it work with deodex
I just did the following
- Phone was at 70%, restarted
- Phone then read 90%
- Installed this
- Phone still reads 90%, I will restart at lunch time in a few hours to see if it jumps at all
I am running Kenneth's stock 2.3.4 ROM
Thanks!
ok phone at 87, rebooting.....
edit: phone still at 87, YAY!!!!!!!!
Was at 73 before and after reboot, seems to be fixed so far...
Did the following:
-phone was showing 96% (about 3 hours ago)
-installed this (didn't wipe dalvik cache or battery stats)
-restarted and was showing 96%
-been using the phone for the last Hour
-phone showed 76%
-restarted
-phone is still showing 76%
Great finally with have a working solution
PS:why should I wipe dalvik cache?
Enviado desde mi MB860 usando XDA Premium App
Thanks just flashed this. Battery reads the same after reboot. Hopefully it will keep on working.
Sent from my Motorola Atrix 4g
This seems to be working for me. Battery level persisted through multiple reboots. Flashed over Ken's 4.5 beta.
I returned to stock rom. I dont have xrecovery anymore. Only rooted. I found theres this file that is being deleted but I cant find the thread anymore. When I charge my phone after an hour it says 100% when I remove it after a minute it switch to 89% instantly meaning the charge is not yet full. I need to wipe battery stats without using xrecovery stats. I really forget the exact file name and location to delete. what is it?
delete batterystats.bin on /data/system
to wipe battery stats
To calibrate battery
1.charge to 100% full
2.delete batterystats.bin on /data/system
3.leave the battery drain
4.offline charging until full
5.turn on
6.Done,Enjoy
Cheers,
XtremePeople
thanks man!
I am running leaked JVU rom with CF-root kernel for 3 days. Excelent so far, great battery, decent speed, very good modem, wifi and gps, one of the best roms I've used so far.
One thing I really don't like is a stupid text on lockscreen "swipe screen to unlock".
Is there a way of removing this text? I don't want to install a 3party lockscreen app.
Thanks!!
Decompiled the framework-res.apk with ADB and "apk manager". In the values's file => open the script.xml with notepad++ for example. Then change or remove the line corresponding to "swipe screen text on lockscreen". To finished recompiled the all and install your new framework-res.apk
did that! no lucky. get bootloop noobies life is hard...
Can you tell me what do you want to make like sentence in place of "swipe screen to unlock"? Or just remove it?
And join me the framework-res.apk stock because i haven't it because i tried
Thank you lolo77_FR for helping me!
I just want no text.
After compile and sign, how do I flash the modified app to phone? Flash with cwm? copy to system? install?
Here is the original file.
I must to let 10 message :-D
---------- Post added at 11:54 PM ---------- Previous post was at 11:34 PM ----------
Hi, sorry for the answer in late,
I changed your framework-res.apk and I put in a zip.
To install using CWM, I haven't tried it but it should work
I link you a restore if it doesn't work
Say me if it's work.
JVU_Framework_Lolo.zip (6.04 MB)
JVU_Framework_Lolo_RESTORE.zip (6.03 MB)
Any possibility to easy change font or date type for lockscreen? It is really ugly.
great work lolo, works like a charm!
thank you very much.
Happy for you that it worked
it works very good for me, thanks
I just lost the percentage battery. I can survive without it
Guys does it still display that stupid "charging" message once the battery drops below 20%?
Thanks.
Don't drink and tapatalk.
nachos3382 said:
it works very good for me, thanks
I just lost the percentage battery. I can survive without it
Click to expand...
Click to collapse
It's present
Fremen567 said:
Guys does it still display that stupid "charging" message once the battery drops below 20%?
Thanks.
Don't drink and tapatalk.
Click to expand...
Click to collapse
exactly what message because there are many
<string name="lockscreen_plugged_in">Charging (%d%%)</string>
<string name="lockscreen_charged">Charged.</string>
<string name="lockscreen_battery_short">%d%%</string>
<string name="lockscreen_low_battery">Connect your charger.</string>
Click to expand...
Click to collapse
lolo77_FR said:
exactly what message because there are many
Click to expand...
Click to collapse
Once battery drops below 20% there's a message " charging " plus battery % even though it is not plugged in.
So I guess it's the first one.
Thanks
Don't drink and tapatalk.
I think you would rather talk about the third because the first it is when you plug the charger
or the last, when you've no battery and your phone written "connect your charger"
lolo77_FR said:
I think you would rather talk about the third because the first it is when you plug the charger
or the last, when you've no battery and your phone written "connect your charger"
Click to expand...
Click to collapse
Thats the message on the screen without the phone being plugged in. "Charging 17 or whatever %" And this happens when phone goes below 20%.
Sent from my GT-I9000 using Tapatalk
Yes, this is bug somewhere in code when battery drops below 20%, there is message on lockscreen "Charging (xx%)" although charger is not plugged in.
Certain part of code is wrongly calling procedure:
<string name="lockscreen_plugged_in">Charging (%d%%)</string>
when battery drops below 20%.
Right procedure which should be called is:
<string name="lockscreen_low_battery">Connect your charger.</string>
or
<string name="lockscreen_battery_short">%d%%</string>
Call function and its reference should be identified.
Try this and say me if it's that you would
Sorry for my english
@lolo77_FR: please tell me how do you make CWM flashable ZIP from framework-res.apk? Do you just ZIP it or? I tried with 7ZIP but file is not CWM flashable. Maybe some special option should be turned on? Thanks.
Take my zip and open it with winrar. If you just want to change framework-res.apk, drag yours in system/framework/ (winrar is going to replace mine).
Also, if you want to make a different ZIP, you must know the place where put your change and create files like in your phone.
Once finished, open updater script (in META-INF/com/google/android/) with Notepad++ and edit it to remove the files that you replace.
The updater script is the most important in your zip, that's its which going to "say" to your phone what to do.
If you have never done, say me what do you edit and link me your zip that I check.
is there any flashable zip to show percentage on battery icon in stock rom ? i want to know exactly how many power remaining ,please..
sorry for my bad English =.=', thank you so much .:silly:
zenki1 said:
is there any flashable zip to show percentage on battery icon in stock rom ? i want to know exactly how many power remaining ,please..
sorry for my bad English =.=', thank you so much .:silly:
Click to expand...
Click to collapse
with app xposed and the module gravity is very easy!!!!
the gravity app download with xposed
How to install:
First step for everything you do: Create a nandroid backup and make sure you know how to restore it!
I'm not responsible for anything you do with your phone/tablet/rice cooker.
There is also the risk to soft-brick your device. In such a case, see below for ways to recover from it.
Installation of the framework:
Download the Xposed Installer APK and install it
Launch the Xposed Installer, go to the "Framework" section and click on "Install/Update"
Reboot
Done!
after dowload gravity to jb with exposed download... active the module reboot again, open gravity and (status tweaks) you find the battery!!!
you can put the trasparent bar too!!!!! it's great!
here the app : http://dl.xposed.info/latest.apk
you need be root
thank you so much, i am gonna try it
after battery percentage show can i delete the xposed ? i worry about battery draining
zenki1 said:
after battery percentage show can i delete the xposed ? i worry about battery draining
Click to expand...
Click to collapse
No, delete the app, delete the battery percentage.... mmm the battery life of my phone it's very good with xposed and gravity installed.
i have the battery percentage, transparent bar, advance reboot menu.