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 all,
I've have a thread running in the i9000 forums but since I've put the patch online, other CM7 devices are supported and it seems more appropriate to start a thread here.
I've implemented this feature request. It allows you to use your external BT GPS mouse as the 'internal GPS' device. It's completely transparent to the user and all GPS applications should work. I've have a CM7 rom prebuilt on my website. Other devices can be built from source.
I need the code to be tested on other devices and other GPS mouses. Please follow the instructions below to enable this feature and report back how it works for you. Please let me know which devices are working and which aren't.
Tested devices:
* Samsung galaxy s + qstarz 818xt (I'm using this combination to develop)
Build instructions for all CM7 devices
Download the source for your device and setup the build environment.
Apply Framework patch
Apply CMParts patch
Follow the build instructions for your device.
Flash rom and report back if it works for you. Include a logcat output if you report problems.
Background information/Howto/Screenshots available at http://iloki.nl
Hi there, I'm SDR (software Defined Radio) amateur, and I'm looking to connect a USB rtl-sdr Dongle to my GT-i9003, I did a search around our forum zone and I see just a "few old" stuff about OTG and our device, some one knows if we can use it with 3.0.101 kernel? so are the modules runing?, someone did a test?.
I'm thinking build a custom kernel for that with this extra modules but I'm not a programer and I dont know fix kernel/modules issues, maybe some advanced developer knows about that or can try?.
Without more, Bye and thanks in anyway.
Best regards:fingers-crossed:.
I'm not running CM11, but with my Dhiru's 10.1 (3.0.8 kernel) I Tried to connect an USB keyboard, but no results.
crDroid(http://forum.xda-developers.com/showthread.php?t=2544686) said it support otg
but i havn't try it
Hey,
i'm just curious about what the title describes. First of all.
What do i really need:
-kernel sources
-binary blobs (extractable)
-recovery / boot.img (extractable)
Let us just talk about the fairphone 2. Additional to the things mentioned we get the full source code of the OS (which i do not need?).
Where do the difficulties lie? For my understanding we just take the kernel sources, the official cyanogenmod (e.g.) source code, the binary blobs and the recovery / boot.img.
How difficult would it be to port Cyanogenmod to the fairphone 2.
Why is it difficult to port a device with existing (again cyanogenmod just as an example) cyanogenmod to a newer Cyanogenmod (Android) version?
I ask this to estimate/evaluate/judge (don't know the right term) the effort needed to do this. I think i'd be able to do that if i put enough work into it (i "speak" c and java), but i just need some answers.
Especially for example why it is more difficult to port Android 6 instead of Android 5 (which is the currently running Android version)
Thanks!
bigCrash
Has nobody an answer? Just one?
Im specifically interested in why it is more difficult to port e.g. cyanogenmod if there is only an older version of stock android and how important the kernel is? Why do we need kernel sources? Can't one just self-compile a kernel.
Where are the limits if i have a device running 4.2. Why can it possibly run 5.1 but not 6? Is the kernel limiting? Or only the effort to realize such a thing.
Thanks!
bigCrash
Hello all,
I have an old ascend mate 7 that a friend gave to me. I was wondering, are there any ROMs (custom or official) for the smartphone that contains an android version beyond 6.0?
I have the mate 7 MT7-TL10.
Thank you
Ok, so I am thinking that I will attempt to compile a version of Android that is above 6.0. However, I do have some questions:
I have already downloaded the source code. I am about to build the source for the Ascend Mate 7. Then, I found out that I might need to know the Device tree? There seems to be some conflicting information regarding this. Using google's guide, all I need to know is the code name for the device and there we go. We can compile the source! (Woot!)
On the other hand, other guides state that I need to download the device identity such as the tree, vendor, and kernel and include this in the source. (See this guide on xda website: https://forum.xda-developers.com/che...pment-t2814763) In another guide, I need to setup the jack server? (https://www.digitalocean.com/communi...n-ubuntu-16-04)
So which is it? Should I just follow Google's guide or do I really need to know the device identity? If the latter, How do I search for the device tree, vendor, and kernel? More importantly, what are these and how do they work in relation to the Android source?
Also, I believe I will need manufacturer drivers for my phone to operate the peripherals. How do I download this? This might be a stretch but can't I get those files from the Mate 7?