Hi all,
i still very much like the Nextbit Robin and i found the concept behind https://maruos.com/ to be very cool and i would like to see this running on the robin.
As maru is now based on LineageOS and Lineage 15.1 was a very stable experience on the device i just wanted to suggest porting maru to robin.
(Sadly i myself lack the skills to do this)
There is a very active google group
https://groups.google.com/forum/#!forum/maru-os
and a development section
https://groups.google.com/forum/#!forum/maru-os-dev
that already contains some hints/patches on how to take this to other devices from existing lineage device trees.
I tought i would post this here so maybe someone with the required knowledge to do a maru build might take an interest in doing so :highfive:
Best regards
I believe this utilizes USB-C to HDMI which isn't supported on ether because of hardware limitations. There may be Chromecast support for it's desktop environment feature but I'll have to check. If so, I see a possible use case.
Hey AnierinB,
i had the same concern but maru supports chromecast & miracast for the desktop environment.
(it should be working already as its shown in the videos on their website)
Best regards
the_bastl said:
Hey AnierinB,
i had the same concern but maru supports chromecast & miracast for the desktop environment.
(it should be working already as its shown in the videos on their website)
Best regards
Click to expand...
Click to collapse
Once my replacement motherboard for my server is here I'll build it and test it out. I'll reply to this thread to share my progress and findings.
Related
Hello.
Recently I made a remote control solution which can control your Android-based phone on PC. Server runs on Windows-based PC only for now. (Server is based on MFC) Client(Your phone) should able to get root permission.
We verified this solution works on Galaxy S, Galaxy S2, Galaxy Note. But not yet tested on the other devices due to lack of devices.
If you have interests controlling your phone on PC, please check this out and leave us feedback. If you are willing to make this project better, feel free contact to us. Remoteroid will get better than ever, with your supports and contribution.
Project site:
- Since I'm new user to XDA, I can't leave URL for project page.
just google 'remoteroid'! (remoteroid on Google Code)
Brief build instructions (For client):
Checkout both 'ActionbarSherlockLib' and 'android' into your workspace, make sure Android 4.0.3 System image exists on your system and latest ADT has installed.
Once all prerequisites are fulfilled, just press 'Run' button on Eclipse to install Remoteroid on your phone.
Please test on Galaxy Nexus for us. If not working I will request this thread be taken down.
Thank You.
Bro, your post should be in the Android Apps and Games or Android Software Development. There is nothing Galaxy Nexus specific in your product or post.
Hi there,
I am planning to start some project in the NGO I am currently working in, a child aid organization in India. Therefore I bought some Zync Z930 tablet with 1,2Ghz CortexA8-CPU, 512MB DDR3 Ram and a capacitive touchscreen. Currently Android Ice-Cream-Sandwich (4.0) is running on it, but I want to install OLPC OS on it which is a Fedora-based distribution especially developed for the needs of children.
Actually, I don´t know how exactly to unlock the bootloader, root the device and install some other OS on it. Is there a general way or is this specific for every device? What about the driver support for the touchscreen etc.? Will it be the same as with Android? Furthermore, how can I make the device boot from SD-Card or USB?
To my knowledge: I have got some knowledge on GNU/Linux, I´m quite familiar with the terminal etc. and I have programming knowledge (C++), too, but none in Kernel or other low-level programming.
Sorry for not posting links to further information, but as this is my first post, I cannot post them...
If further information is required, please let me know it.
Thanks a lot,
badday
We're working on very similar lines
badday2 said:
Hi there,
I am planning to start some project in the NGO I am currently working in, a child aid organization in India. Therefore I bought some Zync Z930 tablet with 1,2Ghz CortexA8-CPU, 512MB DDR3 Ram and a capacitive touchscreen. Currently Android Ice-Cream-Sandwich (4.0) is running on it, but I want to install OLPC OS on it which is a Fedora-based distribution especially developed for the needs of children.
Actually, I don´t know how exactly to unlock the bootloader, root the device and install some other OS on it. Is there a general way or is this specific for every device? What about the driver support for the touchscreen etc.? Will it be the same as with Android? Furthermore, how can I make the device boot from SD-Card or USB?
To my knowledge: I have got some knowledge on GNU/Linux, I´m quite familiar with the terminal etc. and I have programming knowledge (C++), too, but none in Kernel or other low-level programming.
Sorry for not posting links to further information, but as this is my first post, I cannot post them...
If further information is required, please let me know it.
Thanks a lot,
badday
Click to expand...
Click to collapse
Hello badday,
I'm from Mumbai ...
We're working on getting Sugar on similar devices..
We kind of have made some progress..
The idea is to get the kernel sorted out for the particular device, and the base rootfs over which the system can be installed over.
Want to participate in the effort?
Kindly join the mailing list at gnowledge.org/cgi-bin/mailman/listinfo/swarm
Happy hacking!
jquip said:
Hello badday,
I'm from Mumbai ...
We're working on getting Sugar on similar devices..
We kind of have made some progress..
The idea is to get the kernel sorted out for the particular device, and the base rootfs over which the system can be installed over.
Want to participate in the effort?
Kindly join the mailing list at gnowledge.org/cgi-bin/mailman/listinfo/swarm
Happy hacking!
Click to expand...
Click to collapse
Hi jquip,
yes, I would be interested to join ur project, just need a little introduction and some more information. Do u guys have a git repo with the code on it?
Best wishes from Delhi,
badday
So I finally managed to install Sugar on top of Ubuntu on top of Android. First thing I did was rooting the tablet with adb commands, using "Complete Linux Installer", downloaded Ubuntu core, manually enlarged it to have enough space, installed lxde and sugar 0.90 from the official Ubuntu sources, started the xserver and vnc server and finally vnc-ed on the tablet into the graphical UI and started sugar.
However, currently I am facing the problem that e. g. turtle art will fail to start out of sugar but works fine when started just out of LXDE, so let´s see what the problem will be, stay tuned.
As I faced too many problems with Ubuntu, I changed to Fedora. Now activities can be started and it works like a charm...
Here are some pics: https://www.dropbox.com/sh/hcnpkf4a83dczea/dZCr0Rc4U9
Photos are great.
Those pics really motivate me to want to make this happen on the Yeahpad Pillbox7 I am working on to do the same.
I am curious about your work there in India.
I would like to network with you further and beyond the scope of xda-developers. That we can cooperate together on educational goals for children internationally using computer protocols is fascinating. Consider putting me in your Google+ circles (I am at j dot mp slash paulplus) and on facebook i am fb dot com slash paulgydos. you can reach me directly by email at paul at gydos dot com. also I am on twitter @paulgydos and for the tablet project the twitter is @yeahpad. I am about to mention you over there at @yeahpad. I particularly like Google+ lately as it is currently a more serious platform than facebook which on the other hand has the benefit of so many users.
Thanks again for your posts.
I sent you a friend request on facebook as I am not at Google+ and not frequently on twitter.
Nice to have somebody in the same boat.
joined the mail list
this get
"kernel sorted out for the particular device, and the base rootfs over which the system can be installed over" business
and getting ARM architecture away from proprietary-software like constraints seem like incredibly good goals.
so I joined the mail list and I'm reading through some of the archives.
What other places are people gathering around and working on such ideas?
I want to participate!
paul at gydos.com // twitter dot com slash paulgydos // fb dot com slash paulgydos // and also G+ address is j dot mp slash paulplus
bring me into it!
Hello XDA developers!
A few friends and I have been developing a totally new USB open source gamepad called XOPAD. As part of the open source community, we figured we might ask you what you think, possible improvements and suggestions that may arise, before launching it.
Here's what it looks like:
It has :
Stereo speakers embedded in the controller, one on each side
Dual clickable analog joysticks (not sliders, actual tilting joysticks)
An internal battery with a booster that can charge the phone
Software-programmable SENSE-pin resistance, to be able to switch from On-The-Go to AOA 2.0 modes (beta function as of now)
Upgradable firmware through the micro USB port
Uses HID protocol, therefore there's no need for apps, it's real plug&play. We might need to make an app to easily remap buttons in the future for different games.
Adjustable to fit different phone sizes up to the Samsung Galaxy Note 2.
UPDATE:
We have now launched our project! Show us some support and make XOPAD a reality!
XOPAD - an Open Source USB Gamepad for Android smartphones
Tell us what you think!
PS: You can follow the progress of the project in http://www.facebook.com/xopad, our blog http://xopad2012.wordpress.com or our twitter account https://twitter.com/xopad
UPDATE:
Here is the behind the scene video of the XOPAD:
this is very cool
Thank you enadzzz2010! We'll be uploading more videos as the days goes by.
This looks cool, thanks.
wow looks great..keep up the good work :good:
Thank you for your responses! Looking forwarded to get these in your hands soon! :fingers-crossed:
Looks interesting.
Updated main post with Making Of Video
I've updated the main post with a new Making Of video!
Looks very good. I've been waiting for something like this.
Sent from my HTC One S using xda app-developers app
sound awesome
Thank you guys for your responses. We are just a few days away from launching this on Kickstarter. I'll send out an update once this happens on the main post.
Update
We have launched out project on kickstarter! See first post for update.
Google released some weeks ago Android Auto.
http://www.android.com/auto/
An app on your Lollipop device that can connect to cars head units.
So using your phone with the biger display in your car, with apps specially designed for that.
The problem is that you need a new car or a after market head unit that supports Android Auto.
That sounds really expensive!!
BUT what if we could replace that expensive head unit with a raspberry pi?!
Have no idea yet if that would work, that's why I started this topic, for brain storming about this. [emoji1]
Would be nice to have a multimedia central with Waze running... Hope it gets popular fast
that would be awesome and i am totally into that.
as far as i know, some guy made an lolipop port for the pi2. maybe we can use that as a base.
jackcaos said:
that would be awesome and i am totally into that.
as far as i know, some guy made an lolipop port for the pi2. maybe we can use that as a base.
Click to expand...
Click to collapse
Try my Headunit app of course; see sig...
But it requires Android 4.1+, a decently fast H.264 decoder, at least at 800x480 resolution, and USB Host Mode support, or in future WiFi Direct.
mikereidis said:
Try my Headunit app of course; see sig...
But it requires Android 4.1+, a decently fast H.264 decoder, at least at 800x480 resolution, and USB Host Mode support, or in future WiFi Direct.
Click to expand...
Click to collapse
Hi Mike, my apologies for cold outreach. Interested in your technology, please PM me so we can talk.
Thank you
thundpa said:
Hi Mike, my apologies for cold outreach. Interested in your technology, please PM me so we can talk.
Thank you
Click to expand...
Click to collapse
Anyone can email me anytime at [email protected] .
Is this already built? Or are you just suggesting an idea? I'd love to have it in my car. Do post here if when it is ready. (I mean the PI version)
mathewparet said:
Is this already built? Or are you just suggesting an idea? I'd love to have it in my car. Do post here if when it is ready. (I mean the PI version)
Click to expand...
Click to collapse
Quote from OP:
Have no idea yet if that would work, that's why I started this topic, for brain storming about this.
Click to expand...
Click to collapse
I will be/have released my Headunit app as open source, so someone with the skills could do this.
But I likely won't be doing it myself.
If there is someone with skills to compile your head unit app would be great.
Where can we find the code for your app?
Sent from my Nexus 7 using Tapatalk
luci84tm said:
If there is someone with skills to compile your head unit app would be great.
Where can we find the code for your app?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
https://github.com/mikereidis/headunit
I might re-consider and do it myself, but my time is limited. I could also just to try help someone to port it.
I would rather have it working well on Android alone than having it half working on multiple platforms.
Hi,
I started to work on it. but I started from scratch for 2 reasons :
1/ I want to understand how the protocol works, it's important because there is no documentation available.
2/ The dev approach is very different : it's mainly based on libusb only and I try to implement the AA protocol without dependency with the underlying transport.
I plan to open code but now it's just too early. Sharing knowledge is a good start.
The Android headunit source code is very helpful to understand the protocol. Thanks for sharing the code.
So far what is done :
-100% asynchronous processing of usb transport so the thing is fully event based. It seems that the code becomes less messy this way and asynchronous programming model fits well with libusb.
-switch to accessory mode works
-ssl handshake is ok so the init phase of the protocol is working
Now I just got my first encrypted message from the phone. Encryption is not a big deal. I think I will be able to capture the first h264 buffers end of this week.
I imagine RaspberryAuto (codename for now) could run on a very lightweight JEOS style Linux with readonly flash filesystem. I will take look at the Openelec project which leverages this kind of system. I never developed UI for RPI, that's the main pain for me.
As it is a 100% C program it won't need a lot of RAM so the cheapest Raspberry model could be enough. H264 is not a problem as RPI supports hardware decoding. I'm a little bit more worried about the cost of the SSL processing (I don't know if the PI processor is good enough for that.
So why a PI ? Simply because it's open and documented, it's fast for h264 decoding, it supports composite output so it can be connected to the factory head unit of a car. Another interesting point is the my code is working on Ubuntu Intel too so there will be probably more choices for the target device at the end of the story. But PI is just enough for this project.
marcjero said:
Hi,
I started to work on it. but I started from scratch for 2 reasons :
1/ I want to understand how the protocol works, it's important because there is no documentation available.
2/ The dev approach is very different : it's mainly based on libusb only and I try to implement the AA protocol without dependency with the underlying transport.
I plan to open code but now it's just too early. Sharing knowledge is a good start.
The Android headunit source code is very helpful to understand the protocol. Thanks for sharing the code.
So far what is done :
-100% asynchronous processing of usb transport so the thing is fully event based. It seems that the code becomes less messy this way and asynchronous programming model fits well with libusb.
-switch to accessory mode works
-ssl handshake is ok so the init phase of the protocol is working
Now I just got my first encrypted message from the phone. Encryption is not a big deal. I think I will be able to capture the first h264 buffers end of this week.
I imagine RaspberryAuto (codename for now) could run on a very lightweight JEOS style Linux with readonly flash filesystem. I will take look at the Openelec project which leverages this kind of system. I never developed UI for RPI, that's the main pain for me.
As it is a 100% C program it won't need a lot of RAM so the cheapest Raspberry model could be enough. H264 is not a problem as RPI supports hardware decoding. I'm a little bit more worried about the cost of the SSL processing (I don't know if the PI processor is good enough for that.
So why a PI ? Simply because it's open and documented, it's fast for h264 decoding, it supports composite output so it can be connected to the factory head unit of a car. Another interesting point is the my code is working on Ubuntu Intel too so there will be probably more choices for the target device at the end of the story. But PI is just enough for this project.
Click to expand...
Click to collapse
Great work, keep us updated I've just ordered a car with android auto but it would be great to have something affordable for my wife's car.
Juicie said:
Great work, keep us updated I've just ordered a car with android auto but it would be great to have something affordable for my wife's car.
Click to expand...
Click to collapse
Hello Juicie,
Yes my new car will come with AA support as well so I have lost some motivation to complete this work these last few days. I can share my code with anyone that would like to continue.
I will do my best to release an alpha version that will work on Ubuntu but there will be more work to do to use the h264 hardware decoding of PI.
wow! that sounds great!
This could get really interesting now that RPi Foundation have announced a touchscreen....
Hi,
I have good news. I have a prototype fully working on Ubuntu (screenshots attached). The rendering is very good and smooth. Nav is fully working.
Now we just need to port the code on the PI itself. I only used libraries available on the PI so it should be straightforward except for the rendering. For rendering I use gstreamer because gstreamer is portable and supports omx (hardware accelerated h264 rendering on the PI). I think I just need to set the PI omx decoder and sink into the gstreamer code to make it work. The tricky part could be to capture the touch events if the sink doesn't provide them itself.
Problem is I don't have a spare PI to complete the job.
hi,
That's really great news didn't expect such good progress!!
I do have a rpi and can test if you give me the app.
The problem at the moment is that I don't have an android device running lollipop..but I can try to find one
Sent from my GT-I9300 using Tapatalk
I'm going to follow this !
If you need someone to test feel free to ask !
Hi
I will try to build an image pour the PI asap then.But I will have to disable the touch events at beginning because the purpose is to port the code and use the omx decoder engine.. That's a first step.
marcjero said:
Hi
I will try to build an image pour the PI asap then.But I will have to disable the touch events at beginning because the purpose is to port the code and use the omx decoder engine.. That's a first step.
Click to expand...
Click to collapse
Where are you currently hosting your code?
Dear XDA members,
if you feel the same as the friends at https://postmarketos.org/ :
"We are sick of not receiving updates shortly after buying new phones. Sick of the walled gardens deeply integrated into Android
and iOS. That's why we are developing a sustainable, privacy and security focused free software mobile OS that is modeled after
traditional Linux distributions. With privilege separation in mind. Let's keep our devices useful and safe until they physically break!",
then it is time for you to step forward!!!
Last night initial support for the OPPO Find 7a was commited to the postmarketos pmaports git repo
https://gitlab.com/postmarketOS/pmaports with commit https://gitlab.com/postmarketOS/pmaports/commit/1f8095771c4659d31e8b228dd85018e9ca9963ca.
It was a pain to get this committed as I'm not used to the git workflow, nonetheless with the help of the maintainers over there
and after deleting a few merge requests ( a no-no, don't do that!!) at the end we got it done.
At the moment the device port is only for the Find 7a for the simple reason that I own one but I'm sure it can be extended to the
Find 7 and Find 7s.
The answer to the question that you dear reader have in your mind now: "what works?" is easy: NOTHING WORKS YET!!!
The only thing working so far is that the kernel compiles, you can flash it or fastboot boot it, start a rootfs on the microsd card
and ssh into the system over a usbnet connection to look at all that lovely processes running.
Lots of work still needs to be done, I'm pretty shure that I will not be able to do this myself as my knowledge about the hardware
part of the device is minimal and I would need to reinvent the wheel for every little progress.
As I'm sure that there are still a lot of knowleadgeable develepers (THAT'S YOU!!!) lurking around this list my hope is to lure them
to contribute to this project.
I personally dream of the Find 7 running postmarketos and KDE plasma-mobile but even maemo would be ok!!!
Come on, let's do it!!!
Best regards,
farmatito
Links to get more info:
https://postmarketos.org/
https://wiki.postmarketos.org/wiki/OPPO_FIND_7a_(oppo-find-7a)
https://wiki.postmarketos.org/wiki/Porting_to_a_new_device
Screen and touchscreen working!!!
Still a lot of work to do. Help is appreciated!
Progress report
New package for installing various firmware blobs merged!
Next big thing should be to try to make video hardware acceleration work,
if there are any experts here help is appreciated!!!!.
Progress report
The attached photo shows my Find7a running the XFCE4 desktop.
The interface is fast enough even without hardware acceleration.
As the Desktop is not optimized for mobile devices it is not
a such a great user experience, but the basics work.
Still a lot of work to do, help is appreciated.
Progress report
Wifi Works!!! and you can browse the internet!!!
Help is still appreciated!!
No progress
This time there is no progress to report:
video acceleration not working yet due to the fact that the kernel is rather old (3.4.113), backporting newer drivers did not work out as the codebase differs to much (so no KDE plasma).
making the various sensors work is also rather difficult as the kernel uses a Device Tree and so even if there are drivers for the sensors you need some board specific info to create the device tree nodes.
last but not least the last version of xfce4 in alpine linux is not touchscreen friendly. GTK combo-boxes are now unusable (will eventually try maemo).
Help is very, very appreciated.
Saw this post, has a Find 7 and want to know more.