I have been using android for a short time(about 3 months). My phone has had stock 1.5 and 1.6 roms. Apart from that that cyanogen's, dwang's, wesgarner's, htcclay....
The issue that is driving me nuts is that my phone gets disconnected from my car's stock handsfree(vw)
I started with cooked roms with cyanogen, almost everything worked correctly Bluetooth was working OK untill a version(about the time ramhacks appeared) broke my bluetooth handsfree, so I switched to dwang. I didn't have any issue with his roms.
After a time I got bored of his roms so I tried almost all roms posted here(except espresso/sense roms, I don't like them). The same issue with all of them. I might get disconnected in 2 minutes, 50 minutes....
I don't have any fact that could probe my findings, I suspect that it has something to do with a kernel change that cyanogen did and everyone took it for their roms because it only happens with the roms that took that kernel lines.
Now, after using super d, wesgarner, cyano, htcclay.... I am back to dwang 1.17.1 i customized it a little bit and I can use the phone again while driving, bonessy's rom also works flawlessly
Roms working correctly(for my hands free):Stock ones, dwangs, older cyanogens, bonessy ion rom.
Working with disconnect issue: Cyanogen, wesgarner, kingxclick, super D, pay's rom and may be some others
Any help is appreciated solving this issue
Ps: Sorry for my poor english
Moved as not Android development
stylez said:
Moved as not Android development
Click to expand...
Click to collapse
I think it is, it's related to custom kernels. There are no issues with stock roms and some other kernels
Dude has anyone else tried reading this with a Russian accent? lol
Macrophage001 said:
Dude has anyone else tried reading this with a Russian accent? lol
Click to expand...
Click to collapse
Sure it's funny, why don't you try with my fist in your mouth? This is not about making fun and writing stupid things
xabierd said:
Sure it's funny, why don't you try with my fist in your mouth? This is not about making fun and writing stupid things
Click to expand...
Click to collapse
The bluetooth just becomes inactive and Sense Roms don't have working bluetooth.
Ace42 said:
The bluetooth just becomes inactive and Sense Roms don't have working bluetooth.
Click to expand...
Click to collapse
On a 32b board, but do with a 32a board.
I am using 32b htc magic. I solved the issue partially flashing dwang's kernel into Super D 1.9.2, it doesn't get disconnected anymore. The drawback is that wireless is not working, Do I have to flash anything else apart from dwang's boot.img? Any kernel module missing?
Thanks
Edit: Fixed. I flashed proper wlan.ko into /lib/modules. WIFI working!
Ace42 said:
The bluetooth just becomes inactive and Sense Roms don't have working bluetooth.
Click to expand...
Click to collapse
What can I do to solve this issue? I need bluetooth working at least while its paired
Related
Anyone successfully using this thing? It says it's compatible but mine is not working.. and I don't see a driver for it..
http://store.everythinghtc.com/htc-wired-remote-control-stereo-headset/11A29A5242.htm
Hmm i guess no one has got this working yet :O
I got an older one from my trinity and works perfectly on my HTC Magic (vodafone version and standard ROM ).
Nothing added.
Controls music and phone calls
Gregz78 said:
I got an older one from my trinity and works perfectly on my HTC Magic (vodafone version and standard ROM ).
Nothing added.
Controls music and phone calls
Click to expand...
Click to collapse
The exact same one as in the link above? Chrome control panel, etc?
Exactly the same ... in white
When I plug the remote, nothing appears on the phone, no notification.
When I use the music related buttons, the music player doesn't show but an icon appears in the taskbar to show it's playing music.
Green and red buttons to Answer / make calls work too.
Perhaps something related to the Rogers device ?
Mine still plays music through the handset and not through the headphones. And none of the buttons work. This is annoying.. I am surprised there is only a few of us with this thing.. lol.
I think i have tried it on a few differnent roms, and still no luck. I don't see how it could be a hardware thing.. feels like a driver thing. Even if the music doesn't come out of the headphones, there is no way it should still come from the handset!!!
briggs81 said:
Mine still plays music through the handset and not through the headphones. And none of the buttons work. This is annoying.. I am surprised there is only a few of us with this thing.. lol.
I think i have tried it on a few differnent roms, and still no luck. I don't see how it could be a hardware thing.. feels like a driver thing. Even if the music doesn't come out of the headphones, there is no way it should still come from the handset!!!
Click to expand...
Click to collapse
I'm interested on getting this thing to work, too. I'm running cynogenmods 4.0.1 rom on a 32b device from Vodafone germany and I can hear the music in my headphones but the buttonds don't work and the mic does appear to work.
richermartyn said:
You can search your drivers on the site of HTC.
They will provide you complete drivers. If not possible then you can search it from search engine.
Click to expand...
Click to collapse
Does the drivers really support android?
amc0 said:
Does the drivers really support android?
Click to expand...
Click to collapse
I highly doubt this.
The only thing I can foresee is that a lot of these sites selling them are saying they are available late August, so perhaps they are coming out with the same device that does have new drivers for it.
Unless richermartyn has downloaded said drivers and his remote is working perfectly.
I am jealous that some of you actually have part of it working. Nothing on it works for me.
What type of ear buds do you have (that shouldn't even make a difference!). I have some somewhat nice sony ones.
briggs81 said:
I highly doubt this.
The only thing I can foresee is that a lot of these sites selling them are saying they are available late August, so perhaps they are coming out with the same device that does have new drivers for it.
Unless richermartyn has downloaded said drivers and his remote is working perfectly.
I am jealous that some of you actually have part of it working. Nothing on it works for me.
What type of ear buds do you have (that shouldn't even make a difference!). I have some somewhat nice sony ones.
Click to expand...
Click to collapse
Seems like it's only the 32a/HTC Branded devices that are supported. Got that confirmed from HTC Europe after sending them an email.
amc0 said:
Seems like it's only the 32a/HTC Branded devices that are supported. Got that confirmed from HTC Europe after sending them an email.
Click to expand...
Click to collapse
Interesting.. I guess that would be my Rogers 32a magic.. but I have a hero rom installed.. hmm. I guess I will flash a rogers rom later and see if they work, and if they do, maybe someone can rip them from it or something..
briggs81 said:
Interesting.. I guess that would be my Rogers 32a magic.. but I have a hero rom installed.. hmm. I guess I will flash a rogers rom later and see if they work, and if they do, maybe someone can rip them from it or something..
Click to expand...
Click to collapse
Well to quote the support they said:
"The headset/rc has not been confirmed working for the HTC Magic but it will apparently work on HTC Branded phones and most definitly not on your Vodaphone magic (32b)"
I'll try to see if those drivers do any good or if they're only for winmo phones.
Edit: Regarding the ear buds, I use a pair of WESC Bongo deltas and they work great with the rc when it comes to playing music and using in call.
Ah I see.. "Has not been confirmed".. neat lol.
Well let me know how it goes.
Maybe they will release something for real.. I am seeing a lot of online stores advertising these things to work with the Magic.
Very weird that it's still working for some people though.. sigh. I've barely used it.. lol.
It's a cyanogen rom issue. Installed the latest stock rom and it worked brilliantly.
I am about to try a stock rogers rom.
It was not working on jacheroski or myhero etc etc.. those are all probably similar anyways though.
Edit: still does not work! lol. Which rom did you install and what phone do you have?
briggs81 said:
I am about to try a stock rogers rom.
It was not working on jacheroski or myhero etc etc.. those are all probably similar anyways though.
Edit: still does not work! lol. Which rom did you install and what phone do you have?
Click to expand...
Click to collapse
Here's a 32a port of the rom I'm using. It's supposed to be the latest stock rom for the magic and all the buttons seemed to work except the mute button, but that doesn't matter.
I have a german Vodafone Magic with the 32b board.
http://forum.xda-developers.com/showthread.php?t=532902&page=30
Direct link to the fw:
http://android.smartphonefrance.info...gic-28-32a.zip
and when installing, it seems like you must wipe all your data or the startup can hang on the splash or say that the android process is not running which leads to you having to force close.
For the remote, i'm on a 32B and works perfectly on the Voda stock rom.
Now I just updated with a Hero Rom (Qtek 1.3b).
I will try if it still works.
Edit: Tested on QtekRom 1.3b . Works for calls / volume . The sound is ok thru headphones
amc0 said:
Here's a 32a port of the rom I'm using. It's supposed to be the latest stock rom for the magic and all the buttons seemed to work except the mute button, but that doesn't matter.
I have a german Vodafone Magic with the 32b board.
http://forum.xda-developers.com/showthread.php?t=532902&page=30
Direct link to the fw:
http://android.smartphonefrance.info...gic-28-32a.zip
and when installing, it seems like you must wipe all your data or the startup can hang on the splash or say that the android process is not running which leads to you having to force close.
Click to expand...
Click to collapse
yikes, that 32a port won't even flash for me. No signature, and verification failed. gah!
I tried another rogers/ion rom, still no dice.
briggs81 said:
yikes, that 32a port won't even flash for me. No signature, and verification failed. gah!
I tried another rogers/ion rom, still no dice.
Click to expand...
Click to collapse
Do you have the correct recovery ?
Try flashing with Cyanogen recovery. Worked for me on my device.
Edit: I got a reply from another forum member saying that this rc should work on Superhero roms. I although havn't tested that.
amc0 said:
Do you have the correct recovery ?
Try flashing with Cyanogen recovery. Worked for me on my device.
Edit: I got a reply from another forum member saying that this rc should work on Superhero roms. I although havn't tested that.
Click to expand...
Click to collapse
I am running Amon_RA's recovery, 1.2.0 I think. Oie.. seems like I will have to do some more flashing when I have time. Too bad it was not easy to figure out files used for this device.
In the recent cyanogen roms since 4.19 which required flashing with the htc radio my gps has stopped getting fixes. I am limited to only cell tower location. Maybe this is a radio issue? If so what is the best radio alternative which will work with cyanogen roms? I need my gps back. Thanks.
I just tested gps on my dream with cyan 4.2.1 on top of the htc flash. Working with no problems, even indoors. If you don't get any better tips, I would suggest installing again, and this time wipe ext3 partition in addition to wiping, and don't restore anything from backup for root users etc. before you check the GPS.
Hi
This may not be a tip, but i had the same problems when i upgraded rom, I had copilot and Ndive that worked prior, But stopped after urgrading rom to CYAN 4.1.999
Only solution i found was to try other alternatives, the only one i got to work flawlessly was Sygic mobile maps 9 V7.71, gets a fix almost immediatley and works Perfecto.
Hope this helps
I have the exact same problem!
I flashed cyan 4.21 and stopped getting GPS fix. I wiped, wiped ext3 and installed enomther AOSP 1.6 without the expansion pack. I can't get a gps fix anyway...
axlastro said:
I flashed cyan 4.21 and stopped getting GPS fix. I wiped, wiped ext3 and installed enomther AOSP 1.6 without the expansion pack. I can't get a gps fix anyway... What the hell did cyan do this time. He really messes up basic functionality on android, I think that's why google are trying to stop him.
Click to expand...
Click to collapse
Christ, thats an ignorant post
Cyanogen does not "mess up basic functionality", 99.9% of people running his roms have no such problems, myself included. It was probably something you missed or did wrong in the process. Did you follow the steps in his first post carefully, it is a more convoluted process coming from 4.1.11 because of the changes required by Google. In any case, rooting and installing custom roms has its risks and you chose to accept those risks, stop trying to blame someone else when it goes wrong. Take some responsibility, be constructive and try to find a solution instead of crying about it.
Incidentally, the reason Google had an issue with cyanogen was, completely legitimately, because his roms included some of their closed source apps (mail, youtube, market etc) hence why his new roms do not include those and Google are fine with him now. Try reading about it before you shoot your mouth off
I'm trying to work out the problem right now. I wiped again and installed another rom - not cyanogen. The problem is still here. It seems to be a problem that not only I have. It's quite possible that I, and others having the same issue, haven't followed the instructions correctly or did something else wrong.
Try flashing the radio
http://android-roms.googlecode.com/files/ota-radio-2_22_19_26I.zip
Well, seeing as my GPS just got a fix indoors with Cyanogen's 4.2.2, I think the problem is with you.
Now, without posting what you have done to get your phone to the state it is in now, how in the world can we help figure out what went wrong? This really seems like an isolated incident, and obviously not one that is suggestive of Cyanogen's rom being faulty (pretty damn insulting of you to blame him) since you have the problem even after flashing a rom that you give so much praise to for being 'stable'.
So..... how about you reconsider what you might have done to your phone, and try some troubleshooting...
1. When I am having issues with my GPS, sometimes I find it helps to disable GPS (both wireless and sat), reboot my phone, re-enable them, and try again to get a fix.
2. Use GPS Status2 to see if it is connecting to any sats at all.
See what happens... Who knows, maybe there is something wrong with your phone (ever imagine that?).
Not trying to be rude, or bash you, but you were pretty rude and bashing towards Cyanogen, and then you said you had the problem with someone else's rom too...
daveid said:
Well, seeing as my GPS just got a fix indoors with Cyanogen's 4.2.2, I think the problem is with you.
Now, without posting what you have done to get your phone to the state it is in now, how in the world can we help figure out what went wrong? This really seems like an isolated incident, and obviously not one that is suggestive of Cyanogen's rom being faulty (pretty damn insulting of you to blame him) since you have the problem even after flashing a rom that you give so much praise to for being 'stable'.
So..... how about you reconsider what you might have done to your phone, and try some troubleshooting...
1. When I am having issues with my GPS, sometimes I find it helps to disable GPS (both wireless and sat), reboot my phone, re-enable them, and try again to get a fix.
2. Use GPS Status2 to see if it is connecting to any sats at all.
See what happens... Who knows, maybe there is something wrong with your phone (ever imagine that?).
Not trying to be rude, or bash you, but you were pretty rude and bashing towards Cyanogen, and then you said you had the problem with someone else's rom too...
Click to expand...
Click to collapse
First off. I have tried both steps you suggested.
With gps status I can see 4-5 satelites and the lower right of the display says 0 sats. So I can't get fix, the gps itself works. Could be a problem with gps.cfg, I'm going to look at it now.
The issue occured right after I flashed cyanogen 4.2.1 stable. Even afer wiping entirely and flashing another rom I have the same issue, So I suppose that that the problem might be radio related. I actually consider there might be a problem with the phone, but a user who started this thread also had similar problem after going to cyanogen build. Maybe he did the same mistake as I did. Many times I have installed roms and had no issues while others had them - sometimes they occur sometimes they dont - depending on what spl/radio you are on, even what network you are on and what ROM you are coming from. Sorry for being that rude, I realize that now...
axlastro said:
First off. I have tried both steps you suggested.
With gps status I can see 4-5 satelites and the lower right of the display says 0 sats. So I can't get fix, the gps itself works. Could be a problem with gps.cfg, I'm going to look at it now.
The issue occured right after I flashed cyanogen 4.2.1 stable. Even afer wiping entirely and flashing another rom I have the same issue, So I suppose that that the problem might be radio related. I actually consider there might be a problem with the phone, but a user who started this thread also had similar problem after going to cyanogen build. Maybe he did the same mistake as I did. Many times I have installed roms and had no issues while others had them - sometimes they occur sometimes they dont - depending on what spl/radio you are on, even what network you are on and what ROM you are coming from. Serry for being that rude, I realize that now...
Click to expand...
Click to collapse
We all get upset when things don't work that we expect to, my suggestion about that is to go back and clean up your posts before Cyanogen reads them (hopefully) so as to avoid pissing him off.. He has given us so much, and we don't want to alienate him on XDA...
Anyway, about seeing satellites but not getting a fix, have you tried re-flashing the radio?
You said you have wiped, and flashed two different ROMS. The possibility of it still being a software issue are slim (but still there), if the radio doesn't help... it just may be a hardware thing.
I have never had mine get locks on satellites and not lock-in my position.
I know this stuff has been mentioned, but here is your basic troubleshooting process. Complicated, I know. Shouldn't take all day.
Download GPSStatus2 from the market and check to see if it is connecting to any satellites at all.
a) Go outside, away from buildings and trees, and open GPSStatus2. If it connects to 1 satellite, your receiver is working and it's probably some fluke of atmospheric interference (rain, dust, clouds, temperature, vapor, fog all affect microwave transmission; even air quality) that it can't connect to more. Try some different areas with different weather.
b) If it connects to zero, reinstall radio image from the link a few posts up.
c) Still no luck, go all the way back to stock firmware (flash OriginalSPL if you have DangerSPL installed, then RC29) and let it update to Donut, try again.
d) If it's still not working, your GPS happened to randomly die or something. Call T-Mobile cause you need a warranty replacement. They will send you a new phone, you send the old one back.
You know... if you are only trying google maps, try downloading some alternatives. One off the top of my head is RMaps.
I'm flashing the radio now. I have tried the other steps. I tried to get a fix from different locations, now I'm in the mountains and the device has a clear view to the north, where most sattelites are supposed to be... Yes it could be a hardware issue. As you can see another userr ATINsa, who started the topic has the same issue.
still problems
I don't know why you are attacking that guy. There is a problem. I had it on my old dream which was just stolen and replaced. And now I have it with the replacement. Prior to 4.19 and the radio you had to flash to keep cyan cool with google I had no problems. Google tracks, my maps editor, and google maps have a problem. When using wifi can sometimes connect more. The old cyan roms worked fined. Please don't try to explain to me how to use a gps. I have reflashed and redormatted. This has reccured with all roms since I had to replacwe the radio with the one required for him to be cool with google.
So the quesstion is, what other radios are the newest and will work with gps and cyanogens newest rom?
There are 2 people in this thread with the same prob. A third says google maps didn't work but anothewr gps program did. I have experianced this with2 googlde dev dreams. There is a problem and its not a user problem.
Something like this really sounds like a hardware issue. I don't mess around with the GPS code in my ROMs.
AntiNSA said:
I don't know why you are attacking that guy. There is a problem. I had it on my old dream which was just stolen and replaced. And now I have it with the replacement. Prior to 4.19 and the radio you had to flash to keep cyan cool with google I had no problems. Google tracks, my maps editor, and google maps have a problem. When using wifi can sometimes connect more. The old cyan roms worked fined. Please don't try to explain to me how to use a gps. I have reflashed and redormatted. This has reccured with all roms since I had to replacwe the radio with the one required for him to be cool with google.
So the quesstion is, what other radios are the newest and will work with gps and cyanogens newest rom?
There are 2 people in this thread with the same prob. A third says google maps didn't work but anothewr gps program did. I have experianced this with2 googlde dev dreams. There is a problem and its not a user problem.
Click to expand...
Click to collapse
The thing is, the radio that is flashed with the HTC system image, should be the same radio that you were already running on your phone. I don't think that has been changed since 1.5 came out.
And the problem with your theory of this being more than just an isolated incident is this: most people aren't experiencing this problem, only a handful (two or three people here or there does not a system problem make).
I'm 26 years old and have had windows mobile devices and now I've been on android for about half an year. I have used linux back in school when most of the kids here, blindly defending cyanogen were toddlers. I didn't mean to attack cyanogen or whoever else. It's just that the problem is with at least 2 or 3 people and maybe more. The right thing to do is to calm down and try to go back to a state which works. I have reflashed radio and gone to AOSP donut build. Still no luck. When you wipe you wipe /data and /cache right? What about /system ? I bet it's some of the libraries that have something to do with controlling GPS hardware, which remains after a wipe. It would be a nice idea to flash the SPL again. It will probaby clean things up. This is the next thing I'm going to try. It's a good time for someone with better knowledge of how android works step up and give any other ideas.
For now try :
Flash SPL again (whatever SPL you are using)
Flash Radio (latest one from htc developer site)
Flash some basic rom, like TMO cupcake or donut and let's see of it works. That's what I'm trying to do now. If this doesn't help, we might try the proposed reverting to stock spl and RC29.
axlastro said:
I'm 26 years old and have had windows mobile devices and now I've been on android for about half an year. I have used linux back in school when most of the kids here, blindly defending cyanogen were toddlers. I didn't mean to attack cyanogen or whoever else. It's just that the problem is with at least 2 or 3 people and maybe more. The right thing to do is to calm down and try to go back to a state which works. I have reflashed radio and gone to AOSP donut build. Still no luck. When you wipe you wipe /data and /cache right? What about /system ? I bet it's some of the libraries that have something to do with controlling GPS hardware, which remains after a wipe. It would be a nice idea to flash the SPL again. It will probaby clean things up. This is the next thing I'm going to try. It's a good time for someone with better knowledge of how android works step up and give any other ideas.
For now try :
Flash SPL again (whatever SPL you are using)
Flash Radio (latest one from htc developer site)
Flash some basic rom, like TMO cupcake or donut and let's see of it works. That's what I'm trying to do now. If this doesn't help, we might try the proposed reverting to stock spl and RC29.
Click to expand...
Click to collapse
If you wipe it wipes /data, if you flash a new rom it "wipes" (it really formats) /system and /cache. Nothing is left behind on /system...
Ok. I fixed the issue. I'm on danger SPL , newest radio etc...
I reflashed radio (as adviced above). Prior reflashing the radio wiped and installed enomther AOSP+ADP 1.6, with exp pack 2.11.
After that installed an app from market called GPS TEST (Don't know if it had something to do with GPS being fixed)
It detected 5 satelites right by the window indoors. Then Google maps found my location.
axlastro said:
I'm trying to work out the problem right now. I wiped again and installed another rom - not cyanogen. The problem is still here. It seems to be a problem that not only I have. It's quite possible that I, and others having the same issue, haven't followed the instructions correctly or did something else wrong.
Click to expand...
Click to collapse
well if you tried another rom and its still there .. then the problem might lie with your phone and not the roms you installing .... is anyone else around you with a G1 not getting gps location also ?
Has anyone seen this video?
http://www.youtube.com/watch?v=IlrQtaTH3ZE&feature=related
Person claims they somehow flashed Cyanogen's ROM the flashed Hero Over 1.1 and now you have Dream/G1 with working BT. Has anyone confirmed this is possible, or is this just some garbage?
Thanks.
From what I've read of the bluetooth/hero scenario, it doesn't sound plausible.. but I didn't watch the video cos I couldn't tolerate the repulsive music or the inabality to FOCUS HIS F*CKING CAMERA!!
I also don't see how it's possible to flash hero-over directly over CM, unless hero-over doesn't format the system partition as part of the flash process.. but I'd imagine that would cause all sorts of problems... This smells of horse **** to me, but we'll see if he comes out with a workable process.
Over the course of who knows how long the devs have been able to show bluetooth as on, this however doesn't make it useful if you can't have it connect to anything
I thought as much. Thanks for your input.
JAguirre1231 said:
Over the course of who knows how long the devs have been able to show bluetooth as on, this however doesn't make it useful if you can't have it connect to anything
Click to expand...
Click to collapse
The poster of this video claims to have transferred files over it..
i was able to turn on bluetooth a while back on a hero rom .... but u cant connect to anything
people post fake vids all the time...
right now the only solution ive seen is what maxisma posted about flashing the 32a magic spl on the g1 (dont try this unless your super experienced and know what your doing [ie...if you dont know what 32a or spl, you shouldnt even consider it])
He just replied to my request for a process..
mohfuzul12 has sent you a message:
THIS IS HOW I GOT BLUETOOTH ON MY G1?
1st
Download NOW!!!
http://rapidshare.com/files/287548589/recovery-RA-dream-v...
then when u finish downloading
To Install:
Copy it to your sdcard and open the Terminal Emulator app then type in this code:
su
(if a message pops up click always allow)
flash_image recovery /sdcard/recovery-RA-dream-v1.2.3.img
when u finish
just flash this hero over 1.1r3
here is the link
http://www.4shared.com/file/144480210...
when u done wit everything u should be running and cyanogen rom at the same time and also bluetooth will actually be working.
Click to expand...
Click to collapse
Riiiiiiiiiiiiiiiiiight.....
I'm calling shenanigans.
he probably has malicious apps to get your data lol
idk what hes smokin
raptoro07 said:
Has anyone seen this video?
http://www.youtube.com/watch?v=IlrQtaTH3ZE&feature=related
Person claims they somehow flashed Cyanogen's ROM the flashed Hero Over 1.1 and now you have Dream/G1 with working BT. Has anyone confirmed this is possible, or is this just some garbage?
Thanks.
Click to expand...
Click to collapse
I went to the site and pointed out the fact that no one in XDA has come up with a working HERO in that sense and this guy must have SERIOUSLY brainwashed a few of these kids. One of them started emailing me hate mail and attacking me on Youtube just for questioning the situation.
There's another guy named ItsAnAndroidWorld who's got a video claiming the same thing only he never goes into the bluetooth and tries to turn it on.
I've been reading about using bttest and hcitools to get it working on a HERO rom but i didn't have much luck with HERO Sense. It must only work on a very specific HERO rom.
Yeah, i'm definitely with you guys because i've googled all over for an answer to the HERO rom problem with BT, and there are some possible solutions, but.....i'm not risking bricking my phone just to see if they're right.
I really want Eclair bad.. but I can not live without a camera.
What exactly is the ongoing issue with getting Elcair camera to work - is it a kernel issue or a user space one?
If it is user space I might start looking into it myself using the working donut code as a starting point.
There seems to be very little information on this board about the *development* of Eclair. Everyone is just talking about builds and cooking. Should I be looking at another board for actual Java hacking to get the user-space working (assuming it is in user-space) ?
I think it's due to user space as everything works fine in Donut builds. For example, BlueTooth works fine in polyrhythmic's Eclair builds for Kaiser, while other eclair builds don't.
I'm sure if someone took a look at what polyrhythmic did with his build, you could get bluetooth working on other eclairs, and this could maybe even help figure out how to get the camera working as well.
Just shows how we really took advantage of polyrhythmic's work.
Dukenukemx said:
I think it's due to user space as everything works fine in Donut builds. For example, BlueTooth works fine in polyrhythmic's Eclair builds for Kaiser, while other eclair builds don't.
I'm sure if someone took a look at what polyrhythmic did with his build, you could get bluetooth working on other eclairs, and this could maybe even help figure out how to get the camera working as well.
Just shows how we really took advantage of polyrhythmic's work.
Click to expand...
Click to collapse
BT works in the Eclair builds on this forum too, Perhaps not so well on your Kaiser however.
Did Poly get BT audio working?
Regarding the camera. Thats a great question. I am not sure who is working on it?
myn said:
BT works in the Eclair builds on this forum too, Perhaps not so well on your Kaiser however.
Did Poly get BT audio working?
Click to expand...
Click to collapse
Guess he didn't, just tried it myself and it only connects. No BT audio. According to his front page that BT audio is a kernel problem.
For the record, I don't care about Bluetooth, at all. But I can't go to eclair with no camera.
If it is confirmed user-space, then maybe I will start looking into it myself... although, I find it hard to believe months have gone by based on a simple userland issue?
i think it is user space also, because using an eclair NBH on warm donut camera works fine, but same NBH with eclair and the camera doesnt work so that would rule out the kernel most likely
Yes, it's a userspace problem, I wrote the userspace cam lib for cupcake and donut but there will be some changes needed for eclair and froyo.
I don't have much time at the moment and would rather make the kernel better with what time I do have.
It's probably not a difficult job to get it working, pm me if you need any pointers.
Dukenukemx said:
Guess he didn't, just tried it myself and it only connects. No BT audio. According to his front page that BT audio is a kernel problem.
Click to expand...
Click to collapse
polymod 2.1g with the BT&WIFI update had btaudio working for kaiser.
2.1d lost btaudio but is a much faster build.
mnjm9b said:
polymod 2.1g with the BT&WIFI update had btaudio working for kaiser.
2.1d lost btaudio but is a much faster build.
Click to expand...
Click to collapse
I haven't used Polymod in months. I should probably give it another try.
Any info on the status of bluetooth audio working on 4.2.x? I flashed SlimBeans without realizing that BT audio doesn't work on 4.2.x ROMs. I'd like to use 4.2.x, but I guess until this issue is fixed I'll have to use 4.1.x.
thedeany said:
Any info on the status of bluetooth audio working on 4.2.x? I flashed SlimBeans without realizing that BT audio doesn't work on 4.2.x ROMs. I'd like to use 4.2.x, but I guess until this issue is fixed I'll have to use 4.1.x.
Click to expand...
Click to collapse
No info other than this:
You'll know when its fixed. Users want BT, GPS, Camcorder. When any of these work you'll notice all the posts about it.
skeevydude said:
No info other than this:
You'll know when its fixed. Users want BT, GPS, Camcorder. When any of these work you'll notice all the posts about it.
Click to expand...
Click to collapse
Okay, thanks. I had just noticed someone talking about one of your ROMs and said that GPS was fixed or something, but he wasn't sure about Bluetooth audio yet. Didn't know if that just meant he hadn't tested it yet.
Thanks, anyway!
They are tough to fix unless we have a 4.2 kernel...and we dont have a 4.2 kernel, and we dont know when we will get one...
ai6908 said:
They are tough to fix unless we have a 4.2 kernel...and we dont have a 4.2 kernel, and we dont know when we will get one...
Click to expand...
Click to collapse
Ahh, I see. I appreciate you telling me that. I just switched over to the AHD yesterday, and I've been reading all last night and all today on here. Didn't see anything about it however.
Thanks again!