Related
Hi,
I've used Juicy's ROMs (v1.08) and MSR 1.1 and both of them do not permit SSH input.
I've tried both pocketputty and Pragma VT, and nothing works. I can't pass any ls or any command after logging in (Pragma VT passes username and password through application, so that atleast let's me log in).
I think this is an underlying problem and not a ROM issue, can someone please help me figure this out?
Thanks!
---
Solution:
Thanks to jxent for pointing me in the right direction.
Basically, it's not the software's fault or any ROM's fault. What matters is the input type you use.
Full qwerty and compact qwerty just don't work on here. The trick is to use the "keyboard" input method and then you're golden.
Good luck, and thanks for everyone else who banged their head for me, including but not limited to Juicy, Mightymike, Juggalo_X and others.
I'm using the GFTC kitchen from ppcgeeks, and ssh with putty works fine. I'm using the stock kitchen with a couple apps added and some preset phone settings.
jyxent said:
I'm using the GFTC kitchen from ppcgeeks, and ssh with putty works fine. I'm using the stock kitchen with a couple apps added and some preset phone settings.
Click to expand...
Click to collapse
Weird, cuz both the ROMS I've used are off the GFTC kitchen.
I've again tried with pocketputty, to nogo. Currently using MSR 1.1.
Devileyez, can you try my 2.4.1 ROM when it goes up tonight?
I want to know if the issue is resolved.
Why do you need SSH input btw?
Regards,
Carty..
Carty said:
Why do you need SSH input btw?
Regards,
Carty..
Click to expand...
Click to collapse
Why do you need browser input btw?
Juicy47 said:
Devileyez, can you try my 2.4.1 ROM when it goes up tonight?
I want to know if the issue is resolved.
Click to expand...
Click to collapse
I'll try it out over the weekend and let you know.
I'm a telus diamond owner and have used pocketputty on the stock ROM, as well as several versions of Juicy (I'm currently on 2.2). It has always worked for me, using both password and private/public key authentication.
*However*, I've noticed that it typically takes over 90 seconds to reach the login prompt. For whatever reason, I can lower that time to about 15 seconds if I repeatedly bang on the enter key after pressing "Open".
In answer to Carty's question, I use it to securely tunnel remote desktop connections.
biclops said:
I'm a telus diamond owner and have used pocketputty on the stock ROM, as well as several versions of Juicy (I'm currently on 2.2). It has always worked for me, using both password and private/public key authentication.
*However*, I've noticed that it typically takes over 90 seconds to reach the login prompt. For whatever reason, I can lower that time to about 15 seconds if I repeatedly bang on the enter key after pressing "Open".
In answer to Carty's question, I use it to securely tunnel remote desktop connections.
Click to expand...
Click to collapse
I don't know why you had to answer Carty's question. It was like a Grade 2 question. Besides, he's not asking why do you need ssh.. he's asking why do you need ssh input?
*sigh*
Devileyezz said:
I don't know why you had to answer Carty's question. It was like a Grade 2 question. Besides, he's not asking why do you need ssh.. he's asking why do you need ssh input?
*sigh*
Click to expand...
Click to collapse
I answered his question, as I understood it, because he asked. There's no point discussing that interpretation with you - if he wishes to clarify the question I'm sure he will. There is simply no need for elitist responses like yours. What if he *is* in grade 2?
You seem more concerned with this than my attempt to answer your own question. Did I help you at all in regard to your original problem?
biclops said:
You seem more concerned with this than my attempt to answer your own question. Did I help you at all in regard to your original problem?
Click to expand...
Click to collapse
Ofcourse. You actually helped pitch in with the others who said it works on Juicy 2.4*. So, I've decided to wait for a 2.* version that has no data speed problems and battery drain issues (like everyone on 2.4.1 seems to complain about) and I will flash that one.
Devileyezz said:
Ofcourse. You actually helped pitch in with the others who said it works on Juicy 2.4*. So, I've decided to wait for a 2.* version that has no data speed problems and battery drain issues (like everyone on 2.4.1 seems to complain about) and I will flash that one.
Click to expand...
Click to collapse
there are no battery drain issues or speed problems on 2.4.1
I mentioned I had some issues with speed, but I was playing around with PRL, and a hard reset fixed it.
Well, Juicy's 2.5 don't fix it and neither does MSR1.2. Gonna try GFTC Kitchen 1.04 now.
SSH using Pragma VT or PocketPutty doesn't work. I'm able to login via PragmaVT because, as stated before, it passes login credentials from the program itself.
Make that GFTC 1.05 ROM.
Ok, nope. Doesn't work anywhere.
The only place left to try is TELUS stock ROM. This is the weirdest thing ever.
Solution posted on first post.
Thanks for all the help!
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.
Hey guys, this post is just my way in saying thanks for all the help all of you guys have given me and for making it possible to have android on my HD2
Basically I have been doing some testing and have come up with a combination of things you can do to give yourself a fully working android build Ofcorse some of the information I had to test with was provided by other members but this combination I think is flawless, well at least it is for me ^^.
To begin you’re going to want to get the right WM rom for your android, and after testing I found the best one to be
forum.xda-developers.com/showthread.php?t=734238
I have not had any problems with it. Just flash it to your device and let’s go from there.
Next your going to want to do something allot of members do not think of doing, and that is formatting the SD card PROPERLY, as this eliminates allot of problems for various reasons. The correct way to do this is, boot yourself into Linux, Ubuntu is the easiest in my eyes, and you can get it on a live CD or USB so it’s easy to get into, just boot into Ubuntu plug in your SDcard and its better if you can insert it via an SDcard slot in an adapter. Then format it as FAT not FAT32, I wont explain why this is better, but it will. Check this out if you really want to know why you need to do it ^^ but you don’t really need to know
forum.xda-developers.com/showthread.php?t=750780
Next thing is your android build. Now there are ALOT of builds that work well but there is only one that I believe can give you a real working android experience, and the next part of this guide is based on this build so I suggest you use it .
forum.xda-developers.com/showthread.php?t=740963
Ok, so you have got your build on your card you have booted into it and it’s ready to go, right? Not yet. One of the most annoying things that occur in android under the HD2 is the random freezing and this is how I removed this pesky little annoyance.
1. Unlock your screen and hit the settings key (windows key)
2. Hit settings
3. Hit Cyanogenmod Settings
4. Hit User Interface
5. Scroll down to Accelerometer rotation
6. Make sure ONLY 90 degrees is ticked!
7. Done
Now that setting is how I have managed to eliminate the problem, but don’t worry if you still have this issue, just go back into the Cyanogenmod settings and turn off 90 degrees and then under display turn off Auto-rotate screen, this should eliminate the problems but then your screen wont rotate automatically so its swings and roundabouts really ^^
Top Tips!
DONT use live wallpapers, they WILL kill your battery and drastically decrease the performance of your HD2!
Turn off the GPS as it is on by Default, it drains battery ALOT and isn't necessary most of the time ^^
Get the XDA app because its mega? And you suck if you don’t!
Calibrate the Gsensor, it will reduce the screen freezes (that’s if you even have them, witch you shouldn’t after this guide: P)
Finally, always remember that you should turn off your phone to charge it OR have it booted into WinMo, allot of reasons why you should do this but again just do it
Hope this helped someone somewhere Its my first real post that gave something back to the community and I AM a noob hehe, so any addition to this guide is welcome ^^ Again thanks allot all you guys at XDA that made this possible and I will keep this updated as necessary
Thanks allot. Dane.
xpstyle36 said:
1. Unlock your screen and hit the settings key (windows key)
2. Hit settings
3. Hit Cyanogenmod Settings
4. Hit User Interface
5. Scroll down to Accelerometer rotation
6. Make sure ONLY 90 degrees is ticked!
7. Done
Now that setting is how I have managed to eliminate the problem, but don’t worry if you still have this issue, just go back into the Cyanogenmod settings and turn off 90 degrees and then under display turn off Auto-rotate screen, this should eliminate the problems but then your screen wont rotate automatically so its swings and roundabouts really ^^
[...]
Calibrate the Gsensor, it will reduce the screen freezes (that’s if you even have them, witch you shouldn’t after this guide: P)
Click to expand...
Click to collapse
If this works, I'll be eternally grateful.
shadiku said:
If this works, I'll be eternally grateful.
Click to expand...
Click to collapse
I hope it works for you but remember if you didn't follow all the other steps I cant guarantee and fix and even if it doesn't work, you can disable all screen rotation as I mentioned and this SHOULD fix your problem ^^ I really do hope it works for ya.
Dane.
Forgot to discuss about RADIOS and HARDSPL.
Common man.
FriedSushi87 said:
Forgot to discuss about RADIOS and HARDSPL.
Common man.
Click to expand...
Click to collapse
Well if your looking at this guide, you probably already have HardSPL :l and even if you didn't when you take a look at the ROM pages it explains it there, so I don't think its very productive or helpful to post random crap like that :l And as for the radio, i tested several radios and it didn't make any difference TO ME but if you really want to know the radio i am running its, 2.12.50. Happy now ?
Dane.
xpstyle36 said:
Well if your looking at this guide, you probably already have HardSPL :l and even if you didn't when you take a look at the ROM pages it explains it there, so I don't think its very productive or helpful to post random crap like that :l And as for the radio, i tested several radios and it didn't make any difference TO ME but if you really want to know the radio i am running its, 2.12.50. Happy now ?
Dane.
Click to expand...
Click to collapse
I think it's incredibly important to post that here.
Imagine someone sees an HD2 with android or hears about it from a friend, does a quick google search and finds this thread.
They come in here looking for a quick fix for android....
They could end up bricking their device or something....
FriedSushi87 said:
I think it's incredibly important to post that here.
Imagine someone sees an HD2 with android or hears about it from a friend, does a quick google search and finds this thread.
They come in here looking for a quick fix for android....
They could end up bricking their device or something....
Click to expand...
Click to collapse
/sigh, what are you trying to do here ? cause problems.if you had never even heard about android on HD2 you take one look at the writing in this post and think WHAT, it says things like Flash it to your device and lets go. you wouldnt know how to flash or even what it meant, so you couldn't even brick your device as you would not know how :l Please stop filling up this thread that i made to HELP people not argue with some guy who keeps coming up with random crap that is not going to happen, and i am not being unreasonable by saying that and i am sure many other members will agree im not in the wrong.
Dane.
Unfortunately still having the screen freezes, even after toying with CyanogenMod settings.
Back to the waiting game then.
shadiku said:
Unfortunately still having the screen freezes, even after toying with CyanogenMod settings.
Back to the waiting game then.
Click to expand...
Click to collapse
Did you turn off all the screen rotation under cm settings and normal settings and did you calibrate the Gsensor these things can also resolve the problem, you can also disable the Gsensor in WinMO and this will cure your problem but thats not reccomended ^^ Give those suggestions a try, again hope it works for you.
Dane.
Are we allowed to start a poll asking people which mainstream rom they're using just so we know what is the most common and popular rom is,? Or is it a taboo?
xpstyle36 said:
Did you turn off all the screen rotation under cm settings and normal settings and did you calibrate the Gsensor these things can also resolve the problem, you can also disable the Gsensor in WinMO and this will cure your problem but thats not reccomended ^^ Give those suggestions a try, again hope it works for you.
Dane.
Click to expand...
Click to collapse
I turned all the screen rotation off. Since I'm using ChuckyDroidROM, the gsensor calibration is removed.
In android, it worked for a while but tilting it continually in Gallery3D caused a freeze.
I wish I could disable the theming on shubCRAFT, it's the only thing that puts me off using it.
I think that if you look at this thread you will see
xpstyle36 said:
Next your going to want to do something allot of members do not think of doing, and that is formatting the SD card PROPERLY, as this eliminates allot of problems for various reasons. The correct way to do this is, boot yourself into Linux, Ubuntu is the easiest in my eyes, and you can get it on a live CD or USB so it’s easy to get into, just boot into Ubuntu plug in your SDcard and its better if you can insert it via an SDcard slot in an adapter. Then format it as FAT not FAT32, I wont explain why this is better, but it will. Check this out if you really want to know why you need to do it ^^ but you don’t really need to know
Click to expand...
Click to collapse
that this method is a lot of trouble for no additional benefit over a simple format using WinMo in the phone. If you would "explain why" it would be interesting because no one else can. A full WinMo format, not quick, overwrites the complete data space on an SD card with new redundant data. It also only reserves and writes one FAT where Windows on the PC reserves and writes two. You can't get something from nothing and WinMo non-quick format leaves nothing in the data space. (And yes I do understand full mil spec data destruction and redundent and random erase so everything is destroyed.)
http://forum.xda-developers.com/showthread.php?t=760996&page=5
johnboatcat said:
that this method is a lot of trouble for no additional benefit over a simple format using WinMo in the phone. If you would "explain why" it would be interesting because no one else can. A full WinMo format, not quick, overwrites the complete data space on an SD card with new redundant data. It also only reserves and writes one FAT where Windows on the PC reserves and writes two. You can't get something from nothing and WinMo non-quick format leaves nothing in the data space. (And yes I do understand full mil spec data destruction and redundent and random erase so everything is destroyed.)
http://forum.xda-developers.com/showthread.php?t=760996&page=5
Click to expand...
Click to collapse
Well i may be wrong but as far as i was aware, when you put a linux android build on your SDcard it creates a partition or something like that on the card, (i will look it up and get back to you) and windows cannot see it, wheras linux can see it and therefore it can wipe it, and these left over bits that windows cant see dont always get on when you get a new build Thanks for pointing it out though, just wanna help as many as possible ^^
Thanks
Dane.
shadiku said:
I turned all the screen rotation off. Since I'm using ChuckyDroidROM, the gsensor calibration is removed.
In android, it worked for a while but tilting it continually in Gallery3D caused a freeze.
I wish I could disable the theming on shubCRAFT, it's the only thing that puts me off using it.
Click to expand...
Click to collapse
To be honest i think that if you got yourself a Shubcraft build and then followed the guide then you would end up with a pretty stable build, with no freezing, but if you dont like the theme, then i guess that there is nothing i can do, but hope that a sense version of it is relesed so that you can get yourself a nice stable build ;D
Thanks again.
Dane.
shubcraft themes and "stock"
If you dont like the shubcraft theme you can use this ..
http://forum.xda-developers.com/showthread.php?t=760641
there is even a shub version 1.4c with "stock" Froyo theme here
http://forum.xda-developers.com/showthread.php?t=760641&page=3
thanks to all dev's & builders
ugghuggh said:
If you dont like the shubcraft theme you can use this ..
http://forum.xda-developers.com/showthread.php?t=760641
there is even a shub version 1.4c with "stock" Froyo theme here
http://forum.xda-developers.com/showthread.php?t=760641&page=3
thanks to all dev's & builders
Click to expand...
Click to collapse
Ah ! Thanks alot ^^ Hey ! now you can download that one, follow the instructions and hopefully get a working build D:
Thanks again
Dane.
FriedSushi87 said:
Forgot to discuss about RADIOS and HARDSPL.
Common man.
Click to expand...
Click to collapse
FriedSushi87 said:
I think it's incredibly important to post that here.
Imagine someone sees an HD2 with android or hears about it from a friend, does a quick google search and finds this thread.
They come in here looking for a quick fix for android....
They could end up bricking their device or something....
Click to expand...
Click to collapse
@friedsushi definitely agree with you it isn't clarified correctly about different radios affecting the android or that hspl is necessary for it to work. I am constantly getting people pming me to ask for a walkthrough, which on most occasions I have been able to get this working even though my wordage is more simplified in layman's terms-his looks like its been copy/pasted from all over these pages which in effect isn't a bad thing but to call it a guide and not including vital information is a bit haphazard IMO.
& to the op I am not flaming you but there are already guides out there & don't particularly need another unfinished version to add to the numerous threads which have only just been cleaned up by the mods, plus with only 11 posts 8 of which are on here I honestly don't see much experience to be able to give people guides
11calcal said:
@friedsushi definitely agree with you it isn't clarified correctly about different radios affecting the android or that hspl is necessary for it to work. I am constantly getting people pming me to ask for a walkthrough, which on most occasions I have been able to get this working even though my wordage is more simplified in layman's terms-his looks like its been copy/pasted from all over these pages which in effect isn't a bad thing but to call it a guide and not including vital information is a bit haphazard IMO.
& to the op I am not flaming you but there are already guides out there & don't particularly need another unfinished version to add to the numerous threads which have only just been cleaned up by the mods.
Click to expand...
Click to collapse
I dont get it ? not one word of this was copied and pasted from someone else, and this is just the process i went through to get it to work perfectly, i didnt include the parts about the HardSPL and the radio because, i tryed a few different radios and it made no difference to me AND you wouldn't be able to flash or follow these instructions if you didnt know what hard SPL was. Again i am not flaming but i was just providing a set of instructions that i did, to get it working. So its not a unfinished guide, just because it didnt include some realy basic information. Sorry if i did not make this 100% noob friendly, was just trying to get a few more phones running stable ^^
Dane.
No one discussed any where about the below scenarios.
If booting to android, Phone reboots.
If already in booted and trying to make a call or check email again booted.Always getting booten in android randomly after trying various builds.
Anyone has answer for thatt?
Thanks
So, I recently purchased a new Motorola bluetooth keyboard for my tablet, and I'm going a little mad with the fact that I can't figure out how to use other keyboard layouts from QWERTY. In particular, I'd like to use Dvorak, but the closest solution that I can come up with is to try to remap the keys. I've seen a few other posts on remapping keys on other devices, but I can't seem to find anything that relates to the usual letter keys. Everything out there seems to be for launching apps or something else.
Can anyone help point me in the right direction? I'm sure that I'll have to edit some root files, and I'm ok with doing that, but I'd like to have a decent idea of what I'm doing before I go messing around with things that I don't fully understand.
Thanks in advance,
-Sam
Try adding a vendor/product id file for your keyboard in /system/usr/keylayout/ with the desired mapping of the keys. Should work for usb keyboards (haven't tried it yet), probably will work for bt ones too.
Sent from my A500 using XDA Premium App
tkolev said:
Try adding a vendor/product id file for your keyboard in /system/usr/keylayout/ with the desired mapping of the keys. Should work for usb keyboards (haven't tried it yet), probably will work for bt ones too.
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
I'd be happy to put the time into doing that, but I have no experience in how to do that. Can you point me in the right direction so I can learn/ figure out how to do that?
Sent from my A500 using Tapatalk
samstheman42 said:
I'd be happy to put the time into doing that, but I have no experience in how to do that. Can you point me in the right direction so I can learn/ figure out how to do that?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Well I haven't done that myself but it might help looking at the generic file. From what I understand you have to map the whole keyboard with the key functions you'd like. For example when you press 'q' you might want to have 'a' coming on the screen. The hard part is guessing the key numbers (it's easy for the letters - they are in the generic file, but special keys like ctrl, alt, win, etc. are harder to find) and finding your product/vendor id. As I said that should work with usb keyboards, but I'm not sure at all if that's the right approach for bt ones. Try google before wasting your time on something that might not work at all - someone must have bumped at the same case as you.
Sent from my A500 using XDA Premium App
Anybody else able to lend some help on this one?
Sent from my A500 using Tapatalk
I have the same problem : I bought an usb keyboard with an AZERTY layout but when I press A I got an Q.
Any idea to change this?
Look here... http://forum.xda-developers.com/showthread.php?t=1318579 .
JdgM3NT4L said:
Look here... http://forum.xda-developers.com/showthread.php?t=1318579 .
Click to expand...
Click to collapse
So, I've tried to follow the directions from that tutorial as closely as I can and I keep having problems. It seems like every time I try to edit the .kl file for my keyboard it doesn't work at all. It's definitely pretty frustrating spending a bunch of time editing the key and command codes for every button to find out that it didn't even do anything.
Anybody figure this out yet? I'm really struggling.
If it helps, I can try to break down what I've done so far in another post, but I'm at like 3.5 hours on this project alone tonight and don't feel like I've really gotten anywhere with this.
Gah, now I feel like an idiot. I was doing it right the whole time, the one crucial step that I messed up in the process was deleting the old .kl before pasting the new one in.
Finally got it working. I may post a tutorial on this later since others are having difficulty with this as well.
Thanks to tkolev and Judgemental for the posts and help.
My tutorial can be found here if you've happened to stumble upon this thread before finding it.
Well I am trying to figure out how I can get the BT module from a 2.2 rom to a 2.1 rom. This cuss I want to get the media keys from a BT device working. Now they just don't do anything on 2.1 VE6.2...
Well that is my main goal to get those working
Any idea's and tips are welcome
Already checked if the event is logged when I press the button on the radio and the logcat doesnt show a press recieved thingy. so that is a no.
I'd recommend posting this on the cdma forum as well, and maybe in some non-device-specific android dev forum too since it may be a simple answer like "android 2.1 doesn't contain the code necessary to work with 2.2 bt button control libraries" or something like that.
I have a feeling that what you're trying to do is impossible - I mean, android 2.1 never claimed to have bt button support, and it's highly likely that android 2.2 bt libs will simply never work with android 2.1 in that way.
BUT I REALLY HOPE YOU CAN MAKE THIS WORK!
:-D
cdma forum is more dev-aware than gsm forum I think. good place to start.
dkelley said:
I'd recommend posting this on the cdma forum as well, and maybe in some non-device-specific android dev forum too since it may be a simple answer like "android 2.1 doesn't contain the code necessary to work with 2.2 bt button control libraries" or something like that.
I have a feeling that what you're trying to do is impossible - I mean, android 2.1 never claimed to have bt button support, and it's highly likely that android 2.2 bt libs will simply never work with android 2.1 in that way.
BUT I REALLY HOPE YOU CAN MAKE THIS WORK!
:-D
cdma forum is more dev-aware than gsm forum I think. good place to start.
Click to expand...
Click to collapse
Then I do wonder why Kimera 3.0 sometimes work with them. XD prob something HTCish...
Lirasina said:
Then I do wonder why Kimera 3.0 sometimes work with them. XD prob something HTCish...
Click to expand...
Click to collapse
cool, forgot that part. HTCish seems likely. they change so much that android 2.1 isn't really 2.1 any more.
I hope you can pull it off. I'm NOT saying that I know it is impossible. I don't really know. but it seems likely that aosp will have a different set of conditions from sense roms and working in one may not mean it's possible in the other.
Ok I need to get AVRCP implented into the ROM. Then it will work. VE does not have it.
Lirasina said:
Ok I need to get AVRCP implented into the ROM. Then it will work. VE does not have it.
Click to expand...
Click to collapse
I figured bt remote control profile wasn't in it. the question is - can you find a clever way to push it in and ahve it work.
After some surfing I found something that might be of help. "Headset Button Fix" app: https://market.android.com/details?id=at.zweng.HeadsetButtonFix&hl=en
(I found reference to it here: http://forum.xda-developers.com/showpost.php?p=6125629&postcount=14 The entire thread is a good read)
saj222 said:
After some surfing I found something that might be of help. "Headset Button Fix" app: https://market.android.com/details?id=at.zweng.HeadsetButtonFix&hl=en
(I found reference to it here: http://forum.xda-developers.com/showpost.php?p=6125629&postcount=14 The entire thread is a good read)
Click to expand...
Click to collapse
I am gonna try it. And I wonder if it works. if that is the case. I love to know what the app does behind the screens. And well ill try tomorow.
Ok the app does not work. To bad. But well after I read what it does. kinda logical. Like I said. something HTCish makes it work on the sense roms. Well I just need to get that darn profile to work and then it may work.... But guess not