Hi all,
I'm working on a personal project and am wondering what are some possible methods I can use to communicate with an IR sensor over UART. My sensor has it's own chip and requires some configuration and I have it working in an Ubuntu environment perfectly fine through a user space application.
Let us assume I successfully modify the hardware to plug my sensor into my Android device. I'm not sure what's next. I know getting the information from the sensor and into an app will be much easier than getting it to control the entire Android UI, so I will probably look into that first.
I took a look into inputattach but am not certain if that can work with my sensor and couldn't find all that much documentation on inputattach. I thought maybe I could do something with the HAL but once again, I found very little documentation on the Android HAL and couldn't learn very much.
Does anyone have a good place to start or just any suggestions? I'm pretty lost here.
Thanks!
Bumping for answers. Thanks!
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.
I'm hoping someone may let me know if it's possible to write a Driver to access the Android Cameras' directly rather than the OEM's or the Camera API?
I'm looking to have an app that can access both Front and Back cameras at the same time for devices that have dual video processors and looking to hire a developer to do "this" if it's possible.
I imagine it would most likely be C++ at the Linux Kernal or HAL level?
I'm not sure if there's anything at that level that would prevent an app from using it's own driver either?
Android 9 now allows for Dual/Multi Camera support but at that higher level, the Camera2 API only works for some devices. Have tried on Galaxy S4, S6 and S9 all running Android 9 and only the S4 worked.
Any information would help me to see if it's worth pursuing and greatly appreciated.
Just wanted to renew this question. Hoping someone can let me know if it's possible to do this?