Hi, I just recently got my Hero, and the first thing I did was root it and install a custom ROM. Currently I'm using fresh 1.1 (thank you flips) and everything is pretty much working great, but my headphone jack just stopped working. I was listening to music through my headphones and then got a call and the call didn't come into my headphones. Now, after rebooting, the phone still won't recognize when they are plugged in.
I don't think it's the hardware, because I can hear in the headphones the crackle when I first plug them in. Any ideas? Thanks in advance!
I came across this once and realized that when you boot the phone with your headphones plugged in, it will not recognize them. I had to reboot the phone and then plug them in when the phone was fully booted. Not sure if that's the same problem you are having but figured I'd throw that out there just in case it was.
nutswillkillme said:
I came across this once and realized that when you boot the phone with your headphones plugged in, it will not recognize them. I had to reboot the phone and then plug them in when the phone was fully booted. Not sure if that's the same problem you are having but figured I'd throw that out there just in case it was.
Click to expand...
Click to collapse
+1 on that for me as well. I also just re flashed the rom and it solved the problem as well
nutswillkillme said:
I came across this once and realized that when you boot the phone with your headphones plugged in, it will not recognize them. I had to reboot the phone and then plug them in when the phone was fully booted. Not sure if that's the same problem you are having but figured I'd throw that out there just in case it was.
Click to expand...
Click to collapse
It's a common problem with the Hero. Mine does that as well...and it is annoying.
I've had to reboot 2 or three times in a row.
Kept forgetting to unplug the headphones...
nutswillkillme said:
I came across this once and realized that when you boot the phone with your headphones plugged in, it will not recognize them. I had to reboot the phone and then plug them in when the phone was fully booted. Not sure if that's the same problem you are having but figured I'd throw that out there just in case it was.
Click to expand...
Click to collapse
Ah you are a gentleman and a scholar! Occam's razor seems to have disappeared from my toolbox. Thanks again! Hope to be able to contribute more on these boards, very nice for my first foray.
I had the same problem when playing pandora through the AUX jack in my car.
abcdfv said:
I've had to reboot 2 or three times in a row.
Kept forgetting to unplug the headphones...
Click to expand...
Click to collapse
I'm curious...is this headphone issue a problem with the Android/HTC software that we have or is there some design flaw with the hardware?
Good question. Maybe I'll nandroid back to my 2.1 update and see if it is still a problem.
I have found that most phones do this, I had the same issue with my blackberry. I think it has something to do with the way phones recognizes hands free setups
Yeah, booted into 2.1, speakerphone worked, plugged in headphones, they worked.
Rebooted and only speaker/earpeice would work despite unplugging and replugging the headphones.
services.jar, services.odex
This is a known bug in 1.5, you will have to replace your "services.jar" and "services.odex" files, found in /system/framework. I have attached one that worked for me.
Unzip the attached archive. Then (after backing up your existing services.jar and services.odex with "adb pull"):
Code:
adb push services.jar /system/framework/
adb push services.odex /system/framework/
WARNING: This will overwrite a system file, always backup.
Reboot (might not be required but I did it anyway). Worked for me, just did this the other day from a solution I found in the Android forums (sorry, don't have the link any more).
P.S. This "services.jar" is for 1.5/cupcake on Hero CDMA only (works for me running Fresh 1.1).
P.P.S Remember to back up your existing services.jar (adb pull services.jar SOMEWHERE_THAT_WONT_OVEWRITE_THE_NEW_ONE) before trying this.
this is a nice little work around
http://code.google.com/p/toggleheadset/downloads/list
widget to enable/disable headphones
works for me
GL
Related
Earlier today I was at my brother in laws house, was gonna copy some music from my phone to his computer (always have a usb cable in my car ). For some reason windows (vista) kept giving me unknown device and the option of mounting the sdcard never appeared.
I thought that was odd, never had the problem before, was short on time and didnt mess with it besides tryin to unplug and plug it back in. Well I get home and I see there is a new cyanogen build (a couple actually, mine is about 2 weeks old).
I plug in my phone with the normal usb cable I use and nothing. The phone charges (as it did on my brother in laws computer) but I the option to mount it doesnt come up on my phone. I dont see it in device manager and adb also cant find the device. USB debugging is turned on as well.
My only worry is that it is not a software problem because I got pretty drunk the other night and fell on my phone. The touchscreen is cracked a little but its just cosmetic damage, the phone has functioned 100% after that until now. Is there anything I can try here short of wiping and flashing my ROM again?
Tried searching but "sdcard mount issue" and other similar searches come up with pages and pages of unrelated stuff
Vista never sat well with my phone, ADB was a pain to get working and then, of course, I lose my data cable
But as far as that goes, I'm not even sure Vista works with the Android SDK, because I never got it to work. I was able to succesfully mount and unmount like it was a stock phone.
Your best bet is to, indeed, wipe and reflash. Use Cyan's recovery to make a backup and you can restore that after you sort things out with the sync'ing problems.
Well I have had the SDK working just fine, well adb and fastboot is all I have used on both my desktop and laptop.
Guess I will have to dig around for my adapter and give try giving it a wipe.
Well I just wiped and flashed the lastest cyanogen, before doing that I booted into recovery, hit the back button and it went into fastboot mode. I tried giving it the command to reboot, fastboot reboot, cmd prompt showed as it should be successful but it would never reboot.
I didnt think that was a good sign but I went ahead and wiped and flashed, same problem still persists. The sdcard worked fine in the adapter and both my ext3 and fat32 partition are working fine through the phone.
Anyone have any ideas? Would be nice if I didnt crack my screen, although its just cosmetic damage (phone functioned 100% for weeks now), I am pretty sure that will void my warranty if the phone were still under warranty.
This problem isn't huge, would like to be able to use adb again and not have to turn my phone off and use the adapter if I want to flash a new ROM.
Have you tried uninstalling/reinstalling the drivers in Windows?
It isn't showing up in device manager (only way I know to uninstall the drivers).
I think it has to be a hardware issue though, tried multiple computers, couple of different usb cables, wiped and flashed a different rom. Guess it's time to call up asurion
rondey- said:
It isn't showing up in device manager (only way I know to uninstall the drivers).
I think it has to be a hardware issue though, tried multiple computers, couple of different usb cables, wiped and flashed a different rom. Guess it's time to call up asurion
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=531310
try that. if that doesn't work, its a hardware problem.
Yeah that didnt work either. Thanks for the help though guys, just sucks this is gonna have to cost me money through insurance for a stupid crack in the screen.
Hi guys. All of the sudden my earpiece died. I'm currently running Cognition 4.2.2, and I love it, but I'm not entirely sure that is the problem. I don't really want to have to re-flash cognition, because it's just a pain to reinstall everything even with titanium's batch operations... but if I have to I will. Anyways, I've checked it with a wired headset, it works fine. with a Bluetooth headset, it works fine. on speakerphone, it works fine but people can't hear me well. when people call me or I call them they say that they can hear me just fine but I cannot hear them at all until I switch it to speaker or my Bluetooth headset.
Has anyone encountered this issue? is it cognition, or the phone's hardware?
My phone is still under warranty, and everything else works... (except I think the battery is going bad) but that's another issue. If it's hardware, I can Odin it back to the stock rom and then see if they'll replace it under warranty for me.
(if I have to do that, can I transfer my titanium backup to the new phone so I can just flash cog and restore it to it's former glory?) If not, time to get my new inspire I guess.
Thanks guys.
well theres one easy way to find out if its the rom.
flash a new rom.
you should flash stock so if it doesnt work you can reutrn it!
TRusselo said:
well theres one easy way to find out if its the rom.
flash a new rom.
you should flash stock so if it doesnt work you can reutrn it!
Click to expand...
Click to collapse
I think we Canadians can communicate telepathically, because that's exactly what I was thinking. Good job picking up my signal, when I'm all the way down here in New Mexico =P
But anyways, I was going to do this if I didn't get any other ideas to try... just a pain to restore but oh well.
as far as restoring the new device if I get one, can I just drag and drop the titanium folder on my phone to my comp, and then to the new device and run titanium from there? or will it not work that way?
Saying goodbye to this cappy will be so sad though... I'll miss my silver speaker mod.
Yup, itll work that way. Did it on my sisters bf's cappy cause the dumbass threw it and broke the screen. I had to boot it to recovery and hold my working phone in the other hand and synchronize button presses to guide me through getting to mounting it. Copied over the entire sdcard, once the refurb got here just copied over all his **** (which had a tibu folder) flashed him to ff, restored and it's like he never chucked it across the damn room.
studacris said:
Yup, itll work that way. Did it on my sisters bf's cappy cause the dumbass threw it and broke the screen. I had to boot it to recovery and hold my working phone in the other hand and synchronize button presses to guide me through getting to mounting it. Copied over the entire sdcard, once the refurb got here just copied over all his **** (which had a tibu folder) flashed him to ff, restored and it's like he never chucked it across the damn room.
Click to expand...
Click to collapse
....
lol'd.
Alright. Cool. Thanks! shouldn't this work with my inspire too, as long as I only restore apps, not data?
studacris said:
Yup, itll work that way. Did it on my sisters bf's cappy cause the dumbass threw it and broke the screen. I had to boot it to recovery and hold my working phone in the other hand and synchronize button presses to guide me through getting to mounting it. Copied over the entire sdcard, once the refurb got here just copied over all his **** (which had a tibu folder) flashed him to ff, restored and it's like he never chucked it across the damn room.
Click to expand...
Click to collapse
i needed a good laugh this morning...
ya tibu restore apps (+ their data), no system data... (well maybe the green ones if you want, theres 8)
Interesting... phone works just fine after flashing stock...
Cognition problem it was, or so it seems.
Time to flash back. See if it fixes it.
My phone isn't seen by any computer (drivers installed and up to date, it worked right before I installed) after installing TWRP. I used the app from the Play store and said yeah to the memory patch thing, then updated TWRP to 2.8.4. I plugged it into the computer, nothing. Other computers, other drivers, other cables, nothing. I undid the patch from the app. Nothing. I tried mounting storage in TWRP. Nothing. Any ideas? Thank you in advance.
Jonathan_A said:
My phone isn't seen by any computer (drivers installed and up to date, it worked right before I installed) after installing TWRP. I used the app from the Play store and said yeah to the memory patch thing, then updated TWRP to 2.8.4. I plugged it into the computer, nothing. Other computers, other drivers, other cables, nothing. I undid the patch from the app. Nothing. I tried mounting storage in TWRP. Nothing. Any ideas? Thank you in advance.
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showpost.php?p=58297902&postcount=2
Hey, thanks, I forgot to mention it's not showing up in device manager either. Nothing showing here, no sound that it's connected, no indication I've plugged it in at all.
Jonathan_A said:
Hey, thanks, I forgot to mention it's not showing up in device manager either. Nothing showing here, no sound that it's connected, no indication I've plugged it in at all.
Click to expand...
Click to collapse
is this happening when the phone is booted up, or in the bootloader, or in recovery ?
All of the above. Charges fine, but is not seen through USB at any point.
Jonathan_A said:
All of the above. Charges fine, but is not seen through USB at any point.
Click to expand...
Click to collapse
first of all make sure your using the original HTC cable as all cable don't come with the 2 required Data+ or Data- wires inside.
Boot your phone up, plug it into your computer, then check the USB settings on the phone itself by pulling down the notification bar.
These are things I would just try myself, never experienced this issue before, but really the first thing I would do is uninstall anything I installed after it went wrong, I was going to say manually flash a recovery, but that's not much help if your phone isn't being seen in the bootloader either, in all honesty, it sounds more like a hardware problem to me than software.
Yeah, I'm hoping it's something with TWRP that can be fixed relatively easily, like permissions or something, but it does seem to be hardware related. I just don't get how it could be... in any case, I'll try what you suggested. If anyone else has any suggestions, I'll definitely take them.
Jonathan_A said:
Yeah, I'm hoping it's something with TWRP that can be fixed relatively easily, like permissions or something, but it does seem to be hardware related. I just don't get how it could be... in any case, I'll try what you suggested. If anyone else has any suggestions, I'll definitely take them.
Click to expand...
Click to collapse
im sorry but ive tried to replicate this problem but messing with settings in recovery and the bootloader and cant, its sounding more like a hardware problem to me, im at a loss, hopefully someone else can shed some light on the situation.
Jonathan_A said:
Yeah, I'm hoping it's something with TWRP that can be fixed relatively easily, like permissions or something, but it does seem to be hardware related. I just don't get how it could be... in any case, I'll try what you suggested. If anyone else has any suggestions, I'll definitely take them.
Click to expand...
Click to collapse
Have you tried connecting it to a different usb port on your pc? You could also try booting your pc to safe mode and uninstalling "USB Host controller" then reboot and reconnect. I had a similar issue the other day after switching from twrp to cwm to use a cwm nandroid.
After flashing recovery my computer would not detect my phone at all. Simply moveing to a different port fixed it for me. Although when I connected to the original port, that port still would not detect my phone. Reinstalling the USB Host controllers fixed that though.
Well, I plugged it into the charging port on my laptop with a random cable the other day, and it just worked. I have no idea how or why, but it seems to work no matter what now, on all the ports and cables I thought I was having problems with. I guess I'll file this under "user error - anomaly." Thank you guys for your time.
Jonathan_A said:
Well, I plugged it into the charging port on my laptop with a random cable the other day, and it just worked. I have no idea how or why, but it seems to work no matter what now, on all the ports and cables I thought I was having problems with. I guess I'll file this under "user error - anomaly." Thank you guys for your time.
Click to expand...
Click to collapse
Happy Days
Hello, I've had my G Watch R for not quite a full week so far and I've really enjoyed it. Two days ago, I believe that I let the battery die so I placed it on the charger before going to bed. When I woke in the morning i grabbed the watch off the charger without looking at it. Just before i stepped out the door i noticed that it wasn't waking up and It wouldn't even power on. I ran back and slapped it on the charger thinking that it would be more than charged by lunch time. Thats when i noticed the apparent boot issue you can see in the video attached. It hasn't been dropped at all and I have the basic apps installed; facer, watchmaker etc. At this point, Is there anything that I can try short of sending it back?
I've left it on the charger for 24+ hours, it gets slightly warm and stays in the boot loop. As soon as its taken off the charger it has no visible charge and refuses to respond to anything. I purchased it through amazon, so I'm thinking it shouldn't be an issue for me to return it...
http://youtu.be/GgF3iXAhTTI/
Sorry i tried to embed the video but the youtube link for xda seems to be breaking the url somehow
So I have already initiated the return process with amazon and it should be pretty painless. I have almost 3 weeks to send it back, so if anyone has any tips/tricks or ideas I'm more than open to try them....The watch is 100% stock as far as firmware or root is concerned.
Any luck with this? I just got back an RMA for a broken touch sensor, I don't want to have to RMA it again.
try to see if you can get in to the bootloader, and restart the watch from there
i have notice when i charge the watch from empty (so thewatch boots up while charging) it causes problems, usually boot loops as well
I just watched the video (should've done this before hijacking the thread, sorry) and it seems like I'm having a different issue. Instead, mine does the android boot animation, the goes to "Starting Apps" and counting ("x of y Apps"; the y value seems to be different every time), then "Staring Apps" with no count, then it says "Powering Off" and shuts off. But I will post my experience in case someone else with my issue finds this thread.
I'm back up & running today. I got it into the bootloader last night and put it on the charger before I went to sleep (to avoid battery rundown by bootlooping while it charges). I woke up this morning to it bootlooping again. I'm guessing that it restarted itself sometime during the night. I took it off the charger and let it sit for a while (it was pretty warm, so I figured it would be better to let it cool down before trying anything else). I tried to restart it again after about a half hour, but it still only got to "Starting Apps" before shutting off. I reflashed the stock boot, recovery & system images found here: Stock Boot, Recovery and System for G Watch R . I restarted it and completed the initial pairing process (due to wipe when I unlocked it in order to flash system image) and it is now working.
I don't know if what I did actually fixed anything or if it just decided to start working, but I will post again if something happens again. If you don't see any more replies from me, then all is still OK.
EDIT 6/22/15 9:53 pm EDT: No good, see below.
To workaround the bootloop while charging, you can boot into recovery (swipe 10 to 4 a clock while Logo is shown, select and press okay to recovery), than charge battery for a while, after that, you can boot to as normally to AW-system and charge to fully battery!
You can charge with USB on PC, it's work fine for me.
scidon37 said:
I just watched the video
I don't know if what I did actually fixed anything or if it just decided to start working, but I will post again if something happens again. If you don't see any more replies from me, then all is still OK.
EDIT 6/22/15 9:53 pm EDT: No good, see below.
Click to expand...
Click to collapse
So your gwatch r started doing the same thing again? I have the same problem and it won't connect to the computer via fastboot or adb. How did you get on with the RMA? I cant send mine back due to voided warranty. Still hoping for a solution.
Have you tried taking it off the charger and booting it? Also are you running custom software?
bricked watch
atmosphrericks said:
So your gwatch r started doing the same thing again? I have the same problem and it won't connect to the computer via fastboot or adb. How did you get on with the RMA? I cant send mine back due to voided warranty. Still hoping for a solution.
Click to expand...
Click to collapse
Ever find a fix for this? I've been searching like mad the last few weeks. :/
biohazard1150 said:
Ever find a fix for this? I've been searching like mad the last few weeks. :/
Click to expand...
Click to collapse
So i took off the back plate, and found that the spring contact pins inside the watch weren't making good connections to the connect points on the inside of the back plate. Be careful, they are fragile, but you want to bend them out slightly. If you can source parts, get a new contact pin module.
After this, i was able to connect my watch and flash over stock firmware.
I can't guarantee this is what is happening with yours, but let us know if it does work.
I've scince broken the screen and can't find where to get parts!
atmosphrericks said:
So i took off the back plate, and found that the spring contact pins inside the watch weren't making good connections to the connect points on the inside of the back plate. Be careful, they are fragile, but you want to bend them out slightly. If you can source parts, get a new contact pin module.
After this, i was able to connect my watch and flash over stock firmware.
I can't guarantee this is what is happening with yours, but let us know if it does work.
I've scince broken the screen and can't find where to get parts!
Click to expand...
Click to collapse
I still haven't found a fix. My charging works fine, but no PC connection. The bootloader/fastboot wont come up, no logo or anything. I'm sure the EMMC chip is fried, it sounds like many are seeing this issue, some with a black screen and some with a snowy screen. I've had several galaxy phones do the exact same so I'm doubting it can be fixed without going to the manufacturer which mine came from redflagdeals and LG wont service the random online store purchases
I had to take the back off and clean and adjust the contacts that make contact through the back panel. Then I could connect via fastboot.
ouranos2k said:
You can charge with USB on PC, it's work fine for me.
Click to expand...
Click to collapse
This solved my problem. As soon as I plugged it into my PC it booted just fine
ouranos2k said:
You can charge with USB on PC, it's work fine for me.
Click to expand...
Click to collapse
This works for me too! Thank you!
Sent from my SM-N920C using Tapatalk
Seen some more posts around about it but wanted to report what I'm contently dealing with.
Device is charging whenever it wants, sometimes one cable works then doesn't. My best bet for charging is my Xiami Laptop charger but even with that, I might have to plug the cable 2-3 times before accepting it! Well sometimes that doesn't work either, in that case, device has to be turned off then connect the cable and then almost 90% will start charging. Then I can turn it on and still charging...BUT... if I unplug and reconnect the cable it might not charge... yeah I know it sounds ****ed up but that's not all....!
ADB doesn't work cause computer don't recognize it. It might charge sometimes even without turning it off to do so, but still doesn't recognize it! (yeah drivers installed, believe me I have tried almost everything, I'm not new with androids)...
Finally...
File transfer and any other USB option is grayed... tried various things but haven't managed to make it work!
Well, I have read that many people encounter similar issues with this device after an update... don't know about that, when I got the phone it was like that! And it seems like no one knows what the actual problem is or how to fix it! Still, I would like to know your experience and what you think about it!
Thanks a lot for your time.
+cs.tribal said:
Seen some more posts around about it but wanted to report what I'm contently dealing with.
Device is charging whenever it wants, sometimes one cable works then doesn't. My best bet for charging is my Xiami Laptop charger but even with that, I might have to plug the cable 2-3 times before accepting it! Well sometimes that doesn't work either, in that case, device has to be turned off then connect the cable and then almost 90% will start charging. Then I can turn it on and still charging...BUT... if I unplug and reconnect the cable it might not charge... yeah I know it sounds ****ed up but that's not all....!
ADB doesn't work cause computer don't recognize it. It might charge sometimes even without turning it off to do so, but still doesn't recognize it! (yeah drivers installed, believe me I have tried almost everything, I'm not new with androids)...
Finally...
File transfer and any other USB option is grayed... tried various things but haven't managed to make it work!
Well, I have read that many people encounter similar issues with this device after an update... don't know about that, when I got the phone it was like that! And it seems like no one knows what the actual problem is or how to fix it! Still, I would like to know your experience and what you think about it!
Thanks a lot for your time.
Click to expand...
Click to collapse
If you have warranty, just go and have your phone dealt with.
My reply sounds not-fun, but, there is a post from someone pointing out that sending his phone to service centre was his solution. It is reported by him that the issue has something to do with the motherboard.
same issue
+cs.tribal said:
Seen some more posts around about it but wanted to report what I'm contently dealing with.
Device is charging whenever it wants, sometimes one cable works then doesn't. My best bet for charging is my Xiami Laptop charger but even with that, I might have to plug the cable 2-3 times before accepting it! Well sometimes that doesn't work either, in that case, device has to be turned off then connect the cable and then almost 90% will start charging. Then I can turn it on and still charging...BUT... if I unplug and reconnect the cable it might not charge... yeah I know it sounds ****ed up but that's not all....!
ADB doesn't work cause computer don't recognize it. It might charge sometimes even without turning it off to do so, but still doesn't recognize it! (yeah drivers installed, believe me I have tried almost everything, I'm not new with androids)...
Finally...
File transfer and any other USB option is grayed... tried various things but haven't managed to make it work!
Well, I have read that many people encounter similar issues with this device after an update... don't know about that, when I got the phone it was like that! And it seems like no one knows what the actual problem is or how to fix it! Still, I would like to know your experience and what you think about it!
Thanks a lot for your time.
Click to expand...
Click to collapse
i have same issue, before my mia2 working normaly, but after update v10.0.13 usb optopn grey and disable, before that i can use my usb for debuging my android app etc. now its stuck. i think in update have corrupt file system. its bug in rom update. u have solution or have been fix it?
TechnoSparks said:
If you have warranty, just go and have your phone dealt with.
My reply sounds not-fun, but, there is a post from someone pointing out that sending his phone to service centre was his solution. It is reported by him that the issue has something to do with the motherboard.
Click to expand...
Click to collapse
The warranty is off! So it looks like I'm stuck with this ROM cause, its literally dangerous to try installing something else, in case it gets bricked there will be no way restoring that phone i guess!
xplancer99 said:
i have same issue, before my mia2 working normaly, but after update v10.0.13 usb optopn grey and disable, before that i can use my usb for debuging my android app etc. now its stuck. i think in update have corrupt file system. its bug in rom update. u have solution or have been fix it?
Click to expand...
Click to collapse
Seems like there is no solution! But I bet that something can be possible, but who knows... we need to find out
I have the same problem, but the same thing that you say happened to me, I installed a rom and it gave an error and the cell phone died, it no longer connects in any way or does anything, just turn on in fastboot mode or in recovery mode, but I can't install anything, plus everything was formatted
balther said:
I have the same problem, but the same thing that you say happened to me, I installed a rom and it gave an error and the cell phone died, it no longer connects in any way or does anything, just turn on in fastboot mode or in recovery mode, but I can't install anything, plus everything was formatted
Click to expand...
Click to collapse
Well you ****ed up... The whole thing is ****ed up... Seems like the only way to unbrick it is change the motherboard!!
Btw...there is a new update that im about to install... Who knows, maybe it will fix something....
It is not a hardware issue it is a kernel issue...upon boot a "chargeonlymode" file is created in sbin folder... I am a rookie at this but after a month of digging, 2 mia2's and 4 charger modules later, something is focing our phone into chargeonlymode. If i can find the solution I will post it