Related
Modifications for stock 4.4.2
drakeheart77 said:
Modifications for stock 4.4.2
Click to expand...
Click to collapse
I have found that custom ROMS/Kernels and much else for this phone to be sorely lacking. This is by no means an attack on my respected dev peers, simply an observation.
Throughout the woes of our limited forums I see a trend in the gripes about this little wonder.
I am offering my personal settings & preferences that MAY unleash what we can do here.
FIRST THINGS FIRST- Just forget needing buggy builds of TWRP for KK+ rom flashing. There's not much to flash, and TWRP 2.7.1.0 forced me to dl the KK stock firmware & start from square zero.
*NOTE FOR REASONS STILL UNKNOWN EVERY SINGLE PARTITION WOULD RESTORE- EXCEPT THE SYSTEM.
Enough said.
I am using CWM 6.0.2 for stability reasons, and have no issues.
Now I will begin the good stuff.
After my mods/tweaks etc, I am running about 97 apps with 3.9GB internal memory remaining, can go about 11hrs without needing to charge, give or take, and can multitask seemlessly with around 410mb free RAM at stationary.
Obviously, one needs to utilise the KK SD card fix. After this, begin:
Install /system/app/mover from Play Store & BE CAREFUL!!
I proceeded to begin moving bloatware preinstalled apps from being system apps to User apps, freeing essential system rom space & allowing for safe uninstall and transfer to ext sd.
Now on to build.prop.
Unleash what we can do here.
Here is the link to my build.prop zip. Please note all mods & adds specifically, as they are unique to the likings of this phone.
https://docs.google.com/file/d/0B-a-fg6mIteHakZfYXk1eklla3M/edit?usp=docslist_api
Next, I HIGHLY suggest the Override DNS for KitKat. Only one that works for 4.4 & above. Set to Google, which is also feasable in bud.prop, but my experience has been iffy with that, and this app flushes DNS cache w/o reboot and sets DNS KitKat specific.
GPS- FasterGPS.
Here is the link to the Advanced Settings data after basic configuration. The results speak for themselves.
https://docs.google.com/file/d/0B-a-fg6mIteHellndldvUG5Eb1k/edit?usp=docslist_api
Dl and rename to .txt to view.
I use RAM Manager Pro for memcleaning & management.
Use default option, the select custom afterwards to fine tune settings to preference.
If ANYONE needs recovery files for any soft brick needs AND has CWM, please PM me & I will upload mine.
Hope this gives some insight on how to begin using this guy properly.
Open forum. Ask/request away, add to it please!
Screenshots
RAM Manager Pro Custom settings that I use:
NOTE: Notice custom launcher in screenshots- by using /system/app/mover to convert Touchwiz to user, I freed up substantial rom space, mem, and performance. I use Apex Pro.
App Tools
Link to some utilities
Dl, unzip, rest is easy to figure out.
https://docs.google.com/file/d/0B-a-fg6mIteHeXowU1hTakRrZTA/edit?usp=docslist_api
I've begun modding my stock sgh t399 and I was wondering if u could talk with me a lil. I've seen massive potential over cost n this phone. Mainly don't understand build prop yet. Don't wanna brick it
Sent from my SGH-T399N using xda Forum
drakeheart77 said:
Screenshots
RAM Manager Pro Custom settings that I use:
NOTE: Notice custom launcher in screenshots- by using /system/app/mover to convert Touchwiz to user, I freed up substantial rom space, mem, and performance. I use Apex Pro.
Click to expand...
Click to collapse
You guys are in luck. .. the gods had pity and sent someone to steal my galaxy s3 and 5 and Tablet 7.0... so, I ended up with this phone. . But there's little to no development, especially for the metro variant. .. sooo... I'm doing a little work. ... look up .. team rejects.... you'll understand soon. ..good things coming. .
timmetal6669 said:
You guys are in luck. .. the gods had pity and sent someone to steal my galaxy s3 and 5 and Tablet 7.0... so, I ended up with this phone. . But there's little to no development, especially for the metro variant. .. sooo... I'm doing a little work. ... look up .. team rejects.... you'll understand soon. ..good things coming. .
Click to expand...
Click to collapse
Unjustified Dev is working on CM12 for this phone, but he's pretty much the only one. Whether you team up with him or you work independently, it'll certainly be good to have more people working on this phone. Bummer you had to lose your other devices though.
A different route
Hey all, thanx for the attention & activity in getting this thread moving.
I readily & always tell all I am not a Dev, I assist true devs here & there to work towards
stables, patches, fixing kernels, and so on.
That's out of the way, now on to the progress.
I have been using an AOSP deodexed stock 4.4.2 ROM, and praises to the efforts of
the community member, and much to my discredit I can't readily recall who this person
is to post a link to that thread, as is proper. oh well.
While the AOSP stock build is a big showing of progress, I say with a heavy heart that
it is very, very buggy.
What the positive effort was: It is debloated to such a level that upon a fresh install,
the user still has 4.2GB Internal Storage.
This, I've found, is the single most common misdirected goal and focus of efforts with
throw-away-yet-kinda-quality nocontract phone.
After I installed TB Premium, I discovered that the system ROM had around 182Mb available.
I now come to reports.
Every Stock 4.4.2 system app was still there, however the writer replaced a few (ie Camera
with Google Camera, for one) that completely eat up what precious limited RAM/
ROM performance we do have.
The build.prop showed only a few mods/edits, less than five.
The dalvik.vm.heapsize was 128m, heapstart was 8m, and growth limit 256mb.
That was same as stock. Speaking only for me, that was the biggest oversight that
tainted almost all efforts. Those sizes are entirely TOO big for this phone's britches.
If I seem like I just will not stfu, I can't blame you.
I feel I have to be as thorough as possible out of respect for my colleagues.
Now, since I am using Chrome from my device for all of this, you all will find up look oads
and images following this reply, fyi.
My first inspection was to install SetCPU, in small hopes that a customized kernel
had magically came. I am BEGGING for more governors and I/O schedulers, our less-than-
primitive 5/3 is downright insulting.
Kernel supports absolutely no tweaks, VM swap, O/C or min freq. U/C.
My goal is to take the only alternative given on 4.4.2 at all, and make lemonade.
System/app mover from Play Store.
There are countless threads on what is & isn't safe, my mods on that are my prefs.
In the end, I was able to free ROM up to just over 406MB. I can't begin to describe
the difference.
On to build.prop
To compliment my new device I just got, I set dalvik.vm sizes to a less audacious level.
I chose the more conservative of 8m, 64m, 128m. *Note any less on any 3 values, your FCs
will never cease.
Next, I made a few other edits I've favored on several devices, will upload my .txt.
Use of SD Fix for KitKat, along with Force2SD paid, I have 104 apps, many being very large
games, as well as the evil Chrome and FB storage rapists, all Google offenders at that.
I have a smug 4.32 GB Internal Storage available, saving me much embarassment by killing all my ROM wins.
AdAway 2.9 for KitKat, Override DNS for Root Users, the ONLY DNS mod that works on
KitKat, FasterGPS, Seeder 2.0, Root Explorer paid, TB Pro, NG Cache Cleaner, SignalGuardPro
and SD Booster make up my arsenal.
Touchwiz & Trebuchet are gone, I use Nova Launcher Premium.
Restoring TB app backups from external SD put my phone into bootloop.
I am clueless as to any reason why.
Using ANY root sysApp delete to debloat will also softbrick.
System/App Mover seems to be the only way. I speak from a few experiences and Nandroid
system part. restores.
I COMPLETELY CONDEMN MY PRIOR CONVICTION TO CWM.
I completely f*"$ed that up.
TWRP 2.8.0
NOTHING ELSE.
I even attempted a rash Aroma Installer to compensate for MusicFX being gone.
Ac!D Sound Mod.
Worked. And Improved.
RAM Manager Pro is gone too. I've found my build.prop edits are just right.
Any app tweak mucks it up.
Battery Callibrate Root, free on Store. Another win on battery life.
This is the most I can really do now.
Without a custom kernel, we'll be left behind like nearly all Prepaids, non flagships.
That's MY report, I beg for input/feedback/comments/criticism/ridicule, whatever.
Next Replies will be build.prop.txt, gps.conf, screenshots.
Follow up links scrnshots
My modded gps.conf, using FasterGPS
https://docs.google.com/file/d/0B-a-fg6mIteHellndldvUG5Eb1k/edit?usp=docslist_api
My build.prop txt
https://docs.google.com/file/d/0B-a-fg6mIteHWEd1U2pFNUJ5emc/edit?usp=docslist_api
some srcnshots are attached as well.
Plz PM or Reply if I can provide anything else.
DISREGARD BUILD.PROP UPLOAD FROM PREVIOUS.
I missed some critical errors & edits that will negatively impact the phones performance and memory allocation, dang my bad all!
I've been at this phone non stop it seems since my previous post. Need to be less trigger-happy with reporting progress smh.
I'm uploading what I promise is my finished build.prop, for real this time.
Since I am sticking with this stock AOSP build, I was able to successfully flash an Aroma recovery installer mod, the Ac!d Sound Engine.
I should note that the only EQ offered that will work is Nooxide. Awesome Beats EQ is not designed for 4.4 platform.
The Ac!d enhancement and Dolby Mod both have made positive enhancements.
The Play Store that is built in to the .zip install MUST be replaced. Initially the writer included that Play Store will FC upon install, but clearing cache/data in app manager would fix, and was correct.
I can't assume that I'm the only one who has caught this, but I am reposting in writer's thread that Play Store will update to 5.4 build, and it becomes all but unusable.
Any Play Store update beyond 5.2... has never functioned properly for me, it seems Google is making a path for Lollipop migration, and the Play Store versions 5.3 and above are, I believe, geared for 5.0 platform, but still giving it to 4.4 users.
I downloaded a Play Store 5.2 apk from a third party site, saved to my external.
What I now believe is the present solution to this situation is this;
Get 5.2.** apk, keep it on External, or readily available.
Get System/app mover
Root Explorer
After flashing, use System/app mover, and convert Play Store from system to user app.
Reboot. Uninstall Play Store as regular user app. Install 5.2.** apk. open System/app mover & convert Play Store to system app. Hit "cancel" on reboot prompt in app. Go to app manager, Google Play Services, clear cache and ALL data under "Manage Storage". Then reboot.
This has fixed, for good, my issues.
As stated before, use System/app mover at your own discretion and what is your preference, just make a backup first and understand what you are doing.
I am satisfied with what I've worked out, and do not have any other work to do that I can see.
Thanks all.
Next reply is RIGHT build.prop
apologies again.
Drakeheart77
https://docs.google.com/file/d/0B-a-fg6mIteHU081Uko0MU9ENms/edit?usp=docslist_api
Update- have recently corrected setting dalvik heapsize and limit to lower settings, causes many MANY problems, fc's etc.
Set to 8m, 64m, 256m.
Absolutely primed.
Further system mods gave me 433Mb free ROM space, and around 4.1Gb internal storage free.
Happy thus far.
If anyone is keeping up on CM12 build, share to this forum please.
I wish to aid the dev in any way possible.
drakeheart77 said:
Update- have recently corrected setting dalvik heapsize and limit to lower settings, causes many MANY problems, fc's etc.
Set to 8m, 64m, 256m.
Absolutely primed.
Further system mods gave me 433Mb free ROM space, and around 4.1Gb internal storage free.
Happy thus far.
If anyone is keeping up on CM12 build, share to this forum please.
I wish to aid the dev in any way possible.
Click to expand...
Click to collapse
I am using the CM12 build and its pretty good. If you havent tried it yourself you should its pretty stable. I do like to see that you are working on the stock rom though. I like that one too just too much bloatware and not enough free space, so this is good!
I've tried keeping tabs on that here & there, can't seem to find dl link for latest/stable build. I've given up on this stock ASOP, just flashed back to stock 4.4.2. Added all those mods I've been posting, runs 110% better.
Would you be so kind as to point me the right way to dl this CM12? I'm looking again, but it would help a lot lol.
Ty for your participation.
drakeheart77 said:
I've tried keeping tabs on that here & there, can't seem to find dl link for latest/stable build. I've given up on this stock ASOP, just flashed back to stock 4.4.2. Added all those mods I've been posting, runs 110% better.
Would you be so kind as to point me the right way to dl this CM12? I'm looking again, but it would help a lot lol.
Ty for your participation.
Click to expand...
Click to collapse
Here's a link to the cm12 development thread http://forum.xda-developers.com/android/development/dev-cyanogenmod-porting-t2918432
And here's the link to unjustified dev's samsung galaxy light folder that has the latest cm12 build http://forum.xda-developers.com/android/development/dev-cyanogenmod-porting-t2918432
Thanks
Ty I actually found it shortly after I requested that from you.
Been running it since then, a LOT of trial-and-error runs, but I've
managed to get it running just right for me, almost...
Fixed constant soft reboots by setting location to device only
Have no issues at all with phone calls, only the persistent
proximity during a call, I must position my phone a certain way,
my cheek kept touching the speaker and mute icons.
Any advice on that is welcome, I've tried the build.prop edit:
ro.lge.proximity. delay=25
mot.proximity.delay=25
without much luck lol.
And, the MMS issue. I'm on MetroPCS, so I have set the default
APN accordingly.
After researching CM Mod forums & searches, the only
solution anyone has ever provided is to use third-party SMS,
Textra was the specific example.
It seems to be arbitrary, I've had continuous successful deliveries,
then shortly after they fail every time..rebooting has AND has
not fixed this...too random of success/failures to pinpoint myself,
but I by no means am a master at this ☺.
Any help or ideas are most welcome!
Did you clean install? I set my APN to metro fast or whatever its called and have had no problems with texting. The only issues I have other than the proximity that you mentioned, is that videos don't always play. Plus the newest Netflix doesn't work and neither does play TV and movies. Both force close when I try to open
Sent from my SGH-T399N using XDA Free mobile app
Yeah when I had cm12 installed I had no problems with mms after changing the apn to metropcs lte or whatever it's called.
Well, I've since returned to Stock KitKat w/ root & modifications. The Cm12 was nifty at first, but in the end I desire functionality over custom.
Too many apps/features that I want & use often just didn't work unfortunately. Oh well, I'm still willing to pitch in & help out devs!
Maybe you could help develop the cm12 rom. Unjust lent his galaxy light out, and idk if he got it back yet
Sent from my SGH-T399N using XDA Free mobile app
Cyanogen OS 13.0 is rolling out now for the OnePlus One
Cyanogen OS 13.0 has started rolling out, beginning with the OnePlus One and will be followed by other devices. Here’s a look at what’s in this update.
Tastes like Marshmallow
Cyanogen OS 13.0 is built on top of Android 6.0 Marshmallow. Marshmallow offers a number of useful features that Cyanogen leverages, including:
Doze
Doze increases your battery life by putting your device into hibernation mode when the device is not in use. When in Doze mode, your device will limit CPU and network intensive tasks to conserve battery life. You can now forget to charge your phone and still have juice left for the next day!
Permissions control + Privacy Guard
Marshmallow brings new privacy features to the operating system, enabling the user to allow or disallow a particular app from accessing certain device information, such as your contacts or camera. Permission control is complementary to our ever-popular Privacy Guard, which gives users more fine-grained control of what they share and with whom.
App Standby
App Standby determines which apps have not been used recently on your device and then puts them into sleep mode so that these apps no longer consume precious battery.
Quick Settings tiles
An existing popular feature of Cyanogen OS is Quick Settings tiles management, which has been added to Marshmallow in this update. This allows you to customize layout and options directly via the Quick Settings panel, using configuration items such as ‘enlarge first row’ and ‘show weather’ which are now present on Quick Settings panel while in edit mode, and live reordering of tiles.
Truecaller mod for Messaging
Cyanogen OS is already integrated with Truecaller for an enhanced dialer experience — you are able to screen calls via caller ID and block unwanted spam directly from the native Dialer. This global partnership now extends the Truecaller mod into the Messaging app. The Truecaller mod is available only on Cyanogen OS. With Truecaller for Messaging, you can:
Know who is texting with the power of the Truecaller network containing over 2 billion phone numbers.
Identify spam and block them directly from within the Messaging app.
Protect others by reporting spam to the Truecaller community.
Truecaller is integrated directly into the Messaging and Dialer apps. To enable the Truecaller mod, users can accept the Truecaller permissions from Dialer or access the Truecaller settings in Dialer. There is no need to install a separate app and you can turn Truecaller off at any time.
The Truecaller mod for Messaging is available on any device running Cyanogen OS 13.0 and up. The MOD platform is discussed in our previous blog post.
There are plenty of other new and improved features in this OS update on top of the hundreds of features you have come to expect from Cyanogen OS. Among these, you will also notice an emphasis on performance improvements that make the experience even smoother than before. We are looking forward to bringing Cyanogen OS 13.0 to users around the world beginning with the OnePlus One.
Must be nandroid back up and put it somewhere in a safe place. Just incase there is a problem you have your own back up.
Must be stock and fully unroot.
Official Download Link: http://builds.cyngn.com/incremental/bacon/cm-bacon-e36dd78050-to-64003595ee-signed.zip
Stock Recovery: https://www.androidfilehost.com/?fid=24459283995316112
Wait what, it has been rolling out from the start of this month
Transmitted via BACON
COS 13 6.0.1 incremental update ota just flashed. 6.0.1 with security patch level may 1
Duplicate of Cyanogen os 13 is coming --- ceo of oneplus
Please keep one thread for CM 13 Discussion. Thread Closed.
Hey guys,
up till today I'm still using a Samsung Galaxy Note 3 with Android 4.3.
It is modded to the max to exactly meet my needs and "paranoia":
- Custom Rom TouchWiz based rom
- Custom Kernel with some special script based tweaks (for example: MAC randomization everytime I turn Wifi on - handy for time limited free access points and to prevent beeing tracked etc.)
- Full Disk Encryption with a password different than my unlock pin (so when the device is off it requires a long password, but when on only a shorter pin)
- Xposed with the "old" Xprivacy Pro, Greenify and lots of other useful modules (like device shutdown after x failed amounts of unlock password etc)
- Lightning Launcher (allows "pinned" widgets that do not scroll - like the clock always beeing shown on top of all my homescreens) and custom widgets made with UCCW
- Button mods (double tap menu button turns on/off auto rotation, long menu switches last two apps, long back kills foreground app etc.) and homebutton mod to turn on flashlight when held while device is locked (to turn it on blindly / without looking)
- Sidebar Launcher Appsi for all my apps (and using xprivacy to prevent certain apps from showing up in the list at all)
... etc etc.
It took me a long time to set up everything and whenever I bought a new phone I sold it soon after because they never could be modded that hard like my old note 3 could be. (not to mention the built in batteries - I HATE that so much about all new devices).
Long story short: The Mi A1 could maaaaybe finally be the device to replace my Note 3 - but for that I need to be able to really mod it hard again hehe.
What really is important to me is beeing able to use xposed and xprivacy (unfortunately the xprivacy lua is not that good as the old one as far as it reads in the description), controlling the device encryption with my own 20+ Character Passphrase while still having a shorter pin when the device is booted up (and it beeing "full device encryption" not just file based if that still exists?). Removing all google apps except the playstore (and the account manager - dont even want the google play services crap) and preferably beeing able to install modded playstore which does not autoupdate itself etc.
-----
Do you guys think this is possible at all? And if so - should I stay with a 7.1.2 based rom or go for oreo? I mainly care about modability as I explained..
Hope someone is in the same boat or at least knows enough about this phone and the roms/kernels/availabe and working xposed mods to help me out.
There's pretty much no development for Nougat so it would be better if you were to get on oreo
Modabillity is pretty great with this phone so far
Look around on xda and see if you like it
berezker said:
There's pretty much no development for Nougat so it would be better if you were to get on oreo
Modabillity is pretty great with this phone so far
Look around on xda and see if you like it
Click to expand...
Click to collapse
but does xposed and stuff like modded playstore etc exist/work for oreo? and do you maybe know if its possible to have a different boot password than just the unlock pin when device is powered on?
and how about rootcloak and stuff like that? On my old note i can pretty much fake everything to apps and prevent root to be detected or feed them with fake data through xprivacy - but does this all still work to the same extend on the newer android versions? This safetynet bull**** has been around since when again? Can that still be fooled?
zroice said:
but does xposed and stuff like modded playstore etc exist/work for oreo? and do you maybe know if its possible to have a different boot password than just the unlock pin when device is powered on?
and how about rootcloak and stuff like that? On my old note i can pretty much fake everything to apps and prevent root to be detected or feed them with fake data through xprivacy - but does this all still work to the same extend on the newer android versions? This safetynet bull**** has been around since when again? Can that still be fooled?
Click to expand...
Click to collapse
I'm not really sure about modded play store and boot password stuff but what I do know is that you can use Magisk (Similar to SuperSu + Extra useful mods) to hide root from certain apps that you choose
Xposed does work perfectly fine but it depends on the modules and whether they work on oreo. If not, magisk modules are also pretty good
If you happen to own a phone that you can flash Oreo on, (see, Lineage 15), then you can pretty much know and discover everything about Oreo and how modding works on it
My background with android is long and rocky.
A long time ago in a galaxy far away, I had a Samsung Galaxy S, then a S2.
I can remember a Google Nexus phone in there somewhere.
Then at some point I switched over to Windows Mobile for many years.
A couple of hears ago I came back to android with a Samsung Galaxy S8+ and I hated it.
Recently I upgraded to a OnePlus 6T McLaren and here I am.
I had been expecting to see android happily use up 7, 8 or even 9GB of ram before the background task manager would begin to kill tasks.
Except that I seldom saw android use much more than 5GB of ram.
And worse, background tasks were being killed on a regular basis.
Widgets would stop working overnight, or even in just a few hours.
Spotify would close while a playing a playlist.
A quick search on XDA reveals that many users believe that Android will just use up as much ram as your phone has.
However, that is simply not true.
And so, I began my quest to have Android use as much ram as the phone could provide.
In my case, 10GB.
- I understand that there is an inherent trade-off between keeping background apps running and battery usage. I can live with extra battery usage in exchange for keeping my widgets running or Spotify running for an entire playlist.
- I realized very quickly that in order to achieve the results that I was looking for that the phone would have to be rooted. So rooting was one of the first things that I did.
Step 1.
I started with the basic stuff that a quick google search would provide;
- Settings -> Battery -> Battery Saver (off)
- Settings -> Battery -> Adaptive Battery (off)
- Settings -> Battery -> Battery Optimization -> widget app (don’t optimize)
- Settings -> Battery -> Battery Optimization -> Spotify (don’t optimize)
- Settings -> Battery -> Battery Optimization -> Advanced Optimization -> Deep Optimization (off)
- Settings -> Battery -> Battery Optimization -> Advanced Optimization -> Sleep standby optimization (off)
- Settings -> Apps -> Widget app -> Battery -> Background Restriction (app can use battery in background)
- Settings -> Apps -> Spotify -> Battery -> Background Restriction (app can use battery in background)
This helped but not enough to make the widgets or Spotify usable.
Step 2.
I supposed that my specific background tasks that I wanted to keep running were being killed because of the many other apps that were running in the background.
I searched for and found Tomatot DeBloater scripts for the Oneplus 6.
Excellent! Just what I was looking for.
I chose the Tomatot-Debloater-OOS-Light-2.3.zip and installed it.
This helped some more but not enough to make the widgets or Spotify usable.
Step 3.
I realised that there were still some apps running in the background that I didn’t use or want.
So I used Titanium Backup to freeze the following apps;
- Calendar
- Calendar Storage 9
- Contacts (O+)(I replaced with google contacts)
- Dashboard
- Drive
- Face Unlock
- Gboard
- Gmail
- Google
- Google partner setup 9
- Google play music 8
- McLaren AR
- Messaging (O+)(replaced with google messaging)
- OK google enrollment 9
- Oneplus system 1
- Youtube
Perfect! These apps were no longer competing for phone resources with the apps that I wanted to run.
This helped some more but not enough to make the widgets or Spotify usable.
This did make the phone feel faster and smoother.
The phone is much more responsive and fluid to my input.
This made me realize that the apps were being closed not due to a lack of phone resources, but a background task manager being aggressive.
Presumably for battery saving purposes.
I changed my focus to adjusting that background task manager.
Step 4.
Enable the recent screen ‘LOCK’ on the widget app and Spotify.
This didn’t do anything for me.
Everything that I’ve read on it says that it just stops the task from being killed when you click on kill all tasks.
The lock doesn’t lock the task from being killed by the background task manager.
Step 5.
Further google searching led me to believe that the OEM kernel was limiting background tasks.
I choose ElementalX-OP-3.09 and the EX Kernel Manager.
I had to read a lot of google university material to make any sense of the settings in here.
I’m not sure that I fully understand even now.
Eventually, I ended up with the following settings;
Memory
- Adaptive Low Memory Killer (disabled)
- dirty ratio (20)
- dirty background ratio (5)
- min free kbytes (12398)
- vfs cache pressure (100)
Memory -> Low Memory Killer
- apply on boot
- Foreground app (72mb)
- Visible apps (90mb)
- Secondary server (108mb)
- Hidden apps (200mb)
- Content Providers (587mb)
- Empty apps (783mb)
This helped a lot.
This almost made the phone usable to the state that I wanted.
But the widget and Spotify would still stop running overnight and by morning the apps would have to be reopened to get them to run again.
At least the apps would run most of the day without being killed.
Still not the behaviour that I expected from a phone with 10GB of ram.
Ram usage was still not going much over 5.5Gb even if I opened up many apps at once.
Can I ever get ram usage up to the 10Gb that I have?
Step 6.
The last thing that I tried yesterday afternoon was to increase the background task limit in the build.prop.
ro.vendor.qti.sys.fw.bservice_limit=5 (changed it to 60)
ro.vendor.qti.sys.fw.bservice_age=5000 (changed it to 10000)
Yes, I know that I am on PIE and there isn’t supposed to be any effect.
No, I don’t know yet if this had any effect.
I am hopeful.
The widget app didn’t close last night, but Spotify did.
I am getting closer!
This is the best that I could do on my own without asking for help.
So here I am posting my question and asking for help.
How do I get the apps that I want to run to not be killed by the background task manager?
OR
How do I get the phone to use the 10GB of ram?
I feel that I am missing something.
With any luck, one of you smarter persons will be able to point it out to me.
As an aside from all of these changes the phone feels very smooth and fluid.
Except for apps closing that I don’t want to, this phone is a great experience and a pleasure to use.
Apps that I want to run are staying open much longer then before I started.
It’s now just an overnight issue.
And getting the phone to use over 6Gb of ram.
I would suggest that I am 90% happy with it now.
KERNAL: ElementalX-OP6-3.10
ROM: STOCK OOS 9.0.11
PHONE MODEL: 6013 O+6T McLaren
Tomorrow I may try making this change to the build.prop file;
ro.vendor.qti.sys.fw.bservice_enable=true to false
Don't know if it will help or not.
Wow dude, interesting read, i will sign up for notifications from this thread hoping you get your answer because i have the exact same problem but with my work app, throwing it all out of whack and making me a target to big fines (in the $1,000's) and potentially reducing my marketability!
The attached screenies are from before i realized that the app getting killed in the background is what causes the problem (I've left it in the foreground HOURS a few times and it works perfectly!)
UPDATE:
Good news!
I seem to have solved my issue.
Time will tell for sure though.
But this morning and all day today, Spotify and the widget app have been running without closing.
AND I have seen memory usage up to 6.8GB used.
Here are the further steps that I took;
- ro.vendor.qti.sys.fw.bservice_enable=true (changed it to false)
I didn't really notice much of a change.
But then I noticed that perhaps the limit of 60 tasks was not high enough.
I seem to have that many apps open and limiting to just 60 may be an issue.
- ro.vendor.qti.sys.fw.bservice_limit=60 (changed it to 120)
THIS!
This seemed to have worked for me.
All apps seem to be open and be staying open.
Today I got a message/warning from android telling me that the widget app is consuming the battery in excess but I ignored the warning and android did not close the app or stop the widget from running.
I will keep an eye on the phone for the next few days to confirm that this actually solved my issues.
My next step will be to see what effect if any this has had on my battery usage.
I am curious to see if it's all that bad...
geeksquad2 said:
UPDATE:
Good news!
I seem to have solved my issue.
Time will tell for sure though.
But this morning and all day today, Spotify and the widget app have been running without closing.
AND I have seen memory usage up to 6.8GB used.
Here are the further steps that I took;
- ro.vendor.qti.sys.fw.bservice_enable=true (changed it to false)
I didn't really notice much of a change.
But then I noticed that perhaps the limit of 60 tasks was not high enough.
I seem to have that many apps open and limiting to just 60 may be an issue.
- ro.vendor.qti.sys.fw.bservice_limit=60 (changed it to 120)
THIS!
This seemed to have worked for me.
All apps seem to be open and be staying open.
Today I got a message/warning from android telling me that the widget app is consuming the battery in excess but I ignored the warning and android did not close the app or stop the widget from running.
I will keep an eye on the phone for the next few days to confirm that this actually solved my issues.
My next step will be to see what effect if any this has had on my battery usage.
I am curious to see if it's all that bad...
Click to expand...
Click to collapse
Nice find, I checked my build.prop and found this. No wonder my apps are killed
Code:
#ifdef VENDOR_EDIT
#[email protected] modify for app memory
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
#endif/*VENDOR_EDIT*/
EDIT: I see a lot of custom ROM's have "ro.vendor.qti.sys.fw.bg_apps_limit=60" to the build prop, I wonder if that going to make a difference
UPDATE:
I am a silly goose.
I broke a cardinal rule while troubleshooting.
I may have had a few too many wobbly pops and made two changes at a time, thus when change was affected, I was unable to determine properly which change caused the affect.
The rule is, "only make one change at a time when testing".
Yes, all of my apps stay open all the time.
I am getting the behaviour that I was looking for.
However it wasn't necessarily changing the build.prop bgservice_limit from 60 to 120 that did it.
Let me back up a bit.
Earlier I had suggested that locking an app to the recent screen didn't do anything for me, and that in my reading it only locks the app from being killed by you when you try to close it manually.
However in reading up on the oneplus framework-res.apk I found a reference to an oneplus whitelist of apps that will never be killed, and a reference to the recent screen app lock that suggests that oneplus will add a locked app to the whitelist and not kill it.
In the course of a single day, I had inadvertently edited the build.prop and locked the widget app to the recent screen thus breaking the one change at a time rule.
So the next morning and the following days when all apps were staying open I attributed it to changing the build.prop not realizing that it could also have been the app lock.
Last night I realized my mistake.
I unlocked the widget app from the recent screen and went to bed.
When I woke up this morning the widget app was not running for the first time in days.
Also the notifications that I was receiving about the widget app consuming excessive battery have stopped.
It would appear that I was wrong in my earlier observations regarding the app lock mechanism.
It appears to be very useful for keeping apps running all the time.
Did changing the build.prop have any affect on keeping apps open?
Maybe?
I have noticed that my battery life has gone for a complete ****.
I can barely get 24 hours out of the phone.
Worse is that it doesn't matter if the screen is on or not, battery usage remains the same.
i.e. with the screen off and the phone put down, battery life appears to be used at the same rate as when the phone is in use.
I had expected the battery life to be not as good, but I didn't expect it to go to for a **** that badly.
There must be a balance between aggressive app management and acceptable battery life.
The phone didn't display this behaviour until I changed ro.vendor.qti.sys.fw.bservice_enable=true to false.
I think that today I will change ro.vendor.qti.sys.fw.bservice_enable= back to true and observe the battery tomorrow.
kantjer said:
Nice find, I checked my build.prop and found this. No wonder my apps are killed
Code:
#ifdef VENDOR_EDIT
#[email protected] modify for app memory
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
#endif/*VENDOR_EDIT*/
EDIT: I see a lot of custom ROM's have "ro.vendor.qti.sys.fw.bg_apps_limit=60" to the build prop, I wonder if that going to make a difference
Click to expand...
Click to collapse
I think that ro.vendor.qti.sys.fw.bservice_limit= and ro.vendor.qti.sys.fw.bg_apps_limit= are essentially the same thing, except for android versions.
ro.vendor.qti.sys.fw.bg_apps_limit= is for Android 7: Nougat and below.
ro.vendor.qti.sys.fw.bservice_limit= is for Android 8: Oreo and above.
Someone more knowledgeable than me should chime in here though.
Do you think any of this could have to do with the way the phone keeps disabling push in Gmail? (Every other day I need to set my O365 exchange in Gmail back to push because it automatically changes to the default of checking every 30 mins.)
Any conclusion?
Did you guys manage to solve this issue please by editing the build prop?
Latest smurf kernel rc14b seems to have solved the RAM management issue. I haven't had any apps closing in background since using it.
thank you for the thread!
What did you find in the end?
How did you set this ?
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
So what's the verdict on the buildprop edits? Do they make a difference?
I notice that sometimes my on-going weather notification doesn't update, or gets killed off. I also have an app that controls rotation per app, and that also seems to stop doing it's thing after a while.
Just want to share. If you are rooted with Magisk, try appsystemizer module. System apps don't get killed by oneplus as aggressively. Tried it with accubattery and it works.
I am so glad I stumble across this, I just want to say, changing
ro.vendor.qti.sys.fw.bservice_limit=5 to 120
ro.vendor.qti.sys.fw.bservice_age=5000 to 10000
Keep apps in ram for much longer then original! For me the battery life is unaffected, might even be better.
scloss84 said:
I am so glad I stumble across this, I just want to say, changing
ro.vendor.qti.sys.fw.bservice_limit=5 to 120
ro.vendor.qti.sys.fw.bservice_age=5000 to 10000
Keep apps in ram for much longer then original! For me the battery life is unaffected, might even be better.
Click to expand...
Click to collapse
Also want to solve this issue.
On which OOS Version you are? (i am on 10.3.1)
Does this really work in newer OOS Versions?
I have read elsewhere that those settings dont work on newer versions, sadly, cant find the thread/source.
thx
pOpY
popy2006 said:
Also want to solve this issue.
On which OOS Version you are? (i am on 10.3.1)
Does this really work in newer OOS Versions?
I have read elsewhere that those settings dont work on newer versions, sadly, cant find the thread/source.
thx
pOpY
Click to expand...
Click to collapse
I'm actually Oneplus 6, OOS 9.0.9.
I also read that it doesn't work on Android 10 because magisk doesn't mount /system in Android 10, but there is a magisk module workaround that you can use. And hopefully magisk will update in the near future to fix that. Just google "Android 10 can't edit build.prop" and you'll find heaps of info.
This is what I have in my build.prop file and it seems to help. I have Oreo it works great on my phone I don't know about later versions of Oreo.
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_age=5000
ro.vendor.qti.sys.fw.bservice_limit=5
ro.sys.fw.bg_apps_limit=64
All you want to know in one place about
Android Q
General info: https://android-developers.googleblog.com/2019/03/introducing-android-q-beta.html | https://www.google.com/android/beta
Opt In/ Opt Out your Pixel device(s): https://www.google.com/android/beta#devices Enable OTA Updates (You will get the beta updates like usual updates)
System images: https://developer.android.com/preview/download
Official Reddit forum from Google: https://www.reddit.com/r/android_beta/ for Bug reporting and solutions
If you manually flashed Android Q on your device by downloading the image from developer.android.com, you won’t receive updates automatically unless that device is also opted-in to the Android Beta Program for Pixel on the Opt In URL.
Using OPT out and returning to Pie the device will be facotry reseted:
You will not be able to unenroll and revert back to a lower public release version of Android without first wiping all locally saved data on your device. You may also encounter issues restoring a backup.
You will NOT receive separate monthly security updates while on a beta build.
Update working fine from Pie. Data and settings are remain.
Rooting: https://www.xda-developers.com/root-android-q-beta-google-pixel-pixel-2/
Magisk: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Hide back Button: https://www.xda-developers.com/android-q-gestures-back-button/
System seems stable. Call, SMS, Network, Bluetooth, Audio working fine.
Problems / Bugs
- Laggy Camera on all Pixel devices. (I can confirm It is MUCH slower than Pie. First pic about 4-9 sec)
- Slow(er) HDR+ picture processing. New feature: Dynamic depth format for photos
- Google is deprecating the Android Beam API used to share files with NFC
- Now playing not working (For me)
- Edit button on screenshot notification NOT working
- No options to block numbers in dialer or anywhere else
- No info about the charging estimated time
- Built in Screen recording in broken: FIX: https://www.androidpolice.com/2019/...t-in-screen-recording-but-its-broken-for-now/
- Android Q's Dark Mode Breaks Google Photos
2019. March 15.: Live wallpapers with cloud updates are broken FC in every second reported by many users
- Not working apps: https://www.reddit.com/r/android_beta/wiki/index: Some banking apps will not work in this beta, but Google Pay will work!
General App Compatibility Issues
Google Apps
Android System Webview (Beta users should leave the program)
Files by Google
3rd Party
AirWatch Hub
Boxer
Chase
Citrix Secure Hub
Evernote
Fate Grand Order
Firefox (non-nightly builds)
Huntington Bank
LastPass (app loads, major functionality issues)
Lloyds Bank
LinkedIn
Plex
PokemonGo
Samsung Galaxy Wear App
Syncthong
TELLO
Trials Frontier
WeChat
ZMODO Security Cameras
Other Notable Issues with Apps
Android Messages - MMS photo quality degraded
Google Photos & Dark Mode (Cannot read any text, logos are hidden)
MapMyRun will not work in the background (Q Location Permission Changes)
Improvements:
- "Always on" redesigned: https://9to5google.com/2019/03/13/android-q-aod-music/ Lift to wake, and double tap now ignores Always on display and get you directly to lock screen (if any) (This is no improvement for me)
- Much faster finger print reading
- Much faster face recognition
- Play Music lock screen wallpaper redesigned (It is just broken for me)
- New guesture: https://9to5google.com/2019/03/13/android-q-improved-multitasking-gesture/
New Features:
○ System-wide Dark Mode:
Solution 1:
- Use the Battery Saver to Enable Dark Mode.
Solution 2:
- Use ADB to Enable Dark Mode in Android Q
Code:
adb shell settings put secure ui_night_mode 2
- Use ADB to Disable Dark Mode in Android Q
Code:
adb shell settings put secure ui_night_mode 1
- Use ADB to AUTO Dark Mode in Android Q
Code:
adb shell settings put secure ui_night_mode 0
Solution 3:
Before the update set the device theme to Dark in the developer options.
The option removed in Q so you will not be able to modify it after the update.
○ Device Theming:
In the end of the Developer Settings you can find the options:
- Color
- Font
- Icon Shape
Only a few settings. You can play around
○ Time to read
In Settings -> Accessibility You can set the notifications timeout
○ Sharing Shortcuts
New sharing options and redisgned interface
○ Wi-Fi sharing via QR Code
Android Q now allows you to share your current Wi-Fi connection simply via a QR code
○ Feature Flags in developer options
https://www.reddit.com/r/android_beta/comments/b0xmio/feature_flags_hidden_options_and_what_they_do/
https://9to5google.com/2019/03/14/android-q-beta-1-feature-flags/
Desktop mode:
https://www.xda-developers.com/android-q-desktop-mode/
More from Google:
Foldables and innovative new screens
More privacy protections in Android Q
Giving users more control over location
Settings Panels
Improved peer-to-peer and internet connectivity
Wi-Fi performance mode
Camera, media, graphics
Dynamic depth format for photos
New audio and video codecs
Native MIDI API
ANGLE on VulkanNeural Networks API 1.2
ART performance
More to come...
eBENdre said:
All you want to know in one place about
Android Q
Problems / Bugs
- Laggy Camera on all Pixel devices. (I can confirm It is MUCH slower than Pie. First pic about 4-9 sec)
- Slow(er) HDR+ picture processing. New feature: Dynamic depth format for photos
- Google is deprecating the Android Beam API used to share files with NFC
- Now playing not working (For me)
- Edit button on screenshot notification NOT working
- No options to block numbers in dialer or anywhere else
- No info about the charging estimated time
- Built in Screen recording in broken: FIX: https://www.androidpolice.com/2019/...t-in-screen-recording-but-its-broken-for-now/
- Android Q's Dark Mode Breaks Google Photos
.
Click to expand...
Click to collapse
Just to help out a bit, if possible:
Camera seems to be fine on my P2XL - though I have not enabled any HDR+ or raw settings.
Now Playing is working for me, grabbed the theme song off the show I was watching last night.
Markup "edit" button can be fixed. Clear data in markup, open photos and use markup from within that; you should get a permission request. (simply going into permissions on the markup app and enabling any/all may work as well, but is untested)
In dialer/recents, tap the number, and choose block from the drop down menu. I am in the beta for the Google phone app - so that may be part of it. Dirty flash may also affect this.
Clarification only: Photos is broken in dark-mode, but only in that all options dialogs/drop-downs are white text on white background. Other than that, you can still browse photos/albums, etc.
For clarity: My device is the Pixel 2 XL and Q was installed via factory image with full wipe (no dirty flash), and I did not restore from any backups.
Camera is fine for me on 2xl. Nothing different. HDR+ works as normal so does raw DNG.
Mr Patchy Patch said:
Camera is fine for me on 2xl. Nothing different. HDR+ works as normal so does raw DNG.
Click to expand...
Click to collapse
Thank you. I'm on dirty upgrade. I will reset my phone soon. I will test it again.
eBENdre said:
Thank you. I'm on dirty upgrade. I will reset my phone soon. I will test it again.
Click to expand...
Click to collapse
You should check 9to5 Google they have some more adb commands for stuff like the different clocks for aod and how to use swipe left to go back
kevtrysmoddin said:
You should check 9to5 Google they have some more adb commands for stuff like the different clocks for aod and how to use swipe left to go back
Click to expand...
Click to collapse
thanks, I will add more later. Swipe left already on the list btw
Much faster fingerprint?
It already feels almost instant in Pie, what can they improve?
eBENdre said:
Problems / Bugs
- Now playing not working (For me)
- No info about the charging estimated time
- Built in Screen recording in broken: FIX: https://www.androidpolice.com/2019/...t-in-screen-recording-but-its-broken-for-now/
- Android Q's Dark Mode Breaks Google Photos
Click to expand...
Click to collapse
Now playing is working for me - just not displaying on the lock screen. I just got home form a birthday party, and every song the DJ played is in my NP history;
In addition to the charging time estimate, the estimate in the pull down notification area is completely off base compared to the estimated time left in Settings --> Battery;
My built in screen recording works for me, and has worked since I enabled it from the Features flags in Developer Options;
No issues with Google Photos with dark Mode. Caveat: I had dark mode enabled in Pie, and took the Q DP1 OTA over that Pie install;
I found that there is a microphone icon at the top left when selecting Panorama photo mode that I never saw before (was that introduced with Q DP1, or just a very recent Google Camera update?)
I've not noticed a discernible slowdown in the Camera app (and I always use HDR+ / Night sight for my photos), but I have noticed that when I try to view a picture / video, particularly like an MMS in Messages / Google Voice, the phone is extremely slow and laggy.
@eBENdre just got xl 2 ,prerooted,one question,if i install Q 1 will it owerwrite twrp magisk also,will there be problems maybe? Thanks
For years used htc,this is new for me.
Boskoel03 said:
@eBENdre just got xl 2 ,prerooted,one question,if i install Q 1 will it owerwrite twrp magisk also,will there be problems maybe? Thanks
For years used htc,this is new for me.
Click to expand...
Click to collapse
Yes, it will overwrite twrp and magisk.
There are always potential problems with any update to beta builds, however, many are running Q without issues. Best advice I can give is to familiarize yourself with fastboot commands, since you'll need to install twrp again, and read, read, and read again all of the information in the Q threads so you know what to do and expect :good:
Badger50 said:
Yes, it will overwrite twrp and magisk.
There are always potential problems with any update to beta builds, however, many are running Q without issues. Best advice I can give is to familiarize yourself with fastboot commands, since you'll need to install twrp again, and read, read, and read again all of the information in the Q threads so you know what to do and expect :good:
Click to expand...
Click to collapse
Huge thanks mate,and there is problem for me,as keybord not working on laptop...
You'll probably need access to a different computer - or else need to buy a cheap USB KB to use, because use of a separate computer / laptop is pretty much essential to get this working (root + Q, not to mention installing TWRP by using fastboot boot to boot TWRP, then installing TWRP from inside the booted TWRP).
Badger50 said:
Yes, it will overwrite twrp and magisk.
There are always potential problems with any update to beta builds, however, many are running Q without issues. Best advice I can give is to familiarize yourself with fastboot commands, since you'll need to install twrp again, and read, read, and read again all of the information in the Q threads so you know what to do and expect :good:
Click to expand...
Click to collapse
Did it,through twrp,lost it off course,now one more question,will i be able to recive next build,like regular OTA,altough my bootloader is unlocked? Thanks once again....
Boskoel03 said:
Did it,through twrp,lost it off course,now one more question,will i be able to recive next build,like regular OTA,altough my bootloader is unlocked? Thanks once again....
Click to expand...
Click to collapse
You should get the next update fine, provided your on stock recovery without root. I don't run betas personally, but my info comes from reading about others that do. As with anything android...YMMV :good::laugh:
Android Q Beta Experience
I've been on Android Q beta for almost 3 weeks now. It is used as a daily driver since I have only the one Pixel 2. I flashed the new image myself using TWRP rather than opt into the beta with Google. Other than a problem with now playing not always showing up on the screen and a slight delay when I go to the Favorites page in Phone app everything seems to work alright. I am getting roughly the same battery life as with Android Pie. Oh, and my banking app (ICICI Bank, India) is not working. It doesn't send an SMS to activate the app. I thought this might be as the phone number is shown as unknown. I understand that Vodafone in India does not show the phone number in the SIM information in Settings. I have activated dark mode and even photos and camera app work without a hitch. I have rooted with Magisk (Canary channel) and that is working without any problem.
OTOH, I've also been on Q since the day it came out (my birthday, coincidentally - love being an Ides of March baby lol).
I've had some issues crop up here and there, but nothing really serious. I was on Pie, rooted, and used the uninstall routine inside of Magisk to de-root my Taimen before taking Q, and then rooted it again with the (then latest) canary build.
What I'm hoping is that the Magisk procedure to de-root the device, take the OTA, and then before rebooting, applying the patched boot.img to the new partition will work, the same as if you're rooted on Pie and get an OTA.
Time will tell.
My notifications is coming like this only.. is this a bug?
or the clock is missing?
My device is not rooted. I'm not using any module or theme.
Clock missing - have you rebooted?
johnlgalt said:
Clock missing - have you rebooted?
Click to expand...
Click to collapse
Yes I have. Atleast 2-3 times.
Wonder if it is System UI Tuner related?
You could give this a shot and see if the System UI is set to hide the clock, though the last time I actually tried to hide the clock, it didn't leave that space there....
---------- Post added at 04:13 PM ---------- Previous post was at 03:48 PM ----------
New warning posted on the Android Beta page https://www.google.com/android/beta#devices
Caution: The current release contains significant behavior changes that affect apps in particular. The latest updates around isolated storage may cause issues with apps that access photos, videos, media, or other files stored on your device, such as when browsing or sharing in social media apps.
Click to expand...
Click to collapse
I'm installing the update now, let's see just how differently this works on my Taimen.