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 :/
Related
http://www.multiupload.com/7FCS3EORXF
The source for the lgp506 (Aka LG Thrive), im hoping devs well get on this, and apply a p506 version for there existing roms, for them to work with the p506 correctly. Otherwise, from what i've been able to surmise is, the only issue with porting roms from the p500 to other variations seem to correlate from the kernel.
and in regard to the p506, the current cm7 rom port works, only the screen is 8-bit and showing only 3-4 pallets of blue.
Hope this source helps out.
if you dont like or cant use multiupload, other means to get the source is just going to http://www.lg.com/global/support/opensource/opensource.jsp and searching lgp506go.
its 2.2 or 2.2.x ?
ccdreadcc said:
its 2.2 or 2.2.x ?
Click to expand...
Click to collapse
i thought it was 2.2.1
Interesting
Searching the internet for phone specs.
I diff'ed the source against the P500 source.
Practically the only difference is that the P506 has two framebuffer(?) drivers (novatek and hitachi) rather than one (just hitachi), with runtime detection of hw.
Relevant kernel config is CONFIG_FB_MSM_MDDI_NOVATEK_HVGA.
Since /proc/mtd is the same for P500 and P506, I guess roms and recoveries go through with just this display glitch issue, but it'd be great to have a proper one.
Does anyone know whether it is possible to just replace the zImage in CWM/amon_ra, or a compilation is required?
I have installed a 2.2.1 P500 ROM on my P506 with my stock kernel and I can verify that the color issue is history. We just need devs to port there kernels to the P506 and we can utilize the ROMs for the P500.
Please devs help us Thrive / P506 users out a little!
Sent from my LG-P506 using XDA Premium App
Ciaox u use linux?
Any devs looking into this?
Sent from my LG-P506 using XDA Premium App
devs wont be interested, if p506 user base is very low. getting more p506 users to comment here might get devs attention ><
ccdreadcc said:
Ciaox u use linux?
Click to expand...
Click to collapse
Yes I do. Why?
BTW I love AT&T
What do you guys need? A kernel? If so get more users to coment this topic and I'll see if its reasonable to release a kernel with the extra framebuffer. But I need to be sure the user base of this phone is high enough, otherwise it's pointless.
We mostly need help with understanding the following:
Will sticking the stock P506 zImage in a cwm/amon_ra recovery, keeping the initrd and everything, just work? e.g., using mkbootimg.sh ?
The diff between P500 and P506 froyo kernels has the following changes. Are they all relevant? were some of these fixed upstream?
Novatek fb driver (and renaming of hitachi fb functions)
ami304 driver changes (support for gyro and pedometer?), including ami306 support(?) EDIT: it's the driver from Optimus V.
some minor added functionality in drivers/input/sensor/kr3dh.c
LG's fix for the touchscreen bug (?) in drivers/input/touchscreen/mcs6000_ts.c
Camera modifications (parameters, added sports scene) in /drivers/media/video/msm/isx005*
MMC changes, incl. not powering down sdcard on suspend
A change of BRCM_WLAN_SLOT to 100 instead of 2 (BCM432X related)
Units change (mul by 10) in drivers/power/msm_battery.c
USB changes in drivers/usb/gadget/msm72k*
added a call to sock_setsockopt in net/socket.c, function kernel_connect()
Would applying the diff to your kernel (or any froyo kernel) would just compile and work (assuming no conflicts)?
Would applying the diff to a gingerbread kernel work, or gingerbread has some major changes?
Is the change (at least the FB one) simple enough to convince you and/or other P500 kernel developers to incorporate it in your builds (so no fork needed)?
Thanks,
R.
+1 for interest, I've already rooted but when I looked into roms etc. for the P506 I found there weren't any so I'd be glad to test recoveries/roms
OK, I got some answers for my questions, and some new questions.
Swapping p506 zImage for p500 zImage in AmonRa 2.2.1b recovery soft-bricks. Fastboot FTW.
Swapping p506 boot.img in a stock P500h rom boots and works in full color, but the logcat is filled with an AMI304-related error.
E/AmitDaemon( 1289): [AMI304D] AMI304MID_IOCTL_GET_CONTROL error​(I also get "battery hot" warnings, but maybe they're unrelated).
Not sure if accelerometer works, had to restore nandroid.
webosguru: do you have this error as well?
I think I saw that some IOCTL codes have changed in the new ami304 driver, so I guess it should be skipped in custom compilation (or fix AmitDaemon, wherever it is).
EDIT: I think this could be also fixed by using system/bin/ami304d from the AT&T rom. I wonder what other native executables I should take from stock AT&T?
I cannot find the 3 buttons required to get to recovery. Power+Home gets to fastboot, with or without VolDown. I have to use adb or rom manager.
Any ideas?
When booting a recovery via fastboot boot recovery.img, keys are not functioning. adb works, so I can flash and/or reboot recovery, but why won't they work?
I tried to grab froyo source via the repo tool, but it seems to download every piece of code ever written and then fail with some missing manifests. Ideas?
Next thing I'll do is probably to deodex and debloat the stock AT&T rom.
just happy progress, however small, is being made. Lots of smiles today.
Pursuing the deodexed stock AT&T rom path, I found out that my stock backup is (next to) worthless; it didn't include OOB info, and unyaffs fails to extract it.
I used dd if=/dev/mtdX of=/sdcard/mtdX.img instead of nandroid. I wonder if dd'ing it back and then a nandroid backup would work.
I have been following this thread. I am new to android but can help with testing out kernels.
Sent from my LG-P506 using XDA App
Really would love to see some ROM development happen for the Thrive!
Sent from my LG-P506 using XDA App
webosguru said:
I have installed a 2.2.1 P500 ROM on my P506 with my stock kernel and I can verify that the color issue is history. We just need devs to port there kernels to the P506 and we can utilize the ROMs for the P500.
Please devs help us Thrive / P506 users out a little!
Sent from my LG-P506 using XDA Premium App
Click to expand...
Click to collapse
How did you do the install without a custom recovery? Or, if you have a custom recovery, which one did you use?
And, +1 re wanting a custom kernel from P506/P505.
sd_matto said:
How did you do the install without a custom recovery? Or, if you have a custom recovery, which one did you use?
Click to expand...
Click to collapse
Install CWM for Optimus One P500 via Rom Manager.
Recovery shows weird colors, but regular rom uses a different kernel.
Now pick your favorite P500 FroYo rom, replace boot.img with your original boot.img and flash via CWM.
I still do not advise it since the ami304 daemon has problems, btw.
To make it perfectly clear: This is a vanilla development kernel. It has absolutely no features the stock kernel does not have (no ext4, no OC, no nothing). But it may cause problems (SOD, eat battery, the apocalypse... you get the idea). This kernel only exists, because all earlier efforts to compile a stabel kernel have not been successfull.
EDIT: And this one isn't either. SOD-issue not solved - may occur less often, though. I'm not releasing the kernel, because it remains faulty.
EDIT2: Samsung released new sources on the 18th of November. Use these and the new toolchain instead!
First things first: The setup.
The Samsung GB source is used. Extract it to a new directory - do not copy it over the Froyo sources, simply because it says "Update1". You should now have something like
Code:
/home/<user>/<working_directory>/Kernel/...
and a folder for the platform - the latter will not be used.
The toolchain is from Codesourcery: Sourcery G++ Lite 2009q3-68 for ARM EABI. Extract it to wherever you like. Just remember the path (<your_path>).
The path to the toolchain, and the correct EXTRAVERSION are adjusted in the Makefile. Nothing else. The EXTRAVERSION is different for every firmware - see: settings => about phone.
Code:
cd /home/<user>/<working_directory>/Kernel/
gedit Makefile
Look out for:
Code:
...
EXTRAVERSION=.7-CL467143
...
CROSS_COMPILE=/<your_path>/toolchain/arm-2009q3/bin/arm-none-linux-gnueabi-
Thanks to Skin at this point, for his helpful tips!
A little spring cleaning is performed
Code:
cd /home/<user>/<working_directory>/Kernel/
make mrproper
This will delete all precompiled files and the config.
The config is extracted directly from the device with
Code:
cd /home/<user>/<working_directory>/
adb pull /proc/config.gz
gunzip config.gz
cp config /Kernel/.config
What happens after setting up everything:
The kernel is compiled.
Code:
make
The Samsung readme recommends another alternative:
Code:
make android_latona_r08_eng_defconfig
make
Do not run this, if you want to keep the .config from the device intact! This will overwrite it, and you will compile with different settings than the kernel on your i9003.
With the help of Skins unpack-repack-tools (look here), a flashable PDA is created. The CF-root normalboot.img from the 21.08.2011 is used as a basis (I like this one, no special reason ). Only the zImage is replaced with the self-compiled kernel.
The PDA is flashed with ODIN.
After the first reboot, the cache and Dalvik-cache are cleaned in CWM.
Have fun testing! And remember to make a nandroid backup. If you want to go back, flash Skins original CWM, and restore the nandroid backup afterwards.
What do you mean by stable here,XXKPH is quite stable for me
yamchirobe said:
What do you mean by stable here,XXKPH is quite stable for me
Click to expand...
Click to collapse
Dude he is talking about custom kernal & not about stock kernal. Problem with gb sources is that whenever we compile a kernal it has SOD problem. So this thread is suggesting info how to build a stable kernal.
vishal24387 said:
Dude he is talking about custom kernal & not about stock kernal. Problem with gb sources is that whenever we compile a kernal it has SOD problem. So this thread is suggesting info how to build a stable kernal.
Click to expand...
Click to collapse
There is no problem with the sources...it depends on how they compile the kernel...that is causing the bugs!!
Sent from my GT-I9003 using XDA App
ronhoover88 said:
There is no problem with the sources...it depends on how they compile the kernel...that is causing the bugs!!
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
Do u mean that source code.is correct then skin said that it is not compatable & codes are older. I have used skin & amit's oc version. Both have sod problem Are they doing any mistake in compiling kernal?? Please clear doubt.
No what i meant was the sources which were released (could be) for the dev releases XXKP7/KP9/KPE may be after next official update...we could have GB sources!!
Sent from my GT-I9003 using XDA App
You should post here the kernel so more people will test it.... if you have solved SOD and oher issues i can say that you are great... BTW good work, with your explanation many other people can try...
Seems I didn't - phone didn't wake from standby this afternoon.
But I noticed, that it did respond. I could change speaker volume, the soft keys were lid - only the screen remained black. I'm getting really curious...
XDA_Bam said:
Seems I didn't - phone didn't wake from standby this afternoon.
But I noticed, that it did respond. I could change speaker volume, the soft keys were lid - only the screen remained black. I'm getting really curious...
Click to expand...
Click to collapse
I study on it.... the different between normal sleep and SOD is that, if you have a SOD, when you press the button to wakeup the phone the proc modemctl doesn't work and also the display driver cannot be activated.. i'm not sure if modemctl is responsable of turning up the LCD but this is what i found...
Another thing.... can i say now that must be something wrong in the sources?
Hmmm... I just checked: The last edit made in the GB kernel source files is from the 28. of June. There is no way, these are the XXKPH sources.
XDA_Bam said:
Hmmm... I just checked: The last edit made in the GB kernel source files is from the 28. of June. There is no way, these are the XXKPH sources.
Click to expand...
Click to collapse
I wrote again to sammy;
Here my 1st email:
Hi again. I apologize but i have to ask something else.
I try again to build the kernel with the KPH source and i have the same issue (some time cannot wake - up from lock - sleep).
I follow perfectly the guide on kernel compilation so i really don't understand why that issue happen.
I have to insist on the fact that the source is not completely updated or maybe i'm doing something wrong.
I'm saying that the source are not updated cause the issue is part of precedent GB release but not of KPH.
Wish that you check again and report me if i have to do something else.
Thanks again
... they didn't answer so i wrote another:
Hi, i'm sorry but i have to write again. I tryed many times to compile a working kernel and what i build works correctly except that sometime the phone cannnot wakeup from sleep.... we ( me and other xda members) call this SOD. Also other members have compiled the kernel with your source and all have the same problem.
Please, check the source, they cannot be for the XXKPH FW. Or, at least, show us how to solve our issue.
THIS IS THE ANSWER:
Thank you for your continuous interest in our product.
This web site is intended to provide Open Source Software used in our product.
As mentioned previous mail, some of samsung proprietary codes are not included in the kernel. (codes that are not affected GPL - loadable modules) Please understand we do not guarantee opensource code is executable in target device.
We are sorry for not giving you an correct anwser upto your satisfaction.
Please accept our apology for not being able to handle your request up to your satisfaction.
Best Regards
You may find the source code
and if someone can explain me the meaning of "You may find the source code" woud be great....
XDA_Bam said:
Hmmm... I just checked: The last edit made in the GB kernel source files is from the 28. of June. There is no way, these are the XXKPH sources.
Click to expand...
Click to collapse
xcuseme bro... 28 June = KPH? Can you explain better?
Skin1980 said:
xcuseme bro... 28 June = KPH? Can you explain better?
Click to expand...
Click to collapse
These are old sources for XXKPE and below builds and not for XXKPH i guess coz XXKPH was built in august
We better wait for next official GB release and hope they release latest sorce codes...
You better continue with your OC kernel for froyo now...
Sent from my GT-I9003 using XDA App
When i send source codes to doomlord related to usb otg he also mentioned that 'source codes are always present some what in broken form. They never provide complete source code. We have to manage with that'.
May be doomlord know better about this matter.
Mother effin sammy. Proprietary? it's not even proprietary information that we're asking for. We are just asking complete source codes that function properly. Is it something that they own that makes fix for the SOD? I freakingly don't believe so? Can someone pm me their email address?
go to samsung opensource, search for i9003, then send a message
ronhoover88 said:
These are old sources for XXKPE and below builds and not for XXKPH i guess coz XXKPH was built in august
We better wait for next official GB release and hope they release latest sorce codes...
You better continue with your OC kernel for froyo now...
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
Everyone of us might write to sammy... for the kernel i'm sorry but i really don't intend to go back to froyo.... haven't enouth time....
I have a suggestion. We have 3-4 gb releases present with us by samsung. Firs gb source was facing SOD problem a lot. But after that in later version till kph they removed problem successful. Can we compare those kernals & find the differce & come to know what exact changes they have made in kernal so that they reached to stable kernal of kph.
It is not my work!!!
Most of them are made by bbs.mfunz.com , if it is not ethical , tell me and I will delete it. It you need another kernel , tell me and post the sbf file here , I will make it
China kernels : ( may break flash light , use with caution!! )
China 212 : http://www.mediafire.com/download.php?ux8jab7f98dub18
China 260 : http://www.mediafire.com/download.php?7xr7iu9qb44yr2a
China 211 usb fixed : http://www.mediafire.com/download.php?b5akja3pkab7k1p
China 1.11 : http://www.mediafire.com/download.php?qdkyw1a3i1a895b
Others :
3.4.3-36-1.7 : http://www.mediafire.com/download.php?snyxru3rj0b0dfv
3.4.3-33 : http://www.mediafire.com/download.php?b56a54vvq33vl6n
3.4.3-179-002 : http://www.mediafire.com/download.php?nyn5cgrqtrg5iqv
3.4.3-177 : http://www.mediafire.com/download.php?rk5e7kcazklm3dd
ps. Flash it via CWM , FULL WIPE or WIPE CACHE is recommand.
Consider putting up gb kernels too...
Sent from my MB526 using xda premium
nogoodusername said:
Consider putting up gb kernels too...
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I don't know if the new kernels work on old bootloader, I can't test it because it is my only phone. You can post the sbf file here and I will try to make it.
are these from my post on mfunz?
if it is, the zip froyo kernel is not complete. i only put boot.img into the zip without devtree, which means you can only flash between froyo kernels.
if you flash these zips from gb kernel, you won't be able to boot. please flash some fixed.sbf and you can boot again.
dlhxr said:
are these from my post on mfunz?
if it is, the zip froyo kernel is not complete. i only put boot.img into the zip without devtree, which means you can only flash between froyo kernels.
if you flash these zips from gb kernel, you won't be able to boot. please flash some fixed.sbf and you can boot again.
Click to expand...
Click to collapse
I don't know if it was done by you if yes, could you mind I post it here?? thanks for information.
Hi! i've searched informations about kernels but I still don't understand what are the differences between different kernels...will them improve battery healt or change performances or something else? i'm running stock froyo with stock kernel (2.3.32.9- .......), I need to change/upgrade it?
thanks!
kevin_diu said:
I don't know if it was done by you if yes, could you mind I post it here?? thanks for information.
Click to expand...
Click to collapse
of course you can put it here, but with some warnings just as i said.
http://bbs.mfunz.com/thread-157915-1-1.html
are these from the link above?
Hi! i've searched informations about kernels but I still don't understand what are the differences between different kernels...will them improve battery healt or change performances or something else? i'm running stock froyo with stock kernel (2.3.32.9- .......), I need to change/upgrade it?
thanks!
dlhxr said:
of course you can put it here, but with some warnings just as i said.
http://bbs.mfunz.com/thread-157915-1-1.html
are these from the link above?
Click to expand...
Click to collapse
Yes, maybe some of them are copy from your post. And all of those script are copy from your post. I am very sorry about that and hope you don't mind.
FraRiva91 said:
Hi! i've searched informations about kernels but I still don't understand what are the differences between different kernels...will them improve battery healt or change performances or something else? i'm running stock froyo with stock kernel (2.3.32.9- .......), I need to change/upgrade it?
thanks!
Click to expand...
Click to collapse
Different Defy have different hardware and if you flash a appropriate kernel, it improve battery health, but i don't know it can improve performances or something. If you are running stock froyo and kernel, I suggest u don't touch it.
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 -_-'
Can anyone extract boot.img of any Jelly Bean Based ROM & give kernel to me? (ParanoidAndroid would be better )
I wonder why would you need that.
I have really bad upload speed, so it would be hard for me.
Sent from my SGH-I997 using xda app-developers app
The kernel is the same for all JB roms. PA is the same as CM etc. Can't imagine what you need it for or why you can't just download a package and extract it, but I'll attach it here anyway..
Low Bandwidth
zpzp96 said:
I wonder why would you need that.
I have really bad upload speed, so it would be hard for me.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Whizzpopper said:
The kernel is the same for all JB roms. PA is the same as CM etc. Can't imagine what you need it for or why you can't just download a package and extract it, but I'll attach it here anyway..
Click to expand...
Click to collapse
I'm on low bandwidth. & i needed kernel not boot.img. Well, thanks for boot.img
P.S. I need it for compiling PA 2.57 for infuse 4G
i to am wondering why you need the kernel...
samsung boot.img are unlike others, and there isn't tool that i know of that will extract it for you...there is actually no known way to me to extract it...there is also no known way to re inject it into a boot.img...only thing i can think of that might work is to compile a new boot.img from source and use the kernel as a prebuilt...idk if that would work though
anyways if you want the kernel alone your gonna need someone to build it from source and send you the proper file as it cant be extracted as far as i know...then agai its been a while since ive tinkered with things
mg2195 said:
i to am wondering why you need the kernel...
samsung boot.img are unlike others, and there isn't tool that i know of that will extract it for you...there is actually no known way to me to extract it...there is also no known way to re inject it into a boot.img...only thing i can think of that might work is to compile a new boot.img from source and use the kernel as a prebuilt...idk if that would work though
anyways if you want the kernel alone your gonna need someone to build it from source and send you the proper file as it cant be extracted as far as i know...then agai its been a while since ive tinkered with things
Click to expand...
Click to collapse
I'm from Galaxy Fit Forum. I'm compiling PA for infuse 4G, I took CM 10 device config from GitHub. Kernel is not there. So it is stopping d compiling.
AFAIK we need kernel file in device config. During building it uses kernel & compiles boot.img & include it into .zip
RishabhAd said:
I'm from Galaxy Fit Forum. I'm compiling PA for infuse 4G, I took CM 10 device config from GitHub. Kernel is not there. So it is stopping d compiling.
AFAIK we need kernel file in device config. During building it uses kernel & compiles boot.img & include it into .zip
Click to expand...
Click to collapse
Have a look at scotthartbti's github. He has cm, pa, and his own build.. Great dev.
There you will find the kernel, aries-common, proprietary files, and device repos. I bet those are much up to date
Www.github.com/scotthartbti