yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 8.0 Android Development] LittleJoe2005:
Yes, Number 4 is booting
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Ok, well, unfortunately, the issue is when trying to start the cbd service which is required to boot the modem. When I remove the line that starts that service, the tab can boot up. That means that even though the T311 now boots, the modem will not work. At least you can use wifi though.
[Galaxy Tab 3 8.0 Android Development] qqqwerty:
Yes, test4 is working.
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Thanks to Vladimiro G for the donation!! It is also very much appreciated! :D
[Galaxy Tab 3 8.0 Android Development] [Jaco69]:
Personally I don't use SIM card on this Tab, so no problem for me.

Happy to know the journey is not over

Inviato dal mio LG-H815 imperiale usando Tapatalk

---------- Post added at 10:19 PM ---------- Previous post was at 10:14 PM ----------

My Tab is reborn thanks to your job.

Inviato dal mio LG-H815 imperiale usando Tapatalk
[Galaxy Tab 3 8.0 Android Development] LittleJoe2005:
I can live with WiFi-only too

Once more many many thanks to gr8nole for the T311-builds and the test-kernels!

Nougat is really nice on our old tablet :)
[Galaxy Tab 3 8.0 Android Development] pooriaraisi:
Thanks for the update, everything is good not only SIM card

فرستاده شده از SM-T311ِ من با Tapatalk
[Galaxy Tab 3 8.0 Android Development] BfdNova:
I am getting an error failed to download due to missing sd card... I just flashed most recent build, prior I formatted the device then wiped system, Devin, data and cache... then flashed rom then gapps... what am I doing wrong? The device is t310... someone HHEELLP....
[Galaxy Tab 3 8.0 Android Development] gr8nole:
What browser? Make sure the browser has "storage" permission in settings.
[Galaxy Tab 3 8.0 Android Development] BfdNova:
Chrome and I verified the permissions...
[Galaxy Tab 3 8.0 Android Development] gr8nole:
If you haven't rebooted since installing Chrome and setting permissions, you need to reboot to allow the permissions to be applied properly.
[Galaxy Tab 3 8.0 Android Development] BfdNova:
Still didn't help... trying to go back to AICP...
[Galaxy Tab 3 8.0 Android Development] gr8nole:
I downloaded Chrome just to test and got the same error you reported. After giving storage permission and rebooting, it works fine.
[Galaxy Tab 3 8.0 Android Development] Cannonball_CO:
OK, I've been attempting things on my own for a couple days and am getting nowhere, so I would appreciate any help and/or advice with a problem with Hangouts.

I installed the 1/3 build two days ago with "stock" Gapps. Worked great for a day and half (using the built-in root, and Stericson's BusyBox Pro), then yesterday afternoon the file manager stopped seeing the external SDcard, as did many other things (Chrome as well). Cleared data on these, force stopped, looked at their permissions, but nothing seemed to help. I could live with that. Then in the evening Hangouts started to crash every time I typed something into it. I'm a Project Fi person so it's my SMS app, I like it everywhere so that was trouble. I also use MyBackupPro and it originally worked, but was totally broken by this morning.

Today, I wiped everything - including internal sd and even reformatted the external as exFAT. Installed the 1/7 build again with "stock" Gapps. At first, Hangouts... uhh, seemed to work (maybe I didn't check it enough), so I installed about 50 more apps - the stuff I like... and now it's not working again.

I suspect this is my problem - I have some incompatibility going on - but at the same time I'm confused how one app could mess up another (I will not be offended by being called ignorant or naive!)... but I'll check in here just in case. Also, I'm quite capable at the command line, I have adb installed, and 'adb shell' is not an unfamiliar command. Any advice how I could try to trace the source of the error (logs, debug)?

Thanks,

KSH
[Galaxy Tab 3 8.0 Android Development] gr8nole:
First thing to do would be to pull a logcat as soon as you see an issue and look for anything unusual related to that particular app.

As a side note, 50 apps seems like a lot to have installed on this device. Even if you aren't using them all, many of them will have something running in the background and this old device will start lagging and having issues with a lot of background things consuming resources. Most app developers do not care about efficient apps anymore because they expect devices to have more ram than our device has. With that said, the number of apps may not have anything at all to do with it, but that's just a general observation of mine.

Edit: Almost forgot...the built in file manager is terrible...install a better root enabled file manager from the store.
[Galaxy Tab 3 8.0 Android Development] BfdNova:
Must be an issue with the tablet...I downloaded the stock firmware... Do I just flash it from twrp?
[Galaxy Tab 3 8.0 Android Development] gr8nole:
I don't understand much of that. I'll keep an eye out in case I see something that may help.
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Stock firmware files are flashed with Odin.
[Galaxy Tab 3 8.0 Android Development] Cannonball_CO:
Understood. Thanks. The bluetooth righted itself sometime overnight.

Funny, anyone who ever wonders "why is my battery draining so fast" should take a look at logcat. There's a lot of BS going on all the time on this little thing. :silly:

Oh yeah, I remembered... I first installed CM13 on this thing - your CM13 - and I do recall Hangouts worked great on that. I may just go back (powermetza is applying patches to your device trees). If I do that, and it works great, donno what that means but I'll report it back, at least.
[Galaxy Tab 3 8.0 Android Development] Andry7:
Hello all! I only would like to say a very very BIG thanks to gr8nole for the time he spends for our devices. THANKS!

I'm a T311 user. I read this thread daily and I'm sad that I cannot help with tests but I'm using my device daily as hotspot and for other purposes where I absolutely need 3G. So atm, I stay with MM but my fingers are crossed hoping that first or later you can find a solution for it.

Thanks again for all, also for the patience with which you answer to everyone

P.S.

I also would like to say that if anyone (mostly T311 and T315 users) thinks to throw away his tablet to buy a new one, maybe he could ship it as a gift to gr8noble thus helping the whole community and also save time to our dev. I think would be fair and appreciated as are the donations ;)
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Thanks to Joachim B for the donation. It is very much appreciated!! :D
[Galaxy Tab 3 8.0 Android Development] chris-l-a:
I'm experiencing exactly the same problem. With dirty flash, unable to enable WiFi and no access points show. Clean flash, when it comes to the point of adding a WiFi connection the MAC address 02:00:00:00:00:00 is shown but again unable to enable WiFi and no access points show.

For me also, the only working version is from 20161208.

Chris.
[Galaxy Tab 3 8.0 Android Development] mega180:
On sm-t310 dirty flash of 20161231 on a working version, wifi is working. But I did not try to add a new connection.

Envoyé de mon SM-T310 en utilisant Tapatalk
[Galaxy Tab 3 8.0 Android Development] bleui:
stuck on samsung logo bootloop after installation (TWRP log doesn't show any error)

followed all the instructions on the first page (on TWRP 3.0.2-5 & wiped Dalvik/ART Cache, System, Cache, and Data)

either on build 20170101 and 20170107 (T311)

cm-14.1 ROM (build 20161225) is working fine though
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Flash the boot.img in post 417 immediately after flashing Jan 7 build.
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Has any T315 user tested the 20160107 build with the test boot.img I posted in post #435?
[Galaxy Tab 3 8.0 Android Development] gr8nole:
If you guys want to try to help solve this issue:

On the build that has working wifi:

Copy the /system/etc/wifi directory to your sdcard.

Then flash the latest build and bootup.

Replace the system/etc/wifi files on the device with the ones you copied to the sdcard.

Make sure to set the permissions to what they were before replacing (should be rw-r-r)

Reboot and test wifi
[Galaxy Tab 3 8.0 Android Development] hejo1:
Hi,

I dirty flashed the latest release over January 3 release.

WiFi working fine, but now I can't activate Bluetooth.

Anyone else have the same problem?

Device is T310.
[Galaxy Tab 3 8.0 Android Development] AgentJ23:
Unfortunately, it dosn't change enything. After flashing and copying all files from mentioned directory, the result is the some = mac address 02:...
[Galaxy Tab 3 8.0 Android Development] gr8nole:
I have attached a zip file with a macloader binary file init.

Reflash latest build and then replace the current macloader file in /system/bin with the one in the attached zip.

Set permissions to match current file and reboot.

Take logcat.
[Galaxy Tab 3 8.0 Android Development] AgentJ23:
You are THE BEST !!!

With this macloader all is working fine. My mac address is correct and wifi work as normal.

I've made logcat.

Cheers,

Tomek
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Excellent!!

Yet another issue caused by contributors committing code that breaks other devices.

At least I know how to fix it now.
[Galaxy Tab 3 8.0 Android Development] gr8nole:
[MENTION=4685929]xu3sno[/MENTION] Give the above macloader file a try and see if it fixes your issue as well.
[Galaxy Tab 3 8.0 Android Development] xu3sno:
Many thanks [MENTION=3034891]gr8nole[/MENTION]. You're really a helpful dev with great patience. :good:

Will try it out asap and report back.
[Galaxy Tab 3 8.0 Android Development] uzbekgmail:
error

Can't boot lineage on t311, but with old cm13 everything is fine! On line age only appears tab3 logo and nothing. Help me
[Galaxy Tab 3 8.0 Android Development] Jiraaff:
read the posts before

Enviado desde mi D6603 mediante Tapatalk
[Galaxy Tab 3 8.0 Android Development] ACE1972:
Still boot looping on T315 with test1boot.img
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Is there a boot.img from a previous build that boots?
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Yes, I'll look into it.
[Galaxy Tab 3 8.0 Android Development] Cannonball_CO:
I also had that problem, but on the 1/7 release. Thanks.
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Unzip the attached file and drop it in the /system/etc/bluetooth directory and set permissions to rw-r-r.

Bluetooth should turn on after that.
[Galaxy Tab 3 8.0 Android Development] ASicard:
Patch for BT works for my T310
[Galaxy Tab 3 8.0 Android Development] xu3sno:
I have tried it on 20161128 build (sorry, it's one backup I have and system running).

First attempt (copy macloader to /system/bin, change its permission chmod 755) it works out of the box. Got MAC Address the right one 5c:f8:a1:a6:12:b5, no longer a bogus number 02:00:00:00:00:00 appeared. However after a while ( ca. 5minutes, enough updated apps from Play Store), WiFi disconnected itself > try to reconnect > failed!

Went to Settings > About Tablet > Status > WiFi MAC Address remains the right one1!

Second attempt:

Reboot > MAC Adrees back to bogus number! :confused:

Third attempt:

Did like first attempt > WiFi works for a while then disconnected itself! Reconnected > failed.

Will try with the latest T311 build!

Thanks for your effort to help fix the issue. At least, now I knew the issue not related to defect device! You made my day [MENTION=3034891]gr8nole[/MENTION] :good: :good:

My /efs/wifi/.mac.cob:

5c:f8:a1:a6:12:b5

I did e2fsck /efs and it's clean!

and here /system/etc/init.d/80mac

#!/system/bin/sh
#
# Copy mac address to correct file to be read by macloader
#
mount -o remount,rw -t auto /system
MAC_ADDR_SRC=/efs/wifi/.mac.cob

STOCK_MAC_ADDR=$(toybox cat $MAC_ADDR_SRC)
CM_MAC_ADDR=5c:f8:a1:a6:12:b5
[ -f $MAC_ADDR_SRC ] && {
toybox sed -i s/$CM_MAC_ADDR/$STOCK_MAC_ADDR/g /system/etc/wifi/nvram_*
}

mount -o remount,ro -t auto /system
[Galaxy Tab 3 8.0 Android Development] chris-l-a:
I can confirm that copying your macloader file to /system/bin did the trick, even with a dirty flash. I used TWRP and its copy function, after mounting /system.

I didn't know what the permissions should be: just copied from my SD card to the location and it worked.

Thanks tons gr8nole!

Chris.
[Galaxy Tab 3 8.0 Android Development] xu3sno:
What is your device?

After (occasionally) WiFi works on 20161128 build https://xdaforums.com/showpost.php?p=70481390&postcount=481, I tried on 20170107 build and unfortunately MAC Address back to bogus number.

Do not know what's wrong with my T311 device. Maybe something wrong on /efs partition. Perhaps someone don't mind kindly upload /efs for T311. Thanks in advance!

[MENTION=3034891]gr8nole[/MENTION]

Attach logcat and dmesg macloader on 20170107

Thanks.
[Galaxy Tab 3 8.0 Android Development] hejo1:
Hi,

did exactly what you wrote here and Bluetooth is working fine again. Thanks a lot and cheers. [emoji106]
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Couple things from your logcat:

E macloader: Can't open /efs/wifi/.mac.info

Not sure why it can't open the file...does it exist?

I sysinit : Running /system/etc/init.d/80mac

80mac is required to prevent using a dummy mac address

I sysinit : Running /system/etc/init.d/80mac.bak

Where did 80mac.bak file come from? It is not part of the rom. Did you alter the original 80mac?

I suggest you wait for next build and clean flash. If it still doesn't work; then we can start looking after a clean flash.
[Galaxy Tab 3 8.0 Android Development] xu3sno:
IDK, which one right name file .mac.cob or .mac.info

Yes. I did. But 80mac I used is from Rom.

I will, dev. Many thanks for your help.
[Galaxy Tab 3 8.0 Android Development] bhavapat152:
lt013g v/s lt01lte

Hi ,

My tab is lt013g and it is working properly in bliss ROM but when I tried to install Lingage 14.1 it say your tab is lt01lte.

What will be the issue?
[Galaxy Tab 3 8.0 Android Development] gr8nole:
You probably have wrong recovery installed. Did you install recovery for T311 or T315?
[Galaxy Tab 3 8.0 Android Development] gr8nole:
New T310 and T311 builds are up 20170110.

All previously discussed fixes should be included. T311 should boot without any additional boot.img, but RIL will not work still.
[Galaxy Tab 3 8.0 Android Development] ASicard:
20170110 booted without any problème, wifi ok, Bluetooth ok
[Galaxy Tab 3 8.0 Android Development] nabril15:
I don't see the option under wifi advanced to choose the 5ghz band. Is that somewhere else? Or is it not available?
[Galaxy Tab 3 8.0 Android Development] XvPunisheR007vX:
Going to give the 20170107 build a try with the test boot.img, shall return with an answer very soon

Cheers [MENTION=3034891]gr8nole[/MENTION] thankyou for all your hard work :good::good:

---------- Post added at 06:15 AM ---------- Previous post was at 05:53 AM ----------

I got the infamous boot loop :( back to the stock rom or the last build of 13 lol
[Galaxy Tab 3 8.0 Android Development] xu3sno:
[MENTION=3034891]gr8nole[/MENTION]

First of all, many thanks for continuing T311 Lineage 7.1.1 build.

As you suggested, I did clean install (factory reset and wiped system) 20170110 build > Successful > installed Gapps (pico) > reboot > System running (without bootloop :good: ) > WiFi MAC Address 02:00:00:00:00:00 > hence WiFi failed to connect. :confused:

I think something wrong with my /efs/wifi/.mac.cob (someone, owner T311, told me he has ../.mac.info instead)

Attached logcat and dmesg.

Really appreciated so much your help, dev! Many thanks.
[Galaxy Tab 3 8.0 Android Development] gr8nole:
You should have both .mac.cob and. mac.info.
[Galaxy Tab 3 8.0 Android Development] xu3sno:
Should both have same MAC Address as script in 80mac?

Sorry for silly question.

Thanks for your patience in helping me.
[Galaxy Tab 3 8.0 Android Development] h3ok:
20170110-T310 works just fine with dirty flash...
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Yes, they SHOULD have the same address. The .mac.cob should never change, but .mac.info seems to get populated from the information in the system/etc/wifi/nvram... files. That's why we have a 80mac init.d script that copies the mac address from .mac.cob and replaces the standard mac in the nvram files. If you notice, there is no mention of .mac.info in the 80mac script, because the macloader seems to be looking in the nvram files for the mac address.

If we didn't use the 80mac script, then all of our devices would have the same mac address (and this has been an issue in the past).
[Galaxy Tab 3 8.0 Android Development] xu3sno:
Will try it out and report back.

Many many thanks.
[Galaxy Tab 3 8.0 Android Development] gr8nole:
[MENTION=4685929]xu3sno[/MENTION] stay online, I'm building a new macloader for you right now.
[Galaxy Tab 3 8.0 Android Development] xu3sno:
Wow. Yes dev. Take your time.
[Galaxy Tab 3 8.0 Android Development] gr8nole:
I have attached a zip file with a macloader binary file in it.

Replace the current macloader file in /system/bin with the one in the attached zip.

Set permissions to match current file and reboot.
[Galaxy Tab 3 8.0 Android Development] xu3sno:
Thanks. Will do and report back.
[Galaxy Tab 3 8.0 Android Development] xu3sno:
[MENTION=3034891]gr8nole[/MENTION]

I did as you instructed:

.mac.cob 5c:f8:a1:a6:12:b5

.mac.info 5c:f8:a1:a6:12:b5

Replaced the current macloader file in /system/bin with the one in the attached zip. > set permissions chmod 755

Reboot > unfortunately issue persists MAC Address 02:00:00:00:00:00

logcat and dmesg attached.

Thanks you, dev.
[Galaxy Tab 3 8.0 Android Development] gr8nole:
I'll have to re-visit this later. Did wifi work for any Nougat build for you?
[Galaxy Tab 3 8.0 Android Development] xu3sno:
Yes, cm14.1 20161128 build, as i posted #481

Again, many thanks.
[Galaxy Tab 3 8.0 Android Development] bhavapat152:
sim cannot detect. others working fine

hi,

I have updated latest ROM but still sim doesn't detect else other options are working

is there any way to detect the sim?
[Galaxy Tab 3 8.0 Android Development] AgentJ23:
Sm-t310

All is working fine. No more problems with mac address.

Cheers,

Tomek
[Galaxy Tab 3 8.0 Android Development] xmarx:
From this point - have you checked your system/etc/wifi/nvram_* files? ...if there are good permissions, then macloader was supposed to write YOUR macadrress from .mac.cob, in all of these nvram* files. Good permissions for folder system/etc/wifi is 755, and for nvram_* folders and files is 644.
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Using a root enabled file explorer, view the "properties" of the new system/bin/macloader file I gave you and tell what the "SE context" is.

It should be "macloader_exec".
[Galaxy Tab 3 8.0 Android Development] poppis:
t311

Updated to last build. All works fine exept

SIM not detected yet. When i go to settings cellular rete issue com.android.phone process is stopped.

Other bug is host mtp. Tks
[Galaxy Tab 3 8.0 Android Development] xu3sno:
Hi [MENTION=6857246]xmarx[/MENTION]

I did check permissions for:

folder system/etc/wifi is 755, and

nvram_* folders and files is 644.

So I think permissions are okay, but problem persists.

Anyway, thanks for your help, really appreciated.

---------- Post added at 04:31 AM ---------- Previous post was at 04:20 AM ----------

With root enable file explorer it's said: An error was detected. The operation was unsuccessful! While using Root Explorer no "SE context".

Will try with clean install CM14.1 (20161128) once WiFi was working (temporarily) with macloader you gave (post #481).

Thanks for your helps and efforts to fix my problem.
[Galaxy Tab 3 8.0 Android Development] [Jaco69]:
Dirty flash and all is fine, great job man!

Inviato dal mio SM-T311 utilizzando Tapatalk
[Galaxy Tab 3 8.0 Android Development] gr8nole:
You should be able to change the SE context of that file using a good root file explorer such as Root Explorer from the store. Change it to "macloader_exec" and reboot. You should be able to select that context from a list.
[Galaxy Tab 3 8.0 Android Development] xmarx:
OK about permissions, but what about content of nvram_* folders and files? Are in these folders and files YOUR mac address in fields "macaddr=..."? This info is needed to eliminate doubt about macloader functionality.

...and, even you sow your mac address, I suggest you to do an dirty flash. When I tested this, i don't detected changes without second dirty flash.

...
[Galaxy Tab 3 8.0 Android Development] VâmPø:
Tried your 20170110 build on my T311, did a clean install with gapps pico, did not use any mac extensions you provided.

Status: Wifi works for me without any mac problems,

all is well.

(Sim not detected though, its known yet fine)
[Galaxy Tab 3 8.0 Android Development] xu3sno:
[MENTION=3034891]gr8nole[/MENTION]

Still have no chance to change "macloader_exec". Not have proper file explorer. Sorry.

One thing for sure, (also for [MENTION=6857246]xmarx[/MENTION]), 80mac script succesfully read and write MAC Address .mac.cob and .mac.info to /ystem/etc/wifi/nvram_*

My /efs/wifi/.mac.cob and .mac.info is 5c:3c:27:00:57:7c (my working BT Adrress: 5c:3c:27:00:57:3c) and it's exactly copied into "macaddr=" in files

/system/etc/wifi/nvram_mfg.txt

/system/etc/wifi/nvram_mfg.txt_murata

/system/etc/wifi/nvram_net.txt

/system/etc/wifi/nvram_net.txt_murata

I did dirty install 20170110 build for T311

Attached logcat and dmesg.

Sorry for annoying you and flooding the thread with my posts on WiFi problem.

Many thanks.
[Galaxy Tab 3 8.0 Android Development] gr8nole:
T315 users, what was the last CM/Lineage build that booted for you?
[Galaxy Tab 3 8.0 Android Development] XvPunisheR007vX:
The first build i tried was 20170101, the only build i havn't tried is 20161231. I will download that and give it a go
[Galaxy Tab 3 8.0 Android Development] gr8nole:
There are CM14.1 builds in this folder to try as well.

https://androidfilehost.com/?w=files&flid=129598
[Galaxy Tab 3 8.0 Android Development] oritsuro:
on my T315 the last Version which works and boots out of the box was

CM14.1 -> Build from 19.12.2016 :fingers-crossed:

the LineAge OS Builds boots with Bootimage from 19.12. without WLAN :crying:
[Galaxy Tab 3 8.0 Android Development] ADB100:
No vibrate settings?

I am not sure if this is a CM14.1 issue or an issue with this ROM, however there are no Vibrate settings anywhere?

In CM13 under the Sounds menu there was a vibrate section which I would normally enable - 'Vibratre on touch'. Also under the Google Keyboard settings there is a 'Vibrate on keypress' setting. I normally enable these and disable 'Sound on touch' & 'Sound on keypress'

Is this something that can be added?

Cheers

Andy
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Okay T315 users, I have attached 2 test boot.imgs. Please test these on the latest build and let me know if either boot.
[Galaxy Tab 3 8.0 Android Development] [Jaco69]:
I can confirm it. I found quick switching between charging image with bars and smaller solid image, strange.

Inviato dal mio LG-H815 imperiale usando Tapatalk
[Galaxy Tab 3 8.0 Android Development] gr8nole:
What device? I don't believe we have vibrate motor.
[Galaxy Tab 3 8.0 Android Development] h3ok:
The endless possibilities in this universe are surprising me too... (sarcasm)
[Galaxy Tab 3 8.0 Android Development] oritsuro:
both Images where flashed clean direct after lineage-14.1-20170107-UNOFFICIAL-lt01lte.zip flashing

T315test2boot.img - looped in Samsung Logo

View attachment 4001754

T315test3boot.img - looped in Samsung Logo

View attachment 4001756

I hope it will help :fingers-crossed:
[Galaxy Tab 3 8.0 Android Development] ADB100:
Lol, sorry - don't I look silly.... I was comparing it to my HTC One M8. I have a T310.

In CM13 on the T310, in the sounds settings there is a 'Vibrate on touch' setting that can be switched on or off. However I don't think it does anything.

Cheers

Andy
[Galaxy Tab 3 8.0 Android Development] gr8nole:
Two more test boot.img for T315 users to try with latest build.