Related
Hello people, I have a rather peculiar issue with my SII
I have had this issue for some time now and really doesnt bother me that much, its just annoying. And its just now that I have bothered writing a post about it.
If Ive run out of battery, I plug my phone into the charger, turn it on while its charging, I get no service, not prompted to input PIN and get the Uknown IMEI\baseband version. But if I let it charge a couple of minutes, unplug the charger and turn it on, everything works fine. Whats going on here?
I think this problem occured after installing one of bmarko's MIUI roms. I have since full wiped and restored stock rom. Upgraded two new official samsung roms as they have been released, currently running XWKI8 unrooted completely stock and the issue still persist.
I have searched around and there are similar cases out there but not really any clear solutions. Theres even a post over at cyanogenmods forum site, but no replies.
As said earlier its not really a big issue for me, not expecting a immediate solution but I would really like to understand the problem if someone has the information since I dont have the technical competence to understand it myself. I obviously havent corrupted or lost anything in my efs folder since its working without the charger, or? Could there be remains of a bug from another rom still in the system causing this?
Any replies would be appreciated, thanks.
Same Problem
Hey FlipTrick,
I got exactly the same problem. Dont remember how it happened exactly, but do remember I didn't do anything exotic. Can't display my IMEI, unknown baseband version and no prompt for my PIN.
I Tried several things:
- Reflashed the advised codeworx kernel using odin.
- ReInstalled CM 7.1 and tried nightly version.
- Reflashed different RADIO ROMS from XDA (goo.gl/TjoaM)
Nothing worked. Does anyone know what the problem might be? Or know what I could try next?
Greetings,
Xianduras
I had this problem once when I used a jig to reset the flash counter. Given the modem (and the IMEI) wasn't showing up in the phone details, I reflashed the modem which fixed it.
Occasionally after a reboot my modem/IMEI details take around 20-30 seconds to appear, but they've never not turned up/left me without service apart from that one occasion.
problem gone?!
Problem seems to be gone, noticed it after flashing Hydrog3n rom. Cant say if thats the solution though, havent tested it for awhile and i've flashed alot of roms
I have a serious issue with both my I9100 devices.
it suddenly freezes and requires reboot. when i do it, it stuck on boot screen (Where the yellow triangle would be if using unofficial firmware)
nothing helps, only wipe data. once I wipe, device loads fine and starts working again.
I tought at first its rom/kernel related, I switched everything and even tried stock rom.
it keeps happening...today, I tried to swap batteries as one got empty, I took the battery out of the stocked-rom device (after turning it off) and then later when i switched it on, it had to be wiped.
same as with my other device.
Anyone has any clue what this is about?
Its became a big issue for me, I cant flash/wipe every few days...
One device is on Neatrom 4.4 lite, the other stock-everything, both 4.1.2
eranyanay said:
I have a serious issue with both my I9100 devices.
it suddenly freezes and requires reboot. when i do it, it stuck on boot screen (Where the yellow triangle would be if using unofficial firmware)
nothing helps, only wipe data. once I wipe, device loads fine and starts working again.
I tought at first its rom/kernel related, I switched everything and even tried stock rom.
it keeps happening...today, I tried to swap batteries as one got empty, I took the battery out of the stocked-rom device (after turning it off) and then later when i switched it on, it had to be wiped.
same as with my other device.
Anyone has any clue what this is about?
Its became a big issue for me, I cant flash/wipe every few days...
One device is on Neatrom 4.4 lite, the other stock-everything, both 4.1.2
Click to expand...
Click to collapse
u can just rewert to stock ICS 4.0.3 firmware on both the phones and check for the issue (whether its firmware related or any hardware issue as such)
thanks for your help,
It did not happen on 403, tough it didnt happen on 4.1.2 for some while either.
what else would you suggest me to test?
eranyanay said:
thanks for your help,
It did not happen on 403, tough it didnt happen on 4.1.2 for some while either.
what else would you suggest me to test?
Click to expand...
Click to collapse
1) with 403 for some time once again to ensure no issues of freezing.
2)then a different 4.1.2 stock/custom rom altogether to check for the same(freezing) issue.
stay for some time on those firmwares and see (may be one or two charge cycles).
3) do not install any mods on top of the firmware, just stay stock and see
One of the devices is already back to 403, while the second one on stock 412
the hardest thing to tell if 403 solves it or not, as it happens occasionally, once in a week or two.
I tried two different stock roms, so that would rule out #2.
The weird thing is that wiping data is enough.
data is separated from the rom itself, yet it causes the entire device not to boot anymore.
Hi guys. It is my first time to run cyanogenmod on my phone. I have the Samsung Galaxy Exhibit 2 4G and I tried to install the CM 11 of jfbs. I did all the backups and I wiped the data and cache and installed the ROM and Gapps. But I rebooted my device and the Cyanogenmod logo appeared with the spinning arrow and it didn't want to stop spinning (or loading if you want). My phone was stuck on logo and the spinning arrow. I forced the phone to turn off and when I rebooted it I worked but after a little time it went back to the logo and the spinning arrow. I re-installed the ROM and Gapps but like before, the logo and the spinning arrow still there until now and it won't even stop and lead me to the lock screen. PLEASE can somebody tell me if it won't work or what is wrong whit it or if it is matter of time, how long should i wait? PLEASE I need to know what is going on and what to do. :crying:
theking1st said:
Hi guys. It is my first time to run cyanogenmod on my phone. I have the Samsung Galaxy Exhibit 2 4G and I tried to install the CM 11 of jfbs. I did all the backups and I wiped the data and cache and installed the ROM and Gapps. But I rebooted my device and the Cyanogenmod logo appeared with the spinning arrow and it didn't want to stop spinning (or loading if you want). My phone was stuck on logo and the spinning arrow. I forced the phone to turn off and when I rebooted it I worked but after a little time it went back to the logo and the spinning arrow. I re-installed the ROM and Gapps but like before, the logo and the spinning arrow still there until now and it won't even stop and lead me to the lock screen. PLEASE can somebody tell me if it won't work or what is wrong whit it or if it is matter of time, how long should i wait? PLEASE I need to know what is going on and what to do. :crying:
Click to expand...
Click to collapse
(as a dev for this phone)
If you could PM me with more details that would be helpful. When i hear that it continues after a reboot(not the first person to have said that) i think its that you are not waiting enough time. That may or may not be the case. I would give it a good 5 min. I have never timed mine but it does seem to me that prior android versions took about 2-3min maybe and for w.e. reason android 4.4(cm-11.0) takes a few more min. Anything over >=10min though id say is too much. In these cases the only things that can really help are logs. Logs are the only way you can show a dev what you are experiencing.
(as a xda member)
Also i would use the device thread not the general android thread, read through the rom thread of the rom you are tryng to install, and a last and final note, I would recommend that anyone that is new to install older more mature roms first. These roms will yield the best experience in most cases. Then once you are familiar you can experiment with other roms/mods etc etc.
cars1189 said:
(as a dev for this phone)
If you could PM me with more details that would be helpful. When i hear that it continues after a reboot(not the first person to have said that) i think its that you are not waiting enough time. That may or may not be the case. I would give it a good 5 min. I have never timed mine but it does seem to me that prior android versions took about 2-3min maybe and for w.e. reason android 4.4(cm-11.0) takes a few more min. Anything over >=10min though id say is too much. In these cases the only things that can really help are logs. Logs are the only way you can show a dev what you are experiencing.
(as a xda member)
Also i would use the device thread not the general android thread, read through the rom thread of the rom you are tryng to install, and a last and final note, I would recommend that anyone that is new to install older more mature roms first. These roms will yield the best experience in most cases. Then once you are familiar you can experiment with other roms/mods etc etc.
Click to expand...
Click to collapse
Thank you @cars1189 for your answer. I used the device thread to do it but the problem is, I let it spinning for more than 5 hours. I have flashed many roms in my phone since i had it (more than 10 times or more) and i know that it does not take more than 10 mins max to install. But don't worry after that i went back and restored my previous CM 9 rom and right now i'm on the CM 11 build of 1-29-14 of your CM mass thread. It works fine, not at 100% but it doesn't drain my battery like your CM 10.2 build of 1-11-14 and it is almost stable. I will try tonight to use your ADC kernel with the jfbs CM 11 rom that first didn't work for me because I saw in your thread that this kernel may help it to load and install without the spinning issue. So i will give it a shoot. But anyways thanks for your answer and it means a lot to me really. :good:
GOOD
@cars1189 , I'm actually running the 6-18-14 build of CM11 and as far as it goes, i'm not encountering any major issue at the moment. The theme engine is working fine for me and battery life is great for my usage. I use this build as a daily driver, and it does a great job. Calls, texts, data, wifi, Bluetooth and GPS are all working. I had issues before with the amount of RAM available, but now that it has 375MB of RAM, it is more snappy. Just :good: Thank you for your work on our to make our phone still valuable today!! THANKS MAN!!!!!!
Hey everyone. redoing my thread now that we have tried alot of solutions, hopefully someone has a vague idea of what we can do to my phone lol.
So then, my phone (redmi note 3 snapdragon) refuses to go into deep sleep no matter what combination I've tried.
Tried Combos
1. RR+ radon and agni
2. Miui 8 stable and dev preview (7.1.5 and 8.1.1.0)+ stock, radon, and neon kernel (flashing using miflash with unlocked bootloader official)
3. Cm13 latest nightly+ radon, stock, and agni
4. Nitrogen os+ nagato kernel (current rom)
All combinations we're tried with clean installs (factory data, system,cache and internal storage)
Hardware methods tried
1. Physically disconnecting fingerprint sensor (goodix)
now then, with wakelock detector, we can see im troubled with a 99% awake time, along with 100,00's of event wakelocks over 6hours, now event wakelocks deal with the actual hardware of the phone from what i've seen, which makes little sense to me because the screenshot i am attaching was just over an entire night of not touching the phone. so why it has any activity is bizarre to me. so heres what we have tried so far on my previous thread.
Tried methods of fixing event wakelocks
1. Greenify, force doze, wakelock blocker and blocking everything in frustration. deep sleep battery saver.
2. physically deleting events one by one (going into dev/input/eventx (x being wakelocks 1-10) after deleting some my display eventually stopped working, most likely because i just deleted the event that controls the lcd i assume. rebooting fixed the problem and remade the events in their directory so no harm done.
3. removing zram usage figuring it was a thrashing problem (saw a thread in the hd desire of the same issue. didnt help sadly.
4. flashing modem in radon thread, ended up making my phones earpiece not work for calls and still had the wakelocks.
5. disabling gps, along with auto brightness and auto rotate
so then if anyone needs any other information just let me know, currently using an iPhone for the time being so im desperate lol. but still id rather fix and find the problem then go for returning the phone. better to solve a problem for future people in my shoes then just thrust it away is how i see it. also someone bug the strix and darkstrix about this maybe they know the solution. anyway thanks for reading and i hope we can fix my phone soon
^Update^ now using epic rom 7.1.12 from the xda thread, still got wakelocks on stock without any other apps.
I have same problem in all versions of stock MIUI Rom. I too tried all sorts of combination but the problem remains. Finally I'm using RR Rom 5.7.4 (20161113 build) + radon Kernel. My deep sleep problem have been solved (though not 100%). Now my phone looses very little battery in standby time like 1-2% over a night. Before RR Rom I tried many custom Rom but had same problem. If you have not tried the ROM (RR Remix 20161113) I've mentioned above give it a try. Best Of Luck.
Thanks rj I'll install and post logs after work. Fingers crossed that it fixes my problem.
use the rom android 6.0.1 with module powernap , u can fix it !!
http://repo.xposed.info/module/net.jzhang.powernap
Small update: testing stamina mod currently with xposed. ressurection remix will be next only because xposed seemed a bit easier lol
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Then once try nexus rom i am getting good battery life in this rom too.
rjrulz007 said:
Then once try nexus rom i am getting good battery life in this rom too.
Click to expand...
Click to collapse
surer rj which one?
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
That happens to me when background data enabled . when i disable backround data through data usage settings , the battery backup gets better, but sure my social apps wont sync.
It seems the wakelock come from android system itself , go check logcat and you will get messages like "ANDR_PERF_RESOURCES FAILED TO APPLY PERFORMANCE" , the likes of "decided to move IRQ from cpu0 to cpu1" , and the likes of "FPC listener : waiting..." , thats all that i notice and thats happening every single milisecond on every MM roms i have tried so far....
Well when i used miui 7 LL global didnt get that much messages on logcat , but its LL ...
I guess the problem is related to source code , i dont know .
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
D4xel said:
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
Click to expand...
Click to collapse
yes sir still nothing
rohit4kk said:
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
Click to expand...
Click to collapse
hey dont worry man you'll be the first when we find an answer lol
Zaccary said:
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Click to expand...
Click to collapse
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
deltatux said:
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
Click to expand...
Click to collapse
thanks for the tip but we are running on airplane mode only at this point just to make sure we don't have more things to worry about battery drain. i appreciate the information though ^_^
Mine kenzo, tried all miui version, always the same.
sbor-si said:
Mine kenzo, tried all miui version, always the same.
Click to expand...
Click to collapse
I'm not alone!!!
Hey hopefully we find an answer buddy
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
sbor-si said:
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
Click to expand...
Click to collapse
i believe last time i tried 7.3.2.0 it gave me constant reboots and lagged quite a bit. but i also heard it was the best for battery so i can try flashing through miflash again after work. im also going to be trying this rom here https://forum.xda-developers.com/re...nzo-lldlm18-1-3m866beta-real-factory-t3375250. since it uses edl mode instead of fastboot so hey maybe that will knock something lose?
Well, right now I'm trying to get it working - without luck. I can flash 7.3.2. with miflash via edl without troubles, phone started normaly, all seems good, until "No service" for gsm signal. Bad luck. I think that modem version from that old flash is not compatible with hardware.
But it looks so good - Android takes 20% and Android system 6%...
Currently running the latest Pixel Experience ROM and it's solid overall.
But, I have experienced a super weird bug or glitch concerning the wifi and how it connects.
On the stock MIUI setup WiFi was solid and stable, didn't even have to give it a second thought. However, after rooting and ROMs the WiFi capabilities are seriously weird.
On both LineageOS and PixelExperience, whenever I try to to connect to my WiFi network, the phone takes down the whole network. And I mean the whole thing. It just tanks the network into restarting and I have no idea why. It should not happen, but it does.
And to actually connect the WiFi, I need to turn it on and off at least 3 times to get it to connect. But once it does connect it stays connected. It's pretty annoying when I go out and come home and the phone has to jump through these hoops just to get WiFi working properly.
I don't think that it has to do with the Pixel Experience ROM because I've updated it twice now and the problem still persists, so I'm just left thinking that maybe it has something to do with the vendor firmware that I used at the time when I was getting things set up.
Any thoughts? Would be a huge help!
thevietmonk said:
Currently running the latest Pixel Experience ROM and it's solid overall.
But, I have experienced a super weird bug or glitch concerning the wifi and how it connects.
On the stock MIUI setup WiFi was solid and stable, didn't even have to give it a second thought. However, after rooting and ROMs the WiFi capabilities are seriously weird.
On both LineageOS and PixelExperience, whenever I try to to connect to my WiFi network, the phone takes down the whole network. And I mean the whole thing. It just tanks the network into restarting and I have no idea why. It should not happen, but it does.
And to actually connect the WiFi, I need to turn it on and off at least 3 times to get it to connect. But once it does connect it stays connected. It's pretty annoying when I go out and come home and the phone has to jump through these hoops just to get WiFi working properly.
I don't think that it has to do with the Pixel Experience ROM because I've updated it twice now and the problem still persists, so I'm just left thinking that maybe it has something to do with the vendor firmware that I used at the time when I was getting things set up.
Any thoughts? Would be a huge help!
Click to expand...
Click to collapse
Yes, most likely a Vendor Firmware issue. Try the latest.
tnsmani said:
Yes, most likely a Vendor Firmware issue. Try the latest.
Click to expand...
Click to collapse
Sounds good!
But quick questions, when flashing the new vendor firmware do I have to wipe anything? Or can I just download it and flash? And will flashing the new vendor firmware wipe my phone?
Thanks for the help again!
thevietmonk said:
Sounds good!
But quick questions, when flashing the new vendor firmware do I have to wipe anything? Or can I just download it and flash? And will flashing the new vendor firmware wipe my phone?
Thanks for the help again!
Click to expand...
Click to collapse
Just download and flash..no need to wipe anything. It will not delete your data too..
Edit: if your data not encrypted, you'll need to flash dfe (disable force encryption) as flashing vendor will encrypt your data.