Related
Hi, I never root my phone or flash a custom ROM.
The problems was started when I flashed a new ROM from sammobile of another country, my phone comes with 4.2 and I flashed a 4.3.
I flashed newer ROM from only Vodafone-Spain (only those really are my official supplier), and then I update ever with Samsung KIES, (no Knox counter)
So, with Andorid 4.3 I had more problems than now with 4.4, now the only problem is with WIFI
I can use normally, with screen ON, the problem is when sleep for a long time (more than 1 hour) when I touch a button I see the unlock screen, but does not seem to work the touch screen, and screen go off after a seconds, if I touch other button the screen don't go on. And then, after aprox 30s it reboot itself, and show a window telling that the Process System is not responding, do you want to close?, and two buttons, close or wait.
I tried to start my phone in Secure Mode and I have the same problem, so it is not an app, it is the ROM.
I do at least 2 Factory Reset, but the problem is still there.
I think it is a software problem and not a hardware problem, because the problem start when I update to Android 4.3
I tried the trick WIFI Power save Mode OFF (on dialer, *#0011# -> WIFI -> Power save mode OFF) and never reboot automatically, so the problem I think it is with this power save mode. But if I turn off, when WIFI is ON, the battery drain fast.
In the samsung shop they tell me that first will format my phone to see if the problem solve and try for a time, if not solve, then I have to send by mail... and I will not send it because I know the time it will take to repair it is about 1-2 months and I need the phone for my work.
So is there another solution or something to try?
Napalm Candy said:
So is there another solution or something to try?
Click to expand...
Click to collapse
Try reflashing the Firmware once again mate and Here you can follow the tutorial from here
Repulsa said:
Try reflashing the Firmware once again mate and Here you can follow the tutorial from here
Click to expand...
Click to collapse
Since the first ROM (4.2) I flashed 3 or 4 ROMs from SamMobile, so I am not very optimistic. But I don't lost nothing, I will try it
I flash again the ROM, and after 2 days testing, the problem is still there.
Any other thing to try before send to samsung?
Please, give me another idea to try. I really have a problem with WIFI
This is how Wifi (some times) drain my battery when are not connected to a network. But the problem is worst when is connected, because it freeze and reboot.
Hello! You could fix the problem? I took suffering the same problem as your months, and I have not been solved, I'm for kicking the **** mobile! As may give so many problems with the wifi?
regards
manguila said:
Hello! You could fix the problem? I took suffering the same problem as your months, and I have not been solved, I'm for kicking the **** mobile! As may give so many problems with the wifi?
regards
Click to expand...
Click to collapse
Yes I solve. So.. I don't solve it, it solve it self. One day I saw that I don't had wifi connection, then I saw that I don't any WIFI names stored, all was erased automatically, I don't know how.
But the result it, I don't have anymore a freeze or a reboot because wifi. ALL, absolute ALL run fine now. I had a lot of WIFI names stored, about 30-50, maybe this was the problem, a conflict with some of these names, but I'm not sure
No one update, reflash, factory reset, or start in safe mode was solve any problem, the problem solve it self... very strange.
If you try a factory reset, then don't restore all your mobile config. Try to install all apps manually, one by one. I ever restored my backuped config, and I think this was the problem.
Hope you can solve it
Napalm Candy said:
Yes I solve. So.. I don't solve it, it solve it self. One day I saw that I don't had wifi connection, then I saw that I don't any WIFI names stored, all was erased automatically, I don't know how.
But the result it, I don't have anymore a freeze or a reboot because wifi. ALL, absolute ALL run fine now. I had a lot of WIFI names stored, about 30-50, maybe this was the problem, a conflict with some of these names, but I'm not sure
No one update, reflash, factory reset, or start in safe mode was solve any problem, the problem solve it self... very strange.
If you try a factory reset, then don't restore all your mobile config. Try to install all apps manually, one by one. I ever restored my backuped config, and I think this was the problem.
Hope you can solve it
Click to expand...
Click to collapse
Thank you very much for answering so quickly.
Happens to me exactly what you do, but seems to have no solution.
I have tried more than 8 roms, stock or mods, and always fails.
At first I thought it would issue the modem or kernel, but after many tests, I do not ****ing know what is causing the problem.
I'm running out of solutions, anyway thanks for telling your case...
I'm glad that in the end one way or another, you have it fixed.
:good:
manguila said:
Thank you very much for answering so quickly.
Happens to me exactly what you do, but seems to have no solution.
I have tried more than 8 roms, stock or mods, and always fails.
At first I thought it would issue the modem or kernel, but after many tests, I do not ****ing know what is causing the problem.
I'm running out of solutions, anyway thanks for telling your case...
I'm glad that in the end one way or another, you have it fixed.
:good:
Click to expand...
Click to collapse
What happens when you fully wipe, flash a 4.4.2 rom, don't restore anything, not even your google account and don't install any apps.
Lennyz1988 said:
What happens when you fully wipe, flash a 4.4.2 rom, don't restore anything, not even your google account and don't install any apps.
Click to expand...
Click to collapse
Thanks for your interest! The truth is that it is very strange ...
If I remember correctly, already try what you mention me, but I kept going ... It's like at some point something had happened which change roms not seem to solve..
I'm considering installing a rom with 4 files and pit file, but do not know if this will help in something
Let's see if I can come up with the bug because it is becoming a pain in the ass
:good:
I would try what say Lenny1988. So the only change before solution and after solution, was a big crash on WIFi drivers/app/modem (don't sure) it self, and was deleted all my stored wifi access points that I had. It was a problem related to Wifi power save, if I disabled it then I had no reboots/freezes.
So, I would try a factory wipe and DON'T restore anything, and try for a couple days. If work, then you know a way to solve it.
Tell us if it works.
Hello there! I will update with the latest news!
I tried the recommended advice, but no luck...Not seem to affect him leave without restoring.
The only thing that seems to work and keep it running, is to disable wifi power saving system
you know....
Code:
1. Go to your phone dialer
2. Dial *#0011#
3. When you see the "ServiceMode" screen, press the left menu button
4. Select "WiFi"
5. See that "Wifi Power Save Mode" button that is "ON" - well turn it "OFF"
But this way drain your battery much faster,so it does not seem a good solution to the problem.
Curiously, the same phone, some people suffer this problem and others do not....
It may be hardware? or software?
If I find something, I'll note here.
Regards
Hey guys,
I have a Galaxy S4 (i9500). I installed Omega ROM v22 on it and everything went smoothly, Wifi & BT working perfectly.
After a few hours of using the device (nothing special at all, texts and stuff like that) - I noticed my wifi isn't working and by not working I mean that I click the wi-fi button and it changes from gray to the mid-state between gray to green for around 20 seconds before it goes back to green ago.
If I open the menu to see my networks it just says "Enabling" without any networks there.
I had to drive somewhere so I went to my car and tried to enable Bluetooth, and same thing happens there - Bluetooth will not turn on and will stay stuck on mid-state between gray and green for a while and go back to green.
I flashed omega rom v22 again and the problem was gone, or so I thought. I went back to the car for another drive and realized the bluetooth issue is back - and when I got home I realized the wifi issue is back as well.
I figured I need to reset everything so I tried the following:
Full wipe (including dalvik and even including "internal SD card") and then flashing stock rom (from the official website, stock rom of my country).
The issue was back after a few hours. I do not have BT or Wifi access. Yesterday Wifi suddenly started working for a few hours but then it stopped working again.
I really need help! I have no idea what to do with this issue!
Well rule number one when you have problems after flashing without wipe.
1. perform a full wipe and see if the problem persists.
Lennyz1988 said:
Well rule number one when you have problems after flashing without wipe.
1. perform a full wipe and see if the problem persists.
Click to expand...
Click to collapse
Tried that, no luck.
What else would you try?
In some places when people had problems with Wi-Fi they said to flash a different kernel but I don't see why I would have this specific issue with Omega Rom and why the default kernel with it wont work well?
Maybe this could be a root issue? My root works fine but I have this weird gut feeling like this is some permissions thing that's going on.
I'm trying to think why it would work right after the wipe but then stop working shortly after.
Another symptom: It randomly started working for a few minutes and then stopped again (around three hours ago).
Any idea what's going on?
Well, if you fully wiped and didn't restore any apps and settings then it can be two other things.
Or it's a bug in the rom or a hardware failure in your phone.
I would suggest trying a different rom first. Do not restore anything, not even your google account.
wi-fi fix?
Do you actually have an i9505? or is it a canadian or att version? if its the latter sometimes the devs offer some wifi-fixes, also try a different kernel. otherwise it could be that your radio/modem are not compatible with the version of the ROM you are flashing.
Tried arrow ROM and this issue doesn't seem to happen in this rom. Hope it stays like that...
morhsn said:
Tried arrow ROM and this issue doesn't seem to happen in this rom. Hope it stays like that...
Click to expand...
Click to collapse
Sadly, it did happen with this rom, after just a few hours.
I'm now using stock rom and still suffering from the issue.
Does anyone have ANY idea what I can do to fix this?
Thanks in advance!
Hello all,
I've been searching for 3 days now and cannot find a solution to this problem. Normally I try to avoid starting a thread since there is usually one on the internet somewhere already, but this has me stumped.
I have a SGH-I337M on Bell, was running SlimKat 4.4.4 with no problems, and wanted to upgrade to LP. I first tried installing the CM12 optimized build, but it would never get past the boot screen. Then I tried GPE 5.0.2, and it looked beautiful and ran smoothly, but it would not automatically connect to Bell's network. If I went into the mobile networks menu and waited for it to scan, and then selected Bell, it would connect, but a few minutes later it would disconnect again. WiFi worked fine. Needless to say, having no constant service was unacceptable. After that I tried installing SlimLP (wiping cache, system, etc in between all installs) and had the same service disconnection problem.
Then I tried:
-flashing modems
-flashing back to stock from SAMmobile and reinstalling (where a similar problem persisted)
-starting from fresh to GPE, then starting from fresh to SlimLP
-reflashing GPE with all 3 kernel choices, cutting out as many installation options as I could
-trying different combinations of preferred wireless mode, APN, etc
Nothing works. I am back on SlimLP and I have got it to the point where the Bell service will work as long as the screen is on, but when I hit the power button and/or the screen goes off, the network disconnects again. If WiFi is NOT on, when I hit the power button and unlock the lock screen, it will automatically connect to Bell again, but this does not happen if WiFi is on.
Any ideas here..? I've read countless threads and nothing seems to work. Any help would be much appreciated as this is driving me crazy!!
The issue has been resolved! Apparently I was too impatient and was not using the proper modem
But I can't find a way to delete this thread. Damn I must be getting old
Hi guys, I have to clear my mind on a problem:
I have a XT1562 european mono-SIM Moto X Play, and I've upgraded it to Marshmallow (the indian dual-SIM firmware) after unlocking the bootloader and flashed Squid kernel some weeks ago (and then updated to the last build, of course).
Sometimes I'm experiencing an annoying thing: after a reboot RIL dies, and on the best, on the next reboot it reappears; on the worst, after multiple reboots with no luck, I have to do a wipe cache to see it again.
I have root and Xposed (and so, also busybox).
Is anyone experiencing something similar?
There's a way to fix it that maybe I didn't find here on XDA?
Nobody?
have u tried flashing the modem for ur rom?
anks095 said:
have u tried flashing the modem for ur rom?
Click to expand...
Click to collapse
Yes.
But it's strange, because I see it's not modem fault or similar. I see it's something software related because sometimes when I reboot, I also have the stock wallpaper (the green material one).
Now I flashed Marshmallux rom with the exact configuration (apps, modules, etc) and for now all is ok.
But, I still wanna follow this thread because it's too strange and I want to see if someone will expose a pearl.
nplezka said:
Yes.
But it's strange, because I see it's not modem fault or similar. I see it's something software related because sometimes when I reboot, I also have the stock wallpaper (the green material one).
Now I flashed Marshmallux rom with the exact configuration (apps, modules, etc) and for now all is ok.
But, I still wanna follow this thread because it's too strange and I want to see if someone will expose a pearl.
Click to expand...
Click to collapse
Ok..good...but may be u can do a full wipe and then flash factory image and then check it out if the problem sill exist..if not then that should something with software with ur last OS.
anks095 said:
Ok..good...but may be u can do a full wipe and then flash factory image and then check it out if the problem sill exist..if not then that should something with software with ur last OS.
Click to expand...
Click to collapse
Hi guys, I'm back to inform you that I'm on Marshmallux and the problem is still the same. I get randomly "emergency calls only" until reboot (maybe).
I don't understand...
nplezka said:
Hi guys, I'm back to inform you that I'm on Marshmallux and the problem is still the same. I get randomly "emergency calls only" until reboot (maybe).
I don't understand...
Click to expand...
Click to collapse
I don't know if this is the same thing as you but I had "Emergency Calls Only" sporadically as well but it would come back either after a short period of time or after a reboot. I also had random reboots too (didn't matter which ROM I was on at the time).
I lived with this for a bit but then upgraded my SD card (it was old) and I haven't had either problem since.
My guess is that my SIM card might not've been seated properly in the little carrier and/or the SD card I had was mucking things up somehow. I wasn't using it as internal storage either.
Anyways, if you haven't tried this already, might be worth taking out your SIM card and re-seating it (and maybe give the contact part a careful wipe). If you still have the problem and you have an SD card remove it and see what happens. Good luck!
Hi guys! I'm here with news:
after several tests in these days, I discovered the problem was every module that can modify the systemUI.
I tried activating and disabling those modules one by one (I'm talking about GravityBox first, then little modules like Advanced Power Menu or a newer one called NeoPowerMenu), and I saw that without them, I had network at every reboot. The only exception in systemUI is SignalIconsAOSP (I really hate that big "4G" icon next to the signal indicator) and it works at every reboot I did. The other modules (like Xposed GEL Settings, Lolistat, YouTube AdAway) don't annoy the system.
So, I don't know, Moto seems dislike too much modifications on the UI or it's a strange bug. Maybe a bug.
(Edit 1) Found a fix already! Read post 2!!!
Hello there,
I've been having a OnePlus Two since 4 months already, and had like 2 or 3 home button not working issues.
They used to fixed by themselves after a couple of days of not working, but not this last time.
I tried already the reinstalling system (after formatting system via TWRP), clean it several times, hard reset (hold power button for more than 20 seconds), complete drain battery and fully charge it again, force stop fingerprint service, take out the tempered glass screen protector, and none of those solutions worked.
I here attach (copy the link, can't upload a video directly to this post) a video in which you can see that whenever I power on the screen (still locked), the home button works for several times, but as soon as I unlock it (pattern lock) it stops working. This makes me think that the problem is software, not hardware, but as I said before, already tried reinstalling OOS 3.0, wiping system, cache, data, internal storage, etc.
I compressed the video so it wouldnt be too big, but quality is good enough, just rise the volume so you can listen to the "vibration" that the home button produce.
Any help would be appreciated.
Sincerely,
Daniel Castro
Fix for the issue!
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
I have the same problem
Tomorrow i'll try your method
I've posted a questione about this issue,
I think the One plus team should find a solution to this problem that afflict many users
Also, don't forget to rotate your phone 720 degrees, counter clock wise! ? hocus pocus....
DCastro555 said:
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
Click to expand...
Click to collapse
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
LOL9988 said:
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It will erase everything, make a backup before starting the process.
faustin95 said:
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
Click to expand...
Click to collapse
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
pitrus- said:
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
Click to expand...
Click to collapse
If it works, its worth a try . And yeah, but we are not in any OnePlus Forum, neither debating about if they are gonna do anything about their own issue, we are trying to fix what an irresponsable company wont.
can we make together an official request to one plus to give us an answer or explanation about this? a lot of users are facing this issue, it's not normal
This is my second opt I bought that this problem has happened
sorry for my english
I had also tried lot of things but home button is not responsive at all.. H2os,exodus,oxygen 2.1 ,3.0 same everywhere
---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------
Error is: when i open fingerprint setting
Enrollment not working try differnt finger or try again ... Nd fingerprint autotest not starting also
i've turned to stock i've updated to oxygen 3.0 bet and the button worked again
i think rooting installing twrp and installing different roms may be the cause of this issue
faustin95 said:
i think rooting installing twrp and installing different roms may be the cause of this issue
Click to expand...
Click to collapse
Unfortunately that is not the case, it's a hardware design bug.
However you can f-k up your finger scanner by damage your persistant-partition if you flash up and down between different ROM/bootloader revisions. But it's easily fixed by flashing the image file for that partition again.
pitrus- said:
Unfortunately that is not the case, it's a hardware design bug.
Click to expand...
Click to collapse
it's a driver issue
faustin95 said:
it's a driver issue
Click to expand...
Click to collapse
50/50 moisture sensitivity and driver issue.
Home button has been working fine for a year, installed 3.0.1 today and suddenly home button only works in OOS 3.0.1. No longer works in CM 13, yet works fine in OOS 3.0.1. Definitely a driver issue.
Tried installing OOS 2.2.1, wiping, then installing Grarak's CM 13 and home button refuses to work. Wiped system, data, cache, installed OOS 3.0.1 and home button works again. Tried wiping again and installed CM 13, home button stopped working. Wiped and reinstalled OOS 3.0.1, home button works again.
Odd thing, my phone will only work with CM13 roms and OOS 2.2.0 or less for fps and home button. Nothing will fix or ever work.
For me, the home button stopped working for a short while on Graraks, then it just jumped back to life again and I haven't had any more home button blackouts after that. If it's a driver issue, it's an extremely intermittent one.
The fingerprint scanner has stopped working from time to time at lockscreen, but this is acceptable for an official hackjobb supported scanner until official sources are released ?
Need Help with this!
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks! I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet so literally dont know why it happened.
Thanks,
Max