• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Quattrimus JB (CM10.1, AOKP42)

bones420la said:
Tdm. I'm loving your progress. But can I ask for a small favor? Some way to disable the key lights. Maybe a option in the next build or a flashable zip or something?
Click to expand...

The button backlight control file is /sys/class/leds/button-backlight/brightness

If you want to disable it, the easiest way is probably to revoke permissions to modify that file.

By default, init.rc sets owner system, group system, mode 644.

You could create an rc-script that sets it owner root, group root, mode 000.

To do this, create a script with the following contents. Be sure to use Unix line endings, not DOS...

Code: 
#!/system/bin/sh
# Disable permissions for backlight buttons
f="/sys/class/leds/button-backlight/brightness"
chown root.root "$f"
chmod 000 "$f"

Now put that script in /system/etc/init.d or /data/local/userinit.d (either one, depending on how comfortable you are writing to /system and/or whether you want it to stay in place on a dirty flash). Make sure the script itself is executable (mode 755). Reboot and viola, backlight buttons should never turn on.
 
tdm said:
The button backlight control file is /sys/class/leds/button-backlight/brightness

If you want to disable it, the easiest way is probably to revoke permissions to modify that file.

By default, init.rc sets owner system, group system, mode 644.

You could create an rc-script that sets it owner root, group root, mode 000.

To do this, create a script with the following contents. Be sure to use Unix line endings, not DOS...

Code: 
#!/system/bin/sh
# Disable permissions for backlight buttons
f="/sys/class/leds/button-backlight/brightness"
chown root.root "$f"
chmod 000 "$f"
Now put that script in /system/etc/init.d or /data/local/userinit.d (either one, depending on how comfortable you are writing to /system and/or whether you want it to stay in place on a dirty flash). Make sure the script itself is executable (mode 755). Reboot and viola, backlight buttons should never turn on.
Click to expand...

Hey TDM....that brightness file when you open it to see its properties...or what that file consists off, it has the number 255. Hex code RGB for white is 255 255 255.....could I modify that file to something different and maybe have it change the color of those LEDs?

I know it is a stretch but that would be cool

Rich
 
sosaudio1 said:
Hey TDM....that brightness file when you open it to see its properties...or what that file consists off, it has the number 255. Hex code RGB for white is 255 255 255.....could I modify that file to something different and maybe have it change the color of those LEDs?

I know it is a stretch but that would be cool

Rich
Click to expand...


Nevermind answered my own question regarding hex and RGB when I looked up the RGB conversion from hex of 0000ff and got 0 0 255.....DOH

But to sidestep that issue....could there be a hack to change the LEDs or are they fixed white?
 
sosaudio1 said:
Nevermind answered my own question regarding hex and RGB when I looked up the RGB conversion from hex of 0000ff and got 0 0 255.....DOH

But to sidestep that issue....could there be a hack to change the LEDs or are they fixed white?
Click to expand...

I'm not that familiar with the hardware but they seem fixed white.
 
The aokp team merged 4.2.2 and it's building. Unfortunately the screen still doesn't turn off on i_vzw but does on i_atnt. Conversely, the BT MAC doesn't get set correctly on i_atnt but does on i_vzw. I'll probably start investigating both of those in earnest on Monday.
 
sosaudio1 said:
Hey TDM....you don't suppose there is an app in the app store that might "force" the issue?
Click to expand...


Ummmmmm hey guys guess what!!!!!

Did you know that the lockscreen has screens too like the homescreen?

UGH....so yeah...I figured out how to get the lockscreen I always wanted. You slide the lockscreen to the left and hit the add button....I figured this out after making a backup of cLock and uninstalling it to install the Chronus3 apk.

Geeeez:thumbup:
 
sosaudio1 said:
Ummmmmm hey guys guess what!!!!!

Did you know that the lockscreen has screens too like the homescreen?

UGH....so yeah...I figured out how to get the lockscreen I always wanted. You slide the lockscreen to the left and hit the add button....I figured this out after making a backup of cLock and uninstalling it to install the Chronus3 apk.

Geeeez:thumbup:
Click to expand...


a little late there.

that was one of the main features of 4.2
 
idk if it's just me but the signal drops pretty frequently. even the battery menu shows blank spikes in cell signal. wanted to check.

otherwise, this is great! love the rom and it's smooth and lag free. thanks a bunch tdm - you're the man!
 
  • Like
Reactions: tdm
The kids love the daydream with camera pics. But it seriously slows charging down, and gets the phone quite warm for extended periods (this is bad for battery longevity).
 
think this is a bug with the camera app. the app is only meant for a 4:3 screen so images (while taking them) appear stretched or squeezed depending on how you hold your camera. your gf may be shocked to see herself bigger when she checks the gallery later :p
 
aragorn9 said:
idk if it's just me but the signal drops pretty frequently. even the battery menu shows blank spikes in cell signal. wanted to check.

otherwise, this is great! love the rom and it's smooth and lag free. thanks a bunch tdm - you're the man!
Click to expand...

Agreed.my signal on cm10.1 is a lot weaker than aokp.

uploadfromtaptalk1360996708778.jpg
 
Haven't checked this for myself yet... But CyanogenMod put up a Facebook post about it today. Apparently 4.2.2 will prompt you to accept a security key when using ADB through USB now. The post states that they will not introduce functionality to bypass this security feature and that you need to be using ADB from the latest SDK.

Not sure what this would mean for getting logcats and such during boot though.

The post also referenced the #itsafeaturenotabug hashtag if anyone's interested.

Sent from my VS920 4G using Tapatalk 2
 
My signal was fine for the little time that I had 10.1 installed... But to be fair... I can throw rocks at the cell tower behind my house if I wanted to, so I wouldn't expect much of anything to affect my signal.

Sent from my VS920 4G using Tapatalk 2
 
Yoinx said:
Haven't checked this for myself yet... But CyanogenMod put up a Facebook post about it today. Apparently 4.2.2 will prompt you to accept a security key when using ADB through USB now. The post states that they will not introduce functionality to bypass this security feature and that you need to be using ADB from the latest SDK.

Not sure what this would mean for getting logcats and such during boot though.

The post also referenced the #itsafeaturenotabug hashtag if anyone's interested.

Sent from my VS920 4G using Tapatalk 2
Click to expand...

Yeah it's a new feature. An AC post talked about it...

Semi-pro tip: With Android 4.2.2 here, your Android SDK might need updating | Android Central

Note we don't have this in beta3, which was confusing to me. But apparently we just missed the commit. It's in today's changelog:


https://github.com/CyanogenMod/android_vendor_cm/commit/59df363c6097eb4c8b53c1b952d7384a567bafac
 
Hey d2a, can we get some more tags on the issue tracker?

Version-AOKP42
Version-CM10.1
Kernel

Also I removed the tag Version-CM_AOKP from all the issues since it's ambiguous now. I prefer the individual tags anyway. So it can be nuked I guess.

Thanks!
 
Question for anyone:

I need to know what sort of issue everyone is having with GPS. I ask because right now, I'm working on a fix and I get a lock every 30 seconds down to 20ft accuracy in Google maps. It still reports as GPS being off, but it gets a lock. Is anyone else getting a lock like that, or am I on the correct path?
 
Neph81 said:
Question for anyone:

I need to know what sort of issue everyone is having with GPS. I ask because right now, I'm working on a fix and I get a lock every 30 seconds down to 20ft accuracy in Google maps. It still reports as GPS being off, but it gets a lock. Is anyone else getting a lock like that, or am I on the correct path?
Click to expand...

I think you are on the right track because I can't get a lock and it shows in settings that my gps is turned on
 
Neph81 said:
Question for anyone:

I need to know what sort of issue everyone is having with GPS. I ask because right now, I'm working on a fix and I get a lock every 30 seconds down to 20ft accuracy in Google maps. It still reports as GPS being off, but it gets a lock. Is anyone else getting a lock like that, or am I on the correct path?
Click to expand...

When I flash from any rom with active gps, including stock (turned on before I flash it), I open gps test and it says gps is off, even though it shows on in settings. If I toggle gps in settings, no change. The rom doesn't seem to 'see' that the hardware is actually on. No lock, either... Just lock based on cell/wifi.
 
You must log in or register to reply here.
Back
Top Bottom