Database Info

Nexus S, ICS, and capacitive button light notification

One of the things that turned me off and kept me on cm7 was the lack of of capacitive button notification lighting in ICS. Is there a way that this has been resolved on stock without using another CM rom? I am really hesitant to go back to an alpha build because it took me so long to get full functionality from the rom and the phone and work exactly how I wanted it.
Thanks.

Alpha lol!! Flash a kernel with bln....
Sent from my Nexus S using xda app-developers app

CM7 isn't ICS, that's CM9. Also it hasn't been an alpha for at least 2 months, it's in RC1 which is as stable as you're going to get.

Use Airkernel or Martrix Kernel to enable BLN.(You can use NSTOOLS to adjust the settings).

Reread what I wrote. One of the things that turned me off of ICS and kept me on CM7 (I know it's GB) is the lack of notification lit capacitive buttons. I basically want to upgrade to ICS or later (really JB once there is a more functional release) but those lit capacitive buttons are crucial for me as I have the att nexus s that has lcd screen and not the more effecient led screen. So a lot of those led notification apps dont help me. A couple of responses here are helpful. I'm hoping there will be a kernel with bln for stock ota jellybean when that comes out. Will that be easy to attain?

It shouldn't be hard to implement BLN for jb. There are numerous kernels with back light notifications for 4.0.4. Have you even checked the development section?
Sent by pocket technology.

chronophase1 said:
It shouldn't be hard to implement BLN for jb. There are numerous kernels with back light notifications for 4.0.4. Have you even checked the development section?
Sent by pocket technology.
Click to expand...
Click to collapse
I didn't know they were called back light notifications until this post (I had kept searching "capacitive button notification light nexus s" the whole time) , so please bare with me as I'm learning. I appreciate your pointing me in the right direction. It gives me hope that when a very functional release of JB for nexus s is out I will be able to use BLN on it.

Its cool. I didn't mean to come across so harshly. My apologies. Yeah. There's a ton of kernels that support it. Just take your pick
Sent by pocket technology.

[Q] (Q) cm10 lockscreen touch not responsive

Hello,
I hope this is in the right area, xda / android newb (switched from iPhone within the past three months WOOHOO :good but here goes...
I have the HTC One X (at&t) and I'm running CM10 nightly 20121216 with rohan kernel b6. Every once in a while I when I unlock my phone the touchscreen is completely unresponsive, meaning the lock slider does not work whatsoever nor does the notification center pulldown. I did my best to research this issue and I'm not sure how to replicate it or if its even relevant to CM10. As in is it just my phone, or is it rom / kernel combo that causes this? The only way to resolve this issue is to power down the phone using vol down + power as the power menu is unresponsive as well. If anyone has any insight and would like to provide a solution OR if this is a completely new bug I would be happy to provide more information.
Oh, and a big shout out to Richard V. for figuring out LED for notifications :laugh::good:

I'm pretty sure this is probably a bug with Sweep2Wake, enabled by rohan's kernel that you have installed. Try reflashing CM10 without any custom kernel and then see if you have the problem.

Under volting has cause that for me several times on cm. Its the death sleep. I stopped using kernel mods altogether because of stability about a month ago. So not sure if that's what is still happening for you. But perhaps give it a shot
Sent from my One X using xda premium

Thanks guys I'll be sure to try that out. I somewhat had a feeling it might have something to do with the kernel.

[Q] Screen becomes unresponsive upon calls, help?

So to start, my phone is rooted and the bootloader is unlocked. I should also have the latest modem flashed. The problem is that the screen will freeze upon some calls, not all of them, and prevents me from doing anything. I can still hear everything that's coming through but the screen itself is just unresponsive. At that point, I usually just pull the battery and reboot and make the call over again. It hasn't happened to me immediately after a battery pull yet.
This problem has occurred to me on multiple roms. I initially noticed it on LiquidSmooth's 3/16/13 stable build and so I re-flashed it making sure to do a clean install. It kept on happening so I kept switching roms and am now on Carbon Rom and it hadn't given me any problems until just now (been on Carbon for over a week). All of my rom installs are done with clean flashes so I really don't know what's going on at this point.
Any help would be absolutely fantastic!

it's a known issue on AOSP roms

Try using the latest Official CM10.1 nightly. Best to do reset, clean install. That issue has pretty much been squashed on the latest builds.
Sent using Tapatalk

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

I had no idea about it being a problem on aosp ROMs since it hasn't occurred for me on them until recently. But I'll definitely cm10.1 a try! Thanks!
Sent from my SCH-I535 using xda app-developers app

kupnooduls said:
I had no idea about it being a problem on aosp ROMs since it hasn't occurred for me on them until recently. But I'll definitely cm10.1 a try! Thanks!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I am currently using Paranoid Android which is based off cyanogenmod, and I get the same thing. Phone freezes mid call. I was having general freezing problems across the board until I installed PA, I kept thinking is was my launchers, etc, but I am bare bones right now and it still does it periodically, and have once had it do it directly after a battery pull.
When mine does it, the call drops.

Two things..
First, I have been having the same phone freeze issues as everyone else, tried different roms, the dummy file fix, all kinds of different things going through this forum. I wanted to do everything I could possibly do before posting about it.
I am using Paranoid Android. I noticed the cyanogenmod version listed in the phone info is [email protected]#1 Tues March 19
Is this just a PA version number or actually the kernel number? What if I was to flash the newest stable kernel to my PA?
ALSO
I noticed when my phone does its freeze up thing, the battery has been at 53-57%. It does not seem to do it any lower or higher battery percentage. Is it possible that its actually a problem with the battery or the battery percentage programming??? It just seemed odd that it always seemed to be around the same % when it happened.
Any thoughts????

Evervolv JB test build - No radio

I may end up making a proper thread in the dev forum but for now, I'm lazy and I'll just mention it here. This is something to mess around with and hopefully help with jellybean progress. Here's my tweet about it or keep reading for the same info.
[Tbolt] Evervolv testing-2013.07.02 Build
Overview:
* JB 4.2.2 w/ our msm7x30-3.0 kernel
* NO radio/data but good to go on wifi
* camera and many other things are working also
* sweep2wake support: enabled in settings -> evervolv -> advanced -> touchscreen
* plenty left to work on and fix but a good start
Please do not use our bug tracker to report bugs for this build
* can let me know on twitter or discuss in the forum thread if I've opened one
* if you want to contribute to Evervolv, upload commits to our gerrit review (we won't see github pull requests)
Click to expand...
Click to collapse
Download build: here
md5sum: 7a050f382d8d0bad2ffcc2c3df0857f1
If you want Gapps, you can just use the latest 4.2.2 ones(20130301) on goo: here

Unknown baseband in about phone and no network selection at all in network settings.
Sent from my ADR6400L using Tapatalk 2

Sorry if I caused any confusion or wasn't clear but yeah, there is definitely no radio action in this build. I'm not particularly familiar with the RIL stuff and wasn't involved in getting it going for ICS. I'm sure it will get worked out sooner or later with jblack, liquid, santod, and others working on it. That's not to say I won't continue to mess around with it myself but I wouldn't put any money on me making a breakthrough
The purpose of this build was two-fold...to give people something new to play with if they wanted and also just to let the community know about it as another source to draw from and collaborate with.

It's cool. They are working on it together to try fixing data. Your build helped them with some of the other fixes that they needed which was a good thing. Now that a lot of that is out of they way they can focus on the ril. I also found that I can't transfer files over usb. Pretty much everything else works except for what you listed.
Sent from my ADR6400L using Tapatalk 2

Been running this for a couple days now. Really nice. No major problems, except one instance of the phone failing to properly sense touch and slowing to a crawl. A reboot fixed that. Thank you so much for contributing to the cause! It is much appreciated!
Sent from my Amazon Kindle Fire using Tapatalk 4 Beta

It doesn't have the app store and if I install it manuals it won't open
Sent from my ThunderBolt using xda app-developers app

mahmood2331 said:
It doesn't have the app store and if I install it manuals it won't open
Sent from my ThunderBolt using xda app-developers app
Click to expand...
Click to collapse
Did you install Gapps linked in the OP?

This ROM is the best it does everything i need it to. Best ROM ever!!!
Sent from my ADR6400L using xda app-developers app

mahmood2331 said:
This ROM is the best it does everything i need it to. Best ROM ever!!!
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
Edit: disregard

This is a ROM lol. Jb WiFi only
Sent from my ADR6400L using Tapatalk 2

disconnecktie said:
This is a ROM lol. Jb WiFi only
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Lmao. I see that now in the OP. thanks, stupid of the day for me.

quickdraw86 said:
Lmao. I see that now in the OP. thanks, stupid of the day for me.
Click to expand...
Click to collapse
Happens to the best of us lol
Sent from my ADR6400L using Tapatalk 2

This rom worked great for 2 days but now my thunderbolt is bricked. Won't turn on with battery in or out with usb connected. The light inside the grill won't light up either to notify it is charging. All i did was I left it on the charger. It had been doing this before where it would just randomly be off and i wouldn't be able to turn it on but if i took out the battery and tried again it would boot. I had problems with a cm 10.1 build i found searching google where i would get a blue screen and it would crash at random. But I wiped that rom with everything and flashed this to see if this was more stable then that. Don't know why or what caused this. I'd be careful with running this build though.

Ammika13 said:
This rom worked great for 2 days but now my thunderbolt is bricked. Won't turn on with battery in or out with usb connected. The light inside the grill won't light up either to notify it is charging. All i did was I left it on the charger. It had been doing this before where it would just randomly be off and i wouldn't be able to turn it on but if i took out the battery and tried again it would boot. I had problems with a cm 10.1 build i found searching google where i would get a blue screen and it would crash at random. But I wiped that rom with everything and flashed this to see if this was more stable then that. Don't know why or what caused this. I'd be careful with running this build though.
Click to expand...
Click to collapse
Your issue isn't due to this rom. I can assure you of that.
You even stated you were having issues with your device powering on prior to running this,
so why you would claim it to be this rom, is unknown to me.
If you flashed the only CM10.1 build for the Bolt right now, from Jblack and got a blue screen, it was from not having the proper ICS radios installed.
If you are going to run any roms using the Official ICS blobs, then you need to be on the official ICS radios or you will get that blue screen you mentioned.
Sounds like you should be more careful about what you flash and make sure you have the necessary radios prior to flashing a rom.
Also sounds like your device has other issues if it won't power on. Maybe it's your battery.
All I can say for sure, is it isn't due to this rom. This I know for sure.
Just wanted to make that clear as your post seemed very misleading to me.

santod040 said:
Your issue isn't due to this rom. I can assure you of that.
You even stated you were having issues with your device powering on prior to running this,
so why you would claim it to be this rom, is unknown to me.
If you flashed the only CM10.1 build for the Bolt right now, from Jblack and got a blue screen, it was from not having the proper ICS radios installed.
If you are going to run any roms using the Official ICS blobs, then you need to be on the official ICS radios or you will get that blue screen you mentioned.
Sounds like you should be more careful about what you flash and make sure you have the necessary radios prior to flashing a rom.
Also sounds like your device has other issues if it won't power on. Maybe it's your battery.
All I can say for sure, is it isn't due to this rom. This I know for sure.
Just wanted to make that clear as your post seemed very misleading to me.
Click to expand...
Click to collapse
okay then. good rom anyway. i didn't really care about it too much.

Perfect!
This rom will make the perfect credit card machine in my store since I use this as a tablet to use the PayPal swipe Thanks!

[Q] Various potential hardware/sensor related issues

Hey guys,
I have a VZW HTC One M8 with the following version details:
Cyanogenmod 11-20141112-snapshot-m12-m8
Unlocked bootloader
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0222
OPENDSP-V26.2.2-00538-M8974.0106
OS-
eMMC-boot
This phone came to me with a clean Cyanogenmod install on it. I wiped it anyway to be sure. I have an S3 that I've been running CM11 on up until I got this phone so I'm no stranger to Cyanogenmod.
My issues appear to be randomly occurring and I cannot seem to pin down what is causing it or when it actually happens. Here are the various issues I'm seeing:
1. Screen fails to reorient when being turn - this happens system wide, even the home screen fails to reorient. Perhaps a problem reading the gyro sensor?
2. Lux values get stuck, usually at 45. Ambient light sensor?
3. Double tap to wake stops working - need to use the sleep/wake button to turn the screen on. Can still double tap the status bar to turn the screen off
4. Incorrect battery reporting - The battery appears to drain normally and at a consistent pace, however if the phone is shutoff or rebooted I will sometime see a huge drop when the phone boots back up.
I have a screenshot from the phone this afternoon but cannot post it (attachments fail to upload on this forum). I can probably PM it to you though.
I noticed if the phone gets to 5%, sometimes ~15% it will just turn off because the battery has actually died but the OS thinks differently.
The first 3 issues fix themselves after reboot.
Oh and I've noticed that the profiles feature doesn't work properly. If the ring mode is set to vibrate on the work profile, it will stay in vibrate even when it switches back to the default profile which is set to ring mode. The phone will not let me set custom notification sounds with Profiles enabled either. Example: Hangouts uses the notification sound as set by the default in Settings. I cannot change this. I can turn off Profiles and I can change the notification tone on Hangouts all day long.
Not quite sure what I should be looking at here so any guidance or suggestions would be much appreciated. Let me know if you need any more details.

You answered the question yourself in the second sentence of your post.

beaups said:
You answered the question yourself in the second sentence of your post.
Click to expand...
Click to collapse
beaups,
Was really hoping for a more descript answer. Can you please elaborate?

cstokes86 said:
beaups,
Was really hoping for a more descript answer. Can you please elaborate?
Click to expand...
Click to collapse
You are running cm. Probably known cm bugs or possibly you need different firmware. Either way, there's no such thing as a hardware problem until it exists on stock software.

beaups said:
You are running cm. Probably known cm bugs or possibly you need different firmware. Either way, there's no such thing as a hardware problem until it exists on stock software.
Click to expand...
Click to collapse
I forgot to mention in my original post:
I already searched around for the various issues I'm having but was not able to find any mentioning of them in any known issues lists. Was hoping to see if any devs on here had suggestions on things to try.

cstokes86 said:
I forgot to mention in my original post:
I already searched around for the various issues I'm having but was not able to find any mentioning of them in any known issues lists. Was hoping to see if any devs on here had suggestions on things to try.
Click to expand...
Click to collapse
Search better. This took me less than 5 minutes:
http://forum.xda-developers.com/showpost.php?p=56813202&postcount=3167
http://forum.xda-developers.com/showpost.php?p=56733227&postcount=3140
http://forum.xda-developers.com/showpost.php?p=56719654&postcount=3130
and many, many more all in that thread, which happens to be the CM thread for your phone.
Oh, and welcome to XDA

beaups said:
Search better. This took me less than 5 minutes:
http://forum.xda-developers.com/showpost.php?p=56813202&postcount=3167
http://forum.xda-developers.com/showpost.php?p=56733227&postcount=3140
http://forum.xda-developers.com/showpost.php?p=56719654&postcount=3130
and many, many more all in that thread, which happens to be the CM thread for your phone.
Oh, and welcome to XDA
Click to expand...
Click to collapse
Thanks for those links. I was looking in the official known problem lists for Cynogenmod for these issues to see if they actually confirmed anything. I will look at possibly installing a nightly and testing with that, but I'm a bit reluctant to go that route since this is my daily driver.

cstokes86 said:
Thanks for those links. I was looking in the official known problem lists for Cynogenmod for these issues to see if they actually confirmed anything. I will look at possibly installing a nightly and testing with that, but I'm a bit reluctant to go that route since this is my daily driver.
Click to expand...
Click to collapse
If you are looking for stability, flash a sense based ROM. Its just the way it is.

beaups said:
If you are looking for stability, flash a sense based ROM. Its just the way it is.
Click to expand...
Click to collapse
^ Can't disagree with that, but I loathe the bloatware and manufacturer UI and skins they put on their devices, not to mention the freedom and functionality I lose out on by going back to a more or less stock experience. If I want stock non-CM, I'll just flash 5.0 GPE and see how that goes, but I've already tested with that as well and missed the functionality that CM brings. :/
Win/Lose.
Do you think the firmware (not the ROM/OS) is highly out of date and should be updated by now?

cstokes86 said:
^ Can't disagree with that, but I loathe the bloatware and manufacturer UI and skins they put on their devices, not to mention the freedom and functionality I lose out on by going back to a more or less stock experience. If I want stock non-CM, I'll just flash 5.0 GPE and see how that goes, but I've already tested with that as well and missed the functionality that CM brings. :/
Win/Lose.
Do you think the firmware (not the ROM/OS) is highly out of date and should be updated by now?
Click to expand...
Click to collapse
Yes you should update that firmware. There's an emmc controller firmware update amongst other things included you should have. Have you tried gpe or stock with some of the xposed modules now available?