Database Info

power button broken

hi! after a fall my Desire S have some problems with the power button. Now is still working but I have to push harder every day to unlock the phone!
I thought to remove the original ROM and use something like ICE DS to remap the power button to one of the volume keys. New motherboards for this phone are not cheap and I think this is the better solution. Do you have any suggestions? Is this the better way to solve the problem?
10q

S2w is something I used and it is optional on most if not all current dev ROM. U can basically switch the the phone on or off by swiping from the home softkey to the search key. Install it and experience it for yourself.
FromA100

rain987 said:
S2w is something I used and it is optional on most if not all current dev ROM. U can basically switch the the phone on or off by swiping from the home softkey to the search key. Install it and experience it for yourself.
FromA100
Click to expand...
Click to collapse
thank you, S2w could be interesting. Is it too bad for battery life? I tested a week ago a few programs that unlock the phone using the proximity sensor and they didn't work very well.

neonum6 said:
thank you, S2w could be interesting. Is it too bad for battery life? I tested a week ago a few programs that unlock the phone using the proximity sensor and they didn't work very well.
Click to expand...
Click to collapse
Alternatively you could try screen off and lock from the playstore
"Some things Man was never meant to know. For everything else, there's Google."

jugg1es said:
Alternatively you could try screen off and lock from the playstore
"Some things Man was never meant to know. For everything else, there's Google."
Click to expand...
Click to collapse
Yes I was talking about screen off and lock from the playstore when I've said that I don't like it.

neonum6 said:
Yes I was talking about screen off and lock from the playstore when I've said that I don't like it.
Click to expand...
Click to collapse
Ok, I'm using it instead of s2w, had no problems whatsoever
"Some things Man was never meant to know. For everything else, there's Google."

Try s2w, It's great

jugg1es said:
Alternatively you could try screen off and lock from the playstore
"Some things Man was never meant to know. For everything else, there's Google."
Click to expand...
Click to collapse
totalnoob34 said:
Try s2w, It's great
Click to expand...
Click to collapse
Yesterday I have installed ICE DS 6.5 and it's amazing. This ROM comes with s2w already installed, and you can also unlock your phone using the volume keys!
So my problem is solved and I suggest to all people that have similar troubles to think about this solution!

I thought that S2W is just kernel related and not ROM related? So it would be enough to use the kernel from amidabuddha, right?

StormShadowBK said:
I thought that S2W is just kernel related and not ROM related? So it would be enough to use the kernel from amidabuddha, right?
Click to expand...
Click to collapse
If your using a sense rom, then yes
Just remember, if the world didn't suck, we'd all fall off.

Touch Screen doesn't work well

Hi,
My touch screen of my HTC chacha doesn't work well.
Is a driver problem ? I tried several ROm as CyanogenMod, Stock Plus, Void, and I've the same problem.
How Can I fix it?
Thanks for your help

hardware issue
i tried those ROMS too, it was working perfect for me..
maybe a hardware issue?

Can you be more specific?

Maybe you should get it back to stock and get it for warranty. Sounds like you have a ground problem. Heard it on another forum with another phone, but basically, if the ground pin of you phone isn't properly connected, the screen won't work like it should.
Hope this helps.

Thanks everyone ....
It's sporadic. Shoud it comme from the battery?
I don't have the HTC invoice as it's buying second hand

dubis999 said:
Thanks everyone ....
It's sporadic. Shoud it comme from the battery?
I don't have the HTC invoice as it's buying second hand
Click to expand...
Click to collapse
Not sure... Maybe someone could check it for you? And yeah, it comes from the battery... It's the middle pin if i'm correct... Might also be a bad contact on your battery from oxydation...

Bunnybugs_007 said:
Not sure... Maybe someone could check it for you? And yeah, it comes from the battery... It's the middle pin if i'm correct... Might also be a bad contact on your battery from oxydation...
Click to expand...
Click to collapse
In waiting I put money into a new battery. I already remove the HtcLockScreen.apk, but now it's the lock screen by default of Android which is tacking the place of the older.
That's boring because the touch screen doesn't work well. I would like a lock screen which a password code or something else like this for bypassing the touch screen access.
Do you know how to remove it?

lockscreen problem
for the lockscreen problem could you use an app called 'widget locker lockscreen'
here is the link (https://play.google.com/store/apps/details?id=com.teslacoilsw.widgetlocker)

I installed Lock Off, that's solve my slider problem.
https://play.google.com/store/apps/...t#?t=W251bGwsMSwxLDEsImpwLmptb24ubG9ja29mZiJd
But That doesn't solve the touch screen problem........

[Q] Proximity Sensor

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...

[Q] Is there any fix for the proximity sensor problem(during call) for Nexus 5

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.

Wanted to get a Survery: Multitouch on Google Pixel 4A

Alright, so currently im dealing with some Multitouch issues on my Pixel 4a. The repair place i went to UBREAKIFIX said they'll have to do the whole repair they did preciously again and charge me (because of 2 small dents at the side of the screen). Would not recommend. I wanted to get a poll of everyone with this exact issue Here is some steps to test:
1. Enable Developer Options (Go into build number click however many times and get developers options
2. Go to Developer Options in System settings,
3. Scroll down to Input and enable "Show taps" and "Pointer Location.
4. Put two fingers down and see if multiple pointers are shown (If not, Multi-touch does not work)
Also some other Notes:
Downgrading to Android 10, Makes multitouch work for some reason :/
Also would like to know if you've gotten your phone repaired before.
Any help figuring this whole thing out is appreciated

Can I ask what was the repair they did the first time to fix your touch problem?

hammered58 said:
Can I ask what was the repair they did the first time to fix your touch problem?
Click to expand...
Click to collapse
The first time, it was just a broken screen, had to replace it

fbievan said:
The first time, it was just a broken screen, had to replace it
Click to expand...
Click to collapse
Dont know if started happening before or after, but i noticed it recently, and started digging, brought it to the place and they said they wouldnt cover it under warranty because of 2 small dents at the side of screen which have zero relation to the problem at hand

fbievan said:
Dont know if started happening before or after, but i noticed it recently, and started digging, brought it to the place and they said they wouldnt cover it under warranty because of 2 small dents at the side of screen which have zero relation to the problem at hand
Click to expand...
Click to collapse
That's sucks, hard to prove if there right or wrong without putting a known good screen on

hammered58 said:
That's sucks, hard to prove if there right or wrong without putting a known good screen on
Click to expand...
Click to collapse
Also as i noted, for some reason downgrading to andorid 10 has multitouch working. (From flash.android.com)

fbievan said:
Also as i noted, for some reason downgrading to andorid 10 has multitouch working. (From flash.android.com)
Click to expand...
Click to collapse
I honestly cant say if its the hardware or software, maybe it might be a combination of both? I'm not entirely sure, however downgrading to android 10 from googles flash tool does seem to have it work. I had what i would guess is a full screen replacement from UBREAKIFIX, due to shattering the entire screen. Honestly, spending 140 dollars just to see if it might work is not worth it to me, so I'm really not sure what to do.

Even doing it yourself the cheapest I've seen a screen is 110 from AliExpress, which I don't get because I just replaced one on a g7 moto play for 20 bucks off ebay

hammered58 said:
Even doing it yourself the cheapest I've seen a screen is 110 from AliExpress, which I don't get because I just replaced one on a g7 moto play for 20 bucks off ebay
Click to expand...
Click to collapse
Is there any reason why this multitouch would work on android 10? I dont see exactly what is happening here

fbievan said:
Is there any reason why this multitouch would work on android 10? I dont see exactly what is happening here
Click to expand...
Click to collapse
idk,, maybe the sensitivity is setup diff

hammered58 said:
idk,, maybe the sensitivity is setup diff
Click to expand...
Click to collapse
After looking for a while seems the entire drivers are different in the kernel. But that is my brief look at. If anyone who knows kernel drivers would like to take a look at it. Would be helpful

LineageOS 19.1 - multitouch just stopped working today after several weeks without problems. No repairs or damage.

I'm on stock but rooted. I've been slack so still on October patch. Multi touch working fine. Never had a problem with it.
(Finally updated to December patch and it's still working.)

LionDGem said:
LineageOS 19.1 - multitouch just stopped working today after several weeks without problems. No repairs or damage.
Click to expand...
Click to collapse
What fixed it for me was downgrading to android 10 then updating all the way up...
From right here: https://forum.xda-developers.com/t/...ter-apr-security-update.4428089/post-87356703

fbievan said:
What fixed it for me was downgrading to android 10 then updating all the way up...
From right here: https://forum.xda-developers.com/t/...ter-apr-security-update.4428089/post-87356703
Click to expand...
Click to collapse
Wonder how this actually fixes the issue. Sounds strange.

LionDGem said:
Wonder how this actually fixes the issue. Sounds strange.
Click to expand...
Click to collapse
I don't know... As far as I know downgrading has the kernel touchscreen driver seemingly working... from there I know little

fbievan said:
I don't know... As far as I know downgrading has the kernel touchscreen driver seemingly working... from there I know little
Click to expand...
Click to collapse
Multitouch stopped working on my Pixel 4A 5G after updating to android 13.
Maybe a bug caused by an OTA update?

qqBenji said:
Multitouch stopped working on my Pixel 4A 5G after updating to android 13.
Maybe a bug caused by an OTA update?
Click to expand...
Click to collapse
I have LineageOS 19.1 here. So android 12. i'll try that android 10 approach

I can confirm now that downgrading to Official Google Pixel 4a Stock Rom Android 10 fixed the issue. I try to go back to LOS 20 now and see what happens.
PS: Using internal updater to update to Android 13 broke it again. Taking the long route now.
PPS: That chromium based flash tool is really handy. Would be awesome to have something like that for LineageOS.
PPS: As soon as I install anything above Android 10, multitouch stops working. I'll sell this stupid thing as is (will let te buyer know of course). Its a shame.