I'm not planning to update this app anytime soon. You can try alternatives if you want, such as Backlight & Sound Notification. Thanks.
Read the FAQ before asking questions. If you haven't read it, my only reply will be "Does the FAQ help?"
Click to expand...
Click to collapse
You do NOT need a kernel with BLN support to use this app. In fact, I made this because my device has no BLN kernels.
Also, a quick note for those who are gonna read the comments: The attached MDPI/HDPI versions look fine on respective devices. The first version of ButtonLED was only available for MDPI, which should explain the first few comments.
Hey guys,
I've been fiddling around Tasker for the last few weeks and finally decided to create a fully functional app using it.
At this point, some of you will be thinking "another useless, ugly, cluttered Tasker created app that does something nobody needs".
Well, then, I'll try to prove you wrong
You do NOT need Tasker to use the app.
App Description:
ButtonLED is similar to NoLED: It allows you to have led like notifications without actually having the led light. However, NoLED uses uses your screen; ButtonLED only uses the hardware buttons' backlight (your screen stays off). It's customizable to an extent, with more to come depending on feedback and suggestions.
Features:
status bar notifications + missed call/unread text support;
pause for some user defined time on proximity (e.g. If phone is turned down, or is in your pocket);
turn button backlight for x seconds, then off for y seconds;
notification exceptions (e.g. To ignore all notification that contain "hello", add *hello* to the exception list);
logs;
should work on all devices since the user can locate the brightness file;
and some more (check the screenshots, install the app).
Compatibility:
It should work on all rooted devices (some devices have a kernel level limitation; read the FAQ). At the moment, you'll also need to have a proximity sensor to run it. It should work without having to do (almost) anything manually for many devices. If auto locate doesn't find anything useful, you'll have to manually locate the brightness file. Please share the results when you do that so i can improve the auto locate feature.
Running The App:
install and open the app. You should be greeted by a popup showing you a list of files. Select the most appropriate (you're looking for something that has a path such as "/sys/devices/platform/bcm21553-leds/leds/button-backlight/brightness). Once you're done, click "enable buttonled in accessibility" and do so. Come back to buttonled and tap the "test buttonled" button. If your capacitive buttons flash, you're good to go. Otherwise, you will need to select a different brightness file (use auto locate or do it manually).
You may also want to customize the options.
Some examples for the brightness file:
Code:
I'll update this list later.
Auto Locate will not follow symlinks as it can cause infinite loops or imprecise results (if it doesn't search deep enough). Usually, /sys/class/leds will have symlinks to all LEDs, backlight included. Check it out.
Screenshots (actual release is slightly different):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog:
v1.6 (05/05/13):
You can now ignore apps as well.
The battery tweak can be disabled on devices where ButtonLED was flashing the LEDs once or twice before sleeping forever.
You can long press log items to view the full text, for items that didn't fit.
Proximity sensor feature is now disabled (it wasn't working anyway due to a Tasker limitation) (the UI option is still listed as "FEATURE DISABLED"). This should have a minor but positive impact on performance/battery.
Minor UI changes.
Other minor changes.
v1.5 (24/02/13):
Wake locks are released while the LEDs are off and ButtonLED is waiting;
Sleep timer is fixed. The current value is also displayed when changing the sleep start/end times;
Tapping on a log entry will give you the option to add that notification to the exclusion list;
ButtonLED will give you the choice to install Busybox if it's not found;
File Browser/Auto Locate issues might be fixed for users who were having them (pressing File Browser did nothing at all even if Busybox is installed). Please try it if you were having this issue.
Added XHDPI version for everyone. Also added MDPI for JB/CM10 users.
v1.4 (19/01/13):
Manual search is now as fast as other file explorers (busybox is required);
Sleep start/end added (ButtonLED will not react to notifications during that time);
Confirmation added before removing exceptions;
Fixed a (rare?) issue where ButtonLED kept blinking the lights after the screen is turned on;
Might be more battery efficient if using higher LED Off delays, not sure. But if it is, it will be much better (more testing needed);
v1.3.1 (03/12/12):
ButtonLED will stop notifying you about missed calls and unread texts when you turn your screen on, instead of continuing till you view them;
Auto Locate will now simply search /sys for the brightness file. That means it will locate more files, across more devices. It's also faster;
Fixed the bug where ButtonLED would forget resuming once the battery drops below the threshold then go above it again.
v1.3 (03/11/12):
Stop service and exit menu option;
Ignore notifications if battery is lower than threshold;
Fixed exceptions not taking effect;
Changed the path auto locate looks into. Hopefully, this will make it work for more devices;
Two versions are now available, one for mdpi devices, the other for hdpi devices (thanks for .xxx. for testing).
v1.2 (27/10/12):
Rewrote most of the logic;
Better handling of events;
Less battery consumption and more accurate logs;
Logs now show battery percentage on processed notifications, screen on (if notifications are pending) and device shutdown, which should give users an idea about battery consumption;
Fixed logs showing skipped notifications as processed (e.g. Notifications that were issued with the screen turned on were skipped but shown as processed in the logs);
Auto Locate brightness file option (beta; need more device specific info to tweak the search);
Separated missed call from unread text notifications;
Run with higher task priority, should avoid lag (uses the renice linux shell command).
v1.1 (24/10/12):
Missed call/unread text notifications support;
Optional permanent notification;
Option to use flashlight instead of the hard buttons' led light;
Test button that will turn on and off the led/flashlight;
Other minor modifications and fixes.
(original beta thread)
To Do:
Landscape support;
Patterns?
This list is updated based on your feedback. Want to see a feature? Suggest it!
Bugs:
Proximity sensor doesn't have any effect;
This list is updated based on your feedback. Thanks for reporting any bug you find.
Downloads:
Don't forget to post your comments!
Get ButtonLED
Jelly Bean/CM10 users, get the "ButtonLED.x.x.XXXX_JB.apk".
Everyone else, download "ButtonLED.x.x.XXXX.apk".
Don't know which APK to grab? Read the FAQ for info on how to determine your resolution (MDPI, HDPI, XHDPI, ..).
You can find previous versions here.
Tasker Project:
You can get the Tasker project if you prefer, it offers the same functionality but will run inside Tasker instead of being a separate app.
You need Tasker (pre-ICS versions only) and the Holo Light IPack icon pack to use this.
Grab the appropriate project file from here.
Place the XML file in your SD Card (e.g. mnt/sdcard/tasker/projects/) and open Tasker. Long tap on an existing project (if you can't see the projects bar, disable beginner mode in Tasker's settings, then swipe down from the "projects"/"tasks"/"scenes"/"variables" bar), select "import", then tap on the file's name (e.g. buttonled.hdpi). You should see a new project appear with ButtonLED's icon. Apply the changes by tapping on the green check mark in the bottom left corner, then open Tasker again.
To open ButtonLED's configuration menu, run the task named "config".
Click to expand...
Click to collapse
~~~~
FAQ:
Q: It's not detecting my brightness file!
A: Apparently, if you have a kernel with BLN support, you don't have one. Otherwise, try searching manually or asking on your device's forum. And to make sure auto locate didn't miss something, you can run this in a terminal emulator (this will also expand the search so expect some weird results):
Code:
find / | grep brightness
It's worth noting that Auto Locate will not follow symlinks as it can cause infinite loops or imprecise results (if it doesn't search deep enough). Usually, /sys/class/leds will have symlinks to all LEDs, backlight included. Check it out.
Q: The test button works fine, but ButtonLED won't react to my notifications.
A: make sure ButtonLED is enabled in accessibility. Also, check ButtonLED's logs. Is it detecting the notifications? Is it reacting to them, but you fail to see it? If that's the case, try increasing the led on duration.
Q: Can i use this with application xyz (e.g. Whatsapp)?
A: if the application sends notifications, yes. ButtonLED will automatically detect them.
Q: Should i get the MDPI or HDPI APK?
A: if your device's density is ~160, get the MDPI APK. If it's ~240, download the HDPI APK. If you don't know, download an app from the market that will show you (e.g. screen resolution), or grab the MDPI APK and if it looks squished, uninstall it then install the HDPI APK.
Q: Battery usage is too high!
A: ButtonLED will hold a wakelock when it's flashing the LEDs. Configure it to ignore notifications you don't care about (turn the logs on, and use exceptions). See this post.
Q: Auto Locate/File Browser isn't working!
A: Try installing Busybox.
Also make sure ButtonLED has root permissions - check your SU app, and try to revoke permissions then give them back.
If that fails, it might be related to how Tasker checks if your device is rooted:
Tasker decides that a device is rooted if /system/app/Superuser.apk is present and su is present in one of the directories of $PATH
Click to expand...
Click to collapse
Q: Test works, and the logs show that ButtonLED detects and processes my notifications, but it won't light my LEDs!
A: Check this out.
Q: Talkback is talking randomly even when I have it disabled!
A: That's a known Samsung issue. It's not related to ButtonLED.
Q: How do I ask for help?
A: What have you tried? Did you do anything covered in this FAQ but it didn't help? Have you read the last few pages of comments? If you don't answer any of these questions, I'll assume you haven't read this FAQ and my reply will be "Read the FAQ".
Click to expand...
Click to collapse
~~~~
Reserved
fantastic concept, but the lights flash all the time, without notifications, on my mother's lg p500!
i'll keep watching you for updates, and i'll be testing =)
thanks!
joaor10 said:
fantastic concept, but the lights flash all the time, without notifications, on my mother's lg p500!
i'll keep watching you for updates, and i'll be testing =)
thanks!
Click to expand...
Click to collapse
The logs should be useful in that case. Did you check them out? It might be because of another app that has a permanent notification (e.g. Tasker).
edit: did auto locate work for you? If not, where was your brightness file?
I just noticed the exceptions aren't taking effect (forgot a line ). It's fixed in v1.3, will upload it later.
Regarding resolutions, I'll try checking the XML files later and try adapting it to all resolutions. Don't hold your breath, tho. Worst case scenario, multiple versions will be created, one for each resolution.
If you know where a device's brightness file is located (perhaps you own it, or you just read it somewhere), please share so I can improve the auto locate feature.
Thanks.
will there ever be a compatible jb version?
So in other words, it's like Backlight Notification but for all phones?
https://play.google.com/store/apps/details?id=neldar.bln.control.free
Exploitlol said:
will there ever be a compatible jb version?
Click to expand...
Click to collapse
If anyone has Tasker and can generate JB APKs ("Minimum Android Version: 16" setting) without problems, I'll be happy to pass the project for them to export and send me back, after which I'll upload it.
polobunny said:
So in other words, it's like Backlight Notification but for all phones?
https://play.google.com/store/apps/details?id=neldar.bln.control.free
Click to expand...
Click to collapse
Pretty much, although it works differently: BLN "redirects" LED notifications to the capacitive buttons, ButtonLED tries to detect all notifications.
It's more like NoLED but with capacitive buttons.
Thanks GermainZ...Working on my Ace-i
How's the battery drain?
ccab said:
How's the battery drain?
Click to expand...
Click to collapse
I did my best to keep as low as possible: the sensor is only checked when the notification is triggered and every 30 cycles after that.
I did some testing and the drain was around 6.5% per hour on my device (tested for around 7 hours). Note that was before I fully implemented the battery saving features, so it will probably be less. The used settings were: 1s on, 1s off. (current default is 1s on / 4s off)
But then again, it all depends on your device. Obviously, having a kernel that supports underclocking (e.g. setting your frequencies to 156Mhz-1Ghz with a governor that doesn't lock the frequency to the max) helps, since your device will always be awake if ButtonLED is active (active as in turning the LED on and off, not just running in the background).
Thanks a tonne man.. I was waiting for such an app for like months now.. glad it came and yeah fyi I have subscribed to the thread and waiting for more features and updates..
Sent from Hell!!
---------- Post added at 11:08 AM ---------- Previous post was at 10:52 AM ----------
Resizing for hdpi phones is needed hehehe..
And May I ask where the brightness file is generally located ? Because I wasn't able to make the app work for some reason :/
Sent from Hell!!
.xxx. said:
Thanks a tonne man.. I was waiting for such an app for like months now.. glad it came and yeah fyi I have subscribed to the thread and waiting for more features and updates..
Sent from Hell!!
---------- Post added at 11:08 AM ---------- Previous post was at 10:52 AM ----------
Resizing for hdpi phones is needed hehehe..
And May I ask where the brightness file is generally located ? Because I wasn't able to make the app work for some reason :/
Sent from Hell!!
Click to expand...
Click to collapse
Autolocate didn't work?
It depends on the device and ROM used, really. In the first post, I posted two examples (S5830 and S5830I).
Judging from your signature, I'm guessing you're using the Galaxy S3. After some googling, I think this file will work:
/sys/class/leds/button-backlight/device/leds/button-backlight/brightness
If not, well... Try asking on your device's forum and report back once you find it
GermainZ said:
Autolocate didn't work?
It depends on the device and ROM used, really. In the first post, I posted two examples (S5830 and S5830I).
Judging from your signature, I'm guessing you're using the Galaxy S3. After some googling, I think this file will work:
/sys/class/leds/button-backlight/device/leds/button-backlight/brightness
If not, well... Try asking on your device's forum and report back once you find it
Click to expand...
Click to collapse
Auto locate did not work man. When I tried the test, it gave me this reason.
My decide is LG optimus sol with cm7.
I would glad to see a reply soon. Eager to make it work.
Sent from Hell!!
.xxx. said:
Auto locate did not work man. When I tried the test, it gave me this reason.
My decide is LG optimus sol with cm7.
I would glad to see a reply soon. Eager to make it work.
Sent from Hell!!
Click to expand...
Click to collapse
Try this:
Tap the "Browse for the button brightness file" button
Go to /sys/class/leds/button-backlight/
Tap the "brightness" file
Test
If that doesn't work, try the same with /sys/class/leds/button-backlight/device/leds/button-backlight/ in step 2.
GermainZ said:
Try this:
Tap the "Browse for the button brightness file" button
Go to /sys/class/leds/button-backlight/
Tap the "brightness" file
Test
If that doesn't work, try the same with /sys/class/leds/button-backlight/device/leds/button-backlight/ in step 2.
Click to expand...
Click to collapse
Man!!!!!! You are a life saver.. Thanks a lot.. I got the file.. tested the button led light.. and now looking forward for real time notification.
Sent from Hell!!
---------- Post added at 12:12 PM ---------- Previous post was at 12:05 PM ----------
Okay. So, here is the deal.
In test mode it works like a charm. But in real time notification, it won't glow the soft key light.
Sent from Hell!!
.xxx. said:
Man!!!!!! You are a life saver.. Thanks a lot.. I got the file.. tested the button led light.. and now looking forward for real time notification.
Sent from Hell!!
---------- Post added at 12:12 PM ---------- Previous post was at 12:05 PM ----------
Okay. So, here is the deal.
In test mode it works like a charm. But in real time notification, it won't glow the soft key light.
Sent from Hell!!
Click to expand...
Click to collapse
Did you enable ButtonLED in Accessibility?
If you did, check ButtonLED's logs. Do note that ButtonLED will only work if your display is off, and will stop notifying you once you turn the screen on.
GermainZ said:
Did you enable ButtonLED in Accessibility?
If you did, check ButtonLED's logs. Do note that ButtonLED will only work if your display is off, and will stop notifying you once you turn the screen on.
Click to expand...
Click to collapse
I have enabled it in accessibility.
Buttonled log looks normal to me. It catches the going processes.
Yeah, the display was off for a long.time and there were missed calls but soft keys never glowed :/
Sent from Hell!!
.xxx. said:
I have enabled it in accessibility.
Buttonled log looks normal to me. It catches the going processes.
Yeah, the display was off for a long.time and there were missed calls but soft keys never glowed :/
Sent from Hell!!
Click to expand...
Click to collapse
What do the logs say
Normally, it would be something like this:
Code:
14:57: Stopped (screen turned on; battery: 87%)
14:56: Sleeping for 300 s (proximity detected; battery: 87%)
14:51: Sleeping for 300 s (proximity detected; battery: 87%)
14:51: Missed Call (processed; battery: 87%)
14:51: Missed Call (detected)
Also try setting a higher "on" delay, just to make sure it's not turned off too fast.
Related
NEW VERSION RELEASE CANDIDATE 4
NOTE: I DON'T HAVE ENOUGH TIME TO OFFER SUPPORT FOR THIS APP. I'M RELEASING THE SOURCE CODE UNDER GPLV3 LICENSE.
SCREENSHOTS CLICK HERE TO SEE
LedNotifications it's a event based application that will detect when some applications write in the notification bar and will raise a led event.
The app consists in a:
-background process (lednotifybkg.exe)
-configuration tool (LedNotifyGUI.exe)
Bakground process it's coded in C to maximice performance and memory consumption.Background process will trigger the led events so you don't need the configuration tool to be running.
The application it's now hardcoded so only works with HD2 devices.
How to use it
Just run the configuration tool. Now raise a notification (for example a misscall) and go to configure-> add last active notification. Now select the led and press Add. To ensure compatibility you'll only be able to configure the LAST ACTIVE NOTIFICATION. So if you have 3 notification, you'll be able to configure the last one. To configure the others rid of the last one and do the same again.
When you finish, start the background process. If it's started, shutdown it and start it again to apply changes.
PLEASE SHUTDOWN THE CONFIGURATION TOOL WHEN FINISH WITH THE EXIT BUTTON OR THE BATTERY CONSUMPTION MAY BE INCREASED
Warning: The background process will not start automatically.You should start it when your device it's reset.
SOURCE CODE
I'll release the source code when I get positive feedback indicating that the application has no bugs.Just to release something in good conditions. I'm not a software developer so don't expect too much.
THANKS TO...
MichyPrima for the ManilaSDK
NetRipper for LeoExtendedNotifications source code
WARNING: INCOMPATIBILITIES
To raise an event I delete a registry value that saves the id of the active notification. Concretely HKEY_LOCAL_MACHINE\System\State\Shell\Notifications\Active value ID. If you experience any problem with other notification software it can be related with this. Disable my app, make a soft reset and check if the issue has been solved.
MUST READ
I've made an effort coding this application, ensuring it has no bug and fixing it. So now I'm asking you if you like the application please donate to some ONG (ie http://www.supportunicef.org/), so I've helped you with this app, you can help other people with your money . Now you've read this you know that the pword to open the file is donateong
KNOWN BUGS
a) When the bicolor led it's blinking if you rid off some notification maybe it won't shutdown. Please report if this happens to you, I don't know if I fixed it at all.
FAQ
What's the battery consumption?
The battery consumption it's 0!!. The led it's put in an automode so the application it's not responsible of making the on/off process, the app just triggers leds on/off
Why I can't configure led's frequency and duty cicle?
To ensure maximum battery performance the led it's put in an automode. The driver is the responsible to blink the led so you can't configure it. You can still download previous versions but they consume battery power.
Why have you changed the Add apps menu?
With the new system I can't monitor all notifications so I've coded this way to ensure notifications you add will raise an event in the background process.
Why don't you use the netRippers code to blink the keypad?
Because I don't know howto put in automode and this affects battery performance
What's the password for the file?
Please read MUST READ section
DOWNLOAD RC4 SOURCE CODE
DOWNLOAD AUTOSTARTUP RC4 CAB
DOWNLOAD AUTOSTARTUP RC3 CAB
DOWNLOAD RELEASE CANDIDATE 3
DOWNLOAD RELEASE CANDIDATE 2
DOWLOAD RELEASE CANDIDATE 1 HERE
-----------------------------------------------------------------------------------------------------------------------------------------------------
OLD VERSIONS
Hello!,
I'm here to present my first windows mobile application LedNotifications. It's a general purpose led notifier but designed in an HD2 (so by now only works in an HD2).
The application looks for notifications in the notification bar and let's you to configure a led color. The led will start to blink as soon as the notification icon appears in the notification bar. There's a quicklist to enable/disable apps quickly. The app also lets you to override the power led.
There are some known bugs:
1)the configuration tools sometimes crashes.
2) Slide reported that sometimes the app doesn't work in stanby mode, if anybody knows what the reason could be please write in this post
It will let you configure led email notifications on the HD2!
Use at your own risk, I'm not responsible for the damages that this program can cause to you or/and your device.
Background program can crash and run CPU as high as 90% so if this happens it will drain your battery.I've been working on that so I expect this not to happen but it's a possibility.
Configuration files allow you to use in other devices. Format text files are
on.txt -> configuration to bring led on
off.txt -> configuration to turn the led off
so every file has LED_ID,LED_STATUS_VALUE
in HD2 green led is 1 and on status is 1
on.txt looks like this 1,1
I hope you like the program. I will post the source code soon.
The program does not register to startup so a reset will disable it (and solve any problem related to this)
Lots of thanks to MichyPrima for the manila controls
showthread.php?t=566188
Regards,
Jordi
(OLD) Last BETA version LedNotifications003.zip (OLD)
(OLD) DOWNLOAD IT HERE (OLD)
Changelog
31/03/2010 rc3 Solved power led always going green afeter a notification.
Solved bad management of notification. Led was not turned of after rid of the notification.
Solved OverridePowerLed issue
Solved some GUI crashes
30/03/2010 rc2 When you set OverridePowerLed and you rid of a notification, the led goes to its original state
30/03/2010 New background with no power consumption, completely event based. Based on NetRipper's LeoExtendedNotifications code.
21/03/2010 Improved power consumption up to 60%. Improves your battery life
20/03/2010 Fixed bug that did'nt turn off the led after you rid o the notification. Some improvements on the led code. Now the led behaviour it's more similar to the one you see in the configuration tool.
17/03/2010 I've changed the app name to LedNotifications to avoid legal issues. There's a led control app for BB that it's called LedNotifier.
Very interesting!
really interesting ..will check the memory usage.
antoniomistretta said:
Very interesting!
Click to expand...
Click to collapse
Thank you!!
karaern said:
really interesting ..will check the memory usage.
Click to expand...
Click to collapse
The app has two executables. One for the GUI and the other for the background. The background process manages leds and it coded in C++. Only around 70kbyte of memory and around 1% CPU . The GUI it's about 2Mbyte but it can be shutdown once you have configured it.
Will be watching this with exteme interest!
Interesting....keeping an eye on it.
kenkiller said:
Interesting....keeping an eye on it.
Click to expand...
Click to collapse
+1
Olioaglio
Hi htcjordi!
Thanks for the program. I am testing it on my Topaz. It seems to be working perfectly so far. I love the interface.
Many thanks! I will report any bugs I find.
I have a link from the start menu to this so it auto starts after a reset.
So far not too bad... Occasionally the led stays on but otherwise i finally have my flashing email notification
Well done!
Hi! Very interesting application you made there.
I think it would be even more interesting if the 2 settings txt files would be replaced by registry entries.
Thanks for the good work!
I have been testing this for about a day now. I received an email but the LED was not responding. When I woke up my device, the LED illuminated and stayed illuminated even after I removed all notifications and my TD2 was not charging.
It would be nice to be able to configure the different notifications with different LEDs. I haven't figured out how to do this yet.
Otherwise, it is great.
please
we want nimbuzz to notify us when we have a missed call or massage
because there is noway i can know if i have a missed call or massage
can you make your app work also with nimbuzz ? like what you did woth palringo ?
Aqrab said:
please
we want nimbuzz to notify us when we have a missed call or massage
because there is noway i can know if i have a missed call or massage
can you make your app work also with nimbuzz ? like what you did woth palringo ?
Click to expand...
Click to collapse
If you read the about tab in the GUI, this gives instructions on how to do this.
mitsi said:
If you read the about tab in the GUI, this gives instructions on how to do this.
Click to expand...
Click to collapse
yeah but the problem is nimbuzz does not have a notification icon bar
THATS WHY IM ASKING HERE
NO RESPOND FROM NIMBUZZ SITE
EpiphanyNL said:
Hi! Very interesting application you made there.
I think it would be even more interesting if the 2 settings txt files would be replaced by registry entries.
Thanks for the good work!
Click to expand...
Click to collapse
Actually it was easier to do with registry entries but I did it with text files because I think it's more friendly to work with text files than work with the registry. Just in case somebody want to write new files! Anyway I apreciate your comment
mitsi said:
I have been testing this for about a day now. I received an email but the LED was not responding. When I woke up my device, the LED illuminated and stayed illuminated even after I removed all notifications and my TD2 was not charging.
It would be nice to be able to configure the different notifications with different LEDs. I haven't figured out how to do this yet.
Otherwise, it is great.
Click to expand...
Click to collapse
Hi mitsi! I figured out that you have a Diamond, I can't test my app with this machine but I'll try to help you.Did your TD2's leds work through the configuration menu? I mean the menu you can configurate led's frequency and duty cicle. If the led is not blinking you'll have to play with configuration files.
You can configure notifications with different leds. Raise some event in the notification bar to list some app in the app menu. Then activate the app pressing the on/off button : it should appear a menu indicating wich led you want to turn on (in my case green/orange). If different physical leds are avaliable (not one with many colors) they should appear with indepentents on/off buttons.
Thank you for all your feedback
Aqrab said:
please
we want nimbuzz to notify us when we have a missed call or massage
because there is noway i can know if i have a missed call or massage
can you make your app work also with nimbuzz ? like what you did woth palringo ?
Click to expand...
Click to collapse
Hi Aqrab this software works only with the notification bar.I've playing with Nimbuzz and only plays a sound on notifications!!!! I've playing with talkonaut also and the same but at least vibrates.
Aqrab said:
yeah but the problem is nimbuzz does not have a notification icon bar
THATS WHY IM ASKING HERE
NO RESPOND FROM NIMBUZZ SITE
Click to expand...
Click to collapse
If Nimbuzz does not respond I can't do much more . I recommend you to use Palringo instead
How is work going on this?
I seem to keep getting an instant where by the flashing LED stays solid when i get rid of the notification (by reading the email).
I have currently set up a shortcut to the GUI so i can stop/restart it but it's a bit annoying... any chance you can add a restart into the script after the notification is removed?
PS its a HD2....
crispy514 said:
How is work going on this?
I seem to keep getting an instant where by the flashing LED stays solid when i get rid of the notification (by reading the email).
I have currently set up a shortcut to the GUI so i can stop/restart it but it's a bit annoying... any chance you can add a restart into the script after the notification is removed?
PS its a HD2....
Click to expand...
Click to collapse
I'll work on it this weekend. There's a trick to avoid that: get rid of the notification when the led is off.
htcjordi said:
I'll work on it this weekend. There's a trick to avoid that: get rid of the notification when the led is off.
Click to expand...
Click to collapse
easier said than done will practice my timing!
crispy514 said:
easier said than done will practice my timing!
Click to expand...
Click to collapse
Stop practicing! I've fixed the bug
Hello, I'm the developer for the NowNotifier application and decided that the comments in the Samsung store is a bad place for me to keep track of feedback, so decided to start this thread.
Feedback is always welcomed.
Johann
Todo:
* Fix for reading messages.
* Option to hide app after action DONE
* No notifications on sleep mode
* Exit to home / watch screen
Hi,
Nice to see you here. Hopefully we will see a new release with enhancement and bug fixes soon
renegade said:
Hi,
Nice to see you here. Hopefully we will see a new release with enhancement and bug fixes soon
Click to expand...
Click to collapse
Thanks, had to freeze development while the app was being judged and had to take care of other projects. Right now my priority is to fix the message display, do you have anything to report that needs to be fixed?
- J
johann.r said:
Thanks, had to freeze development while the app was being judged and had to take care of other projects. Right now my priority is to fix the message display, do you have anything to report that needs to be fixed?
- J
Click to expand...
Click to collapse
This may be some sort of error on my part, so please bear with me. My only complaint is when using your app the Now Notifier screen seems to stick around. I do have my watch set to wake up to last screen used as that is the only way the Endomondo app is useful when running. Is there a way to turn this off.
lordmorphous said:
This may be some sort of error on my part, so please bear with me. My only complaint is when using your app the Now Notifier screen seems to stick around. I do have my watch set to wake up to last screen used as that is the only way the Endomondo app is useful when running. Is there a way to turn this off.
Click to expand...
Click to collapse
If you have autohide on, and don't touch the notification, it should hide automatically. If you touch it, you should swipe up to down past the green screen to dismiss the application.
johann.r said:
If you have autohide on, and don't touch the notification, it should hide automatically. If you touch it, you should swipe up to down past the green screen to dismiss the application.
Click to expand...
Click to collapse
Got it...thanks. Would it be possible in a future update to allow for the autohide timeout to be changed by the user to something shorter?
Edit: Just received an email through Nine (me email app on my phone). I got the notification through NN, replied to it with NN and the NN screen stayed on the screen until I made it go away. This is what I meant earlier. Is this something that's limited by the APIs, or is it something that can be configured to go away on its own?
lordmorphous said:
Got it...thanks. Would it be possible in a future update to allow for the autohide timeout to be changed by the user to something shorter?
Click to expand...
Click to collapse
What would you consider shorter? If I do it I would prefer to consolidate everything together so more like a selection between none / 5 seconds / 10 seconds / 30 seconds / 1 minute so that way there is no 2 options for the same thing, what you think?
johann.r said:
What would you consider shorter? If I do it I would prefer to consolidate everything together so more like a selection between none / 5 seconds / 10 seconds / 30 seconds / 1 minute so that way there is no 2 options for the same thing, what you think?
Click to expand...
Click to collapse
Is the autohide for the NN screen or the notification itself. If for the notification, the choices of 5/10/20 would probably be ideal, at least to me. If it is for the NN screen, then just a standard 5 seconds would be fine. I wouldn't think you would want it to not show up as all; I mean you want your name out there and all, I get that.
By the way, did you see my edit above?
lordmorphous said:
Is the autohide for the NN screen or the notification itself. If for the notification, the choices of 5/10/20 would probably be ideal, at least to me. If it is for the NN screen, then just a standard 5 seconds would be fine. I wouldn't think you would want it to not show up as all; I mean you want your name out there and all, I get that.
By the way, did you see my edit above?
Click to expand...
Click to collapse
The NowNotifier screen is more for you not to leave by error the app when you don't want it because when you get to it, you are a swipe away from leaving the application.
I think I got it, the auto hide is when you receive a notification. As soon as you touch the application, the autohide stops so you can browse/read your notification. If i understand you well, you want to dismiss the application once you execute an action (like reply) is that correct?
johann.r said:
The NowNotifier screen is more for you not to leave by error the app when you don't want it because when you get to it, you are a swipe away from leaving the application.
I think I got it, the auto hide is when you receive a notification. As soon as you touch the application, the autohide stops so you can browse/read your notification. If i understand you well, you want to dismiss the application once you execute an action (like reply) is that correct?
Click to expand...
Click to collapse
Correct.
Well then yeah, that would have to be a new option something like "Hide application after action" and that basically wouldn't have a delay, once you click the button it hides.
Just came here to say thanks to you! Really love your app! Already rated it with 5 stars!
Ir makes our abondened tizen looks better!
sauliiin said:
Just came here to say thanks to you! Really love your app! Already rated it with 5 stars!
Ir makes our abondened tizen looks better!
Click to expand...
Click to collapse
Thanks for the comment! Still learning how to add new stuff, so I always say that this is a work in progress!
sauliiin said:
Just came here to say thanks to you! Really love your app! Already rated it with 5 stars!
Ir makes our abondened tizen looks better!
Click to expand...
Click to collapse
This:good:
---------- Post added at 03:55 PM ---------- Previous post was at 03:31 PM ----------
johann.r said:
Hello, I'm the developer for the NowNotifier application and decided that the comments in the Samsung store is a bad place for me to keep track of feedback, so decided to start this thread.
* Demo to be added after 10 posts *
Feedback is always welcomed.
Johann
Click to expand...
Click to collapse
I just thought of another "issue", please don't take this as nit-picking. I really do like your app.
I use the stock sleep app at night. This silences notification and keeps the screen from coming on in the middle of the night. Your app still goes off throughout the night and I never remember to turn off your app until after the first time I'm woken up by the buzzing on my wrist. Is it possible to make your app "respect" the sleep mode?
I am not a developer and only have a very generic understanding of api's and such, so this may not be feasible.
Did you email me about that before?
Yes I'm looking into it, by default I just post the messages that the phone broadcast, so I need to find out a way for me to know when the phone is in that mode to block the messages. No luck so far, but still looking into it.
I'll update the main post with a wishlist and work through it later.
No, I never emailed you... But that must mean I'm not the only one who thought of it. Thanks for starting this thread.
Yeah I got some a question about it some time ago, didn't know about that functionality so I'm looking into it. Yeah between emails and see if comments were updated, I saw a question about the application in this forum, so decided what a better place to keep all the feedback in one place.
Also at this moment I'm doing some live development, testing my encoding PC for other project so feel free to drop and keep the feedback going :good:
The link is YOUTUBE /watch?v=vEW-0gI72S8 <- can't post links yet
Here is a quick demo for the hide after action
Ok I have a list of enhancements I would love to see:
Phone app:
1- When first installed, all applications are enabled (checked) by default, it takes a while to uncheck the applications you don’t want to receive notifications from. Maybe a "check/uncheck all" button.
2- Option to receive notifications on Gear and vibrate while keeping screen off.
3- Option to not show notifications on Gear when phone is used “i.e. screen on and unlocked”.
4- Option to dismiss notification on Gear when it is dismissed from phone, and vise-versa.
5- Option for to exclude notifications from “ignored phrases”.
6- Option for “Night/Do not disturb” times.
7- Provide option for different vibration “duration” for each app
Gear app:
1- Theming option (dark background & light background)
2- “Text size option”.
3- You should queue all the notifications received.
4- Swipe right/left for next/previous notification. Swipe down to dismiss. And tap for notification text/details. Swipe up for (suggestions?)
5- After dismissing the last notification, app should go back immediately (1 sec delay?) to watchface.
And most important of all, stability, stability and stability. The problem I have seen with all the notification apps is stability and usability issues. Often they either hang, crash or stop receiving notifications for some reason or another. And that is very frustrating.
Honestly, if you want you app to be the best notification app (whether free or paid), you should look at the two other similar notification app and combine the best features with your app which I believe provides the best visual experience but lacks in features.
renegade said:
Ok I have a list of enhancements I would love to see:
Phone app:
1- When first installed, all applications are enabled (checked) by default, it takes a while to uncheck the applications you don’t want to receive notifications from. Maybe a "check/uncheck all" button.
2- Option to receive notifications on Gear and vibrate while keeping screen off.
3- Option to not show notifications on Gear when phone is used “i.e. screen on and unlocked”.
4- Option to dismiss notification on Gear when it is dismissed from phone, and vise-versa.
5- Option for to exclude notifications from “ignored phrases”.
6- Option for “Night/Do not disturb” times.
7- Provide option for different vibration “duration” for each app
Gear app:
1- Theming option (dark background & light background)
2- “Text size option”.
3- You should queue all the notifications received.
4- Swipe right/left for next/previous notification. Swipe down to dismiss. And tap for notification text/details. Swipe up for (suggestions?)
5- After dismissing the last notification, app should go back immediately (1 sec delay?) to watchface.
And most important of all, stability, stability and stability. The problem I have seen with all the notification apps is stability and usability issues. Often they either hang, crash or stop receiving notifications for some reason or another. And that is very frustrating.
Honestly, if you want you app to be the best notification app (whether free or paid), you should look at the two other similar notification app and combine the best features with your app which I believe provides the best visual experience but lacks in features.
Click to expand...
Click to collapse
Thanks for the list Renegade!
You should have seen this app the first revision 2 months ago, it was as plain as it gets :laugh:
Some stuff is doable, other might not, right now is limited by my limited knowledge of Android an Tizen, like you say I like to work more on stability so for me is means to add 1 or 2 new features per release.
Powy
Powy gives you access to handy shortcuts through the power button. To trigger a shortcut you simply have to press the power button N times (you define how many times) and then the shortcut is triggered.
Powy provides the following shortcuts that you can use:
Hear the current time
Turn on or off your flashlight / torch / LED
Open camera app
Record audio
All of the shortcuts listed above work even if screen is off and/or device is locked. Does not have to be open or in recent apps to work.
You can enable only the shortcuts you want to be usable. You can configure shortcuts key combinations per shortcut. And you can start or stop Powy at any time.
Download
https://play.google.com/store/apps/details?id=com.danilomendes.powy
How to use?
Start Powy by pressing the button in the main screen of the app. Now to trigger the shortcut you want simply press the number of times configured in that shortcut (listed in the main screen).
Story behind Powy
Initially I've developed Powy only for my own needs, the initial purpose of Powy was to simply tell me the current time when I was using headphones, because I use headphones a lot and I'm kind of obsessed with time and I hated to have to take my phone out of my pocket to see what time it was. I developed a quick draft for myself and then now I figured that the app might be helpful to other people.
How it works - Technical description
Since we cannot actually listen to power button key events on background, Powy actually listens to screen on/off events and then after 0.714 seconds, after the last pressed key (maximum of 1.5 seconds), Powy sees if the total number of screen on and off's matches a shortcut and triggers it.
Permissions
RECEIVE_BOOT_COMPLETED - For the app to start running upon boot. This can be turned of whether or not you have Android 6+. You can turn it off on the Preferences section within the app.
CAMERA - *Only for Android versions below 6* This is simply used to use the flashlight.
WAKE_LOCK - Only used for the camera shortcut when it's triggered with the screen off. Powy does not keeps the wake lock for more than 100 ms after the camera shortcut is triggered.
FLASHLIGHT - For the flashlight.
RECORD_AUDIO - To record audio only when the record audio shortcut is triggered.
WRITE_EXTERNAL_STORAGE - Powy only uses this to write the recorded audio to the sdcard.
VIBRATE - Only to vibrate when record audio is triggered.
ACCESS_NETWORK_STATE & INTERNET - These two permissions are used by admob.
Try it and tell me what you think
I'm available to respond through this forum or through here.
Cumps,
Danilo Mendes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It would be really cool to hear some feedback from you guys on how to improve the app or if you are having difficulties using it. Thank you
danilo.mendes said:
It would be really cool to hear some feedback from you guys on how to improve the app or if you are having difficulties using it. Thank you
Click to expand...
Click to collapse
Whenever I try to get the >2 actions to run, I usually fail and it always just reads me the time. Maybe the 0.5s threshold is too low?
MishaalRahman said:
Whenever I try to get the >2 actions to run, I usually fail and it always just reads me the time. Maybe the 0.5s threshold is too low?
Click to expand...
Click to collapse
Hi thank you for replying.
I wrote the incorrect value, the threshold is actually 0.714 seconds. But in any case, try not to press the power button too quickly.
I think if it recognizes two screen on/off's it means it can capture more than that, meaning that the threshold is probably enough, but maybe the maximum time of 1.5 seconds it has to joins presses might not be sufficient.
But try not to press the power button too quickly and tell me how it goes.
Cumps,
Doesn't run on op3t.. freedom os7.1.1
The only one that works for me is "Tell me the time" on a Pixel XL running 7.1.1. I would totally donate if I could use this to toggle my flashlight.
earthplug said:
Doesn't run on op3t.. freedom os7.1.1
Click to expand...
Click to collapse
Hi,
I honestly haven't tested on freedomOS. Can you please give me more info on this? Does the app crashes? The shortcuts are not being triggered?
If the app does not crash try to press the power button calmly, because Powy actually depends on screen on/off events.
Keep me posted on this issue, thank you.
Cumps
overcoded said:
The only one that works for me is "Tell me the time" on a Pixel XL running 7.1.1. I would totally donate if I could use this to toggle my flashlight.
Click to expand...
Click to collapse
Hi, thank you for the feedback. Please note that Powy actually relies on screen on/off events. Try not to press the power button too quickly and confirm if the flashlight shortcut is ON (the switch is on).
Also, if you want, you can change the flashlight shortcut to 2 times power button . You just have to change the shortcut to '2 x Power button' simply by clicking on edit:
Cumps
It currently doesn't work for me on the LG G5 running Marshmallow. I tried using only the time function and pressing twice both quickly and slowly. Neither scenario triggers the action. This is a really cool idea and thanks for the app -- I hope I can get it working on my setup.
danilo.mendes said:
Hi,
I honestly haven't tested on freedomOS. Can you please give me more info on this? Does the app crashes? The shortcuts are not being triggered?
If the app does not crash try to press the power button calmly, because Powy actually depends on screen on/off events.
Keep me posted on this issue, thank you.
Cumps
Click to expand...
Click to collapse
The app doesn't load at all just flashes and that's it back to home screen.
Hi
Only flash shortcut works for me.
Salmusng S5 (neo), Android 6.01 stock.
However good app, thanks!
app crashes immedietly after introduction ends
my currents are in my signature
danilo.mendes said:
Hi, thank you for the feedback. Please note that Powy actually relies on screen on/off events. Try not to press the power button too quickly and confirm if the flashlight shortcut is ON (the switch is on).
Also, if you want, you can change the flashlight shortcut to 2 times power button . You just have to change the shortcut to '2 x Power button' simply by clicking on edit:
Cumps
Click to expand...
Click to collapse
Thanks for the reply, I have tried both slow and fast power button presses, as well as waiting for the screen to turn off before initiating more presses. Like I said, "say the time" does work, so I know what the timing is supposed to be like.
@danilo.mendes Cool idea bro..
I guess the reason why users are facing problems is that the time taken to receive consecutive SCREEN_ON/OFF broadcasts vary for different devices..
Instead of hardcoding the threshold value, you can get the data from user itself..
While opening the app for first time, you can ask the users to consecutively press the power button for N times for calibration purpose (N is your wish).
While the user is doing that, you may record (in your Service) the threshold timings between the SCREEN_ON/OFF broadcasts and compute the average for N trials.
And finally set that as threshold value.
That way, you may get the app working for all devices..
Hope my words are clear
GokulNC said:
@danilo.mendes Cool idea bro..
I guess the reason why users are facing problems is that the time taken to receive consecutive SCREEN_ON/OFF broadcasts vary for different devices..
Instead of hardcoding the threshold value, you can get the data from user itself..
While opening the app for first time, you can ask the users to consecutively press the power button for N times for calibration purpose (N is your wish).
While the user is doing that, you may record (in your Service) the threshold timings between the SCREEN_ON/OFF broadcasts and compute the average for N trials.
And finally set that as threshold value.
That way, you may get the app working for all devices..
Hope my words are clear
Click to expand...
Click to collapse
Hi, Yeah it seems like that's right. That's a really cool suggestion, thank you I'm going to use a mix of your suggestion, because I want to avoid complicating the setup for the first time users. So instead of asking the user, I'm thinking about calculating the threshold automatically for the first time then use those values by default. And also adding a preference for the user to configure the threshold and the max time.
I'll update the apk version asap with this changes. Again, thank you
Cumps
nhmanas said:
app crashes immedietly after introduction ends
my currents are in my signature
Click to expand...
Click to collapse
earthplug said:
The app doesn't load at all just flashes and that's it back to home screen.
Click to expand...
Click to collapse
Hi both, Thank you for the feedback. I just got a crash report related to the TTS (Text-To-Speech) and I'm going to fix it and include it in the next client that I'll upload very soon.
Cumps
sugerdroid said:
It currently doesn't work for me on the LG G5 running Marshmallow. I tried using only the time function and pressing twice both quickly and slowly. Neither scenario triggers the action. This is a really cool idea and thanks for the app -- I hope I can get it working on my setup.
Click to expand...
Click to collapse
Publiuss said:
Hi
Only flash shortcut works for me.
Salmusng S5 (neo), Android 6.01 stock.
However good app, thanks!
Click to expand...
Click to collapse
Hi both, Thank you for the feedback Like GokulNC said, some devices seem to have more different times of screen off/on events than I expected. For this reason I'll develop some changes to make this more flexible and hopefully this will fix your issues. This will be in the next release that I'll release very soon.
Cumps
GokulNC said:
@danilo.mendes Cool idea bro..
I guess the reason why users are facing problems is that the time taken to receive consecutive SCREEN_ON/OFF broadcasts vary for different devices..
Instead of hardcoding the threshold value, you can get the data from user itself..
While opening the app for first time, you can ask the users to consecutively press the power button for N times for calibration purpose (N is your wish).
While the user is doing that, you may record (in your Service) the threshold timings between the SCREEN_ON/OFF broadcasts and compute the average for N trials.
And finally set that as threshold value.
That way, you may get the app working for all devices..
Hope my words are clear
Click to expand...
Click to collapse
overcoded said:
Thanks for the reply, I have tried both slow and fast power button presses, as well as waiting for the screen to turn off before initiating more presses. Like I said, "say the time" does work, so I know what the timing is supposed to be like.
Click to expand...
Click to collapse
nhmanas said:
app crashes immedietly after introduction ends
my currents are in my signature
Click to expand...
Click to collapse
Publiuss said:
Hi
Only flash shortcut works for me.
Salmusng S5 (neo), Android 6.01 stock.
However good app, thanks!
Click to expand...
Click to collapse
earthplug said:
Doesn't run on op3t.. freedom os7.1.1
Click to expand...
Click to collapse
overcoded said:
The only one that works for me is "Tell me the time" on a Pixel XL running 7.1.1. I would totally donate if I could use this to toggle my flashlight.
Click to expand...
Click to collapse
sugerdroid said:
It currently doesn't work for me on the LG G5 running Marshmallow. I tried using only the time function and pressing twice both quickly and slowly. Neither scenario triggers the action. This is a really cool idea and thanks for the app -- I hope I can get it working on my setup.
Click to expand...
Click to collapse
Hi everyone,
Powy 1.0.2 released
Added:
Now the threshold and max time of key presses and shortcuts are configurable
Fixed crash caused by no TTS engine in some ROMs (e.g.: LG G5)
Added method to automatically find best threshold and max time when you use the first shortcut (only on clean installs)
Get it at: https://play.google.com/store/apps/details?id=com.danilomendes.powy
So now, hopefully, all issues should be resolved and the app becomes more flexible because you can configure the settings for each device and to your needs.
Tell me what you think about this new release and rate as you think it's fit
Thank you all for the feedback it was really helpful.
Cumps
Took a little playing with it, but the flashlight is now working for me, thanks!
overcoded said:
Took a little playing with it, but the flashlight is now working for me, thanks!
Click to expand...
Click to collapse
That's good to hear
Thanks for replying back
Hi guys,
Just wanted you to know that Powy now allows you to use Tasker Tasks through the power button. This is now available on version 1.1.0. I think that now by using Powy combined with Tasker you have a lot of flexibility customizing shortcuts on your power button.
For example, now you can add a task on Tasker that turns WiFi on/off and then fire it using your power button through Powy.
Give it a try and tell me what you think
Powy: https://play.google.com/store/apps/details?id=com.danilomendes.powy
Tasker: https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm
Night Light
aka Simple Night Shift
Now in Material Design
An app that do simple editing of KCAL value for our smartphone in order to get night mode back.
This app changes the three RGB value in KCAL file under /sys/devices/platforn/kcal_ctrl.0
REQUISITES:
- A custom kernel that support and use kcal for display colors ( qualcomm devices with MDSS as stated in savoca's thread )
- Root Permission (haven't checked with magisk because i don't use so tell me if it works)
MAIN FEATURE:
- No background processes
- No memory or battery consumption
- Simple slider selection of RGB Value
- Quick settings toggle tile
INSTRUCTIONS:
Open the app , grant superuser Permission then choose the RGB values and refresh with refresh FAB
Click On/Off toggle for enable/disable
Add quick settings toggle for fast On/Off.
P.P.S.: I have tested this app only with stock android OREO and ElementalX kernel so don't guarantee that work with other kernel/roms, if you have doubt try it and tell me if it works, a reboot simple reset this value so don't be shy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG:
V4.0
- Complete rebuilt from scratch with android Studio and material design (no more tasker or appfactory)
- About 8'000'000'000X faster opening and color application
- Real interface with real button
- New icon
- No longer necessary Boot/Read external storage permission
Older Version Changelog:
V2.0
- Initial release
V2.1 - Try to fix FC on startup
- Fixed inconsistent value if never set at least one time
- Fixed save button don't working if not long pressed
- Speed up app opening
- Removed some SU request after first open
- Added minimum value security block to avoid black screen
- Improved some routine
V2.2 UNINSTALL 2.1 BEFORE INSTALL 2.2
- Reverted some wrong changes
V3.0.1
- Fixed FC at startup
- Fixed value stick after reboot
- Fixed wrong SU request
- Now saving some preferences to stick after reboot
- Clean up redundant command
Enjoy! and don't miss the thanks button
Awesome thanks! Could you fix your link though? There's nothing in the folder when I click on the link.
DELETED
This is awesome, thank you! Would you mind sharing your Tasker project? I'd like to be able to toggle night mode with Tasker.
I am trying to use but it not functional. Something I miss?
Edit: Fixed by giving Massages storage permissions.
I tested a little bit the app and then the toggle stopped working
AFK269 said:
I am trying to use but it not functional. Something I miss?
Edit: Fixed by giving Massages storage permissions.
I tested a little bit the app and then the toggle stopped working
Click to expand...
Click to collapse
Hi, can you please explain me what you tested in order to make toggle useless? i have tested ths for a week and the toggle never stopped working, your signature tell that you are unrooted, is right? you have the latest apk attached on the post? if yes can you please attach the kcal file under Night folder in your storage, thanks
moddroid said:
Hi, can you please explain me what you tested in order to make toggle useless? i have tested ths for a week and the toggle never stopped working, your signature tell that you are unrooted, is right? you have the latest apk attached on the post? if yes can you please attach the kcal file under Night folder in your storage, thanks
Click to expand...
Click to collapse
I have the latest 2.0. I gived permissions to mass storage and gived root permissions with Magisk Root. I played with colours to give the correct colour (this yellowish tint that have also pixel devices ) and after that toggle stopped working and when I try to change, I press the and I try to enable with toggle and nothing happens
yochananmarqos said:
This is awesome, thank you! Would you mind sharing your Tasker project? I'd like to be able to toggle night mode with Tasker.
Click to expand...
Click to collapse
I really don't understand this request, why use tasker when this app as no background processes and a simple QS tile? anyway, yes i can share but remember : this app don't enable night mode, only change display rgb value , the end user set this value, more you lower the blue and the green value more reddish your display is , so don't expect a simple toggle for night mode under some settings. i provide a link as soon as possible
AFK269 said:
I have the latest 2.0. I gived permissions to mass storage and gived root permissions with Magisk Root. I played with colours to give the correct colour (this yellowish tint that have also pixel devices ) and after that toggle stopped working and when I try to change, I press the and I try to enable with toggle and nothing happens
Click to expand...
Click to collapse
hmm, strange, please open the kcal file under Night folder in your storage and write here the value inside the file, or try to press the refresh button in the right side of header before close app
Anyway i didn't tried with magisk so i don't know if can depend on this.
moddroid said:
hmm, strange, please open the kcal file under Night folder in your storage and write here the value inside the file, or try to press the refresh button in the right side of header before close app
Anyway i didn't tried with magisk so i don't know if can depend on this.
Click to expand...
Click to collapse
0 58 77
moddroid said:
I really don't understand this request, why use tasker when this app as no background processes and a simple QS tile? anyway, yes i can share but remember : this app don't enable night mode, only change display rgb value , the end user set this value, more you lower the blue and the green value more reddish your display is , so don't expect a simple toggle for night mode under some settings. i provide a link as soon as possible
Click to expand...
Click to collapse
Automation, that's why. Also I want to peek under the hood.
There's a few issues with the app. It app force-closes on startup. Look of Disapproval does the same thing and so did Custom Quick Settings until the dev updated it. I'll try and grab a logcat. It's something to do with Android Oreo, but I'm not sure what.
The app only opened right away on first run, now I have to tap it, wait until MagiskSU grants su permissions a couple times, then tap the Quick Setting tile and then it will open. It does not apply unless I tap the icon in the upper right that looks like a refresh icon or tap the tile again so it's "off", then tap it again to turn it "on".
AFK269 said:
0 58 77
Click to expand...
Click to collapse
The values are right , the app have stopped to work after some time or not worked at all? Have you the stock kernel? i think it's something related to magisk, but i don't have soo much time for checking it right now
yochananmarqos said:
Automation, that's why. Also I want to peek under the hood.
There's a few issues with the app. It app force-closes on startup. Look of Disapproval does the same thing and so did Custom Quick Settings until the dev updated it. I'll try and grab a logcat. It's something to do with Android Oreo, but I'm not sure what.
The app only opened right away on first run, now I have to tap it, wait until MagiskSU grants su permissions a couple times, then tap the Quick Setting tile and then it will open. It does not apply unless I tap the icon in the upper right that looks like a refresh icon or tap the tile again so it's "off", then tap it again to turn it "on".
Click to expand...
Click to collapse
New Update try to solve some problems, waiting feedback ?
moddroid said:
New Update try to solve some problems, waiting feedback ?
Click to expand...
Click to collapse
Stopped working. 2-3 times I changed values to give the right colour and stopped working.
AFK269 said:
Stopped working. 2-3 times I changed values to give the right colour and stopped working.
Click to expand...
Click to collapse
Sorry my fault, wrong fix, updating right one. Uninstall v2.1 and delete Night folder
moddroid said:
Sorry my fault, wrong fix, updating right one. Uninstall v2.1 and delete Night folder
Click to expand...
Click to collapse
I reverted back to stock kernel so I can't test it now. Due to some tweaks to the kernel.
I cant go to 0 to use 0-58-77
Until 30 goes
Anyone use other setting?
noolis said:
I cant go to 0 to use 0-58-77
Until 30 goes
Anyone use other setting?
Click to expand...
Click to collapse
There's a security block to 30.
Why? Because if you accidentally put everything to 0 your screen become totally black, and the only way to restore is via adb or recovery, so i suggest never use value under 30, for a good results i use: Red-255 Green-160 blue-100. ?
Works amazingly on a Moto G4 Plus XT1641 with ElementalX Kernel. Thanks.
Now it works great.
What is SideSqueeze?
SideSqueeze is an innovative and unique app that uses the barometric pressure sensor in your device to detect squeezes and screen presses. It is compatible only with Samsung Galaxy devices from 2017 onwards, although some people have reported varying degrees of success with Pixel devices.
What It Does
SideSqueeze gives your S8/S9/S10 series Galaxy the ability to respond to squeezes, double squeezes, triple squeezes, quadruple squeezes, long squeezes, and/or inertial squeezes, as well as force presses on the screen. For example, you can double squeeze your phone to activate Google Assistant...or maybe you'd like to quadruple squeeze to toggle auto-rotation. And now with Tasker integration, you can even create elaborate tasks to do just about anything and trigger them with any type of squeeze! SideSqueeze's new modular GUI allows you to pick and choose what you want to do with ease.
Features (not all available in trial version)
7 detectable squeeze types (single, double, triple, quadruple, long, long double-squeeze, and inertial)
3 detectable press types (single, long, and 2-finger)
Independently selectable criteria allow you to assign multiple actions to any trigger type (if lockscreen open, if homescreen open, if camera open, if S-Pen detached, if within 5-seconds of power on, if the phone is ringing, if in-call, or if screen is off)
New app picker to launch any app of your choosing
Tasker integration to launch any task of your choosing
Quick Settings tile to toggle detection engine
Wide selection of common actions, such as flashlight toggling, status bar toggling, etc
Adjustable pressure thresholds
Calibration assistant to customize SideSqueeze to your device's unique characteristics
Efficient detection algorithm that is designed to be as lightweight and low-power as possible with no significant impact on battery life
Questions?
See the in-app Help section for answers to commonly asked questions.
Where do I get it?
SideSqueeze 2 is now available on the Play store!
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I like the concept of the app but I tried it and it is very difficult to use coming from a pixel device. I set up custom squeeze pressures but it won't work properly. A squeeze will usually engage what I want but if I move phone around or sit it down it will also do the squeeze action. Good idea but going to be tough to do properly i feel!
oneandroidnut said:
I like the concept of the app but I tried it and it is very difficult to use coming from a pixel device. I set up custom squeeze pressures but it won't work properly. A squeeze will usually engage what I want but if I move phone around or sit it down it will also do the squeeze action. Good idea but going to be tough to do properly i feel!
Click to expand...
Click to collapse
Thank you for your feedback. Have you calibrated it? What are your gain and release threshold set to? What sensitivity level are you using?
ffolkes said:
Thank you for your feedback. Have you calibrated it? What are your gain and release threshold set to? What sensitivity level are you using?
Click to expand...
Click to collapse
I did it kept saying try again and changed values, said like 50 try again then 100 then -10 and kept saying try again. It was really odd
Same here.... S10+..... Seems difficult to get out of the calibration stage. Then, sometimes the squeeze works and sometimes it does not. I also see calibration messages after exiting the app.
Interestingly, the squeeze command seems to always work when in the app.
When I retried to calibrate with a squeeze command already set, the command activated and the assigned app launched.
Will try to play with it again later.
Sent from my SM-G975U using Tapatalk
Now I am getting a notification that side squeeze is running. However, I have had it disabled in the app!
Sent from my SM-G975U using Tapatalk
dctrbnsttr said:
Same here.... S10+..... Seems difficult to get out of the calibration stage. Then, sometimes the squeeze works and sometimes it does not. I also see calibration messages after exiting the app. Interestingly, the squeeze command seems to always work when in the app.
When I retried to calibrate with a squeeze command already set, the command activated and the assigned app launched.
Will try to play with it again later.
Click to expand...
Click to collapse
This is really weird, and no one has ever reported behavior like this. I can't seem to reproduce it. Was there any step that stood out in your mind? Did you do anything unusual? Do you remember roughly what the message said? There are only a few it could have been, any words or phrases you remember from it? Thanks!
The time you tried to calibrate with a command set, did you remember if you tapped the "Start" button at the bottom first?
dctrbnsttr said:
Now I am getting a notification that side squeeze is running. However, I have had it disabled in the app!
Click to expand...
Click to collapse
Is it possible you have the press detection module on? The engine stays running unless both are disabled. Open the left fly-out menu and go to Screen Presses and make sure that is off, too.
ffolkes said:
This is really weird, and no one has ever reported behavior like this. I can't seem to reproduce it. Was there any step that stood out in your mind? Did you do anything unusual? Do you remember roughly what the message said? There are only a few it could have been, any words or phrases you remember from it? Thanks!
The time you tried to calibrate with a command set, did you remember if you tapped the "Start" button at the bottom first?
Is it possible you have the press detection module on? The engine stays running unless both are disabled. Open the left fly-out menu and go to Screen Presses and make sure that is off, too.
Click to expand...
Click to collapse
Unfortunately, I don't recall the text of the toast message. Yes, I clicked on the start button to calibrate. As far as I know, I did nothing unusual. Press screen was turned off.
I just now opened the app, made sure that both screen pressure and squeeze were not enabled. After exiting the app, there is a notification that sidesqueeze is running.
Also, there is an issue with the discord server. I have to open the sidesqueeze app and click on the discord link to open it. I accept the invite. 5 minutes later, the server disappears from the discord app. When I tried to join again thru the discord app, it states that the invite has expired. This is repeatable.
Sent from my SM-G975U using Tapatalk
I got working a little bit, took literally 5 mins to setup though. It's hit or miss now though works maybe 50% of the time and still sometimes randomly
I deleted cache and data. I installed the new test version you sent. It seems to be much more stable and working as it should. I will give it more time to see if all remains well.
Sent from my SM-G975U using Tapatalk
This is new and useful for S10+! Nice app my man! Thanks!
After using the new build a bit more, a couple of observations. First, the action set for one squeeze, sometimes activates without me squeezing the phone. Secondly, with sidesqueeze activated and the press actions definitely switched off, I can no longer double tap to wake my s10+. As soon as I deactivate sideswitch, double tap to wake is restored.
Sent from my SM-G975U using Tapatalk
---------- Post added at 08:55 PM ---------- Previous post was at 08:29 PM ----------
Also, unfortunately, the notification that sidesqueeze is running even when neither squeeze or press is enabled, is back...... This after the playstore update to version 201.
Sent from my SM-G975U using Tapatalk
dctrbnsttr said:
After using the new build a bit more, a couple of observations. First, the action set for one squeeze, sometimes activates without me squeezing the phone. Secondly, with sidesqueeze activated and the press actions definitely switched off, I can no longer double tap to wake my s10+. As soon as I deactivate sideswitch, double tap to wake is restored.
---------- Post added at 08:55 PM ---------- Previous post was at 08:29 PM ----------
Also, unfortunately, the notification that sidesqueeze is running even when neither squeeze or press is enabled, is back...... This after the playstore update to version 201.
Click to expand...
Click to collapse
I have no idea about the double tap thing, I'll have to look into it. As for the notification, when does it come back?
The double tap may have had something to do with the aod..... The notification returned after I rebooted the phone.
Sent from my SM-G975U using Tapatalk
dctrbnsttr said:
The double tap may have had something to do with the aod..... The notification returned after I rebooted the phone.
Click to expand...
Click to collapse
Oh ok, that's actually fixed in the last minute update I pushed out moments after 2.01. It should be rolling out to you any minute now.
I have been noticing that if I set the squeeze strength to custom rather than to soft or medium for example, sidesqueeze resets itself to medium.
Sent from my SM-G975U using Tapatalk
dctrbnsttr said:
I have been noticing that if I set the squeeze strength to custom rather than to soft or medium for example, sidesqueeze resets itself to medium.
Click to expand...
Click to collapse
Thanks for the feedback, as always. Can you reproduce this? When does it happen? Like, does it only reset when the app opens? What were you doing before it reset? Is 'Firm' affected, too?
ffolkes said:
Thanks for the feedback, as always. Can you reproduce this? When does it happen? Like, does it only reset when the app opens? What were you doing before it reset? Is 'Firm' affected, too?
Click to expand...
Click to collapse
Can't pinpoint any specific event or time. Haven't used firm at all. Also noticing that sometimes it seems overly sensitive and other times it won't respond at all. I will try to notice when these things occur.
Sent from my SM-G975U using Tapatalk
Version 2.04 is ready for testing:
Improvements to the algorithm
More responsive
Added Long Double-Squeeze
Multi-squeeze delay is now adjustable
Fixed bug in Quadruple Squeeze
UI improvements and fixes
Crash fixes
Download
Trying it out.... Will see how it goes
Has been running for an hour or so.... Seems much more consistent and stable thus far....
Sent from my SM-G975U using Tapatalk