Hello, guys. First of all, I'd like to apologize in advance for my bad english. If there is any part of the message that isn't very clear, please inform me so I can correct it.
Here's the deal: I've been using for some time the Jelly Bean Ressuction Remix Rom from Westcrip.
Since about a month and a half (since version 3.9, I believe), I've been getting some weird and random signal drops. Back then, I had to manually reboot my phone so the data connection would come back. At the time I thought it was because the rom was still a nightly build, not very stable, so I coped with it.
This problem has worsen considerably since one or two weeks ago: those "signal drops" have become more and more regular. And following the signal drop, the screen would flicker a little and then the phone would automatically turn off. When I turn the phone back on, the battery is almost depleted, even tho it was full right before the crash. Again I'd blame the RR from Westcrip (by the time I was using the version 3.1.0). When version 3.1.2 came out, I did a clean installation (wipe data/factory reset/format system partition/wipe cache and dalvik, etc), even changed the kernels (used both Dorimanx and Siyah), a lot of modems, and still got this same problem: signal drop (usually when the phone is under a relative amount of stress, like playing Angry Birds, browsing the web, and even while using whatsapp!!!) followed by the phone turning itself off.
I then thought: what the hell, the problem has to be with the rom, not my phone. Then, I tried installing different roms (Paranoid Android and Slim Bean), and still got the same results. If anything, the phone is rebooting even more often now than before. I can't use it for 15 straight minutes and I get that problem,
Since this has happened with all these different roms I dont believe its related specifically to any of those.
Another strange thing: this "signal drop" followed by the rebooting only happens when the phone is disconnected from any power source and being actively used by me. If I'm recharging it, for example, the phone wont reboot at all. Also, if it is over my desk but I'm not using it, the phone also wont reboot. However, if I take it out from the power source and starting using it, I'll get another reboot in about 5-10 minutes of use.
I searched the forum and didnt find anyone with a similar problem... have any of you guys seem this happen before? I'm beggining to think that my phone is gonna die on me anyday now.
Regards!!
Daimao1984 said:
Hello, guys. First of all, I'd like to apologize in advance for my bad english. If there is any part of the message that isn't very clear, please inform me so I can correct it.
Here's the deal: I've been using for some time the Jelly Bean Ressuction Remix Rom from Westcrip.
Since about a month and a half (since version 3.9, I believe), I've been getting some weird and random signal drops. Back then, I had to manually reboot my phone so the data connection would come back. At the time I thought it was because the rom was still a nightly build, not very stable, so I coped with it.
This problem has worsen considerably since one or two weeks ago: those "signal drops" have become more and more regular. And following the signal drop, the screen would flicker a little and then the phone would automatically turn off. When I turn the phone back on, the battery is almost depleted, even tho it was full right before the crash. Again I'd blame the RR from Westcrip (by the time I was using the version 3.1.0). When version 3.1.2 came out, I did a clean installation (wipe data/factory reset/format system partition/wipe cache and dalvik, etc), even changed the kernels (used both Dorimanx and Siyah), a lot of modems, and still got this same problem: signal drop (usually when the phone is under a relative amount of stress, like playing Angry Birds, browsing the web, and even while using whatsapp!!!) followed by the phone turning itself off.
I then thought: what the hell, the problem has to be with the rom, not my phone. Then, I tried installing different roms (Paranoid Android and Slim Bean), and still got the same results. If anything, the phone is rebooting even more often now than before. I can't use it for 15 straight minutes and I get that problem,
Since this has happened with all these different roms I dont believe its related specifically to any of those.
Another strange thing: this "signal drop" followed by the rebooting only happens when the phone is disconnected from any power source and being actively used by me. If I'm recharging it, for example, the phone wont reboot at all. Also, if it is over my desk but I'm not using it, the phone also wont reboot. However, if I take it out from the power source and starting using it, I'll get another reboot in about 5-10 minutes of use.
I searched the forum and didnt find anyone with a similar problem... have any of you guys seem this happen before? I'm beggining to think that my phone is gonna die on me anyday now.
Regards!!
Click to expand...
Click to collapse
Hey,
pls backup ur apps and then do this:
0) Do a nandroid Backup via recovery
-- backup and restore
-- backup to internal (or external) sd card
1) Download Rom
2) Put it on internal sd card
3) Go into recovery mode
4) DO A FULL WIPE!! (U won't loose ur backup on sd card [but u can copy it to PC, too, if u want])
-- wipe data/ factory reset
-- wipe cahe partition
-- advanced > wipe dalvik cache
-- mount and storage > format data/system/cache
5) Then flash Rom
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
6) Then flash Gapps
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
7) Recovery > wipe cache partition
8) Recovery > advanced > wipe dalvik cache
9) Then flash Dorimanx
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
6) Reboot and u r done!
Links:
ROM: U should have already the newest one, or at least u know, where u find it.
Dorimanx Kernel
Gapps
Much success,
CHEERS
Hi, thanks a lot fot the help.
I did all the steps above and I'm still getting the same results...
Another thing to notice is that yhe phone gets really hot for apparently no reason at all (like booting up, running aLogcat and other minor apps), and when that happens, I usually get a signal drop (if the phone is plugged in it wont reboot, if its not, it will reboot).
Is there anything else I can try?
Updating: I've been restoring my old nandroid backups for the whole day to see if the problem had anything to do with Jelly Bean. Well, I've gone back to the old ICS days and every version of it had the same random and constant rebooting. Even versions that didn't have any problem before.
I'm beggining to think I have a hardware failure of some sort. Do any of you guys know what could cause this kind of hardware failure? Since the phone has been getting hot for no apparent reason, it seems to me its a problem with the SGS2 cooler. Is that even possible?
OK so I have this problem but only when using my backup battery. (Not official). When It gets around 30% it begins to make my screen flicker and loose signal and just die.
So maybe you haven't got an original (official) battery in your s2?
Sent from my Galaxy SII
I dont think I have an unofficial battery. Its the same battery that came with the phone (bought from Amazon), and also, mine says Samsung on the back. Dunno if its enough to assume its official. Is there another way to check if my battery is official?
Daimao1984 said:
Hi, thanks a lot fot the help.
I did all the steps above and I'm still getting the same results...
Another thing to notice is that yhe phone gets really hot for apparently no reason at all (like booting up, running aLogcat and other minor apps), and when that happens, I usually get a signal drop (if the phone is plugged in it wont reboot, if its not, it will reboot).
Is there anything else I can try?
Click to expand...
Click to collapse
Do u check if u r using the correct Roms for u phone? (i9100, i9100p, i9100g,etc)
CHEERS
Send from my SGSII-i9100, running RootBox nightly with Dorimanx Kernel.
Hi I am also facing the same problem. Mobile is getting hot near the camera lens.
Related
I flashed over Bionix V 1.3.1 with NextGen V2 last week by wiping data/cache/etc instead of flashing back to stock first. Everything worked really well (except for TW4 that force closes everytime) but I was just a little bugged by the 1 sec lag it takes to turn on the lock screen from sleep (the lag is absent when charging). I thought I would ODIN it back to stock and try again. Strangely, the stock has this lag now too. When I try to wipe Dalvik, I got an error "E: Can't mount /dev/block/mmcblk0p2 (File exists)". Also, my phone is still SIM unlocked after ODIN. Does this mean there are some parameters from previous flashes remaining in the system? How can I REALLY get it back to stock?
with windows plug the phone into pc then right click on the internal sd on my computer then format, should get rid of anything left from previous roms, remember to back your stuff up
dont know how to do it on mac
Thanks, will try that.
Another (silly?) question: it's always advised we leave the phone alone for ~15min before we reboot and play with it. Whenever I flash Bionix ROMS, the first thing upon reboot after flashing is a question from Google about knowing my location (or something like that). Does 15min starts the moment the phone reboots or after I've responded to the question?
donnygg said:
Thanks, will try that.
Another (silly?) question: it's always advised we leave the phone alone for ~15min before we reboot and play with it. Whenever I flash Bionix ROMS, the first thing upon reboot after flashing is a question from Google about knowing my location (or something like that). Does 15min starts the moment the phone reboots or after I've responded to the question?
Click to expand...
Click to collapse
id leave it from the moment it first comes on before
when i was flashing between 2.2 roms i always went back to simply galaxy and that had the old start up thing but i use to leave it before going through it then reboot then go through it then reboot after
1 reboot should do it though
Tried formatting but no improvement. Tried softlocker app and was able to turn on the lock screen instantly. However, I was losing about 5% battery life every hour, so that's not quite a solution. I then tried something really simple - remove the external SD. Immediately, I could see a reduction in lag when turning on the lockscreen from sleep (<0.5s vs >1s, if you call that a lag). It seems like the external SD card is the problem but I don't know what. The card seems to be lacking the ext2 partition, thus it couldn't be mounted or formatted in CWM. From what I understand, ext2 may improve I/O performance but I may be wrong. I couldn't get it to partition in my phone. The phone seems to format it back to FAT. I'll try getting a microSD adapter and partition it outside the phone and see if it helps, just out of curiosity.
I know there has been a million posts about this issue and I tried all the solutions. Different roms and kernels, factory resets, changing usb, battery calibrations through different methods all with no effect. In frustration I was ready to toss my s2 in the garbage but before I did I decided to try something else (links below) since I figured I had nothing to lose.
It works!! for me anyway. I removed the IC. Didn't replace just removed and my phone now works perfectly. Charges, doesnt overheat. I was reaching battery temps of 80C within a few minutes of turning the phone on before. It was even overheating while turned off! No more warnings or charging paused. So if you have nothing to lose and are ready to toss your S2 like me try this.
forum.gsmhosting.com/vbb/f258/samsung-galaxy-s2-i9100-short-circuit-solution-1537757/
and
samsunggalaxysforums.com/showthread.php/8912-Water-damage-overheating-u503-%28USB-OTG%29-and-Workaround?p=62780#post62780
I couldnt post outside links so please copy address into your browser
I fixed mine.
http://forum.xda-developers.com/showthread.php?p=41108791#post41108791
droiduzr2 said:
I fixed mine.
http://forum.xda-developers.com/showthread.php?p=41108791#post41108791
Click to expand...
Click to collapse
I tried that also. Didn't work for me
ennayhtac said:
I tried that also. Didn't work for me
Click to expand...
Click to collapse
When I was on ICS my phone ran without any problems.
I can't really remember but I think I had installed an app and it started making my phone go crazy. So I went to AOKP JB 4.2.2 and started having the high heat problem again.
So I removed an app that I had Vault and set playstore to update over wifi only.
I put the Siyah kernel. I did flash a few other modems and I had the same problem. I flashed current modem and all is fine.
Wipe your cache and dalvik cache too.
Try downloading your modem file again.
All I can say is that my battery can now last 3days (in 2g mode no data) but when I do turn on data it does not suck my battery down in 15 minutes.
*I did click on HSDP option and then turned it back on and off and back on again.
1. I would start with a clean basic ROM. Don't just wipe but format everything 2 times.
2. try different modems (I think this is where the problem is)
3. new kernel or different kernel
This phone is working great now.
droiduzr2 said:
When I was on ICS my phone ran without any problems.
I can't really remember but I think I had installed an app and it started making my phone go crazy. So I went to AOKP JB 4.2.2 and started having the high heat problem again.
So I removed an app that I had Vault and set playstore to update over wifi only.
I put the Siyah kernel. I did flash a few other modems and I had the same problem. I flashed current modem and all is fine.
Wipe your cache and dalvik cache too.
Try downloading your modem file again.
All I can say is that my battery can now last 3days (in 2g mode no data) but when I do turn on data it does not suck my battery down in 15 minutes.
*I did click on HSDP option and then turned it back on and off and back on again.
1. I would start with a clean basic ROM. Don't just wipe but format everything 2 times.
2. try different modems (I think this is where the problem is)
3. new kernel or different kernel
This phone is working great now.
Click to expand...
Click to collapse
Like I said tried everything. This fixed mine. Just sharing for others who have also tried everything. I did check the capacitor in question was the source of my problem first and there was extreme heat coming from it.
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
hackkpo said:
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
Click to expand...
Click to collapse
You should try custom rom. Try to Flash Neatrom or any stock custom rom.
Hope it solves your problem.
Sent from my iPhone using Tapatalk
Firstly, you need to verify that it's a genuine S2. Turn the phone off, take the battery out and post on here EXACTLY what you see on the sticker in the battery compartment.... Just don't post the IMEI number...
Sent from my GT-I9100 using xda app-developers app
Model: GT-I9100
SSN: -I9100GSMH
RATED: 3.7V ------- : 1000 mA
FCC ID: A3LGTI9100
MADE IN KOREA BY SAMSUNG
IMEI: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
S/N: R5XA73828F1
That's all, its seems original, right?
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
hackkpo said:
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
Click to expand...
Click to collapse
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Jeetu said:
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
hackkpo said:
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
Click to expand...
Click to collapse
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Jeetu said:
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Why would i reflash again? i dont get it
hackkpo said:
Why would i reflash again? i dont get it
Click to expand...
Click to collapse
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Jeetu said:
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Click to expand...
Click to collapse
No is not, the cellphone starts normal, and while im using it nothing wear happens, but when i left it the screen goes black and the device reboot itselfs. But now im seeing that doesnt happen anymore, i dont know why.
Still with cyanogenmod rom, i connected the phone to charge the battery, and i saw a tendency of reboots and turnings off while the percentaje comes to 100% and a increasing overheat on the left-top of the phone, i suspect that the problem may be related with the amount of charge from battery and the overheating... Hardware problem?
Well... After all this time my cellphone went through the argentinean official service of samsung and the tech guy told me that he couldn't do anything on my device because he tried installing a lot of samsung official roms and the device was still malfunctioning. So he gave up on it, so i'd tooked it to another service (non official this time) and that guy told me that it may be a non official device, so he wouldnt do nothing on it, because i couldnt get the hardware that possible was malfunctioning. So here im now, with the all money spent for nothing.
My question is, what can i do to know if is or isnt an ORIGINAL samsung device? Knowing that i'll choose how to proceed. Txs!
Hey Everyone,
I am having an issue with my screen turning on randomly on my phone. Its a Verizon Note 2 (hence me posting in this section). I'd like to think I've done some troubleshooting but I want somebody else to tell me that I am not insane.
So far what I've done:
1. Flashed Custom Rom - CM11 in this case. Screen turning on and off is persistent between stock and CM leading me to believe hardware problems.
2. Took phone apart, unplugged power button from motherboard. Booted phone back up and disconnected. With the cable disconnected it still persisted.
3. Taking a page from some other threads on XDA I have tried the key test in CWM. My screen was turning on every 1-2 minutes and right now its been sitting for 15 minutes with no key presses registered (with the cable re-connected).
So with all of that being done I'm assuming its an issue with something that Google is restoring to my phone? Does that sound like a logical conclusion? Before I factory reformat and not have anything restore I just wanted to post up and verify.
As a second question - is there a good way to clear all the internal memory before I do a fresh format of CM11 (if i go that direction tonight?) I still have folders on the internal SD card from my stock install that i would like wiped out.
Thank you all in advance: I love this site. I've been flashing every phone i've owned from the guidance here but very rarely post.
TheDigitalSlacker said:
Hey Everyone,
I am having an issue with my screen turning on randomly on my phone. Its a Verizon Note 2 (hence me posting in this section). I'd like to think I've done some troubleshooting but I want somebody else to tell me that I am not insane.
So far what I've done:
1. Flashed Custom Rom - CM11 in this case. Screen turning on and off is persistent between stock and CM leading me to believe hardware problems.
2. Took phone apart, unplugged power button from motherboard. Booted phone back up and disconnected. With the cable disconnected it still persisted.
3. Taking a page from some other threads on XDA I have tried the key test in CWM. My screen was turning on every 1-2 minutes and right now its been sitting for 15 minutes with no key presses registered (with the cable re-connected).
So with all of that being done I'm assuming its an issue with something that Google is restoring to my phone? Does that sound like a logical conclusion? Before I factory reformat and not have anything restore I just wanted to post up and verify.
As a second question - is there a good way to clear all the internal memory before I do a fresh format of CM11 (if i go that direction tonight?) I still have folders on the internal SD card from my stock install that i would like wiped out.
Thank you all in advance: I love this site. I've been flashing every phone i've owned from the guidance here but very rarely post.
Click to expand...
Click to collapse
To format the internal SD card, reboot into recovery (sounds like you use cwm), go to 'mounts and storage' and wipe 'sdcard' or 'data/media.' I havent used cwm in a while so I cant remember the exact wording.
While in mounts and storage go ahead and wipe 'system' and wipe 'data' as well before installing the new rom. Before installing a new rom you should always wipe system and data.
As far as the screen randomly turning on it does sound logical that it could be google restoring to your phone. Im guessing that you don't see new notifications in the status bar? How long did you let the phone sit after installing a new rom?
Whichever way I doubt it's hardware.
If you format and reinstall dont choose to restore from Google servers. If the problem still persists then there are ways to know what's waking up your phone.
Hälftebyte said:
To format the internal SD card, reboot into recovery (sounds like you use cwm), go to 'mounts and storage' and wipe 'sdcard' or 'data/media.' I havent used cwm in a while so I cant remember the exact wording.
While in mounts and storage go ahead and wipe 'system' and wipe 'data' as well before installing the new rom. Before installing a new rom you should always wipe system and data.
As far as the screen randomly turning on it does sound logical that it could be google restoring to your phone. Im guessing that you don't see new notifications in the status bar? How long did you let the phone sit after installing a new rom?
Whichever way I doubt it's hardware.
If you format and reinstall dont choose to restore from Google servers. If the problem still persists then there are ways to know what's waking up your phone.
Click to expand...
Click to collapse
Thanks,
I'll be doing that today. How can i tell whats waking it up? The wakelock detector i have been using isn't ready for 4.4 yet.
Turns out it was noon walk that was doing it
Sent from my SCH-I605 using xda app-developers app
Haha good. How'd you find out?
Sent from my SCH-I605 using Tapatalk
At 40% battery or below I suddenly lose signal. Doesn't come back on even when toggling airplane mode. Only comes back after a reboot.
Don't know if it's firmware or ROM related. I've tried 7.3.2 - 7.4.6 firmware, still happens. Happens on all the Nougat(haven't tried any other versions not even Miui) ROMs I've tried(NOS, AOSiP, Pure Nexus)
bloodytolits said:
At 40% battery or below I suddenly lose signal. Doesn't come back on even when toggling airplane mode. Only comes back after a reboot.
Don't know if it's firmware or ROM related. I've tried 7.3.2 - 7.4.6 firmware, still happens. Happens on all the Nougat(haven't tried any other versions not even Miui) ROMs I've tried(NOS, AOSiP, Pure Nexus)
Click to expand...
Click to collapse
1) Full wipe system, data, cache, dalvik, internal storage and format with must use type "yes".
2) install firmware and ROM.
kounir said:
1) Full wipe system, data, cache, dalvik, internal storage and format with must use type "yes".
2) install firmware and ROM.
Click to expand...
Click to collapse
I always do that when flashing(I get OCD even though I know some parts aren't necessary sometimes). But problem still exist. Don't know if it's because of auto select network or something. I think there's only 1 time when signal isn't lost for 1 day. I just have to live with one reboot a day.
I'm also facing this issue. This happens every time to me no matter what my battery percentage is, i also flashed all kinds of miui roms even the oldest lollipop roms, but the issue still persist. Rebooting the phone only brings back network for sometime ( 10 minutes approx.). I also tried the same sim card on different phones, and it worked good. Also i have a second 3G sim which works nice, i think the problem is with 4G sims only.
If anyone has any fix please share.. :crying:
I was facing this issue few days back, now it's showing no sim card.
Only way I find to solve this issue is removing sim card, restore miui from fastboot, clean flash rom and insert sim again after first wizard setting