[Android Q&A, Help & Troubleshooting] Nefariis:
A team and I have been working on a medical product for the last year and we are figuring out the best way to deploy the project. We all have app building experience but none of us have ever built a ROM before, so we wanted to consult a forum of experienced Devs (you guys) to see if what we have in mind is actually feasible before we invest too much time/energy/resources on this particular path.

In short, the device is a wearable EKG machine that detects seizures, so far we have been able to successfully predict seizures in clinical trials and allow users 1-2 minutes of advanced warning. The EKG part and the algorithm are already working. What we are looking for now are phone calling, messaging, and bluetooth capabilities - which has us (at least me), looking to android.

First and foremost, we do believe that this system will save lives as early as the end of this next year, so any and all help will be greatly appreciated. We are finally coming down the homestretch and we just need a little help/guidance for getting us past the finish. So thank you again.

We want to create something that high risk seizure patients can wear on their arm . This will be an EKG machine and an android device rolled into one, the total size will be about the size of a credit card and about a half inch thick. My plan is to disassemble and strip an android device leaving only the board, battery, radio antenna, and Bluetooth antenna (no screen) and then combine that with the EKG machine.

The initial device that we choose is the LG-MS659 as it is small, lightweight, 2500 mah battery, LTE capable, and running Android Version 4.1.2 (more on that in a second)

So here are the questions we need answered.

1. Will Android work without the use of a screen from start to finish? We literally cant have dialogs anywhere that can prevent or pause the use of the system. We cant have fresh install screen prompts or the visual use of a custom recovery. So is it possible to load a CR, install the ROM, and use the ROM without any user interaction what so ever?

2. The reason we chose 4.1.2 is because once a device is plugged into a computer, there isnt an "allow this computer" dialog. Are there ways around this on Android, or is it just built into Android and we are correct in trying to use 4.1.2 instead? (4.1.2 was the last Android version before the hidden menu and the security prompt was introduced)

3. We would like to delete and uninstall all services and applications not relating to GPS, BT, and Network (Calling/Messaging) including the display drivers, and just run everything from the ADB shell prompt. How feasible is this?

4. Ideally we would like to make the system twice as battery efficient as the S5/S6 Ultra Power Saving Mode, giving us at least 14-21 days of battery time (Samsung claims 12-15). How feasible is this?

5. Where are we going to run into the most trouble?

6. What about this might not be viable?

7. If you were to building this, what would you do? We are primarily looking at Android as they are LTE/Bluetooth/Messaging/Call ready out of the box. They also come with a Li-ion battery and we can easily build apps that can utilize the aforementioned technology without starting from scratch or building our own libraries (no wheel inventing required).

Again, we really appreciate any help we can get on this matter - we are no experts, but we are hoping a few of you are.

- Z