HallMonitor
HallMonitor copied to clipboard
durka
Feature request: support for different sized views
Right now, the app seems to be calibrated specifically for the "Samsung Galaxy S4" as advertised.
This app does work wonderfully with the Note 3, but the opening in the Note 3's s-view is larger than the opening in the S4's s-view, so there's quite a lot of space in the bottom half of the opening when the app activates.
I was hoping a setting to change the view's width, height, and position could be implemented.
Also, if possible, a way to change the position of widgets would be amazing.
I second this request. Especially for using the camera with the cover closed, it's quite ridiculous. If it helps, the Note S-View covers have a square window with the height being the same as the current working width.
added functionality to arrange view size and position
- zoom: scale between 1 and 1.5 for width and height
- slide: change vertical position +/-50
the gestures doesn't not work very well. but in my opion this is acceptable, because we don't need it so often.
So this is interesting. It works to scale a bit but without changing the aspect ratio there's always cut off on the sides and it still doesn't fill the note 3 s view cover which is square not rectangular. I appreciate the effort and am using this version for now, I uninstalled the other.
Actually one issue is it's not reading my battery life. Says 100% now no matter what. Must've been what it was when I installed it or something
check the notifications enable option. had have trouble to enable it without reboot. newer version with logcat output improvements is available. aspect ratio is fix for now. i can't do seriously testing without adequate hardware.
Sorry I did try that and again with the link you put in your last reply but it seems to be the same.. I cannot make it square, it remains a rectangle and doesn't fill the note 3 s view window vertically when made as big as possible and the sides get cut off. Also same problem with the notifications not working and the battery indicates 100% when it's not
And I did reboot after enabling notifications and it didn't make a difference
for a reason i'm not overlooking by now, i was unable to enable notifications. all the time i changed it remains disabled. this strange behavior was solved by reboot.
battery: can you post a logcat output incl. some cover actions (open and close)? aspect ratio: can you post a photo with closed cover and the resize option layout in action? maybe i'm makeing a special version for testing. i don't know what's happend with customizable ascept ratio.
Oic. Yes I had that problem where the notification toggle didn't stick when I installed the text over the official but yes a reboot did fix that. It isn't an issue if you uninstall and reinstall.
Here are the attached log files and I was able to screen capture some stuff for you including how my battery isn't 100% despite HallMonitor saying so lol. Even without me using an external camera to show what the cover looks like you can obviously see the edges of the app are way too close to the left and right sides of the screen. The s view cover for the S4 and the one I have for the note have the same width window requiring the same gap between the left and right sides. And in your official app the position is all the way at the top of my note s view window. I just wanted to extend the bottom down so it fills the entire s view window which is square. And even with this test where I can scale it as much as it will go it doesn't fill the window. I need the app to be a square view not a rectangular view.
On Sep 28, 2016 9:19 AM, "habeIchVergessen" [email protected] wrote:
for a reason i'm not overlooking by now, i was unable to enable notifications. all the time i changed it remains disabled. this strange behavior was solved by reboot.
battery: can you post a logcat output incl. some cover actions (open and close)? aspect ratio: can you post a photo with closed cover and the resize option layout in action? maybe i'm makeing a special version for testing. i don't know what's happend with customizable ascept ratio.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/durka/HallMonitor/issues/50#issuecomment-250163781, or mute the thread https://github.com/notifications/unsubscribe-auth/APE4ch2FUPkJbUhOEu73cPRL5BhFgEoUks5qumlGgaJpZM4CkVRR .
---- Sep 28, 2016 9:37:36 AM ----
09-28 09:31:36.152 999 999 I ActivityManager: Start proc 2417:org.durka.hallmonitor_framework_test/u0a259 for service org.durka.hallmonitor_framework_test/.NotificationService
09-28 09:35:13.511 999 2517 I ActivityManager: START u0 {act=android.intent.action.MAIN flg=0x14890000 cmp=org.durka.hallmonitor_framework_test/.ComponentTestActivity} from uid 10259 on display 0
09-28 09:35:13.869 999 1084 I ActivityManager: Displayed org.durka.hallmonitor_framework_test/.ComponentTestActivity: +275ms
09-28 09:35:51.820 999 1567 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.durka.hallmonitor_framework_test/.ComponentTestPreferences (has extras)} from uid 10022 on display 0
09-28 09:35:52.114 999 1084 I ActivityManager: Displayed org.durka.hallmonitor_framework_test/.ComponentTestPreferences: +238ms
09-28 09:35:57.827 999 1599 I ActivityManager: START u0 {act=android.intent.action.VIEW cmp=org.durka.hallmonitor_framework_test/.ComponentTestActivity (has extras)} from uid 10259 on display 0
09-28 09:35:57.911 999 1084 I ActivityManager: Displayed org.durka.hallmonitor_framework_test/.ComponentTestActivity: +72ms
09-28 09:36:13.656 999 1485 I ActivityManager: START u0 {act=org.durka.hallmonitor.restartFrameworkTest cmp=org.durka.hallmonitor_framework_test/.ComponentTestActivity} from uid 10259 on display 0
09-28 09:36:13.730 999 1084 I ActivityManager: Displayed org.durka.hallmonitor_framework_test/.ComponentTestActivity: +59ms
09-28 09:36:19.405 999 2469 I ActivityManager: START u0 {act=android.intent.action.VIEW cmp=org.durka.hallmonitor_framework_test/.ComponentTestActivity (has extras)} from uid 10259 on display 0
09-28 09:36:19.507 999 1084 I ActivityManager: Displayed org.durka.hallmonitor_framework_test/.ComponentTestActivity: +85ms
09-28 09:36:31.791 999 2509 I ActivityManager: START u0 {act=org.durka.hallmonitor.restartFrameworkTest cmp=org.durka.hallmonitor_framework_test/.ComponentTestActivity} from uid 10259 on display 0
09-28 09:36:31.904 999 1084 I ActivityManager: Displayed org.durka.hallmonitor_framework_test/.ComponentTestActivity: +96ms
09-28 09:36:34.827 999 2625 I ActivityManager: START u0 {act=org.durka.hallmonitor.restartFrameworkTest cmp=org.durka.hallmonitor_framework_test/.ComponentTestActivity} from uid 10259 on display 0
09-28 09:36:34.900 999 1084 I ActivityManager: Displayed org.durka.hallmonitor_framework_test/.ComponentTestActivity: +58ms
09-28 09:36:58.346 999 2956 I ActivityManager: START u0 {act=android.intent.action.MAIN flg=0x14890000 cmp=org.durka.hallmonitor_framework_test/.ComponentTestActivity} from uid 10259 on display 0
09-28 09:36:58.600 999 1084 I ActivityManager: Displayed org.durka.hallmonitor_framework_test/.ComponentTestActivity: +128ms
09-28 09:37:05.097 999 1567 I ActivityManager: START u0 {act=android.intent.action.MAIN flg=0x14890000 cmp=org.durka.hallmonitor_framework_test/.ComponentTestActivity} from uid 10259 on display 0
09-28 09:37:05.413 999 1084 I ActivityManager: Displayed org.durka.hallmonitor_framework_test/.ComponentTestActivity: +186ms
09-28 09:37:08.933 999 2956 I ActivityManager: START u0 {act=android.intent.action.MAIN flg=0x14890000 cmp=org.durka.hallmonitor_framework_test/.ComponentTestActivity} from uid 10259 on display 0
09-28 09:37:09.144 999 1084 I ActivityManager: Displayed org.durka.hallmonitor_framework_test/.ComponentTestActivity: +122ms
---- Sep 28, 2016 9:37:36 AM ----
debug my fork:
- press seven times About ("debug enabled" messages appears)
- do some cover actions
- check the sd-card option
- press seven times About ("debug disabled" message)
- new file should be written to Download
the file contains informations like this:
hardware: samsung GT-I9506 (ks01lte) build: 12.1-20150928-UNOFFICIAL-temasek-ks01lte os: LMY48P test-keys (Dalvik) kernel: 3.4.109-arter97-9.0-g051a6c4-02029-g964e6eb
apk: file: base.apk (/data/app/org.durka.hallmonitor_framework_test-1) package: org.durka.hallmonitor_framework_test md5: 0c298281dc7619ffa9b3707862bafc9b build: Sun Sep 27 13:50:04 MESZ 2015 cert: CN=habeIchVergessen,OU=privat,O=privat (serial: 63491813) version: 1.0.0 (Framework Test) (10) install: Sat Oct 31 13:57:53 MEZ 2015 (Sat Oct 31 13:57:53 MEZ 2015)
preferences: pref_default_fgcolor = '-1' pref_runasroot = 'true' pref_phone_controls = 'true' pref_write_logcat_output = 'true' pref_default_widget = 'false' pref_dev_opts_debug = 'true' pref_default_bgcolor = '-16777216' pref_dim = 'true' pref_phone_controls_user = 'true' pref_delay = '10000' version = '10' pref_do_notifications = 'true' prefDefaultLayoutClassName = '' pref_media_widget = 'false' pref_enabled = 'true'
11-01 18:53:59.299 I/Timeline(32306): Timeline: Activity_idle id: android.os.BinderProxy@316127d time:30480002 11-01 18:54:12.034 D/SKP (32306): SDD called, mValue = 10000, super = false 11-01 18:54:31.833 I/Timeline(32306): Timeline: Activity_idle id: android.os.BinderProxy@10b975e time:30512535 11-01 18:54:57.432 I/Timeline(32306): Timeline: Activity_idle id: android.os.BinderProxy@10b975e time:30538134 11-01 18:55:00.399 D/PreferenceFragmentLoader-oSPC(32306): changed key pref_dev_opts_debug 11-01 18:55:00.410 D/PreferenceFragmentLoader-oSPC(32306): changed key pref_write_logcat_output 11-01 18:55:00.410 D/PreferenceFragmentLoader-oSPC(32306): toggling check box 11-01 18:55:09.920 D/PreferenceFragmentLoader(32306): onPause: 11-01 18:55:19.440 D/PreferenceFragmentLoader(32306): onResume: 11-01 18:55:19.441 D/PreferenceFragmentLoader(32306): versionCode = 10 11-01 18:55:19.504 I/Timeline(32306): Timeline: Activity_idle id: android.os.BinderProxy@10b975e time:30560207
actually we have default width with 315dp and height with 125dp (see dimens.xml). with max. scale we get 472x187 dp. all layouts are tested with this aspect ratio. latest version enables square format (width=height; scale between 0,75 and 1,5) via menu entry.
please report test results
Damn. The debug isn't saving to download.. I'll keep trying.
On Sep 28, 2016 3:52 PM, "habeIchVergessen" [email protected] wrote:
debug my fork:
- press seven times About ("debug enabled" messages appears)
- do some cover actions
- check the sd-card option
- press seven times About ("debug disabled" message)
- new file should be written to Download
the contains informations like this: hardware: samsung GT-I9506 (ks01lte) build: 12.1-20150928-UNOFFICIAL-temasek-ks01lte os: LMY48P test-keys (Dalvik) kernel: 3.4.109-arter97-9.0-g051a6c4-02029-g964e6eb
apk: file: base.apk (/data/app/org.durka.hallmonitor_framework_test-1) package: org.durka.hallmonitor_framework_test md5: 0c298281dc7619ffa9b3707862bafc9b build: Sun Sep 27 13:50:04 MESZ 2015 cert: CN=habeIchVergessen,OU=privat,O=privat (serial: 63491813) version: 1.0.0 (Framework Test) (10) install: Sat Oct 31 13:57:53 MEZ 2015 (Sat Oct 31 13:57:53 MEZ 2015)
preferences: pref_default_fgcolor = '-1' pref_runasroot = 'true' pref_phone_controls = 'true' pref_write_logcat_output = 'true' pref_default_widget = 'false' pref_dev_opts_debug = 'true' pref_default_bgcolor = '-16777216' pref_dim = 'true' pref_phone_controls_user = 'true' pref_delay = '10000' version = '10' pref_do_notifications = 'true' prefDefaultLayoutClassName = '' pref_media_widget = 'false' pref_enabled = 'true'
11-01 18:53:59.299 I/Timeline(32306): Timeline: Activity_idle id: android.os.BinderProxy@316127d https://github.com/android.os.BinderProxy/HallMonitor/commit/316127d time:30480002 11-01 18:54:12.034 D/SKP (32306): SDD called, mValue = 10000, super = false 11-01 18:54:31.833 I/Timeline(32306): Timeline: Activity_idle id: android.os.BinderProxy@10b975e https://github.com/android.os.BinderProxy/HallMonitor/commit/10b975e time:30512535 11-01 18:54:57.432 I/Timeline(32306): Timeline: Activity_idle id: android.os.BinderProxy@10b975e https://github.com/android.os.BinderProxy/HallMonitor/commit/10b975e time:30538134 11-01 18:55:00.399 D/PreferenceFragmentLoader-oSPC(32306): changed key pref_dev_opts_debug 11-01 18:55:00.410 D/PreferenceFragmentLoader-oSPC(32306): changed key pref_write_logcat_output 11-01 18:55:00.410 D/PreferenceFragmentLoader-oSPC(32306): toggling check box 11-01 18:55:09.920 D/PreferenceFragmentLoader(32306): onPause: 11-01 18:55:19.440 D/PreferenceFragmentLoader(32306): onResume: 11-01 18:55:19.441 D/PreferenceFragmentLoader(32306): versionCode = 10 11-01 18:55:19.504 I/Timeline(32306): Timeline: Activity_idle id: android.os.BinderProxy@10b975e https://github.com/android.os.BinderProxy/HallMonitor/commit/10b975e time:30560207
actually we have default width with 315dp and height with 125dp (see dimens.xml). with max. scale we get 472x187 dp. all layouts are tested with this aspect ratio. latest version enables square format (width=height; scale between 0,75 and 1,5) via menu entry.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/durka/HallMonitor/issues/50#issuecomment-250280348, or mute the thread https://github.com/notifications/unsubscribe-auth/APE4coEPv3rkkP3WJjO1SuQL1O0ljebfks5qusWIgaJpZM4CkVRR .
I tried it. I like the default better but they both behave the same in that neither cover the whole sview window.
On Oct 2, 2016 6:17 PM, "habeIchVergessen" [email protected] wrote:
Do you use custom 1 as default layout?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/durka/HallMonitor/issues/50#issuecomment-251000000, or mute the thread https://github.com/notifications/unsubscribe-auth/APE4cuJS4r5DPz5oxL07b-mQA-lFerjsks5qwC2KgaJpZM4CkVRR .
The notifications work in the custom layout tho.
On Oct 2, 2016 6:22 PM, "Billy Votta" [email protected] wrote:
I tried it. I like the default better but they both behave the same in that neither cover the whole sview window.
On Oct 2, 2016 6:17 PM, "habeIchVergessen" [email protected] wrote:
Do you use custom 1 as default layout?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/durka/HallMonitor/issues/50#issuecomment-251000000, or mute the thread https://github.com/notifications/unsubscribe-auth/APE4cuJS4r5DPz5oxL07b-mQA-lFerjsks5qwC2KgaJpZM4CkVRR .
battery update works for custom 1?
Am 03.10.2016 00:22 schrieb "pelo88" [email protected]:
I tried it. I like the default better but they both behave the same in that neither cover the whole sview window.
On Oct 2, 2016 6:17 PM, "habeIchVergessen" [email protected] wrote:
Do you use custom 1 as default layout?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/durka/HallMonitor/issues/50#issuecomment-251000000, or mute the thread <https://github.com/notifications/unsubscribe- auth/APE4cuJS4r5DPz5oxL07b-mQA-lFerjsks5qwC2KgaJpZM4CkVRR> .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/durka/HallMonitor/issues/50#issuecomment-251000254, or mute the thread https://github.com/notifications/unsubscribe-auth/ADzcGn1-_hii_PX04QjLo_3AWTBRm9Mrks5qwC7CgaJpZM4CkVRR .
Seems stuck at 100% still
On Oct 2, 2016 6:26 PM, "habeIchVergessen" [email protected] wrote:
battery update works for custom 1?
Am 03.10.2016 00:22 schrieb "pelo88" [email protected]:
I tried it. I like the default better but they both behave the same in that neither cover the whole sview window.
On Oct 2, 2016 6:17 PM, "habeIchVergessen" [email protected] wrote:
Do you use custom 1 as default layout?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/durka/HallMonitor/issues/50#issuecomment-251000000 , or mute the thread <https://github.com/notifications/unsubscribe- auth/APE4cuJS4r5DPz5oxL07b-mQA-lFerjsks5qwC2KgaJpZM4CkVRR> .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/durka/HallMonitor/issues/50#issuecomment-251000254, or mute the thread <https://github.com/notifications/unsubscribe- auth/ADzcGn1-_hii_PX04QjLo_3AWTBRm9Mrks5qwC7CgaJpZM4CkVRR> .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/durka/HallMonitor/issues/50#issuecomment-251000457, or mute the thread https://github.com/notifications/unsubscribe-auth/APE4cpp1wLh9rZOoYazyAlft0pgP3rOlks5qwC-lgaJpZM4CkVRR .
Actually in that layout the battery does work but the number % doesn't show so it wasn't that clear until I lost more battery.
On Oct 2, 2016 6:52 PM, "Billy Votta" [email protected] wrote:
Seems stuck at 100% still
On Oct 2, 2016 6:26 PM, "habeIchVergessen" [email protected] wrote:
battery update works for custom 1?
Am 03.10.2016 00:22 schrieb "pelo88" [email protected]:
I tried it. I like the default better but they both behave the same in that neither cover the whole sview window.
On Oct 2, 2016 6:17 PM, "habeIchVergessen" [email protected] wrote:
Do you use custom 1 as default layout?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/durka/HallMonitor/issues/50#issuecomment -251000000>, or mute the thread <https://github.com/notifications/unsubscribe- auth/APE4cuJS4r5DPz5oxL07b-mQA-lFerjsks5qwC2KgaJpZM4CkVRR> .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/durka/HallMonitor/issues/50#issuecomment-251000254 , or mute the thread <https://github.com/notifications/unsubscribe-auth/ADzcGn1-_ hii_PX04QjLo_3AWTBRm9Mrks5qwC7CgaJpZM4CkVRR> .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/durka/HallMonitor/issues/50#issuecomment-251000457, or mute the thread https://github.com/notifications/unsubscribe-auth/APE4cpp1wLh9rZOoYazyAlft0pgP3rOlks5qwC-lgaJpZM4CkVRR .