Related
So after installing this amazing rom and loving it for a week or two; I see a kernel update and install it. Everything went smooth but I lost my wifi after the fact. I was hoping someone could help me keep the kernel and get the wifi going. nothing about wifi problems were stated and it work fine previously. I wiped everything and even tried the wifi fix manager thingy i got with the ics rom i was running previously to see if that would do it but to no avail. I wanted to ask the developer but need some 10 post so help a bro out!
p.s....gotta give props to the man who had me running jb before anyone of my friends with newer phones!!! RANDOMBLAME!!!!
bboygmoney said:
So after installing this amazing rom and loving it for a week or two; I see a kernel update and install it. Everything went smooth but I lost my wifi after the fact. I was hoping someone could help me keep the kernel and get the wifi going. nothing about wifi problems were stated and it work fine previously. I wiped everything and even tried the wifi fix manager thingy i got with the ics rom i was running previously to see if that would do it but to no avail. I wanted to ask the developer but need some 10 post so help a bro out!
p.s....gotta give props to the man who had me running jb before anyone of my friends with newer phones!!! RANDOMBLAME!!!!
Click to expand...
Click to collapse
ditto, this happend with my Paranoidandroid install as well. kernel allowed me to stay running without crash, but wifi is a pretty big letdown...
unfortunatly, without the kernel itself being fixed, or the wifi module fixed, we are stuck looking for another alternate kernel... oh yeah, we are pretty limited.
thanks
appreciate the quick reply man. And I'll be keeping my eye out then
bboygmoney said:
appreciate the quick reply man. And I'll be keeping my eye out then
Click to expand...
Click to collapse
found out a very possible reason . are you using his kernel with another system or is this all jt only? he mentioned something about kangbang changing drivers.
dakunesu said:
found out a very possible reason . are you using his kernel with another system or is this all jt only? he mentioned something about kangbang changing drivers.
Click to expand...
Click to collapse
So I'm only using it with jelly time or jb. I'm flashing the os then the kernel cuz the os installs its own. This is an updated kernel for the os.I'm thinking i should maybe wipe the cache partition after the the os then do the kernel but at the same time I would think that other problems would be happening if that was the issue. What do you think?
bboygmoney said:
So I'm only using it with jelly time or jb. I'm flashing the os then the kernel cuz the os installs its own. This is an updated kernel for the os.I'm thinking i should maybe wipe the cache partition after the the os then do the kernel but at the same time I would think that other problems would be happening if that was the issue. What do you think?
Click to expand...
Click to collapse
does the system function without the kernel update?
if it does, you might want to hold off on updating til the ROM updates for it.
dakunesu said:
found out a very possible reason . are you using his kernel with another system or is this all jt only? he mentioned something about kangbang changing drivers.
Click to expand...
Click to collapse
dakunesu said:
does the system function without the kernel update?
if it does, you might want to hold off on updating til the ROM updates for it.
Click to expand...
Click to collapse
It does. N You know I am not even sure what advantages I get from this updated kernel anyways lol but I want it!!
problem solved!
bboygmoney said:
It does. N You know I am not even sure what advantages I get from this updated kernel anyways lol but I want it!!
Click to expand...
Click to collapse
The ROM was updated and the kernel included in the update! Amazing rom , highly recommended especially with the updated kernel!
These kernels are for CyanogenMod 10 - Alpha 4.
The goal of these builds is to fix the issues with phone signal, which is not properly working with the stock kernel. Nothing was changes, no extra features, no nothing.
There won't be any more "development" now that the bug is fixed.
The experimental sync bug fix, as the name says, it's a new sync bug fix I was testing. It's here because it partially fixed the missing signal issue at first, but it's not the real fix.
Downloads:
kernel-cm-10-A4-signal_fix.zip: dhiru's kernel + signal fix [0001, 0002] - (previously known as V1)
kernel-cm-10-A4-signal_fix-exp.zip: experimental sync bug fix [0003, 0004] + signal fix [0001, 0002] - (previously known as V2)
kernel-cm-10-A4-restore.zip: stock alpha 4 kernel.
Note: I forgot to change the "name" of the kernel, so you'll get [email protected]_CM9. Don't worry, it's for CM10
Even though I marked V2 as experimental build and I added it as alternative choice, it's the most downloaded version.
As I reported several time ago, mobile data is maybe less stable with it and I think it's because the PDA state is controlled with early suspend instead of the regulr suspend, as it was in the old Samsung releases. In case of problems, flash V1.
If you noticed anything, please report
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patches attached, applied as indicated above.
I verified that when a stock ROM is used, GPIO 126 is normally set to 0.
UPDATE
Click to expand...
Click to collapse
If you are stuck at Samsung splash screen and you are unable to reboot in recovery (I don't know why some users are facing this issue), so you are not able to flash another kernel or restore a backup, you can try to flash one of the kernels with ODIN.
Downloads:
kernel-cm-10-A4-signal_fix-ODIN.tar: dhiru's kernel + signal fix [0001, 0002] - (previously known as V1)
kernel-cm-10-A4-signal_fix-ODIN-exp.tar: experimental sync bug fix [0003, 0004] + signal fix [0001, 0002] - (previously known as V2)
kernel-cm-10-A4-restore-ODIN.tar: stock alpha 4 kernel.
Reboot in Download mode and flash as PDA.
Kernel modules are not included in the PDA. They are not necessary if you were using dhiru's CM with no custom kernels. If you are not sure, do as follows:
Flash kernel as PDA with ODIN (assuming you are stuck at Samsung splash screen and can't reboot in recovery)
Reboot in recovery (pull the battery if nothing works and use the three-keys combo)
Flash CyanogenMod 10 zip (your data will be preserved)
Flash once again kernel as PDA with ODIN
_____
Older posts:
Update: Now I know what stock ROMs use (GPIO 126 = 0). I'll soon update the kernel.
I already wrote that this won't be a custom kernel, no extra features, overclock etc. I opened this thread simply to test a fix, that's why I opened it in the general section, even though the dev section would have been more appropriate.
I'm lazy, so read this post.
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
Very old post:
Click to expand...
Click to collapse
As I posted in dhiru's thread, with my kernel I catch the mobile signal faster than with the stock kernel. I don't have to wait, all I have to do is to turn off and then on the screen once.
I've recently done some changes to my kernel regarding the sync bug. So, suspecting those changes are what makes the difference, I applied the same changes to dhiru's kernel and built it.
I tried to reboot few times and there's really a difference, at least for me.
I suspect that with the stock kernel there are only issues in reporting the current intensity, because 3G and calls seem to work.
Download: (Flash from recovery)
kernel-cm-10-Alpha4-TEST.zip
kernel-cm-10-Alpha4-RESTORE.zip
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patch attached + unset CONFIG_SVNET_WHITELIST
I don't know if battery life is affected, if the sync bug is really gone (no issues till now) or if there are issues with this kernel (I'm not using it. I only tested it for a few minutes). Flash at your own risk.
Don't report any bug in CM10 thread if you are using this kernel. Use the restore zip first, try to reproduce the bug and then report.
Question
Hi loSconosciuto, i have one question regard alpha 4. I have problem with signal too (as i posted in alpha 4 general thread) but i think it is beacuse my modem (LUBKPD) has been overwrite to DDLE1. Is there any posibility to create a flashable zip only to overwrite my (our, for those who live in south america and has the same problem). Sorry to ask you but i do not know what to do, cause my media storage don't get recognize and i can`t back to stock rom and no one reply my question in general, my phone is practically a stone, except for that moment when get signal (sms and calls only). Thank you!
jsp1984 said:
Hi loSconosciuto, i have one question regard alpha 4. I have problem with signal too (as i posted in alpha 4 general thread) but i think it is beacuse my modem (LUBKPD) has been overwrite to DDLE1. Is there any posibility to create a flashable zip only to overwrite my (our, for those who live in south america and has the same problem). Sorry to ask you but i do not know what to do, cause my media storage don't get recognize and i can`t back to stock rom and no one reply my question in general, my phone is practically a stone, except for that moment when get signal (sms and calls only). Thank you!
Click to expand...
Click to collapse
I could, but I don't have LUBKPD modem.
All you have to do is to take modem.bin from the PDA of your ROM (as you may know, you can open it as a normal tar), copy it in /radio overwriting the existing one and reboot. Permissions will be automatically set on reboot.
If you want, here two (different) flashable zips I made for myself. You have to replace modem.bin inside of the zip with yours and then flash.
radio-cm-XXLE4-galaxysl-signed.zip (will erase /radio and then copy the modem)
radio-cm-KPU-galaxysl-noerase-signed.zip (will simply copy the modem)
Works perfectly. Thank you dear Sir :thumbup:
Sent from my GT-N8013 using xda app-developers app
Ok, I think I almost fixed the problem. sec_get_param_value is an exported symbol defined in param.ko (yeah, brilliant...), but we don't use that module anymore in alpha4. The consequence is that the function that turns on the modem is never executed completely.
It still needs some improvements. switch_sel is never set or initialized, but at least the connection is immediately enstablished now. The problem is that I'm not sure which is the best option, so I'll wait for more opinions about it.
In the meanwhile I built two new kernels:
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
V2 is a little bit more "experimental".
OP updated with the new patch.
__
Maybe this is not the right place for this thread, but I opened it here because there won't be any development.
I flashed the V2 and I got the signal instantly after flashing
Sent from my GT-I9003 using xda app-developers app
Thanks man it works great for me...flashed v2 and boom it turned on
Sent from my GT-I9003 using CM10 alpha4 Tapatalk 2
It works so good thank you so much I hope you will continue your very good job
Envoyé depuis mon GT-I9003 avec Tapatalk
Its working fine till now, Thanks alot!. I just wanted to say would you please add move governers in the subsequent release
This thread should be moved to development section.
So that people are aware of the fix.
And it works perfectly, thanks to losconsiuoto
Sent from my GT-I9003 using xda premium
hi
loSconosciuto said:
I'm lazy, so read this post.
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
As I posted in dhiru's thread, with my kernel I catch the mobile signal faster than with the stock kernel. I don't have to wait, all I have to do is to turn off and then on the screen once.
I've recently done some changes to my kernel regarding the sync bug. So, suspecting those changes are what makes the difference, I applied the same changes to dhiru's kernel and built it.
I tried to reboot few times and there's really a difference, at least for me.
I suspect that with the stock kernel there are only issues in reporting the current intensity, because 3G and calls seem to work.
Download: (Flash from recovery)
kernel-cm-10-Alpha4-TEST.zip
kernel-cm-10-Alpha4-RESTORE.zip
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patch attached + unset CONFIG_SVNET_WHITELIST
I don't know if battery life is affected, if the sync bug is really gone (no issues till now) or if there are issues with this kernel (I'm not using it. I only tested it for a few minutes). Flash at your own risk.
Don't report any bug in CM10 thread if you are using this kernel. Use the restore zip first, try to reproduce the bug and then report.
Click to expand...
Click to collapse
After i flashed with the CM10 alpha 4 the first problem i found the signla problem but thanks to your great hard work it was solved so easily and that too without any errors.
Request to Moderators Please move this thread to Developement or merge this post under the CM10 alpha 4 update
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
spacebar2011 said:
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
Click to expand...
Click to collapse
first tell me which rom were u on, and did you update to cm10 alpha 4 and followed all the instructions properly as mentioned
rahul_rocks3 said:
first tell me which rom were u on, and did you update to cm10 alpha 4 and followed all the instructions properly as mentioned
Click to expand...
Click to collapse
I wrote some of the original instructions on the i9003 forums, so procedure/method is not a problem here.
I think the issue is I flashed the v2 kernel over the ParanoidAndroid latest 2.54 Alpha4 assuming that as the base is this ROM, the kernel would work. But got a soft brick. Its all fine now, had to go through the whole KPE, LF2 process and now flashing CM10 Aplha4.
If you could just tell me if replacing the modem.bin from LF4 is enough for the signal issues or do I still need to flash the V2 kernel?
Thanks in advance!
EDIT: Flashed V2 but got a 2nd soft brick. Went through the whole process again () My signal and data are working but the indicator is greyed out.
resolved problems
I had problems relating to signal strength and storage.
Thanks and its now working perfectly.
---------- Post added at 08:04 AM ---------- Previous post was at 08:03 AM ----------
rahul_rocks3 said:
After i flashed with the CM10 alpha 4 the first problem i found the signla problem but thanks to your great hard work it was solved so easily and that too without any errors.
Request to Moderators Please move this thread to Developement or merge this post under the CM10 alpha 4 update
Click to expand...
Click to collapse
+1
Flashed V2... It's working great. Thanks.
Sent from my Nexus 7 using xda premium
Thanks works like a charm.
spacebar2011 said:
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
Click to expand...
Click to collapse
Spacebar! How the heck are you?
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
arindammanidas said:
Spacebar! How the heck are you?
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
Click to expand...
Click to collapse
I'm very well mate, you? :highfive:
Just been off the radar due to a choked studio schedule. I've been somewhat active on the One X forums though.
Cousin asked me to update his SL (passed on from me) and this happened last night. I'm not sure whether to flash the v2 kernel again as signal etc is working but the icon is all grey and it takes about 15 mins after a reboot to get signal. Don't have the time to go through the entire clean flash process all over again.
spacebar2011 said:
I'm very well mate, you? :highfive:
Just been off the radar due to a choked studio schedule. I've been somewhat active on the One X forums though.
Cousin asked me to update his SL (passed on from me) and this happened last night. I'm not sure whether to flash the v2 kernel again as signal etc is working but the icon is all grey and it takes about 15 mins after a reboot to get signal. Don't have the time to go through the entire clean flash process all over again.
Click to expand...
Click to collapse
I'm doin' good!
I'm still on CM9.... but v2 seems to work for some people including loSconosciuto himself....
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
Hi all,
First let me start by telling you what device I am using a Samsung Galaxy S III I535 running Liquid Smooth 2.37 rom.
I have been flashing phones for years and have bricked, unbricked & in most cases had success with dirty flashing and doing clean flashes. I have gotten to the point in my adventures with flashing phones to experiment with kernels, since that's all anyone talks about that gets some legit performance and battery life stats. So my questions are as follows ( and i apologize now if this has been asked a bazillion times before. If that is in fact the case, some direction to the link would be much appreciated, thanks! )
1) what are the steps one would have to take to properly flash a Kernel
2) are there any pitfalls and caveats i should be concerned about ( bricking is the obvious one here )
Thank you again in advance for taking the time to help me out. Just trying to get fully educated before i decide to start messing around further with my phones!
e_poch145 said:
Hi all,
First let me start by telling you what device I am using a Samsung Galaxy S III I535 running Liquid Smooth 2.37 rom.
I have been flashing phones for years and have bricked, unbricked & in most cases had success with dirty flashing and doing clean flashes. I have gotten to the point in my adventures with flashing phones to experiment with kernels, since that's all anyone talks about that gets some legit performance and battery life stats. So my questions are as follows ( and i apologize now if this has been asked a bazillion times before. If that is in fact the case, some direction to the link would be much appreciated, thanks! )
1) what are the steps one would have to take to properly flash a Kernel
2) are there any pitfalls and caveats i should be concerned about ( bricking is the obvious one here )
Thank you again in advance for taking the time to help me out. Just trying to get fully educated before i decide to start messing around further with my phones!
Click to expand...
Click to collapse
1) Make sure the kernel is compatible with your rom, Do some reading about the kernel -pros & cons.
2) Flash away. In theory, you don't even need to wipe cache or dalvik cache, but just wipe them to make you feel like...it's clean!!
3) The worst thing is you get a bootloop which is an easy fix.
One other thing to note, is AOSP kernels are not compatible with TouchWiz roms, and TW kernels are not compatible with AOSP roms.
Make sure you get the right one, if the developer offers both options.
Sent from my SCH-I535 using XDA Premium 4 mobile app
buhohitr said:
1) Make sure the kernel is compatible with your rom, Do some reading about the kernel -pros & cons.
2) Flash away. In theory, you don't even need to wipe cache or dalvik cache, but just wipe them to make you feel like...it's clean!!
3) The worst thing is you get a bootloop which is an easy fix.
Click to expand...
Click to collapse
Just adding onto this, one good way of ensuring #1 is to flash a compatible AOSP 4.3 or 4.4 kernel that is dated at or about the same time as your rom. If the more recent kernel doesn't work, try the release prior to that.
Sent from my SCH-I535 using Tapatalk 4
Thanks Guys!
SlimSnoopOS said:
Just adding onto this, one good way of ensuring #1 is to flash a compatible AOSP 4.3 or 4.4 kernel that is dated at or about the same time as your rom. If the more recent kernel doesn't work, try the release prior to that.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Much appreciated guys! I decided to go with [4.3/4.4][AOSP] ¤ BMS ¤ d2vzw / d2usc 3.4.y (link below). So far so good, flashed easily and no problems at this point. Ill report back and see how the performance gains are.
http://forum.xda-developers.com/showthread.php?t=2133550
Thanks again for all of your advice!
I run that kernel on all roms. Hope u get good battery life. I suggest let it stabilize a day or two.. Jst my two cents
Sent from my unknown using Tapatalk
wont connect to wifi for me
twistedillutions said:
I run that kernel on all roms. Hope u get good battery life. I suggest let it stabilize a day or two.. Jst my two cents
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
I noticed as soon as I loaded the Kernel there was an issue. It wouldn't connect to any wifi networks. As a matter of fact, I couldn't even turn on wifi, the switch just stayed grayed out after i initially hit it. So currently I am running KT until I can find a solution to my issue. I would love to run BMS given the great response but I need to be able to use wifi lol
e_poch145 said:
I noticed as soon as I loaded the Kernel there was an issue. It wouldn't connect to any wifi networks. As a matter of fact, I couldn't even turn on wifi, the switch just stayed grayed out after i initially hit it. So currently I am running KT until I can find a solution to my issue. I would love to run BMS given the great response but I need to be able to use wifi lol
Click to expand...
Click to collapse
What is the name and date of the rom that you are on? Which version and date of KT747 are you using? Lastly, which version and date of BMS did you flash?
Sent from my SCH-I535 using Tapatalk 4
versions im running
SlimSnoopOS said:
What is the name and date of the rom that you are on? Which version and date of KT747 are you using? Lastly, which version and date of BMS did you flash?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Liquid Smooth 2.37 from 11/06/2013
KT747-AOSP-JB-MR2-3.4-VZW-11-04-2013
BMS_3.4_d2_2014-01-27
U need an older version of BMS thoss new version from dec till now are for 4.4 roms and liquid 2.37 is a 4.3 thats the reason why ur having issues
Sent from my unknown using Tapatalk
Alpha Omnirom 5.0 (Trying to get calls to work properly on CM first before doing more omni builds))
baseband is still unknown. So no phone calls or data.
Alpha Cyanogenmod 5.02 with working baseband
https://drive.google.com/file/d/0B4k5OpXTXcS9NF8zN1dreFAtOUk/view?usp=sharing
Build 5.0.1:
https://drive.google.com/file/d/0B4k5OpXTXcS9NVp0Sm9YMFdEUUE/view?usp=sharing
Calls should now work without lockups. Data seems flakey? Let me know your finding
(This is now working due to rolling back to old RIL blobs (pre 4.3). This means that the connection process takes longer on initial start-up and switching to air-plane mode as well. )
Leave wifi on to avoid reboots.
Also this doesnt have the camera bug fix yet that Derteufel made.
Nice.. Never been a fan of omni.. I'm more a cm or aosp person
Sent from my GT-I9305 using XDA Free mobile app
REVIEW
Thank you very much for this build for the i9305
I have been waiting for the first lollipop build
I installed this rom and this is a written review after one hour of usage
1 the phone boots without any problem
2 lollipop gapps are working
3 Sometimes wifi works and sometimes no
4 Bluetooth works
5 some random reboots and sometimes it stuck so I need to remove the battery to get it working again
6 no FCs at all
7 seems fast
8 when I open an app installe from play store the phone stucks and I remove the battery
Thanks again and I wish u improve this rom in the coming days
Good job mate but I think it'll be better to edit your thread to make something more attractive, Flash Guide for noobs , links to gapps, alternative dl links , what works, what doesn't , credits , shiet like this would be better for everyone.
The main problem of your rom seems to be the kernel (random reboots , wifi issues , random freezes)
Anyways , good luck and thank you for the rom
aaz03 said:
Good job mate but I think it'll be better to edit your thread to make something more attractive, Flash Guide for noobs , links to gapps, alternative dl links , what works, what doesn't , credits , shiet like this would be better for everyone.
The main problem of your rom seems to be the kernel (random reboots , wifi issues , random freezes)
Anyways , good luck and thank you for the rom
Click to expand...
Click to collapse
Thanks for the feedback.
This isnt meant for n00bs to flash yet. This is an alpha.
In Alphas you expect to get problems! This is only meant for testing and for trying out 5.0 on your device...
can we flash this normally?
CM 5.0.1 build added to OP. Please read notes about what isnt working before flashing!
So the latest build is the most stable one (CM12)? Can I help you in any way, testing, logs or something?
limnaln said:
So the latest build is the most stable one (CM12)? Can I help you in any way, testing, logs or something?
Click to expand...
Click to collapse
Well at this point in time no. I've just got to try to figure out whats going wrong still and then people can test to see if it works for them and if there is any long term problems with it. Until then its just make a change, compile and flash and I'll let people know if I get anywhere.
for me it is stuck on bootloop... first flashed wih wipe full/dalvik/cache then flashed gapps - bootloop. second dirty flashed again, booted, android is upgrading, optimizing apps, then rebooted and again bootloop... how to get past this ?
Tested. Boots okay. Data baseband ok. Incoming calls ok. Outgoing calls impossible. Tested with 2g
laurent.siku said:
for me it is stuck on bootloop... first flashed wih wipe full/dalvik/cache then flashed gapps - bootloop. second dirty flashed again, booted, android is upgrading, optimizing apps, then rebooted and again bootloop... how to get past this ?
Click to expand...
Click to collapse
As I said this doesnt have the camera firmware patch added so some people might get bootloops... I'll add this in the next day or two from Derteufel
infrag said:
As I said this doesnt have the camera firmware patch added so some people might get bootloops... I'll add this in the next day or two from Derteufel
Click to expand...
Click to collapse
So, we are at the final step - outgoing calls, huh?
There also appeared some new commits on nameless gerit, just informing
Outgoing calls can be made now. But it seems to lockup when hanging up. New link in OP for 'new' build.
Calls should now work!
This is using old ril blobs so initial connection from boot will take longer. Also I think data is stuffed a bit. Seems to take a long time to get connected. Seems to work for me after that though. Post your finding please!
Hopefully Derteufel can figure out the problem with the newer blobs but till then this is working if anyone is interested.
Edit: only got one question. Can wifi be turned off. Will disabling it cause bootloops?
infrag said:
Calls should now work!
This is using old ril blobs so initial connection from boot will take longer. Also I think data is stuffed a bit. Seems to take a long time to get connected. Seems to work for me after that though. Post your finding please!
Hopefully Derteufel can figure out the problem with the newer blobs but till then this is working if anyone is interested.
Click to expand...
Click to collapse
Yes, it does work indees! In and out! Really great, the whole system is smooth.
Great work. Will be swapping back to the i9305 from the note 2.. All we need now is for someone to work on the stock cm kernel to make it smoother.
Sent from my GT-N7105 using XDA Free mobile app
Great work on calls! Please let us know when you include the camera firmware fix so I can download again and flash, this is the only thing causing me bootloops and preventing me for further testing. Thanks
Sent from my GT-I9305 using XDA Free mobile app
winxuser said:
Great work. Will be swapping back to the i9305 from the note 2.. All we need now is for someone to work on the stock cm kernel to make it smoother.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Stock kernel? We are only using that to get data working... I'm sure Derteufel will switch to his own kernel as soon as he irons out the problems with phone calls locking up etc. (Or he switches to old RIL blobs for now)
Then there will be the challenge of getting R4P0 drivers to work properly.
After that who knows? Fix opensource compass?
Then Nameless may have other upgrades to implement for HWC.
Q&A for [KERNEL][ALPHA][LP 5.1]CyanogenMod 12.1 Kernel with DoubleTap2Wake
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][ALPHA][LP 5.1]CyanogenMod 12.1 Kernel with DoubleTap2Wake. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Bootloop after flashing. Help!
Need some help. I have installed this kernel on CM 12.1 Rohan's build and got bootloop... Some info: I used Philz Touch 6 Fota and wiped cache and dalvic after flash. I recovered from soft brick through but what should I do to avoid bootloop?
File
Sorry for the dumb question but what is zip dl-0? cant flash it, it wont detect it.
Good day. First off, i wanted to say that i've tried this kernel and the d2w is very helpful for preserving the hw power button and i think this kernel is very useful.
The thing is, since their latest releases, i've found that Glade Rom and SlimLP have been the roms that are best for me in terms of what i need and my daily usage. Unfortunately, this kernel doesn't work for either of them. I'm guessing it's because of their base?
Anyway, i'd like to ask if the dev has any plans to get this kernel working for either of those roms or for aosp 5.1.1 roms in general? If yes, that would be awesome. If not, then i still say this kernel's features are still very helpful and i'll be waiting to get a cm-based rom that works for my needs. ?
cascabel said:
Good day. First off, i wanted to say that i've tried this kernel and the d2w is very helpful for preserving the hw power button and i think this kernel is very useful.
The thing is, since their latest releases, i've found that Glade Rom and SlimLP have been the roms that are best for me in terms of what i need and my daily usage. Unfortunately, this kernel doesn't work for either of them. I'm guessing it's because of their base?
Anyway, i'd like to ask if the dev has any plans to get this kernel working for either of those roms or for aosp 5.1.1 roms in general? If yes, that would be awesome. If not, then i still say this kernel's features are still very helpful and i'll be waiting to get a cm-based rom that works for my needs. ?
Click to expand...
Click to collapse
Doesn't work in the sense?
I have plans to bring this to every LP based ROM for XL.
I guess there might be some kernel related change. I will see to it.
corphish said:
Doesn't work in the sense?
I have plans to bring this to every LP based ROM for XL.
I guess there might be some kernel related change. I will see to it.
Click to expand...
Click to collapse
bootloops. even through a clean install or flashing it after an install and clearing dalvik and cache...
i've noticed that the roms that doesn't work with tz 4.15 won't work with this kernel either.
great to hear your plans. really appreciate it.
edit:
both these roms are aosp based and have RRO supported as opposed to cm theme engine. could that have any bearing on it? let me know how i can help.
Problem on my HTC One (M7)
Hello,
first of all I would like to apologize for my English problems. I installed your Kernel on my HTC ONE M7. It is running on Cyanogenmod 12.1 (Android 5.1.1). The problem is that my handy freezes everytime it tries to boot. It freezes on the HTC logo to be more specific. Please let me know if you need to know more details or need even a log and I hope this issue gets solved.
Thank you
usb619 said:
Hello,
first of all I would like to apologize for my English problems. I installed your Kernel on my HTC ONE M7. It is running on Cyanogenmod 12.1 (Android 5.1.1). The problem is that my handy freezes everytime it tries to boot. It freezes on the HTC logo to be more specific. Please let me know if you need to know more details or need even a log and I hope this issue gets solved.
Thank you
Click to expand...
Click to collapse
LOL No, this kernel is not meant for HTC One.
This kernel is only for Sony Xperia L. Please read the full post before trying anything.
Now how to recover? If you are able to go in recovery, flash CM12 or any custom ROM.
Master Solution is flashing stock as always, although I dont know how things are done for HTC [emoji14]
@corphish i kniw i shouldn't but.. If it's possible, may i ask that you add the Intelliactive scheduler if you can? Lulzactive and on demand doesn't really work for me (lulzactive seemed buggy last time i tried it - main core stayed on max freq). Just a request. ?
Wifi stopped working after I flashed this kernel. Previously I was on Tz 4.16. Any ideas what I can do fix this, other than going back to Tz?
primemonitor said:
Wifi stopped working after I flashed this kernel. Previously I was on Tz 4.16. Any ideas what I can do fix this, other than going back to Tz?
Click to expand...
Click to collapse
Well, you cannot go back to TZ now. It flashes kernel in boot-device linked partition, which is a mystery partition about which only Varun knows.
I haven't succeeded in your situation.
Sent from my C2104 using Tapatalk
corphish said:
Well, you cannot go back to TZ now. It flashes kernel in boot-device linked partition, which is a mystery partition about which only Varun knows.
I haven't succeeded in your situation.
Sent from my C2104 using Tapatalk
Click to expand...
Click to collapse
Right, learned that the hard way
Is this a known issue though, or something that you or others have previously faced, that changing from Tz to Zapdos will break wifi? Just curious.
Hey man, I use Primexperia rom, it's CM12 based, soon to be posted new ver CM12.1 based. For some reasons it's not compatible with TZ 4.16, 4.14 only (wi fi missing on 4.16) Will this kernel work for me? The only thing I really need is a stable system with Sony sound
Oh almost forgot, I use TWRP and I think that any other recovery is a waste of time, to be honest. Can I use TWRP?
illague said:
Hey man, I use Primexperia rom, it's CM12 based, soon to be posted new ver CM12.1 based. For some reasons it's not compatible with TZ 4.16, 4.14 only (wi fi missing on 4.16) Will this kernel work for me? The only thing I really need is a stable system with Sony sound
Oh almost forgot, I use TWRP and I think that any other recovery is a waste of time, to be honest. Can I use TWRP?
Click to expand...
Click to collapse
I tried, breaks network .
Sent from my C2104 using Tapatalk
corphish said:
I tried, breaks network .
Sent from my C2104 using Tapatalk
Click to expand...
Click to collapse
Stryder modded the rom while he had TZ installed ... I dont get why but thats it... Flash TZ4.15 and then TZ4.16
Sent from my Xperia T using XDA Free mobile app
Stryflex LP 1.5 Rom
Hi,
I am using Stryflex LP 1.5 Rom.
When used the its kernel,phone freezes randomly & hangs & not responds.
We have to take out battery & restart phone.
Most of the times even if i take out from pocket also it is in DeadState(even if pressed power button alos nothing works.)
So i installed Thunderzap 4.16 ,it is not freezing but Wifi is not working.
Then i shifted to your kernel, thank god it is not at all freezing while operating .
But i noticed that it is going to black screen/Dead State very frequently.
Waiting for any suggestions & help.
I appreciate your help & time.
Could we get 1.7~ OC like in TZ kernel? It was fully stable for me even with thermal throttling disabled.
Maybe it's noob but would the wake up signatures Hurt the touchscreen some how.
I mean it well make it work for 24 hour????
Tz 4.16 with cm 12 work properly and Wi-Fi is goog and with application tenderzap control you can Cheng setting so good and you can change control charge to 2100 ma for faster charging so download tanderzap control.apk
Sent from my C2105 using Tapatalk
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
After installing rom should install tanderzap.zip with via recovery for resolve Wi-Fi problem
Sent from my C2105 using Tapatalk