Hi,
This is the first time I've started a thread so home I'm in the right place etc.
Just working on my first ever app. I created it as a service as that's what I thought I needed to monitor the battery status, screen status etc. I created some intent filters within the program itself to do that and assumed the process had to be running to get them.
Then I read I could have put the intents in the manifest file and my app will be started up if it isn't already running. That sounds quite neat as I can get rid of the notification icon I have to have in the notification area (I had to use setForeground to stop Android killing off the service and then immediately re-starting it). But -
Am I going to use up more battery with this second method? (using intents to wake the process) I'm not sure how often Android is going to terminate my process but if it's quite often then the overhead of my app starting up and reading some variables I'd have to persist could be a drain.
Any rule of thumb help here? I know the answer might have a bit of "depends" in it but really looking for some general advice.
Thanks.
Peter.
TL;DR
If my phone shuts down due to low battery I want to be able to boot up into a reduced OS that would allow me to use a basic UI to utilise basic funtions like (emergency) calling / sending SMS.
I ask if anything like this is in the pipeline, and if not, can I achieve it myself using tools from this site.
Bloat:
Senario:
Imagine your battery is flat, but you really need to make a call.
No problem just boot into a phone only - very low power - mode (OS) that allows you to make a call but has very limited capabilities.
Q1) Is this possible?
I often run out of battery but really need to make a call. I need to either have a spare battery (which I do) or not run out (which I try to do).
But I am pretty sure there is a lot of power left in my battery, I just cannot access it as the Android system is a power hog.
There must be a way to boot a minimal function OS that can make basic calls, maybe as a choice from the hboot/recovery menu.
Q2) Would others find this useful
The best option is a custom built OS with drivers for the key areas of the phone and very basic UI. I think this would be a lot of work, and is well beyond my abilities. Idealy HTC / Google read this and implement one. Basicaly use the phone as a 10yo Nokia.
Q3) Does anyone know of anything like this that exists or is in development?
Another possibility would be a "safe mode" where the Android OS does not boot all the crap it usually does and has a basic black screen interface.
Q4) Does anyone know of anything like this that exists or is in development?
In a world where this stuff does not exist yet can I simulate this using a second dual boot rom. The rom would be stripped bare and all settings to lowest values.
I would also want to undervolt and underclock the CPU in the Hboot/recovery.
Turn off all the boot animations and vibrate on boot.
Q5) Do you think this would work, could I reduce the power drain enough to give myself significant extra life to boot android and make a call or two on a battery that is theoretically dead.
I own an HTC Sensation, from what I can see there is no dual boot kernel for that yet and changing the cpu values can only be done from within Android at which point it may be too late as the large power draw on startup cannot be met. (Bricked can do if from command line if I want to re-flash the kernel in recovery with 0% battery left - not sure if thats a good idea)
Q6) Anyone know of anything for the Sensation I can use.
I am a noob to the site and only rooted a week ago but I have some practice using adb and developing apps in java (none published) and would be happy to develop this idea and share my solutions if people can give me a few pointers.
Of course if you like the idea and want to produce something I can download I could also live with that.
Thanks in advance.
Paul
Hello
I'm thinking about an tracking project.
Not like "Where have you bin all the day?", more like "Where are you right now"
I would like to use an old android device to track a car by using only SMS.
The device should only be used to receive a SMS, switch on GPS, wait for signal and send back the current position.
The device don't need to provide phone functionality, internet or any UI.
The power supply should be connected to the car battery. (I hope it will not discharge to much)
Is it possible to hide the device into the glove compartment and to protract the GPS antenna?
To make a keepalive the device should send a SMS once a week to a given Number.
Is there any project how strip down an android to some basic functionality?
Is there any project which provide likewise functions?
Currently i have install CM7 on my old and CM11 on my new device.
Maybe CM7 with androidlost can do the job.
I found some descriptions about remove most apps like calender, contacts, ...
I'm not sure if the UI can be removed.
Hey!
Long time lurker, first post
I have the Motorola Nexus 6, Chainfire Rooted, Android 6
I did initially upgrade to Android 7 but it was not stable for what I currently doing (more below)
I have a app I am running that is linked to Google (Google Play specifically)
I have ~15 different Google IDs, and I have created 15 user profiles on my phone (had to do some root editing to enable that)
open build.prop
Code:
# Multi Users
fw.max_users=15
fw.show_multiuserui=1
I can change users and the app launches and runs as desired
This has been working great for the last year +/-, the only caveat is that it uses a crazy amount of space (all of the google apps etc.)
So I am wondering if their is a easier way to accomplish this that does not create a full phone profile for each app (similar to the Samsung Secure file app? I have been told this works, but have not tested) or if their is a way to slim down the additional profiles and remove the apps that are not needed (without messing up the stability of the main profile or the alternate profiles)
Any suggestions or ideas are appreciated - thanks! :highfive:
Some more information on the stability issues I encountered with Android 7 (initial package, did not test beyond that)
- Notification bar did not support more than ~8 users
- Users beyond 8 were unresponsive and would not load / switch
I think the Samsung App I referenced is called Secure Folder
androidauthority.com/samsung-secure-folder-google-play-store-779156/
I am not sure if their is a similar app in function for non-Samsung devices
eris667 said:
Some more information on the stability issues I encountered with Android 7 (initial package, did not test beyond that)
- Notification bar did not support more than ~8 users
- Users beyond 8 were unresponsive and would not load / switch
I think the Samsung App I referenced is called Secure Folder
androidauthority.com/samsung-secure-folder-google-play-store-779156/
I am not sure if their is a similar app in function for non-Samsung devices
Click to expand...
Click to collapse
Android devices are not made to handle that many profiles. It was made for a max of 5. Anything more and you will find instability.
There are tons of app lockers so to speak.
I have tried a few of the clone / parallel type apps in the PlayStore - but not much success
- Most only support 2 profiles
- In testing it doesn't differentiate the Google Profile (i.e. the clone loads the default Google Profile, vs the alternate)
If anyone has a recommendation I will gladly experiment
I am probably on the extreme edge here with 13 active profiles (most people are probably closer to 1-3 I would guess)
Ideally I would love to find a solution that:
- reduces the size of the existing profiles (staying on Android 6)
- an alternate way to manage the Google IDs (migrating to Android 7)
My current setup (while working) prevents future device / software upgrades, and currently I am "out of space"
eris667 said:
I have tried a few of the clone / parallel type apps in the PlayStore - but not much success
- Most only support 2 profiles
- In testing it doesn't differentiate the Google Profile (i.e. the clone loads the default Google Profile, vs the alternate)
If anyone has a recommendation I will gladly experiment
I am probably on the extreme edge here with 13 active profiles (most people are probably closer to 1-3 I would guess)
Ideally I would love to find a solution that:
- reduces the size of the existing profiles (staying on Android 6)
- an alternate way to manage the Google IDs (migrating to Android 7)
My current setup (while working) prevents future device / software upgrades, and currently I am "out of space"
Click to expand...
Click to collapse
Nothing you can do. It is the way multi users setup on android.
Not sure why you would need so many profiles but my only suggestion is get a device with more storage.
I am going to try "Parallel Space" and "App Cloner"
it looks like Parallel Space can manage a separate Google ID maybe I can clone that x15 (lol)
eris667 said:
I am going to try "Parallel Space" and "App Cloner"
it looks like Parallel Space can manage a separate Google ID maybe I can clone that x15 (lol)
Click to expand...
Click to collapse
You will still run into the memory issue. There was an OS that focused on something like that but it went belly up as no one really used it and it was plagued by issues on both rom and Google side.
Good luck.
Hmmmmm checking Internal storage differences (i.e. is this any better then the profiles I currently have)
I currently have a 32Gb device, at 29.58Gb Used (phone is calculating storage locations)
Will add more detail and do some additional testing,
I created 2 clones, to establish approximate usage size
I have not had any stability issues with either method so far
eris667 said:
Hmmmmm checking Internal storage differences (i.e. is this any better then the profiles I currently have)
I currently have a 32Gb device, at 29.58Gb Used (phone is calculating storage locations)
Will add more detail and do some additional testing,
I created 2 clones, to establish approximate usage size
I have not had any stability issues with either method so far
Click to expand...
Click to collapse
Be careful. Android has issues when the internal storage starts getting more then 50% full. It will slow down, lag out and have stability issues. Android developers advised never to get more then 35% of device memory full.
Still playing around with it
initial comparison User Profile ~517mb, Parallel Space ~84mb
I have 12 profiles + my main profile (other 3 profiles were not created)
6204mb vs 1008mb = 5196mb saved space
My 32Gb Nexus has 25.98Gb max, to get into the 35% range I should have 9.09 Gb Free?
I need to do some additional testing - and maybe a fresh wipe to Android 7
arghhhhh......
I found (3) old FlashFire backups, ~8gb free now, an additional ~5gb free when I remove the profiles
all said I will probably do a Titanium Backup on a few things a perform a full reset to clean up some trash I have accumulated
Android 6 runs great for me (on this device), still debating if I should go to Android 7 in the near future
Appreciate all of the comments and ideas!
Hi all,
I like the app, Battery Charge Limit (root required), but was wondering how to set the control file. I works fine with Xperia (with/without Lineage), but doesn't work with Pixel 3 stock firmware (Android 10). And finally found how to set it.
This is my memorandum as well as post
The control file is:
/sys/class/power_supply/battery/input_suspend
and as the name goes, when below the limit, set it to 0, and when charged enough, set it to 1.
Regards,
There is an actual battery charge limit file on Pixel 3,
Code:
/sys/devices/platform/soc/soc:google,charger/charge_stop_level
It contains "100" by default, but if you write "80" here (once per boot, for example via EXKM "user settings" or MacroDroid "write file" macro), device itself will stop charging at 80%.
No need for external app actively monitoring charge level and writing 1 to battery/input_suspend once the battery level reaches desired maximum.
I've discovered it browsing kernel sources in drivers/power/supply/qcom folder.
Get the most life from your Pixel phone battery - Pixel phone Help
You can help your phone’s battery last longer throughout the life of the phone by taking care of the battery and reducing battery drain. Important: Some of these steps only work on Android
support.google.com
says:
... your phone automatically limits charging to about 80% under certain conditions:
Continuous charging under high battery drain conditions, like game play.
Continuous charging for four days or more.
I wonder if there's another method & the phone can be fooled to think one of those conditions is true? I presume it sets the varable above, but maybe there's a way of doing it without root?
This has been working well as expected for me, with the default settings.
GitHub - Magisk-Modules-Repo/acc: Upstream repo:
Upstream repo: . Contribute to Magisk-Modules-Repo/acc development by creating an account on GitHub.
github.com
We can also use tasker or something like terminal emulator to run shell:
Code:
echo 80 > /sys/devices/platform/soc/soc:google,charger/charge_stop_level
The phone will stop charging when battery level reaches 80