Hi Guys,
I am back with a new Kernel to try.
I have compile it with last Linaro Toolchain after lots of problems to compress a zImage
This is a 1100MHz version with all Tweaks from my own first kernel.
I attach too my initramfs.cpio.gz modify. Time passed 20 to 5 seconde, 20 is too loooooooooooong
Remember: Report!!!!
FYI: i have made 2200 under Quandrant (not representative but...it's an information), and that's all....i have no game on it (total wipe very often lol).
Have fun!!!
Source:
https://github.com/bizcuite/Archos_Gen8_Linaro_kernel.git
Bizcuite
bizcuite said:
Hi Guys,
I am back with a new Kernel to try.
I have compile it with last Linaro Toolchain after lots of problems to compress a zImage
This is a 1100MHz version with all Tweaks from my own first kernel.
I attach too my initramfs.cpio.gz modify. Time passed 20 to 5 seconde, 20 is too loooooooooooong
Remember: Report!!!!
FYI: i have made 2200 under Quandrant (not representative but...it's an information), and that's all....i have no game on it (total wipe very often lol).
Have fun!!!
Bizcuite
Click to expand...
Click to collapse
I have forgotten that you can see the version of GCC by SetCPU ^^ (to see that it's not a fake)
Bizcuite
I got 300 points lower in Antutu Benchmark. Its quite unstable because I got 3 soft reboots for less about 4-7 minutes. It might be stable with non-OC kernel.
Mavasilisk said:
I got 300 points lower in Antutu Benchmark. Its quite unstable because I got 3 soft reboots for less about 4-7 minutes. It might be stable with non-OC kernel.
Click to expand...
Click to collapse
I have no problem with it
I don't know if compilation is unstable, i have the same kernel like you. (i think that the compression may cause lost of data).
Try this and DO NOT DECOMPRESS THE ZIMAGE.ZIP, JUST RENAME IT, DELETE THE ".ZIP" EXTENSION!!!
I recompile it later and upload it if there are no results.
Bizcuite
ZIMAGE.ZIP (Upload failed on last post)
1000 MHz Version
1000MHz Version:
SAME FAKE: DON'T DECOMPRESS JUST RENAME IT
Please report, if it works or not
Bizcuite
Guess it was the problem cuz I decompressed it until I found a zImage inside. Gonna try it and post the results.
EDIT : The non-OC kernel works good. Gonna try the OC until I fell asleep. I will update the post tommorow.
UPDATED: The latest OC kernel is working good. Video playback is smooth. The whole system is running good.
Testing the OC kernel, seems very stable. All video apps seem to be working. Thanks.
Testing both non-OC kernel & OC Kernel in Archos 101/g8:
The System seems very unstable and easily freeze and YouTube video no output?
--->Change back to Bull-RC2's Kernel then more stable (sometime YouTube video
laggy) !!
I suppose download wrong initramfs.cpio.gz & Zimage file from the thread??
jackson0829 said:
Testing both non-OC kernel & OC Kernel in Archos 101/g8:
The System seems very unstable and easily freeze and YouTube video no output?
--->Change back to Bull-RC2's Kernel then more stable (sometime YouTube video
laggy) !!
I suppose download wrong initramfs.cpio.gz & Zimage file from the thread??
Click to expand...
Click to collapse
I think that the compression of files makes errors on its.
Have you tried the second and the third version of the kernel with original initramfs from Bull?
Bizcuite
bizcuite said:
I think that the compression of files makes errors on its.
Have you tried the second and the third version of the kernel with original initramfs from Bull?
Bizcuite
Click to expand...
Click to collapse
Yes,I tried the second and the third version of the kernel with original initramfs
but results are same?
--> I try to adjust CPU frequency <900MHz then system more stable but
Youtube still no output?
jackson0829 said:
Yes,I tried the second and the third version of the kernel with original initramfs
but results are same?
--> I try to adjust CPU frequency <900MHz then system more stable but
Youtube still no output?
Click to expand...
Click to collapse
Huum i don't know what's append with your, i will make another kernel with only A101 configured on it, share you (only you) to try.
If anybody has same tablet like him can you report it please?
If nobody have the same result i think that your image system is the pb.
What's your release of Bull RC?
Bizcuite
Great work!! a70 g8 working fine, 2760 in Antutu @ 1100Mhz
but compcache not working for me
I have an A101 and I will test tomorrow
Edit : I will test this afternoon, I didn't check my clock ^^
bizcuite said:
Huum i don't know what's append with your, i will make another kernel with only A101 configured on it, share you (only you) to try.
If anybody has same tablet like him can you report it please?
If nobody have the same result i think that your image system is the pb.
What's your release of Bull RC?
Bizcuite
Click to expand...
Click to collapse
I try to re-install "openaos-gingerbread.img" ROM and seems system more
fast and stable no mater with 1100 OC or 1000 non-OC's Kernel, but
Youtube video still could not display no mater with Bull or yours Kernel??
---> I have double checked the UrukDroid 1.6.4 ROM did not have Youtube
video display issue (just 10~20 seconds delay to display)
jackson0829 said:
I try to re-install "openaos-gingerbread.img" ROM and seems system more
fast and stable no mater with 1100 OC or 1000 non-OC's Kernel, but
Youtube video still could not display no mater with Bull or yours Kernel??
---> I have double checked the UrukDroid 1.6.4 ROM did not have Youtube
video display issue (just 10~20 seconds delay to display)
Click to expand...
Click to collapse
Try to format data partition or image from bull. Try if you tube works after reinstalled it
I don't thunk the kernel is the pb.
I hope that it works.
Bizcuite
Sent from my GT-I9000 using xda app-developers app
I am a bit lost
Should I instaol the kernel from the OP on the one 3 post later ?
EDIT : I installed the first one (which is OC to 11000Mhz) but why such different sizes?
---------- Post added at 11:34 AM ---------- Previous post was at 11:05 AM ----------
minidou-77 said:
I am a bit lost
Should I instaol the kernel from the OP on the one 3 post later ?
EDIT : I installed the first one (which is OC to 11000Mhz) but why such different sizes?
Click to expand...
Click to collapse
Is that me or the f****** crack sound is back ?
I used the initramfs which comes with the kernel zip in the OP
Also when I put my ear really close to the back I hear some noise...
Really strange...
I have an A101
minidou-77 said:
I am a bit lost
Should I instaol the kernel from the OP on the one 3 post later ?
EDIT : I installed the first one (which is OC to 11000Mhz) but why such different sizes?
---------- Post added at 11:34 AM ---------- Previous post was at 11:05 AM ----------
Is that me or the f****** crack sound is back ?
I used the initramfs which comes with the kernel zip in the OP
Also when I put my ear really close to the back I hear some noise...
Really strange...
I have an A101
Click to expand...
Click to collapse
the cracking sound was corrected till you use headphones.
If you use them it's still there.
It's caused by dspmanager, it's a known issue
philocritus said:
the cracking sound was corrected till you use headphones.
If you use them it's still there.
It's caused by dspmanager, it's a known issue
Click to expand...
Click to collapse
I have no cracking sound. I have fully format my tab too.
Maybe verify if the system is not the cause before that i see the kernel. I have no pb with my tab and i have exactly same.
Power On since 10h.
Edit: Minidou can you format your tab and reinstall it with last archos firmware. Reinstall bull official or mine with kernel after this. I think that the system is in cause. If you have time to do it of course.
Sent from my openAOS Build of Android 2.3 (cyanogenmod edition) using xda app-developers app
I've done it one or two weeks ago ^^
I'll try with your "old" kernel to see if its gone
Related
This is a self compiled Kernel from these sources. It's a fork of the kernel source git plus some performance tweaks and minus a bad patch, which turned out to drain the battery.
The initramfs (source) is a modified CF-Root v4.1 of the KG1.
I added some /proc and /sys tweaks in init.rc (github of the initramfs):
Code:
+ write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand
+ write /sys/block/mmcblk0/queue/scheduler noop
+ write /sys/block/mmcblk0/queue/read_ahead_kb 512
+ write /proc/sys/vm/highmem_is_dirtyable 1
+ write /proc/sys/vm/dirty_writeback_centisecs 1500
+ write /proc/sys/vm/laptop_mode 5
This probably works best with Villain ROM 2.0 [2.3.4] and the XXKG1 radio image.
History:
Version 1.1:
added touchscreen fix suggested by vincenzo91.
Version 1.2 :
now based on CF-Root 4.1 (was 4.0)
cherry-pick'ed some fixes from cfs-exp branch of ninphetamine github
removed "setprop dalvik.vm.execution-mode int:fast", which prevents JIT
changed touchscreen MOVHYSTI to 5 from 0 (15 original)
Version 1.3 :
removed bogus /sys, /proc settings
use /init from KG1/CF-ROOT
set readahead to 512kb
enabled fuse, so you can use "ntfs-3g" to mount a NTFS drive
There is also a variant with MOVHYSTI set to "0" (Backslash-1.3-HYST0). Let me know, if you have those touchscreen problems with either "0" (HYST0) or the "5" in the normal kernel.
So how does it look like? See the attached image (FastDormancy was not turned off, because it got better in 2.3.4)
Benchmark CF-Bench Pro v1.1
Interpretation left to the reader...
Code:
Stock CF-Root KG1: | Backslash-1.3:
Native: 11256 11478 11172 | 11566 11360 11414
Java: 3155 3235 3071 | 3411 3240 3327
Overall:6395 6532 6311 | 6673 6488 6561
read: 553 535 540 | 564 571 570
write: 138 180 176 | 181 181 173
saturn_de said:
This is a self compiled Kernel from this sources. It's a fork of the kernel source git plus some performance tweaks and minus a bad patch, which turned out to drain the battery.
The initramfs is a modified CF-Root v4.0 of the XXKG1.
I added some /proc and /sys tweaks in init.rc.
This probably works best with Villain ROM 2.0 [2.3.4] and the KG1 radio image.
So how does it look like?
Click to expand...
Click to collapse
So does this also fix the push exchange email battery drain or just some other drain (non-existent to me)?
saturn_de said:
This is a self compiled Kernel from this sources. It's a fork of the kernel source git plus some performance tweaks and minus a bad patch, which turned out to drain the battery.
The initramfs is a modified CF-Root v4.0 of the XXKG1.
I added some /proc and /sys tweaks in init.rc.
This probably works best with Villain ROM 2.0 [2.3.4] and the KG1 radio image.
So how does it look like?
Click to expand...
Click to collapse
This can fix the Android OS draining ?
szav said:
This can fix the Android OS draining ?
Click to expand...
Click to collapse
standby battery usage seems quite good, will try on cognition 1.11 and feedback..
Hy guys is it possibile have this kernel in a zip flashable version..
I haven' t my pc here but i need to try cause i want my phone for 24 hrs...a day...
Regards
cescof said:
Hy guys is it possibile have this kernel in a zip flashable version..
I haven' t my pc here but i need to try cause i want my phone for 24 hrs...a day...
Regards
Click to expand...
Click to collapse
Just flash in CWM. Open CWM and select Flash Kernel, then select this kernel. It will flash then reboot.
Testing it now. Lets hope it works
Btw, have you noticing it not obeying SetCPU?
In both CF-Root and a testkernel I tried then clock would go above the max I set. I had it set at 800 but it still went to 1ghz, 1.2ghz and 1.6ghz...
ante0 said:
Just flash in CWM. Open CWM and select Flash Kernel, then select this kernel. It will flash then reboot.
Testing it now. Lets hope it works
Btw, have you noticing it not obeying SetCPU?
In both CF-Root and a testkernel I tried then clock would go above the max I set. I had it set at 800 but it still went to 1ghz, 1.2ghz and 1.6ghz...
Click to expand...
Click to collapse
Just don't use SetCPU... it's useless. "Race to idle" is the key. Don't be smarter than the kernel and add more load with an app.
ante0 said:
Just flash in CWM. Open CWM and select Flash Kernel, then select this kernel. It will flash then reboot.
Testing it now. Lets hope it works
Btw, have you noticing it not obeying SetCPU?
In both CF-Root and a testkernel I tried then clock would go above the max I set. I had it set at 800 but it still went to 1ghz, 1.2ghz and 1.6ghz...
Click to expand...
Click to collapse
Really? Where did you check your real clock speed? In the Battery statistics in setCPU it tells me 0% for 1200 Mhz if i set it to 500-1000Mhz, using CF-Root for now.
@saturn_de: Isn't CF-Root 4.1 out? I have no idea whats changed but im one of those "the newer the better guys" even though i know thats not always true haha
EDIT: Ill stop using setCPU for today and see how it goes
ante0 said:
Just flash in CWM. Open CWM and select Flash Kernel, then select this kernel. It will flash then reboot.
Testing it now. Lets hope it works
Btw, have you noticing it not obeying SetCPU?
In both CF-Root and a testkernel I tried then clock would go above the max I set. I had it set at 800 but it still went to 1ghz, 1.2ghz and 1.6ghz...
Click to expand...
Click to collapse
it is not an overclocked kernel..and it obeys setcpu profiles..i am using them..
Removing setcpu as per saturn.. lets see..
dr3minem said:
@saturn_de: Isn't CF-Root 4.1 out? I have no idea whats changed but im one of those "the newer the better guys" even though i know thats not always true haha
Click to expand...
Click to collapse
I will have a look what changed in CF-Root 4.1 ...
So anyone here can confirm/deny the battery drain fix?
I cannot see any change yet. Just flashed KG1 and the kernel and the Android OS is still 20%.
We will see in a long-term.
Fingers crossed.
H377 said:
I cannot see any change yet. Just flashed KG1 and the kernel and the Android OS is still 20%.
We will see in a long-term.
Fingers crossed.
Click to expand...
Click to collapse
Email is still draining... Don't know about anything else as I haven't had any other processes / apps draining my power source aka battery.
Pume said:
Email is still draining... Don't know about anything else as I haven't had any other processes / apps draining my power source aka battery.
Click to expand...
Click to collapse
I have Gmail and Exchange all set up to PUSH but I don't have a problem with them. Only the Android OS's battery usage is high.
H377 said:
I have Gmail and Exchange all set up to PUSH but I don't have a problem with them. Only the Android OS's battery usage is high.
Click to expand...
Click to collapse
If your awake bar is not blue when the screen is off then you don't have anything to worry about. Android OS percentage does not mean a thing if the phone stays asleep when it should.
Pume said:
If your awake bar is not blue when the screen is off then you don't have anything to worry about. Android OS percentage does not mean a thing if the phone stays asleep when it should.
Click to expand...
Click to collapse
Thanks!
In fact after 12 or 14 hours I got 50% of the battery with normal usage. I don't know if it's normal or not but my HD2 and Desire also last almost the same.
I always had to charge them at night every day if I didn't want them to run of fuel during next business day.
Hi,
can you tell us what tweaks you applied ?
thx
from my side the kernel looks good so far good idle batterie atm
Flashed via CWM without problems. Will be using this kernel and post results tomorrow night.
I'm on Exynos 2.0.
After 1h2m almost always in idle with screen off (GMail&Exchange Push, 3G on) 1% has gone. The phone was charged to 100% and the battery stats were also wiped.
EDIT: GPS was/is also on
This is a repackaging of DooMLoRD's kernel for the Ray - this is only for the stock Rom at this time, and will not work on MIUI or CM.
It's based on DooMLoRD's Github sources, original thread with more information about the Kernel is here: http://forum.xda-developers.com/showthread.php?t=1172885 - all thanks should go to him, I've edited very little, simply changed some of the config to suit the Ray and tested it.
Brief summary:
* Overclockable to 2GHz (set at 1GHz to start - made sure of it this time!)
* Enabled most of the schedulers so you can choose your favourite (brazillianwax, smoothass, SavagedZen, interactiveX, lagfree, minmax, Scary, smartass, interactive, conservative, ondemand, userspace, powersave, smartassV2, performance).
[UPDATE]
Had a look at the issues with the 'Flash' on the camera not working - this is now fixed.
Also, after being requested by a couple of people I've recompiled it for MIUI - you'll have to flash the second version for it to boot. (Please choose the correct one, flashing the wrong one will let you access CWM-recovery, but the system won't boot.) MIUI isn't working at this time.
Updated Kernel can be found here for Stock Roms:
http://dl.dropbox.com/u/17615284/DoomKernel-2011-12-28-1201.img
[Edit] Kernel for MIUI booted, but became unresponsive after it's been on a while. Taken the link down until I can find a day or two where I'm not using my phone so I can flash MIUI myself and look into it.
Thank you very much for this good present !
I just would ask if it is compatible with bheremans' MIUI rom, and if it's not if someone can port it, or explain to me how it can be done.
hartej said:
Brief summary:
* Overclockable to 2GHz (set at 1GHz to start - made sure of it this time!)
* Enabled most of the schedulers so you can choose your favourite (brazillianwax, smoothass, SavagedZen, interactiveX, lagfree, minmax, Scary, smartass, interactive, conservative, ondemand, userspace, powersave, smartassV2, performance). Think I may have missed a few - shall go back and check when I get a chance.
* Can't remember if I managed to get it working with the latest Ramdisk or not. At one point I was using it with a previous Ramdisk but not sure if I eventually got it working... (Currently the CMW Recovery is version 5.0.2.7?) I'll have to check on this, if it's using an old RamDisk then some of the features may not be available.
Initial release - I've been using it for a day now and it seems quite stable.
http://dl.dropbox.com/u/17615284/RayDoomKernel-2011-12-18.img
Click to expand...
Click to collapse
Can you integrate in the kernel the dual mode call recording ability, please?
aragog53 said:
Thank you very much for this good present !
I just would ask if it is compatible with bheremans' MIUI rom, and if it's not if someone can port it, or explain to me how it can be done.
Click to expand...
Click to collapse
No idea, I think that MIUI, CM7 and Stock Roms require different Kernels (or some serious customisation) so i'd be guessing: No. But it's just a guess.
Tistitus said:
Can you integrate in the kernel the dual mode call recording ability, please?
Click to expand...
Click to collapse
DooMLoRD added this to his Kernel, but I don't have any requirement to record my calls so can't confirm if it's working or not. Feel free to test it out - you may find yourself in luck!
Bah! Uploading failed the first time, but it's fixed now.
If you downloaded the file before I posted this, and only have a 1.2MB file then please DONT FLASH IT. It shouldn't mess anything up permanantly but your device won't boot.
I've uploaded the file again (to the same location), please re-download and flash this one (it should be just over 6MB)
Please make it compatible for miui?;D.......
Sent from my ST18i using Tapatalk
Hi hartej glad to see you back on the forum
A have quick question, how can be repaired this problem: http://code.google.com/p/android/issues/detail?id=3708 DooMLord may be able to help you repair it? Or will show some tips
Sorry for double post...i had found a way to port to MIUI...take a look here hartej..)
bheremans said:
Rom by iriijo
To port kernel : nothing special, just compile it with :
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_2G is not set
and
CONFIG_PAGE_OFFSET=0xC0000000
Click to expand...
Click to collapse
Sent from my ST18i using Tapatalk
Hi Hartej, sorry but even with your second upload. The kernel doesn't boot. It stays at black screen (not even the SE logo)
@hartej: some notes ...
thinking its a good choise using DooMLoRD's kernel as your base, congratulations for your wise decision
some minutes befor i fastboot'ed (temporarly) your image (i.e. fastboot boot <image>)
# kernel cpufreq defaults is ondemand 245760/1862400Hz - no max 1GHz as you'r thinking?
some LITTLE change-requests from me - please
# /proc/config.gz support - a great help for every self-builder
# init.d support - importent i'm thinking, i modifyed init.semc.rc in initrd.img in your boot image for myself (serves only as a example)
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
user root
oneshot
# a git respository of your kernel for self builder
ok, thats all for NOW, thank you for your good work.
greetings
Doesn't boot
I've downloaded your present(RayDoomKernel-2011-12-18.img / 6.23MB) and flash it on my Ray with fastboot tool. But it doesn't boot, just shows me black screen.(Not even show me SE logo ) Anyway I appreciate your great effort.
is it for stock 4.0.2.0.A.42 firmware
Oh I tried.Doesn't boot with the 4.0.2.A.042 FW.
@hartej
glad to see u back on this
some devices cant handle 1.6Ghz+
thats why i keep 2 kernels
2.0Ghz
and
1.6Ghz
for other things u can check my kernel-ramdisk
SWDJPA said:
I've downloaded your present(RayDoomKernel-2011-12-18.img / 6.23MB) and flash it on my Ray with fastboot tool. But it doesn't boot, just shows me black screen.(Not even show me SE logo ) Anyway I appreciate your great effort.
Click to expand...
Click to collapse
masray said:
Oh I tried.Doesn't boot with the 4.0.2.A.042 FW.
Click to expand...
Click to collapse
Lol, I'll upload the right one eventually! Just tried downloading and flashing this myself, only to discover that I'd mistakenly uploaded the latest version instead of the working one. Still playing with getting the ARC ramdisk working with the Ray, possibly because of the speed issue DooMLoRD quotes above which is the reason for the black screen - the Kernel itself is identical, it's just a difference in the RamDisks.
I've uploaded the working one now - sorry for any confusion!
http://dl.dropbox.com/u/17615284/DoomKernel-2011-12-18-1547.img
hartej said:
Lol, ... I've uploaded the working one now - sorry for any confusion!
http://dl.dropbox.com/u/17615284/DoomKernel-2011-12-18-1547.img
Click to expand...
Click to collapse
i'll testet it shortly, now it boot in ondemand 245760/1024000Hz und init.d support works too - super
one questions leaves ...
i want to compile myself. where to get your changes for the ray (.config mainly ???), when i use DooMLoRD's cloned git sources ???
thanks and have i nice day ...
hartej said:
Lol, I'll upload the right one eventually! Just tried downloading and flashing this myself, only to discover that I'd mistakenly uploaded the latest version instead of the working one. Still playing with getting the ARC ramdisk working with the Ray, possibly because of the speed issue DooMLoRD quotes above which is the reason for the black screen - the Kernel itself is identical, it's just a difference in the RamDisks.
I've uploaded the working one now - sorry for any confusion!
http://dl.dropbox.com/u/17615284/DoomKernel-2011-12-18-1547.img
Click to expand...
Click to collapse
Please for MIUI ??
Works Great
Two thumbs up!
It is quite stable even at 2ghz.
But I would stay at 1.5 with smartass v2 considering battery life.
Thank you
-Ray User from Korea.
doesn't work with FXP050 on my Ray ... It does boot into the system but it doesn't show any submenus or option menus ... they are there, i can select by where i remember them to be but it is not graphicly shown
This Kernel is for STOCK Rom !!!! not for cyanogen mod.
v2 Released. Scroll down for info!
Hello,
After lots of help from sirkay and FXP, I've built my own kernel that I thought I'd share with you.
This kernel wouldn't exist without the hard work of FXP. This is built from his source code. All real credit for this belongs with him (and DoomLord too, also an FXP Team member)
That said, this is my take and keeps the rather awesome release that is CM7.2 alive!
To be clear: This is a kernel for Cyanogen Mod 7.2 - Gingerbread! If you want a good ICS Kernel look at Sirkay's Thread.
So, what's different?
Uses a very recent GCC to compile, GCC version 4.6.3 which I optimised the build for Cortex-a8 and NEON.
Is compiled for performance not size (Optimize for size unticked)
Heap Randomisation is disabled.
Enabled SWAP - So you can use swap if you want to...
Default Scheduler changed to deadline, same as the Sony official kernel (still has bfq if you want to use it)
Default governor changed to ondemand.
CONFIG_OABI_COMPAT turned off. (This might break apps, haven't found any yet though)
Disabled CPUFreq Debugging.
Disabled FRAME_POINTERS, enabled STACK_UNWIND. Reason here: http://lists.openmoko.org/nabble.html#nabble-td6126708
There is no boot logo when this kernel boots. Each time I added one, the kernel refused to boot. I'll look at that. Just have patience, your phone is booting still...
(Here's where I make lots of stupid claims about how smooth, how buttery, how much battery life this kernel saves. Except I'm not a screaming idiot, so I'm not going to do that!)
I'm interested in any feedback you have, but I did this mostly for me.
And please remember the real person to thank, FXP. It's his source code I've used to build this. Also again thanks to Sirkay for his help and pointers.
Download it from here.
- muppet
Nice Kernel what's battery performance ??
aditya080908 said:
Nice Kernel what's battery performance ??
Click to expand...
Click to collapse
About the same as every other kernel.
OTG support? ?!
Sent from my ST18i
so good, This is what I looking for
@muppetmania attach here you png file. i can try to convert it to .rle for you
Could GB MIUI have the privilege?
Could we have a CM7 based MIUI 2.3.7 kernel?
I think GB MIUI works just fine and don't want to upgrade to ICS or JB.
But a better kernel for GB MIUI is always appreciated.
Thanks in advance,pls let us know if you'd be willing to.
Anoopnk said:
OTG support? ?!
Click to expand...
Click to collapse
If you'd like me to respond to questions, please post an actual articulate question in the first place. Cheers.
Yes, I'm aware I'm a ****, it's been pointed out to me already
sirkay said:
@muppetmania attach here you png file. i can try to convert it to .rle for you
Click to expand...
Click to collapse
Thanks sirkay, but the problem isn't that I can't make a rle file, it's that the rle file when added to the ramdisk stops the kernel booting. It seems to a bug in the SEMC loader, I found a post about it somewhere. Does the boot.img need to be padded out to a certain size to work?
Sometimes my logo.rle would work, but then I'd make changes, recompile, and the kernel would hang on boot. Annoying, so I've removed it for the moment.
rivtre said:
Could we have a CM7 based MIUI 2.3.7 kernel?
I think GB MIUI works just fine and don't want to upgrade to ICS or JB.
But a better kernel for GB MIUI is always appreciated.
Thanks in advance,pls let us know if you'd be willing to.
Click to expand...
Click to collapse
Hi rivtre,
I'd love to help, but my Ray is the only phone I have and is running CM7.2. While I could make a kernel for MIUI I'd have no (easy) way to test it. It wouldn't be fair to anyone if I started releasing untested things. So I'm sorry, it's not that I don't want to help, but no. Anyway, read the next bit to see why that's probably not a bad thing!
To All:
My kernel seems to be terrible when it comes to HD video recording. Can anyone else test this? I get heaps of dropped frames using my kernel when recording HD video vs a FXP Stock kernel. I need to look more at this, but for the moment I'd recommend not using this kernel!
v2 Released!
Version 2 of muppet kernel released.
What's new?
Compiled with GCC 4.7.1
Reverted to BFQ Scheduler by default
Reverted to Interactive CPU Scaling by default
Added logo.rle so you know it's booting!
Removed Debugging Symbols (CONFIG_KALLSYMS)
Reverted the scheduler and CPU scaling as they seemed to be the cause of the video recording lag.
Enjoy!
Download
does the kernel also work with this rom http://forum.xda-developers.com/showthread.php?t=1424121?
can I flqsh the kernel with flashtool?
is overclocking possible?
borg17a said:
does the kernel also work with this rom http://forum.xda-developers.com/showthread.php?t=1424121?
can I flqsh the kernel with flashtool?
is overclocking possible?
Click to expand...
Click to collapse
Not sure if it works with the stock ROM or not - try it and report back.
Yes, like all kernel images, you can flash it with Flashtool.
You can OC up to 1.6Ghz.
I tried it, but It doesn't work. Booting failed
muppetmania said:
Not sure if it works with the stock ROM or not - try it and report back.
Yes, like all kernel images, you can flash it with Flashtool.
You can OC up to 1.6Ghz.
Click to expand...
Click to collapse
borg17a said:
I tried it, but It doesn't work. Booting failed
Click to expand...
Click to collapse
Oh well sorry. It's only for CM7.2
muppetmania said:
Version 2 of muppet kernel released.
What's new?
Compiled with GCC 4.7.1
Reverted to BFQ Scheduler by default
Reverted to Interactive CPU Scaling by default
Added logo.rle so you know it's booting!
Removed Debugging Symbols (CONFIG_KALLSYMS)
Reverted the scheduler and CPU scaling as they seemed to be the cause of the video recording lag.
Enjoy!
Download
Click to expand...
Click to collapse
Just flashed your kernel, going to give a test run! thanks!!
Edit:
Well it doesn't seem to me that the camera recording works at all ... pictures = fine - but when trying to record video - the image freezes - and the camera app crashes.
I have to reboot to get back into the camera app...
Also, can't play any video I previously recorded...
Anything I'm missing?
I've flashed your kernel and did a cache + dalvik wipe...
Cheers!
Apocalyps2 said:
Just flashed your kernel, going to give a test run! thanks!!
Edit:
Well it doesn't seem to me that the camera recording works at all ... pictures = fine - but when trying to record video - the image freezes - and the camera app crashes.
I have to reboot to get back into the camera app...
Also, can't play any video I previously recorded...
Anything I'm missing?
I've flashed your kernel and did a cache + dalvik wipe...
Cheers!
Click to expand...
Click to collapse
Oh, well that's not the sort of feedback I wanted!
I haven't done much video recording the last couple of weeks (I've been away from work)
Let me do some testing and see what I can find...
Thanks for reporting
If you want a logcat I'll make one and get it to you , cheers
Sent from my ST18i using xda app-developers app
GPS
i just install your kernel on my phone...but why my GPS cannot running well
a1nx said:
i just install your kernel on my phone...but why my GPS cannot running well
Click to expand...
Click to collapse
why your bug reporting so terrible
a1nx said:
i just install your kernel on my phone...but why my GPS cannot running well
Click to expand...
Click to collapse
Update baseband to 75 or 77 ...reflash kernel !!!
Have fun !!
Sent from my ST18i
Hello! This is my first thread, ever, on any forum so please don't bash me if I forget something .
I've decide to make a kernel for the SGP 5.0 for Gingerbread because I loved Entropy512's, but I was slightly jelous of the INTL users and all their new givernors and I/O schedulers. Soooo i used Entropy512's sources and borrowed rumirand's schedulers and governors and tossed in a 1.4 GHz OC and a few cherry picks from KOala888 and voila!
Current features:
O3 optimization
battery pooling - 60sec (KOala888)
touchscreen responsivness tweaked (KOala888)
Screen UV (KOala888)
2.6.35.7 source for GingerBread.
Unsecure mode.
Swap support.
Overclock to 1.4Ghz and undervolt capabilities (use SetCPU or another software for UV).
Added lazy (default), interactive, interactiveX, smartassv2, ondemandX governors.
Added BFQ, V(R) and SIO (default) schedulers.
Init.d support.
Added statically linked busybox 1.19.3 (/sbin)*.
Modified adbd (pointing shell to /sbin/sh), so you can use adbd even if you don't have any partition working.
ext4 support (ghetto lagfix).
ClockWorkMod. Nandroid backup - restore works, mount/umount, format (formats to ext4).
CIFS support.
jhash3.
SoD patch from netarchy/coolbho3k.
TinyRCU.
netarchy's conservative tuning patch.
Custom bootanimation support (/system/media/bootanimation.zip) from Entropy512's kernel.
Per-File fsync() disable
Charginghacks from Entropy512.
I may release a 1.2 GHz version if the community finds 1.4 too unstable.
If there is anything i forgot please tell me!
Download USA
Download INTL
Almost forgot my sources: https://github.com/augiem94/linux_kernel_galaxyplayer
Feature requests are welcome!
Credits:
Entropy512-his sources and his handy build script! Saved me a TON of hassle
rumirand-for his sources
KOala888-for his tweaks
koxudaxi-for his OC settings
I've got Entropy's kernel on my player, and I keep having random freezes. For instance, I'll be typing or scrolling and thing go completely unresponsive for a second or two. I'm not sure if it's a governor thing or what (I've turned off overclocking to see if that helped, but it doesn't seem to have made any difference).
Do I just have a bad install of Entropy's, or is this something everyone has? Would flashing this kernel likely to fix those issues? Can I flash without re-installing my ROM (Gingerbread Based)? Are there any issues I should know about before applying this kernel?
Dr. Cyanide said:
I've got Entropy's kernel on my player, and I keep having random freezes. For instance, I'll be typing or scrolling and thing go completely unresponsive for a second or two. I'm not sure if it's a governor thing or what (I've turned off overclocking to see if that helped, but it doesn't seem to have made any difference).
Do I just have a bad install of Entropy's, or is this something everyone has? Would flashing this kernel likely to fix those issues? Can I flash without re-installing my ROM (Gingerbread Based)? Are there any issues I should know about before applying this kernel?
Click to expand...
Click to collapse
I had the same problem, i could never diagnose the source, but so far i havent had it once with the 1.4GHz OC. if you do get that problem tell me and ill look into it further .
EDIT: Problem still exists, if anyone has an idea what it is please tell me. I believe Mevordel had a theory a while back it was due to facebook being a rogue app and causing it. Feedback on this theory will be greatly appreciated!
EDIT2: Facebook does not appear to be the culprit.
augiem94 said:
I had the same problem, i could never diagnose the source, but so far i havent had it once with the 1.4GHz OC. if you do get that problem tell me and ill look into it further .
Click to expand...
Click to collapse
Well, I've flashed it now. Here's to hoping it's smooth sailing from here on out
I ran this kernel almost all day yesterday. Visually, things in the UI don't look much faster (probably because of the lack of GB hardware acceleration, and Project Butter), but a few 3D games run noticeably better. Those random pauses that occur, especially when typing on a keyboard, have seemed to also disappear. Thanks for making Gingerbread a bit better to use for those of us that can't let it go completely just yet!
I likewise ran all day, and didn't see any issues. I'm optimistic they're gone now. I never install Facebook, to further disprove that theory.
General question lol is it possible to compile gingerbread kernels with a Linaro toolchain?
Sent From My USA Galaxy Player 5.0
augiem94 said:
General question lol is it possible to compile gingerbread kernels with a Linaro toolchain?
Sent From My USA Galaxy Player 5.0
Click to expand...
Click to collapse
Of course But you may get compile errors when building with Linaro, in which case you will need to solve them. There are also a few other things to worry about with Linaro, else you may solve the errors and get the kernel to compile and it won't boot.
Thank you! I am a going to load this right now. Thanks for including smartassV2 in governors. The main reason I used INTL r14 over Entropy.
Edit: 8:50 pm.
Cannot load over clock module from Tegrak. When I try to load the module and change the OC to 1.152 (which I find most stable on my player) the player will reboot. 1.2 and 1.4 seem to be the only option for OC. Been running at 1.2 for now with no issues. 1.4 seemed to run too hot.
YP-G70 USA
R.E.D.D ROM
Rumirand r14 INTL Kernel on YP-G70 USA device
I Like Turtles.
1.152 OC
:fingers-crossed:
HOG1csmith said:
Thank you! I am a going to load this right now. Thanks for including smartassV2 in governors. The main reason I used INTL r14 over Entropy.
Edit: 8:50 pm.
Cannot load over clock module from Tegrak. When I try to load the module and change the OC to 1.152 (which I find most stable on my player) the player will reboot. 1.2 and 1.4 seem to be the only option for OC. Been running at 1.2 for now with no issues. 1.4 seemed to run too hot.
YP-G70 USA
R.E.D.D ROM
Rumirand r14 INTL Kernel on YP-G70 USA device
I Like Turtles.
1.152 OC
Click to expand...
Click to collapse
Same problem here with Tegrak, I'll try to get it sorted out in the next release.
EDIT: I got the module to load i think, but the device reboots directly after. It reboots after the Load Module button greys though so I'm fairly sure its loading
EDIT2: It loads if i set the max frequency to 1.2GHz from No Frills, but if i change it back to 1.4 after its loaded it reboots. Getting there .
it can't get "too" hot from technical side
Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
augiem94 said:
:fingers-crossed:
Same problem here with Tegrak, I'll try to get it sorted out in the next release.
Click to expand...
Click to collapse
You probably can't load the tegrak module because the vermagic is different
android1234567 said:
You probably can't load the tegrak module because the vermagic is different
Click to expand...
Click to collapse
Im really new to the dev scene, mind explaining?
Sent From My USA Galaxy Player 5.0
augiem94 said:
Im really new to the dev scene, mind explaining?
Sent From My USA Galaxy Player 5.0
Click to expand...
Click to collapse
The tegrak module and the kernel have version names in them and the module will only load when the version inside said module matches the version of the kernel. Basically, they need to have the same name. There's some nice info on this here: http://www.tldp.org/LDP/lkmpg/2.6/html/x380.html
android1234567 said:
The tegrak module and the kernel have version names in them and the module will only load when the version inside said module matches the version of the kernel. Basically, they need to have the same name. There's some nice info on this here: http://www.tldp.org/LDP/lkmpg/2.6/html/x380.html
Click to expand...
Click to collapse
Forgive me if im being numb, but i havent changed the version in the makefile at all.
Sent From My USA Galaxy Player 5.0
After using it for a few days now,it seems that scrolling still sometimes locks up. I haven't noticed any issues with typing yet, but that could be not using it at the right time.
Sent from my YP-G70 using xda app-developers app
I've been using this on 1.2 GHz for over a week and it is great.
No persistent issues.
Thanks for the kernel!
I appreciate your work.
YP-G70 USA
R.E.D.D ROM
AC Kernel
augiem94 said:
Forgive me if im being numb, but i havent changed the version in the makefile at all.
Sent From My USA Galaxy Player 5.0
Click to expand...
Click to collapse
It's not the version of the version but the localversion (normally it is 2.6.35.7-XXXXX) The X represents the local version. You can modify the module to actually make it work with the kernel or in your case modify the localversion specified in the defconfig.
Thank you so much for this Kernel!!!! I am loving the 1.4 Ghz. Smooth sailing so far. Once again thanks!
Alright guys, the time has come
As you already might have seen around here, I recently got this device and also started working on it.
Deep down in my heart I am more of a kernel dev than a ROM dev, which is why my first real contribution just had to be a kernel.
And not just any kernel, a wild one even: It's time to unleash the Werewolf in our tablet
As usual, my main goal is to get the best performance out of the device, especially for gaming.
I have been working with Tegra SoC's before, so I can probably make use of my previous experiences.
Now, enough with the chit-chat, time to look at the
Features
Patched CONFIG_KEYS vulnerability
CPU OC (up to 2.5GHz, default is stock 2.2GHz)
GPU OC (924MHz)
Custom I/O Schedulers (SIO, FIOPS, BFQ, CFQ, Deadline) with FIOPS as default
Ported ElementalX governor
[WIP] Added S2w and DT2W (experimental, not fully working --> use on your own risk!)
Added exFAT support
Added fsync toggle
KSM turned on by default with deferred timer
Added /dev/frandom support
Various TCP tweaks (enabled westwood as default TCP congestion control)
Requirements
MM bootloader and any MM ROM (should work on all ROMs running the MM kernel natively like CM13 or Bliss)
TWRP or any other custom recovery
fastboot environment
Installation
Download both the devicetree blob and the kernel zip
Boot into the bootloader and flash the DTB (fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb)
Boot into TWRP and install the zip
Reboot and feel the Werewolf's power
Bugs
S2W and DT2W not working when device is in deep sleep and touch may stop working when it was sleeping for too long
Direct download links
Werewolf_v001_anykernel-2016-01-25_1912.zip.zip
tegra124-tn8-p1761-1270-a04-e-battery.dtb
Feel free to look at this as a sneak-peek, I am far from done with getting the best out of this device
Please let me know what you think
XDA:DevDB Information
Werewolf Kernel, Kernel for the Nvidia Shield Tablet
Contributors
laufersteppenwolf
Source Code: https://github.com/laufersteppenwolf/android_kernel_nvidia_shieldtablet
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v001
Stable Release Date: 2016-01-25
Created 2016-01-25
Last Updated 2016-01-26
Testing, I'll let you know... Thnx!
Any reason why we can't just flash a zip version ? Just wont be at a computer anytime soon thats why
This is MM stock Nvidia K1 base
Is there a way to disable S2w and DT2W? I use the magnetic cover and don't need to double tap to wake.
KCKitsune said:
Is there a way to disable S2w and DT2W? I use the magnetic cover and don't need to double tap to wake.
Click to expand...
Click to collapse
Maybe you can use Kernel Adiutor to disable such options.
MrPhilo said:
Any reason why we can't just flash a zip version ? Just wont be at a computer anytime soon thats why
Click to expand...
Click to collapse
I had to raise the EDP limit as well as the freq table in the dtb in order to reach the oc freqs. You can try it without flashing the dtb, but I can't promise it'll work the way it should
KCKitsune said:
Is there a way to disable S2w and DT2W? I use the magnetic cover and don't need to double tap to wake.
Click to expand...
Click to collapse
Both features are disabled by default. If you want to try it out you'll have to enable it first
laufersteppenwolf said:
Both features are disabled by default. If you want to try it out you'll have to enable it first
Click to expand...
Click to collapse
Excellent. I'll give it a go and see how it works.
Is the battery a Lot weaker with this kernel and oc or is it the same?
Bit lost dev earlier the dtb flashed via fastboot no problems but i had to do a factory reset cause a was getting fcs but now its not working command write failed no such device or adress any ideas cheers
---------- Post added at 04:32 PM ---------- Previous post was at 04:31 PM ----------
skooter32 said:
Bit lost dev earlier the dtb flashed via fastboot no problems but i had to do a factory reset cause a was getting fcs but now its not working command write failed no such device or adress any ideas cheers
Click to expand...
Click to collapse
Edit using bliss rom mm
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
skooter32 said:
Bit lost dev earlier the dtb flashed via fastboot no problems but i had to do a factory reset cause a was getting fcs but now its not working command write failed no such device or adress any ideas cheers
---------- Post added at 04:32 PM ---------- Previous post was at 04:31 PM ----------
Edit using bliss rom mm
Click to expand...
Click to collapse
Edit done it now strange
I wish we had an dolphin version working on MM to try the werewolf
It works! But
So i installed it no problem cpu overclocks to 2.5GHz.
Kernel same page merging is fine .
Elemental x is great.
The the double tap to wake is buggy like it works once then stops working until i disable it then renable it.
My biggest problem is the same i have with EVERY SHIELD TABLET KERNEL YOU KERNEL DEVOLPERS CLAIM IS....... The gpu freq
You say its at 924 but the highest it goes in benchmarks and other apps is 540 and i cant overclock in kerner tuners like
Kernel auidtor
Device control
Kernel tuner
Etc....
All of them say no gpu tweaks.
I will like to point out i am running your kernel on the OG shield tablet not the new model but the old one running a version of android 6.0 that was converted from the new model shield to work on the og shield tablet stock rom so i thought ok lets try blisspop 6.0 and still nothing if you could be one of the first kernel modders to ACTUALLY get the the gpu to overclock and not give up or go quiet like the other kernel modders for this tablet then i swear the community for this tablet will make a satue of you because no one can seem to overclock this thing because they all give up but thanks anyways finally a 6.0 stock kernel that lets me overclock to 2.5ghz and secretly IVE ALAWYS wanted double tap to wake on this thing so if you could fix that as well id be super excited to donate
laufersteppenwolf said:
I had to raise the EDP limit as well as the freq table in the dtb in order to reach the oc freqs. You can try it without flashing the dtb, but I can't promise it'll work the way it should
Both features are disabled by default. If you want to try it out you'll have to enable it first
Click to expand...
Click to collapse
It's weird, because after testing I decided about no raising voltage in BitO-KX series (safety and eco criteria) and it seemed to be stable at max OC, but now I get RR at max freq with your kernel if I don't flash dtb, so I suspect Nvidia had readjusted something in MM kernel... Have you faced this?
Thnx for your great work.
Hi, first I'd like to say thank you for this kernel, I'm super stoked to try it. But I have some questions/fears to resolve first.
If I don't want to overclock do I still need to flash the dtb?
Is there a stock dtb that could be uploaded in case someone wants to revert to stock? Or would I be able to accomplish this simply by restoring a twrp backup?
Anyway, thanks again
Sent from my SHIELD Tablet K1 using Tapatalk
Working fast & smooth on Bliss v6.0. Thanks, laufersteppenwolf!
Nikownzyu said:
So i installed it no problem cpu overclocks to 2.5GHz.
Kernel same page merging is fine .
Elemental x is great.
The the double tap to wake is buggy like it works once then stops working until i disable it then renable it.
My biggest problem is the same i have with EVERY SHIELD TABLET KERNEL YOU KERNEL DEVOLPERS CLAIM IS....... The gpu freq
You say its at 924 but the highest it goes in benchmarks and other apps is 540 and i cant overclock in kerner tuners like
Kernel auidtor
Device control
Kernel tuner
Etc....
All of them say no gpu tweaks.
I will like to point out i am running your kernel on the OG shield tablet not the new model but the old one running a version of android 6.0 that was converted from the new model shield to work on the og shield tablet stock rom so i thought ok lets try blisspop 6.0 and still nothing if you could be one of the first kernel modders to ACTUALLY get the the gpu to overclock and not give up or go quiet like the other kernel modders for this tablet then i swear the community for this tablet will make a satue of you because no one can seem to overclock this thing because they all give up but thanks anyways finally a 6.0 stock kernel that lets me overclock to 2.5ghz and secretly IVE ALAWYS wanted double tap to wake on this thing so if you could fix that as well id be super excited to donate
Click to expand...
Click to collapse
First of all, how do you check the freq during the benchmarks?
I've been running antutu, and the GPU was properly using 924MHz (otherwise I wouldn't have said so)
Furthermore, you don't need to manually OC the GPU, it is OC'd by default simply because of the fact that no kernel tweaking app supported K1 GPUs up until now.
In the future the recommended app will be Device Control because that's what I am using myself. In the coming builds of DC, K1 GPU tweaks will be available there as I have added support for our GPU to Device Control: https://github.com/Evisceration/DeviceControl/commit/b2d4872869d1eda517c47588b83b6f3f895aaa01
DT2W and S2W are still on my list of course, and I'm sure the original shield will also be able to OC the GPU
BitOBSessiOn said:
It's weird, because after testing I decided about no raising voltage in BitO-KX series (safety and eco criteria) and it seemed to be stable at max OC, but now I get RR at max freq with your kernel if I don't flash dtb, so I suspect Nvidia had readjusted something in MM kernel... Have you faced this?
Thnx for your great work.
Click to expand...
Click to collapse
Hmm, no random reboots for me. I do have the dtb flashed, though. When do those reboots happen? During sleep, while playing,...?
Comparing the LP kernel to the MM kernel, quite a lot more stuff has moved into the dtb (like throttling, edp and power limits,...), which makes flashing the dtb even more important. Not sure, though, if they have also changed something regarding the actual voltage levels (except making it harder to add a proper UV interface).
Exile1975 said:
Hi, first I'd like to say thank you for this kernel, I'm super stoked to try it. But I have some questions/fears to resolve first.
If I don't want to overclock do I still need to flash the dtb?
Is there a stock dtb that could be uploaded in case someone wants to revert to stock? Or would I be able to accomplish this simply by restoring a twrp backup?
Anyway, thanks again
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Yes, flashing the dtb is always recommended.
No, TWRP does not make a backup of the dtb partition, I think I have a backup somewhere, though. I could upload it if needed
Ok so i check the freq in file manager system log you find more details about the benchmark like 3dmarks slingshot and whatnot so ok
I feel like an idiot could the reason be because i disnt flash the dtb? Because i forgot?
By the way i use AIDA64 and go to display the gpu goes from like 52 to 924 and i noticed while not using your kernel the maximum is like 824 witch is weird i could have SWORN on 5.0 stock kernel the maximum was 924 anyways it says it can go up to 924 but it stays at 524 i even run the device in max performance and run the benchmark and the app in MM's new multitask feature side by side and it stays at 524 while doing the most demading benchmark ever the 3dmark slingshot one also i benchmarked both using your kernel and not using your kernel and actually scored 80 points lower using yours (witch my highest is like 2480) but im sure this was because i didnt know kernel samepage merging was left on by default by the way is not good for benvhmarks obviously but good for games. But i will say the higher cpu overclock got me more fps in the CPU stress section of 3dmarks slingshot test (by the way all these tests are done on the 1440p one) basically what im getting at here is my device isnt overclocking but maybe thats because i didnt flash the dtb but i didnt think that mattered i will check back later after flashing it and seeing if my reaults are fortunate.
****EDIT**** so after flashing the dtb everything is still the same :/ what do you think im doing wrong is there any way i can send a system log or something i really want GPU overclocking
laufersteppenwolf said:
First of all, how do you check the freq during the benchmarks?
I've been running antutu, and the GPU was properly using 924MHz (otherwise I wouldn't have said so)
Furthermore, you don't need to manually OC the GPU, it is OC'd by default simply because of the fact that no kernel tweaking app supported K1 GPUs up until now.
In the future the recommended app will be Device Control because that's what I am using myself. In the coming builds of DC, K1 GPU tweaks will be available there as I have added support for our GPU to Device Control: https://github.com/Evisceration/DeviceControl/commit/b2d4872869d1eda517c47588b83b6f3f895aaa01
DT2W and S2W are still on my list of course, and I'm sure the original shield will also be able to OC the GPU
Hmm, no random reboots for me. I do have the dtb flashed, though. When do those reboots happen? During sleep, while playing,...?
Comparing the LP kernel to the MM kernel, quite a lot more stuff has moved into the dtb (like throttling, edp and power limits,...), which makes flashing the dtb even more important. Not sure, though, if they have also changed something regarding the actual voltage levels (except making it harder to add a proper UV interface).
Yes, flashing the dtb is always recommended.
No, TWRP does not make a backup of the dtb partition, I think I have a backup somewhere, though. I could upload it if needed
Click to expand...
Click to collapse
I didnt flashed the DTB and all is running fine and smooth without any reboots or something else. So my questions is Do I have to Flash it? @BitOBSessiOn said in his kernel thread that it is not necessary on the New mm bootloader. Thanks for your work!
Nikownzyu said:
Ok so i check the freq in file manager system log you find more details about the benchmark like 3dmarks slingshot and whatnot so ok
I feel like an idiot could the reason be because i disnt flash the dtb? Because i forgot?
By the way i use AIDA64 and go to display the gpu goes from like 52 to 924 and i noticed while not using your kernel the maximum is like 824 witch is weird i could have SWORN on 5.0 stock kernel the maximum was 924 anyways it says it can go up to 924 but it stays at 524 i even run the device in max performance and run the benchmark and the app in MM's new multitask feature side by side and it stays at 524 while doing the most demading benchmark ever the 3dmark slingshot one also i benchmarked both using your kernel and not using your kernel and actually scored 80 points lower using yours (witch my highest is like 2480) but im sure this was because i didnt know kernel samepage merging was left on by default by the way is not good for benvhmarks obviously but good for games. But i will say the higher cpu overclock got me more fps in the CPU stress section of 3dmarks slingshot test (by the way all these tests are done on the 1440p one) basically what im getting at here is my device isnt overclocking but maybe thats because i didnt flash the dtb but i didnt think that mattered i will check back later after flashing it and seeing if my reaults are fortunate.
****EDIT**** so after flashing the dtb everything is still the same :/ what do you think im doing wrong is there any way i can send a system log or something i really want GPU overclocking
Click to expand...
Click to collapse
Alright, so I just did exactly what you described: installed AIDA64 and it really does show 540MHz as max current freq with only AIDA open. Then I went on running sling shot and reading the freq via adb a couple of times during the bench and the freq was hopping between 756 and 924MHz just like it should:
Code:
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
924000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
756000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
924000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
756000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
756000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
924000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
924000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
756000000
Please check via adb as well while running the benchmark and let me know your findings
philipp21897 said:
I didnt flashed the DTB and all is running fine and smooth without any reboots or something else. So my questions is Do I have to Flash it? @BitOBSessiOn said in his kernel thread that it is not necessary on the New mm bootloader. Thanks for your work!
Click to expand...
Click to collapse
Yes you definitely should, especially when using OC freqs. The throttle tables are now stored within the device tree as well, which means the stock ones won't fit the current clock rates which could cause trouble once the devices tries to throttle down.
The DTB is needed regardless of the bootloader, they just have to match one another (LP bootloader and LP DTB vs MM bootloader and MM DTB)
Ok so tell me this if you have the time or backups have you tested the bench with and with out the kernel and i did what you did and whatta you know its overclocking BUT WHAT THE **** so why are we not seeing a performance increase? Is Aida the only reliable gpu checker lol are we being lied to by the system? If so? I wonder where does aida check its gpu freq i feel like going on an app system file ADVENTURE TO FIGURE THAT OUT i dont know maybe im expecting too much for gpu overclocking.
Might i have some suggestions for kernel additions? Like a simple line of code to automatically put in androids new mm multi window feature its buggy but can help ALOT for some stuff
Maybe research a zip called nitrox
Iteli plug so i dont have to use shields custom performance settings set the device at 2 cores to save power THEN go to device control and tick my freq
Most of of BitO's K features
I mention all these as your still the only 6.0 kernel for this tablet and yea i know you just released this kernel and i still love it but just some ideas you know
And GPU overclocking is still a priority