WildKernel
for AT&T Samsung Galaxy S II
Go check out Tame! It goes great with this and it handles OTA updates for this kernel.
This is a Linux based (3.0.101) Kernel which is maintained by me kept inline with the Cyangenmod Kernel so this is compatible with ALL the latest KitKat Roms (unless otherwise stated in the ROM).
Please report anything good and bad so that I know what to keep and what not to keep for the next release. This also helps me push out fixes faster when presented with lots of information (such as logs etc.).
Please see changelogs for an in-depth look at features. Also take a look at the screenshots for a sneak peek.
Feeling like a critic? Leave a review!
Link broken? Try one of the mirrors, Still a no go? Goto my signature and click the file backups link, then navigate to what you were looking for.
v013: AFH
TRU Mirrors: #1 / #2
All Releases: AFH | TRU Mirrors
[#WildKernel-Celox-CL]
[/HIDE]
Thanks:
TeamChopsticks & CyanogenMod
TeamSXL
Cl3Kener
Team Hydra
TeamDS
faux123
Sultanxda
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed
Info on Governors/Schedulers
You may find my source hosted @ Github
There is NO need to clear caches, kernel installer handles everything. Just flash and reboot.
My recommended Governor/Scheduler setups:
Battery w/ Good Performance at 96-1350mhz:
Intellidemand/SIO (personal choice)
Lazy/SIO
Badass/SIO
Ondemand/SIO
Wheatley/SIO
'lil more Performance at 96-1512mhz:
Smartass/SIO
Hyper/Deadline
Samsung/Deadlne
lulzactive/Deadline
Savagedzed/Deadline
Best Performance (worst battery): 384-???mhz
Gaming/Deadline
Performance/Deadline
Did you read the announcement? (page header)
XDA:DevDB Information
WildKernel for the AT&T Galaxy S II (skyrocket), Kernel for the AT&T Samsung Galaxy S II Skyrocket SGH-I727
Contributors
Emmanuel U
Source Code: https://github.com/EmmanuelU/wild_kernel_samsung_msm8660/tree/android-msm-skyrocket-3.0
Kernel Special Features: Too many features to list, just install it.... now.
Version Information
Status: Stable
Current Stable Version: 013
Stable Release Date: 2015-01-29
Created 2014-10-15
Last Updated 2015-02-01
Tried to install but keep getting an md5 error and a message about getprop device not equaling.
Downloaded and tried twice...
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Installer zip fixed, please re download if you downloaded kernel before seeing this message....thanks!
The new installer worked, thanks. I'll play around with it and report back but I can already say that WiFi direct doesn't work (it's always the first thing I check b/c it's the only problem I have with any of the skyrockets current kernels)
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
tsew2674 said:
The new installer worked, thanks. I'll play around with it and report back but I can already say that WiFi direct doesn't work (it's always the first thing I check b/c it's the only problem I have with any of the skyrockets current kernels)
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure that problem is directly related to the kernel? It sounds more like a Rom issue....does it work on your rom's stock kernel?
Emmanuel U said:
Installer zip fixed, please re download if you downloaded kernel before seeing this message....thanks!
Click to expand...
Click to collapse
I guess the burning question for me if this includes all of Sultan's bluetooth fixes. His kernel for CM really is the gold standard for our device thus far.
I see you mentioned him in the OP so I am hopeful lol. I'd love to be able to flash this kernel with any rom knowing the usual plagues (such as the constant BT disconnect) are no longer an issue.
Thanks a lot for this! Nice to see the SR still getting some love
Emmanuel U said:
Are you sure that problem is directly related to the kernel? It sounds more like a Rom issue....does it work on your rom's stock kernel?
Click to expand...
Click to collapse
I'm pretty sure it's at the kernel level only because it works with @Sultanxda's kernel. His is the only 4.4.x kernel that WiFi direct has ever worked on for me on the skyrocket. It worked on the official CM10.2 ROMS/kernels but every since CM11 was introduced it's been broken. The ROM I'm using now could connect with WIFI direct when built with Sultan's kernel.
Even with Sultans kernel, Miracast (with uses WIFI direct) will connect but the graphics are all scrambled. I suspect that has to do with some of the memory enhancements he's made. If I knew how to build kernels I'd like to try using the official CM11 kernel source and only applying his WIFI direct commit to see what the results are, but unfortunately I don't know how to build them and can't seem to find the time to do the research to learn. Maybe one day.
I've had no issues otherwise and I've been using it for a few days now. Thanks
I tried flashing usin dirtya unicorns i can get oast boot logo ut restarts
raptorddd said:
I tried flashing usin dirtya unicorns i can get oast boot logo ut restarts
Click to expand...
Click to collapse
Once your screen goes black from the reboot, hold both the volume buttons until your device goes into recovery. Then either use ADB or your recovery's file manager to retrieve /proc/last_kmsg and it post it here. It always helps to present issues with a log ready, for future reference.
So... I got bored.
I installed the following ROM's and got bootloops for each (basically every 4.4.4 ROM I know of for Skyrocket):
AOKP - Dated 15-Sep-14
CM11 - Dated 19-Oct-14
PacRom - Dated 25-Aug-14
Mokee - Dated 12-Oct-14
Dirty Unicorns - Dated 2-Oct-14
SlimKat - Dated 14-Oct-14
CarbonRom - Dated 17-Oct-14
Beanstalk - Dated 9-Oct-14
CandyKat - Dated 18-Oct-14
Paranoid - Dated 9-Oct-14
I didn't test the following ROMs:
SultanXDA CM11 - Dated 19-Oct-14 Didn't test since I was told it would bootloop
MIUI V6 - Currently getting a bootloop so no reason to try it
Emmanuel U said:
Once your screen goes black from the reboot, hold both the volume buttons until your device goes into recovery. Then either use ADB or your recovery's file manager to retrieve /proc/last_kmsg and it post it here. It always helps to present issues with a log ready, for future reference.
Click to expand...
Click to collapse
Never done this before (well, I know how to get into recovery...lol). I'll post the file in a few minutes after reflashing one of the ones above. Can i empty this folder when I'm done? There's 200 or so subfolders in there.
ETA: Added attachment.
xonelith said:
So... I got bored.
I installed the following ROM's and got bootloops for each (basically every 4.4.4 ROM I know of for Skyrocket):
AOKP - Dated 15-Sep-14
CM11 - Dated 19-Oct-14
PacRom - Dated 25-Aug-14
Mokee - Dated 12-Oct-14
Dirty Unicorns - Dated 2-Oct-14
SlimKat - Dated 14-Oct-14
CarbonRom - Dated 17-Oct-14
Beanstalk - Dated 9-Oct-14
CandyKat - Dated 18-Oct-14
Paranoid - Dated 9-Oct-14
I didn't test the following ROMs:
SultanXDA CM11 - Dated 19-Oct-14 Didn't test since I was told it would bootloop
MIUI V6 - Currently getting a bootloop so no reason to try it
Never done this before (well, I know how to get into recovery...lol). I'll post the file in a few minutes after reflashing one of the ones above. Can i empty this folder when I'm done? There's 200 or so subfolders in there.
ETA: Added attachment.
Click to expand...
Click to collapse
Hmm interesting, since I dont have this device, I can't do this myself. But do u think u can you do the following?
1. Flash one of the Roms you listed that bootlooped above
2. Open my kernel installer and delete /system/bin/thermald
3. Push it to your device and install
4. Does it boot?
Emmanuel U said:
Hmm interesting, since I dont have this device, I can't do this myself. But do u think u can you do the following?
1. Flash one of the Roms you listed that bootlooped above
2. Open my kernel installer and delete /system/bin/thermald
3. Push it to your device and install
4. Does it boot?
Click to expand...
Click to collapse
Sadly, bootloops again (I installed the AOKP rom; clean, no GApps, let it boot once, boot to recovery and flash modified zip).
xonelith said:
Sadly, bootloops again (I installed the AOKP rom; clean, no GApps, let it boot once, boot to recovery and flash modified zip).
Click to expand...
Click to collapse
Too bad i hope emmanuel fix this.. Anything i can do ..
Reboots
I was playing around in Tame earlier and my phone rebooted a few times. I wasn't doing anything too crazy, turned off SweepToWake, changed the governor to Lazy and it froze and rebooted. The first time it happened I had changed the max frequency and a couple of other things, so I attributed the reboot to that, however when it booted back up I only changed the two items mentioned above and it rebooted again, this time it stayed off so I booted into recovery and got the kMsg, hopefully it helps. That's not the first time I've used Tame, I initially installed it, changed a few things and everything was fine, but my phone had been turned off since then so I was going back in to set it back the way I had it.
I'm currently using the liquidsmooth as my ROM, and this is really the first issue I've had with your kernel (other than WIFI direct, but that's pretty much all the kernels for this device). I think you've even improved my battery life, I don't do gaming or anything so I don't really ever notice any performance gains or that sort of thing, but I haven't noticed anything moving slower, which is good.
Update
Another minor update today, sorry about the initial discrepancies! Blame me, since I don't actually have this device. Well it should boot on all ROMs now, enjoy .... I guess.
Works great on PA! I'll mess with it for a bit and provide useful feedback.
Sent from my SGH-I727 using XDA Free mobile app
Flashed successfully on Carbon 10/17 nightly. Seems pretty snappy so far. Nice work! :thumbup:
Hi. Thanks for sharing this Kernel. I have a question...
Before, I was using Carbon with its stock kernel, Conservative governor and noop; there was no lag at all, but battery seems to last too little time in continous use and even when it was with screen off. Even before that, the CPU governor was set by default at Interactive, but the Skyrocket freezes in several times, sometimes after unplug it from charger or after unlocking it after a time (like 1 hour or something), sometimes the device hangs so long until I reboot it or it reboots itself. So, Interactive isn't the best choice for me.
The question is: What is the best choice for a governor if I want the longest battery life, but with any freezing any time?
Could you please help me?
franzpimp87 said:
Hi. Thanks for sharing this Kernel. I have a question...
Before, I was using Carbon with its stock kernel, Conservative governor and noop; there was no lag at all, but battery seems to last too little time in continous use and even when it was with screen off. Even before that, the CPU governor was set by default at Interactive, but the Skyrocket freezes in several times, sometimes after unplug it from charger or after unlocking it after a time (like 1 hour or something), sometimes the device hangs so long until I reboot it or it reboots itself. So, Interactive isn't the best choice for me.
The question is: What is the best choice for a governor if I want the longest battery life, but with any freezing any time?
Could you please help me?
Click to expand...
Click to collapse
See the OP for ny recommendations.
Emmanuel U said:
See the OP for ny recommendations.
Click to expand...
Click to collapse
Yes, I'm sorry, I forgot to say that actually I'm using Lazy governor at 96-1350 and sio as you recommended it, but I thought that maybe there's a no listed recommendation for maximun battery or something like that.
Related
Important!
It is strongly recommended that you flash clockwork recovery via NVFlash. If for some reason this or a future nightly build causes your phone to not boot up, you will not be able to boot into recovery unless you have it flashed via NVFlash.
NVFlash for Linux
NVFlash for Windows
To clear up some confusion, if you flashed your recovery via ROM Manager, you didn't actually flash a recovery. It is what we call a fakeflash, you should still probably flash with NVFlash.
Instructions
Download from http://download.cyanogenmod.com/?device=p999 and flash like you would any other ROM (via recovery or ROM Manager).
Be sure to backup before flashing, and of course a wipe is necessary when coming from stock.
Gapps are available from the usual places, however do not download the version that says it is for Tegra, even though this is a tegra device, as it will not flash.
Mod Edit:
Mikey1022 said:
Google Addon: http://goo-inside.me/google-apps/
Check the lastest package available on top
Click to expand...
Click to collapse
ChrisSoyars Edit:
After skimming some of the posts in this thread, here are some things that you can expect.
What to expect
- Everything working including Wifi, GPS, Audio, Camera, Front Facing Camera
- Screen off animation is not enabled, therefore it isn't broken.
- Occasional audio problems (as far as I know they have not been fixed). If audio does not play just reboot.
- Automagical brightness weridness, this is controlled by the kernel and not userspace, even having it working is very hacky.
Any reference to the first thread you need too look up, it's linked here:
http://forum.xda-developers.com/showthread.php?t=1058131
Changelog:
http://cm-nightlies.appspot.com/?device=p999
Thanks!!! Flashing
Is the server still down? The latest I see is 2011-5-25.
gamefreakgcb said:
Is the server still down? The latest I see is 2011-5-25.
Click to expand...
Click to collapse
I don't know whether it is still down or not, but yeah, that's still the latest build
Hrmm awesome, what about the battery stats? Anyone know if that has been fixed?
G2X & Nexus S
brian6685 said:
Hrmm awesome, what about the battery stats? Anyone know if that has been fixed?
G2X & Nexus S
Click to expand...
Click to collapse
Not on cm7 but Faux has made good progress with the help of debauchedsloth
So does this mean nightlies will resume soon?
edit, nvm oops
G2x with faux AOSP and faux orange kernel. [email protected] 5107 quadrant.
For anybody interested this is a build I just compiled about an hour ago
http://www.multiupload.com/6WEZDZMGSX
WHy a new thread? what is new?
aim1126 said:
For anybody interested this is a build I just compiled about an hour ago
http://www.multiupload.com/6WEZDZMGSX
Click to expand...
Click to collapse
How is your compile different from the gigglebread one from this morning?
jawknee530 said:
How is your compile different from the gigglebread one from this morning?
Click to expand...
Click to collapse
I dot think there's any really maybe one or two commits that got merged throughout the day. I just like compiling my own builds
Sent from my LG-P999 using XDA App
I see this thread kinda senseless as there isn't a newer nightly that was available before using the old thread. Although 2 pages seems more manageable then 300+ (which will happen eventually to this thread.)
Being a website developer I know these threads add up pretty quickly (hurray xda!)
I haven't flashed an actual CM rom in almost a week since the server crash. Hopefully the new thread is a sign that the server was repaired and new nightlies are on the way. Using the latest KANGS to get my fix, I know there is lots of progress. Running the latest KANG from today I think the rom is almost ready for a stable release after a few bugs get worked out.
I think the work you guys are doing is fantastic and much appriciated, although it may seem all we do is ***** half the time. Android wouldn't be the same without all of the developers leading the way. Big props. Hope all is well and I plan to continue to follow your work.
aim1126 said:
For anybody interested this is a build I just compiled about an hour ago
http://www.multiupload.com/6WEZDZMGSX
Click to expand...
Click to collapse
Just installed, cheers!
And thanks CM, I'm coming from #34 and just five minutes in its obvious there's been quite a bit of work done. Status Bar brightness slider is sweet.
i see a build 36 but it won't let me download? says its not found...
shniggies said:
i see a build 36 but it won't let me download? says its not found...
Click to expand...
Click to collapse
Probably still being built. Give it some time and check again.
Sounds like buildbot may be back up... this would be nice. <3
reisaru said:
Probably still being built. Give it some time and check again.
Sounds like buildbot may be back up... this would be nice. <3
Click to expand...
Click to collapse
ho ho... i must have checked riiiiiiight when it was uploading... because its downloading now
How did you find build 36 when 35 isn't out yet?
Sent from my LG-P999 using XDA App
I did not create "this" and I'm not taking credit for it. This is an awesome kernel created by an awesome dev. I have seen a lot of people asking about where to find this kernel so I asked the dev if I could make this thread to help everyone out over here. I do plan to keep this updated as he updates his OP over on Rootz.
LINK TO ORIGINAL POST ON ROOTZWIKI
This is a kexec Touchwiz test kernel. Use his thread to report bugs, etc.
WARNING: If you're on full stock, you must install busybox first.
DOWNLOAD
latest beta kernel: flashable zip
to return to stock kernel: flashable zip
INSTRUCTIONS
Make sure you're on a recovery that supports auto-flash (any CWM compatible recovery should work - I use v6.0.1.0).
Make sure your ROM has busybox installed properly (otherwise it will bootloop).
Download and flash the zip file in recovery (yup that's it).
Reboot (it will appear to boot twice after that and at every boot).
FEATURES
Unnecessary components removed for lean and fast kernel.
Compiled using latest Linaro compiler with additional optimizations.
Latest Linux updates applied (currently up to 3.0.39).
Ramdisk optimizations.
Kexec (credit goes to Mike Kasick, Austin Dicken, etc.)
OC'ed to 1.9Ghz (limited to 1.51Ghz at boot, use an app to change max freq)
SIO I/O scheduler default
Fast Charge (toggle via the "ffc" script - open terminal, type ffc then enter, plug in phone via USB)
On-demand governor backported from Linux 3.5
CHANGELOG (BETA)
v0.1 (b31fd85c46133f21d3e83d2a5c7d6f94) - initial beta release. Changes from test v12.2.
CHANGELOG (TEST KERNEL)
v10.4 - initial test release
v11.1 (0a169bbc58f7f5b14315f6e2dad47226) - leaner kernel, ondemand governor backported from Linux 3.5, latest interactive governor (not recommended yet)
v12 (8d31143328f19a6183ce6ed50d3f2f76) - fixed default max frequency (really set to 1.51ghz), custom boot animation support, init.d support, Linux 3.0.39 update
v12.2 (3640421cf043e4bdb88de3162c9984fa) - fixed blue LED issue at boot for some ROMs.
TODO
This is alpha/test kernel. More development will come.
Remember this is just a repost of his OP. To get support from the dev you will more than likely have to go over to Rootzwiki to get it. All of the links in this post redirect to the OP on Rootzwiki and not to download links. You will have to go to his OP to download the kernel.
Disclaimer said:
Me and this dev are not responible for you not reading the entire post on either site and bricking your device or anything else you might want to blame either of us for.
Click to expand...
Click to collapse
How do I use USB Fast Charge?
1) Unplug from USB cable.
2) Open Terminal Emulator, type "ffc" (without quotes) and enter. This command will toggle your fast charge state.
3) Plug it back in.
Note: running the same command again will disable fast charge.
Also, when fast charge is enabled USB communication will be disabled.
Why KEXEC?
I actually had my own hybrid recovery/kernel method, which was kinda cool. No special kernel modification was necessary, simpler boot hijack, etc. But it did mean that recovery was modified and required flashing into recovery partition for every new version. Plus all the cool cats were using kexec.
I don't mean to be a jerk or step out of place, but ,there really isn't any development here since everything is centered at Rootz. I can certainly understand a DISCUSSION thread in General, but all the actual development is over at Rootzwiki. Why not create a discussion thread in General and allow Imo to make his own thread in development if he so chooses to do so?
That's my 2 cents. Mods feel free to nuke my thoughts here if you'd like.
bobloblaw1 said:
I don't mean to be a jerk or step out of place, but ,there really isn't any development here since everything is centered at Rootz. I can certainly understand a DISCUSSION thread in General, but all the actual development is over at Rootzwiki. Why not create a discussion thread in General and allow Imo to make his own thread in development if he so chooses to do so?
That's my 2 cents. Mods feel free to nuke my thoughts here if you'd like.
Click to expand...
Click to collapse
I didn't want it to get lost in General and I asked him if he wanted me to make one or if he could make one over here for us and he told me to go ahead. I see where you are coming from though.
EDIT: If mods feel this should be elsewhere feel free to move it. I just figured this would be the best place to put it.
Yah i think it will be useful since half of the Rom threads are all about this kernal anyways there taking up way to many pages. There does need to be a seperate thread for it so good ups.
If you did not development nor can support it then it does not belong in Development
Thread moved
Also please show where the original developers authorized you to copy their material and links
Thanks
FNM
kennyglass123 said:
If you did not development nor can support it then it does not belong in Development
Thread moved
Also please show where the original developers authorized you to copy their material and links
Thanks
FNM
Click to expand...
Click to collapse
Sent you a PM with screenshots of imo and I's conversation.
Does anyone know how to get the phone to charge while it's off on this kernel? My phone will just vibrate but won't charge while off.
d1ez3 said:
Does anyone know how to get the phone to charge while it's off on this kernel? My phone will just vibrate but won't charge while off.
Click to expand...
Click to collapse
I have never tried to charge with the phone off. Beta just released about 20 minutes ago. Try that and see if it fixes it.
EDIT: Might have found the answer over on Rootz.
http://rootzwiki.com/topic/31329-imoseyon-beta-leankernel-tw-88-v01-kexec/page__st__260#entry870710
thanks, trying the beta now
No problem. I have the beta on my phone and it seems really solid so far.
this has already been covered in my guide...i think having multiple guide threadz for each and every rom/kernel is silly and confusing. which is why i made a all in one guide that covers all develpment and tweaks...what not. part of the reason i link to the original dev threads so users can keep up on the lastest there but ask questions in my thread.
droidstyle said:
this has already been covered in my guide...i think having multiple guide threadz for each and every rom/kernel is silly and confusing. which is why i made a all in one guide that covers all develpment and tweaks...what not. part of the reason i link to the original dev threads so users can keep up on the lastest there but ask questions in my thread.
Click to expand...
Click to collapse
I didn't realize there was a link to Imos kernel anywhere except inside of ROM threads so I figured I would duplicate his post here so people here would see. There is a whole lot of people who posted in the Synergy thread that they didn't know where his kernel was or where to find it and things like that. I figured the easiest way would be to have a post on XDA devoted to his kernel. If we had a mega thread of all the root methods, tools, ROMs, kernels, and themes then that would probably be better than this to help people find anything they may need for their phone with very little effort.
I'm assuming this wont work on the cm10 nightlies?
Will kexec kernels still work with an unlocked bootloader
Sent from my SCH-I535 using xda app-developers app
vx2ko said:
Will kexec kernels still work with an unlocked bootloader
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
yes. in their current form your device will still boot like 3 times though. There will be no change. In the next few days devs will be unpacking their zips and removing the kexec process. Now they just need to copy over any modules and dd the kernel to mmcblk0p7. But yes, these kernels will still work fine right now.
When the devs repackage them, however, you will no longer have to bootloop 3 times before booting with your custom kernel. it will load on first boot everytime, until you dd the stock kernel back to mmcblk0p7
When I flash nothing happens?
I just put on the Psycho ROM on my i9300 today and wanted to test this kernel out to see what 1.9Ghz feels like. I downloaded both the experimental and stable build.
I flashed the experimental build first, but my Siyah kernel still showed up. So I tried it again, but to no avail. Same incident with the stable build.
I notice when it flashes it seems like less than a second... I downloaded the experimental build v1.7 a few days ago, and its stable build today.
Any ideas?
Heatshiver said:
I just put on the Psycho ROM on my i9300 today and wanted to test this kernel out to see what 1.9Ghz feels like. I downloaded both the experimental and stable build.
I flashed the experimental build first, but my Siyah kernel still showed up. So I tried it again, but to no avail. Same incident with the stable build.
I notice when it flashes it seems like less than a second... I downloaded the experimental build v1.7 a few days ago, and its stable build today.
Any ideas?
Click to expand...
Click to collapse
Ask in the proper section this is for Verizon GS3.
Sent from my Galaxy SIII
Still getting WiFi drops on HD based Roms? Thats the only stopping me from using LK
TokedUp said:
Still getting WiFi drops on HD based Roms? Thats the only stopping me from using LK
Click to expand...
Click to collapse
Nope. Imo says not to use the latest (October 27) release on anything newer than G1.
Sent from my SCH-I535 using xda app-developers app
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 !
*** Latest Build 10-11-2013 ***
For d2vzw! Note the forum you're in!
If you're as big of a fan as I am of KToonsez's KT747 kernel then you'll be happy to know there is now an updated version.
This is a forked version of KToonsez's KT747 kernel with commits pulled from the CM10.2 branch of the d2 kernel.
Disclaimer: Standard disclaimer goes here. I nor KToonsez are responsible for the actions you take when working with your phone. I've done a significant amount of testing and so have others but situations arise where a hiccup could cause data loss, IMEI loss, or phone failure. You, the flasher, assume these risks. Please make sure you backup/nandroid, use nvbackup, etc.
Note:
It has been reported that this kernel will not work with 4.3.1 ROMs, notably the latest nightlies of PAC-MAN. If you're on a 4.3.1 ROM flash with extra caution. If you find otherwise please alert me.
Branch "currentCherry" (my cherry picking branch) CI status:
Branch "mr2" (KT's 4.3 branch) CI status:
Instructions:
There seems to be an odd permissions issue that we've uncovered. Follow these exact steps so when you boot you'll have working cell data:
Reboot Recovery
Clear Caches
Flash your current ROM
Flash kernel
Reboot
Profit!!!
I'm working on clearing this up. I've verified the above process against mastamoon's unofficial CM10.2 10/07 build.
Download Link:
10-11-2013
A big thanks to shane269 for helping me test this from a bootlooper to working kernel!
Thanks!
KT747's sources can be found here:
https://github.com/ktoonsez/KT747-JB
Visit the official KT747 thread here:
http://forum.xda-developers.com/showthread.php?t=1853816
Visit kt's original, ORIGINAL kernel thread here:
http://forum.xda-developers.com/show....php?t=1756776
Also if you like this kernel then please consider donating to the dev that made it all happen, ktoonsez: http://forum.xda-developers.com/donatetome.php?u=4325945
Previous Builds
10-10-2013
10-09-2013
XDA:DevDB Information
KT747 For D2VZW Cherry Picked, a Kernel for the Verizon Samsung Galaxy S III
Contributors
mikejr83, KToonsez
Kernel Special Features: KT747 kernel with latest CM10.2 commits
Version Information
Status: Beta
Created 2013-10-09
Last Updated 2013-10-16
Change log:
-10/11/2013
* Merged the commit for touchscreen optimizations
* Cherry-picked commit for reverting portions of the touchscreen optimizations which may cause us camera issues.
* Changed updater-script to hopefully resolve issue with no data after flashing (still researching issue)
First?
Looking forward to this
tapped from a carbonized d2vzw
ktoonsez gave the OK. Download link is now up. Please follow the instructions or you'll get no data. If you accidently goof and do this just reflash your ROM and then in the same session flash the kernel.
Thanks!
Mike
Thanks for this I've been using this without issues pacman ROM.
Sent from my SCH-I535 using Tapatalk 2
Just flashed on Slim 1.6 weekly and set my kernel settings. No initial issues, thanks for the update. I was going through kernel flashing withdrawals.
Sent from my SCH-I535 using Tapatalk 4
Well @mikejr83 so far so good, thanks for the update!
sent from a custom s3 powered by pacman, ROM ,KT747 kernel w/mods by team kernelizers ,themed by blackout1911,Pimped by the candyshop, and modded by all!
Is anyone not seeing OC working? I have mine set to 1728 but I'm still seeing 1510 in BBS.
Sent from my SCH-I535 using xda app-developers app
mikejr83 said:
Is anyone not seeing OC working? I have mine set to 1728 but I'm still seeing 1510 in BBS.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I normally don't overclock my phone doesn't do well with it. I tried 1728 and it wasn't ever using it. Then I bumped it up to 1809 and it instantly rebooted. As expected, my processor just won't do it. After the reboot the phone was still set at 1728 and it was using that frequency. So maybe requires a reboot work?
Sent from my SCH-I535 using Tapatalk 2
Rebooting seems to make it stick or show up in the apps where I see freq values.
Sent from my SCH-I535 using xda app-developers app
OP Updated
Went through my cherry pick branch and realized I missed some commits. I missed about 2 days worth of merges at the end of August. These are now all added.
There is a gerrit reviewed commit for touchscreen optimizations (and a subsequent fix for camera issues). I'm having trouble merging this commit into my branch. I'll try to get that into the build for tomorrow.
Thanks!
Mike
Can I ask why there is a unofficial version of KT kernel? Did he drop support for s3?
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Rinkle McBally said:
Can I ask why there is a unofficial version of KT kernel? Did he drop support for s3?
Click to expand...
Click to collapse
He's just been really busy and this guy wanted to put a more recent build out since there have been many commits to cm 10.2
Sent from my SCH-I535 using Tapatalk 4
---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------
Are we able to flash the kernel separately yet?
Sent from my SCH-I535 using Tapatalk 4
no cigar said:
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Click to expand...
Click to collapse
Shoot! Ok. Just want to ask a couple of questions to make sure I'm on the same page and I can collect some info to try and figure this out.
10/10 build? Probably a silly question since you posted after I posted the new build, but just checking.
Are you using CWM? If you are what version?
Just to be clear, are you flashing ROM and then the kernel in the same recovery session?
I'm not familiar with liquidsmooth. Is the 2.10 release version 4.3 of Android? I'm assuming it is otherwise you probably would have gotten a bootloop instead of no data.
Thanks for the feedback. It's important that I see these. I've been worried sick that there are people downloading this, having this problem, and immediately thinking that I through out something that is bunk. I want this effort to live up to the expectations that everyone has for KT's kernel. Last thing I want to do is turn people off to his great work!
jamminjon82 said:
He's just been really busy and this guy wanted to put a more recent build out since there have been many commits to cm 10.2
Sent from my SCH-I535 using Tapatalk 4
---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------
Are we able to flash the kernel separately yet?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I was able to flash 10/10 over 10/09 without having to flash the ROM and still have data. I have not gone from sans KT to ROM with KT on the 10/10 build.
I'm going to try to get some input from some devs. I originally thought it was the updater-script applying the wrong permissions during the flash. I did, however, change the script to mimic more how LeanKernel does its flash but that fix was put in 10/09. This along with the touchscreen fixes are my top priorities to get fixed.
See responses below. Thanks!
mikejr83 said:
Shoot! Ok. Just want to ask a couple of questions to make sure I'm on the same page and I can collect some info to try and figure this out.
10/10 build? Probably a silly question since you posted after I posted the new build, but just checking.
Yep 10/10 for sure.
Are you using CWM? If you are what version?
Yes. 6.0.4.3
Just to be clear, are you flashing ROM and then the kernel in the same recovery session?
Yes, all in the same session
I'm not familiar with liquidsmooth. Is the 2.10 release version 4.3 of Android? I'm assuming it is otherwise you probably would have gotten a bootloop instead of no data.
Correct. I'm running android 4.3
Thanks for the feedback. It's important that I see these. I've been worried sick that there are people downloading this, having this problem, and immediately thinking that I through out something that is bunk. I want this effort to live up to the expectations that everyone has for KT's kernel. Last thing I want to do is turn people off to his great work!
I was able to flash 10/10 over 10/09 without having to flash the ROM and still have data. I have not gone from sans KT to ROM with KT on the 10/10 build.
I'm going to try to get some input from some devs. I originally thought it was the updater-script applying the wrong permissions during the flash. I did, however, change the script to mimic more how LeanKernel does its flash but that fix was put in 10/09. This along with the touchscreen fixes are my top priorities to get fixed.
Click to expand...
Click to collapse
Eclipse build 6
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Quie2TP said:
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Click to expand...
Click to collapse
^
SAME
New build in the OP.
Also, changelog is in the second post.
no cigar said:
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Click to expand...
Click to collapse
Quie2TP said:
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Click to expand...
Click to collapse
grislieber said:
^
SAME
Click to expand...
Click to collapse
Thanks for the reports guys. Researching this issue is proving difficult as no one seems to have documented it in the "usual" places. The only suggestion I have so far is checking to make sure the permissions are correct on everything that is flashed. I took a look at a couple of other kernel dev's updater-scripts and tried to modify this one accordingly. Flashing from 10/10 to 10/11's still gave me working data. I'm trying to follow up with a few other devs so please don't think that I'm not working on this. If you flash 10/11 please report your findings!
Thanks!
List all Questions and Off-Topic discussions here
Welcome to VanirAOSP. Our mission is to deliver a clean optimized version of Android to as many devices as possible. This is not a kang rom. You will find versions of the features you love that we've rewritten and improved on plus a few we wrote ourselves. we've tried to acheive a more organized and cohesive setup to improve the user experience while correcting any performance regressions and improving functionality.
If you're the kind of person that needs options to change the font and color on every letter and expect the ROM to end up looking like kid's cereal box then GTFO. You will not find customizations that are done just because someone figured out how to do them. Everything in here has a purpose and is held to a high standard of coding.
General features:
stock mode - ability revert to stock AOSP code with the exception of a few custom features we chose to keep active
enhanced performance.. longer uptime with less slowdown
custom written CRON and init.d.
minor UI and graphics improvements
custom navbar, navring, and hardware key features
active notifications (improved active display + lockscreen notifications)
usability improvements like power reboot menu and sound
animation control
Improved Vanir keyboard
CM's profiles & quicksettings
additional quicksetting tiles
immersive desktop <- fully configurable immersive mode
low profile mode
statusbar mods
clock & battery mods
lockscreen blur and other mods
soon to come -> quick cam and flash notifications
busybox, embedded root, init.d, cron etc
many improvements and new features unique to vanir
more to come when i feel like updating the op
issues:
- stop flashing the moto X binaries. they do not improve anything for you and aren't even for your device.
- open source camera and launcher3 do not have the same featuers as the google versions. use the latest
banks standard gapps if you'd like these. His gapps are super legit and always up to date.
Join our Google+ community for news/updates
Nightly downloads are available on our google+ page or directly from our server
if you're interested in becoming a maintainer.. or just need help please send an email to [email protected]
Download:
http://www.emccann.net/nuclearmistake/VanirAOSPNightlies
Check Vanir Updater for updates daily
Gapps: http://goo.im/devs/BaNkS/GApps i recomend Banks Gapps
Experimental (These are downloads built by me that are not official and may or may not be stable but your welcomed to test them and give feedback)
http://downloads.codefi.re/ethanj99/vanir_evita
Please Consider Rating this thread 5 Star and press the like button
Credits:
Vanir
Slim ROMS
AOKP
AOSP
PAC-Man
codefireXperiment
Code Aurora Forum
DHOMD
nuclearmistake
Jason Downing
PrimeDirective
LorDClockan
tbalden
pingpong
Rc420head
Flashalot
Source:
ROM Source: https://github.com/VanirAOSP
KernelSource: https://github.com/CyanogenMod/android_kernel_htc_msm8960
if you want a clean aosp rom than go into development settings on this rom and enable stock mode and reboot!
List all Questions and Off-Topic discussions here
MINE!!!!!!!!!!!
MINE!!!!!!!!!11
Vanir q&a/t thread:
http://forum.xda-developers.com/showthread.php?t=2797109
Sent from my Evita
Remember all development related questions and comments and bug reporting can be here in this thread. things like questions on how something works or why something happens or descussion about the rom should go in the Q&A thread
Scozzar said:
There is no camera on the 8/15 build? What.
Click to expand...
Click to collapse
List all Questions and Off-Topic discussions here
I flashed the latest nightly (0819) and WiFi seems to be broken...it doesn't even turn on. Great ROM otherwise it's smooth as butter
Edit : torched 4.8 fixed WiFi for me now this ROM is perfect
nicolahaye said:
I flashed the latest nightly (0819) and WiFi seems to be broken...it doesn't even turn on. Great ROM otherwise it's smooth as butter
Edit : torched 4.8 fixed WiFi for me now this ROM is perfect
Click to expand...
Click to collapse
Confirmed.
Edit: Will try torched, did you flash after flashing Vanir, or reflash?
CyanJustice said:
Confirmed.
Edit: Will try torched, did you flash after flashing Vanir, or reflash?
Click to expand...
Click to collapse
I flashed ROM yesterday and WiFi was broken and today I flashed only kernel (torched 4.8) and WiFi is working
I have to say, this ROM is very impressive! Great UI tweaks, very fast, ART works very well. The only bug I've noticed is my cell signal goes out completely for a few seconds every once in a while. Otherwise, very awesome indeed!
Sent from my One X using XDA Premium 4 mobile app
Is this ROM discontinued ? I haven't seen any nightly since 0819...
nicolahaye said:
Is this ROM discontinued ? I haven't seen any nightly since 0819...
Click to expand...
Click to collapse
The latest nightly is pretty stable, been having no issues whatsoever, except the need to flash a new radio every few days or so, but that could just be due to my own location.
Sent from my One X using XDA Premium 4 mobile app
CyanJustice said:
The latest nightly is pretty stable, been having no issues whatsoever, except the need to flash a new radio every few days or so, but that could just be due to my own location.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And also WiFi doesn't work on stock kernel. Only working with torched 4.8. I guess it's related to the latest changes with the WiFi. When I first flashed the ROM it didn't work so I flashed torched to fix it but I've had a lot of random reboots since 3-4 days so I just got back on stock kernel only to remember WiFi is broken.
Edit : still getting random reboot also on stock kernel. I'll try and grab a last_kmsg next time it happens.
nicolahaye said:
And also WiFi doesn't work on stock kernel. Only working with torched 4.8. I guess it's related to the latest changes with the WiFi. When I first flashed the ROM it didn't work so I flashed torched to fix it but I've had a lot of random reboots since 3-4 days so I just got back on stock kernel only to remember WiFi is broken.
Edit : still getting random reboot also on stock kernel. I'll try and grab a last_kmsg next time it happens.
Click to expand...
Click to collapse
Well that's odd, I don't get reboots at all. Maybe that's because of an app incorrectly allocating memory?
Sent from my One X using XDA Premium 4 mobile app
CyanJustice said:
Well that's odd, I don't get reboots at all. Maybe that's because of an app incorrectly allocating memory?
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have no idea :s I got a last_kmsg but I can't post it from this app I'll do it as soon as I'm near my computer I don't quite understand what it's saying.
nicolahaye said:
I have no idea :s I got a last_kmsg but I can't post it from this app I'll do it as soon as I'm near my computer I don't quite understand what it's saying.
Click to expand...
Click to collapse
Have you updated to the newest nightly?
Sent from my One X using XDA Premium 4 mobile app
CyanJustice said:
Have you updated to the newest nightly?
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I haven't but I will as soon as possible. I didn't know there was a new built. I'm actually on 0819 I'll let you know
I installed the 0902 nightly via vanir updater and WiFi now works very well I still get random reboots though, here's the last_kmsg I grabbed while on 0819 nightly, i'll try to grab another one while on the latest as well.
Newest nightly refused to boot for me.. Just endlessly sat on the Vanir splash screen.
Vanir 4.4.4 build required
Hi,
I see that the last vanir build for evita for 4.4.4 was this vanir_evita_4.4.4.112414
But the official repo for vanir only hosts 5.0 builds. If somebody has it downloaded can you please send it to me.
Any help is much appreciated.
TIA!
I love AOSP ROMs but the latest nightlies that I've installed have crashed right after the boot. Please, look into that.
Thanks.
Sent from my One X