yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] moikop:
I think I found something on UART...

This is from Samsung's .32:

s5pc100-uart.0: s3c2410_serial0 at MMIO 0xec000000 (irq = 16) is a S3C6400/10
s5pc100-uart.1: s3c2410_serial1 at MMIO 0xec000400 (irq = 20) is a S3C6400/10
s5pc100-uart.2: s3c2410_serial2 at MMIO 0xec000800 (irq = 24) is a S3C6400/10

And this, from 3.4:

<<<note: ttySAC0 definition >>>
s3c24xx_serial_probe(c06a74f0) 0
s3c24xx_serial_probe: initialising port c0691f2c...
s3c24xx_serial_init_port: port=c0691f4c, platdev=c06a74f0
resource c0670284 (ec000000..ec000100)
[B]port: map=ec000000, mem=f7000000, irq=74 (74,75), clock=1[/B]
s3c24xx_serial_probe: adding port
[B]<6>s3c6400-uart.0: ttySAC0 at MMIO 0xec000000 (irq = 74) is a S3C6400/10[/B]
<<< note: ttySAC1 definition >>>
s3c24xx_serial_console_setup: co=c0692248 (1), 115200
s3c24xx_serial_probe(c06726d4) 1
s3c24xx_serial_probe: initialising port c0691ff4...
s3c24xx_serial_init_port: port=c0692014, platdev=c06726d4
resource c06702bc (ec000400..ec000500)
[B]port: map=ec000400, mem=f7000400, irq=75 (75,76), clock=1[/B]
...

ports map are ok in both cases, but look at the IRQ. 74 and 75, while in .32 it's 16 and 20 respectively.

I've been trying to look where this get's the IRQ from for like 2 hours, but couldn't find it. The furthest I've gotten is this line

Any ideas guys?
[Galaxy 3 Android Development] prabhuthelegend:
Sorry, I am noob..but just googled related to it and i found some file in

arch/powerpc/include/asm/hw_irq.h

could it be any help ???

one more Reference :

http://lxr.free-electrons.com/ident?i=platform_get_irq
[Galaxy 3 Android Development] tom3q:
IMHO it's just another IRQ numbering on 3.4, but might be worth checking how are UART IRQs defined on S5P64x0, S5PC100 and S5PV210.
[Galaxy 3 Android Development] hillbeast:
@tom3q, how do you register a OneNAND device for MTD? I've added the partition table, and I've tried to use your Spica code as a reference, but I must be missing something because it doesn't show up with anything upon boot, not even an error. Is there something I need to add to FORCE MTD to find the partition table and associate it to the device?
[Galaxy 3 Android Development] prabhuthelegend:
Will this help by any chance :

http://lxr.free-electrons.com/source/drivers/mtd/onenand/onenand_sim.c
[Galaxy 3 Android Development] hillbeast:
Tada...

<6>Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
s3c24xx_serial_probe(c09706bc) 0
s3c24xx_serial_probe: initialising port c092e40c...
s3c24xx_serial_init_port: port=c092e42c, platdev=c09706bc
resource c090a700 (ec000000..ec000100)
port: map=ec000000, mem=f7000000, irq=74 (74,75), clock=1
s3c24xx_serial_probe: adding port
<6>s5pv210-uart.0: ttySAC0 at MMIO 0xec000000 (irq = 74) is a S3C6400/10
s3c24xx_serial_console_setup: co=c092e728 (1), 115200
s3c24xx_serial_probe(c090ccd4) 1
s3c24xx_serial_probe: initialising port c092e4d4...
s3c24xx_serial_init_port: port=c092e4f4, platdev=c090ccd4
resource c090a738 (ec000400..ec000500)
port: map=ec000400, mem=f7000400, irq=75 (75,76), clock=1
24xx_serial_probe: adding port
<6>s5pv210-uart.1: ttySAC1 at00[ 0.000000] Booting Linux on physical CPU 0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.4.0-rc6+ (hillbeast@kyorabuilder) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #Test Mon Jul 30 17:10:34 NZST 2012
[ 0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: APOLLO
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] CPU S5P6442 (id 0x36442000)
[ 0.000000] S3C24XX Clocks, Copyright 2004 Simtec Electronics
[ 0.000000] s5p6442_setup_clocks: clkdiv0 = 10100000
[ 0.000000] S5P6442: PLL settings, A=667000000, M=166000000, E=48000000
[ 0.000000] mout_apll: source is fout_apll (1), rate is 667000000
[ 0.000000] mout_mpll: source is fout_mpll (1), rate is 166000000
[ 0.000000] mout_epll: source is fout_epll (1), rate is 48000000
[ 0.000000] mout_arm: source is mout_apll (1), rate is 667000000
[ 0.000000] mout_d0: source is mout_mpll (1), rate is 166000000
[ 0.000000] mout_d0sync: source is mout_d0 (1), rate is 166000000
[ 0.000000] mout_d1: source is mout_mpll (1), rate is 166000000
[ 0.000000] mout_d1sync: source is mout_d1 (1), rate is 166000000
[ 0.000000] dout_a2m: source is fout_apll (1), rate is 667000000
[ 0.000000] dout_apll: source is mout_apll (1), rate is 667000000
[ 0.000000] hclkd1: source is mout_d1 (1), rate is 166000000
[ 0.000000] hclkd0: source is mout_d0 (1), rate is 166000000
[ 0.000000] pclkd0: source is mout_d0 (1), rate is 83000000
[ 0.000000] pclkd1: source is mout_d1 (1), rate is 83000000
[ 0.000000] S5P6442: HCLKD0=166000000, HCLKD1=166000000, PCLKD0=83000000, PCLKD1=83000000
[Galaxy 3 Android Development] Spitlebug:
Where does the 48mhz come from? Is that some kind of odd clock multiplier?

BTW, good work hillbeast and tom3q.
[Galaxy 3 Android Development] andreapier:
You forgot to mention moikop too... i think he made a huge work toom am i wrong?
[Galaxy 3 Android Development] bscraze:
No you're not :D
[Galaxy 3 Android Development] hillbeast:
That's for the audio subsystem.
[Galaxy 3 Android Development] hillbeast:
Right, so I am stuck again... this time it won't init. It wants to load the init binary but it just craps out and panics. I'll track down why it's not booting, but I'm pretty lost. It's confusing because I posted a log moikop made of init working before, but that was back in the old branch which I have since deprecated. Time to go through a diff...

On a lighter note, I updated it to kernel 3.4.5 from 3.4 rc6. Nothing special about that, it's just handy that we can get updates to the kernel with relatively no effort.

EDIT: Only thing I can see that can attribute to this is either the toolchain (as tom3q suggests, I'm downloading the latest CodeSourcery chain now) or the OneDRAM. I'll try both. If anyone has a brighter idea then let me know.
[Galaxy 3 Android Development] moikop:
...
[B]
run_init_process: /init
<3>fsr: version magic '2.6.32.9 mod_unload ARMv6 ' should be '3.4.5+ mod_unload
ARMv6 p2v8 '
<3>fsr_stl: version magic '2.6.32.9 mod_unload ARMv6 ' should be '3.4.5+ mod_unl
oad ARMv6 p2v8 '
<3>param: version magic '2.6.32.9 mod_unload ARMv6 ' should be '3.4.5+ mod_unloa
d ARMv6 p2v8 '
<3>rfs_glue: version magic '2.6.32.9 mod_unload ARMv6 ' should be '3.4.5+ mod_un
load ARMv6 p2v8 '
<3>rfs_fat: version magic '2.6.32.9 mod_unload ARMv6 ' should be '3.4.5+ mod_unl
oad ARMv6 p2v8 '
[/B]
<0>Kernel panic - not syncing: Attempted to kill init! exitcode=0x00008b00

Backtrace:
[<c0012cf0>] (dump_backtrace+0x0/0x10c) from [<c019b324>] (dump_stack+0x18/0x1c)

r6:c0a4c47c r5:c0a4c47c r4:e482e000 r3:00000200
[<c019b30c>] (dump_stack+0x0/0x1c) from [<c019b3b8>] (panic+0x90/0x1cc)
[<c019b328>] (panic+0x0/0x1cc) from [<c0022f14>] (do_exit+0x630/0x72c)
r3:e482e000 r2:e4830018 r1:00008b00 r0:c01ee868
r7:e482e000
[<c00228e4>] (do_exit+0x0/0x72c) from [<c0023284>] (do_group_exit+0x44/0xb8)
r7:000000f8
[<c0023240>] (do_group_exit+0x0/0xb8) from [<c0023310>] (sys_exit_group+0x18/0x2
0)
r7:000000f8 r6:00201fb7 r5:000dc928 r4:000dc94c
[<c00232f8>] (sys_exit_group+0x0/0x20) from [<c000f300>] (ret_fast_syscall+0x0/0
x30)

Apparently it was the initramfs. I'll send you the one I'm using...
[Galaxy 3 Android Development] tom3q:
You might also need a kernel patch for disabling hardware TLS (thread-local storage) on ARMv6, because Bionic supports only software TLS on ARMv6. I will link to respective commit in my spica-3.0 tree later.

EDIT: https://github.com/tom3q/spica-3.0/commit/37d3778436e4d129f11e03427f7c89af496b0cc2
[Galaxy 3 Android Development] moikop:
Just committed it, thanks :)
[Galaxy 3 Android Development] hillbeast:
Indeed you are correct. I used your initramfs and it worked. I'll now try extracting it and testing it one by one to find what went wrong and commit the basic initramfs.
[Galaxy 3 Android Development] bioniclizard:
Hi! Could you maybe tell us what that means overall? If you were to give a percentage to what you've achieved so far compared to how much there is left to do, what would that be? It's quite hard to understand how far from a usable kernel we are and some people may be convinced it's nearly usable. It's okay if you prefer not to say it, I just think people shouldn't get their hopes up since it's still in pretty early stages, and some may not be aware of that.

Thank you for all the great work, it's really inspiring to see you being such hard core developers. Sorry for the intrusion ;)
[Galaxy 3 Android Development] hillbeast:
We need to get the following working:

Battery

USB

WiFi

Bluetooth

SD card

OneNAND

Modem

GPS

Sensors (proximity and orientation)

Compass

Screen

Framebuffer

GPU

GPIO

I2C

Audio

SDIO for WiFi

Backlight

Buttons

Android

Once those are fixerd, then it will be working. We still have a long way to go, we just have it booting is all. Think of it like we have MS DOS and we need to get Windows working now. All we have is a keyboard connected to a CPU with a console right now.

EDIT: The current plan of attack is to get the OneNAND and the SD card working (either or, but preferably both) that way we can then store stuff on the SD card such as logs and such, and copy bulk information from the device back to the computer.

I cannot for the life of me figure out how OneNAND + MTD works, so I'm looking at the SD card and as far as I can tell most of it is working, it has the platform data and is attempting to start the SD cards up, but it can't find the clock source.

[ 3.634966] sdhci: Secure Digital Host Controller Interface driver
[ 3.641001] sdhci: Copyright(c) Pierre Ossman
[ 3.645549] s3c-sdhci s3c-sdhci.1: failed to get io clock
[ 3.650922] s3c-sdhci: probe of s3c-sdhci.1 failed with error -2
[ 3.657058] s3c-sdhci s3c-sdhci.2: failed to get io clock
[ 3.662469] s3c-sdhci: probe of s3c-sdhci.2 failed with error -2
[Galaxy 3 Android Development] tom3q:
You can also use one of my initramfs repositories initramfs-3.0 or initramfs_droidboot as a starting point. The former needs some cleaning and changes for G3, but the latter should be a good starting point for testing and debugging other drivers, as it's rather lightweight, while still having a rather complete version of busybox, adbd and recovery. Also it would add the advantage of not storing initramfs sources inside kernel repository, as it has an initramfs_list file listing all the files to be included in the initramfs and just this file has to be pointed in kernel config.
[Galaxy 3 Android Development] hillbeast:
The using an initramfs inside the kernel repo is only a temporary system. Once we start porting Android we can use the correct method. I put it in there to make sure everyone is on the same page.

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] boostcrap:
maybe you can use this patch for the sdhci http://www.spinics.net/lists/linux-samsung-soc/msg01010.html

btw good work
[Galaxy 3 Android Development] moikop:
Just a little update

[ 0.907677] Muxed OneNAND 512MB 1.8V 16-bit (0x50)
[ 0.907723] OneNAND version = 0x013e
[ 0.910580] Scanning device for bad blocks
[ 1.009510] OneNAND eraseblock 343 is an initial bad block
[ 1.480181] OneNAND eraseblock 2047 is an initial bad block
[ 1.483096] Creating 4 MTD partitions on "(null)":
[ 1.485034] 0x000000a00000-0x000001180000 : "kernel"
[ 1.492934] 0x000001180000-0x00000ed80000 : "system"
[ 1.498741] 0x00000ed80000-0x00001b800000 : "data"
[ 1.503593] 0x00001b800000-0x00001de00000 : "cache"

:)
[Galaxy 3 Android Development] hillbeast:
So it was an S5P like I originally thought... this processor is basically a Hummingbird with an ARMv6 core. I think we should proceed with that belief. Everything we've gotten going so far has used the Hummingbird drivers.

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] tom3q:
Well, AFAIK S5PC100 is also included in Hummingbird series and it contains the s3c-style OneNAND controller. In addition S5P6442 also contains some ancient IPs like FIMG-3DSE and FIMV 1.0, which come from S3C6410. This chip is simply a mix of several other chips. It's just a matter of identifying which parts of S5P6442 are taken from which chip.
[Galaxy 3 Android Development] hillbeast:
Yeah but they aren't going to pay licensing fees to the PowerVR for a good GPU. The rest of the chip seems like a Hummingbird PV210 to me.

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] tom3q:
I wouldn't make such assumptions. As you can see with OneNAND, despite using the same controller as S5PV210, it uses another IRQ pin, same as S5PC100. I would expect more differences like this.

Anyway, it doesn't really matter for us now, as we've got a separate arch added. It's just a matter of picking proper drivers and setting correct platform data.
[Galaxy 3 Android Development] hillbeast:
The next step now is deciding where to next. I think get GPIO and I2C working and then we can get the sub devices working.

I know the WiFi runs on SDIO so we may want to find where its trying to find the clock source.

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] tom3q:
I'd definitely say GPIO, as it's required for most of devices, along with WiFi.

This means two things, generic pin configuration support for GPIO of S5P6442 (including pin muxing and suspend/resume support) and platform-specific pin configuration for G3. For the former, compatible code should be already there and it just has to be configured properly: http://lxr.linux.no/#linux+v3.4.5/drivers/gpio/gpio-samsung.c . The latter will require identifying all the GPIO pins used on G3, most probably from the original kernel sources.
[Galaxy 3 Android Development] hillbeast:
Okay so MTD works for reading:

/ # dd if=/dev/block/mtdblock0 bs=1 count=100
*á*á*á*á*á*á*á*áê(olp*á*á áã*ãV4ï áÀ ãð!á
Gå100+0 records in
100+0 records out
100 bytes (100B) copied, 0.004981 seconds, 19.6KB/s
/ # dd if=/dev/block/mtdblock1 bs=1 count=100
FSR_STLÿÿÿÿþÿÿnR
R¤Ô

100+0 records in
100+0 records out
100 bytes (100B) copied, 0.004971 seconds, 19.6KB/s
/ # dd if=/dev/block/mtdblock2 bs=1 count=100
FSR_STLÿÿÿÿãÿÿÿ

(
Ã ÀJûgæÞ'*ÿ100+0 records in
100+0 records out
100 bytes (100B) copied, 0.004830 seconds, 20.2KB/s
/ # dd if=/dev/block/mtdblock2 bs=3 count=100
FSR_STLÿÿÿÿãÿÿÿ

(
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ100+0 records in
100+0 records out
300 bytes (300B) copied, 0.004548 seconds, 64.4KB/s
/ # dd if=/dev/block/mtdblock2 bs=4 count=100
FSR_STLÿÿÿÿãÿÿÿ

(
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ100+0 records in
100+0 records out
400 bytes (400B) copied, 0.004485 seconds, 87.1KB/s

But not for writing...

/ # dd if=/dev/zero of=/dev/block/mtdblock1 bs=1 count=100

[ 113.998042] onenand_wait: ECC error = 0xaaaa
[ 113.998096] onenand_write_ops_nolock: verify failed -74
100+0 records in
100+0 records out
100 bytes (100B) copied, 0.018687 seconds, 5.2KB/s

I've looked at the two registers it's looking at for ECC and they both look right, but the weird thing is that despite me telling it to only erase 100 bytes, it's clearly erased more:

/ # dd if=/dev/block/mtdblock1 bs=1 count=120
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ120+0 records in
120+0 records out
120 bytes (120B) copied, 0.005318 seconds, 22.0KB/s

Very strange... I'd almost think the write is doing too much hence the ECC error.
[Galaxy 3 Android Development] tom3q:
Don't use standard block write utilities for writing to NAND flash memories. There are dedicated tools available that can handle existing bad blocks (common in NAND flashes) and other errors and report them correctly, e.g. nandwrite.
[Galaxy 3 Android Development] Spitlebug:
Here's an interesting question:

How do you know the memory map is correct regarding the NAND blocks? Would it be pertinent to compare memory maps of the same media using a working kernel to see if it has mapped the bad blocks correctly?
[Galaxy 3 Android Development] tom3q:
What do you mean by memory map? Bad block mapping? If so, then there is no bad block mapping in the MTD subsystem (as opposed to FSR-BML), it can just detect a bad block and it has to be handled in higher layer, for example UBI or YAFFS2. This doesn't bother us anyway, as we're going to use such layer on G3, because we can't (and don't want to) get compatibility with FSR anyway (except limited BML support which is required to be able to flash.kernels from a running system and load baseband firmware, which can be avoided as well, depending on which design we choose).
[Galaxy 3 Android Development] Spitlebug:
Alright, thanks. :)
[Galaxy 3 Android Development] cdesai:
I played around with the kernel source, moved initramfs to another repository, and did some setup. :)

We're now using repo instead of git clone, more info at https://github.com/sg3/apollo_manifest

I'll improve the script later when i'm bored, but it does work for now.
[Galaxy 3 Android Development] tom3q:
OK, this will allow us to keep the kernel repository clean from things that don't belong to the kernel. One minor thing, though, AFAIK it isn't necessary to call make modules after calling make.
[Galaxy 3 Android Development] moikop:
Guys, any idea why NO initramfs will work with me?

The one in the repo just panics (init tried to kill himself), initramfs-3.0 and droidboot (with a couple of tweaks) give me this:

[ 6.010012] init: Timed out waiting for /dev/.coldboot_done
[ 6.011665] init: Unable to open persistent property directory /data/property
errno: 2
[ 6.018077] init: Failed to open socket 'property_service': Function not impl
emented
[ 6.025923] init: init startup failure
[ 6.030009] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[Galaxy 3 Android Development] tom3q:
Something is wrong with socket support and init bails out because it can't open 'property_service' socket. Maybe you're missing something in kernel config?
[Galaxy 3 Android Development] moikop:
You were right. defconfig was missing a couple of things. I'm using driodboot initramfs now. Thank you!
[Galaxy 3 Android Development] andreapier:
I'm unable to build the kernel.

I used the repo method that cdesai suggested to get the git projects.

The error i get is:

Inconsistent kallsyms data
This is a bug - please report about it
Try make KALLSYMS_EXTRA_PASS=1 as a workaround
make[1]: *** [vmlinux] Errore 1
make: *** [sub-make] Errore 2
make: Leaving directory `/home/andrea/git/kernel'

I found this link (which funnily is by tom3q) so i don't know what it might be... i have the toolchain installed i think because compilation starts correctly.

Can you give some advise please?

PS: should i write here compiler version?
[Galaxy 3 Android Development] tom3q:
There is a strange bug somewhere in Kbuild (or maybe even in used buildtools, like GNU Make) that can't get tracked since long time already. Usually a make clean (or distclean) and rebuild helps, but if it's not the case then the workaround with make KALLSYMS_EXTRA_PASS=1 should work.
[Galaxy 3 Android Development] :
Hmmm
[Galaxy 3 Android Development] andreapier:
I can confirm that make KALLSYMS_EXTRA_PASS=1 fix the problem.

I didn't try make clean because the error message suggested to use the other option.

Thanks
[Galaxy 3 Android Development] VinC0deur:
Any news? No Activity since 3 days (Cf Github). You are blocked somewhere?
[Galaxy 3 Android Development] m1trand1r:
wutwuzthatagain?lol:p

Dev's have a life to live too....mate;)

consider this in your next post, please;):cowboy:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy 3 Android Development] hillbeast:
The way I prioritise my life from highest to lowest: my personal life, my family, my housework, my job, then developing and my YouTube work. Currently my department manager is having problems in their personal life and I have to fill in for them, and I'm working 6 days a week doing 9 hours a day. I think getting a new kernel on my phone isn't really a priority.

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] VinC0deur:
Yes I know, like everyone! Also, this is very nice for us, Hillbeast, moikop, Tom3q and Cdsei works very hard for our G3 ! I simply wondering if they had any problems in the development :)

@hillbeast: Yes I totally understand! Good luck to you for your job!
[Galaxy 3 Android Development] m1trand1r:
well....if there were no problems with kernel itself....what do you think it'd be?....i think we would have a fully working kernel then..,if problems wouldnt exist:p...lol...

@to all: I am sorry for :silly: OT...it ends here:cowboy:

Cheers;)

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy 3 Android Development] pxrave:
do you think this kernel is working in q1 2013 @ alpha?
[Galaxy 3 Android Development] cecenac:
why are you so boring?

If I moderated this forums (and i believe noone does) all of the spam and etas like this would be deleted the day they got written, but unfortunatley, our moderator probably doesn't even open g3 pages..
[Galaxy 3 Android Development] MicroGeek:
He seems new to the forums so please don't be so aggressive towards him. Also, moderators have a few forums to moderate so they might miss some threads out but if you message them they will reply quickly and sort out your problems.
[Galaxy 3 Android Development] bscraze:
Micro geek is absolutely correct. U have to tone down and relax. Moderators(like pg101) moderates more than 10 forums and I suppose also checks his own phone's forum to flash his phone. Therefore they do not have time to go through every single thread and every single post. If you're unhappy, report the post or simply pm the moderator with the link to the thread you want cleaned.
[Galaxy 3 Android Development] cecenac:
ok, maybe I am a bit harsh, but check the last lat 7-5 pages (devs discusing and using their thread to make the kernel) and then the last 2, guys like this spamming for no reason, polluting the thread. And please don't respond anymore to this messages and let the guys work here. People open this thread to check develops, not to look at other people spam and eta asks..
[Galaxy 3 Android Development] hillbeast:
No bickering guys. XDA is a happy place. If you want to discuss development then post here. If you are asking questions, ask in the Q&A section. If you are asking ETAs then the answer will always be 'we don't know'.

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] toms95:
http://xdaforums.com/showthread.php?p=30120479 for everybody who wants to discuss about kernel 3.4.x port!
[Galaxy 3 Android Development] GadgetCheck:
What is hapenning here???

Xda is a place to be kept clean and your egos to be keept at ur home... dont bring it in public view in a public forum..

If you have a problem better pm the person dont get into a all our warfare on the forum..

Warning to every one here involved in poluting the thread...

If i find more offtopic here the thread will be closed and infraction/Bans shal flow.
[Galaxy 3 Android Development] hillbeast:
Excuse me, but I would rather you don't close my thread because of other people. Especially considering this is amongst the two greatest developments for our phone...

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] m1trand1r:
well....i think he'll ban someone first if they wont obey rules he posted....it's not your thread fault....it's a big leap to a better galaxy 3 phone....

Keep it up;)...I want to try this kernel on my g3 too...:D...

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9
[Galaxy 3 Android Development] hillbeast:
I know I moan about off topic but I just have to off topic...

I was very naughty today... I ordered my Nexus 7.

Okay, enough OT.