[APP] LG 2X/Black Notifications

Search This thread

xigzil

Member
Apr 29, 2011
15
28
Hi,
I do not speak English, so I am sorry for my bad English.
I have a P920 and I installed this app, but it does not run. I make a missed call to myself, but the leds do not light.

Thank you very much!

Your English is fine :)
Have you rooted your phone ? You could check out the thread in the Optimus 3D-subforum, there is currently another developer working with the app for the P920 and he might be able to help you out.

Hi,

This app is working on gr 4 but each time I reboot, I've a message that says ' superuser permissions refused for LG 2X./Black .....'

Sent from my LG-P990

That sounds strange, it seems the Superuser-app might be configure wrong for the app. If you open the Superuser-app then you can perhaps change so it wont refuse permissions for the app.

I was using this great app with LG Optimus Black stock roms like v10b/c/e, but i can't do it with CM7 nightlies right now. Everytime I open app it says "App detected it has no read or write access to a required file, do you wish to fix this?" I click OK, but still doesn't work.

This message appears everytime I open the app. What could be the problem here?

Thanks in advance.

What happens when you click OK ? Does it say anything or does it seem to work normally ? Did you ever get a question about allowing Superuser-permissions ?
CM7 have their own notification built-in so there might be a conflict, you could try and disable it.

Love the app, just what my G2x needs. Your hard work and dedication are much appreciated.
I do, however, have one problem maybe you or the other fine members of this forum can help me with.
I have a notification ringtone set to go off every 5 minutes after a missed notification. Works great, I love it, wish I had it earlier. However, in the morning it goes off because of the battery 100% notification. Is there a fix, workaround, or setting that I'm missing? (I've searched quite a bit but only see discussions with the SGS2) As long as the circuitry shuts down, I don't care about that notification.

I never experienced this. Are you using a third party-app that puts a notification in the notification bar when the battery is fully charged ? If so you might have to exclude that activity (Notifications -> Exclude activities). If you're uncertain which activity it is you can log notifications in the Advanced-menu and then check the log when it happened again.

@xigzil

How to fully disable the accelerator/g-sensor for power saving ?

why do you have this build in?

without this, i would say its a wonderful valueable app ,with it have to deinstall the app ):-

thanks

The accelerometer can't be disabled. It is used by the app to determine if the phone is being used. For example, you're writing an e-mail on your phone and gets an SMS. At this point the app enables the accelerometer to detect user activity, if it detects activity (by movement of the phone) it disables the accelerometer and doesn't do anything more. If the accelerometer were to be disabled it would start the notification as soon as the screen turns off since it doesn't know if the phone has been used at any point after the notification has been received, which would be quite bothersome.
It might not be the best solution but I haven't found anything else and it works pretty well.

Normally this shouldn't use a lot of battery at all though, since when it is started it is usually only enabled for a couple of seconds. Does it use an unusual amount of battery for you ?
 

thehero21

Member
Dec 6, 2009
33
3
@home
accelerometer usage

...
Normally this shouldn't use a lot of battery at all though, since when it is started it is usually only enabled for a couple of seconds. Does it use an unusual amount of battery for you ?

thx for your answer.

yes, in my app-testings (around 10 minutes, with a reboot) it used 1m30s cpu time ?!?
strange, do you thinking too?
for me it was too much.

any workarounds?

... writing an e-mail on your phone and gets an SMS. At this point the app enables the accelerometer ...

why, the app knows -
if the phone is in suspend mode (do led blinking job)
the phone is on (no led blinking job)

no need for extra accelerometer usage, or whats my fault ?

greets
 
Last edited:

Scumbag Inc.

Senior Member
May 21, 2010
145
20
Austin, TX
I never experienced this. Are you using a third party-app that puts a notification in the notification bar when the battery is fully charged ? If so you might have to exclude that activity (Notifications -> Exclude activities). If you're uncertain which activity it is you can log notifications in the Advanced-menu and then check the log when it happened again.
Right, so I've started logging a couple of days ago. (BTW thank you for that feature.) So far I have not received any anomalies but I will let you know what I do find.
 

xigzil

Member
Apr 29, 2011
15
28
thx for your answer.

yes, in my app-testings (around 10 minutes, with a reboot) it used 1m30s cpu time ?!?
strange, do you thinking too?
for me it was too much.

any workarounds?



why, the app knows -
if the phone is in suspend mode (do led blinking job)
the phone is on (no led blinking job)

no need for extra accelerometer usage, or whats my fault ?

greets

Hmm, how did you perform this test ? Was it during normal usage or after you received a notification ? What did you use to find out the cpu-time value ?
If you listen to all activities there might be some app that frequently updates the notification bar and causes the accelerometer to start unnecessarily. Try enabling the notification log in the Advanced-settings and see what it says after some time.

It is possible to not use the accelerometer, but I can give two examples where it is useful.
For example, lets say you have a screen timeout for one minute and have the phone on silence. You simply leave it on your desk and walk away from it for a while. If you receive a message before the display turns off, it wouldn't be notified since we don't know if the phone is used or not. The accelerometer tells us that the phone isn't moving so the notification will start when the screen turns off, and don't start if you pick up the phone before the screen turns off.
Another example would be if you receive a message for an app that for some reason turns on the screen (like SMS did in 2.2). When this happens the notification event may be received after the screen has turned on. Fortunately we can find out if we're in the lock screen and can use that. Unfortunately though not all third party lock screen sets this value correctly and we don't know again if the phone is used or not. The accelerometer would help out again.

So in short the accelerometer helps, but it shouldn't be a battery drainer, so it might be some configuration issue. I'm happy to help you out and try to find out the problems.

If you really think it is a big issue though I could add a setting to disable the accelerometer completely.

Right, so I've started logging a couple of days ago. (BTW thank you for that feature.) So far I have not received any anomalies but I will let you know what I do find.

I hope you find out what causes it !
 

thehero21

Member
Dec 6, 2009
33
3
@home
accelerometer unnecessarily?

Hmm, how did you perform this test ? Was it during ...

i'm thinking, i'll need to do more testings on this over a longer period of time.

the cpu-values(runtime) i got from CM7's nightly builtin akku consume status (in settings).

if needed, i make here a request to you for one appbuild without accelerometer support.


super your support here - thank you
 

73n5h1

Member
Jun 29, 2010
9
1
I have an LG G2X running CM7 and I've been having an issue.
I've changed the settings in the app so that the leds should be constant when I receive a notification, but they still continue to flash instead. I have tried uninstalling and reinstalling the app as well as clearing out the app's cache, but nothing has solved the problem. I even tried earlier versions with no luck. I wouldn't mind them flashing instead of staying constant, except that when I receive a notification at work, the leds will be flashing for a few hours before I can check them, and by that time, it has severely drained my battery.
 
  • Like
Reactions: misterpsych

misterpsych

Member
Dec 8, 2010
17
3
I have the same issue as "73n5h1." I am running MIUI and the flashing really drains my battery like 30% in over an hour... regardless if I program it to be on constant....

Also...

I am unstalling the app because of battery drain... after uninstalling and rebooting... the app is still working?? After a call or text the 4 keys still light up? I am using MIUI and I used a new (MIUI) rom and it still does it...? I restored back to original tmobie g2z stock gingerbread and it doesnt work but when I use MIUI it the LED notification still blinks?? What is wrong? Thanks!
 

xigzil

Member
Apr 29, 2011
15
28
i'm thinking, i'll need to do more testings on this over a longer period of time.

the cpu-values(runtime) i got from CM7's nightly builtin akku consume status (in settings).

if needed, i make here a request to you for one appbuild without accelerometer support.


super your support here - thank you

I hope you find out anything, just tell me and I'll help you out :)

I have an LG G2X running CM7 and I've been having an issue.
I've changed the settings in the app so that the leds should be constant when I receive a notification, but they still continue to flash instead. I have tried uninstalling and reinstalling the app as well as clearing out the app's cache, but nothing has solved the problem. I even tried earlier versions with no luck. I wouldn't mind them flashing instead of staying constant, except that when I receive a notification at work, the leds will be flashing for a few hours before I can check them, and by that time, it has severely drained my battery.

I have the same issue as "73n5h1." I am running MIUI and the flashing really drains my battery like 30% in over an hour... regardless if I program it to be on constant....

Also...

I am unstalling the app because of battery drain... after uninstalling and rebooting... the app is still working?? After a call or text the 4 keys still light up? I am using MIUI and I used a new (MIUI) rom and it still does it...? I restored back to original tmobie g2z stock gingerbread and it doesnt work but when I use MIUI it the LED notification still blinks?? What is wrong? Thanks!

Both CM7 and MIUI have their own built-in notification using the LEDs (I haven't tested them myself, but I'm quite certain they do). So using my app without disabling theirs first will make everything behave strangely. Since both their notification system and my app wants to use the LEDs it would most likely cause a larger battery drain than usual. So I suggest you disable the built-in notification in the ROM and use my app or the other way around.

So to answer your questions I think that for CM7 their notification system will override the setting in my app, causing the LEDs to flash, and for MIUI the LEDs will flash without my app because of their built-in notification system. And that the battery drainage is because both the ROM and my app is keeping the phone awake making changes to the LEDs.

Since I haven't tried these ROMs I don't know how to disable their notification system so unfortunately I can't help you with that.

I hope this explains the issues you're experiencing !
 

Scumbag Inc.

Senior Member
May 21, 2010
145
20
Austin, TX
So, after excluding a few suspicious activities and running it for a few days the problem seems to be fixed.
Advanced Task Killer, Weather Bug, and Android System.
 

Frank67

Senior Member
Apr 10, 2005
83
1
Cologne
Hello,

i use this app on my LG P920 with the latest
GB update from LG (rooted).
I use LED Notification only ..

Sometimes when i push the Powerbutton to
turn the Phone off,(EDIT: also if i leave it in lockscreen
and it turns off the screen after a few seconds) it leave the LEDs on till
i turn the phone on and off again.

I didint have this before i installed this app.
 
Last edited:

RedeemerSK

Member
Apr 5, 2011
49
2
Bratislava
'ello

Since moving from Modaco GR5 to Thanatos2X v5.1 EXT4 - Based on Official V20o (http://xdaforums.com/showthread.php?t=1334220) app works (signals events) only since the moment I launch its main activity (from app drawer) first time after phone start.

For example, charging signalling: looking at logcat, I can see O2XTouchLEDNotifications processing ACTION_SCREEN_OFF but nothing afterwards. After I launch the app (and immediatelly shut it down using back button), it works - ACTION_SCREEN_OFF is followed by "LED start". Any tips ?

EDIT:
During phone starting (the begining of the stack trace was nowhere to find):
02-10 20:43:54.167: W/System.err(1747): at com.martinborjesson.o2xtouchlednotifications.services.AccessibilityService.readSettings(AccessibilityService.java:107)
02-10 20:43:54.167: W/System.err(1747): at com.martinborjesson.o2xtouchlednotifications.services.AccessibilityService.onStartCommand(AccessibilityService.java:68)
02-10 20:43:54.167: W/System.err(1747): at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2039)

In the moment of the first launch of the app:
02-10 20:51:40.637: D/O2XTouchLEDNotifications(1747): Starting service...

EDIT2:
I succeeded in capturing all the log entries. Here they are
Code:
02-10 20:56:55.877: D/O2XTouchLEDNotifications(1872): Device: LG SU660/P990/P999
02-10 20:56:55.877: D/O2XTouchLEDNotifications(1872): Version: 1.2
02-10 20:56:55.877: D/O2XTouchLEDNotifications(1872): Adding Gmail observer
02-10 20:56:55.887: D/O2XTouchLEDNotifications(1872): Gmail getNumRead() exception: Permission Denial: opening provider com.google.android.gm.provider.MailProvider from ProcessRecord{406a2768 1872:com.martinborjesson.o2xtouchlednotifications/10103} (pid=1872, uid=10103) requires com.google.android.gm.permission.READ_GMAIL or com.google.android.gm.permission.WRITE_GMAIL
02-10 20:56:55.887: D/O2XTouchLEDNotifications(1872): Adding SMS/MMS receiver
02-10 20:56:55.887: D/O2XTouchLEDNotifications(1872): Adding Missed Calls listener
02-10 20:56:55.887: D/O2XTouchLEDNotifications(1872): Accelerometer tolerance: 2.5
02-10 20:56:55.887: D/O2XTouchLEDNotifications(1872): Accelerometer enabled in KeyGuard: false
02-10 20:56:55.887: D/O2XTouchLEDNotifications(1872): Display notification: true (display activity: true, always: false)
02-10 20:56:55.887: D/O2XTouchLEDNotifications(1872): Disable pulse on low battery: true (15%)
02-10 20:56:55.887: D/O2XTouchLEDNotifications(1872): LEDs indiciate while charging: true
02-10 20:56:55.887: D/O2XTouchLEDNotifications(1872): LEDs pulse while charging: false
02-10 20:56:55.897: D/O2XTouchLEDNotifications(1872): React on notifications with FLAG_SHOW_LIGHTS: true
02-10 20:56:55.907: D/O2XTouchLEDNotifications(1872): Monitored activities:
02-10 20:56:55.907: D/O2XTouchLEDNotifications(1872): com.colapps.reminder
02-10 20:56:55.907: D/O2XTouchLEDNotifications(1872): com.google.android.gsf
02-10 20:56:55.907: D/O2XTouchLEDNotifications(1872): com.fsck.k9
02-10 20:56:55.907: D/O2XTouchLEDNotifications(1872): com.android.calendar
02-10 20:56:55.907: D/O2XTouchLEDNotifications(1872): com.android.vending.updater
02-10 20:56:55.907: D/O2XTouchLEDNotifications(1872): eu.radoone
02-10 20:56:55.907: D/O2XTouchLEDNotifications(1872): com.google.android.talk
02-10 20:56:55.907: D/O2XTouchLEDNotifications(1872): com.imo.android.imoim
02-10 20:56:55.907: D/O2XTouchLEDNotifications(1872): fi.xd.android.apps.khrometophone
02-10 20:56:55.917: W/System.err(1872): java.io.FileNotFoundException: /data/data/com.martinborjesson.o2xtouchlednotifications/files/excluded_monitored_activities.dat (No such file or directory)
02-10 20:56:55.917: W/System.err(1872): 	at org.apache.harmony.luni.platform.OSFileSystem.open(Native Method)
02-10 20:56:55.917: W/System.err(1872): 	at dalvik.system.BlockGuard$WrappedFileSystem.open(BlockGuard.java:232)
02-10 20:56:55.917: W/System.err(1872): 	at java.io.FileInputStream.<init>(FileInputStream.java:80)
02-10 20:56:55.917: W/System.err(1872): 	at android.app.ContextImpl.openFileInput(ContextImpl.java:411)
02-10 20:56:55.917: W/System.err(1872): 	at android.content.ContextWrapper.openFileInput(ContextWrapper.java:152)
02-10 20:56:55.917: W/System.err(1872): 	at com.martinborjesson.o2xtouchlednotifications.utils.ObjectSerializer.unserialize(ObjectSerializer.java:33)
02-10 20:56:55.917: W/System.err(1872): 	at com.martinborjesson.o2xtouchlednotifications.utils.SerializableArrayList.unserialize(SerializableArrayList.java:52)
02-10 20:56:55.917: W/System.err(1872): 	at com.martinborjesson.o2xtouchlednotifications.services.AccessibilityService.readSettings(AccessibilityService.java:107)
02-10 20:56:55.917: W/System.err(1872): 	at com.martinborjesson.o2xtouchlednotifications.services.AccessibilityService.onStartCommand(AccessibilityService.java:68)
02-10 20:56:55.917: W/System.err(1872): 	at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2039)
02-10 20:56:55.917: W/System.err(1872): 	at android.app.ActivityThread.access$2800(ActivityThread.java:117)
02-10 20:56:55.917: W/System.err(1872): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:994)
02-10 20:56:55.917: W/System.err(1872): 	at android.os.Handler.dispatchMessage(Handler.java:99)
02-10 20:56:55.917: W/System.err(1872): 	at android.os.Looper.loop(Looper.java:130)
02-10 20:56:55.917: W/System.err(1872): 	at android.app.ActivityThread.main(ActivityThread.java:3683)
02-10 20:56:55.917: W/System.err(1872): 	at java.lang.reflect.Method.invokeNative(Native Method)
02-10 20:56:55.917: W/System.err(1872): 	at java.lang.reflect.Method.invoke(Method.java:507)
02-10 20:56:55.917: W/System.err(1872): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:861)
02-10 20:56:55.917: W/System.err(1872): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:619)
02-10 20:56:55.917: W/System.err(1872): 	at dalvik.system.NativeStart.main(Native Method)
02-10 20:56:55.917: D/O2XTouchLEDNotifications(1872): Excluded activities:
02-10 20:56:55.917: D/O2XTouchLEDNotifications(1872): Logging all notifications: true
02-10 20:56:55.917: D/O2XTouchLEDNotifications(1872): [Accessibility] Adding package: com.google.android.gm
02-10 20:56:55.917: D/O2XTouchLEDNotifications(1872): Call state updated: 0 (previous: 0)
02-10 20:56:55.917: D/O2XTouchLEDNotifications(1872): [Accessibility] Adding excluded package: com.martinborjesson.o2xtouchlednotifications
02-10 20:56:55.917: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_DEVICE_CHARGING
02-10 20:57:11.420: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_DEVICE_CHARGING
02-10 20:57:14.570: D/O2XTouchLEDNotifications(1872): onAccessibilityEvent(): android.view.accessibility.AccessibilityEvent@40521af8; EventType: 64; EventTime: 102909; ClassName: android.app.Notification; PackageName: com.android.systemui; Text: [Skenovanie mediálnych súborov...]; ContentDescription: null; ItemCount: 0; CurrentItemIndex: -1; IsEnabled: false; IsPassword: false; IsChecked: false; IsFullScreen: false; BeforeText: null; FromIndex: 0; AddedCount: 0; RemovedCount: 0; ParcelableData: Notification(vibrate=null,sound=null,defaults=0x0,flags=0x2)
02-10 20:57:29.657: D/O2XTouchLEDNotifications(1872): onAccessibilityEvent(): android.view.accessibility.AccessibilityEvent@40521af8; EventType: 64; EventTime: 118001; ClassName: android.app.Notification; PackageName: com.android.systemui; Text: [Skenovanie mediálnych súborov...]; ContentDescription: null; ItemCount: 0; CurrentItemIndex: -1; IsEnabled: false; IsPassword: false; IsChecked: false; IsFullScreen: false; BeforeText: null; FromIndex: 0; AddedCount: 0; RemovedCount: 0; ParcelableData: Notification(vibrate=null,sound=null,defaults=0x0,flags=0x2)
02-10 20:57:30.687: D/O2XTouchLEDNotifications(1872): onAccessibilityEvent(): android.view.accessibility.AccessibilityEvent@40521af8; EventType: 64; EventTime: 119032; ClassName: android.app.Notification; PackageName: com.android.systemui; Text: [Skenovanie mediálnych súborov...]; ContentDescription: null; ItemCount: 0; CurrentItemIndex: -1; IsEnabled: false; IsPassword: false; IsChecked: false; IsFullScreen: false; BeforeText: null; FromIndex: 0; AddedCount: 0; RemovedCount: 0; ParcelableData: Notification(vibrate=null,sound=null,defaults=0x0,flags=0x2)
02-10 20:57:36.740: D/O2XTouchLEDNotifications(1872): onAccessibilityEvent(): android.view.accessibility.AccessibilityEvent@40521af8; EventType: 64; EventTime: 125082; ClassName: android.app.Notification; PackageName: com.android.systemui; Text: [Prehľadávanie sa dokončilo]; ContentDescription: null; ItemCount: 0; CurrentItemIndex: -1; IsEnabled: false; IsPassword: false; IsChecked: false; IsFullScreen: false; BeforeText: null; FromIndex: 0; AddedCount: 0; RemovedCount: 0; ParcelableData: Notification(vibrate=null,sound=null,defaults=0x0,flags=0x10)
02-10 20:57:38.917: D/O2XTouchLEDNotifications(1872): onAccessibilityEvent(): android.view.accessibility.AccessibilityEvent@40521af8; EventType: 64; EventTime: 127255; ClassName: android.app.Notification; PackageName: com.android.systemui; Text: [Prehľadávanie sa dokončilo]; ContentDescription: null; ItemCount: 0; CurrentItemIndex: -1; IsEnabled: false; IsPassword: false; IsChecked: false; IsFullScreen: false; BeforeText: null; FromIndex: 0; AddedCount: 0; RemovedCount: 0; ParcelableData: Notification(vibrate=null,sound=null,defaults=0x0,flags=0x10)
02-10 20:58:36.547: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_USER_INTERACTION
02-10 20:58:36.547: D/O2XTouchLEDNotifications(1872): pnn: false
02-10 20:58:36.907: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_USER_INTERACTION
02-10 20:58:36.907: D/O2XTouchLEDNotifications(1872): pnn: false
02-10 20:58:41.177: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_DEVICE_CHARGING
02-10 20:58:50.310: D/O2XTouchLEDNotifications(1872): Screen on: false
02-10 20:58:50.310: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_OFF
02-10 20:58:50.310: D/O2XTouchLEDNotifications(1872): Unregister sensor KXTF9 Accel sensor
02-10 20:58:56.007: D/O2XTouchLEDNotifications(1872): Screen on: true
02-10 20:58:56.017: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_ON
02-10 20:58:56.490: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_USER_INTERACTION
02-10 20:58:56.490: D/O2XTouchLEDNotifications(1872): pnn: false
02-10 20:58:57.777: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_USER_INTERACTION
02-10 20:58:57.777: D/O2XTouchLEDNotifications(1872): pnn: false
02-10 20:59:31.517: D/O2XTouchLEDNotifications(1872): Screen on: false
02-10 20:59:31.517: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_OFF
02-10 20:59:31.517: D/O2XTouchLEDNotifications(1872): Unregister sensor KXTF9 Accel sensor
02-10 20:59:37.330: D/dalvikvm(1872): GC_EXPLICIT freed 285K, 49% free 2841K/5511K, external 1448K/1601K, paused 66ms
02-10 20:59:46.810: D/O2XTouchLEDNotifications(1872): Screen on: true
02-10 20:59:46.840: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_ON
02-10 20:59:47.337: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_USER_INTERACTION
02-10 20:59:47.337: D/O2XTouchLEDNotifications(1872): pnn: false
02-10 20:59:49.027: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_USER_INTERACTION
02-10 20:59:49.027: D/O2XTouchLEDNotifications(1872): pnn: false
02-10 20:59:58.487: D/skia(1872): SHAPER: stream created /data/data/com.jungle.app.fonts/tmp/TDdisplay.ttf.. 0x2B3938
02-10 20:59:58.537: D/dalvikvm(1872): GC_EXTERNAL_ALLOC freed 30K, 49% free 2844K/5511K, external 1478K/1601K, paused 30ms
02-10 20:59:58.587: D/O2XTouchLEDNotifications(1872): 55/55
02-10 20:59:58.607: D/O2XTouchLEDNotifications(1872): Read Touch LED value: wled : 2000uA
02-10 20:59:58.607: D/O2XTouchLEDNotifications(1872): Read Touch LED value (int): 20
02-10 20:59:58.637: D/O2XTouchLEDNotifications(1872): Create customize notifications
02-10 20:59:58.728: D/O2XTouchLEDNotifications(1872): Starting service...
02-10 21:00:07.280: D/O2XTouchLEDNotifications(1872): Screen on: false
02-10 21:00:07.290: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_OFF
02-10 21:00:07.290: D/O2XTouchLEDNotifications(1872): Unregister sensor KXTF9 Accel sensor
02-10 21:00:07.290: D/O2XTouchLEDNotifications(1872): Battery status updated (2/89/100) false/true
02-10 21:00:07.290: D/O2XTouchLEDNotifications(1872): LED start
02-10 21:00:11.157: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_DEVICE_CHARGING
02-10 21:00:11.167: D/O2XTouchLEDNotifications(1872): Battery status updated (2/89/100) true/true
02-10 21:00:35.747: D/O2XTouchLEDNotifications(1872): Screen on: true
02-10 21:00:35.747: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_ON
02-10 21:00:36.187: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_USER_INTERACTION
02-10 21:00:36.187: D/O2XTouchLEDNotifications(1872): pnn: false
02-10 21:00:36.367: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_USER_INTERACTION
02-10 21:00:36.367: D/O2XTouchLEDNotifications(1872): pnn: false
02-10 21:01:37.597: D/O2XTouchLEDNotifications(1872): Screen on: false
02-10 21:01:37.607: D/O2XTouchLEDNotifications(1872): onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_OFF
02-10 21:01:37.607: D/O2XTouchLEDNotifications(1872): Unregister sensor KXTF9 Accel sensor
02-10 21:01:37.617: D/O2XTouchLEDNotifications(1872): Battery status updated (2/89/100) false/true
02-10 21:01:37.617: D/O2XTouchLEDNotifications(1872): LED start
... excluded_monitored_activities.dat is really missing.
 
Last edited:

N00BY0815

Senior Member
Nov 6, 2011
2,528
1,897
Hey, sorry for digging this one out, but there are new kernels for OP Black. Maybe you can get it working again for it? Would be nice, if you could have a look into it. If you need links to the new kernels or what has been changed, just PM me ;)
 

baraozemo

Senior Member
Oct 3, 2011
140
20
this seems to be a very usefull application but fails to work with LG Net Optimus Dual (LG P698f)

My device is detected by the program as LG P350...(that is wrong).


and no notification is displayed..

I use the las LG rom for (LG P690/P698f) that is V10E with Gingerbread...

what is the possibility to fix it? this program seem very very usefull...

thank you Martin...

regards
Zemo
 

The Chief

Member
Sep 22, 2005
35
7
48
Volgograd
Extremely useful app. Can add support for Optimus Sol (E730)? Detected now as P930, flashes keyboard LED in "test" mode, but does not flash LED in off-screen mode (vibrating and melody both work well).
 

xigzil

Member
Apr 29, 2011
15
28
I apologize again for disappearing, I have a few other projects that I'm working and I no longer have an LG-device so the app is not a high priority to me anymore. I hope you understand. I'll answer the last few questions but if there is any urgent messages about the app please send me an e-mail at contact@martinborjesson.com

Hello,

i use this app on my LG P920 with the latest
GB update from LG (rooted).
I use LED Notification only ..

Sometimes when i push the Powerbutton to
turn the Phone off,(EDIT: also if i leave it in lockscreen
and it turns off the screen after a few seconds) it leave the LEDs on till
i turn the phone on and off again.

I didint have this before i installed this app.

This was some time ago but if you still have this issue I suggest you check out the notification app in the Optimus 3D-subforum. I think it fixes some issues that exists with the P920.

Is it possible to add Nexus S compatability?

I'm not sure. If anyone with the device is willing to find out then they could look it up. The requirement for it to be added to the app is that there should exist editable system-files that can control the LEDs. If it is possible send me an e-mail and I'll add it to the app.

'ello

Since moving from Modaco GR5 to Thanatos2X v5.1 EXT4 - Based on Official V20o (http://xdaforums.com/showthread.php?t=1334220) app works (signals events) only since the moment I launch its main activity (from app drawer) first time after phone start.

For example, charging signalling: looking at logcat, I can see O2XTouchLEDNotifications processing ACTION_SCREEN_OFF but nothing afterwards. After I launch the app (and immediatelly shut it down using back button), it works - ACTION_SCREEN_OFF is followed by "LED start". Any tips ?

EDIT:
During phone starting (the begining of the stack trace was nowhere to find):
02-10 20:43:54.167: W/System.err(1747): at com.martinborjesson.o2xtouchlednotifications.services.AccessibilityService.readSettings(AccessibilityService.java:107)
02-10 20:43:54.167: W/System.err(1747): at com.martinborjesson.o2xtouchlednotifications.services.AccessibilityService.onStartCommand(AccessibilityService.java:68)
02-10 20:43:54.167: W/System.err(1747): at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2039)

In the moment of the first launch of the app:
02-10 20:51:40.637: D/O2XTouchLEDNotifications(1747): Starting service...

EDIT2:
I succeeded in capturing all the log entries. Here they are
Code:
log
... excluded_monitored_activities.dat is really missing.

This was also some time ago. Is this issue still there ?

Hey, sorry for digging this one out, but there are new kernels for OP Black. Maybe you can get it working again for it? Would be nice, if you could have a look into it. If you need links to the new kernels or what has been changed, just PM me ;)

I've answered your PM, but I'll do a short answer here as well :)
If the app works with the new kernel there shouldn't be a problem. The app relies on the system-files and that the device can keep the LEDs on. If the LEDs stay on when the screen is off with the new kernel the app should work. If additional work has to be done, such as requiring to modify a system-files to tell the device to keep the LEDs on then I would be happy if someone could find out the new procedure and I'll add it to the app.

this seems to be a very usefull application but fails to work with LG Net Optimus Dual (LG P698f)

My device is detected by the program as LG P350...(that is wrong).


and no notification is displayed..

I use the las LG rom for (LG P690/P698f) that is V10E with Gingerbread...

what is the possibility to fix it? this program seem very very usefull...

thank you Martin...

regards
Zemo

Extremely useful app. Can add support for Optimus Sol (E730)? Detected now as P930, flashes keyboard LED in "test" mode, but does not flash LED in off-screen mode (vibrating and melody both work well).

No one has added support for your devices, but since they are detected as a different device they are probably similar. It might be though that the device turns off the LEDs completely when the screen is turned off (such as the latest update did for P970). I'm not sure though. But it seems that LG has chosen to do it like this in their latest updates.
The requirement for a device to work with the app is that it needs to have editable system-files that can control the LEDs. If you're willing to attempt to find out if your device is supported please send me an e-mail.
 

Wlld1

Senior Member
May 15, 2009
204
40
Novosibirsk
I have some strange issuse on my P930/Nitro HD. App works good on all firmwares, exept "official" 18f ICS leak. On fist boot it says that i have "unsupported device" and led notificatoin is not working. On CM9 works fine. But in this firmware LG made new function in Display option that give abbility to disable LED or set ON time. Maybe problem because of this?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 23
    Hi everyone !

    LG 2X/Black Notifications is an app that handles incoming notifications and uses the LED buttons on the device to notify the user of any missed notifications. LG Optimus 2X (P990/P999/SU660), LG Optimus Black (P970) and LG Optimus 3D (P920) is supported. It does not require root if the required files has the proper permissions, if they do not root is required to change them (currently the latest update for T-Mobile G2x and LG Optimus 3D). It should be usable on all ROMs (not tested though). CyanogenMod7 has its own LED-notifications which has to be disabled if you wish to use this app.

    Features
    • Built-in support for Gmail/SMS/MMS/Missed calls
    • Support for any activity that generates notifications by using Accessibility
    • Configurable pulse and vibration for every notification
    • Set the default touch LED brightness
    • Charging indicator

    How the app works
    • The app is in an idle state and will do nothing until the device receives a notification.
    • When an notification is received and the screen is on and not in lock-screen, the accelerometer sensors will be started and used as a way to detect user activity. If the sensor is triggered the feedback will be cancelled. If the sensor is not triggered and the screen is turned off the feedback will start.
    • If the screen is off the feedback will be delayed for 2 seconds. The reason for this is because some notifications might turn on the screen and in turn will cancel the feedback, so the delay will hopefully prevent this. If nothing happens during the delay the feedback starts at once.
    • The feedback will repeat until it is timed out or the screen is turned on.

    If you have any questions and/or bugs to report about the app don't hesitate to post a reply to this thread or send me a message and I'll answer them as soon as possible. I'm also open for suggestions of features to implement. However due to limited time at the moment new features may take a while to be implemented.

    Download

    For more information and free download check it out on the Android Market.

    / Martin Börjesson
    6
    Tell me what and where to modify. I can create the apk

    Enviado desde mi LG-P990 usando Tapatalk 2

    It's ok, I have create an Apk file for people who don't want to recreate the file. I made the file completely compatible with ICS and GB rom. But you need to uninstall the old app before this one.



    Here: https://www.box.com/shared/hy5h68p85gfroaj781pe

    Update: this is the v1 and I deleted the app, the v2 is below.
    Update2: better use either the v1 in the last post (or rmein's version) with SuperSU. It is cleaner this way.

    It would be great if the owner of both this topic and the github repository update the application

    Mr. Börjesson, please give me your email so that I send to you the new java file.
    3
    I'm running my own build of this at the moment, with support for the P990 enabled. I tried installing SuperSU instead of Superuser, and everything loads perfectly well on boot. The rom I am using is just stock v30a rooted with su though CWM, and not a custom one.

    I spotted a post from Rohanajoshi in the DjangoManouche ICS thread saying there was a problem with superuser: apps dont get root access when settings are like "automatic response => Allow"


    SuperSU solves this problem and lets the service run properly on boot. So if you're on the topogigi rom just download ergosum's first version and it should work.

    edit:
    I spoke too quickly there. I had problems with SuperSu for a bit and broke the app completely. Managed to fix SuperSU, then a reinstall of the app and everything works great

    Hmm thanks for the explanation. I had a feeling SuperUser wasn't working very well too. Here is the v1 for people who changed to SuperSu. (I removed it thinking it wouldn't work.)
    https://www.box.com/s/locjbo8j2j5l44kyrn0z
    2
    Hi,
    I do not speak English, so I am sorry for my bad English.
    I have a P920 and I installed this app, but it does not run. I make a missed call to myself, but the leds do not light.

    Thank you very much!

    Your English is fine :)
    Have you rooted your phone ? You could check out the thread in the Optimus 3D-subforum, there is currently another developer working with the app for the P920 and he might be able to help you out.

    Hi,

    This app is working on gr 4 but each time I reboot, I've a message that says ' superuser permissions refused for LG 2X./Black .....'

    Sent from my LG-P990

    That sounds strange, it seems the Superuser-app might be configure wrong for the app. If you open the Superuser-app then you can perhaps change so it wont refuse permissions for the app.

    I was using this great app with LG Optimus Black stock roms like v10b/c/e, but i can't do it with CM7 nightlies right now. Everytime I open app it says "App detected it has no read or write access to a required file, do you wish to fix this?" I click OK, but still doesn't work.

    This message appears everytime I open the app. What could be the problem here?

    Thanks in advance.

    What happens when you click OK ? Does it say anything or does it seem to work normally ? Did you ever get a question about allowing Superuser-permissions ?
    CM7 have their own notification built-in so there might be a conflict, you could try and disable it.

    Love the app, just what my G2x needs. Your hard work and dedication are much appreciated.
    I do, however, have one problem maybe you or the other fine members of this forum can help me with.
    I have a notification ringtone set to go off every 5 minutes after a missed notification. Works great, I love it, wish I had it earlier. However, in the morning it goes off because of the battery 100% notification. Is there a fix, workaround, or setting that I'm missing? (I've searched quite a bit but only see discussions with the SGS2) As long as the circuitry shuts down, I don't care about that notification.

    I never experienced this. Are you using a third party-app that puts a notification in the notification bar when the battery is fully charged ? If so you might have to exclude that activity (Notifications -> Exclude activities). If you're uncertain which activity it is you can log notifications in the Advanced-menu and then check the log when it happened again.

    @xigzil

    How to fully disable the accelerator/g-sensor for power saving ?

    why do you have this build in?

    without this, i would say its a wonderful valueable app ,with it have to deinstall the app ):-

    thanks

    The accelerometer can't be disabled. It is used by the app to determine if the phone is being used. For example, you're writing an e-mail on your phone and gets an SMS. At this point the app enables the accelerometer to detect user activity, if it detects activity (by movement of the phone) it disables the accelerometer and doesn't do anything more. If the accelerometer were to be disabled it would start the notification as soon as the screen turns off since it doesn't know if the phone has been used at any point after the notification has been received, which would be quite bothersome.
    It might not be the best solution but I haven't found anything else and it works pretty well.

    Normally this shouldn't use a lot of battery at all though, since when it is started it is usually only enabled for a couple of seconds. Does it use an unusual amount of battery for you ?
    1
    Thanks!! I've been using this since beta 0.3

    Just a request...

    Can accelerometer be disabled ? Cos i may be picking up the phone but not looking at the screen at all.

    And, can the App icon be reverted to have transparent background (like in the early betas)

    Cheers

    Sent from my LG-P990 using XDA App

    An option to disable accelerometer could be added, but then you would get the pulse for every incoming notification even if you've looked at them (if you were using the phone when you got them). The accelerometer is disabled when the screen is off or in the lock-screen (if you use another lock-screen than the default this might not be true though) so that if you receive a notification and then move your phone around without unlocking it the pulse should still start. So generally the accelerometer shouldn't be a problem, but if you really want an option for it I could add one :)

    I changed the appearance of the icon since it couldn't be seen on Market because it has a white background. I also preferred the old look :) But it might be possible to fix it somehow, I'll note it down and look at it when I have time.