Apex 1.3 hardware button won't light up

roberte1342

Well-known member
Aug 14, 2010
359
11
0
I've been running FlyX for a couple months and have been awaiting a ROM with the awaited fixes from moto.
I have tried Apex 1.3 on two X's and everything works fine except the HW buttons do not light up.
My X still has the boot loader from 2.1, the other is stock ota 2.2.

Is there some setting I am overlooking?

btw also tried Apex 1.0 with same result
[tapatalk - droidx]
 
Sounds like you didn't go through the correct process to get to 1.3. Tell us what u did, and your current bootloader version (30.xx) I also ran FlyX untill apex 1.2, my hardware backlight is fine.
 
Wow never had a issue on any apex. No setting for that to change. Not really sure what could cause it.

Sent from my DROIDX using Tapatalk
 
bootloader is 30.01
process as follows:
received replacement x with stock 2.1
rooted
installed clockworkmod ROM Manager and bootstrapper.
Flashed recovery from Rom Manager
Made nandroid backup of stock 2.1
Downloaded FlyX and installed with wipe option in Rom manager
2 months later made nandroid backup and downloaded and installed Apex 1.3 with wipe option.
no hw button lights.

Other x has bootloader 30.04

[tapatalk - droidx]
 
I think I'll sbf then ota and see what happens. I was hoping it was a simple fix.


[tapatalk - droidx]
 
That was it. Thanks!

Running great, even on the old 30.01 bootloader.

Sent from my DROIDX using Tapatalk
 
That's actually a hardware bug with the Motorola droid x and droid 2.
happens on my DX, my wifes DX and my father in laws D2
not sure why it was never fixed in the d2..
either way it's not anyone's rom doing it.
only way to work around it is to just press the home button when you need the back lights.
 
Guess I just never noticed it before, I probably did other factory resets and ROMs in the daytime and by nighttime I probably had already woken the phone with the home key that day. When I first installed the ROM I was looking for anything that might be a problem before investing the next several hours setting things up on 2 phones. Since I was doing this at night on my bed it was really obvious there was a problem. Just wasn't sure what was causing it. Thanks for the info.
 
np.. I would imagine motorola knows about it.. not sure why it's never been fixed.
 

Trending Posts

Forum statistics

Threads
956,740
Messages
6,969,710
Members
3,163,603
Latest member
blåhaj