Related
So I noticed a number of references in one of the mega XDAndroid threads to overclocking Rhodium. Sounded pretty simple, just a string of text with the desired frequency in a particular file.
A couple of questions for those who toyed with that:
1) was it stable and what was its fastest stable speed?
2) did it run uncomfortably hot?
3) is it possible to alter it on the fly (so you can run it slow when you're reading, and crank it up for video), or do you have to choose a speed preboot and reset to change it?
4) If it can't at the moment, be altered on the fly, might it be possible for some program to do that in the future?
5) finally, why is it so easy on adroid? It seems like no2chem has hit a bit of a wall in making his winmo project hum, but the references here made it sound like a pretty basic task.
Part of the reason I'm asking is flash 10.1 is due for android in Q1. The last I read of CPU requirements had them over Rhodium's specs by a lot. Mobile hulu access would be fantastic, and I'm planning to start dual booting this summer, once classes are done. It'd be nice if my TP2 could eek out enough performance for that.
Thanks
You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.
devilcuban said:
You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.
Click to expand...
Click to collapse
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.
Yep same here. If I add that line, once it goes to sleep in Android, it doesn't want to wake up again...
Reefermattness said:
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.
Click to expand...
Click to collapse
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.
devilcuban said:
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.
Click to expand...
Click to collapse
I did test and confirm this. I think what happens is with smem.fake=1 the phone actually never goes to sleep.... at least the sleep light never turns on. I will have to ask phh if this is the case.
Tried putting the overclock line in Startup.txt but it did not seem to change anything, at least according to the CPU Benchmark app. The battery line did seem to work though, as it thought it was charging even while not plugged in.
Is there a specific order that these parameters need to be added in? I just added the overclock line at the end and the battery one after that.
Using the latest non-sense 2.1 builds.
I'd love to add Rhodium overclocking support to my RogueTools application.
I think there is still a constraint though with write access to /system. I am hopeful that shortly the Rhodium kernel and rootfs developers will deviate out of the current read only SQSH model and go the way of the Vogue, Kaiser and Polaris hosting the system and data in separate EXT2 partitions on the SD Card. NAND would be the next step.
If someone knows another way to overclock on the fly once the system is up (post boot). PM me. Like I said, I'd love to add support for the Rhodium.
so nothing on the OC for 2.1 yet?
bump
I'm about to test overclocking with the SetCPU app. Worked fine on my rooted G1. I'll report back with my findings.
Edit: Did not work with custom and/or multiple devices selected. Can't push any higher than the stock 528. Blah.
on screen keyboard
when i put both sleep fixes and the overclocking cpu command in my startup text i get the on screen keyboard like in rhobuntu. how do i disable this? its not even usable it just lingers there and its very annoying
O.S.K. byebye command is msmvkeyb_toggle=off
OverClocking M2CW & IME
Data corruption is inevitable without running extensive stress testing to find a safe speed. I have yet to find one for msm7k processors, but surely Qualcomm has one. Benchmarking is not the same as stress testing. Such stress testing apps need to be run for several hours & even days. They can't test all functionality accuracy. Stress testing in themselves can cause hardware damage & even catastrophic failure.
Data corruption is often the "silent killer" and goes undetected by you or system checks ... until you need it most. It may be a config file, a message file, a contact database, an executable, a registry hive, a system file. Any non ROM file is vulnerable. Backup OFTEN & NOT while OC, even though BUed corrupted data is still corrupted. Quote "stable speed" isn't such just because device doesn't randomly lock up or reboot.
Every CPU and memory chip has different limitations. Same phones built on same date may not OC the same.
Don't OC when when building new Android data.img file, downloading update files or apps, extracting or creating archived files, installing apps, encrypting or decrypting.
OC doesn't help Project XDAndroid developers. I suspect many "bugs" they spend valuable time on are OC related.
The msm7k processors supported by Project XDAndroid are a speed scaling processor designed for optimum performance vs. battery runtime, ramping up and down the processor speed based on demand. Average device use doesn't utilize full processor speed.
OC is most noticeable in OS boot times (when OC is initialized prior to), certain multitasking operations, some video playback, CPU intensive games, & to a lesser extent web browsing. Many factors determine the effectiveness of OC especially whether graphics are hardware or software supported.
Your OC device may actually perform worse, noticeably more sluggish, or more jerky than when not OC. Ever notice on some boots into Android it takes forever for your carrier to be detected & displayed on the lock screen and it may creep along as if your processor was hijacked by a random process? Ever notice when you open the app drawer not all your apps are displayed?
OC does use more energy thereby shortening battery run time and producing more heat. Don't complain about battery life if you are OC. Accurate battery charge state & battery run time are not synonymous.
While OC may shorten hardware lifespan it most likely, though possible, will not lead to a catastrophic failure in the typical device lifetime due to the rate of current technological innovations and average length of ownership.
My overall performance satisfaction with Project XDAndroid is best when not OC, especially now that hardware 3D is supported or partially supported as in my rhod500.
OC at your own risk.
Hey guys. Anyone found a fix to the lag issue when scrolling up and down in the apps drawer? To know more that I mean, pls click on the below 2 links:
http ://forum.xda-developers.com/showthread.php?t=679037&highlight=scroll+speed
and
http ://forum.xda-developers.com/showthread.php?t=657569&highlight=lag+program+menu+htc+desire
That's strange, I don't experience any lag at all... It's supersmooth and fast.
Ditto, smooth as anything here
Are you using a live wallpaper? one thing i've noticed is cpu intensive live wallpapers make scrolling the apps menu lag quite badly. At a guess i'd say live wallpapers remain running when the apps menu is displayed.
Switch to a static wallpaper or the relatively undemanding htc sense live wallpaper, see if it makes a difference.
Weird..no lag here.
Super smooth.
Yeah, I have a solution for you: buy an iPhone!
Okay, enough trolling. I experienced that as well, but it suddenly stopped and now it's very smooth. I don't know what I did, but I am certain that it stopped after the second 2.2 OTA.
I have a few different ideas you can try. I do all of these on my own phone and it's snappy as anything, even though I've limited the clock speed to 650 maximum.
1) Copy everything back to your phone if you currently have most/all things on your SD card, leaving the things on your SD only if they're actually big. Say, everything below 2mb keep on your phone.
2) Install a different launcher, like ADW. Aside from possibly being a little faster, it allows you to customize your app drawer and remove things you don't need. For example I've removed everything I already have an icon on my home screen for, and now I only use the app drawer for odds and ends or things I'm still deciding if I need them or not - like, 15 things at most usually. I don't even NEED to scroll!
3) Install a better OS, like Cyanogenmod. It's faster in general.
4) Install an OS (or patch/script) which allows you to use an EXT partition on your SD card for apps. EXT2/3/4 are much faster and lower-latency than FAT32.
5) Use SetCPU or a similar app to increase your CPU's MINIMUM speed while the screen is on, from 245 to 384. This will eliminate the initial stutter your phone may have before it decides to clock up the CPU. Even though it's a 50% increase or whatever, in practice it will have virtually no effect on your battery life since it will only take effect while the screen's on - at which time your screen will be using lots more power than the CPU does at any speed.
If #5 solves it for you, just remember the stuttering you're experiencing is only for the sake of battery savings, it's got nothing to do with your phone's performance. In that sense, it highlights one of Android's features rather than a deficiency, even if it's doing this in an unattractive way!
nawoa said:
I have a few different ideas you can try. I do all of these on my own phone and it's snappy as anything, even though I've limited the clock speed to 650 maximum.
1) Copy everything back to your phone if you currently have most/all things on your SD card, leaving the things on your SD only if they're actually big. Say, everything below 2mb keep on your phone.
2) Install a different launcher, like ADW. Aside from possibly being a little faster, it allows you to customize your app drawer and remove things you don't need. For example I've removed everything I already have an icon on my home screen for, and now I only use the app drawer for odds and ends or things I'm still deciding if I need them or not - like, 15 things at most usually. I don't even NEED to scroll!
3) Install a better OS, like Cyanogenmod. It's faster in general.
4) Install an OS (or patch/script) which allows you to use an EXT partition on your SD card for apps. EXT2/3/4 are much faster and lower-latency than FAT32.
5) Use SetCPU or a similar app to increase your CPU's MINIMUM speed while the screen is on, from 245 to 384. This will eliminate the initial stutter your phone may have before it decides to clock up the CPU. Even though it's a 50% increase or whatever, in practice it will have virtually no effect on your battery life since it will only take effect while the screen's on - at which time your screen will be using lots more power than the CPU does at any speed.
If #5 solves it for you, just remember the stuttering you're experiencing is only for the sake of battery savings, it's got nothing to do with your phone's performance. In that sense, it highlights one of Android's features rather than a deficiency, even if it's doing this in an unattractive way!
Click to expand...
Click to collapse
I have my Desire set at 768 max and there really isn't a noticeable difference from the normal 998. Hell. I clocked it way down and it was still WAY faster then my HTC Magic ever was. It's funny that the Desire's processor is faster at 3xx mhz then the Magic's is at 710mhz. I found the Desire to be unstable for sustained periods of anything under 700mhz though. Is yours running stable at 650? Maybe it was just the 691mhz speed I was using.
Hi,
I built a (I would say very nice) bootanimation but the problem is that is seems kind of laggy.
The animation has 2 parts (one that runs once, one that repeats). First part has 175 images, second has 45. All images are sized 360x640. Boot animation works but I have the following issue: it lags! First part always lags, second part lags only on the first run, after that it is smooth as it should be. I also tried using only the first part and it's the same: first loop is laggy, second is smooth.
the desc.txt contains this:
720 1280 24
p 1 0 part0
p 0 0 part1
All seems ok but for some weird reason, it always lags during the first loop...
Does anyone have any idea why? Or how I can optimize it? Is it too much info to process while booting?
this is starting to get on my nerves...
I tried:
making the individual images smaller, more compression (actually, found out how to go to about 10% of the initial size - from 80MB to 9MB)
making it shorter (using only 100 images)
nothing works...i still get a lot of choppiness on the first run...whyyyyyy???
I read that it might be a kernel issue...could it really be?
mrfenyx said:
this is starting to get on my nerves...
I tried:
making the individual images smaller, more compression (actually, found out how to go to about 10% of the initial size - from 80MB to 9MB)
making it shorter (using only 100 images)
nothing works...i still get a lot of choppiness on the first run...whyyyyyy???
I read that it might be a kernel issue...could it really be?
Click to expand...
Click to collapse
If it makes you feel any better, all bootanimations lag for the first few rounds. It's happened on all of my devices. Android starts up and puts a load on the CPU, the last few rounds of a bootanimation are absolutely pointless because the system has been loaded up by that time, it's purely cosmetic. That is why disabling the bootanimation results in faster boot times.
Maybe its because of the sub-par gpu on the nexus? Not sure, just putting that out there
Sent from my Galaxy Nexus using xda premium
mohitrocks said:
Maybe its because of the sub-par gpu on the nexus? Not sure, just putting that out there
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This isn't PS2 emulation, it's a simple boot animation lol
Sent from my Galaxy Nexus
What would you recommend the priority be? Booting up or butter smooth animation?
How about a static image, no animation... and don't reset.
I use the Nexus One animation because even slower, it looks cool. Perhaps try not to make it as busy thus creates an illusion of fluid. Or have the animation still at first, like a logo, then have some animation... like a quick fade in... then a slide?
You just have to get creative to work around it.
Sent from my Galaxy Nexus using xda premium
a static boot animation can prevent battery drain and/or boot more quickly?
EDIT: there is the possibility to see the POST of boot (like a computer)?
Abufinzio said:
a static boot animation can prevent battery drain and/or boot more quickly?
EDIT: there is the possibility to see the POST of boot (like a computer)?
Click to expand...
Click to collapse
they already have that... http://forum.xda-developers.com/showthread.php?t=648555
i mean, the real android post, not an animation
Try this for computer style boot screen
https://play.google.com/store/apps/details?id=eu.chainfire.livelogcat.lite
Add for the lag... Its more than likely not your ba but the phone lagging while it boots. You can try using jpegs instead of png although its been so long since I've done one that I'm unsure if jpegs work anymore. You can also try pngcrush to squeeze more kb out.
Ok - you may be familiar with my mod here -
http://forum.xda-developers.com/hon...ipt-disable-enable-swap-honor-5x-kiw-t3308321
If not - try it - but in any case, from that thread, get SH Script Runner, Stericson's Busybox Installer
What this mod is about -
Makes your phone act like it's 720p instead of 1080p
It's still 1080p
But it moves the work from the GPU to the screen's hardware scaler
There's no such thing as a free lunch so this won't give you more battery duration
This may screw up your favorite keyboard, like SwiftKey - use the Google keyboard
This may screw up your icon sizes in your launcher (so look for launcher options to change that if you care)
This is going to make your fonts smaller in many places
This mod is not guaranteed to work the way you want
You MUST make a nandroid backup before proceeding if you know what's good for you
Run this the same way as you would my swap scripts
What this mod contains -
dpi-switch.zip that you unzip at the top of your /sdcard
If you followed the swap script instructions, you already knew that
720p.sh does exactly what the name implies - it's the mod
1080p.sh does what the name implies - it restores your phone to the default state
You must be root to run - see the instructions - turn on the SU button in SH Script Runner
Your phone will reboot when done
I may or may not change that
What could possibly go wrong -
If you use this with other DPI or screen mods, the sky could fall, your friends will leave and your dog will disown you - plus your phone will be borked
You didn't ignore me, you made a nandroid backup so nothing really bad can happen if you did
The screen may start out as tiny - play with it some, it will sort itself out - maybe even hold power to kill it and start it again
I can reproduce that but not every time
You can get the right sized screen and be fine, just play with it if it hits you
Try turning to landscape and back, that seems to clear it up too
That only happens right after the mod is applied
Important things to know about this mod -
No puppies were harmed during its creation
I am not responsible if your phone dies, catches fire, blows up, tries to take over the world, or starts running like a bat out of hell and makes you very happy
OK, I'm a little bit responsible for that last bit but only a little
Monjori OpenGL Shader benchmark test - 49 fps stock, 62 fps modded
PERFECTLY SAFE TO GO BACK AND FORTH FROM 720 TO 1080 AT ANY TIME
Enjoy - if it's pretty necessary, I'll come back with pictures - but seriously - see the swap thread linked about - this just copies the same approach, and just gives you some new commands.
Cheers!
PS - Yes - you can too do this yourself or use some other apps. No - nothing is as easy as doing it this way if you're not an expert in these things - that's why I made this for you.
Download is right here -
View attachment dpi-switch.zip
Here are the codes:
720p -
Code:
#!/system/bin/sh
# Sets 720p windows defaults on 1080p 5.5" Huawei, such as honor 5x
# Must run as root
# WILL reboot when finished!
# March 19, 2016
# EarlyMon
wm size 720x1280
wm density 320
setprop sys.powerctl reboot
1080p -
Code:
#!/system/bin/sh
# Restores 1080p windows defaults on Huawei, such as honor 5x
# Must run as root
# WILL reboot when finished!
# March 19, 2016
# EarlyMon
wm size reset
wm density reset
setprop sys.powerctl reboot
Is it the same as running
adb shell wm size 720x1280
adb shell wm density 320
adb reboot
Through adb or are there changes in value ?
Edit: I looked into the files and saw a change in density, 267 instead of 320...would it work with 320 ?
Zakaria.R said:
Is it the same as running
adb shell wm size 720x1280
adb shell wm density 320
adb reboot
Through adb or are there changes in value ?
Edit: I looked into the files and saw a change in density, 267 instead of 320...would it work with 320 ?
Click to expand...
Click to collapse
Yep, basically the same thing. There are namespace and zygote differences from Huawei so things in a terminal emulator aren't always the same as when run through adb, so we need root here.
267 comes from Pythagoras -
sqrt( 720^2 + 1280^2 ) / 5.5 = 267
320 is the class value understood by services and both work equally well.
I've updated the script to the use the 320 class value for density and went ahead and changed shutdown to reboot - I've seen occasional weirdness with just a reboot, but the first post instructions say if it's weird, try a shutdown anyway.
I'm not sure the changes make a difference but you're right - most folks familiar with this will expect the class value there, so I've changed the script.
And as I mentioned at the end of the post - no magic, nothing you can't do yourself if you know how, just a lot easier this way for non-experts.
Cheers!
PS - added the script codes to the second post, no secrets to this.
EarlyMon said:
Yep, basically the same thing. There are namespace and zygote differences from Huawei so things in a terminal emulator aren't always the same as when run through adb, so we need root here.
267 comes from Pythagoras -
sqrt( 720^2 + 1280^2 ) / 5.5 = 267
320 is the class value understood by services and both work equally well.
I've updated the script to the use the 320 class value for density and went ahead and changed shutdown to reboot - I've seen occasional weirdness with just a reboot, but the first post instructions say if it's weird, try a shutdown anyway.
I'm not sure the changes make a difference but you're right - most folks familiar with this will expect the class value there, so I've changed the script.
And as I mentioned at the end of the post - no magic, nothing you can't do yourself if you know how, just a lot easier this way for non-experts.
Cheers!
PS - added the script codes to the second post, no secrets to this.
Click to expand...
Click to collapse
Appreciate the explanation good job my friend keep up
Performance Impact for 2D games
I notice my phone is bit laggy when I play 2D game with 720p mode. I doubt scaler is overloaded.
So I compare both score with GFX benchmark.
Here are texturing results. 720p score was about 1270, native was about 1400.
720p mode impact some 2D performance by use hardware scaler always.
Same benchmark shows improvement in other areas - there's no simple answer and this is a mod to use when it benefits games that get along with it. As you've found, not all do.
EarlyMon said:
Same benchmark shows improvement in other areas - there's no simple answer and this is a mod to use when it benefits games that get along with it. As you've found, not all do.
Click to expand...
Click to collapse
Strong agree.
I decided my phone to leave default. 'cause for me, more suitable than 720p. But someone is not.
Not simple.
Here are all results for comparison. for someone.
On my KIW-L21 the Screen did not scale, unfortunately.
Meaning the Screen with a resolution of 720p was stuck in the upper left corner of the screen(Like a window, the rest of the screen was black),
while the touch input was rooted from the whole screen, which made it a little bit challenging to operate the device
Any idea how one could tackle that problem?
Nekly said:
On my KIW-L21 the Screen did not scale, unfortunately.
Meaning the Screen with a resolution of 720p was stuck in the upper left corner of the screen(Like a window, the rest of the screen was black),
while the touch input was rooted from the whole screen, which made it a little bit challenging to operate the device
Any idea how one could tackle that problem?
Click to expand...
Click to collapse
1. Enable auto-rotate. Then rotate your phone at lock screen.(See #1)
2. Try edit script "wm density 267" instead of 320. Use SH script runner on root mode. (See #3~)
3. Try adb command via PC (see #3) if you feel too difficult to operate with touch screen.
I counter same problem. I resolve this with 3. 'cause I can't unlock my phone
ssrnsrsr said:
1. Enable auto-rotate. Then rotate your phone at lock screen.(See #1)
2. Try edit script "wm density 267" instead of 320. Use SH script runner on root mode. (See #3~)
3. Try adb command via PC (see #3) if you feel too difficult to operate with touch screen.
I counter same problem. I resolve this with 3. 'cause I can't unlock my phone
Click to expand...
Click to collapse
1. Autorotate is on. Does not do anything.
2. Edited the script to uses 267 density. Did not work either.
3. ADB kinda works with density 320. I could test, wether to use this mod or not. But in my Use Case I got no benefit whatsoever. Also not beeing able to change this on the go is another deal breaker to me.
Thanks for the support.
I have the same results as Nekly. After digging deeper, the problem lies within the EMUI 3.1 launcher. After you change the resolution/density, the icons look all jacked. I opened some games, and the games look just fine. There is definitely a noticeable FPS boost.
There's no such thing as a free lunch so this won't give you more battery duration
Click to expand...
Click to collapse
After careful thought, I tend to disagree with this statement. While the screen is off, hes right, there is no free lunch there. While I have not tested it, in theory it *should* result in more battery duration while you are using the phone. My theory is that if you were to change the resolution to 720x1280 thats 921600 total pixels rendered on the screen. Instead of the normal 1080x1920 which is 2073600 total pixels rendered. Thats a net difference of 1161000 less pixels that the GPU has to render. So less work for the GPU. The MHZ will still be the same so no change there. If there was no FPS boost in the game, then the GPU would still be doing the same amount of work. But there is an FPS boost.
This is an awesome tweak, I wish I could get the launcher to display the icons correctly. Again great work @EarlyMon!
TouchOdeath said:
I have the same results as Nekly. After digging deeper, the problem lies within the EMUI 3.1 launcher. After you change the resolution/density, the icons look all jacked. I opened some games, and the games look just fine. There is definitely a noticeable FPS boost.
After careful thought, I tend to disagree with this statement. While the screen is off, hes right, there is no free lunch there. While I have not tested it, in theory it *should* result in more battery duration while you are using the phone. My theory is that if you were to change the resolution to 720x1280 thats 921600 total pixels rendered on the screen. Instead of the normal 1080x1920 which is 2073600 total pixels rendered. Thats a net difference of 1161000 less pixels that the GPU has to render. So less work for the GPU. The MHZ will still be the same so no change there. If there was no FPS boost in the game, then the GPU would still be doing the same amount of work. But there is an FPS boost.
This is an awesome tweak, I wish I could get the launcher to display the icons correctly. Again great work @EarlyMon!
Click to expand...
Click to collapse
0.5 × 2 = 1
If you render half as many pixels per frame but increase the number of frames per second by what could be a factor of two, then the system theoretically ends up rendering the same number of pixels per second.
(pixels/frame × frames/second = pixels/second)
GPUs and displays work on fields - even the LCD control matrix doesn't have to refresh in terms of pixels - so the math is actually quite a bit more complex for making predictions.
If you get better battery performance, great!
But I won't promise that because TANSTAAFL.
Nice!! Very deep insight, love the formula!!
Loving these small but useful script contributions, Mon. Thanks for the hard work. Will definately try this when I get home. Question - is the effect on the icons on the native launcher only? I removed that from /system and installed Nova as my only and default launcher, so just wondering if it's Huawei's fault or just a secondary effect from the resolution change.
I have the same results as Nekly. After digging deeper, the problem lies within the EMUI 3.1 launcher. After you change the resolution/density, the icons look all jacked.
Click to expand...
Click to collapse
What I said in the above quote is wrong. Nekly does a great job in describing the problem:
On my KIW-L21 the Screen did not scale, unfortunately.
Meaning the Screen with a resolution of 720p was stuck in the upper left corner of the screen(Like a window, the rest of the screen was black),
while the touch input was rooted from the whole screen, which made it a little bit challenging to operate the device
Any idea how one could tackle that problem?
Click to expand...
Click to collapse
I'm experiencing the exact same problem on my L24 as @Nekly and I now have a ghetto solution.
There is an app called Resolution Changer. It has widgets you can place on your desktop. I have two widgets, a 720p and a 1080p. When the device is rebooted, the resolution will screw up, all you have to do is click on the 1080p, and it will restore fullscreen. Then click on 720p widget, and your screen will be fullscreen 720p. I'll post a better solution when I find one.
+1 to @EarlyMon for coming up with this geniusry. This tweak is clutch.
Can anybody get me a flashable zip that resets the resolution back to 1080p? I used the Resolution Changer app and somehow I screwed up my display. Any help would be appreciated!
EDIT: found this -->https://forum.xda-developers.com/android/general/guide-fixing-resolution-using-nomone-t2921856, this guy saved my day, but it would be more convenient when having a flashable zip file instead of having to connect to a computer and reset res via adb. Cheers!:good:
{
"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"
}
Some battery life stats is what I'm most interested in. This thing discharges by just looking at it.
Still early, some wifi wakelocks but look promising. The guru of GSI, Phh has an S22 on the way so expect the GSI's to be more or less flawless in the future
NisseGurra said:
View attachment 5563881
Click to expand...
Click to collapse
How to flash GSI? Steps please
Steps:
1: Patch stock recovery.img to include fastbootd
Use script : https://github.com/phhusson/samsung-galaxy-a51-gsi-boot/blob/master/run.sh
"Put your recovery in the same folder named recovery.img, edit script to fix path to magiskboot, run run.sh as root, flash r.img"
2: Download vbeta.img from google
3: Download an GSI, https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Andriod 12, AB, arm 64
4: Reboot fastboot
5: Open command window, enter
fastboot flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash system system-xxxx.img ( the name of the gsi you use)
reboot to recovery and do an factory reset
reboot system
NisseGurra said:
Steps:
1: Patch stock recovery.img to include fastbootd
Use script : https://github.com/phhusson/samsung-galaxy-a51-gsi-boot/blob/master/run.sh
"Put your recovery in the same folder named recovery.img, edit script to fix path to magiskboot, run run.sh as root, flash r.img"
2: Download vbeta.img from google
3: Download an GSI, https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Andriod 12, AB, arm 64
4: Reboot fastboot
5: Open command window, enter
fastboot flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash system system-xxxx.img ( the name of the gsi you use)
reboot to recovery and do an factory reset
reboot system
Click to expand...
Click to collapse
Sorry I am nope
I have to edit the script run.sh?
".... edit script to fix path to magiskboot, run run.sh as root, flash r.img"
So you mean I have to download
GitHub - phhusson/treble_experimentations: Notes about tinkering with Android Project Treble
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
and it will download the magiskboot?
as it shows in the run.sh script.
Code:
mkdir d
cd d
~phh/Downloads/magisk/x86/magiskboot unpack ../r.img
~phh/Downloads/magisk/x86/magiskboot cpio ramdisk.cpio extract
# Reverse fastbootd ENG mode check
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery e10313aaf40300aa6ecc009420010034 e10313aaf40300aa6ecc0094 # 20 01 00 35
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery eec3009420010034 eec3009420010035
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery 3ad3009420010034 3ad3009420010035
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery 50c0009420010034 50c0009420010035
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery 080109aae80000b4 080109aae80000b5
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery 20f0a6ef38b1681c 20f0a6ef38b9681c
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery 23f03aed38b1681c 23f03aed38b9681c
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery 20f09eef38b1681c 20f09eef38b9681c
~phh/Downloads/magisk/x86/magiskboot cpio ramdisk.cpio 'add 0755 system/bin/recovery system/bin/recovery'
~phh/Downloads/magisk/x86/magiskboot repack ../r.img new-boot.img
cp new-boot.img ../r.img
can you please share your run.sh script so I can have an idea how to edit that.
Here are the recovery with fastbootd included.
ONLY S22 exynos SM-S901B, SM-S901B_AVC6 firmware
recovery.img
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
NisseGurra said:
Here are the recovery with fastbootd included.
ONLY S22 exynos SM-S901B, SM-S901B_AVC6 firmware
recovery.img
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Thank you so much. Can you please share your run.sh script too? I will be very thankfull. Did you use 7zip in order to compress the recovery image in to .lz4? I am using ubuntu.
Can someone please tell me how to manually add or include fastbootd in a stock recovery.img? I can't get this script to run properly. Thanks in advance.
Hi can anyone give detailed instructions how to enable fastboot on stock recovery ?
Late reply: join phh group on telegram and request an recovery with fastboot enabled. There are memebers that will help you.
Device name? GSI version? - #phh-treble
https://t.me/phhtreble/283195 <--- Read before any question ^^^
t.me
Still waiting for the battery life screenshots. I'm really curious how much better it is on GSI than on stock.
dragos281993 said:
Still waiting for the battery life screenshots. I'm really curious how much better it is on GSI than on stock.
Click to expand...
Click to collapse
As s22 exynos drain 30-40% from wifi bug every night there no way to make an real estimate of battery life.
NisseGurra said:
As s22 exynos drain 30-40% from wifi bug every night there no way to make an real estimate of battery life.
Click to expand...
Click to collapse
NisseGurra said:
As s22 exynos drain 30-40% from wifi bug every night there no way to make an real estimate of battery life.
Click to expand...
Click to collapse
When I get home tommorow night, I'll link you a few places to read and help you do some cleaning up because these Samsung phones are full of junk and services that the phone can live without. I've been going nuts trying to make this rubbish of a device perform better and I managed to get it to waste less battery while active and inactive by disabling and uninstalling A LOT of stuff I don't need and so on. And I came to the conclusion that for daily usage I didn't need 100% of the 8 Gen 1 chipset. I therefore cut in half the frequency for the 3rd cluster and decreased the ones of the other 2 as well. I basically limited the max freq of the CPU without noticeable effects on the performance. Probably benchmarks would should how much performance I wasted, but as I don't care about numbers on paper, I'm pretty ok with how the phone's running right now after cleaning it up. The battery is very small, the CPUs are very inneficient, both SD and Exynos, despite the marketing claims, the apps are very power hungry and the CPU gives the processing power in an aggressive and inneficient when the transition from a frequency to another should be smoother and not as quick to give it all up when it's actually not necessary. Paired with all the useless processes and services which work like lunatics to do whatever BS they're trying to do, whether it is while you're using the phone or in the background, and you're left with a terrible user experience that makes you contemplate throwing the phone away.
I used an iPhone 13 Pro for 4 months before buying this thing and I forgot to look at the battery level because iOS is that efficient. It was terrible for me overall but when it comes to smoothness and battery life, there's nothing in the Android world that comes even close to that. The best Android device that comes close to Apple's latest amd greatest is probably around 5,6 years behind. That's sad but it is what it is.
dragos281993 said:
When I get home tommorow night, I'll link you a few places to read and help you do some cleaning up because these Samsung phones are full of junk and services that the phone can live without. I've been going nuts trying to make this rubbish of a device perform better and I managed to get it to waste less battery while active and inactive by disabling and uninstalling A LOT of stuff I don't need and so on. And I came to the conclusion that for daily usage I didn't need 100% of the 8 Gen 1 chipset. I therefore cut in half the frequency for the 3rd cluster and decreased the ones of the other 2 as well. I basically limited the max freq of the CPU without noticeable effects on the performance. Probably benchmarks would should how much performance I wasted, but as I don't care about numbers on paper, I'm pretty ok with how the phone's running right now after cleaning it up. The battery is very small, the CPUs are very inneficient, both SD and Exynos, despite the marketing claims, the apps are very power hungry and the CPU gives the processing power in an aggressive and inneficient when the transition from a frequency to another should be smoother and not as quick to give it all up when it's actually not necessary. Paired with all the useless processes and services which work like lunatics to do whatever BS they're trying to do, whether it is while you're using the phone or in the background, and you're left with a terrible user experience that makes you contemplate throwing the phone away.
I used an iPhone 13 Pro for 4 months before buying this thing and I forgot to look at the battery level because iOS is that efficient. It was terrible for me overall but when it comes to smoothness and battery life, there's nothing in the Android world that comes even close to that. The best Android device that comes close to Apple's latest amd greatest is probably around 5,6 years behind. That's sad but it is what it is.
Click to expand...
Click to collapse
I swear all the **** Samsung installs on their devices is turning me crazy
No Samsung, I don't want Bixby, I don't want this side taskbar installed by default, I don't want your cloud services by default, no I don't want your "secure folder" thing, I don't want your Samsung Pass thing either
Like come on, the above list is like 25% of all the **** they install
Visually OneUI is awesome and I love it, I love some of the features and options that they provide / provided very early, even before Android sometimes, it's highly customizable and things like Goodlock are awesome, but it would be even better if you could allow us to remove ALL of their apps without having to use ADB or some weird stuff like this
I think Digital Wellbeing is a good example of what should be removable as I don't see everyone using it and it's even more of a shame when you realize that uninstalling it with ADB works perfectly fine and causes no issues...
Something that I love on Windows in the "services" tab where you can see each service, what it does, weither it is ok to disable it or not, what features you lose if you disable it... I think Android should do the same or something similar with system apps
jojos38 said:
I swear all the **** Samsung installs on their devices is turning me crazy
No Samsung, I don't want Bixby, I don't want this side taskbar installed by default, I don't want your cloud services by default, no I don't want your "secure folder" thing, I don't want your Samsung Pass thing either
Like come on, the above list is like 25% of all the **** they install
Visually OneUI is awesome and I love it, I love some of the features and options that they provide / provided very early, even before Android sometimes, it's highly customizable and things like Goodlock are awesome, but it would be even better if you could allow us to remove ALL of their apps without having to use ADB or some weird stuff like this
I think Digital Wellbeing is a good example of what should be removable as I don't see everyone using it and it's even more of a shame when you realize that uninstalling it with ADB works perfectly fine and causes no issues...
Something that I love on Windows in the "services" tab where you can see each service, what it does, weither it is ok to disable it or not, what features you lose if you disable it... I think Android should do the same or something similar with system apps
Click to expand...
Click to collapse
Exactly. They like to push down your throat their crap. All the stuff you mentioned I already disabled or uninstalled altogether. Digital Wellbeings was draining my battery in the background at all times without even having it configured. So that was deleted. Bixby is gone too and a bunch of other things. But the main issue for all this is the small battery for the terrible quality 8 Gen 1 or the Exynos 2200. 4nm is pure marketing at this point.
Sorry, @NisseGurra for not getting back here last night, like I said I would.
I also realized afterwards that you were on a GSI build but I intended to help you clean up the stock firmware.
The best advice I can give you right now though is to try doing what I did. Please don't take it personally if I explain or define stuff that you might already know or actually know even better than me. If someone else reads this, they might learn something from it or do some tweaking even if they're on the stock ROM or something custom. You take only what you need from this.
The whole thing starts with the process of opening the Apps section in the Settings, checking/turning on the "system apps" option and opening everything in there one by one. You'll have both apps and services showing up in there and what you wanna look for is the "Battery" section, or whatever it's named on your GSI. You basically need to see how much battery it's wasted since the last charge. High battery usage=no bueno. In that case, you google that app/service, weird name or not and see if it's rudimentary for the proper functioning of your phone. If it's not essential or it's used as a service for some apps that you don't even use but it's there just in case, then you can get rid of it. And obviously, you have to do this for every single app and service in there. It's a pretty time-consuming job but if you want to keep your sanity in the end, then it's a good activity. After that, for the remaining things, you can use "Servicely" from the Play Store and force the stuff you don't need at all times to sleep/Standby when the screen is off or even prevent it from running in the background altogether.
You should also download Naptime and use it to activate Aggressive Doze and disable Motion Detection too so the phone stays in doze mode even when you're moving around, a scenario in which by default the phone comes out of doze whenever it detects motion.
Stuff like "Find my phone" I had to turn off. There was one option for this thing somewhere in the google account section and also in the Samsung provided services in the Settings, on the stock firmware. Talk about a huge mess. I don't really need those. If I lose my phone, which never happened to me so far, it is what it is, but I'd rather have better battery life than have a service running at all times just for the moment I lose this crap if that ever happens.
This whole thing above is mainly meant to improve the standby time when the phone is idling.
And to not forget to mention this, I have Battery Saver active at all times. Normally, everything should be crippled while this thing is on including the refresh rate of the screen which gets stuck at 60Hz. For that, there's Galaxy Max Hz. It offers the ability to activate something called "Keep smoothness on power saving mode" and you won't even know that the thing Is even on. The essential part is that the OS is supposed to be less active, decrease the background BS and also the power of the CPU down to 75%. This part doesn't really matter because I already planned on downclocking it but if there's anything applied by default to make the CPU less aggressive along with the stock decrease to 75%, then downclocking it would make it even better because now you have lower frequencies which now jump up and down at a slower rate. I mean I hope it's done like that. I haven't monitored the difference in the activity of the CPU with Power Saver on/off so I can't tell for sure. It would be logical to happen that way though. Another important little part is that I installed "Universal GMS Doze" which allowed me to put the Google Play Services on "Restricted" in the Battery section. I had to restrict the "play services framework" too cause they liked to molest my battery too when I wasn't looking. But I digress.
On the stock firmware, I also use Battery Tracker made by Samsung. I really like it because I can easily select the period of time of activity/battery drain by dragging 2 sliders from one side to another and see what happened during that time, and you get background activity stats and what percentage of the battery it's wasted.
For the much better and more detailed Screen on/Screen off stats or charge/discharge information which all show in a useful notification, I use Battery Guru. It barely drains any battery so it's very well optimized.
Back to the technical part, the other important thing was to downclock the CPU, and this is essential for the active time which later translates into better SOT.
I'm using Smart-Pack Kernel Manager for the tweaks because it's the most detailed of them all and well rounded in my opinion and it's also the lightest on the battery, while in use, of course. It's got a side panel with all the sections that have the tweaks I'll mention in this post.
The following part is gonna be a bit more detailed. It's just a few tweaks in the end but I'll throw in some basic information here and there to make it a little more informative and nice to read. Keep in mind that even if I tweaked the stock firmware here, the tweaks are essentially the same for the kernel or at least similar. The values and options shown in the kernel manager can differ in terms of naming or the way you can change them, but they should be overall similar.
Note that this is more like a presentation of what I did on my phone, not a tutorial. You can open that kernel manager, look around and see for yourself the range of tweaks that are available of which a few are the ones I changed.
Now to business.
The stock max frequencies for the 8 Gen 1 on my S22 are something like this:
- 1785MHz for the 4 LITTLE Cores, 2496 for the 3 Middle cores, and 2995 for Core 8, which is also the big core (terribly inefficient "fat" bastard).
So we've got: 1785, 2496 and 2995 respectively.
My phone is running smoothly with all these downclocked right above the border between noticing and not noticing a difference in the UX department if you get what I'm saying.
So my current maximum clocks for all 3 clusters are 1363, 1555 and 1401 respectively. They're lowered pretty drastically, I know, but I don't care about benchmarks, in which you'd probably see a difference. In the real world, opening and closing apps among other regular things, are not gonna be noticeable. It's not like you're gonna sit with 2 phones next to you, a stopwatch in your hand and cheer when your phone is half a second faster than mine. It's just not gonna happen. That 30% increase and performance. blah blah, when a new generation of a CPU is announced you're not gonna notice especially when we're talking about CPUs that are only 1 generation apart.
Anyway, these lower frequencies will obviously help with thermals mainly but also with the battery life, although the difference for the latter is not that huge it's still better than before.
The CPU Governor for all 3 clusters is set "walt" by default. I couldn't find any information on how it's supposed to work and behave but because it's the default, I'm sure it's focused on something in between performance and battery savings. So I set it to "conservative" for all 3 clusters. This governor likes to get the frequencies back down as soon as possible after a task is done. So this is also gonna help with thermals.
Now to the CPU Hotplug. In the past when big.Little became mainstream, a whole performance cluster was called in for the heavy tasks and they followed a basic routine: when a certain threshold is crossed, the big cores take charge of the situation and when they cross a second threshold, which is a lower value, those big cores step away and they hand over the steering wheel back to the Little cores for the light tasks until they're needed again. They still pitched in but a bit more lightly. Now just one big core appears to be able to do that on its own, however, this time the job is split between the big core and the middle ones. So there's a bit more control over a situation because you've got those middle cores that are pitching in for the medium intensive tasks.
Anyway, I decided to up that threshold and basically make the CPU ask for the big core's help when the job gets a bit more difficult, heavier, essentially making it contribute less often. I don't want to reboot my phone to see what the default values were but now they're basically higher: "Busy down Threshold = 50", and "Busy up=70". I just explained what this threshold is, so you probably already got how this is supposed to work looking at these numbers.
And the last thing tweaked is the GPU. Sadly, the stock kernel doesn't allow for the downclock to stick. It's missing the parts which allow for this sort of functionality because it's stock and wasn't meant to be tweaked. The only thing I could do was to change the power level. You haven't got anything in there other than an option to let you change a value. The essence of it though is that the lower the number, the better the GPU performs. It's not gonna work outside of the defined parameters though. It only gets more active. Anyway, the default value is 10. I set mine to 12, which is the last level. This way I basically put the GPU in a more "conservative" state, so to speak. While gaming, I haven't noticed any performance loss, so hooray. It is doing its job but it's a bit less aggressive.
To finish this long a$$ post, I gotta say that after doing all this above, my battery life has improved quite drastically.
3, 3.5h SOT was what I consistently got without tweaking anything. Right now I'm at 4h49m SOT for only 64% wasted. I charged the phone only to 85% and the battery is down to 15%. The idle drain is only 0.3%/h.
I'll post a screenshot for the hell of it. Anyway, so far so good. One thing's for sure though. I'll do some research and if I manage to find any battery from another Samsung phone that's bigger but is very close in size to the one in this phone, it doesn't matter if I have to cut some of the lips inside to make it fit, I'll do it. I'll make that a project.
Edit: Everything I mentioned above is getting balanced out by other things somehow and 3.5h is the definitive SOT on average I have been getting since forever now. I therefore stopped trying anything, relocked the bootloader and I haven't done anything to the OS anymore. The SOT stayed the same and there aren't any improvements with any update. So this is pretty much how it is and there's nothing we can do about it. The phone is simply pure trash regarding the battery life.
dragos281993 said:
Sorry, @NisseGurra for not getting back here last night, like I said I would.
I also realized afterwards that you were on a GSI build but I intended to help you clean up the stock firmware.
The best advice I can give you right now though is to try doing what I did. Please don't take it personally if I explain or define stuff that you might already know or actually know even better than me. If someone else reads this, they might learn something from it or do some tweaking even if they're on the stock ROM or something custom. You take only what you need from this.
Click to expand...
Click to collapse
Thanks, an excellent post on how to get rid of battery leaks.
Its a pity that this work is needed 2022, should be optimized system from Samsung from start.
The problem now is the wifi bug, very strange that Samsung not noticed this in their testing.
How good does the GSI work on this device? Can you use it as daily driver? I am thinking of buying this phone, but don't want to use One UI.
dragos281993 said:
Some battery life stats is what I'm most interested in. This thing discharges by just looking at it.
Click to expand...
Click to collapse
You're welcome to check my thread then
[DISCONTINUED] Samsung Galaxy One UI - Optimization Guide
THIS IS A SUGGESTED CONFIGURATION FOR SAMSUNG DEVICES OUT OF SUPPORT/CLOSED I - RECOMMENDED SETTINGS To Start With - Factory Reset before starting optimisations - Factory Reset after every Major update (One UI/Android) - Remove SIM before first...
forum.xda-developers.com