Hello all,
just got my G2 and rooted and installed some different ROMs to try out. I tried a few including Virtuous Sense Fusion 3.0, the Desire Z port of the Sense, and even CM7 and SuperCM7. Currently I am on SuperCM7. When I was using the base Virtuous Desire Z /w bug fixes/enhancements, I had the standard kernel which gives the phone a moderate 1Ghz overclock supposedly with screen-off built in profiles? Anyway, my point is with that, my phone randomly rebooted once and ever since that I got off that ROM. Eventually I skipped over plain CM7 since I was having MASSIVE data issues with that, and am now on superCM7 which runs fine except that I also had a reboot occur. I was overclocked to 1113mhz in setcpu min and max and had a 245/368 min/max screen off profile enabled. Could the overclock be the problem? I did not adjust any phone voltages or anything of that nature.
Also, I googled this and saw that the "Noisy keyboard" thread under the Q&A and read about how it makes like crinkly and plasticy noises and stuff. Obviously the guy did not notice the piece of thin, film like material underneath the keyboard as that is probably the cause. But is it normal for that material to make extra noise IN ADDITION to typing? What I mean is, okay, say you press a key with like a pen, obviously you will only hear the key click down, but if you actually practically type and type somewhat relatively quickly you will hear the noise every other letter in addition to the keys going down. Is this a defect? My keys do not make any kind of noise if i just grave over them with the surface of my fingers, only when i'm typing. Is this normal for everyone?
Thanks
Related
My desire z is going back for warranty tomorrow ...
The touchscreen and the buttons just under it stopped working without any warning.
Anyone else had similar issues??
Now unrooted with the latest ruu.
Back to my magic
Sent from my HTC Magic using XDA App
When you say it stopped working, did you by any chance have the phone on a worktop? or was you holding it in your hand?
There are reported issues with phones not working all the time when on a worktop, however mine always works when its in my hand.
When my phone is laying flat on any surface the screen just refuses to respond... however if I angle it just slightly it works just fine, or if I pick it up.
I have the same issue when its in the car dock. I didn't have the issue when I was running the stock bell rom this only happened when I installed cyanogen 6.1
My g2's touchscreen gets super lllaagggyyy, like laggy as crap whenever it is connected to the charger @ near full charge. It's random...yet it's not, like for instance..I can put it on the charger and initially it's very responsive. Then, after a few minutes charging the screen *seems* to be unresponsive, I just have to swipe it slowly and it jerks by @ like..5fps seemingly. This has happened on every rom ive tried so far from stock to CM.
Just installed MIUI and haven't had a chance to test..i'm assuming it's hardware related though.
When I First got my G2, The TMo Rep asked me to open it up at the store since i was getting the first one from that store and the touch screen didnt work at all, we turned it off and on and nada. So they replaced it with another one and it worked just fine. Other than that little problem i never had a issue on my G2 as far as touch screen freezing goes
Seems like shoddy hardware to me... I've never dropped the phone.. its always been in a protective cover.
Although I couldn't help thinking.. maybe all the extreme overclocking / general heating up of the phone may have contributed??
Sent from my HTC Magic using XDA App
I have never OC my desire Z (not G2) but I have noticed the exact same symptoms of an unresponsive touch screen after flashing cyanogen 6.1.
I returned back to my stock rom and everything is back to normal.
I haven't had a problem since..
yes, when its on a worktop (table, desk, anything not my hand) and in a dock -- its not as responsive as you'd expect. I have to hold it and caress it with my warm loving hands to get it to respond.
now ---
this is not related to CM 6.1. at all. Ive flashed a lot of things since visionary and its happened on every single rom.
Id go get that phone out of the mail if I were you OP.
I have also noticed the problem with touch screen responsiveness when my G2 is mounted in a car holder.
I have figured that you just have to keep one finger on the aluminium body and the problem is gone. I have to admit that this is somewhat bizarre and I have never had this problem before with my G1 using the same car holder. Seems that there is an issue with electric isolation? I don't exactly understand how capacitive touchscreen works so can't really explain where the dog lies buried.
Maybe this is a feature. Protection and saves battery.
vision...
squbel said:
I have also noticed the problem with touch screen responsiveness when my G2 is mounted in a car holder.
I have figured that you just have to keep one finger on the aluminium body and the problem is gone. I have to admit that this is somewhat bizarre and I have never had this problem before with my G1 using the same car holder. Seems that there is an issue with electric isolation? I don't exactly understand how capacitive touchscreen works so can't really explain where the dog lies buried.
Click to expand...
Click to collapse
The same for my DZ - it is kinda weird, because if the phone is for example in the car holder it is impossible to use the touchscreen unless I put another finger on the phones housing. I tried different roms already, but the 'error' is still there.
It would be interesting if all users have the same problem or if it is just a few examples of phones out there.
Thanks,
Robert
Wow,.... only just noticed this a few days ago. Along with it not vibrating on incoming SMS, i'm starting to get slightly ticked off.
yeah happens to mine too =P
happens to mine also, nothing we can do about this?
ROM: CM9 Kang by winner00
Kernel: Lean Kernel by imoyeson
Basically, I was undervolting the phone, and while testing, the entire screen started rendering a green static-y like thing. Imagine static on TV, but with green and yellow. The touch screen was still responsive (the phone vibrated when I touched the area where the home softkey was). I immediately battery-pulled and reset the phone, and the screen seems to be working now.
Is this hardware damage, or is it a possible result of too much undervolting?
On the other hand, could the GPU have failed?
EDIT: I raised the voltage by 20V to 735V for 350 Mhz, and it crashed again. I'm now running on the default voltages for the kernel and it appears to be stable.
Probably from undervolting.
zephiK said:
Probably from undervolting.
Click to expand...
Click to collapse
But the part that confuses me is how undervolting would cause the screen to stop rendering properly, while allowing me to still use the touch screen and shut down (after holding down the power button and tapping in approximated locations)
I would guess that it's an issue of how the power draw is handled. By undervolting that much, you essentially had enough power to utilize the Android OS and the capacitive panel, but the GPU just didn't have enough kick to display the screen properly.
It could be a Kernel issue.. Franco's kernels used to have a similar glitch. Was a blue static look on mine though.
Sent from my Galaxy Nexus using xda premium
clichename122 said:
ROM: CM9 Kang by winner00
Kernel: Lean Kernel by imoyeson
Basically, I was undervolting the phone, and while testing, the entire screen started rendering a green static-y like thing. Imagine static on TV, but with green and yellow. The touch screen was still responsive (the phone vibrated when I touched the area where the home softkey was). I immediately battery-pulled and reset the phone, and the screen seems to be working now.
Is this hardware damage, or is it a possible result of too much undervolting?
On the other hand, could the GPU have failed?
EDIT: I raised the voltage by 20V to 735V for 350 Mhz, and it crashed again. I'm now running on the default voltages for the kernel and it appears to be stable.
Click to expand...
Click to collapse
Uv'ing too low. Try uv's close to -200 mv. Running too low causes instability. Instability can cause more power drain or glitches like mentioned. I could run stable @ ~300mv but had to bump up to see improvement in battery and heat. I am now running @ ~-250mv but ymmv. Try ogdobber uv setting in the James Bond kernel thread. A lot of people are having success with his settings.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
Today...the unthinkable happened.
I dropped my phone from about 3 feet!
Luckily, I had a case on it, and there wasn't any damage to it...cosmetically. When I went to make sure there wasn't any internal damage, I tried a SetCPU stress test, a quadrant benchmark, an antutu benchmark, and a Linpack benchmark.
SetCPU was stable, quadrant was higher than before, and linpack was about the same. However, when I got to Antutu, my score was about 1000 less than before.
Before, I got RAM=~950, CPU Integer=~1825, and CPU Float=~1427. However, now I get RAM = ~700, CPU Integer = ~1350, and Cpu Float = ~1150. Everything else was about the same.
I should also note that at the time of testing, the phone was pretty hot (100 degrees Fahrenheit). The original scores were achieved on 80-90 degrees. Would you say this is a coincidence (and it was caused by heat), or hardware damage?
Coincidence.
Sent from my Galaxy Nexus using xda premium
I can run quadrant twice, doing nothing between tests but push the start test button, and get two completely different scores.
It was the heat after all. I let it cool down to 80 degrees fahrenheit, and it's back to the normal 6000+ scores. I feel so relieved now.
Did you pick up all the binary bits from the floor? Maybe some bits fell out so phone is still busy looking for the missing bits.
Sent from my Galaxy Nexus using XDA App
You're fine. Luckily the phone was ok. I think I would crap my pants. What case are you using?
Sent from my GSM Galaxy Nexus using Tapatalk
Ulver said:
You're fine. Luckily the phone was ok. I think I would crap my pants. What case are you using?
Sent from my GSM Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Incipio Sylicrylic
It has this awesome silicon layer that absorbs the impact.
rubiconjp said:
Did you pick up all the binary bits from the floor? Maybe some bits fell out so phone is still busy looking for the missing bits.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Nonphysical stuff can't fall, silly.
clichename122 said:
Incipio Sylicrylic
It has this awesome silicon layer that absorbs the impact.
Nonphysical stuff can't fall, silly.
Click to expand...
Click to collapse
Lol
Sent from my GT-P6800 using xda premium
My HTC One M8 fell by 2 feet. On the corner; has hard shell.
After this, the phone was very slow. The kind of slowliness I do not try to dig, and just reboot. Reboot took over 5mn. Then, phone kept screen off; I knew the phone was working: received a phone call; power button was working fine because long press on it could light the flash (Xposed customisation); volume buttons also work fine. After long press power+volume, I could reboot, and during reboot, the screen came one again. Screen could turn on each time I rebooted. After boot was completed, if I let screen timeout and go of, no way to turn it on again.
If I don't let screen go off, and keep it busy, and try to use my phone:
- background image animation lags a lot
- tactile screen works almost fine
- apps are responsive, but viewing on screen lags a lot.
- all system tools report a good iddle time, low load, and available CPU and RAM.
- the whole phone behaves like when it's over-heating, but temperature was low. The problem was perfectly reproductable during several hours.
- system behavior could also be compared toa computer working with full software rendering, without any hardware acceleration. CPU and RAM feel good, CPU reports iddle time, but graphics lag.
Power button was working fine on hardware side because i could use it to force reboot, and switch light on. But power button could not turn screen on. Hardware of screen was working fine, because after reboot, i could get a working screen. But, how could a simple fall produce a software issue ?
I had replaced my battery myself some time ago; so, I know that I have not glued it the way it's done at the manufactory; also I had to break tapes, and could not replace them. I have placed all screws correctly. My thoughts have been:
- CPU or GPU are not strictly overheating, but, maybe their physical connection to heat sink is bad
- maybe the battery moved a bit, and is pressing against something, deforming a heat connection, or pressing hard against a sensible component (and alter it's value)
- inertia could have pulled a cable out of it's plug; maybe there is a bad connection somewhere. Power lines had poor connexion providing too little current (or undervoltage); data line disconnected.
If the GPU is partly broken, system can fall back in software rendering, and a broken GPU may not imply a loss of screen; just switching to an other video mode.
After leaving the phone off for 1h, and rebooting 12 times, phone works perfectly fine again.
There is no way this could be a software issue.
It was a hardware issue, that had very little impact on something, and fixed itself after some hours.
May not be GPU itself, but really thinck it was "video related".
I've read somewhere that others are having the same issue I'm experiencing. The phone gets progressively warm to the touch as u get closer to the home button. I think it got lost in the forum break up but I was wondering if its worth exchanging while I still can or is this normal for the s3?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
cavsoldier19d said:
I've read somewhere that others are having the same issue I'm experiencing. The phone gets progressively warm to the touch as u get closer to the home button. I think it got lost in the forum break up but I was wondering if its worth exchanging while I still can or is this normal for the s3?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
It's pretty much normal phone is very thin is very powerful there's nothing to absorb the heat.
I have had mine replaced once already, but not for overheating. Both phones I have had get the same amount of hotness in the area you describe, but I don't think its a cause for concern. I'm running overclocked at 1.8GHz right now and haven't noticed it getting any hotter. You should be just fine.
My Galaxy S3 i747m from Rogers run quite warm as well... After some Counter Strike Portable for about an hour, my phone is pretty warm especially on the front of the glass...
The back is pretty warm as well.
I use the widget Battery Solo from Google Play store to check my phone's internal temperature and it hit around 46 degC (pretty high for a phone lol)
Running all stock: ROM, CPU speeds etc..
My old Captivate never hit more than 35 degC even under some gaming..
Having a phone that is thin and faster than my 2010 MSI Wind netbook is probably the trade off for the heat. I mean on my MSI Wind, there are fan and vents.. On the S3 there is definitely no fans and no vents. Not to mention passive cooling since the phone is practically a complete Plastics build....
If the S3 has more metal especially on the outer housing (battery cover for e.g.), then the metal piece could act as a passive cooling solution...
***I just checked on eBay, and there are aluminum battery replacement covers for the Galaxy S3 all variants. The aluminum 3rd party covers will maintain the Galaxy S3's thickness so all your cases would fit.
BUT IN THIS CASE, the cover will not act as a very effective passive cooling solution due to the interior of the batter cover is covered with plastic, and only the outer layer has a very thin piece of aluminum plate.
Technically though, the aluminum battery cover from eBay may give the phone a slightly more solid build... Not to mention it comes in different colors as well... I have already ordered the Lime Green for my White GS3 ^_^
Try flashing a different kernel. I prefer using Ktoonsez's kernel, but it's totally up to you.
But as mentioned above, the device getting hot is normal, since it has to hold a massive screen with thin design. I wouldn't expect too much difference.
Thanks guys.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
cavsoldier19d said:
I've read somewhere that others are having the same issue I'm experiencing. The phone gets progressively warm to the touch as u get closer to the home button. I think it got lost in the forum break up but I was wondering if its worth exchanging while I still can or is this normal for the s3?
Click to expand...
Click to collapse
Your sig says you are using AOKP. I had the same observation (phone gets warm and sometimes hot) when using both the ICS and the JB AOKP versions. I have cpuspy installed and it shows the 1512 Hz being used quite often on the AOKP builds compared to say the stock sammy ROM. This in my opinion contributes to the phone getting warm.
I do not believe this is really an issue per se - it might be just that the AOKP kernel deals with CPU scaling freq a bit differently.
The stock Sammy kernel does a great job of utilizing the lower freqs which makes the phone run real cool.
Tophaholic said:
Your sig says you are using AOKP. I had the same observation (phone gets warm and sometimes hot) when using both the ICS and the JB AOKP versions. I have cpuspy installed and it shows the 1512 Hz being used quite often on the AOKP builds compared to say the stock sammy ROM. This in my opinion contributes to the phone getting warm.
I do not believe this is really an issue per se - it might be just that the AOKP kernel deals with CPU scaling freq a bit differently.
The stock Sammy kernel does a great job of utilizing the lower freqs which makes the phone run real cool.
Click to expand...
Click to collapse
My phone ran about the same temp even on stock ROM.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
overheating fixed...
I have know this problem with my S2, it even burned my SD card I had to reformat...
I have met the same phenomenon on my new S3 with a battery I had to recharge twice a day...
I think to have found a solution, look at \parameters\battery. You will distinguish the percentage of consumption of each application in use. And in my case, it was the application "Multimedia" which consumed up to 60%. We can force a complete stop. What I did. Since the opening of a photo takes just a little longer, but my battery is 48 hours and without overheating ...
Ya mine too gets hot at about 43ºC, while playing games... rest is fine.... its slim design is the main cause I beleive. ... nothing to worry....
Sent from my SGH-I747M using xda premium
My phone also has overheating problem while playing games/videos/ browsing with Mobile data
I'm almost certain that I am not the only one who has had this problem, but I would really like to know if anyone is working on it.
When charging my HOX, I notice a considerable drop in all aspects of the touch screen. I am currently running IceColdJelly, and have noticed it significantly when typing out an SMS. I would hit one letter on the keyboard and the tactile feedback will go nuts and i would have ended up typing out a bunch of Q's with a large amount of spaces.
More to the point though. Has anyone looked into why this happens? and if there is a fix? It is really making me despise my HOX, which frustrates me because it is such a great phone when not charging.
It's not a good idea to use the phone whilst charging. I've heard of heating issues and someone electrocuted answering the phone. I stopped making calls on my xe earlier because of bursts of sharp pain on the ear whilst it was charging.
I’m not quite sure the reason for it, but I too have experienced it from time to time with different phones, and I have also seen few others complaining about it as well. Are you using the supplied HTC charger and USB cable ?
Does it happen with all chargers (different brands etc) and USB?
Edit: somehow I missed the post above. Where is the delete post button?
I've noticed this as well. I'm not sure if it's for the same reason but when I had my old Sensation it was pretty severe and the solution was to change the scheduler (?) to 'on demand', if you have an option that allows it. This fixed the problem completely. It was something to do with having 'interactive' selected.
However, I'm not sure whether the cause would be the same thing with a stock rom with stock kernel.