yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 General] :
Ok, build environment set up (installing Ubuntu on a Mac can be a b:eek:). I just synced TeamRegulars repo with a local manifest:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TeamRegular/android_device_samsung_lt02wifi" path="device/samsung/lt02wifi" remote="github" revision="cm-10.2" />
<project name="TeamRegular/android_vendor_samsung_lt02wifi" path="vendor/samsung/lt02wifi" remote="github" revision="cm-10.2" />
</manifest>

I'll start a test build of CWMR while cleaning the appartment, probably going to end with an error but nevermind. Coud someone give me the newest status of TeamRegulars trees? Where should I start next?

I have the official kernel and platform sources from Samsung - should I create repos for both or don't we need them?

As I said, I'm new to this but eager to learn and help! :highfive:

EDIT:

Ok, first build...well didn't even build...got some "unexpected file" errors did some googleing but didn't find any good answers. I'll start over from scratch, using TeamRegular's files as a reference. Maybe I'll get a successful CWMR-Build tonight...

P.S.: Please stop me if you find my posting annoying. It's meant to provide everybody with information on my process so that others can learn - and most of all help ;)
[Galaxy Tab 3 General] :
I'm sorry to keep this thread alive, but I don't have posting rights in the dev-thread...

Got a succesful build yesterday, using my own repo for the moment. My recovery.fstab and BoardConfig.mk are different from TeamRegular's - maybe someone wants to check them out before I flash my recovery:

https://github.com/kaibutsu/android_device_samsung_lt02wifi

recovery.fstab is from stock recovery, BoardConfig.mk was created using the CM porting guide and TeamRegulars. I'd really appreciate some comments! I don't really want to brick my tab beyond repair...

Maybe I'll find some more time to test and pull blobs tonight. Really enjoying this and looking forward to CM...at least as long as my tabs not seriously bricked...:fingers-crossed:
[Galaxy Tab 3 General] N00BY0815:
In fact if you flash the recovery to the correct partition, it wont break anything at all, except for the... Guess what recovery :D

Just a joke ;)

As long as you dont touch the bootloader, you ll pretty much always be able to unbrick your device with odin or adb ;)

So just go ahead and try your luck, hope we can get it working soon.

But I am really too much of a noob still, to properly get CM working...
[Galaxy Tab 3 General] :
Hm...I don't seem to get fastboot to work under linux (device not found/waiting for device) and "make recoveryzip" didn't create a flashable zip. I'll try building the zip again and then flash it via CWM but this kinda sucks. I don't want to reboot to windows to flash with odin all the time... My T210 is recognized as Galaxy S2 in download mode and I read that fastboot doesn't work with the S2 - did anyone get it working? (before you ask: I tried using root/sudo and creating my own udev rules...)
[Galaxy Tab 3 General] ketut.kumajaya:
Feel free to use my kernel source :good: http://xdaforums.com/showthread.php?t=2439564
[Galaxy Tab 3 General] N00BY0815:
Look at my root without odin thread. There is a adb flash recovery script. Just replace the recovery.img.

Did you just get a zImage?
[Galaxy Tab 3 General] Unjustified Dev:
I pm'ed you
[Galaxy Tab 3 General] :
I got the *img (about 6mb), but I used stock kernel, wich I just read won't work anyways. When building a zip, I got "update.zip" and "unsigned.zip", both about 2mb, wich doesn't make sense to me. I added ketut.kumajaya's sources to my manifest and will try to build again - with kernel, then use your script. Thx for the help.

EDIT:

Recovery image not booting, 6mb seems to be to big...just another minor drawback ;)
[Galaxy Tab 3 General] :
I'm sorry to bother you again, maybe I'm too impatient, but I can't seem to figure out how to decrease my recovery.img size. Do I have to use the configure menu in the kernel directory or can I add something to BoardConfig.mk to decrease kernel and ramdisk image size? I already checked the png's but they are pretty small already.

I will continue trying and maybe start pulling blobs using CWM/TWRP from the forum as recovery - but I'd rather do it "the right way"...
[Galaxy Tab 3 General] gr8nole:
The unpacked ramdisk is limited to about 1mb unless you override the size when building the kernel. To get our custom recoveries to work we override the initrd size to make it 3mb.

Sent from my DROID RAZR MAXX HD
[Galaxy Tab 3 General] ketut.kumajaya:
Override bootloader initrd size: https://github.com/kumajaya/android...mmit/2f156084ddcdea962ce23d68ad6a7b191dbc0075
[Galaxy Tab 3 General] ironman38102:
Could anyone tell me what are current issues with buliding or booting of cm? Ill try to help in anyway I can
[Galaxy Tab 3 General] :
I guess you are not talking about Recoveries, as there are allready some there. Here is what I know of CM:

As far as I can see, there are some people working on it. No working build though. There is a pretty good kernel by ketut, so no need to reinvent that (THX!):

https://github.com/kumajaya/android_kernel_samsung_lt02

and

https://github.com/kumajaya/android_kernel_samsung_lt02_modules

I am still stuck at recovery wich is building but not booting. You can check my work at

https://github.com/kaibutsu/android_device_samsung_lt02wifi

I want my build to work as the config needed for recovery are later used for the rest of CM. There is a lot of config and files by unjustified_dev (if I'm not mistaken):

https://github.com/TeamRegular/android_vendor_samsung_lt02wifi

and

https://github.com/TeamRegular/android_device_samsung_lt02wifi

I didn't get those files to build, though.

I think you can either check the TeamRegular repo or mine. (I did't understand what was done in TeamRegular's, so I decided to start over to learn the whole process)

Speaking for myself I can use all the help I can get answering my noob questions and any help I can get generating the needed config files and proprietary blobs for the CM/CWM-Build. Just fork my repo and start working and sharing or do the same with TeamRegular's ;) - Sorry, nothing to test, yet...

Did I miss anything?

P.S.: I didn't figure out how to actually set the initramfs size override in my *.mk's so I tried something else first (my last build booted better than my first - flashing screen instead of logo only). I'll go to bed now while my computer is compiling, but maybe you could tell me where to put the override if ever this build won't boot either...:D
[Galaxy Tab 3 General] ketut.kumajaya:
You have to put in BoardConfig.mk known working kernel and config, for example:

"TARGET_KERNEL_SOURCE := kernel/samsung/lt02"

"TARGET_KERNEL_CONFIG := pxa986_lt02wifi_blackhawk_defconfig"

Even PXA986 and PXA988 cross compatible, the correct platform for this device is PXA988.
[Galaxy Tab 3 General] ironman38102:
I cant compile due to my **** pc but I can pull out properitary files from my tab or test the builds once I download stock rom tar. Btw since the wifi model doesnt have any baseband version how can I get a stock rom tar for my country?
[Galaxy Tab 3 General] :
You should see it under "Preferences" -> "About device" (or sth similar, mine is german ;) ) or you could check http://www.sammobile.com/firmwares/2/ . Good luck!

@ ketut.kumajaya: I never really understood the difference between 988 and 986, but you are right, it says 988 everywhere in my device. Thanks for that.

EDIT: I'll still use the blackhawk kernel as it has initram override enabled and it is known to work on the T210. Unfortunately that still didn't work. That means that override is not the problem...Can somebody help me debug? (Where do I find a log?)
[Galaxy Tab 3 General] ironman38102:
Well I can only see that it got shipped from UAE so I should get stock rom for UAE
[Galaxy Tab 3 General] ketut.kumajaya:
Your (recovery.img - zImage) must less than 3MB. The working recovery from [MENTION=3034891]gr8nole[/MENTION] use xz compressed ramdisk, xz compression better than gzip.
[Galaxy Tab 3 General] :
Why not increase INITRD_SIZE? Setting it to 4MB would solve my problem and it would increase startup speed.

BTW: What do

#BOARD_KERNEL_BASE := 0x00100000

and

#BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x01100000

do? Can't we increase kernel base or ramdisk offset here to help booting? Sounds like this is a memory issue... :confused:
[Galaxy Tab 3 General] ketut.kumajaya:
This is a long of story. Please remember, I have no physical access to T21x. A lot of T21x kernel hacking done remotely between me and [MENTION=3034891]gr8nole[/MENTION]. Why 3MB? I don't remember exactly why I set it that value, trial and error? But since my kernel source already in public domain, feel free to build it yourself. I made it configurable in kernel config, you can set it to 4MB.
[Galaxy Tab 3 General] :
I tried building and booting with 4mb now but it didn't work. Also changed KERNEL_BASE to 6mb. Both have the same effekt like all my builds since I've been using ketut's Kernel: Same slowly flickering screen (actually an advance to only boot logo). To make things easier, I simply copied the blackhawk config and changed (only) the 3 to 4 mb, maybe that's the problem, but I'm pretty shure it isn't. I'll push my commits now and maybe play around with the working recovery builds and my own kernels/ramdisks to figure out what's not working tomorrow...feel kind of down now, I've been working on this for some days now and still don't even have what I could just download... :(
[Galaxy Tab 3 General] Unjustified Dev:
I see you got it :) waiting on mine still. I have 1 more month I think
[Galaxy Tab 3 General] ironman38102:
Yea changed my internet package and they gave me the tab with 2 year contract. Anyway whats taking ur tab so long to arrive? Are u shipping it from somewhere or? I

---------- Post added at 08:42 AM ---------- Previous post was at 08:33 AM ----------

Eventually we would get a working cm. Its just that we need to find that one mistake somewhere in the repo
[Galaxy Tab 3 General] Unjustified Dev:
Seems more people have then Smt-210 . Don't really know about the 3g models so I will be working on this again
[Galaxy Tab 3 General] ironman38102:
Do u really think that people like to hold a tablet near their ear while their talking? No and that is why everyone bought the Wifi model and most carriers are offering wifi models

***Its Going To Be LEGEND--wait for it--DARY! -Barney Stinson(How I Met Your Mother)*** Crapatalk
[Galaxy Tab 3 General] Unjustified Dev:
Lol , I was saying the R version too it has the infrared for TV . But the 3g most likely are used for internet only without depending on WiFi. I doubt someone holds it to their ear. I would like to see that. The issue we are facing is the what's needed and what's not needed it's true I could compile a 4.1.2 ROM , but who wants that? We want 4.3+ so.. We need to take out the 3g model files , don't mistake the sprint model as our 3g it has a msm8930 CPU which is qcom. Our 3g model is Korean I think based on the same Marvell soc . The issue is the tablet system contains files for all models. There are models with NFC , models , with 3g , and models with Infrared. I am only working on the infrared and non-infrared model the t210 and t210r. Confusion exist when it has .sh scripts to grep device files and determine things between all models. I am trying to remove all those 3g and NFC files as well as figure out those weird Marvell files. I have never seen such files nor do I understand it's ramdisk it is very confusing that's why I want help and I am glad others are here to help. I don't need the tablet I have everything I need.
[Galaxy Tab 3 General] ironman38102:
You are still going to need the tab. Once u finishing compiling CM u would want to test it before u upload it. Wouldnt want to brick other peoples devices

***Its Going To Be LEGEND--wait for it--DARY! -Barney Stinson(How I Met Your Mother)*** Crapatalk
[Galaxy Tab 3 General] :
Nice to hear from you again. I'm still stuck at recovery building...I just figured out, that the kernel modules aren't built automatically when I run "make recoveryimage"...puh...one more thing to figure out...how far are you? Did you manage to build recovery from source? I'm glad to help in any way. Got the tab, and building environment and some time at hand. Unfortunately not much idea of what I'm doing...
[Galaxy Tab 3 General] N00BY0815:
If you could compile a 4.1.2 Rom, why dont you? I mean of course KitKat and stuff is tempting, but we would at least have a platform to start working on (see whats not necessary, what might be missing,...). Also I would simply love to finally get rid off this samsung touchwiz! Could you update your tree, so we can build from it? I would still compile it today probably :D

Edit:

Would you mind to explain, what s still missing?
[Galaxy Tab 3 General] ironman38102:
+1 I would want to get rid of this samsung bloatware
[Galaxy Tab 3 General] :
Ok, one step further, my kernel is actually working: using it with initramfs from gr8nole and ketut.kumajaya works. I don't think it's correct though, I cant find the extra modules and don't seem to get them built by "make recoveryimage", still trying though - any help would be appreciated.

As my Kernel is working and size restriction obviously/hopefully only applies to recovery. I'll try to continue with the real CM now. Too much time spent on this...maybe someone will pick it up later (gr8nole, unjustified_dev ?). Until now, I'll see what I can do to get CM running...
[Galaxy Tab 3 General] Unjustified Dev:
Read ketut.kumajaya guide on his github with the modules in the repo. For some reason the code is separated from the kernel as if it's not all licensed with Samsung. When I get mine I will add the drivers into the kernel. Simply enough it's not that hard to include them
[Galaxy Tab 3 General] N00BY0815:
Dont you think, it ll slow the tab down?
[Galaxy Tab 3 General] Unjustified Dev:
Haha no , that has nothing to do with it :) it's a module outside the kernel and is loaded by init with insmod . I really hate how Marvell has this tab set up.
[Galaxy Tab 3 General] :
That's what I did but I tried to put it into my BoardConfig.mk. I'll upload it to my repo, maybe you'll find the error. Building manually now, see if it works.

I guess you are talking about exfat, it is part of ketut.kumajaya's main kernel, not the modules. I don't really understand, why it didn't build with my BoardConfig.mk. It's not mentioned in the configs - as far as I can see...

On a sidenote:

Couldn't we compile exfat into the kernel (not modularized)? This would make the kernel bigger (and probably a bit slower to load) but wouldn't it reduce ramdisk size?

EDIT: I just read about DevDB, maybe we should turn this into a DevDB project?

EDIT 2: I think I found an error in the guide. It says "/data/android/build/..." when building the modules. Shouldn't it be "/home/android/build/..."?
[Galaxy Tab 3 General] :
Ok, I think I got something! Ramdisk size doesn't seem to be the problem but something with the display driver. I compared TWRP, working CWM and my ramdisk and kernels and this is what I got:

CWM:
Size in Byte	Filename
---------------------------------------------
5355520	recovery.img
3824000	recovery.img-kernel
3011584	recovery.img-ramdisk.cpio
1526568	recovery.img-ramdisk.cpio.gz

TWRP:
Size in Byte	Filename
---------------------------------------------
6596608	recovery.img
3824000	recovery.img-kernel
6199040	recovery.img-ramdisk.cpio
2768264	recovery.img-ramdisk.cpio.gz

Mine:
Size in Byte	Filename
---------------------------------------------
5928960	recovery.img
3501624	kernel
3624448	ramdisk-recovery.cpio
2422995	ramdisk-recovery.img

TWRP is in fact bigger than mine, both compressed and uncompressed. I checked the log, both still give an error "Initramfs unpacking failed: junk in compressed archive" when booting but TWRP is working while my CWM isn't.

I diff'd the logs and this is the part that made me think it might be a driver problem (LCD off and on is exactly what I'm seeing):

c0 stop_drawing_early_suspend: timeout waiting for userspace to stop drawing
c0 pxa168fb_suspend
c0 lt02_lcd_power off !
c0 pxa168fb_resume
c0 lt02_lcd_power on !
c0 tc358765_reset
c0 VX5B3D ...START.....
c0 brightness = [0]: vx5b3d_brightness = [0]
c0 VX5B3D ..END.....
c0 backlight control first...[195]
c0 i2c: <pxa_i2c-i2c.1> slave_0x64 error: timeout
c0 i2c: msg_num: 1 msg_idx: 0 msg_ptr: 10
c0 i2c: IBMR: 00000002 IDBR: 000000ff ICR: 000097e8 ISR: 00000004
c0 fs_mgr: Error parsing mount_flags
c1 pxa168fb_release GFX layer, fbi 0 opened 1 times ----
c1 pxa168fb_open GFX layer, fbi 0 opened 0 times ----
c0 stop_drawing_early_suspend: timeout waiting for userspace to stop drawing
c0 pxa168fb_suspend
c0 lt02_lcd_power off !
c0 pxa168fb_resume
c0 lt02_lcd_power on !
c0 tc358765_reset
c0 VX5B3D ...START.....
c0 brightness = [0]: vx5b3d_brightness = [0]
c0 VX5B3D ..END.....
c0 backlight control first...[195]
c0 fs_mgr: Error parsing mount_flags
c1 pxa168fb_release GFX layer, fbi 0 opened 1 times ----

I'll check for more differences in the ramdisks. Another thing I don't understand is: Why is my kernel smaller than yours. Is there some driver inside kernel I didn't build? I built mine from ketut.kumajaya's github but it's > 200k smaller.

Another thing is the "Error parsing mount_flags" error. I am using stock fstab, I'll check that, too.

Maybe someone else has an idea?

EDIT: I just checked the ramdisks, the only thing I found is that mine doesn't include the exfat modules (have to figure out, how to build them into recovery directly) it has exfat binaries though. I don't think that's the problem though. Other than that, I didn't find anything. I'll see if I'll find some time for that tomorrow. Still hope one of you can figure something out ;)
[Galaxy Tab 3 General] Unjustified Dev:
Here's my github for my phone there's exfat https://github.com/Team-Exhibit/android_kernel_samsung_codina-common/tree/3.0.1+/drivers/exfat
[Galaxy Tab 3 General] :
Thanx for that, I got it working now by adding this to my BoardConfig.mk:

# Kernel Modules
SAMSUNG_MODULES:
make -C kernel/samsung/lt02_modules/ clean_modules KERNELDIR=$(KERNEL_OUT) CROSS_COMPILE=$(ANDROID_TOOLCHAIN)/arm-linux-androideabi-
make -C kernel/samsung/lt02_modules/ modules KERNELDIR=$(KERNEL_OUT) CROSS_COMPILE=$(ANDROID_TOOLCHAIN)/arm-linux-androideabi-
mkdir -p out/target/product/lt02wifi/recovery/root/lib/modules
cp $(KERNEL_OUT)/drivers/exfat/*.ko out/target/product/lt02wifi/recovery/root/lib/modules/

TARGET_KERNEL_MODULES := SAMSUNG_MODULES

I consider it pretty messy, but it's working, now I'll diff my built recovery ramdisk and the working CMW ramdisk to find out, where my build goes wrong...

[MENTION=4021423]ketut.kumajaya[/MENTION]: Did you notice the issues I commited to your modules github? I seems to be easily fixable...
[Galaxy Tab 3 General] :
WORKING! yay!

I got my first booting CWM build based on CM10.2. It's highly experimental and WILL probably eat your cat, but it's working. Please go ahead and test! Attached, you'll find the image to flash with adb (use the flashtool from here: http://xdaforums.com/showthread.php?t=2500526)

Thanks go to gr8nole, ketut.kumajaya, unjustified_dev and n00by0815 as well as everybody at CM...

Now off to CM (?) :cool:
[Galaxy Tab 3 General] ironman38102:
May I ask how it helps in developing in CM

EDIT: Also if u want people to flash that using odin ull need to make tar.md5 of it to flash it through odin

Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
[Galaxy Tab 3 General] gr8nole:
Flashed it (with Flashify) and it booted much faster than mine, but the external sd card isn't recognized. Take a look at the recovery.fstab to see how we have it.

Edit: I have fat32 formatted card.

Edit #2: I see you have sdcard managed by vold and in your fstab you have /storage/sdcard1. In the vold I believe it is /storage/extSdCard. I might be wrong, but that may fix the issue (can't look too closely, I'm in an airport right now)

Sent from my DROID RAZR MAXX HD
[Galaxy Tab 3 General] :
For starters I began porting with this guide: http://wiki.cyanogenmod.org/w/Doc:_porting_intro it recommends to build a recovery image first - so I did. It makes sense: if you are able to build a working CWM, it means that your build environment is set up correctly and your config files (BoardConfid.mk, init.rc, fstab) are correct up to the point that a base system (recovery) is running. To run CM there is a lot more files to consider, more configs, more drivers, more deamons to run... Once you know your base system is able to run, you can try to hunt bugs/errors one after the other. With a non booting system, the bug could be in every subsystem.

As to flashing by odin - I'm not a big fan of it, I find it pretty messy. I did't have the time to build zip's and tar.md's. Maybe I'll do it when I find the time - but using Flashify or adb or n00b0815's script actually isn't that complicated as long as you have your tab rooted, its even simpler than odin.

Let's say, you have root on your tab and the Samsung drivers installed on your pc:

Get the script from the post linked above, unzip.

Put the recovery.img in the same folder (it has to be named "recovery.img", overwriting the old one).

Connect the tab to the computer (booted normally, USB debugging enabled) and run the flashing script.

done ;)

Thanks, I already noticed that. Mounting still is an issue. I think I barely got a working fstab. I'm not sure if CM10.2 is compatible with the old fstab format but this is something I'll definitely work on, once I have the time. I'm not sure if the mount point is a problem, but actually I don't really understand vold (now THAT might be a problem ;) ). I'll check it out. It's getting late here. (Hm...testing from an airport - now that's what I call commitment ;) )
[Galaxy Tab 3 General] ketut.kumajaya:
[MENTION=5505894]k.aibutsu[/MENTION] Thank you for using my kernel and modules source. I call this a commitment to open source software, a collaborative work is always better :good:
[Galaxy Tab 3 General] gr8nole:
I finally got external_sd to mount correctly. recovery.img attached. It is the recovery you made with a few modifications. Feel free to unpack the .img and run a diff to see the changes (I use Android Image Kitchen to unpack).:good:
[Galaxy Tab 3 General] :
Thanks, I got it working, too. Added it by hand to fstab. I think the vold-managed line just isn't working, maybe I'll figure it out when trying cm, for now I commented it out. I checked out your ramdisk, did you change anything else but fstab and init.rc? I added the "export SECONDARY_STORAGE" line from yours.

BTW: First CM build was successful, now I'll have to find out what blobs to pull.

EDIT: Just flashed the recovery with a changed fstab and init.rc (see above). external_sd seems to be mounted ok, "Mount usb storage" is a stub for now (before it resulted in a freeze). I think, I'll leave it with that for the moment.

EDIT2: recovery.img attached
[Galaxy Tab 3 General] gr8nole:
I also had to add fstab.pxa988 file to get it to work for me.
[Galaxy Tab 3 General] :
Ah, ok, I added a copy command for it to AndroidBoard.mk, I think.

Progress: Trying to build my first "usable" version with vendor files...
[Galaxy Tab 3 General] safariking:
What do you mean by building first usable version?

Cyanogenmod or CWM?
[Galaxy Tab 3 General] :
Cyanogenmod. But don't get your hopes up just yet, I'm 95% sure it won't work with a 50% chance (estimate) of not even booting :fingers-crossed:

EDIT: So - to clarify: "usable" to flash for trial and error booting
[Galaxy Tab 3 General] N00BY0815:
How did the building go?
[Galaxy Tab 3 General] jetboss:
Wondering that myself