Database Info

[WIP][CM7.2] Micromax A70 [Developers help needed!]

Alpha release of CM7.2 for Micromax A70.
Ported using dsixda kitchen's porting tools (from a LG P500 ROM based on CM7.2 nightly).
Micromax A70 basic info:
Runs on Froyo 2.2.1 presently.
Kernel: 2.6.32.9-perf
600MHz processor.
MSM7627.
256Mb RAM + 160Mb ROM.
Adreno 200 GPU.
Things that work:
Hardware keys.
Sound.
Things that don't:
Touch.
Cellular.
No ADB => No logcat.
Nothing else works apart from that mentioned as working.
No kernel source provided my Micromax even after many requests from many people.
Requesting help from xda devs to help with this.
Regards
DOWNLOAD
Need to flash this afterwards: Boot
How to flash:
1.) Flash the ROM using recovery. (Worked for me both with and without clearing data or cache)
2.) Flash the attached "boot.img flasher.zip"
P.S. Although the boot.img flasher and the rom have save boot.img, it won't boot unless you flash the boot.img flasher zip.

for keys are you changed keychars and keylayout folder under in usr folder with any a70 rom. If not change now so key will work

cips gokhle said:
for keys are you changed keychars and keylayout folder under in usr folder with any a70 rom. If not change now so key will work
Click to expand...
Click to collapse
Hardware keys work as they are supposed to.
Which means the keychars and all are correct.
The touch based keys don't work (as touch doesn't work).

main thing
you are ported cm7.2 nightly rom. Which is nbb(new baseband) for nbb need .35 kernel a70 have .35 kernel. .35 kernel need to fix many bugs . If a70 have .35 then this bug will be fix but don' have then it will very very hard to fix gsm and other bugs. If a70 have .32 kernel then then try to port mike os cm7 rom. It's obb(old baseband) it will work with a70. Nbb to obb port is hard. You can port nbb rom to obb only in this device. If you port nbb rom from other device and don't have any .35 kernel then it hard to fix. And best luck for your rom

cips gokhle said:
you are ported cm7.2 nightly rom. Which is nbb(new baseband) for nbb need .35 kernel a70 have .35 kernel. .35 kernel need to fix many bugs . If a70 have .35 then this bug will be fix but don' have then it will very very hard to fix gsm and other bugs. If a70 have .32 kernel then then try to port mike os cm7 rom. It's obb(old baseband) it will work with a70. Nbb to obb port is hard. You can port nbb rom to obb only in this device. If you port nbb rom from other device and don't have any .35 kernel then it hard to fix. And best luck for your rom
Click to expand...
Click to collapse
Thanx for that info
But the problem is, whatever ROM is tried to port...touch never works
Tried with AOSP GB and even CM6 didn't work

akshaybz said:
Thanx for that info
But the problem is, whatever ROM is tried to port...touch never works
Tried with AOSP GB and even CM6 didn't work
Click to expand...
Click to collapse
can you expalin full toch problem. I mean are you see any ring in screen or full toch is not working?

cips gokhle said:
can you expalin full toch problem. I mean are you see any ring in screen or full toch is not working?
Click to expand...
Click to collapse
Full touch ain't working.
Additional info:
A dev, PlayfulGod, created a boot.img from CM source (changed the ramdisk), using that we were able to boot into these ported ROMs.
If we use stock boot.img, we just have black screen or bootloops.
I flashed that boot.img over stock ROM, touch worked then.
Which means the problem ain't from the kernel.

akshaybz said:
Full touch ain't working.
Additional info:
A dev, PlayfulGod, created a boot.img from CM source (changed the ramdisk), using that we were able to boot into these ported ROMs.
If we use stock boot.img, we just have black screen or bootloops.
I flashed that boot.img over stock ROM, touch worked then.
Which means the problem ain't from the kernel.
Click to expand...
Click to collapse
let me see if I can fix that while compiling from source.
Are you able to separate/find out the touchscreen drivers from stock?

akshaybz said:
Full touch ain't working.
Additional info:
A dev, PlayfulGod, created a boot.img from CM source (changed the ramdisk), using that we were able to boot into these ported ROMs.
If we use stock boot.img, we just have black screen or bootloops.
I flashed that boot.img over stock ROM, touch worked then.
Which means the problem ain't from the kernel.
Click to expand...
Click to collapse
that mean a70 have custom kernel. And you used stock kernel to port rom? Also some time needed to add full toch driver in kernel. But it's not always need. And i don't know more info in a70. Are you asked help from playfullgod? First time i see toch problem in gb. Ics have toch problem. I think other a70 dev will help you to fix toch. Because i never used a70. If you faced ring problem then i can help. In other ported rom adb was working if working then you will find why toch is not working. And in cm7 roms always use custom kernel.

abhis3k said:
let me see if I can fix that while compiling from source.
Are you able to separate/find out the touchscreen drivers from stock?
Click to expand...
Click to collapse
Nope.
cips gokhle said:
that mean a70 have custom kernel. And you used stock kernel to port rom? Also some time needed to add full toch driver in kernel. But it's not always need. And i don't know more info in a70. Are you asked help from playfullgod? First time i see toch problem in gb. Ics have toch problem. I think other a70 dev will help you to fix toch. Because i never used a70. If you faced ring problem then i can help. In other ported rom adb was working if working then you will find why toch is not working. And in cm7 roms always use custom kernel.
Click to expand...
Click to collapse
A70 doesn't have kernel source.
Can't use custom kernel.
We can only modify the ramdisk.
PlayfulGod doesn't have A70 either....

akshaybz said:
Nope.
A70 doesn't have kernel source.
Can't use custom kernel.
We can only modify the ramdisk.
PlayfulGod doesn't have A70 either....
Click to expand...
Click to collapse
Let me make this clear : A ramdisk is something which helps you to boot. After booting drivers are provided by kernel. No wonder, the touch works in stock.
And yes, Micromax has a custom kernel. They have confirmed this over mail. This is the sole reason they did not provide the kernel source code.
I have seen the stock rom thoroughly. The touchscreen firmware there is a binary ts_fw.i. We have to use that one along with yamato firmwares if we need the radio to work in CM7.2. Let me finish downloading the sources. I am ATM building the vendor & device folders & will upload to github when finished.
P.S. I own a LG-P500 myself and I can tell you even if they use same Qualcomm MSM7227 Chipset, form factor is different in both. A70 uses msm7x27_surf form factor.
---------- Post added at 01:06 AM ---------- Previous post was at 12:52 AM ----------
Code:
[B][I]/system/etc/firmware
|-- ts_fw.i
|-- wlan
| |-- cfg.dat
| |-- qcom_cfg.ini
| |-- qcom_fw.bin
| `-- qcom_nv.bin
|-- yamato_pfp.fw
`-- yamato_pm4.fw[/I][/B]
This is the current firmware tree. You need ts_fw.i for touchscreen to work.

abhis3k said:
Let me make this clear : A ramdisk is something which helps you to boot. After booting drivers are provided by kernel. No wonder, the touch works in stock.
And yes, Micromax has a custom kernel. They have confirmed this over mail. This is the sole reason they did not provide the kernel source code.
I have seen the stock rom thoroughly. The touchscreen firmware there is a binary ts_fw.i. We have to use that one along with yamato firmwares if we need the radio to work in CM7.2. Let me finish downloading the sources. I am ATM building the vendor & device folders & will upload to github when finished.
P.S. I own a LG-P500 myself and I can tell you even if they use same Qualcomm MSM7227 Chipset, form factor is different in both. A70 uses msm7x27_surf form factor.
Click to expand...
Click to collapse
Can you tell me what exact email they sent?
Tried adding those firmware files, booted but touch didn't work.

akshaybz said:
Can you tell me what exact email they sent?
Tried adding those firmware files, booted but touch didn't work.
Click to expand...
Click to collapse
Dear Valued Customer,
Thank you for your Email, we would like to inform you that the kernel source key cannot be provided.
For any further Assistance and Query you can contact us on the Customer Support & number given below:
18605008286
You can also log onto our website for information www.micromaxinfo.com
Thanks & Regards, MMX SUPPORT
This was the exact details.
Sent from my LG-P500 using XDA

abhis3k said:
Dear Valued Customer,
Thank you for your Email, we would like to inform you that the kernel source key cannot be provided.
For any further Assistance and Query you can contact us on the Customer Support & number given below:
18605008286
You can also log onto our website for information www.micromaxinfo.com
Thanks & Regards, MMX SUPPORT
This was the exact details.
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
I was taking about the point when you said that they confirmed over mail that they have custom kernel...
Let it be
Did you download the ROM and tried anything?
If we connect device to PC, device only shows charging....
No hint of a USB being connected.

Unless they have custom kernel there is no point hiding the kernel source.
BTW firmware won't load if it is tied to specific kernel version or it is requested by the driver via system call.
No I haven't tried the rom. Can't download it unless sync finishes.
Sent from my LG-P500 using XDA

get stock rom and then try porting.

Copy boot.img of stock rom and extract it you will get everything you want.

karandeepdps said:
get stock rom and then try porting.
Click to expand...
Click to collapse
That's what I used.
karandeepdps said:
Copy boot.img of stock rom and extract it you will get everything you want.
Click to expand...
Click to collapse
What am I supposed to get?
I know the difference b/w the stock boot.img and this one.
Please be more clear on this one

I downloaded n flashed the rom but it didn't go past bootlogo(mmx logo)..i had to pull battery,tried again,no luck..went back for stock then flashed again but same.do i need some specific steps to take..n before some1 ask,i waited at bootlogo for abt 15-20 mins..

mastermind1024 said:
I downloaded n flashed the rom but it didn't go past bootlogo(mmx logo)..i had to pull battery,tried again,no luck..went back for stock then flashed again but same.do i need some specific steps to take..n before some1 ask,i waited at bootlogo for abt 15-20 mins..
Click to expand...
Click to collapse
After flashing the ROM, you have to flash the attached boot.img afterwards ...
Dunno why..
Although the boot.img is same as in ROM but it only boots if you flash it again :/

Let's Get CM10 Booted

Let's try get cm10 too boot atleast im downloading the sources i read a few guides every omap4 device except the lg optimus 3d is either running cm9 or cm10 im gonna try to get it to atleast boot even if nothing else work right well something todo till lg decides to do the upgrade. by the way in the GB Sources for the lg p940 in the kernel sources it contains stuff to do with our phone driver wise i think the only thing that differs is camera + ram.

anybody tried it before?

I'm thinking of trying it, please link the guides you've found!
Sent from my LG-P920 using xda app-developers app

Good luck guys we are all "rooting" (hahah get it, get it ) for you guys , defcomg are you going to try and port the prada ics first and then cm10, or directly ??

If you're hell bent on trying, I would suggest porting a mixture of the Prada ICS and CM10: Prada ICS for most of the drivers and code to make things work and CM10 for the base. This is because you have the CM10 source so it's easy to modify what doesn't work, since the Prada ICS kernel probably won't work out of the box anyway. You could port Prada ICS wholesale but I suspect more things won't work that way given CyanogenMod often has open source blobs for most of the drivers and for whatever chips that are different from the Prada phone whose drivers you need.

defcomg said:
anybody tried it before?
Click to expand...
Click to collapse
yes, but i got an non booting ramdisk + a zipp without media, fonts, vendor and apps.
but it could also be that i have failed, today i will tray it again so let's hope somebody will make it

FPtje said:
I'm thinking of trying it, please link the guides you've found!
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
http://www.kernel-xp.net/index.php/en/guide/25-android/32-compilare-cm10
http://wiki.cyanogenmod.com/wiki/Building_from_source
http://forum.xda-developers.com/showthread.php?t=1668483&highlight=build+cm9+source
http://forum.xda-developers.com/showthread.php?t=1668396
http://forum.xda-developers.com/showthread.php?t=1807505&highlight=build+cm10
rezzsha said:
Good luck guys we are all "rooting" (hahah get it, get it ) for you guys , defcomg are you going to try and port the prada ics first and then cm10, or directly ??
Click to expand...
Click to collapse
Was gonna port it directly i was gonna run a comparison on winhex to see how the kernels differ
pandaball said:
If you're hell bent on trying, I would suggest porting a mixture of the Prada ICS and CM10: Prada ICS for most of the drivers and code to make things work and CM10 for the base. This is because you have the CM10 source so it's easy to modify what doesn't work, since the Prada ICS kernel probably won't work out of the box anyway. You could port Prada ICS wholesale but I suspect more things won't work that way given CyanogenMod often has open source blobs for most of the drivers and for whatever chips that are different from the Prada phone whose drivers you need.
Click to expand...
Click to collapse
Repo failed have to start over damn i think i have identified a few chips. if there was a way to get the kernel what drivers are loaded

Well that's new. Did you do repo init, repo sync and also installing all the dev tools as recommended here (http://source.android.com/source/initializing.html)? To extract the drivers, you'll have to decompile the Prada ICS kernel, extract the drivers, find a CM10 supported device with similar hardware, replace drivers for the different hardware, do a bit of coding to set up a new CM branch on your com and set up brunch/lunch and vendorsetup/makefile and fill it up with the files mentioned above and see if you can compile it.

http://processors.wiki.ti.com/index.php/TI-Android-ICS-PortingGuide
Hope this helps! Good luck!
Sent from my phone.

good luck and hope you manage this would be amazing. A big thank you just for your effort

I just started a new cm9 build with prada ics kernel but with my lame pc it will take some time.

pandaball said:
Well that's new. Did you do repo init, repo sync and also installing all the dev tools as recommended here (http://source.android.com/source/initializing.html)? To extract the drivers, you'll have to decompile the Prada ICS kernel, extract the drivers, find a CM10 supported device with similar hardware, replace drivers for the different hardware, do a bit of coding to set up a new CM branch on your com and set up brunch/lunch and vendorsetup/makefile and fill it up with the files mentioned above and see if you can compile it.
Click to expand...
Click to collapse
Closest Device Running CM10 Same SOC
[JB]Samsung I9100G - https://github.com/CyanogenMod/android_device_samsung_i9100g/tree/jellybean
[ICS]LGE P940 - https://github.com/milaq/android_device_lge_p940
Would This Work Replace the LIBS and Configs in devices/samsung/i9100g with the ones from Prada Compile then in the OUT Folder replace WIFI MOdule wpa_sup the issue here is the kernel i can modify the ICS Kernel of the Prada to Match that of the p920 most things are the same its only a few files that change when kernel is compiled should i just place it on the root of the device folder?

I din't know if that stuff that I think make sense but wouldn't it be better if we try to make at first
a working cm9 zip, and after that try to port cm10? It's because there are already some tutorials of how
to "converting" ics into jellybean.
I also started again building a cm9 build, this time with ics prada kernel source and
the command
Code:
make otapackage
instead of brunch p920.
But it will take some time to compile that because my PC isn't the best (single core 2.8 ghz Intel celeron with 2gb RAM)

This looks way too difficult for me. While I might be able to build Android, I'll have no clue on how to debug or fix issues.

berni987654321 said:
I din't know if that stuff that I think make sense but wouldn't it be better if we try to make at first
a working cm9 zip, and after that try to port cm10? It's because there are already some tutorials of how
to "converting" ics into jellybean.
I also started again building a cm9 build, this time with ics prada kernel source and
the command
Code:
make otapackage
instead of brunch p920.
But it will take some time to compile that because my PC isn't the best (single core 2.8 ghz Intel celeron with 2gb RAM)
Click to expand...
Click to collapse
Well Im Runnning UBUNTU on VMware left it compiling a test build i have two Sources JB/CM @ Android/system ICS/ASOP @ Working_Directory. i just thought it would be much easier to just complile cm10 instead of cm9 then cm10 let me know how your build goes. The Prada Kernel is it modded for P920 or is it stock.
Most tutorials to Compile from Source are not good maybe we could ask codeworx for help he got JB Running on the i9100g
The Needs to be a Convert CM7 to CM9 to CM10 Guide.

FPtje said:
This looks way too difficult for me. While I might be able to build Android, I'll have no clue on how to debug or fix issues.
Click to expand...
Click to collapse
i know what you mean before attempting this i had not even used linux but guides and tuts can only get you so far when Ricardo had a working cm9 all that was whacked was the dsp this was before the lg prada it now has ics wonder why he did not get required dsp drivers and modules from prada ics source it would be cool if he released CM9 at whatever state its in im sure we would manage to get it fully functional

defcomg said:
i know what you mean before attempting this i had not even used linux but guides and tuts can only get you so far when Ricardo had a working cm9 all that was whacked was the dsp this was before the lg prada it now has ics wonder why he did not get required dsp drivers and modules from prada ics source it would be cool if he released CM9 at whatever state its in im sure we would manage to get it fully functional
Click to expand...
Click to collapse
Well I dont thinks so that's gonna happend, I just asked him that on G+ and he said "No".

this time i managed to get apps but who finds the fail?

berni987654321 said:
this time i managed to get apps but who finds the fail?
Click to expand...
Click to collapse
Fail? is it the apps only are the other folder libs etc bin also compiled?
My build was taking to long so i stopped it will attempt again in the weekend this Source Compilation is way hectic

I meant that there's a nfc.apk in the app folder xD . My computer is now working since 9 hours.
app, etc, framework, fonts should be ready but there are some libs missing and I don't know about
the other folders so let's hope that I'm getting this atleast to the cm9 bootanimation.
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
my terminal is completly full just with compiling libwebcore -_-'

[Kernel]Peas-&-Q's

So this forum was pretty barren so i wanted to spruce it up a bit, maybe give you guys some hope that development was going on? inspire someone to start working on something? if anyone has any questions on how this was made or wants to learn i suggest reading teh kernel script i include in all my sources, i am also always willing to offer assistance to anyone wanting to learn
anyways...
this is a stock kernel, does nothing more than change the name of your kernel version in your about phone im trying to merge in some of the oc stuff from my sgs3 kernel but things arent matching up correctly.. might need someone to test what ive got in a future version, for now just enjoy your first source built kernel
Download
CWM Flashable
source​

reserved for pictures of kittens and pancakes

Very nice

shabbypenguin said:
this is a stock kernel, does nothing more than change the name of your kernel version in your about phone im trying to merge in some of the oc stuff from my sgs3 kernel but things arent matching up correctly.. might need someone to test what ive got in a future version, for now just enjoy your first source built kernel
Click to expand...
Click to collapse
I'm willing to test and if you've included a script that'll build a kernel with source I'll start fiddling tonight to see what I can find/do.

KitsunePaws said:
I'm willing to test and if you've included a script that'll build a kernel with source I'll start fiddling tonight to see what I can find/do.
Click to expand...
Click to collapse
you need to modify the script to fit your install and have the ramdisk in the place it points since have all my kernel source in separate folders. and all the ramdisk files in the ramdisk folder.

OK, excuse my n00bness - but how do you create a flashable ZIP out of the boot.img? I am rolling kernels, but unsure of what to do with the resulting boot.img...
I see others say "just take the latest flashable zip for your device and modify" - but there are no other flashable zips of only the kernel... hum.
Thanks!
Edit - I think I'm getting the hang of it... hold please for a new kernel

arrrghhh said:
OK, excuse my n00bness - but how do you create a flashable ZIP out of the boot.img? I am rolling kernels, but unsure of what to do with the resulting boot.img...
I see others say "just take the latest flashable zip for your device and modify" - but there are no other flashable zips of only the kernel... hum.
Thanks!
Edit - I think I'm getting the hang of it... hold please for a new kernel
Click to expand...
Click to collapse
added cwm zip to the OP for ya to kang ;P

How to change boot splash screen?

Hi All,
I'm using [JellyBean][4.1.2]Unofficial CM10 - Updated 11/04 - Butter - MTD - OC Kernel, how can i change the "Galaxy S CyanogenMod" screen?

kitkkkkk said:
Hi All,
I'm using [JellyBean][4.1.2]Unofficial CM10 - Updated 11/04 - Butter - MTD - OC Kernel, how can i change the "Galaxy S CyanogenMod" screen?
Click to expand...
Click to collapse
You have to do it from source...if you don't mind working with android source I'd be happy to tell you how as its fairly simple...or you can yuse the kernel inside slimbean it should be identical to Scotts kernel except for the boot splash as I do use his kernel source...myvoot splas is simple it just says infuse 4g with android 4.1.2 below infuse 4g
I have a screenshot somewhere in the slimbean thread....probably one of the last few pages....
And just to clarify...I don't want to teach you to build from source...more of if your familiar with source I'll show you how to edit the boot splash...sorry, I just don't have the time to teach someone how to build from source ,:/ check out the bottom of my SIG though if you wanna learn..that's where I learned
Sent from my SGH-I997 using Tapatalk 2

Splash Screen
mg2195 said:
You have to do it from source...if you don't mind working with android source I'd be happy to tell you how as its fairly simple...or you can yuse the kernel inside slimbean it should be identical to Scotts kernel except for the boot splash as I do use his kernel source...myvoot splas is simple it just says infuse 4g with android 4.1.2 below infuse 4g
I have a screenshot somewhere in the slimbean thread....probably one of the last few pages....
And just to clarify...I don't want to teach you to build from source...more of if your familiar with source I'll show you how to edit the boot splash...sorry, I just don't have the time to teach someone how to build from source ,:/ check out the bottom of my SIG though if you wanna learn..that's where I learned
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Hi i want to change my splash screen as well i'm running the liquid smooth rom can you tell us how to build the source? or anyway if I change the kernel and i'll put the one from slim bean will I have any issues? Many thanks!

FLASHMINATOR said:
Hi i want to change my splash screen as well i'm running the liquid smooth rom can you tell us how to build the source? or anyway if I change the kernel and i'll put the one from slim bean will I have any issues? Many thanks!
Click to expand...
Click to collapse
Try reading my post again...I clearly say I won't teach you how to build from source...I don't have the time...if you know how to build a kernel from source then I'd be more than willing to help you...as its just one file in the source...
It consists of making the image in gimp, saving it as a c header file, then running a script to format it for source, then replacing the old with the new, and finally compiling the kernel
Sent from my SGH-I997 using Tapatalk 2

mg2195 said:
Try reading my post again...I clearly say I won't teach you how to build from source...I don't have the time...if you know how to build a kernel from source then I'd be more than willing to help you...as its just one file in the source...
It consists of making the image in gimp, saving it as a c header file, then running a script to format it for source, then replacing the old with the new, and finally compiling the kernel
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
MG,
Was wondering with all your free time could you teach me to build stuff, mostly boot animations, from source, of course ??
Actually, just wanted to say congrats on 2,000+ thanks. :good:

Please advise on how to edit kernel

Hi guys
I'm really into Android 4.3.
I'm running CM10.2 (thanks Duy) and loving it.
So I want to make it work with GPS, to be able to make it a daily driver.
SGS i9000 is also working on CM10.2 with aries kernel and GPS is working there.
So I want to compare GPS threads of our and their kernel.
I understand I have to launch a Linux machine (I installed CygWin on my Win8 but couldn't find any proper documentation on what to do with it).
Please explain or direct me to how to extract our boot.img kernel so I will be able to make this comparison and maybe get it started.
Thanks.

Would love to help you, but sadly I don't know how. BUT, I will applaud your initiative. Go, go, go!!!!

Bump
sent from me

@Itzik: tbh I don't have faith for GPS on this phone lol (as for vibrant, GPS works sometimes but lame as hell afaik). Anw, for ur question , I think u should look at the source code tho, compare the two aries upstream at Cyanogen git and our phone aries kernel githubs. Then if u don't know where to start, try reviewing the commits for GPS of upstream aries for vibrant or so. But mayb it's not kernel bug tho, mayb it is device tree bug or vendor as well.
There is no way u can extract a Galaxy S (amd variants) boot.img coz of the kernel header as I read somewhere bout it.
Sent from my SGH-T959V using Tapatalk 2