Related
Hi
I have a weird problem...
Sometimes (not always, but like once every two days), my Hero just scrolls to the right in like every app... even on the homescreen
For example:
-on the homescreen, he scrolls to the right, so towards the last homescreen.. I scroll back, but de hero has its own will and scrolls to the right again...
- in the browser the Hero scrolls to every link (like I would scroll with the scrollbal to the right and it jumps from link to link)
- in an app with different tabs (like People) my Hero also scrolls to the tab on the right, so he goes from "all contacts", to "faorites", to 'groups", to "updates and events" etc...
- in messages, when I want to begin typing, the button "send" is selected in green (like I would've scrolled to the right)... when I'm typing, it doesn't occur..only before I've started typing...
also, I've noticed that like in the browser, when I hold my phone horizontally, the problem doesn't occur.. and when I hold it back ertically, the problem is gone (I think....) ...
Anyone who knows this problem ? Pretty weird, I know
Thanks in advance !
greets
PS: maybe it has to do with the G-sensor (cfr. holding horizontally: no problem...)
I guess that your problem is the trackball, it may be a bit loose on one side so that it will roll sometimes to the right.
Mine does this from time to time. I think it is dirt under the trackball. I just sping the trackball round a few times and it goes away.
HTC support instructed me to send the device to warranty repair due to this issue. Haven't done so yet, though.
Same here, also i think that is a only dust.
After re-spining TB it goes back to normal state
This has been demonstrated a common problem with the Hero. They told me to restore the firmware which is bull. Something's broken, hardware or software we don't know but I should think hardware.
Yeah, I'm still not sure whether this issue is software or hardware related. The whole dust thing seems a bit weird. Especially when my Hero accidently did this -right- after I got it out of the box and started it for the first time.
It's annoying though, but a flick of the scrollwheel always fixed it so far. (or reset)
Ah... I posted previously about this- My fault. Looks like a common problem.
Has anyone found a solution that works?
I also have this problem, for a while I thought it was only me...
I have same problem from time to time, not very frequently.
It's not a "dirt" problem, it has something to do with magnetic fields, which affect the trackball's logic. That's why you see this from time to time, at special areas.
Since a couple of days I have a new problem... the automatically scrolling to the right doesn't seem to appear anymore, but now I can't scroll anymore to the right with the trackball... all the other directions work... could this be software-related then (it cannot scroll anymore in the same direction it used to scroll automatically to...) ??
if it is just dirt... nay idea how to clean that? I've tried rolling with the TB a lot in different directions and even tried with a light moist cloth...
Pr0sper said:
It's not a "dirt" problem, it has something to do with magnetic fields, which affect the trackball's logic. That's why you see this from time to time, at special areas.
Click to expand...
Click to collapse
What, the Earth's magnetic fields?!
Actually that would explain a lot! I followed the textbook advice, and re-flashed the ROM. All was ok until this morning, and the screen started leaping left, rather than right!
...So I've reset the device, and downloaded the ROM again, and reflashed.
I have to say, I'd be surprised if it was a "dirt" problem, because every HTC I've ever owned has been very well sealed. (Unlike my Nokias!)
Is there any way to test if it's magnetic? (I guess "with a magnet...")
Ths has been discussed in greater detail here.
http://forum.xda-developers.com/showthread.php?t=546206
Hmmm... no closer to an answer though. I'll see if my re-flashing helps and will let you know.
I'm not sure it's worth returning my unit: sounds like it's a generic defect.
My network definately alters a lot as I travel a great deal. And I'm often in/out of Wireless zones.
Yesterday I tried the simple solution I turned off the device... put it back on.... and everything seems to work properly now even the trackball scrolls great again... don't know about you guys, but this solved the problem for me sometimes, the answer is just around the corner...
It happened on mine today (this morning when I came in to work) but it went away after it warmed up. It was cold this morning (2 degrees C or so).
It's not associated with WiFi, and I've tried resetting, reflashing and even switching off.
The problem keeps coming back though. It's completely random and really annoying...
singing hound said:
It's not associated with WiFi, and I've tried resetting, reflashing and even switching off.
The problem keeps coming back though. It's completely random and really annoying...
Click to expand...
Click to collapse
I am convinced this is a software issue. The problem is easy to reconstruct:
It is as simple as this: If there is data traffic in the background while on Edge network, this happens. I cant see how this could be a hardware problem. I have found this since I am on a train 3 hours every day and has had a lot of time to figure this out.
Sadly I havent found a way to disable edge network.
raskall said:
I am convinced this is a software issue. The problem is easy to reconstruct:
It is as simple as this: If there is data traffic in the background while on Edge network, this happens. I cant see how this could be a hardware problem. I have found this since I am on a train 3 hours every day and has had a lot of time to figure this out.
Sadly I havent found a way to disable edge network.
Click to expand...
Click to collapse
That's useful: I also commute daily and I think yours is a likely solution.
I just wonder if this is a problem with a batch of Heros... otherwise you'd think everyone would be suffering. It sounds like if I exchange my unit, there's every chance the new one would have the same problem.
Is there a way to disable my trackball for somereason itt scrolls itself down every 10 or so seconds its not a huge problem but its annoying as hell
Motochris said:
Is there a way to disable my trackball for somereason itt scrolls itself down every 10 or so seconds its not a huge problem but its annoying as hell
Click to expand...
Click to collapse
Did you know that you made two threads with the same question?
As far as disabling the trackball, someone has probably done it; I think only through hardware though, not software. You'd have to take apart your Eris and disconnect the appropriate wiring to the trackball.
Your mileage may vary, but before you do that you could try some things that have worked for different people.
You can press VERY hard on the trackball while rolling it around in the different directions and then see how it behaves afterwards. Well, I can't really think of other examples of what people have tried.
Mine only misbehaves while it's plugged in, normally, and then only when I touch anywhere near the trackball or touch the charging cable. The proximity of the USB port and the trackball is one of the reasons the trackball misbehaves. Once in a great while, every couple months or so, I have to press down hard and roll it a while again, and I pressed so hard at one time that I can't actually normally scroll left, but I can scroll the other directions, which is fine, it doesn't bother me that often.
Is your phone rooted? The reason I ask is that there is a replacement version of Amon RA recovery which doesn't require the trackball, in case yours stops working altogether.
I am *not* responsible for what may happen to your phone as a result of my advice.
It may have been because it was plugged in thanks for the advice. it is rooted running froyo because that seems to be the only fast rom
Motochris said:
It may have been because it was plugged in thanks for the advice. it is rooted running froyo because that seems to be the only fast rom
Click to expand...
Click to collapse
You're welcome. I forgot until now also that sometimes jiggling the USB cord at the phone end sometimes helps (expect the trackball to definitely go wonky while doing so, of course). It may take unpredictable combinations of both this and pressing while rolling the trackball to make things a little better, also.
**Please note, i have already searched this forum and found some similar threads as: charging paused, voltage too high, SGS2 charged all the time, Charging suspended. Voltage too high and Phone keeps charging after plugin off the charger but none of them had exactly my problems so i'll try to describe mine better here.**
Some background and possible cause first
I have been using Omega ROM @ 2.3.5 (yes it's old, but it doesn't matter) for more than 6 months now and i haven't had any problems with it, but a few weeks ago i decided to upgrade to ICS so i did a full backup with CWM and also backed up sdcard to pc. Did a full wipe, formatted sdcard and installed the AOKP ICS, hated the camera app, wiped everything again, installed normal ICS, it was looking ok but i needed my usual apps the second day so i decided to go back to my 2.3.5, restored backup, restored sdcard. I don't remember exactly if i had the phone plugged in before installing ICS or after going back to 2.3.5 but when i disconnected it, it showed that it was still connected and charging...
Please note that everything was ok before updating to ICS (which is one reason why i believe it's software related), i used the original mains charger / micro usb cables at home and i also used a cheap car charger but long before this started happening, and the last time i used the car charger was 2+ moths ago.
The thing is, i don't care if it things it's charging all the time, my problem is that when charging it keeps the cpu active, and even when setting it to 100 MHz the battery only lasts about 5-10 hours with low-moderate usage (see the screenshots of cpu spy, it is clear that the phone does not enter deep sleep while it "thinks" it's charging).
Symptoms
At first, it kept showing it was charging all the time, sometimes when reaching ~10% it went back to normal (YES, normal aka reporting as no plugged in and no charging (=discharging), so i don't think there's any short-circuit/something wrong with the usb connector (which i tried to clean up, as suggested, but the problem is still there) :
---
---
Then (and currently) after 1-2 mins of disconnecting charger/usb cable it stops the charging animation but *#*#4636#*#* and some battery app stats show that it's still plugged in but discharging (also it reports over-voltage, which is weird because when it is still charging it shows health:Good).
Also, if it goes back to normal (aka not charging and not plugged) and i connect the mains charger then disconnect and connect usb cable it will still see/think that the mains charger is still connected and i can't connect the mass storage to pc (the dialog never shows, because it still thinks it's connected to mains) and vice-versa, but the battery is charged no matter where it thinks it's connected.
Now the weird part, and the reason why i don't think it's hardware (aka usb pin short circuit or anything else stated in the other threads) if i remove the battery for long enough (something around 10-12 hours) over night, in the morning the phone would be completely normal (i was able to do this 2 times so far and both times the phone clock&date were resetted which makes me think the "connected" state is stored somewhere in a temporary memory powered by a small battery which keeps track of the time and alarms?; also if the time isn't resetted, the phone would still think it's connected (yes, even after removing the battery for some 8+ hours)), but the problem reappears if i connect charger/usb cable (something to note here, if i connect the cable and it's not plugged in, the problem doesn't start so this excludes micro usb connector problem).
---
And also, as in some other posts, while the phone is shut down it keeps showing the charging animation along with some warning high temperature? triangle:
Here is a screenshot of Battery monitor widget showing some weird voltage spikes, is it possible to reach 5V?
The wakelocks (from Better battery stats app):
Also, something that i've wondered if all S2s do, when i remove the battery and plug in the charger (of any kind) the phone shows a no battery image:
One other thing that might worth mentioning is that sometimes, just a few seconds after i lock the phone, the screen just lights up for a second then turns back off for a few times (2-5 times), but this might be just an app problem and it's not really currently bothering me.
Also i just noticed when posting the screenshots that the battery is always pretty hot, is 32 - 37*C too hot or is it ok?
Conclusion
Well, it's been 3 weeks since this problem has started because i updated to ICS and i still didn't fix it. My plan is to order an Usb jig from ebay, get everything back to stock and send it to warranty, but this will take some 2-3 weeks until i get the jig and another 2-3 until the guys fix/replace it so i'm posting here hoping for some suggestions from more experienced members or people that also had this problem, because i ran out of ideas to try here.
It's a very nicely thorough post, very detailed. I like it.
However, I believe your conclusion that it isn't a hardware issue with the port is a faulty one. I think 100% of the times I've seen issues like this it's an issue with the port that is resolved either by cleaning it, (which will likely only be a temporary solution) or replacing it. It's VERY likely they will do just that (replace the port) if you send it to service. If you can get it covered under warranty, do it. Otherwise the part will run you probably $15 or so, USD.
But the fact that the problem comes and goes away without physical actions and also the fact that everyone started getting this after upgrading to ICS makes me a bit suspicious...
dany123i said:
But the fact that the problem comes and goes away without physical actions and also the fact that everyone started getting this after upgrading to ICS makes me a bit suspicious...
Click to expand...
Click to collapse
And the fact that anyone who experiences issues like this, when they replace the part, it fixes all these issues?
if it comes and goes, I'd check the port for something when the issue is present. There's likely something lodged in there when it's happening, which gets dislodged when it's NOT happening.
People tend not to protect the port. It can get damaged over time. Also, ICS versions will seem more sensitive to it, because of additional programming and error messages specific to charging and voltage errors added in.
ctomgee said:
And the fact that anyone who experiences issues like this, when they replace the part, it fixes all these issues?
if it comes and goes, I'd check the port for something when the issue is present. There's likely something lodged in there when it's happening, which gets dislodged when it's NOT happening.
People tend not to protect the port. It can get damaged over time. Also, ICS versions will seem more sensitive to it, because of additional programming and error messages specific to charging and voltage errors added in.
Click to expand...
Click to collapse
Or ICS screws something up permanently or maybe you're right, and it really is the port, anyway i'll still experiment a while until my jig arrives, if i discover anything i'll update the thread.
Btw, thanks for reading my entire post :highfive:
dany123i said:
Or ICS screws something up permanently or maybe you're right, and it really is the port, anyway i'll still experiment a while until my jig arrives, if i discover anything i'll update the thread.
Btw, thanks for reading my entire post :highfive:
Click to expand...
Click to collapse
I just wish everyone who had an issue that needed help was as thorough as you. Most often, posts in Q&A unfortunately look like: "Halp! My fone broked! Whut happen?!?!"
So while some may scoff at the length of your post, they need to understand; when troubleshooting issues, more than enough information is ALWAYS better than not enough.
Don't worry you're not alone.I'm having this issue for about a week and I don't think that it is a hardware issue because my problem appeared when I was doing a restore from backup from custom rom to stock rom and the only thing that I did is that I pulled off the charger while my phone was doing the restore process. The second thing that I think it is not a hardware issue is that my phone is new I bought it two month ago and the USB jig is so clean, I compared to my brothers phone he has sgs2 too and he's USB jig is full of dust and cockroaches and mushrooms and stuff like that but its working perfect. I'm so sorry that I don't have the answer for you but I'm so mad about this problem that I needed to say something and by the way good luck and pm to me if u find the fix
Sent from my GT-I9100 using xda premium
bennycop said:
Don't worry you're not alone.I'm having this issue for about a week and I don't think that it is a hardware issue because my problem appeared when I was doing a restore from backup from custom rom to stock rom and the only thing that I did is that I pulled off the charger while my phone was doing the restore process. The second thing that I think it is not a hardware issue is that my phone is new I bought it two month ago and the USB jig is so clean, I compared to my brothers phone he has sgs2 too and he's USB jig is full of dust and cockroaches and mushrooms and stuff like that but its working perfect. I'm so sorry that I don't have the answer for you but I'm so mad about this problem that I needed to say something and by the way good luck and pm to me if u find the fix
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Please take note.
This is not a hardware problem. This is a Firmware/Backup related problem
Had this exact problem on a friends SGS2 and it kept on happening after he did a restore from Titanium. Not that Titanium is broken BUT your backup stored on your SD has a CRC somewhere. What can I say ... It happens.
Just do a complete wipe and install the Rom you want. DO NOT RESTORE YOUR BACKUP !!!
Install everything again as per normal and set it up and you should be good. If this then still occurs then you can be sure its the hardware but this resolved it for him,
toxicdust said:
Please take note.
This is not a hardware problem. This is a Firmware/Backup related problem
Had this exact problem on a friends SGS2 and it kept on happening after he did a restore from Titanium. Not that Titanium is broken BUT your backup stored on your SD has a CRC somewhere. What can I say ... It happens.
Just do a complete wipe and install the Rom you want. DO NOT RESTORE YOUR BACKUP !!!
Install everything again as per normal and set it up and you should be good. If this then still occurs then you can be sure its the hardware but this resolved it for him,
Click to expand...
Click to collapse
I think it's a bit presumptuous to say it's DEFINITELY not a hardware issue. I've seen a TON of posts where people replace the part for the USB port and the problem disappears.
Maybe for someone its is a hardware problem but my problem appeared during restore from buckup.
Sent from my GT-I9100 using xda app-developers app
Same problem
dany123i said:
Or ICS screws something up permanently or maybe you're right, and it really is the port, anyway i'll still experiment a while until my jig arrives, if i discover anything i'll update the thread.
Click to expand...
Click to collapse
Did you discover the source of the problem? I am having the same issue with my sgs2 (only 6 months old). I have all the same symptoms - it tells me the USB is connected and the phone is charging, and I get the same alternating symbols when the phone is off (battery charging/temperature warning). I have done nothing out of the ordinary - no system alterations, all is as it was when I got it, other than apps etc I have downloaded. The port doesn't look that dirty, although having read your posts I am inclined to think that this may be the source of the issue? Any help would be appreciated!
solved
Same issue after upgrade, was searching for days ...
Factory restore, but didn't work.
Forced to stop all services, cleared all cache and cleared Ram and after restart everything back ok. Was not a hw issue.
toxicdust said:
Please take note.
This is not a hardware problem. This is a Firmware/Backup related problem
Had this exact problem on a friends SGS2 and it kept on happening after he did a restore from Titanium. Not that Titanium is broken BUT your backup stored on your SD has a CRC somewhere. What can I say ... It happens.
Just do a complete wipe and install the Rom you want. DO NOT RESTORE YOUR BACKUP !!!
Install everything again as per normal and set it up and you should be good. If this then still occurs then you can be sure its the hardware but this resolved it for him,
Click to expand...
Click to collapse
I agree with this guy over here, just wanted to congratulate you for this post.
And yes...back ups can be a BH.
Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I put Foxhound ROM on (I'm just used to having to upgrade the rom) and am finding that the sound will work fine after a restart, but then, after it has gone to sleep all sound will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility, what an odd option).
I've tried two ROMs and three kernels.
I've tried searching google and xda for hours but haven't found anything that wasn't related to the headphone port; this affects both speaker and headphone, although when the headphone is in and the sound has died I can hear some strange static noises when it's meant to play sound, could be interference or a clue.
I've dismantled the phone and inspected for damage, nothing obvious. While dismantled I tried applying pressure to the speaker flex cable and various other IC's to no effect.
It really seems like a software glitch since it only happens when the device goes to sleep;
You can turn the screen off and unlock within 3 seconds and it will be OK.
If you wait 5 seconds with the screen off - boom, no sound.
Any ideas? Is there some deep idle sleep setting that kicks in after 3 seconds I can disable or some way to log audio errors or... something?
Thanks
defroster said:
Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I put Foxhound ROM on (I'm just used to having to upgrade the rom) and am finding tht the sound will work fine after a restart, but then, perhaps after it has gone to sleep once or twice (never more than a few minutes unless I'm plying a game, in which case it stays on just fine) the sound, all sound, will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility, what an odd option).
Any ideas?
Click to expand...
Click to collapse
May Be The Phone Was Damaged, Try Stock ROM
i'm downloading a different ROM now but it takes hours (rural australian phone lines...)
same result with a different ROM =/ I've fixed many phones, computers etc before but not sure what to investigate here, guess i'll dismantle it and see.
A second rom and kernel same result.
Seems to lose sound as soon as it goes to sleep (screen off), really seems like a software problem but can't find any other reports on this phone similar.
Help!
Anyone?
Looks like a software problem but can't say where you can look.. If kernel is not the cause..
Maybe hardware after all..
sent from here, there, somewhere!!
The only way I can imagine it being hardware is if it's heating an audio ic during boot to make a connection and then when sleeping it cools and the connection is lost. It's a long shot but if it's software why is it not happening to anyone else? No weird software installed or anything.
defroster said:
The only way I can imagine it being hardware is if it's heating an audio ic during boot to make a connection and then when sleeping it cools and the connection is lost. It's a long shot but if it's software why is it not happening to anyone else? No weird software installed or anything.
Click to expand...
Click to collapse
Does the sound still work through headphones (after the sound stops working)?
Sent from my GT-I9300 using Tapatalk 2
no, it doesn't seem to be headphone jack related.
the only thing I changed (aside from the rom) that I can think of that MAY have done something is some network setting for my carrier (vodafone .au) - there was an option in foxhound rom or something, but I can't for the life of me remember what it was called, I googled it at the time to see what it was but have since lost the browser history, it was some feature of the phone network that stops sending requests to the network when the phone is sleeping or some such... I'm really grasping at straws there though.
can't seem to find a stock rom for Australia either?
updated OP with more info, sorry for the bump, i'll let this die if no-one's got any ideas.
defroster said:
no, it doesn't seem to be headphone jack related.
the only thing I changed (aside from the rom) that I can think of that MAY have done something is some network setting for my carrier (vodafone .au) - there was an option in foxhound rom or something, but I can't for the life of me remember what it was called, I googled it at the time to see what it was but have since lost the browser history, it was some feature of the phone network that stops sending requests to the network when the phone is sleeping or some such... I'm really grasping at straws there though.
Click to expand...
Click to collapse
I think you are talking about fast dormancy toggle.. But I do not think it will cause any problems.. Also as you have already done factory resets an app should not be a problem..
I can only think of hardware faults..
sent from here, there, somewhere!!
yes i just finally remembered it and tried disabling, you're right, no difference.
I'm having trouble figuring out how hardware could be the culprit though, since it's triggered by the screen off for more than 3 seconds, there's something in software causing it.. but you're right, why does it persist over a wipe then? argh!
Downloaded stock rom, problem remains
Hi guys! I'm new around here, I've been lurking the forums for the past year or 2.
I originally had a i9000. Had it rooted, flashed & running 4.2.2 Hellybean, it was a dream, easiest android phone i've ever dealt with.
Today, I bring you a device that is so mind boggling and mysterious, it's ridiculous. Before you ask, yes I've searched and searched countless hours on end & sleepless nights. Trying to work out how to PERMANENTLY fix this device.
Straight up, I'm going to tell you what I've done, what I've tried, where the phone came from, model of the phone & all the useless stuff.
OKAY. Go.
I got the Samsung Galaxy S2 (i9100T) off a friend recently, about a month or two back. He didn't have a back cover for it, and the camera was all smashed up (back camera). It was running on 4.1.2 Vodaphone Stock DVLSH. It had a few issues when the phone got to me.
I wasn't sure if the phones battery was depleted, but I had to muck around with the phone for a couple of hours just to get the damned thing to turn on.
When I had got the phone to turn on, I kept getting "Warning! Battery Disconnected!" messages, this was frustrating. I eventually let the phone fully charged before I mucked around with it and ignored the warning.
When it was fully charged, I went straight to rooting it. I first rooted it by flashing CF-Root and then flashed a custom rom. (Xylon AOKP. 4.2.2)
From here on, the phone started to randomly restart, drop signal, lose battery after random restarts, get semi boot loops.
So I flashed a different stock (XWPL8) and got rid of the Samsung Galaxy SII i9100T boot logo and it was changed to Samsung Galaxy SII i9100.
After this, I then again rooted the phone but this time a different method and used Siyah kernel and flashed Carbon rom 4.2.2.
I still encountered the same problem as Xylon 4.2.2.
So I kept reverting back to stock, re-rooting & trying again.
I've tried countless methods.
POSSIBLE HARDBRICK RECOVERY DON'T TAKE MY WORD THOUGH: I've even managed to HardBrick the device (yes I mean hardbrick, i didn't even JTAG to bring it back... I flashed Dorimax Kernel at some point and it hardbricked it to all ****.) I spent a few days trying to unbrick it when finally I just plugged it into the charged and forced it to internally turn on (i believe) and let the battery deplete (the phone was hot even when i unplugged it. So I let the battery drain.) Yes I even battery pulled and tried to reboot it to see if I could boot recovery or download or the rom even before I tried any of this! (absolutely nothing.)
I took out my SIM card after a full day of letting it drain (just to be sure) plugged it in, took out the battery while the charger was plugged in, put the battery back in, unplugged the charger while holding power, and plugged it back in and I got the charging logo booted into download mode after 80% charge and flashed stock again.
Now the problem(s) with the phone:
SEMI-BOOTLOOPS: Every time i've rooted the phone and even flashed different roms just to make sure, it does a "semi boot-loop" I've searched everywhere for people with the same problem but found nothing on it.
What it does, is it turns on (boots the samsung logo.) turns off, turns back on, turns off, turns back on etc and then after about 2-8 times of doing is usually it boots to the ROM and the phone works for awhile.
RANDOM REBOOTS: I don't get these much anymore since I found a solution where someone had just folded up a receipt and pushed the battery up against the prongs because it had about .5mm movement off the prongs. This fixed most of the random reboots and don't see many anymore.
SLEEP OF DEATH!?!?!? OR JUST A BLACK SCREEN THAT DOESN'T TURN BACK ON!?: This one I'm not 100% sure what it is, I read it's the S.O.D (Sleep of Death). Which is common on 4.0.4 and was apparently fixed in later Android versions. But sometimes, when I lock my phone, or my phone goes to sleep, the screen stays black even after I press the home button or the power button, at first I thought just restart it by battery pull or holding down power like everyone says, yeah it works, my phone boots up and does a semi-bootloop and goes back on eventually, but one day I left it on in the mysterious S.O.D. and waited 5-10 mins pressed the power button and it unlocked... This one really has me baffled and it does it a LOT.
REALLY BRIGHT SCREEN AFTER REBOOT SOMETIMES!: Okay, so sometimes when the phone finally turns on, the screen is really bright, like the brightness is still on half, but it's a lot more noticeable on how much brighter it is, it's nearly like a white.
It's really really BRIGHT. Phone shouldn't be able to look/get that bright. After a reboot though it goes away and goes back to normal but this leads me to believe something to do with the battery just a hunch.
RANDOM FREEZES!??!?: Sometimes the phone will just randomly freeze, I can be doing something and it'll just freeze, it won't turn off, I still get picture on the screen but it's frozen and I can't do anything until I either battery pull or reboot it by holding down the power button.
Before anyone asks, yes, I Factory Reset from recovery, Wipe Cache & Dalvik Cache before, I flash a new rom etc.
- My GApps matches with my Android versions each time.
- The ROMs I have flashed are compatible with my phone.
- And I've made sure everything I have done is completely compatible with my phone and android version.
What I think!:
SEMI BOOT-LOOPS:
This one, I don't think much of, it's got me baffled. It could be something to do with the Boot-Loader, could be something to do with a bad flash (but I've even tried double flashing a single rom.)
the eMMC could be damaged in a certain way that it causes these self proclaimed "semi boot-loops"
RANDOM REBOOTS:
This one, I've pretty much fixed with the help of lurking the internet over and over for hours, so this indicates a battery problem, will be replacing it this week. (Yes I'm aware that this battery problem could be causing everything else to play up and that it could all be due to the battery but can we leave the battery out of this just for now so I have more options on how to fix it.)
SLEEP OF DEATH!?!?!? OR JUST A BLACK SCREEN THAT DOESN'T TURN BACK ON!?:
I believe that this could be due to either a high load on the CPU (maybe not so much high but a really low load that it goes into a state of nothing for awhile.) It drops into a mode where it's turned off (something bigger than deep-idle.)
REALLY BRIGHT SCREEN AFTER REBOOT SOMETIMES!:
I haven't changed voltages or messed with any voltages on my phone, but I believe that it does indeed have something to do with the CPU & GPU voltages or even the BATTERY Voltages either undervolting or being to high.
RANDOM FREEZES!??!?:
I think this one is something to do with my phone not liking the voltages stock set to it.
I read that somewhere Freezing the System Alarm Clock can fix the random reboots, so I've done that and also pushed the battery up with a bit of receipt so it touches the prongs completely.
Anyway, right now, the phone is on Stock Kernel with CWM Recovery6, with PacMan's 4.3.1 Nightly release on XWLP8 Baseband and it still does this all.
I know i'm asking for a lot of help and I'm probably going to get yelled at by Devs or forum mods or some body because I've done something wrong.
But if it doesn't belong here, move it please.
IT TRULY IS A PHONE FROM HELL.
-Thanks, Just another man who wants to fix silly problems for fun.
Youve said "dont mention get a new battery".What if that is the problem.
Maybe the phone has water damage, or it needs that hawkerpaulls scripts run.
Youve just got to try free stuff, then maybe splash a bit of cash I.e battery.
Nothing software/firmware-side is fixing this. Phone has major hardware issues going on. I wouldn't bother beyond trying the 'free stuff' TheUnderling mentioned.
erm - I'm agreeing with you on this 'phone from hell!' also agree with @theunderling and @MistahBungle - it doesn't sound like its worth fixing if the free stuff doesn't work - sounds like it would probably be cheaper to buy a second hand s2! Don't think dori kernel had anything to do with your 'hard brick' - I've been running dori for some time including the experimental builds, dori tests everything himself as do his team of testers - the 'd team' and I have never known him to release anything that even soft bricks let alone hard bricks.
Good luck :cyclops:
Hey guys thanks for the speedy replies! I love waking up to instant replies!
theunderling said:
Youve said "dont mention get a new battery".What if that is the problem.
Maybe the phone has water damage, or it needs that hawkerpaulls scripts run.
Youve just got to try free stuff, then maybe splash a bit of cash I.e battery.
Click to expand...
Click to collapse
Sorry, I was half asleep when writing all this! I am getting a new battery this week! But I wanted to have a go at trouble shooting it but crossing out the battery from the list of problems seeing as it's being replaced this week @theunderling
MistahBungle said:
Nothing software/firmware-side is fixing this. Phone has major hardware issues going on. I wouldn't bother beyond trying the 'free stuff' TheUnderling mentioned.
Click to expand...
Click to collapse
It may sound like it @MistahBungle but I have faith and I come down to being very patient with technology even when I do reach ticking time bomb mode. I believe I can fix it if I just get the right help !
If the new battery doesn't do anything, It might be the logic board and i'll just go buy a new one.
Jimsilver73 said:
erm - I'm agreeing with you on this 'phone from hell!' also agree with @theunderling and @MistahBungle - it doesn't sound like its worth fixing if the free stuff doesn't work - sounds like it would probably be cheaper to buy a second hand s2! Don't think dori kernel had anything to do with your 'hard brick' - I've been running dori for some time including the experimental builds, dori tests everything himself as do his team of testers - the 'd team' and I have never known him to release anything that even soft bricks let alone hard bricks.
Good luck :cyclops:
Click to expand...
Click to collapse
@Jimsilver73 It really is!
I'm not the most wealthy person or have money to just throw at things like new phones etc etc. I'd love to see what I can do on my side and try and trouble shoot every problem for even the simpilest of DIY Solutions. I get a kick out of mucking with phones and computers.
Your probably right, but I was thinking that does Dori kernel keep stock voltages or does it change the voltages at all? Because it just managed to Hardbrick its self a few hours after flashing it which was odd, which led me to suspect that my phone didn't like the Dori Kernel & Carbon Rom Combination!
@theunderling I will try that Hawkers script by the way!
Is this the one? http://forum.xda-developers.com/showthread.php?t=2100558
Phone having no back cover and camera smashed suggests that there is a physical damage to the phone, i wouldn't even try battery to this one, it may just kill the new battery if there is some kind of water damage, tho you seem like having fun trying to repair it Yes, that's hawkers script, use it and couple of ROMs, (ICS,GB etc) to see if there is a software problem. If you can dissamble it, you can check if there are some contact problems between pieces.
Hi @Dakura thanks for the reply!
The camera isn't smashed completely, but at fist I thought that the camera would be screwing up the phone in someway.
I know for sure as well that there is no water damage, and the phone was just sitting around he lost the back cover randomly after he had bought an iPhone 4S.
I can disassemble it, I just need to find my little screw driver I use for stand-off changing on PC cases.
I read somewhere that the proximity sensor has a bit to do with things, so seeing as the back cover isn't on, that maybe dust got into it while it was in his draw and that's the reason for screen-offs? because the phone is still responsive. I can receive calls & text messages just the screen is black and doesn't come back on.
The warning in 4.0.4 "Warning! Battery Disconnected!" leads me to think that in versions above 4.0.4 (4.1.2 for example) don't have warnings and the phone just turns off.
**major update**
@Dakura @theunderling @Jimsilver73 @MistahBungle
Hey guys, so I've just taken the back CASING not the cover. Off the phone.
I've been looking for breaks in solder points on the Logic Board and around it.
- The Camera ISN'T smashed it was the lens on the case..
- Looks a tad dusty.
- Semi Boot-Loops have disappeared! booted the phone with the case off and the semi boot loops are gone tried booting multiple times each time with success!
- No breaks on the logic board from what I can see as far!
- For some reason the Camera app would not connect to the Camera. "Can't connect to Camera!" maybe the camera flex cable isn't in properly.
- First boot with case off, battery gave false reading of -1021032418914 (something along those lines). That's usually caused by a lose battery correct me if I'm wrong?
- Everything seemed a lot more responsive and working.
Hmmm.
So removing the screws and taking the back casing off made the Semi Boot-Loops go away.
Maybe a part of the back casing was pushing on the Logic board and shorting it out?
Maybe the screws torque where messing with it (e.g. on a HDD with computers the simpliest change in toque on the screws in the HDD can screw the HDD.)
But the torque of the screws where very loose.
Any ideas are much appreciated!!
Yep, probably a short-circuit or dust problem or displacement somewhere around there. What you said proves that somehow the phone was physically damaged. You may need to actually disassemble all the pieces, inspect them and put them all back together, and it still may not work, for now, try cleaning the dust and tighten the screws, fasten the board.
@Dakura thanks for the help today Dakura!
Finally got around to putting everything back together after an evaluation, made the flex-cables all snug and tightened up the screws a lot!
The phone appears to be working now.
at 100% it even vibrates now when i tap things it never used to.
I couldn't quite locate the problem, but I have a feeling that one of the flex cables could have come loose but only just enough to generate fluctuation of power between full and under to keep the phone on.
Hopefully the phone stays stable!
@theunderling thanks for recommending me HawkerPauls Nuke script, I'll be using that every time I re-rom my phone from now on!
Will update the thread on a possible fix for anyone else with this problem.
It's always good to run through every possibility and solution to fix problems before going out and blowing money.