yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 General] :
I'm sorry, didn't want to spam by posting everything I do ;)

Building was successfull, booting wasn't :eek: some binaries were missing and some services started that did't work. I think I'll figure it out. I feel like we're getting close to a booting version, but I might be wrong.

It seems fixable though. I can post a flashable (CWM, TWRP probably, too) .zip, in a few hours if you'd like. I reccomend building yourself though (by forking or using my repo on github via local manifest). I don't have the time to explain right now, use the CM-wiki (porting/building) and xda-university, I can go in depth in a few hours...

Reply if you're interested in bug fixing (on this non-booting version using last_kmsg). Otherwise I'll let you know as soon as I have new results.

EDIT: Here is my last kmsg, I think, the crucial part starts at line 650. It's stuck at the Samsung logo at boot. I'll continue later, gotta work :angel:
[Galaxy Tab 3 General] ironman38102:
Glad to hear theres some progress! I hope after fixing these issues itll boot. Also I wanted to ask what version ur compiling

Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
[Galaxy Tab 3 General] moomba89:
[deleted] - sorry wrong inch size
[Galaxy Tab 3 General] :
10.2 wich - just to make it even more interesting - should at some point lead to CM11. And that would mean: Kitkat :fingers-crossed:

But seriously now: Let's make 10.2 work first. Even with a booting build there will be a lot of stuff to do: audio, wifi, bluetooth, camera... :rolleyes:

I'll work on it some more tonight, I think. Right now I have to get back to (real life) work...
[Galaxy Tab 3 General] Marco Lomas:
If some help, there's a booting cm10.1 build for Razr i that has also x86 intel atom proccesors, its booting, smooth and works...a few bugs but the important works :)

Enviado desde mi XT890 mediante Tapatalk
[Galaxy Tab 3 General] N00BY0815:
This thread is about the 7 inch, not the 10 inch version...

Sorry to have to disappoint you, but maybe start your own thread about it ;)
[Galaxy Tab 3 General] Marco Lomas:
O sorry sorry, i not read good, i say that for the Tab 10.1 cause have also a x86.. I havent read that is for Tab 7, my apologize :)

Enviado desde mi XT890 mediante Tapatalk
[Galaxy Tab 3 General] ironman38102:
Please just make CM for this tab hell I care our tab gets kitkat late or early I just wanna cm on my tab.
[Galaxy Tab 3 General] trazfer:
I think we should request cm from the cm forums. So that they can also help us. I have the link to it but I dont know uf I can post it
[Galaxy Tab 3 General] ironman38102:
They wont help because they dont have the device and Im pretty sure we are getting closer to a booting version of CM

Its Going to be LEGEND--wait for it--DARY!-Barney Stinson(How I Met Your Mother)
[Galaxy Tab 3 General] glotzkowski:
i ask for ist in the cm forums to ....but no answer :( many people spend hope in the xda communtity and developer ;)
[Galaxy Tab 3 General] jetboss:
i read somewhere that requests dont really help someone has to get a booting version ported then the cm devs will step in and help get everything working ..
[Galaxy Tab 3 General] Unjustified Dev:
Who's back ready to help :D I am so busy I need to strategize my work ethic between devices. [MENTION=5505894]k.aibutsu[/MENTION] you either missed or changed something for the ramdisk. I have yet to understand the complicated ramdisk of this tab. If I were you I would only modify stock and see what you can remove and delete and improve.

Next I know every thing that needs changing from jellybean up to kitkat . I promise you if you start with cm10 it will be much easier 4.3 had lot's of code changes and the init isn't near inline for 4.2.2. I am starting from scratch to make sure all my commits are understood clearly and others are able to pickup and help

Start by forking my stock ramdisk and make changes to it and see what you can cleanup but have stock boot

https://github.com/TeamRegular/ramdisk_for_lt02
[Galaxy Tab 3 General] :
Thanks for the tip. That explains the issues I've been having with init. Problem is, now I spent endless hours on my ramdisk and am not quite ready to give up on all this work. It would be great, if you could help me with it, as I really spent a lot of time with it.

I think next thing I'll do, is try to diff my ramdisk with a working CM 10.2 build, in the end the ramdisk is only init+rcs, udevent+rcs and some images for the charging mode (I did't tackle charging at the moment, so all those *.lpm.* files, I don't really care about).

I just realized, I don't have fuse in my ramdisk...maybe that could help. I'll figure it out later.

If I keep hitting brick walls, I'll be glad to help you porting cm10.
[Galaxy Tab 3 General] Unjustified Dev:
Add me on hangouts its 4am but android.c357@gmail.com been up since 9am that's a developer :p
[Galaxy Tab 3 General] trazfer:
Why am I the only one thanking the devs haha
[Galaxy Tab 3 General] :
Hi folks!

I did't have much time today so all I got was another non-booting build. Attached you'll find my last_kmsg with loglevel 8. I'm still not sure, where the problem is.

I don't think I'll have much time the next days so maybe someone else could do something. I updated my github repo and uploaded my last build. You can find it here:

http://www.androidfilehost.com/?fid=23212708291678339

(Please remember: It's a non booting build, so you can change the ramdisk or whatever you like with Rom Kitchen - or by hand - and try to get it to boot. You will have to pull /proc/last_kmsg after rebooting into recovery.)

I also attached a last_kmsg of a booting stock rom (rooted) with loglevel 8. I used it to try to find the problem, maybe one of you will...

EDIT: added stock boot.img
[Galaxy Tab 3 General] Unjustified Dev:
[MENTION=4837581]Ironman38102[/MENTION]

[MENTION=5374236]trazfer[/MENTION] [MENTION=3489684]Zidkijah[/MENTION]

Could someone test this build of CWM and let me know how it goes based on my new device tree for cm-10.1 https://github.com/TeamRegular/device_lt02wifi

Attached the image below
[Galaxy Tab 3 General] trazfer:
Stuck at samsung galaxy tab 3 logo. I used flashify. I dunno how to get last kmsg.
[Galaxy Tab 3 General] Unjustified Dev:
It's OK I probably missed something. I'll check tomorrow time to sleep.
[Galaxy Tab 3 General] :
You get these errors:

[ 2.675811] c0 Unpacking initramfs...
[ 2.703491] c0 Initramfs unpacking failed: read error
[ 2.704162] c0 Freeing initrd memory: 1024K

[ 10.033721] c1 init: cannot find '/sbin/ueventd', disabling 'ueventd'
[ 14.974182] c1 init: Timed out waiting for /dev/.coldboot_done
[ 14.974609] c1 android_usb: already disabled
[ 14.975067] c1 init: Unable to open persistent property directory /data/property errno: 2
[ 14.976135] c1 init: cannot find '/sbin/recovery', disabling 'recovery'

I guess the second is consequential to the other. Using blackhawk kernel will fix the problem as it overrides initrd memory. I tried and found no other way to fix this. Maybe you will ;) Ask ketut.kumajaya for advice.

If you want to build the kernel and kernel modules on the fly - check my MakeConfig.mk, it's working (at least for recovery).

I added your info to mine, thanks for that. I'd still like to fork your repo but I still feel like we're having different approaches - I'll just raise issues on github.

EDIT: Full kmsg attached.
[Galaxy Tab 3 General] Unjustified Dev:
I used his kernel this time. I'll upload my source changes and compile a new recovery. About source approaches I'll fix things up to my best of ability. Just don't make huge commits if you change something make sure commit name fits it. Something like fixes isn't good. I've learned in the past month it's confusing to others who reference from your code to understand the reason for adding certain things.
[Galaxy Tab 3 General] ketut.kumajaya:
Take a look https://github.com/kumajaya/android...mmit/2f156084ddcdea962ce23d68ad6a7b191dbc0075. Make sure CMDLINE_INITRD_SIZE_OVERRIDE enabled, it's disabled by default.
[Galaxy Tab 3 General] Unjustified Dev:
I used your kernel and defconfig?

Edit: it's correct

Do you think you could implement kexec hard boot ?
[Galaxy Tab 3 General] N00BY0815:
What if you dont set it? Does the stock ROM still boot, or not? Because if not, I might go and contact Samsung and ask them to provide the actual sourcecode, they used.
[Galaxy Tab 3 General] Unjustified Dev:
I'll just leave this here
[Galaxy Tab 3 General] ketut.kumajaya:
Why not but I have no experience related to kexec.

Oh dear, CWM/CWM based recovery need a full blown busybox embedded in recovery and of course not fit in 1MB ramdisk. [MENTION=3034891]gr8nole[/MENTION] fully understand override 1MB limitation (this value came from bootloader) is the only solution for you. Samsung and Marvell try to make all of you far away from unofficial recovery. Generally 1MB is enough for normal boot but blackhawk kernel with embedded busybox, su, and SuperSU need more.
[Galaxy Tab 3 General] Unjustified Dev:
That makes sense. Seems like we won't get far without it at all. I only wanted kexec hardboot so in the feature when we get roms I can work on getting multirom to work it writes itself into the first 256mb of ram.

https://github.com/Tasssadar/multirom/wiki/Porting-kexec-hardboot

https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM

I don't have the kernel knowledge to do so.
[Galaxy Tab 3 General] gr8nole:
Took a quick look at this recovery (didn't flash it, just looked at ramdisk).

Couple things to note:

1. If you don't incorporate [MENTION=4021423]ketut.kumajaya[/MENTION]'s touchscreen orientation fix, then any time a user flashes a zip with a touchscreen interface (such as any Aroma installer), the touch points are going to be incorrect. A line also needs to be added to the init.rc.

# Set touchscreen to landscape mode for recovery

write /sys/devices/virtual/sec/tsp/orientation 6

2. If you want the recovery to boot faster, remove this line from the recovery.fstab:

/misc	emmc	misc

I just discovered that this line is the reason it takes so long to boot into recovery (it attempts to find "misc" ten times before giving up and booting). I will be updating my recovery builds soon to fix it.
[Galaxy Tab 3 General] ketut.kumajaya:
Hi [MENTION=3034891]gr8nole[/MENTION], thanks for the misc info :good:
[Galaxy Tab 3 General] ironman38102:
Finally the slow booting bug is fixed! Thanks gr8nole
[Galaxy Tab 3 General] jetboss:
Glad to see all the progress being made although this is not for my device I know if we getting everything working a gsm port won't be far behind keep up the good work guys
[Galaxy Tab 3 General] Unjustified Dev:
Thanks , could you upload the ramdisk from your recovery so I can incorporate it into my init.recovery.pxa988.rc I decided to use stock recovery init.rc and create a device init to load exfat . I guess i'll add those lines too.

Actually I have figured out the touchscreen fix it's becaue of init_charging in the boot.img it loads power_saving.sh or whatever inside bin and that disables touchscreen they inteded it for lpm but I guess somehow it gets executed into recovery the fix in my code was to remove that code because on lpm based on aosp we write powersave to make it charge faster k.a.... tested it and said it charges offline without it.
[Galaxy Tab 3 General] Unjustified Dev:
sadly we removed all gsm files from code. We are you trying to eliminate the common files and make it centralized my idea is to only support tablets users have.

Most have t210 and t210r

Also we don't know how everything works with the gsm model. The marvell files are so strange.

Eventually after those models boot my cwm we can try to build a rom and then make source for gsm model.

This won't be easy

Does your model have nfc and infrared? I removed nfc code and the R model has infrared.
[Galaxy Tab 3 General] jetboss:
Nope mine is the 211 3g model doesn't have the ir blaster or nfc
[Galaxy Tab 3 General] Unjustified Dev:
Thanks that makes it even easier because between the 3 no one seems to have a korean model with nfc ,ir ,and 3g .
[Galaxy Tab 3 General] jetboss:
Wish I could help you guys in some way I usually have lots of time in front a pc because of my job
[Galaxy Tab 3 General] gr8nole:
Ramdisk attached
[Galaxy Tab 3 General] jetboss:
OK no problem but I'm using twrp recovery is that a problem also how do I go about doing this sorry I'm a noob but I learn fast
[Galaxy Tab 3 General] gr8nole:
If you haven't seen it yet, I updated my CWM build to 6.0.4.5. Now has swipe interface. :)

Sent from my DROID RAZR MAXX HD
[Galaxy Tab 3 General] jetboss:
Nice
[Galaxy Tab 3 General] Unjustified Dev:
Could you push your cwm device source to github?
[Galaxy Tab 3 General] gr8nole:
I'll get it up there tomorrow. It's really just [MENTION=5505894]k.aibutsu[/MENTION]'s source and your source merged with a few small ramdisk edits.

Sent from my DROID RAZR MAXX HD
[Galaxy Tab 3 General] Unjustified Dev:
Thanks , can't wait to see it.
[Galaxy Tab 3 General] :
Yes, I'm interested, too. Would also be nice to get some credit in your thread ;)

I'm still trying to figure out the error with my ramdisk. I just can't get CM to boot :(

Do you think it needs wifi, sound, bluetooth etc. to boot?
[Galaxy Tab 3 General] Unjustified Dev:
It needs to initialize low level things to boot. Basically the android default things and a few device specific things. It also needs to load certain drivers/blobs.
[Galaxy Tab 3 General] :
I just flashed your recovery. Find last_kmsg attached. Boots but screen resolution is something like 800*600 or so ;)
[Galaxy Tab 3 General] jetboss:
Its booting woottttt that's great news
[Galaxy Tab 3 General] gr8nole:
Credit now given to you both in the threads for CWM 6.0.4.5. :o Should have done it yesterday (too many recovery threads to update).
[Galaxy Tab 3 General] glotzkowski:
sounds good ;) ....hope see your work soon ;)
[Galaxy Tab 3 General] ironman38102:
So is the CM for our tab is somewhat near to a booting build? What are the current issues?

Its Going to be LEGEND--wait for it--DARY!-Barney Stinson(How I Met Your Mother)
[Galaxy Tab 3 General] ketut.kumajaya:
Tab 3 8.0 was more fortunate: http://xdaforums.com/showpost.php?p=47659322&postcount=59
[Galaxy Tab 3 General] :
I don't think that's a big surprise, the 8 inch tab is runs on an Exynos 4212, that means more similarities to the N7100 (Exynos 4210) and developed directly at samsung so better hardware support and "cleaner" config files. Plus it already runs 4.2 (CM 10.1), the 7 inch only runs 4.1 (CM 10). IMHO the 7 inch tab was produced as a low budged device with cheap hardware from a third party manufacturer and sloppy software design. I don't think we can expect much support...:rolleyes:

That only means that we have to work harder ;)
[Galaxy Tab 3 General] jetboss:
Lol love you guys conviction
[Galaxy Tab 3 General] ketut.kumajaya:
Yes, no Marvell reference out there :(
[Galaxy Tab 3 General] gr8nole:
My device source is now on github. Like I mentioned earlier, not a whole lot of changes from you guys already had.

https://github.com/gr8nole/device_lt02wifi
[Galaxy Tab 3 General] :
Nice, thanks. As far as I can see, there's not much change. Did you intentionally load exfat modules twice in recovery.fstab?

IMHO you can delete/comment out wlan and bluetooth modules/drivers from BoardConfig.mk as it won't build CM with it and it's not used in CWM. I think we will need it later, but for now, it's no use. (Know this just by trial and error) :p
[Galaxy Tab 3 General] gr8nole:
Not intentional, probably just missed the first instance of loading them.

Sent from my DROID RAZR MAXX HD
[Galaxy Tab 3 General] Unjustified Dev:
Those WiFi defines need looking at. I'll start adding more code tonight.

Just putting it out there thanks to guys from free scale they even modifed the wifi daemon for pxa988

https://github.com/TeamRegular/andr...mmit/4884e23dbf760c2edd792557216f39b0b90fbdc0

This is what stock uses for wifi MRVL_WIRELESS_DAEMON_API

I added it just incase we can't get wifi to work using BOARD_HAVE_MARVELL_WIFI

I love these guys

https://community.freescale.com/message/362342#362342

We have that too . Please create an account with me. I've had one for over a month and these guys know about marvell and maybe have some code we can look at
[Galaxy Tab 3 General] gr8nole:
Not sure how far you guys have gotten as far as booting, but I compiled my first attempt tonight (CM 10.2) and got the CM boot animation and it look like it tried to boot into the system. A white screen with CM in the top corner (maybe a setup screen) kept appearing and disappearing. Probably some sort of graphics issue. Anyways, I thought that was pretty good for a first attempt.
[Galaxy Tab 3 General] Unjustified Dev:
Nice :) maybe you should logcat :p may need some more work
[Galaxy Tab 3 General] gr8nole:
Tell me how to get a logcat?

I did pull last_kmsg after booting back into recovery. But without USB debugging enabled, how do I get a logcat?
[Galaxy Tab 3 General] Unjustified Dev:
open terminal type adb devices if nothing is there the system has loaded :) you will need to type adb logcat while it boots. If it says offline unpack the boot.img add this to default.prop

ro.secure=0
ro.adb.secure=0
ro.debugabble=1
[Galaxy Tab 3 General] gr8nole:
Tried it and adb never found any device connected.
[Galaxy Tab 3 General] Unjustified Dev:
Sad just :( maybe it's usb related to init.pxa988.usb.rc send me kmsg i'll look at
[Galaxy Tab 3 General] gr8nole:
last_kmsg attached.
[Galaxy Tab 3 General] Unjustified Dev:
It appears to have had no issues. I am new to kmsg so I wouldn't know much. One thing I noticed is the lack of selinux and audit enabled. I am thinking it's issues related to the device. Only a logcat knows btw add me on hangouts android.c357@gmail.com

Enabled SELinux and audit https://github.com/TeamRegular/andr...mmit/0c6cf5fd917cfdc78e5ce415bb47e78614c55b7c

Building kernel from source now :)

https://github.com/TeamRegular/device_lt02wifi/commit/b6936d42814b3e659c311e4b81b1538ee3c77780

Your source is missing ton . It has none of the essential android device configurations

https://github.com/TeamRegular/device_lt02wifi/blob/cm-10.1/device.mk

Notice how much is missing those permissions are needed
[Galaxy Tab 3 General] ketut.kumajaya:
Audit and SELinux optional, not a requirement.

For adb access, try add persist.sys.usb.config=mtp,adb to default.prop or from recovery with mounted /data partatition: "echo -n "mtp,adb" > /data/property/persist.sys.usb.config" .
[Galaxy Tab 3 General] Unjustified Dev:
I was just adding it to make sure everything will be working in time. I am now updating my code to kitkat. Seems like progress is starting to take place. I have eliminated some unneeded things. I'll add that too
[Galaxy Tab 3 General] :
This is actually further than I ever got. I never got to the boot logo, only black screen after Samsung logo...Did you build the kernel from source or did you use stock kernel?

I also got a lot of messages from binder in my kmsg, right now I messed up my config, /system/ isn't mounted...now I have to figure out why...
[Galaxy Tab 3 General] gr8nole:
From source, Blackhawk.

Sent from my DROID RAZR MAXX HD
[Galaxy Tab 3 General] ironman38102:
Well its nice to see some progress but are the graphical glitches are happening due to some cpu/gpu binaries missing?

Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
[Galaxy Tab 3 General] gr8nole:
Tried both methods and still no adb access (except in recovery).
[Galaxy Tab 3 General] :
Try copying my default.prop to out/.../root/ and build again or try reforking/diff'ing my repo it should build with adb support. I already got some egl and gfx errors fixed but still blank screen. I am not using the right build tools though - maybe thats it...or it's because I have the T210...

EDIT: I had to remove automatic build of default.prop (doesn't work ;) ). You'll have to copy/edit it by hand in the out-directory and then rebuild.
[Galaxy Tab 3 General] fabi280:
Nice that you got such far! You guys are awesome!

[MENTION=3034891]gr8nole[/MENTION] maybe you could upload your build so [MENTION=5505894]k.aibutsu[/MENTION] and unjustified Dev could take a look at it and even try to get adb access to it

Gesendet von meinem Nexus 4 mit Tapatalk
[Galaxy Tab 3 General] Unjustified Dev:
Hopefully fixes undetected usb on boot https://github.com/TeamRegular/andr...mmit/1a8586c08df17b53e171b966256616f709551c77

Had same issue with my other phone. It's samsung garbage .
[Galaxy Tab 3 General] ketut.kumajaya:
I was got a slow graphics issue on my binary level hacked Slim Bean on Tab 3 8.0 and found the solution based on my experience in Tab 2. I will try to find a way how to add vsync_time sysfs to Marvell framebuffer driver if not exist.

---------- Post added at 07:14 AM ---------- Previous post was at 07:09 AM ----------

That's the reason way my dual boot kernel has a capability to switch the MTP mode on boot but forgot to inform it here :(
[Galaxy Tab 3 General] :
Maybe you already knew that but you can also override Ramdisksize by adding the following lines to your _defconfig:

CONFIG_CMDLINE="initrd=0x01100000,4m rw panic_debug uart_dma vmalloc=0x10000000 qhd_lcd=1 crashkernel=4k@0x8200000 atcmdmode=1 androidboot.emmc_checksum=3 androidboot.serialno=[androidboot.serialno] board_id=0x05 panel_id=0x00000001 disp_start_addr=0x17000000 ddr_mode=1 androidboot.debug_level=0x4f4c cordon=[cordon] version=Sbl(1.0.0) 2013-05-20 17:46:09"
CONFIG_CMDLINE_FROM_BOOTLOADER=n
CONFIG_CMDLINE_FORCE=y

This will boot into recovery without the need for INITRD_SIZE_OVERRIDE but result in the strange graphical glitch. I believe this is because graphical memory isn't allocated correctly. At the moment I am trying to build with stock kernel (they actually had a typo in their sources...sloppy work...).

The CMDLINE is taken from stock ("initrd=0x01100000,1m" changed to "initrd=0x01100000,4m"), I don't really see, what option is necessary. I know that

CONFIG_CMDLINE="initrd=0x01100000,4m rw board_id=0x05 panel_id=0x00000001 disp_start_addr=0x17000000"

will work, too (with graphical glitch).

[MENTION=4021423]ketut.kumajaya[/MENTION]: I think ION-Support is needed on our tab and actually stock kernel has some ION stuff inside. You made a patch to ION memory carveout. Could you explain, why you did this? Is this why recovery acts strange?
[Galaxy Tab 3 General] ketut.kumajaya:
Please check, when you got recovery graphic glitch, there's no "recovery" key in cmdline. Maybe the bootloader failed to set the "recovery" key to cmdline or bootloader bug! The known solution is reboot to recovery using "reboot recovery" command. Of course without your above config, I used it before but opening [MENTION=3034891]gr8nole[/MENTION] device serial number to the world is a bad idea.

About the ion hack, device with older bootloader needed it. The latest kernel need ion memory size from bootloader cmdline but no ion memory size value in older version. Without ion, you will got a blank popup window as reported by [MENTION=3034891]gr8nole[/MENTION].