Related
Over the last 24 hours i've noticed my mini pro doing something wierd.
The home button seems to not work/phone not responding to it. but also the lockscreen no longer pops up when i turn the screen on. I've looked in both the settings and cyanogen mod setttings.
I know i could probably fix it with a factory reset but i really don't want to have to do that. because i have apps/setup exactly how i like it.
Has anyone else experienced this and know of an easy fix?
Thanks in advance,
Ryan
y'know what. I'm just gonna factory reset and set everything back up. driving me a bit nuts not being able to use the home key...
Your patience busted out in 6 hours. im sorry for what you experienced....
mine also has some glitches and it rarely happens. i wonder if it is the CM7 rom you are using. you can confirm if it is ok with the stock rom.
OR
you can flash your kernel to a custom kernel and use and see. screen touch was waaaaaaay much better on custom kernel. i loved it. see if that works....
OR
try another rom for a change and see if it is rom problem......
Good luck!
Tim
Tommylee567 said:
Your patience busted out in 6 hours. im sorry for what you experienced....
mine also has some glitches and it rarely happens. i wonder if it is the CM7 rom you are using. you can confirm if it is ok with the stock rom.
OR
you can flash your kernel to a custom kernel and use and see. screen touch was waaaaaaay much better on custom kernel. i loved it. see if that works....
OR
try another rom for a change and see if it is rom problem......
Good luck!
Tim
Click to expand...
Click to collapse
I think the rom was fine. I don't know what caused it, but it's fine now.
I reflashed the Cyanocream Sandwich rom following the intructions on the dev page. And everything is working again.
Thanks anyway
In fact, it's for most phones/tablets on HC and ICS with front facing camera. :good:
Installed on my rooted locked stock Prime, tested for around half an hour, seems to be working fine, no FC no problem encounter. go ahead and try it, report to the developer's thread if you have any problem.
BTW, I've also tested ISeeYou lite version but I think this one is more responsive and the UI is much better.
http://forum.xda-developers.com/showthread.php?t=1708012
V1.0.3 SOUND FIX: http://www.mediafire.com/download.php?u1n3umbtk7sei81
All credits go to elnoxvie on the GS2 forum.
stantang said:
In fact, it's for most phones/tablets on HC and ICS with front facing camera. :good:
Installed on my rooted locked stock Prime, tested for around half an hour, seems to be working fine, no FC no problem encounter. go ahead and try it, report to the developer's thread if you have any problem.
BTW, I've also tested ISeeYou lite version but I think this one is more responsive and the UI is much better.
http://forum.xda-developers.com/showthread.php?t=1708012
V1.0.3 SOUND FIX: http://www.mediafire.com/download.php?u1n3umbtk7sei81
All credits go to elnoxvie on the GS2 forum.
Click to expand...
Click to collapse
I tested this one too. Also on my One X. Works on both, but the camera viewing angles make usage a bit tricky sometimes.
Hey guys, i installed AOKP cm9 Monday night and once installed i fell in love. I came from th eclipse rom which was good but just the customization and look of AOKP is beautiful.
SO this leads me to my problems. When i flashed the rom and used it yesterday it was pretty much working great. I didnt use the dialer much so i dont know if t was happening then or just started. It seems if i call someone and the screen goes black due to the proximity sensor it will not come back after to end the call or when i pull the phone away from my face. I have to constantly press the power button to unlock the phone then i can click end then the screen locks again and have to swipe unlock to get back into the phone. This is a major PITA and wondering if it is a known bug or am i the only one.
Also from looking at the official thread here it states the camera is working but mine does not.
NVM just got it going
Also wondering when i was using elclispe and would go into rom toolbox > build.prop tweaks i could adjust about 7 things such as prox sensor and such. Now i only have 4 lcd, ring delay vmheap, scan interval. Why do i only get 4 tweaks versus the 7 i had before.
Add: Also i just noticed now when i get a call my screen stays blank. I had to again click the power button x amount of times to get in and now recieving a message "processcom.android is not responding. would u like to close it"
Ugghh this is so aggrevating
lso noiced in apps running im using at the highest 330-350 mb and states betwee 48-90mb free. thats to high isnt it
jeff5347 said:
Hey guys, i installed AOKP cm9 Monday night and once installed i fell in love. I came from th eclipse rom which was good but just the customization and look of AOKP is beautiful.
SO this leads me to my problems. When i flashed the rom and used it yesterday it was pretty much working great. I didnt use the dialer much so i dont know if t was happening then or just started. It seems if i call someone and the screen goes black due to the proximity sensor it will not come back after to end the call or when i pull the phone away from my face. I have to constantly press the power button to unlock the phone then i can click end then the screen locks again and have to swipe unlock to get back into the phone. This is a major PITA and wondering if it is a known bug or am i the only one.
But for the life of me, trying to use the dialpad was nearly impossible while on a call. That helped ALOT. You can also DL Screeble in the market. That will help.
Also from looking at the official thread here it states the camera is working but mine does not.
NVM just got it going
Also wondering when i was using elclispe and would go into rom toolbox > build.prop tweaks i could adjust about 7 things such as prox sensor and such. Now i only have 4 lcd, ring delay vmheap, scan interval. Why do i only get 4 tweaks versus the 7 i had before.
Add: Also i just noticed now when i get a call my screen stays blank. I had to again click the power button x amount of times to get in and now recieving a message "processcom.android is not responding. would u like to close it"
Ugghh this is so aggrevating
Click to expand...
Click to collapse
I have the same problem on my X2. You gotta go into settings and I forget where at the moment, but you have to enable hysterisis or something to that extent. I kick myself for not remembering.
As for ROM toolbox, don't use it.
COme on man you gotta remember haha what does hyterisis do and why not use rom toolbox
Sorry about that. Had to look up where DZK gave me some insight on that:
dragonzkiller said:
In CM9 (and I believe CM7) there is a setting under the brightness controls (I believe it's there, I don't have either running right now) called "hysteresis." Hysteresis is basically a "smoothing out" of what the light sensor sees and what value is actually sent to the brightness controls. Enabling that will make the screen react slower to changing light situations, but will disable (or should disable) flicker of the screen from the light sensor acting up. It might not be the problem, but it shouldn't hurt to try it out.
Click to expand...
Click to collapse
Also for CM7, I know you said you are on CM9, it says in the original post:
"16. Never user RomManager! (Yes it's included, but that's a CM7 thing and won't work with the DX2.)"
I've also read other areas that ROM manager is a no-no for the X2. Better to be safe than sorry.
Thanks Tally. I found where to play with hysteria and it was getting better but still doing it. I had my display or auto, for the phone to adjust display depending on the light. I turned that off and left it at 80% no matter the light and that fixed it. Wow just the auto brightness display could cause so much crap.
So i should just uninstall Rom manager, I dont usually use it anyways.
You stated in your previous post rom toolbox. Was it toolbox or manager that u are stating we shouldnt use?
Also is 300-350mb of ram ok for the phone to be using fairly regularly?
spoke to soon. It was working now its back to normal. I am ready to bodyslam this phone
Tally.. what settings did you do on your d2 to make it work correctly
Don't do it. Mine was doing exactly what you have described. Once you get it figured out, its ok. But yes... it will make you want to punt it across the room.
Your 300-350 mb of ram is ok.
I wouldn't delete it ROM manager. Just leave it as it is.
---------- Post added at 01:22 PM ---------- Previous post was at 01:12 PM ----------
I had the best luck running CM9 mashed up- not supercharged or anything else. Others here had some luck with the V6 supercharger. Different phones just acted differently. But now that the beta version has the mash up in the build.prop just let it ride. Avoid Facebook and sites that have alot of media to load.
It really does work pretty good once you get a feel of how your phone reacts to it. Alot of the things are tolerable.
What do u mean by mashed up. Do you mean by cm9 or the aokp cm9. I am getting some really wacky stuff happening. System running real slow, screen not coming on usually from a call or sometimes when trying to unlock phone, now my VM wouldn't respond, apps taking a lot more time than usual to open. I don't know if this is the aokp from or the phone. I had the screen glitch w eclipse but not all the other stuff. I called verizon and they r willing to send out a replacement but just not sure if its the phone or rom
ok so this is weird and not sure if it is the problem. I was trying to play with anything that may affect how slow it is and once i flashed the aokp rom i downloaded a little later a cobalt theme for my theme chooser. Was running that all day and just now said " let me try putting it back to system theme" once the system them was in and everything loaded it was back to working quick again.
Now be it , it has only been a half hour but already it is what i saw first thing and the screen glitch is there but i can end calls w the power button. Would a theme make the phone act wacky?
jeff5347 said:
What do u mean by mashed up. Do you mean by cm9 or the aokp cm9. I am getting some really wacky stuff happening. System running real slow, screen not coming on usually from a call or sometimes when trying to unlock phone, now my VM wouldn't respond, apps taking a lot more time than usual to open. I don't know if this is the aokp from or the phone. I had the screen glitch w eclipse but not all the other stuff. I called verizon and they r willing to send out a replacement but just not sure if its the phone or rom
Click to expand...
Click to collapse
Mashup is a flashable add on for roms. It is supposed to make things run smoother and help with the signal. Mashup is pre installed on CM9 alpha 5 and beta 1, I don't believe AOKP comes with it but Im not sure. And I had a bunch of issues with CM9, but Ive been running CM7 for months and love it. Maybe give CM7 a shot till the new ICS roms get debugged a little more.
Ok first off dont ever talk to verizon about your issues, always come to the forums... Always. Verizon doesn't know anything beyond complete stock. You need to spend time looking around the x2 forums read read read. Mashup is a mod that's right here in our dev forum very easy to apply just download the right version and flash in the appropriate recovery
Rolling AOKP in the north.
Out of nowhere, the bottom buttons stopped working today. I was on a Sense ROM (ICS Business) and I figured it was just software related. I tried 5 or 6 different ROMs, even went back to stock. Has anybody else had this issue before? If so, is it hardware or is there a way to get this working again?
For the interim, I just installed an AOKP Rom (Neo 1.5 Linaro) because it offers the software replacement navbar. Out of curiousity, does anybody know what other ROMs may offer the same software replacement?
I was going to look at Neo Rage (1.6 Linaro), but it's listed as AOSP and I'm not sure it offers them or not. I assume there are no Sense based ROMs that offer this?
Thanks!
-J
In any AOSP rom you can enable the soft keys. Some roms you have to manually edit XML files to get them though. In sense, you can't add them
Thanks. I'll poke around some other AOSP ROMs as well. I never really paid attention to them mainly cause I had no use for them heh. Now I really don't have much of a choice.
AshtonTS said:
In any AOSP rom you can enable the soft keys. Some roms you have to manually edit XML files to get them though. In sense, you can't add them
Click to expand...
Click to collapse
Please Ashton, do some fact checking.
xjacobx made softkey mods for early Sense ROMs (like back in January).
Edit:
And here's the thread
http://forum.xda-developers.com/showthread.php?t=1466143
nablicsu and
vgjunkie said:
Out of nowhere, the bottom buttons stopped working today. I was on a Sense ROM (ICS Business) and I figured it was just software related. I tried 5 or 6 different ROMs, even went back to stock. Has anybody else had this issue before? If so, is it hardware or is there a way to get this working again?
For the interim, I just installed an AOKP Rom (Neo 1.5 Linaro) because it offers the software replacement navbar. Out of curiousity, does anybody know what other ROMs may offer the same software replacement?
I was going to look at Neo Rage (1.6 Linaro), but it's listed as AOSP and I'm not sure it offers them or not. I assume there are no Sense based ROMs that offer this?
Thanks!
-J
Click to expand...
Click to collapse
Did you run any of the mods to dim the lights? I know I run a mod that scripts this change and I wonder if that's sticking and not playing nice with the other roms. Do you have anything for dimming the lights in:
/system/etc/init.d? if so maybe remove that
wlmeng11 said:
Please Ashton, do some fact checking.
xjacobx made softkey mods for early Sense ROMs (like back in January).
Edit:
And here's the thread
http://forum.xda-developers.com/showthread.php?t=1466143
Click to expand...
Click to collapse
ehh, I didn't know that thanks!
Ok, looks like I am not the only one, sorry to dig up this old thread, but my Capacitive Buttons stop working today.
I did not install any app, or made any changes and had been using the same (Niles Business 3.6) ROM since Jan.
I never have that dim Capacitive Buttons script.
I did not drop the phone recently either.
I am going to try INFECTION and see if it can tie me over until I get a new phone.
Oj, my guess here is something happened to the digitizer or digitizer ribbon cable. Have either of you had your phone disassembled anytime? If it's not the digitizer and software related, a hard reset or new ROM install should have fixed it no questions asked......
unless some other piece of hardware in this phone has taken a dump. .?
No, the phone had never been taken apart. The only thing that happens to the Rezound, was that I dropped in about 3 ft on asphalt, and it only had a few minor rash on the frame (the shiny part), and that happened many months before the capacitive buttons died.
I am added the info below to hopefully help others that have this issue.
Installed INFECTION, followed Neo's direction (below), and it has a usable phone again.
IAmTheOneTheyCallNeo said:
Add this to your build.prop, fix permissions, then reboot
qemu.hw.mainkeys=0
That will get you a navigation bar
Sent from my Rezound using xda premium
Click to expand...
Click to collapse
I'm hoping someone else has already solved this issue, but I seem to be running into serious problems with AOSP CM ROMs with regards to the power button. Recently I actually bricked my original EVO 4G LTE and got a "new" one via the insurance replacement program with Sprint. I immediately obtained rooted, installed recovery, and obtained S-off. I then proceeded to install CM10.2 (deck's build) and am actually still running 9/20 version of this ROM.
My problem with the power-button is that it sometimes does not respond to a press where it may not wake the screen or sleep the screen. Sometimes it takes 2, 3 or more presses to get it to respond. Additionally, sometimes after the screen sleeps it will immediately wake again. It's as if the button is not properly de-bounced. My first thought was that the power-button was physically broken.
So as an experiment I rolled back to previous versions of CM10.1 and got the same results, even after clean flashes. Then I tried rolling back the stock ROM which came with the phone, from a nandroid backup. Shockingly, no power button issues at all. So with a sense based ROM, it seems to work perfectly, but a AOSP based ROM (specifically, CM10.x) I see the issues.
Could this be a kernel issue? Anyone else seen or resolved this issue already?
Thanks. Sincerely,
Frustrated.
Yeah I have that sometimes too although occasionally it won't even wake up and will have shut off by itself
Sent from my EVO using xda app-developers app
Promising update.
I updated the latest TP firmware from Captain Throwback, on a whim. While it doesn't seem to have fixed the issue, it seems much improved. The jury is still out - and it's only been an hour or so since I installed, so this is hardly enough data to say definitively. But promising.
FW is here: http://tinyw.in/cRCf
nebhead said:
Promising update.
I updated the latest TP firmware from Captain Throwback, on a whim. While it doesn't seem to have fixed the issue, it seems much improved. The jury is still out - and it's only been an hour or so since I installed, so this is hardly enough data to say definitively. But promising.
FW is here: http://tinyw.in/cRCf
Click to expand...
Click to collapse
Yup, spoke too soon. Still having issues. The search continues.
I just got a replacement evo lte and my power button sucks.. I gotta hold it down for a few seconds to wake or lock and that was before root.. I'm rooted now and on sense 5 r145 but I use the swipe to unlock and lock and it works great.. I said forget the power button...
Sent from my EVO using xda app-developers app
hondafreak513 said:
I just got a replacement evo lte and my power button sucks.. I gotta hold it down for a few seconds to wake or lock and that was before root.. I'm rooted now and on sense 5 r145 but I use the swipe to unlock and lock and it works great.. I said forget the power button...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
So your power button was bad with the stock ROM too? That's a bummer. At least mine seems to work OK with the stock ROM. Maybe I should try some modified stock ROMs to see if there is a difference there.
You're not alone. My brother and I both have EVO's and we're both experiencing this issue. It's annoying as hell having to press the power button multiple times to wake the device. Didn't start having this issue until the end of the CM.1 cycle. I also went back to Sense and found no problems. It only appears to occur on non sense ROMs. Does anyone have any insight to this or possibly a fix?
It's a kernel issue. That problem did not pop up until the 3.4 kernels started coming out.
AndrasLOHF said:
It's a kernel issue. That problem did not pop up until the 3.4 kernels started coming out.
Click to expand...
Click to collapse
Well that's great news (sort-of) and means that some day someone could potentially resolve this in the kernel. Maybe we need to X-Post with the CM10.2 development forum, unless they are already aware and are working on this.
nebhead said:
I'm hoping someone else has already solved this issue, but I seem to be running into serious problems with AOSP CM ROMs with regards to the power button.
Could this be a kernel issue? Anyone else seen or resolved this issue already?
Click to expand...
Click to collapse
There were certain nightly/kernel mixes with the 10.2 and Haunted kernel that seemed to clear it up for me.
I can't for the life of me remember which combination. Sorry.
One thing that alleviated that for me a bit was enabling "Volume Buttons Wake Up Handset" or whatever it was.
physix said:
There were certain nightly/kernel mixes with the 10.2 and Haunted kernel that seemed to clear it up for me.
I can't for the life of me remember which combination. Sorry.
One thing that alleviated that for me a bit was enabling "Volume Buttons Wake Up Handset" or whatever it was.
Click to expand...
Click to collapse
Cool, I think I may try the Haunted Kernel. Nandroiding first of course. I will report back later.
Yeah try a new kernel and use kernel tuner and turn on the Swype to wake option it is pretty cool..
Sent from my EVO using xda app-developers app
Haunted Kernel 31 + Unofficial CM10.2 9/20 Build (Deck) appears to still have issues. Although it seems a bit better than before. As to whether this introduces new issues, I'm not sure yet.
The work on the kernel is ongoing. Trust me, it's way better than it was before.
Captain_Throwback said:
The work on the kernel is ongoing. Trust me, it's way better than it was before.
Click to expand...
Click to collapse
Yup, expected to have a few hiccups using bleeding edge ROMs & kernels. Glad to hear that these types of things are being addressed. The Haunted kernel definitely makes things much, much better. It's definitely daily driver quality now.
As a side note, I've also noted that the WiFi seems to work better with the Haunted kernel as well. Not sure if that's related, but where I used to have difficulty staying connect to WiFi at home and at work, it now seems rock solid. Still a bit too early to be definitive, but so far so good.
nebhead said:
Yup, expected to have a few hiccups using bleeding edge ROMs & kernels. Glad to hear that these types of things are being addressed. The Haunted kernel definitely makes things much, much better. It's definitely daily driver quality now.
As a side note, I've also noted that the WiFi seems to work better with the Haunted kernel as well. Not sure if that's related, but where I used to have difficulty staying connect to WiFi at home and at work, it now seems rock solid. Still a bit too early to be definitive, but so far so good.
Click to expand...
Click to collapse
Haunted Kernel is still behind some, last I checked. So while you may have some benefits, you will lose/miss some fixes/optimizations. But to each his own.
Captain_Throwback said:
Haunted Kernel is still behind some, last I checked. So while you may have some benefits, you will lose/miss some fixes/optimizations. But to each his own.
Click to expand...
Click to collapse
Good to know. I will keep flashing and keep trying the new builds as they become available. For now, this seems to be a good combo for me. The current Haunted governor actually kinda seems to be draining the battery fast so I may tweak that. Anyway, thanks for all the responses here, this has really enlightened me on this issue.
Hey.. I'm behind for a reason
Sent from my EVO using Tapatalk now Free