I have decided to start new thread for all who suffer from random soft-reboots while using CAF based ROMs.
There are two reasons for that:
1. I don't want to spam single ROM threads since it seems to be a general issue of CAF ROMs (mainly for D802 users)
2. I want to gather all knowledge in one place and figure out a root cause and solution (or workaround).
I was trying several CAF based ROMs and I'm delighted by their responsiveness. But unfortunately I'm suffering from random reboots. I'm not able to get to root cause of this issue. Initially I thought this is because of some app, or by failure while flashing ROM. Issue is hard to diagnose since phone may be fully-functional even for couple of days. That is why for several times I thought the issue is gone....
Now I am heading more towards modem issue - weak signal and changing BTSes. When I'm on countryside, my phone is able survive couple of days without a single reboot. When I move back to the city (and move around for a while) reboots are becoming more frequent, especially when I'm in the areas with weak signal. I have even got some "favorite" places, when possibility of getting soft-reboot is higher than usual.
Please describe your observations of this issue, providing:
Phone variant: D802
ROM: SlimSaber 0.4
Kernel: provided with ROM
Bootstack: Drgravy's loki LP bootstack from here
Modem (baseband): provided with bootstack (M8974A-AAAANAZM-1.0.190128)
Logs with approximated crash time: I'll deliver mine when I'll catch first soft-reboot after hard reset. If you're not sure how to get logs from crash, please use this app.
Observations:
1. Reboots get more frequent when changing location, visiting areas with lower signal.
Suggested solutions/workarounds:
1. Change modem - DOESN'T WORK FOR ME
Tested on the following modems:
- included in Drgravy's LP bootstack
- cust 30A SG by samuele94(Lg g2 Original Modding Italy G+ Community)
- Modem_D802-30B_EUROPE-OPEN
2. Play with Location/APN settings - PARTIALLY WORKING
Please refer to this post.
After couple days of testing with Location set to Device only I have face one or two reboots. Acceptable for me. Probably switching to Battery savings will remove reboots completely (as reported by others)
3. Disable MPDecision hotplug - DOESN'T WORK FOR ME
Doesn't work and for some kernels inhibits deep sleep.
4. Try to flash kernel from this post: WAITING FOR REPORTS
I just have to find my logs for the tsunamical build
Phone variant: D802
ROM: Euphoria by dr87
Kernel: provided with ROM
Bootstack: From OP by Rashed97 here
Modem: provided with bootstack (M8974A-AAAANAZM-1.0.190128)
Several logs in rar View attachment dr87.rar
Phone variant: D802
ROM: Euphoria by tsunamical
Kernel: provided with ROM
Bootstack: Rashed97 from OP here
Modem: provided with bootstack (M8974A-AAAANAZM-1.0.190128)
Looking for logs
Phone variant: D802
ROM: SlimLP by arcadinal
Kernel: provided with ROM
Bootstack: Drgravy's bump LP bootstack from here
Modem: provided with bootstack (M8974A-AAAANAZM-1.0.190128)
View attachment 2015-07-14_21.18.zip
slaav said:
When I'm on countryside, my phone is able survive couple of days without a single reboot. When I move back to the city (and move around for a while) reboots are becoming more frequent, especially when I'm in the areas with weak signal.
Click to expand...
Click to collapse
I work as a truckdriver and move around a lot. I can confirm that my phone is more stable when I am stationary than driving around. There is a lot of RIL errors in my logs.
I have been speculating to myself that it might have something to do with switching networks from wi-fi to cellular or the other direction. I ride the train to and from work, and the local cable company has free wi-fi at most of the train stations. So as we approach and leave each of the stations, my phone joins and leaves the wi-fi. I started to notice that the phone, just sitting on my lap asleep without me touching it, would suddenly turn on showing the boot animation. It would do this two or three times in a 45-minute trip. I also have the "avoid weak wi-fi" setting turned on, and the other times I've noticed the reboot have been when I'm in a weak signal area (either wi-fi or cellular, like the back of a store).
I got the soft reboots on tsunamical's Euphoria 6/10 build (I never updated to the later ones because people were still reporting the soft reboots). I switched to dr87's Euphoria build this past weekend to see if it was any better, but I was getting them there too. Which at least suggests it's not a kernel problem, maybe, since that's the main difference between them? Anyway, I was just about to start collecting logs and then...
All of a sudden, yesterday morning on the train was the last soft reboot. It didn't reboot once on the train ride home, or the train ride in this morning. Oddly, CPU Spy thinks the phone has been up for about 9 hours LESS than GSAM Battery Monitor does (usually both would only show time since the last soft reboot). So SOMETHING changed around 4pm US Eastern time yesterday, but I'm not sure what. I thought it might have been Google Play services, but that seems to have not been updated since June 18th. But, a few days ago, Google Play services had hundreds of wakelocks. Now? It has 7. Just 7.
I have no idea what all this means, but offer it for what it's worth (or not worth).
Phone variant: D800
ROM: Euphoria by dr87 (also ran tsunamical's)
Kernel: provided with ROM
Bootstack: Rashed97 from OP
Modem: provided with bootstack (M8974A-AAAANAZM-1.0.190128)
i'm waiting more info but if it's gps i might give a look otherwise can someone test that please http://forum.xda-developers.com/lg-g2/general/fix-gps-agps-best-performance-config-t3098819
Haven't we already confirmed it was an issue with the modem panicking?
tsunamical said:
Haven't we already confirmed it was an issue with the modem panicking?
Click to expand...
Click to collapse
I'm sorry if that topic was already covered. I (and, looking through several threads, bunch of oher users) was not able to find that conclusion.
My intention was to move the discussion scattered all over the development threads into one place. I think users without reboot issue have already enough reading about it
I have this issue after installing build 2015-07-02 BlissPop v3.6 by electrikjesus.
Before this I had reboots whrn data changes from wifi to LTE or the reverse way. But now the reboots are random.
Phone variant: D805
ROM: BlissPop by electrikjesus (2015-07-06 build)
Kernel: provided with ROM
Bootstack: Drgravy's bump LP bootstack
Modem: last d805 modem (M8974A-AAAANAZM-1.0.190036)
Ramres said:
I have this issue after installing build 2015-07-02 BlissPop v3.6 by electrikjesus.
Before this I had reboots whrn data changes from wifi to LTE or the reverse way. But now the reboots are random.
Being on Euphoria I don't get any issues like that. Model D802 plus loki lp bootstack. Perhaps bootstack is the issue? I tried others ROM too and have never experienced any reboots. Om Euphoria just several lags possibly having something to do with thermal throttling when phone being heavily used.
Click to expand...
Click to collapse
Thanks for this thread.
802, BlissRom (just flashed today's build clean)
Loki bump bootstack.
Mine will reboot on:
Phone call (random times, sometimes 1 min in, sometimes 10mins in)
Almost always when at station (very low signal) AND when starting music through headphones (uninstalled native music player and using Google Play music now, testing)
Sync BT with car, play music, reboot (only once out of 5-6 times, rebooted half way through song) - was driving out of underground carpark so no signal
about 50% of the time, it will reboot and then 'optimize apps', it's like an auto wipe dalvik cache!! (which is crap since if you want to phone back the person, you have to wait 15-20mins while apps optimize....)
Played music through headphones at home for hours, no reboots. So definitely related to signal/modem etc.
Will post more when testing done this week
Well I need a kmsg after a reboot (pull it from twrp) a modem log please
Edit I don't have any random reboot (bliss d802)
Sent from my Nexus 6 using Tapatalk
genesixxbf3 said:
Well I need a kmsg after a reboot (pull it from twrp) a modem log please
Edit I don't have any random reboot (bliss d802)
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks genesixxbf3
Attached Syslog bunch of files - not sure how useful this is as the phone dalvik wiped, then launcher loaded, then 30 seconds later rebooted itself. Only then could I run syslog
The catlog dump was recording when I was on the way home yesterday, and phone rebooted (was on train so likely to be switching towers). Had headphones in and playing music.
I'll do the TWRP log when it reboots tmr.
genesixxbf3 said:
Well I need a kmsg after a reboot (pull it from twrp) a modem log please
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You will find that in my post. The second in this thread.
Solution?
Yesterday I did something no tester should do in life - changed two settings at once
I have:
changed Location settings to Device only - thanks to LooseSeal
changed APN settings - I don't know why, but I have changed APN (from the one I was using for years to my provider's secondary APN).
As a result:
my phone works for 19 hours without a single reboot. Usually I should have at least two of them - way back from work in the afternoon and to work in the morning. Not mentioning several at my home - I have, by purpose, put the phone in "low signal area location" of my flat where usually reboots are frequent. :good:
when leaving WiFi area my phone connects to LTE network much faster than before. :good:
If my phone continue to run reboot-free, I'll change back Location setting to High accuracy and report after a day or two.
Update:
After 21 hours of testing (no single reboot during that time) I have changed Location settings back to High accuracy to verify if APN change is enough to get rid of reboots.
After 27 hours of testing still nothing. Now the real test - trip home from work.
Unfortunately - three soft-reboots with High accuracy. Changed back to Device only and restarted.
After couple days of testing I've got two soft-reboots - maybe not related but they occurred one after another while watching something on YouTube. For me phone is stable enough for now. Moreover, probably after following suggestion of LooseSeal - reboots will stop completely after changing Location settings to Battery Save
Phone did not reboot at station today. Played music, surfed web etc... lol... hmm...
Did you change anything?
Flashed latest BlissROM yesterday.
The Banks GAPPS didn't install Play store (weird) so I got the APK and also the latest Google Services and installed those manually. All my apps are the same (Titanium restored)... test again tmr see if it doesn't reboot
My solutions for D802 (but only theoretical because I don't have any reboots - currently 4 days uptime in CM 12.1 ROM) :
Try Nice & Fruity 0.25 CAF Kernel (or latest version e.g. 0.30) with patched panic handler (I will build in next week another version with more possible fixes)
Nice & Fruity 0.30-PAN!C CAF Kernel with patches from previous versions + disabled LG panic handler and watchdog v2
Flash KK modem (logcat will throw rild errors, but signal will work - it's a temp solution)
Remove/update Xposed
Please report back if something fixed those weird reboots
Best wishes !
zg85 said:
My solutions (but only theoretical because I don't have any reboots - currently 4 days uptime) :
Try Nice & Fruity 0.25 CAF Kernel with patched panic handler (I will build in next week another version with more possible fixes)
Flash KK modem (logcat will throw rild errors, but signal will work - it's a temp solution)
Please report back if something fixed those weird reboots
Best wishes !
Click to expand...
Click to collapse
Nice for the panic handler cause watchdog panic muck up my kernel
Sent from my LG-D802 using Tapatalk
The only thing I had to do to completely stop reboots for a few days now was to set GPS to device only instead of high accuracy.
Haven't had one reboot and the battery life has basically been twice as good then before
Related
I updated my phone to a DeathStalker (MF9?) ROM and I have two constant issues:
1. I can no longer update my PRL, Profile or Firmware, etc. It keeps telling me my session is in progress and to try again later.
2. Occasionally my phone randomly reboots.
3. When I click the power button to wake the phone the phone goes into sleep of death forcing me to reboot or it doesn't wake and reboots on its own.
No idea what's causing these issues or how to fix them. I updated to Deathstalker from an old (June 2013) ROM and think it might have to do with firmware or something
Laos101 said:
I updated my phone to a DeathStalker (MF9?) ROM and I have two constant issues:
1. I can no longer update my PRL, Profile or Firmware, etc. It keeps telling me my session is in progress and to try again later.
2. Occasionally my phone randomly reboots.
3. When I click the power button to wake the phone the phone goes into sleep of death forcing me to reboot or it doesn't wake and reboots on its own.
No idea what's causing these issues or how to fix them. I updated to Deathstalker from an old (June 2013) ROM and think it might have to do with firmware or something
Click to expand...
Click to collapse
could just be a bad DL try to dl the rom again and do a clean wipe and reflash.....if the issue persists try a different rom to see if its rom related (also there have been alot of issues with MF9 since its release)
Laos101 said:
I updated my phone to a DeathStalker (MF9?) ROM and I have two constant issues:
1. I can no longer update my PRL, Profile or Firmware, etc. It keeps telling me my session is in progress and to try again later.
2. Occasionally my phone randomly reboots.
3. When I click the power button to wake the phone the phone goes into sleep of death forcing me to reboot or it doesn't wake and reboots on its own.
No idea what's causing these issues or how to fix them. I updated to Deathstalker from an old (June 2013) ROM and think it might have to do with firmware or something
Click to expand...
Click to collapse
You should literally ask this in the thread. You will get more help there. But if im not mistaken the developers for deathstalker took out the function to update prl and profile and also the fact that is "almost" a rom ported to our device it wouldnt have that function. Also it the reboots and death sleep could be kernel related.
ROMANTiC KiD said:
You should literally ask this in the thread. You will get more help there. But if im not mistaken the developers for deathstalker took out the function to update prl and profile and also the fact that is "almost" a rom ported to our device it wouldnt have that function. Also it the reboots and death sleep could be kernel related.
Click to expand...
Click to collapse
Right, so this issue is not mutually exclusive to any ROM. All recent MF9 / MDL ROMs I have tried (3 in total) have this issue and so on. I've made posts about this but they sadly went unanswered
Not sure if PRL was disabled by that dev but it's a possibility
Kernel is always whatever is thrown into the ROM so I'm not sure how to proceed and nobody else appears to be having these issues.
Laos101 said:
Right, so this issue is not mutually exclusive to any ROM. All recent MF9 / MDL ROMs I have tried (3 in total) have this issue and so on. I've made posts about this but they sadly went unanswered
Not sure if PRL was disabled by that dev but it's a possibility
Kernel is always whatever is thrown into the ROM so I'm not sure how to proceed and nobody else appears to be having these issues.
Click to expand...
Click to collapse
Well that this happen when your running pure stock? If it does could be hardware problem.
Well you can just download any kernel of your choice in the original development. And just flash but make sure you make a backup and chose the right kernel. Well thats because phone handle kernels differently. It wont be the same for each phone. Just like us we wont have the same experience on each same event or changes. Get me?
MF9 has nothing to do with it. MF9 works great and updates PRL as it should. If it doesn't work in the ROM you are using than its the ROM. Usually you will find the best help for a rom related problem in the rom thread. I see you have plenty of posts to post in the development section so I would start there.
Q&A for [ROM][4.4.4]VanirAOSP[OFFICIAL][Samsung X Cover 2-GT-S7710]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
hi , installed this rom but i still haven't network connection
Double boot when starting phone
Hello all together.
Yesterday I flashed the latest rom on my skomer.
So far everything runs smooth but I recognized one weird thing.
During boot (doesn't matter if a warm or cold start), the phone boots twice.
Means I see the Pin entry screen and after approx. 15s I see the boot animation again.
It does not matter if I enter the pin or not, it boots a second time at all.
After the second boot everything is OK.
This was a clean flash from theboegls prerooted image with normal pa gapps flashed.
Does anyone have a solution for this issue!
Thanks a lot,
Kubunter
Just installed the new nightly(4.4.4.101014) Everything is running smooth. Just wondering if there is a radio for android 4.4.4 and how do i get it if there is?
---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------
ManuelBiancolilla said:
hi , installed this rom but i still haven't network connection
Click to expand...
Click to collapse
I read the forum and tried this code and it worked for me.
run this code in your terminal if you cant find terminal get if from playstore using wifi.
adb shell
su
find /efs/|while read s; do chown radio:system $s; done;
find /modemfs/|while read s; do chown radio:system $s; done;
chmod -R 777 /efs/
chmod -R 777 /modemfs/
reboot
After reboot your mobile data should be working
Camera not working
Thank you for your great work, hopefully devs are reading this subthread, too.
It would be nice, if following message would be referred on the first message, since many people have issues with network. I managed only to find all the information by very inconvenient googling:
http://forum.xda-developers.com/showpost.php?p=55354795&postcount=414
This post is the Theboegl's relevant one:
http://forum.xda-developers.com/show...3&postcount=43
After the newest nightly, camera stopped working. I will downgrade, but here are some details:
Model:
GT-S7710
Incremental version:
eng.nuclearmistake_20141012.042853
Running apps:
Nothing extraordinary
Exception class name:
java.lang.NullPointerException
Source file:
PhotoModule.java
Source Method:
initializeFocusManager
Line number:
1997
Start trace:
PhotoModule.java: 1997, 1835, 96 and 234
Cleaned cache+camera data. I was using SIM-card as my memory.
ManuelBiancolilla said:
hi , installed this rom but i still haven't network connection
Click to expand...
Click to collapse
Did you use the right clockworkmod mentioned on the main post? Also your firmware might be too new, therefore flashing this one might help:
http://forum.xda-developers.com/showpost.php?p=40232503&postcount=43]
If I got it right it must be
- install odin and get cwm on pc
- get supersu and cm on your sd card
- reboot in download mode
- flash cwm on phone
- reboot in Recovery
- well i think you can backup already
- root with supersu
- reboot in Recovery
- wipe data/factory
- install
- reboot
I use 1010114
wifi and camera work here, but sim card seems not to be accepted
good use of hardware buttons after reflashing (this had issues before)
[did not install GApps, but that should not be a problem..?]
tried 10.2 from flxo and had the same problem with SIM
Double Boot
Hello all together,
I have a logcat of the problem, saved at pastebin.
As I´m a new user, I´m not allowed to post a outside link.
Is it possible that I will send someone who is able to post a link a PM?
The second boot happens around 22:44:54 o´clock
Something with a android process seems to be wrong.
Is anyone able to help?
Thanks a lot,
Kubunter
Android Lollipop?
Pushed fix for streaming YouTube should now work next nightly. Downloading source now to build recovery image. Thanks for waiting. I will try to solve the problems we have but I can't guarantee anything due to lack of device. I'm going to discontinue my work for ste devices soon. As long as it builds I will try my best to keep supporting them but fixing problems etc I can no longer continue.
Click to expand...
Click to collapse
@Unjustified Dev, will you made Android 5.0 for xcover 2? (Because you discontinue development)
andrew551 said:
@Unjustified Dev, will you made Android 5.0 for xcover 2? (Because you discontinue development)
Click to expand...
Click to collapse
There are still STE developers and I'm sure this one will get lollipop working if he can't I doubt we will see it , but lollipop might be a large merge and roms might have to rebase or start from scratch porting hardware workarounds and eventually bring back features.
intermittent network signal
Guys please help. I tried this ROM and it looks great but I'm loosing network signal almost every time I'm starting up navigation (Sygic) and I use it a lot. I don't loose it immediately, sometimes after a few minutes, sometimes after 20 min. but the signal triangle finally goes black and doesn't come back after switching off navigation. This makes it unusable to me. I've seen people reporting problems with network signal so I guess it's not the app. issue. Sometimes it looks like I just loose data transfer (it shows no internet) but the signal bar shows that I have network. Some other time I was not moving at all but the signal bar was going up and down from max. to min. within 3 sek. After few minutes it stabilized. Something seems to be wrong with the antenna or modem, whatever is responsible for network signal.
And another thing, that looks to be related, I don't have any arrows and network type sign (2G/3G) showing if I do or don't have internet connection.
There were some posts talking about a fix for network problem by typing some commands somewhere but could someone explain it step by step how to apply it, if it is a working fix.
Thanks!
After a reboot the home button doesn't work until I enter my pin code, which comes like half an hour after boot! How do I fix it and does anyone else have this problem!?
I was about to throw this piece of **** phone away but i gave it a last chance with Vanir. It took me nearly 2 hours to flash the Rom , but i got it working.
First of I want to thank the dev for the work, I realy apreciate it. You managed to make this phone usable again, I hate Samsung so much for this crap Software they used for the Xcover2.
After using Vanir for one week (using not testing), here is what is not working for me:
-maximum volume for every call
-stock photo app crashes
-Location is very inaccurate, my guess is the cell tower fix is working and the GPS is not
-sometimes i cant shut off the phone, it freezes and i have to pull the battery
-phone is sometimes not going to sleep mode, i have to restart it
Everything else is working perfectly, this is thousand times better then the Samsung bull****. Oh, my carrier is Telekom(Germany).
No radio/SIM with GT-7710 XCover 2 on CM11
The forum forces me to open a new thread, apologies.
I gave the Vanir Skomer 4.4.4.101714 nightly a try but my broadband (S7710XXAND2)/IMEI is gone after reboot. Big difference to most reports I've read is that once I return to stock ROM all is fine again. In other words: the SIM was not damaged. Also the chmod/chown and move-files-from-stock trick doesn't improve anything. No idea what else I should try. I'm currently back on stock Android.
This is what I've done:
- Use Odin 3.09 to apply 20140112_cwm-6.0.4.6_skomer_fixed.tar.md5
- Boot into CWM
- Update to CWM 6.0.4.7 via cwm_skomer_test2.zip
- Wipe/Factory + Dalvik reset
- Install vanir_skomer_4.4.4.101714.zip (also tried 20131231_cm_11.0_skomer-ota-eng.flx.zip)
- Install pa_gapps-modular-pico-4.4.4-20141019-signed.zip
- Wipe/Factory + Dalvik reset
+ Copied {efs,modemfs} from stock to vanir (removed vanir's folder contents before)
+ Fixed file perms to 666, folders to 777, owner to radio:system
I couldn't find TWRP for Skomer or a more recent clockwork recovery. Just mentioning this because I've read a post that mentioned recovery is responsible for setting radio related stuff.
Ideas?
Network connection doest work for me to. I like this rom too and like to be it get worked! (Y)
Never mind, fixed my radio issue. See http://forum.xda-developers.com/showpost.php?p=56293409&postcount=37
vanir_skomer_4.4.4.101714
I got that one and currently it's syncing but I have no mobile networks. I'm from Finland and I'd like to know what data I should post to help fix it. (I could recompile and all if I get instructions)
__
Your's Mikko A. Liukkonen
Kiil said:
After the newest nightly, camera stopped working. I will downgrade, but here are some details:]
Click to expand...
Click to collapse
Just wanted to confirm with my Vanir nightly of 101714, my camera app crashes too. No problems with radio or networking though.
Cant call, says my phone is currently airplane mode
hello, just installed the latest (vanir_skomer_4.4.4.102814) and now my phone can't find network and says that airplane mode is on when i try to call. Airplane mode button says it's off and kills the bt and wifi if i turn it on, aka goes to real airplane mode.
Fix for this would be more than welcome.
itsesaatana said:
hello, just installed the latest (vanir_skomer_4.4.4.102814) and now my phone can't find network and says that airplane mode is on when i try to call. Airplane mode button says it's off and kills the bt and wifi if i turn it on, aka goes to real airplane mode.
Fix for this would be more than welcome.
Click to expand...
Click to collapse
What's the latest stock update because we are having incompatible installation due to my kernel being based on older release and blobs
Unjustified Dev said:
What's the latest stock update because we are having incompatible installation due to my kernel being based on older release and blobs
Click to expand...
Click to collapse
What do you mean by stock update?
Edit:
Seems like it's working again, it woke up after an hour. Sorry for the trouble.
As you guys know, MM has started rolling out to the International Model D855!
I've been on MM for 3 days and quite satisfied with the update! Rom's seems faster and snappier, no more micro lag, juice seems to be better than LP tho... What you guys think? To all Lions, Share your thoughts and comments here! Cheers All!!!
Having problem flashing MM?
Use this method:
Reboot to twrp
2. Full wipe (data, internal card, system, cache, delvik cache, format data) All zip move to external card for a clean flash
3. Flash V2 zip - robalm's thread
4. Flash boot zip - autoprime's thread
5. Flash https://mega.nz/#!gxtwVBwZ!41S8Woy2y...HhK4gcGooK7OIo permissive zip (most important part don't forget to flash this)
6. Flash betasupersu 2.52 https://mega.nz/#!F8E02RyC!XeJhx4QZH...bVd14ccRYHbNKg ( no other version worked only this version worked)
7. Flash sharpening mod 3.5 and reboot system
To me this method works 100%
I've tried on 5 of my friend's G3 and all without fail!
4G ,Titanium and ext card works flawlessly
Reserved
Singaporean user here, so far it's been fantastic on stock marshmallow. With 21c modem there's no problem when it comes to connectivity (I'm on Singtel and I get 4G just like on Lollipop). Battery life much better than lollipop (average about 3.5-4h SOT compared to 2.5-3h on lollipop).
Here's a features review I did for the new stock MM
oceangreen said:
As you guys know, MM has started rolling out to the International Model D855!
I've been on MM for 3 days and quite satisfied with the update! Rom's seems faster and snappier, no more micro lag, juice seems to be better than LP tho... What you guys think? To all Lions, Share your thoughts and comments here! Cheers All!!!
Click to expand...
Click to collapse
Sorry to ask but really all International Model D855 got MM update or only Poland ? Please confirm.
OTA in Poland for D855 only
krk2krk said:
Sorry to ask but really all International Model D855 got MM update or only Poland ? Please confirm.
Click to expand...
Click to collapse
currently only Poland has update via OTA or LG PC Suite. However, there are zip files and KDZ files available that you can flash on any D855.
oceangreen said:
Having problem flashing MM?
5. Flash https://mega.nz/#!gxtwVBwZ!41S8Woy2y...HhK4gcGooK7OIo permissive zip (most important part don't forget to flash this)
6. Flash betasupersu 2.52 https://mega.nz/#!F8E02RyC!XeJhx4QZH...bVd14ccRYHbNKg ( no other version worked only this version worked)
7. Flash sharpening mod 3.5 and reboot system
Click to expand...
Click to collapse
Hi oceangreen,
Saw this thread late. Black screen, Red & Blue LED flashing problem after following autoprime's thread.
Some questions:
Step 5 - autoprime didn't have this! However, your Megasync link requires decryption key? Can u provide?
Step 6 - Is this the same as autoprime's SuperSU 2.52?
Step 7 - Is this the correct link to the sharpening mod 3.5 (http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648)? autoprime did not provide this! If I have no issues with the sharpening issue, can I skip this?
Thks in advance.
Is this still MM if use 21c modem ?
Preter said:
Hi oceangreen,
Saw this thread late. Black screen, Red & Blue LED flashing problem after following autoprime's thread.
Some questions:
Step 5 - autoprime didn't have this! However, your Megasync link requires decryption key? Can u provide?
Step 6 - Is this the same as autoprime's SuperSU 2.52?
Step 7 - Is this the correct link to the sharpening mod 3.5 (http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648)? autoprime did not provide this! If I have no issues with the sharpening issue, can I skip this?
Thks in advance.
Click to expand...
Click to collapse
This thread really need updating - or at least a sticky note to say that the better thread to use is http://forum.xda-developers.com/lg-g3/development/stock-t2961073/page252
Answer to some of my own questions:
Here are the mega links without requiring key
https://mega.nz/#!gwFhDAIb!ElPjTOntE...nGotozKUyypoAU
https://mega.nz/#!M5tkgDoR!eWGHs5O29...7uP6fiW-8pOwbw
you don't need sharpening mod if you use v2.52 see http://forum.xda-developers.com/lg-g...ables-t3282012. with this method it's simple & root sticks
The SuperSU 2.52 is the same based on the hash files.
fOxunO said:
Is this still MM if use 21c modem ?
Click to expand...
Click to collapse
yes, modem only affects cellular and things like that. The rom is still MM
Does it have volte with sg telco
Followed the flashing guide to the letter - this V2 rom is great - but for only about 3 days.
After around the 3 day mark, the error message will flash "SIM card removed The mobile network will be unavailable until you restart with a valid SIM card inserted."
The phone will reboot within 10 seconds (even if you go to airplane mode immediately). It rebooted repeatedly first time it happened.
Did a complete nuke wipe, flashed again. Same thing - at the 3 day mark - the Singtel SIM will show the same error and reboot. After that, SIM not usable at all. All telco signals (Singtel) will be gone. No phone, SMS, let alone data of any sort.
Think it is the problem with the modem.
http://forum.xda-developers.com/lg-g3/development/stock-t2961073
(Download v2 (modem from v21c) -> https://mega.nz/#!OIlwGLKS!LlcNIImHK...EzSt_ikHlWj3yY)
Tried flashing 21A, 21B, autoprime's hybrid modem. Doesn't work. Anybody else encountered similar problems?
Flashed on TWRP 2.8.7 from Stock Kit Kat 4.4.2.
Preter said:
Followed the flashing guide to the letter - this V2 rom is great - but for only about 3 days.
After around the 3 day mark, the error message will flash "SIM card removed The mobile network will be unavailable until you restart with a valid SIM card inserted."
The phone will reboot within 10 seconds (even if you go to airplane mode immediately). It rebooted repeatedly first time it happened.
Did a complete nuke wipe, flashed again. Same thing - at the 3 day mark - the Singtel SIM will show the same error and reboot. After that, SIM not usable at all. All telco signals (Singtel) will be gone. No phone, SMS, let alone data of any sort.
Think it is the problem with the modem.
http://forum.xda-developers.com/lg-g3/development/stock-t2961073
(Download v2 (modem from v21c) -> https://mega.nz/#!OIlwGLKS!LlcNIImHK...EzSt_ikHlWj3yY)
Tried flashing 21A, 21B, autoprime's hybrid modem. Doesn't work. Anybody else encountered similar problems?
Flashed on TWRP 2.8.7 from Stock Kit Kat 4.4.2.
Click to expand...
Click to collapse
I have the same problem as you. except, I did not do the update and it happened out of the blue today. Been restarting my phone and if I am lucky, sometimes I get connected to the network for about an hour before the error comes on again.
matthewmax09 said:
I have the same problem as you. except, I did not do the update and it happened out of the blue today. Been restarting my phone and if I am lucky, sometimes I get connected to the network for about an hour before the error comes on again.
Click to expand...
Click to collapse
Hi Matthew,
Saw your PM. Just to confirm that you have the same problem.
Error message - "The mobile network will be unavailable until you restart with a valid SIM card inserted"
- Bar counts up to 100% before phone reboots automatically
This is apparently a very serious problem with Android going back a few years and a few Android OS versions (KK I believe). It happens with various phone models ranging from:
LG G4
https://www.reddit.com/r/lgg4/comments/43p26p/sim_card_removed/
Nexus - Google doesn't give a F*CK
http://androidforums.com/threads/sim-card-problems.467384/
Motorola, Nexus, Samsung Galaxy etc.
https://code.google.com/p/android/issues/detail?id=66964
Google apparently doesn't give a rat's ass about it. As such it is very difficult to pin-point the problem. I have flashed & re-flashed robalm's V2 ROM at least 4 times, each time with a complete (nuke) wipe of everything including the Internal SD card. It definitely happens on the default modem (21C supposedly) that comes with it. Different modems have not helped. If you find one that works, let me know.
It cannot be a SIM card problem. Cos I've never ever taken it out since the day I got the phone. Once the problem happened, I've tried re-seating it, wiping the electrical contacts with microfibre cloth etc. Singtel shop customer service checked all the APN and network settings and confirmed it is correct, asked me to try the SIM card in other phones. Done that, nothing wrong with the SIM..
Googling further, some folks discovered that it is due to Google Apps (Play Store, Maps, G+, Gmail, Play Books/Games/Movies/Music/Services etc. etc.), which are system apps (as part of the ROM package), causing the problem after they are updated via Google Play Store. Don't we all update apps to the latest version, no?
I tried uninstalling all the updates for all of them (Settings>>Apps>>) and replacing them with the factory updates that came with the ROM. I usually freeze all the crap money sucking subscription based or in-app purchasing Google Apps that I don't use anyway. However, whether frozen or not, it still happens. Although not freezing any of them does seem more likely to cause the problem to become even more severe - like going into constant reboots as opposed to intermittent ones. When that happens, you have to go to airplane mode BEFORE the countdown completes and reboot happens. At least when it restarts, it won't hunt for the missing cellular signal and triggering another reboot. This then allows you to freeze the suckers more agressively.
It worked for a few days - I thought I had narrowed the problem down to Google Play Store, Play Framework and Play Services. But yesterday or so it has come back again with a vengeance. Freezing Google Play Store does not help by the way - besides what's the point if you can't use Play Store?
Problem is, disabling the auto-update functions on Google Play Store using:
(Play Store>>Settings>>General>>Auto-update apps>>check "Do not auto-update apps")
doesn't stop Google Play Store and Google Play services from auto-updating themselves! F*ck Google! You cannot prevent it no matter what.
Worse, everytime it auto-updates itself (or if you uninstall updates) - note that it will switch to the default setting of "Auto-update apps over Wi-Fi only" again. So you have to be fast in going to Settings in Google Play each time you reboot and open Play Store.
Some netizens have suggested ADB command line means to cripple the auto-updating. But to me that is not the freaking point. It's about trying to isolate and find the problem.
You end up uninstalling updates for Play Store several times a day but when you find that the cellular signal is gone (no bars), you realise that it has sneakily updated to 6.0.5.
But even when I uninstall all updates for Play Store. It can still happen. Maybe less frequently.
No cellular signal is bad enough. The worst aspect is the rebooting. I tried restoring my beloved KK 4.4.2 Nandroid backup but apparently I'll have to find a compatible modem again as TWRP 2.8.0 (or my previous version before upgrading to TWRP 2.8.7 for this Marshmallow) didn't manage to back it up (even though I tick everything).
Still doing trial and error to try isolating the problem. The Google apps clue seems the more likely cause, but I can't say I can discern a definite pattern yet.
It could be a bug in Marshmallow 6.0. Maybe 6.1 will solve it. Maybe its the damn Polish ROM/modem.
In the meantime, I can only say - Do not flash this ROM! Without any cellular signal, the phone is not a phone. The constantly rebooting makes it useless!
Preter said:
Hi Matthew,
Saw your PM. Just to confirm that you have the same problem.
Error message - "The mobile network will be unavailable until you restart with a valid SIM card inserted"
- Bar counts up to 100% before phone reboots automatically
This is apparently a very serious problem with Android going back a few years and a few Android OS versions (KK I believe). It happens with various phone models ranging from:
LG G4
https://www.reddit.com/r/lgg4/comments/43p26p/sim_card_removed/
Nexus - Google doesn't give a F*CK
http://androidforums.com/threads/sim-card-problems.467384/
Motorola, Nexus, Samsung Galaxy etc.
https://code.google.com/p/android/issues/detail?id=66964
Google apparently doesn't give a rat's ass about it. As such it is very difficult to pin-point the problem. I have flashed & re-flashed robalm's V2 ROM at least 4 times, each time with a complete (nuke) wipe of everything including the Internal SD card. It definitely happens on the default modem (21C supposedly) that comes with it. Different modems have not helped. If you find one that works, let me know.
It cannot be a SIM card problem. Cos I've never ever taken it out since the day I got the phone. Once the problem happened, I've tried re-seating it, wiping the electrical contacts with microfibre cloth etc. Singtel shop customer service checked all the APN and network settings and confirmed it is correct, asked me to try the SIM card in other phones. Done that, nothing wrong with the SIM..
Googling further, some folks discovered that it is due to Google Apps (Play Store, Maps, G+, Gmail, Play Books/Games/Movies/Music/Services etc. etc.), which are system apps (as part of the ROM package), causing the problem after they are updated via Google Play Store. Don't we all update apps to the latest version, no?
I tried uninstalling all the updates for all of them (Settings>>Apps>>) and replacing them with the factory updates that came with the ROM. I usually freeze all the crap money sucking subscription based or in-app purchasing Google Apps that I don't use anyway. However, whether frozen or not, it still happens. Although not freezing any of them does seem more likely to cause the problem to become even more severe - like going into constant reboots as opposed to intermittent ones. When that happens, you have to go to airplane mode BEFORE the countdown completes and reboot happens. At least when it restarts, it won't hunt for the missing cellular signal and triggering another reboot. This then allows you to freeze the suckers more agressively.
It worked for a few days - I thought I had narrowed the problem down to Google Play Store, Play Framework and Play Services. But yesterday or so it has come back again with a vengeance. Freezing Google Play Store does not help by the way - besides what's the point if you can't use Play Store?
Problem is, disabling the auto-update functions on Google Play Store using:
(Play Store>>Settings>>General>>Auto-update apps>>check "Do not auto-update apps")
doesn't stop Google Play Store and Google Play services from auto-updating themselves! F*ck Google! You cannot prevent it no matter what.
Worse, everytime it auto-updates itself (or if you uninstall updates) - note that it will switch to the default setting of "Auto-update apps over Wi-Fi only" again. So you have to be fast in going to Settings in Google Play each time you reboot and open Play Store.
Some netizens have suggested ADB command line means to cripple the auto-updating. But to me that is not the freaking point. It's about trying to isolate and find the problem.
You end up uninstalling updates for Play Store several times a day but when you find that the cellular signal is gone (no bars), you realise that it has sneakily updated to 6.0.5.
But even when I uninstall all updates for Play Store. It can still happen. Maybe less frequently.
No cellular signal is bad enough. The worst aspect is the rebooting. I tried restoring my beloved KK 4.4.2 Nandroid backup but apparently I'll have to find a compatible modem again as TWRP 2.8.0 (or my previous version before upgrading to TWRP 2.8.7 for this Marshmallow) didn't manage to back it up (even though I tick everything).
Still doing trial and error to try isolating the problem. The Google apps clue seems the more likely cause, but I can't say I can discern a definite pattern yet.
It could be a bug in Marshmallow 6.0. Maybe 6.1 will solve it. Maybe its the damn Polish ROM/modem.
In the meantime, I can only say - Do not flash this ROM! Without any cellular signal, the phone is not a phone. The constantly rebooting makes it useless!
Click to expand...
Click to collapse
Yes! correct. we have the same problem. I don't think it is a glitch on mm 6.0 because i was on lollipop 5.0 when the problem occurred and I have only flashed 5.0 roms and modems. can you try the candySiX rom and see how it fairs in your phone? CandySix Rom thread link
I tried it on my phone and was able to connect to tower until I started installing Whatsapp which cause the sucker to break and reboot. But that was in a span of 15 mins. I read that it could also be a GPS problem so I disabled GPS but the phone was still broken. From my understanding, your trail and error seems to point to the play store updating itself that causes the phone to break correct? so why not cripple it using ADB and as for the updating of apps, it be done manually through sideload. because i don't think that there will be many apps that need to be frequently updated right? and even so if we do not update the app, it does not mean that the app will lose its functionality??
matthewmax09 said:
Yes! correct. we have the same problem. I don't think it is a glitch on mm 6.0 because i was on lollipop 5.0 when the problem occurred and I have only flashed 5.0 roms and modems. can you try the candySiX rom and see how it fairs in your phone? CandySix Rom thread link
I tried it on my phone and was able to connect to tower until I started installing Whatsapp which cause the sucker to break and reboot. But that was in a span of 15 mins. I read that it could also be a GPS problem so I disabled GPS but the phone was still broken. From my understanding, your trail and error seems to point to the play store updating itself that causes the phone to break correct? so why not cripple it using ADB and as for the updating of apps, it be done manually through sideload. because i don't think that there will be many apps that need to be frequently updated right? and even so if we do not update the app, it does not mean that the app will lose its functionality??
Click to expand...
Click to collapse
Dude –punctuation please …
I wish it was that simple. I've used Android Firewall (AFSWall+) to BLOCK all internet connections for Google Play Store and Google Play Services. The sneaky bastards at Google can still somehow update the factory Google Play Store from to 6.0.5! Upon that happening, all cellular network connection WILL DEFINITELY be lost. It may or may not reboot after that.
The problem is definitely related to Google Play (Store & Services). But it is not limited to it. Even when it has not updated itself, the error message can still show up and the phone can still reboot randomly with the error message. That is why I don’t think using ADB to disable updates solves anything.
Google is definitely doing something very intrusive with their Play Store apps – (why should and) how the hell apps (even if system apps) can be allowed to affect the functions of SIM card and cellular network reception to this extent is beyond me. Big brother is really upon us.
Not keen on trying custom ROMs anymore since my S2 days. Especially when stock Marshmallow already cause so many problems. Maybe this needs to be posted in the other international LG G3 threads.
Flash tool crashed
oceangreen said:
As you guys know, MM has started rolling out to the International Model D855!
I've been on MM for 3 days and quite satisfied with the update! Rom's seems faster and snappier, no more micro lag, juice seems to be better than LP tho... What you guys think? To all Lions, Share your thoughts and comments here! Cheers All!!!
Click to expand...
Click to collapse
Heyy trying to flash MM but lg flash tool 2014 keeps on crashing on win 10. want to retain data so am not using TWRP. What tool are u using and software version?
Good Sharing... thus far my screen not so often give me a blank screen issue after upgrade to MM Global
Hi guys ( @Preter @matthewmax09 )
my friend's SEA device started to giving your "The mobile network will be unavailable until you restart with a valid SIM card inserted" error too.
did you solved this problem? can anyone tell a solution for this?
thanks.
Hi XDA,
As there ar eno recent thread about 'no deep sleep' (aka on CM13/13.1) I'm opening one here inh ope someone can help me troubleshoot what's wrong...
I've had my OPO for 1.5 yr now, and overall it's doing great. Except since CM13.0, I've been having troubles with deep sleep and therefore my battery time hardly make it through the day.
It all began after the April upgrade, when I decided to encrypt my phone. I did a clean full wipe and installed the zip from TWRP recovery, then proceeded to encrypt the phone... Turns out the boot.img patched by SuperSU is incompatible with the encryption process so I reverted the boot.img ti the original and encrypted my phone, then flashed SuperSU back. Since then, the phone would never enter deep sleep mode, except when data connexion and wifi are disabled.
I've since flashed the latest build (ZNH2KAS1KN) in hope that would solve the problem. The flash was the cleanest I ever took (wipe data, system, dalvik, cache ; reboot to recovery, flash full zip, boot to system and restore all app through the 'play store restore' function, reboot to bootloader, flash TWRP with AtAm fix for CM13 encryption support). Yet, my battery keeps drainign blazing fast and I have no deep sleep at all even with the phone sitting indle on a table for hours. See screenshots.
The only strange thing I see are those 'fd440000.qrypto' kernel wakelocks. Any ideas ? I'm assuming it has something to do with the phone being encrypted, but why would deep sleep be achievable when the phone has no data/wifi ?? It's really puzzling and I can't figure out what to do. I had exactly the same problem on the previous 13.0 release (including the qcrypto wakelock).
edit: the only slight deep sleep period is because my SIM card was not detected for a short period of time (probably bad contacts, I took it out, wiped it a bit and everything was back in order)
Any help appreciated, thanks!
Strange. I haven't had much battery drain issues on Sultan's build. Are you using the official cm13 builds or unofficial builds?
Sent from my A0001 using Tapatalk
CoinCoin88 said:
Hi XDA,
As there ar eno recent thread about 'no deep sleep' (aka on CM13/13.1) I'm opening one here inh ope someone can help me troubleshoot what's wrong...
I've had my OPO for 1.5 yr now, and overall it's doing great. Except since CM13.0, I've been having troubles with deep sleep and therefore my battery time hardly make it through the day.
It all began after the April upgrade, when I decided to encrypt my phone. I did a clean full wipe and installed the zip from TWRP recovery, then proceeded to encrypt the phone... Turns out the boot.img patched by SuperSU is incompatible with the encryption process so I reverted the boot.img ti the original and encrypted my phone, then flashed SuperSU back. Since then, the phone would never enter deep sleep mode, except when data connexion and wifi are disabled.
I've since flashed the latest build (ZNH2KAS1KN) in hope that would solve the problem. The flash was the cleanest I ever took (wipe data, system, dalvik, cache ; reboot to recovery, flash full zip, boot to system and restore all app through the 'play store restore' function, reboot to bootloader, flash TWRP with AtAm fix for CM13 encryption support). Yet, my battery keeps drainign blazing fast and I have no deep sleep at all even with the phone sitting indle on a table for hours. See screenshots.
The only strange thing I see are those 'fd440000.qrypto' kernel wakelocks. Any ideas ? I'm assuming it has something to do with the phone being encrypted, but why would deep sleep be achievable when the phone has no data/wifi ?? It's really puzzling and I can't figure out what to do. I had exactly the same problem on the previous 13.0 release (including the qcrypto wakelock).
edit: the only slight deep sleep period is because my SIM card was not detected for a short period of time (probably bad contacts, I took it out, wiped it a bit and everything was back in order)
Any help appreciated, thanks!
Click to expand...
Click to collapse
looks like you are having weak or no signal. this is likely to cause this issue!
Bac0nator said:
Strange. I haven't had much battery drain issues on Sultan's build. Are you using the official cm13 builds or unofficial builds?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Only the official builds for CM13/13.1, and with the cleanest install as possible... Never tried Sultan's build, is that a kernel, a full rom...?
hellcat50 said:
looks like you are having weak or no signal. this is likely to cause this issue!
Click to expand...
Click to collapse
Definitely not the cause. This happens every day, everywhere, independently of signal strength (i.e. color of bar in graph). I've confirmed with a friend of mine who also encrypted his phone a while ago and he also never goes to deep sleep.
CoinCoin88 said:
Only the official builds for CM13/13.1, and with the cleanest install as possible... Never tried Sultan's build, is that a kernel, a full rom...?
Definitely not the cause. This happens every day, everywhere, independently of signal strength (i.e. color of bar in graph). I've confirmed with a friend of mine who also encrypted his phone a while ago and he also never goes to deep sleep.
Click to expand...
Click to collapse
sultan's rom is cm13 with caf kernel. it is known to be very battery friendly.
Here is the link: http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700
and here I was hoping not to have to full wipe/reflash/restore again.... I've also posted on CM jira in hope of a comment on whether there is a known bug on ecnrypted devices or not. If nothig comes from there I'll try sultan's rom...
Sultan's builds are optimized for battery on the one plus one. They tend to be better than official cm13 builds, most of the time.
Another option is downloading an app called nap time on the play store, which forces your phone to go into deep sleep the moment the screen shuts off.
CoinCoin88 said:
and here I was hoping not to have to full wipe/reflash/restore again.... I've also posted on CM jira in hope of a comment on whether there is a known bug on ecnrypted devices or not. If nothig comes from there I'll try sultan's rom...
Click to expand...
Click to collapse
Steve included some kernel commits recently that address the crypto wakelock. They should be fixed on current nightlies.
I know it fixes it as I had that fd000.crypto kernel wakelock until very recently and I'm encrypted.
I have the same issue on Sultan's Rom. First 20 days battery life was awesome and now all the time phone is awake. I am reflashing sulatn build again
Thanks for this info, this is going in the same direction I observed and somewhat reassuring. Are you talking about CM nightlies then ?
edit: that was inteded for @tiny4579
Sent from my A0001 using XDA Free mobile app
tiny4579 said:
Steve included some kernel commits recently that address the crypto wakelock. They should be fixed on current nightlies.
I know it fixes it as I had that fd000.crypto kernel wakelock until very recently and I'm encrypted.
Click to expand...
Click to collapse
By any chance, would you happen to have SuoerSU as root binary/manager? I recall it patches boot.img which prevented encryption from being run in the first place (to encrypt, I had to reflash the stock boot.img, encrypt, then reflash SuoerSU). I'm wondering if the altered boot.img couldn't be part of the problem.
Sent from my A0001 using XDA Free mobile app
Some heads up: there was indeed a wakelock issue that has been fixed by a commit on the 4th of June.
See associated bug on JIRA: https://jira.cyanogenmod.org/browse/BACON-4987 (and appreciate how it's easier to blame the user than to try to replicate a bug). Hopefully we'll have a 'future OTA' before the end of the year...
I still have this wakelocks issues right now...
Hi! I think I've tried every Lollipop/Marshmallow ROM out there, but I haven't found one as stable as KitKat ROMs (CM11/Stock). I just want a Lollipop/Marshmallow ROM that doesn't hang every time I open YouTube from recents (many apps suffer of that too), and with working WiFi (had this problem with CM13), and with decent battery life. CM13 is actually one of the most stable ROMs I've tried, but it had serious WiFi problems (it simply disconnects from the WiFi and then reconnects saying it doesn't have internet access, very annoying), some kind of TV-like static when booting and sometimes when unlocking the phone, and the recents cards sometimes got cut off (though this is not really a deal breaker). The only Marshmallow ROMs I haven't tried are BeanStalk and Mokee because they are based on CM, so I supposed they have the same problems. So, what's the most stable Lollipop/Marshmallow ROM you have tried? And can that ROM be used as daily driver?
Thanks!
Sorry for my English lol.
Which other Roms have you tried?
MuhammadBilal said:
Which other Roms have you tried?
Click to expand...
Click to collapse
Exodus (5.0, will try 5.1), BlissPop, DirtyUnicorns, dhacker's unofficial CM12, Mokee (5.1), ResurrectionRemix, unofficial CM13...
EDIT: Tried Exodus 5.1, really slow.
MoKee
So far, so good (It's only been 24 hours since I've installed it) on the 17-01-29 build of Mokee here
Wifi has been solid with no issues, rom seems stable, and YouTube ran fine from recents.
Update: Had strange problem with downloading email attachments with both gmail and Yahoo mail. Back to stock KK for the time being.
Update: Turns out the above email problems had to do with permissions.
beeewell said:
So far, so good (It's only been 24 hours since I've installed it) on the 17-01-29 build of Mokee here
Wifi has been solid with no issues, rom seems stable, and YouTube ran fine from recents.
Update: Had strange problem with downloading email attachments with both gmail and Yahoo mail. Back to stock KK for the time being.
Click to expand...
Click to collapse
It doesn't even boot here, first time it booted but it said that encrypting my device failed (WTF?) and then rebooted to do a factory reset, and it wiped the system partition. xD
I installed it again without Gapps and now it won't do anything, it justs sits there in the bootanimation for several minutes and then reboots. Perhaps I didn't downgrade correctly? How did you downgrade? I used RSD Flasher, and it has worked fine for me in the past.
trivialPotato said:
It doesn't even boot here, first time it booted but it said that encrypting my device failed (WTF?) and then rebooted to do a factory reset, and it wiped the system partition. xD
I installed it again without Gapps and now it won't do anything, it justs sits there in the bootanimation for several minutes and then reboots. Perhaps I didn't downgrade correctly? How did you downgrade? I used RSD Flasher, and it has worked fine for me in the past.
Click to expand...
Click to collapse
It took me awhile to find the procedure and files that I used to downgrade/upgrade, but I finally did. Thanks to Nobe1976, this method of going back and forth from KK to JB doesn't require a PC; There are 2 zip files that you can flash w/ TWRP to go back and forth. Here's the procedure and file links: http://www.droidrzr.com/topic/50096-how-tomobile-downgrader-flash-back-10-09-14-14/
I too thought Exodus was stable, but slow. I liked using MoKee 5.1, but I had an annoying problem with it that I couldn't solve: Every time I picked up my phone, there was a notification to sign back onto my WiFi network. It did so without asking for any credentials, but it got too annoying for me.
Right now, I'm using PacMan Rom (4.4.4), and it's been performing very well and is stable. Here's the link in case you wanna try: https://s.basketbuild.com/devs/pacman/moto_msm8960/KK/release
beeewell said:
It took me awhile to find the procedure and files that I used to downgrade/upgrade, but I finally did. Thanks to Nobe1976, this method of going back and forth from KK to JB doesn't require a PC; There are 2 zip files that you can flash w/ TWRP to go back and forth. Here's the procedure and file links: http://www.droidrzr.com/topic/50096-how-tomobile-downgrader-flash-back-10-09-14-14/
I too thought Exodus was stable, but slow. I liked using MoKee 5.1, but I had an annoying problem with it that I couldn't solve: Every time I picked up my phone, there was a notification to sign back onto my WiFi network. It did so without asking for any credentials, but it got too annoying for me.
Right now, I'm using PacMan Rom (4.4.4), and it's been performing very well and is stable. Here's the link in case you wanna try: https://s.basketbuild.com/devs/pacman/moto_msm8960/KK/release
Click to expand...
Click to collapse
Thank you so much! That will save me so much headaches lol.
I'm using lastest CM11 snapshot, working fine, but I find the battery doesn't last as much as in CM12.1.
EDIT: I'm writing from Mokee 6.0! That method for downgrading works flawlessly!
Mokee feels better than CM12.1 except by that TV-like interference when you unlock the device, and I haven't tried the WiFi, but it looks okay.
Thing to remember while reading all of the below, I have an XT905, with a JBBL.
I'm currently using "cm-13.0-20161205-ilichva-xt907_jbb.zip" for my daily. The only repeated "fails" I have is where WiFi will disconnect, however, it only happens if I am not using it and the phone is asleep. One thing I have noticed is that this is the only ROM that actually does go into deep sleep for me. I'm only on Wifi at home for extended periods (ie when phone goes to sleep). This may be the reason the other ROMs don't loose WiFi, because they don't go into deep sleep for me. My Wifi disconnects, and never is connected without internet. I just go into Wifi, select my network and say connect, and its all good again.
Previously (a few years back) I was using BlissPop (Lollipop), but did not use the latest build. I had better luck with "BlissPop-v3.9-moto_msm8960_jbbl-OFFICIAL-20150829-1751.zip"
Others I have used (Lollipop) and found pretty stable (ie used as daily for some time) were:
CARBON-5.1.1-Final-moto_msm8960_jbbl.zip
Resurrection-Remix-LP-v5.5.8-moto_msm8960_jbbl.zip
and for KitKat
LS-KK-MileStone-3.2-moto_msm8960_jbbl.zip
With the CM13 ROM I have a 64GB SDCard, F2FS cache partition, Xposed, Viper, a Linux Swap Partition (512mb) and personally find it to be the most stable ROM I have used (apart from WiFi) on the phone. Some of the Lollipop (bliss pop included) could not run my live wallpaper (Celestial Bodies). I have also noticed that at least one app using the CPU (a Solitaire game attempting to find a winnable deal manually) actually runs a lot faster in CM13 than in the others.
If YouTube bothers you, maybe you should try the alternatives such as New Pipe or OGYouTube etc etc. Actually, I just tried YouTube from the recents,and it worked fine for me.
As for the TV Static on boot (just before animation) I have had that since I first unlocked the bootloader; I thought It was normal. It has been independent of any ROMs and it happens for me on every ROM.
Mokee 5.1
Sorry for going off-topic but would any of you guys happen to have a copy of the last LP Mokee build that was released on 4PDA ?
MK51.1-xt907_jbbl-20160420-ilichva.zip
The link is unfortunately dead and I can't find a mirror anywhere. I'd like to save a copy just in case anyone asks in the future. If any of you have, would you please share privately with me? Thanks a lot!
DiamondJohn said:
Thing to remember while reading all of the below, I have an XT905, with a JBBL.
I'm currently using "cm-13.0-20161205-ilichva-xt907_jbb.zip" for my daily. The only repeated "fails" I have is where WiFi will disconnect, however, it only happens if I am not using it and the phone is asleep. One thing I have noticed is that this is the only ROM that actually does go into deep sleep for me. I'm only on Wifi at home for extended periods (ie when phone goes to sleep). This may be the reason the other ROMs don't loose WiFi, because they don't go into deep sleep for me. My Wifi disconnects, and never is connected without internet. I just go into Wifi, select my network and say connect, and its all good again.
Previously (a few years back) I was using BlissPop (Lollipop), but did not use the latest build. I had better luck with "BlissPop-v3.9-moto_msm8960_jbbl-OFFICIAL-20150829-1751.zip"
Others I have used (Lollipop) and found pretty stable (ie used as daily for some time) were:
CARBON-5.1.1-Final-moto_msm8960_jbbl.zip
Resurrection-Remix-LP-v5.5.8-moto_msm8960_jbbl.zip
and for KitKat
LS-KK-MileStone-3.2-moto_msm8960_jbbl.zip
With the CM13 ROM I have a 64GB SDCard, F2FS cache partition, Xposed, Viper, a Linux Swap Partition (512mb) and personally find it to be the most stable ROM I have used (apart from WiFi) on the phone. Some of the Lollipop (bliss pop included) could not run my live wallpaper (Celestial Bodies). I have also noticed that at least one app using the CPU (a Solitaire game attempting to find a winnable deal manually) actually runs a lot faster in CM13 than in the others.
If YouTube bothers you, maybe you should try the alternatives such as New Pipe or OGYouTube etc etc. Actually, I just tried YouTube from the recents,and it worked fine for me.
As for the TV Static on boot (just before animation) I have had that since I first unlocked the bootloader; I thought It was normal. It has been independent of any ROMs and it happens for me on every ROM.
Click to expand...
Click to collapse
The TV-like static seems to be something with the JBBL, it happens even in recovery for me (when the recovery locks and turns off the screen). About the WiFi, it disconnected even if I was playing a game or using the internet, but I live in a place where I don't have WiFi anymore, so it's not a problem.
Indeed, Mokee 6.0 and CM13 are the most stable ROMs I've tried, even more than CM11, except for the bugs said above, even the battery lasts more.
BTW, how do you increment swap? I've tried several methods, but it still shows 256MB.
trivialPotato said:
The TV-like static seems to be something with the JBBL, it happens even in recovery for me (when the recovery locks and turns off the screen).
Click to expand...
Click to collapse
I only get it when I reboot, but get it every time.
trivialPotato said:
About the WiFi, it disconnected even if I was playing a game or using the internet, but I live in a place where I don't have WiFi anymore, so it's not a problem.
Click to expand...
Click to collapse
I personally have only seen it happen when the I wake the device up. Never has it occurred while I am using it.:angel: Last night I was searching for another thing in Xposed, and I saw a lot of Wifi type modules. Though most were about turning wifi off when the screen goes off; but I wasn't looking for Wifi stuff, so maybe you could find something that helps.
trivialPotato said:
Indeed, Mokee 6.0 and CM13 are the most stable ROMs I've tried, even more than CM11, except for the bugs said above, even the battery lasts more.
Click to expand...
Click to collapse
I tried Mokee, and I cant remember why, but it wasn't OK as a daily for me. To be honest, I would find it hard to go back to a ROM (ie less than MM) that does not have privacy guard. I also forgot to mention on my phone I have Adaway and Lucky Patcher and > 10 boot scripts (such as swap, IO optimisations, trim command, disabling media scanner on boot ... etc etc etc)
trivialPotato said:
BTW, how do you increment swap? I've tried several methods, but it still shows 256MB.
Click to expand...
Click to collapse
I am guessing by "increment" you really mean implement? Assuming that, I use a boot script. Currently I use a swap partition, so, for that I:
1. create a linux swap partition on the SDCard using Minitool Partition Wizard
2. Put the card into my phone, boot it and Find out the partition details (eg "/dev/block/mmcblk1p2" on my card now)
3. create a boot script to enable it on boot. The meat of the script is:
Code:
swapon /dev/block/mmcblk1p2;
Previously I have used a swap file, which is actually more complex. Something like:
Code:
location=/mnt/media_rw/sdcard1/data/local/tmp;
file_name=swapfile.dat;
desiredsizemb=512;
dd if=/dev/zero of=$location/$file_name bs=1048576 count=$desiredsizemb;
swapon -p 16000 $location/$file_name;
Hope the above helps, and let me know if you get it working.
DiamondJohn said:
I only get it when I reboot, but get it every time.
I personally have only seen it happen when the I wake the device up. Never has it occurred while I am using it.:angel: Last night I was searching for another thing in Xposed, and I saw a lot of Wifi type modules. Though most were about turning wifi off when the screen goes off; but I wasn't looking for Wifi stuff, so maybe you could find something that helps.
I tried Mokee, and I cant remember why, but it wasn't OK as a daily for me. To be honest, I would find it hard to go back to a ROM (ie less than MM) that does not have privacy guard. I also forgot to mention on my phone I have Adaway and Lucky Patcher and > 10 boot scripts (such as swap, IO optimisations, trim command, disabling media scanner on boot ... etc etc etc)
I am guessing by "increment" you really mean implement? Assuming that, I use a boot script. Currently I use a swap partition, so, for that I:
1. create a linux swap partition on the SDCard using Minitool Partition Wizard
2. Put the card into my phone, boot it and Find out the partition details (eg "/dev/block/mmcblk1p2" on my card now)
3. create a boot script to enable it on boot. The meat of the script is:
Code:
swapon /dev/block/mmcblk1p2;
Previously I have used a swap file, which is actually more complex. Something like:
Code:
location=/mnt/media_rw/sdcard1/data/local/tmp;
file_name=swapfile.dat;
desiredsizemb=512;
dd if=/dev/zero of=$location/$file_name bs=1048576 count=$desiredsizemb;
swapon -p 16000 $location/$file_name;
Hope the above helps, and let me know if you get it working.
Click to expand...
Click to collapse
Mokee has be running pretty solid here, I'll try CM13 and/or BeanStalk in a few days, though.
About swap, if I run "free" in the Terminal it shows it has swap memory, and I tried several methods (well, apps) to increment it but no luck. I'll try yours in a few days.
About the WiFi and the TV-like static, I bet is some difference between xt905 and xt907.
trivialPotato said:
Mokee has be running pretty solid here, I'll try CM13 and/or BeanStalk in a few days, though.
About swap, if I run "free" in the Terminal it shows it has swap memory, and I tried several methods (well, apps) to increment it but no luck. I'll try yours in a few days.
About the WiFi and the TV-like static, I bet is some difference between xt905 and xt907.
Click to expand...
Click to collapse
Well, the swap you currently see is ZRam, which is a compressed partition of memory used as a swap partition. ie not a file or physical partition on an sdcard (as I use above, in addition to ZRam). To increase ZRam, you loose available memory. That can be simply changed with the following lines:
Code:
echo 1 > /sys/block/zram0/reset;
OR
swapoff /dev/block/zram0;
echo "201326592" > /sys/block/zram0/disksize;
mkswap /dev/block/zram0;
swapon /dev/block/zram0;
The number is 1024*1024*target_size (MB eg 600). I think you have to do it at boot time or you end up with device or resource busy messages.
Or you could use Kernel Adiutor - Virtual Memory
That actually reminds me, one bug I have noticed on all the CM13 ROMs I tried, was that the init.d did not work, I had to use Kernel Adiutor to implement it; and I have a lot of scripts.
Currently running the new Lineage ROM http://forum.xda-developers.com/showthread.php?t=3577746. Thanks to Ilichva...
So far, so good !!! Performing very well with no issues found yet. :thumbup:
It still has the WiFi disconnecting when asleep for me.
beeewell said:
Currently running the new Lineage ROM http://forum.xda-developers.com/showthread.php?t=3577746. Thanks to Ilichva...
So far, so good !!! Performing very well with no issues found yet. :thumbup:
Click to expand...
Click to collapse
Performing well here, too! It has the same bugs CM13 had, but I feel is a bit snappier.
Is it just me, or is the default swappiness set at 100? (cat /proc/sys/vm/swappiness)
I actually tried lowering it to the android default of 60, and the ROM felt less "snappy", so put it back at 100
DiamondJohn said:
Is it just me, or is the default swappiness set at 100? (cat /proc/sys/vm/swappiness)
I actually tried lowering it to the android default of 60, and the ROM felt less "snappy", so put it back at 100
Click to expand...
Click to collapse
Indeed, is set at 100.
Possible Wifi fix?
trivialPotato said:
I just want a Lollipop/Marshmallow ROM ... and with working WiFi (had this problem with CM13), and with decent battery life. CM13 is actually one of the most stable ROMs I've tried, but it had serious WiFi problems (it simply disconnects from the WiFi and then reconnects saying it doesn't have internet access, very annoying).
Click to expand...
Click to collapse
DiamondJohn said:
...I'm oly on Wifi at home for extended periods (ie when phone goes to sleep). This may be the reason the other ROMs don't loose WiFi, because they don't go into deep sleep for me. My Wifi disconnects, and never is connected without internet. I just go into Wifi, select my network and say connect, and its all good again.
Click to expand...
Click to collapse
I have made a change to build.prop, which APPEARS to have bettered my Wifi stability.
Now, its only been a few hours, so its pretty early to say :fingers-crossed: it has definitely fixed it, but normally within this time, I would of expected to loose my Wifi connection, but it hasn't. :highfive:
Also, the change I made, I have read is actually only set at build time and thereby built into the ROM and not read from the build.prop.
The build.prop setting is: wifi.supplicant_scan_interval. My RAZR had it set to 30, while my N5 was set to 15. I have set it down to 5 (for testing purposes ) Searching the net will bring up heaps of explanation of what the setting is for (and also info saying its only a build time property)
So in summary, I have set the following build.prop
Code:
wifi.supplicant_scan_interval=5
And my WiFi has been solid for the past 3 hrs (normally in sleep except for being woken every 10 minutes to check its still ok ). Let me know if it works for you.
DiamondJohn said:
I have made a change to build.prop, which APPEARS to have bettered my Wifi stability.
Now, its only been a few hours, so its pretty early to say :fingers-crossed: it has definitely fixed it, but normally within this time, I would of expected to loose my Wifi connection, but it hasn't. :highfive:
Also, the change I made, I have read is actually only set at build time and thereby built into the ROM and not read from the build.prop.
The build.prop setting is: wifi.supplicant_scan_interval. My RAZR had it set to 30, while my N5 was set to 15. I have set it down to 5 (for testing purposes ) Searching the net will bring up heaps of explanation of what the setting is for (and also info saying its only a build time property)
So in summary, I have set the following build.propAnd my WiFi has been solid for the past 3 hrs (normally in sleep except for being woken every 10 minutes to check its still ok ). Let me know if it works for you.
Click to expand...
Click to collapse
Will try this next weekend (I don't have WiFi right now). I hope it works lol.
EDIT: It didn't. :crying: