My friend's LG P925 would make one call then if she made any subsequent calls the called person would not hear her even though my friend could hear them just fine (didn't matter if the second call is to the same or a different person).
I thought if I updated OS from Gingerbread to ICS it would solve the issue. Well I left it updating OS on my laptop last night via LG software. This morning I found it had completed the update but now phone's screen is greenish. All I see is black and green or a greenish screen.
I tried removing battery, turn it off , restart and such but the nothing helped the greenish display. I didn't have time to test if the calling issue was fixed.
-Now my question is how do I fix this screen,
-What causes the phone to make one good call then mess up subsequent calls?
-What is the solution for that if not updating the OS
-I am also curious if updating OS also updates the phone's radios?
Related
Hello Guys,
a Friend bought a used i9000 on ebay for 130€ from a business man, which got a ne phone from his company and sold hin mobile on ebay and he asked me for a litte work around of his "new" phone.
Optically is the phone perfect BUT if I take a call on Android 2.3.6 display stays black (with backlight) and I can make the call. But I can't do anything more, hang up etc. If the opponent hangs up, I hear the hang up sound but display stays black and thephone wount do anything. So it's needet to pull battery, put it back and restart the phone. On doing a call, the phone has similar problems, it freezes.
After a couple of re-flashes with odin nothing changed.
So I tryed to switch to actual android OS. I flashed SlimBean 2.7. Every thing workes well. but even call-issues. If i receive a call, the phone woun't do anythin and it keeps ringing and "holds" the call for exactly 32 seconds. Now I can talk with the caller. But most callers don't wait 32 seconds to call to me If I do a call in JB I can talk from the first second on, but display freezes and I can't hang up. Thats the state for around 28 seconds and then phone will response normally and I can hang on and do everything I whant.
Even in Slim I tryed reflash a fiew times with no cahnge.
Has anyone an idea?
I think thats a hardware related problem. But in fact its possible to do a call, but only with that issues/delays. So I need a solution, that JB (SlimBean 2.7) don't "hold" the call/freezes for 32 seconds. I think because its every time 32 seconds, thats a fix value in JB. so I need something to cahnge the value from 32 secs to may be 0 oder maximum 5. But thats only guessed by me so I need help of a PRO here to solve that nerving issue.
I also tryed to install other dialers, but thats not a good solution, because the use for calling the stock rom dialer (phone.apk), damn
Please help me guys (sorry for my bad english )
UPDATE: I did read a litte in web and found, that the light sensor could cause issues in calling (start and end). So I downloaded a app whitch will show me he values of the light sensor. Ands its true, the sensor will show me whole time same values. I changed the sensor od the device of my friend and mine but that does not solve the problem. same issue.
In second Post I'll load a some Pictures of both devices up. My device shows around 30 lux and the one of my friend around 5.
UPDATE 2: After some more reading in web I found more guys with same call problem but no solution. May be it could help to disable GP2A Driver oder better only to overwrite the lightsensor value with a fix one.
UPDATE 3: OK I tested with 3 apps and the proximity sensor of the phone is broken ...now i need a solution to disable it or set a fix value in android so that the sensor is unused.
Any ideas?
UPDATE 4: I downloaded the "Hardware Disable" app from Play store and disabled GP2A.
It works for now, I just have to switch off the screen manually by pushing power button at a call and turn it on by pushing power again. But thats no problem for me anf my friend and much better as the call related freezes.
But I need at every startup to confirm to disable the sensor. So I'm looking for a permanent solution for this. Also because the device feels a little bit laggy now.
Pics
SOLUTION
So Guys I found a good working solution fpr proximity sensor delay, 32 second freeze by taking a call.
I wrote my Solution in SlimBean thread
http://forum.xda-developers.com/showpost.php?p=32809014&postcount=4406
Schould work on any ROM (GB, ICS and JB) because they all use the same Hardware .so (sensors.aries.so in this case)
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
tigane1 said:
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
Click to expand...
Click to collapse
Try aoip its up to date and works good.
schuylkillparanormal said:
Try aoip its up to date and works good.
Click to expand...
Click to collapse
working on downloading it but the download keeps failing -_-
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Mwas. said:
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes rom and cache/dalvik. And if I forgot I went back and wiped and re-installed it.
tigane1 said:
Yes rom and cachredowvik. And if I forgot I went back and wiped and re-installed it.
Click to expand...
Click to collapse
There's nothing wrong with the link try redownloading the ROM something might of got corrupted.
I fixed it. Kind of
I did a bit more searching using some different terms and people were having trouble with the proximity sensor on their phones causing similar problems so I turned mine off and the problem corrected itself! So now I guess I just have to deal without having a functioning proximity sensor during calls, oh well, not a biggie. I appreciate the help though guys.
Well ,it has happened before but I didn't want to exaggerate it ,so I left it just as it was until today .It's completely stock ,with custom recovery .It has happened to me since 5.0 and up until now 5.1 .
It doesn't happen always ,just "occasionally" when there is an incoming call ,Nexus 6 turns off itself .It happened now that I didn't even hear that it rang ,it just turned off ,but I know that my dad called me .
Has anyone ever experienced such issue ,is there a fix ?
To mention that it also gives an odd sound befire turning off :/
Same thing happening for me also with Nexus 6
And this keeps happening more frequently over recent months. This also happens when battery is below 30% and I am taking HDR+ photo. Maybe related to aging battery and apps getting more and more power hungry..?
@pauliusz: First, kudos for actually searching for a thread related to your problem. Too many don't bother. Second, replace your battery, as the shutdowns are in fact a direct result of the battery's age.
I've recently flashed the stock rom for my Xperia V as described below for locked bootloader.
http://forum.xda-developers.com/showthread.php?t=2796554
Since then I face problems with the display/phone acting weirdly . About twice a day I can't turn the display back on (display unlock). In this state the phone actually freezes somehow. One strange exampled I've seen today: I received a mail message, with the set signal sound and notification LED. I wanted to check the message but couldn't turn on the display. So I checked if I can call myself with another phone but the mailbox turned on immediately. The notification LED was still active so I'm not sure if the phone actually freezed or not. The only thing I can do at this state is to remove the battery and restart the phone.
Another problem I've since flashing the rom is that when I start a call is that the display turns off immediately no matter if I place my finger/face over the proximity sensor or not. Funny thing is that the call can be held as usual, but after that I'm not able to hold the call as the display won't turn on until the call partner ends it. When he has ended the call the display turns back on. Right now I really don't know what to do.
Here is the history how the problem started:
- dropped phone on floor and display broke
- exchanged display
- I've had installed Xposed installer on external SD card and modified some things on the launcher. While I was waiting for the new display I've used the SD card in a different phone. This has somehow messed with the Xposed settings I assume.
- After I booted my phone with the new display in place and external SD inserted the UI crashed all the time and the launcher won't come back. So I've restored the system with the androids included function.
- This is where I first saw the above described problem.
- I've tried a different, modded rom. With this the display problem didn't occur but the battery performance was really bad.
- Installed stock rom from link above. Now problem with display present again. So maybe there is an issue with the original 4.3 rom?
Has anybody experienced the same issues as I do right now? I really don't know what to do but the problems really annoy me.
Thanks!
Try to repair it using PC companion
Didn't work. Same problem remains.
Ok, I was able to fix the issue with the display turning itself off during voice call.
The headphone connector does somehow connect the light and proximity sensor to the phones mainboard. This connector didn't sit properly inside the middle phone case which cause a bad connection to the sensors. I've reassembled the whole phone and now this problem has disappeared.
The other problem still remains, I hoped it is linked to the display proximity sensor problem, but now it is clear that this has some other source.
Is there some kind of app monitor available? I assume that there is some app which causes the various hang up, but I have plenty of them installed and deinstalling always just one of them and monitor for various days will last for months.
Is there any possiblity to find out if the lock ups are caused by some app?
Really nobody in here who has any ideas? I've now exchanged the display to a new one as I thought it's caused by a faulty display connector, but the problem remained. I'm running out of ideas now.
Hello,
After updating Android Wear (application) to version 2.8, after a certain time the function of the always-on-screen stops working. The screen flashes, the white color turns pink and the screen goes out, but it happens only when the Ambient Mode is on (the full mode doesn’t break down). When, I did the reset factory settings, everything started working again. Afterwards, the situation is repeated, a few hours after the update the screen is not working properly again. The update introduces changes which I liked very much, among other things, the black interface, so I don’t consider going back to the old version. Does anyone know how to solve the problem?
I noticed mine turned off once.. but it was right around while it was doing the update... so I chalked it up to a hiccup while it was installing... right now it seems to be using ambient mode perfectly.
I only use the Line Watchface / Mini Wear Launcher
Yesterday I got one more small update and since then there is no problem