[Q] Complete Froyo Bundle - FRX06 - HELP! - Touch Pro2, Tilt 2 Windows Mobile General

I believe this should just be an additional post to the following thread:
HTC Rhodium: Touch Pro2, Tilt 2 -> Touch Pro2, Tilt 2 -> Android Development **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes
but for whatever reason i cant post there. i have been a member of this forum for a long time but havent posted because ussually i can find everything i need by seraching. anyway to my question...
I have an old tp2 that im trying to turn into a wifi phone for a friend. i have followed the instructions presisely as insturcted in the first post of the above thread. the android os is fast it loads and everything works except wifi. i need the wifi to work so i can add the applications to make it into a wifi phone. any and all help would be appreiciated. the phione is a RHOD400. i have verified the correct startup and gone step by step several times to get it running. the wifi does work under windows mobo 6.5. if i goto settings-wireless & networks-Wi-Fi Settings i am able to enable he wireless but it just blinks scanning every couple seconds and doesnt find any networks. i have tried manually adding the networks and i have completely removed all security from the network to make sure that isnt causing the issue. i have tried it on multiple routers and it never sees nor can it connect with manual configuration. i am running out of ideas. PLEASE HELP! thanks in advance

i have the following problems with froyo android os.
1. the command line in startup text file acpuclock.oc_freq_khz=614400 ore set acpuclock.oc_freq_khz=614400 wont work. it wil say problem in command line 1.
2 the buttons led wil keep on lighting all the time not funny if you want to sleep.
sorry for my bad english im dutch.

there is your prob.
Things broken in this build:
BT - fails completely - fix is in the works.
WEP on wifi doesn't work. I heard an app called 'wifi-ace' (on the Market) fixes WEP!
3.5mm for RHOD400/500
There's a lot of other things that will break at random, I know I list it as stable - but it's not really. Hence the reason it's in quotations.
at the moment gingerbread camera wil only work in dark places if too mutch light get in it wil crash. the other sad part is that is got a lots of SoD. wil try it with g3 off. heard that wil fix it. wil also go back at froyo build. if some one find froyo build nice plz also try gingerbread. realy nice looking.
keep up the good work

koetjeboe91 said:
i have the following problems with froyo android os.
1. the command line in startup text file acpuclock.oc_freq_khz=614400 ore set acpuclock.oc_freq_khz=614400 wont work. it wil say problem in command line 1.
2 the buttons led wil keep on lighting all the time not funny if you want to sleep.
sorry for my bad english im dutch.
Click to expand...
Click to collapse
1. this setting goes in "set cmdline" line, not on a line by itself.
2. the button lights stay in whatever condition they were in when Android started. Don't touch the buttons, let them turn off in Windows, before starting Android.
In my patched kernel the button lights work correctly.

Related

O2 Orbit issues with B&B v4.0 editor version

Hi, Ive just upgraded my Orbit from B&B 3.7 to B&B 4. Everything went well, ROM was running like a dream. After a while of tinkering and using it I noticed a few random issues:
1 - Power button: suddenly stops turning screen back on. Screen turns off OK, but will not turn on again. Soft-reset is needed to startup again.
2- Sound disappearing: sound randomly disappeared for no reason. Have removed HTCHome from today (due to known issue) and it wasnt that. I have nothing on today screen, no running programs, nothing loading at startup. All of a sudden after about 5 resets it came back on.
3 - Blue Rollr-ball and scroll wheel: did work when first flashed device, but now no longer respond, in any menu or window the blue light does not even come on (although does come on when first booted and when screen turned off).
4 - Battery life depleted? - seems to drain battery quicker than normal (although this may be due to me having to leave backlight on constantly as explained in point 1)
5 - Wifi : seems to only stay connected for approx 2minutes. Although it will stay connected if constantly being used (ie. if I browse page after page will work, but if I stop to read a page for minute or two I need to disconnect and re-connect)
Thats all I have noticed so far but will post any new issues.
This post is not to put Orbit user's off using B&B 4 or to disrespect Tom or his efforts at all. This is just my findings so far and hope Tom could read and add any thoughts, I do love B&B 4 its a wicked ROM and fully appreciate the work Tom has put inot building it many thanks, keep up the good work man.
fubofo said:
Hi, Ive just upgraded my Orbit from B&B 3.7 to B&B 4. Everything went well, ROM was running like a dream. After a while of tinkering and using it I noticed a few random issues:
1 - Power button: suddenly stops turning screen back on. Screen turns off OK, but will not turn on again. Soft-reset is needed to startup again.
2- Sound disappearing: sound randomly disappeared for no reason. Have removed HTCHome from today (due to known issue) and it wasnt that. I have nothing on today screen, no running programs, nothing loading at startup. All of a sudden after about 5 resets it came back on.
3 - Blue Rollr-ball and scroll wheel: did work when first flashed device, but now no longer respond, in any menu or window the blue light does not even come on (although does come on when first booted and when screen turned off).
4 - Battery life depleted? - seems to drain battery quicker than normal (although this may be due to me having to leave backlight on constantly as explained in point 1)
5 - Wifi : seems to only stay connected for approx 2minutes. Although it will stay connected if constantly being used (ie. if I browse page after page will work, but if I stop to read a page for minute or two I need to disconnect and re-connect)
Thats all I have noticed so far but will post any new issues.
This post is not to put Orbit user's off using B&B 4 or to disrespect Tom or his efforts at all. This is just my findings so far and hope Tom could read and add any thoughts, I do love B&B 4 its a wicked ROM and fully appreciate the work Tom has put inot building it many thanks, keep up the good work man.
Click to expand...
Click to collapse
I understand u my friend.But u need read and my thead v4.0 B&B.I already fixed almost problem u said..!
Thanks again..!
One more thing I forgot to add:
6 - Red End call button: does not work at all, never has on B&B. I have to tap "end call" on screen. not a big issue, but I sometimes press the button and set the device down forgetting to hang up calls
tom_codon said:
I understand u my friend.But u need read and my thead v4.0 B&B.I already fixed almost problem u said..!
Thanks again..!
Click to expand...
Click to collapse
My apologies Tom, I have been reading the B&B 4 post since u released the ROM, but havent found anyting. Ill go have another look LOL sorry
fubofo said:
One more thing I forgot to add:
6 - Red End call button: does not work at all, never has on B&B. I have to tap "end call" on screen. not a big issue, but I sometimes press the button and set the device down forgetting to hang up calls
Click to expand...
Click to collapse
tested in v4.0 don't have same problem..!
LOL all on front page huh ? I just been reading from last post I last read
Ok the HTC fix is the only thing I can find there, not sure if it has fixed the sound thing yet I will let you know. The Red end call button works also, dont know why that wasnt working earlier. But the other issues remain:
Power button still wont turn screen back on after switched off or locked device using device lock.
Blue Rollr-ball and sroll wheel not working at all
Wifi not lasting very long ( although I think I read posts elsewhere about tht so not too worried )
Any thoughts on the hardware buttons anyone ?
Nope, sound gone again. Installed the HTChome fix (both weather and tab, then tab and weather) still no joy. It was working for a period, now its gone off again. Any time any sort of sound tries to come from the speaker I just recieve a high-pitched "ding" then no more sound until reset.
fubofo said:
Nope, sound gone again. Installed the HTChome fix (both weather and tab, then tab and weather) still no joy. It was working for a period, now its gone off again. Any time any sort of sound tries to come from the speaker I just recieve a high-pitched "ding" then no more sound until reset.
Click to expand...
Click to collapse
Sad your having such a rough time but to make sure its not your device, have you reflashed an original ROM and checked your handset to make sure these problems have gone away. Also, how about reflashing the BB v4.0 ROM again and see if it improves, others prior have posted success after a reflash.
I'm happy these BB ROMs have worked flawlessly from first flash (except with known bugs).
Good luck to you on your journey.
Ok got the sound thing sorted myself. Turns out the sound will only work if I boot my Orbit up while plugged into my PC with Activesync running. Its not a USB thing, Ive tried with just my charger plugged in but no sound there. I also tried loading Activesync on my Orbit before touching anything else, still no sound.
The only way I can have working sound on my Orbit is if I boot up while plugged into my PC with Activesync running ??
bex said:
Sad your having such a rough time but to make sure its not your device, have you reflashed an original ROM and checked your handset to make sure these problems have gone away. Also, how about reflashing the BB v4.0 ROM again and see if it improves, others prior have posted success after a reflash.
I'm happy these BB ROMs have worked flawlessly from first flash (except with known bugs).
Good luck to you on your journey.
Click to expand...
Click to collapse
LOL thanks chum. Im the kind that likes to sit and figure out whats going wrong. Im trying to figure it out n leave posts here incase others have issues and maybe find a fix. Also I just cant be bothered to reflash as it takes too long to reinstall all my apps

[App][BETA] Bluetooth profiler

Hello Everyone and welcome to the first program I provide to the community!
As we all know, a constant bluetooth connection drains your battery quickly.
Now what I've done here is a program, that toggles BT-Radio unter certain conditions
You can (at the moment) choose:
Enable BT when a call comes in
Enable BT when you place a call
Enable BT whe the phone is charging
If a condition is no longer valid, BT will be switched off, i.e. if you end
your call, BT Radio will be disabled again.
Requirements:-NET CF 3.5
Usage: Choose your options and select 'run and hide' from the menu.
This has got a hard coded smart minimize, as the program needs to run in background.
Settings are saved as you make them, there's no save button.
Please bear in mind, this is BETA.
It works for me so far and I hope for willing testers, so any suggestions for further
functionality or bug reports are welcome!
I've posted it under Blackstone because that's the device it's been developed and tested with.
Anyone who wants to install on a different device is fine with me, and as soon as it's stable I'll
post it on general level.
Enjoy!
Cheers,
Thomas
P.S.: Pleeeeze don't call it 'App'
Important:
This programm will only work with devices that implement the MS-Bluetooth stack (such as the blackstone).
Widcomm driven devices (HD2 or HD Mini) will not work!
As soon as I find a decent way, to control the Widcomm stack from C#, I'll provide a version for this.
Changelog / Bugs
20/03/2010
BT switched off after a few sec on incomming call - FIXED
26/03/2010
BT stopped, when charging was completed - FIXED
Code for Charging detection was completely rewritten
BT stopped after a few seconds on outgoing call - FIXED
BT switches on late on outgoing call. Improved (not sure if I can get that any faster ).
Basic functions should be fine now.
Added function to permanently disable BT below a choosable Battery level (this is totally untested...).
The GUI has changed slightly (I'll sort out a propper GUI later).
XML settings file has been moved to application directory
background thread speeded up considerably (prog. still shows up with 0,0% CPU when running in B/G.
Found a tester with a touch diamond
31/03/2010
Build in debug option added
how to use it:
In the applications directory open the file BtProfilerSettings.xml with a suitable editor.
Somewhere in the settings node add the following line: <WriteLog>X</WriteLog>
Restart the program.
In your device's root directory you'll find a trace file per day, named '3132010BTProfiler_Debug.txt' (thats the one for today)
Please note, that entries are not necessarily in the exact order, as there are 2 separate threads, one dealing with System events and one polling data every second. Thats why entries may even occur twice.
01/04/2010
Code for BT Radio control rewritten, now uses direct P/I invoke instead of MS Shared Sources dll. Seems to be a lot quicker in enabling BT
08/04/2010
New version uploaded.
New functions:
Option to enable BT in discoverable mode
Enable BT for 60 seconds
Enable BT permanently
GUI changed to black (as this is BLACKstone...not Greystone )
I refrained from creating a fancy new GUI in order to keep the footprint in Memory small.
It is still beta, but apart from the HD2 issue we're getting somewhere.
enjoy!
Wishlist / ToDo
Option to enable BT for 60 seconds manually (for file transfer or other purposes) - DONE
Option to enable BT when the Dialer shows up to reduce response time on outgoing calls (not sure if this is still required..).
Scheduler to enable / disable BT.
Separate GUI from Worker Thread to get rid of the smart minimize and enable Autostart option (WIP).
It looks very useful to me, as I use HD with BT handset.
I will test it and let you know how it works for me.
Thanks!
EDIT: Quick Report:
At first call-in, it turns ON BT and handset correctly, but if I let the phone ring, it closes the BT after a few seconds. After that, in second call it does nothing.
At a call out, it does nothing (BT remains closed).
Thanks for testing and your patience!
The first issue was a bug (switching BT off after a few secs), fixed in the cab. Please uninstall and reinstall.
Second issue looks like the program was closed.
Whenever you bring it up, please make sure you use the 'run and hide' button from the menu, to send it to background properly.
Cheers,
Thomas
Tested new cab:
Incoming call works all the time, but it has two little problems:
1st. Since first ring until BT handset is ON, there is a delay of about 10-14
secs
2nd. After BT handset is ON, the ringing is passed only to the handset and
the device speaker is silent
At outgoing call, BT Profiler still not working (it is running in the background)
A step forward at least
The time it takes until a call is being transfered to the headset is something I can't influence and I think, that depends on the combination Phone/handsfree.
All I do (at the moment) is switching BT-radio on/off.
Second issue must be some setting I think. With my Jabra handsfree as well as my car kit the phone still rings. The software does not touch any settings.
Outgoing call works with me, but I admit, the delay until BT is switched on is a bit to long, which results from the event being fired a late.
For this one, I'll try to catch a different (earlier) event, which I already identified but this will be not before next week.
Agian, thanks a lot for your effort. I'll keep on developing this thing until it works as desired.
Please be patiend with me, I'm working in dev for some 20 Years now, but I'm just developing my skills in doing smart device software.
Cheers,
Thomas
I'll test this tool on my HD2. By accident I found your thread, hope I'll make more accidents like this! I will focus solely on turning bluetooth automatically on on USB connect (since thats the only time I use it).
edit: It doesn't seem to turn on bluetooth when I connect my USB cable and phone begins to charge.
Did you check, if the program ran in background?
Switching on BT when charging was my main focus bevor I started developing the program.
However, there will be a new version withing tihs week, fixing some bugs with the eventhandlers, so you may give it another try then
thomas_b said:
Did you check, if the program ran in background?
Switching on BT when charging was my main focus bevor I started developing the program.
However, there will be a new version withing tihs week, fixing some bugs with the eventhandlers, so you may give it another try then
Click to expand...
Click to collapse
Yes program ran in BG. Ill wait patiently for your update
housert said:
Yes program ran in BG. Ill wait patiently for your update
Click to expand...
Click to collapse
Currently testing on my device, I'll post it as soon as possible
thomas_b said:
Currently testing on my device, I'll post it as soon as possible
Click to expand...
Click to collapse
Np. Take your time.
New version is up
Please make sure to read the notes in post #2.
Sorry it took a while, but I had to rewrite the charging portion of the program. the managed libraries are not very good in power line detection, so I had to dig into API.
I tested it again. On incoming call it doesnt turn on bluetooth. On charging it doesnt turn on bluetooth. Maybe the way the Leo works is completely different from HD? Or could it be problem i hooked it up to my pc usb, instead of just a charger?
Umm....the current version is running on my HD as well as on a workmates Diamond since Friday and it behaves well, although the time gap before BT is switched on on outgoing as well as incomming calls is still to long (I'm looking for a solution).
This version should recognize USB PC as well as chargers of different kinds (actually tested with Motorola USB charger in my car and different USB Chargers) as long as they provide power, regardless of the battery state.
My HD is not on Stock ROM, but on an Energy ROM, so its 6.5, same as yours.
At the moment I'm working on a version, that can provide debug information in a tracefile, that's probably what we need to sort out why it's not working on your phone.
Hopefully that version will be up tomorrow.
For the time being:
Have you checked (Task manager) that the program still runs in background?
(silly question you got .NET CF 3.5 installed?
Thanks 4 your patience!
Well, its not really about patience. I mean, it's your tool, take whatever time you need. Since I'm using EnergyROM, I've got .NET installed aswell. Having a debug option is a good idea, maybe there's something I did with my phone (I've tried multiple bluetooth solutions to turn on bluetooth on charger-connect before, KixAss Bluepower for example) that causes your tool not to work.
For the time being debug should point us to the right direction. I will be flashing my Lep with new energy when GTX theme from ElCondor is released, NRG cooks it in his rom with Cookie, and I dont see any bug reports anymore (so I think that won't happen in 2 weeks..)
well, if I provide software, it should better work
Debug Version is up, HowTo in post #2.
Code:
13:46:58 App. startup, using settings:
13:46:58 OnChargingX
13:46:58 OnIncommingX
13:46:58 OnOutgoingX
13:46:58 OnBattLow Perc0
13:47:03 Charging finished
13:47:34 BT switched on
13:48:39 BT switched on
13:49:11 BT switched on
13:49:43 BT switched on
13:49:48 Charging finished
13:49:49 Charging finished
13:50:01 Device cradled
13:50:15 BT switched on
13:50:45 BT switched on
But, Bluetooth is not turned on. I also tried to actually look for my phone using a collegue's phone, but it just doesnt pop up on his display untill i manually turn BT on on my phone.
that looks like the HD2 simply is not responding to the BTon request, which I find a bit strange.
I reckon, Bluepower did not work for you either?
However, I've emailed the developer of Bluepower to check if he's willing to share his sourcecode with me.
Bottom line seems to be that I have to look for a different implementation to control BT Radio in Order to make it work on the HD2.
Bluepower didnt work for me neither, that's why was so happy initially to find your topic I've emailed the developer of bluepower over a month ago, no response so far.
Happy youre active!
I reckon he uses the same API as I do. Got no reply so far either.
Shame I don't have an HD2 but I'll see if I can find something in the API doc.
If BT Radio can be controlled by software, I should be able to find it.
Somewhere in the hardware interface layer I guess, as my ROM is based on Leo as well.

Tilt 2 time issues!

i recently upgraded from a touch pro to a tilt 2 and imediately i flashed energy rom to it. afterwards i noticed the time would be wrong from time to time but only by the hour
ive changed my time to to fit my area and ive also tried the auto update and either way my tilt 2 will jump time forward
please help!! much apreciated!
you can go to the settings tab and in one of those options you can get internet time...maybe that will work.
yes ive tried that but no luck
does anyone think this is a ROM issue or maybe a bad flash?
or maybe AT&T cant keep time anymore
i wrote some nonsense and i deleted it, read the post below.
actually that might not help, if you have Advanced Config in your settings, open that then scroll down to miscellaneous and enable automatic daylights savings switch-over if disabled. that should really fix ur issue
Untick automatic update time in phone settings... Had big problems with this on old Hermes..
I used to have the same prob. no matter which rom i used. I found a solution, though, im not sure whether it is unique to my handset. So far i can confirm it has worked on the Feb, March 27, April 1 of the Energy Leo lastest Microsoft build (not the 21xxxx one). Under BSB Tweaks switch auto time sync to off. Restart. Go back to BSB Tweaks and switch it back on and then restart. Your time should now sync to the cell towers. I also change the AGPS to AT&T servers rather than HTC prior to switching it back on. I dunno if this is needed. So if it doesnt work then I would recommend switching to the AT&T AGPS server and then switching it back on.
Thank all of yall for helping
unfortunately none of yall helped but i really apreciate the help (i cant spell)
turns out because i flashed my new rom in excitement i came upon a glitch with my radio that i once seen before that made my start menu icons stack ontop of eachother. what does this have to do with my time issues? well because i was in a hurry i grabed a random radio that sounded good and flashed it to my device to fix the start menu issue, turns out the radio i flashed disabled my gps which in turn disabled my auto time update as well. So simply flashing the wrong radio causes lots of problems so those who dont know this should learn from my mistake

Graphical Glitch

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.

[Q] TouchLockPro setup guide for dummies?

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.

Categories

Resources