Touchscreen drivers - Very important! - Desire HD Q&A, Help & Troubleshooting

I consider this issue as very important for various causes... First of all it effects a lot of people, second is the fact it can hurt very much the experience with this wonderful phone and another reason is this problem not being PERMANENT. I can 100% confirm that 3-4 months ago I didnt have this problem im suffering from it the last month or so.
Here is a video of the problem itself: http://www.youtube.com/watch?v=vj5z08CC5AQ&NR=1
and here is the discussion from last year: http://forum.xda-developers.com/showthread.php?t=946834&highlight=digitizer
They say that its a problem with the touchscreen driver HTC provides and maybe its somehow connected with the kernel (I dont know anything about developing so...) but I know from my own experience that this problem can happen, I mean a fully functional and SMOOTH touchscreen can Become faulty and buggy screen.
I hope some dev can help all of us who have this problem and do something about the driver\kernel.
Thanks.
ps. I noticed my problem after i flashed few new ICS roms that started to come out... maybe some rom messed up with the drivers ? (i know that after you do all the wipes u can before you install a new rom some information still remains, like the clockwork... and one rom can change the things for all the roms u install after it)
PSS. In the video some people say it can be from water/humidity damage, who can confirm this ? it can turn a good touchscreen to a bad one after awhile in the pocket.

Just want to up this before the weekend... Im considering the pocket phone taking all the sweat is the right reason, I want to purchase a screen protector and change my current one to see if this helps

I'd love to see this problem fixed too. The problem is so annoying, ive been trying to play draw something and it's pretty much impossible cos of the wobbly lines.
I too am convinced this is a driver issue, although i must say i noticed the problem the day i got my desire hd and its been there with all roms i've tried.
I wouldn't mind taking a look into this myself. I know c++ and other languages but i wouldn't know where to start. If someone could guide my in the right direction i might be able to figure something out.

Related

[Q] Boot loop problem

Hi, I have a few questions I hope you can help me with?
My wife has a galaxy nexus, stock and unrooted. It is only around 6 weeks old and last week it started crashing, turning off then getting stuck in a boot loop just displaying the starting colours. I understand this is a known problem, she has software version 4.0.2 and it says her phone is up to date.
I "fixed" her phone once with a factory reset however this time she is away with work till Friday and now has no use of her phone or contractual minuets or data ect.
To make things worst she was planning on using the sat nav and wireless tethering to her laptop. It is the second time this has happened and she has lost all faith in her phone. She can maybe upgrade the software by downloading the 4.0.4 software but she/I don't see why she should have too. She just wants a phones that does what it says on the tin without needing to mod or mess around with it.
My questions are...
Is this problem enough for her to exchange the phone for another phone all together, she fancies a One X. Has anyone here managed to exchange the phone for this reason?
If not will updating the software to 4.0.4 fix the issue for sure? She really needs a reliable phone. Maybe it will be best to send it back under the warranty but we are afraid she will get another GNex with the same issue.
Any advice will be much appreciated
Sorry for the long post and thanks for reading,
Oliver
I would just try updating it and then wipe it. If that doesn't fix the issue it's most likely a hardware issue and I would warranty the phone.
Sent from my Galaxy Nexus using xda premium
Hey there,
Well first I would suggest calming down and not reverting to hardware issues just yet, Bootloops are pretty common, especially when using phones which were meant for the (a bit) more advanced user, it's advantage is also it's flaw, being a modding monster that it is..
And this is by no means a flame - but I wouldn't want my wife to have a GN for that exact same reason, yes - she knows about flashing roms and stuff, but she needs a reliable phone, that will work and do what she needs it to do and nothing more, as opposed to me, I like to mess around a bit with my phones (also not that much, I plan to stay stock with my GN).
To your question, I don't have any experience with RMA's but it maybe worth a try.
You also mentioned she fancies the one-x.. that means she wasn't really keen on buying the GN in the first place (I believe).. and also - and don't take this the wrong way - I think she\you don't really know what the GN is all about, this isn't a phone for everybody, I mean - it is, but it's a shame to see it fall into hands that do not appreciate it for what it is, think of it as a nice new Ferrari, sure - it'll get your wife to work But she is not going to the Nurborgring to time her laps with it.. she'll complain that once in a while the clutch is too sensitive and that she cannot count on the car to take her to work every day, and that she really fancies the new Volkswagen beetle... you get my drift
Also - I believe that flashing to the 4.0.4 will sort the bootloops, which usually has everything to do with the kenrel.
Best of luck!
p.s. All of the above is said in a humoristic way!
omricn said:
Hey there,
Well first I would suggest calming down and not reverting to hardware issues just yet, Bootloops are pretty common, especially when using phones which were meant for the (a bit) more advanced user, it's advantage is also it's flaw, being a modding monster that it is..
And this is by no means a flame - but I wouldn't want my wife to have a GN for that exact same reason, yes - she knows about flashing roms and stuff, but she needs a reliable phone, that will work and do what she needs it to do and nothing more, as opposed to me, I like to mess around a bit with my phones (also not that much, I plan to stay stock with my GN).
To your question, I don't have any experience with RMA's but it maybe worth a try.
You also mentioned she fancies the one-x.. that means she wasn't really keen on buying the GN in the first place (I believe).. and also - and don't take this the wrong way - I think she\you don't really know what the GN is all about, this isn't a phone for everybody, I mean - it is, but it's a shame to see it fall into hands that do not appreciate it for what it is, think of it as a nice new Ferrari, sure - it'll get your wife to work But she is not going to the Nurborgring to time her laps with it.. she'll complain that once in a while the clutch is too sensitive and that she cannot count on the car to take her to work every day, and that she really fancies the new Volkswagen beetle... you get my drift
Also - I believe that flashing to the 4.0.4 will sort the bootloops, which usually has everything to do with the kenrel.
Best of luck!
p.s. All of the above is said in a humoristic way!
Click to expand...
Click to collapse
Thanks for your post.
My wife wanted to upgrade her htc desire to a faster phone with bigger screen, she loves android and Google products and the Google nexus seemed like the best choice at the time (b4 the one X was released) she loved the phone till now.
The phone has twice randomly gone into a boot loop and twice we managed to get it working again both times within the week. This has caused her to lose faith in the phone. I guess the update should fix the issue but it doesn't seem to be available on her phone just yet.
A basic phone would not be enough 4 my wife, as I said in my first post she uses it to connect her laptop to the Internet and as a satnav. Also she watches youtube videos (720p screen is handy here) and for facebook.
We never had any such issues with our desires. When my wife returns home we will update her phone via pc if it doesn't void warranty (I'm sure it won't ) and hopefully the issue will be fixed for good.
Sent from my HTC One X using xda premium
Sounds like our wives can get along my wify loves her htc desire hd! and to be honest, in my opinion in many ways it's much better than the sensation I had (stock).
And by what you described, if I was your wife (lol ) I'd also go for the GN.. I trust you know how to upgrade to 4.0.4, if you need any help just say so and I'll be more than happy to help
Also - from what I know upgrading will not void you warranty, you can simply lock the bootloader once you're done upgrading if you wish.
I really wish the bootloops will stop and that you wife will continue to enjoy her GN!
Hi again
I unlocked, rooted and installed Android Revelution HD 3.0.0 (based on 4.0.4) by mike1986 on her phone.
She is happy with her phone again.
Now it's rooted she likes the extra apps she can now install like AdFree.
I have a quick noob question though..
After installing the new rom her phone it said their is an update available. I understand that she should NOT accept over the air updates now she has a custom rom, and is that right?
Cheers, Oliver
Sent from my HTC One X using xda premium
Hey Oliver, sorry.. seems I didn't get subscription notifications on your reply...
anyway, she "can" download the update, but it will not install, it will simply give an error upon installation, the reason is the original files that the update needs to update are not there anymore, or they are but have changed, so it will just give an installation error.. that's the only downside to having a custom rom. me personally - I like mine stock at the moment
Just a quick update, I rooted, s- offed and install Arhd rom on my wife's gnex.
She says her phone is running faster/smoother than ever and has not restarted since. It's running great and she is happy again
Sent from my HTC One X using xda premium

HTC One V Dead

So I bought my gf a one v and she loves it. One month after using it (stock, unrooted) it just went dead. Doesn't charge and doesn't get into bootloader (but not the QHSUSB_DLOAD and Blank Screen issue). Guy at repair told me that this was an issue with the ICS kernel causing a hard brick. Now, I naturally sent phone for repair since it is a warranty case. So far so good, lets just hope they get it done fast.
My question is though: should I root device and flash another ROM with presumably no such issues so I can avoid a future brick? I mean, I'm using a rooted desire and have no issues for over 2 years, now just didn't want to mess with the new phone of my gf and thought 'hey, lets keep it stock'... But the thought that it would die again after having it repaired is really discouraging. My gf is kind of frustraded and I don't want this to happen again. But are there such issues with custom ROMs for the One V? Like I said, I'm using the good old desire and don't know much about the one v, so I would really apreciate if you can tell me - because if such an issue is possible on custom roms, there is no point to bother flashing and voiding warranty.
Thanks for your time guys!
Well at the moment we have only modified stock ROM for this device and one custom kernel (in beta state) which is still an ICS kernel.
However you''ll never know whether this happens again or not. But one thing you can know for sure is that if you unlock the bootloader and install a custom kernel and ROM and it happens again then your are screwed because you lost your warranty.
Maybe you should wait a bit for some stable custom rom. Because an unstable and buggy ROM would make your gf even more frustrated and andgry
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!
1ceb0x said:
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!
Click to expand...
Click to collapse
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper
falconyx said:
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper
Click to expand...
Click to collapse
That guy should really make his homework. In no way a kernel can brick the phone. If this was true, the phone will not boot and work for weeks in the first place. Its not like the kernel has a "time-bomb" inside and it triggers when it is set.
As I said, it is a phone problem, something hardware has failed.
Hopefully it will be fixed for you gf and she will not have any problems in the future.
It happens in India too
My htc one v got bricked suddenly while using it. Forums at internet says it happens if battery charge goes below certain limit. Mine it went down to 24%
It happened to me when my battery level was 14%. now I have to pay 200$ for repairs. (because I live in Iran.)
HTC ONE V dead
falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
Hi My HTC one V just died , I didn't know how it was happened . 10 minutes before I made I call and just after sometime It stopped working .
Even it is not charging at all, mobile is out of warranty. don't really know what to do ..
Any suggestion would be appreciated .
Regards
Manoj

(Mcgyver: FIXED) MB525 BL7 and Battery: Ongoing

ok long story short. never flashed a kernal before but i decided to try cm10 and went with the gingerbread build and so i flashed the kernal and cm10 compatible rom. it wasnt running very well so i flashed back to the froyo kernal and the compatible cm10 rom.
all was ok but i wanted to go back to cm7 because the phone was considerably faster and so...
today tried to restore one of my cm7 kang back ups from recovery and the phone died. i think what happened is i got mixed up with the back ups and i must have restored the gingerbread cm10 first and without realiszing it flashed the cm7 with a froyo kernal and bang we have a dead phone. it simply wouldnt boot past the google lettering and so when i got home i decided to flash a full sbf and start from scratch however when i tired i got the dreaded battery low error so i followed this
http://forum.xda-developers.com/showthread.php?t=892026
and it worked but rsd lite didnt show my phone. there was simply nothing there when i started it. all very annoying so i uninstalled everything and by the time i started again i got the message battery low.
so my question is can mcgyver work if the battery is actually really low say 10-20 per cent or less?
is it worth buying a new fully charged battery and using that?
why wouldnt rsd lite recognize my phone?
is there anyway to charge the battery when it is like this?
nb. i am running windows 7 sp1 and have installed the latest drivers and rsd lite am my phone is a moto defy m525 red lense.
all very annoying and in five years of rooting and flashing i have never been in a situation where i couldnt recover it. too be honest i have been here before with the defy but i had a spare battery and a proper wall charger and so that was problem solved but i dont own them anymore and i am now not sure/ cant remember if a simple full battery will help hence the questions.
In theory it should work. You are supplying the terminals with the intended 5V and a ground.
However it is recommended to charge your battery, use an external battery charger and then flash the SBF. Its hell of a risk trying to flash SBF with low battery. The phone may actually brick with no way to restore it.
it is strange but using the mcgyver method i can get the bootloader ready to program i simply cant get rsd lite to see my phone and neither does windows. there are loads of posts and threads on this but not many (none actually when the situation i am is mentioned) offer a solution.
so i have ordered a new battery which will hopefully arrive tomorrow and i will see how we get on from there.
rockmonkey1973 said:
it is strange but using the mcgyver method i can get the bootloader ready to program i simply cant get rsd lite to see my phone and neither does windows. there are loads of posts and threads on this but not many (none actually when the situation i am is mentioned) offer a solution.
so i have ordered a new battery which will hopefully arrive tomorrow and i will see how we get on from there.
Click to expand...
Click to collapse
do u have blank flash mode enabled in rsd?
does defy show up in device manager?
try switching usb ports
Sent from my MB526 using xda premium
nogoodusername said:
d
try switching usb ports
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
doh!
amazing i simply used another cable and usb port and then i had to unplug it and plug it again and drivers started to be installed. (i had already installed motos drivers but hey windows wanted more!).
i also went back to the older 4.9 version of rsd lite. it has been a long long time since i have had to do this. installing nordic and will try and install one of my other back ups. all should be well very soon fingers crossed.
looks like the spare battery i bought will be going back then. oh well.
cheers mate your post prompted me to try again and just tinker and it worked so appreciate that.
edit: seems a bit stuck and i am now a little unsure what to do. the android bootscreen is stuck and rsd lite is saying maually power up this phone. i am a little concerned because it is still saying in process even though it has flashed the sbf. i have tried turning it off and nothing happens. it looks like i am actually going to have to unplug the cables remove the mgyver wires and take out the battery and boot it.
bollox. it is dead again so i have to start again. trying a different sbf this time. not sure what happened there. maybe i was too impatient?
honestly not sure what is happening here. i have tried a standard blurred sbf 2.2 and the phone is now stuck on the m animation and rsd lite iks omce again saying manually start this phone. what in the world do i do next?
ah god i will have to do some more reading because it is ****ed. i now have a white light and black screen. rsd lite just remained stuck at 100 per cent in process and manually boot your phone. have tried it three times and that is all i get. not sure if it is because i am flashing froyo sbfs when i have had a 2.3 kernal on the device? it is why i have avoided flashing them in the first place and the first time i ever do bang i get a bricked phone when i try to restore it back to cm7. the phone came with 2.1 so should i be flashing them?
very boring and very very annoying.
getting quite tired of this little game and am on the brink of buying another phone.
ok i have a red lense defy and after much reading i have realised that i must be flashing the wrong sbfs now call me stupid but i actually am very confused about which one i need to flash.
i started on 2.1 originally then i flashed 2.2 and then stuck cm7 on the phone with a froyo kernal. however when i upgraded to cm10 i tried the 2.3 kernal.
so with this background in mind will this work???
http://forum.xda-developers.com/showthread.php?t=1595013
can i follow this to flash the sbf and get root?
or is there another sbf i need to flash. all i need to be able to do is root the phone and install cwm and then i can flash one of my back ups (properly this time).
rockmonkey1973 said:
ok i have a red lense defy and after much reading i have realised that i must be flashing the wrong sbfs now call me stupid but i actually am very confused about which one i need to flash.
i started on 2.1 originally then i flashed 2.2 and then stuck cm7 on the phone with a froyo kernal. however when i upgraded to cm10 i tried the 2.3 kernal.
so with this background in mind will this work???
http://forum.xda-developers.com/showthread.php?t=1595013
can i follow this to flash the sbf and get root?
or is there another sbf i need to flash. all i need to be able to do is root the phone and install cwm and then i can flash one of my back ups (properly this time).
Click to expand...
Click to collapse
Thats for BL7.. Some Defy+ with 2.3.6 were BL7. You definitely don't need to flash it..
Just flash the last SBF that worked for you..
neo.ank said:
Thats for BL7.. Some Defy+ with 2.3.6 were BL7. You definitely don't need to flash it..
Just flash the last SBF that worked for you..
Click to expand...
Click to collapse
yes mate i did the last sbf i flashed over a year ago was nordic and i got the error as listed above. have no idea what i am doing wrong but i must be doing something. trouble is the new battery has arrived and i have already tried a new sbf and still getting the same problem... manually need to reboot the phone.
bit worrying because obviously i will only have a certain number of tries before this new battery dies on me.
edit: absolutely annoying. part of the problem with the guides on here are that they are mostly incomplete. they dont actually tell you everything you need to do. take for instance this the guide for unbricking
http://forum.xda-developers.com/showthread.php?t=1828639
it is totally useless because what he fails to mention is that
to boot into stock recovery you need to hold down the volume button when you power on the phone and you will get a droid with an exclamation mark and then you need to hold down both the volume up and down buttons which after a few seconds will take you to stock recovery. then you can wipe cache etc and the phone will boot. i found this out here (notice how people are telling the guy to simply flash a new sbf!)
http://forum.xda-developers.com/showthread.php?t=1608812
the mad thing is if i had found that simple post just above and knew about the up and down volume buttons i would have fixed the defy on the very first try. that is what is so annoying about this situation.
ok
red lense defy.
long story short i flashed one of the bl7 defy plus gingerbread sbfs.
so i have gone through the root procedure by installing the rooted sbf in rsd lite and then i can install 2nd init 2.0.3 and can get a custom recovery installed.
but every time i try to install cm7.2 euro skank it reverts back to the bootloader. here is what i have done twice in recovery with the exact same result.
wipe cache, data, dalvik and battery stats/ flash cm7 froyo kernal/ then flash the rom/ then flash gapps and then wipe again and then reboot.
when the phone starts again i am once again back to the bootloader and i have to start all over again.
so a very simple question from the position i am in what exactly do i need to do to get cm7 running on the phone.
double post but there are worse crimes!
ok so i have realised that i am stuck on the gingerbread kernal and that any froyo based rom is not gonna work.
wow how did i end up here! bloody hell that is what happens when you start getting ****ed off with the phone not doing what you think it should. anyways it is done now and i have cm7 all up and running and have even been able to make a back up so that if anything happens in the future when i am experimenting then i have a decent base from which to start. everything is working including the camera data wifi calls and well everything except...
i have one all rather serious problem that i really need to get sorted (this is it if i can fix this then i can leave the phone alone).
my battery is not recognized. now the phone runs on the battery which is a big step up from before where i was literally having to leave it plugged in just to keep it on. but the battery icon at the top is displaying a question markn and i dont know if it is charging or not. i also have no idea how much battery is left.
i have flashed both the defy red lense ics battery zip and the defy plus battery fix and i wiped cache dalvik and battery stats before i flashed them and the cache after but neither of these worked.
anyone actually care to help out here. what do i need to do to get my battery recognized? seriously if you know then please share because i have wasted a day and a half on this and through sheer frustration dug myself into a huge hole and it took ages to climb out.
all i am asking for is a bit of guidance from someone who actually knows what they are talking about. if that sounds like you do me a favour and simply tell me what i should do because i am now totally and utterly stumped.
cheers.
rockmonkey1973 said:
yes mate i did the last sbf i flashed over a year ago was nordic and i got the error as listed above. have no idea what i am doing wrong but i must be doing something. trouble is the new battery has arrived and i have already tried a new sbf and still getting the same problem... manually need to reboot the phone.
bit worrying because obviously i will only have a certain number of tries before this new battery dies on me.
edit: absolutely annoying. part of the problem with the guides on here are that they are mostly incomplete. they dont actually tell you everything you need to do. take for instance this the guide for unbricking
http://forum.xda-developers.com/showthread.php?t=1828639
it is totally useless because what he fails to mention is that
to boot into stock recovery you need to hold down the volume button when you power on the phone and you will get a droid with an exclamation mark and then you need to hold down both the volume up and down buttons which after a few seconds will take you to stock recovery. then you can wipe cache etc and the phone will boot. i found this out here (notice how people are telling the guy to simply flash a new sbf!)
http://forum.xda-developers.com/showthread.php?t=1608812
the mad thing is if i had found that simple post just above and knew about the up and down volume buttons i would have fixed the defy on the very first try. that is what is so annoying about this situation.
Click to expand...
Click to collapse
rockmonkey1973 said:
double post but there are worse crimes!
ok so i have realised that i am stuck on the gingerbread kernal and that any froyo based rom is not gonna work.
wow how did i end up here! bloody hell that is what happens when you start getting ****ed off with the phone not doing what you think it should. anyways it is done now and i have cm7 all up and running and have even been able to make a back up so that if anything happens in the future when i am experimenting then i have a decent base from which to start. everything is working including the camera data wifi calls and well everything except...
i have one all rather serious problem that i really need to get sorted (this is it if i can fix this then i can leave the phone alone).
my battery is not recognized. now the phone runs on the battery which is a big step up from before where i was literally having to leave it plugged in just to keep it on. but the battery icon at the top is displaying a question markn and i dont know if it is charging or not. i also have no idea how much battery is left.
i have flashed both the defy red lense ics battery zip and the defy plus battery fix and i wiped cache dalvik and battery stats before i flashed them and the cache after but neither of these worked.
anyone actually care to help out here. what do i need to do to get my battery recognized? seriously if you know then please share because i have wasted a day and a half on this and through sheer frustration dug myself into a huge hole and it took ages to climb out.
all i am asking for is a bit of guidance from someone who actually knows what they are talking about. if that sounds like you do me a favour and simply tell me what i should do because i am now totally and utterly stumped.
cheers.
Click to expand...
Click to collapse
First of all Stop whining about the guides being incomplete. They have helped a lot of people before you and are still helping.. If you mean every post should mention trivial stuff like booting into recovery and wiping data then just imagine the redundancy of the stuff.
If only you were patient enough to read before reacting. Defy Beginner's guide clearly mention 'bout booting into recovery & bootloader so its your folly for not collecting the info before processing..
anyone actually care to help out here. what do i need to do to get my battery recognized? seriously if you know then please share because i have wasted a day and a half on this and through sheer frustration dug myself into a huge hole and it took ages to climb out.
all i am asking for is a bit of guidance from someone who actually knows what they are talking about. if that sounds like you do me a favour and simply tell me what i should do because i am now totally and utterly stumped.
Click to expand...
Click to collapse
Don't know what you've wasted your day on, but all I can suggest is flash the battery fix for Defy+. Search for it. not difficult to find.
neo.ank said:
First of all Stop whining about the guides being incomplete. They have helped a lot of people before you and are still helping.. If you mean every post should mention trivial stuff like booting into recovery and wiping data then just imagine the redundancy of the stuff.
If only you were patient enough to read before reacting. Defy Beginner's guide clearly mention 'bout booting into recovery & bootloader so its your folly for not collecting the info before processing..
Click to expand...
Click to collapse
whining! i didnt think i was whining although i can get annoyed and sometimes my frustration is vented without thinking. i accept that the phone being where it is is indeed my fault. in fact if i had just left it alone then it would have been running as well as it ever did. i am also a great advocate of the developers who spend there time providing us roms and tools for us to use and i can say hand on heart i appreciate the fine work they do often for free. i am also an avid reader of the guides being a simple bod with very little knowledge of flashing hacking and what not and they have saved my bacon more times than i care to remember over the last four or five years. and so you are spot on the guides help a lot... not just me but many before me and most likely many after and give us mere mortals the chance to stay current with firmware long after the manufacturer has abandoned the phone. so while i may have been complaining rather angrily i was not whining.
the fact is that guide is incomplete. not only is it incomplete but it is the one that is linked to on the wiki as the guide to follow on how to unbrick your phone.
if you are like me a tinkerer who every once in a while likes to try out a new rom and who doesnt know the every inner workings of the procedures and who needs to follow instructions then i think the least you can expect is for the definitive guide to be correct! i mean that isnt too much to ask for is it.
so yes i do expect them to list every basic important step one must follow to fix the phone because that is what instructions do they guide people who dont know what they are doing. that is there sole purpose and if they dont do that job then they should either be edited so they do or deleted.
and yes yesterday i was very annoyed at the fact that the guide i was following does not actually tell you exactly what one should do and i can promise you if it had of done then i would not be in the position i am in it is as simple as that. i mean you cant seriously expect people to think oh right these are the instructions for unbricking the phone but i bet you they aint right so i had better read some more instructions for the same thing... and hey they might not be complete as well so i had better read yet another set just in case. leave it out will you.
at the end of the day it doesnt matter and at the risk of repeating myself i know that if i had left well alone the phone would be fine so ultimately i have no one else to blame but myself. if i had been a little more patient and less stressed wondering why the phone wouldnt boot after what appeared to be a successful flash then i would have got there in the end without being stuck on a gingerbread kernal.
neo.ank said:
Don't know what you've wasted your day on, but all I can suggest is flash the battery fix for Defy+. Search for it. not difficult to find.
Click to expand...
Click to collapse
well if you had read through this thread then you may have seen i have wasted a day and a half on quite a lot of reading as it goes. you may have also seen that i have flashed 2 battery fixes and that they havent helped. so i am wondering if you know what else i could do to fix the problem? if you do and you dont mind telling me then i would be grateful. if you dont then no big deal... i will read through a few more threads and see if i cant get to the bottom of it.
EDIT: I have reread what i wrote and i take that back the guide is far from useless in fact it is excellent and i mean that. in every other way it is spot on and is the de facto guide to sorting yourself out of a hole. but it does miss out some vital information that (i think at least) really should be there. still water under the bridge and all that. we are were we are and one must move on. bottom line it is only a phone and if it comes to it i will buy another. the only reason i havent actually bought another so far is the buld quality and form factor of the defy is still yet to be bettered. but maybe it is a sign a message from above telling me to move on to pastures new.... although i would still like to fix the battery issue.
ok it is fixed. as i was writing this reply i installed the white rabbit rom (which i read included red lense battery fixes). true to its word there are five downloadable files. i got four (one woudnt download) and rebooted the system and hey presto.
well what a difference a day and a decent nights kip make. and colour me impressed. this rom is a work of genius. i see it is based on euro kangs cm7 effort with a few nice (well actually loads) extras thrown in for good measure. have to say i am really liking it. calls data wifi camera and battery all work and it looks and feels swift and very polished.
so all is well that ends well. and what a journey. man all i wanted to do was restore cm7 from my back ups. flashing the gingerbread based cm10 before i did it i reckon screwed me and i didnt realise what i had done until after when it wouldnt boot. however xda saved the day as it always does (even if it did take me quite a lot time to get there this time round). i may even write a mini guide but then either no one would bother reading it or i would get loads of people whining at me telling me how it aint right so i think i will avoid that little task and leave it to people more brave and knowledgeable than i.
cheers all for the help in this thread, the time taken by others to write stuff down and the people who provide us with some great software for our ageing but still great phone.
me to
pls help
jalal-jap said:
me to
pls help
Click to expand...
Click to collapse
if you need help mate then a little bit more info is gonna be required.
i will say this that i havent quite fixed it completely. i have the rom running sweet as a pie and the phone will work away from a power source but the battery percent/ icon remains locked at 100 per cent so i have no way of knowing if the phone is charging. when i plug it in to my laptop it says usb connected but again it doesnt list it as charging. so i have no way of knowing if the battery is actually getting charged or how much is really left.
i am also far from an expert more a bumbling old timer who rarely posts here unless desperate.
bear all that in mind and i will do all i can to help (provided you specifically say what you want help with)
edit: lmao... i couldnt have picked a worse sbf to flash. amazing. i have been so so careful in all the time i have owned this phone (over a year i reckon now) and i may have finally actually broken it.
i aint even certain i can charge the battery and once it runs down it will simply die. obviously there is hope that someone will come up with a downgrade method at some point in the future but for the time being i think the phone is ****ed.
i will try ics tomorrow and see if i can get any joy there but i think the only way i can now use the phone is to buy an external battery charger. funny really i used to own both a spare battery and a charger for this very reason and yet i sold them when i got rid of the old defy. so i am gonna have to buy one off ebay tomorrow and use it that way. at least then i will be able to use the phone.
rockmonkey1973 said:
if you need help mate then a little bit more info is gonna be required.
i will say this that i havent quite fixed it completely. i have the rom running sweet as a pie and the phone will work away from a power source but the battery percent/ icon remains locked at 100 per cent so i have no way of knowing if the phone is charging. when i plug it in to my laptop it says usb connected but again it doesnt list it as charging. so i have no way of knowing if the battery is actually getting charged or how much is really left.
i am also far from an expert more a bumbling old timer who rarely posts here unless desperate.
bear all that in mind and i will do all i can to help (provided you specifically say what you want help with)
edit: lmao... i couldnt have picked a worse sbf to flash. amazing. i have been so so careful in all the time i have owned this phone (over a year i reckon now) and i may have finally actually broken it.
i aint even certain i can charge the battery and once it runs down it will simply die. obviously there is hope that someone will come up with a downgrade method at some point in the future but for the time being i think the phone is ****ed.
i will try ics tomorrow and see if i can get any joy there but i think the only way i can now use the phone is to buy an external battery charger. funny really i used to own both a spare battery and a charger for this very reason and yet i sold them when i got rid of the old defy. so i am gonna have to buy one off ebay tomorrow and use it that way. at least then i will be able to use the phone.
Click to expand...
Click to collapse
You're on BL7 now and there's a reason people advise to avoid it. Most of the fixes and scripts doesn't work with BL7 including the battery fixes.
I'd suggest you to go for Quarx's build for GB kernel (along with the battery fix), Randomly flashing ROMs and fixes won't help.
Moreover, I strongly recommend you to search and read carefully. You're not the first one to face the problem, and there's a solution. Even if you waste(?) a couple of days reading 'bout it, it won't kill your phone, but if you do something out of desperation it might.
neo.ank said:
Moreover, I strongly recommend you to search and read carefully. You're not the first one to face the problem, and there's a solution. Even if you waste(?) a couple of days reading 'bout it, it won't kill your phone, but if you do something out of desperation it might.
Click to expand...
Click to collapse
i take it you mean this like in retrospect? of course you are right a deep breath and a walk does wonders for a fuddled head and is far better than simply rushing into the next desperate attempt to repair. however it is easy to say this after the event yes!
the battery wont charge and if i flash another rom it gives me the big battery icon with question mark so i am once again stuck in a corner with no where to go. basically it is ****ed because none of the battery fixes work. the battery works when there is power in it but it just wont charge when in the phone. because the battery ran down last night the only way i can use my phone at the moment is tethered to the mcgyver trick.
so the plan is to buy a separate charger and use that to charge the battery. then i reckon i should be at least able use the phone (although this yet to be tested).
amazing seriously amazing. a year of owning this phone a year of flashing and hacking and being ultra conservative and then all it takes is a few minutes of madness and it is royally screwed. the crying shame about it is that i have installed the best rom i have ever seen in the white rabbit and if the external charger doesnt work i wont get to play with it! still live and learn.
edit: by the way do you know if the mcgyver trick actually charges the battery?
.
rockmonkey1973 said:
i take it you mean this like in retrospect? of course you are right a deep breath and a walk does wonders for a fuddled head and is far better than simply rushing into the next desperate attempt to repair. however it is easy to say this after the event yes!
the battery wont charge and if i flash another rom it gives me the big battery icon with question mark so i am once again stuck in a corner with no where to go. basically it is ****ed because none of the battery fixes work. the battery works when there is power in it but it just wont charge when in the phone. because the battery ran down last night the only way i can use my phone at the moment is tethered to the mcgyver trick.
so the plan is to buy a separate charger and use that to charge the battery. then i reckon i should be at least able use the phone (although this yet to be tested).
amazing seriously amazing. a year of owning this phone a year of flashing and hacking and being ultra conservative and then all it takes is a few minutes of madness and it is royally screwed. the crying shame about it is that i have installed the best rom i have ever seen in the white rabbit and if the external charger doesnt work i wont get to play with it! still live and learn.
edit: by the way do you know if the mcgyver trick actually charges the battery?
.
Click to expand...
Click to collapse
The battery fixes replace your battd.bin binary file which stores the info about the battery. Surprisingly there isn't a single binary that work with each phone, it acts weirdly and not sure what fix will work for a particular phone.. I again suggest you, every battery fix you find. You're not the first one to face the problem and its been sorted for many..
Mcgyver just supply the device with intended charge as the battery does. It doesn't charge the battery.
Don't know if you tried this one.
Defy Red Lens Battery Fix
neo.ank said:
The battery fixes replace your battd.bin binary file which stores the info about the battery. Surprisingly there isn't a single binary that work with each phone, it acts weirdly and not sure what fix will work for a particular phone.. I again suggest you, every battery fix you find. You're not the first one to face the problem and its been sorted for many..
Mcgyver just supply the device with intended charge as the battery does. It doesn't charge the battery.
Don't know if you tried this one.
Defy Red Lens Battery Fix
Click to expand...
Click to collapse
i have tried it mate. i have also tired the ics defy red lense and the white rabbit rom had four of them available to download. none of them have worked. basically as it is now the phone will not stay on without the mcgyver leads and the battery wont charge. i have flashed 6 different battery fixes.
edit: it is strange once i have given it a blast on mcgyver for an hour or so i can then use the phone normally. however the battery is locked at 100 per cent and there is no indication it is charging when a usb lead is plugged in. seriously i have tried 6 of the fixes and none have actually worked.
if you are saying there is a fix for this then i would love to know what it is because i havent found one yet.
edit again!!!: ok this is strange because now when i plug it in to a usb lead the green light appears as if it was charging. very very strange this. i mean like really ****ing weird.
final edit: ok i am officially giving up. it has beaten me and for the first time ever i have got myself into a situation that i cant get out of. who would have thought a simple battery would be the cause of so much ****ing grief. anyway. for total clarity.
i am now running white rabbit rom runs great highly recommended and way quicker than the cm10 efforts that are being worked on at the moment. i have tried 6 battery fixes. none work. i am sometimes able to use the phone without being connected to the mcgyver leads but the battery remains locked at 100 per cent. other times the phone dies and the only way to boot it again is the mcgyver leads. if i do that then battery may change to say 25 per cent or even 75 per cent. basically it is all over the shot. i have tried to install another rom and this leads to the exact same thing. if i turn it on without the mcgyver leads i get the battery error. sometimes when connected to the usb port the phone has the led green light like it is charging then other times it doesnt. it is basically well and truly ****ed up.
so i am giving up. i have wasted quite enough time on a phone i have been thinking of changing as it is. i am gonna buy a sensation as a short term replacement. not as nice as the defy form wise but far faster and with a decent modding community so it will do for now. i will return here every now and then to see if someone comes up with a way to downgrade the bl7 but until that happens the phone is gonna gather dust in my drawer.
i think this thread serves as decent guide as to what shouldnt be done if you want to unbrick your phone (and also includes a few little things that may be missing elsewhere) so hopefully someone can learn from it. cheers all and see you later.
ok well this is the end of this thread (unless i find a proper working solution).
i was unable to charge the phone unless i used the mcyver trick. basically the only way it would accept a charge was if the mcgyver leads were connected. however the battery would charge once the mcgyver leads were in place but stays locked at 100 per cent no matter what i do. it may be the rom i am using but every time i tried another i got the battery error.
i have now bought an external battery charger and spare battery. it works a treat. i simply use the charger to charge one battery and use the other battery to power the phone. when the battery dies i simply switch them around and use the phone as normal.
this way i am no longer having to boot the phone using mcgyver and the only thing i am missing is the ability to charge the battery internally or tell how much battery life is actually left.
so all told all is well that sort of ends well. at least i can carry on using the defy. i was looking at buying another phone but they are all either too big or too slippy/ fragile in the hand. the only one i would like to buy is the orange san diego but there is no root and even worse there is no sim unlock. so for the time being i will stick with the nearly indestructible defy and hope that moto see sense and release a four inch, 8mp onboard camera and better screen carbon copy. fingers crossed.

Galaxy Nexus death scheduled ?

Hi,
I've got my GN for about 2 years now. It always runned fine. I use it essentially to make calls, mails, some european "anti-cop" app called "icoyote", spotify and that's it
Everything stock, full google official, no cracked bull**** apps or whatever.
Ok so now for about 1 month it became less and less stable. It literally happened from one day to another. I guarantee i didn't add/change or remove anything.
Main issues are : spotify crashes many times (~20 to 50) a day and 50% of the time the GPS fix fails to go trough, but a simple reboot and it work's instantly.
So I tought I should make a full factory reset. I did that and the issues I was experiencing remained the same.
Now comes the 1million $ question : how the heck can something stop to work from one day to another ? If it was some *unpredicted*, classic hardware failure, a simple reboot would definitely not solve it, for sure.
Leading to think it has to be software related..OK, so a factory reset should solve : it doesn't neither.
Why are those apps crashing even in a very stock/factory config? I even did skip this google restore profile bull**** to be sure i'm workng in a perfect clean state.
The only logic conclusion is that there must be some kind of hard coded counter which reached the end and is now triggering randomly something, *i don't know based on what, or activated how* making this **** happen
It's very very very frustrating because it was working like a charm those past 2 years and i thought it was a good investment. I was obviously wrong, another death scheduled device.
Now with the 4.3, I got the feeling it becomes even worse. Today, I had to reboot 4 times to get a gps fix (working 100% of the time just after the reboot) and it was a hassle to get trough 2 songs without being cut off in the middle of it.
FU samsung
But you only tried to flash 4.3. It's like giving a patient only 1 medicine and when that not works declare him dead. There maybe other ways to revive your phone..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
But you only tried to flash 4.3
Click to expand...
Click to collapse
when did i say that ? i'm done by years flashing a tool I use to work with. i'm not using it as a toy.
i received the update ota
there's nothing left to try, since my last basic test's where made in a official google factory default situation on a google phone
it's just stock u see? everything else i could try from this point would lead to a non-default situation making every further considerations totally pointless
Well, if i'm right, the so called "crash-routine" would *maybe* not be present in a custom rom, but, again, it worked before and has to work the same way now.
I refuse to use any other workarounds than factory resetting it and, since i already did that a few times, i'm done
i'm not awaiting some kind of help here. i'm just exposing my case and the frustration i'm feeling since samsung nicely dry-fcked me ^^
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Read this. It's called Planned Obsolescence. Manufactures purposely make devices with limited lifespan in order to upgrade to their next new device.
http://en.m.wikipedia.org/wiki/Planned_obsolescence
Sent from my Galaxy Nexus using Tapatalk 2
Fastboot, Odin, omap.. All stock..
Sent from my Galaxy Nexus using XDA Premium HD app
johno86 said:
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Click to expand...
Click to collapse
I ain't here to help either, i just couldn't agree more with what he said above... and its 2013, everyone knows that every electronic sh*t comes with a limited life span, if you didnt know that until now, i'm not sure where you been living..
Peace \m/.
Try wiping your SD card

HTC 10 Speaker Crackle/Distortion...

Hi guy,
Not sure if anyone else has had this (can't find anything here, or with search engine, so starting to worry it's not software problem), but just the other night, was surfing then all of a sudden, I get this loud horn type noise from my phone... Certainly woke me up! Then stopped... Then no sooner did it stop, again it happened. I check, but my volume is almost at mute. So I close Chrome, and re-open, and haven't heard it since, but now I have noticed my speakers crackle and distort on certain frequencies.
I'm hoping this is just some software issue, that hopefully I can just update, or re-set, but I haven't come across anyone else having this problem.
Please help
Thankyou, O.
Ob1eron said:
Hi guy,
Not sure if anyone else has had this (can't find anything here, or with search engine, so starting to worry it's not software problem), but just the other night, was surfing then all of a sudden, I get this loud horn type noise from my phone... Certainly woke me up! Then stopped... Then no sooner did it stop, again it happened. I check, but my volume is almost at mute. So I close Chrome, and re-open, and haven't heard it since, but now I have noticed my speakers crackle and distort on certain frequencies.
I'm hoping this is just some software issue, that hopefully I can just update, or re-set, but I haven't come across anyone else having this problem.
Please help
Thankyou, O.
Click to expand...
Click to collapse
Do you have any mods (audio) installed ?
Are you rooted? Running a custom ROM ?
We need a little more information..
If you're completely stock then no it's not normal and I'd put my money on a hardware defect..
If you are rooted with a custom ROM and perhaps some mods installed it still doesn't sound normal and I'd try to go back to a custom but stock type ROM.
Least then you can see; if it replicates, then it's more than likely a hardware issue.
Did u push the speakers a little too much with a mod? Over amplify them or similar? Any water damage? Drops?
From the outset it doesn't look good but until you / we can answer the above we won't know more.
Hopefully it's just a mod gone wrong.
If not then it'll be a defect covered by warranty anyway..So a return to stock and RMA will get it sorted, so a hindrance but not then end of the world.
Let us know.
Sent from my HTC 10 using XDA-Developers Legacy app
dladz said:
Do you have any mods (audio) installed ?
Are you rooted? Running a custom ROM ?
We need a little more information..
If you're completely stock then no it's not normal and I'd put my money on a hardware defect..
If you are rooted with a custom ROM and perhaps some mods installed it still doesn't sound normal and I'd try to go back to a custom but stock type ROM.
Least then you can see; if it replicates, then it's more than likely a hardware issue.
Did u push the speakers a little too much with a mod? Over amplify them or similar? Any water damage? Drops?
From the outset it doesn't look good but until you / we can answer the above we won't know more.
Hopefully it's just a mod gone wrong.
If not then it'll be a defect covered by warranty anyway..So a return to stock and RMA will get it sorted, so a hindrance but not then end of the world.
Let us know.
Click to expand...
Click to collapse
Hi Dladz,
Sorry I didn't put more info in before.
I'm totally stock (running 7.0). Not running away mods, or audio changes.
I suspect that it is just that, a hardware issue, I was just hoping not. I've never had an issue with any of my HTCs' before, nor have any of my friends. The build quality has always been the best you can get.
I guess it's back to the supplier it goes :/
Thanks for the response,
O.
Ob1eron said:
Hi Dladz,
Sorry I didn't put more info in before.
I'm totally stock (running 7.0). Not running away mods, or audio changes.
I suspect that it is just that, a hardware issue, I was just hoping not. I've never had an issue with any of my HTCs' before, nor have any of my friends. The build quality has always been the best you can get.
I guess it's back to the supplier it goes :/
Thanks for the response,
O.
Click to expand...
Click to collapse
Ah that is a shame and no worries, I've skipped info before as i'm sure others have and will
I wouldn't let it put you off HTC they do make some rugged devices and I swear by them, speak to a rep and see what RMA would take then get it done mate
All will be well, this wasn't your fault, I'm just thinking what could've caused it if anything?
Playing at loud volume constantly, music or audio with frequencies which put stress on the speaker??? Nah I dunno mate, either way it's not your fault so get yourself a nice replacement
Good luck fella. :good:
dladz said:
Ah that is a shame and no worries, I've skipped info before as i'm sure others have and will
I wouldn't let it put you off HTC they do make some rugged devices and I swear by them, speak to a rep and see what RMA would take then get it done mate
All will be well, this wasn't your fault, I'm just thinking what could've caused it if anything?
Playing at loud volume constantly, music or audio with frequencies which put stress on the speaker??? Nah I dunno mate, either way it's not your fault so get yourself a nice replacement
Good luck fella. :good:
Click to expand...
Click to collapse
Thanks Dladz,
I've loved HTC from the start, and still do. I recommend them to everyone I know and meet. This is just one fault in the entire history of mine and everyone I know who has or had one! I think that is a pretty good fault rate.
I'm already hankering for the HTC Ocean ? Can't wait ?
Cheers,
O
I had this problem too on my HTC 10 one month and a half ago . I was on leedroid with nebula kernel and no other sound mod and all of the sudden the bottom speaker started to crackle and make many distortioned sounds . I suspected to be the kernel so I asked the developer , but he said that he hasn't touched anything sound related . No one , but only me, had this problem reported on kernel thread . I asked on ROM thread but the same.
Now I see that someone on purely stock had this problem. Only thing I can say is that where I live 2 months ago was a really cold winter and that affected the speaker.
I had send it back to repair services and now it's all good
Ob1eron said:
Thanks Dladz,
I've loved HTC from the start, and still do. I recommend them to everyone I know and meet. This is just one fault in the entire history of mine and everyone I know who has or had one! I think that is a pretty good fault rate.
I'm already hankering for the HTC Ocean Can't wait
Cheers,
O
Click to expand...
Click to collapse
HTC 11 will be interesting, wondering what they're going to do with the screen now that everyone is looking to go bezelless.
dladz said:
HTC 11 will be interesting, wondering what they're going to do with the screen now that everyone is looking to go bezelless.
Click to expand...
Click to collapse
I just hope they don't put the home button on the back!
It is this same issue that´s making me want to upgrade from my otherwise still great HTC One M8. A distorting top speaker that the repair shop couldn't fix (they tried 3 new speakers, to no avail). It´s very annoying and I am waiting to see if the HTC 11 ticks everything I want in a smartphone:
- Full Metal Chassis
- Stereo Front Speakers
- 64GB of UFS 2.1 Storage
- 4GG of RAM
- Support to Micro SD cards
- Snapdragon 835
- Great low light camera with IOS (like the Pixel)
- Preferably with water resistance
Otherwise, I am buying the HTC 10, which is much cheaper now since it´s been almost a year since it was launched.
I dont understand why we dont even have a Evan Blass rumor about the supposed upcoming HTC 11, that is making me a bit worried...
Cheers
I have the same problem.
Now if anyone know what is the certain solution for this problem?
stefan1234566789 said:
I had this problem too on my HTC 10 one month and a half ago . I was on leedroid with nebula kernel and no other sound mod and all of the sudden the bottom speaker started to crackle and make many distortioned sounds . I suspected to be the kernel so I asked the developer , but he said that he hasn't touched anything sound related . No one , but only me, had this problem reported on kernel thread . I asked on ROM thread but the same.
Now I see that someone on purely stock had this problem. Only thing I can say is that where I live 2 months ago was a really cold winter and that affected the speaker.
I had send it back to repair services and now it's all good
Click to expand...
Click to collapse
I am running HTC 10 Android 9.0 - lineageos 16.0 w/ latest oreo firmware and im still having problems. I have tried several other firmwares/ROMs and I feel that it is a software defect but im going to replace the speaker anyway... I'll let you know..

Categories

Resources