Hi all!
I used this init.d script on my Note 3 to make the LED blink whenever there was storage and WiFi activity:
Code:
#!/system/bin/sh
# ShadowLED by CeK! @ PreCog.me / 2014.
# Makes leds blink depending on activity (Wifi, ExtSD, IntSD)
echo mmc2 > /sys/class/leds/led_r:rgb_red/trigger;
echo mmc1 > /sys/class/leds/led_g:rgb_green/trigger;
echo mmc0 > /sys/class/leds/led_b:rgb_blue/trigger;
I kinda sorta got it working on the S7e, but it only blinks white during boot, then it blinks no more. What is the correct syntax?
Thanks!
Of course, all credit goes to CeK! @ PreCog.me. It's his idea and original code.
Related
Guys - this minor release is in response to this thread:.
http://forum.xda-developers.com/showthread.php?t=281581
I've written a small app to disable the LED driver on most HTC devices, ie, battery charging leds, bluetooth, notification led, wifi led(?); this will remain effective until you soft reset.
There are no installers etc for now, it's a work in progress, but I'll put it out for the time being.
Note - by disabling the LED driver, the PDA won't be able to disable any currently activate leds, so eg if you're charging up (orange led active), and then run VJImpoto, the orange led will stay on until you soft reset whether you're charging or not.
So run it when you've got no LEDs on, and they'll stay off.
However: this is alpha, because I noticed that the "heartbeat" flash of the phone radio (green flash of led every few seconds) continues despite the LED driver being disabled: clearly that action is activated elsewhere on the system, so it'll need further investigation. However, this app merely disables AllLedMgr, so any flaws with that strategy carry here too.
Command line options:
-showinfo shows info on usage/donations
-debug shows feedback on whether it worked.
-killall killall will first attempt to switch off any active leds (except radio LED), so as discussed above, running "VJImpoto -killall" will first switch off the orange led, and then disable AllLEDMgr. However, this has the peculiar side effect of making the heartbeat flash now flash on the left green led on the Hermes. I recommend using -killall.
Please give feedback on if it worked for you. I'll make a cab later, .exe only for now.
VJImpoto
V
hi vijay, would it be possible for you to create one for smartphones? thanks
Could you send me over a registry dump? I haven't worked on Smartphones for many years (I had the original SPV - a pioneer!) Don't know if you can point me towards a rom dump as well, but I'll certainly look into it if you can.
V
i exported my T-Mobile Registry using PHM Reg Editor and here it is:
http://filexoom.com/files/2006/11/7/42820/SDA Registry.rar
for ROMs i dont know how to dump mine
Hello,
I've been running WIUI on Defy for a number of months now, but I've not notched up the required number of posts on here to post to the development WIUI thread. It seems that people in this situation need to discuss any issues outside of the Dev area. I've had a search through the site and not found a new member WIUI thread. This seemed to be the most relevant place, so I'm starting a thread here. Please let me know if there's a better place. If this is OK, please draw this thread to the attention of Wajk and the other guys on the Dev thread.
Anyway here's my issue:
I've just upgraded from 1.9.9 to 2.2.3. The behaviour of the LED seems to have changed. It now shows green when it it charging. I read there was a "battery light" patch to do this. I assume it has now become part of the main image. I'd like to return to the old behaviour where the LED flashed when an SMS is received. I keep my phone on silent during the day and this is the way I notice I have received a message. Is there a way to do this? I've searched the settings for "LED", etc, and not found any option to change.
Thanks,
Rhys
I found this.
Thanks for the tip to check that build.prop file.
I found this in there:
# LED charging indicator mode
# off = keep LED off during charging
# white = white LED for 'charging', green LED for 'charged'
# rgb = mixed yellowish LED for 'charging', green LED for 'charged'
persist.sys.charge_led=rgb
Setting it to off disabled the charging LED . I tried adding ro.battery_light=false, but that didn't work for me.
I'm still not getting a flashing LED on SMS messages. Do I need to download a suitable app to get that working again?
Quick question:
I'm on CM7.2 Quarx (i've been playing around with different nightlies since flashing cm7.1 stable) and want to try wiui.
Can i just flash the zip over my current cm7 the same way in recovery? or do i need a fresh install (clear system data, etc.)
thanks,
I'm on wiui 3.1.27, and I have some issues, like rparrygbr
I tried to post a private message to Wajk on a hungarian forum, but I haven't got any replay for it.
So:
1. Play store will start "stop unexpectedly" when the "Applications" page (note the message that something is updated when pressing on, it flies in the play).
Anno (probably the 2.9.x version) FR is made to recover because the cache (Dalvik too) urinates, Play wipe data did not help.
2. Wifi Tether randomly throws himself at intervals, when I turn on 'error' on down there - this time a cache (Dalvik too) excretion solve the problem, at least for the next connection.
3. WiFi random intervals, you can not connect, turn it on, and then it immediately switches - this place used to be a reboot
4. repeatedly used to something being that wifi - 3G switching, if you lose the wifi signal and not turn it off, you can not form a connection to the mobile web, usually have to restart the phone (if you look at the mobile network settings, such as not saving the selected value, for example. "3G preferred") - there is no indication in one of the spots, even though I set.
Many thanks for help me
I've installed the 3.1.27 (GB Stable) last night and the first issue I've encountered was related to WiFi.
Every time I connect to WiFi with me cellphone, it instanty drops the connection with my router, making any other devices (notebooks, tablets etc) don't have access to internet too. So I have to reboot my router (TL-WR441ND) to have access again, but once I connect my phone... it's all the same thing over and over again.
Had the same problem with MS2Ginger 5.0a, so I switched to MIUI 3.1.27 hoping that won't happen.
There is any solution for it?
EDIT 2: Repushed the updated settings.db file and all seemed to be working now. I had reflashed the CM rom first (but I didn't wipe data), I'm not sure if that fixed a conflict somewhere?
Either way, it's working with data now. If anyone knows what might have been going on, I'm all ears and would love to find out, but I'll keep looking around and see what might have been up
##########
Hi all,
I smashed my screen (and digitiser), and had just turned off mobile data before I dropped my phone. I know with a combo of DeskSMS, Pebble and Airdroid etc I will be able to use most of my phone until I can get it fixed. I've had lots of issues getting the sqlite3 binary on my phone, so I decided to pull my settings.db and edit it.
adb pull /data/data/com.android.providers.settings/databases/settings.db
I then used a sqlite3 editor to edit the global table and changed the mobile_data value from "0" to "1". I pushed it back on, rebooted and mobile data was on, but all my other settings appeared to have reset to default. Bluetooth state, brightness, volume etc. This was fine for using DeskSMS, but it killed my Pebble. It's also not the behaviour I would have expected.
What did I do wrong, and/or why was the rest of the DB values ignored, or changed when I pushed them back to the phone? I'm using CM 10.2, 16GB N4 and was using adb from twrp recovery (I hadn't authorised my laptop for adb before I broke the digitser).
Thanks
EDIT: On second thoughts, I think the fact the mobile data is working is due to it actually being on as a default. This would lead me to believe that by changing mobile data to "1" I am actually corrupting the settings.db and it's loading defaults and recreating it on boot. Is there any CM documentation on the possible states that mobile_data or "preferred_network_mode" can be? I can't seem to find that field in the aosp docs.
I turned off pulse notification light in nougat version
after the pie update, pulse notification light option is gone
how do i turn on the option?
usually is better do a reset of the phone when you upgrade to a new major version, to avoid this little bugs and issues.
Yogesh680 said:
I turned off pulse notification light in nougat version
after the pie update, pulse notification light option is gone
how do i turn on the option?
Click to expand...
Click to collapse
Try this with ADB:
Code:
adb shell settings get system notification_light_pulse
Should output "1". If there is "0", use this command:
Code:
adb shell settings put system notification_light_pulse 1
Let us know if it helped
I get a returned result of '1' but I get no LED flashing.
July Pie stock. It stopped working in April or May update. Any ideas?
Maybe try turning it off and on again (put 0 and then put 1)..? Mine notification LED works fine, so it shouldn't be related to the update. Is LED working otherwise? When charging the phone for example.
I tried changing from 1 to 0 and back to 1 again. No change. I do not have the LED when charging. Although a previous update stopped all LED function in the past, the functions came back after another update. I figured this was just the case of the LED being stopped 100% again by software. Maybe not.
When you reboot into fastboot mode and connect to the PC, is the charging LED working? If not, I'd say it's a HW issue.
Alternatively you can try this command in terminal emulator if you have root:
echo 200 > /sys/class/leds/red/brightness
It will turn the LED on. Echo 0 will turn it off again.
Hi, I have an LG V35 AWM on Android 10 and while investigating a higher than expected battery drain when idle, I found the following errors spamming logcat once AOD kicks in:
E HWComposer: prepare: presentOrValidate failed for display 19260222137657473: BadDisplay (2)
E SurfaceFlinger: prepareFrame failed for DisplayDevice{19260222137657473, primary, "SW43402 cmd m"}: -2147483648 (Unknown error -2147483648)
E HWComposer: presentAndGetReleaseFences: present failed for display 19260222137657473: NotValidated (7)
I noticed these while in an adb shell, using "logcat *:W" and they repeat in bursts, at varying intervals (every 1/2 - 2 seconds).
As soon as i wake the screen, they stop and if I disable AOD I don't see them at all when the screen times out.
With AOD on, I'm seeing 1-2% battery drain per hour and ~.5% per hour with it disabled.
Has anyone else seen these or have any idea why this is occurring?
I didn't have the phone long enough on Oreo or Pie to notice the behavior, so not sure if this is unique to Android 10 or not...
Thanks
mjm_xd said:
Hi, I have an LG V35 AWM on Android 10 and while investigating a higher than expected battery drain when idle, I found the following errors spamming logcat once AOD kicks in:
E HWComposer: prepare: presentOrValidate failed for display 19260222137657473: BadDisplay (2)
E SurfaceFlinger: prepareFrame failed for DisplayDevice{19260222137657473, primary, "SW43402 cmd m"}: -2147483648 (Unknown error -2147483648)
E HWComposer: presentAndGetReleaseFences: present failed for display 19260222137657473: NotValidated (7)
I noticed these while in an adb shell, using "logcat *:W" and they repeat in bursts, at varying intervals (every 1/2 - 2 seconds).
As soon as i wake the screen, they stop and if I disable AOD I don't see them at all when the screen times out.
With AOD on, I'm seeing 1-2% battery drain per hour and ~.5% per hour with it disabled.
Has anyone else seen these or have any idea why this is occurring?
I didn't have the phone long enough on Oreo or Pie to notice the behavior, so not sure if this is unique to Android 10 or not...
Thanks
Click to expand...
Click to collapse
Do you have a screen protector or a case on? It might be interfering with one of the sensors. Try booting in safe mode and see if this continues. Also, did you flash the Korean Android 10 or updated via AT&T?
Hi, no screen protector and removing the case doesn't change the behavior. The only upgrades performed where OTA (AT&T).
I also checked in safe mode, same thing...
I went into service mode and performed all the screen & touch tests, everything works as expected.
Note that these messages only appear once AOD kicks in. With AOD disabled, I do not see these messages with the screen on or once it times out.
I also don't see any kind of 'ghost' touch events (watched with logcat 2>&1 | grep SurfaceFlinger). Also tested with "logcat 2>&1 | grep Touch" and the only touch events are when I touch the screen.
I also started looking at the volume of logcat messages (not just errors/warnings) and it is crazy busy, so maybe my concern about these messages flooding the phone are unwarranted as these numbers seem insignificant.
Thanks