Database Info

[Q] Problem with 1.6 Kernel

I Know this should be in the Developer section, but I don't have enough posts. (Since you have to have at least 10 to do so...)
BUT, I installed a kernel from Blades which is the 1.6ghz with the latest version of CWM. The problem is that whenever I try to boot up the device it just stays on the first startup screen, and it also makes a weird popping noise from the speakers about every 10 seconds. I did wipe Dalvik Cache and I also made a back up before installing the new kernel. I've tried restoring but it does the same thing every time. Before installing the kernel I was running PRIMEORDIAL! v3.1...
Any help would be greatly appreciated....
Thanks
cdp

Hi Mate, You are not the only one. Unfortuantely 3.0.1 kernels don't work too well with 3.1 roms as you have discovered.
Not to worry though as this is an easy fix.
Simply flash the 3.1 stock kernel and you're up and running again. You can get it from here... http://forum.xda-developers.com/showpost.php?p=14283676&postcount=94

Wow, I didn't even realize that kernel was only for 3.0.1 lol. THANK YOU! Flashed it and it started right up! C:

You may now have wifi problems, since the kernel update will have installed a different module to the one you need, if this is the case just reflash whatever rom you are using.

Okay cool, I'm on wifi now and it seems to be working fine. So thanks again! :]

Issues with installing certain ROMS [SUCCESS!!!]

Some of the user's here, myself included, have been having issues installing any ROMs/ kernels built by Faux. What I'm trying to do is pinpoint the exact cause of this and hopefully rectify the issue.
I'm currently downloading all available ROMs and will install each to determine which are flashable and which are not.
Flashing Procedures
0. Boot into CMW Recovery: External with EXT 4 support using volume down + power method
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik
4. Format /System
5. Flash ROM
6. Select Power Down from CMW Menu
7. Power on phone without wall charger plugged in
ROM List:
Bionix- Confirmed as working
EagleBlood GB- Confirmed as working
EagleBlood FR- Confirmed as working
Ultimate- Confirmed as working
Light&Sinister- Confirmed as working
Dark&Sinister- Confirmed as working
Faux AOSP-NOW WORKING!!
CM7- Confirmed as working
LG Stock- Confirmed as working
Observations:
Bionix converts /system and /data to ext3. I figured that if the issue we were having with Faux was due to format errors then I could just flash Faux over Bionix and it would boot. In testing, it seems like Faux gets further when flashed this way but still refuses to boot. Before I would only get the initial LG screen and then it would black out. Now I can get to the second LG screen with blue background but it hangs there. Will run logcat to see what is causing the freeze once I get logcat running again.
My current theory is that there is a difference in the boot.img that Faux has built for his ROM that will not boot correctly. I have the same issue with his kernels as well. They boot to the first LG splash screen and then the screen shuts off. Still struggling with my logcat issue so I'm at a standstill until that is fixed.
Development:
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Morfic's CM7 kernel. I personally believe this definitely proves that there is something in Faux's boot.img that doesn't function properly on all devices.
At Faux's suggestion, I flashed his Stock Voltage kernels in order to see if I could get the phone to boot.
Kernel:
[ Start @ 1.0 GHz, Stock Voltage, Max @ 1.2 GHz ]
(Official LGE/Tegra Voltage Values, Same as STOCK LGE Kernel)
CM7 Kernel Version 0.1.9- Boots to second LG splash screen then freezes.
CM7 Kernel Version 0.1.9 With EXT4-Booted fine but still displayed Morfic boot animation for some reason. Kernel version shows as Faux's in about phone, though.

I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?

Mikeglongo said:
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Click to expand...
Click to collapse
I didn't test any of the ROMs for quality but I would personally stick with a Froyo based ROM for now. Gingerbread is simply too buggy and missing a lot of features.

[B][U]SUCCESS!!![/U][/B]
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Trinity's CM7 kernel. I personally believe this definitely prooves that there is something in Faux's boot.img that doesn't function properly on all devices. That would explain why I am unable to flash any of his kernels, either.

Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.

faux123 said:
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
Click to expand...
Click to collapse
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.

hiko36 said:
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
Click to expand...
Click to collapse
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.

faux123 said:
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
Click to expand...
Click to collapse
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.

hiko36 said:
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
Click to expand...
Click to collapse
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.

faux123 said:
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
Click to expand...
Click to collapse
Glad I could help and especially glad I finally figured out a way to boot your ROM. I was feeling left out haha.

Doh! He said rectify lol
Sent from my Xoom using XDA Premium App

[Q] Random visual flashes/errors while using fresh PA

Hello, some of you might recognize me as the one who was having trouble installing PA last night.
Now I've got it installed, and it runs very smoothly.
Specs off the bat...
TF700T Infinity
VoltageControl Overclock system set at 370-1800
Very latest gaps, installed last night from g+
MaxKernel V4 Reloaded RC2
Installed and flashed through TWRP
ParanoidAndroid 3.15
Likely enough for myself, all of a sudden, a few hours into having the ROM, kernel and gapps freshly flashed, the screen starts giving random graphical flashes and blips here and there, and it's grown to a point where I can't use my tablet without a flash every three seconds.
To explain exactly what is happening, when I switch from app to app or UI section to another UI section or any of the mix, it will brightly flash what I am switching to/from while I do it. For example, I will be opening up PIE and it will flash the app screen in full for a split second if PIE is over it.
Anything that I am doing wrong? I have a restore from a few hours ago set up, will I have to use that?
If anyone has any advice/assistance, please let me know.
Thanks,
Neb
EDIT: I tried resetting the overclocking system to stock clock. No change whatsoever.
Also did a restore. No luck

Turn off the corresponding setting in the developer options.

Also Max's kernel is a stock based kernel. I'm surprised PA even boots off it. I'd switch to a PA compatible kernel of I were you.

Thank you for helping me out on this. I saw some posts stating that Max was a PA based kernel. My bad. Got it taken care of by reverting to PA stock kernel

Kernel doesn't seem to be applied after flashing latest DKP for d2vzw

Hello everyone!
I apologize if this is a poor quality post as it's my first, but my issue is pretty much as it says in the title. I'm currently using an SCH-i535 with CyanogenMod 12.1 nightly 9/6. I want to give the latest DKP kernel a go as I've been experiencing some force reboots, and would like to over and underclock my phone a bit as I did with the BMS kernel when I was on Android 4.4.1.
I downloaded the kernel from decimalman's thread and renamed it to dkp-min-1050.zip. When I flash it in CWM Recovery Touch 6.0.4.5 (after clearing Dalvik and cache, of course), I get a message that the new minimum voltage is 1050 mV, which is expected, but my phone still declares it's running the cyanogenmod-g6bceda8 #1 kernel and Adiutor doesn't give me any CPU speed or governor options that aren't included in CM 12.1 by default.
So, essentially, it doesn't seem that the kernel is actually being flashed despite my recovery saying it flashes successfully. Has anyone encountered this before or notice anything I'm doing incorrectly? Thanks so much in advance for your help!

battery problem

Hi everyone,
It's been a few weeks now that my battery couldn't reach more than 5h with firekernel while it could easily before.
I changed the kernel and now the battery is very good but the indicator decreases from 100% to 1% quickly and gets stuck to 1% for a while.
I tried a battery calibration but that didn't help.
My config:
-Xt1541 2gb ram
-rom: AEX 7.1.2 v4.3
-kernel: UltraDevs v3.5
Can you please help me to fix it?
Thanks in advance!

nubry said:
Hi everyone,
It's been a few weeks now that my battery couldn't reach more than 5h with firekernel while it could easily before.
I changed the kernel and now the battery is very good but the indicator decreases from 100% to 1% quickly and gets stuck to 1% for a while.
I tried a battery calibration but that didn't help.
My config:
-Xt1541 2gb ram
-rom: AEX 7.1.2 v4.3
-kernel: UltraDevs v3.5
Can you please help me to fix it?
Thanks in advance!
Click to expand...
Click to collapse
First I'd suggest using latest version of UltraDevs kernel (v4.0).
If that still doesn't help you, take a nandroid backup and clean flash the ROM again and check for the problem without installing any apps. If it doesn't exist, install your apps 1 or 2 at a time and keep checking. You'll maybe find the app which is causing it (if it is called by some app).
If the problem exists with a clean flash and no other apps installed, it's the ROM and you might just report it to the ROM Dev.

nubry said:
Hi everyone,
It's been a few weeks now that my battery couldn't reach more than 5h with firekernel while it could easily before.
I changed the kernel and now the battery is very good but the indicator decreases from 100% to 1% quickly and gets stuck to 1% for a while.
I tried a battery calibration but that didn't help.
My config:
-Xt1541 2gb ram
-rom: AEX 7.1.2 v4.3
-kernel: UltraDevs v3.5
Can you please help me to fix it?
Thanks in advance!
Click to expand...
Click to collapse
take a nandroid backup, then flash back to stock marshmallow, see if things improve. Use either stock moto kernel or squid kernel and post battery stats after that

Thank you both for your reply!
I'm not home now and don't have really good signal so I'll try to get back on stock marshmallow when I will be able to.
Though I flashed Ultradevs v4.0 and the problem is still there. I'm gonna clean flash the ROM again and I'll tell you then.
Thanks again!

Sorry for the double post but do I need to wipe system in recovery for a clean flash?

I get back to the thread because I flashed back stock ROM with stock kernel and that did the same, now I'm on lineage os and the problem is the same. When I reboot bootloader it is say "battery OK" in green but in recovery and in the ROM 1% is displayed. The problem is very annoying and I don't have any idea how to solve it knowing motorola won't do anything the device being unlocked.