Android Devs / chefs,
I was wondering if someone could help me with a Bluetooth incompatibility issue. The Bluetooth in my Mazda CX-9 has never worked with the Froyo builds available on this site. The Bluetooth audio works fine for music playback but the phone crashes when I try to place a call. I figured loosing Bluetooth was an OK price to pay for having a great phone.
Then the EVO Sense builds started coming and suddenly my Bluetooth works great. I assumed it was a difference between the EVO kernel and the first gen kernels and the EVO code base "Fixed" the incompatibility.
In the past week several new /updated builds have been released that combine the EVO kernel with stock android or Cyanmod based builds. I thought they were going to be the answer to my prayers, but unfortunately the old incompatibilities are back.
Now I know your all thinking why don't you just run the sense based builds. the problem is that I don't like Sense. If I wanted Sense on my phone i wouldn't have ever moved off of Winmo.
So here is my question. I am not a developer but I have a workable knowledge of Linux and I have a desire to fix this issue. I understand that it is unlikely that any developers happen to have the exact same vehicle / Bluetooth setup as I do, so how I can provide useful error logs / dump files / ??? to the development community so someone much smarter then I can work this issue?
I am willing to do my part, provide error files, test new versions, donate to a solution. I just want to know the best way to get involved.
Thanks for the help / guidance
Mike
So using CM builds (like HyperDroid) and a Nexus based kernel (like michyprima r11) also your bluetooth doesnt work ?
v-b-n said:
So using CM builds (like HyperDroid) and a Nexus based kernel (like michyprima r11) also your bluetooth doesnt work ?
Click to expand...
Click to collapse
Correct. The only builds that have worked are EVO based sense builds.
Related
Does anyone know the current status of ICS development for Amaze? Contemplating switching from Sensation, which is just at the doorstep of getting pure AOSP ICS, currently few minor bugs to be worked out. Just wondering how far development has gone, perhaps at other sites?
Xboarder is doing a ton of the work here and as far as I know he is the one working on it. I believe his latest thought was porting it from another device but so far all we have had is a functional touchscreen.
craigtut said:
Xboarder is doing a ton of the work here and as far as I know he is the one working on it. I believe his latest thought was porting it from another device but so far all we have had is a functional touchscreen.
Click to expand...
Click to collapse
Similar stuff going on @ sensation - Tripnraver is doing awesome work @ Modaco. I had tried his pure AOSP ICS rom and it's almost ready, save camera and bt, and I can't believe how amazingly fast and snappy it was. Not my daily driver yet, but mighty close.
I guess I should be expecting similar time frame from xboarder (i used one of his CM7 based roms on sensation).
I'll raise a toast to our first successful developer, and send them some beer change, too They all deserve much for their hard work.
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=1378294
The last post from him says he is working on something else currently.
Just out of curiosity, is anyone working on a new ROM for out G-tabs. It's been over two months since a truly new one has been posted.I'm not complaining about what has been accomplished. I'm just observing other devices getting fresh builds, enhancements and even ICS for several. Is out device too long in the tooth for consistent updates? I have donated to some developers so I do support all of the great work on this device. I'm just curious. Please don't take offense to my inquiry.
Have you looked at the ICS build for the GTab that Team DRH is piloting over at Slatedroid?
No I haven't. Ill head over and check that out. Thanks!
You should also check out teamdrh.com
Sent from my Desire HD using Tapatalk
What's the status of cm7 and gtab support? I notice they haven't done nightly builds since november for the smb_a1002 device...
When I get some spare time I'll boot up my build vm and try making some new roms based on stock cm7.
I'm not too familiar with the reasons and the technical stuff. Why isn't there a reliable AOSP ROM for the Rezound? What is it exactly that makes it difficult to develop one?
The ril hasn't been completely worked out for any AOSP roms
It has to do with the way Google has implemented support for CDMA devices. Google doesn't officially support CDMA devices in the Android framework they provide, so its up to device manufacturers (HTC) to create the necessary support and add it in. Right now, the developers who make ROMs are probably tearing apart the recent HTC leaks looking for the bits and pieces they need to put an AOSP ROM together.
It is the LTE that is the problem. Basically any CDMA device can get AOSP no problem but our device has a very complicated radio. It supports CDMA+LTE+EVDO+GSM so it is pretty much hacked together by HTC themselves.
I tell you one thing. The first developer who provides a near perfect working of ICS AOSP is going to get $15 from me.
con247 said:
It is the LTE that is the problem. Basically any CDMA device can get AOSP no problem but our device has a very complicated radio. It supports CDMA+LTE+EVDO+GSM so it is pretty much hacked together by HTC themselves.
Click to expand...
Click to collapse
Not that I know anything about this subject, how did the Thunderbolt get it solved in the end?
the non-Sense development has been disappointing so far, no AOSP and no MIUI....I think the people talking about the ril have it right, if it was LTE that was the problem we'd have AOSP roms out that don't have working LTE like some other phones do
I Am Marino said:
Not that I know anything about this subject, how did the Thunderbolt get it solved in the end?
Click to expand...
Click to collapse
Not sure but it was easier for the bolt cause s-off.
So is it right to assume that if we get full s-off then comes AOSP?
What exactly is s-off?
Cares said:
So is it right to assume that if we get full s-off then comes AOSP?
Click to expand...
Click to collapse
it's possible but can't really be proven since we literally have full access with the exception to the actual radios when flashing. devs can already view radios to iron out the issues. it's just tricky to solve a scattered puzzle
S-OFF has NOTHING I repeat NOTHING to do with AOSP. The TBOLT had more people working on it and the RIL isn't probably as complicated. They still don't have AOSP ICS working either.
Any developers actively working on this? What would it take for CM to start? Do they need the RIL figured out?
Cares said:
Any developers actively working on this? What would it take for CM to start? Do they need the RIL figured out?
Click to expand...
Click to collapse
There is an active CM9 Alpha thread in the dev section with updates on where it is.
First of all, I know that this might not be the right forum for this, but since this id is new I am not allow to post the thread on the development forum. Now that I got that out of the way. I think a lot of you would really enjoy this video =)
We have started an effort to port HTC View to AOKP ICS. It's far from fully working. But we hope to get some of the basic functionality working in the coming weeks before we release the rom. So stay tuned!
Video 1
http://youtu.be/mW8qLrse4pc
Video 2
http://www.youtube.com/watch?v=bA9IllruYZA
List of things that are working so far.
WiFi, touch screen, captivity buttons(no back light), GPS, sound, HW accelaration? (not sure, as we don't know how to test it), internal sd card
List of things that we're working on before a rom release.
1. On screen button has weird look on some apps, it shrinks to a very small icons.
2. HD movies don't play, Omx codec issue?
3. Touch screen seems to be un-responsive in some game apps.
4. BT doesn't work at all (not as important)
5. Pen doesn't work at all (not as important)
If you have any ideas on how to fix these issues or provide some ideas what could be the cause of the issue (for example, you encounter the issue in other devices and know where to look for the issue) Please let us know by posting on the thread or PM us so we could speed up the release.
This thread is now close and has been moved to development forum as there is a pre-alpha rom for download.
http://forum.xda-developers.com/showthread.php?t=1673430
That looks great, i dont have an evo view, but a flyer bu i see that you have been able to avoid the graphic seizure we have on the flyer roms, i think maybe you and drew garen could colaborate some of your work, but idk, im not a dev or anything, but looks great
Drew Garen ROM
Same here hope you can collaborate with drew to get the graphical seizure issue worked ot between the two of you - I'll post this in Drew Garen's Dev thread.
We're open to share our experiences, if someone post specific questions regards to a specific problem like graphical seizure issue mhkabir98 mentioned. We could provide some ideas. But keep in mind that we're still talking about 2 different devices so there might be areas where they will differ.
Can you elaborate or maybe post a short video of what you mean by graphical seizure?
if i get the time i will eventually take some pics and tape it so you can see it
Wow, looks great so far. Hope to see WiFi, Bluetooth, and GPS working soon.
I'm willing to test if you need it. I don't really use my View for anything important right now.
awesome man! pumped!
looking good! thanks for sharing the progress. sounds very promising. as a view user, the idea of getting ics before the flyer makes me grin.
schadenfroh said:
looking good! thanks for sharing the progress. sounds very promising. as a view user, the idea of getting ics before the flyer makes me grin.
Click to expand...
Click to collapse
your name fit's very good to your comment xD
freak4dell said:
Wow, looks great so far. Hope to see WiFi, Bluetooth, and GPS working soon.
I'm willing to test if you need it. I don't really use my View for anything important right now.
Click to expand...
Click to collapse
Got sound to work. Graphic is much better now, there are no red boarders anymore. Wifi is so close to working.... thanks for the offer, will probably need help when we test app compatibility.
yncconsulting said:
Got sound to work. Graphic is much better now, there are no red boarders anymore. Wifi is so close to working.... thanks for the offer, will probably need help when we test app compatibility.
Click to expand...
Click to collapse
funny,
i think the Flyer is at the same stage too
you're in a competition and reached the same breakthrough around the same time, cool!
you should work with Garen on the wifi solution, there are always room for programmers to fix things.
This is awesome!!! I had kind if given up.
Sent from my Galaxy Nexus using xda premium
wow i might have to dust off my view now lol
wifi works now. will post a video later with the latest
I will happily donate for this, thanks for your hard work!
oldpueblo said:
I will happily donate for this, thanks for your hard work!
Click to expand...
Click to collapse
thanks. that's encouraging
Update video.
http://www.youtube.com/watch?v=bA9IllruYZA
That's looking great -- awesome work!
Got a newbie question. Since we're building this rom from HTC HC kernel source + AOKP source tree. Does this consider porting or building a rom? What is the difference?
yncconsulting said:
Got a newbie question. Since we're building this rom from HTC HC kernel source + AOKP source tree. Does this consider porting or building a rom? What is the difference?
Click to expand...
Click to collapse
my personal opinion which is: porting if you have no compatible drivers available or framework already working on the platform.
- If HTC did not develop any drivers and framework for ICS and for our view/flyer, it becomes a port.
- If you use drivers from another device because HTC did build it, its a port.
- If you take panel device kernel driver and adapt it to this device, its a port. but changes are development.
porting is using existing source or drivers and make it work on another device.
kernel is an exception since all of it is opensource and everything build a custom kernel.
framework in aokp builds are modified aosp sources, where most is compiled from source with changes to source (which becomes a port, like you see old games ported to new devices)
but those i made, are nearly 100% ports, i did smali changes, a few library hardcoding changes into binary files, and only a few kernel changes.
i would call my changes 100% porting.
even if i ported a camera driver from desire hd, which again is not build from scratch.
a rom build is very common as i see it, when guys combine files after their choice and changes some graphics + apk's changes. that is a definate rom build. if you got not development c/java/smali involved) it cannot be a port or a developer rom, its a rom mod(ified) of an original with changes.
its not easy to define "build" .
a modified rom build, or compiled build from source.
not a direction on the term, but just my opinion on this.
(previously already mentioned that ports never are any good, and ICS builds from source are better.)
some people porting are better than others.
Has anyone had any luck getting the Samsung OEM Car dock to work in any build of the Unofficial Liquid Jelly Bean 2.0 rom?
I found an app in the market called "Dock Sound Redirect" (by xcaliburnhand) in hopes that this would resolve the no dock audio issue. Unfortunately it did not. I did however have an email conversation with the developer, he advised the following:
Please have the ROM dev supporting your model verify the correct mapping exists between the ROM audio device and the kernel audio path (commonly set in libaudio).
Example: DEVICE_OUT_ANLG_DOCK_HEADSET in ROM should map to the path PLAYBACK_EXTRA_DOCK in the kernel.
On Tue, Sep 25, 2012 at 7:29 PM, "I" wrote:
Device information:
Device: SGH-I717 - SAMSUNG-SGH-I717
OS: 4.1.1 - liquid_quincyatt-userdebug 4.1.1 JRO03L eng.andbot.20120905.214646 test-keys
Last intent: None
Audio Device: 2048
App version: 2.15
Click to expand...
Click to collapse
Can a noob with nothing to lose fix this on their own? (ie Me.)
Is this really an issue with the Kernel or an issue with the JellyBean source?
Is there any information here that might be useful to the DEV on this project?
Should I just STFU and quit trying to be helpful?
-Brandon
I hope to one day play my note's music on my GMC truck using a USB such that I can control the playback from the steering wheel controls like an ipod .
I hope some of these efforts are not seen by others as a waste of time!
Sent from my SAMSUNG-SGH-I717 using xda premium
Same here..
theta1594 said:
Has anyone had any luck getting the Samsung OEM Car dock to work in any build of the Unofficial Liquid Jelly Bean 2.0 rom?
I found an app in the market called "Dock Sound Redirect" (by xcaliburnhand) in hopes that this would resolve the no dock audio issue. Unfortunately it did not. I did however have an email conversation with the developer, he advised the following:
Can a noob with nothing to lose fix this on their own? (ie Me.)
Is this really an issue with the Kernel or an issue with the JellyBean source?
Is there any information here that might be useful to the DEV on this project?
Should I just STFU and quit trying to be helpful?
-Brandon
Click to expand...
Click to collapse
I am facing the same issue with T-mobile T989, can you PM me if you find a solution?
Thanks
joroboyvn said:
I am facing the same issue with T-mobile T989, can you PM me if you find a solution?
Thanks
Click to expand...
Click to collapse
The admins for the program I mentioned advised the following:
Please have the ROM dev supporting your model verify the correct mapping exists between the ROM audio device and the kernel audio path (commonly set in libaudio).
Example: DEVICE_OUT_ANLG_DOCK_HEADSET in ROM should map to the path PLAYBACK_EXTRA_DOCK in the kernel.
Since I am still to new to post in some forums, I dropped it and just put up with it not working.
only on TouchWIZ based ROMs
This has been an issue since the first CM9 or CM10 based ROMs started to roll out. The support for the dock is baked into the Samsung based ROM, and has not been ported. It may not be possible without source. So none of the ROMs in the Original Android Development will have audio out via the Samsung dock. I believe this is an issue on the international Note as well, without fix as of yet.
Only the TW based ROMs (labled like UCLF6 or below) in the Development section will work:
Padawan, Black Star, maybe Nebula, Official ICS Stock, etc.
If it says CM on it, forget it, ain't workin'.
Sucks, I love my dock, but cant stand any of the TW ROMs so I've learned to deal with it.
Buy yourself a 90 degree audio cable like this to help with the sticking out factor: http://www.amazon.com/Auxiliary-Audio-Cable-Right-degrees/dp/B004RIQFEG
It's what I did.
I think the reason there is no support is that a capable developer does not have a dock to test with. Many have asked me to work on it, but I just don't have one.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Cyanogen submitted a usb dock audio change on gerrit recently maybe it will work on tomorrows nightly.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2