So every now and then my GNote has been acting really wierd, it's as if someone is plugging in and out an micro USB cable in quick successions. Now i have a youtube video of it, but im not allowed to post links so i can't show you it here, but search youtube for "0987789023572821" and it will pop up. I'm sorry for the lousy quality and lightning, i couldn't help it since the problem rarely presents itself when im ready with my camera...
So you know, i'm not touching the phone and nothing is plugged in, it's doing it all by itself.
Obviously i suspected that there was dirt in the USB jack, and i spent quite alot of time making it super-clean. I've also suspected the micro-usb assembly was somehow damaged so i opened the phone up and heated the solderposts to re-melt the solder on the micro usb jack. I really couldn't spot any visible damage on the jack itself or the micro usb assembly.
So either this has something to do with software or its damaged without me beeing able to see it, what do you guys think? Has anyone experienced anything like this?
Also, is it possible to buy a new micro USB assembly for the GNote? I've been looking en ebay but can't find anything else then digitizers and screen replacements.
Thanks!
If its a software deal a new ROM will fix it, if not send to Samsung, I wouldnt accept a phone this good and expensive with any issues.
I had the same problem with my s2 flashing a new kernel seemed to fix it.
Are you using a custom kernel?
Sent from my GT-N7000 using XDA
Thanks for the response guys.
I'm not using a custom kernel or rom or anything. The phone is from germany and come to think of it, i might have updated the firmware before this thing started to appear. I'll try to flash in a new firmware to see if that fixes it, thanks again
This seems to be kernel problem
can you confirm, kernel updated successfully?
post this data here from setting - about phone
Baseband
Kernel
Build version
I'm sorry, i didn't look what kernel version it was before i updated the firmware. However after i updated the firmware this problem has not occured once, so thanks again, it seemed like it was a problem with the software after all
Here's what it looks like AFTER the update, as i said i don't know what it was before sorry
Baseband - N7000XXLB2
Kernel - 2.6.35.7-N7000XXLC1-CL1003701
Build number - GINGERBREAD.XXLC1
Yes your present kernel is correct, n so mo problem occurred.
I think it won't happen now.
Gudluck
Sent from my GT-N7000 using xda premium
Same exact thing happen to me after flashing abyss kernel. Restarting from scracth fixes my issue.
Sent from my GT-N7000 using Tapatalk 2 Beta-4
Related
Is this a defect? Do I need to return the phone? I'm working with all the latest OTA updates.
I've tried to force 720p and 480p through settings, and tried auto-detect.
If I have it on the gallery app in a slideshow and plug it in, I see the "HDMI" label in the status bar before it goes black.
Strange thing is that the buttons still light up and go off with the HDMI cable plugged in if I hit the power button. But I can't use the power button to turn it back off. I have to do a battery pull.
PITA! HDMI was one of the reasons I bought this dang phone?
Can anyone out there think of any reason why this might be happening?
Thanks for any help.
You're not the only one. My cable is collecting dust somewhere for the past month. Maybe cyan will fix it? This is my first htc and I'm starting to think I shouldn't hold my breath for the company to fix it. As time progresses, I'm liking this phone less. I don't know if all htc phones are like this that it seems like it was rushed to market too soon without fixing the glaring bugs with it.
Sent from my PC36100 using XDA App
I share some of your sentiment, but not all of it. I still love this phone. But HDMI was one of their big, giant marketing points that got me to buy it. A phone with an HDMI out! That's crazy! Also, when I think of what I can do with it it's pretty cool.
But for it not to work at all? Not one bit? That is just crazy.
My theory is that they didn't realize what kind of copyright hell they were unleashing upon themselves when they put it on there, and so they intentionally broke it. If they ever release some kind of source code maybe one of these chefs can make it work.
Can you try another cable that is known to work? I've been messing around the HDMI output the past week since I got my cable (Molex #687860003, from eBay), and I think the implementation is pretty fault-tolerant. I've been plugging and un-plugging it repeatedly and never had a lockup, with and without the Gallery/Video application active. Blu-Ray rips at 1280x720p look and sound amazing for such a small device. There was some discussion on another forum about a bad run of Amzer cables (that caused lockups), so maybe it's worth borrowing someone else's cable and giving it another go before turning in the phone for replacement. Good luck.
I use it everyday without a problem (Youtube).
rasterX said:
Can you try another cable that is known to work? I've been messing around the HDMI output the past week since I got my cable (Molex #687860003, from eBay), and I think the implementation is pretty fault-tolerant. I've been plugging and un-plugging it repeatedly and never had a lockup, with and without the Gallery/Video application active. Blu-Ray rips at 1280x720p look and sound amazing for such a small device. There was some discussion on another forum about a bad run of Amzer cables (that caused lockups), so maybe it's worth borrowing someone else's cable and giving it another go before turning in the phone for replacement. Good luck.
Click to expand...
Click to collapse
Thanks for the advice. Unfortunately, I don't have another accessible. But you are correct in that I should try it with another cable (and probably on another TV as well).
I went ahead and bought this one. It looks legit, plus it's long. I'll test it again when it arrives. http://cgi.ebay.com/ws/eBayISAPI.dl...40086&ssPageName=STRK:MEWNX:IT#ht_3062wt_1137
ive been using mine since day one without a problem. i bought the phone and cable from sprint on launch day.
The problem is with the old fps fix kernels. now they support hdmi out too. htc has the most lazy ass devs ever if they capped the fps cuz of hdmi... lmao
gmelchert said:
The problem is with the old fps fix kernels. now they support hdmi out too. htc has the most lazy ass devs ever if they capped the fps cuz of hdmi... lmao
Click to expand...
Click to collapse
Wait! Come back!
By "old" fps fix, which do you mean? I'm using the netarchy-toastmod 3.7.2.a kernel, which supposedly had hdmi fixed. (I'm going to update to the latest now, I hadn't noticed there was another.)
Should I be using a different kernel?
Use version c.
Sent from my PC36100 using XDA App
Ok Mr Momoman. I will try when I get home.
Sprockethead said:
Wait! Come back!
By "old" fps fix, which do you mean? I'm using the netarchy-toastmod 3.7.2.a kernel, which supposedly had hdmi fixed. (I'm going to update to the latest now, I hadn't noticed there was another.)
Should I be using a different kernel?
Click to expand...
Click to collapse
thats odd... It worked fine on the 3.7.2b that i was using... hmm yeah try the upgrade
Yeah the release notes say that HDMI is working on all 2.7.x releases. Who knows. I'll try at home and report.
I recently noticed something weird on my Galaxy S. I should point out I am running Darky's Rom (9.5).
Everytime I start (or restart) the phone some weird lines come up for a second or so on the top of the screen while the Galaxy S logo is displayed. I have uploaded a quick video to youtube (http://www.youtube.com/watch?v=_sGbpU6s_38)
I have since reflashed the phone and the lines still persist.
This problem occured after my phone randomly crashed and I had to perform a factory wipe.
Other than the lines during start up, I have had no issues since they came up 2 days ago. No further crashes, the lines don't display anywhere else, nothing.
My question:
Should I be worried and could this possibly be a hardware fault? I am sure its not the screen as the lines only pop up quickly during boot up. I fear if it could be cpu, graphics or ram related.
Any opinion or advice welcome!
Is anyone else experiencing this or has experienced it?
I have the same problem with darkys rom 9.5 :S
I dont think it is bad for your phone...
I have this almost a month and no other problems at all
Sent from my Galaxy S using XDA Premium App
this issue is kernel related, and i bet almost everyone with a custom ROM would of experienced it.
as mentioned above, it is no problem, it wont cause damage. its just one of them annoying niggles what make you think ' **** my phone.... its dying' but its not.
when a newer update for the kernel comes out the issue will most likely go away.
Thanks for the replies! Eases my fears. I guess I just got a fright because it happened (or at least I only noticed it) after the phone randomly crashed
you just assumed that was the culprit.
mine happened 3 weeks after flashing a ROM i just assumed thats what caused it because that was the last thing i did.
turned out to be nothing and now i can sleep again
it is a little 'glitch' with some kernels. don't worry, doesn't harm the phone
Sent from my GT-I9000 using XDA Premium App
god damned, you all not serious... its caused of the old darky kernel....
heres the fix for it with a new version of the kernel :
http://www.darkyrom.com/community/i...ore-1-4-now-with-i897-captivate-support.2055/
saphirrot said:
god damned, you all not serious... its caused of the old darky kernel....
heres the fix for it with a new version of the kernel :
http://www.darkyrom.com/community/i...ore-1-4-now-with-i897-captivate-support.2055/
Click to expand...
Click to collapse
I have installed the new kernel and it worked
Sent from my GT-I9000 using XDA Premium App
I've recently bought a used Nexus S i9020. I noticed that very rarely and randomly, the the capacitive home button light goes off on its own and in fact it is activated as if pressed by hand. I did a little research and found that capacitive buttons (search, back, home) activating on their own is a common problem with Nexus S. On google forums a Google employee even said this was a known software issue and will be fixed in an OTA soon. This post was from almost 1 year ago and we are already on 4.0.3 ICS so I thought I should post again and ask if anyone had the same experience and anyone could find a fix. Any help much appreciated.
I had the search button problem and I fixed it by flashing latest radio for my i9020a. You could try flashing another radio for your device.
Oogway13 said:
I had the search button problem and I fixed it by flashing latest radio for my i9020a. You could try flashing another radio for your device.
Click to expand...
Click to collapse
can I keep the automatic OTAs coming while flashing another radio, or will it break them? sorry I am unsure about this. The reason I bought a nexus is to have the OTAs.
You won't have any problems with OTAs since this only modifies the radio baseband. You will still run on stock (but to flash new radio you do have to root and install CWM).
And you won't have any problems with ota's since Google is very slow zing
Jk
Sent from my Nexus S 4G using Tapatalk
Anyone know where I can find information on best radios?
Sent from my Nexus S using Tapatalk
Oogway13 said:
I had the search button problem and I fixed it by flashing latest radio for my i9020a. You could try flashing another radio for your device.
Click to expand...
Click to collapse
I will have to check this out. I thought the buttons needed to be replaced.
donnieace said:
I will have to check this out. I thought the buttons needed to be replaced.
Click to expand...
Click to collapse
What's the latest radio? Kf1 (new version)?
Sent from my Nexus S using Tapatalk
Imppy said:
What's the latest radio? Kf1 (new version)?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
That is the radio I have on my I9020T and I'm having this problem. Will see if KB3 works (Have had better reception with KB3 but decided to go back to stock GB and so it was switched to KF1).
So I updated to 4.0.4 to see if this problem still occurred( I manually installed when I saw it on xda). Everything seemed fine until this morning when I plugged into the headphone jack. I had enough of this problem and decided to open my phone.
When I arrived home, I pulled out the replacement part that I ordered from eBay, and went to work. Everything seems to work really smooth. The new headphone jack is function as normal.
I just felt like I should share a potential solution to this annoying problem.
I'll later update the status of my new capacitive buttons, along with the headphone jack.
And yes, I was a bit nervous when doing this. I accidentally broke the small power button off while handling the board. It stuck back together by itself and works just fine. This will need a better fix. The thought of soldering comes to mind. But that's another job for later.
Sent from my Nexus S using XDA
donnieace said:
So I updated to 4.0.4 to see if this problem still occurred( I manually installed when I saw it on xda). Everything seemed fine until this morning when I plugged into the headphone jack. I had enough of this problem and decided to open my phone.
When I arrived home, I pulled out the replacement part that I ordered from eBay, and went to work. Everything seems to work really smooth. The new headphone jack is function as normal.
I just felt like I should share a potential solution to this annoying problem.
I'll later update the status of my new capacitive buttons, along with the headphone jack.
And yes, I was a bit nervous when doing this. I accidentally broke the small power button off while handling the board. It stuck back together by itself and works just fine. This will need a better fix. The thought of soldering comes to mind. But that's another job for later.
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
hey donnieace, any updates? How's that new headphone jack working for you?
I noticed that when I unplug my headphones while the screen is on the home button acts like it has been pressed/held down. As a result the recent apps are displayed. The only way to fix this is to turn the screen off then on again. I was wondering if swapping out the headphone jack fixed this because I might give this a try.
Hello all, I have 1 issue with my A500. Only during charger plug in, my tab become super lag. This problem started when I doing overclock using flexreaper extreme.
Tried to flash new kernel from eztery, upgrade bootloader to v8, and flash lightspeed ics rom. None of these works as I still have this problem. Even on recovery screen, my tab is not responsive when charger plugged in.
I don't know what caused this. Is anyone having the same problem? Please help.
im on the same but no probs while charging, maybe titanium backup,. nandroid and wipe all and re-install flexreaper
actually i've tried that already. Real format and wipe all and flash different rom and kernel. Strangely it just heppen while charging. Do you think this is hardware problem?
kazai said:
actually i've tried that already. Real format and wipe all and flash different rom and kernel. Strangely it just heppen while charging. Do you think this is hardware problem?
Click to expand...
Click to collapse
i think it must be as ive never read anything about this anywhere before did it do this when you was stock?
I never have this when on stock. Even after on flexreaper for few months also no problem. This only happen after upgrade to flexreaper extreme with OC. Weird.
have you clocked it back to 1ghz? might help you out? im not really sure dud srry
Does your tablet have a loud screen whine while it charges? Mine has been doing that for sometime now...
bouncer665 said:
Does your tablet have a loud screen whine while it charges? Mine has been doing that for sometime now...
Click to expand...
Click to collapse
def take it back and get a replacement that's a hardware flaw another member posted about that then eventually his tab died and wouldnt charge up, if i was you matey i would take it back asap to show them the whining sound so they cannot say you did something to break it, plus you'll have that noted down incase they dont do anything and it then does break.
bouncer665 said:
Does your tablet have a loud screen whine while it charges? Mine has been doing that for sometime now...
Click to expand...
Click to collapse
Mine have no sound while charging. It charge the battery as usual. Only the tab become less responsive and typing using on-screen keyboard is a headache.
chismay said:
have you clocked it back to 1ghz? might help you out? im not really sure dud srry
Click to expand...
Click to collapse
Tried that already, still have problem. I can minimize the problem by increasing the minimum frequency to 600+MHz.
The whine could also be capacitors (if any) on the logic board that are about to burst or something. Or something is overloaded and getting stressed out.
I don't believe its lag. The switching power supply causes some touch screens (such as mine) to become less sensitive requiring much harder finger presses
Sent from my Iconia A500 using Tapatalk 2
blackthund3r said:
I don't believe its lag. The switching power supply causes some touch screens (such as mine) to become less sensitive requiring much harder finger presses
Sent from my Iconia A500 using Tapatalk 2
Click to expand...
Click to collapse
Bingo. You are right. I just realize that. It is actually less sensitive. Do you have any idea how to solve it?
kazai said:
Hello all, I have 1 issue with my A500. Only during charger plug in, my tab become super lag. This problem started when I doing overclock using flexreaper extreme.
Tried to flash new kernel from eztery, upgrade bootloader to v8, and flash lightspeed ics rom. None of these works as I still have this problem. Even on recovery screen, my tab is not responsive when charger plugged in.
I don't know what caused this. Is anyone having the same problem? Please help.
Click to expand...
Click to collapse
If it worked on other versions, just flash back to what worked before or back to ota for real proof. You said it worked till you changed software, so change back and prove it's not hardware.
kazai said:
Bingo. You are right. I just realize that. It is actually less sensitive. Do you have any idea how to solve it?
Click to expand...
Click to collapse
I found some weird results by making a circuit. Try touching the tab with one finger and a laptop track pad with another. There's a tingle. I think it's a design defect internally - perhaps the screen assembly is touching something it shouldn't be. So in terms of a solution, I don't believe there is one, unless there's a way to earth the screen?
Sent from my Iconia A500 using Tapatalk 2
I have once dissemble the back cover. I'm not sure whether this is where the problem started. But I don't have this problem initially. Something is wrong with my device, just don't know where's the problem come from. I might touch something causing short circuit or something.
Tried flashing the stock ROM and still no luck. I don't think its a software issue.
kazai said:
I have once dissemble the back cover. I'm not sure whether this is where the problem started. But I don't have this problem initially. Something is wrong with my device, just don't know where's the problem come from. I might touch something causing short circuit or something.
Tried flashing the stock ROM and still no luck. I don't think its a software issue.
Click to expand...
Click to collapse
My tablet hasn't been opened and it still has this problem but not always. It hasn't done it recently.
I'm sure it's not a software thing but for the record I'm on Thor's ROM
Sent from my Iconia A500 using Tapatalk 2
Today I noticed something. I do have this problem when charging at my office. Looks like this issue only happen at certain wall plug. It happen at my house but not my office. Could be something with grounding.
Sent from my A500 using XDA Premium HD app
kazai said:
Today I noticed something. I do have this problem when charging at my office. Looks like this issue only happen at certain wall plug. It happen at my house but not my office. Could be something with grounding.
Sent from my A500 using XDA Premium HD app
Click to expand...
Click to collapse
Perhaps it is to do with the consistency of the power supply. My house is pretty old so I suppose there would be more voltage variation. When I get home I'll try and find a spare surge protector and see if it stops the issues. The actual existence of the issues is pretty sporadical though. There is no clear answer to this.
I do think you're onto something though
Turned it on this morning and this is what the screen looks like now. I assume my screen is going out. Would I be correct? I tried turning the unit off then back on but it didn't fix anything.
Sent from my A500 using xda premium
Apparently the screen shot doesn't show what I see so here's a picture from my phone.
Sent from my EVO 4G LTE using xda premium
This is certainly hardware related. It could be damaged or not properly connected LCD ribbon cable.
Before I start thinking about hardware issues, I would start looking at software issues.
I base this on the screenshot issue to begin with.
Quite honestly, I would wipe and format that puppy. Then flash a somewhat stock rom.
Hell, I would wipe and format several times,
Also, some info on what rom you have now would be helpful. Bootloader version would be nice.
Looks like you run an aftermarket launcher,,
MD
I was thinking of trying a reset. Guess I'll try that first.
Also, I'm running non-rooted with stock launcher.
Sent from my EVO using xda premium
Moscow Desire said:
Before I start thinking about hardware issues, I would start looking at software issues.
I base this on the screenshot issue to begin with.
[...]
Click to expand...
Click to collapse
There is a slight possibility that this could be a software issue, but the screenshot seems to be ok, so at least screenshot app is getting correct data.
@guitarman584 how the screen looks when you boot up the tab? Does the Acer logo in bootloader looks ok or is it mixed up together?
It does the same thing on the Acer and Android boot up screens.
Then there's no way it's a software issue. You can try opening it and checking if the LCD cable is properly connected to the motherboard but can void your warranty. You can also damage it more if you're not skilled enough.
Sent from my A500 using xda premium
Well this sucks. The warranty ended on 7/12/12. The timing couldn't be worse. Guess it won't hurt anything to open it up and check the connections.
Some user just posted a link to a500 teardown in the other thread.
http://www.techrepublic.com/photos/...16&tag=thumbnail-view-selector;get-photo-roto
Hope this helps.
guitarman584 said:
Well this sucks. The warranty ended on 7/12/12. The timing couldn't be worse. Guess it won't hurt anything to open it up and check the connections.
Click to expand...
Click to collapse
If you paid with plastic you should look and see if the card has a warranty bonus. I am having crazy issues with 3d, so it was a drag when I checked my warranty @ Acer. Then I remembered that the card I used added an extra year. So thankfully, while I haven't sent it back yet, I know I have plenty of time to goof with it.
I've never heard of that. I used my ATM card, not a credit card so it doesn't seem like I would have it on a normal checking account card.
I just noticed something that doesn't make sense. When I press and hold the bookmarks widget as shown in the 2nd post, the issue goes away until I let go. I did a hardware and software reset but this didn't help. Also when I go to slide to another screen, the issue goes away. I'll try and get video of it so you can see exactly what it does.
Here's the video of what I was talking about yesterday.
http://www.youtube.com/watch?v=4PVIMbYFRis
I just noticed that while on the lock screen, everything is fine. It's only when viewing any of the 5 screens that the issue shows itself.
Sent from my A500 using xda premium
You made the video private. It cannot be played.
Weird, must have been a default setting. Try it again. This time it is unlisted but should work since the link was shared.
Sent from my A500 using xda premium
Well they finally accepted to take it in for repair under warranty, even though I told them the date I purchased it and it was passed 1 year. I hope I get it back soon. It sucks being without it.