Develop Bugs

Overclocking XDAndroid Rhodium

So I noticed a number of references in one of the mega XDAndroid threads to overclocking Rhodium. Sounded pretty simple, just a string of text with the desired frequency in a particular file.
A couple of questions for those who toyed with that:
1) was it stable and what was its fastest stable speed?
2) did it run uncomfortably hot?
3) is it possible to alter it on the fly (so you can run it slow when you're reading, and crank it up for video), or do you have to choose a speed preboot and reset to change it?
4) If it can't at the moment, be altered on the fly, might it be possible for some program to do that in the future?
5) finally, why is it so easy on adroid? It seems like no2chem has hit a bit of a wall in making his winmo project hum, but the references here made it sound like a pretty basic task.
Part of the reason I'm asking is flash 10.1 is due for android in Q1. The last I read of CPU requirements had them over Rhodium's specs by a lot. Mobile hulu access would be fantastic, and I'm planning to start dual booting this summer, once classes are done. It'd be nice if my TP2 could eek out enough performance for that.
Thanks

You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.

devilcuban said:
You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.
Click to expand...
Click to collapse
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.

Yep same here. If I add that line, once it goes to sleep in Android, it doesn't want to wake up again...

Reefermattness said:
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.
Click to expand...
Click to collapse
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.

devilcuban said:
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.
Click to expand...
Click to collapse
I did test and confirm this. I think what happens is with smem.fake=1 the phone actually never goes to sleep.... at least the sleep light never turns on. I will have to ask phh if this is the case.

Tried putting the overclock line in Startup.txt but it did not seem to change anything, at least according to the CPU Benchmark app. The battery line did seem to work though, as it thought it was charging even while not plugged in.
Is there a specific order that these parameters need to be added in? I just added the overclock line at the end and the battery one after that.
Using the latest non-sense 2.1 builds.

I'd love to add Rhodium overclocking support to my RogueTools application.
I think there is still a constraint though with write access to /system. I am hopeful that shortly the Rhodium kernel and rootfs developers will deviate out of the current read only SQSH model and go the way of the Vogue, Kaiser and Polaris hosting the system and data in separate EXT2 partitions on the SD Card. NAND would be the next step.
If someone knows another way to overclock on the fly once the system is up (post boot). PM me. Like I said, I'd love to add support for the Rhodium.

so nothing on the OC for 2.1 yet?
bump

I'm about to test overclocking with the SetCPU app. Worked fine on my rooted G1. I'll report back with my findings.
Edit: Did not work with custom and/or multiple devices selected. Can't push any higher than the stock 528. Blah.

on screen keyboard
when i put both sleep fixes and the overclocking cpu command in my startup text i get the on screen keyboard like in rhobuntu. how do i disable this? its not even usable it just lingers there and its very annoying

O.S.K. byebye command is msmvkeyb_toggle=off

OverClocking M2CW & IME
Data corruption is inevitable without running extensive stress testing to find a safe speed. I have yet to find one for msm7k processors, but surely Qualcomm has one. Benchmarking is not the same as stress testing. Such stress testing apps need to be run for several hours & even days. They can't test all functionality accuracy. Stress testing in themselves can cause hardware damage & even catastrophic failure.
Data corruption is often the "silent killer" and goes undetected by you or system checks ... until you need it most. It may be a config file, a message file, a contact database, an executable, a registry hive, a system file. Any non ROM file is vulnerable. Backup OFTEN & NOT while OC, even though BUed corrupted data is still corrupted. Quote "stable speed" isn't such just because device doesn't randomly lock up or reboot.
Every CPU and memory chip has different limitations. Same phones built on same date may not OC the same.
Don't OC when when building new Android data.img file, downloading update files or apps, extracting or creating archived files, installing apps, encrypting or decrypting.
OC doesn't help Project XDAndroid developers. I suspect many "bugs" they spend valuable time on are OC related.
The msm7k processors supported by Project XDAndroid are a speed scaling processor designed for optimum performance vs. battery runtime, ramping up and down the processor speed based on demand. Average device use doesn't utilize full processor speed.
OC is most noticeable in OS boot times (when OC is initialized prior to), certain multitasking operations, some video playback, CPU intensive games, & to a lesser extent web browsing. Many factors determine the effectiveness of OC especially whether graphics are hardware or software supported.
Your OC device may actually perform worse, noticeably more sluggish, or more jerky than when not OC. Ever notice on some boots into Android it takes forever for your carrier to be detected & displayed on the lock screen and it may creep along as if your processor was hijacked by a random process? Ever notice when you open the app drawer not all your apps are displayed?
OC does use more energy thereby shortening battery run time and producing more heat. Don't complain about battery life if you are OC. Accurate battery charge state & battery run time are not synonymous.
While OC may shorten hardware lifespan it most likely, though possible, will not lead to a catastrophic failure in the typical device lifetime due to the rate of current technological innovations and average length of ownership.
My overall performance satisfaction with Project XDAndroid is best when not OC, especially now that hardware 3D is supported or partially supported as in my rhod500.
OC at your own risk.

KT-SGS6E [Kernel] Builds [Discussion] [G92X] [TW 5.0] ★KTWEAKER SHOP★

ALL THANKS AND CREDITS GO TO THE ONE AND ONLY KTOONSEZ FOR HIS AWESOME KERNEL AND GIVING ME THE OPPORTUNITY TO PROVIDE THESE BUILDS.​
Welcome!
I am in no way affiliated with Ktoonsez or his work. I’m just a simple member of the XDA community who happens to be a huge supporter of this kernel and its creator. This is just my way of giving back. I am aware of some of the issues that may occur on specific kernel builds for some users as well as the difficulties faced when fine tuning the kernel and this is my response to that:
This is by no means intended to replace any of the original KT-SGS6E kernel threads. The purpose of this thread is simply to work in conjunction with them by providing a variety of builds for which users can experiment with and find which versions perform as intended on each of their respective device models. As on previous Samsung devices I am also bringing back the Ktweaker Shop filled with tons of pre-configured settings compiled by myself and others in attempt to further assist S6 & S6 EDGE users with improving their overall experiences on this device or to simply use as a baseline to work upon tweaking further. So I’ve gathered just about all of the current and previous kernel builds I had hidden within my pc as well as all the various Ktweaker settings and am sharing them with the public. I hope this makes a difference for all you guys. ENJOY!! :good:
POST #2: Reserved for UNIFIED {G92X} users
POST #3: Reserved for the KTWEAKER SHOP
POST #4: Reserved for TEST PROFILES
If at any given time you aren't already on the kernel and Ktoonsez hasn't updated his links, there'll be no need to flash previous builds when you want to receive OTA's as ALL posts will be updated regularly upon future releases. So please be sure to refer back here for all builds from this point moving forward!
I will NOT be held liable for anything that may occur to your device nor will Ktoonsez. So please...
***FLASH AT YOUR OWN RISK***​
If you encounter any suspicious issues when updating the kernel, follow my recommended procedure for the best possible results:
1) Backup current Ktweaker settings
2) Open any root browser (make sure it's mounted as r/w) then navigate to /system/app/ and delete the Ktweaker and KTmoniter apk's
3) Navigate to your sdcard and delete the Ktweaker folder OR rename it by adding a ".bak" extension without the quotes.
4) {Optional} Clear all Superuser logs
5) Reboot Recovery
6) Flash kernel
7) Reboot
8) Copy any saved profiles back into /sdcard/Ktweaker/Profiles/
9) Restore Ktweaker settings
10) Profit?
NOTE: If at any point Ktoonsez no longer wants this thread open it will be closed without question.
Please visit original kernel thread for change logs, extras, etc...
If you like and support his work, donate with this link:
http://forum.xda-developers.com/donatetome.php?u=4325945

**********G92X**********​
KT-SGS6 kernel features
•Must have a S6 model G920F and G920I and G920S and G920T and G920W8 and G925F and G925I and G925S and G925T and G925W8
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•Over Clocking
•Under Clocking
•KTweaker app for kernel control
•KTweaker Widgets
•KTmonitor app to watch your cpu cores current speed
Click to expand...
Click to collapse
Downloads
Touchwiz Lollipop 5.0 VERSIONS:
https://copy.com/Yo6i7SqAQS8zsAmg
Main kernel thread: http://forum.xda-developers.com/tmo...lopment/kernel-kt-sgs6e-ocv-ktweaker-t3099758

{
"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"
}
Welcome to the Ktweaker Shop!
Here you will find all of the pre-configured settings provided by myself and Ktoonsez. As a proud member of Team Kernelizers, I am offering a variety of profiles specifically for S6 and S6 EDGE users with their personal needs in mind as it's pretty clear not everyone favors the same governor, scheduler, etc.. Any suggestions are always welcome. All future profiles will be added here for sharing and discussion. Keep in mind that results will always vary per device regardless on the settings being used.
All profiles have been grouped into 3 sub-categories; "Conservative", "Balanced", and "Performance", which are used to classify each profile based on their role and what they are expected to deliver to your device. The 4th sub-group is where you can find some of our best "Projects" in which offers 2 or more profiles per project. Make your selections based on your usage needs and apply what works best for you and your phone. We're here to help eachother out and with more options comes better experiences for everyone running this kernel.
So shop around.. pick and choose.. load and go!!
Installation
Download links will include the specified profile(s) as well as an "Adjustments" and "About" file. The "Adjustments" file is just a simplified view of all the changes made to a profile compared to stock settings.
1. Download the file(s) to your phone.
2. Copy ONLY the XML(s) (DO NOT copy the "Adjustments" or "About" file) to "/sdcard/KTweaker/Profiles" using a file Manager of your choice.
3. Open the Ktweaker app and click on the "Profiles" setting at the top of the slider drawer OR scroll to the bottom and select "Profiles & Scripts" then click "Restore Profile from sdcard".
4. The file you just copied should be listed there. Select the one you want to apply and confirm.
5. Make sure the "Set options on boot" setting at the top of the slider drawer shows a little green boot icon below it, indicating the settings will be applied upon reboot.
6. Profit!
IMPORTANT: Be sure to ALWAYS load your stock voltage table on BOTH CPU clusters IMMEDIATELY after applying a profile as most of these are based on an ASV10 CPU and may result in reboots!!!
1) Apply the profile
2) Quickly go to the CPU voltage for cluster 0 and click "more" and load default voltages, then click apply.
3) NOW go to the CPU voltage for cluster 1 and click "more" and load default voltages, then click apply.
4) Done!
​
Conservative​
Asking Alexandria
This is a battery driven profile in which focuses on saving as much juice as possible while also maintaining stability and providing an extremely snappy feel to your phone. It is quite possibly one of the smoothest and snappiest battery saving profiles available.
Why Asking Alexandria?
It's named after yet another one of my top favorite metalcore bands and I chose this because Alexander The Great basically ruled the world at one point and "Alexandria" is the female equivalent to that name, which has become known to mean the "one who comes to save warriors".
"Asking" was an addition to the title name as an indication in the sense that we are all asking Alexandria what she can really do to our phone.
Coming soon....
Bless The Child
Based on Ktoonservateq and aimed towards battery. This is specifically for all the battery hungry users out there wanting to conserve as much power as possible. So don't expect the BEST but rather decent performance out of this one.
coming soon...
Dead By April
This profile attempts to bring some of the best battery life possible to your device. It is similar to Bless The Child but takes things a step further with it's heavy underclocking as well as it's higher thresholds and online blocks to prevent other cores from coming online too soon. Although It focuses very little on performance it manages to maintain a fairly smooth interface for your average daily use.
https://copy.com/oFLHg4ZG2MyvRzrq
Balanced​
Balanced Bull v1
These settings are very special to me as they were my very first, dating back to the Galaxy S3, and is a profile designed for my own personal usage pattern. It has become notable for it's fairly smooth interface and amazing battery life. If this stacks up to your standards then I encourage you to use it!
https://copy.com/SKdHYHskn1NgLitp
ECLIPSE
This is a performance oriented option where great battery life is also expected to intervene. This not only will bring an incredibly stable, smooth, and snappy feel to your device but will also benefit towards longer lasting battery so you can love and enjoy your phone the way you were meant to.
coming soon
Ktoonsified v1
These settings are my settings, This is a performance oriented option in which also offers a great deal of battery life. YOU WILL NEED TO LOAD YOUR STOCK VOLTAGE TABLE THOUGH since there are 16 different bins of CPUs!!!
Click to expand...
Click to collapse
https://copy.com/COP9WtEfLzTudZ2F
Ktoonsified {MOD}
This mod is intended to work as an alternative to the original Ktoonsified profile. It's specifically for the users experiencing issues such as screen wake and incoming call delays and media stutters on Ktoonsified v1 . Use this profile to repair most if not all of these issues.
NOTE: The adjustments text file will show you the few changes I've made from the original Ktoonsified profile.
https://copy.com/2bcvnievx8suWohD
SmoothManic v1
This profile was put together by none other than the BOSS himself, @ktoonsez!
The idea with this is to get the CPU really high on 2 cores when screen is touched and then bring them both back down really quick so UI is super smooth but don't kill the battery by hanging out at that high Mhz step.
Click to expand...
Click to collapse
https://copy.com/mgoNzpgrYn7TkLZO
Undisputed
This is a universal performance setup in which combines the essential elements of other profiles by providing equal battery life, speed, performance, and stability to bring the ultimate experience to your device.
coming soon
Performance​
Feed The Machine
The exact opposite of Bless the Child. This is a performance oriented option for all hardcore users. If battery isn't a priority for you then this is a great option.
coming soon
From Ashes To New
This is a straight performance profile. It's similar to Feed The Machine and Rebirthing in the sense that it syncs the cores to the boosted frequency on touch and almost instantaneously jumps right back down to 300MHz. The difference between the profiles is that this one makes better use of all the cores. However, due to the rapid scale down I think most people will find battery life to be surprisingly good for this type of profile
coming soon
KTGaming v1
This profile was put together by none other than the BOSS himself, @ktoonsez! This is a super performance oriented option which allows me to play any game with ZERO LAG!!!!!!!
Click to expand...
Click to collapse
https://copy.com/VwSaksMPwJGCfCux
SmoothGaming v1
This profile is based on SmoothManiac v1 but with performance enhancenents to provide a much smoother gaming experience while hotplugging is active. Some of these enhancements include a much higher sampling interval as well as offline blocks to allow frequencies to scale and hotplug at a more reasonable pace.
NOTE: The adjustments file will show you the changes I've made to SmoothManiac v1.
https://copy.com/zI4c1TovjavAQBtI
Projects​
Comatose
This project was inspired by the album of the same name by my #1 favorite rock band of all time, Skillet. It consists of 3 profiles of which are also named after 3 of my favorite tracks from this album (included in the "Extras" folder) and all focus on one key element; VARIETY.
As the name suggests, "Comatose" is geared towards battery conservation. It focuses on keeping CPU low for a prolonged period but utilizes 3 of the 4 cores on touch and the 4th on demand for fluidity. Sample rates have been decreased heavily as to increase polling and allow the other cores to quickly spike towards higher frequencies for a given task then immediately drop back down as if the component had been knocked unconscious.
The second profile is "Rebirthing". This profile will counteract the affects of Comatose by heavily boosting performance as a means to bring life and energy back into this profile that remains unconscious. Rebirthing is intended for those seeking a performance-based version of Comatose but who knows... For such a power hungry profile you may just be surprised by the great battery life it also delivers.
Some of you may not favor the heavy battery conservation that "Comatose" offers or the overall power consumption of "Rebirthing" and much prefer a mashup of elements delivered between the 2 and that is the purpose of "Whispers In the Dark". This profile is directed towards finding the right balance between these 2 profiles while still acting as a it's own profile. It utilizes most of the performance aspects from "Rebirthing" Like "Comatose" it uses a fairly high up_threshold for that extra boost in battery performance. The profile also idles at the same minimum cpu as "Comatose" but ALL profiles run at stock 2457Mhz.
All profiles maintain the same concept of rapid cpu polling. So yes, cpu will be working consistently but my theory here is that more polling will allow the kernel to rapidly check CPU usage, thus allowing CPU to change more frequently according to the load, which in turn will prevent persistent pegging of even higher frequencies and instead consume various amounts of power in various scenarios depending on your usage, consuming even less when a specific task has completed and immediately dropping the load.
This also applies to screen off states but that goes back to what was explained in this post regarding high vs low sampling rates and how they can greatly increase idle times depending on your screen off max.
coming soon
If you'd like to contribute to the Ktweaker Shop all you need to do is post the profile you'd like to share and include a brief description of it's purpose. It will then be tested thoroughly by the community and based on feedback will be submitted here in the Shop for approval and sent out to the dev so he can add the profile to the Shop in Ktweaker!
Useful Links​
Information about profiles can be found HERE
Interested in learning how to fine tune this kernel but not sure of where to start?
Please refer to this Ktweaker User Guide (thanks to @Perseus71) and you'll be tweaking in no time!
Ktoonservativeq governor adjustments explained HERE

Reserved

Reserved..

just in case

Are the Same
LuigiBull23 said:
**********T-MOBILE**********​
Downloads
Touchwiz Lollipop 5.0 VERSIONS:
https://copy.com/NGddRACV6Nm1xulA
Main kernel thread: http://forum.xda-developers.com/tmo...lopment/kernel-kt-sgs6e-ocv-ktweaker-t3099758
Click to expand...
Click to collapse
Hello the G925W8 and G925T its the same phone? use the same Kernel, Can I flash my G925T with sotck G925W8 frimware with Odin? maybe this frimware ask about the unlock code..

fabioplata said:
Hello the G925W8 and G925T its the same phone? use the same Kernel, Can I flash my G925T with sotck G925W8 frimware with Odin? maybe this frimware ask about the unlock code..
Click to expand...
Click to collapse
Yes they are the same, therefore use the same kernel. Not sure about the firmware but you're willing to try. However, as I'm sure you know I take no responsibility of the end result.

fabioplata said:
Hello the G925W8 and G925T its the same phone? use the same Kernel, Can I flash my G925T with sotck G925W8 frimware with Odin? maybe this frimware ask about the unlock code..
Click to expand...
Click to collapse
+1. Let us know if it works especially the sim unlock. Thanks

what worst?
LuigiBull23 said:
Yes they are the same, therefore use the same kernel. Not sure about the firmware but you're willing to try. However, as I'm sure you know I take no responsibility of the end result.
Click to expand...
Click to collapse
What its the worst?? Maybe error in the Odin and need flash with the stock firmware or maybe I can damage the phone?

fabioplata said:
What its the worst?? Maybe error in the Odin and need flash with the stock firmware or maybe I can damage the phone?
Click to expand...
Click to collapse
The worst I'd say is probably a soft brick since the devices are nearly identical but I still can't guarantee a positive result for you. It's a decision you're gonna have to make among yourself.

dont work
LuigiBull23 said:
The worst I'd say is probably a soft brick since the devices are nearly identical but I still can't guarantee a positive result for you. It's a decision you're gonna have to make among yourself.
Click to expand...
Click to collapse
Dont work, in Odin don't work, fail in Odin and now I have my phone in downloaded mode, stuck in this mode, I hope when de battery dies the phone start normally.

fabioplata said:
Dont work, in Odin don't work, fail in Odin and now I have my phone in downloaded mode, stuck in this mode, I hope when de battery dies the phone start normally.
Click to expand...
Click to collapse
Attempt to boot into recovery and wipe your data.

fabioplata said:
Dont work, in Odin don't work, fail in Odin and now I have my phone in downloaded mode, stuck in this mode, I hope when de battery dies the phone start normally.
Click to expand...
Click to collapse
just press power+volume down and it will restart

thanks
batillojr said:
just press power+volume down and it will restart
Click to expand...
Click to collapse
Ok, thanks.. Works for me..
The phone start normally but with Sim lock :crying:

fabioplata said:
Ok, thanks.. Works for me..
The phone start normally but with Sim lock :crying:
Click to expand...
Click to collapse
i know, i received the unlock code but won't work , i tried different roms but always says unlock unsuccessful , s***t ! I'm giving up , i'm just going to sell it on craigslist

I can't
batillojr said:
i know, i received the unlock code but won't work , i tried different roms but always says unlock unsuccessful , s***t ! I'm giving up , i'm just going to sell it on craigslist
Click to expand...
Click to collapse
Oh no.. I can't do that.. I'm in Colombia, I can't sell the phone buecouse don't work with local company's.. ..
I hope a solution.

fabioplata said:
Oh no.. I can't do that.. I'm in Colombia, I can't sell the phone buecouse don't work with local company's.. ..
I hope a solution.
Click to expand...
Click to collapse
Ya se, estamos en una situacion muy dificil , ojala que exista una solucion pronto.. por mientras seguire usando mi nexus6

Very awesome

Good thread dude, loaded some of these on to my phone

[Q&A][UNOFFICIAL] CyanogenMod/LineageOS

Q&A for CyanogenMod/LineageOS for Celox Devices (Hercules & Skyrocket)​
As requested I created a Q&A thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by me.
Before posting, please use the forum search and read through the discussion thread above for your device. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Frequently Asked Questions​
Q: My device reboots when I receive or make a phone call. Why?
If your using OpenGapps read this: https://github.com/opengapps/openga...boots-when-i-receive-or-make-a-phone-call-why
Click to expand...
Click to collapse
Q: Formatting my SD Card as Internal Storage doesn't work. How to fix it?
Goto Settings > Storage. Click on your external sdcard
Tap the Menu button in the top right and select Settings.
Then choose Format as internal. (This erases all the data on the sdcard so backup if necessary)
Once you click Erase & Format, the device will format your card.
The process may get stuck at 20% and timeout after about 2mins. If it does reboot into recovery after it times out.
In TWRP, select Wipe then Advanced Wipe. Select "MicroSD Card - Data" and click "Repair or Change File System".
Choose, "Change File System" and select FAT. Then swipe to change.
Reboot, then goto Settings > Storage. Your sdcard should appear as corrupted.
Continue and format as internal storage. It should then get past 20%. If it does, continue with the steps shown to you.
Click to expand...
Click to collapse

[FONT=Arial,Roboto,Helvetica Neue,Helvetica,Verdana,sans-serif]Frequently Asked Questions[/FONT]​
Since this is a unified thread, I will use Celox to refer to both the Hercules and the Skyrocket. This was their planned codename for the LTE S2, and both use the celox-common branch in source code.
Q: How do I root my Celox? I flashed SuperSU, and my phone won't boot!
A: You don't need SuperSU. Root access is baked into the ROM.
Wipe everything and install the ROM without SuperSU. Now, in Developer options, set Root access to Apps and ADB. If you really, really, want SuperSU, install it from the Play Store and have it install it directly without recovery. (not confirmed working, but should work.)
Q: Do I install this like any other ROM? Why can't I install Gapps?
A: No. This is a virtually partitioned ROM, common in today's Celox ROMs. The different partition layout is necessary to take full advantage of your phone.
Q: Clean flash or dirty flash?
A: I always dirty flash. I never wipe unless I am switching ROMs. You may want to wipe, your choice.
Q: Virtual repartition? Whaaaaaat? Do I need a PIT file? Will this damage my device?
A: The classic issues with the S2 are:
Not having enough room to install apps
Being forced to use tiny Gapps packages
having waaaaaay too much internal sd card free space, even when you have a real SD card that you haven't filled up either.
Virtual repartitioning changes the way the system sees the partitions ("sections" of the 16GB of storage), making it similar to the 16GB Samsung Galaxy S3. This fixes all of those problems!
Here is what happens:
To make more room for apps and data, we made that SD card partition multitask as apps, data, and the internal SD card storage, emulated at /data/media/0, like modern devices. This will wipe those files on the internal SD card partition, though! You now get 11.2GB freely usable by the system.
Since Lollipop, ROMs have been increasing in size greatly. They even use a different installation method. Our measly 598MB /system partition, which couldn't even hold all of 4.1.2 TouchWiz, has been moved to what /data was before. That means 2GB for the ROM, Gapps (yes, you can even flash STOCK!), BusyBox, root stuff, extensions, you name it!
And that 598MB /system partition becomes /cache, because you can always have more cache!
No PIT is needed, and, if you flashed a PIT (like the one that gives you 6GB for data), flash it back to stock! You will end up with 7GB shared for the internal SD card and app data and 6GB for /system, which is ridiculous.
And the best part is: Nothing is damaged. It is 100% safe! It is just a renaming scheme, and you can always flash to stock in Odin.
Q: Which Gapps should I use?
A: Well, as always, it is your decision, so so as you wish. I personally use Nano, which I also recommend. However, you need to install keyboard_patch.zip (attached to this post) after a Full or smaller Gapps or you will get spammed by "Unfortunately, Android Keyboard (AOSP) has stopped.", making it impossible to set up your device.
Stock fixes this issue, but it also adds crapware that I bet you don't need, like Google Sheets, Google Maps, Google+, and especially Chrome.
Q: HALP!! I'm getting "Unfortunately, Android Keyboard (AOSP) has stopped.", I can't set up my phone, and I am about ready to throw this thing at the wall!!!!!1!
A: Calm down. Breathe. I know it is annoying and gives you headaches.
Just reboot into recovery (using the key combo), and flash keyboard_patch.zip, attached to this post.
Q: Whenever I browse the web in Chrome, my phone goes berserk! It slows down, shows me black screens then the lockscreen, etc.
A: Don't use Chrome. The stock browser is about as good and doesn't wreak havoc to our device. However, this is replaced when you flash a larger Gapps package. I recommend using Nano and installing what you want instead. Just wipe system, flash ROM, Nano, keyboard_patch.zip, and reboot. Alternatively, you can use Opera, which has everything Chrome has except Google account bookmark sync and bloat.
Q: I have one of the following issues:
Calls don't work. They reboot or say "Cellular network not available."
When I turn on my device, I don't have a data connection.
A: You flashed the wrong build. Flash anything after 20160126 and those issues are fixed!
Q: My battery life is bad.
A: Here are some general tips I use:
Turn data, WiFi, GPS and Bluetooth off when you are not using them.
Understand that lower signal = shorter battery life.
Settings > WiFi > Menu > Advanced > Keep WiFi on during sleep > Only when plugged in.
Settings > WiFi > Menu > Advanced > Always allow scanning > Off.
Black wallpaper = good.
Underclock/undervolt.
Lower brightness to the minimum you can see.
Enable the Power saver profile (currently not working on 2/16).
Install the blacked out // regression+ theme, which makes most things black. Pure black = good.
If you really want to stretch your battery life, you can do these extreme tweaks, however, they can affect the functionality of your phone.
Green-only mode. It looks pretty awesome and saves battery life. In terms of battery life, AMOLED screens get better battery life depending on the color displayed on the screen. Green > Red > Blue. Black uses almost no energy.
Set to blacked out // regression+
Black wallpaper
Brightness to 0%
Settings > Developer options > Simulate color space > Monochromacy. This makes it so you can (mostly) see non-green colors.
Settings > Display > LiveDisplay > Color calibration and set all but green to 0%.
Download [root] Naptime (with root enabled) and enable the Aggressive Doze mode. Your phone will be practically off (only the cell radio with data off is running) and you will not receive most notifications, sans phone calls, text messages, alarms, and seriously important notifications as soon as the screen turns off. This is also naturally enabled when you leave your phone unplugged and not moving for 30 minutes.
Hold down the power button and select "Power off". This is a feature that causes your phone to use absolutely no power, however, your phone will take about a minute or two to exit this mode and you will not receive any calls, notifications, texts, or anything and WiFi, mobile networks, Bluetooth, GPS and the CPU will be disabled during this mode.
Q: After 30 minutes of my phone's screen being off, WiFi turns off. I just can't seem to shake this bug!
{
"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"
}
That is called "Doze", it is a built-in feature added in Android to attempt to save battery. Jerry Hildenbrand did a good job explaining this at Android Central.
You can configure this using [root] Naptime, but it is a rather advanced tool.
Q: My keys stopped working! What did I do wrong?
A: Disable Sweep2wake in the "Advanced Settings" app. That tweak is cool, but not yet stable enough for daily use.
Q: How do I make things smaller?
A: Settings > Display & lights > LCD density.
Thankfully, they fixed the alignment bug, so you no longer need to edit your build.prop.
The larger the number, the larger things will be, and the smaller the device will identify as.
240 is the default. The 4.5 in (11.43 cm) device is recognized as a measly 3.89 in (9.87 cm). Friends don't let friends stay on 240 DPI.
Technically, the Celox has a DPI of 207, but apps work best with multiples of 20.
I personally recommend 200dpi, which makes the device identify as 4.66 in (11.85 cm). It is quite nice.
However, with a non-standard DPI (standards are 120, 160, 240, 320, 480, and 640), it can cause scaling issues like blurriness.
Q: Should I use EXT4 or F2FS?
A: I use F2FS. F2FS is safer for your data, writes faster, and is actually designed for flash memory (it is called Flash-Friendly File System), unlike EXT4, which is made for a hard drive. However, some people encountered issues with F2FS and the Play Store.
EXT4 is tried and true, and is still relevant.
Q: Why does my camera keep crashing?
A: In the Advanced Settings app, check "Force low-power flash".
Q: I get random reboots. I see the Samsung logo, then a black screen! Grr!
A: At the time of this writing, 1/26 (sometimes 1/27) is the most stable. Try flashing that.
Q: How do I remove the pesky # on the status bar?
A: Install this Xposed module, or it is also a part of this all-in-one tweakbox by the same developer.
Q: Are there any cool features in this ROM/Kernel?
A: Yes, there are more features in this than the usual CyanogenMod Celox kernel. Some features are still being worked on and are a bit unstable, but testing and fixing is welcome on our GitHub repo!
We have, so far:
Wake/Sleep:
sweep2wake
doubletap2wake
doubletap2sleep
pocket detection (enable in Kernel Adiutor)
Click to expand...
Click to collapse
Miscellaneous:
Backlight notification (the keys light up like the LED indicator we never had)
F2FS support
Screen undervolting to -500mV
Low-power flash
zRAM (compressed RAM)
Magically added more RAM: Now we have 834MB.
Click to expand...
Click to collapse
CPU general
Overclock to 1.83GHz
Under/Overvolting
A democracy of governors (see below)
GPU can be overclocked to 320MHz
Click to expand...
Click to collapse
CPU Governors:
Bold are considered (mostly) stable.
hyper
badass
conservative
gaming
interactive
interactiveX
lazy
lionheart
minmax
ondemand (the default)
performance
powersave (though this just locks at the minimum frequency)
sakuractive
samsung
scary
smartassV2
uberdemand
userspace
wheatley
Click to expand...
Click to collapse
I/O Schedulers:
bfq
cfq
deadline
noop
row
Click to expand...
Click to collapse
If you want more, request it!
Or... even better, contribute to the kernel on Github.
Q: Why can't I configure my CPU governors?
There was a bug in the 2/16 build that added governors, but they had issues with case-sensitivity. Flash 2/22 or newer and you get governors and configuration.
Q: When will we get an update?
A: Be patient! Or build it yourself. Don't forget that some people have lives, and some people don't have lives but still aren't going to constantly update.
I will update this with more questions and answers.
Please don't quote this whole thing. Just mention @Easy_as_Pi_3.14 and I should respond quickly. Or don't, I am subscribed to this thread and love to answer questions.

Easy_as_Pi_3.14 said:
Q: My battery life is bad.
Sorry, this isn't the best ROM for battery life. That hasn't really been hammered out yet.
However, here are some general tips I use:
Turn data, WiFi, GPS and Bluetooth off when you are not using them.
Black wallpaper = good.
Underclock/undervolt.
Lower brightness to the minimum you can see.
Enable the Power saver profile (currently not working on 2/16).
Install the blacked out // regression+ theme, which makes most things black. Pure black = good.
If you really want to stretch your battery life, you can do these extreme tweaks, however, they can affect the functionality of your phone.
Green-only mode. It looks pretty awesome and saves battery life. In terms of battery life, AMOLED screens get better battery life depending on the color displayed on the screen. Green > Red > Blue. Black uses almost no energy.
Set to blacked out // regression+
Black wallpaper
Brightness to 0%
Settings > Developer options > Simulate color space > Monochromacy. This makes it so you can (mostly) see non-green colors.
Settings > Display > LiveDisplay > Color calibration and set all but green to 0%.
Download [root] Naptime (with root enabled) and enable the Aggressive Doze mode. Your phone will be practically off (only the cell radio with data off is running) and you will not receive most notifications, sans phone calls, text messages, alarms, and seriously important notifications as soon as the screen turns off. This is also naturally enabled when you leave your phone unplugged and not moving for 30 minutes.
Hold down the power button and select "Power off". This is a feature that causes your phone to use absolutely no power, however, your phone will take about a minute or two to exit this mode and you will not receive any calls, notifications, texts, or anything and WiFi, mobile networks, Bluetooth, GPS and the CPU will be disabled during this mode.
Click to expand...
Click to collapse
I have to differ with this point. As I have said many times in the main thread, my battery life has been awesome. I have a healthy battery. You have stated that your battery is nearly dead and that you jump through these hoops to get it to last.
I post this so that people who see this don't think that this rom is bad for battery life. It's not, if you have a healthy battery. Here are my current settings:
Screen always on Auto Brightness
Wifi Always on (even when connected to Data)
Sync is always on
NFC off
BT off
I use data about 25% of the time
When on Data I have location set to battery saving
I use the Balanced battery setting
I make all my calls through Hangouts
I have dozens of apps installed
I am using Rom V. 1/26 (dirty flashed)
My average battery life right now is about 24-36 hours with 1.5-2.5 hours of Screen on Time. And my battery charges from about 10% to full in about two hours. My best battery life so far has been about 49 hours with 1.25 hours of SOT before needing to recharge. My average Doze usage is about 1.5%/hour- this is without tinkering with Doze settings with an app.
This battery life is on par with newer devices.
edit. Here is a screenshot of my battery usage right now. Nearly two days and this is with about 1 hour of SOT

cameraddict said:
I have to differ with this point. As I have said many times in the main thread, my battery life has been awesome. I have a healthy battery. You have stated that your battery is nearly dead and that you jump through these hoops to get it to last.
I post this so that people who see this don't think that this rom is bad for battery life. It's not, if you have a healthy battery. Here are my current settings:
Screen always on Auto Brightness
Wifi Always on (even when connected to Data)
Sync is always on
NFC off
BT off
I use data about 25% of the time
When on Data I have location set to battery saving
I use the Balanced battery setting
I make all my calls through Hangouts
I have dozens of apps installed
I am using Rom V. 1/26 (dirty flashed)
My average battery life right now is about 24-36 hours with 1.5-2.5 hours of Screen on Time. And my battery charges from about 10% to full in about two hours. My best battery life so far has been about 49 hours with 1.25 hours of SOT before needing to recharge. My average Doze usage is about 1.5%/hour- this is without tinkering with Doze settings with an app.
This battery life is on par with newer devices.
edit. Here is a screenshot of my battery usage right now. Nearly two days and this is with about 1 hour of SOT
Click to expand...
Click to collapse
Well,
You had amazing signal 24/7. Damn you, T-Mobile!!!!! (I miss the days of the you-step-indoors-and-you-lose-signal and AT&T users laugh)
1 hour of SOT. Try this: Marathon it. Do a YouTube playlist. Go on a Google Search frenzy.
You were in Doze 95% of the time.
David (not even gonna try to spell his username, too late at night) was also comparing his battery life to 4.4 AOKP. I have always heard that AOKP is amazing on battery life.
Update, here is my battery life. The Doze part was me using my S3 when this was on my bed, and then finally watching The Force Awakens. (PS: Great movie!)
And that is in airplane mode the whole time.
The rest was mostly me web browsing or watching a YouTube playlist.
Sent from my SGH-I727 using Tapatalk

Great job on this rom. Running great on 1/26. Didn't see it but is there a way to disable superuser icon in the status bar? I saw it for alarm, wifi, etc.... But not for SU. Just curious. Thanks.

tommyguns818 said:
Great job on this rom. Running great on 1/26. Didn't see it but is there a way to disable superuser icon in the status bar? I saw it for alarm, wifi, etc.... But not for SU. Just curious. Thanks.
Click to expand...
Click to collapse
Nope. There may be Yes, there is an Xposed module for that. See two posts down.
Sent from my SGH-I727 using Tapatalk

Easy_as_Pi_3.14 said:
Well,
You had amazing signal 24/7. Damn you, T-Mobile!!!!! (I miss the days of the you-step-indoors-and-you-lose-signal and AT&T users laugh)
1 hour of SOT. Try this: Marathon it. Do a YouTube playlist. Go on a Google Search frenzy.
You were in Doze 95% of the time.
Click to expand...
Click to collapse
Yeah, I get pretty good signal here. I live in a major city. :good:
But about 8 hours of that was in an area of low signal. Also, my Doze usage was for nearly two days! And I didn't baby the phone. I just used it for messaging/calls/email and a few searches, and my calendar and updating a few apps in that time. When I plugged it in this morning I had hit 48 hours with 1.25 SOT with 4% left. I could have gone another few hours if need be.
My average SOT time is closer to 2.5 hours with about 24 hours standby (Doze). I've gotten as high as about 4 hours SOT with about 18 hours standby. I've already run a high drain test, SOT almost at 100% of the time, it averaged about 20%/hour. So at that rate the device would last for about 5 hours. But that is not average usage. My high usage of 3-4 hours with 18 hours standby is a better metric. And by all standards, this is excellent battery life for a device with an 1800mah battery without battery saving features engaged!
Oh, and my Doze usage last night was at 0.9%/hour

tommyguns818 said:
Great job on this rom. Running great on 1/26. Didn't see it but is there a way to disable superuser icon in the status bar? I saw it for alarm, wifi, etc.... But not for SU. Just curious. Thanks.
Click to expand...
Click to collapse
Yep, there is an Xposed mod for that! Disable su indicator (CM12) or in his all-in-one here.
I updated the Q&A. Thanks for asking that question!

@Easy_as_Pi_3.14 can I call you 22/7's?
You might want to include my video demonstrations of the wake algorithms in the FAQ
https://www.youtube.com/playlist?list=PLZ_n933bbFxFX7UUVjookMDEl1DYShSfg
(Sweep2Sleep and leniency are irrelevant to this kernel)
Also make a note that pocket detection makes wake controls not work when it's sufficiently dark
(My algorithm uses the light sensor data to check if it's in a pocket, YMMV on "sufficiently")
Also, btw, you might wanna make a list of recommended stable governors
IMO Uberdemand seems to be one of them
Further more I recommend putting that f2fs is only for data and cache (or maybe put a guide with how to convert to it)
Also, you are missing a few things in the kernel features that might be good to mention, and maybe explain what they are
Vibration Intensity, TCP Congestion Controls, KCAL, MDP Cooler Colors Control
I'll keep thinking of stuff to add to the FAQ
No doubt it will get bigger and bigger as time goes on :/

javelinanddart said:
@Easy_as_Pi_3.14 can I call you 22/7's?
You might want to include my video demonstrations of the wake algorithms in the FAQ
https://www.youtube.com/playlist?list=PLZ_n933bbFxFX7UUVjookMDEl1DYShSfg
(Sweep2Sleep and leniency are irrelevant to this kernel)
Also make a note that pocket detection makes wake controls not work when it's sufficiently dark
(My algorithm uses the light sensor data to check if it's in a pocket, YMMV on "sufficiently")
Also, btw, you might wanna make a list of recommended stable governors
IMO Uberdemand seems to be one of them
Further more I recommend putting that f2fs is only for data and cache (or maybe put a guide with how to convert to it)
Also, you are missing a few things in the kernel features that might be good to mention, and maybe explain what they are
Vibration Intensity, TCP Congestion Controls, KCAL, MDP Cooler Colors Control
I'll keep thinking of stuff to add to the FAQ
No doubt it will get bigger and bigger as time goes on :/
Click to expand...
Click to collapse
For short, call me @π.
Or, 355/113 will still get my attention.

Governor Explanations
I found this interesting thread about different governors, how they work and how to tweak them. Thought some might find it interesting:

@bryan2894, I noticed that the Show CPU usage in Developer options is blocked by SELinux.
I know it is silly, but here is the message:
Code:
type=1400 audit(1456274524.501:678): avc: denied { search } for pid=743 comm="ndroid.systemui" name="3846" dev=proc ino=31386 scontext=u:r:platform_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0

Deleted

Deleted

@bryan2894 @javelinanddart
I got a logcat/dmesg of the infamous touchkey derp.
I got it around 6:00.
Sorry about the "MP-Decision" spam.

Couldn't find it, but is there power menu options to add screenshot?

tommyguns818 said:
Couldn't find it, but is there power menu options to add screenshot?
Click to expand...
Click to collapse
It is there already for me.
However, I found it easier to either use the key combo (volume first helps) or downloading an advanced file manager (my favorite), open Now On Tap (long-press Home in virtual keys, Menu or Search if I recall correctly on touchkeys), hit the share button, then use Save as.
Sent from my SGH-I727 using Tapatalk

Easy_as_Pi_3.14 said:
@bryan2894 @javelinanddart
I got a logcat/dmesg of the infamous touchkey derp.
I got it around 6:00.
Sorry about the "MP-Decision" spam.
Click to expand...
Click to collapse
Yeah idk about the logcat (not my forte), but I looked for some touchkey errors in kmsg:
Code:
[19778.598175] [TKEY] tkey_vdd_enable: enter
[19778.598358] tkey_led_vdd_enable 0
[19778.732757] [TKEY] sec_touchkey_early_resume
[19778.732788] [TKEY] tkey_vdd_enable: enter
[19778.732849] tkey_led_vdd_enable 1
[19779.286621] [TKEY] enter touchkey_auto_calibration
[19952.978363] key pressed
[19953.873016] key released
[19958.626525] key pressed
[19959.776763] key released
[19969.971923] key pressed
[19970.642944] key released
[19977.845245] key pressed
[19978.931579] key released
EDIT: @Easy_as_Pi_3.14 What is the touchkey derp btw? I'm clueless about that, never heard of it.

javelinanddart said:
Yeah idk about the logcat (not my forte), but I looked for some touchkey errors in kmsg:
Code:
[19778.598175] [TKEY] tkey_vdd_enable: enter
[19778.598358] tkey_led_vdd_enable 0
[19778.732757] [TKEY] sec_touchkey_early_resume
[19778.732788] [TKEY] tkey_vdd_enable: enter
[19778.732849] tkey_led_vdd_enable 1
[19779.286621] [TKEY] enter touchkey_auto_calibration
[19952.978363] key pressed
[19953.873016] key released
[19958.626525] key pressed
[19959.776763] key released
[19969.971923] key pressed
[19970.642944] key released
[19977.845245] key pressed
[19978.931579] key released
EDIT: @Easy_as_Pi_3.14 What is the touchkey derp btw? I'm clueless about that, never heard of it.
Click to expand...
Click to collapse
Sweep2wake sometimes makes the touchkeys stop working.
Sent from my SGH-I747 using Tapatalk

Easy_as_Pi_3.14 said:
Sweep2wake sometimes makes the touchkeys stop working.
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hmmm... I've had that before as well, but I do not recall having it on hercules (although I'm on CM11)
I had it on T769 (Candy 5.1)
So maybe it's a LP+ Issue?
Does anyone remember having it from before LP?

Thermals and Kernel Managers

Thermals, Kernel Managers and their affect on short and long term battery life.
As requested, by fellow LePro 3 owners, I created this thread for a discussion on the benefits of thermal management, using manual thermal settings, and sharing flashable thermals and user settings. To be clear I am not yet an expert on this subject, so I am learning along with everyone else. But, why not share the experience?
Of course we want our phones to last, while also pushing them to their limits, but in a safe and efficient manner. Recently our developers have shared their ideas on thermal management, and they have been gracious enough to allow us access to their own settings, that can be used across multiple builds. See the link below to download the first set of flashable thermal management options.
Recently, some of us have encountered shutdown issues, with some roms having battery stats reporting issues, unexpected shutdowns, and unrelated unrelated lockscreen issues. We users have found that often these troubled builds can be fixed by flashing a fix. Such as the thermals from a previous or other builds that did not have the same issue. Fortunately, it appears that we can use alternate perf and thermal management files that have not only offered a quick fix for some of these current issues, but also offers a longterm solution for using old, new, and future roms builds...collectively. :good:
The plan is to make this discussion much more extensive and simple
So consider this initial post to be an ever changing rough draft.
The end goal is to make it much easier for people to access and share their thermal management files or settings in one easily found central location, and hopefully for everyone to share their suggestions along the way
Helpful to Gamers who want safe power and speed.
Helpful to Non-Gamer's who want simply want stable performance, long battery life
Help everyone by helping us learn to optimize our phones to last for the longterm.
For me, no more repeating the same stuff over and over on various Rom threads, or private messages. No more having trouble digging through threads to find a recommended thermal or setting. So please participate, we can keep the OP updated whenever anything new comes along. Should I get access to something new I will add it to the Megadrive and make a post
Inventory
So far we have the thermals from Lineage, AEX, Balkan, AICP, EUI and in my view one the best is the latest by Jabashque. The idea of this post is to share the thermal settings so that they can be used on whichever ROM you want to try out.
Finally, you do not necessarily need to use these thermals unless you have an issue with general usage, heat or battery life. However, you will immediately notice the benefits.
Edit ( Updated Info)
Regarding kernels: Personally, I use BlackScreen 6.3, it has a long list of governors and I like options.
Currently the best thermal option is the Jabashque edit ( Thermal Fix 7 ) Get it Here: https://forum.xda-developers.com/showpost.php?p=78717015&postcount=18
These thermals work!
Over the past 2 weeks, I have gone back and tried several old ROMs, and these thermal and profiles make those old Roms perform so much better! For example, the September 3rd JMXL version of DotOS.: Yes, Its outstanding with the Sergey thermal. BootLegger's is also much improved, and it was already pretty great as it was. The Miui ROMs, are significantly improved by far! etc.
Of course we have so many great Roms. Occasionally, we get a build that is experimental and it may have unexpected issues. We have seen over the past week that flashing an alternate thermal is a perfect way to save the installation without having to revert to an earlier build. I mentioned old Roms above, they also work on every single Pie Rom.
Here is My Mega Drive Link for all of Thermals that I have collected so far
https://mega.nz/#F!9EokAQTb!Au6cBnJaCJXZrUlaXSLjhg
Alternate Link with key
Link: https://mega.nz/#F!9EokAQTb
Key: Au6cBnJaCJXZrUlaXSLjhg
Jabasque's thermals are in the Jabashque folder. Version 1 and 2 :
Probably shouldn't result in any difference if not gaming.
"Most likely, it would only be noticeable if you're not throttled down to 1440/1900MHz and you're running something that's using 100% cpu" ( Jabashque)
What to use
If you are wanting long battery life and low temperatures use Sergey's thermal or JaBashque version 1
If you want stock EUI faster throttling but slightly higher temps use the ShivateJappedi EUI thermal.
If you want to leave your cores unchanged from the default setting with higher temp throttling, more full power access and yet still safe while use JaBashque 6 Its a rework of the EUI 30s thermals designed to work better on modern Pie Roms : See more information here: https://review.lineageos.org/c/LineageOS/android_device_leeco_zl1/+/238809
Soon, I will create a post in the reserved section below to deeply define the details and differences between these thermals. Because while they all have similarities, they are also very different from one another.
In addition, I plan to add various kernel manager settings for various uses : Gaming, Long Life etc.
Finally, even when moving to another Rom. kernel manager programs such as Ex Kernel Manager will allow you to import and use saved profiles. It seems that it is possible to save the best of each of these thermals by saving the profiles of each. We can share those settings! Then later you can manually choose within your kernel manager which settings you want to use by simply importing choosing a preferred profile.
I hope this clears up the confusion. As mentioned this is a work in progress that was requested by 3 people. This is just the beginning of this discussion that will help everyone understand how to use Kernel Managers and the add-on thermals patches. I need to do some further research to make it all worthwhile . For example, although I love the elementalX governor, I haven't researched it enough to explain why I think it's better. So I plan to find out specifically what it's actually doing vs what other governors do, and how does changing sample rates, and wake locks affect performance and battery life etc.
If there are any experts out there? Please chime in and contribute.
See Updated information from Jabashque, which explains the differences between patch 1 and patch 2
https://forum.xda-developers.com/showpost.php?p=78670166&postcount=2
Installation
Dirty flash the patch that you want to use..thats it.
If you want to try a different patch, dirty flash the Rom, reflash Magisk and dirty flash the patch
You can manually adjust settings by going to /vendor/etc/thermal-engine.conf

Update from JaBashque Edit April 21 2019: ( I use ThermalFix7, its my personal favorite/ it is the best and the safest period.)
@tsongming
Hey, after seeing your thread about thermals, I felt I should write an explanation about how my v1 and v2 differ from stock EUI thermals that you could add to that forum post, since the one you have on there was me describing the difference between v1 and v2, not stock EUI: "JaBashque"
There are two different set of sensors that the original config monitors for the CPU:
the CPU temp sensors (tsens_tz_sensor{4,6,9,11}) and xo_therm_buf. The CPU temp sensors measure the temps of the cores themselves. xo_therm_buf measures what seems to be some sort of overall temperature, though I'm not sure what in particular. However, xo_therm_buf does correlate more directly with how hot your phone feels.
Original:
thermal-engine rapidly throttles your CPU down to 902MHz on the little cores and 825MHz on the big cores when any one of the cores hits 95C, and stops only when the hottest core drops back to 65C. When xo_therm_buf gets to 43C, thermal-engine slowly throttles all your cores to 902MHZ little and 825MHz big until xo_therm_buf drops back to 40C.
Patchset 1:
thermal-engine rapidly throttles your CPU down to 902MHz on the little cores and 825MHz on the big cores when any one of the cores hits 85C, and stops only when the hottest core drops back to 65C. When xo_therm_buf gets to 37C, thermal-engine throttles all your cores to 1440MHZ little and 1900MHz big until xo_therm_buf drops back to 34C. When xo_therm_buf gets to 43C, thermal-engine throttles all your cores to 1132MHZ little and 1363MHz big until xo_therm_buf drops back to 40C. When xo_therm_buf gets to 50C, thermal-engine throttles all your cores to 979MHZ little and 1132MHz big until xo_therm_buf drops back to 43C.
Patchset 2:
thermal-engine throttles your CPU down to 1516MHz on the little cores and 2054MHz on the big cores when any one of the cores hits 95C, and stops only when the hottest core drops back to 65C.
This change was made because I realized that the previous version still had a situation where the CPU performance can tank unpredictably. xo_therm_buf-related CPU throttling is same as Patchset 1.
Thanks to JaBashque for sharing his work! Patch-set 2 is my personal preference. Although the Sergey Perf + Combo is also very good.

@tsongming
Thank you very much for listen us and always give your help.
Rigth now I am on BaikalOS 28th December 2018, if I want to flash any Profile of those, what I should to do (Clean flash? This first, later that etc... and Wich of them I should ti flash for best battery, I do not play on movil)
I am very curious for test this...

I have x722, I do not play. I am now on aex 5.7 oreo. The most depends on the battery, so which zip to flash ? This is a great topic.

kukuteku said:
@tsongming
Thank you very much for listen us and always give your help.
Rigth now I am on BaikalOS 28th December 2018, if I want to flash any Profile of those, what I should to do (Clean flash? This first, later that etc... and Wich of them I should ti flash for best battery, I do not play on movil)
I am very curious for test this...
Click to expand...
Click to collapse
You can dirty flash these thermals.
Personally I like Sergey and Jabashque version 2 the best so far on Pie roms.
The Shivate patch works really well on Marshmallow, Nougat and Oreo.
The Sergey patch works really well on Oreo and Pie, I haven't tried it on Nougat Roms yet.
You can manually adjust settings by going to /vendor/etc/thermal-engine.conf and In this same folder ( vendor/etc) you can also make audio changes, and I am not talking about policies and Tasha.xml files, although you would make changes to those files too, if wanted. This will be something that we can discuss in more detail soon.

gsiwy said:
I have x722, I do not play. I am now on aex 5.7 oreo. The most depends on the battery, so which zip to flash ? This is a great topic.
Click to expand...
Click to collapse
Either the Sergey or the JaBashque 2 with be perfect, depending on what you want.
Use Sergey if your goal is battery saving.
Use JaBashque 2 if you want better gaming performance.

@tsongming thank you for this useful thread. I just have one question. I noticed that sergey's thermal file you uploaded comes also with perf so do you know is it maybe EUI perf and if not is it possible to upload just sergey's thermal without perf? Thanks.

I'm using aex 6.2 and i play a lot of games, but i looking for something that gives the power to run the games and after that (of course after some time without using the cellphone to cooldown) use the phone without worry of him overheat with simple use like 39 or 37 ºC. Do you have something like that?
I have a x722

MnMchill said:
@tsongming thank you for this useful thread. I just have one question. I noticed that sergey's thermal file you uploaded comes also with perf so do you know is it maybe EUI perf and if not is it possible to upload just sergey's thermal without perf? Thanks.
Click to expand...
Click to collapse
Sure, I can extract the perf, I will do that and add it to a separate folder so that there are two options.
Edit: Here is the Sergey thermal only
I removed the perf and added the additional key edit options from the Jabashque patch. So this a combo patch.
Use at your own risk
However, I have tested this and it works fine. I wanted to give the caveat that I am a Noob at this! But its okay. FYI: all I did was remove the perf, so now the perf will come from the rom and I added the Moshe key feature, which some Roms such as AICP includes anyway.
https://mega.nz/#F!ZVpXBQjC!PpXn1ZtLEHJb72Gbw7nWqg

Heitor Lima said:
I'm using aex 6.2 and i play a lot of games, but i looking for something that gives the power to run the games and after that (of course after some time without using the cellphone to cooldown) use the phone without worry of him overheat with simple use like 39 or 37 ºC. Do you have something like that?
I have a x722
Click to expand...
Click to collapse
Use the Jabashque 2

See updated in depth info from JaBashque : here: https://forum.xda-developers.com/showpost.php?p=78670166&postcount=2

So, thank you for your work!!One question,i am at the last AICP Pie,do you believe is better to flash one of these or stay with the settings of AICP?
Thanks in advance!

Don't work
I used to play pubg and the big stay on 1,4 ghz and little on 1,0 ghz

tsongming said:
Sure, I can extract the perf, I will do that and add it to a separate folder so that there are two options.
Edit: Here is the Sergey thermal only
I removed the perf and added the additional key edit options from the Jabashque patch. So this a combo patch.
Use at your own risk
However, I have tested this and it works fine. I wanted to give the caveat that I am a Noob at this! But its okay. FYI: all I did was remove the perf, so now the perf will come from the rom and I added the Moshe key feature, which some Roms such as AICP includes anyway.
https://mega.nz/#F!ZVpXBQjC!PpXn1ZtLEHJb72Gbw7nWqg
Click to expand...
Click to collapse
Works good, thanks.

geo307cc said:
So, thank you for your work!!One question,i am at the last AICP Pie,do you believe is better to flash one of these or stay with the settings of AICP?
Thanks in advance!
Click to expand...
Click to collapse
If you are not having any issues, then don't install any of these.
However, if you want to try it, keep a record of your existing performance, battery life, heat levels for battery and CPU (when idle) and compare that against using these thermals.
If you flash one of these thermals and don't like it. You can quickly return to your previous settings by dirty flashing your rom, or by restoring the system part of a nandroid backup.

Heitor Lima said:
I used to play pubg and the big stay on 1,4 ghz and little on 1,0 ghz
Click to expand...
Click to collapse
So which one of the 5 thermals did you try? Some of them include perf
Understand that you still have to setup your kernel manager. If you are wanting to use it for Gaming use the JaBashque version 2 to and leave the cores on the highest setting.
Yes, it works. It works for me a and a lot of other people on Telegram
If you want low temperatures and long battery life underclock the cores at idle my battery hovers around 85 F and the CPU are around 100-105F
Just so you know you can access your thermal.conf file and edit it manually to increase your thermal limit in /vendor/etc/thermal-engine.conf
Next, save a copy of your existing current setup as a profile, so you can easy switch from one to another with ease and easily compare it to the changes of using an alternative file. You can tweak it to the settings that you are wanting...Just keep safety in mind or you could burn up your CPU.

UpDate!
@jabashque has spent time recently improving his thermals further, and released several new versions .
The latest and greatest is now version 6!
Get it here: https://mega.nz/#!pFoSRaQA!R068WV-YltbQAFzuc3aH72z_OPyrN2uBjgsux2h0dNY
If you like it, please thank him!

Anyone who is using the last build of Jabashque 6 . It has a small error with he tthermal.
Flash this zip file from my Mega drive.
https://mega.nz/#!UZwhAQwY!GDUYQX2Ewcj92jjhs2t-oYnVcUKSbu9WfaOyAJjaKzs
The file adds a GPU setting to the Thermal
Repair by Jabashque: https://mega.nz/#!UZwhAQwY!GDUYQX2Ewcj92jjhs2t-oYnVcUKSbu9WfaOyAJjaKzs
Reference : https://review.lineageos.org/c/LineageOS/android_device_leeco_zl1/+/239612

I want to install Bootleggers os 8.1 on x722 and I have a question: after installing romu and gapps and initial configuration I can flash BS5.1-r3 AND thermal.zip a magisk mantle? will thermal.zip not interfere with BS? Thank you.

gsiwy said:
I want to install Bootleggers os 8.1 on x722 and I have a question: after installing romu and gapps and initial configuration I can flash BS5.1-r3 AND thermal.zip a magisk mantle? will thermal.zip not interfere with BS? Thank you.
Click to expand...
Click to collapse
Sorry I haven't been on XDA much recently, and never received the notification.
If you use Bootleggers, the stock kernel is fine. But blackScreen 6.3 will work fine and it gives you more options. You flash the thermal at anytime. I recommend the Thermal-fix7 which is Jabashque 6 that I edited to fix a typo. No there is no conflict

CHUWI Hipad Root, TWRP, +Info, etc.

Little review and tablet issues:
I've been waiting for this tablet for 1 month and it has finally arrived. I bought this tablet for two reasons:
1. I was looking for a tablet with a Wifi AC chip for ~$100. None of the tablets around that price tag had this type of chip (best had Wifi N chips). Therefore after researching for a little while I found out that this was the only option available. The only alternative was Huawei Mediapad T5, with a worse battery (5K vs 7K mAh) and also a $100+ increment in price (~$100 for the Chuwi vs ~$200 for the Huawei).
2. The tablet it clearly powerful, fast and way better in terms of power than other tablets I've been using (even Samsung Tabs). But there are some issues that may be a turnoff for some users and most of them won't be easily solvable by the company.
After reading some reviews I can confirm several issues that won't be fully resolved:
Screen issues
1. The touch screen it's not the best (better with the latest ROM, see workarounds).
They have made an overkill in the Tablet specs (decacore,...) with a cheap touch panel. The game experience is very poor despite they are selling it as a "Gaming Tablet".
Chuwi seems to be more focused in selling at all costs than actually providing what people expect from their products. Probably they should have been selling this tablet for $50-100 more with a better screen, but this way they would have found other alternative products that may have provoked most people not buying this... difficult decission for Chuwi, ending obviously on a really bad experience (for most of the powerful games, like PUBG mobile)
Here is a video comparing Pocophone F1 with Chuwi Hipad:
https://vimeo.com/313134711
There are clearly some lag issues (the stroke is behind the finger most of the time) and it's very imprecise, without the possibility of draw a perfect line, but a trail of individual dots recognized.
Screen Issues Workarounds (WIP)
- I'm going to test a capacitive pen to see if this makes the touch screen a lesser issue. When I test it will comment. With the latest November update, the touch screen performs a little bit better, but marginally better.
- With the new kernel 3.18.60 (Rom 11th Jan 2019) it seems that the tablet it's a little bit more responsive.
- It works worse with the capacitive pen than with the finger.
Game Streaming Issues - Solved
2. Personally I was not interested in playing games directly on the tablet, but streaming games from my PC. And also found some hindrances:
- Steam Link Beta is not currently working: sound works, input works (touch controls) but video is not showing. Not sure where is the problem but when we start the app an error message says: Steam Link performance hasn't been verified on this device (Techain Hi9Air), so it may not perform well
Game Streaming Issues Workarounds
- I'm currently testing two apps: Remotr, KinoConsole. I like Steam Link because it's fully integrated and works extremely good. I've found some issues in Remotr (drag-n-drop not working) and in KinoConsole (issues with streaming image distorted). I don't find any value in Parsec atm at least for what I'm looking for (playing on the go without have to pre-setup anything).
- I've solved the Issue with Steam Link Beta. Here is the solution: https://www.reddit.com/r/Steam_Link/comments/akz50n/troubleshooting_android_video_issues/?
Wifi Issues
3. WiFi chip is very poor: I've been testing with iperf2 tests and there is a 50% speed reduction vs a Pocophone F1. It's important to say that in the same spot Chuwi Hipad is getting around -70-75dBm while Poco F1 is around -60dBm
If I find new issues I will comment them.
Wifi Issues Workarounds (WIP)
3. With the wifi thing there is nothing to do, if I could possibly return the tablet, I may do it, but since I bought it overseas I may forget about this.
For me it's important to have a good Wifi signal, because as I said I'm using it for playing streamed games and with a bad signal games are unplayable.
- Currently I've switched my AC router to a D-Link DIR 882 with a modded DD-WRT ROM to DHT80 and it's working fine. The chip seem to be really bad compared to other alternatives (like my Pocophone F1 Wifi chip), but I have to say that for under $150 I've not seen an alternative tablet with AC at all at the current moment (1Q 2019)
Dissasembling Chuwi HIPAD for repairing (screen, battery, ...)
One of the issues I've found is that opening the tablet it's extremely difficult compared to other alternatives. The tablets its extremely sealed without any screws and just left to open with pure pressure:
{
"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"
}
The BIG problem is that it's so hard to open the case that I've ended breaking the touch screen, so be extremely careful when pressuring the thing trying to not bend the tablet too much or press on any point of the screen. I changed the screen of a Chuwi Hi8 Pro 30 minutes before doing this, so I know what I'm talking about: I would say that the risk of breaking with this model is 8/10.
Why I've tried to open the case? Because in the last days I noticed that the tablet touch screen was not working. I expected that the cable was not adequatelly plugged, or maybe the touch screen was faulty (I think that the touch screen was faulty so I don't really care about breaking it).
Here is an image of the PCB:
UPDATE: 30/3/2019
I started changing the screen and here is the result:
Two mistakes:
1. Ordering the new screen before being sure that I was able to extract it.
2. Trying to extract it WITHOUT an adequate heat gun (just with a hair dryer)
The screen is TOO big, and they only sell the screen replacement WITHOUT the touch panel. In the majority of the tablets they don't sell the touch panel with the screen replacement, BUT the difference is that the screen are rarely sticked to the panel with industrial glue. Therefore, if you don't have a really good heat gun, you won't be able to remove the panel from the screen and you will end breaking the panel. I've changed a lot of screens in other tablets without hassle just with my hairdryer, but this screen it's way harder. If you have never changed a screen the probability of breaking everything as I did is 100%. But for the cost of this tablet, I'm not sure that going for a service it's worth so If you cannot repair it yourself, i think this tablet is not worth at all.
Development: Rooting, Recovery, ROMS
I would like to create a comprehensive list of Rooting, recovery, possible ROMS, that may appear for this recent tablet in the future. The tablet is new and not very well known for most people yet, so we might have to wait a bit until other users start to find some value in this budget powerful tablet, depite of the caveats we have already found.
Flashing Process with SP Flash Tool (no unlock needed)
Remember: there is a risk of briking the tablet!
This will do a full wipe to your Tablet so remember to backup your data before doing so
This is the easy method to flash the tablet. All we need are some tools:
1. The SP Flash Tool: (Download v5.1728 here)
2. A ROM: (check in the bottom section for ROMs).
3. Drivers: There are multiple options, but here are some working drivers for Windows:
64bit: https://chuwiinnovationtechnologysh...jo5exkkrpmd350sicz4ae45yegp/file/337087008142
32bit: https://chuwiinnovationtechnologysh...jo5exkkrpmd350sicz4ae45yegp/file/337086745908
How to flash with SP Flash Tool:
1. Extract ROM and SP Flash Tool in the same folder. Try to avoid special characters in the folders like chinese chars to avoid issues during flash
2. Open flash_tool.exe
3. In "Download Agent" select MTK_AllinOne_DA.bin
4. In the "Scatter-loading-File" select MT6797_Android_scatter.txt
5. In the "Download Only" dropdown select Firmware Upgrade
6. Turn off the tablet and disconnect the Tablet from the USB cable
7. Press the button "Download" in the top
8. Connect the Tablet to the USB cable
9. If everything it's right (including driver installation) it may appear a red line in the bottom that goes to 100%. Just wait until the process is complete with a green tick opening in a window.
10. If it gets stuck at some point (for example at 72%) for some minutes, it will end failing the installation and you will have to start over. Remember that there is a risk of bricking the tablet.
Rooting process
Remember: there is a risk of briking the tablet!
This will do a full wipe to your Tablet so remember to backup your data before doing so
Last time I did the process was with: Android: 8.0.0 custom build Hipad_v1.1_20181107
After updating to the new ROM (Android: 8.0.0 custom build Hipad_v1.1_20190111) tested root process again and worked flawlessly.
1. First we need to install the USB drivers
64bit: https://chuwiinnovationtechnologysh...jo5exkkrpmd350sicz4ae45yegp/file/337087008142
32bit: https://chuwiinnovationtechnologysh...jo5exkkrpmd350sicz4ae45yegp/file/337086745908
2. Install ADB like any other device. There are multiple tutorials out there.
3. Activate the USB debugging option and the OEM unlocking option in the developers option menu (unlocking it by pressing 7 times in the Build number just like any other Android vanilla device)
4. If we plug the USB to the computer and we do a "adb devices", we will see it listed after permitting in the device:
So far, everything exactly the same as rooting for any other Android device.
5. Download the latest Magisk Manager APK from the site https://github.com/topjohnwu/Magisk/releases/ and install it
6. Download the latest boot.img file (download your ROM to get the boot.img within) and place it somewhere you can find it in your phone (Downloads folder for example).
7. We open Magisk Manager and press "Install"
8. There we press: "Patch Boot Image File" and in the file explorer we select the boot.img file we have already downloaded and wait until it is patched.
9. After it's patched we will see this message:
Patched image is placed in:
/storage/emulated/0/Download/patched_boot.img (or whatever route we have used for installation)
10. Connect the Hipad with the PC and transfer that "patched_boot.img" file to the computer to a directory (for example C:/CHUWI we will use this for the example)
11. Now it's time to flash
Here goes the most risky moment. Because we have to enter the bootloader, unlock it and then flash the new "patched root boot image"
12. We go into the console and type: adb reboot bootloader
And it will automatically reboot into the Fastboot
13. Now we unlock the bootloader with the command: fastboot oem unlock
IMPORTANT: Remember that after OEM unlocking the system will wipe to factory default. Backup everything if you have anything important installed in the device
We will see a message that says: "Unlock bootloader", press Volume up to unlock and Volume down to cancel: We press the volume up button.
14. After this, we have an extended bootloader menu that permits going into fastboot, recovery and system fromt there. At this point we are ready to flash the rooted boot img.
15. We type: fastboot flash boot patched_boot.img
And we will see something like ths:
$ fastboot flash boot patched_boot.img
target reported max download size of 134217728 bytes
sending 'boot' (10415 KB)...
OKAY [ 0.348s]
writing 'boot'...
OKAY [ 0.141s]
finished. total time: 0.489s
16. Finally it's time to reboot to check results by typing: fastboot reboot
17. After OEM unlocking we will see the orange Chuwi logo meaning that we have "unlocked it" and suggesting we are in an "untrusted state". That's fine.
18. Be aware, that after doing this it will take a little bit more than usual to boot Android. Just wait for it.
19. When device has rebooted Magisk Manager will be already installed but we will have to update because everything has been wiped as I warned before. If everything has gone right (maybe we will have to reboot again after the first boot for some updates to take in place) we will see this in Magisk Manager:
20. And that's all folks! Root installed in our device:
TWRP process
At this moment we don't have a TWRP or any other recovery compatible with this hardware, stay tunned.
Official ROMs
* 11th Jan 2019, Android: 8.0.0 custom build Hipad_v1.1_20190111: Download
- Big improvement in the touch screen, It seems that the touch screen it's a little bit more responsive
- New kernel 3.18.60
* 6th Nov 2018, Android: 8.0.0 custom build Hipad_v1.1_20181107 Download
- Slight improvement in the touch screen
Other ROMS
We don't have any custom ROMS available yet
Let's see if some ROM devs want to test this and make a custom ROM like Resurrection Remix 6 (based on Oreo).
Updates
- This tablet will be updated mid-2019 to Android 9.0 Pie: https://forum.xda-developers.com/showpost.php?p=78278868&postcount=994

Thank you very much sir!
You were the first brave one to try rooting on this tablet.

Definitely Touch pad is very unresponsive
Sample video with Hipad vs Pocophone F1: https://vimeo.com/313134711

Dupe

I continue with the issues
Today I've been able to troubleshoot the streaming issue with Steam Link:
https://www.reddit.com/r/Steam_Link/comments/akz50n/troubleshooting_android_video_issues/
Still not a great tablet, but a little bit better today

MiSSigNNo said:
Definitely Touch pad is very unresponsive
Sample video with Hipad vs Pocophone F1: https://vimeo.com/313134711
Click to expand...
Click to collapse
Is that really a fair comparison? 6" vs 10" screen. $330 vs $145. I read your critique and ordered a Hipad anyway. But my most demanding app is Nascar Raceview, so touchscreen response isn't a really big deal to me anyway. I'm going to use it to replace my 2016 10" Samsung Tab A which is getting a little outdated.
I do want to thank you, though, for your effort to improve the Hipad's performance.

lewmur said:
Is that really a fair comparison? 6" vs 10" screen. $330 vs $145.
Click to expand...
Click to collapse
Well, is not a comparison in fact. It's just a demonstration of the situation. How it performs the finger and the stylus in a Poco F1 and how it performs with a Hipad.
If I saw this comparison, made for example, by you, I would have not bought this tablet probably. This is something that has dissapointed me. Still, I'm currently using to play some card games like Artifact and Magic Arena via Steam Link. It's a little bit frustrating when you try to press a button by touching the screen and it just press anywhere else except for the place you are trying to do it. And I have to recognice that I have to play carefully becuase if I press without extreme precision, I may end playing something that it's not intended.
So overall, the tablet it's awesome. A+ But the screen is completely ****. The worst element by far. The second worse: the Wifi AC Chipset, very poor power.
But I was intending to buy a Huawei T5 10.1' to compare between both ($200). And I've ended renouncing to it, because I think that it's fine to go on with the Hipad. I think that for what I need it's more than sufficient.

MiSSigNNo said:
Well, is not a comparison in fact. It's just a demonstration of the situation. How it performs the finger and the stylus in a Poco F1 and how it performs with a Hipad.
If I saw this comparison, made for example, by you, I would have not bought this tablet probably. This is something that has dissapointed me. Still, I'm currently using to play some card games like Artifact and Magic Arena via Steam Link. It's a little bit frustrating when you try to press a button by touching the screen and it just press anywhere else except for the place you are trying to do it. And I have to recognice that I have to play carefully becuase if I press without extreme precision, I may end playing something that it's not intended.
So overall, the tablet it's awesome. A+ But the screen is completely ****. The worst element by far. The second worse: the Wifi AC Chipset, very poor power.
But I was intending to buy a Huawei T5 10.1' to compare between both ($200). And I've ended renouncing to it, because I think that it's fine to go on with the Hipad. I think that for what I need it's more than sufficient.
Click to expand...
Click to collapse
Thank you. You just made my point for me. It was a comparison and, IMO, an unjust one. If you had included the statement "So overall, the tablet is awesome A+", then it would have been more even handed. As it was, I was almost convinced not the buy a Hipad.

No news on an update to address the issue on chuwi forums.
I've read somewhere (not sure where so don't get this for granded) that the hi9 plus also has tricky touch.
I'm starting to feel it is a hardware problem and not a software one.
So bad screen inventory or a flaw on the software side? We'll see.
Which stylus are you using in the video?

MiSSigNNo said:
So overall, the tablet it's awesome. A+ But the screen is completely ****. The worst element by far. The second worse: the Wifi AC Chipset, very poor power.
But I was intending to buy a Huawei T5 10.1' to compare between both ($200). And I've ended renouncing to it, because I think that it's fine to go on with the Hipad. I think that for what I need it's more than sufficient.
Click to expand...
Click to collapse
so i just ordered an alldocube tablet, similar x27 chipset and i've been doing some research before it arrive:
apart from the random touchscreen issue, i think the main problem is with the helios x20 series chipset, is it struggles with responsiveness and "short burst" tasks. i am new user can't post links so just google and run "kraken javascript benchmark" in browser.
the a72 cores in helios x20 should mean you score ~4000 here, but typically i see 9000-10000 in reviews for devices using this chipset. so the problem reported is it is not even utilizing these fast cores in these short bursty tasks. of course this is good for battery saving, but bad for performance/responsiveness.
for longer running benchmarks like geekbench, antutu the cores become active and are OK
so there have been some solutions, for example the meizu 6 got updated firmware that boosts the cores more aggressively, and anandtech review said benchmark results improved 2-2.5x, but they don't say how they do this
some portion of the redmi note 4 phones also use the x20 chipset, it is more laggy than the snapdragon counterpart, and there have been a few tweaks in their forums, this one looks promising to me, google "Redmi note 4 (mtk) better gaming Learn how to get the most out of it (root)"
it seems you first disable the mtk perfservice, so the system uses the default cpu governor. then you make some tweaks
of course you need root and you do this at your own risk etc so make sure you read the miui thread and understand before using the code, also it is a good idea to note down the system default values before you change them, for when you want to revert back.
from the thread here is some recommended code for light gaming and general use to improve response, comments are my interpretation of what it does:
Code:
#background "real time" priority task 0.01ms time allocation
echo 10000 > /dev/cpuctl/bg_non_interactive/cpu.rt_runtime_us
#time between when scheduler reschedules 0.95ms for "real time" priority task
echo 950000 > /dev/cpuctl/cpu.rt_runtime_us
#default time allocated by scheduler for "real time" priority task 1ms
echo 1000000 > /dev/cpuctl/cpu.rt_period_us
#this is feature to take in to account number of cores for allotting time, turn it off to increase response time
echo 0 > /proc/sys/kernel/sched_tunable_scaling
#dynamic voltage frequency scheduler for gpu on
echo 1 > /proc/mali/dvfs_enable
#ignore thermal for gpu on, since the cpu a72 cores
echo 1 > /proc/gpufreq/gpufreq_limited_thermal_ignore heat up and cause throttling
# apparently this unlocks the a72 cores
echo 0 > /proc/ppm/policy/hica_is_limit_big_freq
i think this or some other code on that thread can help the system utilize the strong a72 cores, increasing performance but at expense of battery, if you can tweak it such that Kraken benchmark gets close to 4000 score with acceptable battery, i think it is big success.

Thanks for the suggestions @xygn
Where is the article you are talking about?

MiSSigNNo said:
Thanks for the suggestions @xygn
Where is the article you are talking about?
Click to expand...
Click to collapse
i can't post link because new account, but google "Redmi note 4 (mtk) better gaming Learn how to get the most out of it (root)", there are a few suggestions on that thread

I'm not sure how to interpret the kraken results:
https://mzl.la/2N9PSCZ
I may be testing those parameters to see if there is any improvement.

I've tested your mods and there is no improvement in touchpad responsiveness
Also this policy /proc/ppm/policy/hica_is_limit_big_freq
Was not found.

I've screwed up the recovery trying to create a compatible TWRP. Can anyone send me a working hipad recovery img please?

MiSSigNNo said:
I'm not sure how to interpret the kraken results:
https://mzl.la/2N9PSCZ
I may be testing those parameters to see if there is any improvement.
Click to expand...
Click to collapse
the benchmark is measured in time so the higher the longer it took to execute, on the x20 i've seen as low as 3000. for example google "redmi note 4 x20 anandtech", which kind of makes sense since the a72 cores are about twice as fast, and people have found they don't get utilized at all in some workloads, and this should be able to be tweaked.
MiSSigNNo said:
I've tested your mods and there is no improvement in touchpad responsiveness
Also this policy /proc/ppm/policy/hica_is_limit_big_freq
Was not found.
Click to expand...
Click to collapse
hmm that's disappointing, i'll see how my alldocube responds when i get it, still waiting...
MiSSigNNo said:
I've screwed up the recovery trying to create a compatible TWRP. Can anyone send me a working hipad recovery img please?
Click to expand...
Click to collapse
chuwi has stock firmware is that what you need? i just google "chuwi hipad stock firmware" and second result

xygn said:
chuwi has stock firmware is that what you need? i just google "chuwi hipad stock firmware" and second result
Click to expand...
Click to collapse
No, I need the stock recovery. Fun fact, MIUI by default restores automatically the recovery if you don't have magisk installed. So you don't have to ever worry to end (like me) with a corrupted recovery. Things went wrong when I was trying to flash a new TWRP and I could not save successfully the original recovery unfortunatelly (my bad)

To get the stock recovery is simple. For those that have already rooted with my method:
1. Install the app Diskinfo
2. Enable all partitions in the settings
3. Theorically there should appear a partition like /dev/block/mmcblk0pXX (XX is two numbers)
4. Download Terminal emualtor
5. Run the command "su"
6. Run the command "dd if=/dev/block/mmcblk0pXX of=/sdcard/stock-recovery.img" (remember to replace the XX with the number of the partition of the recovery)
Also can be found in the log with Terminal emulator:
1. Command: "cat /cache/recovery/last_log | grep recovery"
And will get a line like:
19 /recovery emmc /dev/block/...
And then with the path (/dev/block/... ) just need to edit the dd if=/path/... of=/sdcard/stock-recovery.img

Why root?
Just received my Hipad and I'm wondering if it is really worth rooting. Normally, that's the first thing I do with a new tablet. But without any custom ROMs available, is it really worth the irritation of the delay in booting?

lewmur said:
Just received my Hipad and I'm wondering if it is really worth rooting. Normally, that's the first thing I do with a new tablet. But without any custom ROMs available, is it really worth the irritation of the delay in booting?
Click to expand...
Click to collapse
Personally I like rooting to have access to Magisk modules. There are some Magisk modules are that are awesome.
By the way, could you checkout my last post, and try to extract your recovery with the method I showed? I was trying to create a TRWP but I "corrupted" my original recovery.
With a new sane recovery I may try to create a functional TWRP and maybe some custom ROM may follow