Has anyone else tried the "27-Aug-2010" zImage? I just tried it and it cause all buttons on the phone not to function except the end button.
The git reads
12 hours ago Lukas D. Gorris htcleo: add additional selectable keymapping htc-msm-2.6.32
Something weird !!
I got the same thing goin on also.. no functioning buttons other then the End Key Button..
djphredee said:
I got the same thing goin on also.. no functioning buttons other then the End Key Button..
Click to expand...
Click to collapse
Just for ****s and giggles, i copied all the modules file in and still didnt help
Same here. Red Close button is the only one working.
Same here.
This is by design, if you look at:
http://git.linuxtogo.org/?p=groups/...;hpb=eed82a0f77f367b929f51cc59e6c64a68a06256a
you can see that there are two new defines: HTCLEO_KEYMAP_DPAD and HTCLEO_KEYMAP_ANDROID. This was done to enable dpad control for software that doesnt support pure touchscreen devices. As there are no other changes, I would suggest using the previous image until the default define is KEYMAP_ANDROID.
Thanks for suggestion... the new zImage didnt worked for me as well
Works ok here with all modules installed on mattc 1.6b radio 2.12, but phones turns off unexpected don't know if that related or my battery has died due to abuse.
the 27 version its very unstable for me =)
buttons work now, but this build constately freeze and processor have hot
carhigh said:
Just for ****s and giggles, i copied all the modules file in and still didnt help
Click to expand...
Click to collapse
lol now i know not what to do haha
VisualD said:
This is by design, if you look at:
http://git.linuxtogo.org/?p=groups/...;hpb=eed82a0f77f367b929f51cc59e6c64a68a06256a
you can see that there are two new defines: HTCLEO_KEYMAP_DPAD and HTCLEO_KEYMAP_ANDROID. This was done to enable dpad control for software that doesnt support pure touchscreen devices. As there are no other changes, I would suggest using the previous image until the default define is KEYMAP_ANDROID.
Click to expand...
Click to collapse
Thanks for explaining that. I learn something new every day
What about the new zImage from today (28th) ? does the buttons work in this build? Could someone test it?
Yes, same cheat !
Same problem here.
dont use as of yet its causing problems for me in winmo
after transfering modules and everything seems the same as other builds but no wifi
The 8/28 version seems to have solved this problem (broken keypad buttons).
alantak said:
Same problem here.
Click to expand...
Click to collapse
alantak said:
The 8/28 version seems to have solved this problem (broken keypad buttons).
Click to expand...
Click to collapse
Me to working good but no see a change of 24/08/10 zimage but just more speed for boot android
i havent been able to get wifi to work
thatruth132 said:
i havent been able to get wifi to work
Click to expand...
Click to collapse
You have replaced module files : bcm and tun.ko ?
Related
can anyone fix this to work on our Vogue? i have been using it an minus a few bugs its sweet.
http://forum.ppcgeeks.com/showthread...iphone+dialer
Thanks!
agentmikeyd said:
can anyone fix this to work on our Vogue? i have been using it an minus a few bugs its sweet.
http://forum.ppcgeeks.com/showthread...iphone+dialer
Thanks!
Click to expand...
Click to collapse
link not working
try this one...
http://forum.ppcgeeks.com/showthread.php?t=6044&highlight=iphone+dialer
agentmikeyd said:
can anyone fix this to work on our Vogue? i have been using it an minus a few bugs its sweet.
http://forum.ppcgeeks.com/showthread...iphone+dialer
Click to expand...
Click to collapse
What bugs do you observe ? I'd really like to try it ...
And when you say it has a SpeedDial function, what exactly does it do different from the stock SpeedDial (press a digit for 3 secs) ?
Finally, if you had to uninstall it, what do one have to do ? easy ? (thanks)
neurocutie said:
What bugs do you observe ? I'd really like to try it ...
And when you say it has a SpeedDial function, what exactly does it do different from the stock SpeedDial (press a digit for 3 secs) ?
Finally, if you had to uninstall it, what do one have to do ? easy ? (thanks)
Click to expand...
Click to collapse
The #s show in the background during Talk mode
http://forum.xda-developers.com/showthread.php?t=311299&page=12
Smartdialing doesnt work
And I think you cant call 911 (I never tried) and 911 GPS is also disabled (how do you really know for sure?..)
I too have truly enjoyed it. I was using it before I upgrade to vogue on my ppc-6700 and still wasn't correctly then. Still I lived with it but not on Vogue. But if these bugs were fixed then I would definitely switch!
So if any could make it work, I would greatly appreciate
app deleted because it was messed up!!!
gr8 app man, this will save we me some time
thanks
what kind of calibration needed in the diamond??
roisagi said:
what kind of calibration needed in the diamond??
Click to expand...
Click to collapse
the screen alignment is done automaticaly by this app... so you dont have to do it manualy
I checked the registry to compare the defaults in the CAB with what I already had.
The CAB had
485,500 785,175 785,825 185,820 188,175
my TP has
485,514 785,835 785,200 193,200 193,835
Now how perfect mine are, I don't know, but I tried to be as perfect as possible. Even tried multiple times until I was happy I hit the center of the cross 5 times in a row.
I installed the .CAB on my Diamond and it inverted the screen taps; everything on the screen appears fine but the tap responses were inverted, I think its a glitch...Just reporting, hope it gets fixed.
I'm not getting how this works... I mean, copied on my Diamond, installed (tried both in Internal Storage and Phone Memory), I get a setup icon in the program menu which, tapped, leads me to another autoalign installation, and so on. Cycle.
What am I missing? Any help? Would really like to try this software and see if it improves my touch experience (not a reference to some mythical UI for WM... ).
teorouge said:
I'm not getting how this works... I mean, copied on my Diamond, installed (tried both in Internal Storage and Phone Memory), I get a setup icon in the program menu which, tapped, leads me to another autoalign installation, and so on. Cycle.
What am I missing? Any help? Would really like to try this software and see if it improves my touch experience (not a reference to some mythical UI for WM... ).
Click to expand...
Click to collapse
Try aligning your screen by hand and mess it up on purpose. Then try it with autoalign and see the difference.
P.S TouchXperience IS NOT some mythical UI! Just watch. It'll be released on Feb 1st.
azharsunny said:
WORKS ONLY ON VGA DEVICES
Click to expand...
Click to collapse
Any ETA when this will work on WVGA?
CR0WN13 said:
I installed the .CAB on my Diamond and it inverted the screen taps; everything on the screen appears fine but the tap responses were inverted, I think its a glitch...Just reporting, hope it gets fixed.
Click to expand...
Click to collapse
CUD YOU EXPLAIN WHAT U MEAN BY " SCREEN TAPS INVERTED"?
so i can fix what the problum might be!!
teorouge said:
I'm not getting how this works... I mean, copied on my Diamond, installed (tried both in Internal Storage and Phone Memory), I get a setup icon in the program menu which, tapped, leads me to another autoalign installation, and so on. Cycle.
What am I missing? Any help? Would really like to try this software and see if it improves my touch experience (not a reference to some mythical UI for WM... ).
Click to expand...
Click to collapse
the file in the program is the real deal.... when u instal that cab, the one in your program menu, that aligns the screen !!!
this is jus my second cab and ill try to make an easier version soon!!
Internet browse fu**ed up!!! Made multipul posts
Internet browse fu**ed up!!! Made multipul posts
AllTheWay said:
Any ETA when this will work on WVGA?
Click to expand...
Click to collapse
if u cud help with the info i need then i can make one for WVGA as well
Thanks azharsunny, I thought it had to be like that but wasn't sure!
Kraize said:
P.S TouchXperience IS NOT some mythical UI! Just watch. It'll be released on Feb 1st.
Click to expand...
Click to collapse
Didn't really mean to upset anyone! It's just that I'm reading about its features since the beginning of my WM life (Sept. 08) and I'm trying it as soon as it is released to the public. Looks very promising and interesting!
Good idea, will give it a try
Thanks for sharing
This app is just brilliant! Timesaving and incredibly useful, now finger touch is at a new level! Thank you so much, that should be included in any Diamond ROM!
sorry for my supid question, but whats exactly the sense of this app? and why does it save time and give new experiences?
What's wrong with the built in screen alignment? Seems to work okay, what makes this different??
the app is still not final!!! im workin on it as a write this !!!
Hey there!
For all of you with SoD, please do try my idea... been testing all afternoon, and even though its early to say, I'm sure it is working.
It occurred to me, that maybe windows still had some control over the hard keys while running Android.... so i had the following idea!
Install AE Button Plus 2.6.5.cab (or maybe another version) and UNBIND all hard keys. I guess maybe the End/Lock key will be enough, but i just unbinded all of them as i dont use Windows mobile anyway since i got Android! ahaha . THEN, launch our dear Android the usual way. This way, I can still answer calls and navigate using touch if i do feel like using Windows Mobile for whatever strange reason!
I now use FD Droidboot and disabled sense/titanium on my barebones Miri Rom.
Result: Screen comes up every single time i press the lock key, and goes off every single time i click the same key. Works as it should now. Immediate response too (using a class 2 card)
Brilliant! Me very happy! This was getting annoying.
Also, yeah i confirm, the workaround for the mic gain, using the wired headset, seems to work for me.
Darkstone Desire V5
Radio : 2.12.50.02_2 (does seem better on the battery! Thanks to whoever suggested it! and thanks to all the devs and testers!)
PLEASE LET ME KNOW IF THIS WORKS! Just thought that I should share this since a lot of people are having the same issue....
Peace and Kudos to everyone and specially to the programmers!
WHERE DO I FIND ''AE Button Plus 2.6.5.cab''? SEARCHED BUT COULDN'T FIND CAN YOU PLS MIRROR
MYKEE92 said:
WHERE DO I FIND ''AE Button Plus 2.6.5.cab''? SEARCHED BUT COULDN'T FIND CAN YOU PLS MIRROR
Click to expand...
Click to collapse
google it i found it.
air23cpt said:
google it i found it.
Click to expand...
Click to collapse
SORRY.. FOUND IT
EDIT: STILL NOT WORKIN FOR ME
thanks. it makes sense. I will try that!
so i assume this method also works for darkstone's and dan's froyo builds?
SOLVED
Just switch back to the no speedy zimage
MYKEE92 said:
Just switch back to the no speedy zimage
Click to expand...
Click to collapse
That still gives me the SOD. I'm gonna try the OP's method and see if it helps. I'll report back soon.
How to disable Lock/End key in Winmo?
Yep, was working all day flawlessly, but towards the end of the day was getting slow and started happening again... even after restarting. Thanks for the help testing this!
Now i notice that after having unbinded all keys, all of them except the End call key, are still unassigned.
Is there a fix or registry key to completely "disarm" the Lock/End key while in Win Mo? I still think this is related to SOD somehow.
Hello
This is regarding the Rhodium bug once updating the OEM drivers to the latest 2.10 build that many chefs have been getting. I'm not sure if this has any negative side effects (I haven't come across any as of yet).
All you have to do is use rilphone.dll from the 2.7 build (I haven't tried the one from the 2.8 build yet but I might soon). Lemme know if it works.
Happy cooking! (^^,)
This is not a downloadable fix but rather information for chefs.
Yep.. I asked the guys in my thread to use an older rilphone.dll because I was sure that's the problem... but nobody was brave enough to try it. They kept swapping radios for some reason.. LOL Thanks for the tip, I'll just use the older rilphone.dll. That new ATT rom is effing whack!!
NRGZ28 said:
Yep.. I asked the guys in my thread to use an older rilphone.dll because I was sure that's the problem... but nobody was brave enough to try it. They kept swapping radios for some reason.. LOL Thanks for the tip, I'll just use the older rilphone.dll. That new ATT rom is effing whack!!
Click to expand...
Click to collapse
Haha, should've known you knew about it Lol, yeah it is.. I'm getting random manila stutters and flickers now and then, that's pretty crappy though. Is that only me?
NRGZ28 said:
Yep.. I asked the guys in my thread to use an older rilphone.dll because I was sure that's the problem... but nobody was brave enough to try it. They kept swapping radios for some reason.. LOL Thanks for the tip, I'll just use the older rilphone.dll. That new ATT rom is effing whack!!
Click to expand...
Click to collapse
Lol.. I was game - just didn't know where to find the old RIL.
http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=7437776&postcount=24652
Couldn't find it in the Radio thread. So where do you go to get this stuff? Thanks a bunch for the link. Will try it right away..
Don't try the cab it seems like it doesn't work for some strange reason.
seeM_ZA said:
Don't try the cab it seems like it doesn't work for some strange reason.
Click to expand...
Click to collapse
too late.. My Radio is hosed for now. Doing another reset - sometimes, replacing ROM components take a couple of resets (new location?)..
Edit: Resets didn't work. Can you link the actual rilphone.dll here?
motoq9h said:
too late.. My Radio is hosed for now. Doing another reset - sometimes, replacing ROM components take a couple of resets (new location?)..
Click to expand...
Click to collapse
Lol you know more about it than me then (^^,). It works perfectly when cooked in though, my bad
seeM_ZA said:
Lol you know more about it than me then (^^,). It works perfectly when cooked in though, my bad
Click to expand...
Click to collapse
Yup.. looks like it is searching for the rilphone.dll in the ROM. copying it over replaced the location. So it is hosed - no phone for me..
Cooking it in is the only way, looks like - Need NRGZ28's help for that.. Unfortunately, my cooking skills don't pass much muster.. lol
Edit: So is there a way to point to the new rilphone.dll location via the registry? Going to be tricky though : ROM vs overwrite location
Edit2: There, that wasn't too bad. Uninstalled the cab and reset - back to using the cooked in rilphone.dll & back to working phone (with 2 bars, ofcourse!) I have the "good" rilphone.dll though. Saved it off before uninstalling the cab - anyone wants it?
Did you try putting phone in airplane mode before installing cab? May'be That could have made a difference!!
momulah said:
Did you try putting phone in airplane mode before installing cab? May'be That could have made a difference!!
Click to expand...
Click to collapse
Lol.. I'm not hopeful - overwriting a ROM file moves the file system entry (to flash?) and invalidates the ROM file (the Cooks/Chef's will know more). The phone code appears to be hard coded to look only at the ROM file - so no deal it appears..
motoq9h said:
Yup.. looks like it is searching for the rilphone.dll in the ROM. copying it over replaced the location. So it is hosed - no phone for me..
Cooking it in is the only way, looks like - Need NRGZ28's help for that.. Unfortunately, my cooking skills don't pass much muster.. lol
Edit: So is there a way to point to the new rilphone.dll location via the registry? Going to be tricky though : ROM vs overwrite location
Edit2: There, that wasn't too bad. Uninstalled the cab and reset - back to using the cooked in rilphone.dll & back to working phone (with 2 bars, ofcourse!) I have the "good" rilphone.dll though. Saved it off before uninstalling the cab - anyone wants it?
Click to expand...
Click to collapse
Well the 'old-fashioned' way was to copy the new rilphone.dll as rilphone2.dll and then edit the relevant registry key to point to it.
Unfortunately, multiple people have tried to do so in the past (check the early Rhodium radio thread posts) and apparently it's something to do with RILPHONE being a module on Rhodium and Topaz devices that makes any method other than cooking it in, fail.
monomer888 said:
Well the 'old-fashioned' way was to copy the new rilphone.dll as rilphone2.dll and then edit the relevant registry key to point to it.
Unfortunately, multiple people have tried to do so in the past (check the early Rhdodium radio thread posts) and apparently it's something to do with RILPHONE being a module on Rhodium and Topaz devices that makes any method other than cooking it in, fail.
Click to expand...
Click to collapse
Thanks.. Yup. Was searching through the Registry a little while ago - no mention of the rilphone.dll
motoq9h said:
Thanks.. Yup. Was searching through the Registry a little while ago - no mention of the rilphone.dll
Click to expand...
Click to collapse
Just for reference, this is the key:
HKLM\Drivers\BuiltIn\RIL
"Dll" = rilphone.dll
I spent the best part of the evening trying to get it to work, but point it to any other rilphone.dll and I would get no signal at all. Resetting the key back to what it was restored it. Hope that helps.
NRGZ28 said:
That new ATT rom is effing whack!!
Click to expand...
Click to collapse
Thats why a heck of a lot of us are here (at XDA) in the first place.
wait, i'm confused. how do we replace the new rilphone.dll with the good/old one? does anyone actually have it/has anyone gotten it to work?
Da_G explains it pretty nicely in this post: http://forum.xda-developers.com/showpost.php?p=3354857.
Without the nk.exe patch, when you replace rilphone.dll, the system checks it against it's internal certificate store, finds that it's not signed with a trusted certificate, and refuses to load it. This is why replacing rilphone.dll on unpatched ROM's results in no radio function.
Click to expand...
Click to collapse
seeM_ZA said:
Da_G explains it pretty nicely in this post: http://forum.xda-developers.com/showpost.php?p=3354857.
Click to expand...
Click to collapse
Aye, if I was reading it correctly, there was an alternate way using DriverWiz to cab up the dll which has worked on older devices, even when the nk.exe wasn't patched, e.g. here: http://forum.xda-developers.com/showthread.php?p=3486508#post3486508
Unfortunately, At0mAng tried to use this method at one stage but it didn't work on his Rhodium. http://forum.xda-developers.com/showpost.php?p=4642101&postcount=215
It would be great if we could get this to work!
seeM_ZA said:
Haha, should've known you knew about it Lol, yeah it is.. I'm getting random manila stutters and flickers now and then, that's pretty crappy though. Is that only me?
Click to expand...
Click to collapse
I am getting this now and then ... try scrolling stuff on manila or weather and taskbar will flicker or blink ... i hate it ....were you able to fix this ? rilphone for which older TM base ?
'▼' said:
I am getting this now and then ... try scrolling stuff on manila or weather and taskbar will flicker or blink ... i hate it ....were you able to fix this ? rilphone for which older TM base ?
Click to expand...
Click to collapse
Nah wasn't able to fix that.. I'm using rilphone from 2.07 Rhodium ROM, that fixes the 2 bar bug.
What is exactly what you call the '2 bar bug'?
HI, i want to inform you that my friend OliWe fixed:
.) FIXED: touchscreen calibration (don't forget to remove the old ts_calibrate file from sdcard.
.) FIXED: touchscreen wrong pointer input (2-3cm jumps)
the hole touch screen problem.
.) ADDED: LONG PRESS of hardware key
now you can (ex) use long press of red button and then you can switch off the phone - this is woring also)
for installation:
===========
please download the latest kernel htc-msm-linux @ 20100819_200730 or newer.
latest kernle downloading on: http://glemsom.users.anapnea.net/android2/htc-msm-linux
Install new kernel:
1.) download kernel + extract the .tar.bz2.
then you'll find a module....tar.gz + zImage...
the zImage.... you must rename to zImage and
both files you must copy tho your SDCard. direct to sdcard ("Storage Card").
ALL HONOR GOES TO OliWe
I can confirm this, just tried it out.
I can type just fine on the keyboard now as opposed to before when it was a nightmare!
Thanks, GREAT job!!
Just perfect
Two big problems killed in the same time! Really great job, Oliwe !!!
Thanks +1
seems to be working for me too. The whole typing experience is now like windows mobile - Great! Thanks!
exactly a great news, many thanks for the hard work...
its amazing
tested
Tested and it works =]
Keep up the good work devs. Sad about the battery and hope there is a fix for this but otherwise loving what you guys are doing and achieving.
Hey, its fixed. And it works. Thats really good news. Thank you very very much.
Hey Guys,
It's nice to see, that my patches are working for all of you
The last patch filters about 99% of all jumps. Small jumps (a few pixels) are still possible, but they are very rare and you won't even notice them.
Have fun playing with android
Thank you @camro for the intensive testing
Sorry, but I just test it with Android 2.1 on my Blackstone.
http://forum.xda-developers.com/showthread.php?t=621498&
And this is not working well, the touch calibration is completely out
What are your options on your startup.txt about touch calib' ?
EDIT: Yeah it is working ! I can check my notification with a shield xD
We have to
- delete the old ts_calibrate file from sdcard
AND
- remove the msmts_calib from the startup.txt (usually msmts_calib=0x395.0x3c9.0x79.0x77 on blackstone)
And I can switch off Android
cis.snakeman said:
Sorry, but I just test it with Android 2.1 on my Blackstone.
http://forum.xda-developers.com/showthread.php?t=621498&
And this is not working well, the touch calibration is completely out
What are your options on your startup.txt about touch calib' ?
Click to expand...
Click to collapse
It looks like you didn't calibrate your touchscreen on first boot. Delete the ts-calibration file from your sd-card and boot into android. It will ask you to calibrate the touchscreen (you have to click on 5 white boxes, you should use the stylus for this).
The calibration in startup.txt is no longer needed. You can delete it
Yes you right.
Sorry I don't see your post before.
Anyway thank you for this patch
wrong post.... sorry
Sorry does not work link.......Pleaseeee add download tanks
Try here - http://balsat.hopto.org/
Tanks very nice..
Is this fix also working for Android 2.2?
Yes I applied this fix to v1.3. Be advised that the TheBrilliantMistake has released a new version (v1.4) that includes this calibration fix plus a few other bits'n'pieces.
woohooo, that's great news, thank you so much for that guys!
Though I don't quite get which button to press to switch off the phone since the top HW btn summons the recent app screen...?
TREMENDO!!!!
works great for me! I have 2.2 froyo, and at last not need the stylus for use the phone! But the power off is not working, freezes while powering off. But i dont care...Im fine, my touchscreen works!!!
Thanks for you hard work!