Develop Bugs

[APP] AudioBoost 2.4 - support and feedback

CREDITS:
My work is ONLY the application, it was intended for my personal use, but I figured that it could be useful to someone else, until supercurio doesn't come out with something better (and I hope he will).
So the HARD PART of the work, like finding out how to tweak the volume limit using alsa, etc. was done by supercurio and we should all thank him a lot for all his work!
Thanks also to RyanZA for creating the z4root application, very very useful!
PREREQUISITES:
1. Your phone must be ROOTED!
ATTENTION FOR FROYO!!:
With froyo official updates, it is NO LONGER possible to flash custom update.zip!! If you want to leave your phone unrooted, however, there is a simple way to achive this:
1. Download from the market the free application "z4root" from our beloved RyanZA! (http://forum.xda-developers.com/showthread.php?t=833953)
2. Use the z4root application to get root privileges
3. Now open audioboost and choose "NORMAL INSTALL"
4. Now or whenever you feel like it, if you want, you can just open z4root again and *unroot* your device. After that, you can even erase z4root and continue using audioboost without problems until next firmware upgrade...the app won't leave any trace and it won't be noticeable that your phone has been rooted.
If you liked this approach, you can also donate to RyanZA for the wonderful app he's created!
INSTALLATION:
If you had previously a beta version installed, please uninstall it before trying the release 1.0.
If you don't have already installed alsa, the app will check your installation when you launch it, and eventually it will ask you to install alsa. Please do so.
FEATURES:
- Headphones, speaker and microphone tweaking!
- I optimized the code a lot, so now it is very low on resource usage, even with a 1-second refresh rate!
- You can leave it in background all day without noticing any lag or anything!
- Now with some sort of icon.
- Signed.
UPDATED 1.1:
- When clicking exit button it will clean up better.
- Cleaned up a bit the Settings activity, and added preview of next feature (statusbar notifications).
- Changed Info activity a bit.
UPDATED 1.2:
- Fixed a bug that prevented the app to work properly!
UPDATED 1.3:
- GLOBAL REFRESH! Now the refresh time and enabling/disabling is under Settings and works for ALL controls (headphones, speaker and mic).
- Fixed (hopefully) problems with ALSA INSTALLATION, plus now a progress dialog is displayed (just for you to know that is working and for me when posting problems - I hope not - you can say "stuck at x%"...)
- Fixed QUIT bug. Now when you click the exit button it should really exit and not show up in background even with task killer. PLEASE DO NOT KILL THE APP, use the exit button!!!
- Now menu has icons!
- Plus a lot of things that you may not notice, but are very useful for overall speed and low system resource impact! The code has been changed A LOT, let me tell ya!
...Well hope everything works just fine! Please post feedback on mic functioning with these new features!
UPDATED 1.4.1:
- Just fixed a little thing which prevented the correct alsa installation, nothing definitive as I'm looking to manage every single possible error scenario...
UPDATED 2.0:
- Works even on unrooted phones
- Alsa installation takes now a split second! You MUST do that even if you used version 1.x (permissions changed...)
- Audio-boosting feature is a service that can be backgrounded
- Statusbar notification
- Start on phone boot
- Refresh rate in milliseconds...you can have values lower than 1 second, default is 500ms...obviously greater values = worst experience = better performance....your call!
- New app logo...hope you like it!
- A lot of other improvements that I'm not remembering right now!
UPDATED 2.1:
- Fixed lagging issues (OMG java Timer class implementation on android sucks badly!!!)
- Dropped "always active" option in settings (not very user-friendly/intuitive)
- Added little dialog when hitting menu/Quit that asks if you want to background the app or close it for good (more user-friendly for my taste)
Regarding *lagging* issues: of course, if you keep like 2-3 milliseconds refresh it WILL lag indeed! That depends on use-cases:
- I, for instance, use my app when listening to music while driving. In that circumstance, I have no problem occupying resources because I'm not actually using my phone apart from playing music. If an email comes in though, I'd *hate* to have to wait 10 seconds to boost volume again, so I keep 100-200ms. When I exit the car, I click "disable" and close audioboost.
- Someone who is listening to music while using the phone intensively should use a higher refresh.
I think that with 2000ms refresh, version 2.1 shouldn't lag even all-day long. Even with lower values it should be fine...you should find your preferred setting by yourselves!
UPDATE 2.2 - 2.3 - 2.4:
- Fixed some bugs.
- Improved froyo compatibility.
- Mounts /system as rw during install.
PLEASE FEEL FREE TO RATE/COMMENT THE APP IN THE MARKET, THANK YOU EVERYBODY
- OLD:
Ok...let's explain a bit. Yesterday evening I wanted to know if it existed a tweak to boost the audio volume coming from the headphones. I think that there is some sort of European law or something like that which limits the volume that headphones can produce. This is probably a good thing to avoid hearing problems with *headphones*, but in my situation it sucks badly! Yes, because I use my phone as a music source in my car, and my car hifi is not powerful enough to let me hear my music at the level I like...
However...I was addressed at this thread, from post #300 on...
Well, I read the thread (and I STRONGLY ADVISE you do the same before downloading anything from my post), but I didn't like very much the limitations of that tweak. It works alright, but it seems to me that an sh script is not the more comfortable way to go on a mobile phone. If you think differently from me, feel free to keep using the script method, without posting useless comments.
So I created a tiny little (horrible I must say) application which kinda does basically the same thing as the script, but in a (from my point of view) much cooler way! It is very ugly, but it's my first android application and I bought the phone just 2 weeks ago...
How does this work? Very simple: there is a textbox in which you can enter the desired amp level, an enable button and a disable one. You should enter the value you prefer (default is 62), then click enable button. You should now leave the app RUNNING in background. When you are finished using the tweak you can tap the disable button to return to the default (of the firmware) settings.
Basically what the application does is it creates a 2-seconds timer which calls everytime the alsamixer (a little better than using an infinite loop as in the script...) with the desired settings. It doesn't seem to impact the battery life too much from my little testing, but please post any feedback on this point.

Thank you! This is useful

what is the default and what are the ranges it supports thanks

The default is 56 (and that's the value it puts when you click the disable button). The range varies from 0 to 63, but from 0 to 35 it's the same low level. It's all written on the supercurio's post I mentioned!

thanks works ok.. you dont have to keep it running the setting does not go back to default unless you unplug and replug in the headphone.. also this is only for headphone boost not for speaker..
finally 2 secs seems like overkill every 10-30 sec would be ok to0.. maybe you could make that user seteable.. also an exit button would be nice since i start it set the level higher and kill it..as long as i dont unplug headphones it stays so i would like to exit without going to task killer..
thanks agian.

lgkahn said:
thanks works ok.. you dont have to keep it running the setting does not go back to default unless you unplug and replug in the headphone.. also this is only for headphone boost not for speaker..
finally 2 secs seems like overkill every 10-30 sec would be ok to0.. maybe you could make that user seteable.. also an exit button would be nice since i start it set the level higher and kill it..as long as i dont unplug headphones it stays so i would like to exit without going to task killer..
thanks agian.
Click to expand...
Click to collapse
I'll look into those suggestions after dinner, thanks! However, I don't see why you should kill it...I mean, it's like 20kb of app...I don't think it occupies that much ram...
The point of the app is that when you unplug the headphone and replug it after 2sec it bumps volume again...if you kill it becomes useless...

carlocb said:
I'll look into those suggestions after dinner, thanks! However, I don't see why you should kill it...I mean, it's like 20kb of app...I don't think it occupies that much ram...
The point of the app is that when you unplug the headphone and replug it after 2sec it bumps volume again...if you kill it becomes useless...
Click to expand...
Click to collapse
it is not the memory footprint i dont like anything running starting up every so often and checking status.. not sure what it does to battery or cpu usage.. especially in not necessary... maybe a widget added to the app with a picture that changes showing boost when on and when you click toggles on or off.. and you only need to open the actuall app for settings..
if you can bundle this with the other app so you dont have to manually install and untar on you card. you could probably charge a couple of bucks for it in the store... but more most people the manual install and untar of the other app is slightly complicated.

lgkahn said:
it is not the memory footprint i dont like anything running starting up every so often and checking status.. not sure what it does to battery or cpu usage.. especially in not necessary... maybe a widget added to the app with a picture that changes showing boost when on and when you click toggles on or off.. and you only need to open the actuall app for settings..
if you can bundle this with the other app so you dont have to manually install and untar on you card. you could probably charge a couple of bucks for it in the store... but more most people the manual install and untar of the other app is slightly complicated.
Click to expand...
Click to collapse
Well that of the widget is a GREAT idea! I'll look into it, but I can't promise anything, because as I said it's the first time I develop anything for a mobile phone, I just read two or three tutorials on android developing this morning and the actual coding part was like a couple of hours of work. Add to that the fact that it's been 4 years since last time I wrote software (let alone java, which was the first language I learned, but I never used it for real developing) and now I'm doing with very different things in my life! Of course I will try to upgrade and make a better app, as this one is horrible...if people are interested I'll do it, but it'll take some time!

carlocb said:
Well that of the widget is a GREAT idea! I'll look into it, but I can't promise anything, because as I said it's the first time I develop anything for a mobile phone, I just read two or three tutorials on android developing this morning and the actual coding part was like a couple of hours of work. Add to that the fact that it's been 4 years since last time I wrote software (let alone java, which was the first language I learned, but I never used it for real developing) and now I'm doing with very different things in my life! Of course I will try to upgrade and make a better app, as this one is horrible...if people are interested I'll do it, but it'll take some time!
Click to expand...
Click to collapse
I'm sure your work will make a lot of people happy.
Thanks for your time Carlo.

Grande Carlo!
Ti consiglierei di salvare il livello di output dell'ultima sessione in modo tale che uno non lo debba reinserire. Ma quanta batteria consuma questa applicazione?
Altro piccolo consiglio: inserisci un terzo pulsante per poter disattivare l'applicazione senza ripristinare a 56 il volume, in modo tale da non dover avere la tua app in background ma poter comunque utilizzare il volume al max
Great idea Carlo!
I'd suggest to modify a few things in your app:
1)Try to insert a third button for closing the service without resetting the volume to the normal one, also because it is enough to unplug the headphones to change it.
2)Can you modify save the latest used volume? This way the next time you open the app you do not have to change it again.
Buona fortuna! Grande idea!

OK...if you look in the first post I updated the app a bit, implementing some of the requests...
It's very important that you uninstall the old one before installing the new one.
It's still early alpha version however, I have in mind a couple of interesting things if I'm able to implement them...
Stay tuned!

2. The refresh rate is in *seconds* and the default is 2. Feel free to experiment with other values, but remember that it's not only the unplugging of headphones cable which causes the volume value to reset. This happens also when you receive a notification (such as an incoming call, message or email), or when there is a 2 seconds or longer pause (such as you just pause the player for a moment). So...imho it's not useful to keep the refresh rate higher then 10 seconds or so...but as always, try various combinations and let me know! The most important thing should be to watch the impact of this setting on battery life...
Also...if you put 0 here as a value, the timer won't start at all. Basically this means that it's just like invoking the shell command...so any notification and the volume won't come back up!
Click to expand...
Click to collapse
strange i didnt experience this in my tests pausing both audible player and ambling book player for more than 2 secs.. the volume didnt reset...
will have to experiement more

ok more info you are correct pausing does setting values back to default..
also one bug.. quite does not seem to totaly quit the app.. it does exist but if you run adavance task killer a process is still showing up as running in the task list.. but anyway i have set it to 10 secs . and it seems to work fine.. no lag while using other apps.

mobile terminal emulator ? allright, couldnt find a tutorial on using adb. can i download a mobile terminal straight to my sgs?

swatsqad said:
mobile terminal emulator ? allright, couldnt find a tutorial on using adb. can i download a mobile terminal straight to my sgs?
Click to expand...
Click to collapse
as long as you have root and busybox you can download the terminal emulator from the market and run the tar command in the first post.
i did it this way on the bus this morning

swatsqad said:
mobile terminal emulator ? allright, couldnt find a tutorial on using adb. can i download a mobile terminal straight to my sgs?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7239659&postcount=3 This is for you!
I like the new version, now maybe you could add a simple image as logo!
Anyway sometimes the app crashes. I think I am unlucky!

help?
$ cd /
cd /
$ busybox tar zxvf /sdcard/alsa-utils-binaries.tar.gz.zip
busybox tar zxvf /sdcard/alsa-utils-binaries.tar.gz.zip
tar: invalid option -- z
BusyBox v1.18.0.git (2010-08-11 01:17:17 CDT) multi-call binary.
Usage: tar -[cxtvO] [-X FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
Options:
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
O Extract to stdout
h Follow symlinks
exclude File to exclude
X File with names to exclude
T File with names to include

Yes some busybox versions don't have tar with gzip support. If u installed the busy box fix from titanium backup u can just run the command thru tar instead.
Sent from my GT-I9000 using XDA App

I dont get it ;/ ..
. So what do i do? OAllready spent 4+hrs on this

Download Busybox by Stericson from the market and that app will let you install the latest Busybox - then that command will work.
cheers
swatsqad said:
I dont get it ;/ ..
. So what do i do? OAllready spent 4+hrs on this
Click to expand...
Click to collapse

I think the reason why the battery drains so fast is the radio!

My home is out of power last night, and I still need the phone to wake me up in the morning. so I turned my phone into flight mode, and it just consumed 2% for 8 hours. For that reason, I personally think the battery performance could be improved significantly in the future when the radio's problem is solved.
Sent from my HTC One X using xda app-developers app

You don't say...

RohinZaraki said:
You don't say...
Click to expand...
Click to collapse
He did !

You my friend have struck gold I can't believe all the devs here didn't figure that one out.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enviado desde mi XT912

Ingenious!:good:

You are a genius my friend! Now we know :what:
Sent from my HTC One X using Tapatalk 2

sxrsxrsx said:
My home is out of power last night, and I still need the phone to wake me up in the morning. so I turned my phone into flight mode, and it just consumed 2% for 8 hours. For that reason, I personally think the battery performance could be improved significantly in the future when the radio's problem is solved.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
What radio problem?
Sent from my HTC One X using xda app-developers app

sxrsxrsx said:
My home is out of power last night, and I still need the phone to wake me up in the morning. so I turned my phone into flight mode, and it just consumed 2% for 8 hours. For that reason, I personally think the battery performance could be improved significantly in the future when the radio's problem is solved.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Wow, man, your battery drain is really bad. I loose 3% in 8 hours with radio on. Theoretically, your drain on flight mode should be like 1% in 30 hours, if the phone goes properly to sleep
Sent from my HTC One X using xda app-developers app

i‘ll hava a notice，thx

My phone would consume a lot of power, I never tested it, but definitely over10% with doing nothing in one night. Sorry to bother you guys:banghead:
Sent from my HTC One X using xda app-developers app

I had a 4.5 day life in ARHD 9.7(ics) with wifi off, radio on.
Now with the same usage on ARHD 16(JB) the maximum im getting is 20+/-2 hours
On the bright side, the phone rarely goes above 35 deg (battery 30) on browsing/moderate usage, as compared to 45/35 in ICS

You should patent that idea. You're one successful man now. Enjoy.
You Live To Die.

Are you sure nobody else touches your phone while you sleep?
sxrsxrsx said:
My phone would consume a lot of power, I never tested it, but definitely over10% with doing nothing in one night. Sorry to bother you guys:banghead:
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse

Some replies here were meaningless and shouldn't have replied in the first place, so trash them my friend.
It is nice that we have people here, whom are trying to contribute to the community. It doesn't matter whether your contribution is significant or not, at least you have done your part.
Back to the topic, your battery shouldn't drop this fast, my best guess is that there is an app that mess up with your phone's "deep sleeping", so in this way, you had many wake ups and therefore bad battery. Find that app, uninstall it and enjoy your phone with a better battery consumption.

neuTrue said:
Some replies here were meaningless and shouldn't have replied in the first place, so trash them my friend.
It is nice that we have people here, whom are trying to contribute to the community. It doesn't matter whether your contribution is significant or not, at least you have done your part.
Back to the topic, your battery shouldn't drop this fast, my best guess is that there is an app that mess up with your phone's "deep sleeping", so in this way, you had many wake ups and therefore bad battery. Find that app, uninstall it and enjoy your phone with a better battery consumption.
Click to expand...
Click to collapse
I think it's bit that kind of problem, or it will kills my battery any way no matter I turn off the radio or not. Maybe it's the problem of the stock rom.
Sent from my HTC One X using xda app-developers app

sxrsxrsx said:
I think it's bit that kind of problem, or it will kills my battery any way no matter I turn off the radio or not. Maybe it's the problem of the stock rom.
Click to expand...
Click to collapse
I have stock and my battery doesn't drop as fast as yours.
Give this a try: https://play.google.com/store/apps/details?id=com.rootuninstaller.bstats (I didn't try it, but it suppose to show you which app is draining your battery ,and it's the easy way).
The old way is using TaskManager, seeing which service is running and analyzing logcat. After that, you just uninstall they faulty app and enjoying your phone as you should.
Here are two quotes of mine (You don't need to follow them, but just so you get the idea):
neuTrue said:
@Iceax123:
First thing first,
Uninstall GSAM,Better Battery Stats, and any other battery stats you might have installed. Also, the app/widget that shows the battery percentage uninstall it as well.
This mean we are now going to depend on, the build in battery stats for reading the battery percentage & depending on it here.
Now, uninstall Juice Defender and Ebay app. You can always reinstall them if you didn't get any improvement. This part is an optional, but I'll recommend you to consider it as we are trying to troubleshooting the faulty app.
Wait until your bedtime, or when you are not going to use your phone.
-Switch off your phone.
-Plug it to the wall charger.
When you wake up, and your phone suppose to have fully charged (indicated by the green LED).
-Turn your phone on (with charger still plugged in)
When your phone is fully booted and turned on
-Replug your wall charger and wait till it's fully charged.
After you do these, use your phone normally like you always do.
When you your battery gets down till (5% or less), I want you to do the following (I Prefer if it in the following orders):
Take a "logcat" of your phone and upload it here.
Start Task Manger (already comes with Sense). Take screenshot of whatever you see there, (the whole list of apps, if there is an app down, scroll down and take a screenshot of it as well).
Go to Settings -> Apps -> Running. Take screenshot of whatever you see there, (the whole list of apps, if there is an app down, scroll down and take a screenshot of it as well).
Provide a full battery stats screenshots (every single thing you find there, take a screenshot of it).
Tell me, what your normal battery stats compared to recent ones.
Finally,
I remind you that I don't guarantee anything to you, also we aren't trying to apply any battery saving techniques here. Only, troubleshooting the faulty app that you think it is causing your deep sleeping issue. So, this mean, we are not going to mess with your sync or anything like this.
Beside that, you could always go with the easy way, and format/reset your phone and start all over.
Good luck.
Click to expand...
Click to collapse
and this one
neuTrue said:
That guy didn't have his wifi/internet on all the time. Also, he is using his phone more efficiently. Which I mean that he doesn't turn on, things he doesn't need or use.
I can easily achieve 4+ hours screen time ,and so you could too.
Here are couple of guide lines you can follow:
1- Switch to 2g only.
2- Turn off NFC.
3- Don't use auto-brightness and keep your brightness low (I'v set a widget with following settings: 0,auto,20).
4- Disable all application you don't need (Facebook, Twitter, EA Games app,...)
5- Reduce sync interval (or better you do it manually).
6- In temperature widget remove all the cities you don't need or care about (one is more than enough!).
7- Repeat step 6 for clock as well.
8- Don't use applications that consume too much CPU power.
-a: Replace your browser and use Opera mini for reading.
-b: As rule of thump if your phone gets hot/warm in certain app then you are wasting your battery on that app.
9-Turn off anything that vibrate: Touching capacitive keys, keyboard,etc...
10- repeat step 9 on sound.
11- Use your wifi only when you need it.
12- Disable your GPS, unless you are using it.
13- Turn of the setting which flips your phone screen (uses accelerometer).
These are currently what I remember that I applied on my phone.
I can tell you my last run, was 3 hours and approximately 15 minutes of screen time while having my phone running for 17 hours. Most of battery wasted on an online game called "Indestructible" (1hour and 20 mins).
I hope you get similar results as well.
Good Luck
Click to expand...
Click to collapse
There is also one missing post that I couldn't find, which shows all apps that I disabled (disabling unneeded apps would help your battery to last longer).
Anyway, I think that's all info your need.
Good luck

neuTrue said:
I have stock and my battery doesn't drop as fast as yours.
Give this a try: https://play.google.com/store/apps/details?id=com.rootuninstaller.bstats (I didn't try it, but it suppose to show you which app is draining your battery ,and it's the easy way).
The old way is using TaskManager, seeing which service is running and analyzing logcat. After that, you just uninstall they faulty app and enjoying your phone as you should.
Here are two quotes of mine (You don't need to follow them, but just so you get the idea):
and this one
There is also one missing post that I couldn't find, which shows all apps that I disabled (disabling unneeded apps would help your battery to last longer).
Anyway, I think that's all info your need.
Good luck
Click to expand...
Click to collapse
Thank you so much :thumbup::beer:
Sent from my HTC One X using xda app-developers app

[TWEAK][APK][CWM] [update2.0.0] Seeder entropy generator to provide lag reduction

FULL CREDIT TO lambgx02!
Original Post | CWM
Guys check this out
Best result on Android 4.+
Description
Hey everyone,
So, I was experiencing significant lag as we all do from time to time, and decided I was going to get to the bottom of it.
After tracing and debugging for hours, I discovered the source of 90% of Android's lag. In a word, entropy (or lack thereof).
Google's JVM, like Sun's, reads from /dev/random. For all random data. Yes, the /dev/random that uses a very limited entropy pool.
Random data is used for all kinds of stuff.. UUID generation, session keys, SSL.. when we run out of entropy, the process blocks. That manifests itself as lag. The process cannot continue until the kernel generates more high quality random data.
So, I cross-compiled rngd, and used it to feed /dev/urandom into /dev/random at 1 second intervals.
Result? I have never used an Android device this fast.
It is literally five times faster in many cases. Chrome, maps, and other heavy applications load in about 1/2 a second, and map tiles populate as fast as I can scroll. Task switching is instantaneous. You know how sometimes when you hit the home button, it takes 5-10 seconds for the home screen to repopulate? Yeah. Blocking on read of /dev/random. Problem solved. But don't take my word for it .. give it a shot!
Update!
I've built a very simple Android app that bundles the binary, and starts/stops the service (on boot if selected). I'll be adding more instrumentation, but for now, give it a shot! This APK does not modify /system in any way, so should be perfectly safe.
This is my first userspace Android app, so bear with me!
Note that this APK is actually compatible with all Android versions, and all (armel) devices. It's not at all specific to the Captivate Glide.
Click to expand...
Click to collapse
Quote Original Post link - Click Here
Requirements
An Android device! No iPhone's allowed!
Need Root
[Optional]-Root File manager
Ryuinferno said:
Before doing anything, please read the first post of this thread to understand how this thing functions!
Read it here: First post
First things first I am not the OP but things need to be sorted out...Ok...this thread is starting to get more and more attention, which is good because with more people to test things out, the more feedbacks and the more improvements can be done...however, the thread is now cluttered by tons on unhelpful posts, like "how to use this", "do I need root" etc...useful posts get pushed wayyy behind, until it is hard for people who are really trying to discuss to keep track...so I am here to answer the basic questions:
Do you need root for the app?:
Yes
Can it work on xxx device?:
Yes, as long as your device is arm based
Where to download the app?:
Here: http://forum.xda-developers.com/attachment.php?attachmentid=1640660&d=1358063993
Or search Play Store for a donate version...
The other 2 attachments are the rngd binary and a diff patch, which are not really required for end users...
How do I know that it is working?
Prior to starting seeder entropy generator through the app (v1.2.4 onwards), the bar below will only show numbers around 100-200++. After you start it, if the bar fills up and the value shoots up to 4000++, then it is working.
Do I have a risk of bricking my device?
No because the app won't modify system files at all...anything just uninstall...
For the zip, it only adds files to your system partition...does not modify any, so if you want to stop using this, you can disable it via the extended menu script...
It does not do anything/It is placebo/I see no improvements/It is awesome!/Wow!:
Well, this is not constructive or helpful...NOT AT ALL...keep in mind that this is still a WIP...research and discussions are still going on...if it is not working or you feel no change or a great improvement, please describe more and explain...which a lot of others are already doing so......keep it up!
Seems that certain people are so bugged by the app...so...for those who prefer to run this via a script and init.d, read on...(the script works the same as the app, but with a few extra features)
=======================================================================================================================
UPDATE: Seeder_v7 is out, as suggested by pepoluan, it now detects for qrngd (built in rngd for Qualcomm Snapdragon-based devices), if it is there, then it will not start as rngd may conflict with it...the rngd binary is also using the latest version (it is turned off when screen is off)...users of previous versions can just flash it over...
INSTALLING
You need init.d support for this!
Download and flash:
http://www.androidfilehost.com/?fid=9390248398092764755
How to use this script?:
After flashing, launch terminal emulator and type
Code:
su
seeder
You will get a menu like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: There will be NO app after flashing! This only installs the necessary binaries and scripts...
For those who cannot install via recovery:
You get a status 0 error -> replace the update-binary in Seeder_v6.zip with one from another zip that works with your device
OR
Use the new installation method!
Instructions:
1. Download Seeder_v7_non-CWM.zip from here:
http://www.androidfilehost.com/?fid=9390248398092764756
2. Extract the zip, you will get a folder named "install"
3. Place the folder in the root of your sdcard (/sdcard)
4. Launch terminal emulator, type:
Code:
su
cd /sdcard/install
sh install.sh
5. Ignore any error messages (those are only warnings, only happens to current users)
6. You are done! The script will auto-delete the "install" folder as it is not required anymore...
Sample output:
UNINSTALLING:
And now for the way to clean up Seeder_7:
Via recovery:
Flash Seeder_v6&7_Uninstall.zip:
http://www.androidfilehost.com/?fid=9390248398092764753
Via terminal:
1. Download Seeder_v6&7_Uninstall_non-CWM.zip:
http://www.androidfilehost.com/?fid=9390248398092764145
2. Extract it to the root of your sdcard (/sdcard), you should get a file named uninstall.sh
3. Launch terminal emulator and type this:
Code:
su
cd /sdcard
sh uninstall.sh
4. You are done! Everything gets cleaned up, including uninstall.sh...
Click to expand...
Click to collapse
Updates
There has been a lot of controversy about Seeder/rngd. In newer versions of Dalvik, nothing touches /dev/random, and yet many users (including myself) still notice a lag reduction. There are theories ranging from kernel lock contention to UI polling load when crediting the entropy pool to simply kicking the governor. And many who believe it's all placebo. I'm trying my best to figure out what exactly is happening, and others are as well.
Someone asked how I arrived at the conclusion I did when I started the thread back in November, and I posted this; I think it might be better served here:
A while back one of the webapps I was hosting on Tomcat (server-side) was experiencing some inexplicable latency and while stracing java I saw it frequently hanging on read()'s from /dev/random. I checked the available entropy, and it was constantly under 250 or so. It was a VM, no HWRNG, so I decided to use rngd to push urandom->random.
Dropped session creation times under load from 5-10 seconds to less than a second.
It's worth noting that Linux is one of very few OSes that have a blocking RNG device. Free/OpenBSD, Windows, etc.. essentially only provide urandom. It's generally considered secure, even for long-term crypto keys, so long as the initial seed is big (and random) enough.
Checked on my device, and saw a few processes grabbing /dev/random. /proc/sys/kernel/random/entropy_avail reporting depleted input pool. Figured it was worth a shot, so I rebuilt rngd for arm (with a few patches, linked on first page), and tried it out. It made a significant difference. Posted it up on this thread, and had a lot of positive feedback. Wanted to get into Android development, so figured.. why not wrap a little UI around it. More positive feedback, so I threw it on the market as well.
I had no idea it would take off like this and was shocked when I saw it Thursday morning. I'm in the awkward position now of explaining why it seems to work for some people, and not for others, especially given the fact Dalvik doesn't have references to /dev/random as of ICS. Theories abound, but it looks like it might be an issue of polling the UI for input events when the entropy pool drops (which never happens so long as rngd is running).
I'm doing this as a hobby. I'm a *nix admin by trade, and can only spend time working on this stuff on evenings and weekends, and the last few weeks have been kinda nuts.
I want to stress to everyone that:
a) It doesn't work the way I thought it did on later Android builds, but it does reduce latency for me and many others even on these builds,
b) I'm offering (and always will offer) Seeder for free to everyone on XDA,
c) Like I say in the market description, if anyone has purchased it and it isn't working, PLEASE email me for a refund (and let me know what device you're on if you're willing).
I was one of the first to root the Captivate glide (my first Android phone), and submitted the A2DP bitpool patch; I was active in the n900 community. I hope everyone understands that I'm doing my best here!
I hope the technique proves useful to people, and if there is in fact contention at the kernel level, I hope it's solved so we all benefit.
Version 2.0.0 attached. No changes.
Version 2.0.0b1 attached. New performance profile selector, I/O queue extender, and power saving control. Improved root checking.
Version 1.4.0 attached. Major refactoring. Service control now fully asynchronous.
Version 1.3.1 attached. No changes from 1.3.1-beta.
Version 1.3.1-beta released. New root check method during ANR-sensitive code.
Version 1.3.0 attached. Proper IntentServices for process control, and notification on upgrade / loss of root / autostart failure.
Version 1.2.9 attached. Yet another update to the upgrade/autostart code.
Version 1.2.8 attached. Asynchronous startup of rngd during boot; this should solve the remaining autostart problems some users have reported.
Version 1.2.7 released. This version introduces a much more efficient suspend-on-sleep mode for rngd.
Version 1.2.6 released. This version reverts the suspend-on-sleep rngd change which may have been contributing to new latency. I'm sorting out a better way of implementing it.
Version 1.2.5 released. This version should fix the autostart failure some users have seen.
Version 1.2.4 released. This version implements a progress bar displaying your currently available entropy, as well as automatic rngd restart on upgrade.
Version 1.2 released. This version implements rngd suspend-on-sleep, and contains minor user interface updates, more robust process and superuser checks, and a new icon (thanks Nathanel!)
Version 1.1 released. This version uses the release signature, so you will need to uninstall the old XDA version first!
Download and flash this if you dont know what to download xD Click here!

if this really works... wow
then it should be included in all custom ROMs from now on and a patch merged into AOSP

Holy crap dude! Using it now on my Gnex. Gunna give a few to see if it really does increase performance. As far as I can tell since installation scrolling in tapatalk has increased tenfold.
Sent from my Galaxy Nexus

Holy crap! Gonna try this now!
EDIT: I've got TWRP, will the CWM zip work in it?

Larry94 said:
Holy crap! Gonna try this now!
EDIT: I've got TWRP, will the CWM zip work in it?
Click to expand...
Click to collapse
I've not tried on TWRP but should work! Flash it! This works on any device also
Sent from my Nexus 7 using xda premium

bradman117 said:
I've not tried on TWRP but should work! Flash it! This works on any device also
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hmm, only files I have in xbin after flashing is bttest, dexdump, and su. :/

Larry94 said:
Hmm, only files I have in xbin after flashing is bttest, dexdump, and su. :/
Click to expand...
Click to collapse
U need to do it manually then with root explorer. Look at bottom of my post. Or try redownload and flash
Sent from my Nexus 7 using xda premium

I just use the app... It seems to work just fine
Sent from my Galaxy Nexus

ÜBER™ said:
I just use the app... It seems to work just fine
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I got tired of turning it on every reboot that's why I used flash.
Sent from my Nexus 7 using xda premium

Just unzip flash and download other file I put up under were I put were the files go. Place and fix the files permission
Sent from my Nexus 7 using xda premium

bradman117 said:
I got tired of turning it on every reboot that's why I used flash.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
It has a set on boot option.
Sent from my Nexus 7

bradman117 said:
I got tired of turning it on every reboot that's why I used flash.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Would you mind doing me a quick favor? The permissions look a little different in ES File explorer. Would you install it, navigate to the different files, long press, properties, and select permissions and grab a screen shot?

I don't feel any improvements on my Nexus7, someone yes¿
Br.

Seems to work for me. Modern Combat 4 used to lag before, flashed this and played a match with no lag. You have my thanks
Sent from my ParanoidAndroid/franco.Kernel powered Nexus 7 with XDA Premium

Nothing for me either and everytime I go into the app it shows it as off.

I flashed the CWM version because the app wouldn't stay on or switch on at boot. Haven't really noticed any difference yet, because I don't have any game that lags, including vice city on max settings, and I'm not over clocking yet either.
If MC4 has the occasional stutter then I'll try installing that and see.
Edit: forgot to mention, I also put it on my galaxy s1, and I can tell you that I do notice a definite difference on that.
Sent from my Nexus 7 using Tapatalk HD

I think I need a kernel with init.d support right?
Don't work on stock...
\\\... send with the Nexus 7 3G ...///

IAmNice said:
Above check set on boot
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
I did. It didn't work for me.
Sent from my Nexus 7 using Tapatalk HD

DominatingSystem said:
I think I need a kernel with init.d support right?
Don't work on stock...
\\\... send with the Nexus 7 3G ...///
Click to expand...
Click to collapse
ya u need custom kernel that supports init.d.

knuckles1978 said:
I did. It didn't work for me.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thats why i put files on manually. set on boot didn't work for me
----EDIT---
Updated post, added downloads if you want to do it manually

[GUIDE][CM] Get The Most Out of Your Battery

This is my all inclusive guide on how to get the most out of your battery without sacrificing functionality. Specially tailored for the i747.
WARNING: I ASSUME NO RESPONSIBILITY FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
!!!NANDROID BACKUP!!!​
This guide assumes that you're running Cyanogenmod 11 or a custom ROM based on it. It is organized from most practical and user friendly, to more technical and intensive.
The first manner of business is to upload to the latest bootloader/modem, which can be found here: http://invisiblek.org/d2firmware.html
This provides the most stability/support for the latest CM Nightlies.
Simply download the .zip and flash it in your recovery of choice.
Go into "Settings" > "Apps" and delete any apps you don't use anymore.
Go into all apps you DO use, and make sure "Location" and "Notification" settings are either OFF or on according to if you need them or not.
Disable "syncing" in weather apps, news apps, and any other apps that have background syncing enabled.
Disable "WiFi" when not in use.
Disable "Data" when not in use.
Disable "Location" when not in use. (THIS INCLUDES LOCATION REPORTING.)
Disable "Bluetooth" when not in use.
Disable "NFC" when not in use.
Disable "Automatic Backlight"
Manually set brightness to lowest setting.
Set Screen Timeout to 1 minute or less.
Disable "Sync" when not necessary.
Disable "Auto Rotation" when not necessary.
Disable all haptic/sound feedback under "Sound."
Go into "WiFi" settings, press your menu key, and press "Advanced." Be sure that "Scanning always available" is unchecked.
CHARGE YOUR PHONE WHENEVER POSSIBLE.
Download "Greenify" from the Play Store, open it up, and start hibernating every app you don't depend on. DO NOT HIBERNATE MESSAGING APPS.
I personally hibernated every non-system app I had excluding "Google Keyboard."
You have a special feature called "App Ops under your "Privacy" settings.
Press "Privacy Guard." You'll be presented with a list of apps. These apps can be "secured" with a click. Simply press and app you don't want accessing your location settings, and the little grey lock to the right of the app will become white. This will disable the app from using location services.
Third, open up your apps list under Settings > Apps > "All" tab. Cyanogenmod has many apps that the typical user doesn't want/need, and that take up precious RAM and CPU cycles.
You can disable system apps by clicking on them, and then "Disable."
Apps that can be safely disabled include:
Android Keyboard – REPLACE WITH GOOGLE KEYBOARD
Android Live Wallpapers
Basic Daydreams
Black Hole
Browser – REPLACE WITH CHROME BETA
Bubbles
CM Updater
CM Wallpapers
com.android.wallpaper.holospiral
Downloads
Email – Up to you.
Exchange Services – Safe to disable only if you disable Email
Face Unlock
Gallery – REPLACE WITH QUICKPIC
Google Backup Transport – ONLY IF YOU DON'T USE GOOGLE BACKUP
Google One Time Init
Google Partner Setup
Google Text-to-speech Engine – AT YOUR OWN DISCRETION
Magic Smoke Wallpapers
Market Feedback Agent – DISABLES... MARKET FEEDBACK...
Movie Studio
Music Visualization Wallpapers
Phase Beam
Photo Screensavers
Pico TTS - AT YOUR OWN DISCRETION
Setup Wizard
Tags - ???
Terminal Emulator
Themes provider – STUCK W/ DEFAULT THEME
Voice Dialer
I have disabled all of these apps and had no ill consequence. I haven't gone as far as uninstalling them, but you may if you wish.
Download KT's latest kernel from http://forum.xda-developers.com/showthread.php?t=1756776
Flash in recovery. Be sure to wipe Cache and Dalvik before and after!
WHAT YOU DECIDE TO DO WITH THIS KERNEL IS UP TO YOU. YMMV.
Open KTweaker app.
Set governor to "pegasusq" - This is a more conservative governor, and also allows hotplugging.
Undervolt CPU by 75 mV across the board. - YMMV.
Undervolt GPU by 50 mV across the board. - YMMV.
Set GPU Governor to "simple."
Set "Set options on boot" to set with a 20 second delay. (In case something goes awry.)
Reboot.
ETC. TIPS:
- Get any widgets you don't use off your Launcher. They eat battery too.
- Don't use custom launchers with riced out animations. This tears up your GPU, and your battery life will suffer as a result.
- Turn off "Mock Location" in Developer Options.
- DO NOT USE TASK KILLERS!!!
- Disable "Automatic home clock" in the stock "Clock" app.
- Use ART!
- Turn off roaming!
I'm sure I'm forgetting something. I'll update this if I remember anything. Let me know if this has helped you at all. Feel free to add any tips as you see fit.
Give me a thanks if I've helped you out!

Pretty good if I say so myself.
Never disabled LTE.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Reserved.

how to get the most out of your battery without sacrificing functionality
Click to expand...
Click to collapse
But the tips are all about disabling services?
I kid, this is a pretty neat start for people experiencing battery issues. I generally recommend also getting a new battery - the Ankers 2200mAh one is legit.

xFallacy said:
But the tips are all about disabling services?
I kid, this is a pretty neat start for people experiencing battery issues. I generally recommend also getting a new battery - the Ankers 2200mAh one is legit.
Click to expand...
Click to collapse
Yeeeah. I wrote the title before I got started haha. They're all optional, of course. Not many people will miss having a random app in their RAM (Greenify solution.) Or disabling location reporting (I hate location reporting.) Or even undervolting, or getting rid of random CRapps.
I did have that Anker battery, but it bloated on me. It was nice while it lasted, though. (About 3 months.)
Sent from my SGH-I747 using Tapatalk

RJantu said:
Yeeeah. I wrote the title before I got started haha. They're all optional, of course. Not many people will miss having a random app in their RAM (Greenify solution.) Or disabling location reporting (I hate location reporting.) Or even undervolting, or getting rid of random CRapps.
I did have that Anker battery, but it bloated on me. It was nice while it lasted, though. (About 3 months.)
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Mine has lasted 6 months so far, strange. I replaced the stock battery after it stopped holding a charge within the first 8 months of ownership.
Also, on the topic of Greenify, when I used to have it, I found it was draining almost as much battery as the things it was hibernating, since it spent every waking moment shutting the other things off. Have you found that to be the case at all?

xFallacy said:
Mine has lasted 6 months so far, strange. I replaced the stock battery after it stopped holding a charge within the first 8 months of ownership.
Also, on the topic of Greenify, when I used to have it, I found it was draining almost as much battery as the things it was hibernating, since it spent every waking moment shutting the other things off. Have you found that to be the case at all?
Click to expand...
Click to collapse
My case may have been user error. It isn't rated to take as quick a charge as the stock battery. I was using a 1A 5V power box. I believe it called for a .7A 5V current.
I have; in the case of my keyboard, and Facebook, as well as Google Play services back when I tried out making it a user app. I got rid of the Facebook app and use the mobile site. It works just as well.
Sent from my SGH-I747 using Tapatalk

RJantu said:
My case may have been user error. It isn't rated to take as quick a charge as the stock battery. I was using a 1A 5V power box. I believe it called for a .7A 5V current.
I have; in the case of my keyboard, and Facebook, as well as Google Play services back when I tried out making it a user app. I got rid of the Facebook app and use the mobile site. It works just as well.
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I don't have FBApp notifications on, ever. I used it mostly for the interface and the seamless photo upload via Wi-Fi.
But since I started using Quantum, the battery has been significantly better. If the Facebook app becomes stupid enough with the battery, however, might just follow your lead there.

xFallacy said:
I don't have FBApp notifications on, ever. I used it mostly for the interface and the seamless photo upload via Wi-Fi.
But since I started using Quantum, the battery has been significantly better. If the Facebook app becomes stupid enough with the battery, however, might just follow your lead there.
Click to expand...
Click to collapse
The problem isn't the notifications, it's the services that the app has that run, even if you have notifications, sync, and background services turned off. I hated it.
I used to use Quantum, back when CM 11 didn't have official nightlies. Great ROM and Dev; not bleeding edge enough for me, though.
Sent from my SGH-I747 using Tapatalk

RJantu said:
The problem isn't the notifications, it's the services that the app has that run, even if you have notifications, sync, and background services turned off. I hated it.
I used to use Quantum, back when CM 11 didn't have official nightlies. Great ROM and Dev; not bleeding edge enough for me, though.
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
That's fair, I just started using it last week, because PA3.99 was crapping out in all kinds of fun ways, and I didn't feel like using SlimKat again. I'm trying out ART now, to see how that affects my battery.

xFallacy said:
That's fair, I just started using it last week, because PA3.99 was crapping out in all kinds of fun ways, and I didn't feel like using SlimKat again. I'm trying out ART now, to see how that affects my battery.
Click to expand...
Click to collapse
It shouldn't be a massive gain, but definitely more fluid and a bit more quick, which let's you get stuff done faster, and the faster you get stuff done, the less time you use the screen, and that takes load off the battery.
Sent from my SGH-I747 using Tapatalk

Apex Launcher doesn't support ART. :crying:

What about Nova?
Sent from my SGH-I747 using Tapatalk

it's a bad idea to suggest charging your phone whenever possible... it'll kill the battery imo
just wait till it's low and charge till it's full

pcshano said:
it's a bad idea to suggest charging your phone whenever possible... it'll kill the battery imo
just wait till it's low and charge till it's full
Click to expand...
Click to collapse
Full cycles like that kill the battery just as fast, if not faster. This is a battery life thread.
Sent from my SGH-I747 using Tapatalk

Sent from my SAMSUNG-SGH-I747 using Tapatalk

RJantu said:
This is my all inclusive guide on how to get the most out of your battery without sacrificing functionality. Specially tailored for the i747.
Click to expand...
Click to collapse
RJantu said:
Disable "WiFi" when not in use.
Disable "Data" when not in use.
Disable "Location" when not in use. (THIS INCLUDES LOCATION REPORTING.)
Disable "Bluetooth" when not in use.
Disable "NFC" when not in use.
Disable "Automatic Backlight"
Manually set brightness to lowest setting.
Set Screen Timeout to 1 minute or less.
Disable "Sync" when not necessary.
Disable "Auto Rotation" when not necessary.
Disable all haptic/sound feedback under "Sound."
Go into "WiFi" settings, press your menu key, and press "Advanced." Be sure that "Scanning always available" is unchecked.
Click to expand...
Click to collapse
So... in other words... sacrifice functionality for battery life. I never understand the point of these threads.

Jaspah said:
So... in other words... sacrifice functionality for battery life. I never understand the point of these threads.
Click to expand...
Click to collapse
Tell me when you're going to use GPS, Bluetooth, and NFC at the same time.
Are you getting directions to McDonalds while you talk to your business client on your Bluetooth headset and paying for your burger with your phone? I didn't think so.
And Sync? Do it manually. What functionality is being lost that can't be toggled in quick settings in half a second? Are you removing any apks, or shutting down any services that wouldn't benefit you again in a couple of clicks?
You're not sacrificing functionality, you're using common sense. Try it sometime.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

RJantu said:
Tell me when you're going to use GPS, Bluetooth, and NFC at the same time.
Are you getting directions to McDonalds while you talk to your business client on your Bluetooth headset and paying for your burger with your phone? I didn't think so.
And Sync? Do it manually. What functionality is being lost that can't be toggled in quick settings in half a second? Are you removing any apks, or shutting down any services that wouldn't benefit you again in a couple of clicks?
You're not sacrificing functionality, you're using common sense. Try it sometime.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I use GPS frequently because I use Google Now for commuting, sports, among other interesting tidbits that come up. I also have a Pebble smartwatch that uses Bluetooth. I have no idea why you bother toggling NFC since its only on when the tag triggers it.
And sync is a critical part of my phone as I work in IT and expect hangouts messages or emails at all times of the day. Both my work, friends, and school use technologies that rely on sync, and some of them are time sensitive.
If you don't want to use the features of a smartphone, use common sense and don't buy one. Sorry I don't find your "turn literally every smartphone feature off" guide useful.
Tell me, what exactly do you use your smartphone for?

Jaspah said:
I use GPS frequently because I use Google Now for commuting, sports, among other interesting tidbits that come up. I also have a Pebble smartwatch that uses Bluetooth. I have no idea why you bother toggling NFC since its only on when the tag triggers it.
And sync is a critical part of my phone as I work in IT and expect hangouts messages or emails at all times of the day. Both my work, friends, and school use technologies that rely on sync, and some of them are time sensitive.
If you don't want to use the features of a smartphone, use common sense and don't buy one. Sorry I don't find your "turn literally every smartphone feature off" guide useful.
Tell me, what exactly do you use your smartphone for?
Click to expand...
Click to collapse
At the moment, I'm using it to reply to you, and that doesn't require many things to be toggled on at all. I use it to find directions when I need it (I'll turn location on when I need it), to text, call, and do some web surfing and email.
You seemed to have failed to read the rest of the OP, as well. Undervolting? Destroying wakelocks? Custom kernels? ART?
Not everyone is as tied to their phone as you are. This is meant for people like me, who seemed to struggle to make a full day's charge and couldn't seem to for some reason.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Making a multi-battery setup on your Mi 9T/K20/Pro, or any other Xiaomi Device

Hello everyone! Some time ago, I watched a video by Geekerwan on making a DIY Gaming Phone and I figured why not try it on my Mi 9T with a swapped K20 Pro motherboard. (More about the motherboard swap here). This could be done with other devices as well but you will have to find specific files that's written for your phone (e.g. AndroidOverlayBattery.apk, which apparently contains some values which might brick your phone if it is flashed on a different model other than Mi 9 or Mi 9T/K20/Pro.
BEFORE EVERYTHING ELSE....​
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by doing these mods.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame me or XDA, or the modules and its respected developers.​
Click to expand...
Click to collapse
PREREQUISITES:
Your phone must be rooted and have TWRP, or any custom recovery of your choice installed.​
Your device must be having a horrible battery life (hence why you're watching this thread xD)​
You have new batteries of the same capacity, voltage, and model ready to install.​
You should have a little background knowledge on how electronics, currents and voltages work.​
Some wires, soldering iron, glue/tape, and a bit of patience.​
A working Windows PC (for modifying the .zip and apk later on)​
HOW IT'S DONE ON THE HARDWARE SIDE:
Spoiler: How to do it on the hardware side
You first need to open up your phone, disconnect the battery, and expose the battery protection board.
Get your extra batteries ready. You will have to remove them from their protection boards very gently, otherwise, you could rip the contacts off.
Male sure the batteries you will use should have the same voltage as with the battery currently installed on your phone. Use a multimeter to check for voltage (the difference should not be any larger than 0.2V). Otherwise, you will get some lovely sparks when you connect them together.
Find a way to connect the extra batteries in parallel to the protection board of your original battery. (You can solder them directly with wire, but I would not recommend that since Li-ion batteries doesn't like heat, and one of mine just swollen up when soldered directly on the battery contacts).
You can experiment with different ways to connect the external batteries to the BMS. I finally nailed mine by spot-welding a Nickel strip on the battery terminal and using superglue to glue the rest of the nickel plate on my battery wrapping (so it wont easily rip off the flimsy battery terminal when moved or jolted around).
When working with bare battery cells, always make sure that you properly insulate and do not short out the positive and negative contacts!!!
I used a mix of regular soldering tin and a generous amount of 138°C solder paste to be able to solder the wire to the nickel strip without damaging the battery with heat.
Check the voltage from the battery FPC connector to see if you have done the connections correctly.
Secure the battery to the phone frame. and connect it to the motherboard. Do note that you will not have a usable back cover anymore.
NOW ON THE SOFTWARE SIDE:
Spoiler: How to do it on the software side
First thing that I encountered with doing this project is how to get the batteries recognized by the BMS as one huge battery. Since Geekerwan didn't go into too much detail about modifying the BMS files, I tried to google around. Luckily, dbpm1 from another thread (Mi 9 beats against Mi 12 Pro in 2022 after stunning modification, #4) gave me a link to IncreasedBatteryCapacity which was a Magisk module that changes the Kernel and Power Profiles to display and recognize the larger batteries correctly. This has options for 4000mAh and 4200mAh batteries.
To adapt this for larger batteries (like mine which had two 4000mAh cells connected in parallel), you need to change some values. You have to change all the capacity values in the service.sh file contained in the .zip archive according to the capacity of your battery setup. You will also need to modify the customize.sh file under the lines:
if [ $DEVICE = cepheus ]; then
echo " - Device is cepheus"
according to your xiaomi device codename to be able to execute this zip on your other xiaomi device since the zip is originally written for cepheus (Mi 9).
Next, you will need to extract the AndroidOverlayBattery.apk from the .zip at system\folder\overlay\AndroidOverlayBattery using WinRAR or 7Zip. After extracting the apk, You will need to decompile the apk to be able to edit the power_profile.xml to your desired battery capacity (this is so that your phone will also report the correct battery percentage). If you skip this step, the power profile value when checked with Device Info HW under "Battery" will not be the same with the kernel profile, and your phone will only charge to the capacity set in power_profile.xml. In my case, I used the 4000mAh version, and so, whilst I changed the service.sh value, the power profile value remained the same. My phone in turn charged to 4000mAh only (reporting 100%), and my phone ate through my batteries as if there was no second battery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In order to decompile and recompile, you will need to have Java Runtime Environment (Java 8+) on your PC. Follow this guide to decompile the AndroidOverlayBattery.apk once extracted. Refer to Apktool - How to Install for installation of apktool. After extracting and decompiling, find the power_profile.xml which will be located at the folder created by apktool \*YourIBCZipName*\res\xml\power_profile.xml. (*YourIBCZipName* is what I used in case you renamed the IBC zip file to whatever else. In my case, I renamed it to IBC-8000-Modified.zip). You can use Notepad to search for the line:
<item name="battery.capacity">4000</item>
Then replace it with your desired capacity, and do not modify anything else, unless you really know what you're doing. After modifying power_profile.xml, You will need to recompile the apk. But first, you have to move an important folder. On the folder created by apktool (\*YourIBCZipName*\) when you decompiled, you will see another folder named "original". Open it and take the META-INF folder and move it to \*YourIBCZipName*\ folder. After that, recompile the apk from this same guide I mentioned above.
After that, you will still need to sign the apk in order to be successfully used on your phone when flashed. Not doing so will result in a bootloop and you will need to open the \data\adb\modules\ folder in TWRP or any recovery of your choice and delete the module folder later on to get your device working again. You will need to download this .jar file and place it on the same folder with apktool in order to sign the apk properly. Instructions on how to sign the apk is provided in the GitHub link of the apk signer, but basically, after you recompiled the apk, take it out from the folder where it was decompiled at (In my case it was on "AndroidOverlayBattery8000\dist\AndroidOverlayBattery8000.apk") and place it on the root directory of apktool. Then input on the cmd prompt/windows powershell/terminal the command
java -jar uber-apk-signer.jar --apks /*name of the apk you just recompiled*/
It should also show you that the apk has been properly signed and verified. Once the app is signed correctly, just rename it to "AndroidOverlayBattery.apk" and then put it back in the IBC zip, replacing the original AndroidOverlayBattery.apk, then flash in Magisk and reboot.
Here's when it's done:
If you feel like needing to make sure the battery capacity is properly reported, turn off your phone and long press Power and Volume Down buttons for about 1 minute while it is constantly rebooting in and out of fastboot mode, then let it boot to system. When done, you'l basically be able to game on your phone longer, and....err...charge a little bit longer. If you like to make a more extreme modification, you can even give the active cooling mod a try. You'll only need to find a way to mount the heatsink, connect the fan, get some decent airflow, and build a case to protect the phone.
Here's my end result (in case this gets confused for another clickbait mod without modifying the hardware itself). Modified with active cooling as well, fan control still due to be added since I killed my original one trying to adapt it to my required application.
BIG THANKS TO THE FOLLOWING: (XDA Forums and Github nicknames)
dbpm1 - really big help linking IncreasedBatteryCapacity
PycmShoma - developer of IncreasedBatteryCapacity
ryanamaral - guide for decompiling and recompiling apks
patrickfav - developer of uber-apk-signer for signing compiled apk

This isn't really a guide...

DevSquad69 said:
This isn't really a guide...
Click to expand...
Click to collapse
Basically this is what you should do if you wanted to modify your Davinci, Raphael, or Cepheus to have more batteries, or if you decided to use larger capacity batteries (if there's any you could find). See the spoilers if you're interested.
That's my raphael, modified with active cooling and an extra battery for longevity, with a 3rd battery due to arrive soon. The black and yellow wires are there for the fan controller which I am still due to replace after I broke the fan controller board trying to make it output 8V since 5v for my tiny fan is too slow to keep my phone cool under sustained heavy loads. (Yes, I overclocked my gpu to 835MHz, and disabled the thermal engine)

friend I have tried to follow your steps but I do not have the same result, I really do not have much knowledge and I have stayed in the part where you download the zip and I do not understand very well how to sign the app

What rom are you using? Cant find the overlay.apk inside my system
Nevermind, found the overlay, now my phone shows 4400mah.

Heracle1697 said:
friend I have tried to follow your steps but I do not have the same result, I really do not have much knowledge and I have stayed in the part where you download the zip and I do not understand very well how to sign the app
Click to expand...
Click to collapse
Instruction for using the uber-apk-signer is in its download page at Github. Read readme.md the instruction on how to use, it's there.
Basically after you recompiled the apk, take it out from the folder where it was decompiled at (In my case it was on "AndroidOverlayBattery8000\dist\AndroidOverlayBattery8000.apk") and place it on the root directory of apktool. Then input on the cmd prompt/windows powershell/terminal the command
java -jar uber-apk-signer.jar --apks /path/to/apks
The apk signer should complete and show you verification that the apk was signed properly.

In the end I solved it in an easier way by installing APK EASY TOOL with a single click

techfreak9356 said:
Did you make the cover?
Click to expand...
Click to collapse

Yes, I am designing a back cover to be 3D printed back cover later. I'm still waiting for the 2nd battery since the one installed now is starting to bloat due to it being a bad cell

techfreak9356 said:
Yes, I am designing a back cover to be 3D printed back cover later. I'm still waiting for the 2nd battery since the one installed now is starting to bloat due to it being a bad cell
Click to expand...
Click to collapse
probably because you are managing 2 cells with 1 bms...
that's just asking for problems.

DevSquad69 said:
probably because you are managing 2 cells with 1 bms...
that's just asking for problems.
Click to expand...
Click to collapse
3 actually. 2 of them are just fine. The third was was from a different seller, which apparently sold bad batteries to begin with. (I had to replace them out since their contacts got ripped off while I was testing out different spot welding techniques). The third replacement I'm getting is still on its way, but yeah, it is indeed asking for problems.

techfreak9356 said:
Yes, I am designing a back cover to be 3D printed back cover later. I'm still waiting for the 2nd battery since the one installed now is starting to bloat due to it being a bad cell
Click to expand...
Click to collapse
Sounds great.
I'm use Mi 9
When I check uevent ,bms and battery full charge and full charge design. I still 3300
I don't know why. added module IBC40000 Miui to magic
Thanks for diy

Hello.
I flashed the Poco x3 NFC following the instructions, but it gave an error and did not flash, why do you think it gave an error?

DevSquad69 said:
probably because you are managing 2 cells with 1 bms...
that's just asking for problems.
Click to expand...
Click to collapse
When connected in parallel, one board is enough.

techfreak9356 said:
Yes, I am designing a back cover to be 3D printed back cover later. I'm still waiting for the 2nd battery since the one installed now is starting to bloat due to it being a bad cell
Click to expand...
Click to collapse
Well, how are things now?

The error occurred even though I signed the APK. Bluetooth and location are disabled. I disabled system signature verification, I installed unsigned apk, it worked on my phone (Poco x3 nfc) 6 Ncr18650 GA batteries total 21.000 mah. Bluetooth is working now.
I integrated the charge full file into the ACC magisk module and flashed it.

I did all what's in the instructions but there's a problem.
Here's what I did:
1: I soldered 2 battery packs positive to positive and negative to negative(parallel)
2: I have also done the apk modification(signed) and flashed it using magisk with no error.
It's already says "8000mAh" on "device info HW".
But here's the problem, it booted just fine, but when I open some games, or tiktok. The phone screen suddenly flickers, and after 1s it reboots.

How did you edit the kernel profile?

Heracle1697 said:
In the end I solved it in an easier way by installing APK EASY TOOL with a single click
Click to expand...
Click to collapse
Sorry for the delay, in the end he was able to modify the kernel with apk tool and apk signer to sign this application, my configuration is 3 batteries with a total of 12000 mah here I leave a link for download in case someone wants it and forgive my English that it's from the translator xD