securing older Android (2.3 4.4 5.0 etc) incl workarounds? - Android General

Could someone point me to good resources on how to properly set up and secure older versions of Android for phones and tablets if that's all you have to use?
For instance I remember hearing of some huge exploit for Android 4.4 I think involving MMS - which sounded like if you just turned of multimedia SMS's the phone would be okay. I am wondering if there are other critical holes or if workarounds like that can stop them?
I'm no security expert and so I don't even know what all various holes exist on various models to begin with, whether certain ones are a hack waiting to happen for instance. Previously my biggest concern about which android runs on something is whether it's new enough to run the app I want. Or trying to avoid models known to ship with malware from china like this AdUps crap. I'm sure that's no longer good enough but i'm not sure where to start learning what I need to know. I don't want to become a sysadmin or hacker, just take reasonable steps to protect personal data and such.
Where is the easiest places to get up to speed and start learning?

Related

Transitioning: Jailbroken iPhone 3GS to Captivate

For anyone considering making the switch, I thought I would give some details on my experience having recently done this myself.
I had an iPhone 3G for about a year before I finally decided to jailbreak it and play with extra features. This led to all out phone modding with my 3GS, and finally the decision to move to Android for even more customization and utility. Here, i'll compare the experience I had with either device for inquiring minds contemplating a similar conundrum.
Jailbreaking and rooting; these words mean essentially the same thing: you gain full access tot he device's file system. There is, however, a distinct difference in the end result. With the iPhone, you typically jailbreak by running a utility that uses a software (or in some cases hardware) exploit to essentially exploit your way in.
Almost all of these will then install Cydia, a type of App Store that is not policed by Apple, and offers apps that only work on jailbroken devices because of their need to access parts of the file system that are typically restricted. From Cydia, you can download and install free and paid apps, and even gain access to black-market sources like Install0us where you can download pirated versions of paid apps.
Cydia contains what I consider to be the staple, or common, jailbroken apps. A few are:
MobileSubstrate: an underlying framework that provides an interface for the phones hardware that is common across many apps.
SBSettings: an easily accessible menu for controlling various functions, and displaying status information (wifi toggle, internal IP address, etc).
Winterboard: a theming app that essentially creates a layer on top of the existing UI to substitute a custom element for a standard one.
There are many others, many of which have been superseded by Apple's own improvements to their OS, such as Backgrounder for multitasking. The entire experience of theming and loading unapproved apps had a very under-the-table feel to it, and it was often difficult to find exactly what I needed, if even possible.
The upside of the iPhone with this is the nearly invincible nature of its systems. Barring hardware failure, or trying intentionally to do it, I can't see how it is even possible to brick an iPhone 3G or later. No matter what you do to it, you can restore it from iTunes and start over.
Android was a very different story. The initial path into rooting and flashing was scarce and difficult to follow at first. I heard a bunch of terms that I had no meaning for, and found it difficult to make sense of it all. Fortunately with the help of a few kind souls here on XDA, I learned what I need to know.
The rooting and modding experience did not have the slightly criminal feeling to it like my experience with the iPhone. I knew neither Apple nor Google was going to bother at all if I wanted to mess with my device; there was nothing to hide. The rooting process was very simple once I understood it, and using ADB from the Android SDK (I'll give details later) made the whole process feel comfortable with good directions. Adding non-market apps was a breeze with the Side-load Wonder Machine.
Finally I decided to try a custom ROM the day that I saw the leaked Froyo beta. Everything else had gone very well, so I felt confident as soon as I learned how to test 3-key download mode and found it successful. I had initially intended to try Cognition, but a recommendation for Assonance made me change my mind. Again, with good instructions, I flashed Assonance 3.1 with great success and have been enjoying the many benefits of custom ROMs since.
Thanks for reading if you've stuck with me thus far.
TL;DR (the experience broken down)
Rooting
iPhone: A full package process that is railroaded for better or worse. Even in the jailbreak community, you have very little options with iPhone. Some folks like--or need--it that way.
Android: At once it feels a little riskier at first, but if you play it safe, you'll find this just unlocks a door to more options.
Unapproved Apps
iPhone: Cydia, Rock, Install0us. What you see is what you get, and just pray the developer of your favorite apps doesn't quit. It can be hard to pay for things without paypal.
Android: It literally could not be easier. You don't even need to root first: http://www.androidcentral.com/sideload-android-apps-all-you-want-sideload-wonder-machine
Theming
iPhone: Tedious or slow; pick your poison. You can either manually replace each UI element yourself, making backups of the originals just in case, or you can use Winterboard, and deal with the performance hit. The plus side is that once you get the basics it is pretty standard across the board.
Android: Theming in general is much easier with LauncherPro, Desktop Visualizer, OpenHome, or ADW; but if you want to do the really detailed things like skin the dialer buttons, you are looking at something quite a bit more arcane than simple PNGs in iPhone. Some of this can be overcome by flashing various themes, but it still isn't individual control.
Functionality
iPhone: For functions not built into iOS, you have a few choices which aren't really choices as much as must-haves. Beyond that, you can just hope someone will happen to make what you need, and it will be maintained through iOS updates.
Android: The sky is the limit, but you need to be able to fly the plane. I can't make apps; no idea how, but the majority of my wishlist for the iPhone was built into Android 2.2 out of the box..
Reliability
iPhone: As I said before, a hardware failure is pretty much the only major dead end, but any piece, even the battery pretty much means a new phone.
Android: Software reliability will take more work than it will on the iPhone. You don't have iTunes making a full restore backup every few days, so you'll need to take the initiative yourself to make copies of pictures and music, and backup apps.
I know this ended up being a little scatterbrained, but hopefully it will help someone out in making the right choice for them. Remember, the iPhone is like James Bond: he is the best there is at doing exactly what he was meant to do. Then Android is like MacGyver: a little rough around the edges, but given the right tools he can do anything. One isn't better, they are just different. Choose what is right for you, stay in school, and don't do drugs.
Haha you got me with the last sentence.
agreed
I agree with what you said. I had an iPhone but couldn't stand to keep it for the full two years so I got rid of it early and got a Captivate. I jailbroke the iPhone and had the same experience you describe. I can't say that any of the jailbreak apps/tweaks were really an improvement over stock iOS, although they do slow the phone down pretty badly and cause it to crash frequently. I haven't rooted my captivate yet (still a few more weeks of getting used to the unrooted captivate) but even unrooted android is vastly more customizable than the iPhone. I just got ADW launcher and none of the regular/jailbroken iPhone apps could do anything like it.
Note one difference between the two: you can install only apps and "tweaks" into a jailbroken iPhone (like 'custom icons'), while you can install custom ROMs/OSs into the android. The iOS source code is not released publicly so devs can't modify the entire OS like they can with android. It is hard, in my opinion, to justify jailbreaking an iPhone because it adds nothing important, but does slow the phone down and make it crash.

Privacy Protection and Data Security in WP7/8

Hello everybody,
I am currently using an android phone and consider to switch to WP8 after it has been release due to better hardware concepts etc.
I already read that WP7 apps are executed in a sandbox and therefore the whole process aint to be more "secure". Anyhow, Iam not concerned about a virus or malware.
My biggest aim is to keep my data private and to secure my privacy.
Regarding WP7 I could not find any hint about that topic. I cannot imagine that nobody cares about this topic around this OS !?
What I want is the following:
Set for each app what it is able to access (e.g. Access to contacts, location etc.)
Control internet access for each app
Maybe it already exists and therefore nobody talks about it, maybe it is technically not possible.... Just want to know
Thank you in advance for your help.
Regards.
WP7 (and presumably WP8) apps use a "Declared Capabilities" model for controlling access to resources like you mention. That is, if an app wants to access the network, it must declare ID_CAP_NETWORKING in its manifest. If it wants to access your contacts, it must declare ID_CAP_CONTACTS... etc. When you view an app in the Marketplace, you can see what capabilities it includes.
However, there's not really any fine-grained control over such things. For example, if you install an app that wants access to your contacts and your appointments, you can't tell it "OK on Appointments, but no Contacts access" short of modifying the app prior to installing (and if you did that, there's a good chance the app would crash when you ran it). Similarly, there's no user-controllable firewall on the phone; an app that specifies ID_CAP_NETWORKING can access anything that is available on the network.
I believe this is similar to the behavior of stock Android ROMs. The advantage that WP7 (and presumably also WP8, but it's too early to tell) has over Android in this regard is that apps go through a much more extensive review process. If an app needs to access your contacts, for example, it better have a good reason for this access and and it will (well, should) be rejected if it sends them off to some advertising company or something.
GoodDayToDie said:
WP7 (and presumably WP8) apps use a "Declared Capabilities" model for controlling access to resources like you mention. That is, if an app wants to access the network, it must declare ID_CAP_NETWORKING in its manifest. If it wants to access your contacts, it must declare ID_CAP_CONTACTS... etc. When you view an app in the Marketplace, you can see what capabilities it includes.
However, there's not really any fine-grained control over such things. For example, if you install an app that wants access to your contacts and your appointments, you can't tell it "OK on Appointments, but no Contacts access" short of modifying the app prior to installing (and if you did that, there's a good chance the app would crash when you ran it). Similarly, there's no user-controllable firewall on the phone; an app that specifies ID_CAP_NETWORKING can access anything that is available on the network.
I believe this is similar to the behavior of stock Android ROMs. The advantage that WP7 (and presumably also WP8, but it's too early to tell) has over Android in this regard is that apps go through a much more extensive review process. If an app needs to access your contacts, for example, it better have a good reason for this access and and it will (well, should) be rejected if it sends them off to some advertising company or something.
Click to expand...
Click to collapse
I see. So basically this means, that I could edit the manifest file of any application myself and set the level of access I want it to have, but the application will probably not work anymore.
For instance, I have an navigation app that wants access to my contacts to offer me a direct navigation option to my friends place as well as internet access for current traffic information. Do I need to trust microsoft, that they reviewed this app so well that it does not send my contact list to the software company ?!
Moreover, this way I cannot prevent microsoft for example to collect whatever they want from my phone, right ?
It is correct, that stock Android does not offer this function, too. However there is the possibility to root it and have apps installed that control all traffic, even those of the OS itself.
ntech3333 said:
I see. So basically this means, that I could edit the manifest file of any application myself and set the level of access I want it to have, but the application will probably not work anymore.
Click to expand...
Click to collapse
Yes. Applications are expecting to see all CAPs they request, as this is an all-or-nothing thing in WP. If you'd edit their manifest, the application could behave arbitrarily, and it would likely crash because an essential assumption it made - that being either it has the CAPs it requires or isn't installed - isn't applicable anymore.
Moreover, this would require at least a developer unlock, for some applications (for instance Skype) an interop unlock and for some applications (all XBL ones at least I think) a custom ROM.
ntech3333 said:
For instance, I have an navigation app that wants access to my contacts to offer me a direct navigation option to my friends place as well as internet access for current traffic information. Do I need to trust microsoft, that they reviewed this app so well that it does not send my contact list to the software company ?!
Click to expand...
Click to collapse
Yes. There is no way to partially grant permissions.
ntech3333 said:
Moreover, this way I cannot prevent microsoft for example to collect whatever they want from my phone, right ?
Click to expand...
Click to collapse
Microsoft makes the system. If they wanted to hide something in kernel mode, and wanted to hide it from all user accessible APIs, this would be easily done. Simply spoken, if you question Microsoft's commitment to their EULA, WP is the wrong OS for you.
ntech3333 said:
It is correct, that stock Android does not offer this function, too. However there is the possibility to root it and have apps installed that control all traffic, even those of the OS itself.
Click to expand...
Click to collapse
Without a kernel built from trusted sources, hiding data streams from all APIs is always possible for an OS maker.
ZetaZynK said:
Yes. Applications are expecting to see all CAPs they request, as this is an all-or-nothing thing in WP. If you'd edit their manifest, the application could behave arbitrarily, and it would likely crash because an essential assumption it made - that being either it has the CAPs it requires or isn't installed - isn't applicable anymore.
Moreover, this would require at least a developer unlock, for some applications (for instance Skype) an interop unlock and for some applications (all XBL ones at least I think) a custom ROM.
Yes. There is no way to partially grant permissions.
Click to expand...
Click to collapse
A custom rom, unlocking etc. is not an obstacle as long as it is possible and serves the purpose
In general I would assume, that any application should be able to run without an internet connection, since it could be possible that you are just not connected to the internet for some reason ?? Therefore, removing the CAP for internet access by editing the manifest file should not lead to any unwanted behavior. Or is it more like that, that all apps check their CAPs they requested on startup and not only when they want to access some ressource ?
This way it would be possible to remove internet access for any application I do not want to send data somewhere without blocking others and without the necessity to remove other CAPs.
Microsoft makes the system. If they wanted to hide something in kernel mode, and wanted to hide it from all user accessible APIs, this would be easily done. Simply spoken, if you question Microsoft's commitment to their EULA, WP is the wrong OS for you.
Without a kernel built from trusted sources, hiding data streams from all APIs is always possible for an OS maker.
Click to expand...
Click to collapse
Generally spoken, I trust nones commitment to any EULA or something. Microsoft, Apple, Google, they all have such documents and every few weeks something comes out that they are tracking you, (anonymously ) etc. Everytime the answer is something like "oh, what a mistake, of course it was not intended to be..."
Of course I do want have the comfort of a smartphone, a tablet pc or a computer, but I want to perserve and control my privacy to such an extend that I am satisfyed with it.
Even on a Windows computer I have got the possibility to control network traffic, to limit access for certain software etc., even to limit access for the OS. So why the heck nobody is interested to have that on a smartphone, why an smartphone must be an free bazar of private information everybody can have and do what they want with it ?
What I want and hope is, that with WP8 (since it will be the same kernel than the PC version) something like that will be possible. Just like on a Andriod phone, too where you can grant internet access for everything, even for system components individually.
Removing ID_CAP_NETWORKING will result in an exception (access denied, essentially) when the app tries to call a networking API. Since the app is probably not expecting that particular exception, it will probably crash. Some apps may have very broad exception handling on their network code and simply assume that they don't have access, though.
You don't really have any control like you describe on a Windows computer. You can set the firewall, sure, but then you're trusting Microsoft to not have some leak or backdoor in the firewall. You can write your own drivers to hook it at the kernel level, but then you're trusting Microsoft not to have a direct access to the HAL that bypasses the network driver stack. You can re-write the HAL (OK, not practically, but let's say "you could install another OS" instead) but even then you're still trusting the manufacturers of your motherboard, your CPU, your network interface hardware, your router, your modem...
At some point, you have to trust somebody. A big, publicly-held corporation with many users, a clear privacy statement, and a lot to lose if they screw up fits the bill is your best bet in most cases. Microsoft fits that bill just fine.
GoodDayToDie said:
You don't really have any control like you describe on a Windows computer. You can set the firewall, sure, but then you're trusting Microsoft to not have some leak or backdoor in the firewall. You can write your own drivers to hook it at the kernel level, but then you're trusting Microsoft not to have a direct access to the HAL that bypasses the network driver stack. You can re-write the HAL (OK, not practically, but let's say "you could install another OS" instead) but even then you're still trusting the manufacturers of your motherboard, your CPU, your network interface hardware, your router, your modem...
At some point, you have to trust somebody. A big, publicly-held corporation with many users, a clear privacy statement, and a lot to lose if they screw up fits the bill is your best bet in most cases. Microsoft fits that bill just fine.
Click to expand...
Click to collapse
Ok, what should I answer ? If you use arguments like that you can extend it to what ever you want.
At some point you need to be realistic when looking at security and privacy. There always can be/is a way to bypass systems on a low level basis to do what you intend to. So what ? You cannot pervent this in any OS.
But when using a third party software firewall that comes with its own drivers, you can be sure to certain extend that you have your networktraffic under control.
This is actually not the point I wanted to make about WP7 and probably WP8.
I understand, that for example an navigation app wants to have access to your contacts to offer you the option to navigate to your friends place. I also see, that this app wants to access the internet to get traffic information. But I do not want this app to have neither access to my contacts nor to the internet since I cannot know what data will be transmitted to the software developer. I even to not want them to do some statistics with me gps positioning. NO. as simple as that. What I do with my information is what I decide.
So what I especially do not like is, that most people in the world do not care about such facts at all. They are running behind apple like lemmings, willingly giveing them all information they have and being happy that everything works so fine on their device !? What the... ?
Anyway, it does not matter, my questions got answered, I will have a closer look at WP8 when it is out and see if it possible to keep my stuff under my control or not.
First of all, EULAs are a binding contract for the first parties, which means that if such a thing were to come out, and it is not a very obvious (actual) bug in the software (Apple's local geolocation data retention bug and Microsoft's bug in WP7 that may have determined the location before you pressed "OK" in the dialog are definitely such - they give nothing of advantage to the two companies), they have a problem named "breach of contract": There will be legal action by activist in such a case.
Then, your argument is valid, a firewall would be effective if you trusted the hardware and software environment. However, I wouldn't hold my breath for it: Firewalls or capability removers are just not fitting in the image of a smartphone. On Android, you also require root for this (important point here: a 3rd party device unlock, it does not come built-in - and apps could also stop working if you withdraw rights from them, since the code might not be prepared for such a scenario either), on an iDevice and Windows Phone it's not possible. It's very much the contrary of how smartphone makers would like to market their devices, a scenario where you might possibly not trust your apps - this could even scare users away from smartphones.
Therefore it is unlikely that WP8 will come with such a capability built-in. Even though WP8 will be sharing the kernel with WinRT, it should be noted that both, WP8 and WinRT will require mandatory UEFI Secure Boot from OEMs. It's likely that this cannot be broken at all unless every a very significant hole can be found that permits to breach the chain of trust or the devices' firmware can be attacked. Hence, it isn't even said whether WP8 can be rooted. If WinRT does not come with Windows Filtering Platform (WFP), it would be the same situation as is on WP7.
You are right, of course the EULA is the first thing to mention But about what legal consequences are you talking ? They will be fined to pay some million dollar ?! Ok, nice, but they still have my data. In this case they bought the information, that's all.
Anyway, I do not want to be paranoid and of course also here at some point you need to stop
To have root access on a device that you own is natural for me. I bought it, it belongs to me, that's why I should be the master on my device. For sure, this does not fit in the global tendency of "not to care about your device, just make it run", too.
On a windows computer I can have administrator privilidges as well. Why they do not want to give me this on my smartphone that claims to be a computer somehow, too?
By the way, WFP is quite a useless piece of invention. I once experimented with WFP for some software project on a windows computer and found out, that the same way I can change every rule someone created for the firewall, everyone else can do. Means: I created a rule to pervent skype to access the internet. Guess what ? Right, Skype detected that and 2min later it deleted my rule and created an own one to grant access again. What use does such a system have ?
There's a rather simple reason, "root" is a badword for most mobile manufacturers: piracy. On Android, that's a different story because you typically can install side-loaded applications, but on the iPhone or Windows Phone you require unlocks to pirate. Typically, piracy is not a practical option on them until you have a root unlock. (If you take a look at WP7, you either require an interop unlock or a custom ROM to have more than 10 unsigned apps - if you wanted to pirate, that would impose a very tight limit on the extend you can do such. Students are even limited to 3 unsigned apps). Root is something that circumvents the control systems of the manufacturer - something that neither Microsoft nor Apple have interest in.
WP and iOS have - compared to Android - very low piracy rates, so this is paying off. (For that matter, WP is probably more locked down than iOS: It took 8 months to public availability of an unlock for my HTC Titan; iOS is usually broken much faster)
I think you're confusing Windows Firewall with WFP. The latter is just a programming interface in the network stack, which allows applications to inspect, filter and modify packets in the network stack. It does not have any rules you could set therefore. Windows Firewall comes with rules, and Skype will - if it has proper privileges to do so - attempt to automatically permit itself in the Firewall.
About the EULA, no. In literally any modern country, data found to have been obtained illegally will result in a sentence to delete the data, to pay a fine and likely to pay the victims damages.
You see, that is the point. The possibility to decide upon your own device is taken away from you due to fears and prejugdes of the manufacturer. Why it always must be connected with piracy ? It means that everybody who wants to have root access on his device is potentially criminal and therefore it is better not to ask for it. Nice.
If you buy a modern house with automatic controlled sun blinds, heating etc. Would you accept, that there is a control room in your cellar, where only the company that built your house has access to? You are only allowed to switch on and off the light in your house. Even the sun blinds open and close whenever they want and tell you when you are allowed to look out of the window and when not. Just because you have no "root" access to change that and you need to accept it.
Fur sure, it is nice to have such system where the user has not rights since most users are not experts and causing mostly only problems where in the other way the system runs smooth and stable...
About WFP, yes I just saw that with Win Vista and Win 7 they introduced such way of filtering platform. I really mixed it up with the windows firewall manager that is accessable via API.
I never saw in any case where data has been found somewhere that users got paid damages. Did Apple do when they tracked their users ? I think no. Did they delete the data ? No they did not, they excused and said something like "oh, what a pitty, we will change that in our next update" Quite safe, isn't it ?
What you fail to see is that android is riddled with issues due to its openness, it is suffering in exactly the same way WM did, you may laugh of WM but android owes its roots to WM. Apple and MS saw the issues, and did something about it.
Yes that restricts you, but you and those like you, are a tiny minority, simply put they have bigger things to worry about, and that is average jo an jane blogs. they do not need that level off access and giving it to them is one of the reasons 10,000s of computers out there are nothing but bots used for DDOS attacks
Remember, WM was slated for being buggy and slow, the reality was far from that, but the networks and OEMs had so much control over the OS they literally screwed it sideways and the magic effect was that they didn't even get the blame, MS did! (ring any bells with android!)
Why didn't WP take off as well as it could have? easy, because firstly it didn't have cool roots to an ipod, secondly because MS tightened up on the OS so much it pissed off the networks, im sorry to say, its little to do with apps and side loading, that's just the first thing people think of when they are talking about something they know nothing about.
Networks like to do things their way and I think you will see their influence in WP8 a lot more, and because of that more than anything else, the networks will like it more, if they like it they will sell it, then you will see a larger uptake in it and thus more apps
anyhow, that's off topic, fact is this, security will only get tighter and rightly so, as much a that is a pain in the arse for you an I, that is the reality, you may have perfectly legit reasons for full access, but I can promise that most who want it probably will use it for something dodgy, MS and Apple can not afford to have a time bomb on their hands in the shape of android.
I fully agree with you !
Just for the protocol: I liked WM very much and I never considered it as buggy and slow, but ok that's another topic.
The reason why Iam using android at the moment is quite simple. There was no satisfying hardware available for any other system. Iphones are useless, for WM almost nothing was there that could be used as a smartphone and WP was likely to be replaced by something else. I was waiting for years that some manufacturer releases a smartphone that has a 2.3" display like a normal mobile. I hate those laptops people try to use like phones with 4" display and what ever.
Since Iam quit unsatisfyed with the quality of my sony ericsson mobile, Iam looking forward to get a Nokia phone again. Moreover, Iam really no fan of open source software since compatiblity is quite bad and the functionality is mostly not really reliable. Iam a heavy MS Exchange user and I do appreciate nothing more than be completely synchronized with my phone laptop and everything. Only WP8 can provide that... So, Iam dealing with it.

ubuntu phone - yes, no, maybe?

It is possible to get 3 different phones with ubuntu phone now, none of them too expensive.
good.
i wonder what people's experience or informed opinion is?
ubuntu is pushing "convergence", which basically means that one operating system runs on all devices, that i can use my smartphone as a computer...
how far along is it?
now there's loads of blog articles and reviews out there, but most of them focus on comparing ubuntu phone (UP from now on) to other phone OSs - with their fully grown app universe. of course UP comes up short!
but that's not what i'm interested in. OS stability, and the standard browsing, music and video, and of course phone and sms is good enough for me.
but, i want the same freedom i have with my linux desktop install: to Do Things.
(my most important project is still to get a usable connection to the data & media stored on my kitchenserver.)
the day before yesterday i had a chat with someone on #ubuntu-phone - i think it was a dev.
i asked if i can use & upgrade it like any normal ubuntu/debian-based, install apps and utilities and so on.
basically he said, gui apps are difficult because UP uses a different gui model than Xorg, but basically yes, but you loose you guarantee that OTA (over the air) updates will work. but they should, regardless.
yesterday i was browsing the ubuntu phone section on ubuntu forums; of course people only post if something doesn't work - it looks like a normal and healthy distro forum to me.
OTA updates come in almost daily, i gather. very lively development.
there was, however, a lot of familiar discussions about how to get some app or other working; familiar from my 2 android phones: convoluted and fragile solutions, like installing ubuntu desktop in a chroot.
UP even recommends adb (android debug bridge?) as the only way to access the phone from your computer. or the standard mtp connection. so it's the same **** as everywhere.
the other aspect is this:
- ok, android is big, evil google, but there's a few established solutions around to use it without an account, use f-droid instead of play store, well documented security hacks and so on.
- UP certainly isn't the white knight here, but if not google, what do they use, is it really "better" than google and can i opt out easily?
yes, i am seriously considering to buy a UP phone, as soon as i get the feeling that it is an improvement freedom and security wise.
i wonder what people's experience or informed opinion is?
bump
...just a gentle one before the weekend ends.
i'd love to get some answers...

Advice on using Screenless Android Phone for IoT device

I would like to create an IoT device by buying new, cheap android phones, strip them down and remove the screen, rebox into my own physical box, install a custom ROM without any bloatware (and that will boot without a screen!), and install my android app on the device to do stuff.
An example of a purpose for this could be a GPS tracker for a car. The box would be placed in the car, and record GPS and accelerometer readings, posting these readings back to a central server via the cellular network. (This is just a random example, so don't focus too much on the detail of this, but there are thousands of uses for a IoT board with the sensor, CPU, RAM, storage, and connectivity capabilities of a budget android smartphone)
The reason I want to use existing phones is that they are wonderful, mass produced, cheap devices with a variety of sensors I can use.
The reason I want to use Android is because it is because of the customization ability, and the mature development ecosystem.
To me, it seems an obvious thing to do, but I don't seem to be getting much joy trying to search for examples of this sort of thing (either here, or on the internet in general).
So some questions:
1. General thoughts? (Good idea? Am I missing some fundamental problem?)
2. What are the challenges of running Android without a screen connected?
3. Are there any custom ROMs you know of that specialize in this sort of thing?
(I've seen Google Brilo, but it still seems a bit early yet, and I really like the idea of just using the standard Android SDK to develop the app - and the abundance of help and information that comes with it)
Thanks!

How did android reach this point?

As advanced android users, we quickly became obsessed with rooting, unlocking, and controlling our phone. On the other side of the poker table, we have device manufacturers and carriers trying to lock the ecosystem down. It's curious to me how this came to be.
Looking at personal computers: I wanted to install linux on my personal computer because I am a developer by trade, so I installed linux. I took a USB, loaded the linux ISO, and followed the installer (actually I didn't, arch btw). I did not need to get unlock codes from my device manufacturer or my internet company, I just did it and no one complained (aside from windows who was glitching out as I tried to reboot)
This computer ecosystem feels healthy, it's my computer, and I can use it as I wish. I'm curious how and why android got to this point where 90% of manufacturers:
1. Don't allow unlocking
2. Make you jump through hoops to get an unlock code
3. Have hardware root checks
Of course, before we even start talking about verizon (they forgot to lock my pixel )
Is the fact that mobile devices are harder to unlock and modify them computers a flaw in android? Is there some actual reason life is like this?
That's even before we start talking about update cycles. I used my old computer for 10 years, going from god knows what to windows 10 before finally deciding that I just could not. My device manufacturer did not control the updates I got, they just came. Why is it the case that updates come from the manufacture, not directly from modifications to the android codebase? Shouldn't the manufacture just add "drivers" to the device to handle the peripherals?
I presume in some way google is complient with this, because android is based on linux, and linux has no such problems.
Many times, consumers that bootloader unlock their devices have no clue that they will lose features such as banking and Widevine D1; these users are oblivious as to what rooting truly does to their device and instinctively contact their OEM's support to get a device replacement as many times relocking the bootloader is impossible.
Verizon's thought process is somewhat similar, but there is likely a darker undertone to their practices: preventing bootloader unlocks and processes of the sort could aid them when blacklisting their devices, as there is no way to circumvent something tagged to a permanent IMEI kept by the same bootloader and firmware. There is a reason why T - Mobile requires you to have your device completely paid off before you can make any modifications to the system firmware.
Compared to laptops and computers, it is, generally, a one - time purchase and not an investment; carriers depend on their consumers to keep paying their devices off time and time again to make money.
Drivers are essentially non - existent on Android; the only thing that comes somewhat close is the kernel and any OEM modifications to the firmware.
Xryphon said:
Many times, consumers that bootloader unlock their devices have no clue that they will lose features such as banking and Widevine D1; these users are oblivious as to what rooting truly does to their device and instinctively contact their OEM's support to get a device replacement as many times relocking the bootloader is impossible.
Verizon's thought process is somewhat similar, but there is likely a darker undertone to their practices: preventing bootloader unlocks and processes of the sort could aid them when blacklisting their devices, as there is no way to circumvent something tagged to a permanent IMEI kept by the same bootloader and firmware. There is a reason why T - Mobile requires you to have your device completely paid off before you can make any modifications to the system firmware.
Compared to laptops and computers, it is, generally, a one - time purchase and not an investment; carriers depend on their consumers to keep paying their devices off time and time again to make money.
Drivers are essentially non - existent on Android; the only thing that comes somewhat close is the kernel and any OEM modifications to the firmware.
Click to expand...
Click to collapse
This explains why carriers do do this, and it makes sense, but how can they do this? The fact that should someone in the black box want to, loose control over my device no matter what I do is frankly scary. Could a laptop manufacturer do the same thing if they wanted to? (Ignoring the fact they could not because of the outrage). I had always thought somehow android as an operating system was connected to this, somehow complient, but perhaps it is really just a choice by the manufactures that android has nothing to do with. (Google could enforce this via GMS I think, but I don't expect them to)
Scaledish said:
This explains why carriers do do this, and it makes sense, but how can they do this? The fact that should someone in the black box want to, loose control over my device no matter what I do is frankly scary. Could a laptop manufacturer do the same thing if they wanted to? (Ignoring the fact they could not because of the outrage). I had always thought somehow android as an operating system was connected to this, somehow complient, but perhaps it is really just a choice by the manufactures that android has nothing to do with. (Google could enforce this via GMS I think, but I don't expect them to)
Click to expand...
Click to collapse
Chromebooks are a prime example of locking down the bootloader. So is the same with macOS laptops and related devices - albeit Apple lets you boot into other operating systems, the process to do so requires jumping through quite a bunch of loopholes due to Apple's Secure Boot, file system, etc.
Just to play devil's advocate for a moment (because in reality, I, too, prefer to own my equipment).....
Security can be a lot more critical on mobile devices than stationary devices like desktop computers. Even in *some* respects, compared to rackmount servers. This is because it can be pretty simple to grab someone's phone and do what you want with it. Having physical access to a piece of equipment is 99.999% of the task of breaking into it. Its relatively far fetched for someone to break into your home or a high security datacenter in order to gain physical access to your equipment, so the need to have it protected against the kinds of intrusions that become possible through physical access is much lower than it is on a phone, which you just might accidentally leave on the counter at a coffee shop.
And that is about the only part of the move towards lockdowns that I actually understand. The rest of it is either ill-conceived "security" or coercion to separate you from your money.

Categories

Resources