Official myLock thread - we don't like the lockscreen

[MotorolaDroid]

Yeah I realized mine doesn't work at all with dolphin open

 

[aamzalag]

Hey, i have a motorola droid, and it wont let me install any of the test builds, the latest ones, i think build 127? are they made to work for the droid? i have the older version running, alpha 2c build. so am i doing something wrong?

 

[petjakob]

what's the error installing? i've been able to install all of these from direct download, i do it that way instead of usb testing to ensure the file will work.

 

[petjakob]

i also just tested and can get a handcent popup in the current 0127 test release without having to fiddle it's settings. i noticed after dismissing it our lockscreen doesn't realize it was asleep, the os sends a 2nd sleep command when power is pressed.

 

[rori]

Hi,
just installed myLock_0127.apk on my Nexus1...worx smooth

 

[Paul1201]

Version alpha3 apk 122 is still the most stable for me. The new apk 127 does not work with handcent popup even with screen on for popup and screen unlock for popup are both disabled.

 

[cupfulloflol]

I've been researching the option of a button mapped call-answer due to popular request. To do it, we would have to create a dialer-capable section of the program and claim it was capable of handling answering calls. then, when a call starts ringing our program would be able to be called. I haven't yet started any coding work on it but I think it could be done. I haven't spent time to research if there is a specific phone replacement out there that might already serve this desired purpose.

That would be so spectacular. That is still one of my biggest gripes about the phone. I have missed so many calls because I fail to swipe properly. I am sure the swiping is my fault, but it is still annoying nonetheless.

Thank you for keeping us updated on what you are doing, and keeping the program updated and moving forward. I greatly appreciate everything you have done so far. This is still one of my must have apps.

 

[geneticflea]

overall i love mylock lite, but the other day it stopped working, even when i restarted it or reinstalled it. so i reluctantly uninstalled. Now, when i get calls, the lock screen stays on and i have to swipe it before i can see who is calling or to answer the call. any idea how i can fix this?

 

[petjakob]

That's odd, paul. I just now got a handcent popup from google voice (I didn't know it could push popups for those!). I haven't changed any settings on it.

flea, I'm looking to update Lite now that I've refined a lot of my code. Check out our troubleshooting faq, it might be a program that is conflicting and causing the stop working, but more likely to just be a CPU stop of the myLock app. Essentially you have to reboot the phone by doing a battery pull to recover from that. It seems very rare but most prone to happen in lite mode.

 

[m21knight]

My predection: This will lead to a marked increase in pocket dialing :biggrin:. Actually, I really appreciate the hard work you guys are putting in over there!

 

[steveninspokane]

I have been using screenModeWidget, and after reaching into my pocket and pulling out a very warm/hot phone that had been recording video with the flash on for who knows how long, I am thinking of trying a different app.

This app sounds great, but... I have no clue how to install it on my phone and which one to install, some assistance please?

 

[Dr01d]

I gave it a try but consistently get a flicker or two on the lock screen. I'd like to uninstall it for now but I've run into a hitch.

I can't seem to figure out how to uninstall. myLock lite.

Since it doesn't show up in my applications list I don't know how to remove the widget from the widget list. What do I need to do please?


*edit* nvm I got it removed with eStrong's.

 

[Paul1201]

Dr01d - uninstall by Menu>Applications>Manage Applications and look for myLock in the list. For some reason it is not in the rest of the M's but is earlier in the list.

I was starting to experience the sliding to unlock to hangup a call bug so I did a bettery pull. Figured I would try the 127 apk again and it seems to be working better for me now. I have not gotten a text yet so only time will tell.

 

[Paul1201]

Well I just got a text and could not unlock the screen. I had to power cycle the phone to be able to uninstall the 127 apk. Just tried it on the wife's Droid and had the same problem. Again Handcent is set to not unlock the screen so I am not sure what is going on. I installed myLock lite and it seems to be working now that I have Handcent configured to not unlock the screen on popup.

 

[petjakob]

Yeah, sorry about those bugs. I've pulled the test build downloads as I've been trying to get these two bugs ironed out. I have some really great additional features planned for an official alpha 3 (options for stay awake - set stay awake apps & auto stay awake when slider is open, pattern mode lockdown idle timeout, key configuring & option for a slide to unlock) and I'm getting frustrated that these snags are holding me back from rolling them out.

I actually have a perfectly working fix for the thing where you can't get the screen on for the handcent pop or alarm clock. I have code that's allowing myLock to know whether it's the main event on screen and respond if it detects that waking up is happening and something else is becoming the main event so we can turn on the screen and not try to lock it back till we become the main event again.

the thing that is really vexing me is how I cannot prevent the screen from resleeping sometimes when trying to instant unlock with this 2.0 optimized method. there's no reason it should go back to sleep after power is pressed to start the unlock, and when I have my device plugged in over USB so I can see event logging, the error won't happen. i've found if stay awake is on the bug doesn't happen but the problem with that mode is that the phone isn't going back to sleep if a side key gets bumped. So despite the fact that the phone is still locked that introduces a complication for when you do want to wake the phone.
------------update on that one: I think I discovered the fix to this though, now that I can retrieve my logs from when I was unplugged I see that the screen is sleeping and for some reason the task that gets ready to put the lockscreen up never runs. I think the CPU is sleeping which I can prevent specifically just for that 5 seconds needed to override the default lockscreen.