yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] o0Arthas0o:
Waiting for the good news.I think hillbeast will do the best.And I like his avatar,:D
[Samsung Galaxy SL i9003] vishal24387:
@ hillbeast

I know that u are not able to get uart out while uncompressing kernel which is most imp paet of development. Galaxy S user now have kernel 3.0 & they also achieved it using uart method (I think). So they must have also faced same problems in the intial stage like we are fcing now a days.

So I think u should contact codeworkx. He is one of the best & top developer of galaxy S. Also he has our device :) May be he can give you an idea regarding how ro get uart output while decompressing kernel.

Please ignore my post if it is not helpful or not important :)
[Samsung Galaxy SL i9003] simmer14:
hmm...

i know that codeworkx is a busy fellow and i hav'nt seen him in i9003 forum for quite a while now..

@ vishal why don't you pm him and explain the situation ?
[Samsung Galaxy SL i9003] vishal24387:
I would have pm him already. But we all know how much strict & busy codeqorkx is. He will not entertain me at all. If hillbeast contact him then hill beast can explain his problem in detail to him more technically :)
[Samsung Galaxy SL i9003] hillbeast:
I can try, but I make no promises he can help. He's working on CM10 for the S2 and S3.

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] loSconosciuto:
@hillbeast

If I understood correctly you are currently using a stock ROM because you want to know better the device.

I know that you are currently using a Gingerbread ROM. Do you think it would make any difference using a Froyo ROM? Our phone came with it and we all know that Samsung broke some things in the upgrade (sync/push not working, unstable bluetooth connections, unstable wifi connections). So I tought that maybe they did something bad to the UART drivers too and that maybe you can get what you need with Froyo.

However I don't know if it's a stupid idea or if starting over with another kernel requires too much effort and you are very close with the resolution of this problem.

In any case, thank you very much for your work.
[Samsung Galaxy SL i9003] hillbeast:
Nah Gingerbread is fine. I mainly just needed it because ICS was being odd with UART and fbcon

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] supergaijin:
please add this to the FAQ:

Q: "lg optimus black has same board and configuration. will this help with the development of any ROM/kernel for the i9003?"

A: "Looking at the board of the optimus, no its certainly not the same. Not even close. Where we have a OneNAND and an eMMC, the Black has a NAND, perhaps an eMMC. The layout of the board may not even be the same. Sure the components may be similar, but so are the specs of a Toyota Celica and a Lotus Exige."

source: Hillbeast

http://xdaforums.com/showpost.php?p=28781890&postcount=135
[Samsung Galaxy SL i9003] Skander1998:
Will be added when i have time, working on my first ROM :)

I will also add latest news.

Thanks.
[Samsung Galaxy SL i9003] bscraze:
Sorry for the OT but... Good luck with your rom, hope it'll be a real beast :)
[Samsung Galaxy SL i9003] vishal24387:
@ hillbeast

Today u had said that u got a way of dual booting. I want to ask u that is it possible to have dual boot rom like sgs2 have (stock rom and aosp rom)???
[Samsung Galaxy SL i9003] Impastik:
@ hillbeast,

for the problem of the UART output, I noticed that the file '/drivers/switch/switch_sio.c' PARAM_CONSOLE_MODE there is a variable that is not defined, this does not portions of code that could possibly serve.

The file '/arch/arm/mach-omap2/include/mach/sec_param.h' defines a number of settings

differences between sources in the file '/arch/arm/plat-omap/include/plat/omap-serial.h' line 33

I9003: #define OMAP_SERIAL_NAME	"ttyS"

OmapZoom: #define OMAP_SERIAL_NAME	"ttyO"

I hope it works.

thanks for the work you're doing!
[Samsung Galaxy SL i9003] hillbeast:
It's possible but the current method that I thought of was highly theoretical. It assumes people have UART and a computer handy to input the instructions to tell it to boot the recovery partition. If someone could create a new Sbl (perhaps instead use u-boot), then it could be possible to do it.

I don't see u-boot being too difficult on this device, u-boot already supports the OMAP3630, and OneNAND, it's just a matter of putting in the right settings and compiling.

The switch_sio.c I am pretty sure is for selecting which processor has control over the UART, the OMAP or the modem. Seeing I already have this set both by the bootloader (blindly typing setenv SWITCH_SEL 6543 works) and with the sys calls in the working kernel, it isn't much help right now, but I will need to implement this in the kernel later, however the way the UART switch works, it won't get switched back unless you tell it to switch between the two. It isn't something that is needed this early in boot.

I'm looking through sec_param.h as I speak to see if I missed anything in there.

I have also noticed that it is now ttyO instead of ttyS and changed it accordingly.
[Samsung Galaxy SL i9003] hillbeast:
Oh okay, yeah sec_param.h is just for defining the default param values for param.blk. In laymans speak, it's just like telling the kernel how to reset the CMOS.

Actually looking at it tells me that it's got a lot of wrong values, for example 'ttySAC2' which doesn't exist on this phone... Thanks Samsung.
[Samsung Galaxy SL i9003] chkneo:
Thanks

@hillbeast

Can you please checkout CM10 too. Becuase if you build kernel 3.0 and on top cm10 then it will be the ultimate build for i9003.

Thanks a lot for you and @dhiru for the work. I am very happy with dhiru's cm9.
[Samsung Galaxy SL i9003] serhiy333:
Sorry for flood,but we have booting phone,some result))):good:
[Samsung Galaxy SL i9003] supergaijin:
have you read the purpose of these threads? it WILL be for things like CM10, but first hillbeast has to make the kernel work before any modifications can be made. have more patience, and read some more about this while waiting ;)
[Samsung Galaxy SL i9003] coolpix90:
is it a question or what?
[Samsung Galaxy SL i9003] hillbeast:
I'm not really an Android developer. Sure, I've made custom ROMs before, but I'm not that great at it. I'll leave Dhiru to handle Android while I work on the kernel.

Wait, you got it booting?
[Samsung Galaxy SL i9003] luiseteyo:
what? did it boot?? :O
[Samsung Galaxy SL i9003] ale210:
luis, i think ))) = ??? hehehe
[Samsung Galaxy SL i9003] ollivong:
Can anyone say how much time it takes with the Kerne?
[Samsung Galaxy SL i9003] bscraze:
Probably when people stop asking for etas
[Samsung Galaxy SL i9003] hillbeast:
Line 2 of the first page of the development thread. Read it. NOBODY KNOWS HOW LONG IT WILL TAKE.

There will be a slight delay with SL development over the next week as we have made a breakthrough on the Galaxy 3 and I now have kernel 3.4 starting to boot far enough in for it to panic and give me detailed error information. This is the stage I wish to get the SL to.
[Samsung Galaxy SL i9003] Impastik:
@hillbeast,

Try to recreate 'normalboot.img" with one of these commands:

mkbootimg --base 0x10000000 --pagesize 4096 --board latona --cmdline 'console=ttyS2,115200n8' --kernel <kernel> --ramdisk <ramdisk> -o normalboot.img

or

mkbootimg --base 0x10000000 --pagesize 4096 --board latona --cmdline 'console=ttyO2,115200n8' --kernel <kernel> --ramdisk <ramdisk> -o normalboot.img

in the cmdline line you could add

no_console_suspend=1

in the kernel can replace the malicious code for samsung

File: arch/arm/plat-omap/include/plat/uncompress.h

Line 148 - 158

replace with

DEBUG_LL_OMAP3(3, latona);

I don't have a level converter to convert the UART lines to USB and I'm sorry if I waste time.

sorry
[Samsung Galaxy SL i9003] luiseteyo:
trying to help is never a waste of time. Thank u man
[Samsung Galaxy SL i9003] hillbeast:
Thanks for the advice. It looked promising, but still no dice. I'm going to make a post in the development thread about UART in a few moments.
[Samsung Galaxy SL i9003] xGiox:
this is not the request just i question,today i was looking for screen prices,and i found out that galaxy s one is rather cheap,so my question is,on the first place would it be possible to replace amoled for our screen,they are same size 4 inch,but still i have no idea are connectors and rest of stuff same.second would it be possible to use galaxy s screen driver in stead of our in kernel 3 to make it compatible with our phone,or it would require more kernel modifications. question is for hillabeast as he has most exp with our kernel.
[Samsung Galaxy SL i9003] vishal24387:
obviously NOT. Every phone's hw is specifically designed for it. U cant just replace it like a memory card.
[Samsung Galaxy SL i9003] iAmBalvinder:
obviously not.

It's a logic, not to be asked from devs. There's a bit of difference between the aspect ratio in both the screen(not pixel wise but size wise a minute difference). The screen guard of galaxy s doesn't fit on galaxy sl.

The screen fitting is beyond question. :D
[Samsung Galaxy SL i9003] hillbeast:
The difference between these two phones is deeper than just the display. The entire phone is different, even the casing is slightly different. Replacing the screen would be a painful and tedious process and who wants to read in the guide to install software 'go on eBay, buy a GS screen and fit it'. Best to get things going with what we have.
[Samsung Galaxy SL i9003] AmmarGitham:
Don't know if it helps... But I found this:

http://processors.wiki.ti.com/index.php/Kernel_-_Common_Problems_Booting_Linux

Maybe HB has already seen this. Was just sharing what I found.:)
[Samsung Galaxy SL i9003] shriom_manerker:
seems exactly what we're experiencing i suggest u post this in the dev area ! it makes sense ! this is where we're stuck at the moment !
[Samsung Galaxy SL i9003] luiseteyo:
Yes, post that please in dev thread

EDIT: I arrived late, I am sorry. Thanks for sharing
[Samsung Galaxy SL i9003] hillbeast:
Thanks for the info. Looked promising but I think this system may have been deprecated.

I have a new idea: I'll try porting an older kernel, say 2.6.36 or something much closer to the Samsung one, even 2.6.35 and see if I can get that one to work. I won't be trying to get a lot working in it, just getting it to uncompress and once I figure out how I do it there, I'll try it on kernel 3.0.
[Samsung Galaxy SL i9003] AmmarGitham:
Ok here's something really interesting which I found can be tried out (if not yet been).

http://blackscratches.blogspot.in/2012/04/how-to-build-android-kernel-308-for-ti.html

it's a "[HOW TO] Build Android kernel 3.0.8 of TI Omap 3630 for Android ICS ".
[Samsung Galaxy SL i9003] Skander1998:
I think they tried that before Hillbeast even started his work, and it doesn't work.
[Samsung Galaxy SL i9003] hillbeast:
Seen it. Sorry.
[Samsung Galaxy SL i9003] vishal24387:
@ hillbeast

suppose if we not able create working kernel 3.x then any plan have u decided to proceed with cm9 with current kernel 2.6.35...???
[Samsung Galaxy SL i9003] simmer14:
dhiru already said it is not possible to back port everything.. our device demands kernel 3 :cowboy:

off topic btw i'm very happy that now we have atleast a stable ROM [value pack]..

i will also appreciate if someone fixes the video recording bug in CM 7.2 because that is the only bug in it :angel:
[Samsung Galaxy SL i9003] luiseteyo:
Dhiru is working in video playback i am sure he will work in video recording or other cm9 aspects.
[Samsung Galaxy SL i9003] hillbeast:
I won't fail. It is possible, its just not as simple as I originally thought.

Its this first hurdle that must be passed. The moment a single character shows on the UART the train will be rolling.

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] :
OMAP3630-Kernel Sources

@hillbeast:

I've searched the web for the OMAP3630-Kernel for our device. Here is a link to the source:

git.omapzoom.org/?p=kernel/omap.git;a=shortlog;h=refs/heads/p-android-omap3-3.0

I hope i can help you
[Samsung Galaxy SL i9003] loSconosciuto:
He is already using these sources.

@hillbeast

I think this should be:

MACHINE_START(LATONA, "LATONA")

codeworkx said that with the wrong machine name init.latona.rc and uevent.latona.rc are not executed.I even tried to build a kernel with "Latona board" before posting this and my phone was stuck at the Galaxy SL screen. I could boot in recovery however.

Probably that's not a problem now, but it will be later. (in Gingerbread however it works with the wrong name)
[Samsung Galaxy SL i9003] hillbeast:
That shouldn't really matter, but if it becomes a problem later then I will change it. It definitely isn't causing the current issue though as the second part (Latona board) is just a label.
[Samsung Galaxy SL i9003] loSconosciuto:
Yes, I know that it's just a label and for this reason I wanted to try to build a kernel with a different label, it's weird that init chooses which file need to be p****d using a label, but my test prooved that codeworkx was right, of course :P.

So I took a look at the sources and I found that the label is used as fallback if you don't provide the hardware name through the kernel command line: util.c. I don't know why it worked in Gingerbread, it should be the same.

I know that the problem is somewhere else, because if I understood correctly the problem is when the kernel is uncompressed or right after that. That post was more as future reference, I wanted to help you somehow, if you'll have this problem you'll know where to look at.

Anyway, thank you so much for your work and for taking the time to read and reply to each post.

EDIT:

I didn't know that pars3d is a bad word :confused: :silly:
[Samsung Galaxy SL i9003] hillbeast:
It's weird because I've sworn several times on this forum and I'm sure it let me. Why block that? It's not really even a swear word, rather a poor spelling of one used by British people. O.o
[Samsung Galaxy SL i9003] supergaijin:
sorry for OT, but I noticed this censorship started after a recent forum update. now that they started including it, it's even going so far as to censor a few member names, like one I've seen in our forum, whose name is p...r...e...s...h...i...t, which is an acceptable Indian name.

and I know you know, hillbeast, but for those less familiar, the "a...r...s...e" in "p...a...r...s...e...d" is a misspelling of "ass" to make it more "acceptable" in normal language. I recommend from now on that people look at their posts after writing them to see if they need to do a "bypass" spelling variation to get around this inconvenience...

do they censor the word pass because of ass? no.

do they censor passed for the same reason? no.

why they're censoring p****d (p.a.r.s.e.d) when they don't block "ass" is beyond me... :eek:

[/OT]
[Samsung Galaxy SL i9003] Skander1998:
I think they censored @rse (@ with a) which is a common way of saying @$$. (@ = A | $ = S | e), people use that to bypass censoring but looks like it's blocked here :D Smart admins..

@r$e = ****

They will probably fix this later and make it block only the actual words and not others that use part of the censored word.

Anyways, let's keep the thread about 3.x kernel discussions, the admins probably know about this i reported my own post later with my concerns and they deleted it, so they probably saw it and will fix it.
[Samsung Galaxy SL i9003] Mamica:
I think it's end with the kernel 3.x but I hope HB will find 'a solution
[Samsung Galaxy SL i9003] bscraze:
Hillbeast said he's not giving up, it's not the end can u read -_-
[Samsung Galaxy SL i9003] :
What all things to do is left for this kernel.??
[Samsung Galaxy SL i9003] muhsino:
Just read this and development thread you will learn what we know
[Samsung Galaxy SL i9003] Skander1998:
Updated First Post.

Please don't spam the dev thread and post anything not related to actual development here.
[Samsung Galaxy SL i9003] Mamica:
something new abut the kernel?
[Samsung Galaxy SL i9003] supergaijin:
no.
[Samsung Galaxy SL i9003] dorukc:
@hillbeast man i am not a developer, just wondering.

did u tried to compile kernel 3.0 without linaro toolchain? i saw many people compiled their kernels with linaro and they stuck on boot. maybe the same thing causes you can not get uart

Sent from my GT-I9003
[Samsung Galaxy SL i9003] Skander1998:
He probably did that already.
[Samsung Galaxy SL i9003] hillbeast:
I never used Linaro. I used GCC 4.4.3 as its stable.

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] wrishaba:
kernel 3x

]Kernel 3x from hillbeast was interrupted by some means.

Any way a great effort by hillbeast regardless of difficulties he is facing.

But altogether It will be the next development.

The tiger hids itself for vigourous jump.

is it so hb?
[Samsung Galaxy SL i9003] hillbeast:
Well right now I'm working on getting kernel 3.4.x working nicely on the Galaxy 3 and it's coming along nicely. If you look at the project page for that you can see that we're making progress now that we got some debugging information, and it'll be the same story for the SL. Just need to get the thing to debug and we'll be sorted.
[Samsung Galaxy SL i9003] Mamica:
very good news. I hope it happens as much 'as soon as possible
[Samsung Galaxy SL i9003] jayharper08:
^^^^THIS is spamming. It has been stated numerous times NOT to ask for ETA.

So......DO NOT ask for eta's. Yes, your question is considered and ETA.
[Samsung Galaxy SL i9003] Wahaha123:
Sorry Jay. Pretty sure mamica is the only person who keeps asking for ETA's ever since ICS came to our the i9003 subforums. we always warn him and tell him not to ask for eta's but still he keeps on doing so. its better to have a moderator like you warn him. he does not listen to us.
[Samsung Galaxy SL i9003] Gondya bhau:
this may come useful
[Samsung Galaxy SL i9003] Androfreak725:
What are the features of kernel 3 and why can't we use odin after flashing it?
[Samsung Galaxy SL i9003] vishal24387:
google it buddy.
[Samsung Galaxy SL i9003] androidjel:
Im from the op black comunitie the will release ics for our device maby you can port when its releases the kernel?
[Samsung Galaxy SL i9003] Skander1998:
The reasons for not being able to use ODIN are available in the faq of the first post, read it again and again or expect to be reported for asking an already answered question.

@The guy from OB:

We already know that, and that's what devs are going to do.
[Samsung Galaxy SL i9003] vegiebiscuit:
Question:

Just asking, is Stratos Karafotis(Developer of Semaphore Kernel for GT-I9000) helping out with the Galaxy SL Kernel 3.0 development? Because there is no updates after this: http://xdaforums.com/showthread.php?t=1762482&page=2
[Samsung Galaxy SL i9003] hillbeast:
Never heard from him or anyone telling me about him before this.
[Samsung Galaxy SL i9003] simratcs:
@hillbeast Keep It Up Dude :thumbup:

Love ur determination !! :)

Sent from my GT-I9003
[Samsung Galaxy SL i9003] Skander1998:
Thread updated, the project is alive again, this thread is open again for discussion to avoid spam in the development thread.
[Samsung Galaxy SL i9003] coolpix90:
it seems like kernel 3.0 woks on i9003... or not?
[Samsung Galaxy SL i9003] :
It boots !
[Samsung Galaxy SL i9003] Skander1998:
Boots then crashes, that means it is way better now then last time, it didn't even boot last time.
[Samsung Galaxy SL i9003] hillbeast:
I think some people are getting ahead of themselves. There are two definitions to booting:

1: booting the kernel as in the kernel starts to load and initialise past the decompression stage (as in the kernel shows text after showing the version number and such)

2: booting the kernel to a console or interface such as busybox shell or Android.

It does 1, but not 2. That is still to come.
[Samsung Galaxy SL i9003] sh7adeh:
new progresses ??

i am xdaholic since optimus sources have been realeased :D
[Samsung Galaxy SL i9003] loneagl:
no ETAs. period.
[Samsung Galaxy SL i9003] sh7adeh:
im not asking for eta's ... just asking for new feeds about our tortoise kernel :D
[Samsung Galaxy SL i9003] hillbeast:
Have now twice seen the same question that CM10 development has stalled in favour of kernel 3.0. I wasn't aware of this until you guys informed me. I still cannot give any ETAs on when it will be finished. Nobody knows how long it will be, only that it won't be any time soon. We have had major progress in the development of this kernel but its still not enough to make the kernel boot into a shell. That is still to come.

Currently I am working on adding separate files for Latona in the kernel so I'm not just overwriting the LG files but its not cooperating very well. I haven't worked on it over the last few days because I'm doing 6 days a week at work again while someone is away (gotta love capitalism...) so I don't have a lot of time to put my head down and program but a lot of what I'm doing at work at the moment I just mind numbing stuff so I have plenty of time to come up with ideas.

I've figured out how I will get past the kernel not cooperating with me and I'm going to try that today. I'm just waiting on my new build server for kernels to finish downloading the source code.
[Samsung Galaxy SL i9003] RonnYap:
@Hillbeast

Actually nobody will asking you ETA..

especially vishal24387 and shriomman (they wont ask)

BUT you take tooo long since 15 June 2012.(almost 105 day)

If you like them, how you feel..:crying:
[Samsung Galaxy SL i9003] hillbeast:
If I'm taking too long, then show me another person who needs the device and I will send it on to them then if I'm too slow and not good enough for it.
[Samsung Galaxy SL i9003] Hetalk:
@Hillbeast Please don't overreact. No one's questioning about you being "Good enough". Your records show that you are more than "Good enough".
[Samsung Galaxy SL i9003] matapollos:
I'm tired of reading this kind of comments... Calling hillbeast slow is the same as demanding a solution right now. You (and also myself) are in no position to ask such things as ETA or 'faster results', call it whatever you like.

He's doing it for free, he kindly accepted helping us with our device, when he had no obligation.

So do not rush him and do not annoy him. If you know another experienced kernel developer willing to help us, start a donation thread to buy him another device, so he can work together with hillbeast.

That's all I wanted to say. Excuse my rude manners, but I get kinda annoyed after reading those comments.

PS: Don't mind them, hillbeast. Cheers!
[Samsung Galaxy SL i9003] Hetalk:
^^ Agree ... lets find another dev and donate to buy another device.

But, still we won't be able to ask for ETA from that dev as well.

Then, in few weeks time, we'll find another one :P

This is fun. YeeHoo.
[Samsung Galaxy SL i9003] loneagl:
Good one, that!:p
[Samsung Galaxy SL i9003] marshygeek:
Why dont you guys try to be contented on what ROM and KERNEL you have right now. The thing is we are too eager. Too perfectionist, we are not contented on what we have "RIGHT NOW". Why dont we be thankful for we have this kind of development (esp. be thankful we have HILLBEAST) and the fact that someday we'll have our BEST i9003 ever.
[Samsung Galaxy SL i9003] Hetalk:
^^ I'm sure everyone here is happy with our phone/rom(Dhiru's base)/kernel(Dhiru's base) that we have right now. Else, we wouldn't be here.

We are more than thankful for having Dhiru, beyond any doubt.

We'd be thankful for the kind of development that you mentioned, if we had any such development.

I don't any comment for the "Someday" part.
[Samsung Galaxy SL i9003] Mamica:
come on guys....hillbeast said that now he is working on this project!what do you want more??I propose to be patient and wait
[Samsung Galaxy SL i9003] ale210:
Ey @hb all community Galaxy SL from spain were pushing you, thank you so much!!

Can you explain your last post from 3.x dev kernel, are good news??
[Samsung Galaxy SL i9003] vishal24387:
I am testing latest build. So far so good :) If any bug I encounter I will report here.
[Samsung Galaxy SL i9003] quan815:
what bulid???:confused:
[Samsung Galaxy SL i9003] Mamica:
did u test and kernel 3.x build??