Hi,
What is the correct method to determine what panel type your phone has?
My phone identifies as a KAIS130 in bootloader and is a 'HTC' branded phone (purchased in Taiwan, has Chinese characters on the keyboard)
I am currently running Android Donut (Myns) with the latest Eclair NBH with the panel type selected as "1" (sony) and everything seems to be working fine, though there is a brief white screen that flashes when the screen is turning on.
So does this mean I have chosen the correct panel type? Is their any proper way to determine which panel type your phone has?
aznphatb0i said:
Hi,
What is the correct method to determine what panel type your phone has?
My phone identifies as a KAIS130 in bootloader and is a 'HTC' branded phone (purchased in Taiwan, has Chinese characters on the keyboard)
I am currently running Android Donut (Myns) with the latest Eclair NBH with the panel type selected as "1" (sony) and everything seems to be working fine, though there is a brief white screen that flashes when the screen is turning on.
So does this mean I have chosen the correct panel type? Is their any proper way to determine which panel type your phone has?
Click to expand...
Click to collapse
As far as I know the correct way to determine the panel type is trying out all three setups and choosing the one that works best.
-Arturo- said:
As far as I know the correct way to determine the panel type is trying out all three setups and choosing the one that works best.
Click to expand...
Click to collapse
That is the only way.
As they said, only by trying them can you see which is the correct type, panel2 and panel3 seem to be the most alike, and only the occasional sleep of death issue can tell them apart.
Basically, if it looks ok, and wakes up then chances are it's the correct type, if the colours are wrong, or it refuses to wake up, or the white screen persists for more than 5 seconds or so, chances are it's the wrong type.
Note that there is no way to identify which type by device type, since the panels are fitted according to supply and demand at the time of manufacture, all 3 types were used as and when available.
Related
Hi All,
Does anyone know how to get this working on our beloved HD's? I hate the way the screen goes completely black during a call, we can't use the light sensor to tell the phone that the call has finished and it is away from your ear (so screen comes back on a la iphone), and i keep doing things during a call with my ear!!
So this seems like the ideal solution - but i can't get it to work!!
I've copied over the file to the windows folder, then soft reset. Changed the registry entry for phoneLockEnable to 1 in HKLM/Software/HTC/Phone but still no joy!
All help would be greatly appreciated.
Regards
DF
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
chanmama said:
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
Click to expand...
Click to collapse
Sorry, i don't have the cab file, i just saw the screenshot and thought 'that's what i need'!!!
Hopefully some bright spark here can help us both (and others probably).
Regards
DF
Beside this transparent canvas, where can I get the orginal canvas?
I am using a offical ROM but I don't see this function!
I hate the way the screen goes completely black during a call, we can't use the light sensor to tell the phone that the call has finished and it is away from your ear (so screen comes back on a la iphone), and i keep doing things during a call with my ear!!
Click to expand...
Click to collapse
that's interesting, because my screen doesn't go blank during calls and it happens quite often that i accidently disconnect a call (i suppose because i hit a button with my ear).
so in search for i solution i found in Advanced config a tab Light sensor > Light sensor polling which i set enabled. the explanation says "uses light sensor to automatically turn screen off when the phone come near from your ear to answer a call". so this should set it like the i-phone does, right?
hence when i tested it, the screen still was on, even when i put my thumb onto the light-sensor.
is this because i don't have a stock rom (i use Duttys HD V1.9b XTREME) or is there something i can do about it.
it would be really nice to have the screen locked when i answer a call and to outomatically unlock it if i remove it from my head to use some function on the screen..
take55 said:
that's interesting, because my screen doesn't go blank during calls and it happens quite often that i accidently disconnect a call (i suppose because i hit a button with my ear).
so in search for i solution i found in Advanced config a tab Light sensor > Light sensor polling which i set enabled. the explanation says "uses light sensor to automatically turn screen off when the phone come near from your ear to answer a call". so this should set it like the i-phone does, right?
hence when i tested it, the screen still was on, even when i put my thumb onto the light-sensor.
is this because i don't have a stock rom (i use Duttys HD V1.9b XTREME) or is there something i can do about it.
it would be really nice to have the screen locked when i answer a call and to outomatically unlock it if i remove it from my head to use some function on the screen..
Click to expand...
Click to collapse
Hi take55,
Yes, i'm aware of the advanced config tweak (also in HD Tweak), and as you correctly state, the screen should/will go blank on call connection (i'm running kwbr's A Touch Of HD 3.3.4 and mine doesn't, even with tweak applied!!).
Unfortunately, when the call ends and you move the phone away from your ear, the screen still stays blank????? I've read somewhere on these forums that it never will work like the iphone (not sure why, as the light sensor should recognise that we've moved the phone away from our ears).
So that is why i'm trying to get this other method to work. What i have noticed is that with the bmp copied over to the windows folder or with a cab i found by A-Math installed, my dialler locks up after every call (as if the transparent phone lock is in place) but i can't actually see it. None of the screen works and i have to soft reset. Maybe something is stopping the bmp to show on the phone....who knows.
It also might be the fact that this was designed for the Diamond (found the cab on the Diamond forums).
Just hoping some genius here might now how to sort this.
I've attached the cab file i've found, give it a try and see if you have the same issue as me.
Regards
DF
chanmama said:
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
Click to expand...
Click to collapse
Hi chanmama,
Found the cab file for you, see previous post.
Regards
DF
Datafanatic said:
What i have noticed is that with the bmp copied over to the windows folder or with a cab i found by A-Math installed, my dialler locks up after every call (as if the transparent phone lock is in place) but i can't actually see it. None of the screen works and i have to soft reset. Maybe something is stopping the bmp to show on the phone....who knows.
Click to expand...
Click to collapse
It has nothing to do with the BMPs but with the registry setting that the CAB also makes. It sets HKLM\Software\HTC\Phone\PhoneLockEnable to 1, in wich case you'll have to press the power button to unock (no need to soft reset). For the BMP to work the phone/dialer software will have to support it, otherwise it just locks the phone in the usual way: black screen, power button to unlock.
Datafanatic said:
Hi chanmama,
Found the cab file for you, see previous post.
Regards
DF
Click to expand...
Click to collapse
tks but your cab only for the canvas skin only, do not contain the original software (slidable canvas), anyway, tks for your help
I've also found this problem to be quite annoying during a phone call but have found some sort of way to deal with it.
Firstly my ROM isn't tweaked, its just the basic one already installed.
After a call is connected, the screen switches off. But if you need to access the screen again during a call, I just press the "Back Arrow" key, one of the four hard buttons on the bottom which brings the screen back up again.
If you press the phone button instead whilst the screen is off, the screen lights up again but it puts the call on hold.
This probably isn't the best way to deal with this, but it seems to work for me for the time being, hope this helps anyone else here.
rubbermonkey123 said:
I've also found this problem to be quite annoying during a phone call but have found some sort of way to deal with it.
Firstly my ROM isn't tweaked, its just the basic one already installed.
After a call is connected, the screen switches off. But if you need to access the screen again during a call, I just press the "Back Arrow" key, one of the four hard buttons on the bottom which brings the screen back up again.
If you press the phone button instead whilst the screen is off, the screen lights up again but it puts the call on hold.
This probably isn't the best way to deal with this, but it seems to work for me for the time being, hope this helps anyone else here.
Click to expand...
Click to collapse
Useful info - I found this particularly annoying yesterday during a ouple of calls.
Also discovered Gyrator tries to turn the phone screen and was laggy - which was even more annoying!
Everyone!!!
CHECK THIS OUT - http://forum.xda-developers.com/showthread.php?t=489034
Answer to all our prayers - a screen lock which uses the g-sensor and not the light sensor.
Now, when a call is connected, holding the phone to the ear blacks the screen, but when you bring the phone down (to use the keypad or something), THE SCREEN COMES BACK ON!!!!!!!
Tried and tested on kwbr's A Touch Of HD v3.3.4 (probably the best manila2 ROM out there!)
Regards
DF
i was wondering if i could get sum people to tell me about ehir experiences with their locking/unlocking programs...such as, which ones youve used with success...im interested in knowing which ones use the least about of battery power, least amount of memory/ram...so on and so forth...any input wiould be greatly appreciated
specifically programs being used with the touch pro 2
I'm personally not a big fan of screen lock programs. I just think that for something as simple as locking the screen, the end-user shouldn't have to give up anything in terms of resources/battery life.
That's why I suggest sticking with the default WinMo lock.
I suggest either SmartLock or LockDevice to auto lock your device. Neither uses up any resources.
I've perused the threads concerning both the locking apps you cite above, but both appear to have some issues (i.e. not everything working properly after the install). I'm specifically looking for a way to have the screen locked when the device is turned on, mostly because I carry the thing in my pocket (yes, with a screen protector) and want to be sure that if I should inadvertently bump the power button I don't end up calling friends overseas from the inside of my pocket. It doesn't appear to me as if the default locking app can do this (and not simply turn on the lock after a timeout) -- or am I missing something?
pistou said:
I've perused the threads concerning both the locking apps you cite above, but both appear to have some issues (i.e. not everything working properly after the install). I'm specifically looking for a way to have the screen locked when the device is turned on, mostly because I carry the thing in my pocket (yes, with a screen protector) and want to be sure that if I should inadvertently bump the power button I don't end up calling friends overseas from the inside of my pocket. It doesn't appear to me as if the default locking app can do this (and not simply turn on the lock after a timeout) -- or am I missing something?
Click to expand...
Click to collapse
I've used both of those apps and it works fine for me. I have the exact same concern that you have. I don't want the device to wake because someone called and hung up after a second, thus making the screen susceptible to taps.
In both apps, you can customize how you want the lock mechanism to kick in. You can set it to lock when you screen goes off. My personal preference is to set it to lock on suspend.
I'm not really sure what you mean. If your device is locked (with the WinMo default lock), you won't be able to do anything (including making calls) without unlocking it first either via tap & slide (WinMo 6.5) or left soft key & unlock button (WinMo 6.1).
I would really like to use the app, but there is a dialer conflict when getting incoming calls for boths apps. For example during an incoming call, I initially get HTC dialer. During the middle of the call, I get the original WM dialer. Do you have any suggestions to avoid this problem?
ohyeahar said:
pistou said:
I've perused the threads concerning both the locking apps you cite above, but both appear to have some issues (i.e. not everything working properly after the install). I'm specifically looking for a way to have the screen locked when the device is turned on, mostly because I carry the thing in my pocket (yes, with a screen protector) and want to be sure that if I should inadvertently bump the power button I don't end up calling friends overseas from the inside of my pocket. It doesn't appear to me as if the default locking app can do this (and not simply turn on the lock after a timeout) -- or am I missing something?
Click to expand...
Click to collapse
I've used both of those apps and it works fine for me. I have the exact same concern that you have. I don't want the device to wake because someone called and hung up after a second, thus making the screen susceptible to taps.
In both apps, you can customize how you want the lock mechanism to kick in. You can set it to lock when you screen goes off. My personal preference is to set it to lock on suspend.
Click to expand...
Click to collapse
Thanks: I've loaded lockDevice and so far so good
ohyeahar said:
I'm not really sure what you mean. If your device is locked (with the WinMo default lock), you won't be able to do anything (including making calls) without unlocking it first either via tap & slide (WinMo 6.5) or left soft key & unlock button (WinMo 6.1).
Click to expand...
Click to collapse
What I meant was that my understanding of the default WinMo lock is that it only locks after a specific period of in activity (which I don't want to happen) rather than after a suspend (which is what I do want).
My touch screen won't respond to touch or the stylist. This just happened but I am beginning to see some bleed on the screen so I know it's a hardware issue.
Got a new one coming to replace it but here's my problem. My settings are set to automatically lock the screen after a period of time for security reasons and to help prevent pocket calls! Does anyone know a work around with the keyboard to unlock the screen?
Most of the software I loaded is on my PC but whenever I rebuild a phone it's always good to look at what is in the thing via "remove program" option. Needless to say, I can't get there without unlocking the screen.
I tried my magic wand and threatened the phone by telling it I was going to replace it with an iPhone but so far... nothing works.
Thanks,
Rick
The lockscreens are based on touch input. The only option I know of to recover your data is to replace the digitizer.
AFAIK, doing that on Windows Mobile 6.5 Stock is completely impossible. If you can get past the slider screen, you can use the numbers on your TP2 keypad and press enter. But I'm running 6.1 (makes me feel better being used to ye olde Pocket PCs), so I can't verify anything.
What a difference a day makes. Yesterday my rad new Xtrons Android headunit was working almost* fine and today, after following conventional wisdom and letting my 15yo nephew pimp it, it's in all sorts of...well fckd.
Keen on some help from the collective wisdom. Before anyone helpfully suggests a factory reset... well, that's been done, sooo many times. When your nephew CHANGES the factory settings, it becomes a cycle of hell.
Unit is an Xtrons PB86MTVP. 8" HD, Android 6.0' Octa-Core 64bit 32GB.
Current main problem is that the touch screen inputs are reverse and diagonally opposed. What the hell do I mean by that? If I want to type on the qwerty keyboard or simply tap an icon, I have to use my cunning and hit an area or button diagonal and opposite for it to work. If I can get past this issue then maybe I can move to the next one which is that the unit doesnt power on/off with the ignition.
To be clear, things tried (multiple times in some cases) include
Reset via reset button
reset via software app section
undoing car battery
pulling unit back out and disconnecting
turning on and off again
swearing
So, who can help? got a silver bullet?
TIA
Joe
You could go to settings start right down the line set your home screen back and you should have a setting there for different keyboards also that should get yoy back to normal
Sent from my LG-TP260 using Tapatalk
djkeylenux said:
You could go to settings start right down the line set your home screen back and you should have a setting there for different keyboards also that should get yoy back to normal
Sent from my LG-TP260 using Tapatalk
Click to expand...
Click to collapse
thanks for the reply djkeylenux. I've got the right keyboard though, thats not the problem. the problem is the touch input on the screen, no matter which screen I'm on.
Well beside calibrate witch I thing you tried you could also go to developer options take a kook at running process see if there's something running causing the problem,
I think you lost the MCU settings.
Go to settings and then into Factory Settings menu. Password is 126.
Then in keys tab re-calibrate the screen. During calibration you will first see a "+1" in one of the corners. Tap it with your finger. Then in opposite corner "+2" will appear. Tap it too. Then accept and apply ypir settings and the unit will reboot. The touchscreen will work correctly then
In the same screen you can also re-configure the touch buttons and physical buttons of yoir device.
It looks like someone potentially did an MCU upgrade/flash. If there was no backup of the settings then you lost it all. Which also means you might have lost bluetooth connectivity as the bt module type on first page of factory setting might be wrong too. Also canbus and other things might be affected. I recpmmend to check out the discussion threads on MTCD devices here. Someone with the same unit might tell you the right settings.
Hint: If you have trouble tapping the icons with non-calibrated screen. Try connecting a standard USB mouse to any of the USB ports.
Thid weird issue started today in the morning, first I noticed that the clock widget had changed size, and that the led me know ring around the cam hole was out of place, but, when trying to write in whatsapp, I no longer could make the keyboard to appear by taping the wrinting field, in fact, nothing located in the bottom worked, what is odd, the bottom gestures worked, as I hid the nav bar since day one, tried everything, changed dpi, changed keyboards, retired the screen protector, wiped cache, to no avail, reluctantly, I updated to android 10, but no luck, after digging more, I found a work around, I changed the resolution from quad hd to full hd, now all is normal, but, this is just a work around, not a real solution, somebody have an idea of what would be the reason for this?
Did you have your phone linked to windows, your computer online and the phone screen displayed at that time? In this case, if you chose to use your computer's hardware keyboard in Your phone settings on your computer, then, when trying to write something in whatsapp, the virtual keyboard on your phone is not displayed or it is partially displayed. In my case, using the AI Type keyboard, only the top row of the keyboard was displayed because the app thought I'm using my computer's keyboard.
Sent from my SM-N975F using Tapatalk
Thanks for your reply, but no, in fact I have never used the phone in that way, something else caused the issue
winol said:
Thanks for your reply, but no, in fact I have never used the phone in that way, something else caused the issue
Click to expand...
Click to collapse
Was your phone charging at the time by any chance?
I found the solution!
I had the exact same problem with my note 10 plus, the gestures worked, and I tested the bottom part of the screen to make sure everything was working and it was, but the buttons in apps like instagram at the very bottom of the screen still were unresponsive most of the time. The solution is to ho to your settings, switch the navigation bar to the other gesture variant and then back to you preffered one and it should work. It worked for me.
Thanks man, I just found what triggers the issue, as odd as it seems, changing resolutions from qhd to fhd id what causes the issue, odd, because I used a bixby routine to save power at nights, by setting medium power saving, which among other things, lowered the screen resolution to fhd, when the routine ended, it should reverse to qhd, and that precisely triggered the issue, I used this routine for months, until, out of the blue, it started to cause this problem