Related
Hi all I have a Galaxy Blaze 4G on the t-mobile network.
I flashed CM 10 cm-10.0.0-t769.zip and the gapps from this thread.
Every thing seems to work very well but when the phone screen times out and goes black or I hit the power button to turn off the screen the hardware buttons ( Menu Home Back Search ) will flash on and off in 2 second intervals.
Any ideas? have I just not found a setting?
Thanks for reading.
Settings / display / notification light. It is probably flashing because of a notification that needs answering.
Romman0 said:
Settings / display / notification light. It is probably flashing because of a notification that needs answering.
Click to expand...
Click to collapse
Thank you for the reply. Yes it was an e-mail doing it.
area1509 said:
Thank you for the reply. Yes it was an e-mail doing it.
Click to expand...
Click to collapse
You need to flash the newest nightly, the stable isn't stable check the date. 3-10-13 is the latest. Plus the stable is missing a few things like the kill all apps button at the top of the recent apps switch.
I'd also really recommend flashing the updated radio located here:
http://forum.xda-developers.com/showthread.php?t=2171664
I was having some issues with not being able to answer/make calls but this seems to have fixed it. It's an updated radio from what you probably have.
Cirkustanz said:
I'd also really recommend flashing the updated radio located here:
http://forum.xda-developers.com/showthread.php?t=2171664
I was having some issues with not being able to answer/make calls but this seems to have fixed it. It's an updated radio from what you probably have.
Click to expand...
Click to collapse
I feel like a car salesman, been trying to tell you guys for a week now.lol
jbats said:
I feel like a car salesman, been trying to tell you guys for a week now.lol
Click to expand...
Click to collapse
Hah, now that's funny. Truth is I stopped checking on XDA for a while, and never even saw that radio update. That's because I felt like I didn't really have a reason to, CM10 seems to be everything I wanted.
So, that's a kudos, all around?
Hi,
I need to know if it's possible disable or recalibrate the proximity sensor of the Atrix 2 because when I make a phone call my screen turn off and I need to push power button to activate de screen and hang up :/.
I'm using JB 4.2.2/CM 10.1
Thanks!
alrojas said:
Hi,
I need to know if it's possible disable or recalibrate the proximity sensor of the Atrix 2 because when I make a phone call my screen turn off and I need to push power button to activate de screen and hang up :/.
I'm using JB 4.2.2/CM 10.1
Thanks!
Click to expand...
Click to collapse
I've noticed this too before, but not since the latest release (4/3/13), could be a coincidence, but if you are on an older build, try updating.
lkrasner said:
I've noticed this too before, but not since the latest release (4/3/13), could be a coincidence, but if you are on an older build, try updating.
Click to expand...
Click to collapse
mmmm, I am using CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com.zip. It is the latest release from this thread: http://forum.xda-developers.com/showthread.php?t=2121029. I'm not sure if it's the same.
Thanks!
alrojas said:
mmmm, I am using CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com.zip. It is the latest release from this thread: http://forum.xda-developers.com/showthread.php?t=2121029. I'm not sure if it's the same.
Thanks!
Click to expand...
Click to collapse
yeah, that is the latest. I'm not sure what the problem is. try a fix permissions in recovery, I haven't been having a problem. also try in different light conditions, as that could be related, as well as any crap that has built up over the sensor (just left of the notification light, you can see it at the right angle)
lkrasner said:
yeah, that is the latest. I'm not sure what the problem is. try a fix permissions in recovery, I haven't been having a problem. also try in different light conditions, as that could be related, as well as any crap that has built up over the sensor (just left of the notification light, you can see it at the right angle)
Click to expand...
Click to collapse
I have this doubt. What it's "more latest" CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com.zip(previously mentioned) or CM10-nightly-NONE_CN-20130412-2102-signed.zip from this thread http://forum.xda-developers.com/showthread.php?t=1869692
I'm sorry if my question is too trivial.
Thanks!
alrojas said:
I have this doubt. What it's "more latest" CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com.zip(previously mentioned) or CM10-nightly-NONE_CN-20130412-2102-signed.zip from this thread http://forum.xda-developers.com/showthread.php?t=1869692
I'm sorry if my question is too trivial.
Thanks!
Click to expand...
Click to collapse
The first one is cm10.1 latest build and second one is cm10 with camera fix
lkrasner said:
yeah, that is the latest. I'm not sure what the problem is. try a fix permissions in recovery, I haven't been having a problem. also try in different light conditions, as that could be related, as well as any crap that has built up over the sensor (just left of the notification light, you can see it at the right angle)
Click to expand...
Click to collapse
mmm and What exactly do Fix Permissions in Recovery?... I just wanna know XD. Anyway It doesn't solve my issue
I would also like info on this because my proximity sensor is broke and always thinks there is an object by the phone, which makes in-call operations impossible...
Hi everyone,
I have been searching for a fix for this proximity sensor( during call) bug which is in Nexus 5 ,i have seen for some other phone like nexus 4 etc.There is fix for it. But is there any solution for Nexus 5.
The issue can be viewed in this Youtube.
trisankur said:
Hi everyone,
I have been searching for a fix for this proximity sensor( during call) bug which is in Nexus 5 ,i have seen for some other phone like nexus 4 etc.There is fix for it. But is there any solution for Nexus 5.
The issue can be viewed in this Youtube.
Click to expand...
Click to collapse
I`am running 4.4.2 and not rooted and i don`t have that issue. Are you rooted and running stock or custom rom, running mods like xposed framework, running a custom kernel and/or recovery? Info please
ya i am rooted and i m in stock rom only,but using Franco kernal(R32).Xposed framework i m using gravitybox(KK).I have CWM recovery.
What is causing this problem any idea??
N thanks for ur reply.
trisankur said:
ya i am rooted and i m in stock rom only,but using Franco kernal(R32).Xposed framework i m using gravitybox(KK).I have CWM recovery.
What is causing this problem any idea??
N thanks for ur reply.
Click to expand...
Click to collapse
Look in the Xposed and/or Franco kernel thread for a similar issue like yours, there may be a fix posted. Last resort is to flash a stock image in fastboot and that will probably fix your problem.
trisankur said:
Hi everyone,
I have been searching for a fix for this proximity sensor( during call) bug which is in Nexus 5 ,i have seen for some other phone like nexus 4 etc.There is fix for it. But is there any solution for Nexus 5.
The issue can be viewed in this Youtube.
Click to expand...
Click to collapse
When asking for assistance it's best to provide as much information as possible. As it stands I have no idea what you're referring to, and I think it's safe to assume most people won't either.
Ok i will search in there threads.Hope there is some fix posted
Thanks.
trisankur said:
Ok i will search in there threads.Hope there is some fix posted
Thanks.
Click to expand...
Click to collapse
Hi,
But what is "this proximity sensor( during call) bug" you are referring? Honestly I have no idea what you are talking about, I never had noticed a bug or anything else with the proximity sensor during call
Like _MetalHead_ said if you want help describe the problem...
Ok fine i will keep that in mind, next time if i post any questions.
trisankur said:
Ok fine i will keep that in mind, next time if i post any questions.
Click to expand...
Click to collapse
For the next time ok, but for now (in this thread here) you can't describe/explain the problem???
There is video on youtube regarding this.i cant post it in here so.
Anywaz the issue is when i m in call,
Steps
1)Call a number
2)Screen goes off.
if i try to make the screen on(to end the all or anything) i have to press 4-5 times power button which also happens by luck to make the screen on.
Also when in call (screen is off),if i try to do something in the status bar.Like if i touch near status bar(in call screen off),when the call ends u can see the status bar was active even if the screen was off.
Hope i m understandable.
i have posted the description of the issue just now .
Historically, this was usually down to a crap screen protector blocking the sensors. OP - are you using an SP?
EddyOS said:
Historically, this was usually down to a crap screen protector blocking the sensors. OP - are you using an SP?
Click to expand...
Click to collapse
Ya i m using Sceen protector,but this issue is for poeple who r not using SP also ,in other forums i have seen the same issue.
Only happens to me in the dark.
touch control
I have the same problem, during call the screen go black like it shuld be ,but its stilk active so if you tuch it it still responsive as if its on, i found thet if i disable touch control the problem goes away...
trisankur said:
ya i am rooted and i m in stock rom only,but using Franco kernal(R32).Xposed framework i m using gravitybox(KK).I have CWM recovery.
What is causing this problem any idea??
N thanks for ur reply.
Click to expand...
Click to collapse
exactly the same for me!!! (except R33)
Same issue on mine, and I don't use a case or screen protector. It's annoying because I have to enter a passcode to check my voicemail, but the screen stays black when I move the phone away from my head. Putting it on speaker seems to fix the issue, but I don't always want my phone calls broadcast to everyone around me.
Hey. I got a new S6 yesterday.
Everything was fine, except one thing. The scanner doesn't work anymore, since about an hour. I tried to test the sensor using *#0*#, and all the fields said "PASS". Setting a new finger works perfectly fine too. But whenever I try to use it on the lock screen, literally nothing happens. Not a single thing.
Is someone able to help me? Is this a known issue?
Kind regards and warm thanks
intel_c0re said:
Hey. I got a new S6 yesterday.
Everything was fine, except one thing. The scanner doesn't work anymore, since about an hour. I tried to test the sensor using *#0*#, and all the fields said "PASS". Setting a new finger works perfectly fine too. But whenever I try to use it on the lock screen, literally nothing happens. Not a single thing.
Is someone able to help me? Is this a known issue?
Kind regards and warm thanks
Click to expand...
Click to collapse
Hard reset will fix your issue same thing with me
irfannexus said:
Hard reset will fix your issue same thing with me
Click to expand...
Click to collapse
Well I just got a notification and opened it (double tap), now it's working perfectly fine.. Thanks for your answer though. Is this a software error or should I be concerned?
intel_c0re said:
Well I just got a notification and opened it (double tap), now it's working perfectly fine.. Thanks for your answer though. Is this a software error or should I be concerned?
Click to expand...
Click to collapse
Mine pleasure bro Its just A softwear Eror As u say Its a new galaxy S6 so Upgrading with latest stock Rom will Fix All bugs and eror.
irfannexus said:
Mine pleasure bro Its just A softwear Eror As u say Its a new galaxy S6 so Upgrading with latest stock Rom will Fix All bugs and eror.
Click to expand...
Click to collapse
I bought it with Android 6.0.1 Marshmallow preinstalled. Already checked for software updates but it didn't find any. I don't really want this to happen again, you know..
Q few months afo i replaced my G3 Screen as old one was broken and after updating it to M.M stock rom or even flashing some other M.M + roms touch is not working from staring after ph boot up.
But when i go down to L.P it work perfectly....
Any one can help....
PlZzz...
Thx....
Yup... need a Moto OEM touchscreen, half of the third party ones, typically the cheaper ones, don't work on Marshmallow. We still don't understand why, but it's been a thing for quite a while.
Piyush Garg said:
Q few months afo i replaced my G3 Screen as old one was broken and after updating it to M.M stock rom or even flashing some other M.M + roms touch is not working from staring after ph boot up.
But when i go down to L.P it work perfectly....
Any one can help....
PlZzz...
Thx....
Click to expand...
Click to collapse
Try nougat roms
Prashant324 said:
Try nougat roms
Click to expand...
Click to collapse
same with that...
Piyush Garg said:
same with that...
Click to expand...
Click to collapse
This is a known issue... we don't know why for sure, but some non-OEM replacement touchscreens do not work with anything but Lollipop... And we don't know how to make it work other than replacing it with an Moto OEM touchscreen or one that is of high quality.
acejavelin said:
This is a known issue... we don't know why for sure, but some non-OEM replacement touchscreens do not work with anything but Lollipop... And we don't know how to make it work other than replacing it with an Moto OEM touchscreen or one that is of high quality.
Click to expand...
Click to collapse
I am interesting why devs dont wanna implement l.mretus synaptics driver in all newer android or custom distributions than lollipop knowing this!
Its really strange , Lenovo is doing nothing in this case but devs could do..but they have conviced that its working(newer driver) for them but its not heh if something is good for everyone..why we can't use it?
pio80 said:
I am interesting why devs dont wanna implement l.mretus synaptics driver in all newer android or custom distributions than lollipop knowing this!
Its really strange , Lenovo is doing nothing in this case but devs could do..but they have conviced that its working(newer driver) for them but its not heh if something is good for everyone..why we can't use it?
Click to expand...
Click to collapse
Because it creates other potential issues for minimal gain I assume. I can't really answer that question definitively.
I have ghost touch issue only while calling........i tried Marshmallow Stock ROM CM 13 and LineageOS14........i couldn't fix this........
NOTE: I didn't remove or replace my display......the phone is intact
Sachin ET said:
I have ghost touch issue only while calling........i tried Marshmallow Stock ROM CM 13 and LineageOS14........i couldn't fix this........
NOTE: I didn't remove or replace my display......the phone is intact
Click to expand...
Click to collapse
Does the screen blank (turn off) when you hold it up to your ear? If so, I do that know, if it doesn't you have a proximity sensor issue and the device needs to be repaired/replaced.
acejavelin said:
Does the screen blank (turn off) when you hold it up to your ear? If so, I do that know, if it doesn't you have a proximity sensor issue and the device needs to be repaired/replaced.
Click to expand...
Click to collapse
Yes the proximity sensor works perfectly fine (Screen Turns off when it's covered while calling)
Sachin ET said:
Yes the proximity sensor works perfectly fine (Screen Turns off when it's covered while calling)
Click to expand...
Click to collapse
So what is the issue then? If the screen is off it shouldn't be recognizing any touches... or am I misunderstanding the problem?
acejavelin said:
So what is the issue then? If the screen is off it shouldn't be recognizing any touches... or am I misunderstanding the problem?
Click to expand...
Click to collapse
I'll explain........the problem is when i am making a call and not holding it to my ear (Or it hapens in the time gap between dialing and holding it to my ear)........same thing happens in the case of incoming call, that is i cant pick the incoming call(either the screen freazes or the ghost touch automatically" Decline" my call).
I am attaching a link down here........please have a look at it........ it is a screen recoded video during an incoming call.
https://drive.google.com/file/d/0B_yXW_DztkJ7Nkt2NlBLQmpQR2M/view?usp=drivesdk
NOTE ( i didn't touch the screen while recording........the whole thing happens automatically)
Thanks