Related
Hi, i have a Lg Nitro HD p930 AT&T with ICS.
I only have the phone for a few days i bought it used on mint condition on ebay.
The problem is that my phone turn off itself and the only way i can turn it on is taking off the battery and then put it back again, also i notice that the battery discharge really fast when i do that, for example if that happens with 90% of the battery when i do the process to turn the phone on, the battery is in 73%.
Another thing is that my phone sometimes gets extremely hot.
Obviously im not an expert but i think maybe its the battery because i only get 4-6 hours with simple use, just chat a little in whatsapp and view a few post on facebook.
I hope you can help me, thanks in advance.
Random reset is an issue on official ics
U can hold power button for 10sec or takeout the battery.
This phone battery usage is high and I think its because of the ips screen.
If you wanna check your battery ,turn off wifi and data and leave your phone for about 5 hours and check battery percentage it should not be more than 5%.but it depend on signal strength of your 3G/4G network
when I play high graphic games or browsing web for long time with high brightness phone gets hot in up sides and its normal
If your phone gets very hot it might be a problem
Sent from my LG-P930 using Tapatalk 2
Yeah, common issue with this phone and ICS and there is no easy fix. You will also sometimes see a red halo on the screen if it turns off by itself and gets hot.
Try to root it and install HoNo's Full Throttle. I heard it doesn't have that issue.
Afriend told me something similar happen to him a he download from de market the App Wake Lock, i download it and the phone hasnt reset since i install it but steal get hot when i use the GPS or chat in multiples APPs and the battery sucks even instaling juice defender.
i just finish rooting my phone a few minutes ago, i would like to instal cyanogen 10, im going to research how to cuz im new i never had install a ROM BUY maybe it work better
can someone send me the link or a tutorial of how to intall a ROM i had my NITRO rooted but i never install a ROM.
wich ROM YOU RECOMMEND i would like a rom that as stable as an official version and dont get my phone hot
thanks
Did you try doing a factory reset? (Hold volume down + power when turning the phone on)
i brick my phone
now i brick my phone, can it be unbricked having lg official icecream sandwich? please and really scared!!!
radhames562 said:
now i brick my phone, can it be unbricked having lg official icecream sandwich? please and really scared!!!
Click to expand...
Click to collapse
Yes, you can unbrick if you're using official ICS; in fact, that's the only way you'd be able to install a custom ROM in the 1st place coming from official ICS. If you just want stock ICS you can use the LG Mobile Update software to restore your device to the stock LG firmware; but if you want a custom ROM you will need to follow one of the 3 unbrick guides located here in the general forum.
radhames562 said:
now i brick my phone, can it be unbricked having lg official icecream sandwich? please and really scared!!!
Click to expand...
Click to collapse
There is no conceivable way to brick an unmodified phone by doing a factory reset, but given the other symptoms that you are describing it might suggest that your phone has a hardware problem. Did you get a warranty with it? It has been my experience that people that have stability issues with this phone and it is 100% stock ICS points to one of two possibilities: software, that a factory reset would resolve or hardware. Good luck.
Sent from my LG-P930 using xda app-developers app
You did root your phone on stock ics but bootloader is locked , so you can't flash any rom via cwm and your phone is bricked.
The only way to unlock bootloader is following unbrick method instructions and back to android 2.3 which has unlocked boot loader and then install rom manager and cwm, then you can flash your favarite rom
If you wana flash stock ics ,use HoNo at&t official ics cmw flashable nor flash what ever you like
Sent from my LG-P930 using Tapatalk 2
thanks
nss007 said:
You did root your phone on stock ics but bootloader is locked , so you can't flash any rom via cwm and your phone is bricked.
The only way to unlock bootloader is following unbrick method instructions and back to android 2.3 which has unlocked boot loader and then install rom manager and cwm, then you can flash your favarite rom
If you wana flash stock ics ,use HoNo at&t official ics cmw flashable nor flash what ever you like
Sent from my LG-P930 using Tapatalk 2
Click to expand...
Click to collapse
hey man thanks you were rigth now im using cyanogen 10 and its great, the phone doesnt get too hot anymore.
now i would love if you help me install GOOGLE PLAY JEJEJE PLIZZZ i dont know how
You should download gapps
But be careful download gapps 4.1.2 for cyanogen 10
Then flash the zip file of gapps like a rom
http://wiki.rootzwiki.com/Google_Apps
Sent from my LG-P930 using Tapatalk 2
nss007 said:
you should download gapps
but be careful download gapps 4.1.2 for cyanogen 10
then flash the zip file of gapps like a rom
http://wiki.rootzwiki.com/google_apps
sent from my lg-p930 using tapatalk 2
Click to expand...
Click to collapse
thanks bro youre the best i install it from the rom manager
radhames562 said:
thanks bro youre the best i install it from the rom manager
Click to expand...
Click to collapse
To solve the problem with reboots, are you still using WakeLock on CM10? And if yes, what mode in WakeLock you are using now?
johnsnow911 said:
To solve the problem with reboots, are you still using WakeLock on CM10? And if yes, what mode in WakeLock you are using now?
Click to expand...
Click to collapse
well the problem was solve but a few day ago my phone just reboots i download the wake lock and its no happening again i used in atage 4
radhames562 said:
well the problem was solve but a few day ago my phone just reboots i download the wake lock and its no happening again i used in atage 4
Click to expand...
Click to collapse
At stage 4 phone doesn't sleep. I've checked out it last night...
johnsnow911 said:
At stage 4 phone doesn't sleep. I've checked out it last night...
Click to expand...
Click to collapse
yeah thats rigth the phone never sleep, im instaling the Ho!no! full trotle to see what happens
radhames562 said:
yeah thats rigth the phone never sleep, im instaling the Ho!no! full trotle to see what happens
Click to expand...
Click to collapse
try to set permission for system/bin folder and file bin/vold to
xxx
xxx
x0x
xxx
My Phone stoped rebooting
it happens again even with wake lock i start installing a lots of ROMs and it happens again then i install ligthing zap and it stop but another day when i try to instal another ROM i cant set the phone always reboot
I make some research and i found LIQUID ROM thats is a ATT&T MODIFIED ICS and so far the phone hasnt reboot or do anything worng and thats all i want, i even get better battery life i hope the phone never reboot himself again.
radhames562 said:
it happens again even with wake lock i start installing a lots of ROMs and it happens again then i install ligthing zap and it stop but another day when i try to instal another ROM i cant set the phone always reboot
I make some research and i found LIQUID ROM thats is a ATT&T MODIFIED ICS and so far the phone hasnt reboot or do anything worng and thats all i want, i even get better battery life i hope the phone never reboot himself again.
Click to expand...
Click to collapse
To increase battery life just install v10e rom backup from here http://forum.xda-developers.com/showthread.php?t=1827379 and try to set permission, like i said above and look, what you will get. My phone keep on for 1day and 19 with some internet and games. Its 1% battery for about 2 hours, but it still working) no reboot and no problems without wake lock))) Its sleep like a calm baby almost all night long)
Hello,
I flashed the Racing Bean Custom ROM and installed the Fusion Kernel, but when I'm starting my phone it takes a long time after the Kernel Logo disappears or I can enter the CWM. The general startup process needs sometimes 7 minutes, and that ain't normal, is it?
I performed a clean install (wipe caches, delete and format etc.) and this occurs on all kernels i have tried so far (Lupus, Fusion, Radeon)
How do I repair this?
Completely normal on first boot after installing new ROM/firmware.
Someguyfromhell said:
Completely normal on first boot after installing new ROM/firmware.
Click to expand...
Click to collapse
I know that, but it still occurs after 5 reboots.
how many days have you had the the new rom working ?
some times you need to let it settle
I'm running on lupus/paranoiandorid and it takes about 45 seconds
but the first ones took (to me ) ages it gets better whit use
also if you delete cache and dalvik the phone will need to update everything everytime
apps etc so be patient and should be ok
Raps
Well I had this new ROM for a few days now - but before that I had CM10 for a month and there was the same problem
Are you using fusion 4, 4.1 or 4.3 with beam ?
I read there were some problem for those using 4.1 and some claim is working well with 4.3 although the recomended is 4.0 might be worth a look
Raps
larsthmn said:
Well I had this new ROM for a few days now - but before that I had CM10 for a month and there was the same problem
Click to expand...
Click to collapse
User error then I suspect, and you should have stated that in the OP.
Sent from Myushi
Well, now I have Racing Bean with the FXP Kernel, which has brought the best Benchmark result so far - I hope the ROM will "settle" as you said and run fine.
Thank you for your help,
Lars
larsthmn said:
Well, now I have Racing Bean with the FXP Kernel, which has brought the best Benchmark result so far - I hope the ROM will "settle" as you said and run fine.
Thank you for your help,
Lars
Click to expand...
Click to collapse
Man, can you tell me exactly which FXP kernel you used? D:
Phenomzye said:
Man, can you tell me exactly which FXP kernel you used? D:
Click to expand...
Click to collapse
The one from Cyagonenmod 10 .. but with it Wifi is not working and I haven't found the Wifi Modules for it yet.
BUT ... I'm now using the Lupus Kernel for a few days and it's still running very badly with every Kernel. Any suggestions to fix that?
Lately I have been getting random reboots and random black screens. The phone will either reboot itself show the galaxy s3 screen then go to complete darkness or vibrate and go straight to complete darkness. This seems to be random and usually starts happening a week or so after flashing a rom or kernel. Right now I am using my own TW rom (in dev section) with kt kernel and team kernalizer scripts. But the kernel doesn't seem to matter as this happens regardless. Does anyone know whats going on? Also this started happening after I ran aokp 4.2.2 for awhile, then odin back to stock and issues started. I've also been having less battery life since then.
Someone please help
anyone?
aamir123 said:
anyone?
Click to expand...
Click to collapse
Running stock Odin may be an option, but here is what I would do first.
Flash the LJC firmware from the second firmware link in my signature. It's in the OP, but isn't immediately obvious. Just scroll a bit and you will see it.
Stop using KT and tkmod for now. These, simply put, are variables that you don't need to deal with right now. There is also a good chance it's a bug in your ROM.
Aerowinder said:
Running stock Odin may be an option, but here is what I would do first.
Flash the LJC firmware from the second firmware link in my signature. It's in the OP, but isn't immediately obvious. Just scroll a bit and you will see it.
Stop using KT and tkmod for now. These, simply put, are variables that you don't need to deal with right now. There is also a good chance it's a bug in your ROM.
Click to expand...
Click to collapse
Before I went to aokp I was using my rom very stably for a good while and others have been using it without problems, but I agree going to least common denominator (stock rom/kernel) sounds like a very good idea. I'll also flash the ljc firmware even though I haven't really had any problems with the 4.1.2 one.
Btw why ljc and not md5?
aamir123 said:
Before I went to aokp I was using my rom very stably for a good while and others have been using it without problems, but I agree going to least common denominator (stock rom/kernel) sounds like a very good idea. I'll also flash the ljc firmware even though I haven't really had any problems with the 4.1.2 one.
Btw why ljc and not md5?
Click to expand...
Click to collapse
Because it's somewhat likely the MD5 firmware is causing your problems. I can't use it on my phone, just kills battery. Maybe your phone has a more severe reaction to it.
Aerowinder said:
Because it's somewhat likely the MD5 firmware is causing your problems. I can't use it on my phone, just kills battery. Maybe your phone has a more severe reaction to it.
Click to expand...
Click to collapse
ok I guess I'll go back but I don't see why the md5 firmware would be a problem now after I was using it with no problem for a while.
Unless you are running 100% md5, it has been known to cause some issues. Seems a lot was done on that update from 4.1.1 - 4.1.2, and it doesn't always like to be mixed with older fw.
Sent from my SGH-T999L using XDA Premium 4 mobile app
DocHoliday77 said:
Unless you are running 100% md5, it has been known to cause some issues. Seems a lot was done on that update from 4.1.1 - 4.1.2, and it doesn't always like to be mixed with older fw.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I flashed the LJC fw and so far it's been pretty stable, only having trouble with excess heat but will probably get better with time. Also I'm having trouble getting a logcat app running (catlog etc). The app opens I give it root permissions, then I get a black screen with loading ring. No log whatsoever, is that normal? tried on both fw btw.
just got another random reboot on ljc fw. any other ideas?
aamir123 said:
just got another random reboot on ljc fw. any other ideas?
Click to expand...
Click to collapse
Just a heads up, my phone was doing this for about 3 days, and then completely crashed. Check out my thread. Stock Rom, but rooted. Hope it doesn't happen to you.
cboss718 said:
Just a heads up, my phone was doing this for about 3 days, and then completely crashed. Check out my thread. Stock Rom, but rooted. Hope it doesn't happen to you.
Click to expand...
Click to collapse
Idk what the issue is I'm gonna go stock for a while without recovering and see if that will fix anything, if not maybe tmobile is the way to go. Btw I tried taking a log cat but get error saying that dev/log/main doesn't exist.
Ok I was doing good for a few hours after flashing stock and not restoring Google account until I got a random reboot just now. I was able to get a log cat tho so I'd anyone can look at it and help.
Sent from my SGH-T999 using xda app-developers app
anybody? Does anyonehave any ideas?
aamir123 said:
anybody? Does anyonehave any ideas?
Click to expand...
Click to collapse
That logcat contains 30 seconds of information. Looks like you pulled it after the device rebooted. It's probably going to be the kernel dmesg that we need. You get that one after the device reboots, but not the logcat.
Aerowinder said:
That logcat contains 30 seconds of information. Looks like you pulled it after the device rebooted. It's probably going to be the kernel dmesg that we need. You get that one after the device reboots, but not the logcat.
Click to expand...
Click to collapse
ok I will try to get that the next time it reboots. Hopefully it's a simple fix, but just not sure what the problem could be.
So I went all these days without a random reboot and finally got one today, but was unable to pull a dmesg as it said does not exist. What can I try to get a dmesg now?
Also the phone feels like it never shuts down, even when I choose to shutdown in the menu it ends up restarting itself then bootlooping or just restarting. I've also noticed that holding home and power to turn phone on works most of the time to get it back to the os only to have it crash shortly after. I press home and power until I see the white splashscreen then let power button go. but staying in os for more than a few mins right now is impossible.
Hello guys,
I searched for this issue on the forum but it seems that nobody encountered anything like this before.
To begin, I would like to mention that I am running the latest CyanogenMod 11 nightly on an HTC One X (Tegra version).
Since somewhere right after the latest M release, I've been having a couple of issues with the phone:
#1: From time to time, I get a "Lockscreen" isn't responding dialog and it asks whether I want to "Wait" or "Close". Well, if I click on "Wait" the phone becomes unresponsive, as if something was running in the background so hard that it would eat up all the ram and would choke the CPU;
If I click on close, it's a hit or miss situation: sometimes it restarts the lockscreen and takes me back to it, even though I previously unlocked the device and sometimes the phone becomes unresponsive as before.
#2: Besides what I mentioned above, the phone sometimes becomes unresponsive without warning and every time this happens, it always looks and feels as if something is chocking the ram and CPU.
Have any of you guys encountered something like this before and if yes, what can I do to fix it?
If not, is there a way in Android, to pull up a log similar to the Windows Task Manager, that would tell me exactly what was running in the background at a given time and how much memory/CPU cycles it was actually using?
Thank you in advance.
Try your stock rom for a while.
Mr Hofs said:
Try your stock rom for a while.
Click to expand...
Click to collapse
Thank you for your reply however, I haven't used sense roms in a while now, plus, it's a downgrade from KitKat, which is why I am not that fond of this option.
On a different note, I just installed the latest nightly "clean", namely with a full factory reset from recovery, flashed boot.img in fastboot and installed the latest GApps from PA.
I don't get the "Lockscreen is not responding" dialog anymore, but from time to time, the lockscreen still closes and now it either resets on its own, or it forces the OS to reset, after which com.android.systemui starts force closing indefinitely and the phone afterwards requires a hard reset.
Has anyone else encountered something similar? Any help?
I'm saying to use the stock rom for a while just to rule out hardware issues !
Mr Hofs said:
I'm saying to use the stock rom for a while just to rule out hardware issues !
Click to expand...
Click to collapse
Cool, will try that. Thanks.
What kind of hardware issues do you think could cause an issue like this?
Not sure but why stick to a rom that is not working properly, go for safe and go for stock if the issue is gone you can search for the issue that is caused by a rom !
Mr Hofs said:
Not sure but why stick to a rom that is not working properly, go for safe and go for stock if the issue is gone you can search for the issue that is caused by a rom !
Click to expand...
Click to collapse
Fair enough! Thank you!
I recently installed CyanogenMod 11 M7 on my LG G Pad 8.3, almost everything is working perfectly.
Whenever I restart or shut down/turn back on (i.e. Cold Boot) the screen is very dim, you can barely see the CyanogenMod boot animation. Then the lock screen is barely visible. If I enter my pin, then turn on/off the screen 1 or maybe two times it's normal brightness and the problem is fixed.
I need to do this every time after a cold boot though. I'm living with it because how often do you restart phones/tablets? But it's an odd one.
Any ideas how to fix this would be appreciated? Thanks.
bradavon said:
I recently installed CyanogenMod 11 M7 on my LG G Pad 8.3, almost everything is working perfectly.
Whenever I restart or shut down/turn back on (i.e. Cold Boot) the screen is very dim, you can barely see the CyanogenMod boot animation. Then the lock screen is barely visible. If I enter my pin, then turn on/off the screen 1 or maybe two times it's normal brightness and the problem is fixed.
I need to do this every time after a cold boot though. I'm living with it because how often do you restart phones/tablets? But it's an odd one.
Any ideas how to fix this would be appreciated? Thanks.
Click to expand...
Click to collapse
Try AIC Kernel, that fixes gamma...
on every ROM flash, GAPPS, also i flash AIC, so its normal...
see the thread: http://forum.xda-developers.com/showthread.php?t=2741405
Thanks Jhon998. Just a few quick questions please:
* What is AIC Kernel exactly?
* Will it interfere with CM11 M7's operation?
* Will it interfere with CM11 OTA monthly updates?
I'm a bit worried about breaking something adding third party code into the mix.
* I presume I need to flash aickernelinstaller.zip and not AIC_kernel_flashable.zip? The instructions say to use AIC_kernel_flashable.zip but I think it's aickernelinstaller.zip that supports CM11 coming from stock 4.4.2.
the installer have an option to choose from whether you have a stock or aosp, and if you choose aosp it just fix the gamma (brightness), but the problem that you have to flash it on every ROM flashing, like monthly, not like gapps, in my hand it is not a problem, but I am using stock with aic kernel on top...
Sent from my LG-V500 using Tapatalk
Jhon998 said:
the installer have an option to choose from whether you have a stock or aosp, and if you choose aosp it just fix the gamma (brightness)
Click to expand...
Click to collapse
Got it. Thanks.
Jhon998 said:
but the problem that you have to flash it on every ROM flashing, like monthly
Click to expand...
Click to collapse
That sounds like a pain. To be clear, if I were to install a CM Milestone Over-the-Air update I'd need to re-run AIC Kernel?
Thanks again.
bradavon said:
Got it. Thanks.
That sounds like a pain. To be clear, if I were to install a CM Milestone Over-the-Air update I'd need to re-run AIC Kernel?
Thanks again.
Click to expand...
Click to collapse
As i noticed it flashes a kernel within the ROM... obviously..
bradavon said:
I recently installed CyanogenMod 11 M7 on my LG G Pad 8.3, almost everything is working perfectly.
Whenever I restart or shut down/turn back on (i.e. Cold Boot) the screen is very dim, you can barely see the CyanogenMod boot animation. Then the lock screen is barely visible. If I enter my pin, then turn on/off the screen 1 or maybe two times it's normal brightness and the problem is fixed.
I need to do this every time after a cold boot though. I'm living with it because how often do you restart phones/tablets? But it's an odd one.
Any ideas how to fix this would be appreciated? Thanks.
Click to expand...
Click to collapse
Maybe it helps to flash 4.4.2 compatible TWRP from here http://forum.xda-developers.com/showthread.php?t=2551499. Did you try that?
nsmart said:
Maybe it helps to flash 4.4.2 compatible TWRP from here http://forum.xda-developers.com/showthread.php?t=2551499. Did you try that?
Click to expand...
Click to collapse
Thanks for the heads up on a new compatible TWRP release Nsmart. I just have. It didn't make a difference unfortunately. I was already running TWRP 2.7.0.1. I guess 2.7.1 hasn't fixed this.
Hopefully Cyanogenmod will fix it. I've decided not to try AIC Kernel. I'm wary of installing third party code into third party code.
Done!
That worked for me! Thank you. I had some problems with rooting the v50020D, when i got it, i got the dim screen problem. Now it fixed. Ty very much.
If you're on cm11... flash Mani kernel.
Worked for me ^^
Unfortunately it's laggy when compared w/ dynkernel.
I only reboot if problem, I can do w/o the lag
Sent from my Kin[G]_Pad ™
bradavon said:
Thanks for the heads up on a new compatible TWRP release Nsmart. I just have. It didn't make a difference unfortunately. I was already running TWRP 2.7.0.1. I guess 2.7.1 hasn't fixed this.
Hopefully Cyanogenmod will fix it. I've decided not to try AIC Kernel. I'm wary of installing third party code into third party code.
Click to expand...
Click to collapse
It's safe, it won't touch anything other than fixing that gamma issue if you haven't flashed the 4.2.2 base before...
Thanks.
How do you mean "flash the 4.2.2 base before"? I was on LG stock Android 4.2.2 then OTA to 4.4.2 and now CM11 M8 (pretty sure it's M8, would need to check).
The 4.4.2 OTA updates the firmware on the device. This firmware is what causes the dimming issue on most of the AOSP based roms (like CyanogenMod). So if you want to avoid the dimming issue and run CM you should flash the following rom first (warning it will take quite a while and make sure to double check the md5 since this is a really big file). The 4.4.2 firmware update also gets rid of the 7 lights bug, so that issue will reappear on your tablet when you go back if you had it before.
Here is the thread detailing the 4.2.2 base rom:
http://forum.xda-developers.com/showthread.php?t=2719411
Basically backup any files you care about, flash the 4.2.2. base rom and then flash CM again. This will solve the screen dim issue on AOSP based roms.
AIC kernel fixed that problem for me
Bill_windows said:
AIC kernel fixed that problem for me
Click to expand...
Click to collapse
Yes, this could fix the problem as well...
Im completey stock no root....and i have this problem
Sent from my LG-V500 using XDA Premium 4 mobile app