yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 7.0 Android Development] A6ekAK:
Waait, what?!
[Galaxy Tab 3 7.0 Android Development] ketut.kumajaya:
So Italy ROM for T211 from http://samsung-updates.com/device/?id=SM-T211 is a leaked/unofficial version?
[Galaxy Tab 3 7.0 Android Development] safariking:
I think it is a leaked version related to the bugs.
[Galaxy Tab 3 7.0 Android Development] ketut.kumajaya:
T21x owner not as luck as T310 owner :crying:
[Galaxy Tab 3 7.0 Android Development] HerroYou:
[MENTION=3034891]gr8nole[/MENTION] I saw from bensonhsu2008's port rom t211 to T210(R) that the WIFI is working, couldn't you look at his sources for the WIFI fix?
[Galaxy Tab 3 7.0 Android Development] rogersb11:
You could. That'd be really helpful
[Galaxy Tab 3 7.0 Android Development] gr8nole:
He doesn't have sources for that rom that we can use. That is just a stock rom that had a few adjustments to work with T210.

Sent from my SCH-I605
[Galaxy Tab 3 7.0 Android Development] HerroYou:
https://github.com/bensonhsu2013?tab=repositories :P
[Galaxy Tab 3 7.0 Android Development] gr8nole:
Thanked by mistake. ..

Just because he has a github doesn't mean he has sources that will help.

He did not compile that rom, he ported it from stock firmware. Big difference.

Sent from my SCH-I605
[Galaxy Tab 3 7.0 Android Development] bensonhsu2008:
Should be helpful.

https://community.freescale.com/thread/311138

I'd like to share my driver porting on iMX6 android 4.2.2 with you.
1. my wireless relevant code on BoardConfig.mk:
TARGET_KERNEL_MODULES := \
kernel_imx/net/wireless/cfg80211.ko:system/lib/modules/cfg80211.ko
BOARD_WPA_SUPPLICANT_DRIVER := NL80211
WPA_SUPPLICANT_VERSION := VER_0_8_X
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_mrvl8787
BOARD_HOSTAPD_DRIVER := NL80211
BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_mrvl8787
BOARD_WLAN_DEVICE := mrvl8787
BOARD_WLAN_VENDOR := MRVL
WIFI_SDIO_IF_DRIVER_MODULE_PATH := "/system/lib/modules/mlan.ko"
WIFI_SDIO_IF_DRIVER_MODULE_NAME := "mlan"
WIFI_SDIO_IF_DRIVER_MODULE_ARG := ""
WIFI_DRIVER_MODULE_PATH := "/system/lib/modules/sd8xxx.ko"
WIFI_DRIVER_MODULE_NAME := "sd8xxx"
WIFI_DRIVER_MODULE_ARG := "drv_mode=5 cfg80211_wext=0xc sta_name=wlan uap_name=wlan wfd_name=p2p max_uap_bss=1 fw_name=mrvl/sd8787_uapsta.bin"
WIFI_DRIVER_FW_PATH_PARAM := "/proc/mwlan/config"
WIFI_DRIVER_FW_PATH_STA := "drv_mode=5"
WIFI_DRIVER_FW_PATH_AP := "drv_mode=6"
WIFI_DRIVER_FW_PATH_P2P := "drv_mode=5"

2. Attached files:
wifi.zip->/hardware/libhardware_legacy/wifi
marvell.zip->/hardware/imx/wlan

You should note that I just write different drv_mode to sd8xxx.ko driver to change different sta/uap/p2p mode. Details in wlan_src/readme_mlan:
The bit settings of drv_mode are,
Bit 0 : STA
Bit 1 : uAP
Bit 2 : WIFIDIRECT

3.Add a framework overlay file on product makefile
/frameworks/overlay/core/res/res/values/config.xml
Edit that option:
<!-- List of regexpressions describing the interface (if any) that represent tetherable
Wifi interfaces. If the device doesn't want to support tethering over Wifi this
should be empty. An example would be "softap.*" -->
<string-array translatable="false" name="config_tether_wifi_regexs">
<item>"wlan.*"</item>
</string-array>
Note that bolded "wlan.*" match my wlan interface name "uap_name=wlan" (BoardConfig.mk). Since Android does not support WiFi station and uAP mode simultaneously, It does not matter we have the same interface name for station and uAp (sta_name=wlan uap_name=wlan).

Extracted from the post.
[Galaxy Tab 3 7.0 Android Development] Lincoln99:
I think I'll try to get Bluetooth working.
[Galaxy Tab 3 7.0 Android Development] sjsharksfan420:
My apologies if this is mentioned, but I just got the Alpha3 build from 6/28 flashed, no problems with installation, but I can't get WiFi to work. Is it known or should I try again?

sj
[Galaxy Tab 3 7.0 Android Development] ironman38102:
This is a known issue. Developers are working to fix the bugs.
[Galaxy Tab 3 7.0 Android Development] sjsharksfan420:
Cool thanks for the post! I knew this is a work in progress, just wasn't sure if WiFi was supposed to work or if I had a bad flash.

sj

Sent from my Customized & Carbonized S4 (SPH-L720) - 7/01/14 aOS 4.4.4 with KTkernel 7/12 using Tap@Talk HD Pro Mobile App

4.X based CarbonROM - $J$harksfan Customized
[Galaxy Tab 3 7.0 Android Development] DHeavy2011:
Working Galaxy Tab 3 T210(R)

Guys there's a working Kitkat rom for us here

https://s.basketbuild.com/devs/safariking
[Galaxy Tab 3 7.0 Android Development] ajws7036:
does it work? wifi and all?
[Galaxy Tab 3 7.0 Android Development] DHeavy2011:
Yes. Absolutely everything works. The only annoying thing is it shows the no service/data symbol and I can't figure out how to remove the dialer and everything but it is stable. I'll work on removing the annoying things
[Galaxy Tab 3 7.0 Android Development] tharmor:
Where is the original thread for this ? Any installation steps ??
[Galaxy Tab 3 7.0 Android Development] DHeavy2011:
http://xdaforums.com/galaxy-tab-3/development-7/rom-kitkat-t210-port-t2819256

That's the original thread. There's really no steps. The steps though are

!) Root your Galaxy Tab 3 T210(R) if you aren't already rooted

2) Install TWRP, Philz Touch, or Clockworld Recovery (I used TWRP) if you haven't already

3) Then just locate where you placed the zip and flash it
[Galaxy Tab 3 7.0 Android Development] A6ekAK:
As far as I know root isn't needed to install recovery.

Also wiping after installing KK is good option.
[Galaxy Tab 3 7.0 Android Development] DHeavy2011:
Oh yeah you're actually right but rooting isn't a bad idea. Might as well root if you're installing custom recovery.

So to the dude who wanted instructions if you don't want to root just install custom recovery and you do that with Odin
[Galaxy Tab 3 7.0 Android Development] tharmor:
Working like a treat....thanks guys....
[Galaxy Tab 3 7.0 Android Development] TRNSLN:
No bootanimation

At first many thanks for this ROM and your effort to bring this piece of work to all Tab 3 users. I just flashed the ROM. There is no bootanimation or my device doesn't support it. By the way I've a T210 without R. Maybe I've to flash a 4.2.2 rom before flashing this ROM??
[Galaxy Tab 3 7.0 Android Development] Lincoln99:
Boot animation doesn't work for me either, I have the SM-T210R.

Sent from my SM-T210R running Android 4.4.2
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Could you guys post in the thread of the port please so we can keep things a bit organized.

[MENTION=3034891]gr8nole[/MENTION] I haven't slept it's past 24 hours I have been working on new device trees and patches.

I haven't yet tested it fully but it compiled cwm.

lt02wifi

lt02wifiue

lt02-common

pxa986-common

marvell-common

Based on t211

vendor

I did all this from your source

The wifi defines were wrong WIFI_SDIO_IF_DRIVER.... is really WIFI_EXT_MODULE... because mlan is a dependency that the sd8xxx module needs you can see the changes in pxa986-common

I also defined BOARD_WLAN_DEVICE := mrvl

You can see why in this patch

Mrvl support in wpa_supplicant

You can get wifi and bt implementation as well

libhardware_legacy

mrvl wlan

mrvl bt

Camera untested commit

Cam Patch

Still need to add those mrvl patches for hwcomposer though
[Galaxy Tab 3 7.0 Android Development] :
qmage, /system/media

run logcat -dC and look for red entries E\ blah

see if there are messages pertaining to qmage

also check /system/media perms for directory and sub-directories 755 and individual files 644

m
[Galaxy Tab 3 7.0 Android Development] gr8nole:
Great...I'll definitely check these out.

Sent from my SCH-I605
[Galaxy Tab 3 7.0 Android Development] tharmor:
Found a bug.....

Screen brightness flickers once battery goes below 5%....cannot use it below 5%
[Galaxy Tab 3 7.0 Android Development] kwood129:
Then dont use it below 5%
[Galaxy Tab 3 7.0 Android Development] rogersb11:
Well duh but the point of a development thread is to report issues or things might go unnoticed. Developing is more work than you can imagine
[Galaxy Tab 3 7.0 Android Development] TRNSLN:
If screen flickers under 5% that's normal. You have to charge it if it 20% or lower. That's the #1 rule of Lion batteries....
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
I've finally got an email back from Marvell I've sent at least 3 the past year. They sent me in the right direction on obtaining the source code. I've only asked for patches to android 4.4. We don't really need open source Marvell files and I'm sure some how posting their code is against NDA without their consent. I don't want to risk that and most of the time we always use pre-built files anyway.
[Galaxy Tab 3 7.0 Android Development] hunting_:
Can I flash this rom in my smt211?
[Galaxy Tab 3 7.0 Android Development] A6ekAK:
No, it's only for T-210 and R version, not 211.
[Galaxy Tab 3 7.0 Android Development] TRNSLN:
Now we got a perfectly working KitKat on our Tab's with thanks to all participated devs... Next step will be a stable working CM 11 I think :o
[Galaxy Tab 3 7.0 Android Development] migui0401:
Wifi is not working here, i flashed the rom (Alpha 3) and minimal gapps for android 4.4.4. May the gapps be the problem of the very very low perfomance and wifi not working?
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
I don't want to go in depth if you don't already know how difficult Marvell and vivate hardware are just know it's not as easy as other such as exynos , tegra , or Qualcomm
[Galaxy Tab 3 7.0 Android Development] tharmor:
This is android 4.4.2 and not 4.4.4.....
[Galaxy Tab 3 7.0 Android Development] ironman38102:
Wow we have CM now? Well good luck devs for fixing the bugs. Tester available here btw!
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Alright, I applied your changed today (on namelessROM, though, but this shouldn't matter at all) but I still can't get wifi running...

If i unload mlan.ko, then insmod it again as well as sd8xxx.ko, I get 3 new interfaces mlan0, uap0 and wfd0 (not wlan0 and p2p0 as on stock). iwconfig tells me that uap0 would be a wireless device @ 2.437 GHz, which would fit WiFi. But no matter what I try, I just can't get it running...

Any ideas on that? Cause I'm out of ideas for today...
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Good news guys, I finally managed to get wifi running :victory: BUT the service dies instantly. What this means is, I was able to get all needed network interfaces up the way they should be and I even was able to run a quick scan of my surrounding wifi networks. And luckily it recognized all available networks, including the 5GHz ones.

On the downside, I made a ton of changes to both the device tree, blobs and I even had to get into hex editing. I need to clean my mess now and only change the files that really need to be changed. Then I can go on fixing the wifi service.

So please don't expect miracles anytime soon, I just wanted to give you a small heads-up and let you know that we pretty certainly will get wifi fully up and running ;)

In case you need some proof :p

wlan0 Scan completed :
Cell 01 - Address: 84:1B:5E:E1:72:D9
ESSID:"NETGEAR90"
Mode:Master
Frequency=2.462 GHz (Channel 11)
Quality:4/5 Signal level:-56 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:Beacon interval=100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
[...]

BTW, [MENTION=3034891]gr8nole[/MENTION] did you have any success in completely fixing the hwcomposer since we last talked about it?
[Galaxy Tab 3 7.0 Android Development] bmatney:
I just want to once again thank the devs working on this tab.
[Galaxy Tab 3 7.0 Android Development] sjsharksfan420:
Excellent news!!!!

sj

Sent from my Customized & Carbonized S4 (SPH-L720) - 8/3/14 aOS 4.4.4 with KTkernel 7/12 using Tap@Talk HD Pro Mobile App

4.X based CarbonROM - $J$harksfan Customized
[Galaxy Tab 3 7.0 Android Development] gr8nole:
Excellent news! !

No, I never did get the color format fixed after getting hwcomposer working. Got sidetracked with the kk port.

Sent from my SCH-I605
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
Have you tried BOARD_USE_BGRA_8888 := true
[Galaxy Tab 3 7.0 Android Development] gr8nole:
I have not. I'll eventually get back to working on it.

Sent from my SCH-I605
[Galaxy Tab 3 7.0 Android Development] clyder:
This is great news. If you need any help with testing stuff I am available and willing. :)
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
What do you think of "splitting forces", you look into hwcomposer and I look into all the wireless connections?

Nice, thanks :)

Alright guys, I was working on it again, and managed to get all needed network interfaces (wlan0 and p2p0) online at boot. It's pretty dirty though and I honestly don't really like it. But it works for now, and that's the most important part. With this achieved, the next step is/was to get the wpa_supplicant and p2p_supplicant up and running. p2p_suppricant is working, wpa_supplicant still refuses to work. This, however, is something one does not need the sources in order to debug it, this can be done via the wpa_supplicant.conf file and a simple adb shell (just take the according command from the /init.pxa988.rc file).

This being said, I just uploaded my latest build (NamelessROM) HERE. BUT be aware that this build is for development/debugging purposes only. You can sure give it a try and see what's working and what's not, but don't report bugs and also do not share the link elsewhere.

I also know that the init files are a bit messy, but I don''t really care about that right now. If you cleaned them, feel free to send them my way and I will update it, otherwise I will do so once everything's working.

So, anyone up for debugging? :D
[Galaxy Tab 3 7.0 Android Development] gr8nole:
Sounds good. It's going to be a while before I get back to this though. I've got family in town all week.

Sent from my SCH-I605
[Galaxy Tab 3 7.0 Android Development] svicenty:
Wow you got to get wifi on this bad boy working looks great the nameless ROM and runs smooth
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
No wifi for me sadly

edit: Going to work with this if I can't get kikat blobs to initialize egl it's failing as soon as surfaceflinger starts
[Galaxy Tab 3 7.0 Android Development] dsilx:
Hello

[MENTION=4716493]laufersteppenwolf[/MENTION] flashed it and seems good
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Wifi isn't really working the way it should (from within android), but you can see that the needed interfaces are up @ boot when running "$ iwconfig"

If you want proof that wifi itself really is working, you can run a quick scan of your surrounding networks by running "$ iwlist wlan0 scan"

Wifi within android is not yet working due to the wpa_supplicant issues. As soon as this is fixed and dhcpd is then working as well, we should have wifi up and running the way it should (even though I don't like this kinda dirty way...)
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Alright guys, this thing is giving me nightmares... I managed to get wifi up in android as well, I can now enable/disable it via settings, but it just doesn't find any networks (even though "iwlist wlan0 scan" finds everything). I suppose I am missing some ROM related patches, which is why I'm gonna focus on that now, helping [MENTION=4911249]Unjustified Dev[/MENTION] to update the repos with all marvell patches.

So for the time being, you might want to play around with THIS ;) (same rules still apply as last time ;) :p )
[Galaxy Tab 3 7.0 Android Development] Ripshock:
Does your rom have wifi?
[Galaxy Tab 3 7.0 Android Development] bierma32:
Have you read The last Posts before, so you now The answere.
[Galaxy Tab 3 7.0 Android Development] Ripshock:
I have read but I thought the one hes0 supported had the fix
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
He says that only through adb shell you see networks but it still needs work before you can't see them in Android system. The difference between the first and second build is now the WiFi switch is enabled rather than greyed out.
[Galaxy Tab 3 7.0 Android Development] Ripshock:
Ok, so the problem is you can't connect.
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Basically the problem is you can't do anything from within Android itself, except turning wifi on and off ;)
[Galaxy Tab 3 7.0 Android Development] tharmor:
Guys........the stock Kitkat is just too laggy ! We need CM11........You guys can do it !!

Eagerly waiting for CM11 running on T210.......:good::good::good::good::good:
[Galaxy Tab 3 7.0 Android Development] Ripshock:
Mmmm I have also tested cm 11, it's also laggy, it's even laggier

But hell man, idk why cm is 250mb and touchwiz is like 700 mb, I mean can you imagine the difference
[Galaxy Tab 3 7.0 Android Development] HerroYou:
Hardware rendering is off, that is why it is laggy.

How many times does someone have to repeat?
[Galaxy Tab 3 7.0 Android Development] clyder:
And this is a development release. Not even an alpha. Not really fair to compare it with a stable rom in any way or criticize it.
[Galaxy Tab 3 7.0 Android Development] :
hi, just curious, what does rfkill list all return ?

m
[Galaxy Tab 3 7.0 Android Development] svicenty:
That not good
[Galaxy Tab 3 7.0 Android Development] bmatney:
Every time someone asks for an ETA, they should make everyone wait another week.
[Galaxy Tab 3 7.0 Android Development] Ripshock:
Posted in wrong thread, sorry
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
everything's unblocked, just like it's supposed to be ;)

but you are right, the wifi interface needs to be unblocked when activating it. But this is all being done automatically ;)

No, development is not stopped. However, it is halted on my side for now, as I just got out of the hospital this tuesday.

Please don't spam this thread or my PM inbox asking how I am and what happened. I had a surgery on my lung as my left lung kinda collapsed (spontaneous pneumothorax) and I'm kinda ok now, but not yet ready again to get back into development. Let's just leave it at that.

Due to this fact, I guess I will be uploading another version of my kernel in the next few days, as I won't be able to keep on working on it anytime soon.
[MENTION=3034891]gr8nole[/MENTION] [MENTION=4911249]Unjustified Dev[/MENTION] if there's anything I can help you with, though, you know how you can reach me ;)
[Galaxy Tab 3 7.0 Android Development] :
Rest, heal.

L,

best wishes, get well. :good:

because i'm a dork, one more question, does the hidden connection approach work like in linux ?

m
[Galaxy Tab 3 7.0 Android Development] svicenty:
Get well health is more important
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Thanks

what do you mean by "hidden connection approach"?
[Galaxy Tab 3 7.0 Android Development] :
L,

ahh okay, while having a miserable time of using the kali mini install method and on occasion with some distros where the connection manager is glitchy there's an option to connect to/create a hidden connection which in short means for me anyway manually entering the connection name you want to connect to and hopefully only the passkey afterwards. one of your nvram files in i believe /system/etc/wifi contains your connection info. you could try as root to manually input the info into the nvram file and set it to read 444 preventing system overwrite and reboot

then see if connection shows up.

you do need to know the name of the connection. i think the right term is like essid ? maybe?

and wpa passkey

alternately maybe a your name here init.d script to run the connection process the old fashioned way might also be a solution. it will require the end-user to fill in the blanks the first time out but if it works then they're good.

m
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
well, in theory you're right and it might work manually (--> also via script that is). I was actually already thinking about the same thing, but I abandoned this idea pretty quickly, simply because there are just too many downsides:

- you can connect to only one newtork (or need to change way too much)

- you need to mess with some stuff one shouldn't have to mess with

- it is unsecure and unreliable

- it just sucks, as after all many apps need a proper android wifi control interface

I know that all except the last point is "fixable", but we would have to create an entirely new interface, with way too much dirty hacking.

BTW, you wouldn't have to mess with the system partition for the passphrases, they are already stored on your /data partition and you would just have to parse them, but for security reasons I will not publicly post the exact location of the file ;)
[Galaxy Tab 3 7.0 Android Development] :
L,

no worries. :good:

to each his own . ;)

be good.

m
[Galaxy Tab 3 7.0 Android Development] Ripshock:
I think we should just wait till kk released for t210/r
[Galaxy Tab 3 7.0 Android Development] ruzell:
About Kitkat

Samsung claims they will release their KK update "SOON" to the T210-R
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
That's not the problem. Blobs aren't the real problem (at least wifi related). Our current problem is the chipset itself (or the way it needs to be handled to be more precise), and that's not going to change with the kk update.

Don't get me wrong, I want the update just as bad as you guys do, but in terms of current development, it will most likely not change anything.
[Galaxy Tab 3 7.0 Android Development] Sachin97:
Will the t210 get the update
[Galaxy Tab 3 7.0 Android Development] ruzell:
T210 and T210-R is the same
[Galaxy Tab 3 7.0 Android Development] svicenty:
Yea ok
[Galaxy Tab 3 7.0 Android Development] DevMyAndroid:
have you tried the new kernel scorces from the nolekat rom?
[Galaxy Tab 3 7.0 Android Development] Ripshock:
It won't work on cm
[Galaxy Tab 3 7.0 Android Development] Sachin97:
And from where did you got the news any link, leak or?
[Galaxy Tab 3 7.0 Android Development] :
Round 4

L,

as per your request.

m

round2

round3

[MENTION=4716493]laufersteppenwolf[/MENTION]

round4
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Guys, in case you wonder what the above means, I was just working on getting the new, official 4.4.2 kernel sources for our device working.

even though the above screenshot uses "~kerNole" as localversion, it still is THIS kernel. I just had to change it as a quick workaround to make the old modules inside the ramdisk working. But I still happen to have some ramdisk issues, so don't expect anything too soon ;)
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Alright guys, the time has come... :p

I have just posted a working 4.4.2 kernel HERE. But not using a normal installer, but using an Anykernel installer. What this is and what this does is all explained in the linked thread.

Please note that this kernel is tested on 4.4.2 only. Even though the installer supports both JB and KK, the kernel has not yet been tested on JB.

Many thanks go to [MENTION=3034891]gr8nole[/MENTION] and [MENTION=5864662]moonbutt74[/MENTION] for testing and troubleshooting :)

In case you are experiencing problems, please always post a recovery log (of the flash) as well as a (last_)kmsg.
[Galaxy Tab 3 7.0 Android Development] Ripshock:
Ok, great but does it work with cm and working wifi?
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Yes, it should work with CM, or any other AOSP based KK ROM.

Wifi, however, is something completely different, so using this kernel will not make wifi work
[Galaxy Tab 3 7.0 Android Development] zach61797:
OK the kernel works except it makes my boot animation dissapear like it was before unjustified Dev made the old panel fix
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
I know about the fix, however, as Sammy used a different source for the panel on this kernel as on the one [MENTION=4911249]Unjustified Dev[/MENTION] used, I figured it would be working...

Lemme look into it. It'd be great, though, if you could provide me a kmsg, please