Trying to fix the bug with using headphones/line-out without mic [SOLVED] - Huawei Ideos X5 U8800

The solution: http://forum.xda-developers.com/showpost.php?p=13982398&postcount=14
I'm trying to fix the bug that when using normal stereo headphones (without mic) or a 3.5mm jack -> 2xrca cable is used, the internal mic is disabled.
I've gotten so far that I have modified rpc_server_handset.c to set value of /sys/class/switch/h2w/state to 2 when headphones are inserted.
Now logcat shows:
V/HeadsetObserver( 148): Intent.ACTION_HEADSET_PLUG: state: 1 name: ksatta headphones mic: 0
D/musicUtils( 829): wired_headset
E/AudioFlinger( 96): EQtype is 0, deviceType is 0
E/SRS_wowhd_binder( 96): startEqualizer EQtype is 0, deviceType is 0
E/SRS_wowhd_binder( 96): startEqualizer bSpeaker is 0
E/SRS_wowhd_binder( 96): equalizer1 EQtype = Default
Click to expand...
Click to collapse
Without the modifications logcat shows:
V/HeadsetObserver( 149): Intent.ACTION_HEADSET_PLUG: state: 1 name: Headset mic: 1
D/musicUtils( 788): speaker
E/AudioFlinger( 96): EQtype is 0, deviceType is 2
E/SRS_wowhd_binder( 96): startEqualizer EQtype is 0, deviceType is 2
E/SRS_wowhd_binder( 96): startEqualizer bSpeaker is 1
E/SRS_wowhd_binder( 96): equalizer1 EQtype = Default
Click to expand...
Click to collapse
So the logs look like my mod is working correctly, however now I can't hear anything from the phone or headphones and also the internal mic is disabled. I've been trying to debug this further, but I can't find where the SRS_wowhd_binder, musicUtils and AudioFlinger logs are generated. Looks like huawei modified some other files than the kernel files, but they haven't released sources for those?
I've tried tags android-2.2.1_r2 and android-2.2.1_r1 from android.git.kernel.org, I found the line where "Intent.ACTION_HEADSET_PLUG: state:..." is logged from HeadsetObserver.java, but I haven't found the others.
Looking further into this..
Anyone have any ideas/suggestions?
edit: looks like Huawei has modified AudioService.class from framework.jar. AudioService handles ACTION_HEADSET_PLUG and and determines if a headset or headphone is connected. Next I think I'll try to decompile the classes and see what's been changed. Or then I'll just try to stick the git version of AudioService on the phone (I wonder what other consequences this'll have, AudioServer handles a bunch of other stuff too).
edit2: I decompiled the phone's AudioService class, it totally ignores the microphone=0 variable Jeez, I wonder why Huawei is cheaper than some others.. Oh well, it's possible to fix. Next step is to edit the decompiled AudioService class and see if that works. Progress
edit3: Actually looks the mic = 0 isn't ignored, the decompiled class just looks really funky. For example "while (true) { return; ...". Might be effects of the decompilation process. Investigating further. The problem might also be in the native libmedia.so
edit4: I found this: http://code.google.com/p/toggleheadset2/ It is used to set output and input to headset.
Might be easiest to fix using a similar way to set output to headphones/line-out and leave the internal mic on.. Looking into that now, I'll post here if I get it to work.

Hey just a quick thing, I have absolutely no idea how easy or difficult it would be to do. But the phones seem to have a problem with headsets/headphones with the iPhone/Blackberry controls on them. It shorts and you can't hear much unless you're pressing the play/pause button.
AFAIK the ground/mic are switched round, but at least for the Samsung Galaxy S there is a kernal + rom out that fixes it so i'd imagine it was somewhat plausible with this phone too.
Don't necessarily need the buttons working (although they work with stock headphones, but meh) it'd just be nice to be able to using any type of headphones.

ryronz said:
Hey just a quick thing, I have absolutely no idea how easy or difficult it would be to do. But the phones seem to have a problem with headsets/headphones with the iPhone/Blackberry controls on them. It shorts and you can't hear much unless you're pressing the play/pause button.
AFAIK the ground/mic are switched round, but at least for the Samsung Galaxy S there is a kernal + rom out that fixes it so i'd imagine it was somewhat plausible with this phone too.
Don't necessarily need the buttons working (although they work with stock headphones, but meh) it'd just be nice to be able to using any type of headphones.
Click to expand...
Click to collapse
I think this would have to be fixed from some other place in the kernel. I'm now trying to mod toggleheadset2 so that it sets the audio output to headphones and leaves the internal mic on. I think your suggestion could be accomplished probably by checking out what they changed in the Samsung Galaxy kernel and doing the same changes.

in HTC devices do not have that problem. After connecting the headset microphone is working, one could see how it is set in the HTC. I have a headset phones that work with HTC and other companies. The X5 does not work and I get the impression that the reason is not software and the construction of the socket (While connecting).

Piron said:
in HTC devices do not have that problem. After connecting the headset microphone is working, one could see how it is set in the HTC. I have a headset phones that work with HTC and other companies. The X5 does not work and I get the impression that the reason is not software and the construction of the socket (While connecting).
Click to expand...
Click to collapse
Yes, the Ideos X5 seems to detect headset connected even if it's headphones or line-out cable. You might be right that it's a hardware issue.
If I get my fix to work it'll just force the internal mic to stay on if headphones/headset is used. It's a workaround

OK. Some "progress"..
When headphones without mic are plugged in the Huawei sets DEVICE_OUT_WIRED_HEADSET to 1 and DEVICE_IN_MIC_ARRAY to 1
When I manually set only DEVICE_OUT_WIRED_HEADSET (even if headphones are not connected), the internal mic is disabled.
If I set both DEVICE_OUT_WIRED_HEADSET and DEVICE_IN_MIC_ARRAY to 0 after plugging the headphones, then the internal mic works, but the output goes to the earpiece..
Then I tried to set:
DEVICE_OUT_WIRED_HEADSET 0
DEVICE_IN_MIC_ARRAY 0
DEVICE_OUT_WIRED_HEADPHONE 1
Then the internal mic worked, but the output was routed to the phone's speaker (speakerphone mode)
I think the problem is in AudioSystem.cpp (part of libmedia.so), of which Huawei hasn't released the source.. Since they haven't modified AudioSystem.java (diffed that..).
There is something really different in there, maybe they have changed it so that always when _output_ is set to headset, input is set to "mic_array" or something... and setting output to headphones sets output to speaker etc etc..
I think I'll still try setting output to speaker (if headphone and speaker ids are switched).. Or then create my own native program which sets output to headphones..
Looks like the main routing is done in frameworks/base/libs/audioflinger/AudioPolicyManagerBase.cpp..
Oh well, I'll continue tomorrow

Thanks for your efforts and for putting so much time into documenting the process.
I think if you can't find a simple solution the next step would be to try and get msm7k drivers with known source code working on our device, rather than spending time on guessing behaviours of a driver which we have no source for.
See the links below for the source for all of the msm7k drivers and a modified msm7x30 kernel from Kali. It might also be interesting to look at the Qualcomm sources to see how they have modified it (I think mostly it's just been changed to accommodate FM radio but there may be other changes).
https://github.com/Kali-/android_hardware_msm7k
https://github.com/Kali-/htc-kernel-msm7x30-exp
I will help with this when I can, but I am extremely busy at the moment with work and uni. Good luck!

stockwell said:
Thanks for your efforts and for putting so much time into documenting the process.
I think if you can't find a simple solution the next step would be to try and get msm7k drivers with known source code working on our device, rather than spending time on guessing behaviours of a driver which we have no source for.
See the links below for the source for all of the msm7k drivers and a modified msm7x30 kernel from Kali. It might also be interesting to look at the Qualcomm sources to see how they have modified it (I think mostly it's just been changed to accommodate FM radio but there may be other changes).
https://github.com/Kali-/android_hardware_msm7k
https://github.com/Kali-/htc-kernel-msm7x30-exp
I will help with this when I can, but I am extremely busy at the moment with work and uni. Good luck!
Click to expand...
Click to collapse
Actually I was thinking the same thing, move on to something of which I have the full source code.
Thanks for the info, I'll look into that. Fixing this "little bug" turned out to be quite a time-consuming process, but I'm getting good experience on modifying android. Also if I one day get this fixed, it'll be awesome

Actually the source for the msm7x30 is in the huawei's kernel source from huaweidevice.com.
I think there are also some problems with the libaudio etc for which Huawei haven't released the source.
Thanks for pointing me in the right direction, I'll see if can modify the msm7x30 from huawei source so that the int. mic isn't disabled.
edit: Yeah, this looks like the place where the actual routing is done. Of course, it's the kernel driver for the sound.. Learning something new all the time

I managed to get some logs from msm7x30.c:
device handset_dual_mic_broadside_tx set 1
device handset_dual_mic_broadside_tx set 0
when plugging headphones in and taking them out..
Now I think I'm getting close. A good point to continue from tomorrow

What I meant was that we don't have the libaudio source from Huawei, but we can use another source (Qualcomm/Kali/etc) for libaudio and then we need to change the kernel driver to suit it (which we can model from Kali's kernel drivers).

stockwell said:
What I meant was that we don't have the libaudio source from Huawei, but we can use another source (Qualcomm/Kali/etc) for libaudio and then we need to change the kernel driver to suit it (which we can model from Kali's kernel drivers).
Click to expand...
Click to collapse
Ahh, I see. Yeah now I understand.
I'll see if I can get the kernel driver modded so that it doesn't disable the internal mic. Ofcourse this would mean that the internal mic is never disabled (the kernel driver doesn't know why the int. mic is being disabled.) So it wouldn't be disabled even when using bt headset etc.. If I have understood correctly. A better way to fix it would be from the libX side. But let's see first how my kernel mod goes

I got it working so that when I plug in headphones during a phone call, internal mic works and the output goes to the headphones
But... the routing doesn't return back to normal without the headphones or if I plug in the headphones before the call etc etc... but this is looking good!

First of all thanks to:
wmi543 and stockwell for helping me get the stock kernel built.
stockwell also for helping me figure out where the problem could be fixed.
genokolar and stockwell for the working recovery.
And everyone else if I forgot to mention someone.
I modified the kernel sound driver (msm7x30.c) so that when the driver is requested to set the headset mic on/off or route to it, the speakerphone mic is used instead. I don't think there's a different mic for the speakerphone physically on the phone, but the device is called "speaker_mono_tx" and it probably uses different settings than when using the phone in non-speakerphone mode. So I figured it's best to use the speakerphone mic device instead of the normal mic settings (When headphones/line-out used).
Obviously DO THIS AT YOUR OWN RISK. It's always a good idea to take a complete backup with perfect recovery (http://forum.xda-developers.com/showthread.php?t=1067490) before changing anything.
Edit: This mod is now included in the franco.kernel (forum.xda-developers.com/showthread.php?t=1166560). You can just flash that kernel. Below are the old instructions.
Installation (in linux)
Note the attached boot.img contains the ramdisk of the Finnish operator Saunalahti. It seems to contain some wifi modules too, so it's better to create a new boot.img from your own boot.img (instructions below)
- Boot the phone in bootloader mode. (Hold down vol up and vol down and power on).
- In ubuntu the phone partitions are mounted automatically, you might have to mount them manually in some other distros.
- Find the phone's partition which contains the "image" directory. Go to the image directory.
- There should be a file called "boot.img". Take a backup of the original and replace it with the attached boot.img.
- Unmount all the phone's partitions
- Remove battery to exit bootloader mode.
- Put battery back and boot
- Now the internal mic should work with headphones without mic or for example when connected to a car stereo.
Updating your own boot.img
- Get abootimg source from http://gitorious.org/ac100/abootimg. (I couldn't find a compiled binary for ubuntu, except an old version 0.3).
- I had to install package libblkid-dev to build it. It probably also needs other packages too, but I had them already installed.
- Build it:
Code:
make
- After make finishes you should have the built binary "abootimg".
- Extract the attached kernel.zip (Contains zImage, the built kernel)
- The next command updates the boot.img, so copy your original to boot.img.orig for example.
- Update the boot.img file:
Code:
[path to the abootimg you built]abootimg -u [boot.img from your phone] -k [zImage from kernel.zip]
- Now you can use this updated boot.img on your phone following the instructions above.
Details
As Piron said I think the root of the problem is in the construction of 3.5mm socket so that it doesn't headphones correctly. However I tried to force the detection so that it always detects headphones instead of headset. But that didn't work. The libaudio etc probably have some bugs with the headphone mode (it's never been tested since the phone never detects headphones .
This mod forces the use of the int. mic instead of the headset mic. Obviously with this modified kernel you can't use a headset's mic if you want to.
The modified msm7x30.c is in the attached zip.
It's been quite an adventure but it's rewarding to finally get it to work
I already tested it in my car with background noise etc and it worked perfectly (I heard the other person via the car speakers and he heard me). Also there was no echo which is surprising. The phone's mic is probably directional or something. It's a good mic
Post here if it works for you or if you have problems with the mod.

stockwell said:
What I meant was that we don't have the libaudio source from Huawei, but we can use another source (Qualcomm/Kali/etc) for libaudio and then we need to change the kernel driver to suit it (which we can model from Kali's kernel drivers).
Click to expand...
Click to collapse
Ahh, I see. Yeah now I understand.
I'll see if I can get the kernel driver modded so that it doesn't disable the internal mic. Ofcourse this would mean that the internal mic is never disabled (the kernel driver doesn't know why the int. mic is being disabled.) So it wouldn't be disabled even when using bt headset etc.. If I have understood correctly. A better way to fix it would be from the libX side. But let's see first how my kernel mod goes
Click to expand...
Click to collapse
Now the headset mic is "replaced" with the phone's mic, so BT etc should work fine.
I tried to find the file from where the msm7x30.c functions are called from. I couldn't find anything from the kernel or from the android git source. Probably because I'm not really a C guru. If we could find the place from where the msm7x30 kernel driver is told to use headset mic etc, it could be also fixed from there. This would be better because then there could be a setting "force internal mic instead of headset mic" or something.
But the current kernel mod works for me. I might look more into this later.
If anyone figures out where the msm7x30.c functions are called from it should also be possible to fix the issue from that side. Or I mean have a setting for forcing the int. mic..

good job~~!

is there anyway to get this fix in an app version for those of us without a rooted phone? thanks.

m2hartman said:
is there anyway to get this fix in an app version for those of us without a rooted phone? thanks.
Click to expand...
Click to collapse
I haven't found a way (yet). It might be possible by calling some method from the internal android libs (something like I tried earlier in this thread) the set available method didn't seem to work correctly. For some reason setting headphones available routes output to speaker, and setting headset output available disabled the internal mic etc..
I might look more into this later, but I don't have time now. If anyone else wants to try I can give some pointers.
Sent from my u8800 using XDA App

Worked like a charm, great work
Edit: It seems that i have a huge battery drain and the wifi is not working after modding the file and the lower part of the device seems to be hotter than the rest. Had to go back to default boot.omg Any ideas?
If you could write a how to replace only the msm7x30.c file of the boot image, maybe could solve the problem?

Add1cteD said:
Worked like a charm, great work
Edit: It seems that i have a huge battery drain and the wifi is not working after modding the file and the lower part of the device seems to be hotter than the rest. Had to go back to default boot.omg Any ideas?
If you could write a how to replace only the msm7x30.c file of the boot image, maybe could solve the problem?
Click to expand...
Click to collapse
The msm7x30.c has to be replaced in the kernel source (http://www.huaweidevice.com/tcpsdow...achmentName=kernel-2.6.32-U8800-Froyo.tar.zip). The boot.img contains the built kernel with only the msm7x30.c changed. I changed some other files while looking for the problem, but I put back the original files before building the kernel I attached here. I can build it again tonight with only the msm7x30.c changed and see if that makes any difference, if I forgot to revert some files.
I've also had some problems with WiFi, but I also had some before my kernel mod. It's possible that the kernel source from huaweidevice.com is different than the one you had on your phone originally. I think Huawei hasn't released the sources for all the different kernel versions out there.
BTW. Are you using Go launcher EX? I just realized after the latest update that it kept hogging the CPU (would cause battery drainage, slow down the phone and heating). I had to kill it once, now it seems to work ok again.

Related

Guide and tips for getting and using A2DP

It seems I am not the only one that have had "some pains" when using A2DP (="Stereo Bluetooth" / "Wireless Stereo"-bluetooth profile).
I thought I write down some tips for getting A2DP to work, and how to minimize the issues people are having...and hopefully others will fill in their tips...and maybe even prove me wrong (I have been wrong before...but what are the odds of that happening TWICE!?" ) on some points?
1. Challenge is getting a headset that supports A2DP, and works well with the Universal
I have had a pair of HP stereo headphones (these are only for music, does not have a microphone), a set of Motorola HT820 and a pair of i-Tech BluePRO. There are probably 20-30 other options as we speak (among other from Ericsson, Nokia, etc).
All the 3 ones I had worked with the Universal using A2DP to listen to music. Here are the PRO's and CON's for each of them from my point of view.
HP Stereo Headphones (same as Logitechs iPod BT headphones)
+ Clear and nice sound.
+ For "over the ear"-headphones, they were comfortable.
- Seems to be fairly sensitive for stuttering/lag/gaps when used for A2DP...at least is MY headset like that!
- Poor batterycapasity (approx 8 hours)
- Not an mini-usb plug (since the JasJar use mini-USB...less cables to bring)
- lacks a little bass wise (at least compared to the i-Techs)
i-Tech BluePRO
+ Seems to have fairly little prob with "lag/suttering" (my specific headset has almost no issues with it at least!)
+ Great bass (a BIG plus for me...I love techno-music
+ Great batterylife (approx 20 hours, and even more if you buy a 2500mah rechargable AA battery)
+ Can play very loud...if you want to that is (actually louder than my wired Koss headphones)
+ Uses 1 AA battery (I felt this was a CON first, but now that I have bought some 2500mah rechargable AA batteries, this actually is a "pro")
- "fuzzy" sound (compared to HP and Motorola HT820, the sound is slighty "fuzzy"...I noticed it when I swapped from Motorola to these, but have not noticed afterwards...so for HiFi people it might be a big CON, for me it was not).
- Reconnect not as expected (will not automatically reconnect to Universal when it is turned off and then on again)
- not very good for phonecalls (people are sometimes complaining it is hard to hear me)
Motorola HT820
+ Clear and nice sound.
+ Great microphone (people on other end say I am crystal clear, even when I walk outside)
+ Good batterylife (15 hours I think)
+ Charges over MiniUSB (hurrah, can use the Universal sync/charge cable)
+ Reconnects as expected (if you turn on the headset it will automatically reconnect with Universal)
- Seems to be fairly sensitive for stuttering/lag/gaps when used for A2DP (not an issue with phonecalls it seems)...at least is MY headset like that!
- ucomfortable to wear over time (after around two hours, they "hurt the ears", due to the way they hang over the ears...might be my ears though
- lacks a little bass wise (at least compared to the i-Techs)
I think that just about any person would chose the Motorola's over the i-Tech's anytime.
...but I am not everyone...so I personally use the i-Tech...and that is ONLY because of the "heavy bass", "loud soundlevel" and "closed earmuffs"...since that means I can listen to music/podcasts in even noisy environments and get what I define as "good sound" (="lots and lots of bass"
[UPDATE 1. august 2006]
I used my Motorola's again when I was on vacation (have used only the iTechs for several months now), and suddenly had a lot of lag/stuttering again...an issue I thought I had resolved with registryfixes and new ROM's.
...but "suddenly" I could not walk around with my headset and listen to "gapless music in stereo"...I could not do a workout at the gym with them, even when the Universal was 2-3 meters away from me...I would get gaps/lags once every minute or so.
With my iTech's this problem is almost non-existent. ...I wrongly thought this issue was fixed on the Universal-side, with the latest ROM's I installed, so forth...but it seems that at least "part of the problem" was the headsets themselves (my Motorola HT820's and my HP headset seems a quite a bit worse off in this regard than my iTech's).
My conlusion...test before you buy, since the headsets ALSO can influence the amount of lag/stuttering you get (as this was not complex enough as it was)!!!!
I am "happy" with my iTechs...but wish they automatically reconnected to Universal when I turn them on...and wish they were as good as the Motorola's for phonecalls.
[END OF UPDATE 1. august 2006]
2. Get a ROM which supports A2DP
This should not be to hard today, you can for example install the latest QTEK ROM (I use the WWE/english ROM, not sure of status on the other versions). Jwright (a user on this forum) have made a custom ROM which also contains A2DP and PushMail, and I know there are quite a few other "official ROM's" with A2DP...but I do not have that overview.
I do not have a QTEK 9000 myself, but actually a "Norwegian i-Mate JasJar"...but I was able to install the QTEK ROM, and U should be able to do it too, regardsless of version of Universal you have. ...it might be a rough ride though, you might need to search these forum and read up on the Wiki pages on how to get around "DeviceID" and "CountryID" issues...but is IS solveable (later I might update this with some direct links to some of those guides posts).
[UPDATE 14.06.2006, tip from "cktlcmd"]
The following are the ROMs with A2DP and AKU2 support (Battery icon replaced Time):
****QTEK ROM (latest ROM)
****T-Mobile NL (latest ROM)
****JWright's Modified ROM (latest ROM)
The following is the only ROM with A2DP support (No AKU2) but with the Time icon still showing:
****JWright's Modified I-Mate ROM (1st test released ROM)
You can find a lot of different ROM installation files here; ftp://xda:[email protected]/Universal/Shipped_Complete_Updates/
PS!
If You have an AKU2 ROM (the ones with PushMail), and do not have A2DP, you can add it with a patch originally made for the HTC Tornado. I have tried this myself with an Norwegian iMate AKU2 ROM that did not have A2DP...and it worked!
It should work on other Windows Mobile 5 devices also (as long as they have AKU2). Then you do not have to reinstall your device from scratch...with all the work that usually involves (in getting everything back to exactly you like it).
You can read about it, and download file from here; http://forum.xda-developers.com/viewtopic.php?t=48491&highlight=tornado+a2dp+patch
So how do I know if I have A2DP or not
When you have bonded with your A2DP-able headset, you should under "Bluetooth Setttings", under the tab "Devices", among other see your headset (for me this is listed as; "i.Tech BluePRO").
If you tap-and-hold this, you will get a context-menu that should contain "Set as Wireless Stereo", if you see that text, you have A2DP. I see for example the following;
Edit
Delete
Set as Hands-free
Set as Wireless Stereo
If anyone reading this know a better/easier way to verify if one has A2DP, feel free to tell me/us...so it is easier for people to check this!
3. Choosing a musicplayer to use on the Universal with A2DP
OK, you have A2DP setup, you have a headset...which musicsoftware should/can you use.
In teory, you should be able to use whatever music software you use today, TCPMP, PocketMusic, MortPlayer, Windows Media Player, so forth. Cause all sounds is sent to the headset (but strangely MortPlayer struggles at least). But you might have problems with AVRCP (AVRCP bluetooth profile, makes it possible to change tracks and play/pause/resume the music from buttons on the headset...very convienient when the Universal is in the rugsack for example).
MortPlayer (exellent player...but A2DP-vise...unfortunately...no)
http://www.sto-helit.de/modules/wmpdownloads/viewcat.php?cid=4
I have always before used a musicplayer called MortPlayer.
The reason for using that one, was that it is incredebly tuned for "doing everything without taking out the stylus" (big buttons everywhere), and that it has an insane amount of options (you can for example set it to always start with a specific voulme, start playing the last song you heard, at the position in the song you left it, and when you quit the sound is set back to what it was before starting it. You can even tell it that a specific folder is "soundbooks", and then it will always remember last listened position of all files in it).
But with A2DP MortPlayer unfortunately does not work well, I get only sound on the left speaker, and the AVRCP buttons do not work. So MortPlayer I must unfortunately leave for now! :-(
Windows Media Player (works...but I "hate" it
You can of course use the built in Windows Media Player. It works with A2DP, and it support AVRCP. There is two (and in my eyes BIG such ones) problems with WMP.
One reason is that is is unbelievably painfull to use in daily use...every time you start it, it "forgets" where you left off the last time, and you have to choose "Storage Card" (it seems to choose "Main Memmory" as default library on startup?), then find the album or playlist and play it...and the areas to click on the screen to do all this requires the stylus (or a "precision finger".
Another reason, is that the play/pause/resume button is not working 100% for all headsets (my HP headset seem to work fine, the iTech and Motorola seems to only work once, then I have to click the next time on the Universal, and then it will work one again...not much use in realworld scenarios).
One big bonus with WMP is that it is already installed, and AVRCP and A2DP works "out of the box", nothing you have to do.
PocketMusic (great, AVRCP works flawlessly)
http://www.pocketmind.com/pocketmusic.htm
This is in my eyes a very good musicplayer for "the go", much like MortPlayer (even though I think MortPlayer is better...with a wired headset that is). It can be set up so that it contines exactly at the same point in the same song as you quit it the day before, and look and behold, AVRCP work with it...and not just that...here the play/pause/resume button works flawlessly (which it does not for WMP for some headsets it seems)...at least with all my 3 headsets.
I now use PocketMusic. The minus with it is that it costs money, but it is well worth it (for me at least). And you can test/use it for free for 15 days or something like that, so you can "test before you buy".
TCPMP (works, at least sound vise)
http://tcpmp.corecodec.org/download
I do not use TCPMP (I use it for video, were I believe it is THE player to use...but not for music...too much fidling with the stylus in my view, but that's just my opinion), so I can not say tomuch about it...but I tested and the sound worked at least over A2DP. I did not get the AVRCP buttons to work...but I have seen some people saying "on the web" that it is possible to use...but I do not "how".
4. Stuttering/lag when using A2DP
A2DP works great...but there is at least one issue that can put most people off, and that is that you can get some stuttering/lag in the sound. This can feel like this; You listen to your music, all is great, and suddenly there is no sound at all for a second or so, and suddenly the music continues, and then it is silent, and then it plays again. Sometimes you get one of these, and no problems for hours, and other extreemes can be that the twice every second the sound disapears and appears all the time, until you give up, curse the "damn A2DP", and in best case puts your headphones hard on the table.
REASON 1: Universal is strugling (CPU/RAM)
One reason for stuttering can be that the JasJar is struggling performance vise. To help with this you can do the following;
1. Install "A2DP priority patch"
This is done by adding a value to the registy of your Universal, you can manually enter the registry value, or use a CAB-file or a REG-file someone has prepared.
http://forum.xda-developers.com/viewtopic.php?t=46811&highlight=a2dp+lag+patch
2. Kill background programs (or do a soft reset)
When you get this problem, it can also be because of some program working in the background.
But as we all know...there is some rare moments when our PDA's/phones' just seem to be living its own life. I have had occations when there is no programs running, and the phone stills is incredible sluggish, and I can see the menus getting drawen painfully slow. ...and of course, if your PDA gets one of those "I-do-not-want-to-coperate"-moments, A2DP or your music player will struggle...but then it really is not an A2DP issue, since you most likely would have had the same problem with a wired headset.
REASON 2: Radio connection is disturbed (object obstructing signal, WiFi nearby, so forth)
It seems that the connection can be very sensitive for obstructions (between Universal and headset). For example, if I have the Universal in a pocket in my pants, while walking around...I can sometimes get lag/stuttering all the time. If I put it in my rugsack, it stutters very rearly...and if I hold it still in my hand in front of me (OK, you look very stupid doing this, it will not stutter at all.
But if I put it on the table, and walk around the room, and even walk into another room, and will be around 10 meters away, it might not stutter. So I assume it depends of what kind of material is between the Universal and headset, and also the amount of it...but also it will depend on the "general amount of radio disturbance" in that area (an area with a lot of WiFi equipment/Bluetooth signals might be a lot worse that an area with little or no such equipment).
In general for me, I have practically no problems when I walk around with it in my rugsack, and generally have a little (and sometimes a lot of) stuttering when I have my universal in my pant-pockets.
I also have no disturbance at home or at the Gym (as long as I have the Universal around 8-12 meters away from me), but at work (Telecom company with lot of radiotransmitters around) it works at best 3-4 meters maybe. All of this without obstructions.
"Hearing the root-cause"
If you have done all this, and still get stuttering, here is a tip for understanding WHERE the issue is. It seems that you actually can hear if it is an "Universal struggling"-issue, or an "radio-disturbance" issue...
If the sound is continuing exactly where it left of, when it stopped...then it is the Universal that is struggling. Meaning, if you hear a podcast and they say; "The president of...[silence]...the united states of America, Bush said today...", then it is the Universal that is struggling, and you could try to close some programs a soft reset or similar.
If the sound does not continue exactly where it left of, like; "The president of...[silence]...Bush said today", then it is an issue with radio disturbance in some form.
...and with this knowledge, you hopefully will be able to resolve it.
Hope this extreeemly long post will be usefull for someone, feel free to comment/correct/add info and experiences...so that "A2DP newbies" get an easier start than us!
Excellent post, just what I need to know as I have just ordered the Motorola HS820.
Two questions - am I correct in thinking that the latest official UK O2 XDA Exec Rom does not include the a2dp profile?
And if so, which ROM should I go for - I don't need push email, and I want as little branding as possible.
Thanks.
Hi Pantaloonie,
I do not know if "latest official UK O2 XDA Exec ROM" have A2DP, hopefully someone else reading this will know and respond.
There is a lot of official ROM out there (ftp://xda:[email protected]/Universal/Shipped_Complete_Updates), but the only two english ROM's that I know for certain that have A2DP is (but I think there are more now);
Jwrights customized ROM (I have not gotten hold of this)
QTEK WWE ROM (ftp://xda:[email protected]_WWE_13077_130176_10900_WWE_Ship_GR2.0.1.exe
)
[WARNING] It seems that my link above is NOT to the ENGLISH version, but to a GREEK version of the ROM!!!!
I will try out myself at home, and change the link to the correct ROM...but can't do this at work...
And if you want to have minimal operator customization, I think the QTEK ROM's are fairly basic ones. And in worst case you can softreset when the installation starts installing all the apps from ExtendedROM when you do an installation of the ROM. But then you will also often miss some utillities that you actually want to use.
Another alternative is to "cook your own ROM" (I did this for my old Qtek9090), but then you can expect to spend a day or two reading up on this forum, downloading the tools for doing this, and creating you own ExtendedRom. If I get hold of Jwrights customized ROM, I will update my post here though.
Excellent post!
The following are the ROMs with A2DP and AKU2 support (Battery icon replaced Time):
****QTEK ROM (latest ROM)
****T-Mobile NL (latest ROM)
****JWright's Modified ROM (latest ROM)
The following is the only ROM with A2DP support (No AKU2) but with the Time icon still showing:
****JWright's Modified I-Mate ROM (1st test released ROM)
Excellent post dude...you just saved me a ton load of internet research...you should do this more often...keep up the good work
cktlcmd, thanks for the great input!!!
Have added it to my original post, so that others reading this post, don't have to scan through all comments...not a problem right now...but might be harder when more people start giving tips and comments!
Pantaloonie, cktlcmd and youmeus, thanks for the positive feedback! Hopefully at lot of other will fill this with more experiences and tips! ...and I will try to summarize all tips into my original post, so that it is as up-to-date as possible!
This topic is under the Universal category, however everything listed in the initial post should be applicable to any device trying to get A2DP to work cleanly.
However, I believe there are several of us that have tried each of the suggested solutions and it still hasn't resolved the lagging issues. I'd be interested in learning about any debugging tools that could be used to figure out the root cause. Are there any kind of system tracing tools available or even a tool that could list process/thread and device driver priorities that could provide some clues. Is there some way we can determine if it's cpu limited, bandwidth limited (cpu to bt i/o?), interrupt related, etc.
I would also be interested in figuring out if there are any tweeks that can be applied to the bta2dp.dll driver other than setting the priority. For example what is the Flags parameter in the registry used for? It's currently set to 65538 on my device. Could it be a buffer size? A baud rate? Anyone know?
It seems to me if we figure out the root cause then it could even help people where A2DP is working so-so, but only if they close all apps, overclock, etc. To me doing these things is just a workaround until we figure out the real issue.
HS820 aren't stereo. HT820 Are... Great post otherwise
Aah...one can very easily use the Tornado A2Dp posted in the prophet section with any of the AKU2 ROMs...I hv successfully used with Nokia HS 12W...with FM..it works...really works
hdubli, are you saying that it actually works with Universal also? Do you have a direct link to the file in that case, so others easily find the correct file.
ady, thanks will correct post, HT820 it is, I remembered it was someting with "820" at least!
hannip, I put it under Universal since I only had experience with Universal in this regard, and also the ROM's...but if I get some tip/help/assistance from others... ;-)
hannip, I seem to have almost no problems anymore, and most of the times I have had lag/stuttering, it seems to have been "radio disturbance" that have been the problem...now I have learned when it work and when it doesn't, and have very seldom any problems. for example having JasJar in rugsack when I walk, and not in frontpocket of pants. ...and due to the size of JasJar you need a rugsack anyway!
That said, I agree it certainly wouldn't hurt to understand more about root-causes.
Will try to find out name of a app I used a year ago, which showed CPU utillation, memmory and processes.
I must quit now, my girlfriend complains about the irritating clicking from the keys of my JasJar here...
Hannip,
Searched for a tool (and tested all I found) you asked for...here is results...
Performance Monitor (does NOT work on WM5...made for Casio E-10x...veeery long time ago I had one
http://www.thumbsupsoft.com/maphtm/pemon.html
Downloaded, installed it on JasJar. Starts up, but only shows ProgramMemory and MainMemory, but no graph, nor any threads)...and does not completely uninstall either!
MemMaid 1.6 (Works on WM5)
http://www.dinarsoft.com/
I have this myself, is not really an monitoring app, but it also can show all running processes (not programs, like built in simmilar program for this) and their memmory usage. On my JasJar when builtin app shows 1 running app (MemMaid), MemMaid shows 17 running processes (and that they take up approx 22MB!).
Great app...but gives no info about CPU utilization unfortunately.
PMH TaskManager (does NOT work on WM5)
http://www.phm.lu/products/PocketPC/TaskMgr/
This one looked really promissing; "Display the running processes with their IDs, number of threads, CPU time, priority and complete path...".
But also is an PocketPC 2002 app, and on the JasJar it only shows process name...no info on CPU time, priority, so forth! :-(
SuperTasks 2.0 (YEEES, it works...and do what we want!!!)
http://www.pocketgear.com/software_detail.asp?id=14661
This one shows CPU time pr process, and a graph for total CPU usage (among other), much like task manager om your PC (if you're one of the Windows-people that is.
It has a 30 day trial, so you should be able to test a lot before deciding to buy or not.
Did an "unscientific" test using SuperTask.
I had no other applications running, started after soft reset all times (but of course WindowsMobile will run some background tasks, but since I soft reset each time it should be at least simmilar for all tests). I played same MP3 track that is encoded with 192 Kbps.
Here is the results;
PocketMusic with A2DP
40-45% CPU
PocketMusic without A2DP
20-25% CPU
WindowsMediaPlayer with A2DP
35-40% CPU
WindowsMediaPlayer without A2DP
15-20% CPU
So A2DP (if we trust this "unscientific test"!) takes approx 20% CPU, and WMP takes approx 10% less CPU than PocketMusic (but I still prefer PocketMusic due to usabillity issues).
And this seems to fit with my experiences with A2DP on my JasJar...I seldom have problems with my JasJar outputting...it is a problem normally with BT signal/connection between JasJar and headset...and that is reduced by keeping them close, few/little objects between them.
...but then again...other people might have more CPU intensive apps running on the Universal than me, and therefore get a problem due to the approx 20% CPU usage of A2DP.
UPDATE: Made a seperate post for the test with more info...here http://forum.xda-developers.com/viewtopic.php?t=53717
I got this from the wizard forum. Apparently there is a free task manager which works on universal as well and shows plenty of info. Can't find the thread though
ady said:
I got this from the wizard forum. Apparently there is a free task manager which works on universal as well and shows plenty of info. Can't find the thread though
Click to expand...
Click to collapse
Thanks, that's a pretty cool app, however the cpu utilization doesn't seem to work for all apps. With PocketMusic playing it shows 0 % cpu for that process. It claims my Idle is 90% with PocketMusic over A2DP. That just can't be correct. Gonna try SuperTasks next.
Using SuperTasks I see the following stats
PocketMusic w/A2DP 15-25% cpu
services.exe 4-6% cpu
device.exe 5-15% cpu
everything else was 0.
So cpu-wise the device doesn't seem to be stressed. What I am hearing is from 2 to 15 seconds of music that gets paused for about a second before it continues. When it continues it sounds like the music is sped up for a moment as if it were trying to catch up.
It's almost like some kind of flow control start and stops. I've tested this in a wireless free area so I don't think it's interference related.
Neither one of these tools show priorities from what I could see. I'm still looking for something that can show process/threads and service priorities.
Mmm how do you get Pocketmusic and AVRCP to work?
I cant get it to work at all......WMP works fine with my HT820's but not with Pocketmusic.
DaveUK said:
Mmm how do you get Pocketmusic and AVRCP to work?
I cant get it to work at all......WMP works fine with my HT820's but not with Pocketmusic.
Click to expand...
Click to collapse
What version are you using? Try the latest one.
http://www.pocketmind.com/files/pmusic.zip
Note that you should disable gapless playback if you experience hangs when switching tracks.
hannip said:
So cpu-wise the device doesn't seem to be stressed. What I am hearing is from 2 to 15 seconds of music that gets paused for about a second before it continues. When it continues it sounds like the music is sped up for a moment as if it were trying to catch up.
It's almost like some kind of flow control start and stops. I've tested this in a wireless free area so I don't think it's interference related.
Click to expand...
Click to collapse
I agree that this does not sound like "interference related". I think that when you have "interference"/"BT signal" issues, you will just loose some of the sound, while when it is JasJar issues it continues where it left of, or sometimes sound like it suddenly speeds up for a short while to catch up.
The behaviour you have here, I have not heard at all in at least a month, and I use A2DP a couple of hours every day...so it makes me wonder if there is something in the ROM that you have or some software on your JasJar that I don't have...!?
Maybe we should compare ROM versions, what services that are running in background of device, what apps we have installed currently, so forth? ...we probably won't find anything...but maybe worth a try!?
BTW
I DID have that issue a lot before though, and I don't really remember exactly WHEN I got rid of it, if it was manually entering the "A2DP lag patch", or if it was uninstalling some software...since I tried so many things in that period to resolve it...it just works pretty well now (except of course that it sometimes lags if there is to much obstructions between headset/JasJar).
On sunday (first time I have chance to "play again" ), I will also test with my Motorola HT820's again...just to verify that it works just as well with those headphones as it does with my iTech headset. ...it would really surprise me if that has had an effect...but I do not remember when it started to work fine...and "desperate people try desperate things"!
hannip said:
DaveUK said:
Note that you should disable gapless playback if you experience hangs when switching tracks.
Click to expand...
Click to collapse
Ahhhh thats the reson for those anoying delays!
Thanks!
Click to expand...
Click to collapse
For some reason the version I downloaded direct from their website was 4.03
The copy you sent works like a charm with AVRCP.
Thanks alot!!!!!!!!!!!
hannip said:
DaveUK said:
Mmm how do you get Pocketmusic and AVRCP to work?
I cant get it to work at all......WMP works fine with my HT820's but not with Pocketmusic.
Click to expand...
Click to collapse
What version are you using? Try the latest one.
http://www.pocketmind.com/files/pmusic.zip
Note that you should disable gapless playback if you experience hangs when switching tracks.
Click to expand...
Click to collapse

[Q] No sound coming

Hey Hi friends
I am using windows 8 Pro
As my Pc was Off from last 7 days after i switched on there is no sound coming from speakers i checked my speakers with external device there are working fine ,when i connected Headphones so there is also no sound coming i checked the Realtek drivers they are working properly and i tried to uninstall them and again install but no luck no sound i don't know whats happening so please help me
Thanks
Hitesh2626
Dam waiting for your reply
Hey please somebody help
First of all, this is not a tech support forum. There are places for that. People here will usually try to be helpful, but you should have no particular expectation that we are going to take time out to fix your problem. Nobody is obligated to help, nor are you entitled to such assistance. Help comes when we feel like it.
Which brings me to the second point: don't bump your own thread like that, certainly not within 24 hours. I read nearly every unread thread each time I check this site, and this is not a high-volume list; your message hadn't gone anywhere. Please read rule (http://forum.xda-developers.com/announcement.php?a=81) 16 (and the latter part of 5), and reflect on what the likely result of disrespecting them is going to be in terms of getting what you want. Hint: it's not good.
Since I'm here anyhow though, I'll point out two likely places for the problem to be:
1) You may have the wrong output device selected. This is particularly likely to be the case if the volume meter on your desktop appears to be working correctly. Right-click the the volume control and click on Playback Devices, and make sure it's not set to something silly and useless like an unconnected HDMI port. Choose the output you want and select "Set Default".
2) One or more of the Windows Services responsible for the sound system may be crashed/hung, turned off, or disabled. Go to Task Manager -> Services (or open Services from Start, or run services.msc) and make sure that the Windows Audio service (audiosrv) and Windows Audio Endpoint Builder service (audioendpointbuilder) are enabled, Startup Type=Automatic, and running. You can try re-starting them if you think there's a problem.
3) A freebie: aside from the obvious and ever-valid advice to try rebooting the computer, Windows also has an audio troubleshooter built in. Open Start, type "play audio" (no quotes), and look under Settings; there should be an item at the top about fixing playback issues. Try that.

[Q] What dash installation ROM?

Currently running timurs rom but it crashes a lot. Are there other roms that allow fast charge, sleep/wake with power, on screen volume etc.
Any help greatly appreciated
adamsilver1987 said:
Currently running timurs rom but it crashes a lot. Are there other roms that allow fast charge, sleep/wake with power, on screen volume etc.
Any help greatly appreciated
Click to expand...
Click to collapse
I've been running Timur's ROM as well and I really want an alternative as well as I've been facing issues with the ROM, and it looks like Timur has discontinued development on the 2012 model.
From what I've seen so far though CM11 should support USB DACs so I'm keen to try that out.
Some notes:
Fast charge - that's a kernel setting so any custom kernel should allow that.
Sleep/Wake on power - After many months of usage, sleep or even firm sleep has been a hit or miss for me. When it works, it works really well but sometimes a some random app might cause a wakelock, draining the battery. Even otherwise, there are many other issues such as USB audio doesn't resume. Plus the battery tends to drains quicker + looses health because of being in a hot car.
So instead, what I'm planning to do, is to just completely shutdown/boot up a tablet on power. Some notes:
- Bootup time is fairly quick - about 30 seconds, upto a minute, which is acceptable for me. You can reduce the startup time even further by using apps like BootManager to prevent unnecessary apps from starting up. Perhaps we can slim down the ROM further by deleting unnecessary apks etc.
- Fresh start is always a better option - you don't want your tablet to crash while driving right? I've had to reboot many times before or during driving, and it annoys me to say the least.
- USB audio always works fine when booted (well, with Timur's ROM anyways, need to test with CM11/others)
- No battery drain due to device standby or wakelocks
- No overheating and loss of battery health
- For shutdown on power loss, we can use Tasker. Maybe make a script to first turn the screen off, and after say 10 minutes of idle turn off the device completely (this will give us a chance to resume quickly in case we stopped the car for some reason).
- For startup on power, we can use the fastboot oem command to make the device automatically power up
On-Screen Volume: From daily usage, this hasn't been very practical in reality. I mean if you're driving, you really shouldn't be looking at the screen and trying to aim at the tiny buttons. Instead, a better option would be to use gestures to control the volume. There are heaps of apps for this, eg: All In One Gestures, Tasker, Gesture Navigation, GMD GestureControl, etc. You could use a single-swipe down and swipe-up to increase the volume up/down. Swipe left/right to change tracks. Two finger swipes to switch between apps. Just use your imagniation.
Might seem like a lot of work initially, but IMHO it'll be worth it, at least to get a stable ROM which is updated regularly (not to mention, you get to use the newest GApps!).
My only concern is to get the DAC working on startup. Might have to look into Timur's startup scripts to see how he does it - maybe even port the FHD scripts over to 2012 if necessary.
do you have a link to any fast charge kernels ? all i can find is Timurs ?
thanks
adamsilver1987 said:
do you have a link to any fast charge kernels ? all i can find is Timurs ?
thanks
Click to expand...
Click to collapse
Kang-aroo kernel.
http://forum.xda-developers.com/showthread.php?t=2558717
Supports fastcharge, OTG, hotplug DAC, firm sleep, multiboot and more.
thanks. this may sounds stupid ( im new to this rooting thing etc ) i am running paranoidandroid ROM. seems to run smoothly. i have flashed/installed that kernel and nothing is different. no extra settings etc? am i doing something wrong ?
thanks again
adamsilver1987 said:
thanks. this may sounds stupid ( im new to this rooting thing etc ) i am running paranoidandroid ROM. seems to run smoothly. i have flashed/installed that kernel and nothing is different. no extra settings etc? am i doing something wrong ?
thanks again
Click to expand...
Click to collapse
Use a kernel tweaking app, like TricksterMod.
ok downloaded that and it means nothing to me im afraid. how would i turn on fast charge for example or OTG host mode, firm sleep etc ?
only thing i can find where i assume you can set things is the " SysCtrl Editor" but it jsut comes up with a huge list of stuff that i have no idea about.
i assume i need to find fast charge in sysctrl and change it from 0 to 1... but cant find anything under the search. not a clue what id be looking for
starting to think Timurs rom was simple compared to this. haha
thanks for the help
Use PowerEventManager:
http://forum.xda-developers.com/showthread.php?p=50265682#post50265682
i saw that, but yet again. dont know how to use it ? where do i place it on the tablet. it doesnt show up in recovery mode
You have to install it. Copy it to your device and then use a file manager to open and install it. It will create an icon in your drawer. When you open it, you'll have options to configure firm-sleep etc.
Done. Worked at first but now I've reverted to timurs rom. The tablet froze loads. Wouldnt open some apps at all and power on/off with ignition wasn't reliable. Sometimes it woke, sometimes it didnt. Will give it another go when i habe more time i think.
On a related note, I haven't had much luck with getting my DAC to work with other ROMs - even with Kang-aroo kernel. I'll have to try CM11 with _crue_'s USB audio patches and Netfluke's kernel this weekend and see how it goes.
Edit: No luck. Maybe because it's I'm on tilapia. Even with cm11, Netfluke's latest kernel, and _crue_'s updated audio patches for cm11, couldn't get it to work. And it's a Fiio E17, which I've had no issues with on Timur's ROM.
And no, I'm not going back to Timur's CM10 - it's old. I can't use any of the newer GApps on it, and the ROM is buggy.
I think I'll swap my tilapia with my 2013 deb and use that as a car device instead. It looks like Timur just updated his kernel to v1.0 which fixes a lot of bugs - at least it's being actively developed. As for my tilapia, I'll switch to a more stable/mainstream ROM like Omni and forget about USB audio for now.
Where did u get timurs updated kernel? Cant find a link
adamsilver1987 said:
Where did u get timurs updated kernel? Cant find a link
Click to expand...
Click to collapse
Oh, you'll have to donate for now, but it should be made public soon.
How much and where?
Thanks

XT1572 Microphone in calls and charging problem.

I posted my problem in few topics about MY mic problem, but nobody responded, so making my own thread to get visible.
About 5 months ago, my microUSB port was damaged, and it was replaced 2 times in local service.
Motorola refused to repair my device, due to unlocked bootloader.
Now my phone charges only when I plug the cable, and reboot it. No quickcharge since this time, also no connection with pc (only adb via fastboot works).
I was forwarded to other "specialised" service points, because there was needed a special soldering iron (whatever it means) that is extremely costly.
So far any service that had that soldering iron I called refused to do the repair (I think the easiest would b to change motherboard, cannot afford this due to costs)
Both problems appear on ANY (even stock) ROM I've tried so far, I tried nearly every single one from XDA.
Some roms allow to bypass the mic issue, by simply turning the speaker mode on (then the other side hear me, not perfectly but I'm able to talk with them, when speaking loud).
To fix mic I tried everything that I found so far:
-Changes in build.prop for the echo cancellation/noise reduction
-Cleaning the mic hole
-Changes in audio_platform_info.xml file (which contains the input/output devices list)
-Setting permissions for dialer/audio effects app
-Change to a different dialer app
-Disable audio effects app
-Various different stuff like service menu settings (*#*# etc)
-Reflash everything using CORRECT device images (5.1.1, 6.0, 6.0.1)
-Use different kernels
-Other things I forgot due to "fix attempts" ammount
The mic itself WORKS - checked it, by using some call recorder app and service test menu (not on the speakermode ofc).
Everything I say is CLEAR TO HEAR on the playback, just the call receiver cannot hear me. Where is the devil hidden?
Here are my Phone app on stock 6.0.1 latest update permissions that I use right now:
I will try anything, just to make it work like it should.
A note to the usb connection and fastcharge - there is a 24/7 running wakelock from the USB 3.0 controller (at least this is what I found it to be) called f9200000.ssusb, dunno how to trace the process responsible for it, I'm not THAT DEEP into android to figure it out on my own, it propably causes the problem (that's why turned on device doesn't respond for connecting the cable, nor to the PC/1A charger/2A quickcharger [aukey one], I've still got to reboot my phone or turn it off, to start charging my device).
I'm able to flash anything in fastboot mode, works without problems.
Upon trying to charge my moto with quickcharger, Ampere shows that the TurboCharger is connected, then after 2-3s charging stops and starts again, looped forever resulting in no charge at all. Only 1A chargers works.
Screenshot of the wakelock:
Thank everyone for reading this, awaiting for ANY tip, I'm struggled with those 2 probs for already 5-6 months, and I've read all the over 100 pages of Q&A without finding the solution, I've finally decided to post it on my own.
Are you still having problems with the Mic?
Mic problem won't go away affecting xt1575
Mycroftski said:
Mic problem won't go away affecting xt1575
Click to expand...
Click to collapse
Here are two things that were done to over come my problem, first thing was to clean/open-up the speaker hole that's on the back of the phone (odd place), I also turned off "Enhanced 4G LTE Mode".
Also remember since the mic is on the backside, flip the phone over when using this feature so you're not blocking the mic hole, because it's very tiny.
These steps worked for me but your problems may be different.

Nexus 7 To Replace Head Unit

Good afternoon,
So after seeing a bunch of videos and out of boredom I ordered almost all the pieces to make the switch. Was amazed by how simple it was until I noticed that the OTG cable was not supported by the Nexus 7? And that to my understanding I would have to root and install a custom rom in order to do this?
Well I did some research and found timurs rom and installed it. Well noticed gapps wasn't installed. Went to install gapps then I spent an entire Saturday trying to get it to work with no avail. I'm not skilled in this line of work. Alot of the articles I'm finding are from 2012 -14.
Just wanna make sure I'm making the right steps not sure if there has been a new way of doing this or possibly an easier method? Would greatly appreciate it if someone could assist with this.
I would love to have GAPPS on which ever ROM will give me the requirements to install the Nexus as my head unit. Im just not entirely sure how to get it to work proplery. I apologize for my lack of knowledge in advance.
List of parts
-nexus 7 (wifi)
-radio harness
-otg
-usb hub
-dac (behringer UCA222)
As well as some other misc items such has a volume knob, just awaiting the Amplifier.
Thank you for your time, hopefully someone can help me with this :good:
So from what I've gathered Autodroid is the newest rom, just downloaded it. Will be giving it a shot tonight. If someone could help me with Google apps and installing it on there that would be awesome!!!
BlackenWkN7714 said:
So from what I've gathered Autodroid is the newest rom, just downloaded it. Will be giving it a shot tonight. If someone could help me with Google apps and installing it on there that would be awesome!!!
Click to expand...
Click to collapse
For Autodroid, look for Slim-Addons-mini_gapps.4.4.4.build.9-20150107.zip from Here.
I had issues with OTG+Charging with Autodroid, but the more i have been tweaking and trying different things, I think the high temperatures were what caused the tablet not to charge. Monitoring the battery, I have noticed when the temp is over say 110* F, it will not charge, but will hold the charge and not drain the battery. The lower the temp gets the faster it starts charging.
I would suggest not converting to F2FS if you plan to use OTG. I could not get it to work properly.
I'm currently running LineageOS 14.1 with Powereventmanager 1.8 installed. This has been working well for me the last week or so, but some issues have me wanting to go back to Autodroid. One issue i've noticed lately with LineageOS is the sound quality doesn't seem as good as Autodroid. It sounds decent for my factory system, but what bugs me is the volume control is not sensitive enough, its either way too loud or too quiet. There may be ways to fix this though, as i have not had time to research a fix. I dont run a DAC, I run my tablet via bluetooth to a headunit hid behind the tablet, so you may not have this issue.
Another issue i have is with PowerEventManager. It will put the tablet to deep sleep, but usually not the first time i turn the ignition off. I have to turn the ignition back on then off, then it will trigger powereventmanger. No big deal, but is a pain since i have to constantly make sure it does go to sleep.
You can also add the volume control buttons to the nav bar through the "buttons" setting. You can add media controls too. This works well for the most part, but there are times the icons disappear, though the control is still functional. I think this issue is caused by my icon size, but not 100% sure.
B|acknd said:
For Autodroid, look for Slim-Addons-mini_gapps.4.4.4.build.9-20150107.zip from Here.
I had issues with OTG+Charging with Autodroid, but the more i have been tweaking and trying different things, I think the high temperatures were what caused the tablet not to charge. Monitoring the battery, I have noticed when the temp is over say 110* F, it will not charge, but will hold the charge and not drain the battery. The lower the temp gets the faster it starts charging.
I would suggest not converting to F2FS if you plan to use OTG. I could not get it to work properly.
I'm currently running LineageOS 14.1 with Powereventmanager 1.8 installed. This has been working well for me the last week or so, but some issues have me wanting to go back to Autodroid. One issue i've noticed lately with LineageOS is the sound quality doesn't seem as good as Autodroid. It sounds decent for my factory system, but what bugs me is the volume control is not sensitive enough, its either way too loud or too quiet. There may be ways to fix this though, as i have not had time to research a fix. I dont run a DAC, I run my tablet via bluetooth to a headunit hid behind the tablet, so you may not have this issue.
Another issue i have is with PowerEventManager. It will put the tablet to deep sleep, but usually not the first time i turn the ignition off. I have to turn the ignition back on then off, then it will trigger powereventmanger. No big deal, but is a pain since i have to constantly make sure it does go to sleep.
You can also add the volume control buttons to the nav bar through the "buttons" setting. You can add media controls too. This works well for the most part, but there are times the icons disappear, though the control is still functional. I think this issue is caused by my icon size, but not 100% sure.
Click to expand...
Click to collapse
Hey thanks for the response!!
I ended up getting timurs rom to work. I attempted to go with Autodroid but it would never load up. Attempted timurs rom and it worked and figured I'd try gapps and finally it worked perfect and I have no issues now.
Now I'm trying to find the best method to incorporate Bluetooth to the car. I'm replacing my entire head unit with the tablet. I wanna be able to play music from my phone and have it come out of the cars speakers.
Any suggestion on that?
BlackenWkN7714 said:
Hey thanks for the response!!
I ended up getting timurs rom to work. I attempted to go with Autodroid but it would never load up. Attempted timurs rom and it worked and figured I'd try gapps and finally it worked perfect and I have no issues now.
Now I'm trying to find the best method to incorporate Bluetooth to the car. I'm replacing my entire head unit with the tablet. I wanna be able to play music from my phone and have it come out of the cars speakers.
Any suggestion on that?
Click to expand...
Click to collapse
Autodroid, you have to flash the kangaroo kernel after you flash the rom. there are people that say you have to flash a version of SlimKat and dirty flash Autodroid over it, but i never had to do this.
Check out HeadUnit Reloaded. it is an Android Auto clone. allows you to make a receive calls, stream music from your phone. There is a 5 minute trial, so make sure you have everything set up before you give it a try.
I've been debating on switching to a DAC, just so i can have better volume control. Something about using software buttons for control is just a pain. I've also thought of hard wiring my removable face from the head unit to somewhere it is accessible, but not sure i want to go through the trouble.
Have you thought of just using the phone as a hotspot and using your tablet for everything else? This is what i do and it saves me from having to fidget with my phone all the time.
Another tip for you, though i dont know what DPI Timurs rom is set at, but on AutoDroid I always increased the DPI to make things on screen larger and easier to control, since it is in a vehicle. I believe i had mine set at 230..
I'll be switching back to Autodroid this evening. the bugs i encounter using LineageOS have just been too much to deal with. Worked great for awhile, just need something more stable and worry free.
B|acknd said:
Autodroid, you have to flash the kangaroo kernel after you flash the rom. there are people that say you have to flash a version of SlimKat and dirty flash Autodroid over it, but i never had to do this.
Check out HeadUnit Reloaded. it is an Android Auto clone. allows you to make a receive calls, stream music from your phone. There is a 5 minute trial, so make sure you have everything set up before you give it a try.
I've been debating on switching to a DAC, just so i can have better volume control. Something about using software buttons for control is just a pain. I've also thought of hard wiring my removable face from the head unit to somewhere it is accessible, but not sure i want to go through the trouble.
Have you thought of just using the phone as a hotspot and using your tablet for everything else? This is what i do and it saves me from having to fidget with my phone all the time.
Another tip for you, though i dont know what DPI Timurs rom is set at, but on AutoDroid I always increased the DPI to make things on screen larger and easier to control, since it is in a vehicle. I believe i had mine set at 230..
I'll be switching back to Autodroid this evening. the bugs i encounter using LineageOS have just been too much to deal with. Worked great for awhile, just need something more stable and worry free.
Click to expand...
Click to collapse
I have thought about being able to supply a hot spot with my note 5. I found ways of getting around it without rooting it but those have seemed to be disabled. Still hoping to come across a simple way of doing it without paying for it or rooting the phone since I'm currently on the "lease program". I plan to keep the phone once I'm finished paying on it so I believe I should have an issue. I just don't wanna end up screwed if for some reason I have to turn it in and I get hit with a large fee since it's rooted.
I will definitely look into that app, can it be connected thru Bluetooth or just wifi? If wifi I will have to wait until I figure out how to make my phone wifi tethering enabled.
Also I though of an idea, I have found the Bluetooth devices for everyday car stereos. Box with usb to charge and an aux to plug into the car audio. My Dac has an input and an output. I'm currently not using the input since it's all thru usb. I'm wondering if I can hook up the $20 Bluetooth piece and then aquire a female 3.5 aux cable to make rca and hook that up to the input on the dac.
BlackenWkN7714 said:
I have thought about being able to supply a hot spot with my note 5. I found ways of getting around it without rooting it but those have seemed to be disabled. Still hoping to come across a simple way of doing it without paying for it or rooting the phone since I'm currently on the "lease program". I plan to keep the phone once I'm finished paying on it so I believe I should have an issue. I just don't wanna end up screwed if for some reason I have to turn it in and I get hit with a large fee since it's rooted.
I will definitely look into that app, can it be connected thru Bluetooth or just wifi? If wifi I will have to wait until I figure out how to make my phone wifi tethering enabled.
Also I though of an idea, I have found the Bluetooth devices for everyday car stereos. Box with usb to charge and an aux to plug into the car audio. My Dac has an input and an output. I'm currently not using the input since it's all thru usb. I'm wondering if I can hook up the $20 Bluetooth piece and then aquire a female 3.5 aux cable to make rca and hook that up to the input on the dac.
Click to expand...
Click to collapse
I'm not sure about Bluetooth with Headunit reloaded... you can use USB. To be able to make and receive calls, you have to have it connected to a "Bluetooth headset" according to their page, but i think this is just for phone calls.. I could be wrong though. I've been curious if my head unit would act as a "headset" since my tablet is connected through Bluetooth...
One day I will buy the app and play with it more, I'm just cheap
About your DAC, I dont see why that wouldn't work. I've read of people using stand alone Bluetooth adapters with their DAC. But like i said before I dont know anything first hand when it comes to DAC's.

Categories

Resources