yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 7.0 Android Development] wranglerray:
The issue is the extract-files.sh are board dependant. There isn't a universal extract-files.sh file. The cyanogen mod wiki says to create your own.

Sent from my HTCONE using Xparent BlueTapatalk 2
[Galaxy Tab 3 7.0 Android Development] bensonhsu2008:
The issue is you can only run that file when your device is running cm10. Otherwise you have to pull it all out yourself.
[Galaxy Tab 3 7.0 Android Development] Zidkijah:
Crap....... that's where I went wrong then......
[Galaxy Tab 3 7.0 Android Development] N00BY0815:
I ll try to build cm 10.2 btw ;) repo is still syncing... takes more than 12 hours already :p I guess thats the disadvantage, of living on the countryside :/ will keep you guys posted, as soon, as I have got anything new ;) good luck for the rest who is trying as well :thumbup:
[Galaxy Tab 3 7.0 Android Development] fabi280:
I've got a fairly good connection and could do a build for you. I'm building PA nightlies for mako but I also keep my cm sources synced. So I'd just need your local_manifest (including your device trees repo) to do a build for you. Would take around 2 1/2 hours I guess...
[Galaxy Tab 3 7.0 Android Development] N00BY0815:
Thanks for the offer, I really appreciate it, but I am @ work currently... I ll see, if it already finished syncing after work and if it did, I ll try my luck. As soon, as I have all the stuff needed, I ll get a git setup, so everyone can join in and also try his luck ;) I gotta confess, I am also still a noob concerning this whole cm build thing. So dont get your hopes up too high. But I am still convinced, that we can get it done together ;)
[Galaxy Tab 3 7.0 Android Development] bensonhsu2008:
Just synced the new source!
[Galaxy Tab 3 7.0 Android Development] fl4m3y:
Sounds quite good what you guys are planning! Keep up and redeem us from the "amazing" Samsung Firmware

Gesendet von meinem GT-I9300 mit Tapatalk 4
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Could someone send me stock boot.img and stock recovery.img for smt210R? Also a system dump. Trying to do something before I get it. I could only find these things for smt211.

I am working on cm-10.1
[Galaxy Tab 3 7.0 Android Development] wranglerray:
https://dl.dropboxusercontent.com/u/73987477/boot.img

https://dl.dropboxusercontent.com/u/73987477/recovery.img

system dump is in general

http://xdaforums.com/showthread.php?t=2381437
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
That can't be stock recovery.img it won't unpack but the one I got from t211 unpacks but its not the same tab. Weird if it is stock though
[Galaxy Tab 3 7.0 Android Development] Tomsgt:
Watching this thread closely. keep up the Good work.
[Galaxy Tab 3 7.0 Android Development] wranglerray:
yep sorry about that its the cwm recovery I ported. Restoring my tab to stock so I can pull it out for you
[Galaxy Tab 3 7.0 Android Development] fabi280:
Would it help if I post the boot.img & recovery.img from a Sammobile Firmware File for Odin?

I'm downloading this right now:

[B]Model:[/B] SM-T210R
[B]Country/Carrier:[/B] Unknown
[B]Date:[/B] 2013 August
[B]Version:[/B] 4.1.2
[B]PDA:[/B] T210RUEAMG4
[B]CSC:[/B] T210RXACAMG4
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Yes please
[Galaxy Tab 3 7.0 Android Development] fabi280:
It will be down in like a quarter hour (hotfile sucks, limits maximum bandwith).

For the meantime I can provide you the files of the SM-T210 (without R, the European Version):

https://www.dropbox.com/sh/kr7odhr3cwt1tuu/5BRJRzRTuK
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
I just found and downloaded the 210r stock from sammobile
[Galaxy Tab 3 7.0 Android Development] fabi280:
Download just finished...

Here are the files: https://www.dropbox.com/sh/gukpjfvvs9h4hgw/N_0XXDumVf

Maybe this is faster for you
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Mine finished already :p but thanks its hard to find stuff when models are all together like this. That link may benefit the next person
[Galaxy Tab 3 7.0 Android Development] iceandfire:
Anyone has device props that they can share? I'm starting the work with the tab and wanna know if I should start from scratch or just try to fix it.
[Galaxy Tab 3 7.0 Android Development] N00BY0815:
I started from scratch... took the empty device tree, althpugh i dont know, which blobs need to be pulled, since they all have different names, than the SII or the tab 2 7.0.
[Galaxy Tab 3 7.0 Android Development] Zidkijah:
That's where I'm at also........ Just scrapped everything and started over......... So how do I pull them from my Tab? I can share the output :)
[Galaxy Tab 3 7.0 Android Development] wranglerray:
i believe they should be in system/lib/hw

and also vendor/lib/hw.

i keep getting errors trying to pull them through adb

maybe someone with a little more experience porting cm could point us in the right direction
[Galaxy Tab 3 7.0 Android Development] mythi:
i have tab 2 i could pull then for you guys ??
[Galaxy Tab 3 7.0 Android Development] wranglerray:
unfortunately no

tab 2 is omap and tab 3 is exynos.
[Galaxy Tab 3 7.0 Android Development] mythi:
but isn't tab3 7.0 a marvell chipset ?

tab3 8.0 exynos ?

and tab3 10.1 intel x86 ?
[Galaxy Tab 3 7.0 Android Development] gr8nole:
Yes, 7in is Marvell

Sent from my DROID RAZR MAXX HD
[Galaxy Tab 3 7.0 Android Development] Zidkijah:
Here is my GIT with the blobs that I was able to pull........ so far

https://github.com/chpettit/Samsung
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Those aren't proprietary not all of them at least you need files from bin , etc , lib , vendor , and more. It's not yet worth finding blobs until your source is finished. Once cm gets to the logo and with an insecure boot.img a log will tell you all missing files btw someone send me a logcat from stock rom while its booting.

These aren't proprietary in system/lib/hw

*local_time.default.so

*gralloc.default.so

*audio.primary.default.so

*audio.a2dp.default.so

*audio_policy.default.so

*keystore.default.so

*power.default.so

*gps.default.so

Anything with default is compiled from source. I have a pretty good start of source but to identify libs I need a full logcat doesn't have to be on boot just start logcat with adb logcat>logcat linux only open a new tab tail -f logcat just go through the system opening things like camera , adjusting sound , and hardware related things. Same directory you started logcat there will be a txt file named logcat send that my way please. The reason its hard to identify them is because of the new processor samsung went with.
[Galaxy Tab 3 7.0 Android Development] wranglerray:
you need a logcat no filters?
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
No filters :)
[Galaxy Tab 3 7.0 Android Development] wranglerray:
running right now in eclipse, will post in a few

here is a log cat of accessing camera, turning on and off bluetooth, audio, wifi. also adjusting vol
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
I need one on boot now just unzip this and dd flash or it or use heimdall I cant make it odin flashable. This is an insecure boot.img with adb enabled
[Galaxy Tab 3 7.0 Android Development] wranglerray:
boot logcat

used dd if=/sdcard/insecureboot.img of=/dev/block/mmcblk0p9 to flash boot img
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Thanks just reading the proprietary files with a hex editor to see what files they depend on I have already identified the basic hw .
[Galaxy Tab 3 7.0 Android Development] wranglerray:
If there is anything I can help with let me know

Sent from my SM-T210R using Xparent BlueTapatalk 2
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
I need cat proc/partitions now to get the partition sizes I still never learned how to get the max number of partitions if you know how that would be great
[Galaxy Tab 3 7.0 Android Development] wranglerray:
boot - 12288 mmcblk0p9

system - 1472512 mmcblk0p14

efs - 12288 mmcblk0p6

cache - 204800 mmcblk0p15

data - 5640192 mmcblk0p17

recovery - 12288 mmcblk0p10

bootloader - 4096 mmcblk0p5

modem - 12288 mmcblk0p8

preload - 204800 mmcblk0p16
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
I still need the output from the actual command :p. That's helpful too
[Galaxy Tab 3 7.0 Android Development] wranglerray:
cat /proc/partitions

7 0 10427 loop0

7 1 4190 loop1

179 0 7634944 mmcblk0

179 1 1024 mmcblk0p1

179 2 1024 mmcblk0p2

179 3 4096 mmcblk0p3

179 4 4096 mmcblk0p4

179 5 4096 mmcblk0p5

179 6 12288 mmcblk0p6

179 7 8192 mmcblk0p7

179 8 12288 mmcblk0p8

179 9 12288 mmcblk0p9

179 10 12288 mmcblk0p10

179 11 10240 mmcblk0p11

179 12 16384 mmcblk0p12

179 13 4096 mmcblk0p13

179 14 1472512 mmcblk0p14

179 15 204800 mmcblk0p15

179 16 204800 mmcblk0p16

179 17 5640192 mmcblk0p17

179 48 2048 mmcblk0boot1

179 24 2048 mmcblk0boot0

179 72 15558144 mmcblk1

179 73 15554048 mmcblk1p1

254 0 10426 dm-0

254 1 4189 dm-1
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Thanks just trying to think of anything else I would need so I can work tonight. I think that may be all. Maybe a kmsg cat proc/kmsg
[Galaxy Tab 3 7.0 Android Development] wranglerray:
a last kmsg from the kernel or just a running kmsg?
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Running kmsg
[Galaxy Tab 3 7.0 Android Development] wranglerray:
here it is
[Galaxy Tab 3 7.0 Android Development] Tomsgt:
awesome work guys
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Ok before I set up my source any input on these tab models

SMT-210 without R and SMT-211 . I am confused on reviews whether one of those support 3g because our source is common according to samsung when you download the kernel it says common. On marvell site it says the PXA986 supports 3g but SMT-210R model is wifi only. Just wondering.
[Galaxy Tab 3 7.0 Android Development] bukog25:
SM T210 without R is also a wifi only tab same with T210R..:)
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Where does the t210 without r come from then? So 211 must be the 3g version then
[Galaxy Tab 3 7.0 Android Development] trazfer:
t210r is us verion of wifi only 7.0 tab 3 the R represents that it has infrared port for remote. t210 is the wifi only versions of other regions without ir port. i hope i said that right.
[Galaxy Tab 3 7.0 Android Development] N00BY0815:
The t210 without r is afaik, the european model. I dont know, if it exists on other continents as well ;)
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Thanks , ill try to add support for the sensor. Getting hard just waiting to buy this tab. Its not easy developing with no reference with its Marvell CPU. One thing I found out is that it has the latest NXP NFC 547 hardware that boasts that it transfers 2x faster. Reading through the decompiled boot.IMG it says it has LEDs as in notification LEDs? Also read it doesn't even have back light for touch key? Just wondering why they have the code in there.

Thanks as well
[Galaxy Tab 3 7.0 Android Development] N00BY0815:
I havent read through the kernelsource yet, but what if they just set the current on those leds to 0 or deactivated them in another way? Gotta check that out. Because I really havent seen softkeys yet, with no backlight at all...
[Galaxy Tab 3 7.0 Android Development] bukog25:
No, it's T210 without R that is available anywhere and t210R are available in two countries, you can check it in sammobile..:)
[Galaxy Tab 3 7.0 Android Development] wranglerray:
I dont believe the 210r supports nfc. Undersettings and more the only option is nearby devices pertaining to DLNA. there isn't an NFC enable in the settings anywhere at all. It may be refering to wifi direct at 2x faster
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
In the dump in lib/hw I found NFC.px988 and in lib I found libnfc files. Just guessing Marvell got this board from Samsung and dropped in their basic files or Samsung removed it from the operating system . I'll decompile the settings and see. Checkout the vendor files I posted in general

. Could download a NFC checker app.
[Galaxy Tab 3 7.0 Android Development] N00BY0815:
I ll probably try to use and port the sgs2 device tree, modify it, to build for a tab and add our kernel source. As we already seem to have quite good blobs already, I think this is the fastest way to start. If I succeed, I ll bring the news here, ASAP, but dont expect anything too soon. I am really tired of working all day long and will have to get up in some hours and again work all day long :p but tomorrow I ll take the evening off and work on this baby, since I really waaaaaant this thing to get going :D
[Galaxy Tab 3 7.0 Android Development] drr00t:
Hi, i have a t210 wifi version of tablet.
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Does it have ir for use as a remote control? Just need to know still setting up my source.
[Galaxy Tab 3 7.0 Android Development] Zidkijah:
The 210R does.........
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
OK so other than that they are exactly the same?
[Galaxy Tab 3 7.0 Android Development] Zidkijah:
Yes, I believe that is the case.
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
So what's your device called? Is it lt02wifi ?
[Galaxy Tab 3 7.0 Android Development] Zidkijah:
Yep, lt02wifi....that's the one.
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
That's kind of crazy . I need to think of another name that won't conflict in that case. The assert prop will still allow users to flash it if I keep lt02wifi. I'll think of something there's no build prop changes in that case . Got a system dump for your version?
[Galaxy Tab 3 7.0 Android Development] Zidkijah:
Yeah, I'll pull one in the morning and push it to git......
[Galaxy Tab 3 7.0 Android Development] 123knarf:
A i have a t210 too and cpuz say to the model it is a lt02wifixx can this help you?

Gesendet von meinem SM-T210
[Galaxy Tab 3 7.0 Android Development] fabi280:
Don't mess up with ro.product.name and ro.product.device.

Your build.prop should be exactly as this one (SM-T210)

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=JZO54K.T210XXAMGE
ro.build.version.incremental=T210XXAMGE
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Thu Jul 25 16:12:30 KST 2013
ro.build.date.utc=1374736350
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-127
ro.build.tags=release-keys
ro.product.model=SM-T210
ro.product.brand=samsung
[B]ro.product.name=lt02wifixx
ro.product.device=lt02wifi[/B]
ro.product.board=PXA986
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=mrvl
ro.build.PDA=T210XXAMGE
ro.bootloader=T210XXAMGE
ril.sw_ver=
ril.official_cscver=I8268CHNALK2
ro.build.changelist=1256430
ro.build.modelname=SM-T210
# ro.build.product is obsolete; use ro.product.device
ro.build.product=lt02wifi
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=lt02wifixx-user 4.1.2 JZO54K T210XXAMGE release-keys
ro.build.fingerprint=samsung/lt02wifixx/lt02wifi:4.1.2/JZO54K/T210XXAMGE:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# system.prop for nevocmcc
#

# System property for Default Brightness
ro.lcd_brightness=195
ro.sf.lcd_density=160

# minimum brightness value
ro.lcd_min_brightness=20

# rotation setting in potrait mode.
ro.sf.hwrotation=270

ro.kernel.qemu=0

persist.sys.storage_preload=1

ro.carrier=wifi-only

# System property for Font Clarity
persist.sys.font_clarity=0

#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=1
persist.service.blcr.enable=0
persist.sys.tools.enable=0
ro.wifi.active_roaming.enable=true
ro.tel.config.path=/system/etc/tel/
ro.sf.lcd_density=240
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.sec.fle.encryption=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.config.voip_dvfs_freq=3
ro.error.receiver.default=com.samsung.receiver.error
ro.tvout.enable=false
ro.com.google.gmsversion=4.1_r5
boot.fps=9
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
[Galaxy Tab 3 7.0 Android Development] 123knarf:
Ok this is my build.pro

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=JZO54K

ro.build.display.id=JZO54K.T210XXAMG2

ro.build.version.incremental=T210XXAMG2

ro.build.version.sdk=16

ro.build.version.codename=REL

ro.build.version.release=4.1.2

ro.build.date=Fri Jul 5 10:50:27 KST 2013

ro.build.date.utc=1372989027

ro.build.type=user

ro.build.user=se.infra

ro.build.host=S0210-12

ro.build.tags=release-keys

ro.product.model=SM-T210

ro.product.brand=samsung

ro.product.name=lt02wifixx

ro.product.device=lt02wifi

ro.product.board=PXA986

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product_ship=true

ro.product.manufacturer=samsung

ro.product.locale.language=en

ro.product.locale.region=GB

ro.wifi.channels=

ro.board.platform=mrvl

ro.build.PDA=T210XXAMG2

ro.bootloader=T210XXAMG2

ril.sw_ver=

ril.official_cscver=I8268CHNALK2

ro.build.changelist=1256430

ro.build.modelname=SM-T210

# ro.build.product is obsolete; use ro.product.device

ro.build.product=lt02wifi

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=lt02wifixx-user 4.1.2 JZO54K T210XXAMG2 release-keys

ro.build.fingerprint=samsung/lt02wifixx/lt02wifi:4.1.2/JZO54K/T210XXAMG2:user/release-keys

ro.build.characteristics=tablet

# end build properties

#

# system.prop for nevocmcc

#

# System property for Default Brightness

ro.lcd_brightness=195

ro.sf.lcd_density=160

# minimum brightness value

ro.lcd_min_brightness=20

# rotation setting in potrait mode.

ro.sf.hwrotation=270

ro.kernel.qemu=0

persist.sys.storage_preload=1

ro.carrier=wifi-only

# System property for Font Clarity

persist.sys.font_clarity=0

#

# ADDITIONAL_BUILD_PROPERTIES

#

keyguard.no_require_sim=1

persist.service.blcr.enable=0

persist.sys.tools.enable=0

ro.wifi.active_roaming.enable=true

ro.tel.config.path=/system/etc/tel/

ro.sf.lcd_density=240

ro.carrier=unknown

ro.com.google.clientidbase=android-samsung

dalvik.vm.heapstartsize=8m

dalvik.vm.heapgrowthlimit=64m

dalvik.vm.heapsize=256m

ro.sec.fle.encryption=true

ro.config.ringtone=S_Over_the_horizon.ogg

ro.config.notification_sound=S_Whistle.ogg

ro.config.alarm_alert=Walk_in_the_forest.ogg

ro.config.media_sound=Media_preview_Touch_the_light.ogg

ro.config.voip_dvfs_freq=3

ro.error.receiver.default=com.samsung.receiver.error

ro.tvout.enable=false

ro.com.google.gmsversion=4.1_r5

boot.fps=9

net.bt.name=Android

dalvik.vm.stack-trace-file=/data/anr/traces.txt

wifi.supplicant_scan_interval=255

persist.wifi_scan_interval=255

Help this ?

Gesendet von meinem SM-T210
[Galaxy Tab 3 7.0 Android Development] N00BY0815:
Not really, since both of you I guess are germans, too and you got the same model. I'd like to see a t210r build.prop though, cause maybe there is a minor difference in naming somewhere ;)

I am not yet sure, if we need 2 gits then, but we ll probably have a little problem with the infrared, as it is not available in the t210 version.
[Galaxy Tab 3 7.0 Android Development] N00BY0815:
Thanks man ;) but we ll jist need it, if we get cm running :) then we can setup a second repo for the other version (no matter, which one this will be), because I think we ll need other blobs as well. Also we ll need to change the device folder, just as in your diff. I ll start working on it in an hour, just came home from my holiday job :p
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Samsung is horrible notice the init is pxa988 I thought we had pxa986. Crazy enough our config doesn't have that keyboard its not set. It even has NFC again our board doesn't set it. I'm just wondering if they are hiding something from us. As if it didn't have those directory it would error in the log. This is crazy it even has NFC files. I'm thinking the blobs are common because it even configures 3g it sets ril path in the init. So technically these files are already universal. All we need to do is make source to accommodate the models that require gsm as its not in my overlay stayed up late 3 days working on the t210r
[Galaxy Tab 3 7.0 Android Development] trazfer:
thank for the hardwork. i am always watching your progress
[Galaxy Tab 3 7.0 Android Development] N00BY0815:
I also wondered about the board they really used... According to the kernel the 988 according to the papers and the build.prop we use the 986... So which one is it? :D maybe they are just special versions of each other (like with infrared or 3G,...) But that's really weird... How are your attempts on the empty tree? I am still trying to get it built with the i9100 tree, but so far I have nothing, since I mostly somehow screw up the whole device tree, till I have to start over again :P
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Empty??????

My tree is no where near empty now :) Please don't take this then build off of it . If you have some input or want to help I can add you to my github

https://github.com/TeamRegular/android_device_samsung_lt02wifi

I haven't yet touched the init files I will today been basically identify blobs trying to understand their bt and wifi files.

Only init I will touch today is updating the fstab to version 2 for 4.3 and reworking the sdcard init files to match most devices so it can be clean

Devices used so far S4 , s3 , grouper , flo , p5xxx , p3xxx , n80xx , and s2 .
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
So I had nothing better to do than to search google all day found two more tab 3 one is a kid version the other is SM-T210L

It has 4.2.2 it's a korean model and its source is on samsung site what I am doing. Downloading it lol

http://pdadb.net/index.php?m=specs&id=4894&c=samsung_sm-t210l_homeboy_galaxy_tab_3_7.0_wifi

Here's the kid version if your sooooo interested

http://pdadb.net/index.php?m=specs&id=4902&c=samsung_sm-t2105_galaxy_tab_3_kids

Here's it on samsung I used google chrome to translate it

http://www.samsung.com/sec/consumer/mobile-phone/tablet/lgt/SM-T210LZWELUC
[Galaxy Tab 3 7.0 Android Development] fabi280:
The strangest part is that actually LG presented that tablet

You don't know if there is a 4.2.2 Odin flushable file for it around?

Gesendet von meinem SM-T210 mit Tapatalk 4
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
No idea it was released with 4.1 Korean put 4.2.2 on it. If I can translate some pages I may be able to find it
[Galaxy Tab 3 7.0 Android Development] 123knarf:
Ok i search the Site and i think the update come via Kies. You cant download from the Site

Gesendet von meinem SM-T210
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Samsung will release an update though. This tab is too new to not get an update sites suggest 4.3 . Pretty sure they could drop 4.4 if they do we would have to wait on every custom ROM to update too. I rather continue my work than wait for something.
[Galaxy Tab 3 7.0 Android Development] Zidkijah:
Here is the dump............

https://github.com/chpettit/Samsung/tree/master/SM-T210R/sys-dump
[Galaxy Tab 3 7.0 Android Development] trazfer:
yah. plss continue.
[Galaxy Tab 3 7.0 Android Development] N00BY0815:
Did anyone already come across this?

http://www.marvell.com/communication-processors/pxa986/

And that:

http://www.marvell.com/communication-processors/pxa988/

So whatever we have got, it should be capable of usb otg and tv out somehow... maybe we need the sources from marvel, to get it going! Just imagine that... Samsung sells a low cost tab, with lots of features not enabled, just to make buyers go for a different tab... do you guys think, this might be possible? O.o

Edit: and it should have the 3G or even higher modules integrated...