yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] sarthak.killedar:
Can you tell what you and others have planned about what next in this kernel?
[Galaxy 3 Android Development] hillbeast:
I want to figure out OneNAND, why it won't write, MMC about what I need to be using as a clock source and then GPIO. That would be after I am finished with this mental week at work.
[Galaxy 3 Android Development] protomank:
I have one doubt about kernel 3.4 development:

I was reading the git changes last week, and noticed on the "TODO" list there is the drivers part. SO my question is if this is only a matter of porting the drivfers to 3.4, or simply all drivers will have to be coded from zero? I don't known how many drivewrs are already open-source for 2.X kernel...

If drivers have to be written, IMHO it will take a really long time until we get a decent 3.4 kernel :)

Thanks in advance.
[Galaxy 3 Android Development] DiGaTTo:
Last veriant
[Galaxy 3 Android Development] RohMish:
I have one question, One the kernel 3.x is in place, how will be ROMs flashed? via CWM or adb-only?
[Galaxy 3 Android Development] VinC0deur:
The response is on the first page and in the Q/A section. Please search before post.

Suggestion for hillbeast: Add [Q/A] link in first page for avoid this kind of post.
[Galaxy 3 Android Development] sarthak.killedar:
Any update on OneNAND or any other hardware driver?
[Galaxy 3 Android Development] dilzo:
Just be calm, even if you do get an update it's not going to benefit you in any way so just be patient and let Hillbeast tell us when he wants. Also if he hasn't said anything then I doubt anything important has happened.
[Galaxy 3 Android Development] hillbeast:
If you want to know progress, just check the Github repo commit log.

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] austin266:
@mark

Is the progress stalled?
[Galaxy 3 Android Development] m1trand1r:
did u check his Github...?

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

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy 3 Android Development] austin266:
Last committed on august19
[Galaxy 3 Android Development] hillbeast:
I have been busy with work and exhausted as I have explained several times. I want to relax and rest my body and my mind before I continue doing serious development.
[Galaxy 3 Android Development] austin266:
Its ok mark

Am not pushing u...?

Take ur time... i know the difficulty in developing a kernel

Best wishe...
[Galaxy 3 Android Development] hillbeast:
I know you're not. Just giving an update on my personal life. Any development I have done in the last month and a half is minor at best and just tweaking stuff in general.

I now also have Nexus 7 users asking me to dev too...
[Galaxy 3 Android Development] MmegaMac:
Please do not abandon galaxy 3 ! You start work then finish it!
[Galaxy 3 Android Development] kylandomos:
Tu n'as rien a dire . Il fait ca sur son temps libre en dehors de son Taff . et tout cela gratuitement . T'as qu'a acheter un autre Phone si t'est pas content .

--------------------------------------------------------------------------------

"You've Got nothing to say . He's Doing that in his free time . And his don't take Money for this . You Should Take another Phone if it don't pleased you ."
[Galaxy 3 Android Development] hillbeast:
Not going anywhere. My work on the Nexus 7 is basically just me uploading my personal ROM, much like it was when I was making Kyorarom on the Galaxy 3: I would upload the ROM I used myself and let others use it. I do development for myself a lot and hardly ever release it due to laziness (I don't want to debug it for others).

The Galaxy 3 is still my main development phone, followed by the SL.
[Galaxy 3 Android Development] austin266:
@ mark

My small suggestion to u... it will be nice if u have a look..

Try release ur rom's with one name( kyorarom/ serenity) to all the devices u r working on .,like cyanogen mod... as it started alike..

As ur work is remarkable among dev's.. keep it up:beer:
[Galaxy 3 Android Development] sudersanmurthy:
+1:)
[Galaxy 3 Android Development] Sergiales:
Great job. But you shouldn't give any explanation, you do this in your free time, sometimes you make more progress sometimes less. Better to keep in silence and just update once you have anything new. Ignore people asking for updates... in case you have it and you want to share it!

good luck!
[Galaxy 3 Android Development] hillbeast:
I was thinking of doing it, but JB doesn't work on my S2. Like at all. It's terrible. It crashes all the time, has wakelocks, devices stop working randomly, the modem restarts all the time... it's just horrendously bad. I've never seen a ROM so unstable, and considering I need it as my main phone I don't have the time to fix them.
[Galaxy 3 Android Development] josip-k:
Wow if you start doing it (and i would LOVE if you did) ill cook a jb rom for Gnex and kyorify it! :D (if you want ofc)
[Galaxy 3 Android Development] hillbeast:
Well the GN doesn't need much done to get Kyorarom to work on it. Would just be a matter of me getting my hands on the proprietary files for it (android/vendor) and compiling it.

However at this stage I don't really want to branch out onto other devices that I don't own as I can't debug them.

Anyway enough OT. If you want to discuss Kyorarom Serenity, then feel free to discuss it on any of my Serenity threads.
[Galaxy 3 Android Development] m1trand1r:
wha@at??:eek:....Mark...i have dualboot setup aka cm9 & cm-x....and cm-x/jb runs like a charm on my s2....:confused:...howcome you feel it soooo bad?...i don't understand....

I have LPX modem and corresponding ril and it works fine...and it haven't crashed even once on my s2....i really don't get it...:o:

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

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy 3 Android Development] BeriCud:
Hi, is someone develop or working on this or this is dead thread...??? I just look on github but one month there aren't any progress or any news about it...

Sorry for my bad english...
[Galaxy 3 Android Development] Pradeep:
Have patience!! :cyclops:

Devs do their work in their free time and its not an easy task to port a entirely new kernel!!!
[Galaxy 3 Android Development] hillbeast:
I've just been relaxing over the last week and recovering my build box. It's back up and running now, but I spent yesterday catching up on housework, which is also very important.
[Galaxy 3 Android Development] MicroGeek:
How's the progress on this project?
[Galaxy 3 Android Development] hillbeast:
Haven't worked on it in a while because the GSL community have been demanding me to make progress...

I want to get MTD working under 3.4 though.

Sent from my Galaxy S2
[Galaxy 3 Android Development] andreapier:
Please, try not to give up as this is very important for G3!
[Galaxy 3 Android Development] cdesai:
You talked to marcellusbe yet?

He has it working on 2.6.32, so it should easy to get it working on a newer kernel now. :)
[Galaxy 3 Android Development] marcellusbe:
@HB : here is the onenand support with samsung AUDI driver, that I use with kernel 2.6.32 and it's working fine.

I commited the changes here :

https://github.com/sdadier/android_kernel_samsung_s5p6442/commits/s5p6442-3.4
[Galaxy 3 Android Development] tom3q:
I believe that this driver is just the samsung-onenand merged with all the generic onenand helpers with some minor changes put inside a single file. Most probably the problem with samsung-onenand driver is really trivial and so not so easy to spot just looking at the code. Unfortunately I don't have much time to spend on such things, so I can't be of much help at the moment.
[Galaxy 3 Android Development] hillbeast:
I was having trouble with yaffs2 compiling as well. I believe we decided to use ubifs though.
[Galaxy 3 Android Development] cdesai:
<snip>

Sent from my GT-P1000
[Galaxy 3 Android Development] hillbeast:
Ours is SLC according to the Sbl. Of course our SoC is such a mess I wouldn't be surprised if the OneNAND is a hybrid as well.

Sent from my Galaxy S2
[Galaxy 3 Android Development] cdesai:
I might be wrong about it being MLC, but pretty sure it's not the same chip, and it's 1GB.

I'll confirm with epic developers (sounds epic ;) ) when I get a chance.

Sent from my GT-P1000
[Galaxy 3 Android Development] tom3q:
AFAIK, AUDI is a codename for this particular OneNAND controller, found in newer S5P*. The driver itself should not depend on the OneNAND chip attached to, this is what the generic OneNAND code should care about. Although it's possible that generic code currently doesn't have support for this particular OneNAND chip in G3, but it should be easy to add, looking at the old driver.

If I understood you correctly, this is kind of dangerous, because if something goes wrong, you might lose your EFS. It's better to create a separate partition, not overlapping with original EFS and preserve the original partition in case of some failure. (The copying itself is fine.)
[Galaxy 3 Android Development] marcellusbe:
no worry, original efs is preserved. I just copy modem.bin and efs files in a new parititon called efs.
[Galaxy 3 Android Development] tom3q:
OK, that's good. Thanks for clarifying this.
[Galaxy 3 Android Development] artifex21:
Any progress with the kernel ?
[Galaxy 3 Android Development] hillbeast:
My build box I've been using for the last two or three months has been terrible at compiling, and refuses to put the initramfs in it properly, or at least I'm blaming the build box because the only things changed since I was last working on kernel 3.4 was the box and the toolchain (Linaro now when I was using Googles GCC 4.4.3 before). I'm making a new build box at the moment and hoping it will fix the issues I was having with the last one. The last one had terrible per thread performance and couldn't handle poorly threaded operations.
[Galaxy 3 Android Development] z3c0:
Do you think the 3.x kernel development will resume in the foreseeable future?

Since there's still a lot of activity around the Galaxy 3 I guess there would still be sufficient interest.
[Galaxy 3 Android Development] hillbeast:
The problem is with a lack of developers in the community with the time, skill or motivation to do so. I haven't got a lot that makes me want to develop on the Galaxy 3 these days seeing its so old now. I am expecting after sending this reply to have the usual 'we-hate-hillbeast' brigade come in here to flame me and say I'm useless blah blah blah (and don't think I don't remember who you all are and what you have said about me) but the fact of the matter is that the Galaxy 3 isn't my main device anymore and therefore isn't that interesting to develop on because all I gain from finishing the kernel is satisfaction of finishing it, which I can get from working on it slowly in my own time rather than having to rush it out.

Sorry.
[Galaxy 3 Android Development] ak700:
Just Kidding. But I know that feeling. After using the Galaxy S 3 for a few days, the Galaxy Apollo has started to feel tiny and pixelated. I'm just saying, but I think we have come to a point where the development can't moved ahead unless we have a Dev who can work from ground to bottom FOR FREE.
[Galaxy 3 Android Development] tanmoyc:
actually i don't think that you should be worried about wat others say about you, i have been into this forum for last 2year and have seen and tested your work and liked it too. and thanks for your contribution in development of sg3
[Galaxy 3 Android Development] z3c0:
I for one still like my G3, because it's so tiny and yet quite powerful. Who knows what it might still achieve if it had a usable 3.x kernel and thus a shot at a full-featured JB...

I think that there'd still be a lot of (non-rude) G3 users and devs who'd love to see the development to go on but I'll admit they're getting fewer and fewer, naturally.

(Also some of the important devs are having / getting fulltime jobs, how dare they?!)

Anyway, thanks so far for your efforts here. I tried to look at the basics of kernel development occasionally and always got thrown off by heaps of missing background knowledge about hardware and low-level CS principles.

Kudos for how far you've got here (mostly self taught, I gather). It's definitely nothing to apologize for.
[Galaxy 3 Android Development] prohank:
So its official now.:(

Would you be developing if we pay you and you can guarantee that it(kernel 3.0)will work.There is an acute shortage of quality develolopers i understand but this is just an offer if you feel lack of motivation.This is no easy job.

I believe there will be other willing participants/contributors too.

Come on guys we have been using everything for free from this forum.lets pay something in return at least once.

Just let us know if you are interested.

You read my post :what::click Thanks.
[Galaxy 3 Android Development] MicroGeek:
I dont think people are allowed to sell stuff on xda or they have to go.to a certain forum to. Sell stuff
[Galaxy 3 Android Development] hillbeast:
I think you guys are misreading what I wrote. I'm not leaving or anything or abandoning development, just saying that progress is slow because I work on it in my own time. Will we see kernel 3.x? Probably, but probably not in the near future, unless someone gets me motivated.

And no, don't pay me. I've just had to deal with a s**tstorm from the Galaxy SL community claiming I promised them kernel 3.x when I did no such thing, I told them I'd help in the development of it which is what I am doing. I gave them UART and the means to debug the device (UART didn't work on the phone using the normal methods) so they could get started. I also gave some of their developers pointers on where they need to look to get things going and such. If you pay me and I fail you then I will feel guilty for betraying your trust and I will get flamed by the haters.

I don't care if people hate me, I already know people do. If people don't like me then they can suck a lemon. I am not here to make friends, I'm here to improve devices. Right now the device that has my attention is my stupid Ainol Novo 8 tablet which has the worst kernel in the world: even the stock kernel is broken beyond belief like it was compiled by a monkey who just learnt how the make command works. Once this device bores me again, I'll look at the Galaxy 3 again. That processor intrigues me as much as it pisses me off (closed source Samsung...)

Note to anyone wanting my advice on a phone to buy next time: nothing that has a Samsung processor.
[Galaxy 3 Android Development] jyotisankar9:
Dear Hillbeast,

What you have done for this community is beyond explainable. I wish you all luck in your new adventure. Do what you want to do, its your wish always. There are people who won't find your current work entertaining as it is not helping them, but who cares. Ignore them. Cheers!!!
[Galaxy 3 Android Development] bsuhas:
I still love G3...but I bought Micromax A110 ( MT6577 1 GHz, dual core, 5" screen, 510 MB Ram, 2.5 GB internal Mem, ICS 4.0.4)....

A110 community is very short of developers...can you help me/developers or guide us to port JB to our phone?
[Galaxy 3 Android Development] pratikmore:
mt6577 have jb i think;just search for it
[Galaxy 3 Android Development] MicroGeek:
I think you should just tell a mod to lock the thread so that people know progress is not going to be made.soon and.people wont force you to provide updates.
[Galaxy 3 Android Development] hillbeast:
I dont have the phone so I cant help.

I don't need to ask a mod. I can do it myself but choose not to in case another developer wishes to use the thread for discussions.
[Galaxy 3 Android Development] MicroGeek:
What's the news on the new Kyorarom?
[Galaxy 3 Android Development] hillbeast:
YAY! After months and months of trying to locate where my old sources for kernel 3.4 went, I FINALLY got working sources that let me actually get to shell. This is what has been holding me back for so damned long.

Kernel 3.4 is back in action.
[Galaxy 3 Android Development] psiva2010:
Good news man,

All the best, could u please share the sources with us some of us can help u to develop.

Siva
[Galaxy 3 Android Development] hillbeast:
I'm currently working on fixing the repo up now.
[Galaxy 3 Android Development] hillbeast:
And with marcellusbes help months ago, I can finally state that MTD is fully working:

[ 3.116354] =================================================================
[ 3.123544] Samsung OneNAND Driver (AUDI).
[ 3.127681] =================================================================
[ 3.135064] OneNAND: Clock gating is enabled.
[ 3.139427] Muxed OneNAND 512MB 1.8V 16-bit (0x50)
[ 3.144196] OneNAND version = 0x013e
[ 3.244215] OneNAND: There's no interrupt. We use the normal wait
[ 3.246684] Scanning device for bad blocks
[ 3.289418] onenand_bbt_wait: ecc error = 0x0001, controller error 0x0400
[ 3.290597] OneNAND eraseblock 320 is an initial bad block
[ 3.514721] OneNAND eraseblock 2047 is an initial bad block
[ 3.518596] Creating 8 MTD partitions on "s5p-onenand":
[ 3.520048] 0x000000a00000-0x000001180000 : "boot"
[ 3.527116] 0x000001180000-0x00000ed80000 : "system"
[ 3.532816] 0x00000ed80000-0x00001b800000 : "userdata"
[ 3.537839] 0x00001b800000-0x00001de00000 : "cache"
[ 3.542448] 0x00001de00000-0x00001f500000 : "efs"
[ 3.547275] 0x00001f500000-0x00001ffc0000 : "reservoir"
[ 3.552386] 0x00001ffc0000-0x000020000000 : "dgs"
[ 3.557075] 0x000000180000-0x000000200000 : "param"

~ # mount /dev/block/mtdblock1 /system
~ # cd /system
/system # ls
hello lost+found
/system # cat hello
Hello there Mr Bond
/system #

~ # mount /dev/block/mtdblock2 /data
~ # mount /dev/block/mtdblock3 /cache
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 163820 0 163820 0% /dev
tmpfs 163820 0 163820 0% /mnt/asec
/dev/block/mtdblock1 218151 2063 204824 1% /system
/dev/block/mtdblock2 200793 1807 188618 1% /data
/dev/block/mtdblock3 37675 467 35263 1% /cache
~ #

Next task: GPIO
[Galaxy 3 Android Development] hillbeast:
I think GPIO is working? Somebody prove me wrong:

[ 0.256043] samsung_gpiolib_init: S5P6442 detected
[ 0.256075] samsung_gpiolib_init: 29 GPIO chips will be used
[ 0.256105] gpiochip_add: registered GPIOs 0 to 7 on device: GPA0
[ 0.256125] gpiochip_add: registered GPIOs 9 to 10 on device: GPA1
[ 0.256143] gpiochip_add: registered GPIOs 12 to 15 on device: GPB
[ 0.256161] gpiochip_add: registered GPIOs 17 to 21 on device: GPC0
[ 0.256179] gpiochip_add: registered GPIOs 23 to 27 on device: GPC1
[ 0.256196] gpiochip_add: registered GPIOs 29 to 30 on device: GPD0
[ 0.256214] gpiochip_add: registered GPIOs 32 to 37 on device: GPD1
[ 0.256232] gpiochip_add: registered GPIOs 39 to 46 on device: GPE0
[ 0.256249] gpiochip_add: registered GPIOs 48 to 52 on device: GPE1
[ 0.256267] gpiochip_add: registered GPIOs 54 to 61 on device: GPF0
[ 0.256285] gpiochip_add: registered GPIOs 63 to 70 on device: GPF1
[ 0.256303] gpiochip_add: registered GPIOs 72 to 79 on device: GPF2
[ 0.256320] gpiochip_add: registered GPIOs 81 to 86 on device: GPF3
[ 0.256338] gpiochip_add: registered GPIOs 88 to 94 on device: GPG0
[ 0.256356] gpiochip_add: registered GPIOs 96 to 102 on device: GPG1
[ 0.256374] gpiochip_add: registered GPIOs 104 to 110 on device: GPG2
[ 0.256393] gpiochip_add: registered GPIOs 112 to 119 on device: GPH0
[ 0.256411] gpiochip_add: registered GPIOs 121 to 128 on device: GPH1
[ 0.256429] gpiochip_add: registered GPIOs 130 to 137 on device: GPH2
[ 0.256448] gpiochip_add: registered GPIOs 139 to 146 on device: GPH3
[ 0.256467] gpiochip_add: registered GPIOs 148 to 155 on device: GPJ0
[ 0.256485] gpiochip_add: registered GPIOs 157 to 162 on device: GPJ1
[ 0.256503] gpiochip_add: registered GPIOs 164 to 171 on device: GPJ2
[ 0.256522] gpiochip_add: registered GPIOs 173 to 180 on device: GPJ3
[ 0.256540] gpiochip_add: registered GPIOs 182 to 186 on device: GPJ4
[Galaxy 3 Android Development] Poil44:
Great news, and nice work :)
[Galaxy 3 Android Development] tom3q:
The log only states that all those gpio chips have been registered. You should also check whether all the banks are defined correctly (probably by comparing with old kernel).
[Galaxy 3 Android Development] hillbeast:
I put in all the definitions myself by using the old kernel as a reference. The ones that were in there were wrong and were S5P64x0 based, but our GPIO bus is a lot closer to S5PV210.
[Galaxy 3 Android Development] tom3q:
OK, fine then.

Now I guess you can start doing some work with peripheral hardware.
[Galaxy 3 Android Development] hillbeast:
Right now I'm just performing a few tests to make sure the GPIOs are fully working. I made it pull values from the GPIOs for a few things like hardware IDs and they seem to give the right results but one was wrong so I am not sure. I'll try getting the buttons to work so I can see if it reads them right.
[Galaxy 3 Android Development] hillbeast:
Weird progress with GPIO related stuff:

I've got it to configure the GPIOs, or at least I think that's what it's doing. Now it does one of many things:

1: When booting it will turn the screen off

2: When booting it will make the screen go black but not off (it will only do one of these top two)

3: Randomly reboots for no reason, and doesn't even show a log as to why it's rebooting

4: Somehow corrupts the kernel meaning I need to reflash it (this happens after it reboots for no reason).

So I have no clue what's going on right now and it's 1AM so I'm sick of looking at this thing. Time for bed.
[Galaxy 3 Android Development] hillbeast:
Derp. Didn't want to quote. Wanted to edit.

Update: I don't think GPIO is working right so I need to look into it after work. Hopefully I can get more done before my ODROID arrives and distracts me...
[Galaxy 3 Android Development] hillbeast:
I played around with the GPIOs a little more and now it seems to be giving me the right information from various GPIOs when it's starting up. Again, it's probably not working 100% as I still need to find some stuff to prove me wrong, and it is still turning the screen off when it starts up, but it seems less random now with what it's doing. The thing that causes the screen to turn off is all the stuff that sets up the GPIO pins in mach-apollo.c so it looks to me like the functions aren't working right with this chipset, or just react differently to how they did in 2.6.32.

EDIT:

Kernel 3.4:

[ 0.268572] apollo_machine_init : hw_rev_pin=0x0
[ 0.268600] apollo_machine_init : bootmode=0x0
[ 0.268616] apollo_machine_init : lcd_id=1
[ 0.268629] apollo_machine_init : uart_sel=1

Modified G3MOD:

check_hw_rev_pin : hw_rev_pin=0x0
check_hw_rev_pin : bootmode=0x0
check_hw_rev_pin : uart_sel=1
s5k4ca cam power off
S5P6442 Power Management, (c) 2008 Samsung Electronics
check_lcd_id lcd_id=1

Think it's right.
[Galaxy 3 Android Development] tom3q:
Seems like you're somehow triggering screen reset. So either there is something wrong with pin numbering (bank register offsets and pin counts) and one pin uses configuration of another or somehow pin reconfiguration causes screen reset pin to go active for some time, even if target state isn't active.
[Galaxy 3 Android Development] hillbeast:
Yep. GPIO is definitely working:

apollo_machine_init : uart_sel (high)=1
¡¥¹}¥¹¥Ñ: uart_sel (high)=1 ý(Á½±±½}µ

It should show:

[ 0.551720] apollo_machine_init : uart_sel (high)=1
[ 0.555248] apollo_machine_init : uart_sel (low)=0
[ 0.558863] apollo_machine_init : uart_sel (high)=1

But in the top one, I told the FSA USB switch chip to receive information from the modem (apollo_machine_init : uart_sel (low)=0) and then switch it back to the processor, and I wasn't sure what to expect, whether it'd just not work, or if that line won't come up, but showing garbage is good enough for me, it shows that the GPIO did get toggled and get switched back without issue. So yes, GPIO is 100% confirmed working.

Yeah I'm not sure, I think a lot of that code is garbage really. I'm probably going to take it all out and remake it by hand because Samsungs stuff is ass retarded, and an absolute mess. The GPIO bus is working, the code that configures what all the pins do isn't, but that's not gonna be hard to fix now.