No Vibration|Need Help| Whyred - General Questions and Answers

I'll try to keep this short yet detailed.
So I basically flashed Custom ROM on my whyred 2-3 years back.
RR Rom and I have no Vibration since then. (I might have wiped incorrect partition Idk, some people said something about the device tree I've no idea.)
Lemme answer few questions that will pop up in your minds.
Yes I checked every setting, everything's ON.
QC Test failed for vibration.
I got my vibration motor changed as well.
I flashed fastboot ROM as well.
Flashed custom kernels as well.
Multiple ROMs - Pixel, Lineage, RR, Evolution X.
Nothing worked for me.
It's been more than couple of years now. Same happened with Kenzo it still work but without vibration.
PS - I've other devices that work fine on custom ROMs, probably because I've been more careful.
PPS- Vibration comes back sometimes but that's literally like once a year.

Sounds to me, like there is not enough power to trigger the actual motor, based on the fact you've tried so many roms and had same problem for so long.
This can be caused by custom roms, or maybe the motor is just old n cranky, (ok, you changed it) and needing a wee shove to trigger it into moving again, after being still for so long.
Think ps3 controller, if you can open your fone, and put the tiniest bit of wd40 on the motor spindle, then lightly turn it by 'finger' lol, that should do the trick if it's not software related, and it works when it CAN rather than when it wants or is told to.
Just a suggestion. If you do go to look and do the wd40, test the power on the red and black cable while instructing fone to vibrate, if all is good, it's the roms.
Edit: Oh, and it's a good idea to look into notification settings, see what permissions are granted to vibrate/sound/on off? Some apps like to change settings we make being not so obvious. Sometimes denying other apps can affect such stupid things.
Yup I got it, but I'm an electronics guy... If you can confirm if there is power TO the motor (set ringer to vibrate then call yourself, while testing power)... yup....if you cant get power to motor, backtrace the power till you find it.
Its software after that.

.

Pachacouti said:
Sounds to me, like there is not enough power to trigger the actual motor, based on the fact you've tried so many roms and had same problem for so long.
This can be caused by custom roms, or maybe the motor is just old n cranky, (ok, you changed it) and needing a wee shove to trigger it into moving again, after being still for so long.
Think ps3 controller, if you can open your fone, and put the tiniest bit of wd40 on the motor spindle, then lightly turn it by 'finger' lol, that should do the trick if it's not software related, and it works when it CAN rather than when it wants or is told to.
Just a suggestion. If you do go to look and do the wd40, test the power on the red and black cable while instructing fone to vibrate, if all is good, it's the roms.
Edit: Oh, and it's a good idea to look into notification settings, see what permissions are granted to vibrate/sound/on off? Some apps like to change settings we make being not so obvious. Sometimes denying other apps can affect such stupid things.
Yup I got it, but I'm an electronics guy... If you can confirm if there is power TO the motor (set ringer to vibrate then call yourself, while testing power)... yup....if you cant get power to motor, backtrace the power till you find it.
Its software after that.
Click to expand...
Click to collapse
Hey, thanks for the reply.
I'm also an electronics guy, and I'll definitely get the motor power checked.
Yesterday only it randomly started working but it was so weak I knew it wasn't getting enough power. But not sure how.
About the setting vibration is on everywhere and There's no app which may cause any sort of problems. I'm pretty sure it's either the kernels or something else entirely.
Thanks again.

Could be time to get a new battery, or look at one of my teenage hacks:
Redmi Note 9S weird Battery Issue
Hello, My phone problem is, whenever i charged my phone to any certain percentage like 80%, 90%, 100%, and unplugged the charger and using the phone, first 5-10 minutes its consume 5-6% battery and first 1 hour of using its consume 10-12%. This...
forum.xda-developers.com

Related

Vibrate does not work

Since the day I purchased my Fuze, the vibrate has been hit and miss. I have checked Sounds and Notifications and such, but it still almost never vibrates when it should. Sometimes it will work when I press the Volume buttons to change to vibrate, but it usually does not. Touch Response does not vibrate either, and a Hard Reset did not fix the problem.
It worked better with the stock rom then it did with either RRE or Energy. Any help?
maybe the little motor inside the phone is broken. try different roms and see what happens. could be a hardware issue though...
In my old 6700 that issue was caused by a slightly dicey connection between battery and phone. Try moving or 'jiggling" the batt - that fixed it for me every time. Also, occurred more often when using 3rd party batts as the size probably wasnt as precise as the OEM.
Thought about the motor, was hoping it wasn't that.
Battery doesn't really move much. I was going to test it with a voltmeter, but one of the points on mine is broken so I can't get it to reach the contacts for the battery.
I think I might see if I can exchange it where I bought it.

[Q] Another G2x noob, is my phone going to be a lemon?

I'm kinda hesitant to post this, because I know you guys go through great lengths to emphasize searching first. I watched the video when I registered, nice touch. More forums could use vids like that!
oh well, here we go:
I have owned an Iphone every since they where introduced to the market. I have been wanting to make a switch for a while now. I was very close to purchasing a G2x back in April when they came out, but I held off. Well recently, a coworker let me check out his HTC G2 and I was amazed at the functionality, features, and other misc items compared to my old Iphone 3GS. I was never a fan of the slide out keyboard, so I knew the G2 was not for me.
Last week, I just missed the free promo on T-MO's web site, so Instead I purchased a G2X locally. I was totally unaware of all the problems you guys where having, as the typical review sites never mention these issues.
I have owned the phone for 8 days, So far here is whats been a going on:
7-29-11 Purchased the phone from Best Buy, decided to buy from them since they where the cheapest out the door with out rebate. I hate rebates! lol
Right before I am going to bed, I plug in to charge, and the phone shuts off, I cannot get it to power back up. I did not know about pulling the battery, I thought it had just died. I was going to wake up the next morning and take it back.
7-30-11 When I woke up, I looked around online, and found out about removing the battery and putting it back in. Now phone is working again.
I was able to get the OTA update to 2.3.3, right after the update, I did a master reset.
8-2-11 I downloaded a "radio scanner" app, and the first time I executed it, the phone froze, requiring another battery pull. Afterwards, the app ran fine.
Those are the only 2 major issues I have had.
Here are a few other things I noticed:
Screen: No separation, very slight light blur around top corners with lit black screen. Does not bother me, and I can't really notice it 99% of the time.
GPS: I know some have been having issues with this, for me, The time to get an accurate fix can sometimes take anywhere from 5-30 seconds. Even with the stock toggle always turned on, I do not always have the GPS Icon in the top bar, I don't know if I am supposed to. Can someone please confirm this?
WI FI: Seems to be working like intended, no complaints there.
BT: I have nothing to pair with the phone, so I will probably never know.
Making calls: this is kinda annoying, I will look through my call log and select a person, I see the dialer initiating so I put the phone to my ear, but a few seconds go by and nothing.... I look at the phone and find myself looking at the call log again, like the dialer crashed? Also, during the conversation the screen will turn off. I think this is normal, but when the phone detects motion shouldn't the screen turn back on?
Other than that, I love this phone so far. However, I do not want to swap handset after handset, refurb after refurb with T-MO or LG.
Is it possible that the phone will NOT continue to get worse as time goes on? Or should I take the first shut down as a sign of whats to come in the future? I have a 6 days left to take this thing back, but I am having a major conflict with myself about keeping it. What makes it even harder, Is I have already ordered a 32g micro SD, Trident case, and 3 extra data cables.
My plans are to root it, and run some sort of rom with it once I read up and half ass know what I am doing.
---------------------------------------------------------------------------------------
TLDR:
Have owned phone for a week. Shut down instantly the first time I charged it requiring a battery pull. Froze/crashed due to an app maybe Second battery pull.
Question a few functions but otherwise works like a champ.
Purchased case, micro sd, extra data cables.
thinking of taking it back and cancelling contract to avoid future headaches, but not sure if I should or want to at this point. need avdice please!
Doesn't sound like a lemon. The stock software is buggy. If you're gonna root it and flash another rom then you're gonna love this phone.
The GPS indicator is normal. It only shows when an app is using GPS for your location. Otherwise it doesn't show.
G2X CM7
It doesn't sound like a lemon to me either. I bought mine in April and my phone had a few reboots while charging overnight and two freezes in the first month. It has been OK since then, although I did not do anything about it (and I'm still on Froyo). The only thing I do is that I reboot my phone manually once in 7-10 days because the phone starts to lag. I believe this is normal for all smartphones including iPhone...or am I wrong?
Oh, forgot to mention when I hit the power button to wake the phone and go to the lock screen, I briefly see the last screen I was in before the phone went into sleep mode. Total lack of QA in my opinion... Will a rom fix this?
And yes Man of La Mancha, the iphone would get somewhat glitchy, but a reboot always took care of it. I didn't really have to reboot it too often, maybe once every 2 weeks or so.
HTXg2x said:
Oh, forgot to mention when I hit the power button to wake the phone and go to the lock screen, I briefly see the last screen I was in before the phone went into sleep mode. Total lack of QA in my opinion... Will a rom fix this?
And yes Man of La Mancha, the iphone would get somewhat glitchy, but a reboot always took care of it. I didn't really have to reboot it too often, maybe once every 2 weeks or so.
Click to expand...
Click to collapse
The lockscreen issue is a known bug. CM7, or any ROM with 2.3.4+ doesn't have that problem.

[Q] Vibration problem

Hello all, I have a problem with vibrations on my I9105P. More specifically: my phone fell down from a table right on the floor (maybe 0.5 meter) and since then vibration doesn't work. Everything else works fine, tried reflashing the system and all - nothing works (first I thought it was kernel's fault). What can I do now? Will the warranty cover the repair?
PS. I use case for my phone - it's made of a silicone or something like this (don't know exactly).
If ur phone falls down, how u can say that is kernel problem?
rs tony said:
If ur phone falls down, how u can say that is kernel problem?
Click to expand...
Click to collapse
Well, maybe I said it wrong. I didn't notice that the vibration isn't working for about 5 hours after the fall and so when I reflashed the kernel I thought about the fall - my phone used to fall from time to time and it never broke, so now I'm quite confused. However today, when I was writing on the phone's keyboard, it vibrated once while pressing the letter. Since then - silence.
If you stay it vibrated once that means it's somehow not completely broken. I would disable every sort of vibration in the phone's settings. The vibration motor is probably stuck and it is probably getting damaged more if it keeps trying to spin like that. What did you think - if the phone survived one fall it will survive 10 more just as well? Try the warranty, there's a good chance they'll cover it. Or learn to live without vibration.
cLick1338 said:
If you stay it vibrated once that means it's somehow not completely broken. I would disable every sort of vibration in the phone's settings. The vibration motor is probably stuck and it is probably getting damaged more if it keeps trying to spin like that. What did you think - if the phone survived one fall it will survive 10 more just as well? Try the warranty, there's a good chance they'll cover it. Or learn to live without vibration.
Click to expand...
Click to collapse
I didn't think like that. I guess it's like every time it fell down I felt a relief, because nothing was broken (I wasn't throwing my phone around my house, as I said, it OCCASIONALLY fell). Anyway, thanks for help - I'll try the warranty, just wasn't sure if they will accept it at the service.

SOD (sleep of death)

I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
60puc said:
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
Click to expand...
Click to collapse
This has happened to me before.What I simply did was replace the display.
Mr.Ak said:
This has happened to me before.What I simply did was replace the display.
Click to expand...
Click to collapse
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
60puc said:
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
Click to expand...
Click to collapse
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Mr.Ak said:
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Click to expand...
Click to collapse
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
60puc said:
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
Click to expand...
Click to collapse
As I already said,the same issue happened to me after I changed my display.I asked for replacement and replaced that damaged display,boom! I don't know what's so hard in it for you to understand.
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
60puc said:
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
Click to expand...
Click to collapse
Aliexpress?
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
60puc said:
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
Click to expand...
Click to collapse
Get ready with a lot of proofs tho'!
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Gab_echelon said:
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Click to expand...
Click to collapse
See previous page,I've already explained what is the cause of the issue.
I just finished replacing my screen, been waiting for my broken antenna cable and volume button flex to arrive. Everything works except the damn SOD i never had with my old screen. Tried turning off the proximity sensor check and still a no go. The screen turns on fine initially and trying to wake it instantly works all the time, but if I leave it off for any longer than 5 sec probably it won't respond to anything - power button, volume button, double tap and plugging in the usb cable connected to a power source.
Does this sound more like a governor issue? The rom installed is lineageOS (just updated to 10-30 release). Looking up my purchase log to open a dispute...
tested it again, repeated lock/unlocks puts it into the SOD state, doesn't even take 2 sec to do it...
oh wow, it does this even in the twrp recovery. I have wiped cache and dalvik cache just for the hell of it but doubt that was the real cause...
Gab_echelon said:
works everything but not touch
Click to expand...
Click to collapse
we've got a reverse situation. touch, buttons, sounds, modem works, but not screen (if you lock/unlock it 10-20 times it can raise again without reboot.
Buratei said:
it does this even in the twrp recovery.
Click to expand...
Click to collapse
i've got the first SOD in twrp mode. it doesn't matter, but at first - no troubles were with that. and now it works so so at home. and if i use it outdoor it becomes very often, but at home it seems that it works ok, just only seems, because if i want - i can do some manipulations (use camera, lock/unlock it etc) and the SOD appears again. but custom os executes SOD more frequently. i think it can be real overvoltage, like people says.
there are many posts here and everyone advices not effective solutions (flash stock, modem, fw ...) at first it helped me, but now i know there is no way, i can just try but ...
long time ago i owned an old tablet iconbit matrix - it has just the similar issue. it boots, but if you go to a sleep mode - it didn't wake up every time. it lights works ok inside, but no image. i had two displays and if i used one in a custom rom it worked ok, but not another one. stock rom works ok with every display. the solution was a display driver, like at windows OS.
cause of developers bugs, it was a little different (not stock-based) and some revisions of display works ok, others aren't.
so, i think it can be fixed, but the solution for me - change a display like the first reply says. Ali seller read this topic and posted me this in a few days after i started this topic:
Your dispute has been processed and the money will back to you in 7~10 working days.
so could you give us a positive feedback, please?
Best regards.
so, i'll order another one, no trouble, i hope this will help me to enjoy my oneplus.
60puc said:
so could you give us a positive feedback, please?
Best regards.
Click to expand...
Click to collapse
They always ask for positive feedback in exchange for refund/replacement.Bastards,aren't they? @evronetwork
For the sake of other people that'll read your feedback and make their decisions upon it,don't do it! Just complain this bribery to aliexpress staff ffs!
well I wish I bought from aliepxress... I bought mine from ebay to pinch some pennies, and because I was waiting on other replacement parts (which were only needed due to damage occurred during a screen replacement op) to ge here I am way over the protection period. aw shiiiiit, I guess you live and learn
gotta tell you though, the screen is a bit wacky in other ways too. the capacitive buttons do light up but not completely (kinda dark in the corners) and the colors look a bit off. hopefully the seller would honor the refund/return request...
EDIT: whoa... kinda hard to believe, but I messed around with battery profile just for the hell of it and by some pure luck discovered that the "performance" profile (second one from the far right) works just fine and wakes the screen every time. The "balanced" profile and everything below that gives me an insta-death. go figure!
EDIT2: guess I spoke too soon. it sure as hell looked like fixed, but it came back after a while. maybe it is just more sporadic than I thought...
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
60puc said:
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
Click to expand...
Click to collapse
What happened to getting a new display?
I use this one, because it works ok, but only at home. As a home tablet. At the street it fails every time.
I can reboot it if it doesn't wake up. But it wakes up often, so i don't want to order new one now. I want to check my mainboard to be sure, that it is dispaly problem
a bit late, but thought I should update on the situation... all working fine after a (yet another) LCD replacement. Much better color balance to boot, points to QC problems at the supplier's end. If I ever have to do this again, I am definitely going to inspect the new LCD as soon as I receive I receive it.

Xz premium freezing and resetting when i unlock it. Also no volume up, related?

Hey Guys so i have searched high and low for a solution and still can't figure out a fix. i've read on sony forums that other people experienced the same issue but can't find a fix. I got the phone second hand (risky i know but i took a gamble) and it already have android pie. At first it was working great and i was quite happy with the phone but as i started using it every now and then it would reset itself at random, even in my pocket, then it started freezing when i unlocked it and eventually reset and work again for a bit. from the start the volume up button was not working but i can deal with that. on other threads i have read that some people are having the exact same issue. Help is very much appreciated.
So far i've tried turning off fingerprint unlock, uninstalling apps, turning off auto brightness, turning off the code unlock, factory reset, flashing to android oreo, and running in safe mode and so far none of that has fixed the issue. (although it helped temporarily giving me false hope!)
i'm going to try flashing back to nougat as a last resort but am not going to have too much false hope. Thanks for reading and any help in advance!
leemo89 said:
Hey Guys so i have searched high and low for a solution and still can't figure out a fix. i've read on sony forums that other people experienced the same issue but can't find a fix. I got the phone second hand (risky i know but i took a gamble) and it already have android pie. At first it was working great and i was quite happy with the phone but as i started using it every now and then it would reset itself at random, even in my pocket, then it started freezing when i unlocked it and eventually reset and work again for a bit. from the start the volume up button was not working but i can deal with that. on other threads i have read that some people are having the exact same issue. Help is very much appreciated.
So far i've tried turning off fingerprint unlock, uninstalling apps, turning off auto brightness, turning off the code unlock, factory reset, flashing to android oreo, and running in safe mode and so far none of that has fixed the issue. (although it helped temporarily giving me false hope!)
i'm going to try flashing back to nougat as a last resort but am not going to have too much false hope. Thanks for reading and any help in advance!
Click to expand...
Click to collapse
You pretty much ruled out a software issue by reverting back to Oreo and all that.
Volume rocker isn't something that just fails on these phones, so that's suspicious to me.
In most cases freezing/rebooting is caused by a faulty current supply (battery) and distribution (conectors, cables, capacitors...), if the software issue is ruled out. Faulty screen, screen connector and cable can cause freezes, the phone itself doesn't freeze up, but the image on the screen does, so it looks like the entire phone freezed, but it didn't, just the screen. Again, this as well can be caused by bad power delivery to the screen.
I would take it apart, take a closer look at the board, connectors, possible corrosion and dirt on capacitors, and replace the battery since it probably hasn't been replaced ever, and it's now a fairly old phone, and second hand, god knows how was it charged and treated in general.
If you never opened a phone before, I wouldn't suggest you start with this one, it's not really "novice friendly". Take it to someone who does board level repairs.
My best bet would be the phone was opened and some service has been done on it, but not properly+bad battery/battery connection.
Volume rocker is very easy to mess up, if you don't reseat it well it can fail to register pushing the button.
There really isn't a simple straightforward answer to you issue, if the software is 100% ruled out, the board and battery needs to be checked out, specially if the phone was opened before.
Atrax2010 said:
You pretty much ruled out a software issue by reverting back to Oreo and all that.
Volume rocker isn't something that just fails on these phones, so that's suspicious to me.
In most cases freezing/rebooting is caused by a faulty current supply (battery) and distribution (conectors, cables, capacitors...), if the software issue is ruled out. Faulty screen, screen connector and cable can cause freezes, the phone itself doesn't freeze up, but the image on the screen does, so it looks like the entire phone freezed, but it didn't, just the screen. Again, this as well can be caused by bad power delivery to the screen.
I would take it apart, take a closer look at the board, connectors, possible corrosion and dirt on capacitors, and replace the battery since it probably hasn't been replaced ever, and it's now a fairly old phone, and second hand, god knows how was it charged and treated in general.
If you never opened a phone before, I wouldn't suggest you start with this one, it's not really "novice friendly". Take it to someone who does board level repairs.
My best bet would be the phone was opened and some service has been done on it, but not properly+bad battery/battery connection.
Volume rocker is very easy to mess up, if you don't reseat it well it can fail to register pushing the button.
There really isn't a simple straightforward answer to you issue, if the software is 100% ruled out, the board and battery needs to be checked out, specially if the phone was opened before.
Click to expand...
Click to collapse
Thanks for the comprehensive reply, so would system ui not responding also be due to the hardware? I just thought it was strange that some other people had posted pretty much the exact same issues.. I'll start looking around for someone to pull it apart for me. I've done some screen repairs on one phones but I'm not willing to screw this one up so I'll find an expert!
leemo89 said:
Thanks for the comprehensive reply, so would system ui not responding also be due to the hardware? I just thought it was strange that some other people had posted pretty much the exact same issues.. I'll start looking around for someone to pull it apart for me. I've done some screen repairs on one phones but I'm not willing to screw this one up so I'll find an expert!
Click to expand...
Click to collapse
Ofcoruse, mostly power delivery. If for example the cpu or the screen isn't getting correct voltage and power, it can missbehave or freeze up as a failsafe to prevent damage.
As I said, I would take a look at the board, and change the battery with a known good one, since I have spares lying arround, to eliminate that variable as well as software.
I presume you're not rooted and you're troubleshooting using oem firmwares. If not, all bets are off.
A faulty battery can be a culprit of many issues that look like software/ui issues, but they're not.
Make a full software repair with latest official version, if it fixes nothing, it's a hardware issue.
Atrax2010 said:
Ofcoruse, mostly power delivery. If for example the cpu or the screen isn't getting correct voltage and power, it can missbehave or freeze up as a failsafe to prevent damage.
As I said, I would take a look at the board, and change the battery with a known good one, since I have spares lying arround, to eliminate that variable as well as software.
I presume you're not rooted and you're troubleshooting using oem firmwares. If not, all bets are off.
A faulty battery can be a culprit of many issues that look like software/ui issues, but they're not.
Make a full software repair with latest official version, if it fixes nothing, it's a hardware issue.
Click to expand...
Click to collapse
Thanks very much, I'll give that a go first!
If it fails where and you are close to me (Melbourne Aus) how would you like a project?
I share with you my personal experience.
The phone is amazing, is very fast, efficient, amazing sound, amazing screen.
I have the same problem with the volume up bottom but in my case it was caused for a fall incident, I took it apart and I discovered there is one flex connector that goes from the mother board and is shared with the volume bottoms, the power- fingerprint sensor, the camera bottom, the lower speaker and the lower microphone.
In fact due to that fall I am having problems with the volume up bottom as I wrote, the lower microphone, the lower speaker and sometimes the fingerprint function does not work.
I think is still worth having the cel phone, I`ll search for the flex to fix it up
I think most of the description Zagreb does of your case can be adjusted to the reality of what is happening, I think is necessary a technical checking of the hardware.
I'M sorry, of course I meant buttons and not bottoms!
Freezing, unresponsive ui and volume buttons not working properly.
I've had this same issue for a few weeks tried hard resets safe mode, etc, nothing helped. So after much frustration searching forums to no avail I set to and tried a deeper investigation into my own device, I accessed the dev options and looked at power hungry services. The most hungry was Xperia home so I stopped it and low and behold my phone hasn't locked up since, still volume buttons are mostly not working but I'm not locked out any more.
Same here,
First randomly reboot, after factory reset randomly system UI failed constantly , very annoying.
Indeed button up volume is not working (properly).
Someone found solution for this? I already purchased a new battery.
@Chernob0g : how you disabled/stopped Xperia Home so I in meantime can use my phone.
Replaced battery, looks better now.
Volume up still not working, but freezing looks solved.

Categories

Resources