Database Develop

Kovsky Kernel Development [2.6.27]

Guys,
Seems like there are lots of threads popping up with new 'packages'. I thought we should create a thread solely for the discussion of kernel hacks/patches so that we can separate the two:
For those of you who dont know, http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm-xdadev is the repo were are working on.
Just to clarify, this topic is ONLY for discussion regarding Kernel patches. Thanks to vdelf's headset patch it seems sensible to focus on:
1. Backlight always on problem FIXED 01/05/10 (vdelf)
2. Battery Issue FIXED 11/05/10 (drlucky)
3. Camera
4. USB
5. GPS

Makes sense. Lets add USB to the list. While charging works, data transfer does not. Also USB might allow us to debug kernel/android on the x1 and that is what dev's always dream of

:suggestion: why not add the latest kernel as download in the 1st post if there is progress. So everyone know where to download the latest updates u ppl do

dexteral said:
:suggestion: why not add the latest kernel as download in the 1st post if there is progress. So everyone know where to download the latest updates u ppl do
Click to expand...
Click to collapse
It will be great to do this, and stick it

@dexteral,
Anyone can checkout the kernel from the above repo I posted. To do what you require we would need to upload the Kernel everytime someone adds a patch...

vdelf said:
Makes sense. Lets add USB to the list. While charging works, data transfer does not. Also USB might allow us to debug kernel/android on the x1 and that is what dev's always dream of
Click to expand...
Click to collapse
Is data transfer even possible in haret? I mean how would system unmount sdcard if it's running from sdcard itself?

not fast data but normal will work

love it
vietdoan20062006

Hi, Lets add fm-radio to the list

Great idea ... otherwise we are creating such a mess with lots of different kernel versions in different threads.
If anyone is interested in compiling the kernel as well as the wifi modules, I have setup a VMWare debian appliance containing all necessary tools and scripts to compile everything. Since this is a few hundes MB, I haven't got a place to upload ... need to check this first. If you are interested, let me know.

@drlucky
Have you had a chance to look at the backlight issue? I am almost out of ideas

Can you post your modifications on the microp-module and what you found out until now?

_Sensible said:
Guys,
Seems like there are lots of threads popping up with new 'packages'. I thought we should create a thread solely for the discussion of kernel hacks/patches so that we can separate the two:
For those of you who dont know, http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm-xdadev is the repo were are working on.
Just to clarify, this topic is ONLY for discussion regarding Kernel patches. Thanks to vdelf's headset patch it seems sensible to focus on:
1. Backlight always on problem
2. Battery Issue
3. Camera
4. USB
5. GPS
Click to expand...
Click to collapse
hey could you post the steps involved for compiling the kernel i am able to comile the kernel but it is not running

Wich toolchain do you use? arm-2008q1 or arm-2009q3?

X1iser said:
Wich toolchain do you use? arm-2008q1 or arm-2009q3?
Click to expand...
Click to collapse
arm-2010q1
could u write all the commands used by you
the way i have written

Personally I'll start to see how to compile the kernel. Can you share the link to download arm-2010q1?
Have you read this post ?

X1iser said:
Personally I'll start to see how to compile the kernel. Can you share the link to download arm-2010q1?
Have you read this post ?
Click to expand...
Click to collapse
http://www.codesourcery.com/downloa...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
but may be it is not the right one it has got 202 in it insted of 67
ya i read that post only
i was able to compile the kernel but it is giving some errors

_Sensible said:
@drlucky
Have you had a chance to look at the backlight issue? I am almost out of ideas
Click to expand...
Click to collapse
Sorry, haven't had the time. Could you push your changes to the git repo, I will try to have a look at it this week ...

okay i tried to make the kernel bt following the guide above by fatsal...
but i got stuck at
make htckovsky_defconfig ARCH=arm
htckovsky_defconfig doesn't exist (in the new repo anyway, i believe)
any help? which defconfig to use? :S

drlucky said:
Sorry, haven't had the time. Could you push your changes to the git repo, I will try to have a look at it this week ...
Click to expand...
Click to collapse
Just played with the klt-driver a bit. I always get version 0x0000, which on a hero means "bootloader mode". I have tried to migrate the hero code, but with no luck. It seems that the microp-klt needs a "reset", which shoudl be done by using a magical GPIO (on hero: 76), but this doesn't currently work at all. Kernel boots up, but still gets no valuable version number.

[JB 4.1.1][ROW] Just managed to compile

Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
--WiFi (Partially: Signal strength indicator broken. Disable avoiding poor networks in advanced menu)
--GPS
--Internal sdcard
Doesn't work:
--Camera
--3G
--Sound
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
==Boot image gzip for flashing with system image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part07.20120724.img.gz
==System image gzip for flashing with boot image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part08.20120724.img.gz
Remember to always do a backup copy of your device images before flashing new ones.

Great work mate! I assume that if we want to test this later on our tablets, we need to be rooted?
suntechnic said:
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
Doesn't work:
--Camera
--WiFi
--3G
--GPS
--sdcard fuse mounting
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
Click to expand...
Click to collapse

Woohoo! Look forward to trying this!

This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.

Great work, thanks! I'm glad that there is work going on!

Great news! As I installed ota3 before rooting my device, I hope that there will be some way to get cwm and root working...
Sent from my GT-I9300 using xda premium

Very happy that you're working on a new ROM for our device!!!
And I really hope that someone finds a way to root OTA3 since I was also too dumb to do that before updating.
Cheers!

Wow!! Keep up the good work!!!

can't wait, great work!

Great!
I thought I will be first
According to full_indigo device ID, it is AOSP, not CM? Wow..
I think together we could at last make 3G work as other hw are relatively easy to fix(may be not true for camera as sources again changed). I familiar with Qualcomm RIL framework and can't wait to see how it works with tablet and more opensource hardware module..
I also had to repack boot image to include configuration changes (init* files).
Click to expand...
Click to collapse
lenovo haven't packed init scripts? Oo how it works then? ;/
PS: hello from Russia

obscure.detour said:
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Click to expand...
Click to collapse
Lenovo released ICS open source code but they forgot to release new kernel sources. This prevents me from building bcmdhd driver instead of bcm4329. It looks like JB is oriented for NL80211 wireless interface and not WEXT.

this isnt for the K1 is it

It's for tpt only

When can we see this in a flashable version? Not to sound pushy, I know we have all see the development slow down.

Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?

What is TPT
Not to sound stupid but what is TPT? I have a K1 as well and am wondering if this will work?

TPT= ThinkPad Tablet

Lenovo released ICS open source code but they forgot to release new kernel sources
Click to expand...
Click to collapse
yes I also tried to get more info but for now no response. At last they released external folder of their custom build, which also contains alsa-audio, as I seen in cm9 device tree, it should fix audio with ease(maybe after patch as sources again changed in JB).
It looks like JB is oriented for NL80211 wireless interface and not WEXT.
Click to expand...
Click to collapse
but WEXT is there isn't it?
Anyway, congrats on working wifi.

Has anyone else got this up and running? I tried uninstalling CWM and reflashing part 7 and 8 but still no luck.

mr toasty said:
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
Click to expand...
Click to collapse
Some of existing software probably blocks normal startup. It is always advised to clean dalvik-cache and user data (backup first). It's up to you.
Right after Lenovo logo you should see 'Android: Optimizing applications' or something similar.

[DEVS ONLY][BCM21553] Samsung Galaxy Pocket GT-S5300 (Cori) Development Discussion

General informations:
This thread's aim is only to represent a central meeting and discussion point for BCM21553 developers and, in particular, for the open Kernel/ROM sources development for the Samsung Galaxy Pocket GT-S5300 (codenamed Cori).
Information for common users:
As already described in the previous section, if you are not a developer, please restrict your posts to the general discussion thread so that developers can maintain good communication. Every post that is not strictly respecting these rules will be reported to the forum moderators. Thanks for your understanding.
For any other BCM21553 device related question or information, please, use this thread as a reference point, instead:
[DEVS ONLY][BCM21553 series] CyanogenMod 11 for BCM21553 Development Discussion

As someone already might know, I'm streambinder, from MoltenMotherBoard team.
I have already followed some projects for the GT-S5300, but especially kept in contact
with some of the events related to the porting of ROM and Kernel sources for BCM21553 chipset based devices.
In this precise moment, the sources in my possession allow you to be able to compile
a bugfree CWM 5.0.2.8 (based on CyanogenMod 7 code) with a kernel based on the Samsung stock one.
The only - fundamental - problem was due to the fact that unless I hadn't used the prebuilt INIT binary
token in the Samsung stock firmware boot.img, the phone would not work - or, better, boot up.
This means that until the situation - regarding this issue - doesn't change, our access to the porting of custom ROM
would be barred.
Recently, I decided to give Cori another chance and rework my sources, looking at the wonderful work brought
by the BroadcomCM team on CyanogenMod 9 (in particular, thanks to @bieltv.3 and @Alberto96) and @psyke83 on CyanogenMod 11.
They've not only been able to run these two ROMs in a more or less crude way, but this developer has been able to write
the necessary strings to make the INIT binary of some of these BCM21553 devices opensource.
Strong of this informations, I readjusted some of the sources of BroadcomCM's CyangenMod 9, which includes
all the progress carried out by both the team and psyke83, in order to make them work even on Cori,
and am now next to the first test of the CWM 6.X.X.X, based on IceCreamSandwich code.
At the same time, @akhbh is working on the KitKat code based CWM.
I hope I can give more information about any progress as soon as possible.

The General Discussion thread for non-development issues is here:
*.[DISCUSSION] CyanogenMod 11 For Galaxy Pocket GT-S5300 Discussion Thread

Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?

streambinder said:
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
Click to expand...
Click to collapse
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.

akhbh said:
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
Click to expand...
Click to collapse
Perfect.
Which kernel have you based your build on?

streambinder said:
Perfect.
Which kernel have you based your build on?
Click to expand...
Click to collapse
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources

akhbh said:
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
Click to expand...
Click to collapse
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.

streambinder said:
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
Click to expand...
Click to collapse
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September

akhbh said:
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
Click to expand...
Click to collapse
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.

streambinder said:
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori | github.com
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
Click to expand...
Click to collapse
have u tried to build cwm v6 from cm9 source ??

cleverior.ipul said:
have u tried to build cwm v6 from cm9 source ??
Click to expand...
Click to collapse
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.

streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that

akhbh said:
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
Click to expand...
Click to collapse
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?

streambinder said:
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
Click to expand...
Click to collapse
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources coz as said earlier, his kernel is used. Well, we were working together to bring cm11 but weren't successful

akhbh said:
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources.
Click to expand...
Click to collapse
Ok, please send it to me, will compare it with my package.

streambinder said:
Ok, please send it to me, will compare it with my package.
Click to expand...
Click to collapse
Here it is:
http://www.4shared.com/zip/1nKFbOJ2ba/ccccGetux_CM11.html

streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
here the link source https://github.com/cleverior/android_kernel_samsung_cori
i've changed the board name. If your device can not boot after using the zImage from this source, then rename init.bcm21553.rc to init.gt-s5300.rc.

@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed

akhbh said:
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
Click to expand...
Click to collapse
Sincerely don't what are you talking about.
Anyway, have to try to understand where's the problem with the not-booting CWM.
Will try with your sources and let you know.

[MOD] MultiROM (sharing kernel)

I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps. Sorry for inconvience.
this is beta release. for p900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock frimware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/RVXpEgc6c4GKo - this is modded recovery. flash via odin
2. https://yadi.sk/d/CHl8wTYYc4GMZ - patched kernel. (patched my 1.3 pro kernel)
https://yadi.sk/d/D2riVhEgc4GPP - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/jc4uxZeCc4GRb - flash this uninstaller through recovery, then flash original twrp
known issues:
- 1920x1200 resolution in twrp
- in List Roms installed roms dont shown
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power)
multirom apk from play store doesnt support this release.

reserved

more reserved

bonuzzz said:
this is beta release. for p900 only.
I'll wrote full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
Click to expand...
Click to collapse
I saw earlier that you had plans for this, but I didn't expect it to happen this quickly.
Anyway, great initiative.

WOW
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!

m_carleone82 said:
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!
Click to expand...
Click to collapse
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers. I thought about ubuntu, but now I'm not going to have a deal with it. I advice you to look linux deploy

Great job
bonuzzz said:
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers.
Click to expand...
Click to collapse
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/

ESmazter said:
Great job
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/
Click to expand...
Click to collapse
If you could get it working it would be great.

arcadia2uk said:
If you could get it working it would be great.
Click to expand...
Click to collapse
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu

bonuzzz said:
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu
Click to expand...
Click to collapse
My appreciation was actually meant for ESmazter saying: I will look into it

oops, i haven't noticed esmazter's phrase

I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.

bonuzzz said:
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.
Click to expand...
Click to collapse
I was still hoping to get the minor issues resolved, notably the issue with Rom's installer are not shown in the installed ROM's section.

Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!

hhairplane said:
Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!
Click to expand...
Click to collapse
I dont have any plans to port to other devices. It doesnt fully working and I dont have any progress with it...

Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?

brock28 said:
Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?
Click to expand...
Click to collapse
I dont recommend to use this multirom because it has the bug with sharing kernel. So you need to use similar roms as primary and as additional. I dont have an idea how to solve it at this moment.

[DEV ONLY] CyanogenMod 12.0 Bringup for Condor

A couple of people were starting to work on CyanogenMod 12. Hopefully they are still interested in working on these projects. I am posting this as a place to share branches and collaborate if there is still interest in helping.My trees build perfectly.And the recovery baked from the cm-12 tree has display,touch working.But while installing zip I get a weird status-7 'failed to execute update binary.but since the Display,touch is working,it will be a pretty easy for working LP build.Please noobs stay away from asking weird questions.
At this point,I need support from any dev willing to work for this project.My trees are here.
https://github.com/ashwinr64/android_device_motorola_condor/
https://github.com/ashwinr64/android_kernel_motorola_msm8610
https://github.com/ashwinr64/android_vendor_motorola_condor
Btw,no hard feelings for anyone out there including @#buzz
I hope we can port LP very easily soon.

First thanks o.o

Why dont u use philz touch recovery or CWm for flashing
on cm and twrp recovery I also sometimes get those errors

Brawn_Sg said:
Why dont u use philz touch recovery or CWm for flashing
on cm and twrp recovery I also sometimes get those errors
Click to expand...
Click to collapse
Philz doesn't support --block flashing or the new method of flashing LP.our twrp has not properly implemented fstab for installation and I'm not able to make twrp with new fstab in cm-12.0 tree as it is throwing a lot of error messages and I currently don't have any kitkat based ROM tree due to my computer corruption few days ago.
I will be trying a clean build 2day.

ashwin007 said:
A couple of people were starting to work on CyanogenMod 12. Hopefully they are still interested in working on these projects. I am posting this as a place to share branches and collaborate if there is still interest in helping.My trees build perfectly.And the recovery baked from the cm-12 tree has display,touch working.But while installing zip I get a weird status-7 'failed to execute update binary.but since the Display,touch is working,it will be a pretty easy for working LP build.Please noobs stay away from asking weird questions.
At this point,I need support from any dev willing to work for this project.My trees are here.
https://github.com/ashwinr64/android_device_motorola_condor/
https://github.com/ashwinr64/android_kernel_motorola_msm8610
https://github.com/ashwinr64/android_vendor_motorola_condor
Btw,no hard feelings for anyone out there including @#buzz
I hope we can port LP very easily soon.
Click to expand...
Click to collapse
Which version of cwm recovery is in the build?

gud work
@ashwin007 is it compiling ? (kernel source )
Edit :
This should help https://github.com/KonstaT/android_kernel_zte_msm8610/compare/cm-11.0...cm-12.0
check if some commits are missing

goutamniwas said:
@ashwin007 is it compiling ? (kernel source )
Edit :
This should help https://github.com/KonstaT/android_kernel_zte_msm8610/compare/cm-11.0...cm-12.0
check if some commits are missing
Click to expand...
Click to collapse
Ya the kernel compiles perfectly.I have cherry-picked all those commits.and display and touch working.installation is the roadblock
Could you do me a favour?
Can you build twrp from kk tree using my fstab in
My device tree.and don't forget to add 'e2fsck' package to device.mk.thanks in advance!!!!!!
BTW I love your t2u.amazing!!!!
P.s:even my native place is Coimbatore.
EDIT:Well @ace312 its no more cwm in cm tree.its cyanogen recovery made by cm

ashwin007 said:
Ya the kernel compiles perfectly.I have cherry-picked all those commits.and display and touch working.installation is the roadblock
Could you do me a favour?
Can you build twrp from kk tree using my fstab in
My device tree.and don't forget to add 'e2fsck' package to device.mk.thanks in advance!!!!!!
BTW I love your t2u.amazing!!!!
P.s:even my native place is Coimbatore.
Click to expand...
Click to collapse
Coimbatorean gr8 , sorry but i dont have enough bandwidth for a cm sync :crying:
bw tat means u cant install it anyway ?
also thanks much for the complements

goutamniwas said:
Coimbatorean gr8 , sorry but i dont have enough bandwidth for a cm sync :crying:
bw tat means u cant install it anyway ?
also thanks much for the complements
Click to expand...
Click to collapse
nevermind.i think i made a dirty build by replacing cmr with twrp without mka clean.so rebuilding now.hopefully it'll work.

Hey,
Why don't you flash system.img and boot.img with fastboot?

ace312 said:
Which version of cwm recovery is in the build?
Click to expand...
Click to collapse
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.

GeekyDroid said:
Hey,
Why don't you flash system.img and boot.img with fastboot?
Click to expand...
Click to collapse
sw33ty4ppu said:
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
Click to expand...
Click to collapse
Geekydroid.system.IMG is huge (700mb).but Motorola has that sparsechunk tech which separates system image into small part(you must be obviously knowing).so installing system.IMG makes it corrupt the /system partition.twrp 2.8.4.0 is working now.but i need to modify fstab for twrp which I forgot to do
Sw33ty4ppu not a problem.I think you have helped many of them.

sw33ty4ppu said:
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
Click to expand...
Click to collapse
okay. it's been months I left ROM development. Sorry about that.

ashwin007 said:
Geekydroid.system.IMG is huge (700mb).but Motorola has that sparsechunk tech which separates system image into small part(you must be obviously knowing).so installing system.IMG makes it corrupt the /system partition.twrp 2.8.4.0 is working now.but i need to modify fstab for twrp which I forgot to do
Sw33ty4ppu not a problem.I think you have helped many of them.
Click to expand...
Click to collapse
Well, sorry I thought it is less than 215MB. I didn't think of it.

My last device was a motorola defy and developer @Quarx has a booting 5.0 lolipop build. perhaps he could enlighten us on how to make a booting build for out device.
Moto defy came with android 2.1 and kernel 2.6 so he should be able to help.

Now even moto e has received the "motorola update services app" update!! So maybe we are pretty close enough to get android L now!!! I think rather than rushing up things for condor cm12 and getting a buggy build after soo much hardwork wouldn't feel good!! Maybe we can wait a while for the android L to hit moto e ans then finally build cm12 which would be more stable too!!
•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•

see the attachment...
Lolipop is more closer...

This is a development thread.Refrain from posting those monotonous posts.I would like to keep this thread clean.

http://www.stjsgadgets-portal.com/2015/02/moto-e-users-start-getting-lollipop.html?m=1

I've received several reports for this thread in the past 2 days, so now it's time to issue a global warning here:
Let's keep this thread on topic, DEVELOPMENT, which is clearly stated in the title AND in the OP.
If you have a question, SEARCH FIRST, per the Forum Rules
1. Search before posting.
Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.
Click to expand...
Click to collapse