I'm running the CM9 beta 0.2.0 by jokersax11 ([Ics] cm9 beta with camera CDMA/GSM/UMTS/HSDPA/WCDMA/roaming 2/22/12) and my capacitive touch buttons at the bottom of the screen*(Menu, Home, Back and Search) are not lighting up at all! I can't figure it out at all and I really need these buttons to light up, due to my recent switch from the LG Optimus S, and before that I had an AT&T HTC Inspire 4g (which have the home and menu buttons reversed). I use my phone alot at night and I desperately need to get this fixed! Is there something in the CM9 settings I'm overlooking? Or is there an app or mod that I could use to get control of them and get them working again? PLEASE HELP! I WOULD REALLY APPRECIATE ANY ADVICE OR ANY INFO ON HOW TO GET THESE BUTTONS TO LIGHT UP AGAIN! This is really frustrating!
Click the link below for the answer ...
http://forum.xda-developers.com/showthread.php?t=1526546
EDIT - Well that was fun. If you haven't figured it out, the link above goes to the other thread you started, with the same title, and the same body, in the same forum .... You should not create duplicate threads. For future reference best practice is create 1 thread and wait a minimum of 24 hours between bumps.
With that out of the way my actual advice is as follows, i dont believe the capacitive buttons are an issue with jokers CM build although i dont personally use it. This would indicate the answer lies in a) something you did b) something you didnt do c) something you installed
1. You can eliminate a and b without losing any info by going into your custom recovery and wiping cache and dalvik cache then doing a dirty flash on the rom (dirty flash = don't wipe data/factory). In this case there would be no reason to reflash gapps.
2. If that doesn't work, do a full wipe (data factory/system/dalvik) and reflash the ROM, then gapps. Be slow to in stall your apps and test the capicitive buttons frequently to ensure you haven't done anything to break them
Set the phone's brightness to Automatic.. Fixed..
People are so over dramatic sometimes lol.
Sent from my MB855 using Tapatalk
Thanks, that pointed me in the right direction. My auto brightness isn't working. I'm gonna do a "dirty flash" and see if that helps. Oh and btw,the second post was an accident and you can't delete your own thread.So, sorry about that.
eszumlas1985 said:
Thanks, that pointed me in the right direction. My auto brightness isn't working. I'm gonna do a "dirty flash" and see if that helps. Oh and btw,the second post was an accident and you can't delete your own thread.So, sorry about that.
Click to expand...
Click to collapse
Please come back and update the thread on if it works or not. Others may experience the same issue in the future and this thread could assist them.
Cheers!
i just now notices mine dont light up but o well my thumb pretty much know ware to push
Well, it's fixed. Don't know what the heck was going on but reflashed my CM9 & Google apps and voila my automatic brightness switch in settings started working again. No more problems and capacitive buttons work fine. Strange but at least it's fixed
Sent from my MB855 using xda premium
And sorry to anyone that needed a fix to this. I was involved in the tornado that hit Branson, Missouri and was unable to keep phone charged due to the power outage that lasted over a week, and had bigger things to worry about at the time, like getting shelter and food. But everything is ok now and hope this thread helps anyone that has this problem. Check to see if your automtic brightness switch is working under settings (mine wasn't working) So if it isn't working just reboot into recovery, wipe dalvik cache & /cache, and reflash your rom and gapps, then check in your settings to see if your automatic brightness is now working. If so your problem should be fixed and your capcitive buttons should now light up. It worked for me, hopefully it will work for you.
Sent from my MB855 using xda premium
eszumlas1985 said:
Check to see if your automtic brightness switch is working under settings (mine wasn't working) So if it isn't working just reboot into recovery, wipe dalvik cache & /cache, and reflash your rom and gapps, then check in your settings to see if your automatic brightness is now working. If so your problem should be fixed and your capcitive buttons should now light up. It worked for me, hopefully it will work for you.
Click to expand...
Click to collapse
Thanks man i just had to set the screen brightness to automatic and reboot once. It worked like a charm
Related
Anyone experiencing unresponsive touch screen issue with GingerDX, this issue only occur in bottom area of display, such as "space button" "delete button" on virtual keyboard and all apps. I need to touch it many times to make it work.
GingerDX is my first ROM, hope someone can tell me how to fix it... According developer thread i have do this :
If you get unresponsive touchscreen, please wipe cache partition, dalvik cache, and reboot twice
Click to expand...
Click to collapse
and I have do it, but still no luck.
Thanks
Sorry my English bad
Kind Regard.
Try factory reset and installing again. It helps you too much
It's not just you - I get the same problem (hard to drag the notification bar back up, bottom row of keys is unresponsive on certain keyboards) - also using GingerDX
I did see the dev acknowledge the notification dragging issue as "a common problem with gingerbread roms" so I'm not sure what's going on.
edit: http://forum.xda-developers.com/showthread.php?p=16699717&highlight=notification#post16699717
benjymous said:
It's not just you - I get the same problem (hard to drag the notification bar back up, bottom row of keys is unresponsive on certain keyboards) - also using GingerDX
I did see the dev acknowledge the notification dragging issue as "a common problem with gingerbread roms" so I'm not sure what's going on.
edit: http://forum.xda-developers.com/showthread.php?p=16699717&highlight=notification#post16699717
Click to expand...
Click to collapse
alll CM7 based ROM's havethis issue because of a bug in CM7 itself i think
I'm running the CM9 beta 0.2.0 by jokersax11 ([Ics] cm9 beta with camera CDMA/GSM/UMTS/HSDPA/WCDMA/roaming 2/22/12) and my capacitive touch buttons at the bottom of the screen*(Menu, Home, Back and Search) are not lighting up at all! I can't figure it out at all and I really need these buttons to light up, due to my recent switch from the LG Optimus S, and before that I had an AT&T HTC Inspire 4g (which have the home and menu buttons reversed). I use my phone alot at night and I desperately need to get this fixed! Is there something in the CM9 settings I'm overlooking? Or is there an app or mod that I could use to get control of them and get them working again? PLEASE HELP! I WOULD REALLY APPRECIATE ANY ADVICE OR ANY INFO ON HOW TO GET THESE BUTTONS TO LIGHT UP AGAIN! This is really frustrating!
Click the link below for the answer ....
http://forum.xda-developers.com/showthread.php?t=1526616
EDIT - Well that was fun. If you haven't figured it out, the link above goes to the other thread you started, with the same title, and the same body, in the same forum .... You should not create duplicate threads. For future reference best practice is create 1 thread and wait a minimum of 24 hours between bumps.
With that out of the way my actual advice is as follows, i dont believe the capacitive buttons are an issue with jokers CM build although i dont personally use it. This would indicate the answer lies in a) something you did b) something you didnt do c) something you installed
1. You can eliminate a and b without losing any info by going into your custom recovery and wiping cache and dalvik cache then doing a dirty flash on the rom (dirty flash = don't wipe data/factory). In this case there would be no reason to reflash gapps.
2. If that doesn't work, do a full wipe (data factory/system/dalvik) and reflash the ROM, then gapps. Be slow to in stall your apps and test the capicitive buttons frequently to ensure you haven't done anything to break them
Since I cant post on the original dev thread:
the torchlight has a bug:
- works only once
- have to reboot to be able to use it again after it is turned off
reproduce:
- use torchlight by turning on (powerbutton hold and use funciton; has to be enabled in rom config)
- turn off
- try turning on again; does not work
- works again after reboot
mby someone can reproduce and confirm the bug;
it is the only issue I am having with the rom; no freezes everything is stable
this seems like missing reset of bool allow_on = true ;P
+1
But for me,i don't have to reboot.
turn on the light one time work.turn off
If i want to return on dont work.
But if i unlock and relock the phone.It work
Let the phone lock itself don't work
I'll have to unlock and lock him manually
I cannot even get the 14.04 version to run!
I had 10.04 and tried upgrading, without wiping, with wiping, etc. I even tried using different kernels, thinking that maybe there was a compatibility issue there but each time the boot stopped showing the pink frozen unicorn...
Sad56 said:
+1
But for me,i don't have to reboot.
turn on the light one time work.turn off
If i want to return on dont work.
But if i unlock and relock the phone.It work
Let the phone lock itself don't work
I'll have to unlock and lock him manually
Click to expand...
Click to collapse
very well then it is a genuine bug, since I am sure you should be able to turn the torchlight on and off as you please and not go into automatic lock to be able to turn it back an
Don't know
I just test for feedback.
For me i enable this option in statusbar options and it works fine.
Hydrogen ROM is weak, and had too many problems to call it a full ICS ROM.
No External SD access, bad battery life unless you monitor everything for 3 days, and now bugs with simple things. I wish it worked, I loved what I saw when I was on it, but its just too janky for my liking.
INB4 flaming fanboys.
Sent from my GT-I9100 using XDA
Have you tried to go onto the Settings and configuring the touchlight there? Try searching the thread, people have been posting about this issue, maybe the answer is in the thread.
Q&A for [ROM][4.4.4][CyanideMod]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4][CyanideMod]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
CyanideMod V2 volume
I am currently having a problem. The volume buttons on the phone are not working for Ringtone and Notification. They will only adjust the volume of the music, games & other Media. I have it set in Sound/Volumes, but it is not working. Also, I am not able to adjust the volumes in the profiles, they just stay set at defaults.
ke7vng said:
I am currently having a problem. The volume buttons on the phone are not working for Ringtone and Notification. They will only adjust the volume of the music, games & other Media. I have it set in Sound/Volumes, but it is not working. Also, I am not able to adjust the volumes in the profiles, they just stay set at defaults.
Click to expand...
Click to collapse
After media volume shows up click to make the volume extendable and then adjust the notification volume. I just noticed this so I'll be looking before I start working on it again
Sent from my SGH-I317 using XDA Premium 4 mobile app
In v3, the classic (stock) recent apps panel seems to crash systemui. Slim recents works OK.
radoo7701 said:
In v3, the classic (stock) recent apps panel seems to crash systemui. Slim recents works OK.
Click to expand...
Click to collapse
Will you check if omniswitch can be set as default recent app still? I fixed the stock recent issue before I uploaded but if omniswitch can still be selected as default then I uploaded the unfixed version. I'll upload V3.5 soon. Working on a kernel/recovery mod at the current time
Sent from my SGH-I777 using XDA Premium 4 mobile app
Yes I can set omniswitch as the default for recents. Just to be sure I did a clean install and still have the issue with stock recents.
radoo7701 said:
Yes I can set omniswitch as the default for recents. Just to be sure I did a clean install and still have the issue with stock recents.
Click to expand...
Click to collapse
Well poop lol. That's actually good tho. Like I said I did already fix this, I just apparently uploaded the unfixed version. Oops. I can run a build fairly quickly as a still have the s2 build cached but I'm using build environment to build and make some recovery changes at the moment
FUSE support?
Hi,
I found this ROM last night and flashed it, and want to say thanks. I was having trouble with other ROMs aborting installation, but this one installed without a hitch. Everything works as it should, and way better than my old CM9 ROM. This was completely painless.
Question: Does the kernel have FUSE support?
I'm trying to get SSHFS working; I can ssh into the target server via terminal emulator, but SSHFS will not mount. It appears to mount but doesn't really. When I click unmount, It complains:
fusermount: error getting lock: Invalid argument
I know this isn't the place to get help with SSHFS, but it will only work if the kernel has FUSE support, so that enters into your bailiwick.
Oh, and a possible issue: It seems I'm not getting as strong a network signal now as I did before flashing this ROM. Is it even possible this could be due to a software issue?
Thanks again for the great work. You are awesome!
Stock recent panel is not working. Could just be my dirty flash. Thank you for your hard work. This ROM is amazing.
Sent from my SGH-I777 using XDA Free mobile app
modem not working
I've been running a CyanogenMod-9 version for quite awhile, until about a week ago when I decided to upgrade. I tried some of the CM-10 versions, and installation aborted midway, leaving me stuck with a non-working phone for a few days.
I flashed CyanideMod-V3-S2 a few days ago, and was very pleased to see it install effortlessly. It looks great, and everything seems to be working, EXCEPT the modem.
The network signal is very weak. I can make calls if I am in town, or on top of a high hill, but often I get no signal at all. I do live in a rural area, but it has never been this weak. Even when I get full bars, they are always white, never blue as they should be. I have no access to data.
I don't know much about AT&T's network; frequencies, etc., but my semi-educated guess is that I'm not picking up all the frequencies I should.
In my settings:
Mobile network is on.
Data is enabled
Preferred network type is set to 3G
Network operators is set to ATT
Access Point Names was set to ATT LTE. I stopped in today at an ATT store, and the rep's phone was set to "ATT Phone" so I experimentally changed to that and rebooted, but saw no change. The settings in the 7 available choices match the setting in other working phones in our household, so I don't think this is a settings problem.
I found the "Consolidated Modem" thread on this site, which lists 13 choices for modems. My phone reports a "Baseband version of i777UCKK6, which is one of the choices in that page, which I assume was installed with the ROM. I don't know if the modem is my problem, and wouldn't have a clue which of these to try. Are they installed through recovery in the same way as the ROM and gapps?
I love this ROM, but the phone is nearly unusable as it is. Has anyone else had this problem, or does anyone have any pointers?
Thanks so much for all your hard work.
Newest modern is UCMD8. Rom wouldn't affect the modem other then the usual kk signal issues
Thanks for the update. Amazing!! Stalk recents still does not work (maybe because of dirty flash, please confirm with other users). Also the power menu-reboot menu does not have reboot to recovery. Reboot to recovery is available in stweaks. But it would be nice to have again in power menu.
dagwoodmash said:
Thanks for the update. Amazing!! Stalk recents still does not work (maybe because of dirty flash, please confirm with other users). Also the power menu-reboot menu does not have reboot to recovery. Reboot to recovery is available in stweaks. But it would be nice to have again in power menu.
Click to expand...
Click to collapse
If you uncheck and recheck Advanced Boot in Developer Options you should get the boot to recovery to show back up. It still shows for me after update.
I am getting FC on Google play services after update and cannot access my account. Would reflashing gapps fix that?
radoo7701 said:
If you uncheck and recheck Advanced Boot in Developer Options you should get the boot to recovery to show back up. It still shows for me after update.
I am getting FC on Google play services after update and cannot access my account. Would reflashing gapps fix that?
Click to expand...
Click to collapse
Thanks for helping him. Yes just reflash gapps. Not sure why it's like that but for some reason it is. I don't need it while testing but then do later on. Strange
Awesome build (V4). Coming from CM of a few months ago, everything is real snappy (also due to flashing afresh).
A few bugs so far:
1) Tapping on notifications in the pull-down drawer doesn't seem to link to anything (the animation works, but the associated action doesn't fire). Additionally, the Halo/Quick Settings buttons at the top of the notification drawer seem to get pushed off the edge of the screen (Would be nice if the Halo button could be removed/Halo disabled).
2) Lock screen slider shortcuts cover up cLock
3) Volume buttons (including from home screen) control system volume, not ringer/notification volume.
Amazing work, in any case! Some day I'll need to get a new phone.
b
Gonna be starting from scratch here.. can you give me a quick runthrough.. I have a bricked i777 that I will be starting with.. starting with an Odin tar(stock rooted 4.1.2?) to get it back up and running. It' s been years but I'll figure it out. just need a simple outline like which stock Odin tar.. then which android versions and recovery to install to get to your 4.4.4 .
thanks
tri0xinn said:
Gonna be starting from scratch here.. can you give me a quick runthrough.. I have a bricked i777 that I will be starting with.. starting with an Odin tar(stock rooted 4.1.2?) to get it back up and running. It' s been years but I'll figure it out. just need a simple outline like which stock Odin tar.. then which android versions and recovery to install to get to your 4.4.4 .
thanks
Click to expand...
Click to collapse
I'm driving but maybe @creepyncrawly could point you there. Flash odin rom, flash odin custom kernel for recovery, make a backup, do a factory reset and wipe system, flash shift kernel, tenor to recovery abs flash rom and gapps. Use V3 of this rom. It's all here. You could probably fine before he sees this. I'm voice typing or I'd help you out
Sent from my SGH-I317 using XDA Premium 4 mobile app
tri0xinn said:
...which stock Odin tar.. then which android versions and recovery to install to get to your 4.4.4 .
thanks
Click to expand...
Click to collapse
Use latest stock 4.1.2, I777UCMD8 which you can get from the download repository (link in my signature) Also some other stuff there if you need it, but not the recovery and firmware you need.
thanks a ton, got everything back to square one with that I777UCMD8 tar, easy after that and now running cyanidemod and it's running as slick as my gs5.. at least it seems to be. thanks again:good:
After a couple days of use its still running super slick.. only issue thus far is pretty bad battery life.. any settings i can adjust to improve things? Or another kernel maybe.. anyone else have issues with battery life?
I downloaded CM12 this morning using the updater. Auto update worked but lots of upgrade issues. Must update Framework but then things got better. Chrome is broken so I'm using stock browser. Recovery is awful. Make a backup before doing it but it sure is a start!
Sent from my Xperia Z Ultra using XDA Free mobile app
mknewman said:
I downloaded CM12 this morning using the updater. Auto update worked but lots of upgrade issues. Must update Framework but then things got better. Chrome is broken so I'm using stock browser. Recovery is awful. Make a backup before doing it but it sure is a start!
Sent from my Xperia Z Ultra using XDA Free mobile app
Click to expand...
Click to collapse
how did you install gapps? the recovery wont let me install them
I was able to. I had to copy it to internal sdcard though.
If you have FC crashes try uninstalling and reinstalling the apps. That helped me with several like News and Weather and Newsstand and Drive.
Sent from my SGP311 using XDA Free mobile app
mknewman said:
I was able to. I had to copy it to internal sdcard though.
If you have FC crashes try uninstalling and reinstalling the apps. That helped me with several like News and Weather and Newsstand and Drive.
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
thanks. i thoght i edit my post, i found another gapps zip and put it on the internal storage and it installed ok.
most stuff works. swiftkey do not..
* Audio trough Bluetooth = broken
Rolle90 said:
thanks. i thoght i edit my post, i found another gapps zip and put it on the internal storage and it installed ok.
most stuff works. swiftkey do not..
* Audio trough Bluetooth = broken
Click to expand...
Click to collapse
Pretty decent nightly, had issue with backlight setting that messed up screen brightness after screen lock. Had to reflash, there was no way back. I would suggest people avoid playing with backlight setting for the meantime.
Flashed nano GAPPS from here http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Rolle90 said:
* Audio trough Bluetooth = broken
Click to expand...
Click to collapse
Confirmed.
How often do you guys think cm will puch updates for this rom?
Rolle90 said:
How often do you guys think cm will puch updates for this rom?
Click to expand...
Click to collapse
Daily?
Just toght that the cm11 build did not get daily updates...
My Bluetooth is working fine, both to my Pebble watch and car.
I'm not sure what's up with backlight on this build. You have two options that seem to be the same on the DISPLAY settings, one says "Adaptive Brightness, Optimize brightness level for available light" and the other says "Adaptive Backlight, Dynamically adjust the brightness of the display's backlight to maximize battery life while maintaining usability".
The first one seems to adjust properly, and the slider bar does seem to set the upper limit for this level.
The 2nd one is a bit more problematic, I'm not really sure it works or how it functions in conjunction with the other one.
Anyone figure this out yet?
BTW I tried the full version of Lux with both of them turned off and it didn't end up well, the screen became so dark I ended up having to reboot and remove it.
Marc
restarted my phone two times and got BT audo, spotify works fine, but if i start Valiant Hearts the audio get realy static and laggy
EDIT:
New build just Launched!
Could you post some Screenshots? I'd like to see how application box and the main screen look like
Thanks!
Anyone tried from clean flash?
Has anyone tried flashing the nightly after doing a complete wipe? Seems like many of the problems mentioned may be avoided by a clean install.
If someone has done a clean install, can you let us know if there are any bugs remaining?
Thanks
mknewman said:
My Bluetooth is working fine, both to my Pebble watch and car.
I'm not sure what's up with backlight on this build. You have two options that seem to be the same on the DISPLAY settings, one says "Adaptive Brightness, Optimize brightness level for available light" and the other says "Adaptive Backlight, Dynamically adjust the brightness of the display's backlight to maximize battery life while maintaining usability".
The first one seems to adjust properly, and the slider bar does seem to set the upper limit for this level.
The 2nd one is a bit more problematic, I'm not really sure it works or how it functions in conjunction with the other one.
Anyone figure this out yet?
BTW I tried the full version of Lux with both of them turned off and it didn't end up well, the screen became so dark I ended up having to reboot and remove it.
Marc
Click to expand...
Click to collapse
The second is how the display reacts to the brightness of the displayed image on screen
---------- Post added at 07:15 AM ---------- Previous post was at 07:12 AM ----------
lkirkw said:
Has anyone tried flashing the nightly after doing a complete wipe? Seems like many of the problems mentioned may be avoided by a clean install.
If someone has done a clean install, can you let us know if there are any bugs remaining?
Thanks
Click to expand...
Click to collapse
.
I did a clean install. Not many problems here, BT audio stop working from time to time, (reboot fix the problem for a while)
Hey, do any of you guys have a flashable CWM recovery? I'd like to try to use it instead of CM's recovery.
alphaandomega said:
Hey, do any of you guys have a flashable CWM recovery? I'd like to try to use it instead of CM's recovery.
Click to expand...
Click to collapse
I've tried all sorts to put a different recovery on. Have ended up with no usable recovery on the phone. Only option is to put up with CM for now.
lkirkw said:
Has anyone tried flashing the nightly after doing a complete wipe? Seems like many of the problems mentioned may be avoided by a clean install.
Click to expand...
Click to collapse
Mine was a clean install, Bluetooth is the only problem for me.
mknewman said:
My Bluetooth is working fine, both to my Pebble watch and car.
I'm not sure what's up with backlight on this build. You have two options that seem to be the same on the DISPLAY settings, one says "Adaptive Brightness, Optimize brightness level for available light" and the other says "Adaptive Backlight, Dynamically adjust the brightness of the display's backlight to maximize battery life while maintaining usability".
The first one seems to adjust properly, and the slider bar does seem to set the upper limit for this level.
The 2nd one is a bit more problematic, I'm not really sure it works or how it functions in conjunction with the other one.
Anyone figure this out yet?
BTW I tried the full version of Lux with both of them turned off and it didn't end up well, the screen became so dark I ended up having to reboot and remove it.
Marc
Click to expand...
Click to collapse
I didn't bother with Lux, just playing with those two settings made my screen super dark, had to reflash.
alphaandomega said:
Hey, do any of you guys have a flashable CWM recovery? I'd like to try to use it instead of CM's recovery.
Click to expand...
Click to collapse
My understanding of the Z Ultra is that the kernel and recovery are both on the boot partition and are not actually separate. If you install TWRP or Philz you will wipe the CM12 kernel out and you won't boot, just be able to get into recovery. Those recoveries are built for stock/stock based installs where you can replace the kernel.
We will just have to wait for a good CM12 Recovery or boot to CM11 and use its recovery to backup /data and then reinstall CM12 before you boot up. I think I've seen that refered to hot booting recovery.
Please feel free to correct me if you are a dev and know more about this than me.
Marc
zs29a said:
I didn't bother with Lux, just playing with those two settings made my screen super dark, had to reflash.
Click to expand...
Click to collapse
Had the same issue. Just leave the second one (adaptive backlight) enabled and the dark screen should stop. You can adjust the first one at will