Hello all. I am enjoying android on my Tilt 2. Thanks to all who have contributed.
I am fairly new to Android and have been having some issues. Although there are references to one of my issues elsewhere none of the posted suggestions have worked for me. I have installed and uninstalled over a dozen different Youtube .apk files and each one results in a force close upon opening the app. Has anyone had this issue on a Tilt2 and how did you fix it?
Secondly, I have seen reference to bluetooth working in some of the newer builds. Is it working on a Tilt2 in any build? When I try to turn on bluetooth it trys for several seconds but never actually turns on. If anyone has it working on a Tilt2 could you please explain how you got it working? Can I use a stereo bluetooth headset with it, if not is there anyway to use usb headphones?
I apologize if this is addressed elsewhere. I am sure there will be some people asking if i even searched. As i mentioned, I have seen references, but none seemed to be clear on what device they were using. (Rhod, Tilt2, TP2, etc..) Any help is greatly appreciated. Keep up the good work. Hopefully soon this will be an option for all-around everyday use on these devices.
Well BT doesn't really work... it'll pair, but it won't pass audio. At least that was my experience on my RAPH - haven't tested on my RHOD.
Youtube, never really tried that either... may need hw3d to work right. I heard that the 'low-quality' version of youtube works tho.
3.5mm headphone jack works - kinda. But currently to get it to work it breaks all other sound. I'm not sure if it works on the extUSB thing, but I'd imagine it would - you just set the snd.force to 1 (I set it to 2 for the 3.5mm jack) and boot Android while a call to voicemail is running - with some headphones plugged in. This does cause adverse effects - no sound other than the headphones, and I noticed funky noises coming out of the speaker when playing music thru the headphones...
lodogg9832 said:
Hello all. I am enjoying android on my Tilt 2. Thanks to all who have contributed.
I am fairly new to Android and have been having some issues. Although there are references to one of my issues elsewhere none of the posted suggestions have worked for me. I have installed and uninstalled over a dozen different Youtube .apk files and each one results in a force close upon opening the app. Has anyone had this issue on a Tilt2 and how did you fix it?
Secondly, I have seen reference to bluetooth working in some of the newer builds. Is it working on a Tilt2 in any build? When I try to turn on bluetooth it trys for several seconds but never actually turns on. If anyone has it working on a Tilt2 could you please explain how you got it working? Can I use a stereo bluetooth headset with it, if not is there anyway to use usb headphones?
I apologize if this is addressed elsewhere. I am sure there will be some people asking if i even searched. As i mentioned, I have seen references, but none seemed to be clear on what device they were using. (Rhod, Tilt2, TP2, etc..) Any help is greatly appreciated. Keep up the good work. Hopefully soon this will be an option for all-around everyday use on these devices.
Click to expand...
Click to collapse
I posted a working YouTube apk here (low quality mode only): http://forum.xda-developers.com/showthread.php?p=7954193&highlight=youtube#post7954193
BT doesn't currently work on the Rhodium. I assume it's because of the different BT stack that's used by our device. Besides that, while BT turns on for the Topaz & Raphael, audio doesn't pass properly, as was already mentioned. 3.5mm Headset doesn't work on the Tilt 2 through the ExtUSB (in fact, no audio passes through the adapter at all).
lodogg9832 said:
Hello all. I am enjoying android on my Tilt 2. Thanks to all who have contributed.
I am fairly new to Android and have been having some issues. Although there are references to one of my issues elsewhere none of the posted suggestions have worked for me. I have installed and uninstalled over a dozen different Youtube .apk files and each one results in a force close upon opening the app. Has anyone had this issue on a Tilt2 and how did you fix it?
Secondly, I have seen reference to bluetooth working in some of the newer builds. Is it working on a Tilt2 in any build? When I try to turn on bluetooth it trys for several seconds but never actually turns on. If anyone has it working on a Tilt2 could you please explain how you got it working? Can I use a stereo bluetooth headset with it, if not is there anyway to use usb headphones?
I apologize if this is addressed elsewhere. I am sure there will be some people asking if i even searched. As i mentioned, I have seen references, but none seemed to be clear on what device they were using. (Rhod, Tilt2, TP2, etc..) Any help is greatly appreciated. Keep up the good work. Hopefully soon this will be an option for all-around everyday use on these devices.
Click to expand...
Click to collapse
Don't know if you've figured this out yet or not, but I had the same youtube issue on my rooted LG ally. I've worked on it for over an hour now, and finally got a solution.
Download Titanium Backup from android market. Go to "Backup/Restore" in Titanium, scroll down to the YouTube entry, tap it, tell Titanium to Wipe Data.
Edit: Okay, I lied. Reboot and back to force closes.
Related
I did a search on the other thread and found many people with the same issue. In order to organize our thoughts on this topic I would go ahead and open a thread for it and maybe this will help jj and community members to find a solution.
My problem is much like everyone else. I can connect my motorola S9 they will play music; however, when I go to try to make a phone call or answer a call all I get is a slight hum through the headset with no audio and a possible freeze of the device. The slight hum is initiated by pressing the phone icon button on the headset.
I hope I haven't pissed people off by starting this thread I just thought it was necessary to come together on this because it is not just noobs having this problem but members and senior members.
EDIT: It looks like from the other thread JJ just came on and addressed this issue and is working on a fix. mods please remove this thread.
donsaxena said:
I did a search on the other thread and found many people with the same issue. In order to organize our thoughts on this topic I would go ahead and open a thread for it and maybe this will help jj and community members to find a solution.
My problem is much like everyone else. I can connect my motorola S9 they will play music; however, when I go to try to make a phone call or answer a call all I get is a slight hum through the headset with no audio and a possible freeze of the device. The slight hum is initiated by pressing the phone icon button on the headset.
I hope I haven't pissed people off by starting this thread I just thought it was necessary to come together on this because it is not just noobs having this problem but members and senior members.
EDIT: It looks like from the other thread JJ just came on and addressed this issue and is working on a fix. mods please remove this thread.
Click to expand...
Click to collapse
yes... still investigating this issue... the drivers i used have A2DP issues...
Widcomm bt project?
My problem:
Parrot ck3100 paired and sincro without problem. But no sound, just static.
Nothing original, as I can read in meny posts.
I wonder if somebody tried widcomm bt drivers (the project for hermes) with black 3.0.1.
I've been seeing a weird issue where the phone doesn't seem to know if BT is on or off. The Comm Manager will say BT is off -- but the blue LED is blinking. You go into BT settings, and it's unchecked (and presumably off) -- but it's still discoverable from PC's. Also hitting the BT button on the comm manager doesn't always toggle BT -- sometimes it works, sometimes not.
It's not a major deal to me, since I only use BT for PAN and file transfers, but that's only because I lost my really nice BT headset.
I have the Motorola HT820.
Black 2.0, not working
LVSW 5/5 working but phone only sometime answers
Black 3.01 - Success! All buttons work and sound is fantastic with stereo. Headset seems to work for call.
Widcom stack on my lappy seems to connect ok, although it seems slower than previous roms for transferring files
I'm currently testing an uncooked version of this ROM and BT is working without any problems
Am using a Jabra BT 250 headset. Initially paired it fine but went to use it an hour later and would not connect.
Re-paired it and it worked but with static.
sag said:
My problem:
Parrot ck3100 paired and sincro without problem. But no sound, just static.
Nothing original, as I can read in meny posts.
Click to expand...
Click to collapse
Mute and Unmute by pressing the Green button twice should bring back the sound.
donsaxena said:
when I go to try to make a phone call or answer a call all I get is a slight hum through the headset with no audio and a possible freeze of the device. The slight hum is initiated by pressing the phone icon button on the headset.
Click to expand...
Click to collapse
Having the same problem on 3.0.1 flashed back to 2.5 untill the fix.
awesome speed of Black 3 looking forward to the fix
Parrot
has anyone got a way to fix that problem with the ck3100 ? i have found i can connect and dial out but my handsfree dosent give out any sound, when i try to hang up on the handsfree it wont. can anyone help me?
sag said:
My problem:
Parrot ck3100 paired and sincro without problem. But no sound, just static.
Nothing original, as I can read in meny posts.
I wonder if somebody tried widcomm bt drivers (the project for hermes) with black 3.0.1.
Click to expand...
Click to collapse
whats wrong with posting this in the thread for black 3.1? i guess this issue will never be solved not the bluetooth the stupidity
If the BT issues are a problem, do as I and many others did; flash Black 2.5 back onto the phone. Hopefully, your backup will be better than mine
But, the reality is that these are ROMs that are put together by volunteers, and use the latest available software. It can, by its very nature, contain bugs. It is NOT JJ's issue to fix them all--he's done a great job (walshieau too!) making these kick-ass roms. If you want to complain about the roms, flash the official carrier rom, and call them and complain. If you want to be on the bleeding edge, you are going to have to READ, LEARN and UNDERSTAND what you are doing--and be proficient enough to at least TRY to fix your own problems.
For some reason my microphone doesnt work during calls at all in android. i tried 1.5 and 1.6 some months ago and because the mic didnt work i didnt use it at all. once i heard they had 2.1 out i got it on and still, no microphone during calls. i thought 2.1 would have fixed the problem, but obvioulsy its an issue with my phone.
is this just a setting i need to change? i tried searching the 2.1 elcair forum and i didnt find anything about anyone elses mic not working. during a call i can hear the other person pefectly, they just cant hear me.
also, the speaker doesnt work, for ringtones and such. is this still an issue that hasnt been resolved, or is it a problem again with my phone. when i try to change the ring tone it freezes the program and i have to force quit.
any help would be awesome and would make me happy. THX
(im just trying to get it to work, i plan on upgrading to the HTC Evo 4g when it is released)
could this be because my default.txt isnt set up correctly?
I have audio problems with calls if I use the voice search feature. Are you using any kind of voice input methods before trying to make a call?
Also, on the builds I have tried (haven't upgraded in a while) the speakerphone feature wasn't working. They may have fixed that in the newer builds, I don't know.
no i havent been using anything else on there... just no mic during calls. its the first thing i test every time i reinstall android. and still nothing. and yes, my mic works in windows mobile every time i reboot.
im aware the speakerphone doesnt work... but i thought that was only during calls as a speaker phone. does the speaker work for ringtones? or was that what wanst working.
the mic works in all builds and the speakerphone works for both donut and eclair with the newer builds, after applying the updates. Make sure you have the latest radio flashed.
latest radio?
that would be why i bet... im running radio version 1.27.14.09
Mic issue.
I'm glad someone starting this tread I was about to. I've been dying to get android because I thought sipdroid was going to be a good voip solution. Tried it on a G1 and realized it isn't. Now I hear about sipagent, and that I hear works. Since it uses the mic at an application level and not the radio level I've been waiting to hear that voice search works cause that implies droid on kaiser is ready for voip development/beta testing.
So can anyone confirm that the mic is fixed, and that the voice search feature is working within some build?
updated the ROM and radio based on the file at the htc website...
WORKS NOW!!!
im so happy. thx. and yes now the speaker works also and plays ringtones. the speakerphone doesnt work, but atleast it doesnt freeze the phone when you click on the button.
pardonmyownage, can you tell me if voice search causes the phone lose its mic?
tyler51773 said:
pardonmyownage, can you tell me if voice search causes the phone lose its mic?
Click to expand...
Click to collapse
I experienced the same. Definitely voice search caused this problem. After re-installation, it's going well.
Too bad I had to drop Android because the microphone issue. I can listen to the people on the phone, but they can't hear what I say. . I have tried 1.70.xx, 1.71.xx, 1.65.24.36 radios, but none of them works. Anybody help me plz , I'm dying for Android (
Kurt Cobain said:
Too bad I had to drop Android because the microphone issue. I can listen to the people on the phone, but they can't hear what I say. . I have tried 1.70.xx, 1.71.xx, 1.65.24.36 radios, but none of them works. Anybody help me plz , I'm dying for Android (
Click to expand...
Click to collapse
I have the same issue! Please, anyone can help us?
I can't find a clear solution.. the people says that changed Radio and works, but WHAT Radio?!
Pls help us!!!
Recommended radio is anything from 1.65.xx.xx up to 1.71.xx.xx, although some find 1.65 better, there are others who find 1.71 better, but audio issues are normally associated with radio lower than 1.64.xx.xx.
If you have a lot of 'no service' issues then change to a radio at the other end of the scale, e.g. if you are on 1.71 then try 1.65, if on 1.65 try 1.71.
From what I have seen so far 1.71 works best for US, 1.65 for europe, not enough data on other areas to say for certain about anywhere else tho.
Just remember, if you are on a radio lower than 1.65 you are more likely to have audio, especially mic issues.
thanks Zenith! Now I have the microphone works!
It works with radio 1.65.16.25
Instructions (for original Kaiser with wm6 and radio 1.27.x.x):
1 - Copy JumpSPL1.93-KAIS.exe to internal memory and Run from cellphone
2 - When show "USB" on cell screen, remove the USB cable and plug it again
3 - In the ActiveSync on PC, Disable USB conections on Settings
4 - Run from computer KaiserCustomRUU.exe.. and next, next...
Here, HardSPL 3.29 it's allright!
5 - To install WM 6.1, run from the computer: UU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship.exe with cell connected on USB.
So.. I used Myn's Warm Donut from thread [ANDROID] Myn’s Warm Donut - [RLS 5 - 04/24/2010] and I have a Android Phone!
thanks
i believe there is a bug in either the GNex's bluetooth hardware or Android ICS.
i have an A2DP adapter in my car to play music from my phone on my car stereo. my car also comes with the ability to connect to a phone for the purpose of taking and making calls thru its stereo and mics (using bluetooth HFP). when both are enabled simultaneously, i am able to listen to my music fine. if i get or make a call, the phone pauses the music, as you would expect, and goes into the call (although when i receive calls there seems to be a delay before the GNex switches over), but in the call the audio is garbled/robotic/scrambled...whatever you want to call it. this is the case both for what i hear and for what the person at the other end hears.
i wanted to start this thread to get more info about this problem from others that have experienced it, and maybe see if we can come up with a workaround.
there is an AC thread about this here:
http://androidforums.com/samsung-galaxy-nexus/524885-galaxy-nexus-bluetooth-bug.html
and i put in a bug at google here:
http://code.google.com/p/android/issues/detail?id=29564
any more info is appreciated!
According to other posts in the forums, the AOKP ROM does not have these issues.
I really did not want to root this device. I know, that's just not cool. But everything else was just working.
My Sensation did not have these problems, but alas I dropped it and it died and I was still on contract. The Nexus was more cost effective than bending over for the off-contract price from TMO.
Anyway, chalk me up as a "me too" on this issue. I'm going to root tonight and try AOKP.
I would be kind of surprised if it didn't exist in AOKP, because the problem definitely exists in CyanogenMod 9 (and AOKP is essentially a kang of that). In fact, I uninstalled CM9 and reverted to stock expressedly because I initially thought that this bug was a CM9 issue and it was annoying enough that I figured I'd revert to stock until CM9 reaches stable, only to discover that the problem is in the official Google builds as well.
ianken said:
Anyway, chalk me up as a "me too" on this issue. I'm going to root tonight and try AOKP.
Click to expand...
Click to collapse
Please let us know how it goes! I've been using Bugless Beast, but would switch to AOKP if it fixes this bug.
I've yet to find a build without BT issues of some sort.
The garbled call audio is new to me. I've not see that on other devices but have yet to find a GN ROM that mitigates it. This is in addition to issues that go back to the Nexus 1. There was an audio.conf fix for that, I'll see if I can wrangle it up and see if it helps here.
My setup: Factory BT hands free (crap Audi OEM goo) + FIPO A2DP device for music. So, two completely discrete BT devices.
Edit:
try this: edit etc/bluetooth/audio.conf and set master=true (backup the file first)
I also set HFP=true (it's commented out in the file)
What I found:
1- Calling: audio quality was still pretty poor with a lot of pops. It sounds a bit "hot." Quite inferior to other devices I've used with this setup.
2- However: A2DP playback no longer glitches. In my case audio played fine after the first connect after BT was turned on. But subsequent connects, say after leaving and the returning to the car would result in glitchy audio.
So far this tweak seems to have improved things. I'm really bummed by the audio all quality.
ianken said:
I've yet to find a build without BT issues of some sort.
The garbled call audio is new to me. I've not see that on other devices but have yet to find a GN ROM that mitigates it. This is in addition to issues that go back to the Nexus 1. There was an audio.conf fix for that, I'll see if I can wrangle it up and see if it helps here.
My setup: Factory BT hands free (crap Audi OEM goo) + FIPO A2DP device for music. So, two completely discrete BT devices.
Edit:
try this: edit etc/bluetooth/audio.conf and set master=true (backup the file first)
I also set HFP=true (it's commented out in the file)
What I found:
1- Calling: audio quality was still pretty poor with a lot of pops. It sounds a bit "hot." Quite inferior to other devices I've used with this setup.
2- However: A2DP playback no longer glitches. In my case audio played fine after the first connect after BT was turned on. But subsequent connects, say after leaving and the returning to the car would result in glitchy audio.
So far this tweak seems to have improved things. I'm really bummed by the audio all quality.
Click to expand...
Click to collapse
audio.conf does not seem to exists in 4.2.2. Has anyone found audio.conf in 4.2.2?
Ok so it's been a while I didn't use my phone with a wired headset, but some time ago I would always use it to listen to music on my daily commute. Lately I started using it again. I've always used it with some Soul SL99 for music and calls with no problems.
But since 2 days ago I noticed it stays on headset mode even after disconnecting the headphones. when I make a call the built in mic and speaker don't work and the proximity sensor disabled. I can use it on speaker with no problem, and if I connect the headset people don't here me clearly. I have to restart the phone to exit headset mode on it, but whenever I connect my headphones it'll stay in headset mode no matter what until I restart it again.
Only weird thing I've done is try out different audio mods, like AwesomeBeats, Ac1d audio and Noozxoide. So I can't tell if it's damaged hardware or software. I've tried full wiping my rom, I've tried 3 different Roms including going back to 4.1 and on every single rom it does the same thing.
So basically my question is, could it be software driver related? Or most likely hardware? If software, would there be a fix? And if hardware, what piece would it be, the loud speaker/headphone module, or the headphone flex cable?
Has anyone experienced this before?
I have no experience with it, but maybe this will fixed in the next update to fix Bluetooth streaming.
Can you try cm10 stable or another 4.2 rom and see if that helps
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
I have no experience with it, but maybe this will fixed in the next update to fix Bluetooth streaming.
Can you try cm10 stable or another 4.2 rom and see if that helps
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I did, I tried AOKP latest build, XenonHD, CNA 3.8.0, and some others. Still does the same thing. Hopefully it is software and I won't have to buy replacement parts.
No one can help?
....
Mods can close this thread, obviously there's no support in GN forums whatsoever,
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Still no one can help?
I've bought a Nexus some days ago and it already came with 4.2.1. I have just added root and CWM.
Yesterday I tried for the first time to connect it to my car's bluetooth handsfree kit. I activated Btooth, but I've not found any way to make the phone visible. Tapping on the phrase "your phone is not visible" did nothing. It was searching for devices but found nothing. Later at home I've found on google forums many people that have problems with bluetooth on 4.2.1. I also found that in some situation it is impossible to turn it off, and it does not work correctly. I have found this advice:
Go in settings - applications. swipe to the right last page "ALL". Search for bluetooth pairing app. Click on it and terminate it. Maybe you have to tap twice. Now your BT is off. Now go in application again (or use your favorite widget, like widgetsoid) and turn BT on again. Now it should work (for some time, only !!) This way I was able to pair Nexus with handsfree and also I've made some calls.
From forums, it seems a software bug. Found in other phones also, not only on Nexus.
Cheers
Sergio
Hello everyone,
My LG G3 is giving me a hard time, when I connect a headset, its microphone isn't working or it does but it's barley audible compared to the device's own mic.
The headphones part is working as usual and when the headset is connected sounds goes only through them like it should.
I've started using this headset a few days ago and it worked like a charm but then it's suddenly stopped working like it had been.
Fortunately I have another LG G3 on hand, so first I checked the headset with it and it works perfect.
So then I've replaced the 3.5 audio jack from the other G3 into my own to figure out if it is causing the problem and it is NOT,
since I got no improvement in my own phone and I also put MY jack in the other G3 and it worked there flawlessly with two different headsets.
I've been trying to record into / monitor with two different apps (lg audio recorder and another another one).
I've killed all apps running in the background. I've restarted numerous times, ran CCleaner to clear cache memories and whatever.
At one point a few days ago, maybe it was just before it started (and this might be a clue) the "plugged device" icon or "headset" icon on the notification bar stayed even after I've disconnected the headset and I think I needed to restart the phone but if i'm not wrong the headset kept working after that.
I was trying to find any kind of audio service to restart or anything like that but I didn't find any, I just killed them all to see if it helps.
I've also tried using "soundabout" app to try to force the audio path to the headset and played with some settings but to no avail (I disabled soundabout service after that attempt).
Right now I see no other option but a hard reset and I'm pretty sure it will solve the issue. but I hate going through backing up and restoring everything. and even so, who said this issue won't happen again? I've tried to search for an answer but found nothing like my problem on the web.
I just read something old from 2013 that mentions a bug in android audio. not sure it's related. something about "AudioPolicyMangerBase" (it seems I can't post links yet) from an app that had a switch to switch between headset mode or phone mode. but in any case it's no longer maintained. again, not sure it's related.
Update: Now I got no sound with two different headsets on the SECOND LG G3 as well. it seems messing with it around, plugging and unplugging messes with it's software somehow and maybe it locks the audio route in a way that it's can't work.
Any way to reset all audio ins/outs routes in the device?
I'll appreciate your help. Thanks a lot!
Roy.