I managed to get Debian booting on my Gemini PDA wifi version pretty easily.
Certainly there are rough edges, but it looks like it will be useful...but for one problem. I can't reliably get it to sleep and wake.
I don't mean the "Sleep" and "Hibernate" options from the "Leave" menu--I have never gotten them to work at all. I'm just trying to get the "Off" feature on the Esc key to work. Or the lid close, either would do.
Trying to reproduce the problem I have had lots of theories of what exactly it takes to make it fail, but none seem to verify. The problem is frequent but erratic.
I do have a clue. The world map screen (the one with the various sized circles) where I type my password tends to do a brightness change; it appears bright, then I think adjusts to the ambient light. In the cases where I see it fail I think it does the same thing, but instead of adjusting to a new brightness it goes black. (No, I can't successfully type my password blind.)
When this does happen, I think the computer is still running, I think I have been ssh-ed in and that was still alive.
Any others had problems with the lockscreen and found what's the problem or a workaround?
Thanks,
-kb
More Info: Network Related
More experimenting and the lockscreen seems reliable as long as wifi is on. If wifi is turned off, it is unreliable. Not 100% failure, but significant.
Suggestions welcome.
Thanks,
-kb, the Kent who wants wifi off to save power.
I can confirm this issue. And Wifi-on does not avoid it, as I had WiFi always on when this happened. Genrally Fn-ESC for screen locking works and unlocking (world map) also. But sometimes, always after longer times of inactivity, the device does not wake up at all. Screen stays black, blind-typing the password does not work, at least the screen stays black. Only solution in this case I found so far is Fn-ESC (aka "Off") until the device is powered off and reboot.
Edit:
Just happened quite shortly after a reboot, so the "always after longer period of inactivity" seems not to apply.
And the UI seems not to work/respond at all. Trying to - blindly, via keyboard - login and shutdown via systemmenu does not work too - typing pwd, Enter, Ctrl+Esc, three times cursor up, one time right, four times down and two times Enter
Partial workround
Using ssh
sudo service sddm restart
gets you to the initial login screen.
As I'm not allowed to post links: See my post on oesf.org forum, topic 35528 for further comments/notes
Related
I wanna make another post here cause in the last post this issue wasnt resolved and i wanna fresh thread here, please only post if you have the solution, thanks hope theres someOne who can get this issue resolved.
Do you use AutoKeylock ?
I had this problem when I started using 6.1 ROMs first.
In my case I had about 6 applications I always installed right off the bat after a new ROM flash. One of those was Maniac's AutoKeylock.
I timed the duration between answering a call and having the call go white one day, and it seemed to me to match precisely with the screen timeout settings I had in AutoKeylock.
I removed the application, and have never seen the problem happen again.
However, I do miss having AutoKeylock.
I realize that this could be totally coincidental, and thus I asked before whether others who had the problem also used AutoKeylock but never got a reply.
Perhaps you can reply as to whether you use it or not. And, if you do, whether removing the application resolves the issue for you.
If there is a correlation then we can alert Maniac to the issue, and he may be able to find a solution.
LiverpoolFCfan said:
I had this problem when I started using 6.1 ROMs first.
In my case I had about 6 applications I always installed right off the bat after a new ROM flash. One of those was Maniac's AutoKeylock.
I timed the duration between answering a call and having the call go white one day, and it seemed to me to match precisely with the screen timeout settings I had in AutoKeylock.
I removed the application, and have never seen the problem happen again.
However, I do miss having AutoKeylock.
I realize that this could be totally coincidental, and thus I asked before whether others who had the problem also used AutoKeylock but never got a reply.
Perhaps you can reply as to whether you use it or not. And, if you do, whether removing the application resolves the issue for you.
If there is a correlation then we can alert Maniac to the issue, and he may be able to find a solution.
Click to expand...
Click to collapse
You know if the reason you miss autokeylock is for the ability to set a time for the screen to turn off and the keypad to lock, smarttoolkit does that, with no problems.
HTCP4000PPC said:
I wanna make another post here cause in the last post this issue wasnt resolved and i wanna fresh thread here, please only post if you have the solution, thanks hope theres someOne who can get this issue resolved.
Click to expand...
Click to collapse
How often it happen?
With my phone running Kavanas I will get a white screen once after a reboot and then I press and button and it goes back to normal and wont do it again. I have gotten used to it.
For some reason I think it has to do with Tornado PowerControl, do you have that installed? I just cant figure it out exactly. Maybe we can find a solution.
We'll i believe this White screen has something to do with the backlight settings in power managment, i find if you leave screen on full and turn off the phone from turning off the screen, the white screen wont happen, this isnt so bad, cause if u want the screen to go off just hold down the disconnect phone button, not too bad cause when your not wanting to use the phone anymore the screen still goes off, also you can turn the backlight off in accessories which is the same as setting the screen to go off automatically in 5 seconds, white screen fixed moreless.
Same issue with Ricky's v24 and now with Rose 1.7
I also am experiencing this issue, but do not have installed neither Maniac's AutoKeylock nor Tornado PowerControl.
It happens sometimes during a call, sometimes not.
It happens when leaving the phone unlocked and timesout idle time. If hit the Home or back buttons, it shows the home screen again and next timeout does work fine.
I have beeing looking up and down for fixes but was unable to find one. Some say turning off "Run Lowlight" JOGGR setting, some say flash after a hard reset...
It seems that running lowlight (joggrinfo.exe -m -t) helps a bit. If the phone is fully bright and rests on the table, the screen goes white after timeout.
However, if run lowlight and let it alone, it turns off the screen normally.
Also when it goes white and hit back or home button, the screen goes mid-bright, and then turns off normally.
However, when unlocking, it goes full bright, and then the issue comes back.
In summary ...
Full Bright -> Times out to whitescreen.
Mid Bright -> Times out to lights off.
Unlock -> Goes full bright -> Times out to whitescreen.
White screen -> Hit Back/Home button goes mid-bright -> Times out to lights off.
It would be great if lowlight could be run when unlocking the device.
Does it work same way for you guys??
Regards.
This will stop White Screen from happening.
ok this is a way to avoid the white screen issue, (Click on Light Config) then open CeleTask and in CeleTask - Tools use Close Screen this will turn off your screen and allow the backlight from turning on when screen turns back on, also remember u need to set your power settings to (Backlight time out on battery 5 Seconds and Backlight on AC can be 1 minute which u never use) and Display time out Never..)
You can also use CeleTask to disable the screen when you make a call, just open CeleTesk when you hit call.
Topic should be changed as not a fix but work around "sortof":
Process of illimination:
My recomendation would be try a hard-reset, don't install any programs see if that fixes it now when installing programs don't bung them all on install 1 @ a time soft-reset give it while see if problem resumes, do this for all software then you may find the culprit?
This is not an issue faced by all so something has to be the culprit.
Bad Flash?
Software Install?
JOGGR?
Power Settings?
They are just examples.
I had this happen once but on WM6 and a hard-reset was what was needed and didn't pop up again........
HTCP4000PPC said:
ok this is a way to avoid the white screen issue, (Click on Light Config) then open CeleTask and in CeleTask - Tools use Close Screen this will turn off your screen and allow the backlight from turning on when screen turns back on, also remember u need to set your power settings to (Backlight time out on battery 5 Seconds and Backlight on AC can be 1 minute which u never use) and Display time out Never..)
You can also use CeleTask to disable the screen when you make a call, just open CeleTesk when you hit call.
Click to expand...
Click to collapse
These instructions have fixed my device... I got an Elf and I made it my primary phone, and now I´m experiencing new ROM´s in my S621. This problem happens in my device (the S621, of course), and I´m now using NRG remade by Ricky and Stylez, and this problem with the screen seems to be solved with this tip.
This problem does not happen when I use "Kavana remade by Ricky and Stylez" only with NRG and it´s Remake.
Regards
If this isnt helping try just disabling Timeout and set everything else ur way u want.
Hi all,
I'm having a few intermittent problems with my phone but before I start asking to have it swapped out, thought I'd check to see if they are just with my phone or if others have the same and if the latter, whether there are any workarounds. All are occasional but have happened enough times that it wasn't just a one-off glitch:
1 - using the physical keyboard when writing a text if I hold delete to get it to delete a sentence rather than pressing it repeatedly it deletes for a bit, then stops updating the display. You can keep pressing delete and it will delete characters, you can even move the cursor and delete characters from elsewhere but you need to close the keyboard and rotate the display before it updates the screen. While writing that it occurred to me I can't remember if other keypresses show up, whether holding any button pressed causes this, or whether it happens in apps other than the SMS app. Will try those later.
2 - wifi sometimes turns itself off for no reason. Not just not connecting or forgetting the password (although it occasionally does both of those too) but just disabling itself. I can pick the phone up to do something and notice no wireless icon and if I go into the communications part of settings, wireless is disabled and I need to reenable it for it to start working.
3 - the rotation sensor sometimes stops working and no screen rotations work. Sometimes restarting the phone doesn't help (but on that occasion shaking it and tapping it seemed to!) I once solved it by recalibrating the sensor (it froze a few days ago while I was using Teeter to demo the motion sensor to a friend) but it's not happened since then for me to try that again.
There are other niggles too, but those are things that I've already seen mention of - these three are things that I've not seen any other reference to but might be too minor or intermittent to be noted. Anyone else seen the same issues on another handset or is it just mine?
Cheers,
Steve.
I'm going mad here trying to find a screen Lock suitable to my needs. Can anyone please help? I want a simple screen lock, nothing fancy, no bells'n'whistles, but with the following two essential features.
1) Screen Lock is quickly unlocked with a simple screen swipe as soon as I either power on or slide open the device (ideally slide-opening would automatically unlock without requiring a swipe).
2) When running on external power the screen should unlock automatically and remain unlocked.
I've now auditioned PocketShield, Sunscape, TouchLockPro and S2U2 all of which may have one or other of those features, but none have both.
Can anyone please recommend anything else? Thank you.
1) In Pocketshield you can auto unlock by sliding QWERTY out if you create the following reg key: HKEY_LOCAL_MACHINE\Software\Pocketshield\ROTATE=1 (DWORD)
2) There is an option for it in settings.
Thanks for that. I've decided to give PocketShield another go and am auditioning it at the moment. Also I've changed my UI from Winterface to Spb Mobile Shell 3.5 because I wondered whether Winterface wasn't working well with PocketShield.
But here's my issue with PocketShield, perhaps somebody can please help?
If I open the slide keyboard I am able for a second or two to use the device as if it were not locked, before PocketShield "remembers" that is supposed to be on and then suddenly the device gets upset, slow, stuck, until I can find and unlock pocketShield. If I first power on and then slide open the keyboard, everything is fine, but everything stays in portrait, even though the keyboard is open. I can unlock PocketShield properly (though sideways) but then everything else is displayed in portrait, even though the keyboard is open.
I tried the reg tweak suggested, but found that that just caused even more confusion; portrait trying to change the landscape at the same time as the UI was trying to appear, at the same time as PocketShield was trying to put up its lock screen, basically chaos!
Any thoughts anyone, please?
My S2U2 v 2.42, has both of those options. Just go to Settings>Others
1. Action when connect to power>Unlock
2. Unlock when Keyboard is opened>On
Thanks. I've been trying out PocketShield all day and it seems that in its simplest terms there is a delay between switching on the unit and PocketShield realising it should be locking the screen, during which time it is possible to start an action which is then instantly stopped when PocketShield kicks in. Ridiculous.
I'll give S2U2 another shot now, cheers.
Smart unlock, its in the software worth installing section, does exactly what you want
I'm getting very frustrated here and beginning to think that my problem is nothing to do with one screen lock program or another, but with my unit.
Whichever screen lock I install, roughly 60% of the time the lock works as it should, but about 40% of the time there is a short period between powering on and the screen lock preventing me from doing anything. During this time it's possible to use the unit normally for a second or two until the screen lock kicks in, at which point often the unit gets confused, actions jam, and I often end up having to soft reset.
With all of the locks I've tried, if I open the keyboard and THEN power on, this also causes confusion.
Can anybody possibly shed any light on all this, please?
Could be that one of your installed applications is subscribed to the power on event and performs a very intensive processing each time device is turned on, delaying other subscriber apps such as lock screens. You might want to try uninstalling one by one to see if any culprit. Last resource is hard reset.
Thanks Pckshd. To be honest I've just had a rough day with the phone: it froze last night and on soft reset wouldn't boot up. This morning was the same story so eventually I was forced to do a hard reset. Then my most recent backup wouldn't restore, claiming there wasn't enough memory in the phone (how can that be? It was backed up from the phone!). Eventually I had to rebuild everything and right now haven't dared install any of the screen lock programs!
Is there not a registry entry anywhere that would show me which programs are taking priority over power on? My UI of choice, Winterface, as its own screen Lock, which is almost 100% reliable but regrettably continues to run went on mains power (I want one that unlocks on mains power, the desired feature that started all this off in the first place).
I have Sprint Touch Pro 2 with the Sense 2.5 Rom. I installed Lock Device v1.6. It does lock the screen and it does seem to work as expected when I try testing it. I have it set to [lock on screen off] and I have [enabled] checked.
However, on a daily basis, when I pull my phone out of my case to use it at random times of the day, the phone is unlocked all by itself 90% of the time and of course unintended apps load and buttons pressed.
What is causing this to happen? I can't seem to generate this issue manually. There has to be something going on when the phone is in my case.
Also, I keep my phone on my dashboard in my car or on my seat when I'm driving. I noticed the phone will wake itself up randomly for no reason at all.
Are these 2 issues related? G-sensor issue maybe? Please shed some light and possibly any fixes.
Thanks in advance,
Daniel
i tried this program for a few minutes...when your phone wakes up...with reminders etc...screen isn't completly locked...neither were the hard buttons...explains the apps starting up.
SupraFast said:
I have Sprint Touch Pro 2 with the Sense 2.5 Rom. I installed Lock Device v1.6. It does lock the screen and it does seem to work as expected when I try testing it. I have it set to [lock on screen off] and I have [enabled] checked.
However, on a daily basis, when I pull my phone out of my case to use it at random times of the day, the phone is unlocked all by itself 90% of the time and of course unintended apps load and buttons pressed.
What is causing this to happen? I can't seem to generate this issue manually. There has to be something going on when the phone is in my case.
Also, I keep my phone on my dashboard in my car or on my seat when I'm driving. I noticed the phone will wake itself up randomly for no reason at all.
Are these 2 issues related? G-sensor issue maybe? Please shed some light and possibly any fixes.
Thanks in advance,
Daniel
Click to expand...
Click to collapse
Does this lock the hard keys for you?
Nvm it doesn't, just starts the stock lock screen when you push power. This doesn't lock hard or soft keys with an alarm, reminder, e-mail, missed call, etc... why your buttons are getting pushed when the phone wakes up.
I've searched for an answer to this problem and, after coming up empty, have humbly come to you, the experts, for a solution. I make many calls that require me to press multiple buttons so I place these calls on speakerphone. My screen goes dark in a matter of seconds, requiring me to keep a close eye on the screen. Otherwise I have to pick up the phone to press the power key, sometimes missing the opportunity to respond in time.
How, in this day and age of hundreds of settings, buried deep in tree branches, can there not be a setting that addresses an issue that hundreds of users on the Samsung forums remain without being addressed by the manufacturer?
I'm old. I'm cranky. I have arthritis. This mess is killing my lack of fine motor strength.
Humbly, I ask you for a solution that doesn't involve downloading a 3rd party app.
Is there a Samsung engineering wizard I can consult in here?
(send help, please)
The phone display turn off time is fixed and not user adjustable as far as I know. On my N10+ it's about 25 seconds. Power management settings may effect it, not sure.
I find it annoying at times so I just keep tapping when it dims
blackhawk said:
The phone display turn off time is fixed and not user adjustable as far as I know. On my N10+ it's about 25 seconds. Power management settings may effect it, not sure.
I find it annoying at times so I just keep tapping when it dims
Click to expand...
Click to collapse
Sadness.