Hey, so last year I bought a China-Tablet called Zenithink C91, it seemed like a good choice back then.
However, the software on it is rubbish. The manufacturer didn't even bother to change anything from the reference software for the hardware platform, did no optimization whatsoever. For example the build.prop is a complete mess with dozens of duplicate lines and references to the reference platform from AMlogic. All the stock firmwares have phone functionality enabled, even though there is no gsm module, showing an empty signal indicator all the time. Or the shipped ICS with gingerbread gapps and so on. The Tablet is just not usable in this state because the software sucks so much, and they do not answer any questions or take advice. Therefore, no sources.
However, I think the Tablet could be much more useful, because it has a decent cortex a9 processor which runs at 1ghz, and a mali 300 gpu.
So much for the situation.
So for a long time I thought about trying to compile a new rom for it, to make it actually work like it should, but I cant find any advice which would help me, because all tutorials that I find require me to use devtrees for devices that already exist. But how would I go to create Android for a device which has none?. I could probably extract most drivers from the latest ICS build. How compatible are they with JB?
On a side note, I wanted trying to Port CWM recovery, does anyone have a pointer where to start?
Thanks and I hope I did not post in the wrong section.
I actually think that there is a source available for your tablet. Check out Slatedroid, as it's a forum dedicated to chinese tablets.
The problem atm is the new version of the amlogic's platform for which they haven't released sources yet.
Oh, and tutorial for Clockwork recovery:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Thanks for your reply, especially for the link concerning cwm.
I am aware of the slatedroid forum, and a user there, too. Zenithink did not publish any sources, I am very sure sadly.
ArRaY92 said:
Thanks for your reply, especially for the link concerning cwm.
I am aware of the slatedroid forum, and a user there, too. Zenithink did not publish any sources, I am very sure sadly.
Click to expand...
Click to collapse
Zenithink maybe didn't, but you can find amlogic sources (the chip/platform manufacturer) here:
http://openlinux.amlogic.com/wiki/index.php/Arm/Android/2.Getting_the_Source_Code
edit: that is if they are using that as a platform ofc, if they're not well from what I see on slate you're limited to modifying stock roms, same as we on elf/aurora ii devices
Yeah, the stock sources are there, but ZT modified them and does not release the changes. No chance then, I guess? Anybody know if there is a chance for JB based on the ICS rom?
Related
Is there any source/ help/ instruction that I can check out to learn how to design/build Android OS for any supported devices? I would like to learn to see if I can build the firmware for my Eken M0001 using the latest Android version.
i think theunlockr.com has a guide of some sort. i would look there!
Code:
android-dls.com/wiki/index.php?title=Compiling_for_Android
This should get you up and running if you are somewhat familiar with the whole Linux thing. If not I would start out by learning how to compile the kernel and some standard libraries for a regular X86(_64) distro. The approach is pretty much the same, only compiling for android requires a lot more work with cross-compiling and getting a working set of standard libraries for arm.
Oh, and sorry about the link thingie. The administrators of this forum are obviously weak minded and have come up with some totally brain-dead limitations for new users. (A new user is not allowed post links , a good RP system would beat that hands down anytime)
Thanks for the info. I will check those links out.
Hi there,
Now, I understand that there's a thread or two and a few web pages directed at compiling Android and its kernel from source.
However, the thread in question is months old, and didn't fully explain the process.
As for the web pages, they are mostly outdated and don't include enough information, not to mention desire specific instructions.
I think that, properly explained, building Android shouldn't be daunting, and everyone should be able to attempt it, if they wanted to.
So, I hope to compose a comprehensive guide on how to do just that.
The problem is that I myself have not been able to put enough instructions together to be able to complete a build. And there is no point digging up old threads.
So, If anyone who knows the ropes (that is, compiling android and a kernel from source) would be willing to lead the way, I'd happily turn it into an easy to understand guide.
Josh.
fllash said:
Hi there,
Now, I understand that there's a thread or two and a few web pages directed at compiling Android and its kernel from source.
However, the thread in question is months old, and didn't fully explain the process.
As for the web pages, they are mostly outdated and don't include enough information, not to mention desire specific instructions.
I think that, properly explained, building Android shouldn't be daunting, and everyone should be able to attempt it, if they wanted to.
So, I hope to compose a comprehensive guide on how to do just that.
The problem is that I myself have not been able to put enough instructions together to be able to complete a build. And there is no point digging up old threads.
So, If anyone who knows the ropes (that is, compiling android and a kernel from source) would be willing to lead the way, I'd happily turn it into an easy to understand guide.
Josh.
Click to expand...
Click to collapse
I followed this guide here and successfully compiled a modified HTC Kernel and I had very little Linux and Android experience.
Obviously instead of cloning the Cyanogen git, you just use the gits you wish to compile
Mekrel said:
I followed this guide here and successfully compiled a modified HTC Kernel and I had very little Linux and Android experience.
Obviously instead of cloning the Cyanogen git, you just use the gits you wish to compile
Click to expand...
Click to collapse
Thanks for the link
Though i don't fully understand the whole 'git' thing. Where do i find them? And how to i know which ones are the ones i want to use?
Josh
EDIT: Also, how do you 'edit' the kernel (i imagine it is somewhat like make menuconfig?). Also:
- Are these sense kernels?
- How do you add modules like OC and UV?
fllash said:
Thanks for the link
Though i don't fully understand the whole 'git' thing. Where do i find them? And how to i know which ones are the ones i want to use?
Josh
EDIT: Also, how do you 'edit' the kernel (i imagine it is somewhat like make menuconfig?). Also:
- Are these sense kernels?
- How do you add modules like OC and UV?
Click to expand...
Click to collapse
A git is a repository for source code, developers upload their source code there and can commit changes. The commit can allow descriptions of what was changed and also details the files changed.
The git system allows other people to add to the source if they have permission, or allows others to read the changes and download the source code.
Git links are usually posted by people who release software, as Android is GPL licensed so people have to release their source code if they're distributing their work.
Editing the kernel, take a look into the git and the commits and it will show you which files were changed and how exactly they were changed. That will give you the best understanding.
UV/OC is done by changing the acpu table in the architectures files and changing the minimum/maximum voltage figures in the board_bravo.c file.
The Cyanogen kernels are not Sense kernels no, it's a modified Google Kernel.
Thanks for the explanation. I followed the guide and built the rom, and it works (always a plus )
Now, the next thing is the kernel. How do I build a kernel with the CM tweaks integrated? I understand that all i would be doing is rebuilding the same one that is already installed, but im doing it to learn.
So, if i synced the GIT, does that include the CyanogenMOD kernel source? If it does, where is it and how do i rebuild it. If not, where do i find it?
Thanks,
Josh.
Hello everybody!
I need an advice on where to get drivers (or what kernel options to use) for my phone (Motorola Quench XT3) build on Qualcomm MSM7227 chpset.
It would be cool to be able to compile new version of Android from source, like gentoo or LFS; we wouldn't depend on Motorola's software updates. The only thing that seems missing is drivers and kernel configuration. (May be I am wrong - correct me)
So how do I find out what drivers/kernel options to use for my hardware?
Any help is appreciated. I would make an understandable guide for compiling Android for Motorola Quench XT3 if I succeed.
Upd:: Motorola Quench XT3 is a "Boston Orange" phone. Look for mods on cyanogenmod forum, in the z71 variants section.
Therein lies the problem.
Linux drivers for phone chipsets (mostly Qualcomm) are often provided as binary lumps for a specific kernel version. When kernel sources are made available for a specific phone then we can generally compile a full AOSP build by making sure that the kernel we build is compatible with the binary blobs, this get more difficult as the framework gets upgraded and depends on features of newer kernels.
So the things to look for are:
What version of Andriod does it run, what do you want to run?
Have Moto released kernel sources yet?
What are the GPU/Radio/BT/Wifi/Audio chipsets
Do we have binder-friendly driver source available for any of the above.
This is all _hard_ stuff and generally if you've never compiled a Linux kernel before this is not the place to start.
Linux drivers for phone chipsets (mostly Qualcomm) are often provided as binary lumps for a specific kernel version.
Click to expand...
Click to collapse
This is OK as long as binary drivers are available for new kernels, I guess.
What version of Andriod does it run, what do you want to run?
Click to expand...
Click to collapse
It has Android 1.6, and my goal is 2.2.
Have Moto released kernel sources yet?
Click to expand...
Click to collapse
yes, they have sources available for download. I downloaded, but couldn't figure out what ".config" they use, in the bundled script "Android.mk" that depends on external variable KERNEL_DEFCONFIG.
What are the GPU/Radio/BT/Wifi/Audio chipsets
Click to expand...
Click to collapse
Ok, I am trying to find that out. Couldn't find specs in the net (including Motorola website), they only give processor (Qualcomm MSM7227) Is there a command like lspci on Android?
if you've never compiled a Linux kernel before this is not the place to start
Click to expand...
Click to collapse
What is the place to start then? Actually I've configured and compiled kernels for several desktops/laptops, they are fine. I am not any kind of expert, but may be it isn't too difficult to build a working 2.2 Android. There's almost no hope to get it from Motorola. Also I don't care about Motorola-specific software.
Overall, thank you for a good & quick response. I will try to figure out exactly what hardware it uses, and post it here.
P.S.: what else people do to upgrade their phones when it isn't supported by manufacturer?
It's MSM7227 !!!
Hello people!
After a lot of reading I start to understand concepts. Turns out, my phone has a good and popular chipset Qualcomm MSM7227. The same chipset is used in, say, HTC Aria and HTC Legend, which are well supported by cyanogen mod. And looks like chipset determines all major drivers I need! (probably except minor things like flash light)
So, I need help of somebody who knows these things better than me in the following questions:
What could be a difference in firmware between (say) HTC Legend and Motorola Quench XT3, which share the same chipset?
Is there a "generic" build for MSM7227?
Any input is greatly appreciated.
Unfortunately that is rarely the whole of it. Slight differences in implementation can make all the difference. E.G. the radio itself has a firmware that may fundamentally change the interface presented to the CPU. Sound/Display/3D are also up in the air.
Short version, if you can find out the chipset driving each of the above (not just the CPU/Radio SOC) and you can either find:
1. 2.2 binary blobs from another phone
2. Open source drivers that can be compiled for the 2.2 kernel
Then you may be ok.
The reason I said that this may not be the place to start is that what you are trying to do here is get binary blob drivers running for a kernel they were not intended to run with, debugging that is some heavy magic on a desktop, even more so on an embedded device.
I also have the same phone and i was looking for a froyo mod.
I would be willing to test it out (i have the same phone ).
I should warn you though i have no mobile phone hacking experience!
SilentMobius, thank you much for good explanations!!
I googled more, and I have strong suspicion that Motorola Quench XT3 is the same as "Orange Boston" phone. That piece of hardware has been manufactured by many companies under many names (GigaByte G1305 Codfish, Apanda A60, WellcoM A88, Vibo A688, Cincinnati Bell Blaze f800, Commtiva Z71, Muchtel A1, Chinavision Excalibur, Motorola Greco, Nexian A890).
Though I am not sure that orange boston hacks would apply to Quench XT3. Is there a way to check their compatability (in hardware, radio firmware, etc) ?
Cyanogenmod
Turns out we are lucky - Quench XT3 is a part of "Boston Orange", and it runs cyanogenmod. This is very nice, and there is no need to make rom from scratch. Moreover, everything I was thinking of is already done for this phone.
Look on cyanogenmod forums in z71 variants section for mods and other information.
Thanks a lot
Uh, could anyone help me?
I rooted the phone with Universal AndRoot but when i click on z41 on rom manager it gets an error.
Help?
qwerty156 said:
Uh, could anyone help me?
I rooted the phone with Universal AndRoot but when i click on z41 on rom manager it gets an error.
Help?
Click to expand...
Click to collapse
In ROM Manager the phone is known as an Commitiva A71. You are selecting the wrong phone.
Hi everyone,
I've been working on CM for the PadFone Infinity (pretty good device, only lacking a good community) for some time, and I've started to have some results now.
I've basically been using Asus' kernel sources and a custom-made device tree. I then tried to build CM and corrected every error I encountered to try to compile ROM successfully. I eventually succeded in compiling it, but it's now that I need help the most.
Why? Because I have no kernel development knowledge at all, and I really don't want this project to die.
So, let's list what does work and what doesn't:
-Recovery compiles and works just fine. I can backup, restore, flash roms, wipe, and everything that is needed.
-ROM and kernel compile without errors too.
-ROM does NOT boot at all. Getting past the Asus logo, the screen just switches off, and phone totally looks like it's shutdown. No backlight, keys are not backlighted either.
So here is what is needed to compile ROM:
-Device Tree
-Kernel sources (modified to compile without errors)
-PadFone Infinity stock ROM (if needed. Also, there are device blobs in it, so it might be useful)
-Asus untouched kernel sources
I do have the device, so if you need anything about it (hardware info, for example), feel free to ask. I'd love to help, even though I've already made some work, I've come to a point where my knowledge will be far from enough...
Thanks everyone for reading, and maybe for helping if you are interested in this project.
Contact Faux, maybe he will be interested in maintaining a Kernel base for this device.
Bumping.
If a xda recognized developer is willing to develop for this device, I'll have one sent to him.
I really want to have CM and some dev community on this device. I started a bounty to be able to have a device sent to a dev, it seems that many people also want development on it.
I'd also bump the thread. I also interested in CM on padfone, and especially after ASUS discontinued device support :-/
mva.name said:
I'd also bump the thread. I also interested in CM on padfone, and especially after ASUS discontinued device support :-/
Click to expand...
Click to collapse
cm always need alot of work and if you don't have the device it's very difficult to have a stable build .
messi2050 said:
if you don't have the device it's very difficult to have a stable build .
Click to expand...
Click to collapse
AFAIRC, topicstarter suggested to donate a device for interested cm-developer
mva.name said:
AFAIRC, topicstarter suggested to donate a device for interested cm-developer
Click to expand...
Click to collapse
Yeah but that was from 2013 look to the post date , i can do it if the offer is still there but i doubt that
Hi everyone. I was given this NS-14T002 tablet for Christmas and after speaking to an insignia employee they promised the update from 4.2.2 to KitKat to be sometime in early summer or late April. Well as you can tell they're a bunch of liars. They recently release a new tablet called NS-15at08 with almost the exact same specs, the only difference being it has a rear camera and it has 1.4 GHz instead of a 1.2 GHz processor. Most importantly the NS-15at08 runs on KitKat. The tasty chocolate I so desire!
Anyways I'm curious as to how difficult it would it be to port it over. I've never ever ported a thing so I'm a bit worried about that but I need myself some chocolate.
My next thought was finding a well-known tablet with the same specs as mine and flashing a custom ROM made for that device. Would this or would this not work? This was actually my preferred way of solving this horrible issue since it would be mean I would most likely also receive Android L. I scoured the web for a device with similar specs but returned empty handed.
Maybe you can help? Here's the specs let me know if you need more information.
Height0.4"
Width8.2"
Depth6.2"
Weight1.2 lbs.
Wi-Fi Built In
InternalHDMI
Ports1Bluetooth
cell lithium-ionpolymer
Operating System 4.2 Jelly Bean
DriveCapacity8GB
Capacity8GBProcessor
BrandRockchipGPS
(RAM)1GBDisplay
TypeCapacitive touch panel (1024 x 768)Processor
Speed1.2GHz
Front Facing WebcamPixels2.0MP
I think this thread [GUIDE]How To Port Different ROMS to Your Device (Simplest and Fastest) would be of help to you.
Perseus71 said:
I think this thread [GUIDE]How To Port Different ROMS to Your Device (Simplest and Fastest) would be of help to you.
Click to expand...
Click to collapse
I appreciate your reply but I was wondering if it would be possible to just flash rom without having to port. A ROM from a device with identical specs.
No. Never. Not unless you love expensive paperweights.
Perseus71 said:
No. Never. Not unless you love expensive paperweights.
Click to expand...
Click to collapse
Okay but I just read the thread and it said I won't be able to upgrade to a newer android version which is kinda the point of me trying to port.
No you can not upgrade unless you have got Source from the Manufacturer.
Perseus71 said:
No you can not upgrade unless you have got Source from the Manufacturer.
Click to expand...
Click to collapse
If I ask for source code they have to give it to me don't they?
developer209 said:
If I ask for source code they have to give it to me don't they?
Click to expand...
Click to collapse
It depends on the manufacturer. Some might others may not.
Perseus71 said:
It depends on the manufacturer. Some might others may not.
Click to expand...
Click to collapse
They said yes and they will email me the source code in a few hours. Now what? ?
You will have to Set up a Linux Build environment and start reading. A lot of reading is required in order not to brick your tablet unless you have good development background.
Here's a Starting point on some of the articles from XDA University. Please note this is just starting point.
Getting Started : Setting up Android Development Environment
How to Build an Android ROM
Porting AOSP ROMs using Source Code
Now please note the mission of XDA Assist is
The mission of XDA Assist is to provide basic help to those who have tried searching but can't find what they are looking for and need assistance. This is not a "helpdesk" providing technical assistance but more to point you in the correct direction with your problem. Perhaps you can't find posts on how to root your phone, install custom recovery or maybe you have questions about how to navigate and use features on the site
Click to expand...
Click to collapse
So we are not able to help you more than this. However if you have further questions on development, you can post in
Android Development and Hacking > Android Software and Hacking General [Developers Only]
or Android Software Development
Perseus71 said:
You will have to Set up a Linux Build environment and start reading. A lot of reading is required in order not to brick your tablet unless you have good development background.
Here's a Starting point on some of the articles from XDA University. Please note this is just starting point.
Getting Started : Setting up Android Development Environment
How to Build an Android ROM
Porting AOSP ROMs using Source Code
Now please note the mission of XDA Assist is
So we are not able to help you more than this. However if you have further questions on development, you can post in
Android Development and Hacking > Android Software and Hacking General [Developers Only]
or Android Software Development[/QUOTEfun.
Gosh this sounds so much fun ??
Click to expand...
Click to collapse