Hi.
I've been playing around again, just trying to learn all about this damn thing.. I might even come around to liking it one day!
But I'm trying to use a different kernel, Have Installed it (boot loops) then I tried Repack the kernel it now works, It Gets 3G but no Wifi, which is slightly annoying.
my uneducated guess thinks that this rom-kernel compatibility probably won't ever work.
ROM - [18-10] [ROM] CyanogenMod 10 - Endeavor Unleashed | 019 (latest)
(old) Kernel - Latest 3.1.10 (022A)
(new) Kernel - [KERNEL][SEP.30][AOSP]Bricked-Kernel|2.6.39.4|v0.7|Sweep2Wake|mpdecision|PowerHA L
But yeah, tl;dr wanting to change kernel, to another custom kernel and the Wifi doesn't work, even after the kernel being repacked.
Should I just switch ROMs to CM10 Nightlies? As I'm sure those work correctly. Anyone with a better suggestion? Hopefully have posted enough information to not look like an Idiot :S
Related
I have seen to many kernel threads and none of them seems to say that the kernels are safe to use with the JB leaks.
I really don't see why they shouldn't, but I really wanted to be sure.
have anyone used a Franco, faux or similiar present kernel with the new JB leaks from Insert Coin or ARHD?
Do we have to repack them to be fine?
I know that kernel version should not be a problem, but we only have source code for the ICS kernel based in 2.6.X and the new kernel is 3.0.X
So I wanna know real experiences if possible
Thanks,
Santroph.
Hi, i have tried repacking a few of them as im keeping a list up together for the maximus thread but none of the linux 2 kernels have worked yet, will try trips kernel when i get round to it this week but it says no support for sense so probably a no go. I havent seen anything new yet but will keep my post updated as and when (link in my sig) they should work for other jb sense 4+ roms too :good:
I would like find the freshest available 3.0 kernel for the Desire Z. Where is it hosted? My intention is to make a kernel more stable than others available, as all are undervolted, and unfortunately with those settings I am experiencing random reboots. I've found some sources, tuned voltages to the original ones (as in htc's 2.6.35 kernel), and the reboots disappeared.
Thanks in advance,
The Andromadus 3.x kernel and cn.fyodor's are the most recent, I might say fyodor's might be slightly ahead being as he is the Andromadus kernel guy and his kernel stuff which goes into his ROM probably gets merged into Andromadus later (or maybe he does entirely different things for each, I'm not sure, you'd have to ask him).
By the way if you manage to get either of the above up and running, I'd appreciate some help as I've been trying to compile the Andromadus kernel but have so far not been able to produce a zImage, although compilation seems fairly smooth .
And are these kernel for sense? I always read on forums that there are kernels for sense roms, but actually I dont know the difference.
Last time I compiled from github / ajhavery / htc7x30-3.0.git, and it compiled well for me.
Then two linked to you by htcdreamon are for aosp/cm/aokp etc, you are right that you can not interchange aosp kernels and sense kernels, by and large they are not compatible
Sent from my Nexus 7 using xda premium
Ive been using the dark flo version if cm10.2 since I got my nexus 7, however when ive tried to install a custom kernel, I get a blue/turquoise screen upon reboot. Ive tried both CAF and normal versions of various kernels, but all with the same results. I tried using the AOSP kernel setting in the aroma installer, then installed some AOSP kernels, which do boot but it has the worst lag ive ever seen since my iPhone! Anyone else experienced this and know a solution? Ive searched the forum but couldn't find anything relevant
Same here: installed CM10.2 unofficial, GApps, rebooted and everything´s fine.
After installing any of the Faux-Kernels (es/m/u) and wiping Dalvik etc., I have the same screen problems and lags, which make the device unusable.
I´m searching for an overclock kernel, btw.
Thanks for your input!
im after the same thing, just an oc kernel. I even tried one with no mods, just the cpu speeds increased and had no luck
UPDATE - I read somewhere that some kernels wont work with CM versions released after oct 2nd. I tried installing a copy of dark flo from the end of September, then tried faux123's latest mainline kernel abd it booted fine! Im assuming its an incompatibility with the latest CM, so I hope the kernels get updated soon!
Thank you for the info!:good:
It´s waiting time again...
how did you get out of the turquoise screen?
Easy fix:
Uninstall CM
Install AOSP based rom
Profit
Seriously, CM has gone to crap since they moved away from aosp and started with CAF. Kernel devs shouldn't have to do extra work just for one rom, especially when said rom is going from bad to worse
Nexus 7 LTE
Stock rooted KRT16S
Faux Kernel
I searched up and down for this, but for some reason when ever I use many of the roms here my menu buttons are still active when I am in call causing me to push the search button and cause google voice search to pop up. This happens way to often.
It doesnt happen when I use the CM Windows based installer to install the rom, but the battery and performance on that is not too great.
Rushing's Roms dont seem to have this but I dont really like touchwiz, and when I try any roms with the uber kernel they all have this bug and I tried to search in those threads for this but the search engine could not find anything.
I think its UBER kernel related, but also the CM Rom with Diablo kernel does the same thing, and I looked up and down in trickster mod control for button behavior but I just cant find it.
Anyone could point me in the right direction at least?
oh come on, anyone?
TheProfiteer said:
I searched up and down for this, but for some reason when ever I use many of the roms here my menu buttons are still active when I am in call causing me to push the search button and cause google voice search to pop up. This happens way to often.
It doesnt happen when I use the CM Windows based installer to install the rom, but the battery and performance on that is not too great.
Rushing's Roms dont seem to have this but I dont really like touchwiz, and when I try any roms with the uber kernel they all have this bug and I tried to search in those threads for this but the search engine could not find anything.
I think its UBER kernel related, but also the CM Rom with Diablo kernel does the same thing, and I looked up and down in trickster mod control for button behavior but I just cant find it.
Anyone could point me in the right direction at least?
Click to expand...
Click to collapse
If it bothers you that much, don't use Uber. Simple.
meekrawb said:
If it bothers you that much, don't use Uber. Simple.
Click to expand...
Click to collapse
Its not that I dont want to use UBER or any other Kernel, if its something that IS as a result of the Kernel and everything else is works well I can deal.
but maybe its an issue thats been fixed and I cant seem to locate the thread because I maybe simply do not know how to word it correctly.
TheProfiteer said:
Its not that I dont want to use UBER or any other Kernel, if its something that IS as a result of the Kernel and everything else is works well I can deal.
but maybe its an issue thats been fixed and I cant seem to locate the thread because I maybe simply do not know how to word it correctly.
Click to expand...
Click to collapse
Ahh. So do the ROMs still have the problem if you don't flash a different kernel?
meekrawb said:
Ahh. So do the ROMs still have the problem if you don't flash a different kernel?
Click to expand...
Click to collapse
been trying it out with various different combinations.
Vanilla AOKP and CM seem ok.
ThDudes's CM 10.2 + Diablo Kernel (Kernel already fused into the rom) button issue still persists, UBER Kernel flashed with TWRP on both AOKP on CM button issue persists.
but then, if I reflash vanilla AOKP or CM through TWRP the issue will still persist.
Its either the Kernel or TWRP, as you "shouldnt" flash UBER through CWP i cant quite isolate the problem.
been going back and forth quite a bit here, I would love to stick with vanilla AOKP or CM but idle battery drain is extremely excessive, and they both crash when trying to change the governor.
I am just trying to find a good stable ground to operate on as I save up for an S4 and to have a well known return point after I go on a flashing spree.
I have only been dabbling with 4.3 based roms, so I havent had the chance to try any previous version roms yet, other than Rushing's Shadow rom which was great with battery, super fast, but sadly had touchwiz which i tried to get used to but it was missing alot of the things I needed.
TheProfiteer said:
I am just trying to find a good stable ground to operate on as I save up for an S4 and to have a well known return point after I go on a flashing spree.
I have only been dabbling with 4.3 based roms, so I havent had the chance to try any previous version roms yet, other than Rushing's Shadow rom which was great with battery, super fast, but sadly had touchwiz which i tried to get used to but it was missing alot of the things I needed.
Click to expand...
Click to collapse
I have been using Slimbean 4.3.1 with @Cl3Kener stable kernel for a long while. It has been rock solid for me.
meekrawb said:
I have been using Slimbean 4.3.1 with @Cl3Kener stable kernel for a long while. It has been rock solid for me.
Click to expand...
Click to collapse
I'll have to give that a try. Been out of the loop on slimbean, used it for a little on my S1 Vibrant a while ago.
Just flashed LiquidSmooth, and apart from being only 4.1.2 AOSP, seems to be running pretty well.
sory if i post in wrong place.
my problem?
i use a lot wi-fi......
I try vanir aosp rom (based on cyanogenmod) and i have AMAZING wi-fi everyware.....
but i dont want a "havy" rom like this one.
I like Iridescent_Zed_III odexed(or not odexed),but there is a weak wi-fi.I try difrends basebands,other kernel,still weak.....
Vanir aosp is using baseband 77, Iridescent_Zed_III is usin 77 too.
What makes the difrent?kernel?
any idea?
isolove said:
sory if i post in wrong place.
my problem?
i use a lot wi-fi......
I try vanir aosp rom (based on cyanogenmod) and i have AMAZING wi-fi everyware.....
but i dont want a "havy" rom like this one.
I like Iridescent_Zed_III odexed(or not odexed),but there is a weak wi-fi.I try difrends basebands,other kernel,still weak.....
Vanir aosp is using baseband 77, Iridescent_Zed_III is usin 77 too.
What makes the difrent?kernel?
any idea?
Click to expand...
Click to collapse
to keep it short:
baseband has nothing to do with ROM. (you have to flash it manually, never changes on ROM flash. the 77 one is the last from stock rom )
now difrences between vanir aosp & Iridescent_Zed_III:
vanir aosp:
- its latest android KK 4.4.2 running on 3.4 kernel (new & powerful, but not as stable as stock.)
Iridescent_Zed_III:
-its BASED on android ICS 4.0.4 running on 2.x.xx kernel (dont know exact) its based on latest firmware we've got official from SONY. its the stablest one, when you will. but its laggy & old.
there are many things affecting the wifi (drivers inside rom, kernel, baseband, ''tweaks'' inside, even router's play a role, etc....) so its hard to say what exactly will make it better / worse. you will have to test it yourself to say if its better or not.
my advice: you say vanir had the better wifi, but its to ''heavy'' (even i dunno what u mean exactly..) so i would recommend to give Legacy Xperia ROM a shot. i think you will get the most out of it. also if you dont need to have the latest android (just want USE your phone) then use android 4.2.2 JB (CM10.1) its the bets mix of power & still very usable. in addition its keep very clean & lightweight.
LINK to thread: http://forum.xda-developers.com/showthread.php?t=2147958
good luck
Thank you for your time.
I testet 11 first...
Laggy,and what about video recording,5 seconts to start.........