I'm looking into building a custom android device to be embedded in a project I'm working on. I won't need GSM/cell service, so this would be more of a 'tablet' with wifi that's the size of a phone. The first version of this project used some lower level embedded controllers, but for a better user experience (capacitive touch screen, full featured app, etc), I'm looking into using an embedded android device and having a friend (who told me to post here about this) write an app to run on it for me. This project is starting to scale, so buying a cheap tablet and tearing it apart isn't really a good option; I'll need to build something from the ground up. My problem is that I'm more of a microprocessors guy, so I don't really know where to start with this kind of hardware.
I found this thread which was a good start, but the info is like 3 years old now.
Has anyone tried to do something like this? Should I be trying to find a manufacturer who already does this type of thing to work with? If so, how do I find someone like that? If I am going to do the design myself, what kind of processors can run an Android OS? Where's a good place for learning that type of info? Are there any reference designs out there I can use to get started? Is running Android on RaspberryPi a good starting spot, or is that simply not scalable?
Thanks for the help, I hope I'm in the right spot. Apologies if not!
Related
Hey there, everyone.
I'm just looking for some advice. I've been using my Verizon Samsung Fascinate since November, and for the most part have been a very happy user. Ever since I installed a Gingerbread-based ROM, I have been extremely happy with both the device's performance and new features (nothing says cool like the Old TV Shutoff animation). Lately, I have been wanting to try my hand at modifying and packaging my own Android ROMs for the Fascinate. Obviously, I have never done something like this before, so I'm looking for some advice.
I've been programming in Java for over a year now and I'm very familiar with the language as a whole. I've used it in various programming competitions through school along with building some applications and tools for the company I'm currently interning with. Right now, I feel that I have the basic programming skills required to look through code and understand what the logic behind it is (at least I hope).
My question for you all is this: should I jump right in and start poking through the AOSP code, or would it be more beneficial for me to start off as an Android App Developer, slowly working my way into Android hacking? I have some ideas for potential apps (which I'll probably end up developing regardless, but at a later date), so if it would be more beneficial to just develop apps, I certainly have a basis for my ideas.
Any personal stories/recommendations would be excellent. Thanks in advance for any/all answers!
Hi xda-developers,
I am an Embedded developer with vastnexperience in Firmware development in C programming (for microcontrollers), pcb designing, corel draw/photoshop (intermediate level) . Now I am looking to stretch my self a lil further by trying my hands on Android Programming. I have no prior experience in Software development. It would be kind of experienced developers out here to guide me with possible approaches that I can give to Android development without a much steep learning curve. As I would be practicing android development mostly on weekends (as of now), I would like to get started with things that I can relate with already. That way it would keep me going. Help me out with:
1. Possible applications I should work on. Something that can also be helpful for the community of users and developers.
2. Starting point and other obstacles I would come across while development.
3. Application ideas.
P.S: I also have a rPi lying around catching dust.
Some of the features still cant use on this. Libraries could be use.
Start with "Hello World"
Regardless of your software development capabilities you should always just mess around with the tools that are available and see what you like and what you don't like.
Try every tool you can, when you feel like you know those inside out have a go at extending the functionality of one of those.
For me when it comes to learning a new technology like Android SDK just playing with it inspires me to want to create real and practical applications.
Goodluck and have fun.
PS: I would stick around and see what happens with the release of Qt 5.2 Hint hint...
Yea. Android like embedded requires you to set up a Dev environment so get that up first. ROM building vs app developing are hugely different. Decide which and download the tools. (May require you to install a whole new os and tweak it heavily. Last time I ventured to compile a ROM it was a day to set up my Linux distro of choice)
And like what was said before start with hello world and move up in small bites. You will gain better understanding of how things work and will be less frustrated. Don't expect a full featured app to appear. Once you play around with all the little components eventually you will see a big picture and the building blocks for the "big app" will be there ready to use.
Sent from my One using xda app-developers app
Hey peeps.
Was looking at these boards online, does anyone here really use them? If so do you find them usefull for developing ROMs?
Ive never used them before but it looks pretty interesting.
As I understand you could build an Android ROM and boot it up on an SD Card installed in the board plugged into a TV?
Is there any benifit using these over an actual device? Apart from the odd bricking lol
CdTDroiD said:
Hey peeps.
Was looking at these boards online, does anyone here really use them? If so do you find them usefull for developing ROMs?
Ive never used them before but it looks pretty interesting.
As I understand you could build an Android ROM and boot it up on an SD Card installed in the board plugged into a TV?
Is there any benifit using these over an actual device? Apart from the odd bricking lol
Click to expand...
Click to collapse
I have an engineering buddy who owns a Beagle Board specially the Beagle Bone black and he used it to follow along with a lot of the free-electrons training material, he loved it learned a lot he said allowed him to get a lot more exposure to embedded development at all stages of the process. He also used it experiment with compiling ROM's, which he liked to use more then his phone (He only had one device to develop one) because whenever he would mess something up he could easily re-flash a working image and didn't have to risk his phone. As far as benefits are concerned there easier to work with in-terms of flashing and risk then regular devices, you can do more with them then most phones/tablets (You can flash literally anything on it from different bootloaders and homemade bootloaders, to other cool electronics projects). Overall he said it was great to have around as an all purpose learning board and project board for all areas of Android development and other embedded tasks. The Panda Board hasn't been updated in several years, and while it was good at the time is pretty outdated now. Additionally the Beagle Board is cheaper and has better hardware then the Panda Board.
Heya folks,
Where would be the best place to search for someone or a team we could put together in creating a custom Android OS for a selection of mobile devices we have? I've tried Freelancer dot com and nothing is really coming up or anyone of any use to be honest..
I did not want to just start posting and find I'm in the complete wrong area.
Thanks,
WISECORP said:
Heya folks,
Where would be the best place to search for someone or a team we could put together in creating a custom Android OS for a selection of mobile devices we have? I've tried Freelancer dot com and nothing is really coming up or anyone of any use to be honest..
I did not want to just start posting and find I'm in the complete wrong area.
Thanks,
Click to expand...
Click to collapse
XDA must have some very talented Android developers looking either for a job or to get paid a little extra on top of their current wages?
If anyone is interested in a good challenging role and with security experience along with knowing how to create custom Android OSs you should let me know.
We have a whole host of other applications to be developed as well. A good selection of handsets that we have complete access to as well, Everyone starts somewhere but you could start with us and progress to something much more within our company, this does not require you to leave you're current position either or you could just jump right in with the required skills.
We also need application developers but have not found very good companies on places such as freelancer, I'm sure they are all working for one another in some way shape or form!
Anyway if you are looking for something good to sink your teeth in to, we have got a wonderful position for you even leading to becoming our chief CTO in the Android department if your that good.
Let's see some interested, we will take an interest in you and value you're input within our business.
Hi,
When I read the questions and guides, it seems the Surface Duo can be unlocked and rooted pretty easily.
So I was wondering why there is no custom ROM for this device which is, by all means, not perfect (it has a lot of flaws) but that I consider as at least a refreshing attempt to dig out of the "one glass rectangle touch screen" that we're now used to for years.
Is it beacause there's no love for the device ?
Or is it because Microsoft released absolutely no sources for the internal hardware ?
If there's anyone willing to try, I can offer build server to do it...
And contacts in a community to help iron out problems...
Regards.
Microsoft has indeed released the sources of the internal hardware, or, at the very least, some of it. I don't really know how to determine whether or not all of the drivers are included with the kernel source code. But they do have this kernel source code hosted on GitHub, under a combination of MIT, Apache, and GPL licensing, as well as full instructions on how to build the kernel. The instructions are located at microsoft/surface-duo-oss, and the scripts end up downloading from other microsoft/surface-duo-oss-* repositories. I've not actually tried to build this myself, and I'm not sure what you actually end up with afterwards, whether it is just a kernel, or if it also includes AOSP, and whether or not this can be included in the process of generating another distribution such as Lineage. But, I think this should at least be some information that can be used to at least start the process assuming anyone with existing experience is interested in starting this.
I have seen it expressed elsewhere that one reason people have not created a custom ROM is that android 10 does not have native support for multiscreen devices, while android 11 does. Meanwhile, Microsoft has only released android 10 for the device, and this includes the surface-duo-oss scripts as well, but that there is plans here soon (late September) by Microsoft release android 11 for the Surface Duo.
Fingers crossed! Looking forward to a robust desktop mode and multiple external monitor support like the regular Surface Pro does
Basically a phone that acts like a Surface PC when you dock at home or at work so you can actually work from the device like a normal Surface laptop and then fold and put it in our pockets when we're done working
I know this is an older post but I sure wish someone would go ahead and give me the dummy guide to flash their custom rom!! If anyone needs a duo that thinks they can make it happen I have a spare one..... The left screen is glitching in and out tho.