Hello,
First off, apologies if I have posted this in the incorrect forum.
The company I work for is looking to update one of it's product lines and has been toying with the idea of using Android as a development platform. Up until now the philosophy has always been to develop simple, bespoke embedded software that provides only the functionality that is needed at the time. The device itself will be a medical device, and as such will have no telephony requirements (and associated things like contacts, calander and the large majority of the pre-installed Android apps).
I have read, and understand it is possible to re-compile Android from source and remove all of these non-required functionality. My question is really if that is worth doing? i.e. stripping out all un-needed applications that get build into a stock ROM. Or would it be a more efficient to use some form of OTS embedded Linux platform?
Something in Android 4.0 that does seem to be useful is the support for Bluetooth HDP.
Kind Regards,
Simon
Well there are other devices that aren't phones that use Android. Take the motoactv for example. It's a fitness watch that runs a stripped version of Android, but it's still Android and applications can still be programmed and installed to it.
May be a dumd question, but I'm asking anyway. Why is Android so hardware specific?. or better yet, why can't you install any android system on any phone?
example: you can install windows or linux on any system, you don't have to have a certain set of chips. Is it a propitiatory type thing with these phone makers. is the whole android system so small, that the coding can't be added to make it installable on any phone.
I'm not a coder, or prgrammer, I do understand it enough to read what it is doing, but cannot write anything. Can someone shed some light on this
Thanks in advance
You've got this completely bass ackwards. Android is decidedly not hardware specific. Phones, tablets, computers, car stereos, home heating/AC, watches, TVs, etc. Android is open source, which means anybody can develop it to work on just about any platform they wish. I mean, you can get refrigerators and microwaves that run Android for Pete's sake.
If you're complaining that you can't get Android on an iPhone or a Nokia Lumia, then you're barking up the wrong tree.
To add some more "devices" to the list above on which android can be installed - cars! I'm working in that industry now
And the answer above is right - if your device is totally closed for others, then you will not be able to install anything on it, maybe, without really breaking into it. Android can be put mostly on any hardware - if the hardware manufacturer wants it. The short description is - Android is implemented on top of HALs (Hardware Abstraction Layer) which are then implemented by manufacturers specific to their devices and then Android works "out of the box".
AOTP | Android Open TV Project
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ben a few weeks since i received my ADT-1 and currently building a device tree with the help of @Unjustified Dev
A few days ago an idea came to mind, why not create a Unified AndroidTV and ASOP (CM, PA, . . . ) Rom
As you may realize this may be a big task and also AndroidTV isn't exactly OpenSource, parts and bits (very little)
I need a Team (Developers / Designers / Skill individuals), Would you like to join this journey? Inbox me or msg on G+!
GitHub Repo: https://github.com/AOTP (not much atm)
Project / Rom Name: AOTP | Android Open TV Project
Others names i thought of were: Android TV Open Source Project (ATOSP), Android Open Source TV Project(AOSTP),
Android Open Source Projec For Television (AOSPTV)
Goal: Unified AndroidTV and AOSP (CM, PA ..) / Something Different / Unique
This Project / Rom isnt only targeted for only to the ADT-1 / Nexus Player but is also for other devices that fall into the
GoogleTV, Android Set Top box categories.
Improve the AndroidTV experience
Beauty / Design enhancement
Teaks / Features
Enhancement
Deliver more
Ideas:
Reboot Menu
Hover by ParanoidAndroid
Broswer & Eleven App (New music aop) By CyanogenMod
Slim Recents by Slimroms (Like the looks, could be use as a SideBar)
Unified Leanback and Lollipop launcher (Leanback launcher is closed source)
* List of Features / Ideas will updated as they are shared (you) and will be taken in consideration.
PS: Im new to ROM developing and learning as a go.
Also the page will regularly updated with more info, ideas ect.
mine!
This sounds awesome!
mkaymuzik said:
As you may realize this may be a big task and also android tv isn't exactly open source, part and bits (very little).
Click to expand...
Click to collapse
Doesn't stop the Sense and Touchwiz custom ROMs from being great!
Sent from my HTC6525LVW using Tapatalk
lorddunlow said:
This sounds awesome!
Doesn't stop the Sense and Touchwiz custom ROMs from being great!
Click to expand...
Click to collapse
Thanks mate. Have alot to do and learn.
True lol all tho i dont exacly like touchwiz.
One thing we need is enabled MTP support.
YoshiFan501 said:
One thing we need is enabled MTP support.
Click to expand...
Click to collapse
this might just be just a kernel thing. i cant know for sure. that why i need skill individuals / devs to help me out with this project.
i have the idea and some skill but not all. this is my first actual big project and want to make it reality.
mkaymuzik said:
this might just be just a kernel thing. i cant know for sure. that why i need skill individuals / devs to help me out with this project.
i have the idea and some skill but not all. this is my first actual big project and want to make it reality.
Click to expand...
Click to collapse
it could be kernel as lollirock enabled it successfully
YoshiFan501 said:
it could be kernel as lollirock enabled it successfully
Click to expand...
Click to collapse
Good to know
I own two ADT-1's and look forward to this project, although I am unable to provide any coding skills I can and have provided testing the ROM during its development.
The MTP issue is a kernel issue and I've worked with kernel developers working on other platforms in the past.
eyetek said:
I own two ADT-1's and look forward to this project, although I am unable to provide any coding skills I can and have provided testing the ROM during its development.
The MTP issue is a kernel issue and I've worked with kernel developers working on other platforms in the past.
Click to expand...
Click to collapse
Thx mate for the interested and i will see what i can do for mtp thing. Have to learn about kernels a little bit more
Short version of my opinion of what the Nexus Player should be, feel free to agree, disagree, or use any part in your creation:
- Full version of Android 5.
- Easily able to switch between a typical Android environment and a Leanback (or similar) environment.
- Voice (via Nexus remote) is going to be important to most users.
- Remapped remote = Home button changed to a shift button, allows addition of volume, channel, and other (launcher swap maybe?) shortcuts.
- xposed or similar tweaks baked in (status bar, themes, etc)
- ScreenCast working
- Web cam and external mic support
- StickMount and FolderMount baked in, or immediate suggestion to download and install (via wizard?)
- Bluetooth headphone functionality (though I don't think this has been solved yet)
I'm sure I'll think of more. Very much looking forward to whatever you can brew up!
Here is what I'm thinking for the remote:
Can the remote be remapped? I'm thinking the home button could act like a shift button, then you could map volume, channel, etc - to combinations of buttons. This would effectively double the amount of functions on the remote, and might make it actually useful! Maybe even add long presses and you'd triple the functions...
Voice = search/home
Up = up/volume up
Down = down/volume down
Left = left/channel back
Right = right/channel forward
Select = select/home
Back = back/force close
Play = play/recent apps
midnightzak said:
Short version of my opinion of what the Nexus Player should be, feel free to agree, disagree, or use any part in your creation:
- Full version of Android 5.
- Easily able to switch between a typical Android environment and a Leanback (or similar) environment.
- Voice (via Nexus remote) is going to be important to most users.
- Remapped remote = Home button changed to a shift button, allows addition of volume, channel, and other (launcher swap maybe?) shortcuts.
- xposed or similar tweaks baked in (status bar, themes, etc)
- ScreenCast working
- Web cam and external mic support
- StickMount and FolderMount baked in, or immediate suggestion to download and install (via wizard?)
- Bluetooth headphone functionality (though I don't think this has been solved yet)
I'm sure I'll think of more. Very much looking forward to whatever you can brew up!
Click to expand...
Click to collapse
There is a rom for the nexus player that is a full android lollipop in development tread called Lollirock just in case you haven't checked it yet.
Like you ideas and most of them were already in mind a fully android lollipop will have to be done like android tv isnt open source. Also creating new launcher is in mind
mkaymuzik said:
There is a rom for the nexus player that is a full android lollipop in development tread called Lollirock just in case you haven't checked it yet.
Like you ideas and most of them were already in mind a fully android lollipop will have to be done like android tv isnt open source. Also creating new launcher is in mind
Click to expand...
Click to collapse
Yep, I've been running LolliRock for a few weeks now and it is great! Zulu just got the screen cast working too so next release will be up soon and better than before.
The reason I posted is that it sounds like we're dreaming of the same thing for the NP, where it is an all around android TV solution and not the same exact thing we've seen on every other device out there.
midnightzak said:
Yep, I've been running LolliRock for a few weeks now and it is great! Zulu just got the screen cast working too so next release will be up soon and better than before.
The reason I posted is that it sounds like we're dreaming of the same thing for the NP, where it is an all around android TV solution and not the same exact thing we've seen on every other device out there.
Click to expand...
Click to collapse
Oh nice and true facts. Im thinking what to do for this rom. I like what zulu did for his rom all tho its speficly for the nexus player. I want this rom to be more as alternative to the close source android tv target to android tv, google tv and and android game console devices.
Yes Please!
mknrls said:
I want this rom to be more as alternative to the close source android tv target to android tv, google tv and and android game console devices.
Click to expand...
Click to collapse
Sorry to necro such an old thread. Is this endeavor being worked on or discussed somewhere else or did interest fade? I would love to see this happen as a lot of perfectly passable GoogleTV devices have been somewhat orphaned when it comes to app support since the (seemingly promised) 4.1+ update never materialized for second gen GTV set top boxes and Google dropped the GoogleTV SDK.
Anyway, a couple of suggestions in case anyone is still interested in doing this:
If Exploiteers (Formerly GTV Hackers) is correct then almost all of the second gen GoogleTV devices are running almost exactly the same basic hardware: "Marvell Armada 1500(88DE3100) 1.2 GHz dual-core processor, with a 750 MHz GPU". It would seem that if you can get one of them running Android L then the rest should follow more easily (but I've never built a custom ROM so I could be way off).
It seems the ASUS Cube would be a good candidate from available Google TV devices as it already supports some AndroidTV features such as voice search through a microphone built into the remote. It has two USB ports, where most of the others only have one. It also has a built in IR receiver (only used by the remote to power the STB on and off, oddly). It would be neat to see if someone could port the Harmony IR remote support from the NVIDIA ShieldTV eventually.
Finally, an extremely cheap micro console to play around with is the PlayJam GameStick. It currently sells for just under $17 US, with included gamepad, at GameStop. It runs an Amlogic 8726-MX system on a chip including ARM Cortex A9 CPU and Mali-400 MP graphics. People have been working on some derivative Jellybean ROMs at GameStickers.net. It would be neat to have AndroidTV installed on something so tiny and cheap, but I believe one of the ROM developers said the SOC couldn't support anything past JellyBean for some reason.
I hope to see an open AndroidTV make progress!
Xenrid said:
Sorry to necro such an old thread. Is this endeavor being worked on or discussed somewhere else or did interest fade? I would love to see this happen as a lot of perfectly passable GoogleTV devices have been somewhat orphaned when it comes to app support since the (seemingly promised) 4.1+ update never materialized for second gen GTV set top boxes and Google dropped the GoogleTV SDK.
Anyway, a couple of suggestions in case anyone is still interested in doing this:
If Exploiteers (Formerly GTV Hackers) is correct then almost all of the second gen GoogleTV devices are running almost exactly the same basic hardware: "Marvell Armada 1500(88DE3100) 1.2 GHz dual-core processor, with a 750 MHz GPU". It would seem that if you can get one of them running Android L then the rest should follow more easily (but I've never built a custom ROM so I could be way off).
It seems the ASUS Cube would be a good candidate from available Google TV devices as it already supports some AndroidTV features such as voice search through a microphone built into the remote. It has two USB ports, where most of the others only have one. It also has a built in IR receiver (only used by the remote to power the STB on and off, oddly). It would be neat to see if someone could port the Harmony IR remote support from the NVIDIA ShieldTV eventually.
Finally, an extremely cheap micro console to play around with is the PlayJam GameStick. It currently sells for just under $17 US, with included gamepad, at GameStop. It runs an Amlogic 8726-MX system on a chip including ARM Cortex A9 CPU and Mali-400 MP graphics. People have been working on some derivative Jellybean ROMs at GameStickers.net. It would be neat to have AndroidTV installed on something so tiny and cheap, but I believe one of the ROM developers said the SOC couldn't support anything past JellyBean for some reason.
I hope to see an open AndroidTV make progress!
Click to expand...
Click to collapse
Are you a developer? We are working on CM Android TV. Its very functional. Supports Nexus Player & (almost) ADT1.
Sent from my Nexus 6 using Tapatalk
npjohnson said:
Are you a developer? We are working on CM Android TV. Its very functional. Supports Nexus Player & (almost) ADT1.
Click to expand...
Click to collapse
That's very exciting sounding.
Hello Folks,
I seen a rumor that Android may about to support iOS on its wear platform. Think Moto360 with iPhone.. See This
Since Android shipped about 720,000 device in 2014, compared to 4.6 million wearable devices in 2014 by estimates. See Here
I have been working on developing an application for the Android Wear platform that will allow iOS communication, but there is a well known bug in Android that is preventing connecting to an iOS device. This is despite Android Wear supporting Bluetooth LE GATT profile, and will connect with most other bluetooth devices over Bluetooth LE using the GATT profile. You would think it seems like an iOS issue. When you dive into the communication handshake between the devices when attempting a connection between Android Wear and iOS, you get an error.
This has been reported to Android and since then, not fixes. I understand they have bigger fish to fry than allowing their watches to support iOS, but since their devices are not selling well this may push them into fixing the bug.
See This ... It explains how the bug in android is failing connecting to iOS devices due to their bug..
I did some deep diving and reviewed the code for the BluetoothDevice.java file in the Android Development Studio and found that there is the option to select either Normal Bluetooth or LE via a transport parameter with connecting... BUT... When android implemented their specific code, they OMITTED the transport parameter and it SHOULD connect via LE, but doesn't.
Here is my comment on the above thread (Issue 58896):
Reviewing the android code for BluetoothDevice.java I found that connectGatt() function has a hidden int TRANSPORT variable that will allow you to use AUTO or specific LE or BR/EDR only.
For some reason, this is available in the BluetoothDevice.java file in android studio, but not listed in the android code reference. When you attempt to use this, it gives you an error. If someone can explain how we can fix the compiler on android studio to compile our code using the TRANSPORT_LE option instead of TANSPORT_AUTO which I assume is being used.
I see someone with Broadcom has requested that the transport parameter be added in May 2014 on the android GIT page (https://android.googlesource.com/platform/frameworks/base/+/b88fa82^!/) which is almost 7 months ago. If this is such a seemingly prominent problem and so many fixes since then and this hasn't been fixed??
So this has been reported by Broadcom in May 2014..... and no fix as of yet???
I am curious how MohammadAG bypassed this snafu. Any thoughts?
Here is his proof..
hhttps://www.youtube.com/watch?v=DIIYmVSc9Yw
Hello!
I too am working on such a project and during my studies have successfully connected my android to my iPhone with one extra step: since android can only act as the central and connect to a peripheral, the iPhone has to be put into peripheral mode, for which I used LightBlue (look in the app store). After they connected I was able to discover the GATT service, but I'm new to android and this is a huge project so I'm kinda lost after that. Would you mind sharing your code with me so I can collaborate with you on this? I'd love to release something like this to the XDA community, and if you're closer than I, I'd love to help!
I hope this answer helps you, but I may be completely misunderstanding the question.
Thanks!
Zachal
I'm wondering if there is anyone out there that might be interested in building a "stock" ROM for the Nexus 5 that uses the BlueZ bluetooth stack instead of the default Bluedroid stack. It should be very simple, as the BlueZ for Android project has done most of the work, including building the kernel. It looks to be as simple as downloading the various source files and compiling. I was attempting to do it myself but I couldn't ever get Linux installed on my PC. Well, I got it installed but could never boot into it. I feel bad asking someone else to build it, but like I said, my PC setup seems to be Linux-averse and my understanding is that this is a simple build.
The impetus for this is that I recently upgraded my car stereo to a bluetooth-enabled unit but I can't transmit the track metadata. Even though the head unit supports AVRCP 1.3, and the Nexus 5 should also support AVRCP 1.3. I'm unlikely to get a firmware update from the stereo manufacturer. All my reading on the issue suggests that bad things happened for Android bluetooth when Google switched from the BlueZ to Bluedroid stack. I'm hoping that incorporating BlueZ in my phone might just increase compatibility between my phone and head unit.
The relevant links for making the build are here:
http://git.kernel.org/cgit/bluetooth/bluez.git/tree/android/README
https://code.google.com/p/aosp-bluez/
What is BlueZ?