Related
I'm no developer, scripter, or any type of person with a thorough understanding of software but I will try to offer a suggestion to those who wish to give me the time of day.
After flashing countless ROMs looking for the fastest and most simple platform to use everyday I have discovered a few things that might help if people agree with me or not. After loading every ROM and first booting... I realize that Advanced Task Manager shows the available system memory at less than half and i haven't even started running apps or installing programs yet. Processes start when the phone boots up that are running in background (asleep but still using system resources) and i believe that a fair percentage of them are not required by the everyday user.
Why is Alarm Clock running in the background when i haven't started it? Why is Email client running and i haven't setup exchange or an email account? Messaging, Maps, Settings, Gallery, these all start up without being physically executed and are using resources. If there is a reason for them to be there like not being able to receive SMS if Messaging is not running, then that is fine and im an idiot... But if there is no need to startup the application from boot then why do it?
My second point is when packages are installed as the ROM is flashed, they cant be uninstalled right? well what if we didnt want tethering apps and facebook apps and proprietary software (Moto apps)? Most of these are available in the market and if not, a 5 min Google search will find an .apk on the net anyway.
So how about a bare bones install with the essentials and nothing else? Youtube, Phone, Messaging, Gmail, Contacts, MT Browser , Maps, Calculator... then anything else can be added at the users will.
If anyone else has something to say... or prove me wrong, then please elaborate.
If you delete the alarm clock task, you're likely to sleep into the morning as the alarm won't go off in the morning. Mail is probably needed for pop3 checks (I rely on my google account).
Anyway, I usualy remove the apps widgets from the ZIP which I don't need prior to flashing, resulting in a liter ROM and less processes which I don't need running in background.
I also used to add the apps I use (ASTRO...) directly into /system/app prior to flashing, putting them to the system partition and ... at this point I am not sure.... this leaves one with more space (internal memory) accessible for apps from market (if you do not use APP2SD). I stopped however doing so, as this makes ROM upgrading painful, as you do have to prepare each .zip before flash.
With regard to operating memory you preferably use either Taskkiller or have your systems autokill file optimized as many ROMS do (CursorSense). Refer to http://forum.xda-developers.com/showthread.php?t=622666
I'm not Linux-guy but I know that Android does this to put those programs in memory ASAP because those are usually the first few apps many people use once they boot up their phone -- meaning those apps, when opened, will quickly open and run faster.
Remember, Linux is made to handle all those opened apps and resources; "Unused RAM is useless RAM".
hol17 said:
I'm not Linux-guy but I know that Android does this to put those programs in memory ASAP because those are usually the first few apps many people use once they boot up their phone -- meaning those apps, when opened, will quickly open and run faster.
Remember, Linux is made to handle all those opened apps and resources; "Unused RAM is useless RAM".
Click to expand...
Click to collapse
Correct!!
People have to stop comparing Android (linux) with WinMo devices, they handle RAM completely different.
dione1200 said:
Correct!!
People have to stop comparing Android (linux) with WinMo devices, they handle RAM completely different.
Click to expand...
Click to collapse
Yes, true.... and well known. However Linux was developped for servers and not mobile phones.
Launching an application into free RAM is slower than pulling it from a suspended state. So much is true.
But first having to free up up RAM (by killing tasks) before launching the application into the freed up RAM is certainly slower than launching into free RAM. Probably that's why guys are tweaking around, as noted in the link of my post above. Also in my opinion the default settings are not optimal, that's why I use tweaked settings. Probably that depends on how you use your phone.
But I agree. Coming from Windows the whole LINUX concept is a f**** nightmare. There are thousands of different methods (Cache/Compcache/ Ext Cache)...
So it's good to have an expert around. Could you please enlight me, whether the system partition is of fixed size or size is been alocated during flashing. In other words, is the Userdata size fixed or depending on the system size? .... and is there a benefit of putting apps to the /system/app as they will go to system parition and I will have more internal storage available?
Thanks in advance.
feicher said:
So it's good to have an expert around. Could you please enlight me, whether the system partition is of fixed size or size is been alocated during flashing. In other words, is the Userdata size fixed or depending on the system size? .... and is there a benefit of putting apps to the /system/app as they will go to system parition and I will have more internal storage available?
Thanks in advance.
Click to expand...
Click to collapse
Your Android Device is divided Into partitions -> (Device memory)
1. Hboot (spl)
2. Radio
3. Data (Where u store ur data apps / passwords / other thing)
4. Cache (temp)
5. System (system dump)
6. Boot (to start the device)
so on
Now partition of memory card is important becoz
1. EXT2/3/4 More Amount of Data Section -> if device memory is less
2. Swap -> To fast up the system
*I m Not best Explaination giving person but i think this is understandable language in which i hav written
I think I side with the OP on this one, I would rather have a rom with less in it and then choose to install Amazon MP3 or whatever by myself. Generally speaking you could argue less apps = better performance, as there will be less happening in the background. That said, I have included Facebook in my rom.
However Linux was developped for servers and not mobile phones.
Click to expand...
Click to collapse
Not really true, Linux is just the kernel and can be ported to anything, it's been in embedded small devices for years and not just installed on servers.
ahmgsk said:
Your Android Device is divided Into partitions -> (Device memory)
1. Hboot (spl)
2. Radio
3. Data (Where u store ur data apps / passwords / other thing)
4. Cache (temp)
5. System (system dump)
6. Boot (to start the device)
so on
Now partition of memory card is important becoz
1. EXT2/3/4 More Amount of Data Section -> if device memory is less
2. Swap -> To fast up the system
*I m Not best Explaination giving person but i think this is understandable language in which i hav written
Click to expand...
Click to collapse
Thank you very much for the feedback! Most appreciated and helps me to improve my general understanding . I find it really hard to come by information, that is not absolutely basic or high level expert.
Thanks again.
Ive got a clock radio that wakes me up... if i have lagging issues with my phone what i do is use advanced task manager to stop all processes im not using (alarm clock, maps, messaging, email, etc) and everything runs fast again.
No use in reboot cause all the apps start again from boot.
ive tried removing zips from rom before flashing... when i goto upgrade the update stops cause of the missing files > incomplete manifest. is this cause you have to re-zip and sign it?
You can either do that and re-sign the zip file.
OR you could just close this thread and use adb to remove things that you dont want from the ROMs.
PS. root explorer also works wonders.
feicher said:
If you delete the alarm clock task, you're likely to sleep into the morning as the alarm won't go off in the morning. Mail is probably needed for pop3 checks (I rely on my google account).
Anyway, I usualy remove the apps widgets from the ZIP which I don't need prior to flashing, resulting in a liter ROM and less processes which I don't need running in background.
I also used to add the apps I use (ASTRO...) directly into /system/app prior to flashing, putting them to the system partition and ... at this point I am not sure.... this leaves one with more space (internal memory) accessible for apps from market (if you do not use APP2SD). I stopped however doing so, as this makes ROM upgrading painful, as you do have to prepare each .zip before flash.
With regard to operating memory you preferably use either Taskkiller or have your systems autokill file optimized as many ROMS do (CursorSense). Refer to http://forum.xda-developers.com/showthread.php?t=622666
Click to expand...
Click to collapse
when i try to remove an app from a ZIP it wont let me flash the ROM. even when i replace an app with a newer version renaming it to match the one im replacing, it still doesnt work. what do i have to edit in order to allow the update to go through?
You need to sign the zip file again. Google signing ROMs, its the first thing that pops up.
Apps starting on their own. Anyone have these issues? All the att stuff is gone but the video and music player are open randomly as well as quik office. I can see gmail opening and others tho check for updates
Sent from my SAMSUNG-SGH-I897 using XDA App
Yes, this annoys the hell out of me. I wish I knew what to do to stop it. I've even downloaded an app that's supposed to stop things from auto-starting, and it doesn't even work.
Search for StartUp Auditor on the market, it may work for you.
Android Market description
Startup Auditor is one of the original task killer & task manager apps. It is a boot monitor and startup monitor tool which displays a list of applications you may disable.
Terminate processes automatically.
Enable/Disable apps& keep disabled. No root.
Full version eliminates ads and can disable unlimited!
Package: com.vesperaNovus.app.StartupAuditorFree
Click to expand...
Click to collapse
On the advice of this forum I uninstalled my app killer. From time to time I use Android System to see what's running and I notice a number of apps that start themselves. These include the stock music and video players along with Slacker Radio, AT$T Maps, eBay, GPS Status and a dozen others at various times. I don't mean they remain running after exiting, I mean they start without my having used them. What could be causing these apps to start when not called upon? The ones that use GPS put a significant drain on the battery without me knowing it. Any ideas what triggers these apps? I think I'm going back to using an app killer.
Miami_Son said:
On the advice of this forum I uninstalled my app killer. From time to time I use Android System to see what's running and I notice a number of apps that start themselves. These include the stock music and video players along with Slacker Radio, AT$T Maps, eBay, GPS Status and a dozen others at various times. I don't mean they remain running after exiting, I mean they start without my having used them. What could be causing these apps to start when not called upon? The ones that use GPS put a significant drain on the battery without me knowing it. Any ideas what triggers these apps? I think I'm going back to using an app killer.
Click to expand...
Click to collapse
Mine does the same thing. I have Advanced task killer on mine. I dont use it to kill apps, just to look and see how much ram is free and whats running. But all kinds of junk opens by itself.
so does anyone have a fix for this?
derek4484 said:
Mine does the same thing. I have Advanced task killer on mine. I dont use it to kill apps, just to look and see how much ram is free and whats running. But all kinds of junk opens by itself.
Click to expand...
Click to collapse
What use is free RAM when it is kept free all the time?
AJerman said:
Yes, this annoys the hell out of me. I wish I knew what to do to stop it. I've even downloaded an app that's supposed to stop things from auto-starting, and it doesn't even work.
Click to expand...
Click to collapse
Use "start up auditor". With personal experience, this only slowed down my system.
dieselstation said:
so does anyone have a fix for this?
Click to expand...
Click to collapse
This is now android works. The way I see this, this is very much similar to "pre-fetch" concept in windows 7.
I have a 6 GB RAM laptop. Base OS uses less than 1.5 GB of RAM. But like an hour or so when I see my RAM usage, its to the tune of 3-4 GB. What I have noticed is that my most frequently/recently used apps are loaded to RAM and kept there idle. Some amount of RAM is always kept free instead of using up all RAM. This way apps start faster. When I load a different memory heavy program, it pushes the existing one out and loads this.
More or less the same in android too. When u go to any task manager app n see the running apps, u'll notice that many of the apps loaded are the ones u use frequently.
These apps do NOT use any CPU. They are just loaded to memory and kept there for quick access.
When I boot up my phone I have like 190+ MB free RAM. Though left in standy mode, within an hour, I see my free RAM fall to 80-120 MB range. I never saw it go less than 80 MB. And the apps in memory are the ones I used the last time, and the ones I use all the time.
Even if u use a task killer to kill these "inactive" apps at intervals, they would be loaded again sooner or later. That's the principle of android. So by using task killers, though u feel u r freeing up memory, in fact, u r only draining ur battery. What's the use of memory if u r not using it effectively.
Don't worry abt free RAM amount. Let android manage it. Systems are intelligent enough these days.
Hope this helps.
All well and good, but when I look at what apps are using the most resources, the GPS-enabled apps are almost always near the top of the list even when I haven't been doing anything with them. That tells me that they are stealing processor time even when not being used and that can't be good for battery usage.
Miami_Son said:
All well and good, but when I look at what apps are using the most resources, the GPS-enabled apps are almost always near the top of the list even when I haven't been doing anything with them. That tells me that they are stealing processor time even when not being used and that can't be good for battery usage.
Click to expand...
Click to collapse
Install Spare Parts and see battery usage. Do u see any GPS time under CPU usage. Though my system has all these apps loaded up, they don't show up as using CPU time or any sensors unless I use the app.
Android Memory Management
Android Memory Management
Android is a Linux based OS with 2.6.x kernel, stripped down to handle most tasks pretty well. It uses native open source C libraries that have powered Linux machines for years. All the basic OS operations like I/O, memory management, and so on, are handled by the native stripped-down Linux kernel.
How to use memory for each application
Android’s process and memory management is a little unusual. Like Java and .NET, Android uses its own run time and virtual machine to manage application memory. Unlike either of these frameworks, the Android run time also manages the process lifetimes. Android ensures application responsiveness by stopping and killing processes as necessary to free resources for higher-priority applications.
Each Android application runs in a separate process within its own Dalvik instance, relinquishing all responsibility for memory and process management to the Android run time, which stops and kills processes as necessary to manage resources.
Dalvik and the Android run time sit on top of a Linux kernel that handles low-level hardware interaction including drivers and memory management, while a set of APIs provides access to all of the under- lying services, features, and hardware.
Dalvik Virtual Machine Dalvik is a register-based virtual machine that’s been optimized to ensure that a device can run multiple instances efficiently. It relies on the Linux kernel for threading and low-level memory management.
The Dalvik Virtual Machine
One of the key elements of Android is the Dalvik virtual machine. Rather than use a traditional Java virtual machine (VM) such as Java ME (Java Mobile Edition), Android uses its own custom VM designed to ensure that multiple instances run efficiently on a single device.
The Dalvik VM uses the device’s underlying Linux kernel to handle low-level functionality including security, threading, and process and memory management.
All Android hardware and system service access is managed using Dalvik as a middle tier. By using a VM to host application execution, developers have an abstraction layer that ensures they never have to worry about a particular hardware implementation.
The Dalvik VM executes Dalvik executable files, a format optimized to ensure minimal memory foot- print. The .dex executables are created by transforming Java language compiled classes using the tools supplied within the SDK.
Understanding Application Priority and Process States
The order in which processes are killed to reclaim resources is determined by the priority of the hosted applications. An application’s priority is equal to its highest-priority component.
Where two applications have the same priority, the process that has been at a lower priority longest will be killed first. Process priority is also affected by interprocess dependencies; if an application has a dependency on a Service or Content Provider supplied by a second application, the secondary application will have at least as high a priority as the application it supports.
All Android applications will remain running and in memory until the system needs its resources for other applications.
It’s important to structure your application correctly to ensure that its priority is appropriate for the work it’s doing. If you don’t, your application could be killed while it’s in the middle of something important.
The following list details each of the application states shown in Figure (see the attached image) explaining how the state is determined by the application components comprising it:
Active Processes Active (foreground) processes are those hosting applications with components currently interacting with the user. These are the processes Android is trying to keep responsive by reclaiming resources. There are generally very few of these processes, and they will be killed only as a last resort.
Active processes include:
* Activities in an “active” state; that is, they are in the foreground and responding to user events. You will explore Activity states in greater detail later in this chapter.
* Activities, Services, or Broadcast Receivers that are currently executing an onReceive event handler.
* Services that are executing an onStart, onCreate, or onDestroy event handler.
Visible Processes Visible, but inactive processes are those hosting “visible” Activities. As the name suggests, visible Activities are visible, but they aren’t in the foreground or responding to user events. This happens when an Activity is only partially obscured (by a non-full-screen or transparent Activity). There are generally very few visible processes, and they’ll only be killed in extreme circumstances to allow active processes to continue.
Started Service Processes Processes hosting Services that have been started. Services support ongoing processing that should continue without a visible interface. Because Services don’t interact directly with the user, they receive a slightly lower priority than visible Activities. They are still considered to be foreground processes and won’t be killed unless resources are needed for active or visible processes.
Background Processes Processes hosting Activities that aren’t visible and that don’t have any Services that have been started are considered background processes. There will generally be a large number of background processes that Android will kill using a last-seen-first-killed pat- tern to obtain resources for foreground processes.
Empty Processes To improve overall system performance, Android often retains applications in memory after they have reached the end of their lifetimes. Android maintains this cache to improve the start-up time of applications when they’re re-launched. These processes are rou- tinely killed as required.
How to use memory efficiently
Android manages opened applications which are running in the background, so officially you shouldn’t care about that. This means that it closes the applications when the system needs more memory. However, most android users are not very satisfied with how it does its things because sometimes it leaves too many processes running which causes sluggishness’ in everyday performance. We can use advanced task killer/task manager and it does its job very well.
Source:
Code:
http://mobworld.wordpress.com/2010/07/05/memory-management-in-android/
Still doesn't answer the question of why the OS is starting apps randomly and without need. For instance, I have Titanium Backup and SGS Tools installed, but can't use them because I am not yet rooted. So why do I keep finding both programs started in the process list? Is the app making the call to start? If so, what can I change to stop it? Whatever Android does to manage memory, it just seems stupid for it to load programs that are hardly used without my asking it to.
Miami_Son said:
Still doesn't answer the question of why the OS is starting apps randomly and without need. For instance, I have Titanium Backup and SGS Tools installed, but can't use them because I am not yet rooted. So why do I keep finding both programs started in the process list? Is the app making the call to start? If so, what can I change to stop it? Whatever Android does to manage memory, it just seems stupid for it to load programs that are hardly used without my asking it to.
Click to expand...
Click to collapse
This is how the systems work in most systems, not just in android.
Take the new cars for instance. Power is generally sent to brakes when in low gears, though u r not actively engaging them. Why? Since u r at low speeds, higher probability of applying brakes. And when u do apply, since there is already some power already being sent, its faster to brake.
On similar lines is this principle of loading apps into memory in android too. It won't load apps to fill up ur memory. Plus the apps loaded into memory in this way don't use any CPU time (this means no battery usage). This speeds up system.
On a side note, if u feel u really do not need an app, and dont' want android loading that app, get "startup auditor" from market. Select the apps u don't want to persist in memory and don't want to auto start. Beware of one thing here: if u make an app as 'do not persist' in memory, and that app is started manually or by any other app, it would be killed giving FC in the app that's using it.
Note: I coined the term 'do not persist'. I do not have the app anymore to check for the exact term.
Edit: In windows, this pre-fetching is done through a service. And one can disable that service, though not recommended. I am not sure if this is done through a service that is "stoppable" in android.
Hi! I've seen some threads regarding how bad memory management is on this device and I think I've found the culprit. I went to 'Low Memory Killer' tab on kernel adiutor and disable the 'Adaptive Low Memory Killer' and the apps stay on background even with multiple apps open at the same time! Unfortunately it seems to be impossible to do this without root but, for those with it, definately try this to see the results!
Eddie_53 said:
Hi! I've seen some threads regarding how bad memory management is on this device and I think I've found the culprit. I went to 'Low Memory Killer' tab on kernel adiutor and disable the 'Adaptive Low Memory Killer' and the apps stay on background even with multiple apps open at the same time! Unfortunately it seems to be impossible to do this without root but, for those with it, definately try this to see the results!
Click to expand...
Click to collapse
App is not more available on play store, i will try with hebf optimizer to see if i can change
Thanks man! Works really well
You are a legend
It works really good
Testing the way to do not use any third party apps for ®termux users! Script must be executed every boot!
Making bash files to easy run on boot:
Code:
echo 0 > enable_adaptive_lmk
echo "sudo cp enable_adaptive_lmk /sys/module/lowmemorykiller/parameters/" > boot
Running on each boot:
Code:
bash boot
Working!
As above. I just updated to Android 11 recently on my Samsung Galaxy Note 10+ (SM-N975F), and holy **** Scoped Storage is a massive pain. Google and various device manufacturers have already been gradually restricting and cutting down access to various power user options (e.g. flashing custom firmware, accessing various settings, making dev features harder to use and/or access), but Scoped Storage is pretty redundant.
For those who aren't familar, Scoped Storage severely restricts access to the Android/data folder in your internal storage. As a result, it just turns the Android/data folder into basically what the data/data partition is - a system-managed folder where apps can only access their own folders and only certain system processes (or root users) can access the entire folder structure. This breaks a lot of apps which historically stored their data in their own Android/data folders which would otherwise work on Android 11.
I was hoping that LineageOS would have had an option to disable this "feature" (I noticed a commit around "opting out of scoped storage" at https://review.lineageos.org/c/LineageOS/android_packages_apps_Eleven/+/286006), but it seems not. For me, I've downgraded to Android 10; thankfully the bootloader version remained the same.
Still, I was wondering, is it likely that a custom ROM maker will be able to find some way to disable Scoped Storage on Android 11 in the future? Thanks for any responses.
Edit: clarified that I meant Android 11+.
ArtemisPilly said:
As above. I just updated to Android 11 recently on my Samsung Galaxy Note 10+ (SM-N975F), and holy **** Scoped Storage is a massive pain in the ass. Google and various device manufacturers have already been gradually restricting and cutting down access to various power user options (e.g. flashing custom firmware, accessing various settings, making dev features harder to use and/or access), but Scoped Storage is pretty redundant. It just turns the Android/data folder into basically what the data/data partition is - a system-managed folder where apps can only access their own folders and only certain system processes (or root users) can access the entire folder structure. This breaks a lot of apps which historically stored their data in their own Android/data folders.
I was hoping that LineageOS would have had an option to disable this "feature" (I noticed a commit around "opting out of scoped storage" at https://review.lineageos.org/c/LineageOS/android_packages_apps_Eleven/+/286006), but it seems not. For me, I've downgraded to Android 10; thankfully the bootloader version remained the same. Still, I was wondering, is it likely that a custom ROM maker will be able to find some way to disable Scoped Storage in the future? Thanks for any responses.
Click to expand...
Click to collapse
It is possible if it downgrade your device to android 10
Austinredstoner said:
It is possible if it downgrade your device to android 10
Click to expand...
Click to collapse
Yeah, that's what I originally thought as well. Still, we can't feasibly remain on Android 10 forever, so I was wondering how is Scoped Storage implemented on the Android OS and whether it can be disabled or that specific module can be rolled back by ROM developers.
ArtemisPilly said:
Yeah, that's what I originally thought as well. Still, we can't feasibly remain on Android 10 forever, so I was wondering how is Scoped Storage implemented on the Android OS and whether it can be disabled or that specific module can be rolled back by ROM developers.
Click to expand...
Click to collapse
They say their some file manager they bypass this restrictions it may work but I can't say for sure
https://play.google.com/store/apps/details?id=com.marc.files
This app may be able to bypass the restrictions
Austinredstoner said:
They say their some file manager they bypass this restrictions it may work but I can't say for sure
https://play.google.com/store/apps/details?id=com.marc.files
This app may be able to bypass the restrictions
Click to expand...
Click to collapse
Yeah, I know some file managers are able to bypass the restrictions (Root Explorer, Solid Explorer etc). The problem is with other, non-file-manager apps (e.g. messaging apps, browsers, games) which are used to storing their data in Android/data.
Many such apps either crash upon opening, or they might ask for permission to access their old folders, which when granted, opens up the Android stock file picker. The stock file picker then refuses to allow the app to use its old folder, saying "to protect your privacy, choose another folder" (or something like that, I've downgraded to Android 10), and there don't seem to be any options to use a different file picker (for some reason the only other app I can see in the file picker is Termux??).
This cripples a lot of older apps which are still very useful but which haven't been updated in a while (and when I say "older", I mean "2019" - not that old, about half of Android devices still run on 9.0 or older).
ArtemisPilly said:
Yeah, I know some file managers are able to bypass the restrictions (Root Explorer, Solid Explorer etc). The problem is with other, non-file-manager apps (e.g. messaging apps, browsers, games) which are used to storing their data in Android/data.
Many such apps either crash upon opening, or they might ask for permission to access their old folders, which when granted, opens up the Android stock file picker. The stock file picker then refuses to allow the app to use its old folder, saying "to protect your privacy, choose another folder" (or something like that, I've downgraded to Android 10), and there don't seem to be any options to use a different file picker (for some reason the only other app I can see in the file picker is Termux??).
This cripples a lot of older apps which are still very useful but which haven't been updated in a while (and when I say "older", I mean "2019" - not that old, about half of Android devices still run on 9.0 or older).
Click to expand...
Click to collapse
Google will finally let file manager apps request "All Files Access" on Android 11 next month
Google has finally announced when it will allow file managers and other apps that target Android request the All Files Access permission.
www.xda-developers.com
This wasn't here when u created this thread but this is good news
Austinredstoner said:
Google will finally let file manager apps request "All Files Access" on Android 11 next month
Google has finally announced when it will allow file managers and other apps that target Android request the All Files Access permission.
www.xda-developers.com
This wasn't here when u created this thread but this is good news
Click to expand...
Click to collapse
Actually the article says that Android/data and Android/obb will be excluded from said access, so it's not really any improvement over the current situation.
One of the alternative band-aids to disabling Scoped Storage might be to find some way to mod the stock file picker so it recognises apps like Solid Explorer and Root Explorer (which can bypass the restrictions) as file managers. However this still doesn't help apps which expect to be able to access their files from the get-go; one example is GTA San Andreas, which seems to just crash upon opening.
Xplore file manager bypasses it
X-plore File Manager - Apps on Google Play
X-plore is dual-pane file manager with tree view, LAN/Root/Clouds and more.
play.google.com
ArtemisPilly said:
Yeah, that's what I originally thought as well. Still, we can't feasibly remain on Android 10 forever, so I was wondering how is Scoped Storage implemented on the Android OS and whether it can be disabled or that specific module can be rolled back by ROM developers.
Click to expand...
Click to collapse
You can stay on Q for the life of the device more then likely. I'm still running Pie with zero issues.
Android's gone Apple tarted
blackhawk said:
You can stay on Q for the life of the device more then likely. I'm still running Pie with zero issues.
Android's gone Apple tarted
Click to expand...
Click to collapse
money will make even the best developers re-tart just take a glance at windows 10
I still got windows xp
revized said:
money will make even the best developers re-tart just take a glance at windows 10
I still got windows xp
Click to expand...
Click to collapse
Sad but predictable to see Android tailspinning in like creepy billgatesware.
XPx64 is still the best.
I run W7x64 too.
After that MS became an useless liability.
Evil clownware
I still wonder though, will LineageOS opt out of Scoped Storage or add a feature to disable it?
An equally effective alternative and probably even better one would be to let the user give specific apps full storage permission. Is something like this realizable (even if it's through rooted means - that would be fine)?
We need CONTAINERS for scoped storage. Same as we do for browser containers.
We need a scoped storage manager to group apps.
We don't need an all or nothing approach designed to push everything through the cloud.
Then again, that could be a workaround, right? Same as the workarounds for the browser when local file access was removed: setup a local server to pass data between processes!!
Hi, just my tuppence worth.
I bought an updated android box couple months ago as an upgrade to couple of old ones I had. Mainly use for watching streamed tv shows, viewing youtube and also checking out my cctv and saving recordings to the usb hdd.
Well the new box was amazing. Never mind the hype it is really good. its the hk1 rboxx4. Very fast on latest android 11. But it was a good month messing about trying to work out why nothing would write to the external usb dd. Then I discovered the scope business and the penny dropped.
Google is going to muscle in on streaming ppv sites. Well android has for years. But if they want to sell premium movies etc. or even just official boxes, They wont want the fee payers making back-ups. Just cant see why else they would do it.
The second thing is X-plore does not solve the problem. Ive used it for years on every device iv ever had. But it will not write to ext hdd on android 11. Tried many times, many versions.
so I got a Sky Devices Elite OctaX from the government for free w/ Service, but the thing acts like it's rooted, but it iisn't all. Anytime I put a game on it, it thinks it's rooted and boots me out of the game. I checked all the usual culprits like if Developer mode was on (it wasn't), if USB Debugging was on (it wasn't) and other things that potentially could trip the program into thinning it's rooted. I don't know what to do with this tablet at this point: I don't know how to install TWRP to install a new rom on it to use as loophole, mainly because there is no supported version for it; same with it adding Magisk as well, so any "safe" rooting ways are out of the question and now im left with the "One Button" methods, sadly.
so Does anyone have any advice as to what to do with the tablet?
A device's Android is rooted when SU binary ( either as part of BusyBox or as part of ToyBox or as standalone ) is present in Android's filesystem and made executable.
It's easy for any app to detect the presence of an executable SU binary.
xXx yYy said:
A device's Android is rooted when SU binary ( either as part of BusyBox or as part of ToyBox or as standalone ) is present in Android's filesystem and made executable.
It's easy for any app to detect the presence of an executable SU binary.
Click to expand...
Click to collapse
so what are my options to get around this? It's a REALLY good tablet, but this has soured me on it, and I demand a refund... despite it getting it for free.
I don't know if this is allowed, but im bumping to see if anyone has an answer to help me with this.
Ramses83 said:
I don't know if this is allowed, but im bumping to see if anyone has an answer to help me with this.
Click to expand...
Click to collapse
If unsure just review the XDA Forum Rules; in case of your question please refer to rule no. 5. Affirmative, you're allowed to bump your question once every 24 hours.
Regards
Oswald Boelcke
Senior Moderator
Bless you good sir
bumping for justice!!
bumping till we can get this done! I believe in you all!
I still believe in you! bumping for hope!
bump
morning bump!
evening bump
Bumping with a result from root beer
bump
bump
still need help with the device.... I've made some advancements, like the reason why it keeps turning off apps is because it has insufficient memory... which is weird since it should have enough memory to run stuff.... im just confused, I think putting in a lower end rom would fix it... maybe. I don't know
Each Android smartphone comes with a fixed amount of RAM. It is part of the phone’s motherboard and it's not configurable by ROM settings. Also Android OS itself takes from this inbuilt RAM ~600 MB, hence device's available RAM is always far lower. So switching to another ROM - as intended - doesn't solve memory problems you may have, IMO.
In Android, each app's program runs in a self-contained VM that is by default assigned a certain amount of RAM ( read: heap ) - typically 128 / 256 MB. This amount is defined in Android's system file called build.prop. To this app-reserved RAM must be added the RAM required by an app's data.
E.g. games like Need for Speed: No Limits or PUBG Mobile can use between 800 MB and 1152 MB in total.
I either have the same tablet or the non elite version, but on mine there is an engineer mode app the opens with a shortcut launcher. There is an adb shell executor that executes commands not as shell but as system so I imagine you can use that to get done what you're trying to do.