Hi guys
I know this question has come up quite a few times, but i have just spend the last hour searching all the threads and not really come up with any results. Does anyone know how to get rid of the black screen during/after call issue? I have tried adding ro.lge.proximity.delay=25 and mot.proximity.delay=25 to build.prop but this does not get rid of the issue properly. There is only ever been 1 rom that i have used that managed to get rid of this problem, but they wont tell me how they did it and i cant fidure it out lol. Anyone?
thanks
brezzz
I'm not 100% certain what causes it, there seem to be various reasons. I found it was cured by ram management, something like the supercharger script and/or a cache cleaner resolved it. Most, if not all, custom roms don't have the problem due to being stripped of bloatware.
ah ok, everytime i used v6 it seemed to cause problems, just seems weird that it only causes problems when in-call. SE-Tweaked is the only rom that seemed to completely fix the problem but it seems weird that some roms only do it now and again. I used to think its was proximity sensor that caused the problem but it seems worse in sunlight so maybe light sensor?
There's a few things that can cause it, sometimes grease on the sensor or a cover. The fix you used works, but I found it was more like the phone hanging on the call process. Tried increased cpu frequency during call and even an app on the market, but decent ram management does the trick.
sinkster©
brilliant, thanks for your help buddy
Hi, Which ROM has the problem solved. I would like to try this, please name the ROM. Thanks
Related
Hi Guys,
I am currently using a Cell Pro Rom and I find that my it keeps flipping to landscape too often when I have my phone in portrait.
I always have to give it a shake to fix itself and it does get a bit annoying.
Does anyone know how to fix this?
(I remember I may have (not certain) that I might have changed the Sensor registry when I first got it, but I am not certain, does anyone know the default measurements?)
Any ideas are welcomed.
Many thanks in advance!
Did you ask in the Cell Pro ROM thread? Seems a more logical place to ask. I tried that one out and did not have the issue you are describing. Good ROM too.
There is a G-Sensor Calibration in Settings- System.
kimtyson said:
Did you ask in the Cell Pro ROM thread? Seems a more logical place to ask. I tried that one out and did not have the issue you are describing. Good ROM too.
There is a G-Sensor Calibration in Settings- System.
Click to expand...
Click to collapse
I'm fearing the fact that I may have changed something in the registery as I got all excited the day i got the phone and went through the tweaks in the wiki.
I am not certain if I made any changes regarding the g sensor so I was wondering if anyone knows the defaults or if there is a .cab or ROM to flash to system restore.
Any clues?
Many thanks in advance
To me the g-sensor is a gimmick. I find it annoying and totally useless so I've turned mine off altogether. If I want the screen to rotate I push the keyboard out. I really don't see any use for it.
I did think the only use I had for it was the face down hands free thing but have since decided that I'd be quite happy to push a button for that. Hardly a hassle.
Really hoping someone can help me. I have had my Defy for a few months and have always been on a custom SBF but continue to experience problems with the Defy working amazingly for hours and then sometimes I turn the screen on and the Defy is working in some kind of super slow mode and opening anything takes ages, everything does eventually open so it’s not crashed but just going super slow!
I am currently on SBF 3.4.2-177 Nordic but have had the same problem on different SBF’s so either my phone has a hardware issue or its some software I have on my phone, I am currently on Beta 6 of CM7 and have had this issue on other betas of CM7 but have never heard of anyone else with this issue. The phone will sometimes go a whole day without the issue also which is weird. It is not overclocked either. When it goes into what I now call superslow mode I have checked to see what the processor and memory usage are and both are around 60% used not being topped out at all. I have even used StabiltyTest to test the memory and CPU when the problem is occurring and both run through fine.
I really would love to know if anyone else had a similar problem or if they know what is causing it or how I can find out what is causing it without removing every bit of software I use. The only piece of software I use regularly that runs in the background is Juicedefender so I am going to remove this now and see what happens over a few days.
Any help would be amazing
Many Thanks
Bob
Did you install the latest patch for the auto-brightness issue? or Did you turn off the auto-brightness?
Thanks for the fast reply I have already installed the latest patch for auto-brightness issue but still have the problem
Was the phone slow in the stock ROM? I mean that's really wired that the problem appears on each SBF
Hi mys_721x, I only had the stock ROM for a matter of days when I first had the phone so really cant remember but I am thinking I may have to go back to see if I do still have problems if no one else can suggest anything else. Cheers
I have this same problem. Only fix seems to be a reboot whenever it happens
bobdigby said:
Hi mys_721x, I only had the stock ROM for a matter of days when I first had the phone so really cant remember but I am thinking I may have to go back to see if I do still have problems if no one else can suggest anything else. Cheers
Click to expand...
Click to collapse
Same here, my phone suddenly becomes sluggish and unusable. Yesterday it was stuck on 100% cpu usage, I entered the task manager to see what was wrong and there wasn't any application that was using the cpu.
Only solution is to reboot everyday.
Glad to see I am not the only one, yea a reboot does the job sometimes it can be twice a day sometimes I don't see it for a few days, do you guys have juice defender installed by any chance as thats the only real program which stays running in my background which is extra to the roms I have used, cheers for your input, lets hope we can figure out whats going on.
Bob
Sent from my MB525 using XDA Premium App
I had it to in the past. When i tried to lock the phone it took long time and it wouldn't unlock for a wile 1-2min what is verry long if your waiting and afterwards scrolling was lame.
Don't know what I did, but it's gone now. Now only when out of memory(dhuu!)
I think I wiped it cleen, went to a 2.2 and didn't have it again, now on CM.
Do you see in spare parts any apps using mutch cpu?
Weirdest thing that happens to me..
Every hour/day the phone loads up some applications prepared to start when I turn on the phone..
That means that if I close say, tigertext or Skype, the following day, without turning off the phone, hey are running again.. wtf?
EDIT: A way of checking what's using the CPU, if you're on Froyo, is check the application manager to check for services CPU usage
Yea I have no idea what is causing it but little to no cpu usage when it happens, when I lock on cm7 the tv effect for screen off is super slow motion its really strange, did a clean wipe yesterday and did its first slow down today just before post, cheers
Sent from my MB525 using XDA Premium App
Anyone have any luck with this? Mine just seems to be getting worse and worse on CM7.
Update: I've opened a issue for this on Github. You can go there to post new information / symptoms so that hopefully it can be fixed: https://github.com/Quarx2k/android_device_motorola_umts_jordan/issues/204
Hi dasbin,
Since uninstalling Juicedefender from my phone I have not had this issue once, it has now been 3 days which is probably a record for me so I would say that it was causing me the issue, do you have juicedefender installed? I am now using green power it is much better so far.
Cheers
I've seen a similar post to this way back in the day when I first rooted my phone, but since then have been unable to relocate said post, so I'll just post here as I've noticed this to be a constant problem, perhaps GB related.
Days where I don't make any phone calls I get decent battery life, about 1% every 2 hours and that's listening to music. But god forbid I have to make a phone call because then Dialer remains on consuming my sensor in spare parts. I've disabled just about everything in call settings related to sensors and even tried turning my BT on as I read it might fix it, no dice. The only way to fix atm is to restart or perform a hot reboot.
Anybody else experiencing this or have found a fix? Currently running Decks 1.3d and thinking of going back to a Sense rom cuz I never dealt with this crap before I tried AOSP, even though I love and prefer AOSP over Sense.
Naturesretard said:
I've seen a similar post to this way back in the day when I first rooted my phone, but since then have been unable to relocate said post, so I'll just post here as I've noticed this to be a constant problem, perhaps GB related.
Days where I don't make any phone calls I get decent battery life, about 1% every 2 hours and that's listening to music. But god forbid I have to make a phone call because then Dialer remains on consuming my sensor in spare parts. I've disabled just about everything in call settings related to sensors and even tried turning my BT on as I read it might fix it, no dice. The only way to fix atm is to restart or perform a hot reboot.
Anybody else experiencing this or have found a fix? Currently running Decks 1.3d and thinking of going back to a Sense rom cuz I never dealt with this crap before I tried AOSP, even though I love and prefer AOSP over Sense.
Click to expand...
Click to collapse
I would look for the topic about wake lock, there is a possible fix in there if I remember right. Also could try to reflash decks, I've never had a problem.
Sent from my PC36100 using xda premium
I agree with the guy above me, you should check the thread of whatever ROM your using as well, and for a quick fix you could always just push the Power/Screen Lock button
http://forum.xda-developers.com/showthread.php?p=14814224
Sent from my PC36100 using xda premium
Hello xda members! I have been experiencing a strange problem with my "T-Mobile G2"'s microphone and would like to share it with you in case you had any insight on it:
My phone's microphone is not working - I cannot use voice input, music recognition services, etc. all it picks up is silence. What makes it a "strange" problem? Well, the microphone will work during calls, but ONLY IF I first snap out the keyboard and then snap it back in! Sometimes the microphone will fade out and then go silent again, at which point I'll open/close the keyboard again so that the other party can hear me again.
I thought it was software at first, but then I flashed it to stock and still had the same issue. Now I'm worried it might be a problem with the ribbon cable that connects the two halves. Have any of you ever heard of a similar problem? Any suggestions as to how I might fix it?
If it is intermittent and you reflashed then my guess would be hardware like you suggested.
Most likely you mic is loose. Does it behave the same as opening and closing if you just hit it or shake it?
Sent from my ghdudsjihfr using dhhcdfhuf.
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
jervill said:
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
Click to expand...
Click to collapse
Do you superwipe?
killj0y said:
Do you superwipe?
Click to expand...
Click to collapse
Yup I did use superwipe.
Incidentally, the issue returned after 2 days of working perfectly. Doing a wipe and then installing that same ROM fresh (not a backup) did not fix it so that new most likely ROM had nothing to do with it. I'm giving up then and calling this a hardware issue, period. I guess it's a good thing that the HTC One phones are are coming out soon!
Hi everyone,
TL;DR: I have an issue with the touchscreen of my Find 7 qhd (x9076), while on any other ROM than stock it my touchscreen glitches or something.
After installing a custom Rom, like PA, Dirty unicorns, CM, Nameless or any other available for this device (I believe I've tried all of them). The device works just like it should, nothing wrong with the touchscreen. But after like half a day, it starts to 'glitch'. Sensitivity is very low, when I press here it detects a press somewhere else.
I've got a temporary solution which is wiping the cache in recovery, then it works for a short period of time, but then it starts gliching again..
On stock rom the issue doesn't exists, but I realy do want to use a custom one.
Is anyone experiencing the same issue? Or maybe someone who has a solution?
Thanks in advance!
P.s every install is a full wipe, tried multiple recoveries, non-unified
I've read that the touchscreen fixes implemented by Oppo only work on ColorOS even though ROM makers have already implemented the fixes into the Roms. I'm not sure why, though
farenteria said:
I've read that the touchscreen fixes implemented by Oppo only work on ColorOS even though ROM makers have already implemented the fixes into the Roms. I'm not sure why, though
Click to expand...
Click to collapse
Hmm that's unfortunate, but it seems to me that I am one of a few people having trouble with this? Why don't other x9076 users have this problem?
B-vb said:
Hmm that's unfortunate, but it seems to me that I am one of a few people having trouble with this? Why don't other x9076 users have this problem?
Click to expand...
Click to collapse
Not sure. I personally have never had that problem
I want to bump this thread, i have this problem aswell and still it isnt fixed. anyone has a idea what to do about it ?
B-vb said:
Hi everyone,
TL;DR: I have an issue with the touchscreen of my Find 7 qhd (x9076), while on any other ROM than stock it my touchscreen glitches or something.
After installing a custom Rom, like PA, Dirty unicorns, CM, Nameless or any other available for this device (I believe I've tried all of them). The device works just like it should, nothing wrong with the touchscreen. But after like half a day, it starts to 'glitch'. Sensitivity is very low, when I press here it detects a press somewhere else.
I've got a temporary solution which is wiping the cache in recovery, then it works for a short period of time, but then it starts gliching again..
On stock rom the issue doesn't exists, but I realy do want to use a custom one.
Is anyone experiencing the same issue? Or maybe someone who has a solution?
Thanks in advance!
P.s every install is a full wipe, tried multiple recoveries, non-unified
Click to expand...
Click to collapse
Try to flash back stock recovery then flash COS 1.20 in systembase, then upgrade to COS 1.25, Then upgrade to 2.0 or above. Then flash custom recovery and rom again. This is the step you will not have problem in custom Rom. I am 100% sure.
Sent from my X9070 using XDA Free mobile app
I have the same problem, and I'm running Stock OS.
v2.1.4i Beta
This is how I bought the phone, interesting that it reads Beta...
I've updated to the latest firmware and still having touch screen sensitivity issues.
Someone has got too have some advise.... Oppoooooo.....
TouchScreen Auto Test - FAIL
I did the TouchScreen Auto Test and showed FAIL. Has anyone else shown this error?
Hi, I am having exactly same touch screen problem with custom roms, have tried both Omni and crDroid.
Is there a solution for this? I didn't have this problem in COS before.
What's the auto test?
I‘m on COS 2.1.5I and sensitivity works ok so far. I did have auto brightness problems but xposed and gravitybox has helped me adjust a lot of that out. Now it doesn‘t over dim in low light.
Auto test in COS is ok, I only had this problem in custom Roms, COS worked smoothly,so I reckon it's could be driver issue in custom Rom, maybe there are new fix for some panels are not included in custom Rom.
I never had any problems with touchscreen on find 7 until now. I have been extremely satisfied with this device until now. I have the find 7 9076.
There is a lengthy discussion of this touchscreen problem on the oppo forums.
My opinion is, it has nothing to do with the rom or firmware. It is a physical problem caused by heat. Once overheated, the digitizer gets somehow damaged.
I left my phone on a table in direct sunlight for hours while working on my lawnmower. I noticed it got very hot to touch. Ever since then my touchscreen has problems where there were no problems for 2 years prior. Dead spots, phantom touches and behaves sluggish in certain spots. Upper screen in portrait.
I tried wiping and reinstalling. Nothing works to fix this.
I even tried sealing it in a ziplock bag and freezing it. This actually works but its only temporary. The digitizer got damaged from heat. There is no "software" fix.
The only solution I can see is to physically replace the digitizer. This is a difficult thing to do but can be done.
I am considering replacing replacing the entire screen along with the digitizer as this is much easier but the problem is getting the high res replacement. Most after market screens are not equal to oppo's. The cost of OEM is too high.
Shame because this problem makes me now shy away from oppo devices.
Okay,
I opened up the phone.
Set to try and pry off/seperate the digitizer and replace with new one.
Decided to try something first.
Unplugged the digitizer and held power button (to release any stored up energy in the phone). Resnapped in digitizer cable to connector.
Reassembled the phone.
Put battery back in. Rebooted.
Sure enough, its all working. The full touchscreen is working with no dead spots or glitches.
For how long? Who knows?
Keeping this thing out of the heat.