Official myLock thread - we don't like the lockscreen

[petjakob]

My best guess is your cpu mod is harshly interfering with the timing and creating the severe failures you experienced.

As for the icon in notifications, the only reason it exists is actually a design choice in android I can't work around. We want myLock to always run and not be stopped by the os. The only way the os will let us do that is by becoming a foreground service and forcing us to be part of the notification bar telling the user we are still there. I've provided the option to not use this mode, and in my testing it is very rare that the os ever tries to stop the myLock background process- I prefer the certainty of reliability as if the background process gets stopped at any point, it has a very hard time recovering without rebooting the device.

 

[Matth3w]

I had my first FC with this app when calling someone and hanging up. It might have an issue because speaker and bluetooth calls lock the screen unlike regular calls, which sucks. So perhaps that's where the issue is.

 

[Matth3w]

In addition, it just stopped working for some reason. I start it up, but it simply doesn't work. Going to try rebooting the phone.

 

[Matth3w]

Ok it worked when I rebooted. Not sure what the problem was. Just a few issues so far, hopefully they will get ironed out.

 

[Matth3w]

Well, sad to say, I love the idea of this, but I uninstalled it. It just doesn't work consistently enough for me. Sometimes it randomly stops working, sometimes it doesn't seem to start up when I reboot the phone, and sometimes it works perfectly. But I'd rather have to swipe the screen than try to figure this app out a couple times per day.

I'm going to stay subscribed though so that I can try out new updates.

EDIT: I had it uninstalled for 5 minutes and started missing it already, so I put it back on in hopes of figuring out what is shutting it off

 

[petjakob]

I have a lot of good info on known conflicts in the troubleshooting faq.
It seems the cpu clock mod and task killers interfere the most with the functionality. I can't explain why. I just don't know.

I duplicated the issue where the lockscreen comes back on an outgoing call if you were on speaker or bt. I have all other relock cases handled but it appears this one is a bug in android. The lockscreen is actually re engaging at the sleep, and I saw the phone manually skipping it with same flash the market ver would have. As a result, the phone app is forced to restore it manually at end of call.

 

[Matth3w]

Yeah I figured it wasn't your problem. Shouldn't lock when on a BT or speaker call, that's just stupid by default, and I guess you just can't fix stupid.

 

[Matth3w]

Sorry to keep bumping this thread. But I uninstalled my task killer but I noticed that sometimes when I reboot the phone it takes at least a minute for the app to kick in or sometimes never at all and I have to restart the program (which sometimes works, sometimes doesn't). I checked the services tab in the settings and it is definitely running so not sure what the problem could be....

 

[Matth3w]

Just for the record, there is some sort of conflict with message pop ups in ChompSMS and lock screen. When I get a message and hit X on the popup even though My Lock is still running it stops working. Only solution is to reboot the phone.

going to uninstall for now, but I'll be following along

 

[petjakob]

popup interaction is fixed in the next update. some like handcent give options to tell them not to try to pass through the lockscreen, enabling that option gets perfect operation restored in the market version

 

[Matth3w]

so if it forces through the lock screen you're saying it will still function after the next update? because my sms is set to send a pop up when the screen is locked

 

[petjakob]

Yep. The next version uses some really cool functions new to android 2.0 that are more integrated into the android OS system. The pre-2.0 lockscreen interactivity is very rigid and inflexible, requiring you to call a stop on the lockscreen, which actually only pauses it (home key and search key won't work unless the user goes home once or you request what's called a "Secure Exit" which then clears the lockscreen all the way out, and forces the pattern unlock screen if user has a pattern). The 2.0 function lets you create a window that always supersedes the lockscreen and doesn't have to do anything special other than exit to restore the regular lockscreen mediation, so the a3 and on revisions are greatly more solid & smooth.

The android 2.0 window-based solution is so great because apps will no longer get in each other's way, because the window just defines the desire to pass through lockscreen and the window manager takes care of actually executing it when & how it is needed.

 

[Matth3w]

Awesome, I can't wait to try it. If we could only get rid of the lock screens while on a speakerphone or BT call...

 

[Martin030908]

I've found, for the Handcent pop-up, that if you change the settings for the pop-up you can work around the myLock interaction.

I'm not sure if ChompSMS has the option, but in Handcent for the pop-up you have the option to "show on locked". Which allows the pop-up to show 'over' the lock screen, therefor disabling it, or disabling that option so that the lock screen remains (you have to swipe to view the pop-up)

I had issues with myLock and the pop-up conflicting until I disabled the "show on locked" option. So now, Handcent pop-up does not bypass the lock screen, but since it 'wakes' the phone, myLock is activated and the lock screen is bypassed

 

[Matth3w]

Mine is set to show only on lock.