yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] mikef:
While I understand your point and agree with it in general terms, I disagree that hillbeast was keeping it 'secret'. I would say he was obfuscating it and for a very valid reason coming from a Recognized Developer: It is not ready yet and the chances of someone bricking their phone or worse is high enough to not make the process available. Or to make seem so easy or to dare people into doing it. I have removed the link in your post above. I believe that hillbeast's post explaining his findings was sufficient proof, and that no one should try to brick their phone.

Perhaps if you all are extremely lucky, hillbeast and dhiru will be able to develop a stable process to help people to recover their UNintentional bricks. But first, please, some patience.

Thank you,

mf2112

XDA Moderator
[Samsung Galaxy SL i9003] Chris089:
I trust you at this point. But don't misunderstand me. There are many "flashaholics". If you say its "secret" they would do the false and flash. In my oppinion it's better to say...hey guys I found a way to do...but don't proof your self...! You are the only one that should do experiments with it, and so tell them. If they want to flash they will, but if you say... better no flashing...secret, you drive them crazy!

As I mentioned before, do it on your own and at the time you need. It's the best way to do some good development, I think.

Don't let some guys drive you crazy even if they want a quick "non functional" result. ;)
[Samsung Galaxy SL i9003] shriom_manerker:
let me put it this way for u ! if u use that program chances of permanently bricking ur phone are 99.99% ! hope that makes u understand :) besides if u've read earlier u would hav understood that it can only work on bricked devices lol ! so i suggest u to just read and observe the progress of kernel 3.0 cus this thing is not really a part of the kernel

sorry for being off topic !
[Samsung Galaxy SL i9003] jan3586:
i think it is also important to point out that this is hillbeast's thread and people will come here to complain if anything happen to their phone. if it is that important to share please start a new thread so thi s does not go off topic from kernel dvelopment. this should be a model thread for development section and i hope it continues to be this way even if there is an already released kernel.
[Samsung Galaxy SL i9003] issobuddy:
Relax guys, why become so frustrated :D

HB, yesterday I had flashed the kernel. Well like you and hetalk says, without UART there isn't much to do. After reboot it just displaying galaxy sl logo :rolleyes: But I've modifying your defconfig, toying around with idea to activate fb during boot or other method to dump log. It's fun to learn however :D
[Samsung Galaxy SL i9003] hillbeast:
fbcon will be of no use until the drivers are loaded. We are way before that.

Unfortunately unlike x86 which has a BIOS and a VGA BIOS which allows the graphics card to operate as a character device and therefore show a debug console on screen, ARM lacks that functionality.

Sent from my Galaxy S2
[Samsung Galaxy SL i9003] issobuddy:
I fear you'll said that hahaha. Oh well that mean fbcon and kernel

dump seems impossible. 2 bulb goes off, still has 9998 to try.

Btw imho I think the log info should be modified to be verbose enough, to trace where it is dies exactly.
[Samsung Galaxy SL i9003] hillbeast:
Its already set in maximum verbosity. I changed the boot parameters on my phone ages ago to turn off loglevel=4 because its useless. I'm going to have to add some printks to find where it dies.

Sent from my Galaxy S2
[Samsung Galaxy SL i9003] Adi_Pat:
Hello hillbeast,

I am sorry if this is off topic.

I compiled CMEM module some days back and from documentation, it says that we can allocate memory to dsp or other hardware to meet their need for reserved memory.

I have got the module to load, but I have no idea on how to allocate the memory specifically.

Any idea?

Sent from hell..!
[Samsung Galaxy SL i9003] hillbeast:
I'm not too sure on how these memory allocation systems work. I am pretty sure ION is designed to handle this though and is the correct new method for new versions of Android.
[Samsung Galaxy SL i9003] mikef:
I really don't want to hand out infractions for continuing to post ETA related requests, so I won't. The next infractions will be handed out for not following instructions from a mod. I want this to be very clear so there are no misunderstandings or complaints when the infraction notifications are received.

ETA related posts, however cleverly worded to avoid the word "when", are not welcomed, are not desired, and are only good for making me come in here and clean them up and then handing out infractions. If infractions are desired, then please do it again and I will unhappily oblige.

Hillbeast is working on it. If you wish for him to drop this project and leave this device forum, then please continue to post ETA requests and non-dev related posts here and I am sure in time he will oblige you as well. When that happens, I don't want to read a single complaint post since you were all warned repeatedly about your actions and the consequences.

Thank you,

mf2112

XDA Moderator
[Samsung Galaxy SL i9003] hillbeast:
Oh well seeing you know how long a kernel takes to be adapted to an undocumented (apart from the SoC documentation) platform, you might as well take over.

I mean heck, it's not like it's that hard. I only have to recreate the entire mach-code, relearn the entire platform and its components, learn the changes that Samsung made to kernel 2.6.35 and put them into kernel 3.0 while also calculating in my head the changes that should be made to compensate for the API changes that took place in 3.0.

Yeah that's just a trivial task. I mean heck, take how far Team Hacksung, a group of elite developers who are (and I'm actually being serious about this) are into porting kernel 3.4 to the Galaxy S2: http://teamhacksung.org/wiki/index.php/Smdk4210_kernel#Progress (and I mean no disrespect to them because I know how hard it is)... WAIT NO SORRY I MEAN IT'S A TRIVIAL TASK! WHAT AM I SAYING!

Yeah kernel porting is just so easy, I do it while I'm asleep.

In all seriousness though, if you must know what I'm working on, I'm working on ION for 2.6.35. If you want to know why, then I can't be bothered explaining because I'm tired of explaining myself to the needy members in the community. I really do want to get this kernel working because I don't like giving up on projects, but you guys make it damned hard at times for me to find the will to develop for them. For those people who are actually being patient and are appreciative of what you have already, I am developing for YOU guys. Thank you for being patient. For those people who consistently bug me about ETAs (I see it so much how many posts have been deleted, because every time you ask an ETA I get an email, and then the mod deletes your post, and then another person asks for an ETA, sometimes I wake up and have 3 or 4 emails asking for an ETA that have been deleted), I am not developing for you guys, in fact I completely ignore you now. I am actually only posting right now because I thought I should let you know I'm working on ION, but this email came in and really bugged me.
[Samsung Galaxy SL i9003] mikef:
This is really not the way I wanted to start off my Friday, especially since I am flying this morning and don't have time to properly deal with this now. I will when I land though.
[Samsung Galaxy SL i9003] Adi_Pat:
hillbeast, I have been working on this since a month now, no luck :(

1) Backported, fixed all necessary stuff for ION to compile.

Added all the board specific code for ION. { Still won't work, dhiru says memblock is broken }

So, I thought omap_reserve() need to be implemented, which again with any small change renders the Kernel unbootable.

[ This is as per my study of other OMAP boards, all of these use omap_reserve() after omap_register_ion() ]

Again, Samsung is using bootmem for memory allocation, while 3.0 uses memblock.

Commit 1: had to revert

Commit 2: had to revert

So basically I am stuck up here.

2) Merged Dsscomp too, but dsscomp needs ION so leave that for now.

3) Debugging: For debugging purposes , since I could not set up UART I thought of some alternatives. (Thanx to cdesai!)

RAM CONSOLE is one which could give me proc/last_kmsg dump.

Backported Necessary OMAP RAM Console with compilation fixes. Commit

Again fails, look at the macro: PLAT_PHYS_OFFSET

Couldn't derive this nor could I find any info on google.

So basically that was my attempt.... hope you can help out.

dhiru is also stuck up at the same place, had a talk with him yesterday.

When you get time, take a look at my commits, and let me know if I have missed out something or if I have gone wrong somewhere.

https://github.com/AdiPat/android_kernel_samsung_latona/commits/ics-samsung-2.6.35.7

Thanks and good luck!
[Samsung Galaxy SL i9003] hillbeast:
Okay I will take a look at your kernel as well. I might have to take bootmem right out and replace it with memblock.

Sent from my Galaxy S2
[Samsung Galaxy SL i9003] wardfan220:
Uh oh, somebodies in trouble #taunt

lmao, no really, I'm not going to overstep since mf has already stated he was going to deal with this issue, but the eta asking does need to stop. Everyone knows through out all of xda that etas are frowned upon.

And posting directly below a moderator telling you not to is not smart. the thread was heavily cleaned, yet it continued. Failure to cooperate with a mod?

mf, if you're busy, send me a pm.
[Samsung Galaxy SL i9003] Adi_Pat:
I actually merged memblock too. Still didn't work..
[Samsung Galaxy SL i9003] dhiru1602:
Kexec on OMAP3 is hard. This is the reason why many of the Boot loader locked phones don't have proper working kexec. Instead they use 2nd boot, which doesnt really help in loading up a new kernel.

OT: All the impatient ones, you very well know how fast the things are moving here. So come back again next year when Android 5.0 is out.
[Samsung Galaxy SL i9003] hillbeast:
Kind of a confession here guys, I cannot for the life of me figure out where I put my SL. I put it somewhere either in my bedroom or in the lounge, but it must have slipped down the back of something and now I cannot find it. I spent all of yesterday trying to hunt for it, and I've found the back of it, but I can't find the rest of it.

I know it's in the house somewhere, but this is what happens when I have to prioritise programming over top of house maintenance: I can't locate stuff. If you want to blame someone, blame me 90% for being careless and trying to do programming in bed, and blame 10% on the people who keep rushing me and don't let me clean my house.

I will find it though and let you know as soon as I know where it went. I'm not normally this careless. I did find my old PSP in the process though, but that's not interesting to me. Haven't cared about it in over two years.
[Samsung Galaxy SL i9003] Misledz:
Not sure if people are thankful that he lost the phone, or thanking him for some other reason I am unfamiliar with.

On another note the phone can be found later, the important part is the UART setup which is required and important. That way no one is pressuring you to find the phone. If you could courier that to any of the following Adi/dhiru/hetal/ooi then that would be much appreciated.

When you find the phone you can keep it.
[Samsung Galaxy SL i9003] heysupratim:
Can somebody point me to the original kernel source tree (one released by samsung - 2.6.x) not the one on dhirus repo ,though i know its one and the same thing :P
[Samsung Galaxy SL i9003] chongns:
Guys. The urat devices is his property. Not the communiti. So. Its unfair to ask for the urat devices.

For the phone its so community property, so better find it..fast. predicted ww3 is comming...

:(
[Samsung Galaxy SL i9003] shriom_manerker:
u don wanna look there mate believe me !! its a **** load of crap ! but heres the link anyways http://opensource.samsung.com/
[Samsung Galaxy SL i9003] Misledz:
The law of the world states equivalent exchange, The phone has been given as promised and UART setup is all that is asked/required. According to XDA Rules you are allowed to ask for it permitted credits are given due. If anything this work is to benefit developers for the community, not for an individual.
[Samsung Galaxy SL i9003] chongns:
Agree on the 1st part.

Agree on the 2nd part, if HB agree on it. Anyway his is the owner.
[Samsung Galaxy SL i9003] Taraen:
I'd say patience is a by far better way, than claiming his UART setup. This won't help the situation at all. You should see the fact that he was very honest telling that to us. Very badly translated to English I tend to say: "The house looses nothing" Lets give him time to search for it. It has to be somewhere.
[Samsung Galaxy SL i9003] hillbeast:
I get what both of you are saying, but chongns is correct, the UART setup is mine. I have provided details on how to make a UART adapter on another page and have told people if they are willing to make one (they can make one equivalent to mine with parts off eBay for less that $10USD) I can provide all the information provided. I am not willing to give away my UART setup as that is used for not just the Galaxy SL, but my Galaxy 3 as well, and my Galaxy S2, and my Arduino is in that setup and I use that thing for projects, and that device is worth its weight in gold in my country. It costed like $400 just to get the little bugger.

I know the phone is in my house somewhere and I've eliminated most of the places it could be. If I still can't find it when I search the last few places, then obviously someone has stolen it and they have a phone which doesn't work anyway, so the thief is an idiot (I don't think someone broke in to steal a phone when there is plenty of other stuff I have, but I wouldn't be surprised if one of my flatmates nicked it).

Give me some more time to look before demanding I send my tools away. It's like asking a builder to give up his tool belt.
[Samsung Galaxy SL i9003] LoLaTiOn:
Development and sharing the golden rule

If you want to privatize should not go to XDA but an external site

It is easy to complain but difficult to contribute to those claiming

@ hillbeast

Do not listen to all the world keep us informed
[Samsung Galaxy SL i9003] mikef:
The UART setup has been discussed in this thread already. There was a nice portal article on it as well.
[Samsung Galaxy SL i9003] Hetalk:
From what I read above no one is demanding (or claiming) the uart setup, if hill beast is still using it for his other devices. It was just a request in case he's not gonna use it.

Also, worth noting here is that dhiru / adi are in need of a uart setup to see logs of things they are actually working on. If anyone else here feels they can read hill beast instructions and provide one, please come ahead and do so, rather than post in vain. I tried but was stuck as I am unable to find a level converter board in india. See if anyone can locate it.

Sorry hill beast. Enough of this off topic over a lost phone. Just post here when u find it. Be assured no one is gonna ask u to give up ur property.
[Samsung Galaxy SL i9003] Misledz:
By all means agreed this was not to claim your personal possession or your work. Losing the device could mean one of the following, in the obvious side work flow could come to a halt. The intention was if that was to occur then perhaps the UART Setup could be passed over to dhiru or such so the progress continues to reap results. Rest assured your work is yours and no one is here to call dibs on that. Your effort, time and production value will not go unnoticed.

If ETA is one we cannot speak of, then perhaps "Time is ticking" would be the right paraphrase, not in terms of pressuring, but rather if we can keep up with everything that flows. 4.2 is on it's way in 4 days (Confirmed) and possibly 4.3 by December (As per the rumors), and by all means that would pressure you not just on the SL side but the other phones you are working on, perhaps their community side will not be as patient or understanding as ours.
[Samsung Galaxy SL i9003] ardicli2000:
@hillbeast

did you check the inside of your pilow or blanket. It may also be under the bed sheet, not under bed i mean.

I think we should come up with the ideas where the pnohen may be :):)

This is how we can contribute to the development right now :D
[Samsung Galaxy SL i9003] tejadakenneth:
hillbeast has a point. if you want something, work on it. it's not easy to share something that you work so hard.
[Samsung Galaxy SL i9003] mjbri0613:
HB pls update us where this developmental phone is..

thank you.. we need an update on what the status of that phone..

thank you...

any noob who want to flame me?

YOU DON'T KNOW HOW THIS COMMUNITY FIGHT FOR THE LATEST DEVELOPMENT... DONT JUST FLAME SENIOR MEMBERS WHO ASK SOMETHING RUDE..
[Samsung Galaxy SL i9003] tejadakenneth:
let's have a deep analysis.

if hillbeast is working on his own room.. may be the phone stored somewhere near on the computer. or may be he put it on the electronic tools.
[Samsung Galaxy SL i9003] mjbri0613:
so for whom is this message? deep analysis? deep patience? deep throat? :banghead::banghead::banghead:

we senior members just need update on where is the phone now... how many hectares is the room??? how many days to be seen...

i think this not eta's for development... thank you..
[Samsung Galaxy SL i9003] neil05:
:eek::eek::eek::eek:
[Samsung Galaxy SL i9003] Hetalk:
^^ I don't think ETA for lost phones count as being against xda rules. :)

@Hillbeast ... We (me + few other users) are planning to setup an uart as a collaborated effort and have zeroed in to this convertor, which, supposedly, is available in India. Do you think this will work for our device? Just need your thoughts about this. I understand you might not be able to confirm for sure. Just your thoughts.

http://www.rhydolabz.com/index.php?main_page=product_info&cPath=80&products_id=1090

@Anyone_except_Hillbeast_wondering_if_you_should_reply Please don't reply to this, unless you have a working UART setup or have a good understanding of this stuff.
[Samsung Galaxy SL i9003] wardfan220:
I'm done, thread closed.

I'm sick of getting reports every few hours about stupid petty crap in this thread.
[Samsung Galaxy SL i9003] vishal24387:
Dhiru should share his build kernel 3.x with hillbeast. With help of uart hillbeast can provide info that why kernel is not booting which will help Dhiru to do changes in his kernel so that it can boot.
[Samsung Galaxy SL i9003] XDA_Bam:
Just stumbled upon this patch. Sounds like it could fix your UART clock problem :)
[Samsung Galaxy SL i9003] hillbeast:
That would be because I'm rebuilding the repository. I'm rebasing it to a different OMAPzoom branch.
[Samsung Galaxy SL i9003] coolpix90:
did u found some problems with the old branch?
[Samsung Galaxy SL i9003] hillbeast:
Well Dhiru recommended I move to OMAPZOOM, and it was best to start from scratch. I also needed to fork the Team Hacksung repo.

It's all fixed now, you can see the sources again.
[Samsung Galaxy SL i9003] sachin sharma:
i hav made the zimage but its not booting!!!!

n tried booting it using uart

but i m getting nothing? i.e. no display not even a single word

y is this happening?

i m sure i have followed ur thread corretly
[Samsung Galaxy SL i9003] hillbeast:
Well that's because it's not finished, and lacks all the device settings. The repo is just the omapzoom kernel with no changes.
[Samsung Galaxy SL i9003] anziclone:
I read a certain USB OTG in that output of uart, does it mean that our chipset does support usb on the go?? If so, it would be a nice feature...

Hillbeast, great work man! Keep it up ... waiting for you to show ur intelligence... would love to help you out....
[Samsung Galaxy SL i9003] Adi_Pat:
@hillbeast

Count me in :)

I will try to help as much as possible though I am not a pro in Kernel development!

:D

www.github.com/AdiPat

Is my github id.
[Samsung Galaxy SL i9003] dhiru1602:
I have setup a repo with the latest sources from omapzoom.

https://github.com/dhiru1602/android_kernel_samsung_latona

Fork them.
[Samsung Galaxy SL i9003] hillbeast:
http://www.ti.com/general/docs/lit/getliterature.tsp?baseLiteratureNumber=swpt024

The OMAP3630 supports USB OTG.

Will do that soon.
[Samsung Galaxy SL i9003] hillbeast:
Changing the repo around AGAIN. Dhiru spoke to codeworkx and he told him to go back to basically how I was doing it in the first place: clean fresh repository with the OMAPZOOM as a remote branch. Oh well, at least my internet is unlimited.

Anyone who forked my repo, go delete it and fork it again when I let you know it's safe to fork it.

And to anyone who wants to help develop, just fork the repository. No need to tell me you want to help, just fork it, make changes and submit the changes in a pull request. When I see people making pull requests, I'll add their name to the developers list on the first post.
[Samsung Galaxy SL i9003] hillbeast:
Update: it's now safe to refork the repository. This time I promise I'm not changing anything.
[Samsung Galaxy SL i9003] alfrix:
@hillbeast

What would you recommend? in terms of toolchain and optimization flags?

Currently i'm using the standard -O2 and arm-eabi-4.4.3

i was thinking on using -Os rather than -O3, i might test out anyway, but what is your experience on this?
[Samsung Galaxy SL i9003] hillbeast:
I am just using the standard ARM toolchain from Android for now as it's stable. Linaro is giving me errors saying the processor doesn't support certain instructions, which is a load of crap because this thing is a Cortex A8 and the only features this core won't support is NEON. I should look up whether this has NEON, but I am 99% sure NEON is an A9 only feature which was a real kicker for Tegra 2 owners who never got it due to laziness from NVIDIA.
[Samsung Galaxy SL i9003] Skander1998:
It does have NEON (?)

http://www.arm.com/products/processors/cortex-a/cortex-a8.php
[Samsung Galaxy SL i9003] alfrix:
AFAIK it does have neon... And no comments on the NVIDIA side, they are what they are.
[Samsung Galaxy SL i9003] hillbeast:
Ah okay. Well good to know that. Still makes it even more confusing that Linaro claims the processor isn't capable of this instruction... stupid compilers.
[Samsung Galaxy SL i9003] hillbeast:
Right so I have disassembled the device to locate the internal UART ports. Here are some photos I have taken for others to take a look at if they wish:

http://d-h.st/Y0B

I have only taken photos of the mainboard as nothing else is of interest. And yes, the device still works. I am experienced in disassembling of handheld devices, so don't worry that I've killed it by opening it. I do know what I'm doing.

On another note, I am watching the UART voltage with my multimeter (I lack an oscilloscope to be more accurate with this), but I notice when the phone boots, the voltage is 5V (normal), and then the kernel boots, and around about where the text goes into garbage the voltage goes to 0V for half a second then comes back: most likely this shows the UART drivers starting up.
[Samsung Galaxy SL i9003] hillbeast:
Has anyone got a link to a stock ROM on this device that ISN'T on ****file? Hotfile just DOESN'T work for me. Period. I want a stock ROM for the device so I can observe the device in full working order, and every link I found so far has been on Hotfile and it's driving me insane.
[Samsung Galaxy SL i9003] klau7:
Don't know if dropbox is fine.

KPE: http://db.tt/13tUTLLV

KPU: http://db.tt/io3o7Cqj
[Samsung Galaxy SL i9003] hillbeast:
Dropbox works fine for me. Thanks for this.
[Samsung Galaxy SL i9003] hillbeast:
I needed to switch to Gingerbread to see the phone in full operation so I have a fully working platform to develop upon, and that required me also getting a Gingerbread kernel to give me UART output, so I took Bam Custom Kernel and compiled it with a few tweaks of my own (LZMA compression, LZMA ramdisk, optimise for size, Linaro compiled, fbcon, etc), and I'm using that.

If anyone wants to use this kernel, I've uploaded it. I don't know if it will have any extra performance over standard BCK, but it's here if people want to try it. This is a Gingerbread kernel ONLY.

Linky Stinky