Related
Right now I'm doing a little research (in my spare time) on adapting the keypad drivers that work on Vogue to also work on HTC Nike. Ducamie got me interested and sent me the files I needed, I poked around here and there and got overly enthousiastic PM-ing him a big bunch of text with maybe 2 words that actually made sense.
However, I think now I have the faintest clue of what to do:
Figure out GPIO codes for keys that are the same on both 16 and 20 key version (the dpad, the call buttons, camera button, power button and volume button should be the same I guess) using HaRET.
Adapt keymapping of board-htcvogue.c (since that's the one we use on our Niki devices?).
Find out additional keys (I can only do this for 16-key version as it's the only Niki I've got), and map those (maybe in board-htcvogue.c as well, maybe need to look at board-kaiser-keypad.c for that).
If anyone knows that I'm going at it all wrong, please tell me
Also, if anyone by any chance already had a run at the Niki and got the GPIO info I need, please do let me know.
I'm not new at programming but I am new at this kind of programming, so all sorts of things might go wrong or I might end up not getting there at all, but my goal is to make everything public, no matter where I get.
So even if I end up only getting the GPIO codes for the keys, if I fail writing the actual driver, the next developer will not need to get those codes and can get his hands on programming immediately.
I hope I am making sense, and I hope we'll be able to fix this driver ASAP, so we can actually try out Android without having to reboot to get back to the homescreen
There is not much interest in android on the dual - I have no idea why you guys arnt flooding the android threads with even idle curiosity.
Anyway, Graey, im glad you got the files and pretty much worked out what to do (sounds right to me). Have you had any luck with haret? Ive had it running in the past, logging key events but only jargon came out, i couldnt correlate between the event logs and key events in the code or see any pattern.
I can have another attempt if you like at the getting the gpio's or could help you set haret up if you have a linux box? i believe it can work via windows too but i only had luck with linux.
Let me know!
ducamie said:
There is not much interest in android on the dual - I have no idea why you guys arnt flooding the android threads with even idle curiosity.
Anyway, Graey, im glad you got the files and pretty much worked out what to do (sounds right to me). Have you had any luck with haret? Ive had it running in the past, logging key events but only jargon came out, i couldnt correlate between the event logs and key events in the code or see any pattern.
I can have another attempt if you like at the getting the gpio's or could help you set haret up if you have a linux box? i believe it can work via windows too but i only had luck with linux.
Let me know!
Click to expand...
Click to collapse
Well, ofcourse I have a Linux box, my main box is linux, I only use my windows laptop (which sadly enough doesn't run Linux right) to flash ROMs and in be .
It seems though that you already know a bit more about haret than I do, so if you could have another go at getting gpio's, that'd be great. And ofcourse on the long run it would be interesting for me to get haret up and running as well
Now I might seem to have a clue as to what to do, but currently that's just about it, I like to poke around in things and sometimes it results in something useful
I'll see what i can find! Dont hold your breath though.
would be awesome ducamie! i'd really love to see android running without problems on this htc device anyway: anyone got the new sdk running? it's posted on vogue site... replace android.zip in download link with android-new.zip... it freezes all the time for me... i got it to boot already, but i end up in a command prompt...
the_fish said:
would be awesome ducamie! i'd really love to see android running without problems on this htc device anyway: anyone got the new sdk running? it's posted on vogue site... replace android.zip in download link with android-new.zip... it freezes all the time for me... i got it to boot already, but i end up in a command prompt...
Click to expand...
Click to collapse
as you will see in the bootloader it says at the bottom "failed to mount sd card". this is because the new sdk is too large to boot from the phone memory so the vogue guys have it booting from the sd card. for this to work we will need a custom sd driver for the nike in our kernel.
Ok... I hope we'll get them soon anyway; where's jerpelea? Is he still working on the drivers?
ok, after lots of playing around this is the best i can get .
i realise some of these gpios are the same and i dont have a clue why - i dont think ive done anything wrong, so sorry if this is not what you need, but this is what haret was outputting for gpios.
16 key nike:
side volume buttons (both)
in1: in1-26(218)=0 (press in)
in1: in1-26(218)=1 (out press)
both start and end call buttons
in1: in1-26(218)=0
in1: in1-26(218)=1
nav up and down buttons
in1: in1-24(216)=0
in1: in1-24(216)=1
left
in1: in1-24(216)=0
in1: in1-24(216)=1
right
in1: in1-25(217)=0
in1: in1-25(217)=1
middle OK button
in1: in1-25(217)=0
in1: in1-25(217)=1
camera button
in1: in1-26(218)=0
in1: in1-26(218)=1
windows key
in1: in1-25(217)=0
in1: in1-25(217)=1
mail key
in1: in1-26(218)=0
in1: in1-26(218)=1
back key
in1: in1-24(216)=0
in1: in1-24(216)=1
1-5
in1: in1-23(215)=0
in1: in1-23(215)=1
6-0
in1: in1-22(214)=0
in1: in1-22(214)=1
* and #
in1: in1-24(216)=0
in1: in1-24(216)=1
i hope this is of some use.
oops i missed the IE key. oh well.
thanks for codes
i am working on the new kernel
BR
jerpelea said:
thanks for codes
i am working on the new kernel
BR
Click to expand...
Click to collapse
sweet
let me know if i can help in any way
ducamie said:
sweet
let me know if i can help in any way
Click to expand...
Click to collapse
please send me your kernel source and .config
thanks
br
jerpelea said:
please send me your kernel source and .config
thanks
br
Click to expand...
Click to collapse
u can find sources of the msm kernel at the android git ive posted before...
I'm working on fixing some keymapping on the polaris android build and need to check the GPIO for the OK button. Any idea on where I can go to find out how to do this?
It has been quite some time since the HTC touch pro came and since the very beginning there was talk about running android on it. I mean I remember a month after the Touch Pro came out someone had Android running on it, although it was just a proof of concept and didn't have touch or anything working.
So how has is been coming? Is Android finally a viable option for the Touch Pro?
I mean I would love to try android on my phone, as long as it works with bluetooth and the hardware buttons...that's really all I need. I can manage without wifi, speaker, etc.
aceofspades1217 said:
It has been quite some time since the HTC touch pro came and since the very beginning there was talk about running android on it. I mean I remember a month after the Touch Pro came out someone had Android running on it, although it was just a proof of concept and didn't have touch or anything working.
So how has is been coming? Is Android finally a viable option for the Touch Pro?
I mean I would love to try android on my phone, as long as it works with bluetooth and the hardware buttons...that's really all I need. I can manage without wifi, speaker, etc.
Click to expand...
Click to collapse
You should have visited the wiki first, before asking a question that has an easy searchable answer
rafyvitto said:
You should have visited the wiki first, before asking a question that has an easy searchable answer
Click to expand...
Click to collapse
Sorry I didn't know about the wiki and I did do a search for android in the ROM development forum and didn't come up with much.
But I was just wondering what kind of experiences people have had with it and wether it has been working smoothly.
www.connect-utb.com
there you'll get newest android roms for diamond and touch pro
Android on Diamond/Raphael thread:
http://forum.xda-developers.com/showthread.php?t=402002
A) Download this:
http://www.connect-utb.com/index.ph...ile&Itemid=68&id=28:android-for-htc-touch-pro
B) just replace the zimages for the newer android builds from GlemSom's site.(updated daily)
http://glemsom.anapnea.net/android/raphael/
Next time you use search, use the search below your username(to search the whole site) instead of the search this forum.
magicman0 said:
Android on Diamond/Raphael thread:
http://forum.xda-developers.com/showthread.php?t=402002
A) Download this:
http://www.connect-utb.com/index.ph...ile&Itemid=68&id=28:android-for-htc-touch-pro
B) just replace the zimages for the newer android builds from GlemSom's site.(updated daily)
http://glemsom.anapnea.net/android/raphael/
Next time you use search, use the search below your username(to search the whole site) instead of the search this forum.
Click to expand...
Click to collapse
A) link is broken... please fix!!
link is fine, but it seems like connect utb is down. Give them until tommorow
Can somebody help me with a weird problem?
Everything boots up just fine, but when I follow the how-to for my mobile networking my hardware keys(home, back, dial & disconnect) won't work!
Does anyone have a solution for that?
edit: it seems to be that the home and dial key are also left and the back and disconnect key are acting like a right key
thx in advance!
You asked for an opinion right?
I did try the android ports, even tried the one that's more recent but I didn't find them usable. They're too complicated and things don't work as expected. Maybe in time they will create a usable port for the touch pro but by then I will want to change my phone...I'm considering that right now too...
BUT. Some quality work has been done and it is a really cool experience. I appreciate all the work that has been put into that project.
This MOD by APP is different than the existing MOD by replacing system apks:
1. No risk of brick
2. Ease of use
3. Universal hack for phones and ROMs that has Webtop
Since this app is intended to support multiple devices, see the original post from the Razr thread http://forum.xda-developers.com/showthread.php?t=1404625 .
Please report the test result in this thread. Whether success or fail and your device, ROM, etc.
It'd be nice to use the "Send" option in the app if it failed.
Thanks!
Working for me on mopho 198_7,rooted,with jokersax 1.3 preuvHighpro! Thank you!
it worked for me too!
It works, but the screen doesn't properly emulate a track pad. Connecting a bluetooth keyboard works fine though.
fendergrab said:
It works, but the screen doesn't properly emulate a track pad. Connecting a bluetooth keyboard works fine though.
Click to expand...
Click to collapse
Is anyone else having this problem? I actually have this issue on occasion with the current webtop over HDMI hack that replaces the stock files. But, it doesn't happen all the time, only some of the time.
Also, if anyone can answer this for me, I haven't bought a lapdock yet, but I am considering it, if I do, I think the other webtop over HDMI hack will have to be removed to make the lapdock work, is that true? Second, if that is true, then this method shouldn't have the same problem right?
Please try with the latest version(v0.5). More diagnostic messages are logged and can be sent using the "Send Info" menu item from the app.
fendergrab said:
It works, but the screen doesn't properly emulate a track pad. Connecting a bluetooth keyboard works fine though.
Click to expand...
Click to collapse
For the first question, I have no idea since I have never tried the "webtop over HDMI hack that replaces the stock files".
For your last question, if the Webtop related things are restored to the stock, this method will still work thus it should have no interference with the Lapdock.
bradleyw801 said:
Is anyone else having this problem? I actually have this issue on occasion with the current webtop over HDMI hack that replaces the stock files. But, it doesn't happen all the time, only some of the time.
Also, if anyone can answer this for me, I haven't bought a lapdock yet, but I am considering it, if I do, I think the other webtop over HDMI hack will have to be removed to make the lapdock work, is that true? Second, if that is true, then this method shouldn't have the same problem right?
Click to expand...
Click to collapse
fendergrab said:
It works, but the screen doesn't properly emulate a track pad. Connecting a bluetooth keyboard works fine though.
Click to expand...
Click to collapse
I cant make the track pad work at all. What stock apk files have to be installed for this to work? I am stock rooted with some bloat removed. I am thinking I might have removed one apk file to many...
Could you use the "Send Info" option in the app after you tapped the "Load' button?
my2cents said:
I cant make the track pad work at all. What stock apk files have to be installed for this to work? I am stock rooted with some bloat removed. I am thinking I might have removed one apk file to many...
Click to expand...
Click to collapse
400757 said:
Could you use the "Send Info" option in the app after you tapped the "Load' button?
Click to expand...
Click to collapse
All give it a go. I tried rebooting my phone, but still no luck. I sent the debug info via email. This is pretty cool. I've never bothered using webtop, but it looks pretty interesting.
EDIT: I already got an email back from the developer. He said that it all looks good, but the extdock state cant be set to 4, which is what mine loads to when I press load. I see what he says.
Yep, it seems that even everything for Razr looks good for Photon 4G, the track pad on the phone could only react to orientation but couldn't receive any touch action.
I will try to first locate this track pad from Razr, and how are the events being sent then inspect if this is working correctly for Photon 4G.
So this may not work at all.
If anyone got any real dock that made the Photon 4G to have the track pad working correctly, please kindly run logcat to log how all these happen and send to me for analysis. This may boost up the progress by differential analysis.
my2cents said:
All give it a go. I tried rebooting my phone, but still no luck. I sent the debug info via email. This is pretty cool. I've never bothered using webtop, but it looks pretty interesting.
EDIT: I already got an email back from the developer. He said that it all looks good, but the extdock state cant be set to 4, which is what mine loads to when I press load. I see what he says.
Click to expand...
Click to collapse
I don't have a dock, so i cant be of much help there. Hopefully someone can run the logcat for you. If you need me to test anything else, I will gladly do it.
Now it seems to me that logcat is not enough.
I've figured out that evbridge is the process that draw the virtual pad on the phone and responsible for translating and forwarding touch events to mouse movement and key inputs to the Webtop world.
It seems to be using /dev/webtop/input/event4 as a placeholder for the touch event. But when evbridge is not running, those event devices won't work.
So in the worst case your phone have the evbridge running, some event4 receiving touch events but just that are not being processed and forwarded to the Webtop world.
In this case I will need to look deeper inside evbridge for how it actually emit the events or how the Webtop world see and process them then find out which part is broken.
my2cents said:
I don't have a dock, so i cant be of much help there. Hopefully someone can run the logcat for you. If you need me to test anything else, I will gladly do it.
Click to expand...
Click to collapse
More of the "track pad" stuffs have been studied(https://sites.google.com/site/androidnothize/nebtop/webtop). What remain are testers like "my2cents".
In short, we used TeamViewer(on PC) + PuTTY(on PC) + SSHDroid(on phone) + WiFi(connect PC and phone) + time.
In the last test I haven't studied enough of the track pad so couldn't make real use of it. But now I've studied more of it and have sorted out 3 possible points of breaking the chain of events from the touch screen to the Webtop. Unfortunately "my2cents" seems to be on a vacation.
If you know what are these and could prepare these, we could arrange a time that both of us could go online at the same time to perform the investigation.
Send me a PM or email me at either this nick name or another at gmail.
400757 said:
More of the "track pad" stuffs have been studied(https://sites.google.com/site/androidnothize/nebtop/webtop). What remain are testers like "my2cents".
In short, we used TeamViewer(on PC) + PuTTY(on PC) + SSHDroid(on phone) + WiFi(connect PC and phone) + time.
In the last test I haven't studied enough of the track pad so couldn't make real use of it. But now I've studied more of it and have sorted out 3 possible points of breaking the chain of events from the touch screen to the Webtop. Unfortunately "my2cents" seems to be on a vacation.
If you know what are these and could prepare these, we could arrange a time that both of us could go online at the same time to perform the investigation.
Send me a PM or email me at either this nick name or another at gmail.
Click to expand...
Click to collapse
Hi 400757,
I was on vacation for new years. I got your email, but it was at 5 AM my time and we left that morning to go see family. I am back at home now and I am happy to help again. I will be available all day tomorrow and possibly tonight. I have to get the kids in bed first...
Follow up of the freshly done live investigation on my2cents's Photon 4G.
Turn out that it is quite different than Razr....that lead to more unknowns and needs a working Photon 4G as the basis to compare with.
One must-fail point is that evbridge is expecting /dev/input/by-id/touchscreen which doesn't exist at all. This is the first problem that made the track pad unresponsive.
Secondly the aev and evfwd input devices are not exposed to the X using xinput like in Razr.
After linking this path to the touch device /dev/input/event4, the track pad buttons became responsive though those events are not forwarded to the Webtop cursor.
strace didn't show further open failure afterward.
Thus in order to ease the life, a working Photon 4G Webtop with track pad is needed for inspection.
Does that mean that if someone has a dock, you could debug that way?
I'm not sure....
If someone has the HD dock, and used it to activate the Webtop mode, and if the track pad works.......
Then later using the Nebtop to activate the Webtop mode should work too.
In contra, if a fresh boot using Nebtop doesn't work, (due to the missing device link) but if the HD dock make it work, then it means there're some extra stuff done by recognizing a real HD dock.
Otherwise, if both Nebtop and HD dock failed, perhaps it's regional issue? eg. Some region's Photon 4G has track pad bug since there will be no selling of HD dock?
The last possibility perhaps related to the "bloat" apps that you've removed/disabled? But this is odd that if the app would create the device link under /dev...
my2cents said:
Does that mean that if someone has a dock, you could debug that way?
Click to expand...
Click to collapse
works great on stock rom rooted. but is this where ads that pop up in notification bar?. .... they are driving me crazy!
Sent from my Motorola Electrify using XDA
ads r driving me crazy! they pop up in my notification bar! are they from this app?!
Sent from my Motorola Electrify using XDA
so swype beta doesnt support the 1024x768 resolution of the hp touchpad. you can hack the installer but then it installs the phone version of swype which is really useless on a tablet. the pantech element, which has the same screen resolution as the touchpad, apparently has swype installed, but i cant find any development on it. not even as much as a root, much less a rom dump. i was hoping to pull it off that device and use it till theres a proper version of swype for the touchpad. does anyone have any info on it?
Perhaps its possible to pull it from the ROM dump but I can't find one.
Another good thing about this device that I just noticed is it has an APQ8060/Adreno 220 just like the Touchpad. It may come in handy as a build.prop device since it has the same hardware and same screen resolution as the Touchpad.
Yeah it needs the snapdragon for lte. It could be a good donor device, if it had any development.
I managed to find a Pantech Element ROM dump and installed Swype along with its lib file. Unfortunately it gives a licensing error message and goes into limited functionality mode where you cant swipe words. It looks great in landscape but doesn't adjust in portrait and gives an error message about screen resolution, even though the Element has the same resolution.
If I'm not mistaken, the newest swype beta supports the tp's resolution just fine. By phone mode, do you mean no TAB key? Cause I can live without a TAB key.
I really like the skin used on the Pantech Element, and also the fact that you can shrink the keyboard down in size which makes swyping faster since you don't have to cover as much area. You can see screenshots of this Swype in action on the Element in this review:
http://www.phonearena.com/reviews/Pantech-Element-Review_id2961/page/2
I'll try getting the beta working and then seeing if I can somehow get the Element version to work after. I'd post the Element files but we are not allowed to post Swype apks so anybody who wants to try will have to hunt them down for themselves.
spunker88 said:
...but we are not allowed to post Swype apks...
Click to expand...
Click to collapse
Thanks for mentioning this. Everybody please keep this in mind.
krook6023 (mod team)
turdferguson92 said:
If I'm not mistaken, the newest swype beta supports the tp's resolution just fine. By phone mode, do you mean no TAB key? Cause I can live without a TAB key.
Click to expand...
Click to collapse
mine didnt look like that last time i used swype.
spunker88 said:
I really like the skin used on the Pantech Element, and also the fact that you can shrink the keyboard down in size which makes swyping faster since you don't have to cover as much area. You can see screenshots of this Swype in action on the Element in this review:
http://www.phonearena.com/reviews/Pantech-Element-Review_id2961/page/2
I'll try getting the beta working and then seeing if I can somehow get the Element version to work after. I'd post the Element files but we are not allowed to post Swype apks so anybody who wants to try will have to hunt them down for themselves.
Click to expand...
Click to collapse
the pantech is using the tablet version of swype, it would be nice, wouldnt it...
http://forum.xda-developers.com/showthread.php?t=1721993
the newest version of swype works on touchpad
Just in time, I was about to spend a bunch of time trying to get the Element version working fully, now I don't have to.
spunker88 said:
Just in time, I was about to spend a bunch of time trying to get the Element version working fully, now I don't have to.
Click to expand...
Click to collapse
just a thanks needed i was frustrated by old fashioned button bashing
Yay! I'm typing this on the tablet version of Swype. About damn time.
ditto, the new beta works great
Sent from my SGH-T989 using Tapatalk 2
Hey there!
I tried to get an Apple wireless keyboard working on my 7500 running the 3G ICS kang. The device pairs up, but pressing keys doesn't do anything. If I remember right you needed the official samsung keyboard app to make keyboards work, would having it installed help?
Sorry if this was already answered, searched google and forum search isn't working for me for some reason ... so, can anyone tell me how to get it to work? =)
Hmm strange, it's working now, seems like a reset was all that was needed and now it works just splendit.
Even stuff like ctrl+c, ctrl+v works fine, didn't think that would work out of the box. The only thing that doesn't work is function keys, but I never thought that would be the case.
So if a moderator sees this, you can probably just delete this whole thread
- Happily typed this on my new Apple wireless keyboard =)