Here is a link that explains more on how Android does it suspend functions. It may provide information to the developers on 'sleep of death' that people have reported with different roms.
http://lwn.net/Articles/416690/ An Alternative to suspend blockers.
Related
Update, here is the new google spreadsheet.
I would like to propose that we document the "openess" state of various Android devices, so that those who are in the market for a new device can potentially get a better picture of which devices might suit them if they are concerned about such things. I have read through countless posts in the last few months, across several forums, to attempt to figure out much of this info myself, for many of the existing devices. Naturally, the state of a device can change as developers figure out how to do things with devices, or as manufacturers release more info, source, or tools. I suspect that at least a few other people would like to share in the fruits of my searches. I also suspect/hope that a few others might be willing to add their own conclusions and references to my research. Let's join together in a common place to do this. Thanks.
I propose to do that with respect to the Open Libre Device guidelines (Specification 0.0) listed below:
Open Libre Device Level 0: Functionally Open
Freedom 0.0: The ability to load software on the device unimpeded.
Freedom 0.1: The ability to access all the intended device's hardware functionality via free/libre software running on the main (non auxiliary) processors. A free/libre software reference implementation must exist to do this.
Freedom 0.2: The ability to use all the device's intended functionality (except for any device communication functionality) without the device communicating with any other device. The reference software implementation must not require external activation of any sorts.
Open Libre Device Level 1: Completely Open
Freedom 1.0: All of the freedoms of level 0
Freedom 1.1: The ability to interact with the device externally with only free/libre software. A free/libre software reference implementation must exist which implements any protocols required to communicate with the device to exercise all the freedoms of level 0. This includes loading software or accessing its functionality such as communications protocols.
Note: the likely currently precludes any cell phones from being level 1 open devices since there are no complete free/libre software stacks for cell networks (yet).
Freedom 1.2: The ability to access the entire device's intended functionality with entirely free/libre software, including all device peripherals (auxiliary processors) running only free/libre software. Free/libre software reference implementations must exist for all device peripherals.
These are guidelines which I came up with a while ago. They are not perfect, and I welcome comments and improvements in both the intent and clarity of these guidelines. I will stipulate however, that I do not ever intend to amend this specification to be in the spirit of Open Source Hardware. The spirit here is about the software that runs on, and interacts with the devices, not about designing the hardware.
So, I am looking for:
A good place to put our list (it could be here in this thread)
A good way to keep track of this info a (table format, a db somewhere, a google spreadsheet?)
Info about devices:
Brand/Device Name/Model #, version (if it matters)
Pass or Fail with respect to any specific point in the guidelines above
A description or reference which (dis)proves 3B
Well, thanks for any support, I look forward to sharing my results with others.
Here is a sample for a device that I currently own:
Code:
Device P/F Freedom Point Reference Date
zt-180 P 0.0 2010/11/24
F 0.1 No kernel source "
P 0.2 (*) "
F 1.0 0.1 "
P 1.1 (*) "
? 1.2 There is likely closed firmware on the GPU "
* No known problems here
Google Spreadsheet
Well, since Matthew Garrett had a pretty good start with GPL compliance listings here:
http://www.codon.org.uk/~mjg59/android_tablets/
I decided to go ahead and create a google spreadsheet which includes columns for each of the freedom points above. I attempted to at least populate the ZT180 all the way at the bottom. Please feel free to add data for any device that you are familiar with. In particular, please add links for any references to help anyone who owns (or would like to own) such a device. Here is the spreadsheet:
https://spreadsheets.google.com/ccc?key=0AnRFPYwp3Th9dHFrRkRXOVFWam01N25DTVdXTUQxM0E&hl=en#gid=1
This particular kernel contains changes to the following:
- binder bugs, i.e. leaks, API misuse
- lowmem killer logic errors
- scheduler, i.e..spurious wakeups, "bouncing cow", fair scoring
- vm subsystem changes to oom killing, google lowmemkiller
- kswapd wasting CPU time no longer occurs
- cpufreq microoptimizations (wakeups, useless computation), interactive governor updated to latest version from msm-kernel for 3.10 Google Wear
Credits:
Kernel forked from work of another xda member. That's documented in github project itself, and revision history.
Changes come from Torvalds tree, msm and common. The kswapd fix comes from a google search. You can look for "contention_wait" yourself to note the source.
hxxps://github.com/sthalik/gcore_kernel
Pull requests and forks welcome. So are quality well-researched bug reports. Feature requests, only if sensible and educated.
-foo
foobie-bletch said:
This particular kernel contains changes to the following:
- binder bugs, i.e. leaks, API misuse
- lowmem killer logic errors
- scheduler, i.e..spurious wakeups, "bouncing cow", fair scoring
- vm subsystem changes to oom killing, google lowmemkiller
- kswapd wasting CPU time no longer occurs
- cpufreq microoptimizations (wakeups, useless computation), interactive governor updated to latest version from msm-kernel for 3.10 Google Wear
Credits:
Kernel forked from work of another xda member. That's documented in github project itself, and revision history.
Changes come from Torvalds tree, msm and common. The kswapd fix comes from a google search. You can look for "contention_wait" yourself to note the source.
hxxps://github.com/sthalik/gcore_kernel
Pull requests and forks welcome. So are quality well-researched bug reports. Feature requests, only if sensible and educated.
-foo
Click to expand...
Click to collapse
Hi there! I would love to try it, how could I?
First post includes a link to the sources. Given an ARM cross-compiler that can build the kernel, it's a matter of repacking initrd and flashing.
Unless you suffer from the kswapd issue, there's little point. Fixes included aren't something you'd notice after using the software briefly.
My intention is to make available the changes. Whether they're given attention or are reviewed at all, doesn't depend on me really.
-foo
foobie-bletch said:
First post includes a link to the sources. Given an ARM cross-compiler that can build the kernel, it's a matter of repacking initrd and flashing.
Unless you suffer from the kswapd issue, there's little point. Fixes included aren't something you'd notice after using the software briefly.
My intention is to make available the changes. Whether they're given attention or are reviewed at all, doesn't depend on me really.
-foo
Click to expand...
Click to collapse
Thanks a lot for your answer, I would love to try it, but i don´t know how to compile a kernel
Contact Ali filth may be he could help.
Sent from my GT-I8262 using XDA Premium 4 mobile app
Please note, you don't have to fork the repository on github to follow the changes.
If you in fact never compile kernels yourself you're not my intended audience.
Still, getting to know C is always the first step toward any serious Linux/Unix hacking.
Kernel stuff isn't any different than others. There are some rules to follow, but this is true of userland code, too. Documentation often says "don't do this and that". Just like with kernel API.
There's already a thread about my Xposed module in the Xposed section but since I'm Galaxy S7 user, majority of the tweaks are intended for S7. Check out the thread but some of the unique latest features are:
Disabling the estimate part in Battery usage and reenabling detailed History details (see the screenshot from actual S7)
Use MTP without manual unlocking/confirming anything (for safety, you are required to use Smart Lock or something similar)
I'm glad for any feedback or requests that improve functionality.
We have compiled detailed guides on how to turn off battery optimizations, Doze and app killers on pretty much every Android version and device. It’s available at:
undoze [dot] com
This may be useful for both users and developers, who don't want their apps being terminated, prevented from performing background tasks, or killed before they can send notifications.
Let us know what you think.
i'm not a developer and have been out of XDA since my HTC HD2
like many of us i have security and privacy concerns regarding today's internet landscape. i had an idea which i'm not sure if it's feasible or not and therefore i'm dropping it here to see if anyone is willing to pick up the project.
i was considering a rom that could take advantage of the blockchain system for most of it's communications (i know, still not enough users), an with the following features:
- a sandbox system to run most apps, giving fabricated sensor data to the apps
- any internet access for the apps would have to be filtered through a firewall that would ask permission, (option for permanent permission or ask every time)
- the firewall would, where possible, identify the server/website that the app was contacting and provide some information about the data being transmitted
- some apps could be given trusted status by the user, (privacy warning given to the user).
- other security features such as the option to completely shutdown the radios.
i'm not aware of anything like this, specially the sandbox, any sugestions would be welcome
XDA:DevDB Information
blockchain/privacy, ROM for all devices (see above for details)
Contributors
adelinobs
ROM OS Version: 9.x Pie
Based On: cyanogenmod
Version Information
Status: Testing
Created 2019-07-22
Last Updated 2019-07-22
Thread closed as duplicated with https://forum.xda-developers.com/android/development/sandbox-t3950597/post79940703