yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] CroNk3r:
Just be patient, They will do it as fast as they can..

You can't expect from developers to work on this project 0/24 becouse they have no profit from this (except donations) and they must do something for living and they must take a rest like other ppls...

Think in this way- if you are developer would you do few hours a day for free, don't think so...

You should be thankfull for their work...
[Galaxy 3 Android Development] andreapier:
... I will not start a fight for respect to devs but still I'm gonna tell you that it is not your duty to answer questions made to devs.

I didn't ask for eta, nor bugged anyone. I just expressed my will for this project and asked if something is stopping progresses.

Do not answer taking this personally, I just asked a question to dev. They can answer "we need time" by themselves if they want.

However I think it is important to dev to know that there are some people interested in non "hot" topics (like ics).
[Galaxy 3 Android Development] hillbeast:
I havent had enough time to do some solid coding on it so there is still no progress. I may need to call the other developers such as apollo and marcellusbe to give a hand. Even if i can get UART I can get the rest figured out. Thats the big hurdle.

Don't worry, I don't feel he was pushing me, bit thanks for sticking up for me, even if I didn't need it, it still reminds me there are people waiting for this.
[Galaxy 3 Android Development] cecenac:
posting to let you know that we're excited about this kernel, take your time, summer is coming, there should be a lot of boring days when you can do some coding.

and here is something i don't know if you developers are aware of: In February 2012 Firmware update for our phone was released in Spain (froyo 2.2 ofc), i don't know is it any help since this kernel is getting rid of samsung code, but maybe there is something useful in it ?

http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I5800&r=1#modelsa
[Galaxy 3 Android Development] hillbeast:
Well for me winter is coming. Damned southern hemisphere. We had a -2C frost yesterday and I can tell it's going to get colder.

I don't think the new firmware will be of an help. The kernel will just be the same old Samsung broken junk, and as tom3q has stated it's not worth it extracting components from the Samsung kernel. If we start with something broken, we'll end up with something broken.
[Galaxy 3 Android Development] mitrjoshi:
good man
[Galaxy 3 Android Development] Spitlebug:
Oh noes! -2° C would be a godsend. Here in AfCanadaStan things get very cold.

Sent from my GT-I5800
[Galaxy 3 Android Development] simbawimba:
well good time to hibernate inside with the code :D

i think there are quite a few people waiting for this project to be a success because then we have the possibility of fully working ICS and maybe it can make our phone able to have the next jelly bean update.

good luck
[Galaxy 3 Android Development] hillbeast:
Well I'm not saying this is the lowest temperatures in the world, just saying that it's getting cold here now.

Also a lot of people keep asking me why we need kernel 3.x.

This is why: Android 4.0 was built for Linux Kernel 3.0.1. It wasn't built for the old kernels. If we want it to work properly, we need to be using what Google specified it should be built for.
[Galaxy 3 Android Development] z3c0:
I totally agree that summer winter autumn is the perfect time for coding, followed by whatever comes next :D
[Galaxy 3 Android Development] ajay.d96:
let me add one more feature of kernel 3.0.1

it has the drivers needed for usb tethering, wifi tethering, offline charging in steps, even more

..
[Galaxy 3 Android Development] Spitlebug:
WiFi tethering without the need for something lik ES File Explorer is nice.

Sent from my GT-I5800
[Galaxy 3 Android Development] hillbeast:
Yeah. Android changed it's driver interfaces quite dramatically between 2.3 and 4.0. Let's just blame Honeycomb!!!
[Galaxy 3 Android Development] Darius_AWS:
did you give a try on our device ?
[Galaxy 3 Android Development] hillbeast:
I haven't gotten any output from UART when I try it.
[Galaxy 3 Android Development] RohMish:
I am a Vodafone IN user and have no problem with the modem.bin of European firmwares. What is the fault? (I hear it for first time that there is any problem).

Actually, the modem.bin i had when i bought the phone was more glitchy with frequent signal losses.

(I once had a problem in 2.2 Froyo (Kyrillos' rom to be exact) and it was not his fault, and he too had experianced it. I don't know if it was a modem.bin problem.

Is the source code available?

And when samsung said that the other two (s3c64xx or s5p-64x0) are similar?

I will not buy a samsung phone and opt for SONY or hTC if they did not release the SC and DS

I checked it and thai is the same thing with more samsung junk.

(Actually, i cant find any differences, what was it, a update to update youtube apk?)

Will data management on ICS work on this kernel, because i remembered that someone said that the fault is of kernel, and that the BT fault is also partly related to it?

If Kernel 3.0 is developed and incorporated in GB alpha 8.1, i think it will reach so near that it will be one step back from beta.
[Galaxy 3 Android Development] D@rekills4:
Its a bug you face only if your Data Network (EDGE for me) is active and then you get a call....

Most users who have confirmed it in that thread are Vodafone users....

I face this problem on every single ROM.

I have to flash "I5801DDJP2" modem after every ROM I flash having a European modem.
[Galaxy 3 Android Development] RohMish:
I too have data active all the time and never got any problem with receiving phone call from 2.1 Eclair to (2.2,2.3) 4.0.3 Ice Cream Sandwich.
[Galaxy 3 Android Development] hillbeast:
Well to be honest out of all the big phone manufacturers, Samsung is pretty much the best for open development. HTC are terrible. They harp on about releasing source codes, but then they lock the bootloaders and choose Qualcomm chipsets, the WORST for providing datasheets, because they release NONE.

The two best SoC manufacturers are TI and Samsung, and Samsung is on the edge about it. They release them (for the popular SoCs) but a lot of the time they are incomplete, but you can kind of use them. If you want development, then stick with Samsung, but look for a phone with Exynos or the OMAP (ie GS2 or GNex).
[Galaxy 3 Android Development] z3c0:
Uh-oh, does this mean there's a chance that this can't be done at all or is it rather just a matter of trying different things?
[Galaxy 3 Android Development] hillbeast:
It just means I haven't got something right. Linux can be ported to anything.
[Galaxy 3 Android Development] D@rekills4:
Dunno....

Must be a problem with only a few phones.....
[Galaxy 3 Android Development] radek.god:
What ? It means If I will flash your new kernel at future, then I will NEVER EVER be able to get original froyo ROMs back thru ODIN? Or I will have to use different way to get original one back and by this step I will restore ODIN flash functionality too :-o

I hope there will be no reason to return to older crappy Froyo, but it will be not good if totally impossible.I am affrtaid of permanent damage where only service should help :(

At this moment ICS is unusable and GB has few bugs what make it unusable for daily use (specially GPS and BT ) so I am again on stock JPS now :(, but I am happy I still have the downgrade possibility
[Galaxy 3 Android Development] tom3q:
ODIN will not work for flashing new ROMs (everything will be flashed from recovery), but it will be able to flash old ROMs based on the old kernel and it will be the only way to do so on top of a new ROM (i.e. reformat the memory to the old format).
[Galaxy 3 Android Development] hillbeast:
No sorry I worded that badly. I mean you won't be able to flash ROMs with ODIN while using kernel 3.x. If you go back then you can use it.
[Galaxy 3 Android Development] f_ck:
Can i ask, if allowed, whats the progress of the port and a rough estimation of the time remaining before we can use it on our phone????
[Galaxy 3 Android Development] hillbeast:
No ETA, and I haven't made any progress on this as I have been super busy.
[Galaxy 3 Android Development] pmanian:
@hillbeast

Check this out.. http://xdaforums.com/showthread.php?t=1316501

Whether it will help us in any way. Sorry if it is of no use.
[Galaxy 3 Android Development] cdesai:
Nope, it's for the exynos 4120, which is nowhere close to the s5p6442 in our apollo.
[Galaxy 3 Android Development] tom3q:
It's not that far either. All the Samsung's SoCs are similar, as I already said some time ago. The differences are mostly in memory map, interrupts, pin configurations, feature sets and versions (and presence) of particular IPs. However, the manual in the package is somewhat limited. I have seen full datasheets for S5PC100, S5PC110 and S5PV210 in the net. (I won't say that I have them, as it might not be fully legal, at least in some countries, but careful search with Google should reveal them.)
[Galaxy 3 Android Development] cdesai:
Well they can be found in the Galaxy S Hack Pack, someone posted em on this forum and AdamOutler included it in the hack pack
[Galaxy 3 Android Development] tom3q:
Indeed, that's the one I've seen for S5PC110.
[Galaxy 3 Android Development] RohMish:
Hardware related?
[Galaxy 3 Android Development] pmanian:
Request all the developers to contribute a little so that at least hillbeast can kickoff the development. I think hillbeast stuck at getting the output from UART. All developers putting little little effort would make a miracle. Please help G3 users.
[Galaxy 3 Android Development] z3c0:
So... you think you'll get some useful output from UART eventually?

Is it a guessing game which wires to plug in what places, or which boot parameters to enable in order to get into the right debug mode?
[Galaxy 3 Android Development] hillbeast:
Well UART is already working on the phone itself. It was really useful for getting 2-stage init to work.

I now just need to get it to work in the new kernel.
[Galaxy 3 Android Development] D@rekills4:
Probably....

Cause I don't see why a software would cause this.
[Galaxy 3 Android Development] austin266:
@mark

Any progress mate...

UNNAMED ROM -ECLIAR

CUSTOM KERNEL
[Galaxy 3 Android Development] hillbeast:
Sorry nothing to report. Been working on other projects and just relaxing in general over the last few weeks.
[Galaxy 3 Android Development] PersianSphinx:
?

So would this fix the seriously annoying lags and slow interface in Google Play? Or will it make the general interface smooth enough, like your S2 (or just smooth enough so it is not annoying)?
[Galaxy 3 Android Development] sharukins:
probably no
[Galaxy 3 Android Development] hillbeast:
Well I don't know really. The phone is pretty much already at it's limit in terms of performance. It might help, it might not. I don't know.
[Galaxy 3 Android Development] z3c0:
only one way to find out :)

I don't even care whether performance can be improved much. ICS brings a lot of enhancements on its own and already feels much faster than anything I had before.

For me this is rather about getting back the missing features, most importantly the camera+preview and the wifi location finder.
[Galaxy 3 Android Development] Uz986:
does 3.x kernel really improve graphics of phone.
[Galaxy 3 Android Development] sharukins:
no, the graphics power might get a little better with tom3q's openFIMG driver as soon as it's finished, but the G3 won't become a gaming machine with that and it's still far from finished
[Galaxy 3 Android Development] tom3q:
Well, not that far, it just needs an implementation of lighting and some more love for texturing and should be able to run correctly most of games.

As for the kernel, it should bring some improvement in I/O area thanks to removing FSR and using a filesystem designed exclusively for flash memories.

I'm not sure about other fields as I don't know the exact kernel configuration used currently. Does current kernel use preemption and SLUB allocator?
[Galaxy 3 Android Development] kyrillos13:
I know for sure that the current kernel doesnt use preemtion. I dont have any info for SLUB allocator.
[Galaxy 3 Android Development] tom3q:
So at least the new kernel will give improved responsiveness thanks to preemption, which I believe is not enabled on current kernel for compatibility with Samsung drivers (at least FSR).
[Galaxy 3 Android Development] kyrillos13:
Yes, i recall that Marcellusbe tried to enable preemtion but there were incompatibilities with the samsung drivers. Anyway, i hope that we will have an alpha build of 3.X kernel soon.
[Galaxy 3 Android Development] nishant_713:
Oh man, that's cool.

PS. How about the Android mainlining in kernel 3.3. Will ut be of any help for us one Google implements that kernel ???
[Galaxy 3 Android Development] hillbeast:
I got the phone to boot with preemption and it was noticeably faster, but some important components weren't working right, namely the battery driver and the headset driver.
[Galaxy 3 Android Development] rajputrajat:
My phone is very happy, for some reason... :-)
[Galaxy 3 Android Development] moikop:
and I got it running with bfs too. even though fsr wasn't working, it was amasing.

I really think if we get this working, it will be better.
[Galaxy 3 Android Development] Shree_Jamdar:
I don't like to populate threads, unless I am contributing to something, but for this, I really have to say Thanks!! :) this is awesome!
[Galaxy 3 Android Development] nishant_713:
All this in the current Samsung kernel or the 3.x kernel???
[Galaxy 3 Android Development] nishant_713:
All this in current Samsung kernel or the 3.X kernel ???
[Galaxy 3 Android Development] prabhuthelegend:
I think this is for Samsung kernel..

Once pre emption is working fine, it will be a boost to kernel 3 porting..this is what Hillbeast said which I remember.. :)
[Galaxy 3 Android Development] eeshlikhith:
Its the 3.x kernel. They already mentioned preemption is not supported by samsung libs
[Galaxy 3 Android Development] nishant_713:
You mean that the devs have already got kernel 3.x booting on our phone???
[Galaxy 3 Android Development] cdesai:
Samsung

Preemption will make the phone much faster, rather then being a boost to porting.

No and yes.Running Android from sdcard without using the only Samsung **** being done currently (FSR modules), that's how it works.

Nope, a lot of work to do.
[Galaxy 3 Android Development] erikkubica:
Hi there,

I am interested to try kernel 3 on my phone but I dont know how to do it. I have windows and linux too. Please write me step by step instuctions. how to build how to flash, roms that work with kernel 3..........

EDIT: sorry i missed the last post, I cant boot it :-) or is it possible now?
[Galaxy 3 Android Development] tom3q:
It has to be ported first, including rewriting some of the drivers and debugging any possible problems. So this is a purely development project at the moment, waiting for us, developers to find some time and start some serious work on it.
[Galaxy 3 Android Development] CroNk3r:
Will this kernel be able to run older android versions (froyo and gb) or just ics and jb?
[Galaxy 3 Android Development] tom3q:
Froyo - no, Gingerbread - possibly, but a new ROM will have to be compiled, using a configuration compatible with the new kernel.
[Galaxy 3 Android Development] devilgod18:
please try to add call recording function...i heard it is blocked by samsung and can be unlocked by new kernal
[Galaxy 3 Android Development] prabhuthelegend:
So once the kernel 3 is ported, all the features that are working currently in ICS needs to be modified?
[Galaxy 3 Android Development] CroNk3r:
lol, kernel is not even developed and you are already asking for some additional features:silly:

I think so...
[Galaxy 3 Android Development] MmegaMac:
I obtain this error:

mathieu@mathieu-laptop:~/kernel-3.0$ make apollo_defconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/lex.zconf.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
***
*** Can't find default configuration "arch/x86/configs/apollo_defconfig"!
***
make[1]: *** [apollo_defconfig] Erreur 1
make: *** [apollo_defconfig] Erreur 2
[Galaxy 3 Android Development] hillbeast:
Please read the first page. I have answered this already.

I have gone over this already: it is illegal in my country so therefore no.

Need to specify arch=ARM

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] MmegaMac:
I have change in Makefile to

ARCH	?= arm

and always the same error :

make apollo_defconfig
***
*** Can't find default configuration "arch/arm/configs/apollo_defconfig"!
***
make[1]: *** [apollo_defconfig] Erreur 1
make: *** [apollo_defconfig] Erreur 2

EDIT : SOLVED !
[Galaxy 3 Android Development] hillbeast:
:= not ?=

10 cchars
[Galaxy 3 Android Development] devilgod18:
Not in every country it is illegeal..and when it comes to call recording or something else why ppl think always illegal point of view..i have part time job of telemarketer so i usually record calls for that traing purpose...and mostly to record the voice of the girl I love so i can save it forever...I understand so i ll force you to create this but i will be seriously happy by this if you will help me...Sorry Hillbeast and others if i sound stupid Guys :(
[Galaxy 3 Android Development] hillbeast:
I know other countries it is illegal, but the fact of the matter is that in mine it IS illegal, therefore it is illegal for me to create the system for doing so. I am not going to risk legal battles over my development, considering I make no money from this whatsoever, and it's a simple hobby. I also have no purpose for such a feature so therefore I am going to break the law for the sake of something I won't get any benefit from, or any use for.

Please try to understand my point of view on this. I have already had this discussion multiple times. If you want call recording, then you will need to ask someone else to do this.

Also, note to everyone, don't ask for features in this kernel. This kernel is going to be a new stock kernel. It's going to be the bare basics needed to run the kernel. Once this is running fine, then I will encourage kernel developers (if any still remain on this phone) to release kernels with OC, or compcache or whatever.
[Galaxy 3 Android Development] hillbeast:
Well considering the code doesn't work yet... of course it won't compile right.

And what repo are you using? We aren't using mach-s5p6442 anymore. It's going to use mach-s5p64x0.
[Galaxy 3 Android Development] MmegaMac:
Ok I am going to try with mach-s5p64x0.

I use the repo https://github.com/sg3/android_kernel_samsung_apollo (branch apollo-3.0)
[Galaxy 3 Android Development] hasjee:
There are both free and paid app's in the playstore, Just type in call record et voila. No need to bother a dev imho with stuff you can get from the playstore.
[Galaxy 3 Android Development] TheCreat:
That doesn't work just because there is an app. Call recording needs to be enabled in the kernel. Otherwise it can just record a call by using the speaker and recording both parties with the Mic. What he was asking for was support to record both internally (and in good quality).

Please stop commenting on things you know nothing about...

But I agree that we shouldn't bother Hillbeast with this. Especially since he has already answered this request (and said no). It's also in a much too early stage of development to even think about this stuff. Just let the devs do their thing in peace!

Swyped on my Galaxy 3
[Galaxy 3 Android Development] hillbeast:
If people badly need to record their calls, then use a tape recorder.
[Galaxy 3 Android Development] nishant_713:
No dev stuff here... Only feature requests... Poor old g3. I fear this dream project would never be completed :( Only if i could hear from hillbeast that he got it booting..... But probably it's a long way to go....
[Galaxy 3 Android Development] RaymanFX:
This is not quite right.

Rom support and such is pending on some init files in the ramdisk.

We can add hybrid support for all known roms if we get the kernel to work halfways properly first.

And no, no new rom will need to be compiled. As I said, just a ramdisk is needed to be created. I have such a ramdisk. But I'm currently busy developing for the transformer, other than that, I have no UART, so I think I am not able to help much to get the kernel working. I could just check the code and make the device drivers work, with a huge hassle.

But for now, the Transformer's 3.1 kernel development keeps me busy. However, Hillbeast might contact me if he needed help with some driver code, e.g. the gauge driver for the battery meter - this should be pretty easy.
[Galaxy 3 Android Development] tom3q:
Please don't talk about something you don't have an idea about...

New kernel will require ROMs to be compiled with proper settings compatible with it and with different hardware support libraries compatible with new drivers.
[Galaxy 3 Android Development] RaymanFX:
And this ain't correct either.

Kernels need so be compiled so they are compatible with Roms, not vice versa.

I actually have an idea of what I am talking about, at least my jelly bean port works, and guess what,only changes needed where made in the kernel.

But it's okay, so then move on on your own if you think you are the alltime master.
[Galaxy 3 Android Development] tom3q:
Well, if you want to run a ROM designed for the old 2.6.32 kernel with all the poor code, needing all the workarounds, without any changes on a clean, close-to-mainline 3.4 kernel, then I wish you good luck.

And you are wrong with the statement that kernels should be compiled for ROMs. This way you wouldn't be able to add any innovative changes to the kernel, because they would break compatibility with existing low level interfaces in the userspace. This kind of policy has its advantages too, but you can see all its disadvantages in Windows and this isn't definitely the policy used by Linux environment. In Linux, both the kernel space and the userspace evolve continuously to improve things.
[Galaxy 3 Android Development] hillbeast:
That would be because Jellybean is similar to Ice Cream Sandwich and requires little changes only in the init.rc. Samsung use proprietary drivers in their ROMs and they also use their useless FIMG drivers that will be expecting the old kernel interface and the effort involved in adding support for this will just break the kernel.

Don't go around knocking tom3q saying he doesn't know anything because he has clearly gone through this before with other people considering her ported kernel 3.0 to the Spica.

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] cdesai:
^What he said.

I'm using a jellybean kernel on CM9, and it works just fine.

Only minor changes were needed in the ramdisk to get it booting (init.trace, new file init.trace.rc)

That an it booted.

Also @rayman this isn't the way to talk.

Be polite.
[Galaxy 3 Android Development] RaymanFX:
I don't intended to knock anyone, he did get me wrong for that. Yes,I think we're at a point where we can't get to the same opinion, so I will stop arguing.

Anyways, could someone (hillbeast) provide a list which drivers you use in the Kernel ? (Gauge, Touchscreen, audio, graphics, etc) ..?
[Galaxy 3 Android Development] tom3q:
Neither did I. Sorry if my post sounded offending.

Well, opinions are opinions, but facts are facts. Considering what is this project about, what I'm saying is perfectly fine. This isn't just a kernel version bump by merging upstream changes, but rather a complete platform re-bring-up.

If you read the first post you will find that the project is about to get rid of most of the improper old code from Samsung and replace it with things done properly, so many interfaces will change to something completely different (although it's going to be a change for better - from proprietary interfaces, like bml/stl to standard ones mtd/ubi - and Samsung is here to be blamed for ignoring existing standards). Considering this, there is simply no way to maintain direct compatibility with existing ROMs.