Just one caveat: I have done searches (read: multiple).
How in the world does CyanogenMod get to all of the supported devices? All of a sudden once CM9 is released, it goes out to all devices or what? Does it need to get ported from the source for each and every individual device? In general, how is CM updated and how does it get out to the officially supported phones/tablets?
The most important things of Cyanogenmod are the same on every device.
The special driver and some device-specific features are developed by a part of the team.
There are a lot of Cyanogenmod developer out there in the whole world. Every developer has his own favorite phone.
I hope I could help you.
Greetings,
KanocX
Related
I’ve been working on getting my source trees on Github in shape so that anyone can build a basic CyanogenMod system. Some small parts still need added but things are looking good there.
I’m also continuing to examine the backup/restore option for the proprietary bits necessary to operate your device, so I can simply ship open-source code only. I believe this is well within the license and the spirit of the ADP1 and ION devices.
A lot of people are helping to work many of these issues out, notably the guys from Google (Dan and JBQ) who manage the open-source project. Some great discussion and initiatives are happening like the Open Android Alliance and the Replicant projects. As much as it sucks to be sort of the “fall guy” for this, I can take it. Let’s fix the problems and move on.
Expect more from me by the weekend!
http://www.cyanogenmod.com/home/just-a-quick-update
keep it running! =)
That's Greeeeat!
I take my hat off to you sir!.
Excellent News...
it's nice to get updates, but i'm sure most of us are smart enough to visit the site directly for his updates or check his twitter.
no need to open new threads for this. -.-
thats the way more donating to you
Android-x86 is a project to get android up and running on x86 architecture. It is currently ran by just two people, and 1.6 is more or less completely functional on Eeepc and Dell Mini's.
However, progress has slowed, and the developers are beginning to lose interest due to the current community following. A large amount of the followers of the project demand things, and give little back, often getting angry if they are not instantly provided what they want. This is a scourge of most opensource or hack projects, but especially so here, as the project has had little interest from other devs, leaving them on their own.
Whilst I do not have the ability to give a whole lot of help myself (yet), I desperately think this project should succeed, and am asking any able developers with free time who are up for seeing Android up on a new platform to give it a go.
The google discussion group is here: http://groups.google.com/group/android-x86
The homepage is here: http://www.android-x86.org/
Thanks for reading, and thanks for any support you are able to give these guys.
I saw in the development thread that a bootloader unlock tool is available, which is great news.
But besides the "thanks" "awesome" and "doesn't work" wouldn't it be usefull to share the full experience?
For example: I noticed that there are initiatives to install CM9 after unlocking it.
- how well does CM9 (or any other for that matter) work with the TF300T?
- the stock TF300T showed trembling/shaking of certain UI elements, are those absent with CM9 (or any other)
- can apps still be purchased through Google Play?
- hickups with WIFI, bluetooth, etc?
- etc
(Although I might be showing some occupational disability when asking for all this info )
Cheers!
The unlock tool was just released yesterday. No ROMs are available yet. You have to give the devs some time to port CM9 and whatever other ROMs. So just sit tight and watch the dev section. When the CM9 port is ready, it'll be there.
Many ROMs in early stages will have bugs as well, since the dev can't test every app and every scenario with their device. The community helps out quite a bit by flashing and seeing for themselves, then reporting. However, the dev will usually tell you of known bugs if there are any.
Give it some time and you will see some cool things in the development section.
The UBports Project
What is The UBports Project?
Ubports team of developers and a meeting place for developers that wish to port Ubuntu Touch to as many devices as possible, This is a place where Developers can talk to other developers and learn from each other and help push Ubuntu to more devices as teams, or by yourself but with community support if you wish.
If you’re a user of a device without much developer knowledge this is also a place you can help out, you could try to link developers together if you think they could help, you could send a link, or help by throwing a bone, donate devices or money for things such as OTA (over the air) update servers, web server, CI servers and other money costing services and items!
A user can also get some help if they spot a bug or have any issues with there Ubuntu Touch Device, there are many Developers and Users that would love to help you with any problem you have!
This is a place for Users and Developers to Play, I mean Port nicely!
What is Ubuntu Touch:
Ubuntu Touch is a new OS to mobile devices, developed by canonical. The biggest problem with it now is the lack of support to different devices, that is what we want to change…
So are you interested in Ubuntu touch? Does it look like something you would use as a daily driver? or may you just be curious on what this all is about, Join us at the forum or download Ubuntu touch to your device. If the device is not listed in the device page, you can vote on your device to get ported.
What Devices do you support?
Currently we only support the OnePlus One, and we will try our best to port the new OnePlus Two as fast as it's out. That said, we are always looking to port new devices!
Device page: devices.ubports.com
Cannot find your device? send an email to [email protected] with your device, and I will add it to the list.
Are you a developer?
Join us make Ubuntu Touch available on a number of different devices, and also make it stable and safe to use as a daily driver… Instead of working alone, join our community and get your device supported as a official UBports, then your device will get OTA servers, Download servers, CI for builds and support by other UBports developers.
Any question, please let me know! comment bellow or join our forum at forums.ubports.com
Hi everyone,
I'm new to this forum and have joined as I've started working on a private/commercial version of AOSP. I've worked in mobile apps natively and more recently using React Native for the last 5 years and am enjoying hacking and playing around the source.
The main usage for build of AOSP is for a bespoke vehicle tracking device with a few additional features. So far I've managed to build AOSP, flash onto a device, and most recently set the tracking app as the home app so that it boots on launch.
The question that I can't find a solid answer to online is does anyone the best way of going about modifying AOSP so that we can deploy an OTA zip update and have the OS download and update it?
I'm not sure if this is necessarily the best way/use of time. I'm guessing it might be easier to just update the app itself internally and not develop OTA updates for the OS? I think at this stage I'm just after opinions before I spend too much time getting stuck into it. My only concern would be that we have 100+ devices out there and no ability to update the OS... although if it's a basic build of AOSP that just removes a few pre-installed apps, has a custom bootlogo and replaces the home app, maybe that's not necessary?
Any advice at this early stage would be gratefully received! Additionally, any tips for development or something a noob would benefit from would be great.
Thanks,
Joel