Related
The other day, i was sitting with my trusty Thinkpad T60p and my Galaxy S and suddenly i got this idea... i want to build a Android phone into the palmrest! So now i'm just throwing thoughts out the get myself started.
It would be great to have everything Conky provides now, calendar, email and other stuff, placed on a small LCD on the laptop.
So i need to get a spare palmrest for the laptop of eBay, in case the idea doesn't really work out, and a Android phone i can play around with. It seems as Windows Mobile phones are cheaper 2nd. hand, and as i don't really need the phone part of the phone to work, it might be the way to go. So what WinMo phones are good enough to run Android to get: booting into Android without user interaction, touchscreen and hardware buttons, maybe wifi and 3G, but only it it's good enough to provide a access point, USB net and Android 2.x?
What native Android phones should i look for? I think i'll need the hardware buttons to be on a separate PCB, a small (2,8" to 3.2") screen. CPU and memory isn't really that important. Also the LCD and main PCB needs to be quite flat. If i had brought a screwdriver to school, i could have measured just how flat.
Is there a launcher that can do everything in landscape mode?
Have anyone done something similar to this? Build a Android phone into anything else?
I need to modify the battery circuit to make to phone run of the laptop battery, as i don't think i can find internal room for it and connect the USB port in the phone to the internal USB header where my fingerprint reader isn't going to be anymore.
Hey guys,
I have an evo that has a weird glitch with the USB port.
It seems, anytime the weather is humid, my phone will sparatically start switching in and out of car-mode repeatedly. This has been causing my phone's cpu use to spike, screen to turn on randomly, and worst of all - when the phone is in car mode, I lose control of changing media volume with up-down switch, it forces dock volume.
From what I've found online, car mode is enable/disabled with the 4th pin going to ground in the USB port, which apparently my phone has been finding a way to bridge sporadically.
There are plenty of solutions that say 'delete the apk for the car mode app', but it'll still make me lose control of audio volume, and always be in speaker mode in calls.
Other than this problem, my phone works perfectly normal.
So, is there a way to prevent this pin from being picked up by the kernel or have android completely ignore this event or intent?
If I knew it was in the kernel source code (and where), I wouldn't mind learning how to cook a kernel myself to do it.
Thanks for any help.
MrStabby said:
Hey guys,
I have an evo that has a weird glitch with the USB port.
It seems, anytime the weather is humid, my phone will sparatically start switching in and out of car-mode repeatedly. This has been causing my phone's cpu use to spike, screen to turn on randomly, and worst of all - when the phone is in car mode, I lose control of changing media volume with up-down switch, it forces dock volume.
From what I've found online, car mode is enable/disabled with a 5th pin going high in the USB port, which apparently my phone has been finding a way to bridge sporadically.
There are plenty of solutions that say 'delete the apk for the car mode app', but it'll still make me lose control of audio volume, and always be in speaker mode in calls.
Other than this problem, my phone works perfectly normal.
So, is there a way to prevent this pin from being picked up by the kernel or have android completely ignore this event or intent?
If I knew it was in the kernel source code (and where), I wouldn't mind learning how to cook a kernel myself to do it.
Thanks for any help.
Click to expand...
Click to collapse
I have this issue as well and have been trying to figure it out. Currently have something close for aosp roms, but going to take more time to figure out for sense. I have been looking into it.
Wow, I thought it was just me/my phone.
github said:
Wow, I thought it was just me/my phone.
Click to expand...
Click to collapse
nope we should start our own club. Busted ass usbport club. I looked into swaping the port out and soldering on a new one. But after I looked at this little tiny piece of hardware, I though a software edit will be easier. And it is you need some intense tools to pull off a good swap. its sooooo small.
lithid-cm said:
I have this issue as well and have been trying to figure it out. Currently have something close for aosp roms, but going to take more time to figure out for sense. I have been looking into it.
Click to expand...
Click to collapse
Thanks, I figured it's a common problem but it would be nice to find a good solution.
I haven't seen too much of a connection with particular roms causing the issue. When it was originally a big problem a few months back (before it stopped happening for me), it would act the same way on every rom I stuck on it.
However, I just switched from deck's aosp rom to Synergy not long before this started happening again, and the sense roms definitely make it much more of an apparent problem than the AOSP roms would.
Physically to stop the problem, I know it's related to the MicroUSB port and I may try disassembling it if it gets bad enough.
From another post on it: "It's pin 4, not 5 , 5 is ground in the usb cable, when pin 4 is grounded it puts the unit in dock mode."
I'd post a link to the pinout, but the system makes me too newb to post pin outs. (Just google kineteka microusb b)
The same thing happened to my phone yesterday and it is pissing me off. Will it eventually go away over time or is it a permanent issue. Meaning when it dries off will everything be ok. I'm thinking about taking it in since I have insurance and see if they will either fix it or swap it out. I'm going to wait a couple of days to make sure there is no moisture in there.
There is an app called NoDock that you can download to fix this. In my experience, it does not work with MikG (which is probably a Sense 2.1 compatibiltiy issue). I am running Deck now too, and so far no issue with the AOSP ROM. If there is an issue, I read on the NoDock market page that CM based ROMs have an option to disable, and thus NoDock is not needed in this case.
Hmm. I'd think an app could be written that would catch the intent and do nothing, as well as manually adjust car dock volume via the volume controls. Maybe. But I don't think any kernel-level edits are needed. Maybe a decent dev can write something like that for you (I couldn't). [Edit: looks like NoDock might be that app] Another thought that might be stupid: have you taken a can of compressed air to your USB port?
Also, just a friendly reminder, there isn't any development work posted here so instead of the development subforum, this really belongs in General, or maybe Q&A. As a general rule, new threads in this section are only for sharing work you've done. Not to pretend I'm a mod or anything, just wanted to warn you so you don't get flamed to death next time.
In sense roms might be able to check AndroidManifests for either
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_DOCK
or
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_MODE
Then remove the intent from the application, so that nothing would happen.
lithid-cm said:
In sense roms might be able to check AndroidManifests for either
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_DOCK
or
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_MODE
Then remove the intent from the application, so that nothing would happen.
Click to expand...
Click to collapse
I was definitely looking into this within the android.policy.jar but my developer knowledge is minimal compared to your expertise. I'm really hoping to not have to download any apps and I'm reluctant to go get an insurance claim until the new OTA has been rooted successfully. Anybody makes any move forward on this I would be glad to donate. This started happening to me when I was working out with my phone in an armband and some sweat most likely got into the charger port causing a short (my theory on what happened). If it is still going on by the time the OTA gets rooted, I'm going to go swap it out at the Sprint store.
mjhuffer said:
I was definitely looking into this within the android.policy.jar but my developer knowledge is minimal compared to your expertise. I'm really hoping to not have to download any apps and I'm reluctant to go get an insurance claim until the new OTA has been rooted successfully. Anybody makes any move forward on this I would be glad to donate. This started happening to me when I was working out with my phone in an armband and some sweat most likely got into the charger port causing a short (my theory on what happened). If it is still going on by the time the OTA gets rooted, I'm going to go swap it out at the Sprint store.
Click to expand...
Click to collapse
I am actually looking to buy a rooted one on ebay. Then use this one for deving. I really like the evo no reason to let it go yet.
lithid-cm said:
I am actually looking to buy a rooted one on ebay. Then use this one for deving. I really like the evo no reason to let it go yet.
Click to expand...
Click to collapse
I thought it was illegal to sell rooted phones period. Or is it only illegal to make extra profit just based on the fact that it is rooted. That isn't to say that someone will do it anyways. My brother, who is phone illiterate, just got a nexus s and I really like it. I heard that the GSM version will be the first phone to get ICS (ice cream sandwich) so that means the CDMA one will be next. I'm perfectly happy with my EVO except when dumb stuff like this happens. I hate myself for asking but you got any progress on the rooting of 4.24 and the newest Hboot. Has the source code for the new Hboot been released?
I had a similar problem however it was caused by me putting my phone in my car dock
I had to freeze/uninstall both car panel and dock mode for it to finally stop giving me a notification and blinking the screen on and off when I hit bumps
Soldering USB port
lithid-cm said:
nope we should start our own club. Busted ass usbport club. I looked into swaping the port out and soldering on a new one. But after I looked at this little tiny piece of hardware, I though a software edit will be easier. And it is you need some intense tools to pull off a good swap. its sooooo small.
Click to expand...
Click to collapse
Had the USB issue on mine too.
Usb port is anchored down to circuit board in 4 places, those solder joints get
loose and the trouble begins.
I used a regular soldering iron to heat up the solder and bring the port back against the circuit board tight, no more car-mode.
Ed
chile62 said:
Had the USB issue on mine too.
Usb port is anchored down to circuit board in 4 places, those solder joints get
loose and the trouble begins.
I used a regular soldering iron to heat up the solder and bring the port back against the circuit board tight, no more car-mode.
Ed
Click to expand...
Click to collapse
I appreciate the response and im looking into it myself but what exactly do those points have to do with the electronic conductivity of the port? Do they have something to do with the ground.
odd, i had this same problem, what fixed mine was flashing a new different nv, it stopped it almost immediately
MrStabby said:
Hey guys,
I have an evo that has a weird glitch with the USB port.
It seems, anytime the weather is humid, my phone will sparatically start switching in and out of car-mode repeatedly. This has been causing my phone's cpu use to spike, screen to turn on randomly, and worst of all - when the phone is in car mode, I lose control of changing media volume with up-down switch, it forces dock volume.
From what I've found online, car mode is enable/disabled with the 4th pin going to ground in the USB port, which apparently my phone has been finding a way to bridge sporadically.
There are plenty of solutions that say 'delete the apk for the car mode app', but it'll still make me lose control of audio volume, and always be in speaker mode in calls.
Other than this problem, my phone works perfectly normal.
So, is there a way to prevent this pin from being picked up by the kernel or have android completely ignore this event or intent?
If I knew it was in the kernel source code (and where), I wouldn't mind learning how to cook a kernel myself to do it.
Thanks for any help.
Click to expand...
Click to collapse
loose usb port
mjhuffer said:
I appreciate the response and im looking into it myself but what exactly do those points have to do with the electronic conductivity of the port? Do they have something to do with the ground.
Click to expand...
Click to collapse
The 4 points only hold the usb plug on to the board, on the backside of the plug, is where the actual connections are being made. They are almost like spring loaded connections.
When the soldered points get weak, the usb gets pulled pulled away from the mother board and some of the pins will not make contact.
Ed
Here is a kernel for CM7 removing dock accessory detection based on the latest CM7 kernel. If someone wants to build a version for Sense or based on another kernel, just unselect config_usb_accessory_detect and config_dock_accessory_detect support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
This is crazy mine an my girls phones are doing this we bought a charger off of eBay an that's when it started I tried titanium pro an froze car mode seems to work but just a bandaid
Sent from my PC36100 using XDA Premium App
sbradymobile said:
Here is a kernel for CM7 removing dock accessory detection based on the latest CM7 kernel. If someone wants to build a version for Sense or based on another kernel, just unselect dock support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
Click to expand...
Click to collapse
Thanks man I'm going to wait for some dev to jump on this. Hopefully someone can create a .zip so you can flash it over any kernel. I would really just like the stock kernel with this option added in.
After I got my skyrocket, many of my friends and family also decided on the skyrocket Well, now it's up to me to make sure they're all in working order.
So one of my family members left her skyrocket in a bag of water for a while while she was at the beach, and it was completely unresponsive. I fully disassembled it (not my first time), dried out the majority of the water, then left the phone in rice for a few days. The good news is, the phone boots up and seems to work. The battery still works and it charges over USB.
The bad news is, the cellular radio does not work, IMEI comes up as unknown, bluetooth mac is "unavailable", front facing camera is also unresponsive. Really bad news: data/adb over usb does not register at all. A few more days in rice haven't helped.
The phone is completely stock. My first thought was that flashing a new radio might reset the cellular somehow, but not having cwm/odin makes that impossible. I can't seem to get the phone into download mode either because of the USB problem.
One thing that DOES work is the stock recovery. I can tell it to flash the official ATT ICS build, which contains a radio!
However when I try flashing it says.. "E: Short write of /tmp/sideload/package.zip (No space left on device) Installation aborted". Other zips "failed to verify whole-file signature"
Any ideas? My next step will be buying a used skyrocket with a cracked screen, and transplanting the working screen from this unit...
Tom
First off, please use the Q&A section for, you know, questions and answers. Don't create a new thread; I'm going to ask the mods to move this one instead.
Second, your issue is that the hardware radio is dead. The stock ROM only has a software radio included. To put it a different way, the stock ROM includes programming that tells the cell radio what to do. It can't fix the cell radio if it's broken, though. Unfortunately, based on the amount of damage you've got there, I'd say your phone is pretty much toast.
If you're completely stock, try to warranty it out. Just be up front with Sammy about what happened (because, in this instance, they will figure it out if you make up a story or play dumb), and the worst thing they can say is no. You might get a sympathetic rep who'll help you out. If they won't take it, you've already got your backup plan in the working SR.
T.J. Bender said:
First off, please use the Q&A section for, you know, questions and answers. Don't create a new thread; I'm going to ask the mods to move this one instead.
Second, your issue is that the hardware radio is dead. The stock ROM only has a software radio included. To put it a different way, the stock ROM includes programming that tells the cell radio what to do. It can't fix the cell radio if it's broken, though. Unfortunately, based on the amount of damage you've got there, I'd say your phone is pretty much toast.
If you're completely stock, try to warranty it out. Just be up front with Sammy about what happened (because, in this instance, they will figure it out if you make up a story or play dumb), and the worst thing they can say is no. You might get a sympathetic rep who'll help you out. If they won't take it, you've already got your backup plan in the working SR.
Click to expand...
Click to collapse
Meant to post this in Q&A, woops. Too many xda tabs open trying to figure this out. Sorry about that
I do know the difference between the hardware/software radios... My thought was that while the phone was turned on and submerged, the software radio could have become corrupt... A long shot perhaps
I'll try contacting samsung, but somehow I doubt they'll cover it. Sidenote, do you really think they have a more sophisticated way to check for water damage than the internal water-damage indicator sticker?
The question still stands though, if anyone is interested. Even without a cell radio, I'd like to be able to root it for other purposes
Thanks for the advice
Tom
dutchthomas said:
Meant to post this in Q&A, woops. Too many xda tabs open trying to figure this out. Sorry about that
I do know the difference between the hardware/software radios... My thought was that while the phone was turned on and submerged, the software radio could have become corrupt... A long shot perhaps
I'll try contacting samsung, but somehow I doubt they'll cover it. Sidenote, do you really think they have a more sophisticated way to check for water damage than the internal water-damage indicator sticker?
The question still stands though, if anyone is interested. Even without a cell radio, I'd like to be able to root it for other purposes
Thanks for the advice
Tom
Click to expand...
Click to collapse
Yeah, based on the amount of things going wrong, it's hardware. If the software radio was corrupt, it would be because the internal storage had been corrupted, and your phone likely would not boot.
And yes, they can find water damage beyond the sticker. They can see corrosion plain as day when they open it up and look at the internals.
You can root it without USB working. Is your wifi working? If so, download GooManager off the market, then follow the instructions in the TWRP thread to get TWRP on your phone. Download a custom ROM to your PC, then transfer it to your external SD using an adapter/card reader so you can place it on the card directly (instead of going through the USB port). Use TWRP to flash the pre-rooted ROM onto your phone and viola. Unless there's a pre-rooted stock out there (and I don't think there is for SR), a custom ROM is the only way I can think of to do it.
Be advised, though, that because of the amount of damage done to your phone's internals, there's a better-than-normal chance that something won't work and you'll brick. I'm not responsible for your decisions or for the brick if that happens.
Long story short, just get a replacement SR.
Same thing happened to my girls Atrix. She gave it a nice bath in Green Tea. After shutting it down and pulling it apart I gave it the rice treatment for 48 hours. Booted but returned a radio error. Her USB port was working so I was able to root it and install a few custom ROMs on it. No change. So I would bet you actually fried the chip. Call Sammi and get a quote to cover the repair which will be a new mobo. They pay shipping both ways and are usually pretty cheap.
hechoen said:
Same thing happened to my girls Atrix. She gave it a nice bath in Green Tea. After shutting it down and pulling it apart I gave it the rice treatment for 48 hours. Booted but returned a radio error. Her USB port was working so I was able to root it and install a few custom ROMs on it. No change. So I would bet you actually fried the chip. Call Sammi and get a quote to cover the repair which will be a new mobo. They pay shipping both ways and are usually pretty cheap.
Click to expand...
Click to collapse
Heh, this is my mother's phone actually. First she ripped the screen ribbon cable on a nokia E75. Then she smashed her Atrix's screen, tried to fix it herself with a new screen, and managed to rip part of a ribbon cable... so it no longer has a working touch digitizer. Now she left her skyrocket in a bag of water. The girlfriend managed to crack her skyrocket's screen, which I replaced... I've also had to fix 2x nokia N95's, an N97, and a bunch of water damaged dumb phones over the years...
FWIW, the skyrocket seems to have the best repairability / internal layout of any of the phones I've messed with
The cracked screen skyrockets on ebay seem to be going for more than I thought, so I'll be giving sammy a call for sure
Well I have been a owner of a LG Nexus 5 for the past (almost) 2 years now, in fact I am coming to the end of my contract very soon and will be able to either goto another company or get a new phone.
Anyways, sometime ago I experienced a problem with my microphone and external speakers not working, or at at least some of the time... After a bit of research online I found out my problem was related to a connection inside the phone that connected the bottom assembly to the main board at the top of the phone. It required me to remove the back panel and a few screws to remove the plastic cover, but the poster suggested putting some tape on top of that connection to hold it down more firmly to the socket it connected too. So I did this. I put some black tap (electrical tape cut to fit.) on top and then assembled the phone again. Viola, It worked!
Well, a short time after I decided that I wanted to update my phone from stock kitkat (4.4.4). Always been curious about custom ROMs and gave Cyanogenmod a try. Not only that I got bold and tried the nightly releases of the new marshmellow update. After some time I started experiencing things not working, like the camera, and a lot of freezing, hang ups and random reboots (not so much the reboots as the constant freezing). Often I couldn't get anything on the screen or the phone to respond from a locked state and when I did, often the phone would lag so much, that doing anything would take a long time and proved to be impossible.
I started thinking it was the nightly releases as the source of my problem and just kind of shrugged it off and figured "they will eventually fix the problem". I kept this thinking for quite some time. But it occurred too me one day that something else was causing the issue I was facing for the simple fact that the lag started showing up in the recovery mode (also custom) and a lot of times would continue to show up after I rebooted my phone. Hence, would rule out any 'software' issues I was facing.
I began to think that my problem was hardware. Maybe it was just time for a new phone. But still months away from the end of my contract, this meant I would have to pay off the 'problematic' phone first before getting a new one. I really didn't like that idea. So while looking into this problem, in a last ditch effort, I opened my phone again. Dunno why but I also decided to get rid of the tap on the connection I tried to fix before... I popped off the connection there and had a look at it. It didn't seem damaged in any way nor did the socket. Strange as it was I put that connect back in the socket and put the cover plate back on making sure not to torque the screws and assembled everything back up....
Now the mic and ext speakers work just fine and the phone is working like I just opened the box and took it out for the first time. And I have not once seen any problems... I understand what's happening here... still just wanted to share that for it was definitely weird or what?
https://drive.google.com/open?id=0B0pUNVcVRCJ7MThMc0NHLUNkSEU
Sorry about the link, only way I can upload an image.
Just so there is no confusion... an image of the effected area, inside the phone. The arrow points to the connector and more importantly the area of the connector that seems damaged. If I press lightly where the arrow is pointing on this image, the assemable at the bottom (speaker/mic) will work, indicating a loose connection. Although after visual inspection, I cannot see any damage to connector or the socket. I suppose the only way to really "fix" the issue is to order a new part. As stated previously, already tried tape on the socket to help hold it down, but that seem to cause just as many issues with the phone performance. Any other suggestions?
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Does anyone else have issues with there ext. speaker and mic not working?
An update on the phone;
back to square one. My ext speaker and mic will not work. And that socket has something to do with the LCD connection on the screen as it will black out if just the right area on the back of the phone is pressed. Only way to revive the phone is to long-press the power button for a reboot. Then will come up fine but speaker and mic still do not work.
audit13 said:
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Click to expand...
Click to collapse
Wow, that sounds pretty low level tactics of LG... just shameful really, but not hard to believe these days...
Quite honestly, I am just going to replace the phone. Think I got a pretty good run out of it and think its pretty well time for an upgrade. Anyway, for the reason I got the phone, it wont matter the speaker and mic don't work. Just going to use it for development and it will be a good test device.
Oh an this post is related to this thread so I thought I would link it for it may help someone else facing similar problems....
https://forum.cyanogenmod.org/topic/125227-nightly-cm13-releases-make-my-nexus-5-very-slow/
I'm not sure that LG had anything to do with the low-quality replacement parts.
If I were you, look for a n5 with a smashed screen that is suitable for parts.
audit13 said:
I'm not sure that LG had anything to do with the low-quality replacement parts.
If I were you, look for a n5 with a smashed screen that is suitable for parts.
Click to expand...
Click to collapse
Good idea, except the iphone is the most popular phone around here ... find it pretty hard to find one, been looking. But thanks.
I have seen quite a few busted n5 phones in Toronto. I have managed to get working phones with a smashed screen for as little as $30 which is rare for Toronto. Average I pay is $40 to $50. For this price, I either use the phone for parts in several phones or I get third part screen from Aliexpress for around $40 CAD.
I just want to update this as well...
I am fairly certain (now thinking about causes) its not really a design flaw, but more so because I frequently sat on my phone when it was in my back pocket...
audit13 said:
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Click to expand...
Click to collapse
It was not me but I had that same experience. Replaced with a cheap oem and it didn't charge after that.
I found out why. The charger usb socket was not connected to anything ! Unbelievable! It lacked the black plastic backing for that part of the cable to connect to.
I've got two OnePlus Ones sitting in front of me:
1) Physically in mint condition (not a scratch on it, never been dropped, flip case from day1, etc), my original phone that has (as far as I'm concerned) a faulty flash storage chip. It kept committing suicide whenever the bad part of the flash got "touched". Eventually hard bricked itself, and all the ColorOS based recovery tools kept getting stuck with the dreaded "Sahara" error nobody seemed to know how to get past. I consider repairing this a lost cause directly.
2) My girlfriend's old phone. Physically, pretty beat up. Corner of the screen is cracked slightly, but it still works - although the touch screen is a bit flaky on detection. No problems with the storage chip, never had any OS issues. Presently just installed the latest Resurrection Remix rom on it.
My question is simple. Can I transfer the basic guts from phone #2, into phone #1? I've been skimming through various tear down guides - it looks like a pain to disassemble, but doable.
I'm hoping none of the hardware is married?