Develop Bugs

[] 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

iFive Air Tablet - 9.7" 2048x1536px - RK3288 - Android

FNF iFive Air 9.7" Tablet​
CPU: Rockchip RK3288 Quad-core Cortex-A17 processor, 1.8 GHz (seems to be locked to 1.6 GHz for heat/battery concerns without much loss in performance, maybe lower binned processor)
GPU: Mali-T764 (or Mali-T760MP4 - 4 core GPU)
Screen: 9.7", 2048 x 1536 (4:3), Capacitive, Retina, IPS, 10-point multi-touch
Memory: 2 GB DDR3 RAM (not sure if LP or not), 16/32 GB eMMC, microSD, OTG
Networking: WiFi 802.11ac, Bluetooth 4.0, Miracast
Camera: 8MP back camera , 2MP front camera
Sensors: Gravity Sensor, Gyroscope
Battery: 8200mAh
Net weight: 534 g / 18.84 oz
Size: 240 x 168 x 7.5 mm (review measured at 240 x 168 x 7.8 mm)
OS: Android 4.4.4 (RK3288 are supposed to get 5.0, so this device might as well)
Rebranded versions: HaierPad 971 in Europe
Official Links
Main Page
Product Page (Tab Order: Info / Pics / Specs / Intro Video / Firmware / 16 GB TMall / 32 GB TMall)
5Fans Subforum
Reviews
iambillbil (Chinese - use your favorite translator -- Chrome built-in or Bing seem to work well, Google Translate is slower)
Appearance
Hardware Evaluation
Performance Evaluation
Game Evaluation
Endurance Evaluation
Other
iFive Air Skin Review
Mu-Yun's Review
iMP3.net Review
Videos
Official Intro Video (YouTube Version)
Unboxing
Unboxing and Tactile Test from HongKongGeek
Accessories
Cases
There is an "official" case for the tablet -- it's a PU leather flip case in 5 colors (black, white, blue, pink, and gold) that can be found on AliExpress and other similar sites searching for "iFive Air case". There are two brands of the case that can be found -- one with a brown interior with volume holes that seem off to one side based on the pictures. The other one has a gray interior with centered volume holes. I got the gray one and it actually fits quite well. There are some areas that aren't protected well (mostly the lower right corner. I ordered the "black" one, which is actually much more of a dark gray. It actually really looks good with the white front and light gray back. The cutouts match very well (better than it looks in the pictures).
iPad Air/iPad 5 cases -- as the dimensions are close (240 x 169.5 x 7.5 mm), some of those cases might work as long as you take care to get the ones that leave the top part of the tablet exposed for the different port layout -- they may also not work. According to iambillbil in his "Appearance" review, you can use the iPad Air hard plastic and silicone covers as the buttons and cameras line up (although, from his pictures, not quite exactly) but not the Apple shell covers (I assume he means the magnetic attach ones, but I'm not sure). I ordered an iPad Air Origami case from AliExpress. Even thought the dimensions match, the side profile of the tablet is different from the iPad Air, so it didn't fit in the case at all. The case needed the slightly more rounded profile shape.
universal 9.7" tablet cases
Screen Protectors
The tablet comes with a screen protector installed. iPad Air protectors should work as well, but they will generally have a cutout for the home button which is unneeded for this tablet.
ROMS
Official Firmware
Official 4.4.x Firmware
Official 5.1.x Firmware
Official 6.0.x Firmware
Official Alternative Firmware
My Custom ROMs
4.4.x
iFive Air 32GB Nexus v1.1.0.x (Bare Base)
iFive Air 32GB Nexus v1.1.2.x (Bare Base)
5.1.x
iFive Air 32GB Nexus v2.0.6.x (Bare Base)
CrewRKTablets' ROMs (Thanks Oma!!)
4.4.x
Oma's Customized Stock v1.x
Oma's Customized Stock v2.x
Oma's OmniROM (RK32xx Generic)
Oma's Air AOSP
5.1.x
Oma's AOSP 5.1.1 v1.1
Oma's CM12.1 v1.2.1
Oma's 5.1.1 Custom Stock v1.0 (based on 2.0.3)
6.0.x
Oma's 6.0.x AOSP Based
Oma's CM13 Based
Custom Recovery (Thanks CrewRKTables!)
CWM 6.0.5.1 / TWRP 2.8.3.0
CWM 6.0.5.1 / TWRP 2.8.4.0
TWRP 2.8.4.0 for 5.x+
TWRP 3.0.0 for 6.0+
Known Issues and Bugs (All ROMs)
moved to separate post
Tutorials
Official Firmware Flashing Instructions (Translated)
Firmware Customization Tutorial
Rooting the iFive Air
Resources
RK3288 Specs
Mali-T760 Specs
CNX-Software RK32xx News
Dev Resources
Firefly Dev Board Wiki
Linux Rockchip Wiki
Androtab
Linuxium
CrewRKTablets Dev Forum
Freaktab
*** Remember, anything you do to your tablet is AT YOUR OWN RISK -- following any procedure here may result in bricking your device ***

Reserved

Official Firmware Flashing Instructions (Translated)
This document is included in the official firmware flashing tool, but in Chinese. There are pictures in the document. Here is the translated text (between Google and Bing)
To get the software to be in English instead of Chinese, go into the config.ini and change the [Language] > Selected value from "1" to "2".
Step 1: The Pre-Upgrade Considerations
Make sure that the tablet has enough power, not in a low power state. (>30% of power)
RK3188 RK3288 upgrade tool and can not be universal.
Make sure USB debugging is turned off ("Settings > Developer Options > USB debugging " should be unchecked)
Make sure USB connection type is set to "Mass Storage"
If the connection to the computer automatically switches to upgrade mode fails , reconnect again.
Please copy important files to another storage device in advance, the upgrade will format, to prevent loss of important documents.
Step 2: The Driver Installation
machine turned on, press the switch button 15S, during machine shutdown will be black, but do not let go.
Connect the USB to the computer, and other computer recognizes the device let go (to windows7, for example), as shown below:
If you do not pop up this option, select the desktop or the Start menu, computer / right click My Computer, and select Manage.
After opening management, select the Device Manager, which can be seen when an unknown device.
Driver Installation
Facing the unknown device, right click and select Update Driver Software.
Click the Select Browse my computer for driver software. Note: You can click on the automatic search.
Click Browse and select the location of the driver
Upgrade tools folder has a folder Driver, Driver folder contains a version upgrade drive, if your computer system is 64, select X64; if it is 32, select X86, then according to operating system selection.
Pop up whether to install this device software, select Install.
After the installation is complete, in the Device Manager can see the driver Rockusb Device.
Step 3: Firmware Upgrade
Extract the downloaded iFive Air upgrade kit if not done already.
Open FactoryTool.exe [UpdateTool.exe is referenced in the document but outdated]
Select the "firmware", and select the path of the next firmware.
Check the "repair" option.
Select the "Start" option.
Connect the tablet to the PC via USB
The machine will automatically enter download mode and download the firmware.
After the firmware download is completed, there will be a green icon prompt, unplug the USB cable. (Otherwise the machine will go into upgrade mode). [This is super important, because otherwise it will switch to upgrade mode and keep doing factory resets on the device. until you stop it].
Select "Stop" option, and then exit the upgrade program.

GPU question.
Hi,
I have a question about the GPU. Hope anyone can answer.
On their website its advertised as Mali-T764-16 core GPU (@326GFLOPS)
Shouldn't that be Mali-T760 MP16? As far as I was aware Mali T-764 is a quad core GPU (@ around 90GFLOPS)
Any idea which GPU is on this tablet, I'm planing to buy this tablet.(or Pipo P9).
Thanks.

pal2342 said:
Hi,
I have a question about the GPU. Hope anyone can answer.
On their website its advertised as Mali-T764-16 core GPU (@326GFLOPS)
Shouldn't that be Mali-T760 MP16? As far as I was aware Mali T-764 is a quad core GPU (@ around 90GFLOPS)
Any idea which GPU is on this tablet, I'm planing to buy this tablet.(or Pipo P9).
Thanks.
Click to expand...
Click to collapse
Everything I've seen listed has it as the Malt-T764. However, if you got the ARM/Mali website, no such core exists. I've seen it listed on other sites as T760MP4. Going by the Mali site (http://www.arm.com/products/multimedia/mali-performance-efficient-graphics/mali-t760.php), it says it scales up to 16 core product. I'm not sure what the MP4 means. I've also seen other tablets with the 762/760MP2.
Scalable would mean that a company incorporates it into their design, they could use up to a 16 core version (MP16 as you said). The RK3288 design is just using the 4 core version, which is what you'll find across all the RK3288 chips.
I wouldn't get to wrapped up in the Chinese manufacturer specs, they all seem a little "enhanced". Many of them cheat on their AnTuTu scores. iFive also lists the tablet as having a 1.8 GHz chip when it's limited to 1.6 GHz (not sure if a lower binned part, or just software limited). Most RK3288 chips are at 1.8 GHz. The reviews show that it's performance is pretty close to the same but with lower heat and better battery.
The PiPO P9 will probably perform slightly better since it's at the full 1.8 GHz and also running a lower res screen (1920x1200 vs 2048x1536). I wanted the 4:3 screen for reading documents. I personally don't like PiPO because I don't like the charging via DC adapter rather than USB method they use. I don't need another, different cable around.

I ordered one during the 12.12 sales and am waiting for it now. I wish the processor wasn't slightly underclocked, but the performance numbers aren't really hampered by it that much, and I'm not really getting it for gaming as much as document viewing.
The biggest problem so far has been finding a case for it. The semi-official one (the only one actually designed for it) seems to not even fit it that well, and is well, pretty blah looking. I figure some of the iPad Air cases should work, but I'm hesitant to order one without knowing.
Anyone out there with this tablet try any cases?
[Note: I just moved this from reply 2 down here to clear that out as a reserved reply]

Firmware Customization Tutorial
needs to be done in Linux, as you're working with ext4 filesystems -- however, you can do it in a VM install just fine (I'm using a VirtualBox install with shared folder support)
not a Linux tutorial -- you'll need to know what/how to get root access in order to run the appropriate commands for your distro
at various points, depending on how much you're changing the system.img, you may need to resize the filesystem and the image file
Accessing the system.img filesystem
if needed, unpack the firmware image
using Android Tools 2.3, click on the Advanced tab [part of Oma's downloads, or can be gotten from Firefly's website)
under the firmware selection box ("...") navigate to the packed firmware image (i.e., stock one, not Oma's)
click on the "Unpack" button
navigate to the "Output" directory under wherever you ran the AndroidTool.exe from to find the extracted firmware portions
in Linux, mount the system.img file
Code:
mount -o loop path_to_image path_to_mount_point
if this fails with "mount: unknown error -1" you probably don't have the loop module running
as root run
Code:
modprobe loop
and retry to mount
the image should also be accessible as /dev/loop0
go to the mounted directory and make desired changes
defrag the image file if you want using e4defrag
unmount the loopback image
Resizing the filesystem/image file
dd method (example included step not needed for this purpose (partition resizing)
use dd to make image file the size you want
use dd to copy over the old image file into the new file
run e2fsck and resize2fs on the image file
(basically, this is extra work beyond letting the resize2fs taking care of resizing the image file for you)
filesystem resize method
image must not be mounted
e2fsck -f ./system.img
resize2fs ./system.img [size] ("768M" for example, see the man page for more info)

Thanks for the info.
I think I'll go with the PIPO P9. I'll be using it mostly for gaming. I considered the Xiaomi MiPad, but the screen is bit too small for my taste. The other high end tablets are out of my budget.
TeutonJon78 said:
Everything I've seen listed has it as the Malt-T764. However, if you got the ARM/Mali website, no such core exists. I've seen it listed on other sites as T760MP4. Going by the Mali site, it says it scales up to 16 core product. I'm not sure what the MP4 means. I've also seen other tablets with the 762/760MP2.
Scalable would mean that a company incorporates it into their design, they could use up to a 16 core version (MP16 as you said). The RK3288 design is just using the 4 core version, which is what you'll find across all the RK3288 chips.
I wouldn't get to wrapped up in the Chinese manufacturer specs, they all seem a little "enhanced". Many of them cheat on their AnTuTu scores. iFive also lists the tablet as having a 1.8 GHz chip when it's limited to 1.6 GHz (not sure if a lower binned part, or just software limited). Most RK3288 chips are at 1.8 GHz. The reviews show that it's performance is pretty close to the same but with lower heat and better battery.
The PiPO P9 will probably perform slightly better since it's at the full 1.8 GHz and also running a lower res screen (1920x1200 vs 2048x1536). I wanted the 4:3 screen for reading documents. I personally don't like PiPO because I don't like the charging via DC adapter rather than USB method they use. I don't need another, different cable around.
Click to expand...
Click to collapse

Is there any way to disable vibration on notifications?

pylly said:
Is there any way to disable vibration on notifications?
Click to expand...
Click to collapse
Mine's not vibrating on notifications. But I turned off the "Vibrate on touch" setting. Maybe those are linked?

The Pipo P9 has a larger screen with lower pixel count than the iFive Air. The Pipo P9 can be charged using the Micro USB and/or the AC charger, this is also possible with the P1.
I don't like false advertizing, especially not with the CPU and GPU and I highly doubt that the RK3288 clocked at 1.8 GHz would have generated more heat than the aluminum case could cope with.
The biggest factor with power consumption is the screen brightness, not the CPU clock. I need to dim my scren to the lowest setting and it is still extremely bright.
With a higher clocked CPU I can always change the clock frequency to clock it at 1.6 GHz in case I want to. But since I pay for 1.8 and only get 1.6 GHz, I cannot clock it higher than 1.6.
Antutu 5.5 shows over 35000 points and Geekbench 3 reports 720 points with the single core test, very good. But all the lies, this needs to stop. It is chid's play and not very mature.
Ah just in case, the iFive Air does not have GPS and it is missing HDMI out, otherwise it is a very solid choice. The 5GHz WiFi works very well. But I regularly see red flashing frames around Chrome browser what is an indicator that the CPU is not powerful enough to cope with the browser's CPU power demand.
And because it also has ART support, I switched to ART from DALVIK. Big mistake. The iFive Air does not boot anymore and is stuck in the boot animation. There is now way to fix this and wow it get's better.
I cannot even flash a new firmware because the OMA ROM flashing method does not work. I always get Error "Match device type failed,stop running!".
How to recover from accidently switching to ART runtime switching (installing factory firmware):
You can download the factory firmware from the first post in this thread. The Factory Tool provided there will not work.
Download the Factory tool from this forum link, it will correctly work and show English Language when starting it up. You will also find the working RK3288 drivers there.
1. Install the drivers for the RK3288 (don't bother with the adb folder, just use the installer
2. power the iFive off
3. Start the Factory tool
4. Press Power button on the iFive and check if it is finding a loader entry with the USB tree shown in the factory log. If you do not see a Loader text, it won't work, e.g. if ADB is shown, nothing works, try powering it off and on until you see Loader as text next to an USB port.
5. Load the factory image using the appropriate button
6. Run the update. You will see progress next to the loader text.
7. Wait until the iFive flashes the ROM and do not remove the USB cable yet.
8. After the iFife tablet has booted up, remove the USB cable and close the Factory Tool.
Rooting the iFive Air:
1. If you would like to root the iFive Air, use Root Genius 1.8.7. You can download it from here.
1. Enable USB Debugging in the Settings and then start the tool Root Genius.
2. It will install drivers needed and after it recognizes the tablet you can then root the tablet using the green Root button.
3. Root Genius will install Kinguser.
4. Update the Kinguser program and then install Link2SD from the Google Play Store.
5. Link2SD will allow you to uninstall all the chinese programs.
Disable all the crappy utilities in the factory ROM (all with chinese signs) and you are set.
Warning: whatever you try, do not switch the iFive Air to ART runtime, it will not boot anymore after that.

StardustOne said:
The Pipo P9 has a larger screen with lower pixel count than the iFive Air. The Pipo P9 can be charged using the Micro USB and/or the AC charger, this is also possible with the P1.
...
But I regularly see red flashing frames around Chrome browser what is an indicator that the CPU is not powerful enough to cope with the browser's CPU power demand.
...
And because it also has ART support, I switched to ART from DALVIK. Big mistake. The iFive Air does not boot anymore and is stuck in the boot animation. There is now way to fix this and wow it get's better.
...
I cannot even flash a new firmware because the OMA ROM flashing method does not work. I always get Error "Match device type failed,stop running!".
Click to expand...
Click to collapse
I didn't know the PiPO's could still charge over USB. It seems silly to bother adding in an extra charging method.
They definitely need to stop putting out wrong specs. Although, I wonder if it's just a kernel bug, since EVERY other RK3288 is at 1.8 GHz, including the similarly spec'ed mini tablet. I can't imagine they would just arbitrarily get a lower binned processor for this flagship tablet.
I haven't had any flashing frames in Chrome -- maybe you have a bad unit? Although, I haven't done that much browsing yet, mostly scanned PDF's in the 150 MB+ range, which I would think would stress the CPU/GPU pretty well (the device gets pretty warm).
That's curious about ART. It seems a little odd. It would probably be one of the build in iFive/Chinese apps. Did you remove all of those?

Known Issues and Bugs (All ROMs)
General HW Issues
CPU is at 1.608 GHz instead of the advertised 1.8 GHz. Every other RK3288 devices seems to be at the advertised 1.8 GHz. This could be a kernel bug or it could be intentional (either a lower binned processor or due to thermal concerns). It would seem a little strange for a lower binned processor since their smaller tablet of the same specs is at full 1.8 GHz.
Volume buttons may be mapped backwards. Pushing on the button farthest from the power is "Vol Up" and the close one is "Vol Down". So in landscape mode it maps correctly to what you'd expect, but in portrait it's backwards from expected. And this is generally a portrait tablet. Discussion on the forums seems to be saying that other tablets have the same mapping, so probably not an actual bug.
Stock ROM
list of stock issues from 5Fans
Analaysis/commentary from Mike Canex
Storage
stock ROM splits eMMC into two data partitions (This is due to the RK3288 SDK setup apparently. Rockchip hasn't upgraded to the newer standard of unified storage.)
mount points aren't setup correctly in /storage for external SD card
/mnt/sdcard -> /mnt/internal_sd
/sdcard -> /mnt/internal_sd
/storage/emulated -> nowhere
/storage/sdcard0 -> /mnt/internal_sd
/storage/sdcard1 -> no created/linked -- should go to /mnt/external_sd
WiFi
If WiFi is set to turn off during sleep, it won't resume the connection without a restart. However, if you leave the option ticked to allow Android to scan WiFi points even when turned off, it will work correctly. I assume it's an issue with the WiFi chip not coming out of full lower powered state correctly.
Net Connections
Even with all the iFive and Chinese apps disabled, there are still connections being made to China via the Google Accounts services.
cause unkown
flashing red border in Chrome and other apps (relates to Developer Mode and Strict Mode)
Oma Stock-Based ROM
same as stock
Oma integrates some of his own preferred system apps, which may or may not be an issue for you. The ones that affect system functionality:
AdAway
Viper4Android
Oma's OmniROM Universal Build
any stock kernel issues
camera may not be working yet

Rooting the iFive Air
integrate root and a SU app directly in the ROM
use a ROM with root/SU app already integrated
3288 Ez Root Tool
This works really well as it packages root up as OTA update the system will automatically prompt you to install. You just have to put it in the root of either internal or SD card storage and wait till it rescans and finds the update. Make sure to read the instructions though, as the actual update.zip is inside the file you download.
no PC required
This is a generic RK3288 root method.
I used this method for stock and it worked perfectly.
Chinese Root Methods
ROOT Genius
requires a PC.
[*]@StardustOne provides instructions
ends up installing KingUser for the SU app
KingRoot (from Chinese forums)
360 Root (from Chinese forums)
dev hack -- Apparently on some RK3288 devices, if you go into the calculator and enter !^06^ it will prompt you if you want to root the device. This didn't work on the iFive Air for me. Some people in the FreakTab forum seemed be using an external mouse though, and perhaps the difference.

StardustOne said:
You can download the factory firmware from the first post in this thread. The Factory Tool provided there will not work.
Click to expand...
Click to collapse
I used the factory tool provided with the stock ROM download and it worked perfectly for me. The place I ordered from converted the language for me (which was nice), but I'd also prefer it be same as from the factory, so I reflashed it the second I got it.
Now, if you're stuck in the boot loop, probably just needed to put it into recovery mode first. From off, if you hold power and the farther volume button, it will get into that mode. That might help it connect to the Factory tool.

Oma posted a new stock based ROM (v.1.1) which fixes the chrome red ring problem and other minor fixes. You can get it from the link on the first post.

Multi-Window v2.0 has landed on iFive Air
- Oma -
{
"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"
}

Oma7144 said:
Multi-Window v2.0 has landed on iFive Air
- Oma -
Click to expand...
Click to collapse
Ha, welcome to the thread. Thanks for the great work.

Oma's posted a new ROM for the Air based on pure AOSP. Link is in the first post.

Android 5.0
iFive Air Tablet can be upgraded to Android 5.0? If yes, where to download firmware?

CUBOT Cheetah2 - Information & Reviews - 5.5" FHD | MT6753 | 3GB | 32GB | Fingerprint

CUBOT Cheetah2 - Information & Reviews - 5.5" FHD | MT6753 | 3GB | 32GB | Fingerprint
CUBOT Cheetah 2
{
"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"
}
Specs:
Dimensions: 153.6 x 75.0 x 8.5 mm
Weight: 188 g
Chassis: Aluminum Alloy
SoC: MediaTek MT6753
CPU: ARM Cortex-A53, 4x1300MHz + 4x1300 MHz, Cores: 4 + 4
GPU: ARM Mali-T720 MP4 600MHz, Cores: 4
Network: 4G Cat.4 (150MBps)
RAM: 3 GB
Storage: 32 GB
Memory cards: microSD, microSDHC, microSDXC
Display: 5.5 in, 1080 x 1920 pixels, 24 bit
Protection:
Battery: 3000 mAh, Li-Polymer
OS: Android 6.0 Marshmallow
Back Camera: 4160 x 3120 pixels (13MP), Samsung S5K3L8 Sensor, Dual-Flash, PDAF
Front Camera: 3,264 x 2,448 pixels (8MP), Sony IMX219 Sensor, Wide-Angle Lens
SIM card: Dual-SIM, Dual-Standby
Wi-Fi: b, g, n 2.4GHz, dual-band, Wi-Fi Hotspot
USB: 2.0, Type-C
Bluetooth: 4.0
Positioning: GPS, A-GPS, GLONASS
Other Features: Fingerprint Scanner, Notification LED, Gyroscope, Compass
Colors: Blue, Gold
Click to expand...
Click to collapse
Official Website:
https://www.cubot.net/smartphones/cheetah2/
Development & Support:
https://forum.xda-developers.com/android/general/cubot-cheetah2-development-support-t3689094
Click to expand...
Click to collapse
Reviews:
My own review: Post #3 & #4
Click to expand...
Click to collapse
​

Reserved

Review (Part 1)
Introduction
This is the CUBOT Cheetah 2.
Hardware
Just like the previous model, Cheetah (not 2), this successor is powered by a Mediatek MT6753 SOC clocked at 1.3GHz, with the same Samsung 13MP Rear Camera and Sony 8MP Front Camera. Also the Storage Configuration hasn't been changed, 3GB of RAM and 32GB of RAM are still there. Maybe a SOC upgrade (MT6753 to MT6750) would have been appreciated.
Unboxing
Packaging comes with some accessories: 1x Type-C USB Cable, 1x 5V/1A USB Charger, 1x Quick Start Guide, 1x Compliance Regulation booklet, 1x TPU Cover and the Smartphone (of course). A screen protector is already applied. Unlike previous CUBOT devices, this doesn't come with a Glass Screen Protector.
Based on the CUBOT website, this is the third MT6753 device launched by the company. Compared to the previous CheetahPhone, this one hasn't been made in collaboration with CheetahMobile (luckily), and doesn't use anymore an Unibody Metal Chassis (this is a downgrade). As you can see below, they kept the Metal Chassis though. It is solid, with Antenna Bands matching the device color.
It is 15.37x7.50x0.93cm, with thin bezels. It weights 194g, slightly heavy but not too much. It is still comfortable to use and the included TPU cover makes the weight even more uniform.
On the front side there is the common 2.5D Curved Display and the upper front side of the device features the standard set of things: an Huge Front-Facing Camera (Sony IMX219, consider that most low-end devices use this as a Rear Camera sensor, impressive), an Earpiece, and the Sensors hole that includes Light, Proximity and Gesture Sensors. The Notification LED is here, but supports only two colors. (Red and Green)
I won't talk about the Notification LED in the Software paragraph because it isn't customizable at all. Here you can see some real-life photos.
On the lower front side there is the Touch Keys area, with Menu, and Back touch buttons, together with the Fingerprint Sensor, positioned on the Home Physical Button. No Backlight is here.
On the back side there is the Removable Rear Cover, made of Plastic and similar to those used by Samsung on the Galaxy S3 & S4.
The upper rear side of the device features the Camera Sensor supported by a Dual-LED Flashlight (not Dual-Tone) and the CUBOT logo.
On the lower rear side there are some Logos and Words about the Device's Certifications, nothing else. The Speaker is positioned on the lower side of the device.
Device
Screen
Something that deserves a medal for this device is the Screen. It is perfect, providing one the best Color Accuracy i have ever seen on a FHD IPS screen while keeping the Brightness super-high. Well Done CUBOT!
Light Sensor supports smooth light changes, this is its maximum brightness. This is the brightest 5.5" FHD IPS screen i have ever tested.
Viewing Angles are as good as you would expect from an IPS screen, even a bit better thanks to the high brightness.
Camera
Featuring a Samsung 3L8 13MP sensor, with PDAF, the Photos Quality is unfortunately average. The amount of noise is too high to get a sharp photo, but there is something positive though. Colors are not washed-out or inaccurate, they are Natural without any over-sharpening.
"HDR off" on the left and "HDR on" on the right. HDR photos seems to be a bit better, but the amount of noise is also higher.
Photos taken on medium light conditions are decent.
Macro Photos are not so great, it seems that there are some focus issues with near objects.
The Dual-LED Flashlight provides enough light to take some nice shots, bright and warm enough to not damage any color.
As regards Video Recording, 1080p videos are average, still noisy just like Photos. I hope to see some improvements with upcoming OTA updates.
Front Camera is a Wide-Angle Sony IMX219 (Native 8MP, interpolated to 13MP), something rare to find. Consider that this sensor is used by many devices as a Rear Camera sensor, so expect some high quality photos here. Maybe this is the cheapest Selfie-Camera Device? It might be.
Audio
Speaker's Quality could have been better, at maximum volume the sound gets distorced, maybe this is a bit too much high for the Speaker. No issues with the Earpiece though, perfect while in-call and to play Whatsapp Voice Messages.
As regards the Microphone, it is calibrated for any kind of usage, everyone was able to hear me correctly. There is no Secondary Microphone for Noise Suppression though.
GPS
The MT6753 SOC is pretty known to have good GPS reception, with no issues that are present on newer SOCs such as MT6750/MT6755, and this test confirms its glory. GPS Signal is high, with no accuracy issues. I won't test it indoors this time because it is pretty clear that the Antenna is great enough to get some GPS signal even in difficult conditions.
Telephony, Mobile Network & WiFi
CUBOT, like some other brands, provides full european bands support, with 4G Band 20 (some other Chinese Smartphones don’t have it). 4G Signal Reception doesn't seem to have any issue, stable and with decent speed.
3G Signal Reception is excellent, actually I never managed to get connected to the 2G Network of my Mobile Operator because there was always some 3G Signal available. (luckily there are no coverage issues here)
As already said, 4G Network Speed is decent, even though it highly depends on your Mobile Operator and mine isn’t pretty good, the result is equal with other properly working devices i have reviewed. 3G Network Speed is, as always, pretty low even on H+, not a Device Fault though.
WiFi 5GHz is supported here, working sufficiently well with my 802.11n Dual-Band Connection. It isn't able to get full speed (100/20), but it is still a bit higher than 2.4GHz speed. Connected to 150MBps, i might have expected some higher speeds.
Battery Life
I have measured the real battery capacity using my USB Tester, and it seems that the real battery capacity a bit lower than the declared one. (declared 3000mAh, real ~2850mAh).
This is the Geekbench Battery Test, the battery runtime is pretty negative for a 3000mAh battery, i hope to see some improvements here.
https://browser.primatelabs.com/battery3/391930
As regards battery charging times, the 5V/1A charger isn't a good choice to handle 3000mAh batteries so expect more than 2 hours of Charging Time. It took, more or less, 2 hours and 45 minutes here.
Software
Unlike the previous CheetahPhone that was full of, let's say, crap from CheetahMobile, this Cheetah 2 is completely clean. Running Android 6.0, with some usual Mediatek Additions, it runs smooth enough to handle basic tasks but due to its Full HD screen, some occasional lags are here. That's why an MT6753 isn't sufficient this time, Mediatek claims that only the MT6753T is made to be used with 1080p screens.
Something different from the other last-gen Mediatek Devices is the software, only the Scheduled Power On/Off feature is present here. Even though the Double-Tap to Wake would have been useful, this is a nice step forward to not use Mediatek Crap.
Almost all Sensors are present, Magnetometer/Compass and Gyroscope, with no Barometer. Well Done CUBOT!
As already said before, even though there is a Notification LED, it isn't customizable at all.
The Fingerprint Scanner is probably the best one i have ever tried, no accuracy issues found. I managed to unlock the screen everytime, perfect. As regards the unlock speed, it is almost instant, not lightning fast.

Review (Part 2)
Benchmarks
I have used 3DMark, AndroBench, Antutu Benchmark, Epic Citadel, GeekBench 4, GFXBench, PCMark (Work 2.0, Computer Vision, Storage & Work 1.0) and Vellamo to stress the device to the limit. I won’t test Games or Video Playback because there are already some related tests included in these Benchmark suites.
3DMark – GPU Performance is mediocre, the Full HD doesn't help here.
AndroBench – eMMC Performance is great as regards the Reading Speed, decent for the Writing Speed.
Antutu Benchmark – I won’t say a lot about this benchmark, this isn’t as reliable as others. I’m providing this just for benchmarks lovers.
Epic Citadel – 3D performance isn't so good, the Mali-720MP3 struggles to handle 1080p Games.
GeekBench – CPU Performance is nearly as good as other CPUs with the same configuration (8x Cortex-A53).
CPU
Compute
GFXBench – There are no chances to see good results here, overkill for the device.
PCMark – Standard MT6753 Performance here, with some decreased scores due to the 1080p screen.
Work 2.0
Computer Vision
Storage
Work 1.0
Vellamo – Nothing to say about it, decent.
Well, even though i am happy to see that CUBOT used a Full HD screen on this device, i would have expected a better SOC because, as you can clearly see, the old MT6753 GPU is just not enough to handle this screen resolution.
Conclusions
I'm happy to see that CUBOT doesn't cooperate anymore with CheetahMobile, providing the best Android Experience even though the Performance isn't great. Except this issue, everything else is just fine. Great Screen, Fantastic Fingerprint Scanner and Solid Build Quality.
I hope to see some improvements with the next OTA updates to improve Battery Life and Camera Quality.
So, do I recommend it? Yes, unless you manage to find something better at the same price.
Pros:
Superb Screen Brightness
Excellent Fingerprint Sensor
Solid Metal Chassis
WiFi 5GHz Support
Notification LED (even though a bit limited)
Gyroscope & Magnetometer Sensors
Cons:
Camera Quality needs to be improved
Low GPU Performance
Slow Charging Times (1A maximum, no Quick Charge)
Insufficient Battery Life
Rating: 8.6
Packaging and Accessories: 9
Design and Materials: 9
Performance and Heat Dissipation: 7.5
Screen: 9.5
Camera: 7.5
Sound: 8
Battery Life: 6.5
Software: 10
OEM Support: 9
Price: 9.5
You can find full-res images (I know, Quality isn't excellent) here: http://imgur.com/a/XhJcX
Official Website: www.cubot.net/smartphones/cheetah2
You can buy it on many online shops. Official, and authorized, Retailers are listed in the CUBOT website.​

my 50 cents:
Review Cubot Cheetah 2 5.5 "FHD MT6753 1.3 GHz 3 / 32Gb - Fingerprint- 3000mAh
Packaging, Content, Aesthetics:
The packaging is a classic from a year now for Cubot, on the back there is a label with the model and on the low side of the IMEI numbers.
Box contents: Smartphone incorporated in its transparent silicone cover, further covered with a plastic seat cover with double-sided adhesive, 1 Power Adapter with USB 5V 1A White EU socket, 1 USB cable Type-C, an instruction manual and the "Compliance Certification Regulatory ".
- External dimensions of the smartphone average of 5.5inches ChinaPhone "; it measures 153.6 x 75 x 8.5mm for a little over weight 189g.
- High quality construction, the materials return a good feeling to the touch, the metallic finish of the side frame gives strength and elegance, the back cover plastic still fulfills its purpose well although it is very smooth and slippery (and in blue version retains much fingerprints).
- On the right side we find the volume rocker on the top and the power button slightly lower.
- On the upper side we find the only audio jack; on the underside there is the Type-C USB jack, the microphone in the left grid and the speaker in the right one.
- In the back top center there is the 16-megapixel camera from Samsung S5k3l8 13Mpixel f / 2.2 (16Mpixel interpolated), slightly to the side of the double LED flash (not dual tone).
- On the front we find at the top the capsule headset, 8Mpixel camera Sony IMX219 f / 2.8, the brightness / proximity sensors, the notification LED (colors red and green); down the central physical key features of footprints and the soft outer side touch buttons to the screen reader, but not backlit ..
- Outer pane with pre-applied film; It has a rounded 2.5D machining but the film does not have a good oleophobic treatment and thus holds the fingerprints and is quite reflective.
- Display brightness and excellent viewing angles; LCD FHD IPS OGS screen with good color fidelity, excellent sharpness for the category, good white balance and possibility of adjustment through Miravision menu.
- Touch sensitive and equipped with multi-touch 5-touch, quick writing and with swipe feature that you type with two fingers (used SwiftKey / google keyboard); with film applied to the sensitivity it tends to decrease slightly due to the excessive thickness, so if you use its silicone cover, you can also remove it.
- Fingerprint performs well, always recommend to store many times the same finger in additional memory locations after the first (5 memory locations and you might as well use them all to have a recognition reliability, for example the right thumb, close to 100 %.
- Two sim slots: 2 slot Micro + Nano Sim (dynamic 4G from software menu) and slot for MicroSD tested up to 128Gb.
- Battery is not removable 3000mAh declared, to the test with ammeter we found about 2800mAh, which can cover the average day with about 4 hours of heated screen (more if alternate data sim with wifi)
- Android 6 without any customization and usually launcher with 3 standard now obsolete icons (there are no unwanted apps or as it was for his brother Cheetah of Cheetah Mobile bloatware that slowed down the system unnecessarily and could not be uninstalled)
- Open app and switch between apps quickly .. browser stock enough usable but we recommend Chrome that makes it quick and enjoyable navigation.
- Excellent management of internal rom 32Gb which are available in a 25GB partition for apps and data.
- Good management ram 3Gb by Android .. more than 1.6 GB of RAM left over after loading some apps into memory at startup.
connectivity:
WiFi b / g with no problem, stable coupling, good power, the presence of the 5Ghz band.
BT 4 tested pairing with headsets, car and other smartphones without problems
OTG: Properly functioning.
GPS: very good, the outside is cold fixato in 20 seconds, 13 satellites, with an accuracy of a few meters; Glonass compatibility!
camera:
- Main camera from Samsung 35k3l8 13Mpixel f / 2.2 that produces good confiscated in daylight; pretty fast focus; mediatek camera interface; the good power flash.
In low light conditions, the cove sharpness and focus limps, the iso with the stock app does not rise above 600, the result is slightly moved shots without flash and a tendency to knead.
- Good performance with FullHD video files but with some critical issues in focus
- Second Camera for Selfies 8Mpixel Sony IMX219 with face detection function, and video shots higher than the category average (just think that this sensor is used by many other brands to the main camera)
.
Bench:
Antutu 6 more than 37000 punti..risultato in line with the other MT6753 CPU 1.3Ghz.
Geekbench with 2470 points in the multi-core test and 600 in the single core test.
https://browser.primatelabs.com/v4/cpu/1214302
Audio:
Audio without infamy and without praise, good the speaker volume and earbud (even slightly too low and tend to distort a bit at the most), good microphone, the other party has no problem and feel the voice is free from noise or interference or metallic effect.
Good vibrations and sound in very good quality headphone.
of Fingerprint Reader
The fingerprint has a menu that allows the storage of different fingerprints, up to 5; the memorization stage is driven (although parts of the menus are in English, without translation into our language) and allows you to complete the stage in no time (access the fingerprint of the security menu).
The front print reader position is easy to reach by inches and indexes and makes it definitely more secure smartphone.
conclusions:
PROs:
- Aggressive price from about 140 to about 160 € according to the store; good for a terminal with medium level specs, 3Gb RAM / 32GB ROM and fingerprint reader.
- Screen 5.5 "FULL HD showing good brightness, color and viewing angle of the display; 2.5D glass and the metallic finish of the frame lend elegance and style.
- Led Notification Green / Red.
- Great assembling, the materials used, consistent with the class of the device.
- Good reception and above average audio.
- MicroSD card support with separate slot (support up to 128GB tested).
- Two Sim Slot (Micro and Nano) with the switch via software 4G traffic between a slot one and the other.
- WIFI with 5Ghz band
- Ability to select a different ring tone for the two sim directly from the audio menu.
- 4G supported in 1,3,7,20 bands to the advantage of compatibility with European regions.
- Pretty much stock Android 6 dated October 2016.
- Fast and accurate GPS, fix also inside home where others failed.
- Compass and Gyroscope implemented.
- OTG supported.
- Transparent silicon case in bundle.
- Fingerprint reader which further increases the security of your data if entitled to do so.
- Certification and Declaration of Conformity:
UL + SAR http://www.cubot.net/pdf/ce/CHEETAH2-ce.pdf
Safety: http://www.cubot.net/pdf/doc/CHEETAH_2_DOC_Form.pdf
RoHS: http://www.cubot.net/pdf/rohs/cheetah2-rohs.rar
- Modding (Root) possible via the TWRP compiled by me
CONs:
- Charger Standard 1A with a charging time of about 2h and 50 minutes.
- Soft Touch NOT Backlighted.
- Heavy, 190g for a device with a plastic cover and battery 3000mAh, are objectively too much.
- NON Removable Battery.
- Black frames and even asymmetrical as seen in previous Cubot (fortunately not so visible since the dark blue of my sample)
- Notification LED that although present, has no settings in the menu, no double tap for unlocking (even if we have the middle button which is also physical).
- Main Camera sensor from Samsung, that in the face of a good specs, fails to realize its potential because of the usual mediatek software and drivers poorly optimized (common evil to the vast majority of devices Camera).
Sorry for mistakes due to automatic translation!
For reference, here's stuffs for development thread:
Rom RC_mt6753_n378bh_6143cgms_chuanqi_cc-cubot_256gbitp24d3_m_lte_3m-fdd-cs_mul_20161027-143211_songlixin_PC
https://mega.nz/#!VUc1TIjK!0FK1U5bt0NIL8RNEt-LkV-U5byVBroqV0PU92VzM5iE
Flashtool 6.1644 windows:
https://mega.nz/#!iINRFLAC!VZTD2enLeh5HzkJUWVwvV0nP_8cmvjPRRHt-1BWQoeo
TWRP 3.0.2-1 porting by megthebest:
https://mega.nz/#!TUdXiRyJ!CasPXBbA-CYuKL58w3QES0MYw5VNol8MTbB0L21RqlQ

Here are mirrors and more:
Android 7.0 v14 and up MDSTWRP_3.1.1-1_CubotCheetah2_Nougat.zip
Android 6.0 v08 and low MDSTWRP_3.0.2-7ES_Cubot_Cheetah2.zip 1st start spanish (MTP support)
source: MDS
Cheetah+2+TWRP+3.0.2-1.zip 1st start english mfi.re/?gpzahq5v9j1afz3
I confirm both TWRP work, thanks megathebest!
Root on Nougat (v14) i have to clean next spoiler SORRY SuperSu-forum
1. Download (maybe flase sorry try 2 get & fix soon) this zip and save to phone
2. Update to latest firmware (nougat)
3. Power off phone
4. Press and hold volume up while power up phone
5. Select fastboot
6. Install - flash the downloaded patched boot zip
7. Install Magisk manager and v14.2 magisk (or up)
Excuse maybe not working without flashfire (additional tool /adb)
No data lose, no additional pc tools
For recovery it is good to install flashfire (else) and make full backup.
If you come from rooted API23 you can flash a stock recovery via TWRP to get OTA update
If xposed is present better uninstall installer first.
old tutorial:
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
url boot.img
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this xxx !
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Click to expand...
Click to collapse
My note:
Do not flash whole firmware just select patched boot.img or flash patched file via adb
instead of
fastboot flash recovery recovery.img use fastboot flash boot boot.img
For recovery use https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools or https://flashfire.chainfire.eu/
Keep in mind getting latest firmware atm v15
Instead of mauimeta tool use mobil uncel apk befor flashing to backup IMEI
Firmware and note about update:
the API24 full Nougat v14 update here http://forum.cubot.net/viewtopic.php?f=21&t=1475
or OTA https://forum.xda-developers.com/showpost.php?p=73007684&postcount=11
Some older API23 Marshmallow updates:
V07 Sadly i do not have a propper V08 link. If TWRP is present you have to install a recovery (v07) to get latest firmware via OTA.
CUBOT_6143C_CHEETAH_2_V02_20161027.zip (flash tool inside)
With TWRP you can not install OTA update, so install latest firmware befor flashing TWRP! If you like to update firmware with TWRP installed, make a full backup for example with Titanium backup. Copy backup to a save location (pc^^ do not leave it on a plugged external sd)! Backup any user related floder (DCIM, Bluetooth, Download and any additional floder) copy them manuel to another storage TWRP or Titanium never restored them.
Then you can recover all data, apps and files if update is done.
If you now go to recover apps with Titanium backup, do not restore old system apps just data!
Flashing a orginal stock rom = factory reset
Flashing TWRP = factory reset if you have to unlook bootloader
To recover system apps or sound you maybe use my aroma installer base on V08 Android 6 API23 (see next reply).
With V14 maybe use the nougat aroma i provide
Me unlocked bootloader & flashed TWRP like that MTK6753 tut
Maybe install last Superuser version https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
Backup all files if you start TWRP!!!
For security you maybe set password to your TWRP with
lockable-twrp-recovery
https://forum.xda-developers.com/android/general/lockable-twrp-recovery-t3150750/
More useful apps - custom notifcation led, etc. :
You can simple install most following apps even more via my aroma installer (see next reply)
Latest Es Explorer support root access now or Fx explorer &root add-on
xposed API23 /sdk arm64
some xposed modul besides firewall:
MTP as Default USB Connection
Android N-ify Led-control but better -->
Led blinker works well for me. To use power led as notification light (red/green) but only if blinker app is not activ
More xposed modul i use: AppsOps, CameraNotify, BootManager, CleanLockscreen, Marshmallow SD fix
Roaming on national network? It can be fixed with https://forum.xda-developers.com/xp... can flash most of thoses apps via recovery
For simple imei r/w i used a mod of Mobileuncle Tools-com.mobileuncle.toolbox but offical final version do not work.
A TWRP flashable bootanimation 1080p - landscape from https://forum.xda-developers.com/android/themes/bootanimation-android-marshmallow-t3180984
A video of stock recovery
https://youtu.be/wqXhLF_WOKI
To start into recovery reboot
Press and hold Volume + (hold befor and till boot!.)
or shut down system
hold Volume +
Press again Power
Now the boot menu pop up :good:
Volume - is "enter/ok" in bootloader
additional note related to positioning / location / gps /
(save last system setting)
This happend as i block some system apps with firewallIf location (gps) is toggled on and you reboot it also seems to save state of Wifi, mobil date, etc. setup as it was set befor toggle location on.
By doing so you can choise if you like to have enabled wifi etc. while boot that may also take effect to sound-volume other system settings! - )
If you set location service (gps) off while boot you maybe get similar network connection issue as me!! Whenever i switched location on, some apps e.g. email or weather did not connect to net, other apps e.g. browser worked.
So my advice to you toggle gps on while boot if you like to use it often

Now my own thread
https://forum.xda-developers.com/android/general/cubot-cheetah-2-nougat-aroma-t3732579
my cubot cheetah 2 web floder:
http://www.mediafire.com/folder/5k0832h9u1cce/Cubot_Cheetah_2
#####################################################
Note about firmware update:
Release date: 2017-1-3 OTA update:
CUBOT_6143C_CHEETAH_2_V0820161230_103516
http://forum.cubot.net/viewtopic.php?f=21&t=1218
Contain some new apps:
Smart Wake, gesture to turn on/off display by tap on it or to start apps etc.
News,
Youtube,
Duo, (google video chat)
TalkBack,
more...
Security improve by update a little if password is used, request is now befor pin of sim.
If you like to install TWRP, run OTA update first or you have to flash stock-rom befor you can upate to V8.
edit:
Direct update from V2 to V8 did not work. First i had to install V7 to get OTA V8 update...
This maybe trigger V8 is not a full stock rom
Since i packed an aroma installer for a Lollipop device i decided to build one for the cubot cheetah:
Cubot+Cheetah+2+toBsucht+aroma+1.1.part1.rar
Cubot+Cheetah+2+toBsucht+aroma+1.1.part2.rar
The new download contain all system app, including the entire priv-app system, sounds (system/media/) < all taken from stock-rom v08
3 bootanimation, launcher / keyboard mod xperia, all applications from the previous publication
.....more
It should be useful for restoring deleted system applications. It should be useful to set up a Cubot cheetah after installing TWRP.
previous publication
You can flash those app:
FileExplorer_v5.1.3.0
FileExplorerRootAddOn_v1.0.2
VLCforAndroid_v2.0.6
321MediaPlayer_v1.3.0
MediaConverter_v0.9.3
PuffinWebBrowser_v6.0.9.15863free
com.UCMobile.intl_v11.3.0.950
Befor install Xposed flash xposed sdk zip
XposedInstaller 3.1.1 -->Have to be installed to use most of following:
AppOps_v1.9.1
com.mohammadag.xposedledcontrol_v5_8add0d
com.semon.cameranotify_v8_bfb03f
gd.sec.cleanlockscreen_v16_9bebee
tk.wasdennnoch.androidn_ify_v5_b94a95
LightningWall-385
dev.ukanth.ufirewall-2.9.1
Greenify.v3.4
MTPasDefaultUSBrayyan.black.fem.ind.runner_v4_ac7499
Marshmallow_SD_Fix_v2.0
ru.freshmobile.networkmodeenabler_v4_a34228
RoamingControl_v1.50.apk
If you don´t want an app you can simple leave it unselected in aroma installer menu.
Yes, aroma installer touch menu works flawless.
Cubot+Cheetah+2+toBsucht+aroma+1.1.part1.rar
Cubot+Cheetah+2+toBsucht+aroma+1.1.part2.rar
Fix since last version:
-bootanimation (standard) selection
-added titanium backup and open camera
-gapps removed simple get a arm64 pack from opengapps.org if needed
If you like to mod the aroma feel free to share :fingers-crossed:

Hi guys, I just got the Cheetah 2 a couple of days ago, updated to Nougat 7 and wanted to root. I followed the Unlock Bootloader (this bit worked) and flash TWRP but the TWRP won't open. When I flashed it the CMD window confirmed it had tranferred and the device confirmed in tiny text also but the device will only boot to stock recovery.
I'm guessing this version of TWRP won't work on Cheetah2 with Nougat 7, so if anyone finds one that does can you please let us know here. I will do the same if I find one. Thanks guys!

RoastPorkDinner i got same and no root permission. ..
However still no xposed for Nougat. Now i swipe to my Marshmallow v08 backup which already seems to have Nougat features by modding as shown.
1. edit:
Guessing it´s our fault. We forgotten to unlock to bootloader twice..kind of tricky. At the moment i´m still on v07 since i do not unlock bootloader (2x) befor flashing TWRP img.
2. edit:
Finally i am back on v08 but lost all files and pictures from internal standard floders: download, DCIM, bluetooth, etc.
I do not know how to recover them with TWRP or Titanium backup. If i use twrp to restore data partion only i am not able to get files back.
So if someone like to recover that i suggest to backup those folders manuel.
Yesterday i liked to replace superSU with Magisk but installation failed on a boot.img error. Maybe someone else got Magisk as superSU replacement?

toBsucht Psp said:
RoastPorkDinner i got same and no root permission. ..
However still no xposed for Nougat. Now i swipe to my Marshmallow v08 backup which already seems to have Nougat features by modding as shown.
Click to expand...
Click to collapse
I think I'll wait, I can't be bothered to roll back to Marshmallow, takes to long to set my damned phone up how I like it!
Something will come along soon to provide root access, I'm sure

Just install TWRP to get root access, should work with Nougat but you have to setup your phone again after unlock bootloader.
You can backup with stock recovery but that only works if you fail on TWRP installation ..stock backups can not loaded with twrp.
If you got TWRP (root) you can restore any app with titanium backup
Yeah wait some days i´m going to build a flashable* rom from the Nougat stock. As i said, i stay on Marshmallow for xposed modules.
*most likely for TWRP
----------------- stock rom Nougat v14 update -----------
http://www.mediafire.com/?ubypzwp75qg59j1/ Cubot+Cheetah+2+Nougat+v14.part1.rar
http://www.mediafire.com/?hzwbo1mqzb12ygx/ Cubot+Cheetah+2+Nougat+v14.part2.rar
http://www.mediafire.com/?rhuzovc7sxqe6zg/ Cubot+Cheetah+2+Nougat+v14.part3.rar
Download all 3 parts into one floder then you can extract nougat update.
---------------------------
If someone found an alternative tool to enable root it would be nice to reply. With root you can flash recovery.img via flashify
----------reupload nougat aroma installer
https://www.mediafire.com/folder/zfc9h5x8nfty8/Nougat
Cubot Cheetah 2 Nougat aroma 1.0b
-requires twrp
-download all 3 parts to extract the nougat.zip rom
Guessing can not be used to update from Marshmallow (API23) to Nougat (API24) since i packed whole system but not boot.img
As usual backup befor flash

toBsucht Psp said:
Just install TWRP to get root access, should work with Nougat but you have to setup your phone again after unlock bootloader.
You can backup with stock recovery but that only works if you fail on TWRP installation ..stock backups can not loaded with twrp.
If you got TWRP (root) you can restore any app with titanium backup
Yeah wait some days i´m going to build a flashable* rom from the Nougat stock. As i said, i stay on Marshmallow for xposed modules.
*most likely for TWRP
----------------- stock rom Nougat v14 update -----------
http://www.mediafire.com/?ubypzwp75qg59j1/ Cubot+Cheetah+2+Nougat+v14.part1.rar
http://www.mediafire.com/?hzwbo1mqzb12ygx/ Cubot+Cheetah+2+Nougat+v14.part2.rar
http://www.mediafire.com/?rhuzovc7sxqe6zg/ Cubot+Cheetah+2+Nougat+v14.part3.rar
Download all 3 parts into one floder then you can extract nougat update.
---------------------------
If someone found an alternative tool to enable root it would be nice to reply. With root you can flash recovery.img via flashify
----------uploading nougat aroma installer
requires twrp
Click to expand...
Click to collapse
I already mentioned I unlocked bootloader successfully, but TWRP wont flash. Fastboot says it has transferred to phone successfully but only stock recovery will open, no sign of TWRP
I think a new TWRP for Nougat on the Cheetah 2 is required. I even tried to temporary flash the TWRP you provided with "fastboot boot recovery recovery.img" no joy for this either.

That happend to me if i unlock bootloader only once or false. Yes, i also transfered recovery.img and got an success message if i unlocked bootloader just once or flase!
By the way the Nougat aroma rom is fully re-uploaded
https://www.mediafire.com/folder/zfc9h5x8nfty8/Nougat

Ok, I want to try and port TWRP for Cheetah 2 Nougat... any idea how I can get the Stock Recovery.img from Nougat??
I'm new to this kind of procedure and the stuggle is real lol !

Cann´t find a recovery inside Nougat v14 update. I unpacked whole files to get system floder for the aroma. Only the boot.img i did not unpack but boot.img do not contain recovery. Sorry i´m little lazy to reinstall Nougat again for testing.
To enable my device update from V08 Marshmallow to Nougat, i flashed V07 recovery via adb. Maybe not needed anymore if i flash Nougat aroma.
Maybe try a little spanish at MDS twrp thread
You maybe saw MegaTheBest account is disabled so you maybe try contact at needrom.

toBsucht Psp said:
Cann´t find a recovery inside Nougat v14 update. I unpacked whole files to get system floder for the aroma. Only the boot.img i did not unpack but boot.img do not contain recovery. Sorry i´m little lazy to reinstall Nougat again for testing.
To enable my device update from V08 Marshmallow to Nougat, i flashed V07 recovery via adb. Maybe not needed anymore if i flash Nougat aroma.
Maybe try a little spanish at MDS twrp thread
You maybe saw MegaTheBest account is disabled so you maybe try contact at needrom.
Click to expand...
Click to collapse
Yes, I did the same. I have your V14 ROM which only contains a Boot image and I have your Aroma nougat ROM which has neither Boot or Stock Recovery image. I did unpack the Boot image and of course, nothing to be found there.
If there's no Stock Recovery image in the Nougat Roms, they must still be using the original one!

RoastPorkDinner said:
Yes, I did the same. I have your V14 ROM which only contains a Boot image and I have your Aroma nougat ROM which has neither Boot or Stock Recovery image. I did unpack the Boot image and of course, nothing to be found there.
If there's no Stock Recovery image in the Nougat Roms, they must still be using the original one!
Click to expand...
Click to collapse
Yes :good:

I was going to try and port the new Nougat Stock Recovery, but if it's the same Stock Recovery as Marshmallow then theoretically MegTheBest's port should work. As we know, it doesn't, which means I need to use the latest TWRP, 3.1.1 (or whatever it is). I just need to locate the damned Stock Recovery image!! Not so easy without root and I can't root without it... bah!

RoastPorkDinner said:
I was going to try and port the new Nougat Stock Recovery, but if it's the same Stock Recovery as Marshmallow then theoretically MegTheBest's port should work. As we know, it doesn't, which means I need to use the latest TWRP, 3.1.1 (or whatever it is). I just need to locate the damned Stock Recovery image!! Not so easy without root and I can't root without it... bah!
Click to expand...
Click to collapse
No dude megathebest TWRP and MDS TWRP should work!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Again! My suggestion to you retry bootloader unlock!!!
If you have a believe it only work with a MarshMallow firmware downgrade and check how to install TWRP propper. Then you know how to. If you see what you made wrong on installing twrp maybe then you like to retry on Nougat.
But feel free to port a new version of TWRP. Use v02 or v07 recovery to port it if needed.
Again no v14 stock recovery i had the v07 installed as i made a direct upgrade to v14. The kernel is in boot.img

I'm sure Bootloader is unlocked. It says bootloader unlocked=YES and also Warranty=NO.
However, I'm going to take your advice and try unlocking it again. I hate having to set my phone up after a wipe so much though...
Be back soon with a good result i hope!

Stock Oreo - CPU not scaling

This morning my Pixel C felt slow and sluggish.
Rebooted and removed recently installed apps but no difference.
Installed a CPU monitoring app and see that the CPU stays at 204Mhz even under load.
Any ideas before I try a full wipe?

Full reset seems to have fixed though notice cpu maxes at 1326
This right?

I'm not sure most CPU monitors know what to do with the X1, I know CPU-Z doesn't recognize it beyond a general "Nvidia Tegra" chip. What app are you using?

I switched from AOSP for acbit but yesterday had the same issue. Tablet felt slow and sluggish.
CPU monitor app showed CPU not scaling.
Went back to stock Oreo and still "feels" slow.
Geekbench4 says single core 926 and multi 2561
This is wrong?

My Pixel C performance is strange still the OREO update. I know this going to sound weird but when in splitscreen, the app on the left in landscape or on the top in portrait is lagging a lot. Scrolling, page swiping, etc.. takes a distinct longer time than expected. The app in the other half of the screen is acting normally.
Could this be related to the same issue?
With the pixel C now discontinued, Google is unlikely to fix a bug, especially if nobody reports it.. Bit of a worry, what to do?

I'm facing this issue as well. Already wiped cache and did factory reset, with no results.
It's now a very fancy digital picture frame.

There is no such problem. I used the first available monitoring program (cpufloat) and the CPU frequency change is shown adequately.
https://play.google.com/store/apps/details?id=com.waterdaaan.cpufloat

Vartom said:
There is no such problem. I used the first available monitoring program (cpufloat) and the CPU frequency change is shown adequately.
https://play.google.com/store/apps/details?id=com.waterdaaan.cpufloat
Click to expand...
Click to collapse
Thanks - in that case, the issue is less obvious to spot but I have definitely noted a lag in split screen mode refreshing the app on the left (yes, I know how strange it sounds..).
In addition, there have been quite a few report of the new January patch release affecting Pixel (phones) users. I can't help thinking our Pixel C issue with the last update and these new issues are too much of a coincidence..
I am hoping Jan patch might fix my Pixel C issue...
L

laurentbon said:
Thanks - in that case, the issue is less obvious to spot but I have definitely noted a lag in split screen mode refreshing the app on the left (yes, I know how strange it sounds..).
In addition, there have been quite a few report of the new January patch release affecting Pixel (phones) users. I can't help thinking our Pixel C issue with the last update and these new issues are too much of a coincidence..
I am hoping Jan patch might fix my Pixel C issue...
L
Click to expand...
Click to collapse
At the moment I'm using the kernel I've modified, and I have no problem with scrolling on the left side of the screen in split screen mode.
you can try it.

Install Kernel Auditor and deselect CPU Multi-core power saving option in CPU tab, that was on for some reason.

MrPhilo said:
Install Kernel Auditor and deselect CPU Multi-core power saving option in CPU tab, that was on for some reason.
Click to expand...
Click to collapse
For what? if the frequency control and so works normally

Just updated January-ota and nothing has been solved... What can we do to make google solve it. The bug with the navbar continues and the split-screen is impossible to use
I started a thread when I noticed this bugs
https://forum.xda-developers.com/pixel-c/help/bugs-android-8-1-t3718156

AlfreGarcia98 said:
Just updated January-ota and nothing has been solved... What can we do to make google solve it. The bug with the navbar continues and the split-screen is impossible to use
I started a thread when I noticed this bugs
https://forum.xda-developers.com/pixel-c/help/bugs-android-8-1-t3718156
Click to expand...
Click to collapse
https://issuetracker.google.com/issues?q=componentid:190923+ Click "Create Issue" Report the bugs in detail how to replicate etc Someone from the dev team should get back to you

liam_davenport said:
https://issuetracker.google.com/issues?q=componentid:190923+ Click "Create Issue" Report the bugs in detail how to replicate etc Someone from the dev team should get back to you
Click to expand...
Click to collapse
I dont know why, but the blue buttons are unclickable for me, so I cant create the issue.

Bringing back from dead.
So if you use Kernel Auditor to turn off some of the cores when this is occurring, the clock speed goes up for the primary core. It's as if they set a total limit, then divide by total core count. When battery charge is above 67%, you get the full max speed. No reboot or anything, just charge it up and you unlock the speed again. I suspect the Oreo kernels have bad throttling algorithm for this CPU.

My Pixel C was lagging quite bad when the battery fell below 67% using stock 8.1 (locked bootloader, everything untouched). I tried reflashing the factory images, but the problem stuck around. I rooted (magisk 18.1) and installed Kernel Adiutor. The problem was obvious, the CPU would heavily throttle (under 67% battery) depending on the amount of core active (with 4 cores, they would all run at ~200 mhz, with 2 cores, about 700 mhz and with 1 core about 1100 mhz). It wasn't so terribly laggy with 1 core running at 1100 mhz, but it was still pretty slow.
To try and troubleshoot the problem I then installed LineageOS 15.1 and followmsi's kernel (https://forum.xda-developers.com/pi...p-flashable-monthly-update-zip-pixel-t3375591). To my surprise the problem remained, despite the custom ROM and custom kernel. I think there is something wrong with the 8.1 oreo kernel and the Pixel C (see google forum post here: https://productforums.google.com/forum/#!msg/nexus/x7izNIUIHeI/VO4n9l_DCAAJ ). So I tried a second solution. This time I did the following:
1. Flashed TWRP: twrp-3.2.3-0-dragon.img
2. Flashed in TWRP: Followmsi's unoffical lineageOS 16.0: lineage-16.0-20190206-UNOFFICIAL-dragon.zip
3. Flashed in TWRP: (same session, before booting into LineageOS): OpenGAPPS Arm64 Pico package: open_gapps-arm64-9.0-pico-20190302.zip (m
4. Flashed in TWRP: (same session, before booting into LineageOS): Followmsi's Android 9 custom kernel: tegra-3.18_kernel_pie_dragon_v190205_unicorn-xceed-followmsi.zip
And voila, back to full speed. In fact the tablet seems to run better than ever. After some testing I installed Magisk 18.1 (for root and to pass safetynet), and everything is running great. The CPU's now appear to be managed properly by the 9.0 kernel. I'd recommend anyone experiencing this problem to go ahead with what I outlined above. Alternatively, if you're not comfortable with custom roms, you can install the last Android 7.1 build (ryu-n2g48c-factory-0bc0ee15.zip - guide here: https://mmikowski.github.io/pixelc-revert-nougat/).
Hope this helps.

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