Tried searching first but couldn't really find anything
I know there aren't any kernels available for the 4.4 kitkat roms but I was curious if any of the 4.3 kernels would functions. Ideally I just want to be able to do some overclocking.
keithwired said:
Tried searching first but couldn't really find anything
I know there aren't any kernels available for the 4.4 kitkat roms but I was curious if any of the 4.3 kernels would functions. Ideally I just want to be able to do some overclocking.
Click to expand...
Click to collapse
I am using Palmer's kernel. It works well for me going on 3 days with omni. But don't complain if it breaks something as its not a supported kernel.
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
I am using Palmer's kernel. It works well for me going on 3 days with omni. But don't complain if it breaks something as its not a supported kernel.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
4.90 for CM10.2?
4.90 for CM 10.2 broke wifi and possibly some other stuff on CM 11.0 unofficial. Had to nandroid back, perhaps palmers kernel only works on AOSP based roms for 4.4
Yes, WiFi will be broken on any newer builds. In 10.2 it assumes a kernel module and now it assumes that the WiFi driver is built into the kernel.
In addition to WiFi issues, I would expect some oddities in the display. These may get worse on the next round of builds.
For the time being, you'll need to be patient. Any time I spent on a custom kernel would mean less working on getting our device supported properly for CM 11.
Related
I was just curious if anyone was planning on building TRWP 2.4 for the fassy since its not yet supported by their team.? Or does it still not play nice with the fassy?
BDogg718 said:
I was just curious if anyone was planning on building TRWP 2.4 for the fassy since its not yet supported by their team.? Or does it still not play nice with the fassy?
Click to expand...
Click to collapse
I'd love to see it on the fascinate! I'm rolling with it on my a500 and its freaking awesome
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
http://teamw.in/project/twrp2/40
Xceptiona1noob said:
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
Click to expand...
Click to collapse
You don't have to unlock the fascinate its all open just put cwm on it and flash cm10.1 twrp won't work on cm10 and above so you have to use cwm use this guide here http://forum.xda-developers.com/showthread.php?t=1238070
Sent from my SCH-I500 using Tapatalk 2
Xceptiona1noob said:
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
http://teamw.in/project/twrp2/40
Click to expand...
Click to collapse
cm10 includes it's own "cmupdater" app. Checks for new builds on your schedule (or manually), notifies of new builds, displays change logs, and installs the updates. Works well. It's visible on the "about phone" settings menu. Also available in the app drawer...
Sent from my SCH-I500 using xda premium
I've fixed twrp to work with cm10.1. Works pretty well. Too bad injection doesn't work any more.
jt1134 said:
I've fixed twrp to work with cm10.1. Works pretty well. Too bad injection doesn't work any more.
Click to expand...
Click to collapse
Nice I've never used twrp so I may have to try it
Sent from my SCH-I500 using Tapatalk 2
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Updated source code is here:
https://github.com/jt1134/Team-Win-Recovery-Project/commits/twrp2.4
https://github.com/jt1134/android_device_samsung_fascinatemtd/commits/myjb-next
http://www.mediafire.com/?ul4n2gc1ba044sb
jt1134 said:
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Updated source code is here:
https://github.com/jt1134/Team-Win-Recovery-Project/commits/twrp2.4
https://github.com/jt1134/android_device_samsung_fascinatemtd/commits/myjb-next
http://www.mediafire.com/?ul4n2gc1ba044sb
Click to expand...
Click to collapse
Thanx JT! Back-up and restore work just fine! Great work as always!
BDogg718 said:
Thanx JT! Back-up and restore work just fine! Great work as always!
Click to expand...
Click to collapse
Good to know. Thanks for testing it
jt1134 said:
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Click to expand...
Click to collapse
And it does work on the latest hellybean as long as you 1st flash your cm kernel to it :thumbup:
Sent from my SCH-I500 using xda premium
hhp_211 said:
And it does work on the latest hellybean as long as you 1st flash your cm kernel to it :thumbup:
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
I'd love to see this incorporated into the devil kernel
Seems my changes have been merged in the main TWRP repository
I still can't seem to come up with a decent way to replace the recovery permanently from kernel to kernel, but I've fixed fakeflash to work with the current version of TWRP. Fakeflash allows you to temporarily flash a different recovery by flashing a zip file in your current recovery. This allows it to work regardless of what kernel/recovery you are currently using.
A test version is linked below. Flash it in your current recovery and it will reboot into TWRP. Subsequent reboots will run your previous recovery, the zip needs to be flashed each time to use TWRP. Anyone who has had the fascinate for more than a year and a half should know all about fakeflash it's the original way we used recovery (**** you samsung).
http://www.mediafire.com/?tq0uq2uo24lofcl
Thanks jt. It`s a step forward. You da man that's all I can say. :thumbup::beer:
Sent from my SCH-I500 using Xparent Green Tapatalk 2
if you are on fassy, notta posted a pa twp recovery flashable test as of now
LasVegasRomeo said:
if you are on fassy, notta posted a pa twp recovery flashable test as of now
Click to expand...
Click to collapse
does that kernel notta posted kill your WiFi?
kill type ?my wifi is workin I havent had any issues as far as i know. ran wifi a lil bit earlier and no issues. My wifi has is always crappy for me though here at home. Seems spotty a lil but like i said thats normal for me.
jt1134 said:
Seems my changes have been merged in the main TWRP repository
I still can't seem to come up with a decent way to replace the recovery permanently from kernel to kernel, but I've fixed fakeflash to work with the current version of TWRP. Fakeflash allows you to temporarily flash a different recovery by flashing a zip file in your current recovery. This allows it to work regardless of what kernel/recovery you are currently using.
A test version is linked below. Flash it in your current recovery and it will reboot into TWRP. Subsequent reboots will run your previous recovery, the zip needs to be flashed each time to use TWRP. Anyone who has had the fascinate for more than a year and a half should know all about fakeflash it's the original way we used recovery (**** you samsung).
http://www.mediafire.com/?tq0uq2uo24lofcl
Click to expand...
Click to collapse
is there a way to modify the source to use the prebuilt bootimage.Also when compiling it fails to create the utilities folder.
I lost track of which versions of CM have which issues.
My phone has finally started exhibiting the flicker issue. I'd like to revert back to whichever CM it was prior to this becoming a problem, but I can't recall which it was. Were those the MDM builds?
Or do I have to avoid CM altogether if I want to avoid the flicker? I hope not, as it would kill me to have to go back to Viper after all this time on JB!
You should try techyon. It is a cm based build. I have had no issues on his rom.
Sent from my Fireball on TACHYON using XDA Premium 4 mobile app
any cm build with the 3.14 kernel will have a high % of the flickering screen. this hasnt been fixed yet. FYI
Right - my question is when was the kernel integrated? What versions are prior to that which I could try?
chupajr said:
Right - my question is when was the kernel integrated? What versions are prior to that which I could try?
Click to expand...
Click to collapse
you want to use mdm's 5 build.
(I cant post a link, but go to the CM thread, and go to "unofficial builds")
chupajr said:
Right - my question is when was the kernel integrated? What versions are prior to that which I could try?
Click to expand...
Click to collapse
that i dont know for sure. i know the 10.2 all have the 3.14 so you will need to look at 10.1
i do believe @PrimePalaver is correct, the mdm05 was one of the last builds with the 3.08 kernel
http://goo.im/devs/mdmower/fireball/cyanogenmod/mdm-releases
I was just wondering if now that there is a 4.4.2 ota out for the DNA that it will make the custom roms more stable? I updated to it and kept root and it doesn't seem to be any different and I hate the stock ui. Want to go back to a custom Rom but they all seem to have some issue or other that gets old over time so I end up crack flashing everything on here every few days haha.
CH1978 said:
I was just wondering if now that there is a 4.4.2 ota out for the DNA that it will make the custom roms more stable? I updated to it and kept root and it doesn't seem to be any different and I hate the stock ui. Want to go back to a custom Rom but they all seem to have some issue or other that gets old over time so I end up crack flashing everything on here every few days haha.
Click to expand...
Click to collapse
For you : http://forum.xda-developers.com/showthread.php?t=2560010
voxuanvy said:
For you : http://forum.xda-developers.com/showthread.php?t=2560010
Click to expand...
Click to collapse
Yea I saw that a couple days ago. Guess I worded it wrong. Now that the droid has a stock 4.4.2 will the developers be able to take whatever parts they need from it to fix the bugs etc on custom roms? Or will the DNA having the 4.4.2 radio and kernels etc will it make the custom roms such as the m7 and m8 ports and Google editions of 4.4.2 more stable?
HTC did in fact release the 442 kernel source, so new 442 Roms will be stable and I can fix z and my beast mode kernel
.torrented said:
HTC did in fact release the 442 kernel source, so new 442 Roms will be stable and I can fix z and my beast mode kernel
Click to expand...
Click to collapse
Awesome!!!
.torrented said:
HTC did in fact release the 442 kernel source, so new 442 Roms will be stable and I can fix z and my beast mode kernel
Click to expand...
Click to collapse
4.4.2 Sense based ROMs definitely should be much better. The CM based ones probably not a big difference.
crpalmer said:
4.4.2 Sense based ROMs definitely should be much better. The CM based ones probably not a big difference.
Click to expand...
Click to collapse
how about the gpe m8 port?
I am using the latest Pacman kitkat nightly and i am very satisfied with it.
I read the official KK rom is laggy. Is that true.
Any reasons for switching back to the original Rom?
Jequan said:
I am using the latest Pacman kitkat nightly and i am very satisfied with it.
I read the official KK rom is laggy. Is that true.
Any reasons for switching back to the original Rom?
Click to expand...
Click to collapse
mhl to hdmi does not work on custom roms (at least seems so..)
i'm planning to test a stock rom, maybe 4.3 since i can't find 4.4 for sgp311 and i can't update via pc companion since i unlocked bootloader.
apart from mhl issue i think ppls are very happy with custom roms so not many reasons to go back to stock.
Not finding much lag here, but YMMV. If you're happy with pacman stick with it. But, if you flash anyways you can always give stock 4.4.2 a try!
Sent from my SGP321 using XDA Free mobile app
Yo! What do you guys think is the best combination to get reasonable battery life and good performance? Im getting 59k on antutu using AICP ROM and stock kernel. Do you think i could get more with some custom kernel ?
I am just using stock since Pure Android is what I want, with ElementalX kernel. Using ElementalX on my Nexus 6, Nexus 9, and GPE HTC One M8 and love it. I look forward to Xposed working with Android 5.1 and N9 being updated. I used to flash ROMs, but on Google devices Xposed is more then enough.
metaphz said:
I am just using stock since Pure Android is what I want, with ElementalX kernel. Using ElementalX on my Nexus 6, Nexus 9, and GPE HTC One M8 and love it. I look forward to Xposed working with Android 5.1 and N9 being updated. I used to flash ROMs, but on Google devices Xposed is more then enough.
Click to expand...
Click to collapse
Im using AICP5.1.1 Rom on my N9.. Is it possible to just flash the elemental kernel without messing with the rom itself?
MikeLeema said:
Im using AICP5.1.1 Rom on my N9.. Is it possible to just flash the elemental kernel without messing with the rom itself?
Click to expand...
Click to collapse
I'm on Dirty Unicorns with Fire - Ice kernel. Insanely stable and the most functional of the ROMs I have used.
As far as just running a kernel, yes you certainly can just flash the kernel w/o changing to a different ROM. But what's the point in that??
wingdo said:
I'm on Dirty Unicorns with Fire - Ice kernel. Insanely stable and the most functional of the ROMs I have used.
As far as just running a kernel, yes you certainly can just flash the kernel w/o changing to a different ROM. But what's the point in that??
Click to expand...
Click to collapse
Can you please explain me that? Im still a noobie I tought that just by flashing elementalX kernel on my N9 I could improve AICP and overall tablet performance. I guess im totally wrong xD
MikeLeema said:
Can you please explain me that? Im still a noobie I tought that just by flashing elementalX kernel on my N9 I could improve AICP and overall tablet performance. I guess im totally wrong xD
Click to expand...
Click to collapse
Sorry when you asked the question, I didn't realize you were already on a non stock ROM. AICP already has it's own customized kernel. Yes you can flash any other custom kernel in place of the one which comes with AICP.