Database Info

[Share][8-Sep-2011] Almost all fix for CM7 and MIUI, include some optimization v2

Just share all these with anyone.
All fix included:
New added in v2:
1. A more native fix to USB connection ( moto portal&tool is available now )
2. add imoseyon tweak script
3. improve GPS(add UK/brazil/CH+HK+TW/USA services info)
4. some adjustment on auto brightness
5. fix losing (gapps) icon issue (area related issue, redirect google services in hosts)
6. enable WIFI tethering
7. try to improve battery charging(replacing charge_only_mode)
8. try to improve touch sensitivity (build.prop)
9. clean some system apps/junks ( common/necessary gapps are reserved )
10.update moto IME from GB leak
11.improve network and voice (not sure)
12.fix sensor/GPS crash in 0906 version(replace 2nd-init with RC1.5)
Download Link: http://www.mirrorcreator.com/files/VMXNTP1B/All_in_One_Fix_for_CM7_and_MIUI_v2.0.7z_links
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1.bootmenu overclock
2./data formatting and restoring issue on CWM
3.CPU governors
4.light/gravity
5.keyboard mapping (QWERTY/Z)
6.GSM fix
7.keyboard backlight
8.camera upside down
9.dual way call recording
10.soft keyboard half size
11.random SD card mounting issue in CWM
12.charger light
13.compass
14.APN fix
15.share sd card / DATA function in bootmenu
16.300mhz fix
17.stock recovery fix
18.battery jumping
and also include tweaks and optimization：
1.enhanced sms and location info(ch)
2.moto IME
3.tweaks on framework and build.prop
4.optimized auto brightness
5.power profile
6.some scripts from wajk in /system/etc/init.d
7.full Gapps
Unsolved:
1.video decoding/encoding(720p recording)
2.enable 4-lv freq setting in bootmenu( a little edit in overclock.c)
3.share SD/data/system function in bootmenu are still buggy,sometimes is ok, sometimes not.
4.Alt-lock (I thinks we can ingore this)
5.battery charging(im not sure, but someone said the full voltage in stock 2.2 can reach 4200+ and down in 3100, in CM7 it only get 4160 and down in 3300)
Please use winrar3.50+ or latest 7zip to depack it.
Download link: http://www.mirrorcreator.com/files/IYOX37NY/fix-for-CM7_0.7z_links

Amazing share man!!! Thanks a lot!!!
The link does not work for me.
[Failed to open redirect file]

sahilarora911 said:
Amazing share man!!! Thanks a lot!!!
The link does not work for me.
[Failed to open redirect file]
Click to expand...
Click to collapse
My fault. I post the wrong link. I have updated a new one. Try again.

Endless7 said:
My fault. I post the wrong link. I have updated a new one. Try again.
Click to expand...
Click to collapse
Hey Endless, can you post what is missing/still needs fix?

r2beta0 said:
Hey Endless, can you post what is missing/still needs fix?
Click to expand...
Click to collapse
1.video decoding/encoding(720p recording)
2.enable 4-lv freq setting in bootmenu( a little edit in overclock.c)
3.share SD/data/system function in bootmenu are still buggy,sometimes is ok, sometimes not.
4.Alt-lock (I thinks we can ingore this)
5.battery charging(im not sure, but someone said the full voltage in stock 2.2 can reach 4200+ and down in 3100, in CM7 it only get 4160 and down in 3300)

Ah,for 720p recording. Jorixine send me a PM with a possible method. I try,but failed. But I still want to post here.
The fix is somewhere within media_profiles.xml and build.prop
media_profiles.xml can be edited as you please, even for making the HD videos to size lesser than normal
For it to work, in the build.prop you have to change the following:
ro.media.capture.maxres=5m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=60
ro.media.enc.hprof.vid.width=1280
ro.media.enc.hprof.vid.height=720
ro.media.capture.flash=led
ro.media.capture.useDFR=1
ro.media.capture.flashIntensity=42
ro.media.capture.torchIntensity=42
ro.media.capture.classification=classE
ro.mot.setuptype=1
ro.media.enc.aud.fileformat=3gp
ro.media.enc.aud.codec=amrnb
ro.media.enc.aud.bps=12200
ro.media.enc.aud.ch=1
ro.media.enc.aud.hz=8000
ro.media.dec.jpeg.memcap=20000000
r,o.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
He insists, recording 720p is working, the thing is that the phone reboots by itself a lot and some of those reboots are even when it never finished loading the OS, its very annoying.
Seems like the key question is to keep playing with these values. Moreover where it says ClassE, because in GB that comes as ClassH, but he changed it.
Maybe somebody with more expertise can playaround with these two files, get the correct configuration and avoid the rebooting issue.
Click to expand...
Click to collapse

Endless7 said:
Ah,for 720p recording. Jorixine send me a PM with a possible. I try,but failed. But I still want to post here.
Click to expand...
Click to collapse
I think we can make it work with the original camera application.<
Hey im the onlyone getting "unsupported compression method" on 7z¿

WeeDv2 said:
I think we can make it work with the original camera application.<
Hey im the onlyone getting "unsupported compression method" on 7z¿
Click to expand...
Click to collapse
Use winrar3.50 or latest 7zip. Because I use highest compress level.

I think I have fix the battery charging issue. Now I am on 4167 at 92%. No jumping during charing.

What about USB not working as in Stock? any update on that? i think its the MotoUSB.apk, ill try replacing it with stock USB.apk from Arg Movistar 2.2.2
(and yeah i already edited MIUI framework-res.apk)
Endless, your framework-res.apk included is the CM7 one right? cuz the one of MIUI usually is about 7 to 8 MB and your is 4/5 MB

WeeDv2 said:
What about USB not working as in Stock? any update on that? i think its the MotoUSB.apk, ill try replacing it with stock USB.apk from Arg Movistar 2.2.2
(and yeah i already edited MIUI framework-res.apk)
Endless, your framework-res.apk included is the CM7 one right? cuz the one of MIUI usually is about 7 to 8 MB and your is 4/5 MB
Click to expand...
Click to collapse
It's CM7 one.
word patch.

Very nice share Endless7 Thanks

Endless7 said:
I think I have fix the battery charging issue. Now I am on 4167 at 92%. No jumping during charing.
Click to expand...
Click to collapse
I too get to somewhere around there while charging but at 100% I get 4169mV I guess, but if I keep charging it after that it drops to 4134 mV something.
And the link is fine now, thanks!!

Endless7 said:
1.video decoding/encoding(720p recording)
2.enable 4-lv freq setting in bootmenu( a little edit in overclock.c)
3.share SD/data/system function in bootmenu are still buggy,sometimes is ok, sometimes not.
4.Alt-lock (I thinks we can ingore this)
5.battery charging(im not sure, but someone said the full voltage in stock 2.2 can reach 4200+ and down in 3100, in CM7 it only get 4160 and down in 3300)
Click to expand...
Click to collapse
So, have media playback besides mp3/mp4 been fixed?

Is this a complete CM7?
Because decompressed its only ~83 MB....

As the title says, they are fixes for applying on a defy's cm7 or miui, to make it work on milestone 2.
It's not a complete ROM.

ah ok and install logically in cwm "apply update from zip" ?

r2beta0 said:
So, have media playback besides mp3/mp4 been fixed?
Click to expand...
Click to collapse
No,this issue is described in 1th point as video decoding.And i think this also cause the 720p problem.

mj084 said:
ah ok and install logically in cwm "apply update from zip" ?
Click to expand...
Click to collapse
No,but you can overwrite cm7 package with this.

overwrite cm7 package with this....how?

[TUT][Script]v6 Supercharger and Kick Ass Kernelizer script WORKS

Hello. The supercharger script by zep worked great on my galaxy ace. Now, has anyone been able to use it with the tab+? I think it would be a huge help to remove kauncher redraws and in improving the battery life. Do you guys think it would work on our tab? Our brothers from the gtab 10.1 were able to use it. http://forum.xda-developers.com/showthread.php?t=1256796&page=24
Click to expand...
Click to collapse
EDIT. 12/29/2011
Okay. Since no one bothered to reply, i took the risk and applied the script. To cut to the chase, IT WORKS. There are no launcher redraws and my tab sure feels a lot smoother. I also have 400 used RAM instead of 600 after a restart. Not to mention, i now have 6037 AnTuTu benchmark score as opposed to the 5700 that i got before supercharging.
------------------------------------------------------------------------
EDIT. 12/31/2011
------------------------------------------------------------------------
EDIT. 02/02/12
(I updated the versions to their latest in accordance with zepp's latest released scripts. supercharger 5.2 and KAK 3.1. The steps to be followed are still the same.)
If anyone wants to try, here are the steps that i followed.
BUT first things first.
CREDIT GOES TO zeppelinrox FOR HIS GREAT WORK ON THIS SCRIPT.
I ALSO WOULD LIKE TO THANK mroneeyedboh FOR THE STEPS HE PROVIDED OVER THE GTAB 10.1 FORUMS.
Original supercharger thread http://forum.xda-developers.com/showthread.php?t=991276
GTAB 10.1 supercharger guide http://forum.xda-developers.com/showthread.php?t=1256796
P6200 CWM and Root by garyd http://forum.xda-developers.com/showthread.php?t=1392348
***You MUST be rooted and have busybox 1.18.2 or upper (I have 1.19.3)***
So let's cut to the chase!
DOWNLOAD THE FOLLOWING.
v6 Supercharger script U9 RC5.2 http://forum.xda-developers.com/attachment.php?attachmentid=877591&d=1327834355
Script Manager https://market.android.com/details?id=os.tools.scriptmanager&feature=search_result
Zepp's original post with the log changes http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Save the supercharger script anywhere on your storage
Run Script Manager and press Browse as Root (the one under Install). When the SU dialog appears press allow.
While on Script Manager, browse to where you save the supercharger script click it
A new window would appear. Press the "Su" icon under the Run button at the upper left hand corner. Press Run.
A lot of codes would appear. Some sort of system check bla bla bla. Just a little patience...
"Press Return Key... and Come Get Some!!" would appear. DON'T PRESS THE RETURN KEY. Press anywhere and press any key and then press enter.
You would then see a lot of options 1-31. Please enter number 9.
It would now run the setting we chose. Like lowmemkiller values, OOM groupings, Kernel/Mem Tweaks, etc..
If an option to not use Build.prop appears, cause it might cause boot loops, then allow the creation of local.prop (i think. i can't remember). Just follow your heart. haha
Press the back soft key. "Script is running. What do you want?" Choose Kill.
Since we're all using stock ROMs (for the moment), press the back soft key until you reach the ROOT directory. Then open the Data folder and click on the 99Supercharger.sh
Then under the Run button, press the icon for Su and Boot. This would automate the supercharger script upon boot. Then press run and then kill the script.
Run the first script again (yup the one from Step 1). and now, choose option number 30. It would now super clean the system and restart.
DONE! Feel the difference!
If I missed anything, please inform me.
You could also install the Kick Ass Kernel Tweaks (KAK) from here http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021. Get the update 3 RC3.1
KAK Direct Download http://forum.xda-developers.com/attachment.php?attachmentid=877590&d=1327834355
IMPORTANT!!!!! Just follow the steps from above and be sure not to apply the IO Tweak as it is very unstable and might cause boot loop
Then using step number 11, navigate to 98KickAssKernelizer.sh and make it run upon boot.
Reboot your device and DONE!
Based on MY observations, here are the changes that I noticed.
Completely no launcer redraws (wherein the widgets disappear and appear. it's like refreshing in windows), I'm using the default Touchwiz UX.
There is no delay with the Task Switcher. (the third soft key) Before applying the script, I had like 1-1.5 second delay with it. Now it only has 0.5 or so.
The RAM usage is stable at 530-570. Compared to 660 before supercharging
The best part about this script is that multi-tasking has been easier. Jumping from one app to another is now a breeze. Applications start faster than before.
The thing is, our tablet is already blessed with great hardware which is why it is already fast and smooth to begin with. BUT, there is always room for improvements. FACT.
BR

That's impressive!
I have the P6210. Are you using the P6200 with the 3g?
Dan

Interesting find. Would you mind sharing the installation process. From the original post seems quite easy, but on the 10.1 tread it looks way more complicated.
P_

rp518dan said:
I have the P6210. Are you using the P6200 with the 3g?
Dan
Click to expand...
Click to collapse
Yes. i have the P6200 with 3G. I think the process and result would be the same with the P6210.
pakalrtb said:
Interesting find. Would you mind sharing the installation process. From the original post seems quite easy, but on the 10.1 tread it looks way more complicated.
P_
Click to expand...
Click to collapse
okay. i'll update it in a while.

just tried it, enabling the 99supercharger.sh and 98kickasskernel.sh at boot threw me into a boot loop. it said to make sure to enable at boot, so i did. will give it another try or just manually add custom lines to build.prop ..

chrisrotolo said:
just tried it, enabling the 99supercharger.sh and 98kickasskernel.sh at boot threw me into a boot loop. it said to make sure to enable at boot, so i did. will give it another try or just manually add custom lines to build.prop ..
Click to expand...
Click to collapse
really? I wonder why. I did not encounter any boot loop. Could you check my steps that i just posted and compare it with the steps that you did?
Also, what busybox version did you use?
I think it's with the KAK Tweak. Maybe you applied the IO scheduler?
as quoted from zeppelinrox
Updated August 1: Added Kick Ass Kernel Tweak Installer but without io scheduler tweaks. Use this new script if you try the regular Kick Ass Kernel Tweak Installer and get a boot loop! (My apologies to those that got the boot loops )
Click to expand...
Click to collapse
SOURCE: http://forum.xda-developers.com/showpost.php?p=15948434&postcount=1127

And you think that I would wait for tutorial or tester to try it out !?!?!
OK, I did the following :
1) downloaded the script and put it in the sd card ( not external sd ) root
2) downloaded and installed script manager
3) run the SM and selected the script
4) selected run as root and hit the RUN
5) selected 1 as scrolling speed
6) selected 9 ( MegaRam 2 )
7) selected 17 = Exit
8) broswed back to ../data and selected the 99supercharger.sh file
9) selected the run as root and run at boot option
10) Save and Exit the SM
11) Rebooted
All fine ( I mean no bootloop ) but to be quite honest NOTHING changed in terms of performance. I double checked that the script was run at boot and it did, since the values have been changed.
But the benchmarks are the same and the tab seems lagging as usual.
Also the amount of free RAM have not changed from previous stock configuration.
I fear that the main problem is GoLauncher, that seems to have slowed down the tab even more after the last update.
P_
---------- Post added at 12:01 PM ---------- Previous post was at 11:44 AM ----------
chrisrotolo said:
just tried it, enabling the 99supercharger.sh and 98kickasskernel.sh at boot threw me into a boot loop.
Click to expand...
Click to collapse
What do U mean by boot loop, and how did you get out of it ?
P_

pakalrtb said:
And you think that I would wait for tutorial or tester to try it out !?!?!
OK, I did the following :
1) downloaded the script and put it in the sd card ( not external sd ) root
2) downloaded and installed script manager
3) run the SM and selected the script
4) selected run as root and hit the RUN
5) selected 1 as scrolling speed
6) selected 9 ( MegaRam 2 )
7) selected 17 = Exit
8) broswed back to ../data and selected the 99supercharger.sh file
9) selected the run as root and run at boot option
10) Save and Exit the SM
11) Rebooted
All fine ( I mean no bootloop ) but to be quite honest NOTHING changed in terms of performance. I double checked that the script was run at boot and it did, since the values have been changed.
But the benchmarks are the same and the tab seems lagging as usual.
Also the amount of free RAM have not changed from previous stock configuration.
I fear that the main problem is GoLauncher, that seems to have slowed down the tab even more after the last update.
P_
Click to expand...
Click to collapse
Hmmm.. Maybe it's because we have different applications installed, settings, etc. With my experience, there are some very noticeable changes.
Completely no launcer redraws (wherein the widgets disappear and appear. it's like refreshing in windows), I'm using the default Touchwiz UX.
There is no delay with the Task Switcher. (the third soft key) Before applying the script, I had like 1-1.5 second delay with it. Now it only has 0.5 or so.
The RAM usage is stable at 530-570. Compared to 660 before supercharging
The best part about this script is that multi-tasking has been easier. Jumping from one app to another is now a breeze. Applications start faster than before.

I think it may hav had to do with changing the I/O tweaks from local.prop to build.prop, it said it was dangerous. after reboot about 20 sec or so SuperUser toast says script manager was granted root permissions, meaning the 98/99.sh scripts were loaded. I didnt run the v6script at boot. after about the 3rd reboot, I had time to go into app drawer and quickly drag uninstall and it stopped constant reboot.

tried the instructions in the OP and i can confirm this works on my P6200 and solved a lot of the lag I had.
Sent from my GT-P6200 using xda premium

Hmm, I had originally used the V8 version . I have uncharged, wiped the cache and recharged it with RC4 9V . But still the same. I do not see any difference from the original performances and the Antutu Benchmark gives pretty much the same results as before. I was hoping my tab would fly out of my hands after this hack ......... but not really
Curious to read about others, it looks like we have only 3 brave souls so far
P_

pakalrtb said:
Hmm, I had originally used the V8 version . I have uncharged, wiped the cache and recharged it with RC4 9V . But still the same. I do not see any difference from the original performances and the Antutu Benchmark gives pretty much the same results as before. I was hoping my tab would fly out of my hands after this hack ......... but not really
Curious to read about others, it looks like we have only 3 brave souls so far
P_
Click to expand...
Click to collapse
Haha yeah. And I am hoping that there would be more brave souls in the Development Section.
What score did you get in the Antutu Benchmark?

5648/5804/5727 three consecutive tests.
uncharged everything and got back to stock config : 5654/5841/5708
After uncharging I still got left a 1000HP Super-(6,12,200,220,240,275).sh file in ../data
P_

Bump.
No more testers?
P_

I am giving it another shot .
The only noticeable difference is that the amount of available RAM is always around 300 mb. BUT this also tend to decrease ( sometimes to 100 ) with extended use. With stock configuration I'd have 100/250 available, with the system bumping it up to about 300 when it was going lower than 100.
As for the quick access button, it's definitely snappier when you turn the device on, but it goes back to about 1 sec after a while.

I have a P6200 and applied the script, look smooth then before applied the script. Thanks for the instruction

Hey just wondering if anyone knows how to remove this script..Thanks!
Sent from my GT-P6200.

DevilBeyond said:
Hey just wondering if anyone knows how to remove this script..Thanks!
Sent from my GT-P6200.
Click to expand...
Click to collapse
It has an option to unsupercharge. It's listed in the menu with the different options of supercharging etc.

I'm currently suggesting that people do NOT use this script.
There are bugs in the GT-P62x0 kernel(s) that can (and do) cause kernel panics. Under normal circumstances, those panics would cause your tablet to simply reboot.
However, this "supercharger" script overrides a kernel parameter and prevents the kernel from rebooting on a panic, instead forcing it into an infinite loop. Instead of the bug rebooting your tablet, it causes your tablet to be frozen (if the screen is off, it appears to be a so-called sleep of death.)
To make matters worse, if this situation occurs when the tablet is running on battery power (not plugged in), then the infinite loop will completely deplete your tablet's battery (which can harm it.)
Take care
Gary

I have used supercharger on my phone without issue but after
reading what Gary discovered, I won't be using it again.
Thanks Gary

[Q] that .10 kernel-which power config?

I put on cromi-x 5.4 using that .8 kernel...All is good.. sort of ...
Main problems I have is Flixster doesnt seem to work. AND also with my precious Zen Pinball. Can't go into portrait mode. Had this problem on stock but it fixed as was perfect when it updated to stock .10 .. Would going to " _that's .10" solve this? If so, which cpu power config would be best? I noticed when you choose that kernel you get a choice of 3 and no indication of what is default. H.A.N.O. (Help A Noob Out)

Anyone got an opinion on which power config to use for the that.10 kernel.?? Anyone?Anyone?

toastman430 said:
I put on cromi-x 5.4 using that .8 kernel...All is good.. sort of ...
Main problems I have is Flixster doesnt seem to work. AND also with my precious Zen Pinball. Can't go into portrait mode. Had this problem on stock but it fixed as was perfect when it updated to stock .10 .. Would going to " _that's .10" solve this? If so, which cpu power config would be best? I noticed when you choose that kernel you get a choice of 3 and no indication of what is default. H.A.N.O. (Help A Noob Out)
Click to expand...
Click to collapse
I don't understand the question
What does power mode (power saving, balanced and performance) have to with portrait? I think you are confusing _thatv10 with the Aus stock upgrade .10. They are different things.
The default is 1Ghz / 1.5GHz / 1.7GHz. When you install _that in the rom installer you get 1.3/1.5, 1.5/1.8 or 1.3/1.8 (power saving stays the same).
If you install _that v10 you will just have 1.5/1.8 but you will still have the same issues.
I think you need to lookup how to take a logcat, start the app, let it fail to do what ever you expect it to do, then grab the logcat and post it here

sbdags said:
I don't understand the question
What does power mode (power saving, balanced and performance) have to with portrait? I think you are confusing _thatv10 with the Aus stock upgrade .10. They are different things.
The default is 1Ghz / 1.5GHz / 1.7GHz. When you install _that in the rom installer you get 1.3/1.5, 1.5/1.8 or 1.3/1.8 (power saving stays the same).
If you install _that v10 you will just have 1.5/1.8 but you will still have the same issues.
I think you need to lookup how to take a logcat, start the app, let it fail to do what ever you expect it to do, then grab the logcat and post it here
Click to expand...
Click to collapse
ok, so there's no correlation between the app and the kernel, got it..fine..
So I guess main questions now are..is the that.10 kernel so much better over the .8?
And if I went to .10, which config do people like?
Thanks for the understanding.

toastman430 said:
ok, so there's no correlation between the app and the kernel, got it..fine..
So I guess main questions now are..is the that.10 kernel so much better over the .8?
And if I went to .10, which config do people like?
Thanks for the understanding.
Click to expand...
Click to collapse
It's not It's basically the same kernel but _that added some stuff to add better preinit scripting for auto detecting partition types and using romn2sd and data2sd etc. For normal users _that v8 = _thatv10.
If you flash _that v10 you will lose the abilty to choose a config and be forced onto 1.5Hz and 1.8GHz as I already explained as you are just flashing a kernel and it will overwrite your cpu settings. You could use trickster mod to set the frequencies yourself of course

Hp devices - all things root guide

A lot of cleanup has been done. if you wish to view the old version, there is a signed word document with the password pleaseclickthethanksbutton
Rooting hp slate 7 or 6 voicetab is very easy
Warning n.1 :- do not install any otas. Fotakill is uploaded for convenience
You will still receive updates after rooting
Many hp devices already have busybox, bash,swap support etc
you will need to install openvpn, sqlite, etc binary separately
rooting :- Root it through kingo root
While rooting your device may turn off and start charging, if it happens turn it on
The same will happen again
Turn it on again
Done! Rooted
If it didn’t work, try vroot
To replace vroot with supersu , go to http://goo.gl/r9uENy
Try cydias impactor as well
Important warning :- Don’t take any otas, especially if you have the hp slate 7 6102ra voicetab
The above method worked for me.
Tell me if there is any problem.
Vroot link :- http://goo.gl/sFnoCX
Kingo root link :- http://goo.gl/7vT35O
I will write a comprehensive guide to speed up these devices.
I have uploaded my modded build.prop you can check it once

Safe to install xposed
Safe to root
If you're an Indian user there is no update.zip to restore the device to factory state
Don't install update to KitKat on hp slate 7 6102ra it will brick your phone
Don't ask how to unlock bootloader. There is already a guide on xda-developers.com

Please support chainfire
You can support chainfire by installing supersu pro

No illegal activity
Please do not do illegal things with root.
If you intend to use lp, use it for legal things like DPI patches etc.

after root
after root, there's lot work to do for this phablet
I'm curious, how to overclock it to 1.283Ghz? the SKU setting tell it capable to run till 1,3Ghz (*#*#4636#*#* method), I've tried modify its governor and cpu frequencies under /sys/ directories, it still refuse to run 1.3Ghz, the file revert back to its original state after I modify it
my device detail:
6002ra, 1.01.06 A, stock ROM Android 4.4.2, kernel 3.4.39, rooted, ART runtime.

Are you running on Marvell chipset or Marvell processor? Please read carefully this guide is for hp slate 7 6101 and 6102ra voicetabs and for slate 6 phablets.

There's an easier way to clock it.
Sorry but it's impossible to do it in root.
Luckily, I found a method :-
1 Open secret menu *#*#4636#*#*.
2 Click on Marvell testing.
3 Click on powersettting.
4 Turn powersettting service and power meter on.
5 Go to frequency setting.
6 Turn off dynamic frequency.
7 Click on set frequency.
8 Click on benchmark.
9 Over clocked to highest anything else requires a custom kernel.
I am not responsible for things like over-heating etc.
Over clocking vpu is a bit tricky I'll post a guide on that too.

If you want to know how to root a phone ask me
However you should take responsibility for anything that happens to your phone
It is safe to install xposed on these devices
See my other guide to root Panasonic eluga a
It is impossible to unlock bootloader. Don't try it

allz.hat said:
after root, there's lot work to do for this phablet
I'm curious, how to overclock it to 1.283Ghz? the SKU setting tell it capable to run till 1,3Ghz (*#*#4636#*#* method), I've tried modify its governor and cpu frequencies under /sys/ directories, it still refuse to run 1.3Ghz, the file revert back to its original state after I modify it
my device detail:
6002ra, 1.01.06 A, stock ROM Android 4.4.2, kernel 3.4.39, rooted, ART runtime.
Click to expand...
Click to collapse
No probs look ↑ there's a method

overclock the vpu in sys/devices/devfreq-vpu folder

Youtube video
Youtube video at :- http://goo.gl/dmHxd1 (no, there isn't a video tutorial.).

Today, at 0:02 3rd march 2015 the thread was updated.
What's in this update?
improved rooting method (old method available for download. look at 1st page)
fixed typos
added a method to overclock cpu, vpu, gpu ,ddr
fixed grammatical mistakes

speed up tutorial
go to http://goo.gl/VZn5EX

overclocking the VPU give me nothing but overheated battery, I revert back to its factory settings at 400Mhz
funny fact that slate 6 will work much more cool and responsive if you set the memory speed at 533Mhz,, 3D and 2D engine at 384Mhz, leave anything else stock
Note: ART runtime will ruins device stability, don't use it in its stock 4.4.2 ROM

i am back !
allz.hat said:
after root, there's lot work to do for this phablet
I'm curious, how to overclock it to 1.283Ghz? the SKU setting tell it capable to run till 1,3Ghz (*#*#4636#*#* method), I've tried modify its governor and cpu frequencies under /sys/ directories, it still refuse to run 1.3Ghz, the file revert back to its original state after I modify it
my device detail:
6002ra, 1.01.06 A, stock ROM Android 4.4.2, kernel 3.4.39, rooted, ART runtime.
Click to expand...
Click to collapse
first go to *#*#4636#*#* > marvell testing > power setting and turn on power setting go to frequency setting and turn off dynamic freq
hi,
to tell you how to clock it, i will take example of the VPU (GPU)
after a lot of experiments , i found you cannot use the echo >> <xxxx> /sys/devices/platform/devfreq.vpu0/min_freq command but if you copy the /sys/devices/platform/devfreq.vpu0/min_freq to /sdcard, modify it and place it back to /sys/devices/platform/devfreq.vpu0/min_freq, it works!
to make a startup script
type cp /sys/devices/platform/devfreq.vpu0/min_freq /sdcard
modify it (caution - value should be equal to /sys/devices/platform/devfreq.vpu0/max_freq !) and use rom toolbox pro/free to create a startup script as follows
cp /sdcard/min_freq /sys/devices/platform/devfreq.vpu0/min_freq
or use
cp /sys/devices/platform/devfreq.vpu0/max_freq /sys/devices/platform/devfreq.vpu0/min_freq
i will upload a screenshot of my startup scripts when i get time.

allz.hat said:
overclocking the VPU give me nothing but overheated battery, I revert back to its factory settings at 400Mhz
funny fact that slate 6 will work much more cool and responsive if you set the memory speed at 533Mhz,, 3D and 2D engine at 384Mhz, leave anything else stock
Note: ART runtime will ruins device stability, don't use it in its stock 4.4.2 ROM
Click to expand...
Click to collapse
hi,
please try going to developer options (these are hidden - google it) and select force gpu rendering, disable hw overlays, force 4x msaa and profile gpu rendering (caution - profile gpu rendering can cause negative performance if the graphics card quality is poor-it happens on my hp slate 7 voicetab
im sorry, i cant test on ART as hp released a buggy update.zip to kitkat file which bricks any device- rooted or unrooted. so i can't test on kitkat and xposed doesn't work on kitkat ART anyways

thanks, i have overclocked and found no heat. perhaps you are using a different device with a faster processor ? ill try to reproduce the problem at my end. if you are using greenify, uninstall it unless using xposed mode. i got a really hot phone (hot enough to cook my food) while using greenify in root mode but no problem in xposed mode

1979 views on youtube video ! thanks guys you rock !

do not flash audio mods. your phone's sound will totally go away !

allz.hat said:
overclocking the VPU give me nothing but overheated battery, I revert back to its factory settings at 400Mhz
funny fact that slate 6 will work much more cool and responsive if you set the memory speed at 533Mhz,, 3D and 2D engine at 384Mhz, leave anything else stock
Note: ART runtime will ruins device stability, don't use it in its stock 4.4.2 ROM
Click to expand...
Click to collapse
its not at all funny. the more you speed it up, the faster a task will complete. the phone can then go into sleep mode much more frequently-even when the screen is on. this means your processor will be sleeping 50-70% more if you increase clock speed which translates into a cooler device with much more responsiveness and better battery life. who says oc is bad for battery life? (unless you overdo it-be careful,my friend)

OC-K1 Nougat

3.0
given up using peoples dirty code, so downloaded nvidias dirty code instead lol
cleaned the code up best i could, things ive noticed while playing games on the tablet is -
when i play "nitro nation" the first race no longer stutters
when popups appear they dont take a while to appear..
when i play "word mind" it doesnt take ages to load with crackling sound
when using "kernel auditor" if you set the GPU max and min values high (i only did this trying to keep the values standard), when the GPU gets hot, it cant scale down the GPU frequency so it starts trying to kill tasks.
i dont think you need to download/flash blobs as they are for flashing binary stuff, but i cant find a need for it, think its more of a precaution to ensure the kernel boots.. but dont think i have flashed them
-----------------------------------------------------------------------------------------
3.1 : FINAL,
dunno what changes i made but ive recently upgraded my tablet so figured id upload my latest and last
obveously i have had to start again running 3.10.96 but done alot of work to make it as fast as i can so far, but i deleted all references to my old code and cant find them anymore,
GPU is now at 914 MAX as ive found its the GPU that generates a lot of heat, which causes it to throttle, and found values higher than this just degraded performance.
ive known for a long time that "DT2W" works great while connected to USB, due to the custom USB wakelock, i know the app "wakelock revamp - power manager" would resolve it. but ive found tapping where "notifications" would be wakes the screen (ive found bottom right where the camera would be is a good spot) im trying to figure out how to apply the wake lock better.
scores on PCMARK are above the scale on most values
scores on 3DMARK are around 3250 ~ 3320
=========================================
if you want to create your own, i created a guide, also the website i used to help me understand
https://************/how-to-build-android-kernel-on-windows-10/ appuals . com
-----------------------------------------------------------------
Thanks to :
-----------------------------------------------------------------
"hazel nut" for his support, as if he never said "cant wait for it to come out" i dont think it would of pushed me so much
----------------------------------------------------------------
"BitOBSessiOn" for his source code
https://github.com/BitOBsessiOn/android_kernel_nvidia_shieldtablet
-----------------------------------------------------------------
"laufersteppenwolf" for his source code and commits to overclocking and DT2W/STW
https://github.com/laufersteppenwolf/android_kernel_nvidia_shieldtablet
-----------------------------------------------------------------
"Christopher83" for his cross compiler
https://github.com/Christopher83/arm-cortex_a15-linux-gnueabihf-linaro_4.9
-----------------------------------------------------------------
Microsoft, if i didnt hate windows 10 so much, and didnt get a message regarding dropping support for windows 7,
i would still be using a virtual machine which due to it being so slow, i would of probably given up a long time ago
----------------------------------------------------------------
thanks to everyone that has said thank you

Nice to see that you open a thread.
Appreciate a bit companionship here.
In your guide didn't you specify how you create thr zip file.
I used the nethunter installer, which is based on lazy flashed in regard of the external modules, this come in handy, but I found relatively little among the Shield kernel support.
I noticed that you set the make command with the addition of the specifications of the number of CPUs, which are to be used, before every command.
Is this a typo, or is this the correct procedure when you compile with Windows?
Did you mean with
"bin-bash-command"
Click to expand...
Click to collapse
-
cd ~
Click to expand...
Click to collapse
?
PS
1

response
That's just how I make the command, as if you tap the up key, you can scroll through previous inputs, if it makes it faster- that's a bonus.. but you're right about being very little support.
With regards to the zip file - you could use mine or any other zip that is a kernel flash - as long as you drop it into the kernel folder.. I believe there is an "anykernel.zip" somewhere if you prefer to use that.. also if you wish to add your own personal touch, you can modify the script file in the metadata folder

Response
I also chose different colours in the guide and placed it in a separate line so people could understand the exact typing.. or they could copy and paste..
But with regards to support it is one of the reasons I made the guide, in hopes the Nvidia community could follow it, understand how to achieve their own kernel, and improve the tablet. As there seems to be a serious lack of support..
I had to learn on my own, through Google and YouTube, but hopefully this will speed up what took me a month of trial and error..

Is it compatible with stock based fw (5.4)? Just need to flash blobs, then kernel and reboot?

Respond
Yeah, extract the blobs before flashing.. only available for stock/stock+ rom

Reply
Oh, by the way, you can’t compile with windows unless you’re using a virtual machine.. has to be Linux/terminal

Bleeblun said:
Yeah, extract the blobs before flashing.. only available for stock/stock+ rom
Click to expand...
Click to collapse
Thank you, I will try out as soon as I can get to my computer. I have downloaded the wakelock v3 app and kernel adiutor an I can't enable wakelock in kernel adiutor (I can't see any option for it). Only this new kernel will support this option, am I right?

Reply
attom93 said:
Thank you, I will try out as soon as I can get to my computer. I have downloaded the wakelock v3 app and kernel adiutor an I can't enable wakelock in kernel adiutor (I can't see any option for it). Only this new kernel will support this option, am I right?
Click to expand...
Click to collapse
You must of done something wrong as “wake” is below “gpu”
You extract> then flash the blob at the fastboot menu via typing - fastboot flash staging <blobfilename>
Then via TWRP recovery you install the “OC K1” kernel without extracting.. I have 3 tablets and it’s worked on them all.. hope this helps,

Bleeblun said:
You must of done something wrong as “wake” is below “gpu”
You extract> then flash the blob at the fastboot menu via typing - fastboot flash staging <blobfilename>
Then via TWRP recovery you install the “OC K1” kernel without extracting.. I have 3 tablets and it’s worked on them all.. hope this helps,
Click to expand...
Click to collapse
Yeah, everything worked, awesome, thank you!!

Response
attom93 said:
Yeah, everything worked, awesome, thank you!!
Click to expand...
Click to collapse
Thanks for letting me know, originally you wouldn’t of needed the “wake v3” app, but I started fresh, which gained performance, and I decided to look for an easier way to stop the tablet “deep sleeping” on me.. less of a headache this way :laugh: