Is there a build of MIUI that keeps the features?
Like,
Samsung Codecs (Divx, Xvid MKV) + Samsung video player
Samsung Browser that supports flash, Camera app that lets me use my external storage
I Really do like the MIUI Rom but they have removed everything I love about the Galaxy S over other Android phones
Misticdw said:
Is there a build of MIUI that keeps the features?
Like,
Samsung Codecs (Divx, Xvid MKV) + Samsung video player
Samsung Browser that supports flash, Camera app that lets me use my external storage
I Really do like the MIUI Rom but they have removed everything I love about the Galaxy S over other Android phones
Click to expand...
Click to collapse
Miui didn't remove anything, they just didnt work it out yet Miui is bulid on cm base, and because samsung has a closed source code it isnt that easy to implement those things that you are missing.
As Player i use QQPlayer which is able to play all file formats. (flv, avi, mp4....)
And the location for the pictures? Come on.
Copy your pictures from time to time on your external SD and the problem is gone...
As browser you have to use Dolphin Mini which supports Flash and all other things like gestures, bookmark sync, fullscreen and a very good speed...
MiUi is great, smooth and beautifull.
Hey community
someone recently asked me per email how i do ROM Development.
i prefer to use Android Studio, but it doesnt fully support all, as some internal and hidden api's are just not visible.
This video shows you, how to expose these features and make use of them while coding
for example, if you implement new Methods and Constants etc, android studio wont pick them up and display them by default.
with doing this little trick, it does.
i think its really usefull, but decide yourself
oh, before i forget, sorry for the bad video, im just bad at recording
----------------------------
Video Recorded on Linux, Elementary OS using Kazam
Used Software, Scripts, etc:
Android Studio
Dex2Jar
----------------------------
Link: http://www.youtube.com/watch?v=C9vXkhZiEyc
I am setting up to do an embedded project.
For this I need an android development board which supports displays about 3 to 4 inch ones and a camera. I considered a the raspberry pi. It runs the raspbian os. I found that it can be flashed with an android 4.0.3 ICS os. But I need to kow for certain that i can interface a small display and a camera for the raspberry pi running on the ics os.
I found these 2 products for the pi website
Display:
https://www.crazypi.com/raspberry-pi-products/Raspberry-Pi-Accessories/32-TOUCH-DISPLAY-RASPBERRY-PI
Camera:
https://www.crazypi.com/raspberry-pi-products/Raspberry-Pi-Accessories/RASPBERRY-PI-CAMERA
But i think they support only the raspbian os I want to know if it can be used for android os and if not what alternative can i hope for?
I'm not exactly sure but to make the screen work, especially with the Android OS, you'll probably need some specific drivers. The product description for the screen indicates that it is compatible with the Raspbian OS. You may need to program your own drivers to make the touch screen work on Android.
The display you mention has only resititive touch. Have anyone found one with capacitive touch?
I have a Android BOX TV with classic Android 6 version (no Android TV).
Is possible add Chromecast Build-in function like on Android TV?
I would like to cast my video to Android BOX. I don't want use app like AllCast because I want use cast button from youtube, spotify, ... and select my Android BOX like a Chromecast device. This is possible in Android TV.
Is possible add this feature in a classic Android version (with root)?
Hi, I installed the built in version from apk mirror to my TV box nexsmart D32.
Now , cast appears in config , but my mobile doesn't see it.
I'm near haha but my phone don't connect
[Tutorial] How to get the ultimate android TV experience on R-box Pro. Google it
Hello,
I would like to announce my newest project called OpenAuto.
Donate
What is OpenAuto?
OpenAuto is an open source AndroidAuto(tm) headunit emulator application based on aasdk library and Qt libraries. Main goal is to run AndroidAuto(tm) on the RaspberryPI 3 board computer smoothly.
Demo video: https://www.youtube.com/watch?v=k9tKRqIkQs8
Status
Project is currently under beta testing.
Links and open source code
https://github.com/f1xpl/openauto
Features
480p, 720p and 1080p with 30 or 60 FPS
RaspberryPI 3 hardware acceleration support to decode video stream (video stream up to [email protected])
Audio playback from all audio channels (Media, System and Speech)
Audio input for voice commands
Touchscreen and buttons input
Bluetooth
Automatic launch after device hotplug
User-friendly settings
Supported platforms
Linux
RaspberryPI 3
Windows
Before you start using OpenAuto please read Readme and wiki page. Also check OpenAuto Pro.
Whoa, nice work. Would this also have a audio EQ/Crossover interface for the Pi?
Can you post a Windows binary build please? Thanks
Daved+ said:
Can you post a Windows binary build please? Thanks
Click to expand...
Click to collapse
Is this at least possible OP? Noobs here, Thanks in advance.
Will this work as standalone or does it need the app?
"Do not use while driving" Well where is the fun in that?
look like someone may able create Open AA instead and resolve blocking issue by google..i guess
Time to give my ride a sweet upgrade
Will raspberry survive high or low temperatures?
I'm trying to compile it, but I got a bit rusty in building under linux.
Code:
[ 6%] Building CXX object CMakeFiles/autoapp.dir/src/autoapp/Main.cpp.o
In file included repos/android-auto/openauto/src/autoapp/Main.cpp:19:0:
repos/android-auto/openauto/include/f1x/openauto/autoapp/USB/USBMain.hpp:22:40: fatal error: f1x/aasdk/USB/USBWrapper.hpp: No such file or directory
#include <f1x/aasdk/USB/USBWrapper.hpp>
Did I forget something when configuring with cmake?
f1x said:
Hello,
I would like to announce my newest project called OpenAuto.
Donate
What is OpenAuto?
OpenAuto is an open source AndroidAuto(tm) headunit emulator application based on aasdk library and Qt libraries. Main goal is to run AndroidAuto(tm) on the RaspberryPI 3 board computer smoothly.
Demo video: https://www.youtube.com/watch?v=k9tKRqIkQs8
Status
Project is currently under beta testing.
Links and open source code
https://github.com/f1xpl/openauto
Features
480p, 720p and 1080p with 30 or 60 FPS
RaspberryPI 3 hardware acceleration support to decode video stream (video stream up to [email protected])
Audio playback from all audio channels (Media, System and Speech)
Audio input for voice commands
Touchscreen and buttons input
Bluetooth
Automatic launch after device hotplug
User-friendly settings
Supported platforms
Linux
RaspberryPI 3
Windows
Before you start using OpenAuto please read Readme and wiki page.
Click to expand...
Click to collapse
Hi! First of all, thank you for bring us this post! Amazing I've the same question as another guy here, Could you post the Windows binaries or link to the step by step to get it running under windows?
Thanks a lot in advance!
Seriously impressive, great work.
Works perfectly on my Pixel 2/PI3.
Do you think it would be possible to get Android Auto Wireless functionality at a later point? Or does this require some specific wireless/bluetooth protocol that Google hasn't released just yet?
bluethoot
What can you do with the bluethoot feature ?
xbenjiiman said:
Seriously impressive, great work.
Works perfectly on my Pixel 2/PI3.
Click to expand...
Click to collapse
Thanks for your feedback. Great to see it working .
Zaf9670 said:
Do you think it would be possible to get Android Auto Wireless functionality at a later point? Or does this require some specific wireless/bluetooth protocol that Google hasn't released just yet?
Click to expand...
Click to collapse
I think it will be possible but needs some time and effort to implement it. OpenAuto is a hobbyist project and I cannot promise the exact deadline but this feature is on the TODO list.
brett1996 said:
What can you do with the bluethoot feature ?
Click to expand...
Click to collapse
What do you mean?
f1x said:
I think it will be possible but needs some time and effort to implement it. OpenAuto is a hobbyist project and I cannot promise the exact deadline but this feature is on the TODO list.
Click to expand...
Click to collapse
I wasn't sure how much of Android Auto is "open" to use. I haven't invested too much time looking into these forks like Auto and Wear but I know they're not quite as public as standard Android. At least that is the take I have gotten over the past few years.
Hopefully it's something that won't require some sort of specific hardware. Best of luck! I hope to test this out on my Pi 3 in a few weeks myself. I'll be sure to keep tabs on the project!
I promise I'm not one of those XDA ETA/update zombies.
Woohoo!! Thank you for this effort!
I'm curious which hardware, aside from the Pi, has been used successfully so far? Is that the Raspberry Pi Foundation touch display? Any HATs?
Thanks again!
-Chad
MasterCLC said:
Woohoo!! Thank you for this effort!
I'm curious which hardware, aside from the Pi, has been used successfully so far? Is that the Raspberry Pi Foundation touch display? Any HATs?
Thanks again!
-Chad
Click to expand...
Click to collapse
Only Raspberry PI 3 has been tested so far in case of embedded platforms. Code itself is portable for any Linux-based or Windows platforms. If hardware acceleration of video decoding is supported by underlying backend used in Qt multimedia library (GStreamer for Linux and DirectShow for Windows) then OpenAuto will run smoothly without additional effort. If hardware acceleration is not supported by underlying backends then it must be implemented in OpenAuto (like in case of Raspberry PI 3).
I apologize, I meant in addition to the Pi, not alternative platforms. Things like which screen is it that you've used, any HATs on your Pi, etc. ?
Thank you!
MasterCLC said:
I apologize, I meant in addition to the Pi, not alternative platforms. Things like which screen is it that you've used, any HATs on your Pi, etc. ?
Thank you!
Click to expand...
Click to collapse
Screen is the official one from PI Foundation (7''). Basically any screen should be suitable to run OpenAuto (as long as it is supported by the OS that hosts OpenAuto). The same for other hardware.
Dude! You're my hero, I've been playing around with so many ways to get this working, yours seems to be the perfect solution, I'll take it for a test drive tomorrow