Tip: Fix for that constant SwiftKey reloading lag! - Galaxy S6 General

Hey guys and girls!
Having put up with SwiftKey and other third party keyboards being intermittently force closed by all 5.1.1 TouchWiz versions, I've managed to pinpoint and disable the culprit. By looking at my logs, I could see that the system closed SwiftKey because it was assigned the lowest score by a Samsung module/add-on/thingy called SPCM. Now, I don't know what manner of witchcraft SPCM used to arrive at the conclusion that SwiftKey was so worthless, but using any of the standard Android LMK switches to keep SwiftKey running (like setting it to -17 or resident in xposed App Settings) had no effect at all.
However, after disabling SPCM in build.prop I haven't had a single reload of SwiftKey or its dictionary. Instead, it always appears immediately like you'd expect on a high-end device like this. Even better, there has been no downsides or ill effects of disabling SPCM and I'm really glad to be rid of this major annoyance!
TLDR;
To fix the SwiftKey lag/delay/reloading, open your build.prop and change the following line (requires root):
sys.config.spcm_enable=true
to:
sys.config.spcm_enable=false
Please report your experiences!

That's interesting. Maybe this also fixes the Android wear app constant reloading too.

dedei said:
That's interesting. Maybe this also fixes the Android wear app constant reloading too.
Click to expand...
Click to collapse
I've got no way of testing that, but I guess it might. Feel free to try it and report back! ?

Hey, thanks for the fix!
Is it safe to disable this?
Will it affect any other applications or the phone's overall performance?

Swiftkey New update in Google play, maybe they fixed the problem
Enviado desde mi SM-G920F mediante Tapatalk

Gaiosan said:
Hey, thanks for the fix!
Is it safe to disable this?
Will it affect any other applications or the phone's overall performance?
Click to expand...
Click to collapse
Nope, as per above, I haven't had any adverse effects at all. Performance is unaffected.
Apop10 said:
Swiftkey New update in Google play, maybe they fixed the problem
Enviado desde mi SM-G920F mediante Tapatalk
Click to expand...
Click to collapse
The problem is not with SwiftKey but with TouchWiz - it also affects other keyboards such as Fleksy and Google Keyboard.

Change applied. All good for now. Thanks!.

Fruktsallad said:
Nope, as per above, I haven't had any adverse effects at all. Performance is unaffected.
The problem is not with SwiftKey but with TouchWiz - it also affects other keyboards such as Fleksy and Google Keyboard.
Click to expand...
Click to collapse
I've never had it once happen to Google's keyboard; only with Swiftkey. Thanks for the fix though.

wvcadle said:
I've never had it once happen to Google's keyboard; only with Swiftkey. Thanks for the fix though.
Click to expand...
Click to collapse
My pleasure! Count yourself lucky, I've had it on Google's keyboard myself and others have reported issues with both that and Fleksy.

Thank you sir !
Yup , is working !

Testing it now, so far so good!

Lol weird I don't even have that in my build.prop.

guaneet said:
Lol weird I don't even have that in my build.prop.
Click to expand...
Click to collapse
Ok. If you're still affected, try just adding the false line and I guess it should work anyway. [emoji4]

After changing the line in build.prop (and a reboo) my multi-tasking just went crazy ! If i open like 6 apps and go to the 7th (just an exemple) it will lag like hell !
Changed back to normal and all went back to normal too with the multi-tasking .. so it must have something related to that or maybe it's just incompatible with my rom/kernel (i'm using arter kernel and crash rom)

on XtreStoLite Deo-Mod Edition 2.3 and Arter97 v5 kernel.
working great and been monitoring for about an hour now.
SuperSwiftkey-5.3.8.37

Thanks! Works like a charm

Fruktsallad said:
Hey guys and girls!
Having put up with SwiftKey and other third party keyboards being intermittently force closed by all 5.1.1 TouchWiz versions, I've managed to pinpoint and disable the culprit. By looking at my logs, I could see that the system closed SwiftKey because it was assigned the lowest score by a Samsung module/add-on/thingy called SPCM. Now, I don't know what manner of witchcraft SPCM used to arrive at the conclusion that SwiftKey was so worthless, but using any of the standard Android LMK switches to keep SwiftKey running (like setting it to -17 or resident in xposed App Settings) had no effect at all.
However, after disabling SPCM in build.prop I haven't had a single reload of SwiftKey or its dictionary. Instead, it always appears immediately like you'd expect on a high-end device like this. Even better, there has been no downsides or ill effects of disabling SPCM and I'm really glad to be rid of this major annoyance!
TLDR;
To fix the SwiftKey lag/delay/reloading, open your build.prop and change the following line (requires root):
sys.config.spcm_enable=true
to:
sys.config.spcm_enable=false
Please report your experiences!
Click to expand...
Click to collapse
hi dear friend on note 4 after upgrade to 5.1.1 i have the same problem an in my build.pro i found this line
sys.config.samp_spcm_enable=true is this the same tool and i will change to false it?

tlf55 said:
After changing the line in build.prop (and a reboo) my multi-tasking just went crazy ! If i open like 6 apps and go to the 7th (just an exemple) it will lag like hell !
Changed back to normal and all went back to normal too with the multi-tasking .. so it must have something related to that or maybe it's just incompatible with my rom/kernel (i'm using arter kernel and crash rom)
Click to expand...
Click to collapse
Yeah, that's weird. Can't tell any difference here at all from before/after. Running Xtrestolite and latest UniKernel. As you can see, it seems to be working for others running arters kernel, so either it's a fluke or something's up with that config of yours. If you decide to try again, with or without a different setup, please let me know.
SUNUN said:
hi dear friend on note 4 after upgrade to 5.1.1 i have the same problem an in my build.pro i found this line
sys.config.samp_spcm_enable=true is this the same tool and i will change to false it?
Click to expand...
Click to collapse
No idea mate, but I'm guessing it should work the same. Try it and find out! If it doesn't work, you could try adding our S6 line too. And again, please report back. [emoji106]

Fruktsallad said:
Yeah, that's weird. Can't tell any difference here at all from before/after. Running Xtrestolite and latest UniKernel. As you can see, it seems to be working for others running arters kernel, so either it's a fluke or something's up with that config of yours. If you decide to try again, with or without a different setup, please let me know.
No idea mate, but I'm guessing it should work the same. Try it and find out! If it doesn't work, you could try adding our S6 line too. And again, please report back. [emoji106]
Click to expand...
Click to collapse
Looks like its works. After applying about 2 hours it not killing from memory viber and my watchfaces.

SUNUN said:
Looks like its works. After applying about 2 hours it not killing from memory viber and my watchfaces.
Click to expand...
Click to collapse
Thanks, good to hear! Did you change your own line or did you add the S6 one?

Related

[Q] Action memo no longer opening from stylus pop up.

For me to open action memo, I have to open my app folder and go directly to app. Does anyone know how to fix this issue? I'm running cleanrom 1.7 JB 4.3.
Armyrj127 said:
For me to open action memo, I have to open my app folder and go directly to app. Does anyone know how to fix this issue? I'm running cleanrom 1.7 JB 4.3.
Click to expand...
Click to collapse
Check in settings under S Pen. There is an option to choose what happens when you remove the pen. If this doesn't fix the issue try wiping cache/davlik.
kinstre11 said:
Check in settings under S Pen. There is an option to choose what happens when you remove the pen. If this doesn't fix the issue try wiping cache/davlik.
Click to expand...
Click to collapse
Thanks, I tried it and it didn't work. Any other ideas?
Armyrj127 said:
Thanks, I tried it and it didn't work. Any other ideas?
Click to expand...
Click to collapse
Its a longshot but check to see if Air Command is turned off. I don't know if the two processes are integrated but given the amount of integration Samsung has done to its apps (i.e. Samsung keyboard requiring My Magazines) I wouldn't be surprised.
Other than reflashing the rom I don't think there is another way. It seems like a lot to reflash for something seemingly minor.
(Sorry for the late reply).
kinstre11 said:
Its a longshot but check to see if Air Command is turned off. I don't know if the two processes are integrated but given the amount of integration Samsung has done to its apps (i.e. Samsung keyboard requiring My Magazines) I wouldn't be surprised.
Other than reflashing the rom I don't think there is another way. It seems like a lot to reflash for something seemingly minor.
(Sorry for the late reply).
Click to expand...
Click to collapse
Thanks, I really appreciate it. My air command is off and I was planning on reflash ing but I just downloaded NC2 KitKat and waiting til I have some free time and will flash that. Hopefully that fixes my issue.
kinstre11 said:
Its a longshot but check to see if Air Command is turned off. I don't know if the two processes are integrated but given the amount of integration Samsung has done to its apps (i.e. Samsung keyboard requiring My Magazines) I wouldn't be surprised.
Other than reflashing the rom I don't think there is another way. It seems like a lot to reflash for something seemingly minor.
(Sorry for the late reply).
Click to expand...
Click to collapse
Before I reflashed, I tried switching air command on and it worked. Thanks a lot!
Armyrj127 said:
Before I reflashed, I tried switching air command on and it worked. Thanks a lot!
Click to expand...
Click to collapse
Glad we could figure it out.

Stock 5.1.1 killing apps that should be persistent

Updated to stock 5.1.1 on my note 4 n910u variant last week, and I noticed that it kills apps that are suppose to stay in memory,like Adguard or pintasking. This was not an issue on 5.0.1 and I'd like to know if anyone has observed this.
I'm not running any task killing apps or Xposed modules.
Sent from my SM-N910U using Tapatalk
Yep, me too. 5.1.1 is closing apps like Network manager, Silent, No root vpn,...
don't have task killer and not rooted
pr1jker said:
Yep, me too. 5.1.1 is closing apps like Network manager, Silent, No root vpn,...
don't have task killer and not rooted
Click to expand...
Click to collapse
Damn. I guess it was too much to ask to get a fully functional firmware update from Sammy? ?
Sent from my SM-N910U using Tapatalk
I think it happens when an app calls System.exit() upon service termination. Previously, the system would restart the service but now it seems it kills it until restarted manually.
Try contacting the app's author to ask if they do that.
Well, on second thought, it seems to still kill my app even though I removed System.exit().
I have no idea why it happens. Services are supposed to be restarted automatically.
zapek666 said:
Well, on second thought, it seems to still kill my app even though I removed System.exit().
I have no idea why it happens. Services are supposed to be restarted automatically.
Click to expand...
Click to collapse
Sigh... this is probably why 5.1.1 is giving me better battery life... it kills everything ?
Sent from my SM-N910U using Tapatalk
I wonder what "algorithm" they use through because it doesn't happen with everything. I know that once a service is killed that way, the only way to run it again is to start the app manually.
Could it be that? http://androiding.how/fix-app-reloading-galaxy-s6-5-1-1/
zapek666 said:
Could it be that? http://androiding.how/fix-app-reloading-galaxy-s6-5-1-1/
Click to expand...
Click to collapse
It'd be interesting to know and I may try it later on. I wonder if this might help with multitasking in general - not just services being killed.
EDIT: doesn't help with multitasking, but I'll see if it helps with the persistent apps closing.
Sent from my SM-N910U using Tapatalk
Ok, the thing is called "SmartAdjustManager" and it's indeed some thing that tries to classify running processes.
I'm not fully done with it yet but it seems the following factors avoid killing:
- it's a Samsung process (of course)
- it's a carrier added package
- it's some Google services (but not Android Wear it seems, which is quite an oversight)
- it has a widget running on the homescreen (could be a usable workaround for some apps)
- it has a notification
- its packagename ends with ".cocktailbarservice" *
It does its statistics during a few days (3 days.. 7 days..) which explains why things can run well then all of a sudden a particular services gets killed all the time.
Its whitelist can be updated by some external system but I didn't find where the file is yet.
The following build.prop vars control it (default in parenthesis):
sys.config.samp_enable (true)
sys.config.samp_hotness_enable (true, needs samp_enable too)
sys.config.samp_spcm_enable (false)
sys.config.samp_debug (false)
sys.config.samp_debug_trace (false)
sys.config.samp_debug_spcm (number, none)
It also uses these vars for memory management (when to kill and so on):
sys.config.s_dha_margin
sys.config.s_dha_bg_max
sys.config.s_dha_bg_min
sys.config.s_dha_db_kill
sys.config.s_dha_extra_cache
sys.config.s_dha_cache_max
sys.config.service_kill_adj
*: so it seems the workaround in my case is to add .cocktailbarservice to my packagename.. ridiculous.
You can add the package name to a whitelist stored at:
/data/misc/lpnet/lpnetConfig
(needs root)
Ok, I tested:
Code:
sys.config.samp_spcm_enable=false
This disables the service killing. My phone is now more reliable (no missing wear notifications, no missing calls from my VoIP app, etc...).
Also for improved memory management:
Code:
sys.config.samp_enable=false
ro.config.fha_enable=true
The first one disables the whole SmartAdjustManager nonsense. The 2nd one switches to a simpler memory management closer to the one that AOSP uses. It's like I'm using a new phone!
Conclusion: the Samsung mobile team has no idea of what they're doing. If they think that killing and restarting processes all the time is going to solve anything, they're wrong. It only gives a sluggish phone as a result.
Are you using any DHA tweaks or just those few lines?
Sent from my SM-N910U using Tapatalk
To zapek666:
Are those last 2 lines to be added below the first line you mentioned?
Sent from my SM-N910G
zapek666 said:
Ok, I tested:
Code:
sys.config.samp_spcm_enable=false
This disables the service killing. My phone is now more reliable (no missing wear notifications, no missing calls from my VoIP app, etc...).
Also for improved memory management:
Code:
sys.config.samp_enable=false
ro.config.fha_enable=true
The first one disables the whole SmartAdjustManager nonsense. The 2nd one switches to a simpler memory management closer to the one that AOSP uses. It's like I'm using a new phone!
Conclusion: the Samsung mobile team has no idea of what they're doing. If they think that killing and restarting processes all the time is going to solve anything, they're wrong. It only gives a sluggish phone as a result.
Click to expand...
Click to collapse
Are these edits exclusive to Lollipop 5.1.1 or will they work on Lollipop 5.0.1 or even Kitkat 4.4.4?
Same problem here. Apps get killed all the time. So what to do with a non rooted phone? I tried to change settings of this awful smart manager thing, but still: my phone is not reliable anymore. Btw: Battery life is more or less the same for me.
EP2008 said:
Updated to stock 5.1.1 on my note 4 n910u variant last week, and I noticed that it kills apps that are suppose to stay in memory,like Adguard or pintasking. This was not an issue on 5.0.1 and I'd like to know if anyone has observed this.
I'm not running any task killing apps or Xposed modules.
Sent from my SM-N910U using Tapatalk
Click to expand...
Click to collapse
Try COI or COJ Stock update.
Everything feel much better from COH.
All your problem is from fingerprint bug.
If you are in COH update, try disable fingerprint until you update to COI or COJ stock.
I'm on COJ stock update with fingerprint enabled.
No more random lag, random hot boot & no more random app killing.
zapek666 said:
Ok, I tested:
Code:
sys.config.samp_spcm_enable=false
This disables the service killing. My phone is now more reliable (no missing wear notifications, no missing calls from my VoIP app, etc...).
Also for improved memory management:
Code:
sys.config.samp_enable=false
ro.config.fha_enable=true
The first one disables the whole SmartAdjustManager nonsense. The 2nd one switches to a simpler memory management closer to the one that AOSP uses. It's like I'm using a new phone!
Conclusion: the Samsung mobile team has no idea of what they're doing. If they think that killing and restarting processes all the time is going to solve anything, they're wrong. It only gives a sluggish phone as a result.
Click to expand...
Click to collapse
I'm still testing these, but first impression is that these seem to work, thanks. DHA only allowed about 4 active apps, now I can keep 7 or 8 apps in RAM and multitasking is much better. For people who want to give this one a shot, comment out all DHA lines in your build.prop if added by a Custom ROM, kernel etc and activate FHA instead.
vprasad1 said:
Are these edits exclusive to Lollipop 5.1.1 or will they work on Lollipop 5.0.1 or even Kitkat 4.4.4?
Click to expand...
Click to collapse
The SPCM background services killer was added in 5.1.1. If the rest improves memory performances, I would guess so but I can't confirm as I didn't try with older firmwares.
More info here: http://zapek.com/blog/how-to-make-your-galaxy-note-4-fast-again/
can't you just use settings -> battery -> app optimization to edit the whitelist and disable smart manager?
just choose to never optimize certain apps and they should work normally again.

Nexus 6p freezes when installing/updating apps please help

Hello guys, ever since I got my phone. Everytime the phone trying to do update an app or installing one it froze for a new minutes until the apps is installed. It was like that on stock and it is like that on every custom roms I've tried. I don't know if I'm the only one or not. Please help and thank you.
TheUndertaker21 said:
Hello guys, ever since I got my phone. Everytime the phone trying to do update an app or installing one it froze for a new minutes until the apps is installed. It was like that on stock and it is like that on every custom roms I've tried. I don't know if I'm the only one or not. Please help and thank you.
Click to expand...
Click to collapse
Does it completely freeze up?
Heisenberg said:
Does it completely freeze up?
Click to expand...
Click to collapse
No, just for a few mns until the application is done updating/ installing or un installing Then the screen either hang or locked itself. Like the system did a soft reboot.
TheUndertaker21 said:
No, just for a few mns until the application is done updating/ installing or un installing Then the screen either hang or locked itself. Like the system did a soft reboot.
Click to expand...
Click to collapse
It's normal for a device to slow down or lag a little when installing apps sometimes, the screen locking definitely isn't normal though.
Even my does the same
Like it i update am app or install from play store and use a diff app say I'm on whatsapp then when the app is installing it will be freezed no touch works nothing but screen remains as it is
Cheers ?
Prattham said:
Even my does the same
Like it i update am app or install from play store and use a diff app say I'm on whatsapp then when the app is installing it will be freezed no touch works nothing but screen remains as it is
Cheers ?
Click to expand...
Click to collapse
Even when installing app? That's odd. My note 5 doesn't freeze when installing apps or updating them
It's an issue with aosp package installer. You won't see it on other devices as the oems re-write that code.
It's mostly noticeable on anything FB puts out. As they are known for having the worst coded apps on the market.
zelendel said:
It's an issue with aosp package installer. You won't see it on other devices as the oems re-write that code.
It's mostly noticeable on anything FB puts out. As they are known for having the worst coded apps on the market.
Click to expand...
Click to collapse
Any fix would be nice. I thought my phone was bad
TheUndertaker21 said:
Any fix would be nice. I thought my phone was bad
Click to expand...
Click to collapse
So far I don't think there is a fix. Can't say about official Google. As I have not run a stock rom since I got my first device. If they have fixed it they have not pushed the fix to aosp which is happening more and more with google
zelendel said:
So far I don't think there is a fix. Can't say about official Google. As I have not run a stock rom since I got my first device. If they have fixed it they have not pushed the fix to aosp which is happening more and more with google
Click to expand...
Click to collapse
I'm rooted and running custom rom. It's the same thing.
TheUndertaker21 said:
I'm rooted and running custom rom. It's the same thing.
Click to expand...
Click to collapse
Well as the custom roms sync their source with aosp, then Google has not pushed a fix if there is one. This is happening more and more. Google fixes something but doesn't push it to aosp so it stays broken in 3rd party roms until the devs find a fix
Has this been solved? It's happening to me.
facing same issue. Also my YouTube pause video whenever some app gets updated in background.
Noticed this along with horrible battery life due to system ui restarts or something in all latest may version of Roms. I went back to b29I or whatever "I" version stock rom. No problems since. Goodluck

ExistenZ Marshmallow problems and solutions

Our beloved developer @niaboc79 is getting very tired of people always asking the same questions and posting their problems in the development topic of his rom.
So I decided to make this topic in the "general" section of the forum where people can post about their problems and hopefully some solutions, in the hopes that it will help him and the people having problems at the same time.
Whenever a cause or a solution for a problem is found, I will put it in the second post, right underneath this one.
I want to make clear that I'm not an expert and cannot help much myself, I will just collect and centralize information, and I'm in no way affiliated with @niaboc79 and his work, and do absolutely not deserve any credits for his work.
Also there is no guarantee that the information I collect and post in the second post will be a solution for your problem even if it has apparently worked for other people with similar symptoms.
I invite everyone that uses his rom to share helpful information here. (please)
Firstly ; a copy of the FAQ that @niaboc79 posted himself. You should read it before asking questions.
niaboc79 said:
Frequently Asked Questions
Q: How to flash the DRM fix and avoid loosing of recovery
A:http://forum.xda-developers.com/showpost.php?p=67111204&postcount=1169
Q: Hey, that thing doesn't work!
A: Check if there isn't an (*) at the right of setting description, that means that you must restart SystemUI.
If it is not the case, try to enable/disable option a few time and reboot or read thread to find an answer.
Q: Why is there greyed options in eXistenZ settings!
A: These otions aren't available yet.
Q: Weather isn't working on lockscreen or in expanded status bar...
A: Go in settings/eXistenZ/Notification Panel/Weather Settings;
Press on Weather panel icon, then on Display weather switch;
Select OpenWeatherMap as Weather source;
Use Custom Location;
Set your Location
Click to expand...
Click to collapse
Recovery access problems:
-Don't update busybox
-Don't update Kernel
-Don't flash DRM fix (see FAQ)
If you haven't done one of the above, you should be able to enter recovery by pressing volume down (repeatedly) while starting up the phone.
If you did do one of the above, simply reflash the rom.
Note: since version 4.7 (or alternatively version 3.9) lag is no longer appearing in the rom. If you do witness lag on 4.7 (3.9) there is probably something that you have done that is causing it. Check and double check your apps and settings before trying other solutions in that case!
Lag problems:
-Update to rom version 4.7 (or 3.9 for the rom based on the beta firmware)
-Follow the instructions posted here on rom version prior to 4.7 (3.9)
If you still witness lag after that:
-After installing, give the rom some time to settle, it has to index all your files and the memory management still has to find out what apps (you) are running. This takes a long time (depending on your usage) so give it some days.
-Some xposed modules and Greenify are known causes. Disable that if you use them and see if the lag still persists. If it is gone, you can find the exact module/setting that is the cause by disabling just one module/setting at a time and try if the lag has gone. (this also counts for other problems by the way)
-Stamina mode makes the phone slower as it lowers processor speed etc. Turn it off and check if the lag has gone.
-Many (also popular) apps use quite a lot of system ressources even if you aren't using them. You could uninstall your apps, then reinstall them one at a time, use the phone a bit to check if the lag came back, if not install the next app, and so on until you find the app that is making your phone lag/behave weird.
-Never restore a titanium backup (or similar) when coming from a lollipop rom. There are several differences between lollipop and marshmallow so you risk to restore incompatible stuff.
-Activating blur in recents causes lag (v 3.5, should be solved with the next update of the rom) Fixed in final version
Profile picture (top right of status bar) won't remain after reboot:
-Open the contacts app and go to the first contact (that should contain info about you, and no image) and choose the picture you would like to see in stead of the blue user icon (click on the pencil and then on the image)
Now the image for the user switch in the status bar has been changed too, and it will stick after reboot.
Switch user causes a crash of the beta feedback app and doesn't work
-Remove beta feedback app
You can now switch users, although the system will crash/reboot, it does switch. (will be fixed in a future release of the rom) Fixed in final version
Reserved for later use
i have a problem...
using v 3.5 existance and when i open camera then navigation bar does not showing.. any help?
Ab.Shaheen said:
i have a problem...
using v 3.5 existance and when i open camera then navigation bar does not showing.. any help?
Click to expand...
Click to collapse
Are you using the default camera app? Do you use a theme?
Knutselmaaster said:
Are you using the default camera app? Do you use a theme?
Click to expand...
Click to collapse
am using default camera..
it also does not works on previous versions of existanc marshmallow..
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
Ab.Shaheen said:
am using default camera..
it also does not works on previous versions of existanc marshmallow..
Click to expand...
Click to collapse
i just checked on another camera app... but same result....
not showing there also..
Did you try another theme?
Did you try cleaning all data of the camera app(s)?
systemUI and lock screen are very laggy i tried clean install didnt work also dirty one and had same resualts and thats the only issure i ever faced using this rom since lolipop
Knutselmaaster said:
Are you using the default camera app? Do you use a theme?
Click to expand...
Click to collapse
nope default camera iam using.....which comes in existenz v3.5
rudhraraj said:
nope default camera iam using.....which comes in existenz v3.5
Click to expand...
Click to collapse
Knutselmaaster said:
Did you try another theme?
Did you try cleaning all data of the camera app(s)?
Click to expand...
Click to collapse
xRevengerZee said:
systemUI and lock screen are very laggy i tried clean install didnt work also dirty one and had same resualts and thats the only issure i ever faced using this rom since lolipop
Click to expand...
Click to collapse
Did you check the the lag part of the second post?
I tried all of what u mentioned but tonight i flashd xperia x system ui v1.5 and that made every thing smooth like never before also i dont have any mods installed but problem is after installing the other system ui now existenz feature dont work
xRevengerZee said:
No send me link please
Click to expand...
Click to collapse
The second post of this topic right here...
i did try to reflash the rom after upgrading busybox, but i just cant find a way to flash zip file through pc.
is there a way to flash the rom without flashing back to stock?
Maybe this will work
But if you have problems, there is nothing better than starting from scratch and do a clean install imo
Good morning guys
Any idea of what the hell is making Android OS drink my battery like a martini?
Sent from my Sony D6503 using XDA Labs
FellipeSilvaRJ said:
Good morning guys
Any idea of what the hell is making Android OS drink my battery like a martini?
Sent from my Sony D6503 using XDA Labs
Click to expand...
Click to collapse
By just looking at that image, not really.
I see that you haven't used your phone much during the time of the picture, so no apps are using battery, nor your screen. That automatically makes the operating system the most consuming thing, as it is needed to keep the phone running.
FellipeSilvaRJ said:
Good morning guys
Any idea of what the hell is making Android OS drink my battery like a martini?
Sent from my Sony D6503 using XDA Labs
Click to expand...
Click to collapse
By just looking at that image, not really.
I see that you haven't used your phone much during the time of the picture, so no apps are using battery, nor your screen. That automatically makes the operating system the most consuming thing, as it is needed to keep the phone running.
Click on the app to see what is consuming (radio, processing.... ) if it is the radio, maybe you had very bad connection. If it's the process that prevents the processor going to sleep you should try to find out what is running all the time.
Knutselmaaster said:
By just looking at that image, not really.
I see that you haven't used your phone much during the time of the picture, so no apps are using battery, nor your screen. That automatically makes the operating system the most consuming thing, as it is needed to keep the phone running.
Click to expand...
Click to collapse
Actually, I take at least 7 pictures with Camera FV-5/ 7 with stock app, with screen brightness full. Used WhatsApp and Telegram too, normally these apps and screen should be on top of the list. I have no idea of what the hell I do :silly:
Sent from my Sony D6503 using XDA Labs
FellipeSilvaRJ said:
Actually, I take at least 7 pictures with Camera FV-5/ 7 with stock app, with screen brightness full. Used WhatsApp and Telegram too, normally these apps and screen should be on top of the list. I have no idea of what the hell I do :silly:
Click to expand...
Click to collapse
F***ing 457mAh, there's something really wrong here
Sent from my Sony D6503 using XDA Labs

How Can I Get Notification's On Lock Screen

Hi,Guys how can i get notification on my lock-screen i have them enabled etc but they do not show on the lock-screen any ideas will be really appreciated
Notifications only work with magazine block screen
Sent from my ALE-L21 using XDA-Developers mobile app
Fedroid said:
Notifications only work with magazine block screen
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
is it a theme?how do i enable it ?
You can give this a try - http://forum.xda-developers.com/showthread.php?t=2641557
The app hasn't been updated by the dev in ages but it still works, even with marshmallow.
bumjrah said:
You can give this a try - http://forum.xda-developers.com/showthread.php?t=2641557
The app hasn't been updated by the dev in ages but it still works, even with marshmallow.
Click to expand...
Click to collapse
Did you get the marshmallow on the p8 lite ?I will try the app really sorry for the trouble caused
Bilal_Habib said:
is it a theme?how do i enable it ?
Click to expand...
Click to collapse
Execute themes app and choose default theme.
That is all.
Fedroid said:
Execute themes app and choose default theme.
That is all.
Click to expand...
Click to collapse
I use default theme and nothing Changers on lock screen plus I have. No theme by the name or even saying magazine and other help will be appreciated
I don't know if you are on MM yet but I noticed that there is a thing under App's (on MM) in settings where you can set what apps draw over e.g.. facebook chat bubbles. I think if you enable your apps that you want notifying you on lock-screen to draw over mode then it may show on lock-screen. Its working so far for my weather updates from google app... I could be entirely wrong and I am using a fairly wonky build of MM but I just thought I would offer my insight Best of luck bud.
Horacio55555 said:
I don't know if you are on MM yet but I noticed that there is a thing under App's (on MM) in settings where you can set what apps draw over e.g.. facebook chat bubbles. I think if you enable your apps that you want notifying you on lock-screen to draw over mode then it may show on lock-screen. Its working so far for my weather updates from google app... I could be entirely wrong and I am using a fairly wonky build of MM but I just thought I would offer my insight Best of luck bud.
Click to expand...
Click to collapse
I am not on marshmallow as yet waiting for the Ota
I'm sure MM will fix that for you bud!
I do know the struggle, waiting on OTA's for us in New Zealand is painful. On top of the fact that before I went MM I wasn't getting notifications at all, calls missed cause it wasn't bringing the call screen up...all sorts of havoc.
Worst comes to worst you could try factory restore, then do the theme thing that other guy mentioned. You should technically have a default, it's weird you are missing it.
Horacio55555 said:
I'm sure MM will fix that for you bud!
I do know the struggle, waiting on OTA's for us in New Zealand is painful. On top of the fact that before I went MM I wasn't getting notifications at all, calls missed cause it wasn't bringing the call screen up...all sorts of havoc.
Worst comes to worst you could try factory restore, then do the theme thing that other guy mentioned. You should technically have a default, it's weird you are missing it.
Click to expand...
Click to collapse
Let's hope I tried all that never work the phone is basically brand-new confused why!I managed to find under themes to download but when I download .Same thing lol
Try Next Lock screen from microsoft:
https://play.google.com/store/apps/details?id=com.microsoft.next

Categories

Resources