Database Develop

CPU Temperature

I have setcpu installed on my Nexus One, along with the Zimage and lib files I need to overclock it. Can anyone tell me what an appropriate temperature range is for the Nexus, as would be shown in the SetCPU widget? I want to be sure I don't cause my Nexus to overheat.

Around 21-36 for me.. highest it ever got was 40.3 degrees.
crawler9 said:
I have setcpu installed on my Nexus One, along with the Zimage and lib files I need to overclock it. Can anyone tell me what an appropriate temperature range is for the Nexus, as would be shown in the SetCPU widget? I want to be sure I don't cause my Nexus to overheat.
Click to expand...
Click to collapse

rjhay22 said:
Around 21-36 for me.. highest it ever got was 40.3 degrees.
Click to expand...
Click to collapse
Is that in Celcius or Fahrenheit?

i would hope its in Celsius, or it would mean that the CPU is cold enough to freeze water

Alright thanks mines been on average about 99 degrees Fahrenheit

that's what I get when I'm charging my phone, so that's pretty high if that's what you have on standby.
crawler9 said:
Alright thanks mines been on average about 99 degrees Fahrenheit
Click to expand...
Click to collapse

Would it matter if I have a silicon case on it? And how high is dangerously high?

I have the same case, I wouldn't want it to go over 40C or bout 102 F. Thats pretty hot, I notice my phone gets sluggish and starts forceclosing too... What ROM are you running? And are you using OC-UV kernel? If not I suggest you get it.
crawler9 said:
Would it matter if I have a silicon case on it? And how high is dangerously high?
Click to expand...
Click to collapse

rjhay22 said:
I have the same case, I wouldn't want it to go over 40C or bout 102 F. Thats pretty hot, I notice my phone gets sluggish and starts forceclosing too... What ROM are you running? And are you using OC-UV kernel? If not I suggest you get it.
Click to expand...
Click to collapse
At the time I had SetCPU and was overclocked, I had Cyanogen's latest stable ROM (5.0.5.3?) installed. I was using the UV kernel. Last night I switched to Alpha r20 of MoDaCo's desire ROM for Nexus along with whatever kernel that comes packaged with.

You should be able to flash the OC-UV kernel by pershoot over Modacos desire ROM.
Battery life means more than OCing to me so here's my SetCPU profile settings if it helps.
Default setting: 998/245
Charging: 844/245
Standby: 245/245
Power<35%: 883/245
Failsafe batt > 40: 729/245
I should add that I'm charging right now, music player on, using my phone non stop and my batt temp is 95F.
crawler9 said:
At the time I had SetCPU and was overclocked, I had Cyanogen's latest stable ROM (5.0.5.3?) installed. I was using the UV kernel. Last night I switched to Alpha r20 of MoDaCo's desire ROM for Nexus along with whatever kernel that comes packaged with.
Click to expand...
Click to collapse

rjhay22 said:
You should be able to flash the OC-UV kernel by pershoot over Modacos desire ROM.
Battery life means more than OCing to me so here's my SetCPU profile settings if it helps.
Default setting: 998/245
Charging: 844/245
Standby: 245/245
Power<35%: 883/245
Failsafe batt > 40: 729/245
I should add that I'm charging right now, music player on, using my phone non stop and my batt temp is 95F.
Click to expand...
Click to collapse
Sounds like a good profile, and I think I'll try that myself and see where my temperature lies with those settings. Just curious... what are the advantages of using the OC-UV without overclocking?
Here's information on the kernel with the ROM I'm using, directly copied from the page with the ROMs.
What kernel are you using? Any other tweaks worth knowing about?
The ROM has the usual MCR tweaks (tun.ko, openvpn, busybox, dropbear etc.) and is running a custom kernel by teknologist and myself based on the stock .33 source (check the changelog below for more details). Himem is enabled. The kernel runs at standard clock speeds, uniquely only using undervolt at the lowest clock speeds.

Good question, I had an option to just undervolt it, there is a UV @stock speed kernel by Persianone too, but I opt to get the OC-UV just incase I need to show off how fast my N1 is. LOL. Better to have the option to use it when i need it.
crawler9 said:
Sounds like a good profile, and I think I'll try that myself and see where my temperature lies with those settings. Just curious... what are the advantages of using the OC-UV without overclocking?
Here's information on the kernel with the ROM I'm using, directly copied from the page with the ROMs.
What kernel are you using? Any other tweaks worth knowing about?
The ROM has the usual MCR tweaks (tun.ko, openvpn, busybox, dropbear etc.) and is running a custom kernel by teknologist and myself based on the stock .33 source (check the changelog below for more details). Himem is enabled. The kernel runs at standard clock speeds, uniquely only using undervolt at the lowest clock speeds.
Click to expand...
Click to collapse

rjhay22 said:
Good question, I had an option to just undervolt it, there is a UV @stock speed kernel by Persianone too, but I opt to get the OC-UV just incase I need to show off how fast my N1 is. LOL. Better to have the option to use it when i need it.
Click to expand...
Click to collapse
Alright thanks for all the help.

My pleasure
crawler9 said:
Alright thanks for all the help.
Click to expand...
Click to collapse

[Kernel] Dragon 3.6

Download link: http://goo.gl/vzEB4
FAQs: http://forum.xda-developers.com/showpost.php?p=11436660&postcount=11 (Thanks Alienz!)
Yes, the kernel is still based on the i9000 JPX source release. Hopefully we get real source soon.
Main Features:
NEAR STOCK BATTERY!!! (Thanks Morfic!)
Overclock up to 1.4Ghz.
BLN (Backlight Notifications).. A basic app is included to turn it on if you want it
Voodoo lagfix v5
Voodoo Sound v4
Many parts of the "speedmod" patch from the i9000 forum
OC is based on raspdep's OC patches, also from the i9000 forum
Various speed tweaks
CIFS/SMB and NFS support compiled in (no modules)
Tunnel support compiled in (no modules)
Changes since 3.2:
New boot logo. (Thanks Alexia!)
Added battery drain fix in standby discovered by Morfic. Should be about the same battery as stock now.
Voltages and frequency scaling have been adjusted to more quickly jump to higher frequencies and come down slower. Improves response time while you use the phone.
The Voltage Control app has the correct voltages, I recommend leaving the lower speeds alone to start with. Going too low can cause the sleep of death. That's why they are as high as they are. NOTE: The voltage control app does not control the available states they way the older ones do. That screen is useless, ignore it. Set your max and scheduler if you wish, and the voltages if you want to change them.
SetCPU.... If you want to use it, you can have it set min/max. If you set profiles, don't set the max under 800. The phone needs 800 to be available. I use a screen off profile at 100-800 just to keep the OC disabled while sleeping. No reason it should need to really crank up the speed if I'm not looking at it. SetCPU is NOT required, I'm offering this as a tip for fans of that application.
The kernel has proven stable for a number of testers so far. If you get crashes, disable any OC/UV settings and try again. I recommend you only change one setting at a time, and NOT set at boot until you have run for a while to ensure you can run stable at that voltage/speed.

Great job testing it out now. Edit: screen is a little dark but the kernel is super smooth
Sent from my SGH-T959 using XDA App

Going to test! Will post results in a couple of hours.

onix
I am considering flashing this new kernel but have a couple of questions I would like to ask first. I am currently on Bionix V 1.21 and love it. Is this kernel compatible with Bionix V 1.21? It appears that this kernel is Voodoo enabled so I presume I would not have to disable voodoo. If I decide to go back to the Kb1 with voodoo enabled which I believe is the stock kernel for Bionix V 1.21 would i just flash the kernel( is is available on TW forum?)or would I have to flash the whole rom again? I would think I would not have to but want to be sure before I leap. I would not like to have to ask for help for problems that could have been avoided by reading and asking questions. Any and all help is greatly appreciated.

Is it ok to not use set cpu? Will this kernel will oc over 1000?
ttabbal said:
Download link: http://goo.gl/vzEB4
Yes, the kernel is still based on the i9000 JPX source release. Hopefully we get real source soon.
Main Features:
Voodoo lagfix v5
Voodoo Sound v4
Many parts of the "speedmod" patch from the i9000 forum
OC is based on raspdep's OC patches, also from the i9000 forum
Various speed tweaks
CIFS/SMB and NFS support compiled in (no modules)
Tunnel support compiled in (no modules)
Changes since 3.2:
New boot logo. (Thanks Alexia!)
Added battery drain fix in standby discovered by Morfic. Should be about the same battery as stock now.
Voltages and frequency scaling have been adjusted to more quickly jump to higher frequencies and come down slower. Improves response time while you use the phone.
The Voltage Control app has the correct voltages, I recommend leaving the lower speeds alone to start with. Going too low can cause the sleep of death. That's why they are as high as they are. NOTE: The voltage control app does not control the available states they way the older ones do. That screen is useless, ignore it. Set your max and scheduler if you wish, and the voltages if you want to change them.
SetCPU.... If you want to use it, you can have it set min/max. If you set profiles, don't set the max under 800. The phone needs 800 to be available. I use a screen off profile at 100-800 just to keep the OC disabled while sleeping. No reason it should need to really crank up the speed if I'm not looking at it.
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

This kernel is much more stable for me than the dow kernel. Great work.

tenbeau said:
I am considering flashing this new kernel but have a couple of questions I would like to ask first. I am currently on Bionix V 1.21 and love it. Is this kernel compatible with Bionix V 1.21? It appears that this kernel is Voodoo enabled so I presume I would not have to disable voodoo. If I decide to go back to the Kb1 with voodoo enabled which I believe is the stock kernel for Bionix V 1.21 would i just flash the kernel( is is available on TW forum?)or would I have to flash the whole rom again? I would think I would not have to but want to be sure before I leap. I would not like to have to ask for help for problems that could have been avoided by reading and asking questions. Any and all help is greatly appreciated.
Click to expand...
Click to collapse
Im not sure if you have to disable voodoo or not .. probably not but don’t take my word for it and no you do not have to flash the whole rom again, just the kernel. Thanks for not clogging up the forums. Lol I know its hard to ask questions in the vibrant forums, (cause you'll get beaten to death with mean comments) but ask them anyway, someone will answer eventually. Ignore the whiny, ungrateful 2 year olds that somehow wandered onto this forum...
Sent from Bionix powered vibrant! If I helped, hit the thanks button!

I flashed without disabling voodoo
treyvaporizer said:
Im not sure if you have to disable voodoo or not .. probably not but don’t take my word for it and no you do not have to flash the whole rom again, just the kernel. Thanks for not clogging up the forums. Lol I know its hard to ask questions in the vibrant forums, (cause you'll get beaten to death with mean comments) but ask them anyway, someone will answer eventually. Ignore the whiny, ungrateful 2 year olds that somehow wandered onto this forum...
Sent from Bionix powered vibrant! If I helped, hit the thanks button!
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

tenbeau said:
I am considering flashing this new kernel but have a couple of questions I would like to ask first. I am currently on Bionix V 1.21 and love it. Is this kernel compatible with Bionix V 1.21? It appears that this kernel is Voodoo enabled so I presume I would not have to disable voodoo. If I decide to go back to the Kb1 with voodoo enabled which I believe is the stock kernel for Bionix V 1.21 would i just flash the kernel( is is available on TW forum?)or would I have to flash the whole rom again? I would think I would not have to but want to be sure before I leap. I would not like to have to ask for help for problems that could have been avoided by reading and asking questions. Any and all help is greatly appreciated.
Click to expand...
Click to collapse
It is compatible with Bionix 1.2.1, that's what I developed it on.
If you have the red voodoo recovery, there is no need to disable voodoo for flashing. Generally speaking, kernels can be flashed without disabling voodoo in any case.

This is what iv'e done, I've lowered my Volts on some clocks, 1000 and up, and I was wondering should/can I use setcpu for profiles?

Answers to COMMON questions:
1. Can I flash this over Voodoo or RFS (stock)
You do NOT need to disable Voodoo. Flash right over Voodoo or RFS kernels. Make sure you are not running JFS though. JFS is not supported
2. How is stability? Does it crash? Sleep of death? etc?
Stability on this is AMAZING. It will not crash unless you overclock/undervolt and your settings are unstable. If that is the case, you know its your settings.
3. Do I need SetCPU to overclock?
You do not need to use SetCPU (You can if you want to). Use the Voltage Control App to overclock.
4. How do I overclock? Can I use this without an overclock?
By default, the kernel will boot to 1.0Ghz. To OVERCLOCk to 1.4Ghz (or lower) you need to use the app that this kernel installs during the flash. The app is called "Voltage Controll" and can be found in your app drawer after the flash
5. What is the battery life?
Battery life should be close to stock now. The battery drain issue that was present in the I9000-based kernels earlier has been solved.
6. Does this support BLN (Back-light-notificaations)?
Yes. You need the BLN control app from the market to use it.
7. How do I use Voodoo sound? What is it?
Voodoo sound is a vast improvement to the sound quality of your phone. To use it, download the Voodoo Control app from the Market.
8. What ROMs is this compatible with?
This is compatible with ALL Vibrant Froyo ROMS. This means 2.2 ROMS made for the Vibrant. 2.2.1 is not yet tested but should theoretically work.
I hope this helps.

ttabbal said:
It is compatible with Bionix 1.2.1, that's what I developed it on.
If you have the red voodoo recovery, there is no need to disable voodoo for flashing. Generally speaking, kernels can be flashed without disabling voodoo in any case.
Click to expand...
Click to collapse
Thanks so much for your kind and patient and swift reply. Donation just made. I really admire yours and all of TW generosity and patience with noobs like me. I am flashing the kernel now. Thanks again for sharing your brilliant work!!!!!!!!!!!!!!!

cashyftw said:
This is what iv'e done, I've lowered my Volts on some clocks, 1000 and up, and I was wondering should/can I use setcpu for profiles?
Click to expand...
Click to collapse
You can use setcpu for profiles, just keep 800Mhz available. The phone will likely crash if you don't. I set a screen off profile of 100-800 to keep the oc disabled when I don't need it, as 800 is a lower voltage.
Hint with voltages, try to keep 1000 and higher at the SAME voltage. Changing the voltage too often can cause instability as the voltage regulator doesn't adjust as fast as we would like sometimes. OC makes this worse as you need a higher voltage to maintain a stable CPU at the higher frequency. The kernel is set to jump to 1000, then to the max set clock speed. Setting 1000 to the higher voltage gives us some extra time to stabilize the new voltage before the just into the OC speeds.

tenbeau said:
Thanks so much for your kind and patient and swift reply. Donation just made. I really admire yours and all of TW generosity and patience with noobs like me. I am flashing the kernel now. Thanks again for sharing your brilliant work!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Thanks for your kind words and the donation. I'm glad you find my work useful.

just flashed this..
and a few questions ive never used OC before..
What does VOODOO Sound really do?
I set my thing on SetCPU as 1.4ghz as max and .1 as low with conservative.
then a profile with screen off and on conservative.
will those save battery?

xriderx66 said:
just flashed this..
and a few questions ive never used OC before..
What does VOODOO Sound really do?
I set my thing on SetCPU as 1.4ghz as max and .1 as low with conservative.
then a profile with screen off and on conservative.
will those save battery?
Click to expand...
Click to collapse
SetCPU by itself will NOT overclock. You need to use the Voltage app that comes with the kernel. See my above post with the Common questions.

I'd like any of the kernels developers gave me a clue about an issue im having with all custom i9000 based kernels (eugene's and TW's). The problem is with line2 voip app which calls isn't heard in the other end when running these kernels, but in stock/voodoo it works just fine. Please any of you have an idea of what could be going wrong?
thanks.

Okay tested so far, everything is working good (undervolted to about 175 for lower clocks 100-1000 and 75 for higher clocked 1200-1400)
Don't try this, as every phone can't handle some things, i'm just stating.
EDIT: I'm seriously stupid, how do I remove the settings again? I know it's in system/ something
Edit: NEVERMIND fixed

I've never used an OC kernel, was thinking of giving it a try. If I decide its not for me is this like removing a voodoo injected kernel, disable, then flash a diff kernel then delete files?

kcp877 said:
I've never used an OC kernel, was thinking of giving it a try. If I decide its not for me is this like removing a voodoo injected kernel, disable, then flash a diff kernel then delete files?
Click to expand...
Click to collapse
Just flash other voodoo kernel on top of it no need.to.disable voodoo
Sent from my SGH-T959 using Tapatalk

[Kernel] RieGo Kernel 0.7 (3.1 only)

Hi guys, finally i want to release my kernel.
This kernel is based on pershoots latest source. So it's mostly his work
-Contains Lazy governor by Ezekeel
-Contains SLQB slab allocator
Changelog:
Code:
[SIZE="1"]coming next:
[/SIZE]
0.7:
-use SLQB slab allocator
[SIZE="1"]0.6:
-no more GPU OC for now (doesn't work)
-additional modules
-a few minor performance tweaks
-more "lazy" tweaking
0.5:
-tweaked "lazy" a bit and set as default
-optional gpu overclocking (experimental)
0.4:
-started from scratch
-added lazy governor
-NO gpu overclocking until i can get it working
-should work with all devices now (please feel free to test :))
0.3:
-ondemand is default
-GT-P7510 with TW should work
0.2:
-removed SmartassV2 - freezed max frequency sometimes
-added Lazy governor by [URL="http://forum.xda-developers.com/showthread.php?t=1276092"]Ezekeel[/URL] and set as default
-20% 3D GPU overclock (experimental, may freeze, but works fine so far)
0.1:
-ARM: tegra: speed up framebuffer copy
-added SmartassV2 governor (set with SetCpu) [B]*testing*[/B]
-13% GPU overclock
0.0:
-100% pershoots Kernel[/SIZE]
Download: (Only 3.1!)
(Flash with CWM)
No GPU OC:
GT-P7500
GT-P7500 Touchwiz
GT-P7510 (WiFi-only)
GT-P7510 (WiFi-only) Touchwiz
Modules Archive

Welcome, we need all the devs and cooks we can get in here. Would you consider supporting the GT-P7500 also? We are starving!

nickwarn said:
Welcome, we need all the devs and cooks we can get in here. Would you consider supporting the GT-P7500 also? We are starving!
Click to expand...
Click to collapse
I'll try my best to support the GT-P7500 in the future

Downloading and trying now. Thank you
---------- Post added at 03:00 PM ---------- Previous post was at 02:49 PM ----------
The 7500 version is messed up. It boots but the rainbow colours that sometime can show themselves at bootup acctually show themselves when its booted. Its impossible to see anything, the whole screen is covered by these coloured lines. But the tab is booted, it responds to screen timeout and when i press power button the screen goes black and it turns on when i press it. so it boots but something is messed up with graphics. Please check and i try the update for you.

nickwarn said:
Downloading and trying now. Thank you
---------- Post added at 03:00 PM ---------- Previous post was at 02:49 PM ----------
The 7500 version is messed up. It boots but the rainbow colours that sometime can show themselves at bootup acctually show themselves when its booted. Its impossible to see anything, the whole screen is covered by these coloured lines. But the tab is booted, it responds to screen timeout and when i press power button the screen goes black and it turns on when i press it. so it boots but something is messed up with graphics. Please check and i try the update for you.
Click to expand...
Click to collapse
Thanks for trying. I'm not sure what the problem is. I'll take the links down.
Reflashing an other (working) kernel should solve the problem for you.
It's weird because the graphics part should be the same for all. I really have no idea where the problem is.
I don't think it's because of overclocking
... enough kernel developing for today.

Sorry for asking, but did you use the right base for 7500 version? Its easy to mix up stuff. maybe it was built on 7510 base or non TW base. anyway good try

nickwarn said:
Sorry for asking, but did you use the right base for 7500 version? Its easy to mix up stuff. maybe it was built on 7510 base or non TW base. anyway good try
Click to expand...
Click to collapse
I think so. I'll look into it later

im gonna sound like an idiot...but whats the difference between this and pershoot's? does pershoot's have any gpu overclock?

K Rich said:
im gonna sound like an idiot...but whats the difference between this and pershoot's? does pershoot's have any gpu overclock?
Click to expand...
Click to collapse
right now the difference is:
-ARM: tegra: speed up framebuffer copy
-added Lazy governor by Ezekeel and set as default
-20% 3D GPU overclock (experimental, may freeze, but works fine so far)
(more to come )
and no, pershoot doesn't have gpu overclock.

sweet, im always up for new mods/tweaks!
ill be giving this a try as soon as i get home from work

Does overclocking the GPU improve video playback?

CazeW said:
Does overclocking the GPU improve video playback?
Click to expand...
Click to collapse
I don't think so. only the 3D rendering part is overclocked. but you may give it a try, maybe I'm wrong

I'll wait till somebody tries the wifi only/touchwiz version

Thanks for giving the gpu overclocking a go so quickly.
Wifi touchwiz does not work... Yet. It gives the same static.
BTW, anyone know a good graphics benchmark for honeycomb? Neocore doesn't work.

non-touchwiz seems to be working so far...gonna keep testing.

Ive been playing Order&Chaos on the tab and would love me some GPU oc.
I'm on TW tho, but tempted to flash non just to try it out. Either way, much appreciated. -

so far so good, everything seems to be running well.

Kernel working well. Flashed over tasks and phantoms stock hc, n my tab is awesome smooth and fast. Best its ever been. Thank you for your work.
Oh and my lag has reduced quite alot, dont know if its just me or something has changed.
Btw im overclocked to 1.4 interactive.
Sent from my GT-P7510 using xda premium

AngeredNumber said:
Kernel working well. Flashed over tasks and phantoms stock hc, n my tab is awesome smooth and fast. Best its ever been. Thank you for your work.
Oh and my lag has reduced quite alot, dont know if its just me or something has changed.
Btw im overclocked to 1.4 interactive.
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
1.4 interactive for me as well, nice and smooth!!
Sent from my GT-P7510 using Tapatalk

I'm on a TW rom now. I'll try to get it working the next days.
AngeredNumber said:
Kernel working well. Flashed over tasks and phantoms stock hc, n my tab is awesome smooth and fast. Best its ever been. Thank you for your work.
Oh and my lag has reduced quite alot, dont know if its just me or something has changed.
Btw im overclocked to 1.4 interactive.
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Nice! There's still some oc possible. Xoom users have 30% overclock. but that's too dangerous for me right now
You should have seen how fast it is with smartass governor. (I'll try to get that working asap)

[Kernel][CM10][26/08] CMOC10-Kernel [New! MaxOC version]

Hello people,
This is a CM10 overclocked kernel, based on Metallice's CM9 version. Thanks for jumpstarting me, mate! :laugh:
It's features:
Overclockable to 1.38GHz, 1.52GHz for MaxOC
Underclockable to 150MHz, both
GPU overclocked to 384MHz, 512MHz for MaxOC
L3 overclocked to 224MHz for MaxOC
Wheatley governor (by Ezekeel)
Pegasusq governor
NTFS Read-only support
SIO scheduler (by Ezekeel)
SLQB memory allocator (by Ezekeel)
Optimized CRC32 & ARM RWSEM algorithms
LowMemoryKiller backported from 3.4 kernel
and several other fixes and optimizations
Click to expand...
Click to collapse
***Read Me***
DO NOT, UNDER ANY CIRCUMSTANCE, USE SETCPU PROFILES OF ANY KIND OR ANYTHING SIMILAR WITH THIS DEVICE. Things like screen off max frequency, temperature throttling, and others are already built in to the OMAP architecture. Using ANY profiles will ONLY lead to problems, instabilities, and battery drain.
***************
***Changelog***
26-08:
Included cifs module in zip. Re-enabled touchboost for smoother response. NTFS support (read-only)
NEW! MaxOC version. CPU @ 1.52, GPU @ 512, L3 @ 224 & significant overvolt @ max speed.
***************
Download links:
Regular version: http://goo.im/devs/Johnsel/kernels/CMOC10-Kernel_P31xx-20120826.zip
Use at own risk!! These values are HIGH!
MaxOC version: http://goo.im/devs/Johnsel/kernels/CMOC10-Kernel_P31xx-20120826-MaxOC.zip
Source:
https://github.com/Johnsel/android_kernel_samsung_espresso10/tree/jellybean

Installing right now. Thank you

Awesome! Thanks man. Will give it a good run.
Edit: won't boot. Gets stuck at the Samsung logo. Will try to post logs.
3113

scottx . said:
Awesome! Thanks man. Will give it a good run.
Edit: won't boot. Gets stuck at the Samsung logo. Will try to post logs.
3113
Click to expand...
Click to collapse
for me too (P3100)
Tried to reinstall, but after some minutes on Samsung logo my P3100 has rebooted, but still on sam logo (

P3110, flashed zip via CWM, same problem here, no-boot: stuck at Samsung logo.
How do we acquire logs to post, by the way?
Thanks though, Johnsel! Nice to see we're on our way to a swish new kernel for CM10

New build uploaded. Hope it works now.

boots but wifi not working on my P3100
Edit: tried also with a full wipe but nothing, Wifi doesn't work

jym1975 said:
boots but wifi not working on my P3100
Click to expand...
Click to collapse
Agreed - boots now (hurrah!) but no Wifi, it will not turn on. P3110 here

And updated again.

Wifi still broken.

Now it should work. Please don't hit me for f'ing up that many times in a row :]

Yeah, WiFi now working
Sent from my GT-P3100 using xda app-developers app

Zoom Zoom on my p3113! Thank you!

Johnsel said:
Now it should work. Please don't hit me for f'ing up that many times in a row :]
Click to expand...
Click to collapse
Glad to see you got it all up and running. Good work! I'm always open to PMs if you have any more questions or whatnot.
Also be careful with live OC. It doesn't just overclock CPU/gpu/bus. It overclocks EVERYTHING. A lot of which don't like being overclocked. I would disable it for things like the DSP or other miscellaneous frequencies if you want it to go higher and be more effective. The source should be pretty straightforward on how to disable it for those elements. At least that's how it was the last time I looked. Maybe its different now.
Sent from my Nexus 7 using xda premium

I confirm, so far it's fine.
Try @1200 and 1380. Thx for the work.
Sent from my GT-P3110 using xda app-developers app

Metallice said:
Glad to see you got it all up and running. Good work! I'm always open to PMs if you have any more questions or whatnot.
Also be careful with live OC. It doesn't just overclock CPU/gpu/bus. It overclocks EVERYTHING. A lot of which don't like being overclocked. I would disable it for things like the DSP or other miscellaneous frequencies if you want it to go higher and be more effective. The source should be pretty straightforward on how to disable it for those elements. At least that's how it was the last time I looked. Maybe its different now.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'll respond in a PM on your post to not clutter the topic. Aside from that, again thanks for the help, couldn't have done this without it :highfive:

Good work. Now I don't mind using 10 as a DD.
Just need tablet mode @ 145dpi now.

Touch screen , became unresponsive, after sitting there, over 3 hours ,,anyone have had this happen?, (OC setting was at default )
Sent from my GT-P3100 using xda app-developers app

Just tested latest version. Works pretty well.
Today I played with LiveOC:
CoreOC: setting 101 or any number -> instant crash.
GPU: works well.
As Metallice said, it just overclocks everything, so this behavior is expected.
I just want to ask you if you can add 2 features?
1. Pegasusq governor. I'm using it on my I9100 (Siyah kernel for S2) and it's really good in performance/battery.
2. Can you take a look at the sound enhancement (voodoo sound based) found in Siyah kernel for S3. The tab uses the same audio DAC WM1811, so it wouldn't be difficult.
Regards,
RJ

I had voodoo sound on my infuse and it was nice and clean. Would really like it here.

[Kernel]NN-J-Kernel-LP-T710/810-5.1.1-3/10/16

This is the BOJ1 version of NN-kernel. It's going to go in a little different direction than the previous kernel. And I'm not very good with Git. So may I present to you.....
NN-J-Kernel​
This will work on the T710 and 810 Wifi only models. I built this for my BNN Nook, but it works with other 710's and 810's.
You flash this at your own risk. There's the discaimer. :silly:​
Install instructions:
You MUST HAVE ROOT and TWRP installed to flash this!!
It's built on Lollipop 5.1.1 - I have no idea what will happen if you flash this on anything else!!
REMOVE SYNAPSE "set on boot" BEFORE INSTALLING!!!
Flash kernel then wipe cache and dalvic
Reboot and profit!!
Changelog
V1.3
GPU Control
UV now possible as well as select frequency
Samsung has the Max listed as 600Mhz. I'm pretty sure its 700 as thats what I've been using this at. Just an FYI
V1.2
Charge Control for battery - It's the best I can do for a "Faster Charge". Be careful. This can shorten the life of your battery. Or worse, ruin it if you change from default. You have been warned.
Maybe some other minor stuff
Also see/read this post
_______________
V1.1
Hotplug Big cores - They are the only ones that can be
OC/UC Big and Little - 2.1Ghz-500Mhz, 1.6Ghz-200Mhz
UV all CPU's
650Mhz step added to GPU
FIOPS Scheduler
Booting freq to 1.4Ghz
Lots of Optimizations
Gentle Fair Sleepers
Synapse stuff added
HMP controls - Big little cores
Memory controls
_______________
V1
OJ1 source
Synapse tuner - it's the only one that seems to work. Finally, after much effort.
Selinux Permissive
KNOX removed
Init.d support
Enabled OTG
Updated Frandom
Govs enabled- Powersave, Conservative, Ondemand - removed Userspace
Some optimizations
_____________________________
This is a Tablet, so I won't be adding things like I would for a phone.
Use "Synapse" from the Playstore for your Kernel tuner
______________________________
Downloads:
NNJ-Kernel-V1.3-710
NNJ-Kernel-V1.3-810
NNJ-Kernel-V1.2-710
NNJ-Kernel-V1.2-810
NNJ-Kernel-V1.1-710
NNJ-Kernel-V1.1-810
NNJ-Kernel-V1-710
NNJ-Kernel-V1-810
Thanks to:
ashyx
BigBot96
UpInTheAir
djmax81
And other peoples gits I can't remember
XDA:DevDB Information
NN-J-Kernel-LP-T710/810, Kernel for the Samsung Galaxy Tab S2
Contributors
engine95
Source Code: https://github.com/engine95/Exynos5433-BOJ1-gts28-210wifi.git
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2016-02-24
Created 2016-02-24
Last Updated 2016-02-24

And yes, Schedulers are fixed in this.

Flashed, running perfectly so far....
Thank you for your work.
Gesendet von meinem SM-T810 mit Tapatalk

I flashed this kernel (oj1-based) and the NN kernel (oh7-based) and let antutu benchmark the performance of both kernels (both default settings). This kernel wins outstanding!

Is this the "newer" one yes ?

Awesome! Thanks, it's nice to see some development on thus tablet. Otherwise there is nothing to flash
Sent from my LG-D855 using Tapatalk

halloarno said:
I flashed this kernel (oj1-based) and the NN kernel (oh7-based) and let antutu benchmark the performance of both kernels (both default settings). This kernel wins outstanding!
Click to expand...
Click to collapse
I did the same and the OJ Kernel is slower for me. Did 2 tests. 69-70k in old Kernel while i getting 62-65 with OJ1. Any idea ? How much do you get?

I tried setting max core to 2.x ghz but its not working, is it fixed to 1.9 ghz=no oc enabled so far?
Very strange, worked before i think. Just have Synapse installed and also wiped caches after flashing.
Any idea?

IngoPan said:
I tried setting max core to 2.x ghz but its not working, is it fixed to 1.9 ghz=no oc enabled so far?
Very strange, worked before i think. Just have Synapse installed and also wiped caches after flashing.
Any idea?
Click to expand...
Click to collapse
This kernel has no OC function, at least until now.

Actually, right now, it has no OC or extras. This is just the start. It's in the changelog.
Antutu scores, for me are 66-67000.
OC/UC and UV will be coming shortly. It's done. I just can't find out why Big 1500 ghz and Little 1300ghz are favored. Messed with a lot of stuff to no avail. Yet

V1.1 is up!!
SEE/READ changelog as there is a ton of stuff in it now. Both Kernel and Synapse. Yea for Hotplug!!!
Google "HMP" so you can understand it better. Big/Little core control. Little cores are ALWAYS online.

Think I found a way to get us a Fast Charge. Gotta finish and test it. So far it's looking good.

engine95 said:
Think I found a way to get us a Fast Charge. Gotta finish and test it. So far it's looking good.
Click to expand...
Click to collapse
Incredible. Fast charge on our tab s2? I hope so?

Great job! Thanks! Flashed and works perfectly, new synapse settings seems cool. UC seems to work fine.
Shiuldnwebuse the DVFS app as mentioned in synapse?
Sent from my SM-T810 using Tapatalk

whynottoday said:
Incredible. Fast charge on our tab s2? I hope so
Click to expand...
Click to collapse
Gugus38 said:
Great job! Thanks! Flashed and works perfectly, new synapse settings seems cool. UC seems to work fine.
Shiuldnwebuse the DVFS app as mentioned in synapse?
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Thanks. I have no idea if that app helps as I'm new to Samsung. If you try it, make a backup first.
Everything works fine without it though.
Can you say Fast Charge?!!!!!
I had to port Hotplug and Fast charge, but I think we're good to go. I still need to put finishing touches and build for both 710/810. But it should be out tomorrow IF my Tab doesn't meltdown while charging tonight. :silly:
Edit: Also, remember that as with everything computer, Fast Charge will be limited by Thermals. Just like CPU/GPU.

engine95 said:
Thanks. I have no idea if that app helps as I'm new to Samsung. If you try it, make a backup first.
Everything works fine without it though.
Can you say Fast Charge?!!!!!
I had to port Hotplug and Fast charge, but I think we're good to go. I still need to put finishing touches and build for both 710/810. But it should be out tomorrow IF my Tab doesn't meltdown while charging tonight. :silly:
Edit: Also, remember that as with everything computer, Fast Charge will be limited by Thermals. Just like CPU/GPU.
Click to expand...
Click to collapse
It wont really be fast charge as our tab doesn't support it

Reuben_skelz92 said:
It wont really be fast charge as our tab doesn't support it
Click to expand...
Click to collapse
Interesting. Guess we'll find out. I have been able to vary the voltages while charging. Up and down. But as I said, thermals will probably limit it.
Edit. Let's call it "Charge Control" then.

engine95 said:
Interesting. Guess we'll find out. I have been able to vary the voltages while charging. Up and down. But as I said, thermals will probably limit it.
Edit. Let's call it "Charge Control" then.
Click to expand...
Click to collapse
Sorry me being an idiot. Will be cool to see our tabs charge a little.bit quicker

Thank you very much for the kernel!
Running 1.1 with
A57 cores at 1300/500 and UV 50mV
A53 cores at 1000/200 and UV 25mV
2 A57 cores online
FIOPS scheduler, 2048 readahead
Gentle Fair Sleepers enabled
It's running snappy! Will watch battery life
P. S.: Why doesn't Synapse have live monitoring where one can see which frequency each core has at the moment? Just like other kernel tuners?

hasenbein196601 said:
Thank you very much for the kernel!
Running 1.1 with
A57 cores at 1300/500 and UV 50mV
A53 cores at 1000/200 and UV 25mV
2 A57 cores online
FIOPS scheduler, 2048 readahead
Gentle Fair Sleepers enabled
It's running snappy! Will watch battery life
P. S.: Why doesn't Synapse have live monitoring where one can see which frequency each core has at the moment? Just like other kernel tuners?
Click to expand...
Click to collapse
They are there. On the core screen at the top. Just wiggle the screen and you'll see it change. Big cores don't move as much until there is demand for them.
V1.2 is in the OP! With "Charge Control" See/read changelog for warnings.
This was a big port, and everything seems to be working. Just watch your tab for temps just to be sure it can handle the voltages. We should be ok, as it's built in and not on it's own. Meaning that all of Samsungs limits are still there. So Thermals should hold it from melting down. My Tab has been plugged in all night and is just fine.
This has all kinds of cable configurations, so it should cover about everything out there. I only use AC and USB but left all the others in for all of you.
One more time, we should be OK using Charge Control, but BE WARNED that it may ruin your battery and shorten battery life span. You use this at your own risk.