Related
how can i enable the camera and recorder buttons after update, they are not working any more ???? PLEASE HELP
specify rom version
what rom version did you use? could you specify? and if you don't mind, where did you get it?
There is no fix for your problem. Since Buzz lightyear issued WM2005 it has been a game of chance as to weather your camera and record buttons work. If you search the forums on here and www.buzzdev.net you will find that lots of people have this problem. It seem to be related to where the unit was maunfacutured. I think its some thing like: if you have an unlta bright screen then you buttons will not work. If your screen is about 30 - 40% less bright ( that is to say if you put the 2 units side by side) then you buttons will work. I know because i have upgraded loads of XDAII's. So there you have it i hope it makes sence . The botton line is there is no fix for your problem
I know this has been asked many times about remapping of ok button on front of hermes .....i also have reassigned the ok button to close instead of minimize using ae button plus 2.52 but long press function of ae on OK button doesnt work....
i want that when i long press the OK button spb pocket plus menu opens whereas when i press OK button it closes the running application.
Thx in advance
i really luv this community.
Hey max, when did you get a hermes? What happened to your magician?
I've been away for quite a while and missed a bit.
V
vijay555 said:
Hey max, when did you get a hermes? What happened to your magician?
I've been away for quite a while and missed a bit.
V
Click to expand...
Click to collapse
got it after my xams as birthday gift....sold magician quite a time ago.now running black 4 and the ok button is really irritating me .....plz help
There are a number of threads about remapping the ok button. However, I've not seen any about the press and hold.
AE Button Plus is the best app I know/knew of for remapping. If it doesn't work, it doesn't work I'm afraid. Speak to the author of the app specifically to see if it's a known issue.
V
try handy switcher v3.0, it works for me
Dear Vijay555,
glad to see you somewhere in hermes forum, about ok button mapping, i know you already give us VJOkButt. your tools is my choice.
is it possible to write a tini app that simulate the click at the top corner x button so it does close running app via HTC-xbutton, and we safe to close everything phone,activesync..? or this is useless?
thanks Vijay
VJOkButt already has a mode to emulate clicking the top right close button I think -
http://www.vijay555.com/?Releases:VJOkButt
-justclick
simply click the existing ok button (for compatibility with other task managers)
Click to expand...
Click to collapse
VJOkButt has code built in to not close various important apps that would crash the system. But closing things like the phone is possible,
-phclose
will force the phone to close, not minimise, to save extra memory (but will cause minor incompatibility with dialing from contacts - reload with VJTogglePhone or launching cprog.exe)
Click to expand...
Click to collapse
let me know if you need something else.
V
hello
i waana have mutiple functions from ok button like if i press it
once-.....app 1 runs
twice........app 2 runs
thrice.......app3 runs
long press.....app4 runs
i want to have this functionality.help anybody
max414 said:
i waana have mutiple functions from ok button like if i press it
once-.....app 1 runs
twice........app 2 runs
thrice.......app3 runs
long press.....app4 runs
i want to have this functionality.help anybody
Click to expand...
Click to collapse
Don't know if this is you're looking for, but here you have one great and free software to try...
http://forum.xda-developers.com/showthread.php?t=306794
ey, and it's here at XDA what a chance...
Regards.
hi all,
i know a japanese software PQZII can remapping the hw ok button with close app,it has many other amazing functions about the hw button,too
hope that it can give u a hand
Wished i could do that with ae button plus...as i really like the app.
Have you tried PQz max?
V
vijay555 said:
Have you tried PQz max?
V
Click to expand...
Click to collapse
I tried it when i had a magician didnt like it and afterwards installed ae buttons but i can give it a try if it solves my problem
Guys, I need a little help with 3.5.x! I use a WM6.5 + Manila 2.1 ROM (signature).
I want to activate the 3D accelerated messages and carousel. I tried with the registry changes here, but it didn't work. I set GlEnabled, HqReflection and Reflections to 1, but nothing happens even after a soft reset. Some weeks ago I had almost the same ROM (a previous version), but with a different Model No. (KOVS100 instead of X1i) and I had the option in settings to turn acceleration on, and it worked OK and very fast. I think I have the X2 video drivers installed as part of the ROM in the signature.
Thanks for the help!
Modify ModelName.txt
darthmelk said:
I want to activate the 3D accelerated messages and carousel.
Click to expand...
Click to collapse
The easiest way I've found is to make your device think its someone else... change the contents of the \Windows\ModelName.txt (currently "X1i") to the model code for the Touch HD ("HTC Touch HD T8282") and you get 3D Acceleration!
You'll probably need to reboot to get it working and I always need to re-run the Connection Setup afterwards.
Caution: Although I haven't noticed any issues with this technique, making the phone think its a different model may have some implications somewhere along the line!
Nice, thanks! After changing the Modelname to HTC or KOVS100 or anything - the 3D acceleration menu appears there.
But now another problem - after I activate 3D acceleration (and soft reset or not, doesn't matter) pressing the carousel button doesn't do anything anymore and looking at SMS or Email will look the same as it was before, without 3D acceleration. As soon as I disable 3D acceleration from the SPB settings menu, the carousel works again (of course, without 3D effects).
I wonder if the X2 drivers are the problem somehow. Should I try to change my 3D drivers?
darthmelk said:
Nice, thanks! After changing the Modelname to HTC or KOVS100 or anything - the 3D acceleration menu appears there.
But now another problem - after I activate 3D acceleration (and soft reset or not, doesn't matter) pressing the carousel button doesn't do anything anymore and looking at SMS or Email will look the same as it was before, without 3D acceleration. As soon as I disable 3D acceleration from the SPB settings menu, the carousel works again (of course, without 3D effects).
I wonder if the X2 drivers are the problem somehow. Should I try to change my 3D drivers?
Click to expand...
Click to collapse
Activate 3D acceleration and change the contents of the \Windows\ModelName.txt back to X1 and it wil be ok!
With this change the panels keep on working? thanks
hiey said:
Activate 3D acceleration and change the contents of the \Windows\ModelName.txt back to X1 and it wil be ok!
Click to expand...
Click to collapse
That I didn't try. I eventually changed the ModelName back to X1i, but I had already changed the 3D acceleration to Off. I'll try this when I meet my father (who is using SPB) again.
But I'm not sure this would work. Before I had a ROM (almost the same as I use now, an older version) with the ModelName KOVS100 and it worked without having to change it to X1i.
I'm pretty sure that it's an X2 driver issue, since the older ROM with ModelName KOVS100 didn't have the X2 drivers. But I don't know how to change back to X1 drivers (uninstall is not possible, the drivers are cooked in the ROM). Can anyone help?
Work but the panel crash....
If you like to experiment, you could try with the X2 Panel Manager, maybe that one doesn't crash... Dunno.
Ok... got a problem:
I opened the file model.txt and modified the X1i to HTC Touch HD T8282.
Then, I looked into the SPB settings menu and there was no 3D accel. info, so I decided to softreset the device.
After the softreset, when windows mobile loads and asks for the password, my password is not accepted.
Is there any chance for me to get and use again my phone, except for hard reset ?
Interesting... I didn't have a password when I changed the .txt.
yeah... I had to use SonyEricsson update software and flash my rom.
reinstalled everything but this time I disabled the Lock all together. Modified the txt file, soft reset, changed the 3D settings, modified txt file to X1i and then soft reset again, looks like this time no problems
So far it works ok with my X1 (original ROM, winmobile 6.1), after modifying the ModelName.txt, no hangups.
albireox said:
So far it works ok with my X1 (original ROM, winmobile 6.1), after modifying the ModelName.txt, no hangups.
Click to expand...
Click to collapse
What about the panel manager? Still working while you have 3D acceleration on?
That I haven't checked. But it seems it's not working. You have to switch back to No 3d acceleration, do a soft reset, and just then the panels work again. I usually use the panels just when I need the FM radio. By the way, is there a method to start the FM radio without using the panels?
LE: Got it . Thanks Pubba!
Maybe you could try with the X2 panel manager. Unfortunatelly I don't have the X1 with SPB right now to try it myself, but hopefully in a few days...
Thanks a ton for this info. I had tried the registry edits too to no avail. Changing model id to KOVS100, reset, turn 3D on worked.
Unfortunately, carousel won't open when I change back to X1i.
Also, X1 Panel Manager freezes phone.
Solution is just to leave it at KOVS100 - doesn't appear to cause any issues.
Also, just use this app http://forum.xda-developers.com/showthread.php?t=531600 for FM radio and the usefulness of Panels is obsolete.
With the panel manager of the x2 the panel works?
emuX said:
The easiest way I've found is to make your device think its someone else... change the contents of the \Windows\ModelName.txt (currently "X1i") to the model code for the Touch HD ("HTC Touch HD T8282") and you get 3D Acceleration!
You'll probably need to reboot to get it working and I always need to re-run the Connection Setup afterwards.
Caution: Although I haven't noticed any issues with this technique, making the phone think its a different model may have some implications somewhere along the line!
Click to expand...
Click to collapse
Hello, I´ve tried this out but the phone says that I cannot edit the document......do you have any idea why??
Thanks
alehung79 said:
Hello, I´ve tried this out but the phone says that I cannot edit the document......do you have any idea why??
Thanks
Click to expand...
Click to collapse
You will have to do it with total commander
Chaosstorm said:
You will have to do it with total commander
Click to expand...
Click to collapse
Thanks buddy
Here's my problem: ever since I flashed CM7 and tried to tolerate all the FXProject defects (eg. No touchpads for Dead Space, no camera, no haptic feedback /vibration, no flash, etc.), there was one of those defects that really hurt me from inside... the fact that the circle button is treated ONLY as a back button, and not a game button. I'm aware there are files in the internal flash memory that set the phone's key layout (/system/usr/keylayout/) but I'm just to lazy to figure it out so I'll leave the question to the pros on the forum: How to fix it? I bought this phone considering I'm a dedicated gamer (still have a life tho ) and not being able to kick the opponent's face in Bruce Lee and every other kind of silly stuff you could do with this epicness we call Circle button is just pathetic. You could send me the Original stock rom key layout file(s) so I can replace/compare and fix. Thanks in advance
For starters i'm sure FXP is sorry you have to "Tolerate" all his hard work second the O button acts as the back button on stock too. It's just these games are meant to work in conjunction with sony's software. Remove that and replace it with a rom built from source and thats what you get.
Sent from my R800i using Tapatalk
AndroHero said:
For starters i'm sure FXP is sorry you have to "Tolerate" all his hard work second the O button acts as the back button on stock too. It's just these games are meant to work in conjunction with sony's software. Remove that and replace it with a rom built from source and thats what you get.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Firstly, I somehow understand that part of "remove that and replace it with a rom..." and now the part I didn't understand pretty much, "...built from source". I understand everything has to be compiled from source code to be executed, but as a noob, I simply didn't understand, could you explain?
Secondly, I downloaded an app from the Market called "Xperia Play Test" that showed up what buttons are pressed in the screen and when I press the circle button it appears next to the physical back button showing up as "back", haven't tried yet on stock rom andsee what happens.
Third, I really think fxp did a good job bringing such a nice rom onto the Xperia's, which gives you simple2ext, theme engine, power bar widget and other cool stuffs, which is why I haven't decided yet to revert to stock.
Anyways, just explain that 'rom built from source' thingy please. Thanks
DanielEGVi said:
Firstly, I somehow understand that part of "remove that and replace it with a rom..." and now the part I didn't understand pretty much, "...built from source". I understand everything has to be compiled from source code to be executed, but as a noob, I simply didn't understand, could you explain?
Secondly, I downloaded an app from the Market called "Xperia Play Test" that showed up what buttons are pressed in the screen and when I press the circle button it appears next to the physical back button showing up as "back", haven't tried yet on stock rom andsee what happens.
Third, I really think fxp did a good job bringing such a nice rom onto the Xperia's, which gives you simple2ext, theme engine, power bar widget and other cool stuffs, which is why I haven't decided yet to revert to stock.
Anyways, just explain that 'rom built from source' thingy please. Thanks
Click to expand...
Click to collapse
On the pad, the default android actions are X=Ok or select and O=Back, Xperia play optimised games work in conjunction with the sony firmware to ignore the default android action while in a game thus allowing you to use the buttons for game inputs. If you remove the sony software, many of these games can no longer ignore the default android action rendering the O button useless in most cases. This is nothing to do with cyanogen nor can it be fixed as it's not a bug.
"Built from source" just means the rom was compiled from the source code provided by the Android open source project (Asop)
AndroHero said:
If you remove the sony software, many of these games can no longer ignore the default android action rendering the O button useless in most cases. This is nothing to do with cyanogen nor can it be fixed as it's not a bug.
Click to expand...
Click to collapse
So, basicly, I can't do nothing for it, and while I have cyanogen the O button is rendered useless, unless I use stock? Or is there any other whatnot that can ignore the O button? Or disable the back function so the key is still recognized by the app? I can live without using the O button as a back button.
DanielEGVi said:
So, basicly, I can't do nothing for it, and while I have cyanogen the O button is rendered useless, unless I use stock? Or is there any other whatnot that can ignore the O button? Or disable the back function so the key is still recognized by the app? I can live without using the O button as a back button.
Click to expand...
Click to collapse
It dosent happen for every game. For example gameloft games can use the O button no probs. Maybe you can get the results you want with a button mapping app. I think there is one in themes and apps
BUMP:
sorry to resurrect this thread, but this is still a problem, I'm working on a JXD S601 that uses AOSP and I've hit a wall with modifying the qwerty.kl on that device trying to get back/circle to function the same as stock xperia play.
As stated in this thread, the problem is app specific, most operate fine with BACK and others do not, Trying to change it to BUTTON_A (what I determined to be the translated input by viewing the stock qwerty.kl file) does not fix this either.
I have cyanogenmod on my play and I recognize it as a problem on that device as well. Is it possible we can get some assistance looking into what is wrong here?
johnsongrantr said:
BUMP:
sorry to resurrect this thread, but this is still a problem, I'm working on a JXD S601 that uses AOSP and I've hit a wall with modifying the qwerty.kl on that device trying to get back/circle to function the same as stock xperia play.
As stated in this thread, the problem is app specific, most operate fine with BACK and others do not, Trying to change it to BUTTON_A (what I determined to be the translated input by viewing the stock qwerty.kl file) does not fix this either.
I have cyanogenmod on my play and I recognize it as a problem on that device as well. Is it possible we can get some assistance looking into what is wrong here?
Click to expand...
Click to collapse
It is STILL a problem, but this thread will die and nothing will stop that. Sorry.
I already gave up and flashed Stock ROM and with lots of effort I have found nothing on the interwebs that serves as a fix to the O button. That's sad isn't it.
I'm not on CM, but have you tried changing the appropriate keylayout file in /system/usr/keylayout/ from "BACK ALT WAKE_DROPPED" to "BUTTON_B"? Cuz with it set to BUTTON_B, it's still recognized properly in-game on the stock ROM but doesn't act as the "Back" button anymore
You said you tried changing it to BUTTON_A but that's wrong anyway
jacklebott said:
I'm not on CM, but have you tried changing the appropriate keylayout file in /system/usr/keylayout/ from "BACK ALT WAKE_DROPPED" to "BUTTON_B"? Cuz with it set to BUTTON_B, it's still recognized properly in-game on the stock ROM but doesn't act as the "Back" button anymore
You said you tried changing it to BUTTON_A but that's wrong anyway
Click to expand...
Click to collapse
Oh really? I thought BUTTON_A was square and BUTTON_B was triangle...
DanielEGVi said:
Oh really? I thought BUTTON_A was square and BUTTON_B was triangle...
Click to expand...
Click to collapse
Nope, square is BUTTON_X and triangle is BUTTON_Y
i meant button_b but regardless, the keylayout is identical to the stock on aosp. I think the problem might be in the kcm binaries rather than the keylaout files. It's a theory I'm looking into
Hi,
If enough people will want this app Tigger31337(WildChild ROM) said he would look in to it..
Please post a reply if you're interested.
Tnx!
Camera
That would be awesome. Having to touch the screen actually makes it a little harder to snap a quick picture.
That would be great!
Yes i want it too
Me too want this cam
Sent from my HTC Wildfire S A510e using xda premium
Count me in.
Sent from my HTC Wildfire S A510e using xda premium
Me Too
Yes me too :thumbup:
Tigger is my favorite developer
And his Rom is the best
Send from my HTC Wildfire S
ROM. Wildchild. v2. 0
Me tooo
Sent from my HTC Wildfire S A510e using xda premium
Me too
Sent from my Wildfire S A510e using xda app-developers app
meee tooooo :laugh:
Me too, please!
(Oh, wait... )
So, now that the WildChild Sense is 99.9% finished (look for it soon) I promise to give this some attention.
Off the top of my head, it seems trivial to remap the VolUp key to be a global Camera Shutter key (if anyone's desperate for this, I can release it in about 5 mins!) but I have the feeling that we all want the VolUp key to release the shutter only from within the Camera app itself. That will require some fancy footwork. I've yet to see it done for a Sense 2.1 ROM so... no promises, but I will take a look at it shortly.
Thank you, all, for voicing your request.
Enjoy the weekend,
Tigger31337 said:
Me too, please!
(Oh, wait... )
So, now that the WildChild Sense is 99.9% finished (look for it soon) I promise to give this some attention.
Off the top of my head, it seems trivial to remap the VolUp key to be a global Camera Shutter key (if anyone's desperate for this, I can release it in about 5 mins!) but I have the feeling that we all want the VolUp key to release the shutter only from within the Camera app itself. That will require some fancy footwork. I've yet to see it done for a Sense 2.1 ROM so... no promises, but I will take a look at it shortly.
Thank you, all, for voicing your request.
Enjoy the weekend,
Click to expand...
Click to collapse
Thank you very much for this!!
We really appreciate the effort.. And looking foreword for updates..
Have a great weekend.
Hi, I can give U a temporary solution.
Download this software
https://www.dropbox.com/s/d7x58xb2orf1n1s/BR0.2.4.1.apk
Install it.
Remap the keys as you like (you can only remap volume up and volume down shown as Media next and media previous in the soft).
U just need to know what state means. 3 states are there, Wake, Wake_dropped & none. For camera button I'd prescribe U should select NONE.
Wake = Means they will work even when screenlock is on
Wake Dropped = Means will work only when screenlock is off
You can alternatively do the same by editing /system/usr/keylayout/marvel-keypad.kl
Same process but in that case u have to do it manually. Just a little more time consuming. And revert back is a click away in that software(check >Menu>Settings). or in the second process delete marvel-keypad.kl and rename marvel-keypad.kl.bak as marvel-keypad.kl!!!
finance.resat said:
Hi, I can give U a temporary solution.
Download this software
https://www.dropbox.com/s/d7x58xb2orf1n1s/BR0.2.4.1.apk
Install it.
Remap the keys as you like (you can only remap volume up and volume down shown as Media next and media previous in the soft).
U just need to know what state means. 3 states are there, Wake, Wake_dropped & none. For camera button I'd prescribe U should select NONE.
Wake = Means they will work even when screenlock is on
Wake Dropped = Means will work only when screenlock is off
You can alternatively do the same by editing /system/usr/keylayout/marvel-keypad.kl
Same process but in that case u have to do it manually. Just a little more time consuming. And revert back is a click away in that software(check >Menu>Settings). or in the second process delete marvel-keypad.kl and rename marvel-keypad.kl.bak as marvel-keypad.kl!!!
Click to expand...
Click to collapse
Thanks mate ..
But I want to remap the Vol.up only for the camera app..
finance.resat said:
Hi, I can give U a temporary solution.
Download this software
https://www.dropbox.com/s/d7x58xb2orf1n1s/BR0.2.4.1.apk
Install it.
Remap the keys as you like (you can only remap volume up and volume down shown as Media next and media previous in the soft).
U just need to know what state means. 3 states are there, Wake, Wake_dropped & none. For camera button I'd prescribe U should select NONE.
Wake = Means they will work even when screenlock is on
Wake Dropped = Means will work only when screenlock is off
You can alternatively do the same by editing /system/usr/keylayout/marvel-keypad.kl
Same process but in that case u have to do it manually. Just a little more time consuming. And revert back is a click away in that software(check >Menu>Settings). or in the second process delete marvel-keypad.kl and rename marvel-keypad.kl.bak as marvel-keypad.kl!!!
Click to expand...
Click to collapse
I didn't download the s/w, but if it behaves the way you say, then that won't quite work. For starters, I need to map volume to more than just WAKE or MEDIA (it has to be CAMERA). If your s/w can't do that, then I can just do it by hand (very easy). The problem, as I described earlier, is that it will be a GLOBAL change. Nobody wants that. The goal is to get Vol+Up to Shutter only from within the camera apk.
Second, your description of WAKE vs. WAKE_DROPPED isn't entirely accurate. It has nothing to do with screen on/off. It has to do with whether or not the h/w button function will be passed along to the app after the WAKE call. (WAKE sends the h/w call to the app, but WAKE_DROP does not).
Anyway, gimme another couple of days and I'll start working on this. Sorry about the delay.
Just a little teaser...
I'm able to get the HTC camera app to take a picture with the Volume rocker... but I don't like it.
I must have broken something else in the process because I (sometimes) get visual artefacts on the bottom of the picture (green bars). Also, the layout looks a bit wonky but still functional.
And finally, it's unpredictable when the camera will zoom and when it will actually take a snapshot when the vol keys are pressed. It seems like a long press will zoom and a short press will release the shutter (which is what i wanted) but it doesn't always work that way.
Now here's the real issue. I always thought that a h/w shutter button would be better than tapping the screen. But, after hacking around with it, it turns out that tapping the screen generated less shake for me! Try it yourself. If you hold your phone steady and press the Vol Up button, for me, there is a very slight movement on the camera. But if I'm holding the phone the same way (by all 4 corners) and then use the tip of my index finger to tap the shutter icon, I get practically no motion == clearer shot. (Maybe that's just me!)
In any case, I'm quite happy with the touchscreen shutter (and I'm busy as hell) so I'm not really driven to complete this project. That being said, I will glady spend a few more days on it and then release whatever I have for some other keener, smarter folks to complete.
Thanks dude..
We'll appreciate what ever release you'll give us..
A small motivation..
I was trying to take a pic of me and my gf yesterday..
It just impossible with the touch shutter..
But in the other hand.. Why ruin the view with my ugly face
It'll be fine if you simply disable the volume zoom function. Its digital zoom anyways, so we can always crop the pic later. So you can maybe map volume down to re-focus & volume up to click!
maoz59 said:
Thanks dude..
We'll appreciate what ever release you'll give us..
A small motivation..
I was trying to take a pic of me and my gf yesterday..
It just impossible with the touch shutter..
But in the other hand.. Why ruin the view with my ugly face
Click to expand...
Click to collapse
HTC's self-portrait is amazing. Its got face detection, try it out!
Hi all
Tigger U r the boss and I m just a noob. I hardly know anything about android.
Anyways, here is another temporary solution... Hope U like it or hope U not But i'm using it currently so ill just post that, glad if it help anyone.
Download camera360 and this S/W
The camera is better than stock I think. Use the longpress camera key shortcut as any volume control software (I use hide it pro). And long press search key as the Aneq Equalizer free so that U can switch equalizer when u listening to music. I use vol up as next track and vol down as camera. works pretty well for me. Vol up press after remap is also used to change radio stations.. I m having good fun.:good: