Related
I haven´t found any info around the web about CM team making a vivo release? Does anybody have information about that?
weaselEST said:
I haven´t found any info around the web about CM team making a vivo release? Does anybody have information about that?
Click to expand...
Click to collapse
The CM team tend to not discuss a lot of what they will release untill it is due soon. Guess it's to stop people nagging about deadlines.
They are probably waiting for the source code and kernel.
acme anvil said:
They are probably waiting for the source code and kernel.
Click to expand...
Click to collapse
Source code for HTC ROM? Or what?
weaselEST said:
Source code for HTC ROM? Or what?
Click to expand...
Click to collapse
They are waiting for the source code for kernel 3.0.16. Currently, it only works for Sense ROM's and not AOSP ROM's. AOSP for our device uses 2.6.x GB kernel hacked to work with ICS which is why our ROM's aren't fully stable yet unless your using the stock 3.0 kernel.
I emailed HTC regarding kernel sources and was told they will release it 90-120 days after the release of the WWE ICS RUU. The RUU was released a few weeks ago, so a few months to go unfortunately.
ZaySk said:
They are waiting for the source code for kernel 3.0.16. Currently, it only works for Sense ROM's and not AOSP ROM's. AOSP for our device uses 2.6.x GB kernel hacked to work with ICS which is why our ROM's aren't fully stable yet unless your using the stock 3.0 kernel.
I emailed HTC regarding kernel sources and was told they will release it 90-120 days after the release of the WWE ICS RUU. The RUU was released a few weeks ago, so a few months to go unfortunately.
Click to expand...
Click to collapse
exacly
s*ck but we must waiting
check ice cold sandwich
4 me best ics rom
5!
Just curious, what is the difference between AOSP kernel and Sense kernel in general? If I got the source for the Sense kernel, what do I need to do to make it work for AOSP?
itandy said:
Just curious, what is the difference between AOSP kernel and Sense kernel in general? If I got the source for the Sense kernel, what do I need to do to make it work for AOSP?
Click to expand...
Click to collapse
do you have the source ;o !
and you would need to build a aosp kernal based on the sense source
naathaanb96 said:
do you have the source ;o !
and you would need to build a aosp kernal based on the sense source
Click to expand...
Click to collapse
Just don't get so excited. It's just a big IF. ,-)
What do you meaning building an AOSP kernel based on the Sense kernel? I previously compiled some AOSP kernels from source but dunno about porting Sense kernel to AOSP.
Sent from my Incredible S using Tapatalk 2
itandy said:
Just don't get so excited. It's just a big IF. ,-)
What do you meaning building an AOSP kernel based on the Sense kernel? I previously compiled some AOSP kernels from source but dunno about porting Sense kernel to AOSP.
Sent from my Incredible S using Tapatalk 2
Click to expand...
Click to collapse
i think you need to compile a AOSP kernal from the sense kernal source. id private message kaijura or lord clokan or nik, being developers they would be able to tell you more do you know someone who is a htc dev or something ?
naathaanb96 said:
i think you need to compile a AOSP kernal from the sense kernal source. id private message kaijura or lord clokan or nik, being developers they would be able to tell you more do you know someone who is a htc dev or something ?
Click to expand...
Click to collapse
I wish I do but I don't
Sent from my Incredible S using Tapatalk 2
Now as the source code is available, we can hope for stable ICS rom.
Well ICS is already kind of stable just some minor bugs if you mean that. However JB would very likely be possible imo.
Our devs are working on it and I'm sure CM10 will be on our device Nik just got a port from DHD ROM booting and will release it tomorrow Also Floatshow and djpbx are building a JB ROM from source and I guess they're making awesome progress, too. So it's just about time, mate
Nice to see that my old thread has been awaken
Waiting from CM10 now.
Just a matter of time. Gonna be a fun few weeks
Sent from my HTC Incredible S
Nik got it booting!
Sent from my HTC Incredible S using xda premium
Nik released his JB rom stating he uses CM10 kernel. I understand that kernel is phone specific and does that mean we well see a CM10 alpha build really soon?
weaselEST said:
Nik released his JB rom stating he uses CM10 kernel. I understand that kernel is phone specific and does that mean we well see a CM10 alpha build really soon?
Click to expand...
Click to collapse
It doesn't surely mean that but it's possible
What about CM9. will we get it?
Sent from my Incredible S using Tapatalk 2
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least
TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....
There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app
CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.
Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.
TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:
zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!
markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed
Hey guys, I know this is probably a dumb question. But it is better to say oh well than what if.
Can i have cyanogenmod 10.1 and badseed kernel running together? I have a Sprint HTC One I have S-Off and write protection disabled fully rooted.
No. CM is AOSP and badseed is made for sense roms. With CM or any AOSP based roms you have to use an AOSP based kernel.
Sent from my HTCONE using xda premium
tristandespain said:
With CM or any AOSP based roms you have to use an AOSP based kernel.
Click to expand...
Click to collapse
Which currently doesn't exist.
sauprankul said:
Which currently doesn't exist.
Click to expand...
Click to collapse
Well, they do exist or we couldn't run AOSP ROMs on our devices. No dev has made a flashable zip of thier AOSP kernel available for our device.
Sorry, I thought custom/separate kernel was implied.
Thank you!
Thank you guys so much, I just had to make sure i had that cleared up. This community is the best.
Im not sure if this has been addressed already, sorry if has but are there any kernels for 4.3 roms that dont break tne camera???
davidwritesmusic said:
Im not sure if this has been addressed already, sorry if has but are there any kernels for 4.3 roms that dont break tne camera???
Click to expand...
Click to collapse
Nope, source code isn't yet released by HTC
Sent from my HTCONE using Tapatalk
Okay thanks, wasn't too sure.
Sent from my HTC One using Tapatalk
Sorry to dig up an old thread, but I was going to ask a similar question so I figured I'd continue this conversation.
HTC released the kernel source for the GPE 4.3 sometime ago, is that not usable for Sense kernels or, at the very least, AOSP 4.3 kernels? I'm looking for a kernel with S2W on 4.3 but haven't seen any... So not possible yet?
FPBug: Meet the very first stable kernel for the Galaxy S2 i9100, S2 AT&T i777, S2 Epic 4G Touch d710 and Note n7000 since Gingerbread days
Every single Android 4.x kernel for these devices has had a serious bug (FPBug) that randomly corrupts the state of processes, starting with Samsungs's stock ICS and JB and spanning every custom kernel out there newer than Gingerbread.
Please refer to the main thread for details.
Downloads
You will find kernels for various CyanogenMod releases, M-snapshots and nightlies here.
XDA:DevDB Information
FPBug-n7000, Kernel for the Samsung Galaxy Note GT-N7000
Contributors
Lanchon
Source Code: https://www.androidfilehost.com/?w=files&flid=22853
Kernel Special Features:
Version Information
Status: Testing
Created 2014-12-19
Last Updated 2014-12-19
Thank you!
Will test it and get back to you!
This... this is awesome...
slimkat last version wifi not turning on!
180490 said:
slimkat last version wifi not turning on!
Click to expand...
Click to collapse
lol these are cyanogenmod kernels!!!
@Lanchon thank you soooo much for all of your hard work for our device even tho you don't even own them!
Hope this is not rude, but may I ask if you plan on releasing a kernel (or kernels) for non-CM-based ROMs? Or are you planning to let them devs themselves merge the fix, and only release CM kernels?
Sorry if this was rude, please ignore me or sth if it was.
Once again, thank you for all or your hard work.
Wow thanks
Does FPBug related somehow to kitkat overheating and random reboots?
LAKAME_MAN said:
@Lanchon thank you soooo much for all of your hard work for our device even tho you don't even own them!
Hope this is not rude, but may I ask if you plan on releasing a kernel (or kernels) for non-CM-based ROMs? Or are you planning to let them devs themselves merge the fix, and only release CM kernels?
Sorry if this was rude, please ignore me or sth if it was.
Once again, thank you for all or your hard work.
Click to expand...
Click to collapse
nothing rude! i will only release kernels for CM. but i published the fix and others will merge it into their kernels soon
Lanchon said:
nothing rude! i will only release kernels for CM. but i published the fix and others will merge it into their kernels soon
Click to expand...
Click to collapse
Yep, I'm cooking something right now for Touchwiz and AOSP. The fix seems to be working well, tested with the detector.
ASMI1 said:
Wow thanks
Does FPBug related somehow to kitkat overheating and random reboots?
Click to expand...
Click to collapse
yes!
Lunchon, if i may, a paired request Could you make a TRIM + FPbug kernel, for LP ?
Wow! You're a hero, been using your kernel only for 24h, but no problems yet. One question tough, can i switch to the ART runtime when using your kernel, or should i stay on dalvik?
daedric said:
Lunchon, if i may, a paired request Could you make a TRIM + FPbug kernel, for LP ?
Click to expand...
Click to collapse
dont know what LP is. is it a rom? then no!
pls ask you kernel maintainer to merge
mkalic said:
Wow! You're a hero, been using your kernel only for 24h, but no problems yet. One question tough, can i switch to the ART runtime when using your kernel, or should i stay on dalvik?
Click to expand...
Click to collapse
dont know. answer is same answer that applies to the standard CM kernel
Sorry,I'm new to all of this. I've all but given up on a stable kitkat experience on my good old note, but you madw it happen. Thank you, and happy hollidays!
Lanchon said:
dont know what LP is. is it a rom? then no!
pls ask you kernel maintainer to merge
Click to expand...
Click to collapse
By lp he means android 5.0 overall. Not specific rom. Are you able to prepare lollipop kernel for community?
Sent from my GT-N7000 using XDA Free mobile app
KalZakath said:
By lp he means android 5.0 overall. Not specific rom. Are you able to prepare lollipop kernel for community?
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
the fpbug should be integrated in cm soon. so i think official cm will be fixed long before cm12 is released.
mkalic said:
Wow! You're a hero, been using your kernel only for 24h, but no problems yet. One question tough, can i switch to the ART runtime when using your kernel, or should i stay on dalvik?
Click to expand...
Click to collapse
I`m using ART with latest CM11 and this kernel — everything is working fine for me.
Lanchon said:
the fpbug should be integrated in cm soon. so i think official cm will be fixed long before cm12 is released.
Click to expand...
Click to collapse
Fpbug- yes, but what with trim?
Sent from my GT-N7000 using XDA Free mobile app
Grok said:
I`m using ART with latest CM11 and this kernel — everything is working fine for me.
Click to expand...
Click to collapse
Just switched to SlimSaber, i don't like CM. The developer included the FPbug fix and it runs great with ART.