After surfing the forums for a couple days and not finding a completely precise answer to my problem, and due to being limited by posts, I have to ask a question here. I have rooted my phone, installed a number of different roms, but the only issue I have run into is flashing faux123's kernel and the Trinity kernels. No matter what kernel I attempt to flash I receive the wonderful black screen. The touch buttons light up when the screen is pressed, but the rom does not seem to load in the background. I am doing something wrong when I flash the kernel, or is there another problem that I have not found?
I have flashed UV and normal voltage kernels, along with going to advanced under CWM and formatting each part of the phone.
EDIT: Resolved the issue. It appears the only rom that works with these kernels on my phone is the nightlies. Thanks everyone though.
Jakkumn said:
After surfing the forums for a couple days and not finding a completely precise answer to my problem, and due to being limited by posts, I have to ask a question here. I have rooted my phone, installed a number of different roms, but the only issue I have run into is flashing faux123's kernel and the Trinity kernels. No matter what kernel I attempt to flash I receive the wonderful black screen. The touch buttons light up when the screen is pressed, but the rom does not seem to load in the background. I am doing something wrong when I flash the kernel, or is there another problem that I have not found?
I have flashed UV and normal voltage kernels, along with going to advanced under CWM and formatting each part of the phone.
EDIT: Resolved the issue. It appears the only rom that works with these kernels on my phone is the nightlies. Thanks everyone though.
Click to expand...
Click to collapse
if i was me after reading what I've found online i think i would look for a more reputable dev when it comes to kernels.
Reputable? Faux and morfic are among the elite devs for our device. They don't get any more reputable than them.
-custom sig.
CM7 should work, whether nightlies or stable. Trinity requires ext 4 support, meaning CWM touch won't work. Previous version 5.0.2.0 (I believe) should be used to install trinity. Faux should have worked so not sure why it failed on other than nightlies.
All CM7 based ROM should work with these kernels.
-- The noob says:
Three in the morning I woke up... it was hot... the g2x had SODd!
Related
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
Hello android gurus/deities (too much?),
Just got my first smartphone, a Droid Charge. Great phone, especially for the price. The screen is freaking fantastic and of course Android is amazing as ever.
However, since first activating it, I seem to get random crashes. I can't replicate the problem, since it doesn't seem connected to anything visual. First time it happened when I decided to check out the camera, took a picture, and tried to view it. Other times have been the first time trying out netflix, first time sending a text. Seems to happen the first time I use some apps.
The crash basically consists of a short 5-10 second freeze followed by a reboot. Any ideas? Is this a hardware issue I need to have addressed or more likely a software issue that I just need to wait for updates to come along and fix it? Or is this a common occurence with Android and I just need to suck it up? lol
Edit: Has also happened 3 or 4 times while browsing the web, including this site...
charges hardware are pretty great for the price the software is a big issue for the charge whitch is why most of us myself included suggest rooting your device whitch literally a dummy could do using odin... i am running a stock based of a leak called infinity rom pretty amazing for a stockish rom for now so reboots are known at least for me but i really think the majority of the problem for this phone is the software gps loss signal going in and out as in data (this is a hit and miss) ..... hope this helped you iron things out...
Out of curiosity, what will rooting my device accomplish with respect to the reboots? Anything?
I rooted the device, then tried infinityROM but ran into so many problems I flashed back to the factory rom X(... Rooted again, but still get reboots, any ideas?
Where can I get a more solid kernel? From reading around it sounds like that "might" solve the reboots :\
RevTorA said:
Where can I get a more solid kernel? From reading around it sounds like that "might" solve the reboots :\
Click to expand...
Click to collapse
http://rootzwiki.com/topic/4847-guide-new-users-guide-everything-how-to-root-rom-kernels-radios-cwm/
Also depends what rom you are running.
If it keeps happening after you root and flash a new kernel (and maybe install a rom) upload a logcat to a filesharing place and hop on IRC to ask for help.
irc.andirc.net
#charge
Port 6666
Sent from my SCH-I510 using xda premium
Thanks... once that site's back up I'll download a the kernel from there... The kernel on that page should work my Charge if it's currently the factory rom right?
Edit: Just to check, Imoseyon's kernel (listed here is the only available kernel aside from the factory kernel? I should try flashing this to see if it fixes my problem? Where can I get the factory kernel (just the kernel :\) if things go awry?
Edit2: Also found imnut's PBJT kernel here. I'm unaware of some of the terminologies (I've only messed with a couple Ubuntu/Fedora distros of linux), can this and any other kernel for the Charge work with Gingerbread (2.3.6)?
RevTorA said:
Thanks... once that site's back up I'll download a the kernel from there... The kernel on that page should work my Charge if it's currently the factory rom right?
Edit: Just to check, Imoseyon's kernel (listed here is the only available kernel aside from the factory kernel? I should try flashing this to see if it fixes my problem? Where can I get the factory kernel (just the kernel :\) if things go awry?
Edit2: Also found imnut's PBJT kernel here. I'm unaware of some of the terminologies (I've only messed with a couple Ubuntu/Fedora distros of linux), can this and any other kernel for the Charge work with Gingerbread (2.3.6)?
Click to expand...
Click to collapse
PBJ is a Froyo kernel. It will only work with Froyo.
I recently rooted my TF101 using Razorclaw root and installed clockwerk recovery. I have a B70 tablet that wont use NVflash so im assuming i have the SBK2. I tried to install a kernel and kept booting with a very distorted screen and i couldnt do anything. My question is: is my TF bricked? Does flashing a custom kernel not work on the TFs with the newer SBK's or can my processor not handle being overclocked that high. Because i believe it was a 1.8Ghz kernel that i flashed. I fixed it by pulling out the stock kernel from a rom and flashed that in recovery. Just wondering what's going on here.
Could be your TF not able to handle the 1.8Ghz. Did you install any app to manage
the frequencies, ect.... I use SetCPU but there's other apps that does it.
Make sure it's set to about 1Ghz first before flashing the OC kernel.
After which you can increase it slowly
Well it wouldnt even boot to the lock screen and the screen was all distorted. I dont know if its set at 1.8 right when it boots or lower. or maybe a bad download. but i didnt even have a chance to unlock the thing.
Are you still on the stock but rooted ROM? If so it's probably not compatible with a OC kernel.
im not sure what the problem is. because now, i tried to do custom roms again and im on revolver with a 1.6Ghz overclock and having no problems at all.
kernel flashing problems
I have had the same thing with a couple different kernels. I found some various kernel source trees on git for TF101 and tried rebuilding them and cross-compiling on my Ubuntu system. Most of the time it works fine but there were a couple that when I tried to flash them all I got was a screen full of snowy colored lines, kind of like the snow on an old color TV and could hear some weird 'spacey' sounds coming from it but it wouldn't boot any further. I don't know if these sources were for projects working on ICS or if they were trying to modify source from some other device or what the deal was, but those 2 wouldn't boot.
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
Hello. I have the GS5. For over three months it overheats like hell. Why because I did the firmware update and it all started with this.
TL;DR: I need an app or program that shows detailed percentage of usage and temperatures of apps. It would be great if you can find a real-time monitoring one like on PCs. My phone is rooted so feel free to recommend any app that suit my needs.
It overheats so much that I can barely able to hold the phone because it slips through so easily from my hand (nope my hands are not dirty, I wash them with lots of soaps ).
I bought a case and it is still somewhat hard to hold the phone with one hand but the case surely helped. Can use it with two hands but was able to use with one hand without any problems so why should I accept this right?
The cpu is around 40 Celsius at idle to very low usage. The battery is around 28 Celsius at idle. The room temps is 26 Celsius.
After using my phone for about fifteen mins, the battery is going up to 36-38 Celsius. The cpu is around 50 Celsius. Not playing games at all, just surfing on the web and installing one to two apps from Android Market. Do you think it is normal or excessive? I fell the heat in my hands. It was not been like this before the firmware update.
Although I did all wipes and flash the whole rom from scratch (even ticked Nand Erase All), my problem still persists so I am out of ideas. Maybe I can buy a new battery and a charger but I would like to make sure that the problem is not causing by software. Thank you.
karasahin said:
Hello. I have the GS5. For over three months it overheats like hell. Why because I did the firmware update and it all started with this.
TL;DR: I need an app or program that shows detailed percentage of usage and temperatures of apps. It would be great if you can find a real-time monitoring one like on PCs. My phone is rooted so feel free to recommend any app that suit my needs.
It overheats so much that I can barely able to hold the phone because it slips through so easily from my hand (nope my hands are not dirty, I wash them with lots of soaps ).
I bought a case and it is still somewhat hard to hold the phone with one hand but the case surely helped. Can use it with two hands but was able to use with one hand without any problems so why should I accept this right?
The cpu is around 40 Celsius at idle to very low usage. The battery is around 28 Celsius at idle. The room temps is 26 Celsius.
After using my phone for about fifteen mins, the battery is going up to 36-38 Celsius. The cpu is around 50 Celsius. Not playing games at all, just surfing on the web and installing one to two apps from Android Market. Do you think it is normal or excessive? I fell the heat in my hands. It was not been like this before the firmware update.
Although I did all wipes and flash the whole rom from scratch (even ticked Nand Erase All), my problem still persists so I am out of ideas. Maybe I can buy a new battery and a charger but I would like to make sure that the problem is not causing by software. Thank you.
Click to expand...
Click to collapse
Please provide further information in regard to your device e.g. ROM, kernel etc.
noc.jfcbs said:
Please provide further information in regard to your device e.g. ROM, kernel etc.
Click to expand...
Click to collapse
Sure. I haven't touched to kernel yet but I have a custom rom installed. I just installed it yesterday. Was using stock rom of Lollipop 5.0 of my country before. I also tried the UK rom (BTU) but all the same.
karasahin said:
Sure. I haven't touched to kernel yet but I have a custom rom installed. I just installed it yesterday. Was using stock rom of Lollipop 5.0 of my country before. I also tried the UK rom (BTU) but all the same.
Click to expand...
Click to collapse
Despite only little information available, I assume the issue is kernel related. Had you e.g. overclocked and over-voltaged? Most likely not as you were on stock.
Your custom ROM certainly came with its own, new kernel. I suggest to monitor the overheating first as you just recently flashed the custom ROM. However, you can also play with the kernel settings (my current one has its own control-apk, or by using e.g. an apk called "Kernel Adiutor") to see what's best serves your requirements. If you're not happy with the custom ROM's kernel, you can flash a custom kernel but check compatibility first. And remember, when you're on a custom kernel every time you flash the custom ROM you'll have to re-flash the kernel.
Here's a real good guide regarding CPU governors, I/O schedulers and more:
http://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
noc.jfcbs said:
Despite only little information available, I assume the issue is kernel related. Had you e.g. overclocked and over-voltaged? Most likely not as you were on stock.
Your custom ROM certainly came with its own, new kernel. I suggest to monitor the overheating first as you just recently flashed the custom ROM. However, you can also play with the kernel settings (my current one has its own control-apk, or by using e.g. an apk called "Kernel Adiutor") to see what's best serves your requirements. If you're not happy with the custom ROM's kernel, you can flash a custom kernel but check compatibility first. And remember, when you're on a custom kernel every time you flash the custom ROM you'll have to re-flash the kernel.
Here's a real good guide regarding CPU governors, I/O schedulers and more:
http://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
Click to expand...
Click to collapse
So I think I should update kernel on this custom rom with a new one? Because the OP says that flash hispasian kernel after flashing his rom. I haven't do that yet, nor I have experience about it. I believe I have a custom rom with stock kernel right now. I don't think it is related to custom rom. It overheats like I was on stock rom. Could be kernel. Can kernel be updated through the firmware update? It may explain why it starts to overheating after that. No, I haven't overclocked and over-voltaged the cpu. Maybe it came overclocked or over-voltaged with this custom rom but it isn't described.
karasahin said:
So I think I should update kernel on this custom rom with a new one? Because the OP says that flash hispasian kernel after flashing his rom. I haven't do that yet, nor I have experience about it. I believe I have a custom rom with stock kernel right now. I don't think it is related to custom rom. It overheats like I was on stock rom. Could be kernel. Can kernel be updated through the firmware update? It may explain why it starts to overheating after that. No, I haven't overclocked and over-voltaged the cpu. Maybe it came overclocked or over-voltaged with this custom rom but it isn't described.
Click to expand...
Click to collapse
I suggest to surf your custom ROM's thread and to figure out, which kernels can go with this ROM and which are the experiences of other users with the respective kernel.
Firmware updates (I assume you mean now updates of your ROM) won't solve your problem because with the update comes its own kernel i.e. you need to flash afterwards the kernel you want again.
I always flash my custom kernel through recovery. As recovery, I personally recommend TWRP in its latest version (as you see in my signature block, I'm using TWRP v3.0.2). An in my opinion very good tool, to install (actually flash through your current recovery) TWRP is via an App (apk) called "Flashify".
After you've flash TWRP and rebooted, google how to flash a kernel or search XDA for my postings. I think I already describe somewhere how to do so.
noc.jfcbs said:
I suggest to surf your custom ROM's thread and to figure out, which kernels can go with this ROM and which are the experiences of other users with the respective kernel.
Firmware updates (I assume you mean now updates of your ROM) won't solve your problem because with the update comes its own kernel i.e. you need to flash afterwards the kernel you want again.
I always flash my custom kernel through recovery. As recovery, I personally recommend TWRP in its latest version (as you see in my signature block, I'm using TWRP v3.0.2). An in my opinion very good tool, to install (actually flash through your current recovery) TWRP is via an App (apk) called "Flashify".
After you've flash TWRP and rebooted, google how to flash a kernel or search XDA for my postings. I think I already describe somewhere how to do so.
Click to expand...
Click to collapse
I mentioned firmware updates because I was wondering if stock (Samsung) rom firmware update did break something in stock kernel. Is it possible? I'm %99 positive this happened after the latest firmware update. I mainly flashed this custom rom to get rid of overheating problem but the problem persists.
I just flashed HispAsian kernel, which the creator of this custom ROM recommended, through TWRP and works fine for now. But nothing's changed about overheating.
karasahin said:
I mentioned firmware updates because I was wondering if stock (Samsung) rom firmware update did break something in stock kernel. Is it possible? I'm %99 positive this happened after the latest firmware update. I mainly flashed this custom rom to get rid of overheating problem but the problem persists.
I just flashed HispAsian kernel, which the creator of this custom ROM recommended, through TWRP and works fine for now. But nothing's changed about overheating.
Click to expand...
Click to collapse
Look into the kernel settings as mentioned in post #4 (http://forum.xda-developers.com/showpost.php?p=67135599&postcount=4).
Before you change anything I suggest to educate yourself via the thread mentioned in that post, too.
noc.jfcbs said:
Look into the kernel settings as mentioned in post #4 (http://forum.xda-developers.com/showpost.php?p=67135599&postcount=4).
Before you change anything I suggest to educate yourself via the thread mentioned in that post, too.
Click to expand...
Click to collapse
I actually don't care about custom roms. As long as I can find a solution for stock roms I would return to them. Could you please give me your solution for stock roms?
karasahin said:
I actually don't care about custom roms. As long as I can find a solution for stock roms I would return to them. Could you please give me your solution for stock roms?
Click to expand...
Click to collapse
It's always your decision and desire. I think everything said also applies to stock ROM. Check your kernel settings and manipulate to your needs. Some tools were mentioned before.
noc.jfcbs said:
It's always your decision and desire. I think everything said also applies to stock ROM. Check your kernel settings and manipulate to your needs. Some tools were mentioned before.
Click to expand...
Click to collapse
It is too complicated for me. If you could just point how to downlock the CPU's clock speed then I can try and see if it works to prevent overheating.
Also let's say I decide to return to stock rom. Will current kernel replace with stock one?
karasahin said:
It is too complicated for me. If you could just point how to downlock the CPU's clock speed then I can try and see if it works to prevent overheating.
Also let's say I decide to return to stock rom. Will current kernel replace with stock one?
Click to expand...
Click to collapse
I'm not familiar with your phone (wasn't it a Samsung Galaxy S5) or your stock ROM (Lollipop?). I suggest that you address your questions in the GSG5 forum, where the gurus for your phone rest. Sorry for that.
Anyhow, I added two screenshots of the apk "Kernel Adiutor" (first two), and two of AGNi control, which came with my kernel. As you see both of them support manipulation of kernel settings.
IRT your last question: I'm convinced flashing stock ROM is also replacing current kernel. ...but as said: GSG5 forum.