Related
TouchLockPro is not exactly new (currently at version 1.9), but it was posted in the Diamond thread, because there things started. But because other phones are also supported, maybe the TouchLockPro thread could move to here. If this cross posting is not wanted, I hope the moderators let me know how to continue. At the Diamond thread or in this one?
But Windows Mobile has an OEM screen locker!
Yes, Windows Mobile locks the screen, but unlocks the Answer and Ignore buttons as soon as a call rings, so it is useless. The same happens when any notification pops up, the Snooze and Dismiss buttons are enabled even when screen is locked, leaving them vulnerable to any accidental touch.
Supported phones (known)
Touch Diamond
Touch Pro
Sprint CDMA Diamond
Touch HD (only triple touch capacitive sensor for unlock does not work)
Summary
There are already a lot of applications to disable touchpanel and/or hardware keys for the Touch Diamond and Pro. I added yet another one:
* lock using the Power button, BattClock and/or Stylus Sensor
* auto-unlock by the Light Sensor
* unlock using triple touch of the Capacitive Sensor
* unlock using Stylus Sensor
* unlock when on AC/USB power
Why is TouchLockPro better than other locking solutions
TouchLockPro is designed not to interfere with running applications and is a multipurpose locking application. Other locking solutions are often specific for locking only incoming calls/SMS. A lot of locking solutions also place a (transparant looking) Window on top of the running application (e.g. slide 2 unlock), so the information of the background application is no longer visible. This is not the case for TouchLockPro, so it can be kept lean and mean. Also the used resources is very very low.
Does TouchLockPro use much battery, RAM, CPU
Not at all, TouchLockPro is designed to be lean and mean!
TouchLockPro does not have noticeable effect on battery life. It only uses 33 Kb RAM in memory, whereas other solutions often use much more. For example S2U2 uses 4 Mb (125 times more) and PocketShield 1.7Mb (50 times more) memory. TouchLockPro uses 0% CPU (check it with a task manager!) and is totally event driven. Polling is kept to a minimum (currently only for polling once per second the light sensor when LOCKED and the screen is on). Requested features which would violate the "lean and mean" principle are rejected. Note that larger UI related stuff is done in a separate TouchLockAction.exe (e.g. editing settings), so the memory is only used when that program is active for a small moment.
Which other solutions exist
This is a list of other solutions, which may suit you better:
* Built in locking of Windows Mobile
* Stylus(BattC)lock
* Get A Reward! Create A "answer Only With Hw Buttons" Option!
* S2U2
* PDAVIET's dialer
* CSDEVCTRL
* SensorLock
* Answerkeys Disabler
* PocketShield
* ThrottleLock
Interested in *FREE* TouchLockPro?
I just posted TouchLockPro version 1.8.
I also posted the source code belonging to version 1.8. Hope you will learn something from it and you are inspired to make great programs too. At the end programming Windows Mobile is not so difficult if you have programming experience. Prerequisites for programming:
* Visual Studio, Express editions are free!
* Windows Mobile 6 Professional SDK (also free)
Note that others pointed out, that Express editions are not suitable for Windows Mobile development. See Smart Development for what is supported by which version. I used myself Visual Studio 2008 Professional SP1.
Note that TouchLockPro is written in C++ and TouchLockAction in C# (and deployed using .NET Framework 2.0).
Enjoy the software and source code
you can lock specific programs? waaahhh? this is what I've been waiting for for a very long time. downloading right now.
lennie said:
you can lock specific programs? waaahhh? this is what I've been waiting for for a very long time. downloading right now.
Click to expand...
Click to collapse
I do not know if HTC x7501 has the same sensor like capabilities. Does it work for you? Or do you have another phone too?
anybody tried with tytan II ?
shuren said:
anybody tried with tytan II ?
Click to expand...
Click to collapse
TouchLockPro uses the unique sensors since Touch Diamond was brought out:
* auto-unlock by the Light Sensor
* unlock using triple touch of the Capacitive Sensor
So probably those functions will not work on your phone. BUT I continue without those functions when the loading of the needed HTC libraries fails.
There is also a stylus sensor, but TouchLockPro just observes a registry key for detecting if the stylus is in or out. So you can check if that registry key also exists on your phone, before you try to install:
HKCU\ControlPanel\Keybd\StylusOutStatus
1 = out
0 = in
If this registry key does not exists, probably TouchLockPro will not work for your phone.
For the rest it is standard Windows Mobile programming, although the locking of the hardware keys may also not work. But the locking of only the TouchPanel should work (setting "LockTouchPanelOnly = 1". TouchLockAction is written in C# and needs .NET Compact Framework 2.0.
Note that controlling the locking only with the stylus is also doable, actually my first version only supported this:
StylusLock
So you could use TouchLockPro with only the Stylus (if that registry key is written) and/or LockTouchPanelOnly, you miss only some of the unlocking features. Actually if you only lock the touchpanel, you can assign the command "\Windows\TouchLockAction.exe unlock" to a hardware key for unlocking.
Hope this helps......
So you say it won't lock some hardware buttons...this won't get around the problem with Samsung i730 and the power off key?
No program I have found yet can lock that hardware key to prevent it from powering off while in my pocket
EDIT: Nevermind...it isn't supported on the i730 anyway
First of all:
Congratulations for your post. Didn't see a long time an informative post like this - your own program is introduced, the reason for doing it AND other existing solutions!!! Hat off to you.
ZuinigeRijder said:
I also posted the source code belonging to version 1.8. Hope you will learn something from it and you are inspired to make great programs too. At the end programming Windows Mobile is not so difficult if you have programming experience.
Click to expand...
Click to collapse
Thank you very much for sharing the source code. It is for sure helpful in both ways - to learn and to get inspired. I already took my hat off otherwise I would do it again.
StrykerC3 said:
So you say it won't lock some hardware buttons...this won't get around the problem with Samsung i730 and the power off key?
No program I have found yet can lock that hardware key to prevent it from powering off while in my pocket
EDIT: Nevermind...it isn't supported on the i730 anyway
Click to expand...
Click to collapse
Actually it does lock ALL hardware keys, even "Power Off" key.
But maybe you meant the "Power On" key (actually, the same key).
That is why TouchLockPro does also lock immediately at Power On or Screen On (due to an external event, incoming call, or via pressing the power on key).
Code:
// --------------------------------------------------------------------------
// HTC Touch Panel
//
// Reverse engineered from HTC's TPEnable.exe and TPDisable.exe
// --------------------------------------------------------------------------
#define IOCTL_HTC_HAL_ENABLE_TOUCHPANEL CTL_CODE(FILE_DEVICE_HAL, 2698, METHOD_BUFFERED, FILE_ANY_ACCESS)
struct STouchPanel {
BYTE n1;
BOOL bEnable;
};
DWORD nBytesReturned;
STouchPanel s = { 0, !disable };
KernelIoControl(IOCTL_HTC_HAL_ENABLE_TOUCHPANEL, &s, sizeof(s), NULL, 0, &nBytesReturned);
But indeed, it will not work on your phone
ZuinigeRijder said:
Actually it does lock ALL hardware keys, even "Power Off" key.
But maybe you meant the "Power On" key (actually, the same key).
That is why TouchLockPro does also lock immediately at Power On or Screen On (due to an external event, incoming call, or via pressing the power on key).
Code:
// --------------------------------------------------------------------------
// HTC Touch Panel
//
// Reverse engineered from HTC's TPEnable.exe and TPDisable.exe
// --------------------------------------------------------------------------
#define IOCTL_HTC_HAL_ENABLE_TOUCHPANEL CTL_CODE(FILE_DEVICE_HAL, 2698, METHOD_BUFFERED, FILE_ANY_ACCESS)
struct STouchPanel {
BYTE n1;
BOOL bEnable;
};
DWORD nBytesReturned;
STouchPanel s = { 0, !disable };
KernelIoControl(IOCTL_HTC_HAL_ENABLE_TOUCHPANEL, &s, sizeof(s), NULL, 0, &nBytesReturned);
But indeed, it will not work on your phone
Click to expand...
Click to collapse
Well right, power off/power on, but when the phone is powered off, I am not worried about it being power on by accident, only the other way around
Why can't any one make a program for WM5 that can disable the Power On/Off key?!?! Ugh!
Finally!
So far, this seems to be the best solution to accidentally pressing hardware buttons or screen buttons while the phone is in my pocket. When using bluetooth I was constantly hanging up on people. Also, I would accidentally call people with the phone in my pocket when an SMS or e-mail would "wake up" the phone and then 2 unknown presses of the hardware "answer" button would first bring up call history and then call the first person on the list. I'll wait a few more days and, if all is well, I'll make a donation. Thank you so much for your effort. (tried Sensorlock, S2U2 and Answerkeydisabler but none did the trick)
mspingeld said:
So far, this seems to be the best solution to accidentally pressing hardware buttons or screen buttons while the phone is in my pocket. When using bluetooth I was constantly hanging up on people. Also, I would accidentally call people with the phone in my pocket when an SMS or e-mail would "wake up" the phone and then 2 unknown presses of the hardware "answer" button would first bring up call history and then call the first person on the list. I'll wait a few more days and, if all is well, I'll make a donation. Thank you so much for your effort. (tried Sensorlock, S2U2 and Answerkeydisabler but none did the trick)
Click to expand...
Click to collapse
I am a bit surprised the other locking solutions do not work well together with bluetooth. Others reported indeed that TouchLockPro does not interfere with bluetooth and you can pick up the phone with bluetooth, although the keys are locked.
Enjoy the software
The other solutions worked with bluetooth but the bluetooth call connection would wake up the phone and activate either the screen, the hardware buttons, or both causing the accidental hang ups or calls. TouchLockPro locks both the screen and the hardware buttons. btw I have the touches set to 2 and the light sensor set to 500. Very convenient!
mspingeld said:
The other solutions worked with bluetooth but the bluetooth call connection would wake up the phone and activate either the screen, the hardware buttons, or both causing the accidental hang ups or calls. TouchLockPro locks both the screen and the hardware buttons. btw I have the touches set to 2 and the light sensor set to 500. Very convenient!
Click to expand...
Click to collapse
Good to know.
In the upcoming version TouchLockPro 1.9 I will introduce the ScreenOffWhenCallConnected option, so you cannot accidently press stuff with your ears. Also I will introduce the option UnlockWhenCallConnected, so you can still use the hardware keys, when the screen is off (e.g. for ending the call) and it is not locked when the call is ended from the other side.
Dependent of the bluetooth usage, if you have the phone in your pocket, you may want to disable these settings.
TouchLockPro version 1.9
I just uploaded version 1.9.2 on my new website.
See TouchLockPro thread for more details.
Many thanks to Dennis van de Sande, alias Mr_Q from XDA-Developers, for sponsoring/donating the website and domain.
I wish you a merry christmas and a happy new year!
Version 2.0
I uploaded version 2.0, which fixes some (small) issues and added some features, like unlocking when sliding the keyboard out (if available). See Version 2.0
[APP][Updated 11-01-2009] TouchLockPro version 2.1
I just uploaded TouchLockPro version 2.1. Hope this version is again more perfect.
TouchLockPro 2.2.1 with GSENSOR support for unlocking
I just uploaded TouchLockPro 2.2.1 with GSENSOR support for unlocking.
TouchLockPro version 2.3
TouchLockPro version 2.3 is available.
How to unlock using touchprolock?
Im using xperia (no gsensor, no light, etc) ??
royalbloodvi said:
How to unlock using touchprolock?
Im using xperia (no gsensor, no light, etc) ??
Click to expand...
Click to collapse
Then you must unlock with a key sequence, using TouchLockPro 2.8.2.
See http://www.zuinigerijder.com
01-09-01 pm NEW release ENU 2.0F RELEASE
Strongly recommended update and read below
All Langugaes could Update（EXCLUDING 0804)
But Only 0409/0404/0419 hidden the windows of incoming call notify.
ChangeLog:
1.Fixed little bug of 2.0e
2.using KBD HOOK instead of enablekeybbd,it disable kbd from low level.
NOTE:YOU CAN'T INSTALL IT WITH APP WHICH USED HOOK.
SUCH AS AE Button Plus.THERE IS ONLY ONE HOOK IN WINCE 5.
I THINK 2.0F EATEN MORE POWER THAN 2.0E
01-03-01 pm NEW release ENU 2.0E RELEASE
ChangeLog:
1.Fixed a dead lock bug with blocklist thread.it will produce strange problems
2.Add a new function. disconnect DATA connection (GPRS/EDGE/3G).
;;Code by UNICODE
;;one exe(process name) one line and at the end of the file make a enter.
;;e.g.
;;
;;
;; ;in front of a line means disable it
;; "/r/n" means a ENTER .Please do not input it
;; # means when all processes marked with # exit,disconnect the DATA connection.(GPRS/EDGE/3G)
;; NOTE:If DATA connection are created by other process (NOT marked by # or even not in the list below),
;; while no process marked with # running when all processes marked with # exit,nothing happen
;;
;; XXX.EXE/r/n Right format Enable it
;; XXX X.EXE/r/n Right format Ignore the spaces in front of a line.
;; XXX.EXE /r/n Wrong format Do not ignore the space int the end of a line
;; XXX.EXE ;YYY.EXE/r/n Wrong format ;Should be in front of a line.
;; ;XXX.EXE/r/n Right format Disable it
;; XXXX.EXE Wrong format There must be a ENTER in the end of last line.
;; #XXX.EXE/r/n Right format Enable it
;; # XXX.EXE/r/n Wrong format Do not ignore the space between # and XXX.EXE
;; #XXX.EXE/r/n Right format Ignore the spaces in front of a line.
;; #XXX.EXE /r/n Wrong format Do not ignore the space int the end of a line
;; ;#XXX.EXE/r/n Right format Disable it
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;NOTE:Case Sensitive
Explorer.exe
#UCWEB.exe
pword.exe
solitare.exe
#KingDom.exe
Click to expand...
Click to collapse
edit it and reboot then setting work.
you can find it in Windows
Please edit it with PC make sure it code by UNICODE
01-01-01am NEW release ENU 2.0D RELEASE
Strongly recommended update and read below
ChangeLog:
Fiexd a serious bug of 2.0C
lock fails
serious bugs
stop 10 hours
Im sorry Please uninstall 2.0C and waiting for new
09-12-31am NEW release ENU
Strongly recommended update and read below
This app depends on OEM driver.Maybe some oem drivers is different .The Microsoft just give a suggest .so if it works abnormally. I m sorry.
2.0C is same as 2.0B just add a reg value named Enable .
So it will not hang on OS without new styple lock, If 2.0B work will you donot need 2.0c
Many device do not implement boot message So abolish lock on boot.
there is no enough information to distinguish 6.1 and 6.5 ,So if your rom is 6.5 ,check new WM 6.5 lock .The default is uncheck it.
09-12-31am NEW release ENU
2.0B
Changelog:
1.Add option disable hardkeyboard when call connected
2.Add option blink LED when CALL connected or GPRS/EDGE/3G connected
3.Fixed some bugs of 2.0A
4.More robust.
5.Do not sign with MS SDK cert.cab
sign version will release tomorrow.it is same as today but sign.
I hope many people test it without sign.And report below.
(JUST FOR TESTING)
how to fixed device donot dim
HKLM\\SYSTEM\\CurrentControlSet\\Control\\Power\\State\\BacklightOff
bkl1:
4 or 2
09-12-28pm NEW release ENU
Strongly recommended update and read below.
All Langugaes could Update（EXCLUDING 0804)
But Only 0409/0404/0419 hidden the windows of incoming call notify.
[/COLOR]
For some bugs of uninstall app ,Please uninstall 1.9X then reboot then install
2.0A
ChangeLog:
1. Optimize some code .
COLOR="Red"]2. Add BlockProcessList.txt . one or more apps run which is in the list .when device dim ,it doesn't lock .edit it and reboot then setting work.
you can find it in Windows
Please edit it with PC make sure it code by UNICODE
[/COLOR]
3. fixed some bugs of 1.9 series.
09-12-24am NEW release ENU
Strongly recommended update and read below
Only 0409 can update other language please do not update.
Other language OS will find notify window in a while.
christmas version
Uninstall old
option:reboot
Install new
Change log：
1. Add lock sound。
How to replace sound yourself.
uncheck Enable sound and OK.
rename sound file to unlock.wav or lock.wav
copy them to window over write old one.check enable sound and ok.
just support wav format. it better no longer than 3 seconds.
2. fixed a faults. check incall lock , when a call coming ,a call coming notify windows will show by OS.It doesn't show again now.it 's related to language of OS .
（ language of OS: 0409.0404) has fixed.
For fix a bug when a call incoming ,show a notify window .show .
I need it 's name with different language.
for example
0804
电话 - 拨入
0409
Phone - Incoming
I need :
other languages. and language code: e.g 0804
09-12-20am NEW 1.9A release ENU
Strongly recommended update and read below
Maybe no body online on 12/25 so....release early.
Change:
1.add setup.dll to cab. it works after install without reboot.also uninstall it stop work without reboot.Delete all file and reg very clear.
But if you install any old one you'd better make a hard-rest .
2. separate lock trigger and stand-by. there are no relationship between them.
3.add delay time .it start from screen lock app run. but it work just you check lock and then stand-by
4.add energy optimization. Check it the stand-by means that suspend without call connecting and USER_IDLE with call connecting.
. But every app stop run.So be careful with checking it.e.g:if alarm ring ,it wake up device, but when it suspend ,alarm stop and silence.Uncheck it ,Stand-by means SYS_IDLE without call connecting, USER_IDLE with call connecting.
5.Separate ms sign 。So if it do not works please install cert.cab and reboot..
6. Fix all exist bugy.
09-12-17am NEW 1.8G release WWE
fixed:better exactly 5 seconds than 1.8F
debug: when ac on, screen still turn off one time.
some time screen off but no lock
when call disconnected, it doesnt lock within 5 seconds.
this is last one of 1.8
So you can make rom with it now.
next version . add a new option suspend time so you can set
not just 5 seconds.
09-12-16am NEW 1.8F release WWE
add a new option when on AC it still works.OR uncheck it .when on AC it unlock（in call or call lock still work)
debug: when ON AC,it do not dim if you check dim trigger lock
wake up while it lock,it do not suspend with 5 seconds for some device.
For some device ,,it do not dim if you check dim trigger lock .If you find this bug, please do a hard reset then install new cab.
fixed: when a call come or out a call ,old lock do not lock ,but HW key still lock.
09-12-15PM
If you find the bug below that is to say the device do not send a resume and on notify when device wake up.
that is so sad.
you can try new pm.dll drivers from oem.
or waiting for a new version.
bug:when device wake up with device lock,but the screen donot turn off with 5 seconds.
how into sleep state. just make you device off for a long time and do not run any app which prevent device from sleep.
C++, NATIVE,SMALL SIZE,SMALL MEMORY,INTERRUPT ,NO PROCESS,GOOD ROBUST。。
09-12-12AM NEW 1.8e release WWE
Christmas gifts
CONTINUE DOWNLOAD
Maybe the last one version of 2009
1.The new interface is easy to understand
2.There are no Dim and Light when backlight trigger lock
3.fixed some bugs of 1.8C when press power device into unattended mode but
smartlock will make it to SYS_IDLE MODE. this will not happen again
4.Most of the code rewrite,save more power.No sleep No poll ,All are Notification and wait...fewer and fewer bug
5.Be reg callback is very slow,So when you press power button trigger the lock app,this need a little time,so if you on and off quickly you will see the app locking,don't wary about it.
PS I need Multilingual。 German Spanish Portuguese Japanese French
Is any body help me ?
If you find unlocking WM LOCK APP twice issue .(not 3d part software.)
Export [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\State] of register and POST
09-12-10am NEW 1.8D release WWE
Fiexd some bug of 1.8C especially old style lock app issue.
09-12-08pm NEW 1.8C release WWE
fixed some bugs of 1.8b
if new lock is unchecked .Device doesn't lock with old lock app when out call or income call .
new：
1.when you receive a call while lock screen running.
Device will into USER_IDLE MODE NOT SYS_IDLE MODE within 5 seconds when call is connected
2 when you send a call while lock screen running.
Device will into into USER_IDLE_MODE NOT SYS_IDLE MODE even if call is not connected.
3.All the hardware key are locked . when coming a call or out a call. You can't receive or reject a call via any hardware key.If screen is off automatically within 5 seconds. (USER_IDLE) You can press any hardware key to turn screen on(INCLUDE reject or receive button.Do not warry about rejecting a call or receiving a call).You can't press power button.Because device is ON just into USER_IDLE MODE.
PSOWER MODE
ON :EVERY THING RUN WELL.
SUSPEND:EVERY THING STOP RUN BUT GSM/CDMA MODE.
USER_IDLE:SCREEN OFF AND YOU CAN TURN SCREEN ON VIA PRESS BUTTON BUT POWER BUTTON.
SYS_IDLE/SCREEN OFF MODE:SCREEN OFF AND YOU CAN ONLY TURN SCREEN ON VIA POWER BUTTON
If check out call connected lock ,when send a call beforce it connected , lock screen run be other reason when call connected.
Device still into USER_IDLE .key still lock
09-12-07pm NEW 1.8B release WWE
fix a bug of 1.8
suspend lock is same like suspend after lock.
when locking with 5 seconds .device ide.
09-12-07 NEW 1.8 release WWE
better save power and power button.
new change.
the suspend after lock if you check it.
if you start lock screen the device will into ide mode after 5 senconds(led light off,and you can't tape screen but press power button.but the program will go on.you can listen to music or make a call.If no program prevent it into suspend mode within 30seconds.The device will into suspend mode and just waiting a call,every program stop run)
)even you alway tape screen.
But if you unlock screen within 5 senconds , the device donot into ide mode.
any body understand me?
09-12-05 Next year(2010.01.01) it will be a new version.
Some new function.
The suspend time and suspend status.some program can set or reset .such as music player. video player. msn .
but the smart lock doesn't know which program set or reset .So new version have a program list.
you can chose it work or not work when some program run.
The new version can
I m sorry for stopping development and for my pool english
It will be continue.....
Hey here's a good summary, pictures, and features list for little program.
Thank ace10134 for providing.
http://thewingster.com/autolockscreen.aspx
PS: This app depends on OEM driver.Maybe some oem drivers is different .The Microsoft just give a suggest .so if it Doenst work I m sorry.
YOU CAN FIND LINKS IN MENU-SYSTEM
CHS-SMARLOCK
email to me.
thinks for donate:
sleuth255
support my work
This works excellent! I'll have to use this in conjunction with CSDEVCTRL to get in call locking though.
Edit: The in-call locking feature has been added! Thanks!
I'm gonna give it a shot. I really needed this.
Thanks.
upupup~downdowndown
could be great ! but even better in english, cause now, I've only squares ^^
can you describes the 3 lines, and the 2 soft buttons ?
Thanks
lpaso said:
could be great ! but even better in english, cause now, I've only squares ^^
can you describes the 3 lines, and the 2 soft buttons ?
Thanks
Click to expand...
Click to collapse
english.is any body give me a discription.? so I could complie a english version
3 when back light off .it locks
left buttons :yes
right :help->about
OK :yes
biosxjj said:
english.is any body give me a discription.? so I could complie a english version
3 when back light off .it locks
left buttons :yes
right :help->about
OK :yes
Click to expand...
Click to collapse
I have :
First line (checkbox) : WM6.5 ... ?
Second line (checkbox) : ?
Third line (checkbox) : ?
Can you tell us what is written on these 3 lines ?
Thank you
1 WM 6.5 use new lockscreen . gray when in wm6.1 or older
2 lockscreen when startup
3 lockscreen when suspend or back light off
Great !
Works really fine. Great soft
Change it to WWE
Hopefully the TS wont be mad at me
I have change it to display in English
Menu are as mentioned in the thread
cheers
Not working on Touch HD. It locks the screen using the old screen lock
gbjack said:
Not working on Touch HD. It locks the screen using the old screen lock
Click to expand...
Click to collapse
which version of your windows mobile .
you must check the first checkbox . if you want to use new screen lock with wm 6.5
upupup..
Hey, I might be a dummy but ... how do I access options?
HKLM Software\\Microsoft\\Shell\\LockScreen.
key dword value suspend =1 .lock when suspend
AutoRun =1 lock when startup
if you don't setup frequently you can
convert cab to oem
copy dll to windows
import the reg and reboot ..
it will work also.
Would be great if U could add into Your software ... to turn off screen after 5 sec when locked because now screen is on for too long. And battery is drain in this moment until it goes off. ... F.ex. to see the "time" for a sec and than screen goes off Then it would be the best apllication i`ve ever seen ! Simply and usefull !
The time you can set in setup- system-back light or setup-system-power
but there is no time to set up WHEN LOCKED ... I dont want to turn off screen after 10 sec (because it is minimal in there) because f,ex. when i`m using Opera and read any thread i don`t want to turn off screen in so short time. I just want to off it WHEN LOCKED
you means lock device but screen is on?
I mean ... step by step: Turn off device by POWER button. And when i want to check the TIME i turn device on and device goes lock (and that is great) but screen is ON for a long time ... i don`t want to use POWER button to turn it off again. I want to go back to off automaticyally in 5 sec WHEN LOCKED. We are talking all the time in situation WHEN LOCKED
Hi,
I noticed, that after a total standstill, there is now a little movement on the nike android front. I want to contribute a little share to that.
I have set up an autobuild service for the android kernel. I automatically uploads a fresh zImage with the newest patches every full hour. I also reenabled Vibration as I never had any problems with that. If there are still people aound that need a kernel without Vibration let me know, I could set up a second build, too.
[update 03.03.10] Kernel without vibration for niki100 included.
The fresh kernel is found here.
[2010.03.31]UPDATE:
- IRQ wakeups enabled -> sleepmode 1 works
- Red led flashes when sleeping
- hw3d for eclair can be chosen in commandline (not fully functional)
- Double press cam button is home on 20key nike now
[2010.04.08]UPDATE:
- Some Keypad and defconfig changes to support ubuntu
[2010.07.01]UPDATE:
- Added .patch files to downloads for all who want to compile on their own (Recommanded! Some new devs would be very welcome here)
[2010.07.02]UPDATE:
- Removed .patch files again, they don't work as intended. Just 'git apply' the "Changes compared to stock kernel" instead...
- Fixed audio (please give me some feedback if it works now)
[2010.08.30]UPDATE:
- I just was tipped of that the service has been down for full 3 months (thx youngsien)
- Service is now online again, but will from now on only be updated once a day (should be enough)
Happy Androiding everyone!
mblaster
PS: If you don't know what a zImage is or does: It is the core of the Android operating system. It is usually in the same folder like haret.exe. You can tell your Android build to use a specific zImage in default.txt
Nice idea...
That's what we need to make good android builds working on nike.
The vibration ALLWAYS freezes de touchscreen, maybe a htc p5500 model issue.
i will follow this post hourly...
OK, I included the stock kernel without vibration in the service. Have fun!
@arleybarros: I dind't mean to post here hourly, but my server will keep the kernel up to date
the stock kernel freezes after a little vibration..
shouldn't vibration be disabled on stock release?
nik2208 said:
the stock kernel freezes after a little vibration..
shouldn't vibration be disabled on stock release?
Click to expand...
Click to collapse
Yeah, you're right. The files were exchanged by my build script... Thanks for the hint, everything should be fine now.
*bump*
New updates in first post... I hope everything works
mblaster,could you post your default.txt cmdline, please? seems like nike still does not sleep, there no signs of flashing red led on mine.
my cmdline: "pm.sleep_mode=1 mddi.width=320 mddi.height=480 hw3d.version=1"
I'm running msmissions eclair.
are you running it without rootfs? there seems to be a problem with the norootfs basefiles that prevents sleeping.
yup, norootfs.
ok, got progress, I've runned android again, now nike felt asleep and flashing red led. wakeup works too - double tap on dpad center. I think that was because there was no reboot after installing after data wipe, norootfs missing some controls on power.
also, there is another power problem - MSM's standard reboot/poweroff commands from android does not working, can we fix this? device just freezing, seems like some revision on vogue's power controlls broken ours.
rzk333 said:
also, there is another power problem - MSM's standard reboot/poweroff commands from android does not working, can we fix this? device just freezing, seems like some revision on vogue's power controlls broken ours.
Click to expand...
Click to collapse
The same here with the norootfs stuff. I tried myn's donut on sqsh and norootfs. SQSH works like a charm (powermanegement, net, reboot, powerdown), but the same build/kernel combination has the problems mentioned before...
[minor UPDATE] Double press cam is home now on 20key nike
here is that someone is going to operate the headphones??
i can't use internet.
help me.
i set my carrier.but i can't use internet
[minor UPDATE] Double press cam is home now on 20key nike
Click to expand...
Click to collapse
can we make something about "Enter" key on niki100?
I've tried to run kaiser ubuntu and stuck with login - I simply cannot press enter :/
maybe some virtual button can be mapped to something?
rzk333 said:
can we make something about "Enter" key on niki100?
I've tried to run kaiser ubuntu and stuck with login - I simply cannot press enter :/
maybe some virtual button can be mapped to something?
Click to expand...
Click to collapse
Where would you like to have the enter key? I can try to fix it in, but i am not sure where to put it.
Some ideas would be:
- Put enter on cam, press WinKey once = menu, press Winkey twice = home
- Put enter un the key on the lower right (InternetExplorer in winmo?), probably better, but i dont know for shure which button it is. Dou you get a 'z' if you press it? I guess you do:
Code:
{{KEY_Z,FALSE,FALSE,FALSE,FALSE},FALSE}, // UNKNOWN KEY
Can you confirm that you get a 'z'? I will change it to enter then.
€: If ubuntu works it would be nice if you could start a thread about it. Would be great to have a full blown linux box in your pocket
Latest Kernel is working nicely on my Nike100, really impressed with the battery life now, great job on getting sleep to work. I have a request though... would it be possible to make one more kernel for the Nike 16 key? at the moment you can't type on it or use any of the keypad as the mappings are all wrong. If it would help I can tell you what keys are currently mapped to what on the 16 key. I don't know how hard it would be to change but if it is doable I would really appreciate it as it is really the last thing that is stopping the port from being day to day usable for me and other 16 key users. Unfortunately the onscreen keypad is just a bit small for typing with daily.
Thanks, hope its not too hard a fix.
MWG_Thomas said:
Latest Kernel is working nicely on my Nike100, really impressed with the battery life now, great job on getting sleep to work. I have a request though... would it be possible to make one more kernel for the Nike 16 key? at the moment you can't type on it or use any of the keypad as the mappings are all wrong. If it would help I can tell you what keys are currently mapped to what on the 16 key. I don't know how hard it would be to change but if it is doable I would really appreciate it as it is really the last thing that is stopping the port from being day to day usable for me and other 16 key users. Unfortunately the onscreen keypad is just a bit small for typing with daily.
Thanks, hope its not too hard a fix.
Click to expand...
Click to collapse
Do you have this parameter in default.txt?
Code:
board-htcnike-keypad.keypadlayout=1
If not, add it and remove other entries concerning keypad layouts (might be there from kaiser). Most of the keys should be mapped correctly. Enter key seems to be missing. Could you try to press the button on the lower right (Internet explorer or something like that, depending on the branding of your phone) and tell me if it prints the letter 'z'?
Where would you like to have the enter key?
Click to expand...
Click to collapse
iexplorer key is useless in ubuntu and android, I think, so we can remap it, camera home key is used widely in android, you dont need to open up slider to access menus
If ubuntu works it would be nice if you could start a thread about it.
Click to expand...
Click to collapse
that would be nice too, now we can run LXDE or other X windowmanager compiled for ARM, ubuntu boots up fine and works like on kaiser. you can learn how this happen for ARM in Omegamoon's blog
The patched kernels will be ready on my download page in a few minutes (compiling...). Please let me know if it worked.
Both the on-screen keyboard and the menu keep annoyingly popping up on my Viewpad7. It is driving me crazy.
At some point I thought it had to do with how I moved the device around, but I still think it's a random thing. It was/is a problem before and after loading it with a custom rom.
Is this a known hardware (or software?) bug ? If so, is there a cure for this? I have looked for settings, but was unable to find them. Thank.
SWVer=3.16K
MODEL=FM6-0001
HWVer:103
Android 2.2.2
Hi
Have the same problem and some other users here too.
Seems the Touchscreen/Softkeys are faulty and have to be replaced.
I bought mine 1 week ago and day by day it went worser. I didn't upload a custom rom so far, so it's a stock problem.
Now every 2nd time I take the device it vibrates and menu/keyboard keeps popping up/down. Looks like, the "menu" softkey does his own business, right?
Also the G-Sensor/Compass seems to be defective for me - after a few hours I have to calibrate always.
I made some videos, look at this thread:
http://forum.xda-developers.com/showthread.php?t=1258052
Where have you bought yours?
Regards
With my device it was when I held it in landscape mode and touched the bottom part of the right side or the rightmost part of the bottom of the device itself. It was also HWVer 103. You will most likely have to get the screen and soft keys replaced like I did.
Sent from my ViewPad7 using XDA App
Or, it could be just be a "normal" thing with Froyo OS itself, I've noticed it on 2 newer build - both ITE enabled - in U.S. market.
SWVer=3.41
MODEL=FM6-0001
HWVer:107
Android 2.2.2
This happened only on certain Apps - even when Auto Rotation under Settings are turned off, it will switch to the "opposing" mode and won't go back once it make that orientation change, i.e. YouTube whereas Angry Birds will stay landscape all the time. Device has been calibrated & sensors working, as I had no issues with GPS status & Maps, etc.
Should be a simple fix or patch on the OS or custom ROM .... BTW, I'm running the stock, rooted 2.2.2 ROM while waiting for an OC one with the ITE kernel working to boost the Quadrant scores, LOL.
Ours seems to be more a hardware problem since it happens anywhere, with autorotation on or off, after a complete hard reset (without any additional apps installed) and simply by touching the case itself (not the screen)...
astuermer said:
Ours seems to be more a hardware problem since it happens anywhere, with autorotation on or off, after a complete hard reset (without any additional apps installed) and simply by touching the case itself (not the screen)...
Click to expand...
Click to collapse
Hmmm, interesting after I checked out a few YouTube videos & it sounded like it's all HWVer 103 yet running Froyo 2.2.2. Is the device ITE enabled as I noticed that the pop-up keyboard is "standard" whereas mine has Swype style keybaord with ITE.
It's a pain to get it returned, exchanged & repaired at the authorized factory service center and be without the use for 2+ weeks, unless one's within a 30 days period & can send it back to the place of purchase for a new one (could take just as long)
Another post mentioned a new stock ROM just being released, it might be worth an effort or try to flash it (FM6-3350-0-1008-A01.nb0) upon downloading & using the SUTL3 app to do it - would need to root it again - if one is brave enough (since it's going back for repair/exchange anyway?)
BUT, I'm guessing whether this newly released stock ROM is for ITE devices vs. non-ITE ones with HWVer 103, 106 and 107's ???
The button clicking by itself or when under vibration is an HW fault.
pulling the back off and wedging some paper near the touch IC to keep pressure on it has fixed mine.
Brought it back to the store for repair. I think they put a new screen and cover (back) on it. Works like a charm.
flez1966 said:
The button clicking by itself or when under vibration is an HW fault.
pulling the back off and wedging some paper near the touch IC to keep pressure on it has fixed mine.
Click to expand...
Click to collapse
Can you describe more precisely how and what did you do or can you (better) do some photos?
Did you pulled off a back cover and inserted a piece of paper somewhere?
Need to experiment
Software solution
This is a solution from a user 'retrochip' from 4pda.ru forum
(Link to original post in Russian and i'm not able to post is here)
1. Root your device (can be done with Gingerbreak)
2. Find out codes for Menu button and Search button (229 and 217)
3. Edit configuration file /system/usr/keylayout/qwerty.kl (you can use RootExplorer)
In qwerty.kl:
Find text:
key 217 SEARCH WAKE_DROPPED
and change to:
key 217 MENU WAKE_DROPPED
Find text:
key 229 MENU WAKE_DROPPED
and change to (just comment it with #):
#key 229 MENU WAKE_DROPPED
Save and reboot.
Now Menu button isn't active and Search button works as a Menu button.
No annoying random popping keyboard anymore.
This has killed my all soft buttons, now the only option is to fix it in adb, because screen keyboard doesn't appear in terminal, I need to touch menu then screen keyboard.
We are building a custom hand held device with MT 6580 chipset and Android 5.1.
- Device has 4 buttons that will be used to capture user input data like counts.
- A pre loaded app runs on the device to receive the key events and process the data.
We want the device to wake up and resume the activity when the user presses any of the 4 buttons while the device is in sleep mode.
Tried anything similar? Is it doable?
Thanks