Are there any plans for porting the applications permissions revocation system to Cyanogen Mod 9?
I have read that the original developer was planning to port it in January, however no further news have been released. Judging from the comments of several Cyanogen Mod developers it seems this feature is not high priority for the team, however my question is: will you ever approve it?
Thanks in advance for your reply.
bump... any news about this feature?
Nobody else is interested in this feature apart from me??
Diggin this up Yes me too.
Why the hell did Google not already fix it?
I think this is not considered a design flaw neither by Google nor by Cyanogenmod team. Google may have interest in pleasing developers, who make money out of data mining, Cyanogemnod may just be too popular and just need to comply with higher regulations in order to survive.
Probably the best choice would be installing Fdroid: http://f-droid.org and start using Open Source applications.
I have an old Desire with CM7 and i can set permission per application if i remember. I'm surprised that this feature was remove from CM9 ?
I try LBE, but it's slow the phone and can easily crash.
There is PDroid privacy protection on the market, but it's only for 2.3 and you need to patch the phone.
What i miss is the same SMS/MMS/Phone privacy app built in MIUI. For now, i take extra care when installing new app, double check permission and i use Droid Wall and AdFree to prevent unwanted network access and ads.
Since you put more and more of your life in the phone, i think that a built in permission management and security is needed.
Give the enhancement request a star on Cyanogenmod tracker
utonto said:
I think this is not considered a design flaw neither by Google nor by Cyanogenmod team. Google may have interest in pleasing developers, who make money out of data mining, Cyanogemnod may just be too popular and just need to comply with higher regulations in order to survive.
Click to expand...
Click to collapse
There's been a lot of speculations and ambiguous mambo jambo on this that can't be taken seriously. If a developer want's to implement this, there's nobody in the power of stopping it. See feature request in Cyanogenmod issue tracker: code.google.com/p/cyanogenmod/issues/detail?id=6615 and give it a star.
spidermoon said:
I have an old Desire with CM7 and i can set permission per application if i remember. I'm surprised that this feature was remove from CM9 ?
I try LBE, but it's slow the phone and can easily crash.
There is PDroid privacy protection on the market, but it's only for 2.3 and you need to patch the phone.
What i miss is the same SMS/MMS/Phone privacy app built in MIUI. For now, i take extra care when installing new app, double check permission and i use Droid Wall and AdFree to prevent unwanted network access and ads.
Since you put more and more of your life in the phone, i think that a built in permission management and security is needed.
Click to expand...
Click to collapse
It was never removed, just not ported forward/redone for ICS/JB. Give it a star at code.google.com/p/cyanogenmod/issues/detail?id=6615
Related
Market filters:
When a user searches or browses in Android Market, the results are filtered, and some applications might not be visible. For example, if an application requires a trackball (as specified in the manifest file), then Android Market will not show the app on any device that does not have a trackball.
The manifest file and the device's hardware and features are only part of how applications are filtered — filtering also depends on the country and carrier, the presence or absence of a SIM card, and other factors.
Changes to the Android Market filters are independent of changes to the Android platform itself. This document will be updated periodically to reflect any changes that occur.
Click to expand...
Click to collapse
Does anyone have any idea what the market filters are checking against?
That's not really a good reason to do anything, let alone not using 2.2
dik23 said:
That's not really a good reason to do anything, let alone not using 2.2
Click to expand...
Click to collapse
Not being able to get apps? Did you read the link? Doubtful. Uh sure. Have fun with vanilla 2.2 and 0.0 apps.
I'm sorry, did you read your own link? If you had scrolled down, it shows several examples of what can be filtered. The filters are implemented by the application developer themselves, and if they don't, they still show up in the market.
Besides, filtering by the application has been in Android since 2.0. Any application that deems a device incapable of running it (for example, a lack of a light sensor) can stop itself from running.
some kind of filter (the ones I've heard of so far are incompatible screen resolution, unverified builds, and protected apps) is already being applied to 2.1 in the AOSP build. I couldnt see Yelp, the Android Community and TMZ apps for whatever reason
cashless said:
Not being able to get apps? Did you read the link? Doubtful. Uh sure. Have fun with vanilla 2.2 and 0.0 apps.
Click to expand...
Click to collapse
Oh yeah, how suspicious. French people couldn't possibly prefer apps in French and people with that new Dell pad thing probably still want SMS and contact apps.
Yeah
so you are saying not upgrade to 2.2 because marketplace will filter apps for our phone, but stick with 2.1 because it doesn't?
well genius, why don't you go and install http://www.appbrain.com/app/com.yelp.android on your phone and let us know how that 'no filtering' works out for you.
When I was running my Vougue we ran into this problem as well, its not a big deal at all. from what I remember it was checking about the build.prob and screen size that is setup in your startup. what I used to do was set my phone to my the specs for the G1, then install the apps after adjusting the density to fit everything on screen and then reboot using factory startup. it worked pretty well for most of the apps since many only blocked off whatever border the developer had.
heres the problem though but with the pace we are going it wont come up for a while, once we decide we have a rom stable enough to flash we lost the abilty to change the settings since WM is copletely gone and no haret was used. I switched over to the Touch Pro and we had the exact same problem which was solved in the EXACT way but we were not flashed still(TP2 still has a LOOOONG way to go sad to say), kept the touch pro 2 for only a few weeks before they replaced my Sprint Line TP with a Touch pro 2 due to all the TP1 problems and i'm still saddened by the slow progress. I am a developer myself and even an avid budsmoker and was still able to help out. now Refer has done a great job but from my understanding he is just doing most changes to the Android Filesystem, theirs a couple other guys working on the kernels which would be were all the hardware problems are going to be fixed from. no matter what build we use something in the kernel is either not right, or we dont have the driver in place for Android itself and since we have few Hardware level developers working on these things it seems to be low progress.
Why doesn't Google just add the best features of all these ROMs into native Android?
It's so stupid that people have to root their phones in order to get these features. I understand that maybe Google doesn't want Android to seem overly complex, but have a Customization area all in a submenu that you can unlock buy sliding Customizations to ON.
Things like this (in order of necessary > bloat):
Global volume rocker as cursor movement keys (hope this baby is patented so Apple doesn't steal it!)
% battery icon
Brightness slider toggle + AOKP toggles!!!!
Screenshot on Power Menu
Volume panel
Custom targets on lockscreen ring
Custom notification LED colors >> this would really make the hardware unique from Apple and it's really handy, esp when you're in meetings / theaters / church / or any quiet time; the different color assignments are really useful! Even vibrate is now disruptive in meetings.
Weather on lockscreen
Show notification count
Custom colors for Nav Bar
I don't think that's so much that it would overwhelm the average user. Whenever a family member or friend sees our phones, they want me to root theirs and make it the same.
Maybe someone at Google can get this message and we can see this in 4.2? They could release it as a "Android Power Toys" add-on type marketing the way Microsoft did with Windows?
I'm sure there are a number of reasons. First many of these things can be done with third party apps. Google mainly keeps to things that have to be built into the os, or related to Google services.
They have incorporated some features like additional lock screen targets, some toggles on tablets, resizable widgets, ect. It sounds like themes may be coming in 4.2 too.
Another thing I've noticed is while these features are great, they do slow things down a bit, so they may not be beneficial to everyone.
I'm fine with getting these features from other sources of they can put out things like project butter and Google now.
Sent from my Nexus 7 using xda premium
A lot of what you listed up there I would term bloat, lots of unnecessary options for features I don't want.
Toggles are the exception, I'd love to see a really nice AOSP toggle implementation. I think most normal users would like that too.
Copywrite violations.
I think an easy explanation may be, because the Nexus line is currently only two devices (including the N7). Nexus owners comprise a very small segment of the Android population, and Google develops the device with root users, ROM devs, and themers in mind...meaning, they know we're going to change our devices ourselves (which is part of the fun), so they may not find all of those changes necessary for the Nexus line.
As it pertains to Android in general, I think manufacturer skins (Touchwiz, Sense, Blur) would be the primary deterrent. Google would spend all that time, developing features, that manufacturers would either alter or delete entirely, meaning Google had wasted time and man-hours on developing those additions.
However, word on the street is that LG is getting the Nexus next, but that all manufacturers will also have the ability to make a Nexus device, provided they follow Google's guidelines. This means Nexus devices in the hands of more end users, and possibly, an increased impetus for Google to incorporate some of the features you mentioned. I think we'll see 4.2 and 5.0 implementing some massive changes to the system, in regards to customization and personalization.
Personally, I would like to see the launcher improved. There's no reason why Google couldn't spend a little more time, and create a customizable launcher, like Nova or Apex. That would be a massive improvement IMHO, and one that every user could benefit from. The current launcher is nice, but I know very few rooted users who actually prefer Launcher2 to either of the aforementioned launchers.
Sent from my SCH-I800 using Tapatalk 2
I wonder if they are not included for the sake of simplifying the OS for the average user. It's a lot easier to get someone to just add a widget to add functionality than to explain to them how to enable weather on the lock screen or how to pick which pull-down toggles they want. A lot of those options are redundant because you can access them with widgets on the launcher.
redwingfaninnc said:
I wonder if they are not included for the sake of simplifying the OS for the average user. It's a lot easier to get someone to just add a widget to add functionality than to explain to them how to enable weather on the lock screen or how to pick which pull-down toggles they want. A lot of those options are redundant because you can access them with widgets on the launcher.
Click to expand...
Click to collapse
That makes sense, but honestly, how many Nexus owners do you know that fit into the "average user" category? I know 35 people who own a Nexus device, and only 3 of them aren't rooted. In general Android terms, you're probably 100% correct though...most "average users" would not know what to do with some of those changes, and many would consider them bloat. Geez, Google's even removed Maps from Gapps, because people thought it was bloatware, so they are sensitive to that issue.
Sent from my SCH-I800 using Tapatalk 2
Remoteconcern said:
A lot of what you listed up there I would term bloat, lots of unnecessary options for features I don't want.
Toggles are the exception, I'd love to see a really nice AOSP toggle implementation. I think most normal users would like that too.
Click to expand...
Click to collapse
I agree, what prompted this post was the AOKP toggles, that's what people like the most when they see mine and my gf's phones.
Also, I agree that it's bloat. But, that's why they can release it in the Play Store as a "Power Toys for Android" add-on. It makes it easy for average users to get access to these features and they don't have to root and they don't have to play the milestone game waiting for a stable daily driver.
jjhiza said:
I think an easy explanation may be, because the Nexus line is currently only two devices (including the N7). Nexus owners comprise a very small segment of the Android population, and Google develops the device with root users, ROM devs, and Turner's in mind...meaning, they know we're going to change our devices ourselves (which is part of the fun), so they may not find all of those changes necessary for the Nexus line.
As it pertains to Android in general, I think manufacturer skins (Touchwiz, Sense, Blur) would be the primary deterrent. Google would spend all that time, developing features, that manufacturers would either alter or delete entirely, meaning Google had wasted time and man-hours on developing those additions.
However, word on the street is that LG is getting the Nexus next, but that all manufacturers will also have the ability to make a Nexus device, provided they follow Google's guidelines. This means Nexus devices in the hands of more end users, and possibly, an increased impetus for Google to incorporate some of the features you mentioned. I think we'll see 4.2 and 5.0 implementing some massive changes to the system, in regards to customization and personalization.
Personally, I would like to see the launcher improved. There's no reason why Google couldn't spend a little more time, and create a customizable launcher, like Nova or Apex. That would be a massive improvement IMHO, and one that every user could benefit from. The current launcher is nice, but I know very few rooted users who actually prefer Launcher2 to either of the aforementioned launchers.
Sent from my SCH-I800 using Tapatalk 2
Click to expand...
Click to collapse
The launcher is a great idea too. I forgot to mention that. However, Nova launcher is easy for the average user to install. You don't even need to be rooted.
Neo3D said:
The launcher is a great idea too. I forgot to mention that. However, Nova launcher is easy for the average user to install. You don't even need to be rooted.
Click to expand...
Click to collapse
Very true, but most normal Android users simply run the out-of-the-box setup from day one, until the day they upgrade. If Google took the time to build a slightly better launcher, those of us who want extra customization (grid size, icon editing, etc) can have it, while those who run stock from day one, won't even notice the changes, because they'll never use them.
Looks like Google might be one step ahead of us.
http://www.androidpolice.com/2012/1...oject-roadrunner-updated-google-play-and-now/
"Customization Center"?
That would be sweet if it were true and included some of these awesome ideas that custom ROM devs have come up with.
That's generally how it works, Google borrows from developers and OEMs' UIs.
Sent from my ADR6400L using xda app-developers app
jordanishere said:
Copywrite violations.
Click to expand...
Click to collapse
What copyright? If i remembered correctly all custom ROMs are open sourced, which means copyright doesn't apply.
Do correct me if i'm wrong.
jimmyco2008 said:
That's generally how it works, Google borrows from developers and OEMs' UIs.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
This is it right here. Let the devs do the muscle and brain work and Google cherry picks what they think should be the next evolution of android.
The great thing about open source is that sharing is what it is all about. If you don't like sharing, then there are two other clubs to join. Both of which could be more awesome if they didn't take the mine all mine approach.
...
@rbiter said:
This is it right here. Let the devs do the muscle and brain work and Google cherry picks what they think should be the next evolution of android.
The great thing about open source is that sharing is what it is all about. If you don't like sharing, then there are two other clubs to join. Both of which could be more awesome if they didn't take the mine all mine approach.
...
Click to expand...
Click to collapse
Yep, all about the cherry picks.
Perfect example is SMS quick reply, I'd say that's a dead cert as the immediate reaction to JB notifications was fantastic but let me do even mooaaar!!!
Sent from my Galaxy Nexus
They can't just slap every option in the world in. You'd have a bloated mess. (That's part of why skins are so bad... feature overload).
Sent from my Galaxy Nexus
Most of those things can be do e from an app, maybe Google let's the door open to the free market and get devs to earn money making these addons.
Sent from my Nexus 7 using Tapatalk 2
Besides, if Google took all the best features from our ROMs, nothing would hardly ever need updating in future versions.
I Am Marino said:
Besides, if Google took all the best features from our ROMs, nothing would hardly ever need updating in future versions.
Click to expand...
Click to collapse
Well I think its important to note that even if Google wanted to implement some of these features commonly found on custom ROMs that it'd take more than just one version of Android to bring them in.
jjhiza said:
I think an easy explanation may be, because the Nexus line is currently only two devices (including the N7). Nexus owners comprise a very small segment of the Android population, and Google develops the device with root users, ROM devs, and Turner's in mind...meaning, they know we're going to change our devices ourselves (which is part of the fun), so they may not find all of those changes necessary for the Nexus line.
As it pertains to Android in general, I think manufacturer skins (Touchwiz, Sense, Blur) would be the primary deterrent. Google would spend all that time, developing features, that manufacturers would either alter or delete entirely, meaning Google had wasted time and man-hours on developing those additions.
However, word on the street is that LG is getting the Nexus next, but that all manufacturers will also have the ability to make a Nexus device, provided they follow Google's guidelines. This means Nexus devices in the hands of more end users, and possibly, an increased impetus for Google to incorporate some of the features you mentioned. I think we'll see 4.2 and 5.0 implementing some massive changes to the system, in regards to customization and personalization.
Personally, I would like to see the launcher improved. There's no reason why Google couldn't spend a little more time, and create a customizable launcher, like Nova or Apex. That would be a massive improvement IMHO, and one that every user could benefit from. The current launcher is nice, but I know very few rooted users who actually prefer Launcher2 to either of the aforementioned launchers.
Sent from my SCH-I800 using Tapatalk 2
Click to expand...
Click to collapse
Ahhh jjhiza. Havent seen one of your essays since the droid3 days aha
Sent from my Galaxy Nexus using Tapatalk 2
it will be possible a porting of samsung multiwindows for the nexus 4?
Possibly, though I'm pretty sure that MultiWindow requires hooks in Touchwiz, so you would need a Touchwiz based ROM on 4.2 for it to work.
I'd love this on the N4 aswell. But it might need as said before a touchwiz rom or maybe CM11?
a rom with touchwiz wil be ok for me
There probably won't be a fully functioning Touchwiz ROM for our phone.. There are plenty of "floating" apps that offer similar functionality.
Sent from my Full Android on Grouper using Tapatalk 2
Doesn't paranoid android have this feature? And I remember a rom for the hp touch pad had this thing called cornerstone which allowed for multiple apps to be displayed at once
Sent from my Nexus 4 using xda app-developers app
neer2005 said:
Doesn't paranoid android have this feature? And I remember a rom for the hp touch pad had this thing called cornerstone which allowed for multiple apps to be displayed at once
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Google basically asked cornerstone to stop development of that app I think. I read that somewhere. Not sure where though.
Sent from my Nexus 4 using Tapatalk²
See post below.
kcls said:
Google basically asked cornerstone to stop development of that app I think. I read that somewhere. Not sure where though.
Sent from my Nexus 4 using Tapatalk²
Click to expand...
Click to collapse
Here is some helpful info
https://groups.google.com/forum/?fromgroups#!forum/cornerstone-dev
Basically what it looks like was Cyanogenmod was going to include Onskreen Cornerstone in their CM10 builds but Google are trying to stop it in a somewhat threatening maner.
See this post for more information
CM10 said:
Steve Kondik
Join group to reply
More message actions
Feb 15
We (the CM team) have been experimenting with Cornerstone on our
tablet builds. There are a few things to iron out, but for the most
part it's working pretty well. What is causing me some concern, is a
response to a re-share on Google+ by Dianne Hackborn, an engineer at
Google working on the Android platform. She raises some pretty valid
concerns (probably threatening to ban us from the Market if we include
it was a bit far over the line, though). I was wondering if someone
from Onskreen would care to comment?
https://plus.google.com/u/0/100275307499530023476/posts/ViCME1bb8F6
Click to expand...
Click to collapse
Google said:
Dianne Hackborn
15 Feb 2012
+56
Okay, let me please please beg you not to do this. I can guarantee you this introduces all kinds of application compatibility issues. We work really hard to give our developers a consistent environment where their apps will operate correctly across all the devices Market runs on, not being impacted by negative reviews from bad devices that they should not have to deal specially with.
If you start making your own distributions of Android behaving in such fundamentally different ways, I suspect we are going to need to start doing things to prevent you from impacting our app ecosystem. I'm not sure what, but I could imagine things such as restricting how users can interact with Market apps on these devices (not allowing reviews or such).
We have let a lot of things in this area slide -- for example to be allowed to include Market on your device you are supposed to fully pass CTS. However, if you start really diverging from the core Android platform (I would argue this takes you well into the realm of a fork rather than a customization) then some deep issues are going to come up about how we handle these custom builds.
We have been putting a lot of thought and work for a number of years into how to let Android applications run on increasingly diverse and dynamic screens. Doing this correctly, without impacting our app developers in a negative way, is a really challenging problem. I also think it is something that needs to be done at the mainline platform level, not as a customization, because doing it right is going to require new well defined interfaces with applications for them to interact with it, possibly starting with just a facility they need to use to opt in to it.
Click to expand...
Click to collapse
Cornerstone dev said:
onhsnm
Feb 15
Steve,
Thanks for reaching out. We have heard variations on this theme for
some time, so it appears that it is time for us to respond.
We very much appreciate the amount of work that the Android team has
done to address the complexity of supporting applications on the
variety of screen sizes that "real" Android runs on. The Onskreen team
has spent an immense amount of time to continue that effort while
creating the Cornerstone experience.
As far as responding to Diane's comments directly, it’s a bit
difficult because there are no specific concerns mentioned. Her
contention appears to be that changes were made to the Android
Framework at all, not with anything specific with Cornerstone. We'd be
happy to have a conversation with them about anything specifically
they feel negatively impacts apps. We have more work to do on the
product so there are definitely items on our todo list to continue to
improve, but the first release clearly stays within the realm of an
Android optimization (most definitely not a fork) and outside of bugs,
does not break Android apps.
One of our goals was to support Android applications unchanged without
introducing Cornerstone specific APIs or modifications that
applications must conform to. As Diane said, there are some great
things we could have done by introducing multi-tasking specific
interfaces and manifest declarations, but we did not so Cornerstone
did not fragment from Android as it exists today. After all that is
what the app developers have targeted for their apps. Throughout the
code, you will find a number of architectural decisions to ensure apps
run without fragmentation (Ex: setting correct Configurations, not
running multiple instances, etc...); as well as feature decisions to
ensure the same (Ex: ability to turn Cornerstone off, removing the
ability to swap so that apps weren't forced to deal with changing
screen size, etc...)
Threats to rescind Market access are a bit much, we prefer to stick to
specifics and open a dialogue. We are happy to discuss specific
concerns and we expect that once the Google team has had a chance to
dig into the code, we will hear some. We also expect that dialogue to
make Cornerstone better for everyone, one of the reasons we open
sourced the code to start with.
hansmeet.
Click to expand...
Click to collapse
Hi
I want to root my nexus 7 but I do not know about which oen to go with. I am hoping that some experienced users can help me out with choosing the right one. Back in the days there was only cymod, so it was easy. Now that they forked out to a different path I need new directions.
Here is how I will use my android device
I never use gapps
I do not care about gplay
I do not care about million apps out there
I only use Fdroid
I do not care about maps
I do not care about location features
I like it barebones, non bloat
I do not care about interface
I care about privacy (no tracking, no hidden pinging etc)
I care about stability
I do not want to sign up for accounts to boot up
So which rom/rooting method should I go with for my nexus 7 2013?
thanks
h
hajkan said:
Hi
I want to root my nexus 7 but I do not know about which oen to go with. I am hoping that some experienced users can help me out with choosing the right one. Back in the days there was only cymod, so it was easy. Now that they forked out to a different path I need new directions.
Here is how I will use my android device
I never use gapps
I do not care about gplay
I do not care about million apps out there
I only use Fdroid
I do not care about maps
I do not care about location features
I like it barebones, non bloat
I do not care about interface
I care about privacy (no tracking, no hidden pinging etc)
I care about stability
I do not want to sign up for accounts to boot up
So which rom/rooting method should I go with for my nexus 7 2013?
thanks
h
Click to expand...
Click to collapse
You're going to have to try things for yourself. Pretty sure XDA doesn't allow for these threads because they tend to devolve into flamewars rather quickly. Go for AOSP though based on what I can see.
Rirere said:
You're going to have to try things for yourself. Pretty sure XDA doesn't allow for these threads because they tend to devolve into flamewars rather quickly. Go for AOSP though based on what I can see.
Click to expand...
Click to collapse
Rirere thanks for your post. I am not looking for the best rom, or a rom better than x or y. So I doubt that this could turn into a flame war. What I am looking for is a specific rom that comforms to my needs. Also trying all the roms can take long time with alot of mess in my hands that is why I was lookign for recommendations.
Thanks for the suggestion I will check it out.
Which ROM is the best type threads are no longer allowed on these forums...
My personal recommendation would be if you have been familiar with CM chose that rom. If for any reason your not satisfied with the rom, read up on the rest of the OP's features and make your decision.
-Thread Closed
Hello,
I'm going to take the jump to a custom rom on my s4 mini. Yet I've tried to enforce my privacy on a non-rooted samsung android 4.2.2 with NoRoot Firewall, SRT: AppGuard and F-Droid apps.
From my own search OmniROM would be the one I'd like to go for but it is not available to the s4 mini. Next one wold be Replicant that is neither available to the s4mini. CyanogenMod + freecyngn would help with the proprietary parts, something I'm also looking for (as some custom roms use e.g. Nova launcher) but doesn't get rid off googles own call back/tracking/identification services in use (I don't/won't use).
Thanks for your help in advance!
I am curious, what do you use for email? your own email server?
chemicalrage said:
I am curious, what do you use for email? your own email server?
Click to expand...
Click to collapse
a German email provider via pop3, encrypted with PFS and DANE/DNSSEC, ip-stripping, anonymous payment, no sale/trade of data, their Linux-server encrypted with dm-crypt/LUKS, internal connections encryted with SSH and TLS, harddrives (mails on it) encrypted therefor too, etc.
No_Signal said:
a German email provider via pop3, encrypted with PFS and DANE/DNSSEC, ip-stripping, anonymous payment, no sale/trade of data, their Linux-server encrypted with dm-crypt/LUKS, internal connections encryted with SSH and TLS, harddrives (mails on it) encrypted therefor too, etc.
Click to expand...
Click to collapse
woah...that's crazy. What OS do you run on your PC/Laptop? Did you check out http://prism-break.org/en/ ?
I don't want to go into this too much as it might become rather a positional discussion/debate on principles.
In no way I'm speaking for everyone here, don't mean to offend anyone and if it helps read it as my personal opinion:
Most likely Germans (Europeans) have another view on privacy due to their history and experience and are sensible to it.
[censoring myself and cutting it down to] a hypothesis what for Americans is their right of freedom of speech, is for Germans right of privacy which threatened.
Back to topic please
If I understand correctly, any ROM that doesn't have gapps built in (which is most/all bigger releases) will do what you want. Just don't install gapps manually
No_Signal said:
Hello,
I'm going to take the jump to a custom rom on my s4 mini. Yet I've tried to enforce my privacy on a non-rooted samsung android 4.2.2 with NoRoot Firewall, SRT: AppGuard and F-Droid apps.
From my own search OmniROM would be the one I'd like to go for but it is not available to the s4 mini. Next one wold be Replicant that is neither available to the s4mini. CyanogenMod + freecyngn would help with the proprietary parts, something I'm also looking for (as some custom roms use e.g. Nova launcher) but doesn't get rid off googles own call back/tracking/identification services in use (I don't/won't use).
Thanks for your help in advance!
Click to expand...
Click to collapse
Would be interested if you find something. So far I did not have luck, so running a patchwork of privacy extenions
- cyanogenmod
- freecyngn
- xprivacy
- afwall+
I am as far as possible away from any google apps, but even every other app is pretty much gathering data they won't need to function.
Funny side effect is extended battery life, since a lot of the syncing and data usage is cut out.
You might also look into compiling and doing some changes to cyanogenmod yourself, as getting strong ciphers otherwise is pretty hard.
Regards
Chris
sysKin said:
If I understand correctly, any ROM that doesn't have gapps built in (which is most/all bigger releases) will do what you want. Just don't install gapps manually
Click to expand...
Click to collapse
Nope, that's not correct - even without gapps your android mobile will phone home to google. There are still parts of the system that are open source and communicate with Google (eg. AGPS and captive portal check). These are just some examples.
Though CyanogenMod always claimed to be open-source, there were only few versions that had an open userspace (Some drivers and firmware have always been proprietary, but it's not CMs fault).
The first CM version I ever installed on a device was CM7 and it contains koush's proprietary ROM Manager app. CyanogenMod 9 seemed to have no proprietary parts, but since CM10 they included Google Analytics Client library (libGoogleAnalyticsV2.jar) within cmstats in the settings app (so it's not even possible to disable it). In CyanogenMod 10.1 CMAccount was included. It relies heavily on Google's Cloud Messaging service and includes the proprietary Google Play Services Client library (google-play-services.jar).
There are some people here at xda (including myself) that installed CyanogenMod because it does not ship GAPPS and is a fully (except vendor files) open-source and free rom. Since i noticed it's not, i started building CM without these closed-source stuff, but it's a pity to do so. That's when the idea of freecyngn started.
Click to expand...
Click to collapse
[TOOL/SCRIPT] freecyngn - Removing proprietary userspace parts from CM10+
Being completely anonymously in this world never was an option for me because it simply takes too much energy.
However, since I already have all applications I need there's really no sense left in using gapps right now, they annoy me.
I can't contribute much for the current problem of privacy but want to throw in some hope for the future (availible from 2015):
http://en.wikipedia.org/wiki/Galile...on)#Political_implications_of_Galileo_project
phz. said:
Being completely anonymously in this world never was an option for me because it simply takes too much energy.
However, since I already have all applications I need there's really no sense left in using gapps right now, they annoy me.
I can't contribute much for the current problem of privacy but want to throw in some hope for the future (availible from 2015):
http://en.wikipedia.org/wiki/Galile...on)#Political_implications_of_Galileo_project
Click to expand...
Click to collapse
The Galileo Project might become one part of the puzzle.
Something I'm looking forward to is Liberate your Android device.