Database Info

[Solved] [Q] Build Android for phone on Qualcomm MSM7227 (Motorola Quench XT3)

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.

Android parts in HP Pre 3 kernel

Hello everybody,
I was just looking around the Pre 3 kernel sources to find something useful about turning on the flash LED to make a torch when I found some lines related to Android.
Maybe HP just used Android sources to make their kernel or maybe this kernel is ready to start Android ?
What do you think about that ?
Code:
# Android
#
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ANDROID_LOGGER=y
CONFIG_ANDROID_RAM_CONSOLE=y
CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y
# CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION is not set
# CONFIG_ANDROID_RAM_CONSOLE_EARLY_INIT is not set
CONFIG_ANDROID_TIMED_OUTPUT=y
CONFIG_ANDROID_TIMED_GPIO=y
CONFIG_ANDROID_LOW_MEMORY_KILLER=y

legsim said:
Hello everybody,
I was just looking around the Pre 3 kernel sources to find something useful about turning on the flash LED to make a torch when I found some lines related to Android.
Maybe HP just used Android sources to make their kernel or maybe this kernel is ready to start Android ?
What do you think about that ?
Code:
# Android
#
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ANDROID_LOGGER=y
CONFIG_ANDROID_RAM_CONSOLE=y
CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y
# CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION is not set
# CONFIG_ANDROID_RAM_CONSOLE_EARLY_INIT is not set
CONFIG_ANDROID_TIMED_OUTPUT=y
CONFIG_ANDROID_TIMED_GPIO=y
CONFIG_ANDROID_LOW_MEMORY_KILLER=y
Click to expand...
Click to collapse
Qualcomm's reference kernel for that processor is an Android kernel. So all devices based on that processor start with an Android kernel and work from there.
-- Rod

rwhitby said:
Qualcomm's reference kernel for that processor is an Android kernel. So all devices based on that processor start with an Android kernel and work from there.
-- Rod
Click to expand...
Click to collapse
so,is it possible to run android on hp pre 3?

Yes, both the Pre3 and touchpad were developed with android due to mismatch in speed between hardware teams and webOS teams. I.e. webOS teams were way too slow.

pablo_max said:
Yes, both the Pre3 and touchpad were developed with android due to mismatch in speed between hardware teams and webOS teams. I.e. webOS teams were way too slow.
Click to expand...
Click to collapse
On what authority do you make this statement? Do you work in either of those teams? You'll need some facts to back up a bold, unprovable statement like that.
-- Rod

pablo_max said:
Yes, both the Pre3 and touchpad were developed with android due to mismatch in speed between hardware teams and webOS teams. I.e. webOS teams were way too slow.
Click to expand...
Click to collapse
Seriously ? It sounds a little weird, I thought that the Pre 3 was developed with WebOS 2.1.
Anyway, it still would be great to be able to dual-boot Android or at least make Android apps working, maybe within a chroot like there is with the Touchpad.
By the way, would the Touchpad Android IPK work on Pre 3 ? Is there any reason I shouldn't try ?

legsim said:
Seriously ? It sounds a little weird, I thought that the Pre 3 was developed with WebOS 2.1.
Click to expand...
Click to collapse
Without further proof, you should treat that post as trolling. There is no Android available from HP for the Pre 3.
Anyway, it still would be great to be able to dual-boot Android or at least make Android apps working, maybe within a chroot like there is with the Touchpad.
By the way, would the Touchpad Android IPK work on Pre 3 ? Is there any reason I shouldn't try ?
Click to expand...
Click to collapse
You should read the threads on PreCentral where the damage that package does to your kernel installation is outlined. Folks are having to doctor their devices to recover full capability again.
-- Rod

I tried to install the IPK but it didn't want to install the modified kernel.
So I did it manually and now the Pre 3 won't boot anymore.
It's time for doctoring in recovery mode

legsim said:
I tried to install the IPK but it didn't want to install the modified kernel.
So I did it manually and now the Pre 3 won't boot anymore.
It's time for doctoring in recovery mode
Click to expand...
Click to collapse
that's the attitude.
gratz

Wondermedia WM8880 SoC TABLET's - JB/KK ROM and KERNEL+Recovery's Development

Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. So don't be an *** ****
*/
hi.. i'm already started make some modifications on ROM with other Brazilian DEV's for "Evertek S.A - SKMtek Genesis Tab GT7305"... we already found the source kernel from another Netbook or Development Board PC who uses the same SOC... but nothing already have been maked to kernel, we use the provided kernel from stock (Kernel 3.4.5+)... and about the ROM we already have two custom ROM's... One is Stock Modded (4.2.2) and another is KitKat Ported ROM from another Evertek Device... *Portuguese-Brazil Language Site/Forum
And we already make some modifications to this KK port...
- ROOT
- BusyBox
- Init.D support
- Build.Prop Mods
- SuperUser
- zipalign apps after boot
.. and other mods.
we already make too much on ROM but nothing about kernel... we want make a better kernel with optimizations and a better TCP/Clock Table, More Governors , More I/O Scheduler and maybe Overclock to 1600mhz to start after have a custom Kernel booting...
Now we need someone who understand about recovery's like CWM or TWRP and Kernel Compilation better than me to we can start make something awesome =D i think this can be used to another company's/Chinese tablets too, using the same SOC (WM8880) evidently... . . . (Found^^Working^^Recovery's)
i can't start testing here because if i flash this kernel using the Stock Recovery (WonderMedia Recovery tool) maybe i can possible brick my tablet... so if someone understand about CMW recovery to start would be nice =D

Update Progress / ChangeLog ¬
Code:
# 25/12:
- [STRIKE]Found Possible match [URL="http://forum.xda-developers.com/showthread.php?t=2305268"]CWM port[/URL] from [URL="http://forum.xda-developers.com/showthread.php?t=2216390"]Asus MeMo Pad 7{ME172V}[/URL] on XDA Forum[/STRIKE] #NOPE...
- FOUND WOKING [URL="http://blog.hadi-cpu.com/2013/09/cwm-recovery-6036-w8850-rc2.html"]CWM Recovery[/URL] from Malasya Blog from Generic WM8850 SOC tablet , Founded [URL="http://blog.hadi-cpu.com/2013/10/twrp-touch-wondermedia-wm8850-jb-version.html"]TWRP recovery[/URL] too but not tested (Thanks to #Rollidark to notify me about and #osinaldi to discover that from malasya blog) [Mirrors -> [URL="https://www.4shared.com/rar/2POyc0B0ba/CWM_WM8850_NSFAT-RC2.htm?sop=true"]CMW[/URL] -> [URL="https://www.4shared.com/rar/rJBfUTQF/TWRP-JB-NSFAT-WM8850.htm"]TWRP[/URL]] // [URL="https://www.facebook.com/groups/NewSmartFrenAndroTab/"]Facebook Group of Recovery Developers[/URL]
- Studying some way to introduce the missing Touch driver to kernel from [URL="https://gist.github.com/psachin"]psachin Github[/URL]|[URL="http://cdn.liliputing.com/wp-content/uploads/2013/01/rock_02.jpg"]apc-rock-II-[/URL]|[URL="https://github.com/psachin/apc-rock-II-kernel"]kernel[/URL] how already modded the Source to work with [URL="http://tinyurl.com/oqxmuam"]Generic Netbook[/URL] who uses the same SOC
-- Merry Christmas to #ALL
# ?? to 23~24/12:
- ROM JB and KK + ADV. Patch developed by Brazilian Dev's team
- found Source Kernel to WM8880 SoC
Brazilian Developers who already help this projects from forum - genesiseries :
Code:
# KK ROM:
- #paulomsilva2006 {KitKat ROM Port}
- #Rollidark {KitKat Patch}
- #Wcfuria
- #? - Pedro Alves
- #? - Pedro Victor
- #? - Walter Moretti
- #? - Moises Teixeira
Code:
# JB Stock ROM:
- #ylukasy {ROM Dev.}
- #Rollidark
- #paulomsilva2006
- +?
if i forget someone.. please comment below :highfive:

Reserved

wow there's only a handful on and off development going on for this SoC, I still keep my WM8880 tablet just in case somebody made a breakthrough in doing Custom ROM or even getting real ubuntu/debian to boot natively... are you still on this?

funtikar said:
wow there's only a handful on and off development going on for this SoC, I still keep my WM8880 tablet just in case somebody made a breakthrough in doing Custom ROM or even getting real ubuntu/debian to boot natively... are you still on this?
Click to expand...
Click to collapse
just a few Brazilian and Malasya Developers still make progress with this SoC... if you want to try install the custom ROM´s i have shared upper topic.. it will be by your won and I am not responsible for bricked devices...
i´m already started make progress with Custom Kernel but i need found the touch screen driver source and re-work the sound driver(Alsa Drivers...) and compile the recovery with kernel too.. to than have some trust on my work to flash it on tablet =#
:highfive:

DvDwx. said:
just a few Brazilian and Malasya Developers still make progress with this SoC... if you want to try install the custom ROM´s i have shared upper topic.. it will be by your won and I am not responsible for bricked devices...
i´m already started make progress with Custom Kernel but i need found the touch screen driver source and re-work the sound driver(Alsa Drivers...) and compile the recovery with kernel too.. to than have some trust on my work to flash it on tablet =#
:highfive:
Click to expand...
Click to collapse
meh, its my rom testing ground anyway not really worried .. i actually have the tablet connect directly from the battery wires(the battery removed) to the adapter(usb)... anything is better than nothing for the development hehe...wait by Malasya do u mean Malaysia? whos that developer lol..

funtikar said:
meh, its my rom testing ground anyway not really worried .. i actually have the tablet connect directly from the battery wires(the battery removed) to the adapter(usb)... anything is better than nothing for the development hehe...wait by Malasya do u mean Malaysia? whos that developer lol..
Click to expand...
Click to collapse
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/

DvDwx. said:
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
Click to expand...
Click to collapse
what a coincidence , I was wondering today when you will reply lol
ah I see too bad, maybe you will share it at techknowme forum, ... wow Malaysian ?, Im asking because I'm Malaysian, can you pm me the link where its shared?

DvDwx. said:
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
Click to expand...
Click to collapse
please continue developing this project..i have using acer b1 740 and it dont have android 4.4 update

tuyenat3 said:
please continue developing this project..i have using acer b1 740 and it dont have android 4.4 update
Click to expand...
Click to collapse
man... i just don't want blame anyone but... to we can do something to your tablet we need the kernel source and that don't stay open to developers... on this Chinese tablets we have some little configurations to can work with... but the custom kernel project i need to abandon for two reasons... first i don't have much time to can work to create a stable and functional custom kernel to everyone... second i don't have a kernel source compatible with tablets... what i found is from a electronics engineering Project computer Board ... and to it can fit on tablet is missing too much drivers compatibles with to can work smoothly and functional... someday if i found a new source maybe i can try comeback developer something to that =#

please continue developing this project
I use a genesis 7305 his kernel is very poorly optimized would like to make this usable tablet sorry for my bad English I use Google translator ;-;

2021... I tried to put a Chinese rom, but I brick the tablet, it only responds to fastboot, when I put the sudo command fastboot flash:raw boot uzImage.bin ramdisk.bin and plug in the charger and press power it appears a genesis screen.
Boot FOSSEE-OS from SCARD | FOSSEE-Laptop
laptop.fossee.in
GitHub - FOSSEE/FOSSEE-netbook-kernel-source: A low cost fossee-laptop based on wm8880 ARMv7 SoC
A low cost fossee-laptop based on wm8880 ARMv7 SoC - GitHub - FOSSEE/FOSSEE-netbook-kernel-source: A low cost fossee-laptop based on wm8880 ARMv7 SoC
github.com

What is necessary if I want to compile a ROM?

Hi guys. 2 months ago I've came into Android World deeper than before and now I'm very fascinated. I downloaded linux, all the necessary files to compile a rom but I still don't understand some things.
My device is Redmi Note 2 and I use stock MIUI 7. As we all know mtk and/or xiaomi haven't released kernel sources (6795) so developers have to think hard how to make a rom. And there are my questions. Does kernel source is really necessary? What if I compile rom successfully and then port boot.img from stock? Will it work? However developers made some roms based on LP for this device. And I read that I need device tree and vendor, which doesnt exist for redmi note 2 or I still can't use github.
Second question which I have is: does compiling for 64 bit CPU differ from compiling for 32 bit CPU (like 6592)? If yes, could you give me some tips?
Ohh I think you can understand what I wrote
Thanks in advance and please dont blame me for silly questions

If you are looking to compile roms then you picked the wrong device to do it. They are the worst with kernel source. You can't completely compile a rom but use a patch system that does most of the work.
Yes it is different. There are some Tuts around but they are few as most don't use that type of chip.
If you really want to learn to develop then I would suggest getting a different device. One that respects the copyright and gpl laws.

zelendel said:
If you are looking to compile roms then you picked the wrong device to do it. They are the worst with kernel source. You can't completely compile a rom but use a patch system that does most of the work.
Yes it is different. There are some Tuts around but they are few as most don't use that type of chip.
If you really want to learn to develop then I would suggest getting a different device. One that respects the copyright and gpl laws.
Click to expand...
Click to collapse
Thank you for your advices. I have HTC desire 310 and I found the kernel sources. I know what I'll do in my free time

Monsterlevel said:
Thank you for your advices. I have HTC desire 310 and I found the kernel sources. I know what I'll do in my free time
Click to expand...
Click to collapse
To compile a rom u need kernel source, device tree and proprietary, bye

[Research] Supported MTK Custom Roms?

Hi All,
I'm looking for active MTK Custom roms.
I've been browsing all over, but have been unlucky in my search for the moment.
I recently bought an android smartphone on aliexpress and it's a budget phone with moderate specs.
But I'm unsatisfied with the current factory performance of current OS, so I'm searching to replace it with something I might optionally tweak over time as well, but any active custom rom will do.
I'm specifially using the MTK6899 cpu on this phone.
I had to aswell already factory reset to fix storage capacity issue, so not a good sign to begin with either.
I'm really looking for any answer to clarify my quest/research in understanding the possibilities to port this phone to a different rom.

AFAIK Mediatek's source code for their chipsets isn't open source, hence developing Custom ROMs suitable to a specific Mediatek chipset is impossible.

jwoegerbauer said:
AFAIK Mediatek's source code for their chipsets isn't open source, hence developing Custom ROMs suitable to a specific Mediatek chipset is impossible.
Click to expand...
Click to collapse
Hmm that's a bummer, if only I knew this before acquiring this phone, right?

So should I aim at finding one for another mediatek chipset?
Or will there be too many issues caused by incompatibility?

bossc2 said:
So should I aim at finding one for another mediatek chipset?
Or will there be too many issues caused by incompatibility?
Click to expand...
Click to collapse
As I can see you didn't get it.
A Custom ROM basically doesn't depends on Android device's chipset, it only matters with regards to being a 32-bit or 64-bit chipset.
Developers of a Custom ROMs claim their Android ROM is oftentimes faster, more efficient, and use less memory because
they ripped out useless garbage, such as OEM/ carrier installed apps ( AKA bloatware ) or
they optimized the kernel. For example, an undervolted kernel can provide a much better battery life than the stock one.
That's all.

jwoegerbauer said:
it only matters with regards to being a 32-bit or 64-bit chipset
Click to expand...
Click to collapse
(noob here) regarding a tablet
What device info do I need, other than 32/64bits, in order to find a ROM that works?
and I mean basic functions, browser, wifi, touch screen etc... (No need any GSM/celular/mobile etc..)

gsi roms works also on mtk devices

wetito said:
gsi roms works also on mtk devices
Click to expand...
Click to collapse
hey i am looking for a gsi for my Moto G 5G 2022 (Austin) I am a noob i dont know where to find any that will actually work... the device is a mt6833 MediaTek Dimensity 700 and is on android 12... i'd like maybe an android 13 gsi like pixel experience but have no idea where to start.

gr3uh said:
hey i am looking for a gsi for my Moto G 5G 2022 (Austin) I am a noob i dont know where to find any that will actually work... the device is a mt6833 MediaTek Dimensity 700 and is on android 12... i'd like maybe an android 13 gsi like pixel experience but have no idea where to start.
Click to expand...
Click to collapse
Same here, if you're able to get a GSI please share, I'm running Android 11 and I want Android 12 stock ROM