Hi, if someone is willing to try this kernel I will appreciate !
I need more user input, I tested it only on Droid 4 but the user base is not so large as RAZR so I made a build for it.
the kernel is a clean 3.0.31 (almost) there are no additional stuff like those present on dtrail JBX kernel, no overclocking, and based on my tests I can say it's stable. Most of the my version of kernel where merged on dtrail's kernel.
you can see in the picture attached that the standby seems to be really good (on 1735mah)
you need to use safestrap 3.65 or overwrite the files directly in the rom image.
I repeat that I don't own a RAZR and I would appreciate your input.
Edit:
the sources are here:
https://github.com/lucize/android_kernel_motorola_omap4-common
07.04.2014 - improve hdmi detection, should work 1080p everywhere, hwc.c update is needed from your ROM maintainer
19.03.2014 - hdmi from kernel 3.4, my sony avr is now a good boy and outputs sound
18.03.2014 - fixed HDMI native cable and colors, 720p and sound over HDMI on my philips but 1080p over DVI, movies 1080p over HDMI, but no sound on my sony receiver without a monitor attached, please share your experience.
17.03.2014
WIP HDMI, on my philips monitor, hdmi - hdmi is not working, only hdmi - dvi, please test if this is working for you, the colors are reversed, hopefully i'll understand why, tested only on droid 4, please share your experience.
Regards
Thanks, umts_spider ? (XT910)
By.TRabZonLu™ said:
Thanks, umts_spider ? (XT910)
Click to expand...
Click to collapse
No screen time on battery using screen?
Maybe later I try. anyway thanks for sharing with us
( Hacı ekran süresi yok. Bence kötü gibi denemedim ama )
By.TRabZonLu™ said:
Thanks, umts_spider ? (XT910)
Click to expand...
Click to collapse
should work, I don't know if there are more stuff to be enable for UMTS except modifying the build.prop
droid 4 is made for cdma by default, but I use it on gsm
I don't know what is the average standby of the battery for razr, but for droid 4, only when the phone was in standby and not moved around would last about 20h, now I have 45% with 24h uptime and in the middle of the week.
Regards
anticor248 said:
No screen time on battery using screen?
Maybe later I try. anyway thanks for sharing with us
( Hacı ekran süresi yok. Bence kötü gibi denemedim ama )
Click to expand...
Click to collapse
for screen you can see this
http://forum.xda-developers.com/showpost.php?p=50423144&postcount=588
but the battery was ~50% when I flashed the last kernel
It's a bit laggy and battery drain is considerable. Tried it with Liquidsmooth kitkat 18/02 + PA gapps
Sent from my XT910 using XDA Premium 4 mobile app
halifage said:
It's a bit laggy and battery drain is considerable. Tried it with Liquidsmooth kitkat 18/02 + PA gapps
Sent from my XT910 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thank you for testing and input !
I would like to know if someone else is having bad experience whit this (regarding to standby and not heavy usage, because lacking 100 mhz support), over jbx kernel thread I see lot of positive things after drtail incorporating it to his work.
I don't know what to think if this kernel is good on general omap4 without more tweaks or only on droid 4?
trying to merge parts of 3.4 or greater should be considered ? or is waste of time as I achieved my goals with this (except hdmi).
thank you for your input !
Regards
lucize said:
I would like to know if someone else is having bad experience whit this (regarding to standby and not heavy usage, because lacking 100 mhz support), over jbx kernel thread I see lot of positive things after drtail incorporating it to his work.
I don't know what to think if this kernel is good on general omap4 without more tweaks or only on droid 4?
trying to merge parts of 3.4 or greater should be considered ? or is waste of time as I achieved my goals with this (except hdmi).
thank you for your input !
Regards
Click to expand...
Click to collapse
i will try this kernel sir, what governor and i/o scheduler available on this kernel sir? can instal on any rom? sorry for asking many question
lucize said:
I would like to know if someone else is having bad experience whit this (regarding to standby and not heavy usage, because lacking 100 mhz support), over jbx kernel thread I see lot of positive things after drtail incorporating it to his work.
I don't know what to think if this kernel is good on general omap4 without more tweaks or only on droid 4?
trying to merge parts of 3.4 or greater should be considered ? or is waste of time as I achieved my goals with this (except hdmi).
thank you for your input !
Regards
Click to expand...
Click to collapse
This kernel, JBX and also the Moto stock kernel are true hybrids. Means that there are many backports from higher kernel versions, like 3.4, 3.7, etc. In JBX are addituional backports from 3.8, 3.10, 3.11. In fact these kernels are very mixed Btw: Currenlty patching JBX to 3.0.72 --> 3.0.88.
dtrail1 said:
This kernel, JBX and also the Moto stock kernel are true hybrids. Means that there are many backports from higher kernel versions, like 3.4, 3.7, etc. In JBX are addituional backports from 3.8, 3.10, 3.11. In fact these kernels are very mixed Btw: Currenlty patching JBX to 3.0.72 --> 3.0.88.
Click to expand...
Click to collapse
Just... amazing. How are you all so overpowered/extremely talented?
Sent from the Ace's MB865 using Tapatalk
Aceofzeroz said:
Just... amazing. How are you all so overpowered/extremely talented?
Sent from the Ace's MB865 using Tapatalk
Click to expand...
Click to collapse
Well, that's about 2 years of constant learning C code and not giving it up.. :laugh: And kind of a iron will to make things work like imagined before.. LOL
But there's still a LOT of stuff to learn even for me! People like Hashcode seem to have a brain, bigger than a whole football field... :silly:
dtrail1 said:
Well, that's about 2 years of constant learning C code and not giving it up.. :laugh: And kind of a iron will to make things work like imagined before.. LOL
But there's still a LOT of stuff to learn even for me! People like Hashcode seem to have a brain, bigger than a whole football field... :silly:
Click to expand...
Click to collapse
LOOOOL, you have a point there! He makes mainframe computers look like toys. xD We all still have a lot to learn, but the little we contribute can mean the world to others, thank you.
Sent from the Ace's MB865 using Tapatalk
dtrail1 said:
This kernel, JBX and also the Moto stock kernel are true hybrids. Means that there are many backports from higher kernel versions, like 3.4, 3.7, etc. In JBX are addituional backports from 3.8, 3.10, 3.11. In fact these kernels are very mixed Btw: Currenlty patching JBX to 3.0.72 --> 3.0.88.
Click to expand...
Click to collapse
I first started with nexus 101 but hashcode told me to rebase it to omapzoom 31, anyway they are getting the code to mainline kernel after we and other omapzoom users test it's stability
the goal is to have a better kernel in CM by standard and I don't know if your approach would be accepted, that's why I try to remain on the "vanilla" version but I don't know if the approach is good because lack of user input from other omap4 platforms.
every razr user is using your kernel ?
as I see there is ducati binary for 3.4 kernel so trying something wouldn't hurt but I'm starting to be busy and it took me almost a month to make 31 as you see it
Regards
lucize said:
I first started with nexus 101 but hashcode told me to rebase it to omapzoom 31, anyway they are getting the code to mainline kernel after we and other omapzoom users test it's stability
the goal is to have a better kernel in CM by standard and I don't know if your approach would be accepted, that's why I try to remain on the "vanilla" version but I don't know if the approach is good because lack of user input from other omap4 platforms.
every razr user is using your kernel ?
as I see there is ducati binary for 3.4 kernel so trying something wouldn't hurt but I'm starting to be busy and it took me almost a month to make 31 as you see it
Regards
Click to expand...
Click to collapse
I tried this kernel and get a black screen after reboot sir. What iam doing this is wipe dalvik cache-cache-flash this kernel. I am on xt910 umts spyder. By the way thx for developing
aldiandrew said:
I tried this kernel and get a black screen after reboot sir. What iam doing this is wipe dalvik cache-cache-flash this kernel. I am on xt910 umts spyder. By the way thx for developing
Click to expand...
Click to collapse
are you using safestrap 3.65 ? if not the files shoul be overwriten in the rom zip
lucize said:
I first started with nexus 101 but hashcode told me to rebase it to omapzoom 31, anyway they are getting the code to mainline kernel after we and other omapzoom users test it's stability
the goal is to have a better kernel in CM by standard and I don't know if your approach would be accepted, that's why I try to remain on the "vanilla" version but I don't know if the approach is good because lack of user input from other omap4 platforms.
every razr user is using your kernel ?
as I see there is ducati binary for 3.4 kernel so trying something wouldn't hurt but I'm starting to be busy and it took me almost a month to make 31 as you see it
Regards
Click to expand...
Click to collapse
This ducati version doesn't work for us - unfortunately
Gesendet von meinem XT910 mit Tapatalk 4
Does this revamped kernel address kitkats bluetooth handsfree+assistant bootloops and restarts on all roms?
Crumplet said:
Does this revamped kernel address kitkats bluetooth handsfree+assistant bootloops and restarts on all roms?
Click to expand...
Click to collapse
could you elaborate so I can do tests ?
Regards
lucize said:
could you elaborate so I can do tests ?
Regards
Click to expand...
Click to collapse
I have spoken about this issues a few times in different thread since January of this year, however i will be more then willing to explain the details so that you can maybe reinvent the situation.Rom used "Cyanfox" with and without JBX, using a bluetooth headset along with any assistant program example "Dragon Mobile Assistant" app.Use it and the phone process goes into hearing what you say to the assistant, and that's when the problem occurs.The phone starts to freeze up and the lockups then reboots.If you attempt to do it again it will just repeat the same process every time.That is all i really know.I even tried to use different assistant programs and it would create the same problem.
Related
-initial release for 2.6.38, for Gingerbread.
-based off of AOSP's dima, android-msm-2.6.38-wip
-merged up to kernel.org's 2.6.38.8
-merged in coolbh3k's oc patch
-frequency range is from 245 to 1113; default bootup is 245-998.
-undervolt some frequencies (max mv is 1275)
-merged in zinx's GAN_ETH wifi calling module modifications
-merged in changes from: cyanogen's cm-kernel, pershoot's kernel-2635, and AOSP's common
-optimisations based off of .35 release from Nexus/DS.
-added/amended a few things to the config (-xtra (please see below and in github)).
-includes rogerpodacter's/loginwithnoname's enhanced battery driver/extensions.
-includes audio boost for in-call audio
http://droidbasement.com/db-blog
Will this work if I am not using cm 7?
Markdental said:
Will this work if I am not using cm 7?
Click to expand...
Click to collapse
i am unsure if all the bits will work (camera, etc.).
check it out, and see.
Running now on rc4. No issues found
Tried on OTA GRI40 and camera force close..
IIRC, a lot of these custom kernels will have an issue opening the camera the first time. I've had crashes and even phone reboots after first installing an UV/OC kernel.
Try opening the camera again. It usually works fine, and stably after that.
And lest I forget, thanks Pershoot!!
Ota does not have the needed camera frame/bits to deal with the current drivers being used.
Excellent, I'll try this out tonight.
Sweet we nexus one owners use the latest Linux kernel <3
Sent from my Nexus One using XDA App
Now on CM7 RC4 & your kernel & there seem to be no issues at all !!
Beaten to the punch! Damn real life!
drive2droad said:
Now on CM7 RC4 & your kernel & there seem to be no issues at all !!
Click to expand...
Click to collapse
Thanks your information
im on RC4, ill flash this Kernel now...
Thanks pershoot
This kernel seems to be the best combination for CM7 , Performance wise (I can't state for battery usage right now) .
drive2droad said:
This kernel seems to be the best combination for CM7 , Performance wise (I can't state for battery usage right now) .
Click to expand...
Click to collapse
battery is great (as it was on the mid-to-later .35 series), from what i can tell, so far. i only have wifi on tho (which uses less power), but it should be good, nonetheless.
make sure to calibrate using rogerpodacter's/loginwithnoname's app! (shameless plug ), to get the most out of your specific battery.
pershoot said:
battery is great (as it was on the mid-to-later .35 series), from what i can tell. i only have wifi on tho (which uses less power). but it should be good, nonetheless.
make sure to calibrate using rogerpodacter's/loginwithnoname's app! (shameless plug ), to get the most out of your specific battery.
Click to expand...
Click to collapse
where can i get this app ? any market links please ??
drive2droad said:
where can i get this app ? any market links please ??
Click to expand...
Click to collapse
battery calibrator in Market, by Jon Richards.
then follow this:
http://forum.xda-developers.com/showpost.php?p=9583271&postcount=340
.38? Pardon my french but holy ****!
pershoot said:
battery calibrator in Market, by Jon Richards.
then follow this:
http://forum.xda-developers.com/showpost.php?p=9583271&postcount=340
Click to expand...
Click to collapse
have added this to the droidbasement blog posting under instructions.
phewizzo said:
.38? Pardon my french but holy ****!
Click to expand...
Click to collapse
I know.... the numbers just keep climbing higher and higher....
Sent from my Nexus One
redstar3894 said:
I know.... the numbers just keep climbing higher and higher....
Sent from my Nexus One
Click to expand...
Click to collapse
Yes, its very impressive.
AOSP Kernels for HTC's 8x50, 7x30, and 8x60 Devices
Also available for the Motorola Xoom
Tiamat kernels are designed for use on all ROMs that are built from the AOSP source code. This includes ROMs built from MIUI, CyanogenMod, and others.
Tiamat receives no support for use with ROMs based on HTC's Sense - use at your own risk.
Click to expand...
Click to collapse
Tiamat Kernels
You can find full details about Tiamat Kernels at our website. The site is up and running and serves as a more centralized location to get updates, downloads, and changelogs for all Tiamat Kernels. There is no forum or Registration, it’s just a more convenient way to keep things organized as we work to add support for more devices.
Click to expand...
Click to collapse
Support
Join the Tiamat Kernel developers on IRC at irc.freenode.net, #tiamat. Support and questions are generally handled faster there than the forums. You can easily join via webchat here.
Click to expand...
Click to collapse
Special Thanks to:
toastcfh, slayher and the CyanogenMod team for the base kernels and everything else they do for the Android community
bcnice20 for generally being awesome
TeamWin for also generally being awesome
netarchy, chad0989, cuviper, and invisiblek for some great code
intersectRaven and redstar3894 for the Mjolnir compiler
JasonK75 for updating threads
Click to expand...
Click to collapse
Quick Links
Click to expand...
Click to collapse
8x50 Changelog
8x60 Changelog
7x30 Changelog
Downloads
FAQ
Source Code
reserved for later
This kernel has been around for the Inc and the Evo. Now I'm bringing it to the N1 and the Desire!!
Great stuff, always nice to have more kernel choices
MOD : Can you post only Nexus One kernel on your post please (more readable)
Had been having some wifi issues this past week using cm7 nightly along with various kernels. Wifi was frequently dropping or just very slow. Spent most of Sunday screwing with my home network which seems stable now. I think comcast must have been doing something. however, my phone wifi was still poor. installed this kernel last night and so far phone is performing as it should on wifi. the difference was immediate. not sure whats going on. cant comment on battery life yet, but it's looking very good through this mornings use. Thank you!
allofusjw said:
Had been having some wifi issues this past week using cm7 nightly along with various kernels. Wifi was frequently dropping or just very slow. Spent most of Sunday screwing with my home network which seems stable now. I think comcast must have been doing something. however, my phone wifi was still poor. installed this kernel last night and so far phone is performing as it should on wifi. the difference was immediate. not sure whats going on. cant comment on battery life yet, but it's looking very good through this mornings use. Thank you!
Click to expand...
Click to collapse
I'm glad it's working for you, but that is strange... The only change I make to wifi from CM is undervolting it. And now that I think about it, I may have forgotten to bring that tweak over to the n1 and desire...
Can you summarize how your kernel differs from the others (CM, pershoot, wildmonks, redstar).
mr_raider said:
Can you summarize how your kernel differs from the others (CM, pershoot, wildmonks, redstar).
Click to expand...
Click to collapse
Versus the main CM kernel, this has unrestricted overclocking, HAVS, smartass, undervotling, sysfs interface and several other tweaks/improvements. I don't have a N1 and honestly dont know anything about the other kernels out there for it. The kernel started on the Inc and Evo, mostly around MIUI, and I was asked by a few people to bring it over to the N1 and Desire, so I figured I would post it up for everyone.
Hi all,
Been running this since 0800 this morning (its now 1800) no problems at all.
Can't say its faster or better on the battery for sure but its certainly no worse than CM stock.
Whats the smartass govenor? Just the same as on demand as it seems to replace it?
Oh, just one thing, although it has the option (in SetCPU) to go down to 128mhz, I've not seen it go lower than 245mhz which makes me wonder if its clocking down to 128 with the screen off.
Anyone else?
bryanchapman9999 said:
Hi all,
Been running this since 0800 this morning (its now 1800) no problems at all.
Can't say its faster or better on the battery for sure but its certainly no worse than CM stock.
Whats the smartass govenor? Just the same as on demand as it seems to replace it?
Oh, just one thing, although it has the option (in SetCPU) to go down to 128mhz, I've not seen it go lower than 245mhz which makes me wonder if its clocking down to 128 with the screen off.
Anyone else?
Click to expand...
Click to collapse
The on demand governor was removed to force the default to smartass (the default is usually set to on demand by the ramdisk and is not affected by setting the default in the kenrel), but the two are not similar. Smartass was built off the interactive governor.
As for the 128Mhz floor - that is something finicky about the smartass governor. It should drop to 128 on any other governor though.
Smartass Governor shows real potential...thanks for this!
what about the wonk?
From what I gather the wonk is due to something in CM7 kernel. I also noticed that it is absent from stock 2.3.3 and also absent from AOSP builds.
Has anyone tried CM7 with this kernel?
thanks for the N1 kernel.
I'll try ASAP.
I will try this kernel now, thanks for posting. New kernel cooks are always welcomed.
After about 18 hrs on this kernel, the results are pleasing.
Extremely stable on the Smartass Governor, which is surprising because I've had friends compile me kernels incorporating this governor, and the end result = unusable.
Battery life seems fantastic so far.
Clocked 128-998. No profiles.
Thank you again for this kernel.
Results on N1
I have been running this kernel for 24hrs at 128/1228 and it's been running great with smartass selected on my AT&T N1. I tried going even higher than 1228 but that causes it to crash immediately (I'm surprised it can even handle 1228.) Linpack is a little low at 23 compared to other kernels that can get up to 40. Quadrant also comes up behind at only 1051.
tried going at the highest setting & it crashed my N1 , BACK TO RESDTAR'S kernel .
Been using the kernel for a few hours, Kernel seems stable but definatly doesnt feel snappy.
phewizzo said:
Been using the kernel for a few hours, Kernel seems stable but definatly doesnt feel snappy.
Click to expand...
Click to collapse
same here, got some freeze
btw oc at 1267 without any crash
Just got a brand new Razr Maxx on the cheap! So excited to have freedom from my charger! Made the switch from galaxy nexus just because of the battery life. Anyways, I have rooted the device and installed safestrap 3.0, and I want to install CM10 but I don't know the difference between Kexec and Stock type builds. Can someone please explain the differences for me? From what I've read I think maybe kexec builds can run custom kernels? I did a bunch of searching but I'm clueless still. Although rombitch.com is down, I found a download page on goo.im for hashcode's cm10 builds here (http://goo.im/devs/Hashcode/spyder/cm10). Does hashcode upload the same builds as the ones on rombitch.com/spyder, or does anyone have a link for the latest version? Are there any drawbacks from going OEM stock to CM10? From older posts i found in my search battery life and signal issues were present but I'm curious what you all think currently. I am pretty happy with the stock motoblur ics and bloat apps removed surprisingly, but after just 1 day of use I'm already eager to try and get the purest android experience.
Thanks
Wes
wtfmate913 said:
Just got a brand new Razr Maxx on the cheap! So excited to have freedom from my charger! Made the switch from galaxy nexus just because of the battery life. Anyways, I have rooted the device and installed safestrap 3.0, and I want to install CM10 but I don't know the difference between Kexec and Stock type builds. Can someone please explain the differences for me? From what I've read I think maybe kexec builds can run custom kernels? I did a bunch of searching but I'm clueless still. Although rombitch.com is down, I found a download page on goo.im for hashcode's cm10 builds here (http://goo.im/devs/Hashcode/spyder/cm10). Does hashcode upload the same builds as the ones on rombitch.com/spyder, or does anyone have a link for the latest version? Are there any drawbacks from going OEM stock to CM10? From older posts i found in my search battery life and signal issues were present but I'm curious what you all think currently. I am pretty happy with the stock motoblur ics and bloat apps removed surprisingly, but after just 1 day of use I'm already eager to try and get the purest android experience.
Thanks
Wes
Click to expand...
Click to collapse
I don't know the differences other than stock is what is in the OTA ICS builds?
But I do know that what is on goo should be identical to what's on rombitch and rombot.
Sent from my CM10 XT912
Yes kexec can run custom kernels but the builds currently have some big issues, especially the lack of deep sleep so it kills your battery. Moving to cm10 you lose the ability of web top, HDMI, and screen rotation animation.
Full-Throttle Team
moderator at bdhroms.freeforums.org
prsterero said:
Yes kexec can run custom kernels but the builds currently have some big issues, especially the lack of deep sleep so it kills your battery. Moving to cm10 you lose the ability of web top, HDMI, and screen rotation animation.
Full-Throttle Team
moderator at bdhroms.freeforums.org
Click to expand...
Click to collapse
also I believe that camera is not working in kexec roms
thanks alot everyone. I got a stock-cm10 build up and running with safestrap v3 and it's running great.
wtfmate913 said:
thanks alot everyone. I got a stock-cm10 build up and running with safestrap v3 and it's running great.
Click to expand...
Click to collapse
Did u use Hashcode Rom? I run it in slot 1 and LOVE it. Never a problem. Camera works great!
Hmm I'm on a kexec rom (LiquidSmooth) and deep sleep is working great and the camera also works flawlessly.
Edit: I just realised that OP was created ages ago
Hello there. Yes I have hashcodes ROM installed but at the moment I'm running the new AOKP build that is newly posted. Hashcodes works great but for some reason I still get a problem with the ROM getting stuck at a black screen sometimes when I boot and I can't figure it out. Tried older safe strap version. Deleted ROM slot1 completely...fresh installs...fixed permissions....and I still get that problem.
Comparison
Camera on stock roms is better
also the stability is better on stock roms rarely any crashes
some stock roms give the ability to use some of the motorola goodies.
whereas with kexec u get
smoother UI and android 4.2.2
Innovative features like integrated pie controls and customization( try liquidsmooth)
and also the ability to overclock with the use of the JBX OCE kernel by dtrail1
<---hit thanks if i helped any of u! :laugh:
Gautam Padirooted said:
Camera on stock roms is better
also the stability is better on stock roms rarely any crashes
some stock roms give the ability to use some of the motorola goodies.
whereas with kexec u get
smoother UI and android 4.2.2
Innovative features like integrated pie controls and customization( try liquidsmooth)
and also the ability to overclock with the use of the JBX OCE kernel by dtrail1
<---hit thanks if i helped any of u! :laugh:
Click to expand...
Click to collapse
Kexec does not have FHD video recording, not even HD, only SD works for now. Well, you can use LG camera and it does work Full HD but it is not a standard app. Newer dtrail kernels are very stable, I have not had a reboot for over a week, just look @ some screenshots in his kernel thread. CM10.1 is very fast, very overclockable (1.5Ghz in my case) while vanilla rom (ICS or JB) are less overclockable (up to 1.35Ghz) and slower on top of that. They offer some futures not found in CM - webtop mode and working HDMI for example (not to forget about FHD recording).
Debloated vanilla rom would be a good compromise, especially with some custom launcher.
mat9v said:
Kexec does not have FHD video recording, not even HD, only SD works for now. Well, you can use LG camera and it does work Full HD but it is not a standard app. Newer dtrail kernels are very stable, I have not had a reboot for over a week, just look @ some screenshots in his kernel thread. CM10.1 is very fast, very overclockable (1.5Ghz in my case) while vanilla rom (ICS or JB) are less overclockable (up to 1.35Ghz) and slower on top of that. They offer some futures not found in CM - webtop mode and working HDMI for example (not to forget about FHD recording).
Debloated vanilla rom would be a good compromise, especially with some custom launcher.
Click to expand...
Click to collapse
What is this vanilla ROM of which you speak?
Sent from my XT912 using Tapatalk 2
garywojdan81 said:
What is this vanilla ROM of which you speak?
Sent from my XT912 using Tapatalk 2
Click to expand...
Click to collapse
Those are Motorola roms.
mat9v said:
Those are Motorola roms.
Click to expand...
Click to collapse
Thanks, never heard stock ROMs referred to that way.
Sent from my XT912 using Tapatalk 2
mat9v said:
Kexec does not have FHD video recording, not even HD, only SD works for now. Well, you can use LG camera and it does work Full HD but it is not a standard app. Newer dtrail kernels are very stable, I have not had a reboot for over a week, just look @ some screenshots in his kernel thread. CM10.1 is very fast, very overclockable (1.5Ghz in my case) while vanilla rom (ICS or JB) are less overclockable (up to 1.35Ghz) and slower on top of that. They offer some futures not found in CM - webtop mode and working HDMI for example (not to forget about FHD recording).
Debloated vanilla rom would be a good compromise, especially with some custom launcher.
Click to expand...
Click to collapse
All of this will be fixed, be patient, hashcode is working on it! And yes I do prefer Cm 10.1 over stock rom to be honest. I never had any issues with cm 10.1 RC2.
HDMI, webtop and 1080p recording is on his todo-list and I am confident that he will fix it.
I'm not worried or dissatisfied, was just answering a question really I'm using CM10.1 myself and really happy with it.
mat9v said:
I'm not worried or dissatisfied, was just answering a question really I'm using CM10.1 myself and really happy with it.
Click to expand...
Click to collapse
I know just answering some of question for members who have not tested cm 10.1 and are worried about the performance
wtfmate913 said:
Hello there. Yes I have hashcodes ROM installed but at the moment I'm running the new AOKP build that is newly posted. Hashcodes works great but for some reason I still get a problem with the ROM getting stuck at a black screen sometimes when I boot and I can't figure it out. Tried older safe strap version. Deleted ROM slot1 completely...fresh installs...fixed permissions....and I still get that problem.
Click to expand...
Click to collapse
same black screen problem here with AOKP on slot 2- BMM.
and there're same complains on same problem with cm and liquidsmooth
Development Goals:
- stability
- energy savings due to more efficient algorithms (whether theoretical or not is unimportant)
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
- all improvements should require MINIMAL user interaction (e.g. you don't need to do anything except flash the kernel or at the very least use SetCPU or the like to set fixed options)
- stability
Latest Kernel Here
20130625_10XX:
- updated with fix for more recent 4.1.2 Sense ROMs (should fix camera issue)
*unsure if this becomes incompatible with older 4.1.2 Sense ROMs though
20130602_07XX:
- NTFS support
- compiled using 4.8 linaro compiler
- improved workqueue queueing
- sleeper improvements
- responsiveness patches to the frequency controllers
20130531_09XX:
- fixed earpiece volume during calls
20130528_17XX:
- more optimizations (see GitHub)
20130527_18XX:
- more ARM implementations (see GitHub)
20130527_10XX:
- ARM implementations of kernel algorithms (see GitHub)
20130527_09XX:
- compiler optimization flags
20130526_22XX:
- initial version
- uses Linaro compiler
You can find my kernels at:
intersectRaven's Kernels
GitHub is at:
intersectRaven's GitHub
FAQ or something like that:
1.) Camera doesn't work!
- Try this fix from Golv here. This usually occurs on older ROMs.
*Latest 20130625_10XX version should solve this without flashing older camera libs.
Reserved 2
Reserved 3
Nice to see ir taking interest in the One. Truly a great dev
Sent from my Nexus 4 using Tapatalk 4 Beta
Uhhh nice to see you here
intersectRaven said:
Development Goals:
- stability
- energy savings due to more efficient algorithms (whether theoretical or not is unimportant)
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
Click to expand...
Click to collapse
Could you please expound on your statement that undervolting is relatively pointless?
From my experience, undervolting
1. Improves battery life because of lower wattage (Voltage * Amperage = Wattage). Even with a really bad binned CPU, it can still make a difference.
2. Cooler operation. This means longer component life - especially important as this phone is very difficult to repair. Battery is sandwiched so the cooler we can keep the device, the longer the battery will last. (Battery longevity practices could be a topic of it's own)
3. It's Fun! Haha. But seriously. I love to tinker. How low can you go??? It's fun seeing a 25% decrease in voltage and it still run stable
I really like your approach with the rest of your points though. We should have a stable kernel that doesn't have to be tuned or tweaked at all. This however, only suites the majority. The minority may want more. I'm currently in the process of making a kernel with as few restrictions as possible. Except that I will put a ceiling on the maximum voltage (1.25v for the cpu)) because I discourage overvolting beyond spec.
Anyway, thanks for the work. The One is Awesome!
m0nz said:
Could you please expound on your statement that undervolting is relatively pointless?
From my experience, undervolting
1. Improves battery life because of lower wattage (Voltage * Amperage = Wattage). Even with a really bad binned CPU, it can still make a difference.
2. Cooler operation. This means longer component life - especially important as this phone is very difficult to repair. Battery is sandwiched so the cooler we can keep the device, the longer the battery will last. (Battery longevity practices could be a topic of it's own)
3. It's Fun! Haha. But seriously. I love to tinker. How low can you go??? It's fun seeing a 25% decrease in voltage and it still run stable
I really like your approach with the rest of your points though. We should have a stable kernel that doesn't have to be tuned or tweaked at all. This however, only suites the majority. The minority may want more. I'm currently in the process of making a kernel with as few restrictions as possible. Except that I will put a ceiling on the maximum voltage (1.25v for the cpu)) because I discourage overvolting beyond spec.
Anyway, thanks for the work. The One is Awesome!
Click to expand...
Click to collapse
Should have put a qualifier there huh? Anyways, it's pointless from a no tweaking perspective since undervolting may not work for some chips and could cause more trouble (random restarts and the like) than it's worth. It's fun for a tweaker (like when I did something like that for the N1) but not for someone who's the flash and forget type. :fingers-crossed:
Thanks
P.S you missing the ":" on the http link
Really glad to have you here iR. Missed your kernels from my nexus one days with those hybrid AVS kernels.
Camera is buggy
Sent from my HTC One using xda app-developers app
chourmovs said:
Camera is buggy
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The camera will problably need som librarys, like most other kernels, I think. There is a zip for this in other threads (couldn't find it right away)
chourmovs said:
Camera is buggy
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
What is the problem exactly? Also, is this a custom Sense ROM or stock Sense? Just mentioning that it is buggy doesn't actually help me solve it since there are no bugs in my phone.
Sorry
I m on last ardh by mike86 and when I launch camera, it stuck on black canvas then I ve to hard exit
Sent from my HTC One using xda app-developers app
Intersect my man. Nice to see u in the HTC one forums!
Sent from my HTC One using xda app-developers app
Camera troubles
If somebody have problems with the camera, use the camera Fix from here:
http://forum.xda-developers.com/showthread.php?p=41712563
The bug is due to the old source code, released by HTC
If you are using a ROM based in 1.29.xxx.16 like the most of the new custom Roms flash just after the kernel.
Are the old camera libraries, that works with the Custom kernels.
chourmovs said:
Sorry
I m on last ardh by mike86 and when I launch camera, it stuck on black canvas then I ve to hard exit
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Can you try the link posted below by Maikeu and get back to us whether it fixes the issue?
Maikeu Locatelli said:
If somebody have problems with the camera, use the camera Fix from here:
http://forum.xda-developers.com/showthread.php?p=41712563
The bug is due to the old source code, released by HTC
If you are using a ROM based in 1.29.xxx.16 like the most of the new custom Roms flash just after the kernel.
Are the old camera libraries, that works with the Custom kernels.
Click to expand...
Click to collapse
Posted this in the second post here for future reference.
HI, after fashing this kernel , i cannot hear any sound from call dial ,
008325 said:
HI, after fashing this kernel , i cannot hear any sound from call dial ,
Click to expand...
Click to collapse
Thanks for the heads up! Missed that in my testing. :silly:
*Uploading a fix now.
intersectRaven said:
Thanks for the heads up! Missed that in my testing. :silly:
*Uploading a fix now.
Click to expand...
Click to collapse
Thank you very much i really like this kernel , smooth , cold , save battery
This is loosely based on CTXz's kernel. I just wanted a little more from it. I'm using it on my "Nook". Hence the name.
So may I present to you.....
Nuki - Kernel
Install:
Just flash this through TWRP recovery. I use 2.8.7.0. It'll do it's own wipes.
It's built for the "Nook" version. But should work for any WiFi only ROM.
My preferred tuner for the kernel is Kernel Audiutor . But others should work also.
Changelog
V1.1 - Ubertec and Linaro toolchains
Enabled KSM and tweaked
init.d support
Selinux permissive
V1
OC to 1344mhz
Intelliplug 3.9
govs added - lionheart, pegasusq, conservativeX, darkness, nightmare.
Shedulers - sio, vr, zen. I haven't been able to get "row" to compile without errors.
Frandom
Lots of tweaks/optimizations
Downloads:
Nuki-V1.1-Linaro
Nuki-V1.1-Uber
Nuki-V1
Stock-OG1-Nook-Kernel
Thanks to
@CTXz
@laufersteppenwolf
@friedrich420
And the ton of other git's I went through to get this.
XDA:DevDB Information
[Kernel] Nuki-Stock-T230NU, Kernel for the Samsung Galaxy Tab 4
Contributors
engine95
Source Code: https://github.com/engine95/Degaswifi-CPU-tweaks.git
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2015-10-17
Created 2015-10-17
Last Updated 2015-10-17
reserved
Mine! Will post feedcack! :fingers-crossed:
@engine95 - awesome. Gonna test it out and let you know
Looking good. Confirm working looking the SM-T230NU......should work on SM-T230 as well.
Well done. I hope it works good for you all!
Just a little update.
I'm trying to work on the GPU now, and it's proving very interesting. This GC1000 GPU treats the cores as being separate. Meaning one is for 2d @ 416mhz the other is for [email protected]
It looks like our possible freq's are 533, 624, 702. And maybe one close to 800 according to the specs.
The problem I see happening, is that we'll be locked into whatever freq I build into it. Meaning there isn't a way to change it through a kernel tuner.
So far, I havent had any luck OC'ing either of them. But we'll see what happens.
V1.1 is in OP See read changelog
Still no luck with OC GPU. But theres 2 builds: Linaro and Ubertec toolchains. Let me know which one you like/prefer.
Enjoy
Nice
so what's the point?
new features?
overclocked?
emoboy (Official Name!)
Nice
so what's the point?
new features?
overclocked?
Click to expand...
Click to collapse
I don't know you. So I don't know if this is sarcastic or not. So I'll play this answer in the middle.
Read the change log and look at the git. Almost everything here has been reworked, updated and/or added. Oc is the only thing I haven't touched. Yet.
@engine95 - for me, my tablet runs smoother on the linaro build.
Nice update and thank you.
g_ding84 said:
@engine95 - for me, my tablet runs smoother on the linaro build.
Nice update and thank you.
Click to expand...
Click to collapse
Thanks
On my past kernels, Ubertec seems to usually run faster. While Linaro runs smoother. But on this tab, it's harder to tell. So Thanks for letting me know. :good:
I am impressed with a lot of the optimizations that "Sammy" has already build into this. Source code I'm used to changing is already in it. And this thing sleeps like a baby.
It's too bad Marvell/Vivante/Sammy has throttled this CPU/GPU so much according to the specs. I mean, for a low-end setup it could be a lot better. But then, it would probably lose battery.
I'm not going to add anymore "stuffs" to it, as I think we have a good selection now. What is in it should satisfy " battery thru performance" depending on the settings people choose.
I haven't even looked a OC CPU yet. All I've tried so far is GPU and that hasn't gone well.
These will be the next things I'll work on. Unless......"SQUIRREL!"
forgive my ignorance, normally i would use the googles and xdas to educate myself before asking such a question, however, I have basically given up on this tablet.....so does your development of this kernel bring the tab 4 7" owners any close to getting an aosp build, this tablet is useless running TW?
edit: upon review, my post was thankless but i am very thankful for you doing what you do for this tablet, it so needs the attention!
gammaxgoblin said:
forgive my ignorance, normally i would use the googles and xdas to educate myself before asking such a question, however, I have basically given up on this tablet.....so does your development of this kernel bring the tab 4 7" owners any close to getting an aosp build, this tablet is useless running TW?
edit: upon review, my post was thankless but i am very thankful for you doing what you do for this tablet, it so needs the attention!
Click to expand...
Click to collapse
Its all good. No worries.
Unfortunately, no. It just improves on stock.
Im new to Samsung, so its all a new learning curve for me. I am kinda shocked at how "low-end " this is for a mainstream tablet. I'd have thought it would be.....better.
T-230 with nuki v1.1 linaro. Working amazingly. Thank you much.
Thank you for this kernel! I've never even thought to use another kernel for this low-end device.
Mine was originally the Nook version as well but I have flashed the latest non-nook firmware and heavily modded it.
I'm using the Linaro version. Xposed is running with a few modules. tuning with Kernel Audiutor.
The device it running very well. smoother than normal. It's a bit warmer too. but we'll see about that though.
Uber variant. Makes a huge difference. Thank you!!!
Still using the linaro. I can't seem to make either of the CPU frequencies stop being max. (1344)
Any suggestions? I'll end up trying the Uber kernel in a moment.
brossovitch said:
Still using the linaro. I can't seem to make either of the CPU frequencies stop being max. (1344)
Any suggestions? I'll end up trying the Uber kernel in a moment.
Click to expand...
Click to collapse
When you reboot, you'll need to set min, manually. I don't know why.
Or, try a different gov. Lionheart and conservativex are my preference.
You may need to remove the set on boot option, then reenable it.
It shouldn't be sticking like that
Mhh, that all sounds very interesting. Possible I can test it this weekend.
CTXz kernel is my first choice all that last year, so I can test it against yours. Don't get me wrong it will be very interesting to see what's different.
Not to see what is better, I wish to see the difference. Every ROM has his specific use and modifications. So it is the science guy who wish to know it .
Will report later about it and CTXz I will be every time a fan of your work .