Android without a screen? I think Embedded Linux is a lot more suited to this case. Android SDK for the app without a screen will be quite a fun feat (not really what Android was meant for).
BTW on side note: If you build a dedicated device for your case you will get it a lot cheaper even in smaller quantities, because board will be smaller, less obsolete stuff and CPU does not really need to be that fast, so you save at least 10 USD there. On Thu, Nov 3, 2016 at 3:30 PM, Bruce Rankine <therealviperpi...@gmail.com> wrote: > 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! > > -- > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > > --- > You received this message because you are subscribed to the Google Groups > "android-porting" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-porting+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
