Related
I noticed some Kernels have different issues with wired headset.
Headset cuts my voice during voice calls
Auto dials and auto pulls call log
Headset button doesn't work
anyone notice strange behavior with your headset plugged in? Lets make a list of issues to make it simpler for devs to find a solution.
Any solutions? (one is to use stock kernel which is linked in this thread)
Post your issues with wired headset and please note which kernel is acting up. maybe we can combine code from different kernels to make one that works. (I noticed that some kernels have one issue but not the other)
Thanks for all your support and great work everyone is doing on the Epic!
Yes, I noticed the behavior between different kernels (using stock ROM). I know for a fact that with Xtreme Kernel, it disconnects my calls whenever I plug in my headset. The devs say to use only with ACS ROM, but given that the kernel is the bridge between the hardware and software, I doubt the ACS ROM would fix the issue.
I forgot what happened with the other kernels. I settled with Pheonix for now at the conservative governor (interactive sometimes leaves the CPU running at 100MHz and wont ramp up).
Seems we wont be getting any fixes for a while. All the kernel devs are having too much fun playing with Froyo.
Glad I am not the only one! Lets see if we can work this out! Using your phone without headset will give you BRAIN CANCER! Plus its more convenient with a headset when I have to deal with clients.
had problems using epic experience w/ mixup kernel and the latest Xtreme
I can confirm that wired headset handling is kind of fubar in our community kernels. Samsung had made some bugfixes between DI07 -> DI18 versions, but those changes don't appear to have been added to the DI18 source code.
Have any of you tried using the stock DI18 kernel to test this? If it works properly, then we have to cross our fingers and hope the issues don't persist in the kernel shipped with Froyo - as it stands there's no way to know what changed to fix this stuff easily in our community kernels.
The only time I ever gotten headset to work with phone mic was using stock rom and stock kernel after an odin.
effudee said:
The only time I ever gotten headset to work with phone mic was using stock rom and stock kernel after an odin.
Click to expand...
Click to collapse
Yep, that's the exact issue with the missing changes in the source Samsung released.
effudee said:
The only time I ever gotten headset to work with phone mic was using stock rom and stock kernel after an odin.
Click to expand...
Click to collapse
It's only the custom kernel(s) that cause this issue...flash whatever rom you want, flash the stock kernel and you should be good to go...
also, FYI, already a thread on this issue here:
http://forum.xda-developers.com/showthread.php?t=771861
any link to stock Kernel? would be good if we could find a solution for the custom kernels, Is there any other way to install stock kernel besides restoring stock rom through ODIN?
lucifermoh said:
any link to stock Kernel? would be good if we could find a solution for the custom kernels, Is there any other way to install stock kernel besides restoring stock rom through ODIN?
Click to expand...
Click to collapse
Don't recall where I got it from but here is the stock DI18 kernel...
ScientificOne said:
It's only the custom kernel(s) that cause this issue...flash whatever rom you want, flash the stock kernel and you should be good to go...
also, FYI, already a thread on this issue here:
http://forum.xda-developers.com/showthread.php?t=771861
Click to expand...
Click to collapse
Oh really? I remember trying andromeda with stock kernel and it still didn't work for me. I'll try Syndicate with stock kernel eventually then. Thanks for the information
thanks for the zip!!! any idea if devs are aware of this issue?
lucifermoh said:
thanks for the zip!!! any idea if devs are aware of this issue?
Click to expand...
Click to collapse
I doubt it. I posted my bug on the Xtreme Kernel thread and Devin never responded. The only response I got was to use a specific ROM .
Yes, well at least this one is. I'm examining the audio right now to try and hunt down a fix for this and the bluetooth routing bug.
The leaked 2.2 still has the bluetooth bug afaik. I'm hoping samsung releases this fix with their source next time.
Using extreme kernel and when i plug in AUX cable for audio to my car it isnt recognized as a headset.
You mean it doesn't pop the icon in the notification bar, or that it doesn't play audio?
Nothing I plug in pops the headset icon when using a custom kernel - not even the wired headset. Pretty sure it's another symptom of the bug.
[edit] Nor in the froyo stock kernel. /shakes fist at samsung!
This is really weird as my phone keeps rebooting especially when i'm on a somewhat lengthy phone call. The phone will turn dark and when i move it away from my ear the light will not come back on. About 30 seconds or a minute later, the phone reboots. This is so annoying and am looking for a solution. I heard that manually rebooting your phone can help out. Any other solutions that can help with this situation?
Ok,
Are you rooted?
If so, what ROM are you running?
What Kernel are you running?
The more details about the phone, the better
Regards,
UselessSniper001
rjones9902 said:
This is really weird as my phone keeps rebooting especially when i'm on a somewhat lengthy phone call. The phone will turn dark and when i move it away from my ear the light will not come back on. About 30 seconds or a minute later, the phone reboots. This is so annoying and am looking for a solution. I heard that manually rebooting your phone can help out. Any other solutions that can help with this situation?
Click to expand...
Click to collapse
Need a bit more information. Rooted? ROM? Kernel? Up time before reboots start?
Sorry GIS but had to head out for a minute. Anyway I'm rooted and running Slim 2.9 ROM. My dumbass pretty much leaves my phone on and now think that's why I'm having this issue.
And in using the kernel which is included in the ROM, which is the Bedalus Marmite kernel.
Sent from my GT-P3113 using xda premium
rjones9902 said:
Sorry GIS but had to head out for a minute. Anyway I'm rooted and running Slim 2.9 ROM. My dumbass pretty much leaves my phone on and now think that's why I'm having this issue.
And in using the kernel which is included in the ROM, which is the Bedalus Marmite kernel.
Sent from my GT-P3113 using xda premium
Click to expand...
Click to collapse
Have you tweaked anything on the ROM like over clocking, under clocking etc. If so please specify to what extent as well.
Regards,
UselessSniper001
UselessSniper001 said:
Have you tweaked anything on the ROM like over clocking, under clocking etc. If so please specify to what extent as well.
Regards,
UselessSniper001
Click to expand...
Click to collapse
No basically i have kept everything as is. No over or underclocking. And don't know if i have said it already but i am rooted. Now i'm running the SlimBean ROM and thus far it has not given me any trouble but still am wondeering what could be causing the problem.
rjones9902 said:
No basically i have kept everything as is. No over or underclocking. And don't know if i have said it already but i am rooted. Now i'm running the SlimBean ROM and thus far it has not given me any trouble but still am wondeering what could be causing the problem.
Click to expand...
Click to collapse
Random reboots are a reported thing with Marmite that is being worked on. Try flashing another kernel like Matr1x. Us the CM cfs version. Flash it and let it settle in and report back in a few days. Marmite uses bigmem and not every phone agrees with it.
Let me know the turnout.
mdean1981 said:
Random reboots are a reported thing with Marmite that is being worked on. Try flashing another kernel like Matr1x. Us the CM cfs version. Flash it and let it settle in and report back in a few days. Marmite uses bigmem and not every phone agrees with it.
Let me know the turnout.
Click to expand...
Click to collapse
+1
And let me know as well.
mdean1981 said:
Random reboots are a reported thing with Marmite that is being worked on. Try flashing another kernel like Matr1x. Us the CM cfs version. Flash it and let it settle in and report back in a few days. Marmite uses bigmem and not every phone agrees with it.
Let me know the turnout.
Click to expand...
Click to collapse
To mdean and Useless Sniper:
Again i want to thank both of you for your help. I flashed the Matr1x 24.0 CFS CM kernel and thus far it's working out great. granted it's only been roughly 12 hours but i had made calls without any reboots or any problems. I'm still keeping my fingers crossed but i'm sure with all the knowledge and info you guys gave me, this will probably be the end of my troubles. Thanks again.
Sorry about that. Reboots seem to be solved. Next version of slim should be fine.
Standard disclaimer:
I do not guarantee that modifying your original software will not destroy your device. I do not promise to provide support to those with issues. However, this is a community and any kindness effort that you put into your inquiries and questions will likely be returned. Good luck.
Background:
As an owner of the T-Mobile D801, I realize the apparent lack of specially catered ROMs for the device. I will provide some background. It is possible to install all other G2 variant ROMs on the device, however many of these will bring with them issues. For example: ATT's (D800) extra microphone will break speaker phone on the D801, as well as cause other audio issues. Verizon's ROM is generally unstable due to the different hardware it employs. The Canadian versions, I have not tested myself, but so far have seen no Canadian-made ROMs that are better than the International counterparts.
The exception, of course, is the International variant: D802. As far as I've found, all functions on D802 ROMs work fine on the TMO D801 device. You'll just need to flash a D801 kernel over the D802 ROM.
This guide is not intended for the seasoned XDA warrior. It is simply aimed at the average D801 owner who's looking to flash some custom ROMs, only to find that he doesn't have the best selection among all the G2 variants.
Issues:
PAC ROM for D802 doesn't work using this method.
Data may not work initially due to bad settings. First, check to make sure that your APN Settings are correct. If your APN settings are all set and you're still having issues with LTE vs. UMTS/HSPA+, try changing your network mode to include LTE. Of note, a build of Vanir was having issues with data at the time of writing, so if you cannot fix your issue, try another ROM.
The only thing that I've not seen in custom ROMs based off of anything other than LG's D801 stock is WiFi calling. If you use WiFi calling, following this advice will take away that feature. To retain WiFi calling, you will need to stick to near stock. Please, if I am in error about this fact, PM me and let me know, or reply below.
Your device's build.prop will identify as a D802 from now on. You may choose to edit this back to D801. Either way, don't trust OTAs or device-specific quirks like open-recovery scripts. It's your job to be a little cautious, and avoid automation that could brick your device. Always have at least one NANDroid backup to return to.
How this works:
Very simply, the most device-specific aspect of these ROMs is the kernel (boot.img). It controls very base-level functions such as managing where boot pointers lead to and providing hardware control. G2 kernels do not mix-and-match from one device to the other. After installing a D802 ROM, you now have a completely incompatible D802 kernel. You must install a D801 kernel to fix that. Afterwards, everything generally seems to work fine. If you can find any issues, report back here.
HOWTO: Install an International LG G2 D802 ROM on the T-Mobile LG G2 D801 device.Requirements:
You must have a custom recovery (like TWRP) installed.
As far as I've seen, you also need to be rooted (IOroot method) before installing a custom recovery on this device.
Instructions:
Download the D802 ROM of your choice. [Warning: PAC ROM for D802 doesn't work]
Download a kernel made for the D801.
For stability, you may use your stock kernel for LG ROMs (backing up/restoring just "boot" in recovery --> that's the kernel), or an AOSP-friendly stock, as built by Houstonn
For features, Custom G2 is a great modified kernel. It includes a D801 version for both Stock LG-based ROMs, as well as AOSP-based ones.
Reboot into recovery.
[Optional, but strongly recommended] Perform a NANDroid Backup, in case anything goes awry. Backup at least System, Boot, and Data.
Perform a Factory Reset, then wipe cache & dalvik cache.
Install the D802 ROM, including Gapps if needed. DO NOT REBOOT.
Immediately install the D801 kernel.
Reboot.
Enjoy.*
If you ever update your D802 ROM, through .zip or per-ROM OTA, you must always flash a D801 kernel afterwards.
Troubleshooting:
*It may take a while to get by your first boot. I've personally never had the first boot take longer than 2 minutes or so. If it takes upwards of 10 minutes, then try forcing a reboot by holding the power button. If the device still won't boot, something must have gone wrong. Reboot into recovery by holding the power button until the screen goes black, then hold Vol-Down & Power, and when the LG logo appears, release and re-press/hold this key combination. You will arrive at a screen offering a factory reset. Just press the power button twice, ignoring the warnings, and you will boot into recovery. Restore the NANDroid backup you made earlier.Your phone should boot now. You may attempt to try the whole thing again. Post the combo that gave you issues to this thread. Again, this has never happened to me when following the correct procedure. An issue I could see is attempting to use an AOSP-friendly kernel with an LG Stock-based ROM, or vice-versa.
If you are having issues with data, see the "Issues" section above for my recommendation: APN Settings.
-----------------------
I've been running D802 ROMs for weeks, without any abnormal issues, including CleanROM, Vanir AOSP, AOKP, and CM.
Which ROM works best for you? I'm about to try CM M1 for D802..
Sent from my LG-D801 using xda app-developers app
.BetaBoy said:
Which ROM works best for you? I'm about to try CM M1 for D802..
Click to expand...
Click to collapse
Works best? None. They are all rather stable.
Out of all the CM-based ROMs I tried for the G2, my personal preference turned out to be VanirAOSP. I like the default task chooser (AOKP uses an alternative), the features it kanged from other ROMs, such as the swipe-to-switch between quick toggles & notifications, the navigation bar settings (taken from AOKP), and more. Of course, all ROMs have their own little quirks and feels.
I personally don't need PIE or Halo, as I find that a higher DPI (400-440 instead of stock 480) and a smaller Nav Bar fix my screen real-estate issues. That's why I don't invest time into Paranoid Android. However, some people swear by Paranoid.
AOKP is great if for nothing other than their organization.
CM is wonderful because of its legacy.
SlimBean has a system-wide dark theme and some ICS-like features that some people love to hold onto.
VanirAOSP is newer and took a lot of the features I liked from AOKP and merged them with the stability of CM.
There are other options. Try going down different roads. You'll see what you like.
Altogether I'd sum up by saying that the cores are something like:
CM: stability and uniformity.
AOKP: throw a lot of features at the wall, see what sticks.
PA: radical earth-shattering features, which some may or may not like.
Others: Usually a combination of all of the above. Read the descriptions.
Also: new kid on the block is OmniROM. It looks like it'll be great, but as of yet isn't completely polished. I'm excited for their 4.4 release!
Well I can confirm that the M1d802 cm ROM works with d801 kernel, seems like signal is a little weaker though!
Sent from my LG-D802 using xda app-developers app
.BetaBoy said:
Well I can confirm that the M1d802 cm ROM works with d801 kernel, seems like signal is a little weaker though!
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
What about sound quality? When I tried AOSP 801 Roms the sound seemed distorted at times and people on the other end seemed to notice a difference.
The radios/modems don't get overwritten with a flash, so that's strange that you'd have varying signal quality. I'm on WIND in Canada, so I can't really vouch as to how TMO's signal quality is on different ROMs. I've noticed, though, that my WIND experience has been pretty similar on everything except a D800 ROM, which really messed with loudness levels and quality, due to the microphone differences.
Effectively on a D800 ROM I had these issues:
-Earpiece is BLISTERING loud. Lowest volume, too loud for comfort. Highest volume, can hear from the next room.
-Generally quiet. I need to speak into the mic directly, lest I not be heard.
-Non-functioning speakerphone. I can hear the other end, but they can't hear me.
So your back using a stock T-Mobile Rom now though? I'm fine with the Buckeye Rom but do miss flashing Roms like I did with the S4. Did you try the Omni Rom? What about MIUI? I kind of like to change things up. Thanks for the this thread I was wondering if this was possible.
sweets55 said:
So your back using a stock T-Mobile Rom now though? I'm fine with the Buckeye Rom but do miss flashing Roms like I did with the S4. Did you try the Omni Rom? What about MIUI? I kind of like to change things up. Thanks for the this thread I was wondering if this was possible.
Click to expand...
Click to collapse
Haha, you sound excited. I'm using a stock T-Mo ROM for the Camera app and the battery, but I am really just waiting for the 4.4 ROMs to roll in. I'm pretty certain that the OmniROM and MIUI will work fine, so make a backup and go try them!
You might also want to include more of a vanilla kernel in your guide, modified kernels are not for everyone and often go under heavy changes and development at anytime which often make them unstable. Houstonn has kernels built for all our devices, I'd suggest to recommend those as they are far more likely to have less issues than a modified kernel.
http://forum.xda-developers.com/showthread.php?t=2502789
slayer3032 said:
Houstonn has kernels built for all our devices, I'd suggest to recommend those as they are far more likely to have less issues than a modified kernel.
Click to expand...
Click to collapse
Added to OP.
THANK YOU
Thank you for figuring this out! I am flashing the latest CM 10.2 nightly (11/11) with Houstonn's AOSP kernel and will report back with any issues in this thread.
Maybe it's time I start dev'ing again, let the endless downloading, installing and setup begin!
And I just cleaned everything up with a fresh install.
I hate you Android... I was so close to getting away... DAMM YOU!
Flashed VanirAOSP 802 build. I was bit worried because it seemed to take longer to flash. Guess I flashed the wrong kernel since I have no data. WiFi works. I also can't figure out how to rearrange the nav buttons. I like the back button on the far right instead of left.
sweets55 said:
Flashed VanirAOSP 802 build. I was bit worried because it seemed to take longer to flash. Guess I flashed the wrong kernel since I have no data. WiFi works. I also can't figure out how to rearrange the nav buttons. I like the back button on the far right instead of left.
Click to expand...
Click to collapse
Vanir should have nav bar settings... But data is probably APN settings. Are you on TMO? See the documentation on TMO's site: http://support.t-mobile.com/docs/DOC-2090
Set up your APNs, report back. None functioning data would be pretty bad.
EDIT: also kernel should not really affect data. If your signal is working but without data, it is almost always missing APN settings and sorry about the formatting on this reply... This is from my Nexus 7
sweets55 said:
Flashed VanirAOSP 802 build. I was bit worried because it seemed to take longer to flash. Guess I flashed the wrong kernel since I have no data. WiFi works. I also can't figure out how to rearrange the nav buttons. I like the back button on the far right instead of left.
Click to expand...
Click to collapse
I flashed vanir and no data, set correct APN, Change network type by dialing *#*#4636*#*# to LTE/GSM not LTE GSM WCDMA
i had to change networks like 3 or 4 times til data kicked in
Working solid now
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
I flashed the official PAC man rom and flashed wootevers custom kernel and it never booted
stuck on animation screen, can anyone confirm OFFICIAL PAC working with WOOTEVERS CUSTOM KERNEL ?
I got data working but keeps bouncing around 3G and H+. What kernel should I be using. Thanks guys.
Sent from my LG-D802 using xda app-developers app
sweets55 said:
I got data working but keeps bouncing around 3G and H+. What kernel should I be using. Thanks guys.
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
I'm getting the same problem on the CM 10.2 ROM. I can't get it to connect to 4G or LTE. I've changed my APN and set the connection type to LTE and still nothing. It was doing the same thing on Vanir as well, any ideas?
ska8tdude said:
I'm getting the same problem on the CM 10.2 ROM. I can't get it to connect to 4G or LTE. I've changed my APN and set the connection type to LTE and still nothing. It was doing the same thing on Vanir as well, any ideas?
Click to expand...
Click to collapse
I changed the APN to fast.T-Mobile.com but didn't help. Have no idea. Sorry.
Sent from my LG-D802 using xda app-developers app
Forgot this.
Sent from my LG-D802 using xda app-developers app
No lte here :/
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.
Hi i am currently using Cm12 Nightly 5.0.3 030315, With cm stock kernel. When i play audio thru my car Bluetooth it skips after ever 5 to 10 sec. If i watch video, the audio is delayed. The audio works perfect on regular bluetooth headset. The troubleshoot i did fix this problem so far.
Tried ever build after 02/21 till now still same thing.
I tried custom kernel like franco and elementalx. Did changes in hotplug while using franco kernel. Change Processor setting to performance under cyanogenmod. I have been trying find the fix but with no luck. The only thing that works is if i go back to cm11. Once i do that everything is normal.
Side Note, Every time i installed the Rom it was clean install.
Any help is appreciate at this moment. Thanks in advance.
No such issue here. Try full wiping and then reflashing CM.
thanks for reply. I did that several time. But with no luck. Any other suggestion ??
avalanch said:
thanks for reply. I did that several time. But with no luck. Any other suggestion ??
Click to expand...
Click to collapse
I recently had BT issues on CM12 and I do think that's a rom issue. Other users also reported bugs with BT.
Flash every nightly until the fix comes or switch to another custom rom for the moment.
Primokorn said:
I recently had BT issues on CM12 and I do think that's a rom issue. Other users also reported bugs with BT.
Flash every nightly until the fix comes or switch to another custom rom for the moment.
Click to expand...
Click to collapse
Thanks for that info. Good to know i am not the only one. I am on a mission of trying all the Cm12 Nightly from jan onward till today. Hopefully 1 of them will work... Any suggestion for most stable of nightly is appreciated. Thanks. Trying different roms too.
avalanch said:
Hi i am currently using Cm12 Nightly 5.0.3 030315, With cm stock kernel. When i play audio thru my car Bluetooth it skips after ever 5 to 10 sec. If i watch video, the audio is delayed. The audio works perfect on regular bluetooth headset. The troubleshoot i did fix this problem so far.
Tried ever build after 02/21 till now still same thing.
I tried custom kernel like franco and elementalx. Did changes in hotplug while using franco kernel. Change Processor setting to performance under cyanogenmod. I have been trying find the fix but with no luck. The only thing that works is if i go back to cm11. Once i do that everything is normal.
Side Note, Every time i installed the Rom it was clean install.
Any help is appreciate at this moment. Thanks in advance.
Click to expand...
Click to collapse
I have the same problem with a 32GB nexus 5 and the recent cm12 nightlies, I have found a dozen or so forums/pages about the problem but nothing that seems to help. I have tried flashing different radio.img file and different kernels, the problem only happens in my car, my bluetooth headphones and everything else works fine. My car can take phone calls but not play back music/audio from anything without skipping every 5-10 seconds for ~1 second
That's because CM team still don't get, that it's better to start building a house from the ground, then from the roof. It's a kernel related issue.