[Q] Froyo puts my screen to sleep. . .? - Fascinate General

I have been encountering a strange problem with every 2.2 flash I have done. After a random amount of time the sensitivity of the touch screen fades away until it becomes completely unresponsive. Then if I lock and unlock the phone it will work again for a while. It seems if I keep doing something on the screen it wont do it, but if I let it sit for a few seconds it happens. Sometimes it starts to act up right after the flash and other times it takes 10-12 hours.
I have had the exact same problem with DL30 and EB01 clean and stock versions. I have disabled and removed voodoo before any changes, I have wiped wiped and wiped again. I even did the D101 odin package then worked forward. I have let it sit unchanged for hours after the flash not letting it update anything same result. Launcher pro Tw, same result.
I guess I am fine with my wonderfully working DL09 Superclean but without getting past this I am at the end of my road for all the development goodies, and I want flash!
Anyone have any ideas??

dw77x said:
I have been encountering a strange problem with every 2.2 flash I have done. After a random amount of time the sensitivity of the touch screen fades away until it becomes completely unresponsive. Then if I lock and unlock the phone it will work again for a while. It seems if I keep doing something on the screen it wont do it, but if I let it sit for a few seconds it happens. Sometimes it starts to act up right after the flash and other times it takes 10-12 hours.
I have had the exact same problem with DL30 and EB01 clean and stock versions. I have disabled and removed voodoo before any changes, I have wiped wiped and wiped again. I even did the D101 odin package then worked forward. I have let it sit unchanged for hours after the flash not letting it update anything same result. Launcher pro Tw, same result.
I guess I am fine with my wonderfully working DL09 Superclean but without getting past this I am at the end of my road for all the development goodies, and I want flash!
Anyone have any ideas??
Click to expand...
Click to collapse
Going to sound completely random, but are you using an aftermarket charger? Or is this not happening on dl09?

jenisiz said:
Going to sound completely random, but are you using an aftermarket charger? Or is this not happening on dl09?
Click to expand...
Click to collapse
Stock charger and not happening on DL09. It does it really bad (2.2) whenever the charger is plugged in, I have heard this is a known issue. Perhaps somehow related to my problem?

do you run aLogcat or anything like that? I would wonder if there is anything logged by the system when this happens...

M00NEY said:
do you run aLogcat or anything like that? I would wonder if there is anything logged by the system when this happens...
Click to expand...
Click to collapse
No, I do not. Normally I do not post and ask questions as I prefer to figure them out myself, but I am truly at a loss!

dw77x said:
No, I do not. Normally I do not post and ask questions as I prefer to figure them out myself, but I am truly at a loss!
Click to expand...
Click to collapse
I have actually noticed this issue a couple times also, completely annoying. And certain spots on the screen that will go unresponsive, but only certain spots, and if I lock/unlock, it will start working again, REALLY annoying when trying to send a text message.. and its always different parts of the screen.

this dosent help but i have the same problem at least we not alone

micdawg12 said:
I have actually noticed this issue a couple times also, completely annoying. And certain spots on the screen that will go unresponsive, but only certain spots, and if I lock/unlock, it will start working again, REALLY annoying when trying to send a text message.. and its always different parts of the screen.
Click to expand...
Click to collapse
Yes, I forgot to mention it happening in certain spots, then eventually the whole screen.
It "seems" to me that the touch screen is prematurely shutting down with the back light still on. Although, sometimes this happens right after I unlock it. Grrr frustrating!

bubbleywine said:
this dosent help but i have the same problem at least we not alone
Click to expand...
Click to collapse
How bad have you had it? bad enough to flash back to eclair or have you been dealing with it? It drove me nuts, I went back. I sure would like to figure it out though!

I believe it has something to do with the charger either being incompatible with the phones hardware or software. I bet the issue disappears the second you disconnect the charger too doesn't it? Mine was doing the same thing. I bought another charger directly from verizon at the store and it resolved my issues. I realized it after hearing a few complaints on the forum. I had an issue like this once before on my Samsung Moment...and it fried my phone.

jenisiz said:
I believe it has something to do with the charger either being incompatible with the phones hardware or software. I bet the issue disappears the second you disconnect the charger too doesn't it?
Click to expand...
Click to collapse
First I have the charger that came with the phone so I don't think that is the problem. Second I do have the problem much worse when plugged it. But it still persists with it un plugged, to the point of it being un usable.

jenisiz said:
I believe it has something to do with the charger either being incompatible with the phones hardware or software. I bet the issue disappears the second you disconnect the charger too doesn't it? Mine was doing the same thing. I bought another charger directly from verizon at the store and it resolved my issues. I realized it after hearing a few complaints on the forum. I had an issue like this once before on my Samsung Moment...and it fried my phone.
Click to expand...
Click to collapse
I have the issue on and off the charger, mostly off.. I don't think thats the case.

dw77x said:
First I have the charger that came with the phone so I don't think that is the problem. Second I do have the problem much worse when plugged it. But it still persists with it un plugged, to the point of it being un usable.
Click to expand...
Click to collapse
Yeah for me it ended up being the charger. Dunno, maybe something happened to your port or it got damp and fried something...but I'm telling you, exact same issue happened to me. I couldn't use my phone when it was plugged in. Haptic would go crazy and I couldn't text. Got used to unplugging it when I wanted to send a text. Then after about a week, the issue started happening to the phone after it was unplugged. Took it in and sprint voided my warranty on that one b/c they said I'd fried the port by using an unauthorized charger.

jenisiz said:
Yeah...it's as a result of the charger. Dunno, maybe something happened to your port or it got damp and fried something...but I'm telling you, exact same issue happened to me. I couldn't use my phone when it was plugged in. Haptic would go crazy and I couldn't text. Got used to unplugging it when I wanted to send a text. The after about a week, the issue started happening to the phone after it was unplugged. Took it in and sprint voided my warranty on that one b/c they said I'd fried the port by using an unauthorized charger.
Click to expand...
Click to collapse
Not saying I don't believe you but why does it work fine on any eclair setup if it's a physical/damage issue?

dw77x said:
Not saying I don't believe you but why does it work fine on any eclair setup if it's a physical/damage issue?
Click to expand...
Click to collapse
No, re-worded my phrase. It was for me. No idea how or what happend. To this day it bewilders me. It's possible that if the amount of voltage required to run can be tampared with, then who knows what else can be? People fail to understand that phones are no different from computers. You plug a buggy power supply into a main board and it's highly likely things will get fried or damaged. Especially if you start messing with the bios and try to overclock/underclock.
Most logical way I can explain it is by using cars as an example. Different grades of gas are not equal. If you're vehicle needs to run lean and you start filling her up with unleaded, you might get away with it for awhile...but after bit, your engines gonna start knocking.

jenisiz said:
No, re-worded my phrase. It was for me. No idea how or what happend. To this day it bewilders me. It's possible that if the amount of voltage required to run can be tampared with, then who knows what else can be? People fail to understand that phones are no different from computers. You plug a buggy power supply into a main board and it's highly likely things will get fried or damaged. Especially if you start messing with the bios and try to overclock/underclock.
Click to expand...
Click to collapse
I guess when an oem Froyo comes out <sinkers quietly> I will odiin back to E101 and try and ota and see what happens.

jenisiz said:
Most logical way I can explain it is by using cars as an example. Different grades of gas are not equal. If you're vehicle needs to run lean and you start filling her up with unleaded, you might get away with it for awhile...but after bit, your engines gonna start knocking.
Click to expand...
Click to collapse
Not to bash Samsung but sheesh, if they are that fussy, I will probably not buy again.

Related

hardwarre problem on wing

so i think my wing may be in the process of biting the big one. A few days ago, my wing restarted itself for no reason, i figured it was probably a system error and didnt think twice about it. Now all of a sudden my wing will constantly restart, sometimes in the middle of a call. Sometimes when it does restart the screen will either turn white or fade to white. I reinstalled the original rom to see if it was a software issue and it is still doing it. Also, it doesnt normally do it when it is just sitting there, and sometimes i cant turn it back on. Any ideas?
Make sure the battery isn't loose inside the case... and that all the prongs are making contact.
For the life of me, i cant figure it out. I know it has to have something to do with the phone not getting power. At this point, it wont even fully turn on. Short of taking it apart and checking the solder, does anyone have any ideas?
dcmtnbkr said:
For the life of me, i cant figure it out. I know it has to have something to do with the phone not getting power. At this point, it wont even fully turn on. Short of taking it apart and checking the solder, does anyone have any ideas?
Click to expand...
Click to collapse
If you already reflashed the original rom, and it is still doing it, that tells you it is definitely a hardware issue. It does sound like it's losing power which could be a host of things. (loose battery, defective battery, loose solder on board, etc) I would try what duprade said, and check to make sure your battery has a good connection first. If you had a friend that had a wing as well, you could try his to make sure it's not the battery.
dougstoner said:
If you already reflashed the original rom, and it is still doing it, that tells you it is definitely a hardware issue. It does sound like it's losing power which could be a host of things. (loose battery, defective battery, loose solder on board, etc) I would try what duprade said, and check to make sure your battery has a good connection first. If you had a friend that had a wing as well, you could try his to make sure it's not the battery.
Click to expand...
Click to collapse
Brand new battery (free from tmo to replace the dynapack) Everything on the mainboard looks like it is soldered well. There is an internal watch batter though, could that have something to do with it?
dcmtnbkr said:
Brand new battery (free from tmo to replace the dynapack) Everything on the mainboard looks like it is soldered well. There is an internal watch batter though, could that have something to do with it?
Click to expand...
Click to collapse
I doubt it. I would guess that's the cmos battery. If that were to go, then your phone wouldn't keep time, but that wouldn't stop your phone from functioning. (I used to work in the service center at a computer store).
maybe its the processor then. sometimes, after it freezes, it artifacts before shutting off
dcmtnbkr said:
maybe its the processor then. sometimes, after it freezes, it artifacts before shutting off
Click to expand...
Click to collapse
There is the possibility of you overclocking your phone, and it heated up and could have burned or cracked some solder. It might even be overheating and that's why it reboots. At any rate, it def. sounds like hardware though. Sorry man. You could try to resolder the connections on the board just to make sure, but it sounds like you have a paperweight. Is it under warranty or do you have insurance?
only ever oc'd once, for a few minutes, and not very high (like 267 i think) It's on right now on the power cable (this wouldnt work yesterday) I honestly have no fricken clue whats going on with it.
Is it possible for the battery to completely diminish itself without being used for a day? Before it died on me last, it had a full battery, now it is showing 1% (and charging).
By the way, as I stated above, it is a brand new battery sent to me by tmo.
Dang it all! Stupid thing just shut off again... ARG!!!
dcmtnbkr said:
Dang it all! Stupid thing just shut off again... ARG!!!
Click to expand...
Click to collapse
Hey dcmtnbkr. I seem to have the exact same problem with my Wing. It shuts off for no reason, and it does it absolutely randomly. Sometimes it would work for 3hrs straight no matter what i use it for. And other times it shuts off every 30sec. and it takes 3 to 10 tries to turn it back on(most of the times it would not get past the windows mobile welcome screen). I was gonna flash it with the newer Rom, but i'm afraid that the damn thing might shut off during flashing . So i'm stuck. If you find the way to fix it - please let me know.
actually, i just talked to tmo, and apparantly NOW after i told them I'm cancelling when my contract is up, now they can apparantly cover it under manufacturer warranty (as opposed to the last time i called about a week ago) I would call them even if you didnt buy it from them, tell them you dont remember where you bought it, but it was some company online. These phone's arent that old and you may still be under the manufacturers warranty. Also, i would try and flash it back to the original. These phones are very hard to brick, and i would ask around to see if a powerdown in the middle of an upgrade would do it. I just got mine to reflash without a problem.
my wing rstarts itself wen i jus tap the back of it where the battery cover is but it wont restart everytime. anyone have any ides?

Big Problem with USB

Hi. I moved from a DInc on Verizon to the Vibrant because I hated the sunlight on an AMOLED, and because Verizon was stealing my money. Although honestly verizon just lowered prices, and Tmo's network is still crap in my town.
Anyways down to business: My phone is rooted, and I applied one click lag fix. I am assuming that was when problems started but then again not for sure. I've gone from stock to Vibrant5 to Vibrant6 roms, no change.
The first problem here is this: my phone always thinks it's plugged in to USB. It cycles on an off, but never just stops and stays normal. I'm talking several times a minute ''usb connected'' or whatever on, off, on, off... annoying but no big deal. Except that freaking battery meter that pops up when your phone is off but plugged in via USB starts popping up when it's not plugged in and my phone is turning on... but since there isnt really usb in, it just hangs and resets. The second I plug in a real usb, meter pops up and i just turn it on and all good.
Second problem, which makes it so bad: my phone does this things that I've seen on XDA several times where when the processor bogs down, or GPS is on, or whatever taxes the phone, it will randomly reset once or twice a day.
Put those together and what you get is me, in public away from a charger, with a phone that won't turn on. WTF. So I repeatedly take the battery out and jam the power button till once in a while I'm able to start it before the stupid usb thinks its plugged in. Other times I'm screwed till I find my car charger.
Now, what can I do? Before anyone says warranty, yes I unrooted, did my best to unlagfix, and went to the Tmo store. They ordered me a new phone. However I have to send mine in when it gets and here and would like to insure there is no root related crap for them to find, plus I'm stuck with this phone freaking out on me for another week.
I was having the same problem , but it started since.my dougther put the usb canle in her mouth xD , I just cleaned the contacts and waited a few hours but now is fine , running
Vibe6 oc
Sent from my SGH-T959 using XDA App
cleaned the contacts on your cable, or inside your usb port on the phone? How would you clean those?
Sooooo, no input huh. Okay then.
trevorwhopkins said:
Sooooo, no input huh. Okay then.
Click to expand...
Click to collapse
If people keep messing up their phones by rooting and flashing roms and then, rather than trying to fix the problem, send them into tmobile, I bet future firmwares and android phones will be more like the iPhone and iOS.
First I would try to flash it back to stock and leave t factory. Then if problem persist, its probably hardware. I mean you are returning it anyways so flash it back to the stock rom and do a factory reset
Sent from my SGH-T959 using XDA App

[Q] It seems to be a "full brick"

Was updating using Odin when, as my luck always proves out, a circuit breaker tripped and cut power to my PC. The phone seemed to be frozen on the "Download Mode" screen (30+ minutes of zero activity) so I pulled the battery. Upon reinserting the battery I discover that the phone is 100% unresponsive. I've tried every trick google could produce for me with the exception of the "homemade jig" method as it seemed fairly clear that the phone needed some semblance of life for that to be effective.
So, my question is... WTF??? I've soft modded wiis, hard modded xboxes, hacked PSPs flashed hundreds of phones and generally revel in futzing around in this manner of endeavor and have NEVER bricked a device (even after some incredibly stupid mistakes). This just doesn't make sense and I haven't seen sysmptoms such as mine presented in any of my web searches. Any ideas???
I'm not saying your not a modder, but you should know to have a UPS hooked up to your dev box, for me its a laptop, so...
Anyway, try removing the battery for 1m, press power button with batt removed, now start up Odin, plug the phone in (batt removed still) and see if the phone connects. I'm sure someone will pop in here and provide links to several threads that describe different methods to help you fix this, I would but I'm sorta busy...
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616
Sent from MyEF02 using XDAPA...
Keep the battery out for like a half hour and then try again. That has worked for some people.
Or try the mysterious button that may or may not exist. I know I'd be pushing the heck out of it just in case.
Thank you so much for your quick input... I tried precicely that 3-4 times (google search turned it up) and it was a futile endeavor.
And yes, I am fully aware of all the proper precautions to take, unfortunately I am also fully stupid with frightening regularity (well, maybe just lazy and reckless), I seem to have become a tad cocky as I have never really had to face disaster before today.
It won't happen again!
plug phone into computer without battery. Then hold power and 1 to go into download mode (still no battery)
That there is what I've seen as most effective thing to work on bricked phone's.
cool... I just popped out the battery and will let you know the result in about 40 minutes...
this happened to me recently, i found a post with the solution being to pull the battery out of the phone hold down 1 and the power button at the same time before popping the battery back in and it will send you to the proper screen to odin back to what you need, worked perfect for me
oh crap I editted my previous post. i forgot to mention go into download mode...
It's --
Remove battery and plug into computer. then go into download mode WITHOUT Battery still.
If your not getting any sign of life from ur phone, try this:
http://forum.xda-developers.com/showthread.php?t=1042746
It worked for me.
Krojian said:
If your not getting any sign of life from ur phone, try this:
http://forum.xda-developers.com/showthread.php?t=1042746
It worked for me.
Click to expand...
Click to collapse
there is no hole in the back case of my device. I've had my device powered on and bent the **** out of a paper clip trying to push the 'hidden magic button' to no avail.
YMMV (false hope ??)
Cool, didn't know that little button existed!
I bricked mine the same way a few weeks ago and tried every trick in the book over the course of 2 days. It was truly bricked. I don't have insurance; however, my phone was under warranty. Since I couldn't get the phone to boot or anything I figured there was no real way of telling what went wrong. I sent it in for warranty repair and 10 days later, the phone returned in working order. Work order says they replaced the main board. I marked the phone before returning it so I know its the same phone and it works fine now.
And before anyone says anything, I know, I'm an evil bastard. But I figure it's payback for a samsung flatscreen that died 6 months out of warranty.
I've done this, leaving my battery out for 20 mins or so, and leaving it out while going into download mode worked for me. I don't know why but sometimes I can't even get into download mode with my battery in.
keeepinitgansta said:
Cool, didn't know that little button existed!
Click to expand...
Click to collapse
it doesn't..
to prove this (or dis-prove it).. go into clockwork and make a nandroid backup (you know, just in case)...then boot normally and while you're looking at your home screen, jam a paper clip in there as hard as you can. Your device will do nothing.
daddymikey1975 said:
it doesn't..
to prove this (or dis-prove it).. go into clockwork and make a nandroid backup (you know, just in case)...then boot normally and while you're looking at your home screen, jam a paper clip in there as hard as you can. Your device will do nothing.
Click to expand...
Click to collapse
I hope you guys are messing with him...
hardrock121 said:
I hope you guys are messing with him...
Click to expand...
Click to collapse
No, it's just not proven. Some people swear by it, some say it's a myth and some say it depends on when your phone was made.
Sent from Godot's place.

Dead Nexus S

Hi guys,
Tried searching for my problem, but though I found some similar stuff, noone had quite my problem.
I was checking my Nexus S after a trip and it was with the 'emergency only' message. This sometimes happens to me, not sure if it's due to the roaming activation or caused by a bug where the radio subsystem crashes after a long period without network.
Anyway, I proceeded to my common solution: Turn off and reboot.
Except that after the phone was off, it would not turn on.
It doesn't even vibrate. It doesn't show anything when connected to the wall socket or to the computer. It's just completely dead.
Now, I'm not even sure if this is a hardware or software problem. Any idea on how I can debug this?
Here's what I've tried:
1. Take the battery out: no changes (even tried leaving it out overnight).
2. Charge the phone overnight: no change.
Next step: I'll go to a store and try a different battery... meanwhile I'm without my primary phone which sucks... Can anyone help?
Thanks in advance!
Try booting your phone into the bootloader. Hold the power button and volume up button simultaneously.
If it is not the battery, i can see what else you can do, a "dont turn on" phone is a dead end...
Sent from my Nexus S using XDA App
Guess I'm screwed... I had some pics and other data there... anyway I can get it back? i.e. is there a way to remove the internal sd card?
saranyan said:
Try booting your phone into the bootloader. Hold the power button and volume up button simultaneously.
Click to expand...
Click to collapse
Was this tried? Cause if that works there's hope for you yet.
BlackHawkA4 said:
Was this tried? Cause if that works there's hope for you yet.
Click to expand...
Click to collapse
Yup, it was one of the first things I tried. No sign of life... I can't get a single sign that the phone is even being powered. It's like the battery was taken out.
nunocordeiro said:
Yup, it was one of the first things I tried. No sign of life... I can't get a single sign that the phone is even being powered. It's like the battery was taken out.
Click to expand...
Click to collapse
Sounds like something is wrong with the hardware then. Have you brought it the store? Might need to get a new one on warranty.
I have the same issue with my old Blackberry 9000. It worked fine up until I stopped using it. Left it in a drawer for a few months. Went to sell it to Sprint. Wouldn't turn on. No LED, no nothing. Worked fine months before when I was still using it. To this day I have no idea what's wrong with it and it doesn't turn on.
Why not get an external battery charger and charge the battery up and then test it?
All true, and after trying with a new battery I'll have a bit more information.
But what strikes me as odd is that I didn't leave it in a drawer - I didn't even let the battery run down... it was just a damn reboot! I shut it down, and then couldn't power it up again (try and imagine THAT happening to you). It would be odd for the battery to be sucked dry all of a sudden...
I have a feeling that there's something else... maybe while shutting down something burned out in the power circuitry....? =S
No one ever heard of anything like what I'm experiencing? It sucks to be the only one!
Thanks for all the help so far, guys!
If you can get to download mode nothing is lost. Just flash new image via Odin.
Sent from my GT-I9000 using Tapatalk
nunocordeiro said:
All true, and after trying with a new battery I'll have a bit more information.
But what strikes me as odd is that I didn't leave it in a drawer - I didn't even let the battery run down... it was just a damn reboot! I shut it down, and then couldn't power it up again (try and imagine THAT happening to you). It would be odd for the battery to be sucked dry all of a sudden...
I have a feeling that there's something else... maybe while shutting down something burned out in the power circuitry....? =S
No one ever heard of anything like what I'm experiencing? It sucks to be the only one!
Thanks for all the help so far, guys!
Click to expand...
Click to collapse
Never heard of that happening, but it's a possibility... Still, I would first attribute it to a bad battery and try that first
Sent from my Nexus S 4G
With a new battery (that works on another nexus S) still no luck. =(
I still can't find anyone with this problem. I feel like the unluckiest idiot on Earth.
I assume I can't get to download mode since I can't even get the phone to report it is charging (it used to do that even if off). Do you want me to try anything, though? I'm open to suggestions until Monday. Then I'm taking it to Samsung. Hope they can recover my pictures.
BTW, my receipt doesn't have the IMEI and a customer service rep told me I need it on the receipt or they won't give me free support. How can I get it with the phone off?
Regards and thanks to all who responded,
Nuno
nuno, if you cant power on even with a new charged battery, then it's a harware fault and nothing can me done... =o\
but thanks for the advice, i never thought about the data in sd card, i guess i should make some backups! =o)
nun
BTW said:
Look under your battery. IMEI should be printed on the sticker beneath. Good luck!
Click to expand...
Click to collapse
I've got the same problem: dead nexus s after a reboot. It says "no service" emergency call does not work. I tried pretty much everything like switching the battery, recovery mode, plug it in, etc. I even updated its image to the latest I've got access to. No luck. I'm already contacting samsung to get it replaced.
odd things can happen ... it sucks
igorgatis said:
I've got the same problem: dead nexus s after a reboot. It says "no service" emergency call does not work. I tried pretty much everything like switching the battery, recovery mode, plug it in, etc. I even updated its image to the latest I've got access to. No luck. I'm already contacting samsung to get it replaced.
Click to expand...
Click to collapse
Did you try flashing a different rom? Or radio/
I haven't experienced this myself but I'm very interested on what happened. Did you guys flash any custom ROMS? or Radios for that matter?
This looks very similar to what i have. I just got my nexus s GT-i9023, it doesn't boot into fast boot, recovery, download mode or normal. The most activity i have got so fare is when i take the battery out, put it back it, and try turn the phone on it will sometimes flash then do nothing. I have looked every ware. When i use "./platform-tools/adb get-state" it returns "unknown". Any help would be great.
What i think i did was this:
- Unlocked bootloader, this worked
- restart
- installed clockwork mod with fast boot, this worked
- wiped data
- wiped cache (correct me if i spelt that wrong, or anything else)
- flashed cyanogenmod, this got an error but i didn't notice it the first time and i can't remember what it was.
- flashed gapps, this didn't work, when i restarted the phone it said that the installer for gaps had quit.
- restarted
- flashed cyanogenmod again, this is when i noticed the error
- restarted, didn't change anything
- wiped data
- wiped cache
- flashed i9020t recovery, this http://forum.xda-developers.com/showthread.php?t=1061855 i think this is what stuffed it up because my phone is i9023
- wiped data after flashing, thats what it said to do, i thought it was strange but i went along with it.
- wiped cache
- reboot
- now doesnt work.
Take it to the store where you purchased and claim ignorance!

Big voice talk problem and car mode notification

Ok so maybe I spoke too soon. Yesterday I was telling my brother that the Note is the most reliable phone I've ever owned.....then....
I started having issues with charging. My Note would not charge, then it would change after several resets. It would charge, then stop, then start again etc etc....making a lot of beeping noises.
Now, it seems to be charging, but Voice talk keeps loading, and I've turned off the home key activation option. I also get the notification icon saying to disable car mode.
I really hope someone can help, thanks in advance.
kris
Great, now it's not charging, again!
Actually when I get the notification issue from Voice talk, the battery starts charging for a second until the notification disappears and stops charging....
Now factory reset my phone again and charging worked while restarting and restoring but when loaded the voice talk app keeps coming up and going off, so I have a black flashing screen constantly....gonna try restarting/reset without restoring...
Hi leicashot, this shouldn't happen. Which firmware version are you currently running? I recommend installing the latest LB1 stock, unless you have AT&T Note.
Some users have reported similar symptoms when there was dust in the mini usb port. Try cleaning the device, and if all else fails, you should send it back to Samsung for repair.
Bassarnis said:
Hi leicashot, this shouldn't happen. Which firmware version are you currently running? I recommend installing the latest LB1 stock, unless you have AT&T Note.
Some users have reported similar symptoms when there was dust in the mini usb port. Try cleaning the device, and if all else fails, you should send it back to Samsung for repair.
Click to expand...
Click to collapse
I'm using the latest 2.6.35.7. Any idea how to try clean the port? Definitely seems like something is wrong with the port....
No charging issues for me but my Note started doing the driving mode thing at about 3am today and has been doing it on and off all day!
Exceedingly annoying!
are you trying to charge from a PC or a wall outlet?
I usually charge via mains but it wasn't charging or even plugged in at the time this started happening. It was just sitting on the table by my bed. I even powered it off but it switched itself back on!
Here is how to fix it.
Take out the battery and take a plastic edge like credit card or even a regular tiny small screwdriver and push the pins (strip) inside the phone. I mean, to take the screw driver and push in the pins back inside the phone, in inside the usb charging port. your problem will disappear. make sure your plastic flexible after-market phone cover has a big enough hole at the bottom to allow you to connect a usb cable easily to the phone, or else, cut open a bigger hole on the cover.
Good luck
so here it is again: you have to push in the usb port pins back inside the phone, straight in without bending them. you can also buy a usb charging port from ebay for 22 bucks and change it yourself in 10 minutes. its a hardware problem so stop resetting your phone.
Nop bro i dont think so, cuz it happened same with me sometime after i bought galaxy note same thing happened with me too. I mean exactly same. So before i didnt knew rooting and flashin roms and all so i gave to service centre and they put newer version of ron in it and my problem was fixed after that.
Sent from my GT-N7000 using XDA
coolcrab said:
Nop bro i dont think so, cuz it happened same with me sometime after i bought galaxy note same thing happened with me too. I mean exactly same. So before i didnt knew rooting and flashin roms and all so i gave to service centre and they put newer version of ron in it and my problem was fixed after that.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Indeed. I remain convinced this is not hardware and is software related. The main reason for my thoughts there are that as well as the driving mode thing it seems that some piece of software is trying to load up as it asks me if I want to run whatever it is in either Clock or TuneIn Radio. Bizarre. Also, the first time it happened it was bang on 3am. Everytime I turned the phone off it would come back on exactly two minutes later.
The second night it started doing it bang on 1am.
I'm waiting to see what time it starts tonight.
It doesn't (so far) do it at all during the day.
Going to give it a couple of days to see what happens then go figure out how to go back to a factory ROM rather than the the Rocket 22 I have on here now.
Lakota said:
Indeed. I remain convinced this is not hardware and is software related. The main reason for my thoughts there are that as well as the driving mode thing it seems that some piece of software is trying to load up as it asks me if I want to run whatever it is in either Clock or TuneIn Radio. Bizarre. Also, the first time it happened it was bang on 3am. Everytime I turned the phone off it would come back on exactly two minutes later.
The second night it started doing it bang on 1am.
I'm waiting to see what time it starts tonight.
It doesn't (so far) do it at all during the day.
Going to give it a couple of days to see what happens then go figure out how to go back to a factory ROM rather than the the Rocket 22 I have on here now.
Click to expand...
Click to collapse
Same thing is happening to me. I tried pushing the USB pins in slightly. I'll let you guys know if it helped or not.
Sent from my GT-N7000 using xda premium
I've been having the same problem for a few days now.
I've just pushed the pins in with the corner of my charging cables connector and the problem stopped.
There was also a notification that flashed up saying something like: USB connector or device removed.
Voice talk is still managing to launch itself, even after pushing the pins in. I'm on stock LB2 so maybe I've finally found a reason to flash a GB rom?
Happened to me yesterday. Got a toothbrush and cleaned usb port on phone. Now seems ok
Sent from my GT-N7000 using xda premium
engineer
aftabbabar said:
Here is how to fix it.
Take out the battery and take a plastic edge like credit card or even a regular tiny small screwdriver and push the pins (strip) inside the phone. I mean, to take the screw driver and push in the pins back inside the phone, in inside the usb charging port. your problem will disappear. make sure your plastic flexible after-market phone cover has a big enough hole at the bottom to allow you to connect a usb cable easily to the phone, or else, cut open a bigger hole on the cover.
Good luck
so here it is again: you have to push in the usb port pins back inside the phone, straight in without bending them. you can also buy a usb charging port from ebay for 22 bucks and change it yourself in 10 minutes. its a hardware problem so stop resetting your phone.
Click to expand...
Click to collapse
this method solve my problem.

Resources