Test your sdcard with your phone - Android Software/Hacking General [Developers Only]

Is there a program that will run my sdcard like quemu does on my computer... but on my phone?
sent from my oc'd pos LG P500 running:
Void @ 787mhz
Quad - 585
Linpack - MFLOPS 8.281 / Time 10.12 seconds

So after searching untilled my eyes bled I found nothing on the topic. I think I'm going to try and build an android app "sdcard emmulator". Goal is to have a GUI or fullscreen emmulator that runs the sdcard in a virtual environment much like quemu does on my desktop.
Any suggestions or tips would be much appreciated as I do not program at all this is Greek to me at the moment.
sent from my oc'd pos LG P500 running:
Void @ 787mhz
Quad - 585
Linpack - MFLOPS 8.281 / Time 10.12 seconds

Related

/proc/meminfo shows total memory as 99040KB

/proc/meminfo on my G1 shows total memory as 99040KB. I thought the G1 had 192MB of SDRAM. Clearly I must be missing something here. The free command shows the same as well.
Good question... with that said where is our ROM at too? I don't see 256MB of ROM... by my calculations I am missing about 50MB but I could be wrong.
neoobs said:
Good question... with that said where is our ROM at too? I don't see 256MB of ROM... by my calculations I am missing about 50MB but I could be wrong.
Click to expand...
Click to collapse
The fact that they advertised it has having 256MB of ROM seems strange to me, since the internal memory that comes closest to that (268,400KB - when adding up the total sizes of the /dev /sqlite_stmt_journals /system /data and /cache partitions - is actually 262MB) is definitely not Read-Only-Memory. And it wouldn't appear to be 256MB, unless that /sqlite_stmt_journals is a subdivision of another partition like the /system/modules and /system/xbin (which I obviously left out of my calculations), that would bring it down to 264,304KB or 258MB - pretty close.
But that is still not ROM, so I don't know what they were getting at with that.. Unless I missed a memo and ROM doesn't just mean Read-Only-Memory any more...
I was confused about the use of "ROM" too. Apparently, it's just to differentiate between memory and storage. The /data partition is definitely not read-only.
techvd said:
/proc/meminfo on my G1 shows total memory as 99040KB. I thought the G1 had 192MB of SDRAM. Clearly I must be missing something here. The free command shows the same as well.
Click to expand...
Click to collapse
I think that the rest of the memory is reserver for the framebuffer and video textures etc.
The question was already answered by Hackborn on the mailing list.
https://groups.google.com/group/android-platform/browse_thread/thread/adb2fa9946275b73
i dont think that thread responds to "where the hell are the 100 MB remaining"
i dont believe "radio firmware" + "graphic framebuffers for shadows" + "etc" is eating 100 Mb of memory. I dont believe and in that forum they dont explain the numbers.
windows XP, with 800x600 x 65.000 colors, is able to run with just 64 Mb of ram, and only 200 Mhz. That would give as 120 Mb Free. to run games like diablo 2, baldur's gate (i played baldur's gate with my pentium mmx 200mhz)
This phone is superior than my Pentium 200mhz who had 64 ram. why this phone cant do the same with 3x times memory x 3x times cpu?
Why windows Xp (a real operating system) is running with a lot less resources than android ??? where is our 192 Mb of ram??
a 200mhz Pentium >>>> 384 mhz ARM processor
*) first of all, a pentium is faster than the arm we use, especially for things like gaming.
a PC is optimized for performance, an embedded architecture is optimzied for efficiency (especially regarding power consumption)
*) your PC has a graphiccard that has its own memory.
*) android = linux = real OS.
why do these rants always pop up whenever embedded systems are discussed.
it was the same with the gp2x / pandora scene, the same in every windows mobile forum, etc.
people, get a clue. attend a course about systems architecture or read a book or two...
Take a look here: http://forum.xda-developers.com/showthread.php?t=482228
Same discussion
you saw i called windows xp a real os and you started freaking out, lol !
*) cpu is 528 Mhz clocked down to 384 (google says: to conserve battery!!!!) , so they stole us speed and memory. Performance vs eficiency? i dont buy it. Its all the same running the same kernel.
*) my graphic card sucked balls, old ati radeon 128 with 16mb ram. So, 16 mb doesnt mean a **** in the middle of the 100MB we are missing.
*) android = java = resources devour, when i discover android = java i was disapointed, the real operating system running on my phone is the good kernel+debian armel which i had to host in memory card instead of internal memory because lately google is acting like microsoft. and im starting to think android will be as ****y as windows is.
yea i readed a pair of books and i know how to count, where is my Mhz and where is my Memory?
greetings

Enable JIT in telechips tablets

Hi
If you dont know what JIT is, read the next article:
http://androidandme.com/2010/02/news/jit-compiler-coming-to-android-sooner-than-you-think/
THE FOLOWING STEPS CAN BRICK YOUR TABLET, MAKE IT UNUSABLE OR SLOW. TRY YOURSELF. I ONLY TESTED IT IN A SMARTQ V5 WITH ROOT AND ACCESS TO /SYSTEM.
Hardware.
Smartq V5
Tests:
Reboot
Kill all the apps with Advanced Task killer
Wait 60 secs
Launch Linpack for android or Quadrant Advanced (every launch has a reboot before, and quadrant only runs cpu test)
Results:
Linpack without JIT = 2507 Mflops
Linpack with JIT = 4004 MFlops
Quadrant without JIT = 463 points
Quadrant with JIT = 645 points
To use JIT you must write this line:
dalvik.vm.execution-mode=int:jit
in /system/build.prop
To get back you only must change jit by fast at the end of the line.
To test if JIT is working you must get lines like this in logcat:
D/dalvikvm( 1212): Total arena pages for JIT: 2
All Androids 2.1 delivered with Tablets that have Telechips cpu seems that has the correct libraries, so must work with all of them.
Corvus.
I have Cube U6 / G10 7" pad, will these JIT steps works for my pad ?
I am running android 2.1 Jan 2011 version.

Porting Thunderzap MTK6577 kernel to Star N9588?

I'm interested in overclocking my STAR N9588 it's the MTK6577 1ghz cortex a9 1gb ram and I wanna port this 1.4Ghz kernel over.
Can someone explain exactly how to do that?
thanks
1chris89 said:
I'm interested in overclocking my STAR N9588 it's the MTK6577 1ghz cortex a9 1gb ram and I wanna port this 1.4Ghz kernel over.
Can someone explain exactly how to do that?
thanks
Click to expand...
Click to collapse
Mate, no OEM has realised JB Sources for the MTK6577 as of yet, well Wiko do realised ..
but our dev found them rather incomplete for successfully compiling a kernel!
Wow that really sucks
We should be able to overclock the MTK6577, right? If we put all of our brains together for some super brain storming...
Anyway couldn't I just go into each relevant file being probably 10 or more in /system/device I believe and there's all about max frequency and everything on all these CPU_MAX_FREQ files etc etc...
What do you think?
I just really think the MTK6577 needs some help in the HD decode department and especially a gpu overclock as even the Live wallpaper lags when scrolling...
*OH YEAH*
Can I port CM10 to my STAR N9588?
Thanks bro
1chris89 said:
Wow that really sucks
We should be able to overclock the MTK6577, right? If we put all of our brains together for some super brain storming...
Anyway couldn't I just go into each relevant file being probably 10 or more in /system/device I believe and there's all about max frequency and everything on all these CPU_MAX_FREQ files etc etc...
What do you think?
I just really think the MTK6577 needs some help in the HD decode department and especially a gpu overclock as even the Live wallpaper lags when scrolling...
*OH YEAH*
Can I port CM10 to my STAR N9588?
Thanks bro
Click to expand...
Click to collapse
First, This isnt the Right section to post..Contact a MOD to change the thread to appropraite one... CM isnt yet available for Mediatek phones...SO have to wait....
1chris89 said:
Wow that really sucks
We should be able to overclock the MTK6577, right? If we put all of our brains together for some super brain storming...
Anyway couldn't I just go into each relevant file being probably 10 or more in /system/device I believe and there's all about max frequency and everything on all these CPU_MAX_FREQ files etc etc...
What do you think?
I just really think the MTK6577 needs some help in the HD decode department and especially a gpu overclock as even the Live wallpaper lags when scrolling...
*OH YEAH*
Can I port CM10 to my STAR N9588?
Thanks bro
Click to expand...
Click to collapse
All that is possible if we have a full tree of the sources.. without them even of you try to play with boot.IMG it won't boot and you will be stuck in a rut!
It appears overclocking the thing isn't that hard at all. Only problem is pull the right files, editing them then pushing them back. Like any file in /sys/devices/ etc I'm trying to adb pull /sys/devices and it doesn't seem to pull all the files. So I tried adb pull /sys/devices/*.* and it didn't seem to like that either. I tried editing the files and they simply don't save. So basically I need to say edit the files in the rom .zip prior to flashing in say TWRP and I can get a nice overclock no problem. It's not a matter of the stupid A** MTK crap it's a matter of modifying the android system (Cortex A9) portion with the updated files to allow for overclocking. As it's all so possible and they say the Cortex A9 can handle upwards of 1.6Ghz without any overvolt necessary.
Once I get this rolling I can help a few of you who are truly interested out. Unless you want to continue to think its impossible to do so then I say continue thinking that as it won't get you anywhere in life.
1chris89 said:
It appears overclocking the thing isn't that hard at all. Only problem is pull the right files, editing them then pushing them back. Like any file in /sys/devices/ etc I'm trying to adb pull /sys/devices and it doesn't seem to pull all the files. So I tried adb pull /sys/devices/*.* and it didn't seem to like that either. I tried editing the files and they simply don't save. So basically I need to say edit the files in the rom .zip prior to flashing in say TWRP and I can get a nice overclock no problem. It's not a matter of the stupid A** MTK crap it's a matter of modifying the android system (Cortex A9) portion with the updated files to allow for overclocking. As it's all so possible and they say the Cortex A9 can handle upwards of 1.6Ghz without any overvolt necessary.
Once I get this rolling I can help a few of you who are truly interested out. Unless you want to continue to think its impossible to do so then I say continue thinking that as it won't get you anywhere in life.
Click to expand...
Click to collapse
hello
it is possible for our canvas 2 to overclock on jellybean all we have to do is port thunderzap kernel for jelly bean.
thats how the HTC explorer got jelly bean
but we dont have much devs
I need to edit the files within /sys/devices/ to increase the max governor clock and max info clock and then look up the cortex a9 power profiles from say a known to be stable device. Like any cortex a9 tablet to know what voltages are ideal.
They say the cortex a9 can handle 1.6ghz with little to no voltage increase.
I'd also like to overclock the gpu PowerVR SGX 531.
If I can I'm going to push for 2.0Ghz if possible.
****Can someone help me adb pull /sys/devices/? Like what command to completely copy all files from /sys/devices from adb and then edit the files and then adb push? Or create a CWM or TWRP .zip with the updated kernel files for overclock?
Thanks
1chris89 said:
I need to edit the files within /sys/devices/ to increase the max governor clock and max info clock and then look up the cortex a9 power profiles from say a known to be stable device. Like any cortex a9 tablet to know what voltages are ideal.
They say the cortex a9 can handle 1.6ghz with little to no voltage increase.
I'd also like to overclock the gpu PowerVR SGX 531.
If I can I'm going to push for 2.0Ghz if possible.
****Can someone help me adb pull /sys/devices/? Like what command to completely copy all files from /sys/devices from adb and then edit the files and then adb push? Or create a CWM or TWRP .zip with the updated kernel files for overclock?
Thanks
Click to expand...
Click to collapse
That really sounds very noobish
1. You cannot simply pull the interfaces since they are symlinked infinitely
2. And do you think Mediatek will leave Clocksource interface controllable to do this? You cannot simply do "2Ghz" in the pulled interface and boom push it back to make your phone fly? eh? The new values will get RESET to original values since they are blocked/limited to the specific values. And thats why we have a thing called "Kernel Sources"
I found the mtk6577 source data... which shows the 1.2Ghz frequency available but it's not in the right table.
https://github.com/wiko-sources/cin.../platform/mt6577/kernel/core/cpufreq-mt6577.c
Maybe I could write a script like
#change cpu to 1.2Ghz by zhuzhuojie 2011-07-23 *EXAMPLE*
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor hybrid
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed 1209000
**If I can get the Motorola Xoom ElementalX kernel source data and compare and copy I think I can attempt to achieve 1.7Ghz**
#define DVFS_F1 (1001000) // KHz, 1/1 <---------- I say change this value to 1209000 or test beyond 1.2ghz until instability occurs.
#define DVFS_F2 ( 834166) // KHz, 5/6
#define DVFS_F3 ( 750750) // KHz, 3/4
#define DVFS_F4 ( 667333) // KHz, 2/3
#define DVFS_F5 ( 500500) // KHz, 1/2
#define DVFS_F6 ( 250250) // KHz, 1/4
#define DVFS_F7 ( 166833) // KHz, 1/6
#define DVFS_F1_TM (1209000) // KHz, 1/1
#define DVFS_F2_TM (1007500) // KHz, 5/6
#define DVFS_F3_TM ( 906750) // KHz, 3/4
#define DVFS_F4_TM ( 806000) // KHz, 2/3
#define DVFS_F5_TM ( 604500) // KHz, 1/2
#define DVFS_F6_TM ( 302250) // KHz, 1/4
#define DVFS_F7_TM ( 201500) // KHz, 1/6
--------------------------------------------------------------------------
* Operate Point Definition
****************************/
#define OP(cpufreq) \
{ \
.cpufreq_mhz = cpufreq, \
}
/***************************
* MT6575 E1 DVFS Table
****************************/
static struct mtk_cpu_freq_info mt6575_freqs_e1[] = {
OP(DVFS_F2_MT6575_E1),
OP(DVFS_F1_MT6575_E1),
};
/***************************
* MT6575 E2 DVFS Table
****************************/
static struct mtk_cpu_freq_info mt6575_freqs_e2[] = {
OP(DVFS_F4_MT6575_E2),
OP(DVFS_F3_MT6575_E2),
OP(DVFS_F2_MT6575_E2),
OP(DVFS_F1_MT6575_E2),
};
/***************************
* MT6577 E1 DVFS Table
****************************/
static struct mtk_cpu_freq_info mt6577_freqs_e1[] = {
OP(DVFS_F6_MT6577_E1),
OP(DVFS_F5_MT6577_E1),
OP(DVFS_F4_MT6577_E1),
OP(DVFS_F3_MT6577_E1),
OP(DVFS_F2_MT6577_E1),
OP(DVFS_F1_MT6577_E1),
};
/***************************
* MT6577 E1 TM DVFS Table
****************************/
static struct mtk_cpu_freq_info mt6577_freqs_e1_tm[] = {
OP(DVFS_F6_MT6577_E1_TM),
OP(DVFS_F5_MT6577_E1_TM),
OP(DVFS_F4_MT6577_E1_TM),
OP(DVFS_F3_MT6577_E1_TM),
OP(DVFS_F2_MT6577_E1_TM),
OP(DVFS_F1_MT6577_E1_TM),
};
static unsigned int mtk_cpu_freqs_num;
static struct mtk_cpu_freq_info *mtk_cpu_freqs;
static struct cpufreq_frequency_table *mtk_cpu_freqs_table;
extern struct kobject *power_kobj;
extern bool clkmgr_high_speed_check(void);
extern int cpufreq_state_set(int enable);
extern CHIP_VER get_chip_ver(void);
So have you tried? I'm really interested in getting this thing overclocked
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
@FooFighter312
What Device are you wanting to overclock specifically? Because your ASUS Transformer Pad TF700T uses a Nvidia Tegra 3 Quad Core with 5 cores in total all 4 running at 1.6Ghz by stock and the 5th being a power savings core. I've seen 2Ghz out of those but what I have seen is the Tegra 3 benefits primarily by a GPU core Clock increase to I believe 550Mhz was ideal for stability and at least a 20fps increase in game from my testing. Use TrixsterMod from Play Store with a modded kernel and root to push to 550Mhz.
***** IN REGARDS TO THE MTK6577 (ARM Cortex A9) *****
I used OPENSSH via the Play Store to use my PC to remote into the /sys/devices/ etc and change the parameters which doesn't sound hard. However when I changed parameters in files and tried saving it would either give me a permission error, or it would change the value back after I saved it.
Which makes me believe all the files/ parameters within /sys/devices/ etc are "Shadowed" by an unknown source of the system.
If I could determine where it's being shadowed from, I could then change it from the source. From there the "Shadowed" "Source" data would then automatically manipulate the files within /sys/devices/ and achieve the overclocked speeds. According to my research the MTK6577 and the ARM Cortex A9 in particular are using a voltage well beyond it's theoretical optimum. Meaning it's using more voltage than required for firstly stability, but also the ease of overclocking to huge speeds without ever needing to touch the voltage! According to several sources and ARM directly, they put enough volts into the 1Ghz stock speed to usually be able to achieve up to 1.6Ghz without a volt increase. However anything beyond 1.6Ghz requires a heavy volt increase which would ultimately result in epic amounts of heat.
If anyone can give more info on this that would be excellent!
Thanks
I was referring to the MTK6577 for my UMI X1. As far as I've seen there are no custom kernels for my device and the stock one just isn't enough for me. I'd like to push it a little further if possible, and I also would like more governors and io schedulers available. Another problem is that when I change any of the settings, they automatically revert to stock after a reboot.
I'm quite a noob when it comes to programming, especially on android, but I'm learning slowly. Right now I'm just an advanced user, nothing more.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
no update tutorial?
costum kernel for axioo picopad 5Gew
please custom kernel for axioo Picopad 5 GEW. mtk6577 dual-core 1GHz 512mb ram so that support for overclocking. 1.4 Ghz and swaap

rk3188[x7010] - Performance Tweaks, Test Journals, Learning diary, and custom ROM nV 1.03 for x7010

rk3188[x7010] - Performance Tweaks, Test Journals, Learning diary, and custom ROM nV 1.03 for x7010
First of all, I wanted to say thanks to LEOLAS of FREAKTAB for all the knowledge I've learned and also for OMA for making his roms PUBLICLY ACCESSIBLE AND FREE!!
PLEASE DO NOT COPY/PAST MY/THIS ARTICLE/POST Without Giving the right credit/Link to this post and XDA Forum too!!!!
I'm A WRITER AND I Dont like PLAGIARISM !!!
although It is fine for me if you will rewrite it in your own words
Oh I will introduce my self first, I am From the Country of [>--] Philippines, though very few developer came from our country, this is because of the LACK of INTEREST / PASSION of most of my countrymen.
I am th3f33, Pronounced as DAFFY or read as The Fee, ayt? xD The real name is Demi francisco, I am a Professional DESKTOP and Laptop Tech, and was used to be my previous work / job. Now I am currently focused on Web Developing and Programming (HTML,CSS,PHP,MySQL,JAVASCRIPT,ETC) that's why I am pretty familiar in the way the ANDROID Language goes (C+,Perl,PHyton,java Ayt?). I AM THE MAD PROGRAMMER!! lol XD (Just like hohouin kyouma).
For the sample/preview of my first cooked rom performance, Here is a YOUTUBE Video for it, stress test in HD Games.... http://www.youtube.com/watch?v=mm1ewtDljuk&feature=youtu.be
Vid is 14 minutes long, it would be better to check this first at least the first 5 minutes, and if you are interested, then you can continue to read.
So the device is:
SKYWORTH SKYPAD X7010
(quickly phased out on Skyworth MAIN Upon the release of x7011)
Full SPECS: (Stock)
Rockchip 3188 Quad Core Processore (28nm, 512kb l2 cache, 1.6ghz)
2GB Hynix DDR3 SDRAM 1600(h5tq4g8) Clocked @ 300mhz idle, 400mhz 1.2v
Hynix 8GB Internal Nand FLASH h27ucg8t2atr
Mali 400MP4 GPU @ 600mhz
Wifi and BT By mediatek (MT5931 and MT6622BT)
UP TO 64GB micro sd support
USB OTG
NTFS SUPPORT
HDMI SOCKET
7", 1280 x800 resolution
Audio is Realtek RT3261
NO GPS, No other sensor except accelerometer
Stock OS JB 4.1.1 (Ported/unperfected rom, missing libs, cannot run NBA2k13 on stock rom 4.1 due to the missing lib)
Facebook Group for my Custom Rom with Links to Download - please join my group, im CREATING an Army XD
https://www.facebook.com/groups/187854081403188/
NV v1.03 Custom rom By: Th3f33 (yey its me!~)
Features:
Rooted
Tweaked for MAXIMUM Performance for the price of a little battery timespan.
ANDROID SDK 2.0 4.2.2 (4.3) Based
Incomplete UI (Kitkat Based/Transparency), Not calibrated very well...
Internal storage(system) increased from 1GB to 2GB while internal SD decreased to 4.4gb
Anti-Aliasing x4 Unlocked on Developer Options
Comes with the CWM Recovery (Thanks again to LEOLAS!!! YOU ROCK!! HAPPY NEW YEAR)
Faster Reading And Writing Speed
Nand Flash and RAM Tweaks
GPU Tweaks!
99.7% Fully Functional and Error Free (As far as I tested, until Nov 2013, Im not sure right now, but may not have any problems updating google apps at all)
Bloatware Removed / Reduced
Added Apps:
Root Explorer
Jota+
Android Kitkat 4.4's Office
Android Kitkat 4.4's Google Launcher
Chrome
Rebooter App
PPSSPP (PSP Emulator)
Viper4Android Sound Effects
DOWNLOAD LINK IS SOMEWHERE IN THE MIDDLE of the whole article...
if there are some that i had forgot to mention, please do remind me XD
Instructions.
1.Install Adb Drivers after downloading the zip,
2.enable usb debugging or enter the bootloader mode by turning off the device, then holding both the volume button and power.
3.run the nV flasher, install drivers, if not yet in bootloader mode, reboot now by pressing the reboot on the flasher.
4.clear nandb then flash!
I AM NOT HELD RESPONSIBILITY IF IN ANY CASE YOUR DEVICE GETS BRICKED!
EXCLUSIVELY FOR Skyworth's Skypad x7010 only, but may also work on chuwi v88 [not tested]
I do provide unbricking service for a fee, but if you will read thoroughly this whole post, you will see the keywords to search for to unbrick rockchip rk30 devices!
DETAILS
I do believe that these tweaks / Performance increase / Speedup can be applied to all RK3188 devices, with the same logic / techniques can also be applied to rk3066 to maximize the performance. BUT BEWARE ON THE RAM(MEMORY) CHIP!!!!
Now here are the information on What i Modded and how to Improve the Performance
NOTE: (If the performance of my tablet on the video on youtube is the same as the performance of stock rockchip rk3188 tablets/devices, please do say it to me so that I will be able to change some Description on all of my posts across the INTERNET!! Thank you!)
so.... here is the learning diary and test journal
CHAPTER 1. Full brick at 1st week
The x7010 did not had any kind of update OTA from skyworth, and was replaced quickly by x7011. Since skyworth is a chinese company, i am not really expecting anything from them. but the sad part for me was when i bought the tablet, (About $150 converted currency) and then looked over the internet for supports such as CWM Recovery, CROM, Cyanogenmod or anything else, I FOUND NONE! Great! Not even a Copy of STOCK ROM! Which give me the idea of studying/learning the developing since i had already interested in doing so, and will also make me one of the pioneer custom developer/cooker for our device.... YEY!!... but it was not easy, IT WAS A HARSH PATH....
After my 1st week of trying, I already got a FULL BRICK ON MY DEVICE, But lucky me, im a great actor, so it ended up replaced from the store since it was still covered in the 1week replace 1 year service warranty. (I had softbricked the device by trying to flash Finless rom 1st try, then glassrom 2nd try, then i fully bricked it by flashing with no bootloader & parameter, erase nand db so that the store wont find out that it had been rooted and flashed!)
Chapter 2: Unbricking Success!
So on my 2nd chance, First thing i did was to do a ROMDUMP for backup (NO CWM YET), then I tried to create another CWM Again BUT I FAILED, Where i left it as is with no recovery but working system.... then i posted my 1st post here and in freaktab WHERE I stated that I want to learn and dont want to be spoonfed... Then after a few days, leolas tried to make the CWM!!! but I cant seem to flash it via flash_image, so I used a 1.37 rk tool, to flash the recovery, (Now i know that i messed up the partition offset of the recovery before so it doesnt really boot to recovery!). but by testing out what i understand from the forums, researched alot regarding parameter, mtd partition, the way android system boots and operates, i finally flashed the CWM Successfully on my device! so i backed up trice the device, and since i was so excited, i tried to flash a new rom again, but the excitement and an old mouse that double/triple clicks BRICKED my device by flashing it with NO PARAMETER AND BOOTLOADER, and all other are checked and the flash are already being erased.
No more bootloader mode, no more adb, not detected in PC In any way. then i found out the pin 8& 9 shorting for the nandflash unbrick method, tried it, stripped down my tablet, but i was so sleepy so it resulted in a failure. I dreamed that i will be able to revive the device by retrying it so when i woke up, the first thing i did was to do the PIN SHORTING then i plugged the usb cord, then poof,! Success! MASK ROM MODE FOUND!! then flash my romdump (Backup from cwm with tar and tar.a cannot be flashed ). Although i have one problem, the dump have the system in .tar and i need a .img, so once again, GOOGLE! kept on searching till i stumbled on a forum where an instruction of how to make a System.img flashable from update.zip. Using a Linux mint VM then plus learning basic syntax of linux, got it working ! .
Chapter 3 - BRAVERY!
This scenario made me think that NOTHING CAN STOP ME NOW! since it was the most difficult part for me, especially the unbricking part. so ill make it a little bit short, i flashed many roms, and recorded the differences for every rom,(ALL ROM ARE FOR RK3188, m9, u8gt,mk908, t428, glassrom, m9, etc), some rom displays, some don't, some boots, some doesn't. I also learned to logcat, read logcats, read and debug using dmesg. the rom that had been most compatible for my device is the chuwi rom v88 by oma (Yeah it rocks!) with working wifi, bluetooth, and everything else except for 3 problems, Inverted Camera, Accelerometer not working and NO SOUND! NO AUDIO! WAAAAA but was able to use it still, and checked the performance. run some benchmarks, played some games, although no sound, it was fine, with a few random lagging.... still, i continued to study it and modifying.
Next part was the System UI - framework.res and baksmaling and modfying apks, mostly for the User interface, and those were pretty easy since you can use the TRIAL AND ERROR Technique!. I have already the idea for the configs in build.prop, and just did some trial and error. By doing all of this, continuously, i am learning different syntax & commands too using adb and terminal emulator. so in the end, i maximized the performance of the rom, without touching the kernel. But i still notices the lag, one scenario is this, Fresh boot, Playing NBA2k14, then by some reason, after the camera zoom, the game slows down or get a little lag, about 22 - 28 fps, in order to get back to the max fps gaming, sometime i touch the notification area, sometime pause - resume. and when i am on max fps on any game, then accidentally touched the home / recent button, when i return to the app, it gets so lag! and when playing simultaneous game, it gets really lag.
Start the tweaking
I know this symptom, Applying my knowledge & experience in desktops. I had declared to myself that THIS IS THE EFFECT OF A BOTTLENECK! (Unbalanced specs & performance) or Memory bus width too low therefore bandwidth limits the overall performance so i checked the OC of the device, then found out that it was not overclockable thru software.
Google is my friend, and found out that i need to compile my own kernel that enables the Clock adjustment of the device to exceed the 1.6ghz. I was too naive that I Underestimated RK3188's Power. my initial goal was to OC the CPU itself, but after googling hours and hours, asking my mentor on how to compile a kernel, looking for sources which was the same for our device, eventually i found none xD, then, I stumbled upon.... OVERCLOCKOMATIC / Patchomatic!! a linux app that enables patching kernel's clock settings. And i found out that it can patch ram / gpu / cpu!
Since i was An Experienced Overlclocker (Overclocking on desktop, e5400 (2.7ghz Raised to 3.15ghz), On AIR / STOCK FAN + Exhaust & intake circulation). First i did was a hand made heat spreader (To make this, you need an aluminum foil, fold it into three, with the width of about 1-1.5 inch, then cover most of it with any tape except for the part that will be connected to the target(my target is the cpu), and the other end for the receiver/outer/safe place to transfer heat.) first, my target is my procie and spread it through the sd card slot, and another one from the procie to the aluminum case on the wifi & bt (it was covered!) i moved the 1st end from the sdcard slot to the back cover later on when i realized that i might damage the sd card or the socket itself .
Then I tweaked it and tweaked it for days, checked stability, compared results.
our kernel is 3.0.36 compiled on ubuntu! Yey! at first i was running the device on 1.8ghz, then later on i reverted it back to 1.6ghz, due to heat issues that may damage the device with prolonged use and to save battery spantime too.
But not everything is about the clockspeed, especially when i checked the GPU CLOCK IS ALREADY MAXED, So what would be the cure or solution for the bottleneck....
of course, the logics of tweaking a processor or ram or gpu are the same for the desktop. SO HERE ARE THE MOST IMPORTANT THINGS THAT I LEARNED AND WILL SHARE FOR EVERYONE EVEN IF THEY ALREADY KNEW IT OR HAD IT ON THEIR DEVICE ALREADY OR DOESNT hAVE A CLUE!
Chapter 5: OVERCLOCKING? the correct term to it for me was clock correcting / clock tweaking.
This is the EXACT modification of the kernel clock and stepping on both cpu & gpu and ram on my kernel which IS INCLUDED IN MY CROM Where everyone in our country(philippines) with x7010 tried and was satisfied of the great improvement of performance. and last week, some russian had already visited our facebook group and was testing my rom already . they also shared some roms of their own, although i think they are ported too.
nV 1.03 [first Edition] by th3f33 Download Link:
http://bagongpleion.net/th3f33/nv103.rar
RAM
modifying the RAM (2g DDR3 sdram 1600mhz) to be run @800mhz like a ddr2 instead of the stock @400mhz like ddr1 thus increasing the bandwidth have a huge impact on MALI-400mp4 gpu since the Quad Core Rockchip Processor were fast enough to make up for the lost clock cycle but lacks bandwidth because of the 32 bit bus width. BEWARE! Our ram is 2gb ddr3-1600mhz, which have a normal voltage of 1.5v. Low profile sdram modules have only 1.2 / 1.3v normal running voltage. YOU WILL NEED TO MANUALLY CHECK THE SDRAM MODULES ON THE DEVICE ITSELF TO IDENTIFY What type of ram it is, is it a ddr3 sdram? ddr2? a low profile? and clock timings? Ive used google to fully identify my hynix ram specs and even tried running the RAM @ 800mhz 1.5v and no restarting / corruption issues! it just that it drains the battery really fast. for our device, the exact and sufficient Voltage for the ram to perform well @ 800mhz is around 1.3v - 1.35v although im using 1.3v only. THIS IS NOT APPLICABLE TO ALL RAM and WILL REQUIRE MOST OF THE ATTENTION, EFFORT AND TIME TO APPLY CORRECTLY AND SAFELY!
I cannot guarantee your life or you freedom !
Some Info on ram: Lower clock speed of ram have faster clock cycle (on default clocks of actual ram sticks) Higher Clock Speed of ram have slower clock cycle BUT Bigger Bandwidth.
Low Profile RAMS Uses less energy(VOLTAGE), expect a slight decrease in overall performance....
Some Rams have lower clock cycle and latency in their stock settings compared to other. This are the high profile / OC'ed version of rams..
Anonymous asked: "Why did you use ddr800 against ddr400 config for our ram?"
RK3188 is a quad core processor with 512kb (L2 cache per core i believe) running @ 1.6ghz which are ULTRA FAST and can be compared to an AMD athlon Mobile processor ! it was so fast that before that RAM Cycles to refresh, all the data have been stored in the ram had been processed already, so there was really no need for the quick cycle, PLUS The GPU Is an Onboard/SOC/bundled along with the CPU (like intel's I series and AMD A Series). Now They will need a Bigger bandwidth so the power of the cpu can be utilized more since more data (RAM IS 2gb, can store a lot of data! Really...) can be passed as the bandwidth is higher. therfore GPU have a wider data path for transferring the rendered graphics data to the cpu to process then pass back to the GPU or ram, dpending on situation, without clogging up the I/O Path.
Short Answer: Faster GPU and Read/Write speed at no cost (aside from a little energy drain for the increased voltage of ram, since the cpu can handle that load!)
Chapter 6: Cpu and GPU
CPU
Kernel patched, using rkpatchomatic / overclockomatic! (linux)
I also reduced the Clock stepping and adjust the voltage of the cpu from:
312mhz @ .9v
504mhz @ .925v
816mhz @ 1v
1008mhz @ 1.075v
1200mhz @ 1.150v
1416mhz @ 1.250v
1608mhz @ 1.350v (this may not be right, if i am not mistaken it was only 1.3v @ 1.6ghz on stock)
(6steppings)
to
504mhz @ 1v
1008mhz @ 1.115v
1416mhz @ 1.250v
1608mhz @ 1.350v
(4steppings)
AND the GPU speed increase by loading the driver module with:
insmod /system/lib/modules/mali.ko (removed mali_dvfs & mali_init_clock=133)
and also changing the GPU voltage and stepping FROM:
133mhz @ .975v
200mhz @ 1v
266mhz @ 1.025v
300mhz @ 1.050v
400mhz @ 1.100v
600mhz @ 1.250v
(6 Steppings)
To
200mhz @ 1.05v
400mhz @ 1.15v
533mhz @ 1.2v
600mhz @ 1.35v /1.3v
(4 steppings)
OR
266mhz @ 1.05v
400mhz @ 1.175v
600mhz @ 1.35v
(3 steppings)
The Steppings Reductions Resulted in a VERY VERY Fast Application Switching (Not using a multiwin rom, but able to run about 6-7 HD games with seemingly no lags on switching). BUT Additional battery power may be consumed because of higher idle values for each settings.
My theory, explanation, and strategy was.....
GPU & CPU Steppings logic are the same, while for the GPU the clock increases, so as their texture and pixel fillrate. But gpu power may not be nough @ 1.25v during heavy loads, that is why i've used the maximum allowed voltage for the gpu, and adjust most of the voltages so that the system will never be short on current especially when switching state.
Wanderer asked: "why did you reduced the steppings and what exactly is that?"
Stepping is the term I used for the clock settings / stop point, It came from intel, they use Speedstep and steppings. as you can see, Most of the time, when not playing hd games or not running so many many apps, The cpu (based on my new config) will either run fine at 500mhz, - 1ghz only. (large bandwidth maximizes the power of the quad core of rockchip). so it wont need to adjust itself to 1.4ghz unless it really needs it, and it will not revert back to 500mhz unless all apps and memory are cleared and closed. (Even if you press the recent apps, it will stay @ 1ghz and will not drop to 500mhz). When running a solo HD game, except for 2013 Q4 HD games like CoD & GTA SA, cpu will be fine @ 1ghz, when running other apps, like browser, music player, etc etc, it will be kept in memory, and the cpu will have to speed up itself so it will be stable @ 1.4ghz, when running multiple hd games, it will run @ max 1.6ghz.
The stepping settings helped the cpu to be STABLE @ certain clock during prolonged usage.
Plus, rk3188 is not a very good at clock switching / stepping adjustment. Some users of rk3188 uses a cpu tweaker and set their clock permanently to 1.6ghz right? but it consumes battery faster. I tried different numbers of steppings and clock config and this was the best result for performance. Well in reality, if you are going to overclock a desktop processor, you will disable the speedstep or clock switching feature because it consume power and energy. imagine that the processor needs to consistently monitor the cpu load and adjust it according to its needs. even a human will have a delay of a few seconds during the adjustment and calibration of the strength, the same logic applies to the processors too, plus if you will add the stress of the switching of the GPU, bugs and lags are generated, sometimes, it takes quite a while for the gpu to adjust its clock, from 133, to 200, then lags a little, adjust cpu, then gpu from 200 - 400, then suddenly you pressed the home button while playing, gpu reverts back to 133mhz which is far from the max, ew, where in my config, you start at 233, making everything seems to be so smooooooth, even if you enable AAx4 in the developer options you wouldnt notice the impact of it in performance, then you can disable hw overlay and enable gpu rendering too to maximize performance! if you want to save battery, then choose the 4 steppings on gpu, if you are a hardcore gamer on tablet, then use the 3 steppings on gpu, if you want more, replace the 400mhz config in the 3steppings with the 533 from the 4steppings.
STORAGE
I have Also increased the Speed if reading / writing in the nand flash by mounting mtd partitions with:
ro noatime nodiratime noauto_da_alloc data=writeback barrier=0 nobh
TIP {
instead of using an app to mount the android folder in external sd, you can use a terminal emulator, then this command to mount the folder from exterlan sd - internal, so you can play more games! (Note: please do create the /Android/data and /Android/obb on both internal and external SD
$ su mount -o bind /mnt/external_sd/Android /mnt/sdcard/Android
or
# mount -o bind /mnt/external_sd/Android /mnt/sdcard/Android
to remove the mount/bind
$su umount /mnt/sdcard/Android
or
# umount /mnt/sdcard/Android
The mount / bind is not permanent though, and you will need to enter the command every restart of the device.
}
end of message...
Elp Psy Congroo
XDA:DevDB Information
nV v1.03 [1st revision], a ROM for the Android General
Contributors
th3f33, th3f33
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: ANY x7010 firmware / softbricked
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: v1.03
Stable Release Date: 2013-11-14
Current Beta Version: v1.00
Beta Release Date: 2013-09-09
Created 2014-01-07
Last Updated 2014-01-07
Reserved
ROM Screenshots, And Benchmarks:
Passmark Results:
{
"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"
}
Antutu:
Rom:
Reserved
about:
if there are any question, or criticism, or bugs, or anything else, feel free to post, i will entertain anyone :good:
th3f33 said:
if there are any question, or criticism, or bugs, or anything else, feel free to post, i will entertain anyone :good:
Click to expand...
Click to collapse
can you provide a version that have a default Android icon on the NavBar? [Back][Home][Switch]
Hey TH3F33! Its me Patrick! Hehehehe, nice you're already starting to spread your name and our tab, I hope this becomes successful and well known, will always have your support!
Edit: They really should make a forum for our tab.
Sent from my XT890 using Tapatalk
samplermonhar said:
can you provide a version that have a default Android icon on the NavBar? [Back][Home][Switch]
Click to expand...
Click to collapse
Yes, maybe I will do that maybe tomorrow, I just have to finish another task from my work.
The nV 1.04 will be Philippine themed
re
Jabbzz said:
Hey TH3F33! Its me Patrick! Hehehehe, nice you're already starting to spread your name and our tab, I hope this becomes successful and well known, will always have your support!
Edit: They really should make a forum for our tab.
Sent from my XT890 using Tapatalk
Click to expand...
Click to collapse
Tnx
I was already creating our own forum, just be patient, its a virtue. :good:
Why are you using xt890 ? Lol
th3f33 said:
Tnx
I was already creating our own forum, just be patient, its a virtue. :good:
Why are you using xt890 ? Lol
Click to expand...
Click to collapse
No I mean a category here in XDA..hehehe..
XT890 is my smartphone, the one I use for texting, blah2. Motorola RAZR i
Sent from my XT890 using Tapatalk
Jabbzz said:
No I mean a category here in XDA..hehehe..
XT890 is my smartphone, the one I use for texting, blah2. Motorola RAZR i
Sent from my XT890 using Tapatalk
Click to expand...
Click to collapse
we alreay got a place, check facebook group -.-
Looks like only a few skyworth users visits xda....
Sent from my x7010 using Tapatalk
Wait a moment, is there a 4.3 rockchip rom? The blobs it is using are from 4.2?
Edit: sorry, I just saw this: ANDROID SDK 2.0 4.2.2 (4.3) Based
jsevi83 said:
Wait a moment, is there a 4.3 rockchip rom? The blobs it is using are from 4.2?
Edit: sorry, I just saw this: ANDROID SDK 2.0 4.2.2 (4.3) Based
Click to expand...
Click to collapse
yep it is a 4.2.2 based on 4.3
two thumbs way up for you kabayan! I'm no coder, but I love to read and tweak usually consolidating tweaks/scripts for my myPhone Vortex.
Good thing its a fairly popular phone in India, else I would have been stuck with the stock rom.
I'm curious if your rom can be applied to the recently released tablet from Starmobile : Engage 8 quad+
It sports the same processor as your Skyworth but with 1G of RAM only, 8G internal. Been looking around and I've read through
the list of roms you've tried (PIPO, M9, GLASS) and its a good thing I found your thread. I would have risked to root and flash
my tablet with any of those roms.
I'm currently reading on rooting my tablet using this method below, however I'm now hesitant to proceed. Would you have another method that
would work? or at least give me a little more confidence of root success. Thereafter, its CWM, then flashing time! woot
http://www.slatedroid.com/topic/88850-rooting-rk3188-tablets/
btw, I've found the manufacturer of this tablet, guess Engage 8 is a rebrand of this unit.
http://www.google.com.ph/url?q=http...Q4BrZw&usg=AFQjCNEsT9Dux2uMCLEZykSB5umoY8nyOQ

[UNIFIED] Render Kernel [OOS-N-EAS-R2][LOS-N-EAS-R8]

{
"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"
}
for OOS-N, and LOS-N​
Code:
/* *** Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* BOOM goes the Dynamite
*/
I am releasing this kernel because I like to share my work and have had requests to do so and, lastly, because we needed yet another kernel released for our beloved OP3! I started out at XDA because I wanted to learn and share what I have learned. My goal with this kernel is to be a very fast and stable build that offers some things that the other kernels do not. I also want to initiate Development Discussions among the community. This will be a noob friendly thread as long as users follow two rules. First is to do some research before asking. Most likely your question has already been asked. If not in this thread then in another. Remember to always search first! Second is BE RESPECTFUL. You do these two things and even the most hardened Dev will assist you.
Wanna be notified of an Update? Here is my PushBullet Channel!!
https://www.pushbullet.com/channel?tag=renderkernel
Current Features
General List:
* EAS Only
* Built with LINARO 6.x
* Updated with CAF LA.UM.5.5
* IO Scheds - FIOPS, CFQ, BFQ, ROW, DEADLINE, NOOP, and ZEN Schedulers
* Flar Sound Control
* Wake Gestures - DT2W, S2W, and S2S
* Complete Color Calibration Thanks to @savoca
* F2FS Support
* Adrenoboost
* USB Fast Charging
I recommend Kernel Aduitor for making kernel changes
Kernel Downloads:
LOS-(EAS/HMP) Downloads
OOS-(EAS/HMP) Downloads
Instructions:
* Boot into Recovery
* (Recommended) Make a complete backup of everything!
* At least backup BOOT via TWRP
* Flash Zip
* Reboot
THANKS!!!!
First I want to say thank you to everyone who has answered my questions and responded to my pm's when I know they are busy with their own lives. Pretty much everyone I have come into contact with here on XDA has been truly helpful and respectful. Here is a list of people that had helped me in one way or the other:
Neobuddy89, ak, myfluxi, Dorimanx, Savoca, Faux123, DespairFactor and Many More!
Thank you guys! Without your contributions to the community we would not have the level of performance, stability and interaction that we have today
Special Thanks!
Donators: @nfin1te, @MrDarkKV, @V1TRU, @Really now @erad1
Source Links:
https://github.com/RenderBroken/OP3-kernel
https://github.com/RenderBroken/OP3-LOS-kernel
https://github.com/RenderBroken/RenderKernel-AnyKernel2
XDA:DevDB Information
[UNIFIED] Render Kernel [OOS-N-EAS-R2][LOS-N-EAS-R8], ROM for the OnePlus 3
Contributors
RenderBroken, Mostafa Wael, joshuous
ROM OS Version: 7.x Nougat
Version Information
Status: Testing
Created 2016-11-23
Last Updated 2017-12-15
Note:
Great write-up from @Mostafa Wael
HMP vs EAS - OxygenOS 4.1.3 stable
Right here we go!
First things first, this is a comparison between two kernels and NOT just two different scheduling systems. With the latter being undeniably the biggest difference between RenderKernel and the stock kernel, changes can extend to other default settings, should @RenderBroken choose to do so. One of which is the default choice of BFQ I/O scheduler instead of the default CFQ I/O scheduler of stock kernel. If you want to have a quick debrief of what (the current implementation of) EAS is all about, read this post here
MMX Hill Dash
HMP - most of the time the game is mainly operated by the big cluster while the little cluster is mostly at the lower end of the frequency table, hovering around the absolute minimum frequency of 307 MHz for most of the time. The big cluster however was noticeably more active, hovering around 1.25 GHz to 1.55 GHz with rare dips below 1 GHz and slightly more often spikes to 1.7 GHz and above. So to sum up HMP's management of the CPU in this particular game, it is safe to state that the game is more or less solely operated by the big cluster, running mostly on the intermediate frequency steps between 1.25 GHz and 1.55 GHz with occasional spikes to 1.7+ GHz and much scarcer dips to sub 1 GHz. As far as performance goes, there are no major complaints. The game runs incredibly smoothly and the game is loaded in a reasonably quick manner; launching the game takes between 8s and 10s from the get-go.
EAS - It's remarked that all 4 cores are active when playing this game, unlike HMP, with the little cluster spending almost all of the time at the 1.11 GHz step with very rare dips to the minimum frequency. While that may sound like a bummer, there is an upside to the surprisingly increased activity of the little cluster. Apparently the big cores have some of the loaded lifted, since the big cluster is being utilised at noticeably lower frequency steps compared to HMP, staying on the 1.11 GHz frequency step much more often, otherwise roaming between 1.25 GHz and 1.55 GHz with very scarce spikes to the max frequency. Like HMP, the game runs flawlessly with no major complaints and surprisingly the game is loaded just as quick as HMP too, if not a tad quicker sometimes! Crikey!
True Skate
HMP - Both clusters are heavily fluctuating with no predictable trend. However, it is quite noticeable that the big cluster can hit the high end of the frequency table quite often. Little cluster is relatively less active, but it is not that dormant either. With that said, it is no wonder that the game runs silky-smooth. However, there were some instances where the frame rate would suddenly drop to around 40-45 fps for mere seconds, where the cause has been determined to be some background tasks being executed like Play Store checking for whether there are apps need to be updated, and social media apps refreshing in the background. Theoretically such an issue would not exist on EAS due to cleverer tasks placement techniques to avoid overstressing the CPU.
EAS - Both clusters spend most of their time at the 1.11 GHz frequency step, with the big cluster ramping up to the max frequency for a considerable amount of time. With that said, a natural consequence would be witnessing one of the most consistently smooth and fluid gaming sessions of that particular game. And even with lots of background processes taking their toll on the silicon, performance is not hindered by any means.
Browsing via Chrome
HMP - Flinging through the webpage will immediately crank up the big cores to max frequency straight away till the content is loaded. Should there be a video to be buffered, the big cores keep operating at medium high frequencies between 1.25 GHz and max frequency with rare dips to minimum frequency. Once all contents are loaded, the big cores gradually get toned down and caged into the lower end of the frequency table. The little cores on the other hand are not wrestling with the controls surprisingly enough, rather sitting most of the time comfortably at 0.96 GHz to 1.1 GHz, with a considerable amount of time spent on the lowest two frequency steps of 307 MHz and 422 MHz. Scrolling through the webpage is reasonably smooth, though sometimes it tends to be a bit unresponsive and wonky if a lot of interactions were present or a lot of content are being loaded while scrolling. As far as battery backup goes, there is no escape that such a task would sip a lot of juice from that tank. And at 18%/hr, there is a lot to be desired when it comes to efficiency, bearing in mind that such a high active drain rate does not guarantee you a flawless silky-smooth UI.
EAS - Like HMP, flinging through the webpage will engage the big cores fully till the page contents are loaded. However, unlike HMP, the big cores do fade out quite faster when the page contents are loaded successfully. Things get much better when there is a video to be streamed, where the video is mainly handled by the little cluster while the big cluster is impressively tamed and utilised at sub 1 GHz frequencies, 0.7 GHz on average, while the little cluster lifts the burden from the furious big cores, operating at frequencies between 1.1 GHz and max frequency of 1.59 GHz. Scrolling through the pages is silky smooth with no hiccups of any sort, even when loading a lot of content while stubbornly scrolling the page, it does not stutter as much as it does on HMP. However, things are not all rosy when it comes to battery drain. Web browsing is undeniably demanding, which makes it logical to see a not-so-impressive 17%/hr drain rate. While it may sound marginally better, web browsing inevitably does take its toll on the battery for sure, and things are not that drastically better when it comes to battery conserving. However, when you couple that with the increased fluidity and consistency gained, EAS is the clear victor.
YouTube streaming
HMP - For such a medium/light workload, it is no wonder seeing the little cluster being noticeably more active than the big cluster, where it spends most of the time on the lower end of the frequency spectrum, with more than 60% spent on the lowest 2 frequency steps of 422 MHz and 307 MHz. However, there were some occasional bumps to a rather unexpectedly higher frequency of 960 MHz, taking around 11% of the total time. While the big cluster was relatively quite dormant, it was not asleep either. With around 7% of the time spent on 1.25 GHz, it is far from being asleep, which raises some eyebrows for sure. It's not that grim though. At 11.6%/hr drain rate, it's highly unlikely to find your phone depleted before lapping some 9 episodes of your favourite TV series, which in my case was the old Top Gear UK.
EAS - Surprisingly enough, there are almost no tangible improvements in battery life while streaming some videos on YouTube. With the consistently reported figure of 11.3%/hr by EXKM battery monitor, I am struggling to say anything other than the fact that battery life is very similar to that of HMPs. Moreover, the frequency distribution is not that all different either. Little cluster is expectedly sitting most of the time at the lowest two frequency steps with much shorter duration at the 480, 556 and 652 MHz steps. Same goes for the big cluster as well, with respective frequency steps considered of course. But rest assured, it is still as highly unlikely to miss out a season of your favourite TV series as with HMP.
Overall battery life
HMP - in the past couple of days, I often read a value between 14%/hr and 16%/hr in EXKM's battery monitor with my mixed not-so-light usage, which is pretty much decent though not perfect and definitely leaves something to be desired in that area. But since I get more than 5 hrs SOT at the end of the day with some little juice left in the tank at the end of the day, I think it is safe to say battery life is good enough for the overwhelming majority of users
EAS - While people may think this is pure EAS terrain, results are not dramatically different from what you get from HMP. Surprisingly enough, I often stumble across an active drain rate between 13%/hr and 15%/hr with approximately the same usage pattern, which is 3%/hr less than what you get from HMP in the best cases. This is a substantial improvement, make no mistake, but that may not live up to the expectations from an energy aware scheduling system. However, an area where EAS truly shines is screen-on idling. Not only does the CPU retreat to the minimum frequency quite quickly, but also remains utterly dormant with absolutely no random spikes, causing a dramatic decrease in the battery drain. This is purely e-book readers heaven for sure! The same cannot be said about HMP for sure.
let's get to the numbers...
App launches
[HMP]
PCMark: (7.13 + 8.32 + 6.65 + 7.00 + 7.85)/5 = 7.39 sec
Slack: (1.60 + 1.78 + 1.79 + 1.65 + 1.75)/5 = 1.71 sec
YouTube: (1.40 + 1.44 + 1.41 + 1.44 + 1.45)/5 = 1.43 sec
Telegram: (0.65 + 0.72 + 0.70 + 0.54 + 0.61)/5 = 0.64 sec
WhatsApp: (1.28 + 0.72 + 1.27 + 1.34 + 1.28)/5 = 0.91 sec
Hangouts: (1.38 + 1.34 + 1.31 + 1.34 + 1.38)/5 = 1.35 sec
Dropbox: (1.25 + 1.26 + 1.37 + 1.22 + 1.21)/5 = 1.26 sec
Chrome: (1.18 + 1.36 + 1.19 + 1.50 + 1.38)/5 = 1.32 sec
Keep: (0.94 + 1.03 + 0.97 + 0.94 + 0.97)/5 = 0.97 sec
MMX Hill Dash: (7.56 + 12.87 + 12.09 + 11.60 + 10.81)/5 = 10.99 sec
Twitter: (1.69 + 1.81 + 1.90 + 1.66 + 1.91)/5 = 1.79 sec
True Skate: (1.60 + 1.69 + 1.62 + 1.59 + 1.54)/5 = 1.61 sec
XDA Labs: (1.41 + 1.53 + 1.47 + 1.48 + 1.52)/5 = 1.48 sec
Test has been done with no active Internet connections (WiFi and mobile data turned off) to ensure that the phone is not bottlenecked by anything but the I/O and the CPU
CPU governor is Interactive with stock settings and I/O scheduler set to CFQ with 512 KB read ahead buffer size
[EAS]
PCMark: (9.13 + 9.63 + 9.50 + 9.84 + 9.50)/5 = 9.52 sec
Slack: (1.66 + 1.79 + 1.69 + 1.75 + 1.85)/5 = 1.75 sec
YouTube: (1.66 + 1.69 + 1.63 + 1.62 + 1.69)/5 = 1.66 sec
Telegram: (0.69 + 0.66 + 0.63 + 0.59 + 0.78)/5 = 0.67 sec
WhatsApp: (0.75 + 1.19 + 1.16 + 0.97 + 1.21)/5 = 1.06 sec
Hangouts: (1.34 + 1.29 + 1.36 + 1.25 + 1.31)/5 = 1.31 sec
Dropbox: (1.40 + 0.84 + 0.86 + 0.85 + 0.87)/5 = 0.96 sec
Chrome: (1.32 + 1.37 + 1.39 + 1.56 + 1.32)/5 = 1.39 sec
Keep: (0.97+ 0.91 + 0.85 + 0.93 + 0.84)/5 = 0.90 sec
MMX Hill Dash: (11.31 + ---) the game refuses to launch seamlessly, to be investigated later..
Twitter: (2.25 + 2.53 + 2.50 + 2.57 + 2.37)/5 = 2.44 sec
True Skate: (2.00 + 1.58 + 1.71 + 1.75 + 1.74)/5 = 1.76 sec
XDA Labs: (1.72 + 1.44 + 1.47 + 1.53 + 1.43)/5 = 1.52 sec
Test has been done with no active Internet connections (WiFi and mobile data turned off) to ensure that the phone is not bottlenecked by anything but the I/O and the CPU
CPU governor is Schedutil with stock settings and I/O scheduler set to BFQ with 512 KB read ahead buffer size
.
Synthetic Benchmarks
[HMP]
AnTuTu: 148,471
Geekbench 4.1.0: 1733 + 4191
Vellamo - Multicore: 3215
Vellamo - Metal: 3541
Vellamo - Chrome: 4825
[EAS]
AnTuTu: 143840
Geekbench 4.1.0: 1740 + 3290
Vellamo - Multicore: 2511
Vellamo - Metal: 3569
Vellamo - Chrome: 4350
This test was conducted with RenderKernel-OP3-OOS-N-EAS-R1-WALT and OnePlus's inbuilt kernel. OxygenOS version used was OOS 4.1.3 STABLE
Coming up next is a brief technical breakdown of OOS's behind-the-scenes stuff and how OnePlus fiddled around with them by XDA member @chinmai560621 .
Hope such an analysis benefits someone here. Sorry for the delay, but i have been double slapped by life for the past couple of weeks every day....
Reserved
An amazing write up by a talented dev @joshuous:
PELT and WALT
Time for me to flex the analogy muscles.
Just to set things straight, PELT and WALT are different load tracking metrics that try to determine the load of the system. The load will eventually be used by the frequency governor to set the frequency. Think of them (the load tracking metrics) as an employee who is dedicated to announcing how quickly customers are coming into your burger restaurant. The frequency governor is the burger chef, who isn't able to see the number of customers entering, so he has to rely on the announcer in order to know the rate at which he is making burgers. The announcer can say that there are "many" customers, and the chef has to decide how fast to make the burgers based on how he interprets "many".
One announcer can say that 10 customers is "many", while another may say that 20 is "many". An announcer may also attempt to predict the number of customers that will enter based on how many he sees at the current point in time. In this way, burger output is more 'bursty'. For example, there are 10 customers ("many"), then no customers ("none"), then 15 customers ("very many"). The chef works hard, then thinks he can take a break for a moment, then suddenly has to work like crazy to dish out burgers for 15 customers. An oversimplified analogy to WALT.
On the other hand, another announcer may observe a trend of customers and apply some prediction to guess how many customers might come through the door. Using the same customer sequence as before, he may instead tell the chef "many", "some", then "many". So the chef may make burgers even when there are no customers, in anticipation of future customers, but he won't be worked so darn hard all of a sudden. This is less bursty and more consistent. An oversimplified analogy to PELT.
In the same way there are different chefs (e.g. Sched and Schedutil). They have different interpretations of what "many" means to them. That's why their burger outputs may be different even when having the same announcer.
So which is better? It all boils down to your workload, and even so it is difficult to make a conclusion. All I can say is that you must test each mechanism for over a week and check your active drain rate (Ex Kernel Manager is good for this). Active drain rate is a much better measure than SOT. And make sure to keep jumping back and forth between the two to account for anomalies.
Edit: On another note, to complete the analogy... Interactive and HMP is more similar to the chef being the announcer as well. Except for he is able to see less than a dedicated announcer can. I.e the chef (interactive governor) can't look at the queue outside his restaurant but only the ones in his restaurant (so he is partly blind). A dedicated announcer can look at customers inside and outside the restaurant though.
Do note that this has little to do with EAS per se. EAS is a different beast that focuses on optimizing which customers is assigned to which chefs. I'll probably write the analogy for this another time if there is a demand for it
You can't imagine how happy I am to see you here!
Sent from my ONEPLUS A3003 using Tapatalk
Download links says, N6?
ELoTRIX said:
Download links says, N6?
Click to expand...
Click to collapse
See OP#2. Sorry, still updating OP
Work with 3.5.5. cb?
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
isoladisegnata said:
Work with 3.5.5. cb?
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry, it will not work for CB yet. I made that clearer in OP.
I would like to offer support for it though.
TaRsY said:
You can't imagine how happy I am to see you here!
Click to expand...
Click to collapse
Me too!! I love render since lg g2 times.. Thanks Render for coming here
omg another kernel. Im so exited !!!!!!!!
thank you very much!!!
cant wait to test!!!
looks very promissing!!
MBurns2 said:
Me too!! I love render since lg g2 times.. Thanks Render for coming here
Click to expand...
Click to collapse
Thanks! Glad to be here!
nadejo said:
omg another kernel. Im so exited !!!!!!!!
thank you very much!!!
cant wait to test!!!
looks very promissing!!
Click to expand...
Click to collapse
I appreciate the kind words!
Everyone, please remember to provide logs in case of a reboot. I dont like to release such builds but it will happen from time to time. Especially when porting new features such as EAS.
You can get a log from
/sys/fs/pstore/console-ramoops
New build. Fixes default governor not being set properly.
Default gov is supposed to be "SCHED"
R1-T40-EAS
Great work bud
__
v7
RenderBroken said:
New build. Fixes default governor not being set properly.
Default gov is supposed to be "SCHED"
R1-T40-EAS
Click to expand...
Click to collapse
Good to see you here Buddy.. No doubts now we have one more best kernel for our beast OP3. surely gonna use permanently...
Sent from my aicp_oneplus3 using Tapatalk
Render is great just bringing another great kernel to the Oneplus 3
Look who's here.. Render.. One of the most friendly and vocal devs.. Thank you for the kernel mate.. You made opo so amazing..
Flashed looks good!
lets see for next battery cycle.
Great! EAS is really where I was hyped for! Thx for your amazing work!.
I'm going to run it 24 hours and see if there are any reboots, if there won't be ill let you know. I noted that the Cpu frequency stays quite high when there is barely any load? Is this normal?
Edit: issue with standby, couldn't get my phone on when I didn't use it for like 3-4 minutes. Had to reboot, but couldn't reproduce the problem
Issues I encountered:
1. Had an instant where my phone's screen was off for 2 minutes, i couldnt get the screen back on so i had to reboot. Yet i failed to reproduce the issue. (Logs didnt show anything)
2. CPU frequency seems to be really overkilling a task. It doesnt like to stick to 300Mhz either.
Other then that it works smooth and flawless! Even Snapchat is now using all 4 cores instead of only 2 little ones on HMP.
Hi, I know you only support OOS. Having said that, will it cause any problems if I use it over custom roms?
ROM OS Version: 2.3.x Gingerbread
Click to expand...
Click to collapse
Sorry for disturbing, but OP need some correction
Anyway, I'm impatient to test it !

Categories

Resources