I recently bought an ATRIX 4G off of ebay. I needed a GSM upgrade for my DROID x2 and this was really a great steal and the lapdock coupled with the unlocked bootloader make it a real 'uphrade' (even though it's older).
Anyway... it has a few small problems. They aren't dealbreakers and I can definitely live with them but I would like to fix them if its at all possible (every detailed solution gets a 'thanks')
Microphone does not work (in any apps)
Speaker only works when i twist the phone (apply pressure, in opposite directions, on the ff camera and the search button)
Headphone jack works rarely (i clean the jack with a cotton swab but they stopped working after i turned off the phone)
And finally, the usb doesnt recognize the charging cable when im hooked into a wall charger. Originally it didnt recognize being plugged into the computer, but after i unlocked the BL and flashed cwm, the computer was recognized.
I was running stock 2.3.6 4.1.141 but am now running faux's 1.3 and nottachtrix 1.3.1 the problems persisted on both setups.
Only other thing I can tell you wonderful, intelligent, good-looking, helpful people is that I suspect the screen has been replaced. Its just in too good condition to be used.
Meany105 said:
I recently bought an ATRIX 4G off of ebay. I needed a GSM upgrade for my DROID x2 and this was really a great steal and the lapdock coupled with the unlocked bootloader make it a real 'uphrade' (even though it's older).
Anyway... it has a few small problems. They aren't dealbreakers and I can definitely live with them but I would like to fix them if its at all possible (every detailed solution gets a 'thanks')
Microphone does not work (in any apps)
Speaker only works when i twist the phone (apply pressure, in opposite directions, on the ff camera and the search button)
Headphone jack works rarely (i clean the jack with a cotton swab but they stopped working after i turned off the phone)
And finally, the usb doesnt recognize the charging cable when im hooked into a wall charger. Originally it didnt recognize being plugged into the computer, but after i unlocked the BL and flashed cwm, the computer was recognized.
I was running stock 2.3.6 4.1.141 but am now running faux's 1.3 and nottachtrix 1.3.1 the problems persisted on both setups.
Only other thing I can tell you wonderful, intelligent, good-looking, helpful people is that I suspect the screen has been replaced. Its just in too good condition to be used.
Click to expand...
Click to collapse
honestly, it sounds as if they damaged some of the internals when trying a screen replacement, if you've tried loading a different kernel/firmware onto it and the problems persist, then it's definitely hardware related.
Related
One day when I plugged out my headphones from my phone it didn't seem to notice it. I couldn't get any sound from the speakers, and when I plugged the headphones back in nothing happend, like it didn't notice they were gone. I rebooted my phone several times and still no sound from the speaker. Even the radio (which you need headphones to use), works when I disconnect them (except no sound of course).
It's probably a software bug. Any ideas?
UPDATE: It seems to work now
same problem
dude even im facing the problem fr the pas 3 days... even i tried soft resetting aswell as hard reset the fone but still got the same prob , even wen starting fone it says headfones detected n prompts to select hedfones , hedset n tvout ...
PLEASE IF U GET ANY SOLution respond ASAP
Headphone jack
rjswaroop2004 said:
dude even im facing the problem fr the pas 3 days... even i tried soft resetting aswell as hard reset the fone but still got the same prob , even wen starting fone it says headfones detected n prompts to select hedfones , hedset n tvout ...
PLEASE IF U GET ANY SOLution respond ASAP
Click to expand...
Click to collapse
answer is here
I've been having headphone problems for a while, (it kept asking me what was plugged in with nothing plugged in). Up to now, it didn't hurt too much, but today it finally made my Omnia II unusable and I had to put my SIM in an old backup phone.
In the past, I've tried sticking a needle on the physical contact to "exercise" it, and putting some WD-40 and alcohol on it with a toothpick. Today, however, nothing worked. I ended up taking the phone apart, (since it was unusable I figured I had nothing to lose), and found that the headphone jack is a single component with a ribbon cable and connector to the main board. I found an online store selling this headphone part via Google and have ordered it, (I had to buy three as that was the minimum--if they work, I'm keeping them all as future replacements, sorry). I won't say what store because I don't know them or if this will fix the problem, but if they deliver and it works, I'll re-post with details. I really hope this fixes the problem because I've spent a *lot* of time and money getting this phone up to replacing my old Palm TX and was expecting it to be around for a few more years...no other mobile OS does what I want right now and I'm totally fine with the O2 hardware/software other than this bloody headphone issue.
I received my new headphone jacks yesterday and replaced the one on my phone. And...it works!
The new jacks are a different design. The "plug-in" sensor is at the top now and the whole thing is a lot tighter. Also, when I plug something in, (I tried headphones and a headset--not TV out), it no longer asks you what's plugged in. It seems to auto-sense the type of plug fine.
It's only day 1, but my phone is usable again. Yay!
The store I bought the jacks from is globaldirectparts.com. I had to buy three jacks, but it only ran about $20US. I'm keeping the others as spares in case this ever happens again as I plan to hold on to this phone for a few more years, (bought off contract).
After getting the back off and exposing the internals, I was able to just lift the top edge of the main boards with a popsicle stick use a small, flat screwdriver to unplug the old jack. I then slid the new jack in, made sure it was lined up, (it does this pretty much on it's own--not much wiggle room), and pushed down on the board until it "clicked" on.
Hi.
Yesterday my phone stopped recognising the earphones/speakers when plugged in ?! It doesn't show the "headphones" icon any more, and even on full volume I can here sound/music only on the left speaker/earphone very silently. I've tried 2 different headphones, 2 different speakers as well ... ale same results.
Is there a way how to determine whether it's firmware/software issue or hardware ???
Thank you in advance.
P.S. : what I did prior to noticing this problem - we have a new sound system in our school that has two places for connection. We were using one of them, but couldn't use the another one, because of lacking cable. Once the cable arrived and we connected the cable to the system - I've tried whether it's working with my phone. It played the sound only in the way, that I've described. So we have tried it with an Iphone (the same results) and later PC, which played the sound correctly. I'm still waiting for response from the Iphone owner, whether he has the same problem - but could the cable/system caused the fault ??? Do you think, that my phone would get damaged by "some current" ???
From what you say, it seems to be an hardware problem. To test this, you can perform a factory reset and if the problem persists it's definitively an hardware problem.
one possibility is you got dust/lint in the earphone socket. the cover broke off on my defy, and i occasionally have to pull some lint out using a toothpick
I've checked that as well, but couldn't see anything there. Well never mind now...I've sold the Defy and bought a new one. Such a great phone deserves that everything is running as it should
Thank you for your help.
Sent from my MB526 using xda premium
Hi all,
I recently purchased an MK808B. Ive had a few issues with reboots.
If I try to add a bookmark to the default internet browser the device reboots. This wasnt a major issue so I downloaded Google Chrome. The device has now rebooted multiple times when trying to open some apps. Most notably when trying to open Facebook.
The WIFI signal is poor, my router is within 3 feet of the TV and I get a strong signal on other Android devices. Is there something I can do to improve the signal strength?
The device isn’t rooted. I have read on Geekbuying's blog how to do it and it seems straight forward enough but is there a better way to root? Can someone recommend a custom ROM. I have read about a couple of roms on this forum and ona couple of others. Should I flash the stock rom from geekbuyings blog? Does anyone know about Finless rom?
Also is there a default way to power off the device?
The reboot issue sounds like a power supply problem. If your PSU is too weak your device will reboot randomly when using.
Yea this is common using the stock power adapter. Those Chinese adapters aren't known for being accurate or stable.
Try powering from a PC USB or a spare name brand charger with a 1A+ output. Fixed mine.
There are lots of wifi antenna mods. Basically they did a horrible job soldering. They shorted the ground with the positive on many of them. These are dual antenna. One of mine was shorted. I fixed it by just pulling off the ground completely. I eventually removed all built in antennas and added one from an old router. Full signal now, but no where near pocketable anymore. Haha.
Most people drill a hole in the case and make a cable come out and back in... like a mushroom shape.
My favorite firmware is the Minix Hybrid by lewry. Newer ones come rooted and have a custom kernel too. Very fast and stable. Use the 720 versions. The 1080 makes things too small. You don't need to be rooted to flash roms. You flash the chips using a program.
To flash... CHECK CABLE. Mine will charge but doesn't pass data. Took me a while to figure that out.
Disconnect all USB. Hold down the little hidden button with a paper clip THEN connect the OTG port to the PC (this will also supply power). Holding the paperclip in WHILE plugging in the OTG cable is a challenge. You'll hear the PC ding immediately and ready to flash.
Sent from my Nexus 7 using XDA Premium HD app
I recently got the courage to unlock and root, but I feel like a bull in a china closet. I just breaking things and fixing them! I really feel like a dumb animal, but I keep reading and learning. So far, I've been able to fix or reflash until this post.
My issue is my when placing phone into car dock, I can't hear a call afterwards. It doesn't matter if I leave the phone in or take it out, I can call out, but the person I"m calling can't hear me. The only cure is a reboot, in which calling can resume until I enter the car dock.
A little background, I have flashed several ROM's over the past several days and I'm not sure where it started. PacMan, DeadCalm, etc. Now I'm using 4.2 RootBox. During my flashing spree, I did have almost the same issue, but minus the car dock. I think it was with PacMan, after every call I would lose the ability to hear or talk on the next call until a reboot. Again, now is good, except for when I use the car dock.
I also flashed Arrghs, 19 kernel with DeadCalm to fix the known screen proximity issue and borked my phone. I got a bootloop I couldn't get out of and had to use recovery.
Does this make any sense? Before every flash, I'm wiping numerous times. Any help would be appreciated!
I use no-op dock.
As to custom rom that WORK a 100% I can't find any.
My daily driver is a mildly moded Telstra stock rom.
See link below. Go to the OPs Russian site & they have a poll of popular roms. I linked to their site in same thread.
You aren't doing anything wrong as far as the "audio loss" part is concerned when using the car dock. You're using the official Motorola car dock, and the ROM developers for this phone either don't own the dock or have no interest in fixing it (nothing against them, it's extremely proprietary). The audio is just redirected and doesn't come back without a reboot.
The reason the audio is redirected is that Motorola designed it to work with their also proprietary audio/charging cable, which splits a usb charging port and audio jack out so you don't have to plug an aux cable directly into your phone when you want to hear it on your car stereo. Catch is, this never caught on, because they didn't include this splitter cable with most of the docks they sold.
The dock has a chip in it (and a crap ton of small circuitry) that tells the phone not only what dock it's on, but integrates tightly with the smart actions included by default on the phone. The custom roms are made for standard docks, or custom solutions using the resistor value tricks that Samsung is famous for. It's unlikely that we'll see more support for this type of dock system unless the new Moto X uses the EXACT same system.
To bypass this issue for me, I disassembled the car mount and removed the offending circuit board, then soldered on this breakout board (http://www.jayconsystems.com/usb-mini-breakout-board-556.html) and finagled it in there (carefully) using some of that epoxy steel stuff you see in auto parts stores. This simply made the car mount what it already appears to be: a pure pass-through. You cannot get around this issue without either disconnecting the internal circuit, removing the usb jack portion from the mount altogether, or reprogramming the offending part of the ROM you want to use (because I don't think anyone's working on it yet).
Btw, if you spend $10 or more you get free shipping, so why not throw in the OTG cable (among other random things) if you don't have one: http://www.jayconsystems.com/usb-otg-cable-female-a-to-micro-a-5.html
Donowolf said:
You aren't doing anything wrong as far as the "audio loss" part is concerned when using the car dock. You're using the official Motorola car dock, and the ROM developers for this phone either don't own the dock or have no interest in fixing it (nothing against them, it's extremely proprietary). The audio is just redirected and doesn't come back without a reboot.
Click to expand...
Click to collapse
Wow, good reply. I didn't know about the chip inside of the dock, but it makes sense since when I enter the phone into the dock it automatically goes into Car Mode.
I tried the No-Op app from the Play Store that Avi mentioned (thank you too), but car mode still started when I used the dock and of course I lost audio.
Stinks, I really like the OEM car dock. I'm in sales and rely on the GPS a lot for work. I always put the phone right into the dock as soon as I get into the car which is numerous times throughout a normal day. So no ROM's have working audio with Motorola dock? I guess I get rid of the dock or go back to stock.
perkinscl said:
Wow, good reply. I didn't know about the chip inside of the dock, but it makes sense since when I enter the phone into the dock it automatically goes into Car Mode.
I tried the No-Op app from the Play Store that Avi mentioned (thank you too), but car mode still started when I used the dock and of course I lost audio.
Stinks, I really like the OEM car dock. I'm in sales and rely on the GPS a lot for work. I always put the phone right into the dock as soon as I get into the car which is numerous times throughout a normal day. So no ROM's have working audio with Motorola dock? I guess I get rid of the dock or go back to stock.
Click to expand...
Click to collapse
I have the same problem (obviously). I have not done this yet but was thinking I would set up a Tasker task to reboot the phone as soon as it is disconnected from the dock. This phone reboots so quickly (on PAC at least) that I don't think it should interfere with much. I have just been too lazy to set it up
styndall said:
I have the same problem (obviously). I have not done this yet but was thinking I would set up a Tasker task to reboot the phone as soon as it is disconnected from the dock. This phone reboots so quickly (on PAC at least) that I don't think it should interfere with much. I have just been too lazy to set it up
Click to expand...
Click to collapse
I ended up going back to stock (almost - Deodexed 98.16.3 Base) All good so far. I had one hiccup and couldn't hear during a call, but that was only once and everything has been peachy since. Just no cool custom ROM goodies...:victory:
Just opened my atrix lapdock for the first time in a while to try it out and had a bunch of weird things happen that i havent seen listed eleswhere. Just wanted to know if anyone else seen something like this.
First, i'm running the latest Carbon nightly on my Razr HD.
Things that happened:
1) I plugged in the HDMI/USB and the phone mirrored onto the screen, however the mouse/keyboard didn't work and it wasn't charging the phone.
2) I removed the phone, checked the jacks and plugged it back in again. This time, the lapdock's backlight turned on, but nothing showed up on the screen. I ran an lsusb and it does show a device there (when i remove the usb it doesn't list anything).
I can't seem to get the phone to mirror again though. I've since rebooted the phone and tried a few other things, but i can't seem to replicate #1.
Anyone have a similar experience?
djuniah said:
Just opened my atrix lapdock for the first time in a while to try it out and had a bunch of weird things happen that i havent seen listed eleswhere. Just wanted to know if anyone else seen something like this.
First, i'm running the latest Carbon nightly on my Razr HD.
Things that happened:
1) I plugged in the HDMI/USB and the phone mirrored onto the screen, however the mouse/keyboard didn't work and it wasn't charging the phone.
2) I removed the phone, checked the jacks and plugged it back in again. This time, the lapdock's backlight turned on, but nothing showed up on the screen. I ran an lsusb and it does show a device there (when i remove the usb it doesn't list anything).
I can't seem to get the phone to mirror again though. I've since rebooted the phone and tried a few other things, but i can't seem to replicate #1.
Anyone have a similar experience?
Click to expand...
Click to collapse
That's pretty much normal on custom JB roms. You can get the phone to output to the Lapdock in a bastardized 1080p if you go to dev settings and disable hdcp -- there's a bug in the custom kernel regarding both obtaining the lapdock's EDID as well as the phone always trying to initiate the hdcp handshake even though it's really a dvi monitor with an hdmi>dvi adapter. With HDCP disabled, the phone will force output to 1080p, only the monitor is 1366x768, and due to the buggy EDID, none of FB1's (framebuffer 1...hdmi output) settings are tweakable...mainly the resolution setting like we have to use in Stock Moto JB. Sucks knowing the bug and not knowing how to fix it.
Good news is the Lapdock is reported to work just fine with Stock KitKat. Once the dev team is ready and start releasing CM11 with the 3.4 kernel, we'll finally be able to use the Lapdock with custom KK roms like we did with stock ICS.
skeevydude said:
That's pretty much normal on custom JB roms. You can get the phone to output to the Lapdock in a bastardized 1080p if you go to dev settings and disable hdcp -- there's a bug in the custom kernel regarding both obtaining the lapdock's EDID as well as the phone always trying to initiate the hdcp handshake even though it's really a dvi monitor with an hdmi>dvi adapter. With HDCP disabled, the phone will force output to 1080p, only the monitor is 1366x768, and due to the buggy EDID, none of FB1's (framebuffer 1...hdmi output) settings are tweakable...mainly the resolution setting like we have to use in Stock Moto JB. Sucks knowing the bug and not knowing how to fix it.
Good news is the Lapdock is reported to work just fine with Stock KitKat. Once the dev team is ready and start releasing CM11 with the 3.4 kernel, we'll finally be able to use the Lapdock with custom KK roms like we did with stock ICS.
Click to expand...
Click to collapse
I actually had HDCP disabled during all of those cases i mentioned. I was doing some testing on laggy playback of protected video streams via HDMI (Netflix/Xfinitity/etc. had been lagging the video stream and getting out of sync recently) and had disabled it to see if it would help. The other odd part is that now i can't even see the hub via lsusb. When i plug the phone in, the little white LED on the trackpad lights up, so it definitely sees a connection, however lsusb shows 0 results on the device. I'm wondering if maybe the small cables that go through the hinge got damaged somehow while i was messing around with it last night.
djuniah said:
I actually had HDCP disabled during all of those cases i mentioned. I was doing some testing on laggy playback of protected video streams via HDMI (Netflix/Xfinitity/etc. had been lagging the video stream and getting out of sync recently) and had disabled it to see if it would help. The other odd part is that now i can't even see the hub via lsusb. When i plug the phone in, the little white LED on the trackpad lights up, so it definitely sees a connection, however lsusb shows 0 results on the device. I'm wondering if maybe the small cables that go through the hinge got damaged somehow while i was messing around with it last night.
Click to expand...
Click to collapse
What kind of Lapdock? I have the 500 and it's unable to work in the proper resolution on custom roms since around June of last year (when Epinter's hdcp/hdmi commits started showing up in the cm kernel). When it did work, did it work with the correct resolution? Because it's in a forced 1080p with no way of changing it on the Atrix HD & any custom rom (and only then when HDCP is disabled).
The hinge cables...that would suck if that's what happened. I could see that being a difficult fix to do, though I've never taken my Lapdock apart to know if it's actually that difficult.
skeevydude said:
What kind of Lapdock? I have the 500 and it's unable to work in the proper resolution on custom roms since around June of last year (when Epinter's hdcp/hdmi commits started showing up in the cm kernel). When it did work, did it work with the correct resolution? Because it's in a forced 1080p with no way of changing it on the Atrix HD & any custom rom (and only then when HDCP is disabled).
The hinge cables...that would suck if that's what happened. I could see that being a difficult fix to do, though I've never taken my Lapdock apart to know if it's actually that difficult.
Click to expand...
Click to collapse
It's the atrix lapdock (which i believe is a different model from the 500 or 100). I had picked it up cheap for my old OG Razr and i know that it did work previously. The resolution was actually correct though. It showed up full-screen without the black bars, which was quite surprising given what i've read elsewhere. There are quite a few exposed screws on the bottom of the unit, so if i HAD to go in there and replace the cable that runs from the hub to the dock, i think i could, but i've only opened up the back-dock section to flip the jacks around to fit the HD.
djuniah said:
It's the atrix lapdock (which i believe is a different model from the 500 or 100). I had picked it up cheap for my old OG Razr and i know that it did work previously. The resolution was actually correct though. It showed up full-screen without the black bars, which was quite surprising given what i've read elsewhere. There are quite a few exposed screws on the bottom of the unit, so if i HAD to go in there and replace the cable that runs from the hub to the dock, i think i could, but i've only opened up the back-dock section to flip the jacks around to fit the HD.
Click to expand...
Click to collapse
Odd, especially since they all run at the same 1366x768 resolution, but it could simply be a case of the phone registering the incorrect EDID from the 100 and/or 500.
There isn't a single exposed screw on the 500 without removing all the rubber feet and rubber screw blocks.
Thursday needs to hurry on up and get here. It's when my replacement Atrix HD will arrive. No phone sucks.