Hi there !
My Xperia S has been quiet slower ever since the problem appear, the wifi wouldn't turn on, button just freezes trying to work.
I have changed several custom roms and kernels and nothing worked sometimes a normal factory reset let the wifi work for 1 day (I thought that this will exclude the hardware problem ?). I know the tricks that consists into wiping the data\misc\dhcp directory but this won't work neither; I really can't see what is wrong; do you guys have any idea ? So if hardware though i don't think it's that wich piece is it ? (i've taken evrything out of my phone cleaned and reassembled but nothin made it .. :/ ) and if software, which firmware is the right one ?
(by the way XDA is just great)
Thanks
Related
this problem is occuring with the new roms , it s quit irritating... how to solve it ??????????????????????????????
Got the same over here
Trued allot of roms bud still didn’t got a good one
When you have afresh rom installed
It looks like it gone work properly it reacts fast like it should be
Then when you install your favo aps lik battery pack or spb
It still works oke the signal strength is maximum
Bud if its on for a day it’s terrible
Y think something in the rom making it hang
To bad there isn’t any task bar ap so you can see what’s making the universal hang
Still looking for the right one
i meant right after power on ... device is not responding
i didnt mean slowness after a while due to loaded program memory, i meant TOTAL hanging / stop responding of the whole device for few seconds right after you power it on .... ??????
We need more information such as...
What ROM version are you using?
What softwares do you have installed and running?
Does a hard reset solves the problem?
Did it ever occurred before this?
Did you install something different this past few days?
do you have software at the today screen which is installed on SD card?
if yes, remove from today screen or install to main memory...
le_toubib said:
this problem is occuring with the new roms , it s quit irritating... how to solve it ??????????????????????????????
Click to expand...
Click to collapse
Are you using Wisbar Lite ???
AKU/cashe ????
when i press the power button the screen goes on , but no icons are responding at all , untill few seconds...
it occured with "JASJAR_ME_13082_171_10900_wwe_ship"
also with the recent o2 rom
the new arabic i-mate rom
but it didnt occur with older roms
also it occured in a baby windows ( before installing anything )
i believe it is related to the AKU2 , i think it is related to a change in cashing or so ....
many thanks for reply
One more idea: about the same happened to me when I installed the new Qtek ROM.
After a while I found a note on these forums that it is advisable to remove SDDAEMON.EXE from the startup. It was causing a lot of duplicated notifications, and my device was hanging frequently.
So I deleted the SDDAEMON link from startup. Since than it's all OK !!
Hi guys,
maybe somebody may help me with the problem.
I am a owner of the Desire Z.
Done a Update to 2.2.1.
Used this faq for downgrade and rooting.
http://forum.xda-developers.com/showthread.php?t=905261
Afterwards i ve installed the recovery of http://www.klutsh.com/ .
First everything worked fine (WLAN etc.)
Cause i installed different Apps (Titan Backup, SMS blocker etc.) through WLAN.
Cant tell what happened but now i am having the following problem:
- Does not connect to my WIFI AP even if it worked quite well before.
- When i turn on WLAN through option menu the icon/symbol does not appear at the upper Part of the phone.
- Even closed APs (not mine) aren´t shown at the menu for the WLAN configuration.
- It is still possible to establish the internet connection to my provider and this one still works proper.
What am i doeing wrong?
Which further Infos do you need to help me with this problem?
Greetz
Jake555
Sounds like something you have installed has broke the WiFi as it was working when you first installed the ROM.
My advise would be to back everything up, do a factory wipe & then start again. This time after installing each app & its backup checking the WiFi.
This way you will find the app which is to blame & can get rid of it
Delivered by Western Union in the rain after 70 Years
You are wright with your solution of the problem.
I think this would help.
But i thought that there would be a easier and less time intensive solution like.
updating kernel, radio or something else.
Or am i wrong?
Because your solution looks more like trial and error which would takes a lot of time again.
The issue is that something is broken in your phone and it's not a common problem (you may be the only one who is experiencing it), so there isn't an accepted solution for it yet.
If you nandroid back up your phone as it is now, then wipe, you should be able to identify what app you installed or what you changed to break WiFi, from there if you wished you could restore the nandroid backup and work on fixing the problem. If you share what you learn it might be of help to anyone who runs into a similar issue in the future.
Edit - never mind, misunderstood the question.
actually i am sorry i can t tell to 100 % what changed the seetings.
have done a wipe and tryed some ealier backups which i have done before.
In one Backup the Functionality was still given and i hadn t to install from the beginning again.
If i will have again the problem i will write here a report.
greetz
jake555
Hey guys.
Maybe somebody could help me with my problem. I debraned my DHD from T-mobile some month ago... rooted it, installed Bootloader, Rom Manger and Clockwork recovery...
all works fine... then i installed Leedroid 2.3.2.. all worked fine, system was stable.
Then some weeks ago, i noticed, that my touchscreen doenst work anymore... I turned the phone off, took the accu out w8 some mins, rebooted over CW.. then it wokred again...
today i got a phonecall, wanted to take it... again... no reaction from the touchscreen or the keys down.... i tried all today, wiped all data, did a recovery, installed new ROM's.. nothing worked.. the volume buttons and the power button did work... i dunno what to do anymore?
Maybe anbdy got some ideas?
Greetz
I would suspect LeeDroid, has issues. Have been hearing a variety of issues....
When you said installed new ROM's, does that mean different ROMs, versions of Leedroid, or what?
first of all i reinstalled, the current leedroid... doesnt work
then i wiped all data and installed MIUI... system, all is working fine (it seems so)
but the touchscreen still doenst work...
i read something about to install a RUU rom.. but that wasnt based 100% on my problem
nobody got any idea ? :-(
If its not a software problem.. than you can try some hardware stuff....
take any hair dryer and .. blow some hot air on the screen boundries... and just press it ....not too hard, just a bit softly.. as if you are trying to stick screen back. This might help you... Please try this at your own risk
Just a note: This is the Desire forum, not the Desire HD
Hello iv'e had a similar issue before with a different device
overnight after a sudden crash of the phone itself wifi no longer turned on
it's simply saying that "turning on" but never does
ive tried different roms swell currently on "viperx" and it hapened on "paranoid anrdoid" and tried some variants of CM10 in between aswell
i allways flash the boot.img from the rom zip and using costum kernels just caused a boot loop .
tried to reflash root aswell just to be sure evendough it was working fine before . allso installin gnewest supersu from play store .
no roms even turn wifi on to show any networks not just weak signal .
as i understand the wifi module is mainly controled by the kernel but how can it then stop functioning after a software crash and continue to not work after several kernel reflashes .
would anyone reccomend a "best" kernel for paranoid android scince i really like the tablet mode on most of its apps but with no wifi all roms seam useless
any help appeciated
Tried doing the whole process from start even locking and reunlocking the bootloader .
now latest thing i tried is did a full restore from RUU back to stock and locked bootloader ...
the wifi still wont scan so would this mean it is a HW issue ?/or is there something else to try aswell :crying:
Hi
I've been going back and forth for a couple of days now , thinking if i should post this post or not .
so here it goes , i had a n910p for a couple of months now it was on 4.4.4 when i got it and it worked just fine no problems except some dying battery related problems -phone shuts down when using the flash camera, the phone shuts down without any warning and then i find the battery at 5% when turned back on - ( i didn't know it was a battery problem back then ) , but everything else was just fine .
-i should mention i'm in Jordan not the US so the phone is unlocked sim .
So i wanted to upgrade to Marshmallow maybe the problems got fixed , so in order to upgrade to MM i had to first upgrade to 5.x.x and i did and tested it for a couple of days it had some Freezes but nothing unmanageable , i changed the battery while i was on 5.1.1 there was no problem here no freezes no random shutdowns .
And then i upgraded to MM that's when the problems started to show one after the other , all described here and add to that i had to add and remove the battey 3-4 times in order to turn on the phone.
so i thought to my self it started since i upgraded to MM , maybe if i downgraded to kitkat it'll go away .
i downgraded to 4.4.4 not the stock just to see if it was any better, and it was !!
no freezes no random shutdowns except for one problem if i wanted to shutdown the phone or do a restart i had to remove and add the battery in order to get back on .
so my question is , why is this happening ?
is it a hardware problem and just my luck it started popping out when i started upgrading ?
why is it there is less problems when i downgraded to Kitkat ?
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Mohannad_Almasharqa said:
Hi
I've been going back and forth for a couple of days now ,
.......
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Click to expand...
Click to collapse
This problem is a little confusing and beyond me, but I have to ask and suggest one thing.
Instead of doing OTA, Have you tried to just use odin to flash the Marshmallow firmware you want?
Mohannad_Almasharqa said:
Hi
I've been going back and forth for a couple of days now , thinking if i should post this post or not .
so here it goes , i had a n910p for a couple of months now it was on 4.4.4 when i got it and it worked just fine no problems except some dying battery related problems -phone shuts down when using the flash camera, the phone shuts down without any warning and then i find the battery at 5% when turned back on - ( i didn't know it was a battery problem back then ) , but everything else was just fine .
-i should mention i'm in Jordan not the US so the phone is unlocked sim .
So i wanted to upgrade to Marshmallow maybe the problems got fixed , so in order to upgrade to MM i had to first upgrade to 5.x.x and i did and tested it for a couple of days it had some Freezes but nothing unmanageable , i changed the battery while i was on 5.1.1 there was no problem here no freezes no random shutdowns .
And then i upgraded to MM that's when the problems started to show one after the other , all described here and add to that i had to add and remove the battey 3-4 times in order to turn on the phone.
so i thought to my self it started since i upgraded to MM , maybe if i downgraded to kitkat it'll go away .
i downgraded to 4.4.4 not the stock just to see if it was any better, and it was !!
no freezes no random shutdowns except for one problem if i wanted to shutdown the phone or do a restart i had to remove and add the battery in order to get back on .
so my question is , why is this happening ?
is it a hardware problem and just my luck it started popping out when i started upgrading ?
why is it there is less problems when i downgraded to Kitkat ?
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Click to expand...
Click to collapse
Odin MM like suggested.. Don't do any mods. If it persist, then you might be looking at faulty hardware ie main board.
i just flashed MM after reading your replay , and will test it out.
any tips on what to do with the phone if it's a hardware problem ?
so right at the first boot i had this error shown in the images (attachment)
i removed the battery and restart the phone and it booted correctly , the same problems began to show freezing random restart and it keeps booting to recovery and i had to add and remove the battery a couple of times to turn the phone on .
i returned to stock 5.1.1 apparently it's the most stable thing i can use right now , honestly i'm puzzled on this problem i'm quite sure it's hardware and software somehow and if i send it to a local shop they probably will say "i don't know what seem to be the
problem "
so i'm just going to keep using it until it becomes a replacement parts for his other brothers . :crying:
I'm no expert, but i've poured through dozens, maybe hundreds of pages about this issue. Happened entirely with MM, and most people have thrown their hands up calling it "faulty hardware".
All the accounts, the symptoms, the timing, and the root problem (eMMC error) point to a bug in MM that messes something up when it installs itself- *sometimes*. Those unlucky enough to catch this bug are stuck with it, and end up with essentially a brick or returning it.
Hardware doesn't make sense, not when the issue completely coincides with an update. Unfortunately, I don't know how to completely 100% wipe this device and re-load it from scratch, which is what I think it's gonna take. I don't even know what all *can* be wiped 100% :/
akira6968 said:
I'm no expert, but i've poured through dozens, maybe hundreds of pages about this issue. Happened entirely with MM, and most people have thrown their hands up calling it "faulty hardware".
All the accounts, the symptoms, the timing, and the root problem (eMMC error) point to a bug in MM that messes something up when it installs itself- *sometimes*. Those unlucky enough to catch this bug are stuck with it, and end up with essentially a brick or returning it.
Hardware doesn't make sense, not when the issue completely coincides with an update. Unfortunately, I don't know how to completely 100% wipe this device and re-load it from scratch, which is what I think it's gonna take. I don't even know what all *can* be wiped 100% :/
Click to expand...
Click to collapse
Here is the thing though (I have the same issue). If you remove the battery and put it back in, say 30 seconds later, it won't turn on. If you remove the battery for like 5 minutes and then put back in, it might turn on. I'm talking about the first little vibrate it does when holding the power button to turn on. It really acts like a hardware issue to me. The only work around that has worked for me is an app called wakelock. Using this app and selecting partial partial wake lock makes the phone run completely normal.
What REALLY sucks right now is that I have an OTA update waiting for me and the phone needs to reboot to install. The phone won't reboot. When it turns off, it won't turn back on without removing the battery for 5+ minutes.
IT is the MM Update
Im not an expert or anything but i have the same problem cant update cuz phone has to be restarted i finally had enough of it took it in told them (sprint) to update it thay said thay did but thay didnt. Called and thay couldnt fix it so i said the heck with it and i flashed it still doe the same must use wake lock app wish someone could figuer this out.
gbennett21 said:
Im not an expert or anything but i have the same problem cant update cuz phone has to be restarted i finally had enough of it took it in told them (sprint) to update it thay said thay did but thay didnt. Called and thay couldnt fix it so i said the heck with it and i flashed it still doe the same must use wake lock app wish someone could figuer this out.
Click to expand...
Click to collapse
Yes having the same issue as well but now even the wakelock app won't keep it. The phone wil stay for maybe an hour, then reboots and will continue to reboot until I take the battery and then start it again afterwards. The length of time the phone stays on varies really and it could be as long as 3 or 4 hours, but it will definitely reboots itself, I cannot got 1 day without this happening. At this point the phone is unusable. I am on another phone at the moment.
I did flash the MM updates (even went back 3 or 4 older versions) using ODIN and same issue. I am debating whether I flash an older Lollipop version and see if that makes a difference.