Develop Bugs

[Q] Info on V6 Supercharger script

Is it possible to run this script from galaxy w? I have some ram issues and sometimes my phone lags.
In running services these applications are always open:
Facebook
hotmail
go launcher ex + go launcher notification + go locker
maps
swiftkey
I have read somewhere that this script is not very good with multitasking but it makes the phone run faster and smoother. These applications are considered in multitasking? Or in this case multitasking means for example to have messaging, browser etc running at the same time?
Thanks

Yes u can install v6 script in GW
Ur phone will be faster
But u should search the forum before posting
From My GWonder

Okay thank you!
Sent from my GT-I8150 using xda app-developers app

I've had some probless with supercharger, when closing apps with stock task manager, launcher would always close, and have to reload all the apps and widgets (stock touchwiz launcher). Can this be solved?
Sent from my bananaphone.

piefert said:
I've had some probless with supercharger, when closing apps with stock task manager, launcher would always close, and have to reload all the apps and widgets (stock touchwiz launcher). Can this be solved?
Sent from my bananaphone.
Click to expand...
Click to collapse
That is called "Launcher Redraw", technically, when you clear memory or run a resource-demanding apps, Launcher will be killed as well to give more memory.
To prevent this, set the "lock home in memory" option in V6Supercharger. Note that doing this will make your home launcher unkillable and thus your free memory will be lower.
My advice: If you do want to lock launcher in memory, use a low memory usage launcher, such as zeam, Go Launcher uses too much memory.
Hope this helps.
Reidzeibel
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)

I installed Supercharger on my phone and now it works better altough some games runs slower and freezes on my device,

reidzeibel said:
That is called "Launcher Redraw", technically, when you clear memory or run a resource-demanding apps, Launcher will be killed as well to give more memory.
To prevent this, set the "lock home in memory" option in V6Supercharger. Note that doing this will make your home launcher unkillable and thus your free memory will be lower.
My advice: If you do want to lock launcher in memory, use a low memory usage launcher, such as zeam, Go Launcher uses too much memory.
Hope this helps.
Reidzeibel
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
Click to expand...
Click to collapse
Ehhh??
Lock home in memory is not in V6....actually, if it is enabled in Launcher or ROM, Zepp recommends not to do this!!!
From my memory, you got "Hard to Kill", "Die Hard" or "Bulletproof" depending on OOM and Minfree values you choose in the script....
Obviously, Bulletproof means Launcher will never be killed!!
But, the script expects that "lock home in memory" to be disabled, AFAIK.....if I am wrong, I apologise in advance!!!
BTW, if your not on ICS, can I recommend that old favorite Launcher Pro.....it may lack support from the Dev, but it runs silky smooth on GB and is lightweight with many options!!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!

irishpancake said:
Ehhh??
Lock home in memory is not in V6....actually, if it is enabled in Launcher or ROM, Zepp recommends not to do this!!!
From my memory, you got "Hard to Kill", "Die Hard" or "Bulletproof" depending on OOM and Minfree values you choose in the script....
Obviously, Bulletproof means Launcher will never be killed!!
But, the script expects that "lock home in memory" to be disabled, AFAIK.....if I am wrong, I apologise in advance!!!
BTW, if your not on ICS, can I recommend that old favorite Launcher Pro.....it may lack support from the Dev, but it runs silky smooth on GB and is lightweight with many options!!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
Click to expand...
Click to collapse
Yes, Zepp advise not to enable the option IF you don't know what it is used for
Yes, If the launcher or ROM supports "Keep home in memory", do this instead of using supercharger script, I forgot to write this, thanks Irish for adding that part
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)

reidzeibel said:
Yes, Zepp advise not to enable the option IF you don't know what it is used for
Yes, If the launcher or ROM supports "Keep home in memory", do this instead of using supercharger script, I forgot to write this, thanks Irish for adding that part
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
Click to expand...
Click to collapse
Well, I don't know friend.....
every tutorial I have seen or read including Zepp on the V6 Thread, says you should disable this setting if you have it, as it interferes with how V6 manages memory.....
and if you leave it enabled, it may cause lag on your device, the advice is to disable it, and Compcache [zRam]....If you don't have the option, it don't matter, so it's mainly aimed at CM7/9 ROMs.......
to achieve same result, V6 uses the Bullet Proof Launcher, but I think Zepp now advises to use the HTK option, as BPL breaks some other stuff in ICS.....
just to emphasise, it is important to read the outputs given in the script......
Zepp can be a hard taskmaster if you ask something covered there or in help files, etc.
Small example of his comments here:
{
"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"
}

//EDIT2:
My original writing here was:
Forget the Supercharger. Instead take cear of the number of your apps and their intent-behavior.
Scripts like Supercharger are pure mess when targeting a solid daily driver system.
The number of people using this script is only high because there are a lot of folks with little knowledge about the underlying techniques.
Click to expand...
Click to collapse
These words might have been choosen to sharp for this given thread. See the further discussion for more details.
The essential core of my statement is to use the Supercharger with care, as you might run in more problems than before, if you do not know about your usage scenario and the side effects that come with every change in those parameters.
Tweaking settings like those of Supercharger is always a trade-off - but you can only adjust them if you know which flavor of system-behavior you prefer. Most users don't have a clue, so they have to believe magicians - Unlucky for them, because the provided magic potions are not more than nicely advertised placebo.
But at least, they got some great funky banners, so you can easily spread your unawareness in the whole xda forums via your signature through adding them.
// EDIT:
You can optimize memory management for either single task scenarios or multitasking scenarios. Logically, this is a classic trade-off.
To give an simplified example:
- Higher low-memory-killer-borders increase the chances of getting a smoother experience when running only one specific app most the time.
- On the other side, multitasking user experience will suffer, as activities get flushed out of memory earlier, when free memory decreases.
Other example: The VFS Cache Pressure parameter, which controls the weight between file system cache and application memory space.
- Lower values should give you better experience, wenn handling similar task scenarios most of the time, since their access patterns improve through caching
- On the other side, there is less memory space for applications, so this setup will give you slower task switching, as it is more likely now, that your desired new foreground application is not present in memory anymore.

XR-7 said:
Forget the Supercharger. Instead take cear of the number of your apps and their intent-behavior.
Scripts like Supercharger are pure mess when targeting a solid daily driver system.
The number of people using this script is only high because there are a lot of folks with little knowledge about the underlying techniques.
Tweaking settings like those of Supercharger is always a trade-off - but you can only adjust them if you know which flavor of system-behavior you prefer. Most users don't have a clue, so they have to believe magicians - Unlucky for them, because the provided magic potions are not more than nicely advertised placebo.
But at least, they got some great funky banners, so you can easily spread your unawareness in the whole xda forums via your signature through adding them.
// EDIT:
You can optimize memory management for either single task scenarios or multitasking scenarios. Logically, this is a classic trade-off.
To give an simplified example:
- Higher low-memory-killer-borders increase the chances of getting a smoother experience when running only one specific app most the time.
- On the other side, multitasking user experience will suffer, as activities get flushed out of memory earlier, when free memory decreases.
Other example: The VFS Cache Pressure parameter, which controls the weight between file system cache and application memory space.
- Lower values should give you better experience, wenn handling similar task scenarios most of the time, since their access patterns improve through caching
- On the other side, there is less memory space for applications, so this setup will give you slower task switching, as it is more likely now, that your desired new foreground application is not present in memory anymore.
Click to expand...
Click to collapse
Sounds like you've been reading my thread.
Thanks for confirming everything I've said LOL
Fact is, nobody can preach about android memory management and be right without confirming my findings.
So you're right.
And you confirm my findings.
Thanks and you're welcome.
PS. People know they hate launcher redraws and know they like it fixed.
But then again, you haven't read the thread or tried supercharger otherwise you'd know that it has different flavours for multitasking, aggressiveness and balanced.
And it's popular because it's for those that do know, and those that don't - not to mention that it works and does what it says.
If anybody thinks it's a placebo, it's in their head.
And you're wrong when you say "scripts like SuperCharger" because there is no such thing as a script like SuperCharger... silly.
edit: oh about VFS cache pressure, you can check that and all the other placebos in the Kick Ass Kernelizer script.
You fail to mention the importance of min_free_kbytes and dirty ratios and lease-break-time in your attempt to sound knowledgeable.
I guess you were too busy enjoying hearing yourself talk.

Man...
I woz goin to write that....but you just did it for me....
from the horses mouth, so to say!!!
Thanx....
hope you didn't mind the pic.....captures the essence of Zepp
EDIT....of course in XR's OP the EDIT bit was missing, so of course be had a quick look at the V6 thread....went Ohh Ohhhh!!!!
Code:
Edit:
I withdraw offending remarks about XR.....
as I have no knowledge as to his level of knowledge....
and in all humility I know phuck all myself....
OK??
Peace
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!

irishpancake said:
Duplicate post!!! Sorry
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
Click to expand...
Click to collapse

irishpancake said:
Man...
EDIT....of course in XR's OP the EDIT bit was missing, so of course be had a quick look at the V6 thread....went Ohh Ohhhh!!!!
Click to expand...
Click to collapse
Sounds logic. I see that a am completely wrong at the V6-thread, so i go back, place a big EDIT-Label under my text, and add more text, so that every one can cen see it? Not.
Seriously, the examples i gave are there to line up the claim i did in the first part: V6 SuperCharger is no the glory fire-and-forget solution, most of those performance-increases come with some kind of accordant disadvantage. This should be mentioned.
irishpancake said:
Man...
but he is so "knowledgeable" or some kinda know-it-all know-nuttin
Click to expand...
Click to collapse
For some kind of stuff, one does not need >500 posts, but a solid technical comprehension, common sense and some research on the web.
---------- Post added at 03:47 PM ---------- Previous post was at 03:36 PM ----------
@zeppelinrox
What i wanted to express is: Those settings are trade-offs concerning the user experience. This stands in contrast to your explanations, which claim to bring both speed and multitasking to every phone. Forcing the home launcher to stay in memory is a good idea, but it was a one-liner until ICS came, so this can't be the reason for running hundreds LOCs at system startup.
The majority of users has a bunch of other problems, with their device configuration messed up, too much resource-intensive apps installed or a bad-performing ROM installed at some time.
And then there comes this shiny tool, it sounds like the good old american way of life (and is named like it): giving resources here, spending some more memory here - there's no limit, it makes your device blazing fast, it gives you all the things you dreamed of, on your old sluggish device.
Naturally, thats not the case: Yes, there might be useful scenarios, as it allows switching beetween LMK-profiles etc. But lets be honest: Normal users have no clue what they are doing there, playing around and getting more problems than before.
Actually, i like your idea of making those parameters accessible with more ease. As a advanced user, you can archive performance gains, because you know what to set for your specific usage scenario.
Its simply not the fire-and-forget-speedup for android, but people tend to believe this.
// Update:
I added a more diplomatic statement to my original post. Although my technical base argumenttion is the same as before, i guess its good for the discussion if there are less misleading emitotional expressions.

Just read post 3 in my thread.
It was never a one-liner. (well bulletproof launcher used to be at first)
Lock Home in Memory was a one-liner and it wasn't good enough.
All 3 launcher strengths are stronger than "lock home in memory" and there are 3 strengths precisely because there are trade offs...
Reading the script output would explain it anyway but suffice to say, you have said nothing that contradicts anything that I've said.
And very few users have problems with it and has a very good reputation.
Otherwise, this wouldn't happen:
http://goo.gl/qM6yR+
http://goo.gl/1JPl8+
Of course, that is only counting clicks on the goo.gl links... not all clicks.
But you get the idea: the sky's the limit.
And yep... it's like getting a brand new phone.
I've listened to you talk in circles so here's some advice: know what you're talking about before talking about it.

XR-7 said:
Sounds logic. I see that a am completely wrong at the V6-thread, so i go back, place a big EDIT-Label under my text, and add more text, so that every one can cen see it? Not.
Seriously, the examples i gave are there to line up the claim i did in the first part: V6 SuperCharger is no the glory fire-and-forget solution, most of those performance-increases come with some kind of accordant disadvantage. This should be mentioned.
For some kind of stuff, one does not need >500 posts, but a solid technical comprehension, common sense and some research on the web.
---------- Post added at 03:47 PM ---------- Previous post was at 03:36 PM ----------
@zeppelinrox
What i wanted to express is: Those settings are trade-offs concerning the user experience. This stands in contrast to your explanations, which claim to bring both speed and multitasking to every phone. Forcing the home launcher to stay in memory is a good idea, but it was a one-liner until ICS came, so this can't be the reason for running hundreds LOCs at system startup.
The majority of users has a bunch of other problems, with their device configuration messed up, too much resource-intensive apps installed or a bad-performing ROM installed at some time.
And then there comes this shiny tool, it sounds like the good old american way of life (and is named like it): giving resources here, spending some more memory here - there's no limit, it makes your device blazing fast, it gives you all the things you dreamed of, on your old sluggish device.
Naturally, thats not the case: Yes, there might be useful scenarios, as it allows switching beetween LMK-profiles etc. But lets be honest: Normal users have no clue what they are doing there, playing around and getting more problems than before.
Actually, i like your idea of making those parameters accessible with more ease. As a advanced user, you can archive performance gains, because you know what to set for your specific usage scenario.
Its simply not the fire-and-forget-speedup for android, but people tend to believe this.
// Update:
I added a more diplomatic statement to my original post. Although my technical base argumenttion is the same as before, i guess its good for the discussion if there are less misleading emitotional expressions.
Click to expand...
Click to collapse
OK man XR......I have removed my offensive comment about you, mainly becoz I don't know you and have no basis for the comment I made, and also becoz I think I cannot stand over it, so accept my apology please....
its not my usual form at all!!
You can check my posts!!
But, you were being provocative IMHO, and that is usually a good basis for discussion
OK!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!

irishpancake said:
I have removed my offensive comment about you, mainly becoz I don't know you and have no basis for the comment I made, and also becoz I think I cannot stand over it, so accept my apology please....
its not my usual form at all!!
Click to expand...
Click to collapse
That's okay. As i mentioned above, i had also choosen sharp words, guess there might have been some more suitable writing style.
Nevertheless, i also guess that both sides - positive and negative - of the supercharger script should be discussed, as it is definitely note the magic silver bullet as it is sometimes perceived.

zeppelinrox said:
But you get the idea: the sky's the limit.
And yep... it's like getting a brand new phone.
Click to expand...
Click to collapse
Yes, it's remarkable. Not only one's device becomes at least a Galaxy Nexus, but it also increases display size, brigths up your teeth and pleasures your girlfriend.

You should get this for your girlfriend: https://play.google.com/store/apps/...GwsMSwxLDEsImF0dGljbGFiLkRyb2lkVmlicmF0b3IiXQ..
But if her device is SuperCharged, you're out of a job but mostly because you bore everybody to death.

i try v6 for a day, at night i realized that sms that i send in a day just keeping sending without being sent, i've tried to unsupercharged and reboot phone, but sms still sending, until i restore system to earlier setting than restart the phone, and check for the messages are sent
what is wrong with it?
what version of v6 that support stock rom?
is v6 increase free ram or is it does anything else? because i see no different on free ram that showed in ram booster
one more thing, when i run the script, i see text "it will not run on this rom, but you still can cook bla bla bla" is it normal?
Sent from my GT-I8150 using xda app-developers app

[MOD/EXPERIMENTAL] almost double your RAM

So, it turns out the /preload partition is 500 megs of almost unused space, just to show us a video of Asphalt. So, how about turning it into swap space to almost double the effective amount of memory you have? To use this mod, you must be rooted, and have busybox installed. I recommend the stericson busybox installer https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I would like feedback on whether or not it actually speeds up the device, especially when running graphics-intensive games, and also effects on battery life.
How to install:
1.Be rooted.
2. Get busybox. If you don't already have it, you can get it here https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
3. You must have init.d support. This is built into my NardROM but you can also flash the file attached to this post.
4. Flash the script installer, attached below. NOTE: This will wipe your /preload partition. You can make a nandroid before you perform this step but CWMR doesn't back up /preload. Back up anyway
5. If it's successful, you will see something like the following screenshot when you open a terminal window and execute "free". Notice the swap being used. If you don't have swap enabled it will read 0 available.
To disable the mod:
1. Delete the script from /system/etc/init.d
2. Reflash your Asphalt video from a backup
To disable init.d:
1. Delete /system/etc/install-recovery.sh, /system/etc/init.d (entire folder), /system/bin/sysinit, and /system/xbin/run-parts
Disclaimers:
Using nand memory as a swap can significantly reduce its life. Your phone's internal memory will wear out in years rather than decades
A lot of people argue using Android swap works against the built in memory management of the Dalvik machine
http://forum.xda-developers.com/showthread.php?t=1504774

This is awesome, glad to see people spending time on this device
Tappin' Typin'

'' /vendor '' also has 590,56 Mbyte of space..
what kind of data is there? there are some folders called ''multi_pose_face_landmark_detectors.3'' and ''yaw_roll_face_detectors.3'' ? is this the carrierIQ stuff?
After deleting everything on that partition it says 395,95 mb used, 194,61 mb free.

ludacris1 said:
'' /vendor '' also has 590,56 Mbyte of space..
what kind of data is there? there are some folders called ''multi_pose_face_landmark_detectors.3'' and ''yaw_roll_face_detectors.3'' ? is this the carrierIQ stuff?
After deleting everything on that partition it says 395,95 mb used, 194,61 mb free.
Click to expand...
Click to collapse
I think it's device-specific info for face unlock to compensate for various things like the angle you're holding the phone at and the distance away from your face. And if you'll look a little more closely, you'll find /vendor is symlinked from /system/vendor, it's not actually a separate partition. You should probably put those files back if you want face unlock to work.

Technically I just downloaded some ram
Sent from my SGH-I927 using xda app-developers app On Ics

FYI, this could be a potential source of serious slowness. Swap isn't anywhere near as fast as real RAM.
I wouldn't do this unless you're legitimately having issues you can directly attribute to running out of RAM. It may be useful as Android marches on and demands more and more RAM but for ICS we're already a good clip above the recommended specs.

Same thing I was thinking. I have more than enough RAM but if by some miracle we get something past JB that uses a lot of RAM I'll do this. Nice work on it though!
sent from my captivate glide running ICS (NardROM 0.4 Rooted)

roothorick said:
FYI, this could be a potential source of serious slowness. Swap isn't anywhere near as fast as real RAM.
I wouldn't do this unless you're legitimately having issues you can directly attribute to running out of RAM. It may be useful as Android marches on and demands more and more RAM but for ICS we're already a good clip above the recommended specs.
Click to expand...
Click to collapse
Waiting for the comparison,then

mewatashiakumoi said:
Waiting for the comparison,then
Click to expand...
Click to collapse
So with this hack having been out a couple months now, how are the reviews? Performance increase? Fewer slow downs?

pm2gonzales said:
So with this hack having been out a couple months now, how are the reviews? Performance increase? Fewer slow downs?
Click to expand...
Click to collapse
1) this is not a hack, this is a simple tweak
2) swap file is ALWAYS has a performance decrease effect, no matter what (desktop PC, android phone). The only reason of use is when the device has no enough RAM, and the background processes shall be kept elsewhere
3) android has it's own RAM managing system and methods, simply stick to that as only that will gives you the best performance and user experience
4) "slowdown" occurs when the device runs out of free RAM and starts closing background applications to give everything to the foreground app. When you close the heavy resource use foreground app witch caused android to close every possible background apps, the phone reloads them (launcher, live wallpaper, app drawer, widgets, user apps, etc...) and this is what causes a temporary slowdown, and this is unavoidable, no matter if you use swap or not.

[] 7/19 []AROMA FLASHABLE MOD- ext2 SYSTEM, DATA, CACHE #performance!

MOD IS FOR ANDROID 4.1.2 FOR T-MOBILE NOTE 2 ONLY. DO NOT USE WITH CM. CHANGE LOG AT THE END OF THIS POST
SYSTEM DATA AND CACHE ARE NOW WORKING 100%. ALSO, PLEASE SEE POST #72 FOR FURTHER INSTRUCTION ON SETTING UP YOUR CPU PROFILES APPROPRIATELY TO INCREASE STABILITY AND PERFORMANCE
BIG bug fix in aroma... we have figured out what is causing boot loops. The issue is that twrp is mounting data as ext4 after the mount command is executed. This is an issue with twrp, not aroma. Instructions at the end of this post on how to get around this until we figure out how to cause this not to happen...
As of right now these modifications are only being provided to you for touch wiz. I will not provide links to CM based kernels simply because is more prone to being unstable. Do this mod on CM on your own, and at your own risk. Again, kernels in this thread are touchwiz based, and will not work on CM ROMs.
First of all, let's talk about file systems.
ext2 - (second extended file system in linux) is different from ext3 and ext4 in the sense that it does not use something called journaling. There are other differences as well, but for the sake of showing what kind of performance improvements this file system provides over the latter two (3 and 4), we'll cover what is relevant to us Android users. Data is directly written to a disk as it comes through on ext2 devices.
ext2 does have file limitations compared to ext4. ext4 uses pre allocation of blocks and delayed allocation of data writes and also organizes data a little more efficiently on inodes/blocks. It also has a way to "mark" unused blocks, this reduces IO search times. ext4 also uses a checksum in the journal to improve reliability since the journal is one of the most used files of the disk. In a nut shell, journaling is an overhead feature of ext4 that ensures file/data integrity. This is useful if a system is not shut down cleanly, or the stability of the system has been compromised in some way. And even THAT being said, ext4 has it's own unique issues with data corruption through the delayed allocation feature. Furthermore, and probably the most important to note, those features are really only useful when you have extremely large disk sizes in the exabyte or terabyte range. Our devices are INCREDIBLY small in disk size. ext4 really only outshines ext2 in performance when you are dealing with large databases (and 16 GB, partitioned, is not large... at all). The point to bring up here is that ext4 is only used on these devices out of the factory for total stability. The devices were not designed out of the factory with the advanced user in mind, they were designed with the everyday person soccer mom who needs a "safe" device that will take and handle all kinds of beatings and abuse. The cost for that, unfortunately, is performance. So let's fix that problem.
Here is some more info about it online, an extremely informative article of some test data samples of different files systems in Linux, and their performance.
http://mindplusplus.wordpress.com/2012/01/11/finding-the-fastest-filesystem-2012-edition/
This thread is going to show you guys how to convert your file systems to ext2.
First of all, let's address some useless init.d scripts that I have seen littered all over ROMs to "optimize" ext4.
Code:
tune2sfs -o journal_data_writeback /dev/block/mmcblk0p13
tune2fs -O ^has_journal /dev/block/mmcblk0p13
mount -o remount,noatime,noauto_da_alloc,nodiratime,barrier =0,nobh /system
and so on and so forth for the other two partitions (cache and data)
Now, to be fair, the implementation of this code is not utterly USELESS per say. It does provide a very small amount of IO performance increase. However, this fact still remains:
The op paths in the fstree are optimized for the journal, so simply disabling it makes the code path redundant. And furthermore, the journal-optimized block sizes now have empty overhead (basically you are still using the exact same amount of disk space). On top of that, the performance increase really is not noticeable. Therefore, it is not worth the trouble. And most of the time these "hacks" are tossed into /etc/init.d/ and the user comes alone not knowing to make a back up after flashing this ROM, or has no clue what these actually do (and sometimes the dev doesn't quite understand it either).
ext2's strength is it's simplicity, which goes well with "noop" IO scheduling if the fs itself relies on virtually NO ops. As it comes through, so it is done. The performance benefits of this are absolutely unreal you guys. Your device that used to boot in, say, 30 seconds? - Now boots in maybe 10. That is the real time performance difference we are talking about here. Cut out all the hoopla of ext4.
For those of you who are saying "well what about stability??" my answer is simply this: if you refuse to make a back up of your data and system (recoveries are called recoveries for a reason) you are simply doing yourself a disservice. I have been using ext2 file systems for a long time now, and let me tell you - never will that change. You just can't beat the performance, and the reliability is as sound as you make it - if you are one of those that feels the need to run your processor on performance all day at 2.4 GHz, well you are bringing about your own problems. BUT, like I said, even for the extremist, JUST MAKE A BACK UP OF YOUR DATA!!!! - gravy. :good:
DIRECTIONS>>>>
1.Download and flash your ROM of choice. Or if you have one installed that you like, just boot to recovery and proceed.
2.In TWRP, make a backup of your /system and /data, do not enable compression, just do it how I did it and save yourself some potential headache. If your backup gets ****ed. It’s time to reflash from scratch.
3. Since you will be wiping data, your backup cannot stay on your internal SD. So boot back up, and copy that SOB to your desktop computer. It should be in your internal storage under a directory named “TWRP”. Open it up and COPY, do not cut, the “BACKUPS” folder to your computer and/or external SD card… also, verify both of your backups are actually in that folder before you proceed. There will be one for system and data, and a couple of md5 files, some logs, etc etc… a handful of files. Also, download the two kernels attached in this thread … “TNT-ext2_sys_TMO-TW23-600” and “TNT-ext2_sys_cache_data_TMO-TW23-600” and put them on your EXTERNAL SD CARD. INTERNAL SD IS NOT AN OPTION BECAUSE IT WILL EVENTUALLY GET WIPED IN THIS PROCESS.
4. Boot back to recovery, go to settings, and change the format option to “format using rm –f” ALWAYS ALWAYS ALWAYS FROM THIS POINT ON MAKE SURE THAT IS CHECKED EVERY TIME YOU GO TO RECOVERY
5.After you do that, go back to TWRP main screen, select “advanced” and “terminal” or whatever… it will ask you for a starting directory. Just make sure you are at root, then hit the little button on the bottom that says “select”… it will then take you to a terminal session.
6.From terminal, type the following command then hit enter or “GO”
Code:
“mke2fs /dev/block/mmcblk0p13” (without quotes)
MAKE SURE YOU TYPE THAT CORRECTLY! CANNOT STRESS THAT ENOUGH 0p13 0p13 0p13 0p13 0p13 0p13 0p13 0p13 0p13 ZERO P THIRTEEN SAY IT IN YOUR HEAD
Let it finish. It will only take a couple seconds.
7.After it is done, hit the back button until you are on the main screen on TWRP again… and just for good measure, again verify in your settings that “format with rm –f” is checked. Now go back and select “restore” from main MENU in TWRP. Restore your system backup only.
8. After that is done, flash the “TNT-ext2_sys_TMO-TW23-600” kernel.. again, make sure this is not the sys_cache_data version. Your other two partitions are not formatted yet.
9. REBOOT! Enjoy your system on ext2 and battery and performance improvements. If you only want /system as ext2, stop here. If you are the extremist, and want data and cache optimized as well, proceed.
10. Since your internal storage such as downloads, zedge files, whatever else you have on there, is going to get wipe during THIS phase…. Please make backups accordingly. Your entire internal storage is going to be reformatted – Again, prepare accordingly by backing it up to your external SD card or a desktop computer.
11. Boot back to recovery, at this point your system is already ext2, cache and data are still ext4. So here we go. And I will take you through the long process but the safest.
12. From Recovery MAIN menu, select “MOUNT” and uncheck the boxes for cache and data. Go back to main menu.
13. From recovery MAIN menu, select advanced again, (PLEASE FOR THE LOVE OF HADES AGAIN MAKE SURE YOU HAVE BACKUPS OF YOUR STUFF… if you come crying in here about “hey my downloads and zedge ringtones were wiped wtf bro” I will ignore you and wish death and damnation upon you, you noob. So just don’t do that. Make backups before proceeding)… ok, so again after hitting advanced, select the terminal again, make sure you are at the root directory, hit that little select button. You are now in another terminal session.
14. From terminal, type the following commands (WITHOUT QUOTES and hit enter after each one)… and please again for the love of EVERYTHING HOLY TYPE THIS CORRECTLY AND DOUBLE CHECK CORRECT NUMBERS ARE PUNCH IN AFTER “p” … have this page open while doing this. Look at it, and then look at it again. This is pretty straight forward stuff guys, but a small mistake can be detrimental. So please pay attention.
Code:
“mke2fs /dev/block/mmcblk0p12” <--this is the cache partition
“mke2fs /dev/block/mmcblk0p16” <--this is your data partition, including internal SD.
Now we need to manually create your /data/media/ directory… because it is gone right now buhbye. Rofl
Again, straight forward… without quotes… you get the idea by now
Code:
“mkdir /data/media”
BOOM.
15. Go back to TWRP MAIN menu, and flash “TNT-ext2_sys_cache_data_TMO-TW23-600”
16. Reboot.
17. Success! You are now on ext2 file systems for /system, /data, and /cache.
At this point you have 2 options. After your device reboots, you will be asked to sign back into your google accounts, etc etc etc… data was wiped, so you are at square 1 again with your particular setup. If you wanna set up real quick (like say you are the simple type that just has a few apps, not a whole lot of work to get back to where you were, etc) then maybe a restore isn’t really necessary. You decide. If you neeeed your bajillion million apps restored, no problem. Continue reading.
18. Hook your device up to your PC, find your internal storage. There should be a directory there named “TWRP” if it isn’t there, simply create it.
19. Grab that “BACKUPS” folder and drop it in the TWRP directory of your internal SD.
20. Reboot to recovery.
21. GO TO SETTINGS AND VERIFY “format with rm –f” is still checked… otherwise you are starting this whole instruction over again. Lmaooo… happened to me last night. I’z like…..fakk.
22. All good? Ok now go back to MAIN menu, select restore, and restore both system and data
23. After that is done, MAIN menu… just for good measure…. Select WIPE, then ADVANCED WIPE… and wipe ONLY CACHE once… two… times…. 9 times… whatever tickles your pickle people I’m OCD so even though I know doing it more than once is redundant and unnecessary I do it twice.
24. REBOOOOOOOOOOOOTTTTTTTT
Well wasn’t that fun? Now always keep a backup of your system and data handy (just in case you ever need it, or you have a lockup, whatever the case may be where you feel like your system has been compromised) and you will be a-ok. I’ve personally never had issues with this.
Enjoy.
Download links for modified kernels are up! See below... Thank you morfic for allowing me to post copies of your kernels here. Only things changed are mount points to accommodate the new ext2 paritions. His git is here>> https://bitbucket.org/morfic/note2-tw
UPDATED WITH fsck DISK CHECK FOR INIT.D.... remove the ".txt" extension and drop this file into /etc/init.d and give it full permissions.
Instructions for flashing with aroma installer***********
1. Put aroma installer on external SD card
2. Boot to recovery (make sure you have already flashed the ROM you want to use)
3. Once you are in recovery, make a back up of your current system using the twrp method and CHANGE THE BACKUP LOCATION TO YOUR EXTERNAL SD CARD. Then going into settings, and check the box that says "format using rm -f" or whatever it says... you'll see it once you are there. MAKE SURE THIS IS CHECKED! EVERY TIME you go to do this. The only time you should uncheck this option is if you are trying to revert back to ext4.
***Cannot stress #3 enough you guys, it was the reason you were all boot looping. If you come back here saying you are boot looping, I will e-slap you so hard your face will actually hurt. We will raise up armies against you and those around you. Carnage will ensue. Ok maybe not.... but just make sure every time you go into recovery to do something with this aroma installer that you check that box. EVERY TIME... because sometimes it unchecks itself.
4. Well, easy enough. Now flash the installer. Only use it to convert /system for now, and use the manual method (above) for /data
You can try doing data through the aroma installer, just make sure you check that box in settings of twrp before you attempt to do so.
"That was easy."
AROMA INSTALLER FOR EXT2
http://tweaked.mediafire.com/download/ody7u8wxzarjv37/ext2inizer.zip
md5 = EB0EB296B06DF5BEFFAA26D1D39291DA
Seem appropriate to start a change log for this.
July 19, 2013
Stock kernel added as an option in aroma for those who cannot run morfic
No more options in aroma to only do /system. You now can only do all 3.
July 18, 2013
K this should be nailed down now.
July 17, 2013
1. Bug found. Boot looping issue has been identified and pinpointed. See flashing instructions. (above)
July 16, 2013
1. Misc code fixes in aroma (more like optimizations really) for the backup logic
2. fsck script for init.d updated - calls to /system/xbin now
3. Some more manly stuff
Previous Versions
1. Initial release and various small optimizations with aroma

Great write-up. Interesting info
Sent from my SGH-T889 using xda app-developers app

So much reading
Sent from my SGH-T889 using xda premium

Just a quick update on this… I want to give you guys an idea of just how much overhead is generated by your ext4 file system.
Right now I am currently sitting at 87% battery, 5 hours off the charger, and 1 hour and 3 minutes screen on time.
This is only with /system mounted as ext2. /data and /cache are still mounted as ext4.
To give you a comparison (and my usage throughout the day is 100% consistent, so I am a good test model for this particular thing) 5 hours off the charger, at 82%.... I am usually looking at about 50 minutes of screen on time.
In short, simply changing my /system partition to ext2 has saved me 5% battery at this point in my daily activities, while still gaining 12 minutes of screen on time.
So converting that….
Improved screen on time by 25%, and overall system usage and battery drain has improved by about 60%
That is just /system
EDIT** screen of /cache successfully mounted as ext2
{
"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"
}

Hi I am looking for a long time to convert my SD card and my system to Ex format because I cannot use my 32 gb sd card efficient for example my limit is 5gb would that fix my problem?

Since you like to convert between filesystems, do us all a favor and run Bonnie++ on them.
http://forum.xda-developers.com/showthread.php?t=1169910
Maybe there is a noticeable difference on Note2 hardware, but in the past, it hasn't been the case. To keep things "even", run from adb shell in recovery. That way you don't have the pesky OS overhead etc... Just format a partition, run the test, copy/paste the results, format and run again.
Now, that IS a benchmark and all the usual benchmark caveats apply, however, it is also a useful start to determine how the hardware handles the various cases.
Speaking from experience on previous phones, particularly the Samsung Vibrant, the speed difference wasn't really noticeable. You could see it in benchmarks, but in real life, if I were to write a boot script that would randomly change them back and forth, 99% of users would never notice. Now, the downside of ext2 did rear it's ugly head a few times, with users getting stalled boots and having to run fsck at boot after a crash, or power loss. Complete filesystem loss is possible in theory, but I've never seen it, so let's just discount that one. Early mods didn't account for needing to run fsck and would stall the boot, to the user it looked bricked. If you do end up needing fsck, it can make those "long" ext4 boot times look pretty fast..... However, none of the failure scenarios are really all that likely, so let's stick to performance.
As I said, Note2 hardware is different. Just putting the past out there. This is OLD ground. Perhaps the hardware makes all the difference..... From some of the previous testing back in the day, JFS and Reiser looked like good candidates for phones.... I don't know if anyone ever actually tested running Android on them though.

patches said:
Since you like to convert between filesystems, do us all a favor and run Bonnie++ on them.
http://forum.xda-developers.com/showthread.php?t=1169910
Maybe there is a noticeable difference on Note2 hardware, but in the past, it hasn't been the case. To keep things "even", run from adb shell in recovery. That way you don't have the pesky OS overhead etc... Just format a partition, run the test, copy/paste the results, format and run again.
Now, that IS a benchmark and all the usual benchmark caveats apply, however, it is also a useful start to determine how the hardware handles the various cases.
Speaking from experience on previous phones, particularly the Samsung Vibrant, the speed difference wasn't really noticeable. You could see it in benchmarks, but in real life, if I were to write a boot script that would randomly change them back and forth, 99% of users would never notice. Now, the downside of ext2 did rear it's ugly head a few times, with users getting stalled boots and having to run fsck at boot after a crash, or power loss. Complete filesystem loss is possible in theory, but I've never seen it, so let's just discount that one. Early mods didn't account for needing to run fsck and would stall the boot, to the user it looked bricked. If you do end up needing fsck, it can make those "long" ext4 boot times look pretty fast..... However, none of the failure scenarios are really all that likely, so let's stick to performance.
As I said, Note2 hardware is different. Just putting the past out there. This is OLD ground. Perhaps the hardware makes all the difference..... From some of the previous testing back in the day, JFS and Reiser looked like good candidates for phones.... I don't know if anyone ever actually tested running Android on them though.
Click to expand...
Click to collapse
Well, I wouldn’t really call this benchmark irrelevant… but it is certainly not needed because the logic and theory behind the two file systems is sound and proven.
Of course you are not going to SEE a difference when opening, say, your messaging app even tho it is mounted to an ext4 system. But the performance benefits are still there, the reduced IO operations on your disk are real (that is reflected in battery life, as I mentioned above), and your boot times being faster is also a real time that you can see. Less cpu cycles, less overhead, more efficient. The operation is still taking place, is what I am saying. And having a powerhouse processor like these that uses more juice to complete a task than the devices of old (two years ago, rofl) is all the more reason to optimize as much as possible.
As far as the “instability”, like you, I have not personally experienced any of the horror stories of data corruption or a total system loss at a catastrophic level, nor have I ever had problems simply booting the device.
All I can say is this fact remains: ext2 > ext4 when it comes to performance. My whole idea behind this stems from the fact that as root users of these machines, we have the luxury of backups, and therefore we have no reason to not run a truly optimized (performance-wise) file system. Ext4 is a waste of disk space and cpu cycles on these devices.
Just my opinion of course. I’ll run the benchmark, however, just because I am curious to see what it says.
b rrrrr bbbb

This is work is for all kernels?
Sent from my SGH-T889 using xda premium

jpeps said:
This is work is for all kernels?
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
This will work for all kernels that support ext2 (most should)
It will still require you to change the mount points, however. That I cannot do for you.

Updated.... Successfully mounted ext2 file system for /data/
Holy monkey balls r/w speeds are nuts. Device booted in about 15 seconds.
I'll have a battery stat report tomorrow...

Please make video how to do this or how to
Thanks
Sent from my SGH-T889 using xda premium

Admiral Sir Manley Power said:
Well, I wouldn’t really call this benchmark irrelevant… but it is certainly not needed because the logic and theory behind the two file systems is sound and proven.
Of course you are not going to SEE a difference when opening, say, your messaging app even tho it is mounted to an ext4 system. But the performance benefits are still there, the reduced IO operations on your disk are real (that is reflected in battery life, as I mentioned above), and your boot times being faster is also a real time that you can see. Less cpu cycles, less overhead, more efficient. The operation is still taking place, is what I am saying. And having a powerhouse processor like these that uses more juice to complete a task than the devices of old (two years ago, rofl) is all the more reason to optimize as much as possible.
As far as the “instability”, like you, I have not personally experienced any of the horror stories of data corruption or a total system loss at a catastrophic level, nor have I ever had problems simply booting the device.
All I can say is this fact remains: ext2 > ext4 when it comes to performance. My whole idea behind this stems from the fact that as root users of these machines, we have the luxury of backups, and therefore we have no reason to not run a truly optimized (performance-wise) file system. Ext4 is a waste of disk space and cpu cycles on these devices.
Just my opinion of course. I’ll run the benchmark, however, just because I am curious to see what it says.
b rrrrr bbbb
Click to expand...
Click to collapse
Fewer instructions doesn't necessarily == greater performance. There was a lot of time between ext2 and ext4, a lot of work was done on the underlying code in that time. In many tests, ext4 reads out-perform ext2. As the storage is by far the slowest part of any computer, using a few CPU cycles for better caching etc. is often well worth the tradeoff. Performance of the two is by no means a given, this was hotly debated long ago and the same issues remain. I'm an open minded sort of person, so I'm not saying it isn't possible that it makes a bigger difference now.
One note... while current CPUs use more power at the higher clock speeds, they also complete the tasks faster, and thus, spend less time at higher clock speeds, getting back to sleep faster than older CPUs. Modern chips also have features that older chips did not, like sleeping individual cores. There are a LOT of variables at play, it's never as simple as that.

ttabbal said:
Fewer instructions doesn't necessarily == greater performance. There was a lot of time between ext2 and ext4, a lot of work was done on the underlying code in that time. In many tests, ext4 reads out-perform ext2. As the storage is by far the slowest part of any computer, using a few CPU cycles for better caching etc. is often well worth the tradeoff. Performance of the two is by no means a given, this was hotly debated long ago and the same issues remain. I'm an open minded sort of person, so I'm not saying it isn't possible that it makes a bigger difference now.
One note... while current CPUs use more power at the higher clock speeds, they also complete the tasks faster, and thus, spend less time at higher clock speeds, getting back to sleep faster than older CPUs. Modern chips also have features that older chips did not, like sleeping individual cores. There are a LOT of variables at play, it's never as simple as that.
Click to expand...
Click to collapse
While I agree with some of what you said, the fact of the matter is ext2 out performs ext4. Mostly because even though ext4 has all of these nifty little pre-allocation for blocks, and inode/block numbering, and even a function in place to mark blocks that are not being used so it knows where exactly to search when a request is made on the disk (this is where that read performance comes in that you speak of)... it is still slower because of journaling. And you still have overhead IO operations. And disabling journaling doesn't fix that entirely, it just makes it more unstable.
HOWEVER... you are still wrong, and whoever debated that ext4 outperforms ext2 on these devices, was also wrong. Let's break this down a bit. So you can understand where my logic is coming from to make that conclusion.
First of all, I will say this, and it is fact. The ONLY reason google switched to ext4 was because they needed a file system that could handle MUCH MUCH larger disks. ext4 has far greater file capacities, and also overall disk capacity than ext2. We are talking exabytes, terabytes, not measily 16 GB devices such as these.
A full odexed ROM on this device, for example, has a total of about 1900 system files, it is less if you are de-odexed (dex files are moved to /data/dalvik-cache). ext2 has an overall file subsystem limit of 32,000, I believe (off memory please correct if I am wrong) and ext4 has some number ridiculously higher than that... I think it is actually 64,000 if I'm not mistaken. Why is this relevant? Because the ONLY reason ext4 has ALLLLLL those cool little extra overkill organizing features is because it is designed to handle data and file clusters that are literally 100 times larger (or even more) than a measily little Android OS that takes up 1.2 GB of space on a 1.7 GB partition ... ext4 is overkill for these devices and the only reason it is implemented by Samsung and Google is because they want it to be as reliable as possible. The average user will not know how to make a backup, root, or restore a backup if something goes wrong.
ext2 is simple and fast. The fact that it was developed years ago doesn't mean anything. "Improvements" in these types of things are most of the time brought about by some type of demand, not necessarily because it is faster or more efficient. In ext4's case, the demand was larger storage devices and a rock solid stable file system.
If you need another reminder of proof.... again read my reports of boot times and battery life. That should be enough evidence to undo whatever you may have read in the past about what is best for either.
Apply applications and modifications as necessary. I'm not running warehouse full of servers... it's a handheld computer with a very small operating system and disk. ext2 will outshine ext4 in any application like this.
Were I running servers, though, or were I Google.... yeah.... I'd probably be looking at ext4.
Just because the device was delivered to you with this or that, doesn't mean it is the best or fastest in that condition. Variables, again, were developers taking into account the every day user. Thus, they decided on ext4. You and I, are not the every day user.

I think it's time I leave this thread, you seem to be getting worked up over my little posts. I'll try once more though...
Search my history, I've done a LOT of work on various filesystem based things. Remember my mentioning the Vibrant? I contributed to Project Voodoo and did other related mods back then. ext2/ext3/ext4 with various options, installer based stuff, etc... And, from experience, on that particular phone, the day-to-day difference was very small. As I said, the Note2 is a very different beast, but the various filesystems haven't changed that much. I'll probably test your mod when there's an installer, I don't have time to fiddle with formatting everything myself these days.
As for battery life, I was leaving it alone as I considered it off topic.... The Android battery meter simply isn't accurate enough for the comparisons you are talking about here. It's an educated guess based solely on the voltage at the moment. Connect a logging ammeter inline and you might have something to go on. But the % meter is a red herring for any other comparison.
Boot time, well, I did say I thought it could be faster. The question is one of degrees. Frankly, the boot time isn't really that interesting... I don't boot my device that much.
What I care about is performance in general use and, to some degree, just pure faster I/O. As I mentioned, it's the slowest part of any system, making it faster is always nice. The system loads during boot are kind of a special case... What I care more about are things like how fast I can push records in/out of a sqlite DB from my app, copy files about, etc.. I suspect it will be faster on ext2, particularly for writes, the question is how much? Is it enough that I would notice on a daily basis? And yes, it depends greatly on the user, what apps they have installed, running in the background, various system options that would use memory, state of the cache, etc... But if it is a significant boost for the general case, it should be noticeable to the user.
There is also the error case... if you are writing to the FS and pull the battery.... what happens? ext2 gets angry when you boot. ext4 replays the journal, you might lose data, but you don't have FS issues and it doesn't refuse to mount until you run fsck on it. Now, it's possible ext2 has improved some since then, but do you have a boot check to ensure it's not an issue? You should if you want a general use setup. I'd rather have the device stall a bit while booting and run an automated fsck than just refuse to boot. As I said, this situation isn't common, but it was one we ran into back in the day, so I'm mentioning it for the sake of any users that follow your steps or use any flashables you set up. Please do include an init.d script to handle it. You can find some in the various mods from back then. I don't think people were losing data, but really, it's simple to just check for it and fsck at boot time. The fsck issue and the fact that the performance difference wasn't huge, led most to just use ext4 as it was faster than ext3 and didn't require boot checks. But, as they say, that was then. The situation could have changed. I'm curious to see what comes of this. Don't take me the wrong way, I'm trying to provide info so you don't end up getting caught on stuff I've seen before. And in typical user fashion, if this happens, you will have people coming here yelling that you bricked their phone, blah, blah, blah.
And now you see why I don't do much dev stuff on here these days. Good luck though.

Lol... Bro I'm opinionated and although I disagree with much of your statements, particularly about battery life and so forth (which isn't a percentage based on a bunch of different variables, it is actually quite simple and pretty accurate - x volts = x % ... Not hard to compute... Its also pretty straight forward logic, and monitored by the kernel, relayed through the OS... easy), don't take it as anything personal. I enjoy the back and forth technical conversation.
If you are running a note II, though, you should give this a shot. Really and truly I believe you'll have a positive experience with it.
I'll make a script later for init.d so we can reduce issues even more. I used to run ext2 "back in the day" as well and personally had no issues with it whatsoever. The key is to run a stable kernel, though, to be honest. There is no reason to not be able to run your device cleanly for weeks on end without a lockup or reboot. That is key, stable kernels.
Give it a shot, and see for yourself.
And stick around here... And share your insight. Seriously

Any luck on the kernels i cant find the download for them?

HOGWILD said:
Any luck on the kernels i cant find the download for them?
Click to expand...
Click to collapse
Yes waiting to hear back from a dev about posting his work here. He is a friend of mine, but he is also busy.

Updated OP with an fsck script for init.d... this is going to slow your boot times a bit, but very much worth it. Thanks tabbal for the suggestion (a good one indeed).
Still waiting to hear back from morfic about his kernel... I dont think he will have a problem with it but I respect him and his work, so we'll have to wait.
EDIT*** links are up, thanks morfic...
LIKE A BAWS

OK.... So here is my battery update....
16 hours off the charger...
48% left....
4.5 hours screen on time...
Ummm. Yeahhh... Lots of unnecessary CPU usage going on under the hood on ext4 I would say. That is a HUGE difference from what I typically see. Almost an hour if screen on time gained.

Cool
Dose it work on all kernels ???
Sent from my SGH-T889 using xda premium

Random Builds and Development

Hi all.
This thread is for random builds and development. There is no agenda other than to keep the Kindle Fire alive for the few of us that remain. This thread is not meant to support any specific ROM. I hope this is okay with the forum administrators.
With that said, please join in. We're all in this together.

Cm-12.1 2015-10-15
I made a public viewable folder on my Google Drive for Android stuff here https://drive.google.com/folderview?id=0B7BjC3Ky49TVcjdZQlpHYV9JWXc&usp=sharing
I uploaded a build of CM-12.1. The file name is weird so I will explain (in case you care):
cm-12.1-20151015-UNOFFICIAL-kad-rsm-O3-mo3-wifi-otterx.zip:
kad = kernel compiled with ArchiDroid toolchain
rsm = ROM compiled with SaberMod toolchain
O3 = almost all compiled with -O3
mo3 = more optimization, specifically as much of JustArchi's compiler flags as would work. The '3' is my third attempt to add more optimizations.
wifi = hack to make wifi work without doing a clean install, that is, there is a script, fix-mac.sh, which I think only gets run with a clean install. My hack was simply to copy the file that the wifi driver wants to the name that it wants. This should allow either dirty or clean flashing.
Suggestions:
* Change the animation duration levels in Developer Options to 0.3x or less.
* Use the Noop I/O scheduler for regular things like reading a book (that's why you bought a kindle, right) or browsing the web.
* Use the Deadline I/O scheduler for interactive things like playing a game.
* If you like Gapps, I suggest OpenGapps or TK Gapps. I have not tried this ROM with Gapps.
* You will need to get a third party program to change kernel settings. I like Kernel Adiutor.
The issues:
* Don't use the brightness slider in quicksettings. If you do use it, the status bar goes away and leaves the top part of the quicksettings panel in its place. I suggest disabling the slider and using the brightness control in the status bar settings. I'm not sure if this is a new bug or the result of too much optimization.
* There are no app snapshots in the recents switcher. This may be internal to Android as a way to save memory for low RAM devices, or it may be a bug in CM.
* The Kindle Fire just doesn't have enough RAM (or rather Android is just too freakishly bloated). Attempting to run memory intensive apps will likely result in them crashing or running slowly because the RAM they are using is being swapped to ZRAM. You may be able to adjust the ZRAM size and get better results.
There you have it. I hope you find it useful.

Ah. I just realize this thread. Going to try the 12.1 now
Sent from my Nexus 5 using Tapatalk

@pfederighi. Running fine and fast on the first boot. I clean flashed it without gapps.
After I flash Pico opengapps, it's rather slow now, but probably adjusting things. I'm going to use this for a while and see.
I M using privacy guard to block wake up and keep wake permission for (almost) all apps, since I don't use app that need to do that. Been set it up like that since ur cm11. Gave me very good battery life.
Will post some screenshot later
Thanks for this
Sent from my Nexus 5 using Tapatalk

Here you go. It's getting faster now.
Is there any downside of using higher zram? Default it 60mb, I change it to 1gb. Using noop as suggested. Low memory killer should be okay I think, but previous cm11 use much lower than this (120mb). Although I changed it to around 100mb too.
{
"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"
}
Edit. Oh one more thing. I try out the brightness slider, working just fine on mine. Ur issue probably because of dirty flash?
Sent from my Nexus 5 using Tapatalk

Battery life looks good.
Sent from my Nexus 5 using Tapatalk

dokie80 said:
Here you go. It's getting faster now.
Is there any downside of using higher zram? Default it 60mb, I change it to 1gb. Using noop as suggested. Low memory killer should be okay I think, but previous cm11 use much lower than this (120mb). Although I changed it to around 100mb too.
View attachment 3514625View attachment 3514626View attachment 3514627
Edit. Oh one more thing. I try out the brightness slider, working just fine on mine. Ur issue probably because of dirty flash?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I tried increasing ZRAM to 100 MB, I think, and found some things crashed, like the Amazon Underground and Monument Valley apps. I think there wasn't enough real RAM to allocate that much for ZRAM. I changed it back to 60 MB and both of those apps worked again, though slowly.
I'm not sure if I had KSM (kernel samepage merging) enabled. If I didn't, I probably should have. KSM can free up quite a bit of RAM, at the cost of CPU. Though, one can change the parameters for KSM and perhaps find a nice compromise.

Hello,
I'm following your instructions but when I start Kernel Adiutor I get the message No root available. I tried installing SuperSU but it fails when trying to update its binary. Any suggestions?

kev716 said:
Hello,
I'm following your instructions but when I start Kernel Adiutor I get the message No root available. I tried installing SuperSU but it fails when trying to update its binary. Any suggestions?
Click to expand...
Click to collapse
U don't need supersu. There's su app built in. Try installing Adiutor again, I remember I had that issue too, but I re open it, and it ask superuser request.
Su setting is on developer options. It's enabled by default.
Did u open kernel Adiutor and supersu from notification panel? (the one that tell us that xxx app is installed). I did, and it give that error. starting the app from home screen and app drawer works fine. Dunno if it's related to notification panel one, or u just need to open it twice.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
pfederighi said:
I tried increasing ZRAM to 100 MB, I think, and found some things crashed, like the Amazon Underground and Monument Valley apps. I think there wasn't enough real RAM to allocate that much for ZRAM. I changed it back to 60 MB and both of those apps worked again, though slowly.
I'm not sure if I had KSM (kernel samepage merging) enabled. If I didn't, I probably should have. KSM can free up quite a bit of RAM, at the cost of CPU. Though, one can change the parameters for KSM and perhaps find a nice compromise.
Click to expand...
Click to collapse
I don't use that many app, so dunno have experience with crashing. I use 1gb zram since ur cm11, although I don't see any benefit. No crashes though.
I'll try 256mb later then.
I thought swap is remmended at 2x ram on Linux?
Sent from my Nexus 5 using Tapatalk

dokie80 said:
I thought swap is remmended at 2x ram on Linux?
Click to expand...
Click to collapse
Indeed, but that is swap to disk. ZRAM is the method of allocating an area of RAM that is treated as a compressed disk and using it as a swap file system. It is a way of using limited RAM more efficiently, at the expense of CPU time, but it is still using RAM. So, on our device, 100 MB is eaten up by graphics buffers and proprietary firmware. Another ~300 MB is eaten up by Lollipop itself. This leaves us with ~100 MB for user programs, which is not a lot. If you allocate ZRAM at 60 MB, that leaves 40 MB of regular RAM + ~120 MB compressed on the ZRAM drive for programs. This gives us more memory to work with, but effectively 75% of it is compressed, which means every time it's read, it needs to be decompressed, and every time it's written, it needs to be compressed. The memory manager of linux does a great job of making it efficient, but it still slows down the system.
If Android were to actually swap to disk, which it can do, it would wear out the solid state media very quickly because there are a limited number of writes before the media no longer works. There have been great advances in the field of solid state technology such as Intel's and Micron's new 3D XPoint (it's awesome, check it out). So, in the near future this may no longer be an issue, but it doesn't help our old devices.
If you really do need the memory, you can make a swap file on an externally powered USB hard disk, mount the drive, and then issue a `swapon path_to_your_swap_file` from the terminal. I've done it before. It's painfully slow, but it works.

Thanks for the explanation.
Cmiiw, so zram is on the ram itself?
So if I'm not using many apps at the same time, probably better to use zero zram? Assuming the free RAM is enough for the app.
about KSM, does it mean that with KSM enable, ram that is used for the system can be put on zram (compressed)? And by that, does it mean that zram is used only for user apps?
Sent from my Nexus 5 using Tapatalk

dokie80 said:
Thanks for the explanation.
Cmiiw, so zram is on the ram itself?
So if I'm not using many apps at the same time, probably better to use zero zram? Assuming the free RAM is enough for the app.
about KSM, does it mean that with KSM enable, ram that is used for the system can be put on zram (compressed)? And by that, does it mean that zram is used only for user apps?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Regarding not using ZRAM:
From what I understand, yes, if you have enough RAM without using ZRAM, then it's generally better to not use it.
Regarding KSM:
KSM compares the specified number (default 100) of RAM pages per check. If it finds that any RAM pages are identical, it merges them to a single copy-on-write page (that is, they will remain merged until a process attempts to write to it, at which point it'll be copied back to separate pages). Since there are often many read-only pages that happen to be identical, it tends to be very effective.
It runs at the specified interval (default 500ms). I've found that increasing the interval to 750ms or even 1000ms significantly reduces system load with no appreciable difference in the amount of RAM freed.
Because for some CPU & RAM intensive programs I've noticed slightly worse performance with KSM running, I have sometimes run KSM for a few seconds to free up the RAM, disabled it, and then run said program. It seems to work rather well. I suppose I could also have left it running and just increased the sleep interval to a higher amount, say 10000ms.
In general, KSM will free up about 10% of the total RAM, which in my experience is true.

CM-11.0
I've uploaded another CM-11 build. The kernel is compiled with ArchiDroid, the ROM with Uber. I think it is slightly faster than the previously posted all SaberMod build. It still suffers from all the regular CM-11 quirks on our device. The direct link: https://drive.google.com/open?id=0B7BjC3Ky49TVVGF3TFJ0ckJzYjA
Try as I might, I have failed to find a solution for the annoying wpa_supplicant error. That is, about every 2 seconds, `logcat` will spit out the following: "E/wpa_supplicant( 490): recvfrom(ctrl_iface): Try again". The 490 is the process ID number, yes?. I've found various references online, but no solutions. Does anyone know what the issue is or how to fix it?
And now for something completely different:
Is there anyone who would be interested in a CM-10.2 OtterX build? Since the general consensus is that CM-10.2 was noticeably faster than CM-11 (I remember it being so), I thought it'd be a good challenge to convert it, but only if there's a desire for it. Please let me know.

Cm10.x is better in performance, but imo, the sound is better/louder on cm11-12.
But no privacy guard on JB, right? I can't get similar battery life on JB, even using deep sleep apps. Unless you can bring privacy guard to cm10, I'll stick on 11+
What cm-11 quirks are you talking about?
Thanks for this.
Sent from my Nexus 5 using Tapatalk

dokie80 said:
Cm10.x is better in performance, but imo, the sound is better/louder on cm11-12.
But no privacy guard on JB, right? I can't get similar battery life on JB, even using deep sleep apps. Unless you can bring privacy guard to cm10, I'll stick on 11+
What cm-11 quirks are you talking about?
Thanks for this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.

pfederighi said:
I've uploaded another CM-11 build. The kernel is compiled with ArchiDroid, the ROM with Uber. I think it is slightly faster than the previously posted all SaberMod build. It still suffers from all the regular CM-11 quirks on our device. The direct link: https://drive.google.com/open?id=0B7BjC3Ky49TVVGF3TFJ0ckJzYjA
Try as I might, I have failed to find a solution for the annoying wpa_supplicant error. That is, about every 2 seconds, `logcat` will spit out the following: "E/wpa_supplicant( 490): recvfrom(ctrl_iface): Try again". The 490 is the process ID number, yes?. I've found various references online, but no solutions. Does anyone know what the issue is or how to fix it?
And now for something completely different:
Is there anyone who would be interested in a CM-10.2 OtterX build? Since the general consensus is that CM-10.2 was noticeably faster than CM-11 (I remember it being so), I thought it'd be a good challenge to convert it, but only if there's a desire for it. Please let me know.
Click to expand...
Click to collapse
I would be interested in a 10.2 build.
And of course thx for all your interest in keeping this device alive. Great little tablet.

pfederighi said:
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
Click to expand...
Click to collapse
I don't remember facing those issues. About have to press button several time to wake up, sometimes it just need 1-3 secs for the screen to wake, probably because of low cpu clock too.
I remember using 10.x that has privacy guard, but it's different from 11.x. As long I can block wake up and keep wake, I'm sold.
As the sound,
Anyway, since you re offering otterx version, I definitely will test it out, since it's easy and won't require a pc.
Thanks
Sent from my Nexus 5 using Tapatalk

pfederighi said:
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
Click to expand...
Click to collapse
I thought CM11 had more free ram than CM10?

VTCruzer said:
I thought CM11 had more free ram than CM10?
Click to expand...
Click to collapse
10 is faster, much more responsive than 11. For free RAM I'm not sure, but AFAIK, free RAM can be set using minfree. More free RAM doesn't mean it will run faster, it just mean less crash on apps and more capable on running apps that need high ram.
@pfederighi already explain about the zram. Using that, we can get more free RAM, but will use More cpu to decompress the zram when accessed. So, probably not faster than without using zram.
If we really want to compare the ram, I suggest to compare the usage (system), not the free one.
Sent from my Nexus 5 using Tapatalk

I too would be very interested in a 10.2 build for otterx

General GSI runs nicely on the S22

{
"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