[Q] Problem on [UNOFFICIAL][ROM]CyanogenMod 7.2 - Bug black screen - Optimus One, P500, V Q&A, Help & Troubleshooting

I'm new user so i can't replay here
http://forum.xda-developers.com/showthread.php?t=2314436
I flashed the rom of Fitamp with no change and following instruction.
http://i.cubeupload.com/meL93n.png
http://i.cubeupload.com/9K8JSq.png
I have baseband V20g, on phoned is showed stranges char.
The bug is that when the phone become black for the incoming call, later remains black.
5 times over 5. I have to remove battery or to plug the usb to exit from this state.
Before i flashed the: [ROM][4.1.2][CM10][UNOFFICIAL]LG Optimus One Family CM10[Jan. 8, 2013: Build 7/Final]
http://forum.xda-developers.com/showthread.php?t=1811325
And sometimes the same bug happened.
For this bug i changed the ROM:crying:. But now i'm in a worse situation.

There is some stupid error on tapatalk/xda which is causing my post to get deleted or get reposted on this thread (That's the reason I am editing this post many times :banghead: )
Will try to post your question in the thread after some time
Sent from my GT-I9082 using xda premium

After some other test:
system exit from the "black screen state" when i plug usb cable to pc, not to the charger.
Setting->Call setting->Always use proximity:
when i call the screen never shut down. Nomore this bug, but is another bug
Setting->Call setting->Keep screen awake:
nothing change. Same bug

Today also with:
Setting->Call setting->Always use proximity
the screen remains black.

Yesterday i downloaded and flashed the DJNoXD's kernel v2.5.8-ta-vsyncOff-20121129-signed.
I made 1 call and the bug didn't happen.

Related

[Q] Nexus S screen turns off during/after a call

Is there anyone else having the same issue as I have? My Nexus S screen would turn off during/after a call, sometimes it would turn on when i press the power button and sometimes it would not. I am on stock Android 2.3.4 baseband I9020AUCKD1 Kerne version 2.6.36.7-ge382d80 android-build2apa28 #1 Build number GRJ22. I just got the OTA update the other day. Is this some kind of bug that comes with the update? I hope someone could shed a light on this matter. BTW I am on At&t if that helps. Thanks in advance!
Have den same problem in my phone to
Android 2.3.4
i9023
The screen turn's off when i answer a phone call.
I think it turns off when your in a call so that you don't touch the screen, it can detect you proximity , try on the middle of a call take the phone from your ear the screen should turn on.
Sent from my Nexus S using XDA App
I have the same problem... sometimes the display stays black after the call is finished. Then I have to press the power-button.
Rom: MIUI-1.8.19
Kernel: Netachy-1.3.7
I don't have a solution for this problem, but it certainly annoys me too.
It seems that the screen lock timer is still running while the call is in progress. You can verify this by trying to hit the home screen in the middle of the call and seeing the lock screen come up.
I also have this problem and can be very annoying.
This also happens sometimes when I am watching flash video content. As soon as the video finishes the display turns off. The person who said something about the idle timer continuing to count idle time sounds plausible. As soon as the app that was preventing the sleep/lock ends it sleeps immediately.
Sent from my Nexus S using Tapatalk
I think its the in pocket detection... does anyone how to update my kernel from 2.6.35.7 to 2.6.36.7?im not sure how to do?
I think you should just wait, as its going to be March real soon and we should start to see updates for the Nexus S and 4g coming up. If you really can't wait, go ahead .
mclee235 said:
I think its the in pocket detection... does anyone how to update my kernel from 2.6.35.7 to 2.6.36.7?im not sure how to do?
Click to expand...
Click to collapse
Are you rooted? Are you on a customer ROM?
If I'm not wrong, you can only update your unrooted stock ROM when you get an official update. (Somebody more experienced please confirm this)
However, once rooted and with a custom ICS ROM there is a whole list of Kernels that can be flashed and each one has the instructions on their respective pages.
dino993 said:
I think it turns off when your in a call so that you don't touch the screen, it can detect you proximity , try on the middle of a call take the phone from your ear the screen should turn on.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
you are correct
is that possible:
1. proximity sensor during the call in order to avoid your face accidentally touched the screen
2. over time to lockscreen , like 1 minute , but you spoke 2 minutes ... and then phone automatically screen off ?
I exprienced that sometime in stock GB ROM and custom GB ROM. I have yet to experience it in ICS so far. It could be that when you try to wake the screen up, the phone may actually try to wake up but at that time your phone call may take higher priority -- cpu wise, so it is busy processing your phone call instead. I'm thinking Windows processing priority and I'm a noob.. Or the proximity sensor processing got stuck.
This does actually happen sometimes on my 2.3.6 stock ROM (i9023). Never had problems with turning the screen back on afterwards, though.

Issue with the display - post official ICS update

Hi,
I upgraded my Samsung Galaxy R today to the official ICS version. The phone was on the stock ROM (Gingerbread) earlier.
I did the update using KIES and the update went without any errors. Post upgrade, my Samsung Galaxy R's screen isn't working normally when viewing things involving pure black background. For example, when I open the "Settings" and try scrolling through the list that is shown in the black background, the text leaves streaking effect (leading to multi color dots in the black areas). As a result, the text in the black background becomes scrambled. This problem also happens when the phone is powered on and the start up splash screen (samsung logo in pure black background) appears. The weird fact is that the screen looks absolutely normal when there is no "pure black" element involved in the display and all other colors looks okay.
Just to confirm, I installed the Gingerbread version again (using custom ROM) and the screen works perfectly okay even when scrolling through the various settings with pure black background. Splash screen at the start up doesn't leave any streaks/dots either.
Finally, I tried to install ICS once again in OTA mode and the display issue started happening again. Please find attached the image that shows the problem.
Could you please let me know if I am missing something.
P.S: One more interesting point to note is that the problem happens only when the screen is kept in the portrait mode. The moment I turn the phone to the landscape mode, the screen becomes perfectly clean.
Thanks,
KB.
Hi,
I have attached a couple more screenshots that illustrates the problem.
The issue gets fixed once I put the phone in landscape mode and the issue doesn't happen when displaying colors other than black.
Thanks!
ece2k2 said:
Hi,
I have attached a couple more screenshots that illustrates the problem.
The issue gets fixed once I put the phone in landscape mode and the issue doesn't happen when displaying colors other than black.
Thanks!
Click to expand...
Click to collapse
Hmmm..Its may be lag of ICS. can you give me details like, is it was happening to you in GB as well..??
Or have you flashed any other ROM for the fix..??
kataria.vikesh said:
Hmmm..Its may be lag of ICS. can you give me details like, is it was happening to you in GB as well..??
Or have you flashed any other ROM for the fix..??
Click to expand...
Click to collapse
Hi Vikesh,
I am not facing any issues with GB. The display is absolutely perfect when I tried out GB. I tried the following sequence:
1. The phone was working perfectly in GB and I decided to upgrade to the official ICS
2. Upgraded my phone to ICS using Samsung Kies. Found the display issue the minute ICS started
3. Worried about the problem, I tried flashing the stock GB ROM. This fixed the display issue
4. Tried upgrading to ICS once again - without KIES this time (using Wifi - OTA). Upgrade went without any error, but the display problem started once again after the upgrade
Currently I am using the ICS and it works fine except for the aforementioned display problem. Even the display is pretty responsive and I don't feel any lag while using the phone. Display issue gets sorted the moment I turn the phone to the landscape mode and the problem happens only with black backgrounds in the display.
I am not sure what I am supposed to do and I am thinking of moving back to GB.
Please let me know if you need any other information.
Thanks,
KB.
ece2k2 said:
Hi Vikesh,
I am not facing any issues with GB. The display is absolutely perfect when I tried out GB. I tried the following sequence:
1. The phone was working perfectly in GB and I decided to upgrade to the official ICS
2. Upgraded my phone to ICS using Samsung Kies. Found the display issue the minute ICS started
3. Worried about the problem, I tried flashing the stock GB ROM. This fixed the display issue
4. Tried upgrading to ICS once again - without KIES this time (using Wifi - OTA). Upgrade went without any error, but the display problem started once again after the upgrade
Currently I am using the ICS and it works fine except for the aforementioned display problem. Even the display is pretty responsive and I don't feel any lag while using the phone. Display issue gets sorted the moment I turn the phone to the landscape mode and the problem happens only with black backgrounds in the display.
I am not sure what I am supposed to do and I am thinking of moving back to GB.
Please let me know if you need any other information.
Thanks,
KB.
Click to expand...
Click to collapse
buddy, This kinda problem I never faced. Might b few problem while updating your device, is occurring (which is not reporting as error). So, My suggestion is can you please use ODIN V3.07 & flash it using Offiline mode. i.e. Flashing ICS using ODIN.
Procedure is here -> Click here
First 3 question & answer will let you know everything.
If still problem persist, then do visit SSC or flash latest cm10.1 & based ROM over it.

[Completed] Nexus 5 BLACK SCREEN ( FASTBOOT ONLY)

I had my nexus 5 using multirom manager i had liquid smooth and paranoid android roms on it and i flashed ubuntu too the phone was working fine on all of the three roms.. the only issue i had was the microphone that wasn't working on phone calls but it worked only on speakers so i tried to change the mic piece and same the mic wasn't working. So i thought that it was something wrong with the software and i tried to flash a different kernel (Franko Kernel ) and i tried to flash couple GAPPS and nothing still with the mic problem and in the ROM i had a message that says com.play.services not responding so i tried to go on play store and upgrade the services and the play store wasn't working so i dowloaded some play services from chrome, after i installed the apt file i tried to reboot the phone and as soon as i did the reboot the screen had some rainbow an gray colored lines all over the screen horizontal and vertical lines, after that the screen was only black but i could see the backlight on it. I tried to restore stock with fast boot and still nothing i restored android 4.4.4,5.0,5.0.1 and nothing happen the screen was still black, the only thing was that the phone was able to be seen on fast boot and so i thought that the problem was the screen or the flex cable so i tried to buy a new screen i did ordered it from eBay and last night i changed the screen, but nothing worked I'm still having the black screen and the phone is still going on fast boot mode but I'm not able to use my phone... PLEASE HELPPP !!!!
Hi
Thanks for writing to us at XDA Assist. I had a quick search and found a great q&a thread for your device here:
[HELP THREAD] Nexus 5 | Ask any question
I'd suggest you ask your question there, that way it'll reach the most suitable people to answer your question.
Thread closed, thanks.

Issues everywhere, hardware problem?

Hi there,
I'm experiencing massive issues with the Nexus 5 of my wife. Everything is basically broken
It started 2 days ago, the phone start rebooting without reason and heating a lot. Applications sometimes hang for a long time, or the screen stays black with only the notification bar displayed.
Wifi is never able to connect, even though the welcome screen is able to display available wifi. On the welcome screen after a fresh flash, nothing happen when I enter the WIFI password and try to connect. Only the "ignore" button is available, as if I have done nothing.
LTE connectivity seems to work, but I have removed the SIM card for further testing, so it's hard to say.
Parameters screen sometimes works, sometimes won't. Battery consumption screen never works.
The phone is never able to shutdown properly, it hangs forever on the shutdown loading circle; I always have to hard-reboot.
I changed the battery (I had a spare one ordered few days before the problem occurs just to see if it improves the battery life), with no luck.
When I opened the phone to change the battery, it is clear the heat come from the CPU.
I tried (I wiped everything each time in between):
- factory reset
- flash a stock rom from Google website (MMB29K)
- flash latest Cyanogenmod rom (ZNH0EAO2NM)
I have the same issues with any of those 3 roms. I captured some logs while running MMB29K and ZNH0EAO2NM:
Stock (MMB29K) logs: https://drive.google.com/open?id=0B-CDc3nzF3e3M28tM2xjTmJKa28
Cyanogenmod (ZNH0EAO2NM) logs: https://drive.google.com/open?id=0B-CDc3nzF3e3TVUtTmExZDBLUms
The only state where the phone is stable is when TWRP is booted, which is not so useful...
I'm thinking of a hardware issue, but is there anything else I can try? What do you think?
Thanks a lot!
Nobody?
I said the same thing in another post. The fact that flashing different ROMs with the same issues kinda point to hardware problem. I'd guess something fried on the motherboard and it's causing weird behavior. Funny thing, the other post also reported wifi not connecting issues, so I'm thinking there is something that breaks in older Nexus 5 phones that cause wifi issues along with other random reboot problems.

[HELP] Partially Blank Screen but otherwise active device OR Sleep of Death

Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
pesche80 said:
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
pesche80 said:
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Click to expand...
Click to collapse
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Click to expand...
Click to collapse
Thanks!
I'm going to consider a new display... but not a new gf
pesche80 said:
Thanks!
I'm going to consider a new display... but not a new gf
Click to expand...
Click to collapse
Don't forget to invite me to your wedding.

Categories

Resources