Related
This is doing my head in to the point I have borrowed a new HTC Sensation only to find the problem exists on this phone also.
When using the Camera App If I hit the power button the screen turns off. I am then unable to switch the screen back on - It appears the phone crashes.
Behaviour some times differs depending whether I have taken a photo or not.
The following behaviour is observed:
The lights stay illuminate on the soft keys at the bottom of the screen.
The phone can receive calls how ever it doesn't ring and I unable to answer them.
This problem is confirmed on 2 seperate devices which have been flashed with:
Android Revolution HD 3.6.12
10.58.9035.00U_10.15.9035.02_2 radio
I have also run super wipe on the phone before installing the HD Rom.
Please help!?
Ive also had this problem on a few diffrent roms.
But i flashed amaze camara update, and not had any prob since.
Im now running the latest ICS with sense, with what ever camara software came with the rom. And not had any problem
big_sw2000 said:
Ive also had this problem on a few diffrent roms.
But i flashed amaze camara update, and not had any prob since.
Im now running the latest ICS with sense, with what ever camara software came with the rom. And not had any problem
Click to expand...
Click to collapse
Cheers moved to ICS and its now fixed.
edwardblum said:
Cheers moved to ICS and its now fixed.
Click to expand...
Click to collapse
Having the same issues on both mine and my wives phones, both running AR 3.6.11 along with lag and other issues! Pretty fed up - and considering a different ROM. How is the ICS ROM, any issues like the 3.6.11? Is it hard to install?
I would try Elegancia ICS. Maybe a little pain to install, if you need to update your firmware.
http://forum.xda-developers.com/showthread.php?t=1429953
Firmware
http://forum.xda-developers.com/showthread.php?t=1432220
You may have to superCID if the firware dont work. Also easy todo
See post 4
http://forum.xda-developers.com/showthread.php?t=1192300
Have a read of the last 10 pages or so of the ICS thread for superCID info if your stuck, but it is easy.
I will give it a try! Do you just download the zip firmware and flash it?
It's not a rom problem, it is faux's kernel problem.
You can flash bricked kernel to solve.
banasik72 said:
I will give it a try! Do you just download the zip firmware and flash it?
Click to expand...
Click to collapse
Put the img zip directly on the SD card, not in any folder.
Boot the phone in to bootloader Power on volume down same time.
Just follow the instructions.
DO NOT POWER OFF REMOVE BATTERY ETC.
You will have to remove file from memory card before rebooting.
If you fail with the upload, then you will have to superCID
So I have a little bit of a strange issue.
I had flashed the AOKP Milestone 5 on my TF, and although I managed to fix the CWM bootloop, it doesn't appear I'm able to install any other ROM.
Since I've flashed it, any other ROM I attempt to flash either fails to complete it's first boot (watched a few different ones try for hours yesterday) or wifi will not turn on. The wifi issue is also present in my backup from stock.
Perhaps for the ROMs that are booting for me there is a different kernel I may have better luck with? Thoughts, anyone?
frankxanders said:
So I have a little bit of a strange issue.
I had flashed the AOKP Milestone 5 on my TF, and although I managed to fix the CWM bootloop, it doesn't appear I'm able to install any other ROM.
Since I've flashed it, any other ROM I attempt to flash either fails to complete it's first boot (watched a few different ones try for hours yesterday) or wifi will not turn on. The wifi issue is also present in my backup from stock.
Perhaps for the ROMs that are booting for me there is a different kernel I may have better luck with? Thoughts, anyone?
Click to expand...
Click to collapse
What recovery are you using? might pay to try another (Recommended: http://forum.xda-developers.com/showthread.php?t=1759452)
You may want to obtain a kernel compatible with the ROM you want to try and flash both the ROM and kernel at the same time. The wrong kernel could definitely cause both the booting problems and the wifi not turning on.
I think about a kernel problem too, go to your ROM thread and you'll see the best kernel to flash with it...
Hello everyone,
Ive seem to run into some trouble, that I cant find a solution too.
I rooted my phone with Gingerbreak V1.20, and flash my recovery with CWM.
I proceeded to add the Nightly Four E rom, than the trouble began.
My colors on the phone display are diffused and distorted, mainly showing the color green and blue.
I read thatI need to flash the stock 2.2 rom again and it would fix it but it didnt.
Can someone help me with this, its quite annoying.
Trytohaxme said:
Hello everyone,
Ive seem to run into some trouble, that I cant find a solution too.
I rooted my phone with Gingerbreak V1.20, and flash my recovery with CWM.
I proceeded to add the Nightly Four E rom, than the trouble began.
My colors on the phone display are diffused and distorted, mainly showing the color green and blue.
I read thatI need to flash the stock 2.2 rom again and it would fix it but it didnt.
Can someone help me with this, its quite annoying.
Click to expand...
Click to collapse
It's a kernel issue. From what you've stated, stock 2.2, your device never got it's official 2.3 update. So, you have an old baseband P505. You should be able to flash ROMs made specificially for the P505 as well as P500 ROMs. Since your device is old baseband, you also have the option to flash P509 ROMs. P509 never got an official GB update so it's always an old baseband device, same with the P506. The catch with P500 ROMs and most P505 ROMs is they are build for new baseband so an additional patch, old baseband, will need to be applied after flashing the ROM. P506 devices use a different touchscreen than the others so you'll have issues installing one of those ROMs.
The old baseband patch is to get your radio, cell signal, working with new baseband ROMs. I hope this wasn't information overload If you used ROM Manager, it's possible that is screwed up the radio too. ROM Manager is not friendly to the Optimus One device family. Android Flash Recovery, link in my signature, is designed for flashing recoveries via fastboot and fastboot mode. You may, especially if color banding is an issue with your recovery, want to reflash your recovery too.
Oh, and have you seen the LG Optimus One FAQ?
I appreciate the reply you've giving, but this is my first time using the Optimus One.
You stated its a kernel issue, how would I go upon fixing a kernel issue?
You also stated I should reflash the recovery, is there a specific recovery I should be using?
Trytohaxme said:
I appreciate the reply you've giving, but this is my first time using the Optimus One.
You stated its a kernel issue, how would I go upon fixing a kernel issue?
You also stated I should reflash the recovery, is there a specific recovery I should be using?
Click to expand...
Click to collapse
For the kernel issue, you can search the forums here to find some that are compatible with your device. The kernel you need will depend on the version of Android you are wanting to install since there isn't a universal kernel for all Android versions. Most of the newer kernels are for ICS( Android 4.0 ) and JB( Android 4.1, 4.2 ). I've never used it but they say Franco has a kernel for GB ( Android 2.3 ). SweetnSour has a kernel for JB and the AndroidArmv6 Team has a new 3.0 kernel for JB.
If you like GB, then you may want to look at this CM7.2 ROM( Direct download ). It is for a P500, so you will need the old baseband patch from post #9 in the LG Optimus One FAQ. I''m using that ROM on my P509 ATM.
As for the recovery, I only suggest reflashing it if you are experiencing color issues with it too. I use CWM 5.0.2.7 Touch, but it will only allow P500 ROMs to be flashed. It's no big deal for me, but for someone new to the game it can be troublesome. CWM 5.0.2.0 is also a good recovery. I don't recommend using ROM Manager to flash anything. If you should decide to reflash your recovery, I would recommend using Android Flash Recovery for Windows( in my signature ) or FlashImage GUI which can be found in the Play Store.
It seems no matter what I do, the color will not correct.
I've tried switching roms, flashing a new kernel and recovery nothing seems to be working..
Trytohaxme said:
It seems no matter what I do, the color will not correct.
I've tried switching roms, flashing a new kernel and recovery nothing seems to be working..
Click to expand...
Click to collapse
Do you still have a backup of your stock ROM? I mean a backup that was made while in recovery mode. If you do you can try booting in to recovery and then try wiping and formatting everything but your sdcard. Then restore the backup you made and reboot the device. Other than that, I hate to say it, but I'm at a loss.
I just flashed the CM 7.2 ROM, and franco.Kernel | 2.6.35.10.
I just about did everything, but the color remains distorted once the actual ROM boots up.
Note* If the phone is off and I power it on, the first LG logo has perfect color and clarity but once the ROM kicks in the colors wacks out.
Edit - The phone no longer allows me to access CWM it's just a black screen.
Trytohaxme said:
I just flashed the CM 7.2 ROM, and franco.Kernel | 2.6.35.10.
I just about did everything, but the color remains distorted once the actual ROM boots up.
Note* If the phone is off and I power it on, the first LG logo has perfect color and clarity but once the ROM kicks in the colors wacks out.
Click to expand...
Click to collapse
The kernel is part of the boot image. It's possible that somehow your partitions have been damaged.
---------- Post added at 06:30 PM ---------- Previous post was at 06:27 PM ----------
Trytohaxme said:
I just flashed the CM 7.2 ROM, and franco.Kernel | 2.6.35.10.
I just about did everything, but the color remains distorted once the actual ROM boots up.
Note* If the phone is off and I power it on, the first LG logo has perfect color and clarity but once the ROM kicks in the colors wacks out.
Edit - The phone no longer allows me to access CWM it's just a black screen.
Click to expand...
Click to collapse
Hmm. I'm about convinced there's something wrong with your partition tables. Your data is getting corrupted.
So basically I just ruined the phone?
Trytohaxme said:
So basically I just ruined the phone?
Click to expand...
Click to collapse
Yes and no. If you can find or get a hold of the partition.mbn for your device you can use LGMDP to repair the partitions. The P500 one might work too, I'm not sure tho.
EDIT:
You can also install a recovery and ROM in the same process with LGMDP
shinobisoft said:
Yes and no. If you can find or get a hold of the partition.mbn for your device you can use LGMDP to repair the partitions. The P500 one might work too, I'm not sure tho.
EDIT:
You can also install a recovery and ROM in the same process with LGMDP
Click to expand...
Click to collapse
Yeah, I'm screwed I have no idea how to do that so I'm just gonna have to buy a new phone.. :crying:
Im sorry didn't read too well, bad luck, i didn't read your posts before, i knew how to fix the blue colors on your screen
gabo_lope said:
Im sorry didn't read too well, bad luck i didn't read your posts before i knew how to fix the blue colors on your screen
Click to expand...
Click to collapse
Well how exactly do you fix the screen color than?
Trytohaxme said:
Well how exactly do you fix the screen color than?
Click to expand...
Click to collapse
you only had to flash this on your p505 after the rom https://code.google.com/p/sweetnsour-kernel/downloads/list; one of these
kernel-20130224_1312.zip version4-CFS-P505-P506 for battery life
kernel-20130224_1306.zip version4-BFS-P505-P506 for performance
You have saved my phone my good sir, and I thank you greatly!
Now that I have the correct kernel, can I install different roms now?
Yes, but only ics and jellybean roms , if you use the kernel on gingerbread you will get a lot of troubles...
I just flashed the unofficial CM 10.1, and booted the phone and the color was diffused again.
So I flashed the kernel again and booted the phone, and everything is working perfectly.
Thank you so much!
P.S - CM 10.1 doesn't come with Google Apps or Rom manager, how do I get that back?
To get the google apps you will need to flash a gapps.zip, but first you need to trim the cm 10.1 rom, because
The recommended gapps package is not quite small enough to fit along with the rom in our limited /system partition. The size of the rom can be trimmed by deleting or converting some system apps to user apps, deleting unwanted ringtones and fonts.
Click to expand...
Click to collapse
Also
Take off anything that can be installed from Play, same for gapps.zip!!
Click to expand...
Click to collapse
There is a tool designed for that, is in shinobisoft's signature, oone rom editor, download that tool and in the help docs you will find information about trimming, and what can be removed safely... Here it is http://forum.xda-developers.com/showthread.php?t=1959023
If this the first time you are installing roms, i will recommmend you to stay in ice cream sandwich, because is more stable, and it has a lot better battery life than jellybean...
Hi,
I Flash this Custom Rom on Gionee E3& getting some problem with the screen, my screen goes off automatically & i have to press volume rocker then it came back for a Second & then goes off again every thing is working fine except screen issue after flashing the Rom.
If Any one have solution to this let me know. I have made a small VIDEO of this problem kindly check it & help me out.
Need Solution
Can any one provide the solution of this problem....
try flashing your stock firmware (the actual os that came with your phone)... if all is working normally then the problem is in the rom and you'll have to contact the developer of the rom.
Gauraav said:
Hi,
I Flash this Custom Rom on Gionee E3& getting some problem with the screen, my screen goes off automatically & i have to press volume rocker then it came back for a Second & then goes off again every thing is working fine except screen issue after flashing the Rom.
If Any one have solution to this let me know. I have made a small VIDEO of this problem kindly check it & help me out.
Click to expand...
Click to collapse
Is it an issue with screen tun off time layout?
How to solve that issue?
daemol said:
Is it an issue with screen tun off time layout?
Click to expand...
Click to collapse
How to solve that issue? Tell me the procedure?
Gauraav said:
How to solve that issue? Tell me the procedure?
Click to expand...
Click to collapse
screen time out is in you settings under display i believe.
You might check the build.prop file under /system for weird settings.
Also look for settings for your proximity sensor to recalibrate, it might be that.
It can also be a driver issue, just revert to stock rom then.
Even I have tried the same ROM on my E3.Its worked perfectly.But when I switched back to Stock ROM I faced the similar issue after an update.
Flashing the perfect ROM is really important to avoid these bugs.
I got it to service center and they flashed my E3 with the original stock one and the issue was sloved.
Stock ROM available in the net is not a perfect one.
Try a different ROM mate.
Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!