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.
Related
I was running MIUI for a couple of weeks with no problem, a couple of days ago the lights on the keyboard and the circular buttons on the phone quit working. I didn't really think much about it, just figured it was a theme I applied just didn't agree with my phone. I tried restoring a nand of MIUI and still no lights. So yesterday I flashed mikshift ROM and still no dice. I'm now running the leak from yesterday and still none of my lights are working. I really don't want to run the ruu and go to sprint unless I absolutely have to.. any ides?
crump84 said:
I was running MIUI for a couple of weeks with no problem, a couple of days ago the lights on the keyboard and the circular buttons on the phone quit working. I didn't really think much about it, just figured it was a theme I applied just didn't agree with my phone. I tried restoring a nand of MIUI and still no lights. So yesterday I flashed mikshift ROM and still no dice. I'm now running the leak from yesterday and still none of my lights are working. I really don't want to run the ruu and go to sprint unless I absolutely have to.. any ides?
Click to expand...
Click to collapse
try running the back to stock zip by newkidd but remove the hboot and recovery img w/out unzipping the .zip.
riggsandroid said:
try running the back to stock zip by newkidd but remove the hboot and recovery img w/out unzipping the .zip.
Click to expand...
Click to collapse
Excuse my ignorance but how would I remove the hboot and recovery without unzipping the file?
Edit: Never mind.. dumb question. Thanks for the suggestion, I'll give it a shot when I have a little free time today.
I have had the same problem using several roms. One fix that worked for me was to disable auto-brightness, reboot, enable auto-bright, reboot again with my finger covering the sensor & both keyboard+onscreen lights work again. Try it if you haven't already.
Sent from my CM7 2.3.4 Shift using XDA Premium App
nvhush said:
I have had the same problem using several roms. One fix that worked for me was to disable auto-brightness, reboot, enable auto-bright, reboot again with my finger covering the sensor & both keyboard+onscreen lights work again. Try it if you haven't already.
Sent from my CM7 2.3.4 Shift using XDA Premium App
Click to expand...
Click to collapse
dont forget to rub your stomach while you pat your head and spin around on one leg while screaming "CM IS THE BEST"
jk but thats what i thought when i read your suggestion
nvhush said:
I have had the same problem using several roms. One fix that worked for me was to disable auto-brightness, reboot, enable auto-bright, reboot again with my finger covering the sensor & both keyboard+onscreen lights work again. Try it if you haven't already.
Sent from my CM7 2.3.4 Shift using XDA Premium App
Click to expand...
Click to collapse
Tried it.. no dice would have been nice if it was that easy. I'm making a nand now and going to try the One zip a little later.
riggsandroid said:
dont forget to rub your stomach while you pat your head and spin around on one leg while screaming "CM IS THE BEST"
jk but thats what i thought when i read your suggestion
Click to expand...
Click to collapse
lol.. yeah seemed a little hoakey but figured it couldn't hurt to try.
riggsandroid said:
dont forget to rub your stomach while you pat your head and spin around on one leg while screaming "CM IS THE BEST"
jk but thats what i thought when i read your suggestion
Click to expand...
Click to collapse
Hey it's not my fault this app adds in a stupid signature ;-)
I can manually remove it but then I have to push more buttons.
CM nightly builds have a lot of issues but Sense roms are a big no-no for privacy reasons. Look at the logs and see for yourself what the damn OS is doing in the background. Sprint & Google don't need to broadcast audio from my phone everytime I take a crap and the cops already get informed when you go over 65mph on the freeway anyways. Have you seen the secret Sprint web app that law enforcement uses on people? I have.
Sent from the not so secure interweb
Here's my own link to the back-to-stock zip. Enjoy.
http://web2.google-it.info/PG06IMG.zip
nvhush said:
Hey it's not my fault this app adds in a stupid signature ;-)
I can manually remove it but then I have to push more buttons.
CM nightly builds have a lot of issues but Sense roms are a big no-no for privacy reasons. Look at the logs and see for yourself what the damn OS is doing in the background. Sprint & Google don't need to broadcast audio from my phone everytime I take a crap and the cops already get informed when you go over 65mph on the freeway anyways. Have you seen the secret Sprint web app that law enforcement uses on people? I have.
Sent from the not so secure interweb
Click to expand...
Click to collapse
Don't worry about that, Riggs is already a CM fanboy And I figure the more they can watch me the less they'll care. I'm boring as hell.
^ Shift Faced
nvhush said:
Here's my own link to the back-to-stock zip. Enjoy.
http://web2.google-it.info/PG06IMG.zip
Click to expand...
Click to collapse
Well it looks like I'm not going to be able to do this until later tonight or tomorrow. Just a question, why is the file size in your link so much smaller than the one in the original thread??
It should be the same file since I've used it before. I will do an MD5 check and reupload if it's a mismatch. Does anyone have the MD5 sum of the original? If so pls post it. Thanks
EDIT:
Here is the updated link: http://web2.google-it.info/PG06IMG-backup.zip
MD5 Checksum: b213b282889e173f53b3a871a4941ffd
Again someone please confirm the checksum. Sorry about the broken link.
Well ran the one "zip" back to stock and still no lights.. Not real sure what the issue is. I have noticed over the past 24 hours that the lights on the keyboard will randomly work but it's not consistent. Guess I'll be heading to Sprint at some point.
How i fix the keyboard lights
This is how i fix the lights on my keyboard, the home and and menu buttons those still dont know how. First you go to settings>display>check automatic brightness>go to system update>update profile> turn off screen (on/off button), this is the important part! unlock your cell phone using the keyboard. Dont press on/off button then slide the keyboard for some random reason that doesnt work, just slide the keyboard on landscape mode then the light of the keyboard should work i think. Hope this work for someone else too.
hi i understand there is still no BLN for Galaxy note yet but there is for galaxy S2. Is there any way to flash S2 kernel on note? Or is there any tutorial on add bln to any kernel? thanks!
No. And No, or it would have happened. BLN will requires a dev to get it working SPECIFICALLY for our hardware. People always suggest, 'can we just grab that kernel' and no, never.
bLED (http://forum.xda-developers.com/showthread.php?t=1389394) is on the way to replace BLN...
thanks for the info. unfortunately for me, right now, BLED not only lights the touchkeys but also the entire screen up, which sort of defeats the purpose of lighting the touchkeys.
The_Steph said:
bLED (http://forum.xda-developers.com/showthread.php?t=1389394) is on the way to replace BLN...
Click to expand...
Click to collapse
inertiaholic said:
thanks for the info. unfortunately for me, right now, BLED not only lights the touchkeys but also the entire screen up, which sort of defeats the purpose of lighting the touchkeys.
Click to expand...
Click to collapse
lit the entire screen up? where did you get that assumptions? did you even tried it?
It really did but probably some conflict with another program. Fortunately after a full wipe, and reinstall of rom and bled, it's now fine! Thank you!
watch_mania said:
lit the entire screen up? where did you get that assumptions? did you even tried it?
Click to expand...
Click to collapse
inertiaholic said:
It really did but probably some conflict with another program. Fortunately after a full wipe, and reinstall of rom and bled, it's now fine! Thank you!
Click to expand...
Click to collapse
No worries. Glad it worked fine now. Please post anything you find on the bLED thread. So far 0.2 had been working veeery stable on mine now
Same for me , just terrific! And contrary to some, I really like it blinking instead of permanently lit! Keep up the great work. If not for your bled, I may have gone back to s2!!
watch_mania;20[B said:
[/B]294289]No worries. Glad it worked fine now. Please post anything you find on the bLED thread. So far 0.2 had been working veeery stable on mine now
Click to expand...
Click to collapse
I think the title is quite self-explanatory
I have a Stock JB 4.1.2 and i'd like to add the navigation bar!!
Are there any noob proof tools that can do it??
MarkRain said:
I think the title is quite self-explanatory
I have a Stock JB 4.1.2 and i'd like to add the navigation bar!!
Are there any noob proof tools that can do it??
Click to expand...
Click to collapse
Are you rooted? You need to be rooted.
polobunny said:
Are you rooted? You need to be rooted.
Click to expand...
Click to collapse
Yes i am, sorry, i forgot to mention!
How can i do it? i'm looking for an "easy" way, cause i'm not that good in mods :S
MarkRain said:
Yes i am, sorry, i forgot to mention!
How can i do it? i'm looking for an "easy" way, cause i'm not that good in mods :S
Click to expand...
Click to collapse
You simply need to edit your build.prop and add the line qemu.hw.mainkeys=0. You can use any good editor in Android to do that, or Build.prop Editor.
polobunny said:
You simply need to edit your build.prop and add the line qemu.hw.mainkeys=0. You can use any good editor in Android to do that, or Build.prop Editor.
Click to expand...
Click to collapse
Did it, couldn't hope that it was so simple, it just needed a reboot.
Thank you so much!!
MarkRain said:
Did it, couldn't hope that it was so simple, it just needed a reboot.
Thank you so much!!
Click to expand...
Click to collapse
You can also go one step or two further by disabling the backlight on the keys at the bottom AND even disabling them completely (nothing happens when pressed).
Disabling the lights will need a custom kernel however.
How can I disable the keys completly? I'm on cm 10.1.
xbs said:
How can I disable the keys completly? I'm on cm 10.1.
Click to expand...
Click to collapse
Here:
http://forum.xda-developers.com/showthread.php?p=34985922
Once again, for them not to light up, it's necessary you have a kernel that supports BLD.
polobunny said:
You can also go one step or two further by disabling the backlight on the keys at the bottom AND even disabling them completely (nothing happens when pressed).
Disabling the lights will need a custom kernel however.
Click to expand...
Click to collapse
I'm looking for an easy way to do this, maybe i'll flash the simple kernel for this purpose.
I'm doing this cause my softkeys are not properly functioning, most of the time there are only 2 of 4 visible, and my warranty is expired.
The navigation bar can be a good alternative i think!!
MarkRain said:
I'm looking for an easy way to do this, maybe i'll flash the simple kernel for this purpose.
I'm doing this cause my softkeys are not properly functioning, most of the time there are only 2 of 4 visible, and my warranty is expired.
The navigation bar can be a good alternative i think!!
Click to expand...
Click to collapse
Not a big fan myself, the Nexus S is rather "small" for today's standards and the navigation bar takes quite a bit of estate. But working around your problem without wanting to physically repair it, I believe that works.
polobunny said:
Not a big fan myself, the Nexus S is rather "small" for today's standards and the navigation bar takes quite a bit of estate. But working around your problem without wanting to physically repair it, I believe that works.
Click to expand...
Click to collapse
Unfortunately i have to agree, i don't like that solution too, cause the screen gets smaller than it's real size.
But to be honest i do prefer to apply a "patch" like this more than paying half the value of a 3 years old device to repair it...
I'll also try to flash a kernel with the bln mod and see if i can get used to use the device with no navbar and no softkeys light.
Thanks for your help!! :good:
Searching on the forum i found that should also be possible to decrease the navbar height!!
it would be great, but i saw the procedure, and i'll never be able to do it ... :S
MarkRain said:
Searching on the forum i found that should also be possible to decrease the navbar height!!
it would be great, but i saw the procedure, and i'll never be able to do it ... :S
Click to expand...
Click to collapse
Someone might be able to help you.
Hi All,
I'm actually running Dirty Unicorns v4.0 for Skyrocket and am running into an issue. When I turn my screen off, the hardware keys are still vibrating. Is this a known defect? I was trying to post this in the Developer forums to ask them but I'm new
Dave
Dliunatic said:
Hi All,
I'm actually running Dirty Unicorns v4.0 for Skyrocket and am running into an issue. When I turn my screen off, the hardware keys are still vibrating. Is this a known defect? I was trying to post this in the Developer forums to ask them but I'm new
Dave
Click to expand...
Click to collapse
For me, it's only occured with the ProBam ROM which turns on your phone by sliding your finger across all icons when the phone is off.
wolfsbay said:
For me, it's only occured with the ProBam ROM which turns on your phone by sliding your finger across all icons when the phone is off.
Click to expand...
Click to collapse
Hmmm I don't have any slide functionality that I know of. I've gone through all the settings and the only way that I can get this to stop vibrating is if I turn off "vibrate on key press" overall. Any other ideas or info?
Dliunatic said:
Hmmm I don't have any slide functionality that I know of. I've gone through all the settings and the only way that I can get this to stop vibrating is if I turn off "vibrate on key press" overall. Any other ideas or info?
Click to expand...
Click to collapse
It can always just be due to not letting the ROM settle after flashing, not letting a ROM settle can cause issues or lagg.
wolfsbay said:
It can always just be due to not letting the ROM settle after flashing, not letting a ROM settle can cause issues or lagg.
Click to expand...
Click to collapse
It's been installed and settling for over 2 weeks at this point ... maybe 3...
Dliunatic said:
It's been installed and settling for over 2 weeks at this point ... maybe 3...
Click to expand...
Click to collapse
settling occurs after flashing a ROM and before setup. Try flashing the ROM again and let it settle for 10 minutes before you set it up with the language and stuff.
wolfsbay said:
settling occurs after flashing a ROM and before setup. Try flashing the ROM again and let it settle for 10 minutes before you set it up with the language and stuff.
Click to expand...
Click to collapse
Thanks for the clarification wolfsbay. I'll try reflashing again. Out of curiosity, are both of you running Dirty Unicorns as well?
Dliunatic said:
Thanks for the clarification wolfsbay. I'll try reflashing again. Out of curiosity, are both of you running Dirty Unicorns as well?
Click to expand...
Click to collapse
both of you? lol before I switched to CM 11 i used to be on ProBam which I think had some of dirty unicorn or I think its called AOKP but it was basically Paranoid android,Cyanogenmod, and aokp or dirty unicorn but i didnt let it settle and it kept vibrating after i locked my phone. I then found the slide to unlock feature.
So, yea hit the thanks button if i helped :3
Hi,
yesterday I was on racetrack Nürburgring and tried my new OnePlus One.
Everything was cool except one thing.
Most time, when I took the OPO out of my trousers, the screen was on and an app was open?
Is there a setting for that, that this never happens? Don't want to share battery lifetime to my pockets and don't want to place calls to the whole world.
Is anyone having same problems or could someone help me?
Settings/Interface/Gesture Shortcuts, disable everything.
Transmitted via Bacon
You forgot display -> double tap to wake
It is scheduled to be fixed by OTA-update xnph28s; before unlocking the proximity sensor checks if the device is currently in a pocket.
See bugreport: https://jira.cyanogenmod.org/browse/BACON-16
Good to see, d4fseeker.
Do you know, when this update is ready for download?
Don't want to disable the Oppo features on opo
They say the update should be released in the next week or two.
Transmitted via Bacon
Where can i see the gerrit of cm11s??
Any news on the date of the next OTA update ?
aka_ronin said:
Any news on the date of the next OTA update ?
Click to expand...
Click to collapse
Typically when its ready, it was posted a week ago in 2 weeks time but no promises as they want to get it right in this OTA.
If you can't wait, you can flash custom ROMs as they already have this commit where it checks the proximity sensor. If the proximity sensor is blocked then gestures will be disabled until the proximity sensor is not blocked.
zephiK said:
Typically when its ready, it was posted a week ago in 2 weeks time but no promises as they want to get it right in this OTA.
If you can't wait, you can flash custom ROMs as they already have this commit where it checks the proximity sensor. If the proximity sensor is blocked then gestures will be disabled until the proximity sensor is not blocked.
Click to expand...
Click to collapse
Thanx for the tip :good: ...but I think I will wait.
d4fseeker said:
It is scheduled to be fixed by OTA-update xnph28s; before unlocking the proximity sensor checks if the device is currently in a pocket.
See bugreport: https://jira.cyanogenmod.org/browse/BACON-16
Click to expand...
Click to collapse
Does paranoid android fix this?
jameslfc5 said:
Does paranoid android fix this?
Click to expand...
Click to collapse
I don't use paranoid android but go into their thread and search for the keyword proximity. Chances are they probably did include it.
Sent from my One using Tapatalk
zephiK said:
I don't use paranoid android but go into their thread and search for the keyword proximity. Chances are they probably did include it.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Does paranoid android have the lockscreen gestures then?
Thanks
jameslfc5 said:
Does paranoid android have the lockscreen gestures then?
Thanks
Click to expand...
Click to collapse
Like I said before, I don't use Paranoid Android. Go into the thread and search for the keyword "lockscreen" ... if the ROM is based on CM for the OPO then it will have the gesture controls.
Edit: Heres your answer, http://forum.xda-developers.com/showthread.php?p=53677403&highlight=gesture#post53677403 next time just search
Not only as stable as CM is, it includes all device specific features of CM like offscreen gestures, Quickboot, Soft/hard buttons...
Click to expand...
Click to collapse
FormelLMS said:
Hi,
yesterday I was on racetrack Nürburgring and tried my new OnePlus One.
Everything was cool except one thing.
Most time, when I took the OPO out of my trousers, the screen was on and an app was open?
Is there a setting for that, that this never happens? Don't want to share battery lifetime to my pockets and don't want to place calls to the whole world.
Is anyone having same problems or could someone help me?
Click to expand...
Click to collapse
You either need to upgrade the trousers or keep your hands where they belong - in someone else's trousers.
Mike
mhannigan said:
You either need to upgrade the trousers or keep your hands where they belong - in someone else's trousers.
Mike
Click to expand...
Click to collapse
Or just disable the "Double tap to wake" feature like I did... ...and wait for the next OTA update.
aka_ronin said:
Or just disable the "Double tap to wake" feature like I did... ...and wait for the next OTA update.
Click to expand...
Click to collapse
That is a FIX and not a full-fledged semi-effective workaround. Unacceptable, but thanks for trying.
Mike
This is CM inc's chance to show what they can do.
You know they have a One Plus as a test phone but they let it go out with low call volume and sub par signal strength. As well as touch screen problems and more. Just look at the bug reports. There no hiding them.
Software makes the phone work so to me that is what I have to look at.
All in all its a great phone I just expect more from CM inc.
Vortex1969 said:
This is CM inc's chance to show what they can do.
You know they have a One Plus as a test phone but they let it go out with low call volume and sub par signal strength. As well as touch screen problems and more. Just look at the bug reports. There no hiding them.
Software makes the phone work so to me that is what I have to look at.
All in all its a great phone I just expect more from CM inc.
Click to expand...
Click to collapse
To be fair the phone is still in its infancy stages and is invite only. So in a way you can say we paid for the phone to be "internal beta testers" and when the phone is not invite only thats when its out for the masses.
I agree with you though, these major problems should have been addressed in a hotfix rather than having users wait for the next OTA. Luckily for the most of us, we're able to fix it in our own hands but for those who aren't then they'll just have to wait.
zephiK said:
To be fair the phone is still in its infancy stages and is invite only. So in a way you can say we paid for the phone to be "internal beta testers" and when the phone is not invite only thats when its out for the masses.
I agree with you though, these major problems should have been addressed in a hotfix rather than having users wait for the next OTA. Luckily for the most of us, we're able to fix it in our own hands but for those who aren't then they'll just have to wait.
Click to expand...
Click to collapse
I agree with that and thank you for one of the fixes.[emoji3]