Related
Hello guys! Some of you may have participated in the beta of Killswitch, our app for tablets and phones with cases that turns off the screen whenever the case is shut.
We need some feedback from people running roms on thier Galaxy Tabs. Could those of you that participated please leave some comments and thoughts on improving the app's functionality?
We have just released a major update that should solve some sensitivity issues and wonder if this has affected users, and its very hard to get constructive feedback from the market.
Works much better for me - seems to have fewer false turnoffs
[RUS] Последняя версия работает значительно лучше — гораздо меньше ложных срабатываний [/RUS]
We are trying to improve this... could you please try setting a higher Activation Delay value so that we can test what kind of effect this has?
Its possible this very rough filtering will be very useful in certain conditions!
Did it help?
well? its so annoying when people on a forum like this one don't provide technical feedback...
I bought the application but every time the display decrease brigtness (for battery reason), kilswitch ask to go on standby.
Please solve it.
Sent from my GT-P1000 using Tapatalk
Hi, could you be more specific? Please send a logcat!
Tick "debug mode" then run aLogcat from the market, reproduce the error and send me the text from aLogcat.
Ill be looking into some major changes to killswitch next week, so nows a good time to give tech feedback and suggestions!
Guys, im almost done with the extra functions, so now would bve a good time to send those logcats you were telling me about!
I will volunteer to help as soon as I get my cover LOL (got one on the way from ebay). cheers looks very nice can't wait to try it out.
Looks interesting but I see you don't have a trial version on the Market and with Google's policy of only 15 minutes return I am reluctant to spend over £2 on something I can't test properly.
We now have a trial version, with almost all features included!
norm2002 said:
Looks interesting but I see you don't have a trial version on the Market and with Google's policy of only 15 minutes return I am reluctant to spend over £2 on something I can't test properly.
Click to expand...
Click to collapse
same here, would love to test, but not gonna pay to test for you. would buy later if it was something I liked. i do like the idea, . . . . .
Guys, there is a demo version on the market you know - im not asking anyone to pay!
https://market.android.com/details?id=fahrbot.apps.killswitchlite
ftgg99 said:
Guys, there is a demo version on the market you know - im not asking anyone to pay!
https://market.android.com/details?id=fahrbot.apps.killswitchlite
Click to expand...
Click to collapse
Webpage not available
Sent from my GT-P1000 using XDA App
Try https://market.android.com/details?id=fahrbot.apps.killswitchlite&feature=more_from_developer
The market is quirky...
Also https://market.android.com/details?...locker.beta&feature=more_from_developer&hl=en
And search for fahrbot.apps.killswitchlite
I tried this. Doesn't seem to work on my tab. I closed the cover on my case and nothing happened. Also can't seem to uninstall which I find annoying.
Sent from my GT-P1000 using Tapatalk
cbb77 said:
I tried this. Doesn't seem to work on my tab. I closed the cover on my case and nothing happened. Also can't seem to uninstall which I find annoying.
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Same here. Also startup randomly.
The trial version limits the minimum shutdown time to 23 seconds, which is why it didnt seem to do anything.
In order to uninstall you have to uncheck admin permissions, as it says in the OP, the help file and the relevant setting item.
It starts randomly when sensitivity is too high and when your Activation delay is very low. Read the help.
Video calling was working just fine on my XOOM until the above update so.....has anyone got an APK for the previous version that they could possibly link me to?
I dunno if anyone else uses it but today when we tried to call my dad, the XOOM just locked up and was locked in the call with black video window. Very frustrating and my daughter really wanted to see her grandad.
So, any help greatly appreciated. ;-)
This version is pretty old but its the only one that works problem free on my Nexus One
dl.dropbox.com/u/132570/android/apps/Skype_2.0.0.47.apk
mcnob said:
Video calling was working just fine on my XOOM until the above update ... I dunno if anyone else uses it
Click to expand...
Click to collapse
Funny you say that, 'cause about an hour after the update I made a ~10-minute Video call to Israel (and one later within Cali, a lot less interesting ) and it worked flawlessly, w/o even any sync or lag issues.
Did you try rebooting? I'm rooted and overclocked, but I suspect that's had very little to do with my good performance.
Well i managed to track down 2.5.0.160 which seems to be the one i had prior to the issues and all is well again.
Thanks for responding guys.
Sent from my Optimus 2X using XDA App
mcnob said:
Well i managed to track down 2.5.0.160 which seems to be the one i had prior to the issues and all is well again.
Thanks for responding guys.
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
I have the same problem with my Galaxy S WIFI 5.0. After update, the front/back camera is upside down.
Can place the apk somewhere accessible on the internet? Many many thanks.
Literally 5 threads down in this very forum is exactly what you seek.
Really, guys...
....................deleted
sodaboy581 said:
Literally 5 threads down in this very forum is exactly what you seek.
Really, guys...
Click to expand...
Click to collapse
Yeh, it's a shame the OP of that one didn't search first...eh? What with this one being dated prior to that one and all......
Kaspersky detects this in the S Note app. Seems very unlikely that this is a threat though I am curious about any other experiences and/or suggestions. Thanks.
Kyndig66 said:
Kaspersky detects this in the S Note app. Seems very unlikely that this is a threat though I am curious about any other experiences and/or suggestions. Thanks.
Click to expand...
Click to collapse
found this might help a bit ,but not a lot http://forum.xda-developers.com/showthread.php?t=2243189
jaythenut said:
found this might help a bit ,but not a lot http://forum.xda-developers.com/showthread.php?t=2243189
Click to expand...
Click to collapse
I did do a search before posting and saw similar stuff but nothing for this app on the N3. Haven't rooted yet but from what I've read so far it might be troublesome. This is from Juniper networks. http://www.juniper.net/us/en/local/pdf/additional-resources/jnpr-mobile-signatures.pdf
Edit: The offending apk is possibly hq2.itqmmi.hjbr_94100600_0.apk (taken from HERE). This report was updated three weeks ago.
I'll ditch it once I root. I have a lot of multitasking going on right now so unfortunately it may be a few days.
Most of us here don't care that Google tells us our device is uncertified, blame it on the custom ROM, will ya?
However that isn't enough, many are ignoring the fact that while we have safetynet passing, Google play still sees our device as uncertified. This can create problems for safetynet bypass in the future and should be solved. Also, why did you pay for the device if you're going to live with uncertified? If the device shows up as uncertified in the play store, some apps may not work
Below is a magisk module that corrects this bug
It may also fix an issue for some users who are simply not able to bypass safetynet after repeated attempts
After flashing this module, check your play store. It will show Device certification true
If you're a ROM dev and want to include this patch in your ROM go here: https://github.com/anupritaisno1/an...mmit/b388c3b0265b0ab7697505d1ac618421654e46b1
Source code: https://github.com/anupritaisno1/op2_certification_bypass/commits/master
Before somebody argues that magiskhide works and fixes this issue, it doesn't
You can check the current certification in the play store setting
Tested here and does change it to certified.
Unfortunately not working here, using the newest OpenGapps and your ROM.
anupritaisno1 said:
Most of us here don't care that Google tells us our device is uncertified, blame it on the custom ROM, will ya?
Click to expand...
Click to collapse
Ahh, great just had a discussion about this exact issue, great to have this instantly solved, within 24 hours or so, lol Thanks for sharing
Sent from my OnePlus 2 using XDA Labs
Sam Nakamura said:
Ahh, great just had a discussion about this exact issue, great to have this instantly solved, within 24 hours or so, lol Thanks for sharing
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
Sorry not aware of any discussion on this issue. Moreover, I've been trying to fix it for a while and finally it works
anupritaisno1 said:
Sorry not aware of any discussion on this issue. Moreover, I've been trying to fix it for a while and finally it works
Click to expand...
Click to collapse
It was a private thing so don't worry..
Anyways, on first attempt flashing your module didn't show up any different but after clearing Playstore app data the "uncertified" notification is gone and it's now status certified.. Again, great & thanks
Sent from my OnePlus 2 using XDA Labs
Not the correct place to post this, reported.
parasthakur37 said:
Not the correct place to post this, reported.
Click to expand...
Click to collapse
And why is that?
parasthakur37 said:
Not the correct place to post this, reported.
Click to expand...
Click to collapse
LoL :laugh:
Please give us some insight on how you came to this "conclusion"?
Sent from my OnePlus 2 using XDA Labs
Sam Nakamura said:
LoL :laugh:
Please give us some insight on how you came to this "conclusion"?
Click to expand...
Click to collapse
Working fine for me. Thanks for this module @anupritaisno1 and thanks for the hint on clearing play store app data Sam
Hubi97 said:
Working fine for me. Thanks for this module and thanks for the hint on clearing play store app data Sam
Click to expand...
Click to collapse
I believe you mixed up the creators
anupritaisno1 said:
I believe you mixed up the creators
Click to expand...
Click to collapse
Edited my post. Didn't mix you up. Just wrote it misunderstandable. Your work is appreciated but without Sam's hint it would have seemed to me that it doesn't work
Hubi97 said:
Edited my post. Didn't mix you up. Just wrote it misunderstandable. Your work is appreciated but without Sam's hint it would have seemed to me that it doesn't work
Click to expand...
Click to collapse
Nah don't listen to anything I say unless it's about development. Anything else and I am mostly trolling
anupritaisno1 said:
Nah don't listen to anything I say unless it's about development. Anything else and I am mostly trolling
Click to expand...
Click to collapse
Yeah ok, I noticed that you like trolling in other threads before but it seems I'm not talented enough to understand if you wrote something serious or not :laugh:
After uninstalling, reinstalling the module, clearing Playstore data and lots of rebooting I can't get Playstore to display "certified" again, neither "uncertified", the category where Playstore used to display this vanished all together, no idea what's going on
I could get some magisk logs later if you want them...
Sent from my OnePlus 2 using XDA Labs
Sam Nakamura said:
After uninstalling, reinstalling the module, clearing Playstore data and lots of rebooting I can't get Playstore to display "certified" again, neither "uncertified", the category where Playstore used to display this vanished all together, no idea what's going on
I could get some magisk logs later if you want them...
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
Pretty normal. Just wait a bit
anupritaisno1 said:
Pretty normal. Just wait a bit
Click to expand...
Click to collapse
All right :laugh: probably the only thing I didn't.. lol
Last time it switched instantly,
that's why I was irritated
Edit: and another short unrelated question, where was your module "thermal throttle killer" posted, I got it of from someone's Dropbox but never saw a thread or anything related..
Sent from my OnePlus 2 using XDA Labs
anupritaisno1 said:
Most of us here don't care that Google tells us our device is uncertified, blame it on the custom ROM, will ya?
However that isn't enough, many are ignoring the fact that while we have safetynet passing, Google play still sees our device as uncertified. This can create problems for safetynet bypass in the future and should be solved. Also, why did you pay for the device if you're going to live with uncertified? If the device shows up as uncertified in the play store, some apps may not work
Below is a magisk module that corrects this bug
It may also fix an issue for some users who are simply not able to bypass safetynet after repeated attempts
After flashing this module, check your play store. It will show Device certification true
If you're a ROM dev and want to include this patch in your ROM go here: https://github.com/anupritaisno1/an...mmit/b388c3b0265b0ab7697505d1ac618421654e46b1
Source code: https://github.com/anupritaisno1/op2_certification_bypass/commits/master
Before somebody argues that magiskhide works and fixes this issue, it doesn't
Click to expand...
Click to collapse
Nice work using fake fingerprints. Magisk hide works here though.
B!Gguy said:
Why the hell we need this when there's magisk hide?
Click to expand...
Click to collapse
Why the hell is there a magisk module when we have magisk hide?
Before somebody argues that magiskhide works and fixes this issue, it doesn't
Click to expand...
Click to collapse
Go through the post again
Hi
As most of us all know that oreo roms are stable and giving good results.but all roms lack Ok Google feature when screen is off.and no one seems to fix it i wonder is it because its difficult or simply because people don't find it compelling enough.
What if i wanted to fix this issue? What would be a good start in the right direction?
Also if any one knows or has info that can help please share.
Thanks
Sanabil said:
Hi
As most of us all know that oreo roms are stable and giving good results.but all roms lack Ok Google feature when screen is off.and no one seems to fix it i wonder is it because its difficult or simply because people don't find it compelling enough.
What if i wanted to fix this issue? What would be a good start in the right direction?
Also if any one knows or has info that can help please share.
Thanks
Click to expand...
Click to collapse
My Moto Z Play on 7.1.1 does not have "OK Google" with screen off and it's completely stock. Is there an example of a phone with "OK Google" working with the screen off?
Guapo613 said:
My Moto Z Play on 7.1.1 does not have "OK Google" with screen off and it's completely stock. Is there an example of a phone with "OK Google" working with the screen off?
Click to expand...
Click to collapse
Bro almost all nexus phones have this functionality to activate Ok Google from screen off. I do not know about other manufacturers though but i think it can be turned on in most phones via voice or assistant settings.
Sanabil said:
Hi
As most of us all know that oreo roms are stable and giving good results.but all roms lack Ok Google feature when screen is off.and no one seems to fix it i wonder is it because its difficult or simply because people don't find it compelling enough.
What if i wanted to fix this issue? What would be a good start in the right direction?
Also if any one knows or has info that can help please share.
Thanks
Click to expand...
Click to collapse
I haven't fixed it for LineageOS, because I didn't know where to start.
Additionaly it's not very important for me.
Elektroschmock said:
I haven't fixed it for LineageOS, because I didn't know where to start.
Additionaly it's not very important for me.
Click to expand...
Click to collapse
Oh i see ? well in that case what do you suggest?
may be this feature is useful for some, like myself.
And it will be nice to see it in !
Sanabil said:
Oh i see well in that case what do you suggest?
may be this feature is useful for some, like myself.
And it will be nice to see it in !
Click to expand...
Click to collapse
My suggestion?
Fix it
I know this isn't very helpful, but I really don't know what changed with O and why it isn't working any more.
Perhaps you can start to find out why shamu's custom TriggerTraining.apk isn't launched anymore like it used to be on N.
Elektroschmock said:
My suggestion?
Fix it
I know this isn't very helpful, but I really don't know what changed with O and why it isn't working any more.
Perhaps you can start to find out why shamu's custom TriggerTraining.apk isn't launched anymore like it used to be on N.
Click to expand...
Click to collapse
:laugh: ok let's see.
Elektroschmock said:
My suggestion?
Fix it
I know this isn't very helpful, but I really don't know what changed with O and why it isn't working any more.
Perhaps you can start to find out why shamu's custom TriggerTraining.apk isn't launched anymore like it used to be on N.
Click to expand...
Click to collapse
You see i am no developer, but i see your statement gives hints and certain clues to what to look for. ?
I searched and found a thread on xda from 2016 , Op was suggesting to modify build.prop via text editor , so changed device name to pixel xl , finally rebooted
AAAaanddddd
It didn't worked ?
Back to more searching,
Sanabil said:
I searched and found a thread on xda from 2016 , Op was suggesting to modify build.prop via text editor , so changed device name to pixel xl , finally rebooted
AAAaanddddd
It didn't worked
Back to more searching,
Click to expand...
Click to collapse
If it was that easy it would have been fixed already.
Elektroschmock said:
If it was that easy it would have been fixed already.
Click to expand...
Click to collapse
Can i ask you something?
All the devs who put out such ROMs can't they just debug or know where code requires modification.??
Also do you know a coder or dev that you think has a chance of doing it.
Thanks
Sanabil said:
Can i ask you something?
All the devs who put out such ROMs can't they just debug or know where code requires modification.??
Also do you know a coder or dev that you think has a chance of doing it.
Thanks
Click to expand...
Click to collapse
I don't know what you think who those devs are. I did the oreo bringup for shamu, but I am a hardware developer and my software skills are very limited.
Additionally all devs do it in their free time and for fun. If a feature is not implemented or not fixed then there is a high chance that nobody is interested or able to fix it.
If you want it working then you should learn to debug and to code.
Elektroschmock said:
I don't know what you think who those devs are. I did the oreo bringup for shamu, but I am a hardware developer and my software skills are very limited.
Additionally all devs do it in their free time and for fun. If a feature is not implemented or not fixed then there is a high chance that nobody is interested or able to fix it.
If you want it working then you should learn to debug and to code.
Click to expand...
Click to collapse
Bro i meant no disrespect to any dev who do such work, i appreciate their hard work . I also realize that they take special time to do such work.I didn't knew much about how its all done. But since you explained, i thank you.
And i think as you mentioned i will look into it myself. :good:
Today i used nokia 6.1 with Android Oreo 8.1 , i checked its assistant and to my surprise it too did not supported ok Google function with screen off.
So my guess is that its more of an Android 8.1 change , they have limited this functionality to certain phones.
This means it is not a bug, and needs some custom coding or programming/modification to make it work again .
Well i think i am isolated but i shall continue to find what ever i can and post .
I read on Reddit post of this problem and a user posted build prop trick where one tricks the Nexus 6 into thinking its a pixel device.
I tried but it didn't worked and also camera app crashed too. Voice match remains greyd out , it did how ever at first showed sign that its working but nope upon real testing it failed.
I then tried switching name to nexus 6p and it enabled one option which was previously greyd out, it allowed me to record and voice and asked for pin to use voice match but then disabled 'use ok google from any screen' option. .... and camera was not working too..
Is it the right direction? perhaps..perhaps not.
Update:
This issue is definitely from Google's server side, the voice match issue is not present on nexus 5 and nexus 7 tablet. here is a thread of ongoing discussion.
https://productforums.google.com/forum/#!topic/nexus/0GmbO8FgvQg;context-place=forum/nexus
I think Google decided to ditch ok Google screen off functionality altogether from Nexus 6. There tech team never responded to the complaints mad by users. So it's kinda dead now.
Sanabil said:
I think Google decided to ditch ok Google screen off functionality altogether from Nexus 6. There tech team never responded to the complaints mad by users. So it's kinda dead now.
Click to expand...
Click to collapse
I've been looking for a solution to this. I spent a weekend last month flashing various 8.1 and 7.1.X roms and trying to renable it. Same story every time. Apparently Google's just decided we don't get to use this feature anymore. I'm gonna start playing with other assistants (Cortana, Alexa, Hound, Autovoice) and see if any work like we want Assistant to.
lpjunior999 said:
I've been looking for a solution to this. I spent a weekend last month flashing various 8.1 and 7.1.X roms and trying to renable it. Same story every time. Apparently Google's just decided we don't get to use this feature anymore. I'm gonna start playing with other assistants (Cortana, Alexa, Hound, Autovoice) and see if any work like we want Assistant to.
Click to expand...
Click to collapse
I wish you best of luck bro . ?
Has anyone tried this on a 100% stock, unrooted device? I got Google One for being a good Local Guide, and Google Customer Support says root may cause this. I'm going to try Magisk Hide and report back.