Related
I installed the Android OS on my phone that was found on this post:
http://forum.xda-developers.com/showpost.php?p=5480057&postcount=7353
I updated it and everything to what he has but occasionally my hard buttons at the bottom will either stay lit or not respond at all. Or it will even go crazy as if I were sitting there spinning my finger around the middle hard button thus making it highlight everything on my menu. That also causes trouble because then it thinks that when I press the home key it decides to bring up the call log screen.
Is there anyway to disable the "iPod Scroll" on the center hard key?
Dude. You should update to the newest build. And update Rootfs and zImages.
everything is in the XDAndroid thread in this forum.
I updated to the one found here:
http://forum.ppcgeeks.com/showthread.php?t=104276
And my scroll wheel and hard buttons still mess up from time to time.
What device do you have? RAPH100?
Sorry I don't know the developer names but its the HTC Fuze for AT&T so it's either the RAPH100 or just the RAPH. The start up config I'm using for Droid is the RAPH config.
Its best not to touch the capacitive DPAD and scroller during boot up. (safe time is when you can see a n d r o i d or the bootscreen.) This and having the pad clean is very crucial if you don't want it going crazy.
Try cleaning it with a wet cloth/tissue and try again.
I also had a screen protector which was massively scratched which caused problems. Ever since removing it the DPAD has been working great.
dude i totally have the same problem.
i ve tried wipe it clean but no luck.
sometimes everything work great but all of a sudden the buttons go wild and start flashing. after that, nothing will bring it back to normal. maybe after a few minutes if will stop blinking, lefting one or two LEDs on, and the button is then less responsive, though still works if you place your finger on the button you want for a few seconds before pressing.
I've seen a few people complaining about this but other says its because of our own device...
However everything works normally in WM... so i guess it might be about the sensitivity or something like that.
no matter it get fixed or not, I do want a method to disable the scrolling too, and maybe the left and right buttons, because they never work even under WM...
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
also getting the exact same problem a lot, with everything up to date, clean, and not touching on bootup. would it be difficult to implement a code where we could just disable the middle scroll wheel? thats the thing that causes the most problems, and its not really that useful anyway.
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
twiggy159 said:
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
Click to expand...
Click to collapse
Its not off topic at all. I have been using Xandroid as my one and only OS for about a month now. I do charge it quite often, and I leave it on my desk at work on a charger. I also charge it at night as I sleep. I start off the day with 100% and can go 6 or so hours without issue. I continuously get 3-4 days in a row without a reboot or a failure. I find that it has become a suitable alternative to Winmo. The difficulty that I have is that there are primary functions which I miss a bit (camera mostly). But I feel that in order for me to fully understand and appreciate this, and to be able to contribute as a quasi beta tester, I must be willing to spend as much time with it as possible. I keep up with these forums on a regular basis , checking them sometimes 2-3 times a day. It is difficult to distinguish helpful info sometimes, since there are several versions floating around, and not everyone has the same setup & environment. I search as much as I can to find my own solutions, and for the most part, I'm relatively proud of myself. I usually only chime in when something is really bugging me, or I see something valuable that I can add to a conversation.
This issue was one that I had seen a few people talk about, and it had always been chalked up to being a dirty sensor type of thing, or someone touching the pad while it was booting. Having tried all of these solutions with no success, I had come to the determination that it was not constant, it could be ignored or dealt with, and eventually someone would fix it. It is most definitely not a "hot" item, so I never made a stink about it. Now that others have brought it forward, I decided to add my experiences.
I have loads of respect for the developers, and realize that they are not doing this for me. They are doing it for themselves, and fortunately, they share it with us. I am envious of their ability to make this project possible, and have no expectation or demands. I just take what they give us, and try to make it work for me.
Just my two sense, I'll step away from the pulpit now.
+1 for Navigation Wheel or capacitive D-pad issue
reverendkjr said:
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
Click to expand...
Click to collapse
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
spideyngo said:
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
Click to expand...
Click to collapse
I think mine is a RAPH100... i cant take out the battery and double check... but mine is a unbranded version fron 3 australia... which i remember is raph100. and i totally have the same issue so this is not only happening on raph110 i believe.
Hey guys,
I was having the same problem in wm6.5 using many different energyroms, i disabled the scrollwheel altogether within the registry, never used it anyway. I am now getting the same problem in Android. is there is a registry parallel in android?
btw using a RAPH100 (all above fixes did not work)
devs, is there no easy way to implement a disable scroll wheel setting?? i swear that wheel will drive me crazy at times
While this could be an issue with all Raph 110's (AT&T Fuze), I think it is just a subset due to hardware problems. For me, the problem only happens occasionally and it does not only occur in xdandroid, but also in WM. There is an HTC tool (for WM) named NavDbgTool.exe that will show you what is happening with the capacitive buttons/touch area on the Raph. For me, when I have issues it lights up all over and shows touches occurring that are not occurring. I know of at least one XDA member (Captain Throwback) who was able to get a replacement phone (a Tilt2) from the insurance carrier because of this issue.
Perhaps this is a problem that eventually happens with all Raph 110's due to a hardware flaw. If that is the case, maybe enough complaints to AT&T will cause them to replace all of the devices (similar to how Sprint is replacing all their Touch Pro's due to overheating issues). In the meantime, if you have insurance, you should be able to get a replacement phone, just use the NavDbgTool.exe to document the problem in WM.
Also, due to this issue, it would be nice to have the option to disable the capacitive touch area on the Raph 110 in xdandroid (while keeping the D-pad working). I don't use it for anything now that zooming doesn't work for recent versions of Opera in WM.
I'm starting to think that this is Winmo ROM related. I noticed that since I've used the ROM that I have installed right now, the amount of times this issue has affected me has been slim to none. I am currently running the an NRG rom from june 12 with sense 2.5.
link: http://hotfile.com/dl/47992175/ccd8b44/Energy.RAPHAEL.21905.Sense2.5.Jun.12.7z.html
I'm not guaranteeing anything, but its working for me.
Maybe it has something to do with a package that is built into certain roms. I have noticed a few times where the winmo ROM i have loaded will affect Android's performance as well. The ROM that I am currently running was also what provided me with the ability to get GPS working in Android.
I hope this helps some of you.
I don't think it has anything to do with WM. For me, it only happens in Android.
firstly i have a raph100 that has this issue too, so its not just raph110
secondly, for me, this happens in wm too but a lot less frequently and seems to repair itself. It happens in android 70% of time when i boot, the 30% else happens later...
newly released zimages seem to shutdown the capacitive panel when sleeping, and this solved my problem a little bit since every time it goes crazy I can put the device in sleep then resume it...
But when it goes asleep the two buttons on the right act as back, the two on the left act as home. I think there is only one physical button on both sides, the touch figures if you are pressing back or end.
Sent from my AOSP on XDANDROID MSM using XDA App
I am using Myns Android ROM withthe wifi update + 110 pixel density update, booting via SD card and every now and then I get a graphical glitch/system crash that shows as thin, black and white stripes on my screen.
Anyone know what might be the cause/how I can fix this?
If i chose to install to NAND, would it be more stable/faster? And can I simply flash it with a WM ROM to go back to "normal"?
Thanks!!
I cant say about the glitch, try changing the kernel maybe. But your second and third questions have been asked and answered so many times, its ridiculous. But since its your first post, I'll answer:
would it be more stable/faster?
Click to expand...
Click to collapse
Yes to both
can I simply flash it with a WM ROM to go back to "normal"?
Click to expand...
Click to collapse
Yes again. Also, Try using the search button in the forums, and read the stickys, go through some threads etc.
My apologies for not going through the threads properly.
I half knew the answers to my 2nd and 3rd question, but wanted clarification
I am trying Super Eclair Lite, and whilst wifi works well, I cannot hook up to 3G(gprs/wap/hdspa/EDGE etc)
I can call and make/receive texts though :S Hit this glitch a couple of times too, but i noticed it seemed to happen when putting the device to sleep, so I changed the screen setting to 30 minutes and turned of animations etc.
p.s. How do you remove widgets?
graphical glitches are usually caused by using the wrong panel type in default.txt when using haret, or the wrong NBH panel type when using Nand, to fix the first, edit default.txt, to fix the second flash another NBH with another panel type, (panel type is usually in the filename).
To remove a widget, press and hold on it, then move it to the bottom of the screen.
Apologies for being a totaly newbie, but what are the "panel types"? MY default.txt shows the correct resolution, but I cannot see anything about panels (I might just not be looking hard enough lol!)
I now have a problem when booting from the SD card that my resolution is "bigger" (icons are larger and overlap, menu items are larger too) But it was fine before i rebooted....
Any help for the GPRS issue?
mr_pablo said:
My apologies for not going through the threads properly.
I half knew the answers to my 2nd and 3rd question, but wanted clarification
I am trying Super Eclair Lite, and whilst wifi works well, I cannot hook up to 3G(gprs/wap/hdspa/EDGE etc)
I can call and make/receive texts though :S Hit this glitch a couple of times too, but i noticed it seemed to happen when putting the device to sleep, so I changed the screen setting to 30 minutes and turned of animations etc.
p.s. How do you remove widgets?
Click to expand...
Click to collapse
You can remove widgets by long pressing on them until the bottom tray becomes a bin/x or something similar, then drag them to it.
About the 3g problem, I had that a while back after installing a new build, what solved it for me was changing the kernel. I had flashed to nand so I simply got another nbh. For you it might be zimage. If you say you got that graphical glitch when the device went to sleep, then you should try changing your panel time. For a good smooth android experience, you will have to take some time, and flash many different nbhs/updates and change settings etc to get what works best for you.
I am trying out Myns Warm Donut again with the wifi update.
How can i change panel time?
Dunno if this helps but I managed to get GPRS/3G working on SuperEclair. I had to manually put in the APN and made sure the mcc mcn codes were right.
When i changed the codes the APN disapeared from the list but data connection established itself after a couple of minutes.
This is the link I used to get the right APN codes:
http://george.insideiphone.com/wp-content/uploads/2007/12/mcc-and-mnc-codes.pdf
For NBH files the panel type and resolution is in the filename: KAISIMG-PANEL1-320-ECLAIR.NBH : the filename shown is for Panel1 resolution 240x320.
To change panel type simply flash another NBH with panel2 or panel3, it will not affect your install, since the android nbh's don't format Nand, this is done by the installer
For Haret installs the panel type is changed in default.txt look for the line: board-htckaiser.panel_type and change the value to 1, 2 or 3.
Wow, that is great! I've searched for a solution for this problem a long time, but this is the first thing that works for my Kaizer 130.
Many thanks!
I had android running off the sd card most of the day yesterday, using the panel type of 1 worked well (did notice the odd glitch when coming out of sleep mode, but it didnt crash)
still not sure what the panel type does, can anyone explain? (curiosity really)
However, I tried to use the camera, and after switching to vide and back again to photo mode, android crashed.
I can suffer not using the camera, as its nothing amazing.
p.s. anyone know if you can remap the buttons? as the hang up button puts the phone into sleep mode, the wheel doesnt do much, and other buttons dont do much either.
Panel type refers to the LCD panel, there are 3 different types of panel fitted to the kaiser series, one manufactured by Sony, the other two by Topoly, functionally they are identical, however there are some differences in the electronic controllers fitted to each, which in winmo is detected automatically, however Android is unable to detect the differences and the correct type must be passed to the kernel at boot time, either by boot parameters in default.txt or hardcoded into the NBH. Due to the way electronics factories work, the panel type depends on which one was available at the lowest price, and shortest lead time, when it was required, hence the reason for the confusion, since some people still think that panel type is set for certain models of kaiser, which is inaccurate, since both my KAIS130's have different panels fitted.
Camera does not work in any Eclair build yet, it does in Donut builds, however it's still a little low quality even on the 3Mp Kais130, Video does not work on any android builds very well, if at all.
Remapping buttons can only be done by recompiling the kernel I think, however after a while the button layout becomes second nature, I actually get lost using winmo now, lol.
My Screen has totally stop touching and Ive searched and searched for a solution.... and yet havent found any. I deleted the ts-calibration file and yet still screen no work
BUMP Help!
You mean that the screen is not working within android of with windows mobile?
If you mean windows mobile then your screen is broken or if you think it is because of the cab, you can try a hard reset.
If it is only in android then uninstall this version of android and download the .rar and extract it to your SDcard.
I have sort of the same issue. My screen doesn't work (most of the time). For some reason it is responsive sometime (not clear how to recreate that). I can see the screen is responding, although if I go to the menu and try to select a icon with my finger it holds the icon and drags it (and I cannot let it go)
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Deleting the calibration file doesn't work for me. Also I have tried hard resets and rom upgrades several times, with no succes. It looks like installing android changed something, but doesn't set it to his old state after removal.
Anybody?
This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.
yea i was having the same problem and couldnt figure out a solution, i deleted the ts-calibration, i've tried deleting all android files and starting over but the problem still exists. I think it might have something to do with the little bit of moisture i see under the screen because before i started seeing that, it used to work. But the screen works just fine when WinMobile is running so i dont know
If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?
arrrghhh said:
This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.
Click to expand...
Click to collapse
No, in both. This problem originated from the fact I was never able to start up a blazin android. It started booting, but for some reason never finished it. With the previous editions I never had any problems.
arrrghhh said:
If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?
Click to expand...
Click to collapse
I know you are replying on another user, but I still want to respond
Yesterday my screen was responding for a short moment. I have replaced the WinMo rom after that several times, no success. Also deleted android and reinstalled it again. (I've been trying trial and error for a while now, without any success.)
My WinMo rom btw was an energy build. Any similarities with other users experiencing this issue?
Is there some internal memory where these type of settings (keyboard layout and such) are stored and what not always change if you upgrade roms?
Perhaps I should go back to the original T-mobile rom.
Just upgraded to the original tmobile rom, but I'm stuck at the WinMo startscreen (tap the screen to start using it for the first time) I noticed that if you slide the phone open (keyboard visible) the display of the screen is correct. If I flip it back I'm missing parts of the screen.
dwaaz said:
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Click to expand...
Click to collapse
I'm sorry for spamming this topic, but isn't it really weird that only for entering your pincode the numbers are correct, but afterwards the layout is all messed up?
6_7_8 = 123
Y_U_I = 456
H_J_K = 789
N=0
I have the feeling my phone is using system files (after login) of a completely different phone (and no.. I did use the right rom's ) This goes for the keyboard as well as the screen issue.
any bright ideas?
Just to bring it under the attention again, because I'm on the edge of sending it back to t-mobile. (I hope they are not going to charge me because I have a diamond 2 that also needs repairing, touchscreen doesn't work as well, and I'm seeing some costs coming up there. For some reason I always manage to wreck my phones in the first 2 years. )
Any bright ideas?
I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slighty and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App
It worked!
trotmanc said:
I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slightly and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App
Click to expand...
Click to collapse
I was kind of skeptic here of this solution, because my phone looked quit clean. But there I was, on visit with my parents, fiddling with my phone, thought; let's put my nails between the lines next to the touchscreen..... and wtf.. it worked My screen is back up. Very surprising but good.
No I only have my keyboard to worry about. Any thoughts on that?
Hey guys,
Quick question here: Is it possible to disable the physical slide-out keyboard in either WM or android (specifically android) without having to take the thing apart?
I saw this thread:
http://forum.xda-developers.com/showthread.php?t=692022
But that didn't work for me. Has anyone else had luck with this solution? Is there any other way to disable or turn off the keyboard without physically unplugging it?
Why would you want to do that...? If you don't want to use it, then don't. The on-screen keyboard is pretty good, and you can get swype or whatever else you want... You never need to slide the kbd open.
So what's the point?
The keyboard is damaged. It sat in a puddle overnight, so now whenever I need to input text, the keyboard just outputs random characters. Constantly. Even when the physical keyboard is not engaged. I've been able to work around it in WM (its still VERY annoying), but as soon as I boot into android, it automatically goes to the browser and starts the random text thing again. I cant keep it on the home screen for more than half a second before it goes opens the browser again.
Whats even weirder is that I checked the water damage stickers on the phone and none of them have turned red.
I'm assuming some of the keys shorted out and are now always "on." So I just want to disable the physical keyboard and only use the soft keyboard.
Ouch. Well, if you have TEP just get the thing replaced - especially if it doesn't show any water damage.
With that said, I'd say the best option would be to physically disconnect the cable. I'm not aware of any software way to disable the kbd in Android... Curious, how do you do it in WinMo? I'll poke around to see if there is any way to do it in Android, not sure how it would be done. There may be a secret option that I'm not aware of, because it never comes up
The simplest option is probably to create a minimal microp key layout that only contains mappings for the three front panel keys handled by microp, and then perform surgery on your init script to replace the existing keymap entry for your rhod with your new minimal one. Nevertheless, init is embedded in your rootfs.img and isn't easily edited from a Windows computer. Thus you'd need to either copy init over to your sdcard with the terminal emulator inside of android, or install the Android SDK onto your computer so you can pull/push the file with adb. If you have a computer running Linux then there are more options.
Pop over to this thread: http://forum.xda-developers.com/showthread.php?t=828011&page=3 and maybe you'll get some ideas about how to create yourself a special keymap with nothing in!
Thanks for the info guys. I really no good at doing any deep editing, so a lot of those suggestions just went right over my head :-}
I know this is a big request, but if someone has the time and knowledge to create an empty key map for me and tell me how to apply it, that would be greatly appreciated. If not, no big deal. I just don't want to screw up my phone any more than it is, ya know?
Roots08 said:
I just don't want to screw up my phone any more than it is, ya know?
Click to expand...
Click to collapse
LOL you don't really seem to have much to lose at this point...!
Sounds like it may be more complex than originally thought. Unplugging that cable still seems to be your best bet... Otherwise you'll have to muck around with things everytime there's an update.
rootfs with bad kbd option
Roots08 said:
Thanks for the info guys. I really no good at doing any deep editing, so a lot of those suggestions just went right over my head :-}
I know this is a big request, but if someone has the time and knowledge to create an empty key map for me and tell me how to apply it, that would be greatly appreciated. If not, no big deal. I just don't want to screw up my phone any more than it is, ya know?
Click to expand...
Click to collapse
Download the rootfs found here. and follow these instructions:
1) Uncompress the file via the 7zip utility.
2) Rename it to: rootfs.img
3) Copy it over to the android boot folder (usually andboot) on your sd card.
4) Open up the file startup.txt found in the same folder with your favorite text editor.
5) Find the line that starts with set_cmdline and look for an entry on that line that begins with physkeyboard= and change its setting to: physkeyboard=rhod_badkbd
6) Restart your phone.
Since you're the one who has requested this, you're my designated tester. It should turn off all your keyboard keys. It should also leave the keys on your front panel working. Let me know how it works for you. If it works fine I'll submit this modification for inclusion into XDAndroid. If it doesn't, we'll have to tweak it further. You can thank Arrrghhh for talking me into doing this.
I have had this procedure work on several phones....
Take the battery out.
Submerse the entire phone in alcohol. The alcohol will displace the water in the phone. After a minute, take the phone out of the alcohol. The alcohol left in the phone will evaporate. After 24 hours, place the battery back in the phone.
Should work like new.
Although I'm a fairly experienced WinMo user I was initially completely dumbfounded by TouchLockPro's setup UI. For some reason, after reflashing to Jackos ROM (after using DeepShining for a day - brand new TP2) values i know should be in some boxes on the Nav Sensor tab are blank and I have no idea what to put in them. The manual - what exists of it - is indecipherable to me in places and the Quick Setup guide on the web site is anything but.
I tried choosing the phone profile from the small dropdown box (to 6: 'HTC Rhodium (Touch Pro 2)') but even after resetting all the TLP settings to Defaults and trying again, I still can't get some things like the zoombar unlock features to work. (just can't get it to accept input to perform lock/unlock actions). The proximity sensor constantly reports -1 or 0 even though it's marked as enabled in the registry and obviously works because the screen blanks when I'm making a call (and turns on again as soon as I take it away from my head).
I really want to love this program and feel that it solves the problem I'm currently having (...no good device lock!) but I can't figure out how to configure it correctly to actually do what I expect of it. Anybody else who's run the gauntlet with the TLP setup interface care to give me some pointers or point me at a good setup tutorial?
Cheers
Chris
christopherwoods said:
Although I'm a fairly experienced WinMo user I was initially completely dumbfounded by TouchLockPro's setup UI. For some reason, after reflashing to Jackos ROM (after using DeepShining for a day - brand new TP2) values i know should be in some boxes on the Nav Sensor tab are blank and I have no idea what to put in them. The manual - what exists of it - is indecipherable to me in places and the Quick Setup guide on the web site is anything but.
I tried choosing the phone profile from the small dropdown box (to 6: 'HTC Rhodium (Touch Pro 2)') but even after resetting all the TLP settings to Defaults and trying again, I still can't get some things like the zoombar unlock features to work. (just can't get it to accept input to perform lock/unlock actions). The proximity sensor constantly reports -1 or 0 even though it's marked as enabled in the registry and obviously works because the screen blanks when I'm making a call (and turns on again as soon as I take it away from my head).
I really want to love this program and feel that it solves the problem I'm currently having (...no good device lock!) but I can't figure out how to configure it correctly to actually do what I expect of it. Anybody else who's run the gauntlet with the TLP setup interface care to give me some pointers or point me at a good setup tutorial?
Cheers
Chris
Click to expand...
Click to collapse
You will have more luck when you post your question in this thread:
TouchLockPro thread
So also others can help.