Hi all, Not been around for a long time, but I've picked up a HD2 to play around with WP7.
Settled on Yuki/XBmods BTTF ROM - fully updated (8107). Although I have an issue with the physical keys on the device - they only light up when they're being pressed - they don't remain on for a few seconds afterwards.
I've installed Leo Advanced (As I've read that can change those settings), but when I try to load up key map, the HD2 will vibrate once then close Leo Advanced (It has full root permissions through use of WP7 Root Tools).
Is there a registry setting where I can change this, or a fix I've overlooked to get Leo Advanced working? I've tried a search but I'm not finding anything specific to this ROM. If I use pdaimates or Ansars rom the backlit keys are fine.
No backlight on BTTF (Cotulla Driver not installed)
I'm guessing there's no way around this?
Related
Because I am new here, I would like to say "hello" to all users first
About two weeks ago I bought new HTC Touch HD from official polish dealer. I was not satisfied about performance and lots of unneeded software provided with stock ROM (apparently it was standard ROM for polish network "Orange") so I decided to flash my Touch HD with Barebone 2.6 ROM found on this forum.
After that operation I experienced problems with wireless manager built in the ROM.
The application is not launching as it should - after tap on the icon I can see that default application icon is appearing on the task bar (I am using WisBar Advance, newest version) and then just disappearing after a second or two. Manager is not opening, only number of soft resets is occasionally makes the wireless manager work properly.
I've already tried to:
- Hard reset the device
- Install newer version of wireless manager (with 8 buttons, posted on this forum)
- Change registry value for "redirection" key
- Install patch for wireless manager provided with wm6.5 (also posted on this forum)
- Exit form WisBar Adv and boot system without it
Unfortunately problem still persists, if any user could give me some advice how to solve this case I would be grateful.
P.S forgive my bad English, I am still learning...
Just reflashed the image on my phone to the latest Energyrom Sense 2.5
Since doing so, I have problems with Copilot Live 8. It appears to be an issue with the screen overlay as the menu buttons for Copilot are down at the bottom of the screen where this ROM has the start button.
When in Copilot the start button is covered up by the copilot screen and the menu buttons do not work at the bottom.
Any ideas on how to fix?
I am also using Co Pilot live. And while it does consume the full screen, hard buttons work just fine. I am using the Titanium only version, as I use SPB MS as my primary shell.
Have you tried uninstalling and reloading CoPilot?
I think that's by design for Copilot. Opera 10 and Mini 5 also hog up the whole screen. If you need the start menu, and you don't have a device that already has a hard start button, perhaps you can map one of your hard keys to the start menu w/ the Rhodium Keyboard Config floating around these boards.
I'm using Copilot 8 on an Energy's latest 21903 rom, and it works just fine.
I unfortunately cannot do an uninstall as I cannot select the up arrow in the bottom left corner when copilot is running.
I can do a re-install by running the CAB again and it finishes OK.
All other areas of the screen work, but since I cannot select the up arrow bottom in the lower left corner, I cannot change any settings, or modify anything. It's stuck once it comes up.
Ran find in the previous energy ROM I had loaded.
Reflashing to ER 21903 Sense 2.5 and will Re-Install copilot to see what happens.
I'm totally stumped on this one!
I've wiped the device several times with Task 29 and re-flashed with several different builds of 21903 with no luck.
Co-Pilot is on my flash drive and I have deleted the folders, re-copied from my PC and kicked off the CAB files again. Still no luck.
My problems started after putting on 23569 build which puts the start button right across the bottom of the screen where the copilot buttons are located.
I thought task 29 would wipe everything and get me back to start, but it appears that there is something leftover somewhere that is causing this.
Anyone care to give some thoughts?
[email protected] said:
I'm totally stumped on this one!
I've wiped the device several times with Task 29 and re-flashed with several different builds of 21903 with no luck.
Co-Pilot is on my flash drive and I have deleted the folders, re-copied from my PC and kicked off the CAB files again. Still no luck.
My problems started after putting on 23569 build which puts the start button right across the bottom of the screen where the copilot buttons are located.
I thought task 29 would wipe everything and get me back to start, but it appears that there is something leftover somewhere that is causing this.
Anyone care to give some thoughts?
Click to expand...
Click to collapse
Weird, I had problems with my tp2 after installing 23569 and loading copilot... put me in a bootloader loop 4 times. Not completely sure that this combo is involved, but the problems started after the maxmanila version of 23569 was flashed. For more details see this thread: http://forum.xda-developers.com/showthread.php?t=691984
let me know how it goes...
You could try this...
1. Hard Reset (with phone off hold down talk and end buttons and press the power button)
2. abort setup
3. start to bootloader
4. flash task 29
5. reflash HardSPL
6. Flash favorite ROM
7. Load Copilot
This sequence is what I finally did to overcome whatever broke mine. Keep in mind that I am still testing the fix AND I am not smart enough to know what I didn't need to do but it's working and I am using copilot without problems.
Hi all
I had the exact same issue.
When choosing the language during the installation the "next" arrow at the bottom of the screen didnt work.
The issue was with a 28xxx rom.
After in installed a 21xxx rom the issue wasnt solved.
Eventualy i reinstalled the original rom from the htc site....still no luck!
I noticed, on my sd-card there was one cab file for installation (copilot_wmsp.cab)
Om my pc there were two cabfiles: copilot_wmsp.cab and copilot_wmppc.cab.
Probable for use on an SmartPhone or PocketPC.
When i copied the files from my pc to my phone and installed copilot_wmsp.cab the issue still wasent solved.
When i installd copilot_wmppc, it worked perfectly. The configuration screen has a little diffrent layout, and that worked.
Now i have the latest energyrom 28xxx with working Copilot!
I have build a custom hd2 rom with oskitchen and xip/sys 28244.
It's working very well.
Now I have added some ext packages found here that seems to be useful. And now the new rom has the following issue: After leo goes to standby by itsself or by pressing the off key and some time later it will not wake up. Buttons are lightened but screen stays black. I have to put the battery out or to reset. Than rom is working again until next standby.
It happens only, if device is in standby for some time. If you press off and then wake up device immediately, all is working well.
Any idea, if this can be result of some added package or some component of the xip/sys build?
Have now found out something:
If I remove the following ext packages from my built rom, the rom works without freezing after going to standby:
HTC Tweaks
AMEBA
Opera Mini 5.1
Google Maps 4.1.1
But If I install those apps as cabs, the rom is working well after installation.
Can it be that they conflict with some built-in package of leo which causes the freezing issue, which is not there if installing the packages?
thunder141, not sure what you mean by HTC Tweaks but if you increased system cache (as it proposed to do somewhere in Leo related threads) to absolutely huge unacceptable meaning - your phone just tries to cache memory...
Get rid of that tweak, or check your Storage Card (maybe format will help) - possibly the system is trying to cache to it and it's fragmented or just too slow....
i mean the app hd2 tweak with standard configuration converted to an ext from the cab
thunder141, am I supposed to know what does that mean - "app hd2 tweak with standard configuration "?
I tweak my roms by myself and never try to have fun with someone's "tweaks compilations"
Can you be more specific? Give me a link to the cab or attach your package for me to have a look.....
sorry ;-) I thought it is a known prog cause i found it here at xda.
http://forum.xda-developers.com/showthread.php?t=452505
But I misspelled it. Its hd tweak not hd2 tweak.
I imported the cab with oskitchen's import feature. And when I cook it in, my rom freezes after going to standby. If left it out, rom works fine.
I attach the ext, oskitchen created for me
Its not a spelling problem but the fact that those tweaks are made for HTC HD not HD2.
I suggest you to dont use it, simple solution.
thunder141 said:
sorry ;-) I thought it is a known prog cause i found it here at xda.
http://forum.xda-developers.com/showthread.php?t=452505
But I misspelled it. Its hd tweak not hd2 tweak.
I imported the cab with oskitchen's import feature. And when I cook it in, my rom freezes after going to standby. If left it out, rom works fine.
I attach the ext, oskitchen created for me
Click to expand...
Click to collapse
af974 said:
Its not a spelling problem but the fact that those tweaks are made for HTC HD not HD2.
I suggest you to dont use it, simple solution.
Click to expand...
Click to collapse
No, at his page there are hd tweak for other device and hd2 tweak for hd2 (leo). (http://www.montecristoff.com/hd2tweak.htm)
But, as I said, its not only this ext pkg but the others mentioned make my device freeze, too. And if used by cab install, not. And I do not understand the difference for those apps, if they worked when not cooked in.
I decided to put them in my uc_net folder for now and left them out of my rom, so my device won't freeze
before my hd2 got bricked due to my stupidity, i was trying to find solution to freezing issues.
i found out that if cad.dll and wavedev.dll are excluded, no death occurs after sleep. (of course, these dlls are vital for sound, so we cannot exclude them).
so my suggestion would be to first exclude these 2 dlls and include your packages to see if this clash is causing problem and then find compatible version of your packages with these 2 dlls or find compatible dll.
personally, i think these 2 dll have some odd bug with certain versions of windows system.
Hi, i really need some help. I am trying to install android on my HTC leo but my call 'accept' key doesnt work so when i am getting to the part in DAF.exe where i have to use the volume buttons to scroll up and down and select (out of the 12 options) different options i cant choose one.
Is there a way around this?
Thanks
J
No. You are probably stuck running winmo with android on sd, unless someonhe edits magldr/cwm to use a different key, which currently no one has.
Get you call/send key working is about the only option you have.
Hi guys, I need help. Today I hacked android device HTC Aria and installed WindowsCE 6.5! Everything working perfect expect hardware buttons (but volUp and volDown working). I want to change layouts for button keypad "call, home, menu, back, endcall". Where is stored preferences about hard keys, is this is in registry or it is in a dll? Thanks!
you can down rom , change rom