yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] hillbeast:
NO MATTER HOW YOU WORD IT, THIS IS STILL ASKING FOR AN ETA. NOBODY KNOWS HOW LONG IT WILL TAKE AS NOBODY KNOWS WHAT OBSTACLES WE WILL FACE. I AM REPORTING THIS POST AND ANY FURTHER POSTS WHICH ARE ASKING ALONG THE SAME LINES.

I know you all want to know how long it will be, but how developers read it is "hurry up and finish it". It also means to developers "tell me how long it will take and if you tell me you must finish in that time or I will flame you".

I gave an ETA on something once before and I nearly left the XDA because I was actually being abused on Facebook and the XDA being called a liar and that I don't deserve the RD title for not keeping my promise.

I will not give an eta or any estimates. End of discussion. And this is the last time I will say this. From now on I am only reporting these messages.

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] jayharper08:
Just take note here: Repeat offenders will be going on vacations for asking ETA's. This is a DEVELOPMENT thread.

Directly from the OP:

Now respect the developer and do not ask that question.
[Samsung Galaxy SL i9003] preshit10:
Hey hillbeast this is what I found earlier today. A user named 23tushar started a new tread stating this.

Developer of Semaphore ICS Kernel For GT-I9000 Has Agreed To Help Us.

And He Can Develop ICS Kernel For Galaxy SL Too

Developers Please Contact Him.

stratosk

home :semaphore.gr

mail : stratosk@semaphore.gr

I know we already have sufficient amount of devs working on this, but since our device is a little similar to I9000, this guy could you out as the problems would be somewhat similar. Its all upto you and our fellow devs to decide. Keep up the good work!
[Samsung Galaxy SL i9003] hillbeast:
Well similar is a little bit of a lie too. The phones are actually very different. The only similarities I can see in hardware to the i9000 is the OneNAND and the USB switch chip. Pretty much everything else is different.

Not impossible, just extremely hard. You can work on stuff like adding mach-code but you just can't debug it. That's the hard part is relying on other people to provide you with debugging information before you can continue, and hence why I was hesitant to help with this phone before I was offered it.

But if this developer wishes to help then I invite him to contact me. As I say to any other developers, just send me a PM stating your interest, fork the repo, make some changes and send a pull request when you think you have something. I can certainly do with someone helping me figure out why I STILL can't get UART output from decompression.
[Samsung Galaxy SL i9003] hillbeast:
I don't need hardware as I already have a build server (unless you wish you buy me more RAM as it's stupidly low on it (I'm not asking)), research won't really help as I already have the OMAP documentation and there is no documentation for this phone (or at least any that is relevant), testing will be public when it is working enough, and hosting, well XDA gave me 25GB for free on Dev-Host, so I'm sorted there.

The main thing I'm trying to wrap my head around why UART isn't showing anything when the kernel is decompressing. If you can help with that then feel free to.
[Samsung Galaxy SL i9003] hillbeast:
Guys enough discussion over whether someone is worthy of helping us out. As I have said numerous times, I am happy for anyone to contribute in any way shape or form. They only need to do a pull request. No more bickering, okay? The XDA is a happy place.
[Samsung Galaxy SL i9003] frapeti:
Would you mind telling me what kind of documentation / info is missing / needed? It may be clasified / confidential
[Samsung Galaxy SL i9003] jayharper08:
Pretty sure that arguing is not "Development". If you want to argue about something, do it on another site, or in pm, or whatever, but not in this thread.
[Samsung Galaxy SL i9003] hillbeast:
Everything is missing. The service manual is useless as it doesn't even refer to the phone that is in it, and the information in it is wrong.
[Samsung Galaxy SL i9003] bobby_loveing:
sorry if im wrong.But it may be helpful or may not be.

lg optimus black has same board and configuration..

It's manual may help you...
[Samsung Galaxy SL i9003] hillbeast:
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, I'm not sure but even the layout of the board is not the same. Sure the components may be similar, but so are the specs of a Toyota Celica and a Lotus Exige.

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] supergaijin:
I will try and get this added to the front page of the Q&A.
[Samsung Galaxy SL i9003] wardfan220:
Enough!! I've deleted the posts and any more comments pertaining to them will result in infractions. That all around disrespect WILL NOT be tolerated.
[Samsung Galaxy SL i9003] hillbeast:
Progress Update:

Nothing has happened over the last week or two as I have been busy with work/wanting to relax/working on other projects/experimenting with my tablet (my tablets kernel is closed source and I have been slowly getting an open source kernel working on it since I got it, but haven't put any real effort into it).

However this weekend I haven't really got any plans, so I am going to set my goal to get decompression to show up on UART. I know some of you guys are pestering the devs and I really wish you would stop because it doesn't make us work any faster. Try to understand that we all have our own things going on, and also understand that currently the development is being stalled by me as I am the only person who can get UART working. I know I can, and I know somewhere I just have something missing, I just need to find what it is.
[Samsung Galaxy SL i9003] Wahaha123:
We appreciate your time and efforts you give for our phone. even if you are having a busy week, you still look for time to deal with this UART decompression. we will wait for your progress and we will stay as patient as we could possibly be for the sake of the advancement of this phone. once again, thank you HillBeast! :D
[Samsung Galaxy SL i9003] hillbeast:
Progress Update:

I don't know if I told you guys but I can't see the bootloader over UART either, I never have been able to and it is unrelated to what kernel is on the device. It won't output at all. This has really pissed me off because I can't control the SWITCH_SEL from the bootloader, I can't control anything. Now I've always attributed this to it trying to output Sbl to ttyS0 or ttyS1 or something else, however I have been discussing with xplodwild, and he told me that holding Home while putting the battery in on the SGS2 will output the bootloader to the UART while booting. I tried this on my S2 and sure enough it works.

Now how does that help the SL? Well it doesn't, but it gave me an idea: i tried it on the SL and it didn't output. Again, how does this help? Well he also told me to try holding enter on my keyboard while doing this, and I noticed this stopped the device from booting. It would stay at the Galaxy SL i9003 logo on the boot, like the phone was waiting for input. I then tried typing reset and pressing [enter] on my console (as if I was typing into a console I couldn't see), and sure enough it reboot.

And now you're really confused as to why I am bringing this up. Well the thing is, what this tells me is that the Sbl is there, and it is attached to ttyS2, but only the input is on ttyS2. Is the output on another console? I don't know but there is certainly a console there, the fact I could type reset and it would reset confirms Sbl is there.

I am going to do some digging into this, because this could also be the reason I am getting no UART from kernel 3.x. This is progress, while it may be sideways it is progress. Seeing the Sbl will definitely help me.
[Samsung Galaxy SL i9003] hillbeast:
Further Information About 'Blind SBL'

As I can't see the SBL, it does limit things until I figure out why it won't display anything, however I won't let Samsung beat me like that, and I progressed by hex viewing the SBL partition on the OneNAND, and I found something interesting:

andr_load_normal..Load Android Normal-boot image from the flash device..andr_load_recovery..Load Android Recovery-boot image from the flash device..andr_load_kernel..Load Android Kernel and Ramdisk using the current boot-up reason

Trying to decipher it, this seems to be the output of the help command, and these three commands seem interesting, as they seem to allow booting the normal kernel (normalboot.img), or the recovery kernel. I'll try flashing something different in the recovery partition and see what it does. I'll try flashing something like the CM9 kernel. If I can get this figured out then perhaps if someone is daring enough to mod the SBL, we could get a working recovery partition. The functionality appears to be there, so I can't see why not.
[Samsung Galaxy SL i9003] hillbeast:
Oh wow I didn't expect it to be that easy. I just took another kernel (I used BCK seeing it works on GB), renamed normalboot.img to recovery.img, put it back in a tar and flashed it with Odin, then went into the blind Sbl, typed andr_load_recovery [enter] boot [enter] and away it went. Obviously I had no UART apart from decompression seeing BCK doesn't support UART, but going into Settings > About Phone > and seeing XDA_BAM in there when I hadn't touched the normal kernel was quite cool. So that's how you dual-boot on a GSL.
[Samsung Galaxy SL i9003] mohamadfar:
This kernel support persian and arabic languege ? I want Android 4.1 in my I9003 ...
[Samsung Galaxy SL i9003] bscraze:
Kernel doesn't decide the language. The rom does.
[Samsung Galaxy SL i9003] hillbeast:
Right this UART is pissing me off now, so I've decided to go right back to basics and start from the top of where the problem could be. I'm going to now assume I have done nothing towards getting UART working and I'm going to go through every single line of code that builds up to UART output, compare it to Samsungs code by hand (not using diff because that just doesn't work), and see what's wrong.

Here is every file that is referenced at the start of the kernel booting. I am only going to look at decompression stage. Anything afterwards doesn't matter seeing if I can see anything, and I mean ANYTHING I can get it working. That is how me and fellow developer moikop got kernel 3.4 starting to boot on my Galaxy 3: we had UART working from stage 1 on that phone (ironic seeing it's the closed down undocumented phone) and that meant we could just spam the UART debug with messages every time it did anything, and we could then follow what it was doing and pinpoint the exact line it was crashing, and now as a result we have this: http://xdaforums.com/showpost.php?p=25865865&postcount=2 (well more now...)

This will expand when I find more that is referenced. I have removed the files that are universal includes and do not matter and bolded the ones that I need to look at.

boot/compressed/head.S
[B]> mach-omap2/include/mach/debug-macro.S[/B]
[B]>> plat-omap/include/plat/serial.h[/B]

boot/compressed/misc.c
[B]> mach-omap2/include/mach/uncompress.h[/B]
[B]>> plat-omap/include/plat/uncompress.h[/B]
[B]>>> plat-omap/include/plat/serial.h[/B]

boot/compressed/decompress.c
[Samsung Galaxy SL i9003] shitman66:
Follow to booting up device.

1)Is there anything let us know what's running while boot? :confused:

Just like when we're boot our pc or nb up the mainboard will show what're excute while booting.

2)Is there anything let us know where's wrong command line when you or any dev write/complie the kernel?

So sorry if i spam this thread.
[Samsung Galaxy SL i9003] hillbeast:
Unfortunately that's what I'm trying to get going. I don't have either of those.

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] crackerizer:
Ok, this reply is just a reference for those who ran into the same situation.

You can format a RFS partition by /sbin/fat.format ;)
[Samsung Galaxy SL i9003] shitman66:
Hmmm, I see.

Did you mean you these are stuff for kernel development but there's not any thing let you know the wrong line or missing word?
[Samsung Galaxy SL i9003] hillbeast:
Not without what I'm trying to get going.

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] shitman66:
I'll help you find it. Or the way to let you know. But I know nothing about linux language. It's too bad.:(

At first time when you start this project I though to change my platform from Windows to linux for study about linux language and join the project. But I have many things that might run on Windows.

Right now , The only one 3 things that I can do is follow,find the way and wait for your successful in our device.

Cheers bro. :good:
[Samsung Galaxy SL i9003] crk1995:
linux 3.5 is out...
[Samsung Galaxy SL i9003] Gondya bhau:
ya....just checked it....

this is the feature list

http://www.phoronix.com/scan.php?page=news_item&px=MTE0MjA

most changes seem graphic card related though......any changes which could help android ?? hillbeast ?:confused:
[Samsung Galaxy SL i9003] hillbeast:
Not interested. Maybe later once we have 3.4 working 100% I will port it. Linux 3.5 may be out, but the Android kernel 3.5 isn't out.
[Samsung Galaxy SL i9003] hillbeast:
Update to this:

serial.h

Most of it is the same, except I noticed Samsung has __init omap_serial_early_init defined while OMAPZoom doesn't. Will look into this.

uncompress.h

Everything looks good here.

debug_macro.S

Everything seems fine but I'm not sure. The new code just has more stuff for different chips as far as I can tell.

boot/Makefile

I checked this too and nothing special here, or in compressed/Makefile. This is more confusing...
[Samsung Galaxy SL i9003] Mamica:
this is a good news?
[Samsung Galaxy SL i9003] luiseteyo:
Well, it depends in what u think of "this is confusing".... Please don't spam the thread. Sorry for the OT
[Samsung Galaxy SL i9003] hillbeast:
This depresses me:

I bought a new modem/router today, another Cisco as I love them (not just because I'm a CCNA, rather because they're good) to replace my old one which had a wireless chip which was slowly giving up. I decided to have a quick poke at the old router... and I got Linux 3.3.4 on it... in 4 hours.

And I can't even figure out Linux 3.0 on the GSL. This is actually pissing me off that this phone is beating me. I won't give up though, so don't think that. I just need to have a think about what the problem could be. I'm now down to thinking perhaps the kernel image isn't being loaded by the Sbl correctly which now points me back to the Sbl now showing anything so I can't rule that out as an option. For all I know, the Sbl is pointing it to the wrong part of the kernel to boot from and I can't see this because of a really bizarre idea Samsung had of making the Sbl invisible.

And I have tried other resistor values for the UART and it made no difference: can only see UART (on a working kernel) from when the kernel boots onwards. Again, kernel 3.x either isn't decompressing at all, or it is not outputting at all.
[Samsung Galaxy SL i9003] simmer14:
please excuse me HB but what if you email samsung support they could help you imho..

skin also contacted them and they helped him.. atleast they could drive you in right direction..
[Samsung Galaxy SL i9003] cukierkas:
Wow, never thought that would be so difficult :eek:

Good luck, patience, bright mind :thumbup:
[Samsung Galaxy SL i9003] moikop:
I don't think the SBL isn't executing the Kernel.. Generally the SBL does what we want it to do.

If the SBL doesn't initialize the UART ports at that stage, then UART won't be initialized until the kernel does it. And if you're having problems after decompressing the kernel, that's not gonna happen.

If I were you (and if you're that frustrated), I'd try to port UBoot as a third boot stage (Like we talked for the G3, but in that case, it was only for "comfort" reasons. Here seems needed if you can't access the sbl shell). I've seen a couple of trees of UBoot with OMAP 3630 support (that's the cpu here, right?) and hopefully it'll say something.

Good luck.
[Samsung Galaxy SL i9003] hillbeast:
I have been thinking of getting u-boot working,but am trying to toss up whether it'll be too much hassle. It's most likely going to have the same issues as this and then I have another system I'd have to debug. I'm mainly confused about how Samsung got it going...
[Samsung Galaxy SL i9003] hillbeast:
This coming week, I don't want to concentrate on any other projects apart from finishing building my new server (not build server, my fileserver and such at home which I just did an upgrade from terrible hardware to not as terrible hardware with Windows Server 2008, but that won't take too long. It's just doing updates now so it's basically done.

I'm going to concentrate and find why this thing isn't working. I'm now suspecting it's a bad line of code in head.S or something that it doesn't like that crashes the phone. All the UART addresses are correct and I really cannot see any lines of code in Samsungs code that switches the UART output on that isn't already in OMAPZooms kernel so now it's just down to perhaps the ASM itself. Perhaps it's being fed a bad register from the bootloader or something, I don't know. I really do doubt the Sbl is causing the problems because I can't see why Samsung would be that retarded. I know they are idiots, but they aren't stupid enough to make the bootloader intentionally not show anything and the kernel must then turn it on. It would be the Sbl turning on output as the very last thing it does most likely.

So now to look at hundreds of lines of assembler... it's like being back in Polytech again when we were developing boot sectors... great...
[Samsung Galaxy SL i9003] lovesingh25:
i wana thanx hillbeast for his continous effort..

But should we ask codeworkx for his little help on this???

I know he will be too busy with JB updates but atleast he can guide...

I checked his profile and he still owns galaxy SL i9003 ......

so may be he will be little bit interested!!!
[Samsung Galaxy SL i9003] samisax:
Hey Hillbeast,

Is it possible you just have a bad device that's got some hardware issue? Has anyone replicated these UART issues?
[Samsung Galaxy SL i9003] LoLaTiOn:
I joined thanks for those who developed the kernel of this phone as pathetic

I'm sorry to spam this topic but I take the risk of avertsement.

Why, because it is the door open to new developers who are waiting to make their contribution and on behalf of big names like you hillbeast.

If only I could help you but unfortunately I already hard to understand and follow.

I was still listening and thank you for giving us so much information and news, I see that you are not the type to give up easily.

Sincerely ...
[Samsung Galaxy SL i9003] iAmBalvinder:
Agreed 101%

HB's dedication demands appreciation.

Respect !

Sorry for OT.(just for morale boost).
[Samsung Galaxy SL i9003] hillbeast:
I have tried contacting him, and it's almost impossible. He's on the other side of the world and he's always busy.

I doubt it. I can't see whyit would be a hardware fault when it works fine in the old kernel but not the Sbl.

And I have tried a different Sbl.
[Samsung Galaxy SL i9003] empreror:
we share the same Chipset with nokia n9

hill beast while i was looking around i noticed that we share the same Chipset with n9 and so far they are have a working ics... i dunno i thought it might help to see they code and implement some of it if there is sth to implement...
[Samsung Galaxy SL i9003] Adi_Pat:
N9 is using 2.6.32 Kernel even on Jellybean ;)
[Samsung Galaxy SL i9003] hillbeast:
Unfortunately if it were that easy I would have done it already :(

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] luiseteyo:
Hillbeast, I am sorry to pollute the thread, but maybe some of ur kernel developers from g3 can help u with this. Since u know a lot about kernel 3.0 u must know a lot of people. It is not necessary to be codeworkx, who left us until waleedq and gm007 worked hard in our device. Just an advice. Hope it is useful and again sorry to OT
[Samsung Galaxy SL i9003] bscraze:
@ hillbeast how about contacting dharam? Does he know anything abt UART?
[Samsung Galaxy SL i9003] AmmarGitham:
I posted this in the general thread. shriomman suggested I post it here. So here it is...
[Samsung Galaxy SL i9003] hillbeast:
I could ask them but I doubt they would know. I'll ask them if it comes up but none of them have worked with non Samsung SoCs AFAIK. I'm the only one who has left the safety of Samsung for other brands and architectures (MIPS, Broadcom, TI, Amlogic, etc).

Dharam doesn't even develop on the G3 anymore. He is an S2 guy full time. He was going to treat his G3 like I do and use the G3 as a development platform and keep the S2 as a phone, but obviously he didn't have the time for that, so I don't know if he could help. We didn't have UART when Dharam switched to S2 so I doubt he has it at all.
[Samsung Galaxy SL i9003] bscraze:
@hillbeast for older kernels, you could contact doomlord/napstar/xda bam if you get stuck on the older kernels, they are kernel devs and I'm sure they would not hesitate to help.
[Samsung Galaxy SL i9003] hillbeast:
Well right now I'm having weird build issues with Linux kernel 2.6.35.13 and I haven't even done anything and I've tried several toolchains. I'll try Android kernel 2.6.35 instead. Most likely it's kernel.org being crap as per usual...

EDIT: I'm forking github.com/android/kernel_common branch 2.6.39. Hopefully this'll work better than the rubbish kernel.org expect people to work with...
[Samsung Galaxy SL i9003] cdesai:
Use codesourcery, and make sure the version is the one samsung left in the Makefile / README, and you should be fine.
[Samsung Galaxy SL i9003] hillbeast:
I just use the Android toolchains or Linaro, depending on which one works, so either 4.4.3, 4.6 or Linaro 4.7. I find the Android ones Google provides are rock solid. I would get CodeSourcery but it's hard to track down these days. If you have a link then that would be helpful. It can go in my collection of toolchains.

EDIT: Oh and note I'm not working with the Samsung kernel right now. I've had the Samsung kernel compiling fine for ages, I'm just using a stock kernel because I can't be bothered.
[Samsung Galaxy SL i9003] loSconosciuto:
Here:

2009q3-67

2010.09-51

EDIT: list
[General Questions and Answers] edgex:
My girlfriend is a blackberry user, as was I from first generation blackberry until last gen, then I made the leap and won't go back. But now she wants a bold 9900 and curious if any phones are specifically more accurate or better for typing. Or even any good androids or maybe windows phones on at&t with keyboards?

Sent from my GSII Skyrocket
[General Questions and Answers] songokuj5:
Doesn´t she like touch's keyboard like GSII? The accurate and speed is better than a hardware´s keyboard.
[General Questions and Answers] Stridar:
I've had iphones, blackeberrys, GSII and now I've got the SG3.

I realised that the most practical and easiest to type with was the iPhone 4.
[General Questions and Answers] a.cid:
On androids, what keyboard you use aldo has an impact on your writing speed/ease...

I use smart keyboard pro, and I can still type better than my iphone and bb trotting friends...

On touchscreens, practice is required to get used to it...

Typed using a small touchscreen
[General Questions and Answers] edgex:
Interesting, I'm getting 3 free iPhones as soon as the iPhone 5 releases from family who is upgrading, maybe she will like it.

I tried swype and was terribly inaccurate. Have used SwiftKeyX for months and I'm pretty fast but not that fast. On a blackberry I could hold a verbal conversation and be touch texting 100% accurately without looking, which is why she still prefers a physical board.

Sent from my GSII Skyrocket
[Epic 4G Accessories] VassagoX:
What kind of car dock/phone holders are everyone using for the Epic? naturally, I want one that will leave the aux and charger port open. What are you using? Thoughts?