Database Users

Car Home starting at random

Hi @ll,
I have the following problem with my DHD (Cyanogenmod 7.2). Since a few weeks ago the "Car Mode" App is starting many a time and ususally even restarts again after closing it. After having searched in several discussion boards I found out that the signal for the Car Mode getting started is emitted by some kind of magnetic sensor or the like, suited to the car charching cradle. Though because I have none, I assume that there's a loose contact or something at that magnetic sensor, but to fix it, I initially have to know where it is. Can someone help me please?
Thanks in advance.

Try to clean your usb port. A friend had the same problem and that helped.
Sent from my Desire HD using xda app-developers app

Fix permission in recovery..maybe it should help...
Sent from my Desire HD using Tapatalk 2

Thank you, I tried both methods. Now I'm waiting for it to happen again or not.
What did the "Fix permissions" function actually do?

So it helped?
Sent from my Desire HD using xda app-developers app

Yea, seems as if one of your both suggestions has helped

Hello there.
I did the "fix permissions" but it didn't help.
How did you guys clean the USB port?
Regards,
F.

Just clean it with compressed air from a compressor and use contact spray if needed.

Reflash
i had the same problem with jellytime.... i just reflashed the rom again and it went away .... hope it helps...

sometimes car home starts to pop up when it came in contact with any magnetic thingy..
If Car Home is going off without being near anything magnetic then you may have a bug. It's a very easy fix. Root your phone and download a app called Bloat Freezer. That just freeze car home and every other piece of bloatware you will never use.
---------- Post added at 01:47 AM ---------- Previous post was at 01:39 AM ----------
Also u can use app like :
"Dock No-op" or
One more app is there named "Do Nothing "whenever it pop up it just block that happening. Just seach this on play store. I hope might help.

moizeali said:
sometimes car home starts to pop up when it came in contact with any magnetic thingy..
If Car Home is going off without being near anything magnetic then you may have a bug. It's a very easy fix. Root your phone and download a app called Bloat Freezer. That just freeze car home and every other piece of bloatware you will never use.
---------- Post added at 01:47 AM ---------- Previous post was at 01:39 AM ----------
Also u can use app like :
"Dock No-op" or
One more app is there named "Do Nothing "whenever it pop up it just block that happening. Just seach this on play store. I hope might help.
Click to expand...
Click to collapse
I did all the thing read here and on other forums ( freez carhomeGoogle.apk , delete from system/app , full wipe format , reinstal rom , even downgrade to gb , and now i'm back to ics , cleaning the charging slot ) car home does'nt open but the icon on notification still appears and dissapears randomly and my screen goes on and off all the time )
sorry for my bad english

I had this issue and the only way to fix was to replace the micro-usb port as it kept coming back.

replacing the micro-usb port usally helps.

Against all rumors,
the CAR home is started if the right resistor values are applied between certain USB contacts. No magnetics or magic needed.
To get rid of the problem no magic is needed either:
Take a wooden toothpick and crush one tip until you have kind of flat brush of about 4mm length, but as flat as possible.
Then take this 'wooden brush' and scratch all dirt out of the usb port. Be carefull not to apply presure to the small contact bridge in the middle.
Other than the name suggests, please do not use your teeth to form this brush. Humidity and electronics are not so compatible...
Best way:
It is easy if you just brush out the dirt by going in, brush, out allways the same way, collecting the dust in one edge.
Try to collect the dust in one edge of the connector on the lower wide area corner.
Then push it out with the intact side of the toothpick.
Never try to use the intact tip in the small area above the connector bridge. It will break it.
After that, Car Panel should stay closed and your USB cable shouldn't fall off anymore.
Astralix

[Q] Broken Screen Challenge

Hey guys,
So I've been loving the crap out of my nexus 4... that is, until a random stranger on a crowded subway knocked it out of my hands as I was taking it out of my pocket. So the front of the screen is messed up pretty bad glass-wise; the lcd works fine but the digitizer is messed up so I can't use the touchscreen at all.
I'm going to have to shell out on a new screen soon, but I'd like a workaround in the meantime. I figured if I could get a bluetooth mouse connected I could at least navigate around my phone, but of course I need to use the touchscreen to pair with the mouse. Or maybe not, that's why I'm posting.
Can it be done? Through adb or some other means, could I pair a bluetooth mouse without using the phone directly? The only method I could think of might be to pull the bluetooth address config file and insert the MAC address of the mouse into it to potentially trick the phone into thinking it had already paired with it. Does that make sense? Even if it does, I'm most likely going to need some guidance in figuring out how to actually pull it off.
Let me know if it can be done somehow, and thanks! :fingers-crossed:

should have knock the guy out and drop his phone...sound like a fair deal...eye for an eye
Sent from my Nexus 4 using xda app-developers app

pak-stars said:
should have knock the guy out and drop his phone...sound like a fair deal...eye for an eye/QUOTE]
Ha ha maybe I would've, but the station was so busy that I couldn't tell who bumped into me... It was on an inclined walkway so the phone actually slid away from me by a few feet, by the time I got it whoever did it was long gone
Click to expand...
Click to collapse

Use the play store webside to load a remote desktop app on it so you can take over it's screen (assuming those apps exist and it's not stuck at the PIN entry screen)

I haven't found any screen sharing/control apps that don't require me to use the phone to generate a code/url, but I'll keep looking

well I figured it out... for future reference you can use the input keyevent lines to navigate around the phone. It's a bit tedious but it's only until I connect it to a bluetooth mouse

Recovering photos from cracked phone

I have a Galaxy S5 that belongs to my brother which has a cracked screen. It powers on fine and recently factory resetting itself but can't see the screen. I'm trying to recover photos from the device of my brothers son during the first year of his life. The photos are very important to him and I'm trying my best to recover them.
I'm using MobileEdit Forensics and other recovery software but having problems connecting to the device. I'm thinking it's because of USB debugging isn't enabled. Is there a command of the line code I can run to enable it?
Would replacing the screen be any benefit to me? Am I taking the right approach?
Thanks in advance for any help given.

Do you know if touching any part of the screen has any effect (even of you can't see what touching it does)?
Replacing the screen is an option, but it's an expensive option if there are other things that might/could work instead.
The reason I asked about whether the screen is still responsive is because if it is, you can simply get an MHL adapter from somewhere like ebay and use it to connect your device to a TV so that whatever is on the phone screen (even if you can't see it) will be on the TV screen. Then you can perform the retrieval from the phone by looking at the TV screen.
The MHL adapter I got to use with my phone cost me £5.

The galaxy s5 don't have a digitizer so probably if the screen is dead,then the touch function is too(as I know from my brothers note 3 witch has the same mechanism for the screen).
You said you did a factory reset on the phone.. If you did, wouldn't those pictures be deleted?
A good option is to try Samsung back up (I think it backs up pictures too) or other back up software the phone may have..
Another thing to try is if the phone have adb enabled then you could unlock it by:
Powering it on
Let it auto connect of to a wifi you have already given the password for it when the phone was workings (if WiFi was enabled last time the phone worked)
Log it to Samsung website and apply the'unlock my phone' option
Then connect it to the PC and obtain the pictures...
Tryed to see if the pictures are located in the SD card?
If nothing of this works then the only solutions remaining are repairing the screen or get it to a data recovery company..
Hope I helped you and good luck with it

Uh...The S5 *does* have a digitizer....In exactly the same way that *every* other touchscreen device ever produced does.

keithross39 said:
Uh...The S5 *does* have a digitizer....In exactly the same way that *every* other touchscreen device ever produced does.
Click to expand...
Click to collapse
It doesn't.. It reads touch events directly from the amoled screen.. The digitizer is just a glass for the s5.. It does nothing, the phone can work too if you just remove the glass and it reads touches normally

The digitizer is the part of the screen that tells the device *where* the screen was touched ie the 'grid reference' of the interaction. If the S5 doesn't have a digitizer, what replaces it...without the digitizer how is the S5 going to know what to do when you touch the glass at a specific point...which app/function is being selected at any given location on the display if the device can't tell the location of the touch?
---------- Post added at 09:01 PM ---------- Previous post was at 08:51 PM ----------
The digitizer part of the screen exists...pure and simple. It is usually bonded to the underside of the outer glass panel.
If as you say, the touch works without the glass, then it's built into the amoled display....but it *is* present and a part of the screen, regardless of what part of the screen module it's built into.
That *may* well have implications for the touch functionality.
If it's just the 'backlighting' that has failed, but the touch functionality remains, then connecting the device to a TV via MHL should work.
If the screen is totally dead, an MHL connection will be pointless, and a new screen is probably the only option. But as has already been mentioned, if a factory reset has been performed, the chances are that what you are trying to recover has already been erased.

Fingerprint reader once a day not working

Hi guys. At least once a day I take my phone out of my left pocket and the fingerprint reader doesn't work. I have to press the power button and then it works perfectly fine until the next time. I always put the phone in my pocket without anything else. Anyone else getting the same bug???

Same bug here. Only happens after the phone has been in my pocket for awhile.
Sent from my PH-1 using Tapatalk

crawldit said:
Same bug here. Only happens after the phone has been in my pocket for awhile.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Did you find anything that helps? I'm on my second device and it too has the same fingerprint reader glitch.

mhajii210 said:
Did you find anything that helps? I'm on my second device and it too has the same fingerprint reader glitch.
Click to expand...
Click to collapse
A single press of the power switch does the trick, like you said. I don't have any other solution. I'm surprised more people haven't mentioned this considering most people carry their phones in their pockets.
Sent from my PH-1 using Tapatalk

crawldit said:
A single press of the power switch does the trick, like you said. I don't have any other solution. I'm surprised more people haven't mentioned this considering most people carry their phones in their pockets.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
https://www.reddit.com/r/essential/comments/709dph/ph1_issues/
I found a few other users reporting it, but it doesn't seem to be widespread. My guess is somehow the friction created in the pocket is messing up the fingerprint scanner.

Display side facing towards leg
I searched the web and there seem to be many different phones with this problem. One suggestion was to put the phone in the pocket with the display side facing towards the thigh. I'm going to try that suggestion and see if it works. I would highly recommend you give that a try too. Since it never glitches when I have it sitting on my desk, there is something weird going on in the pocket.

Anything metal in your pocket?
The pins affect the fingerprint reader.
Support told me it's normal and to not put my phone on a metal surface if it bothers me so much.
-_-

JCBomb said:
Anything metal in your pocket?
The pins affect the fingerprint reader.
Support told me it's normal and to not put my phone on a metal surface if it bothers me so much.
-_-
Click to expand...
Click to collapse
I have no metal in my pocket. So far putting the phone with the display side towards my leg in the pocket seems to be working (knock on wood). Normally by now it would have acted up. It's crazy but somehow putting it in my pocket with the fingerprint reader facing towards my leg has the same effect as putting the device on a metal surface. Maybe I'm a cyborg and nobody told me???

mhajii210 said:
Hi guys. At least once a day I take my phone out of my left pocket and the fingerprint reader doesn't work. I have to press the power button and then it works perfectly fine until the next time. I always put the phone in my pocket without anything else. Anyone else getting the same bug???
Click to expand...
Click to collapse
Define doesn't work. It knows that you are pressing it but makes you enter your passcode. Or it doesn't register at touch at all. Sometimes mine after being in my pocket will have me enter my password. I haven't experienced an issue where it doesn't register a touch.

swagglepuff said:
Define doesn't work. It knows that you are pressing it but makes you enter your passcode. Or it doesn't register at touch at all. Sometimes mine after being in my pocket will have me enter my password. I haven't experienced an issue where it doesn't register a touch.
Click to expand...
Click to collapse
It's crazy but putting the phone in my pocket with the display facing my leg has solved my problem. By "doesn't work" I mean it's completely dead. The fingerprint sensor wasn't detecting my finger (no vibration). It's the same exact thing that happens if you put the phone down on a metal surface, but obviously I don't have any metal in my pocket.

mhajii210 said:
It's crazy but putting the phone in my pocket with the display facing my leg has solved my problem. By "doesn't work" I mean it's completely dead. The fingerprint sensor wasn't detecting my finger (no vibration). It's the same exact thing that happens if you put the phone down on a metal surface, but obviously I don't have any metal in my pocket.
Click to expand...
Click to collapse
Interesting, I haven't experienced that issue. Maybe I will face my screen out in my pocket and see if I can recreate this on my device.

My finger print reader won't unlock my phone now. It was working fine until yesterday. I tried restarting, turning it off but nothing seems to work.
It won't let me add another fingerprint either. I get some type is cryptic error message.
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
liquidDroid said:
My finger print reader won't unlock my phone now. It was working fine until yesterday. I tried restarting, turning it off but nothing seems to work. If I press the power button then the fingerprint reader works.
It won't let me add another fingerprint either. I get some type is cryptic error message.
Click to expand...
Click to collapse

I'm also noticing fingerprint problems. I'm seeing both unresponsive (not registering anything) an also failed attempts (vibrates but does not unlock). This seems to happen randomly about once a day.
---------- Post added at 02:11 PM ---------- Previous post was at 02:06 PM ----------
Side note:. I just tried to add my another fingerprint to the phone, and upon the first press on the reader I'm getting "enrollment not complete" every time I try to add.

I've been having issues with fingerprint reader also.
Says "finger moved too fast"
or "couldn't process, please try again"
I factory reset the phone, and it worked ok, for about 24 hours.
Hasn't been a problem on my Pixel
Sent from my PH-1 using XDA Labs

I also have problem with fingerprint.
It does not detect my finger 50% of the time (no vibration and if the screen is on I get message "couldn't process fingerprint, please try again").
Factory reset didn't help.
Is it a faulty hardware?

I have had mine for almost 3 weeks and I never put it in my pocket. It is either in my holster on my belt at work or in my purse. Many times it does not work. Even laying on the table by my chair it doesn't work. My 2 year old Nexus 6P worked perfect every time. Getting to be a pain.

Odd.. mine works great.. first time setting it up on a phone and am so impressed how quick it works.. how did you set it up.. i retrained mine after noticing that i only placed a part of my finger on the sensor sometimes.. after that it was great.. added another finger after so both hands could unlock..
Sent from my PH-1 using Tapatalk

I came from the Nexus 6P which worked flawlessly each and every time. I set this one up the same way but the PH 1 takes a few times to accept the finger prints when setting it up. And does not always work every time. I have set up two first fingers and neither of them work but about half the time. I am hoping an update will fix that.

A question for a new LCD Display

Hi
I bought a new screen and installed it but the touch did not work then I installed another screen and the touch did not work
What is the problem with solving it?

I'd say if two different screens have the same issue, it's the hardware problem with the phone itself. Could be the connector for the ribbon cable - if you have a magnifying glass or visor, see if you can find anything wrong with it. Try cleaning it (compressed air is the safest way, but sometimes a wooden toothpick works well, if you are careful). Also, make sure the adhesive "flaps" on both sides of the connector are properly attached to the grounding shield. Other than that, I have no other suggestions for a DIY fix...

mamdooh191 said:
Hi
I bought a new screen and installed it but the touch did not work then I installed another screen and the touch did not work
What is the problem with solving it?
Click to expand...
Click to collapse
Some have lost touch when they messed up flashing or when Essential Sep update had a problem, as I recall, I think they fixed it by side loading an OTA image. Research this first yourself (might be on reddit etc)
---------- Post added at 05:22 AM ---------- Previous post was at 05:10 AM ----------
Seems like it was Oct update, I was thinking of
https://forum.xda-developers.com/essential-phone/help/phone-lose-touch-flash-oct-update-t3849787

IronRoo said:
Some have lost touch when they messed up flashing or when Essential Sep update had a problem, as I recall, I think they fixed it by side loading an OTA image. Research this first yourself (might be on reddit etc)
---------- Post added at 05:22 AM ---------- Previous post was at 05:10 AM ----------
Seems like it was Oct update, I was thinking of
https://forum.xda-developers.com/essential-phone/help/phone-lose-touch-flash-oct-update-t3849787
Click to expand...
Click to collapse
Hi
Thank you brother for your reply
Do I install a new image from the mobile site?

kt-Froggy said:
I'd say if two different screens have the same issue, it's the hardware problem with the phone itself. Could be the connector for the ribbon cable - if you have a magnifying glass or visor, see if you can find anything wrong with it. Try cleaning it (compressed air is the safest way, but sometimes a wooden toothpick works well, if you are careful). Also, make sure the adhesive "flaps" on both sides of the connector are properly attached to the grounding shield. Other than that, I have no other suggestions for a DIY fix...
Click to expand...
Click to collapse
thanks YOU brother
This method did not work

IronRoo said:
Some have lost touch when they messed up flashing or when Essential Sep update had a problem, as I recall, I think they fixed it by side loading an OTA image. Research this first yourself (might be on reddit etc)
---------- Post added at 05:22 AM ---------- Previous post was at 05:10 AM ----------
Seems like it was Oct update, I was thinking of
https://forum.xda-developers.com/essential-phone/help/phone-lose-touch-flash-oct-update-t3849787
Click to expand...
Click to collapse
The method did not work

mamdooh191 said:
The method did not work
Click to expand...
Click to collapse
You haven't told us what happened when it first stopped working. Guess it must be hardware then. As KT said above, I'd look at their ribbon cable first if not a new one supplied, they crack easy & even if still touching over time the joint oxidises and then stops current following. Same sort of thing can happen in connector pins or solder joint on components, but you really need a very strong magnifier/eyepiece tool see it though you might get lucky. Also look for any signs of corrosion or dendritic growth, clean with a little alcohol if anything visible on nearby components on PCB.

IronRoo said:
You haven't told us what happened when it first stopped working. Guess it must be hardware then. As KT said above, I'd look at their ribbon cable first if not a new one supplied, they crack easy & even if still touching over time the joint oxidises and then stops current following. Same sort of thing can happen in connector pins or solder joint on components, but you really need a very strong magnifier/eyepiece tool see it though you might get lucky. Also look for any signs of corrosion or dendritic growth, clean with a little alcohol if anything visible on nearby components on PCB.
Click to expand...
Click to collapse
Hi brother
At first, the screen was broken but the device was still working after a while I passed the wrong picture and the device is not working, I installed a picture with the help of
https://forum.xda-developers.com/essential-phone/help/device-hung-start-t3891580
I installed the screen after editing and I had a problem with the touch
Your style brother did not work
Can AC Touch Crash? Or need a touchdriver on the device?

mamdooh191 said:
Hi brother
At first, the screen was broken but the device was still working after a while I passed the wrong picture and the device is not working, I installed a picture with the help of
https://forum.xda-developers.com/essential-phone/help/device-hung-start-t3891580
I installed the screen after editing and I had a problem with the touch
Your style brother did not work
Can AC Touch Crash? Or need a touchdriver on the device?
Click to expand...
Click to collapse
Am I right in saying,
at first the screen was cracked but touch was working,
then you flashed wrong image & touch lost
(what image? another stock image or something else? Or you flashed it to wrong slot (A or B))
But then you got it working by flash image from link above but then edited some file when you install new screen & then lost touch. What did you edit? Did the new screen ever work?
Don't know what AC Touch is, yes a driver would be needed which for touch screens is normally OEM embedded so should be in the chip of the cable of the new touchscreen, I think (I am not 100% certain on our phone though so possibly driver comes with Essential kernal) either way you should have one.
did you get whole screen assembly lcd+digitizer? Do you know for certain the screen you have is confirmed to work on our phone eg by another xda member? If yes then probably it's the file you have edited, then I think your problem is probably software, but it is not fixed by flashing a new FULL STOCK image (try different ones) then you have a problem only Essential can fix, but I don't think they will do this. maybe a more knowledgeably member can confirm some of this ...

Or you flashed it to wrong slot (A or B))
slot B

mamdooh191 said:
Or you flashed it to wrong slot (A or B))
slot B
Click to expand...
Click to collapse
We can't tell if that is right or wrong… it depends which slot you were on before… as it changes with each update on A/B partition phones. I don't know if flashing to wrong slot can give the problems you have though… I haven't read up on that problem...