yashsingh1/xdaforums huggingface dataset:
[Magisk] switchem:
Should a LUKS partition mount automatically on boot? An img container file using the loop option does mount automatically, but I've decided to encrypt the entire card and mount that with the part option. It mounts just fine when I manually run `fbind -b`, so it's not a big deal if I need to pop into Termux and run that every time I reboot, but it would obviously be nice it if mounted automatically. Just wondering if that's possible? Here's my config line:

part /dev/block/mmcblk0--L,password $intsd/_sdstorage
[Magisk] lanosalf:
Hi i need some help, i cant bind Whatsapp folder to its new location "$intsd/Android/media/com.whatsapp/Whatsapp"

extsd_path /mnt/media_rw/E7FA-66DF
from_to "test" ".fbind/test"
from_to "Android/media/com.whatsapp/Whatsapp" ".fbind/Android/media/com.whatsapp/Whatsapp"

With this i can perfectly bind the "test" folder in the external sd to the internal sd and all is working as intended.

But the Whatsapp folder in that location is not binded.

Anyone with the same problem?

In fact i cant bind anything inside "$intsd/Android/media" folder

perhaps a permission problem? how can i solve it?

thanks in advance

ps: I mean, if in the future the bind is created, perhaps i will need to change permission for whatsapp to be able to access the folder, i dont know, but for now, nothing is created, the bind is not created.

edit: I have a Samsung S7 edge with Lineage OS 19.1 (Android 12.1) installed

Edit2: this are the sdardfs and FUSE mounts I have

Spoiler content hidden.

Spoiler content hidden.
[Magisk] lanosalf:
Noone has the same problem?

Am i doing something wrong?

The thimg is that Indeed i can bind folders from the internal to the external. But I can't bind from $intsd/Android/media that is what I need.

In fact if Whatsapp had its folder at internal storage root as before (/Whatsapp), I wouldn't have any problem .

Thanks
[Magisk] samhhmobil:
Of course, yes. I had the same problem.

This is due to the fact, that all folders in $intsd/Android/* have special permissions/uid/gid and even any "normal" file explorer cannot access these folders.

If you mount that to $extfd these permissions are violated.

So... fbind cannot work for these folders.

I gave up long ago.

samhhmobil
[Magisk] lanosalf:
Ohh f**k, one off the primary reasons to flash a custom and rooted rom was to be able to manage space, in particular the WhatsApp folder which is getting bigger

I can bind to $intsd/Android/, but I can't bind to $intsd/Android/media

Also, in fact for what i read here in this thread there is also the possibility to bind in obb folder $intsd/Android/obb.

So perhaps there is still some possibility.

I understand that newer Android version add a lot of mess to permission and the usage of the external sdcard is being almost discarded. I'm using Android 12.1, lineage os 19.1 in an s7 edge.

Thanks for answering
[Magisk] samhhmobil:
I'm sorry to have no better ideas.

On my backup phone (Xperia XA2), I downgraded to LineageOS 17.1, and there WhatsApp is located NOT in $intsd/Android/media/WhatsApp, but instead it's "old fashioned" in $intsd/WhatsApp. And THAT is mountable with fbind to $extsd.

That works.

So sorry,

samhhmobil
[Magisk] TrueHD:
Hello friends, could this module be used to mount second partition of MicroSD so i could move or link some of the apps there? Becouse i have only 8gb of internal memory (total!) and its f**king very little.

Redmi 5A lite, LineageOS 20 Official, Android 13, Magisk 26.3

And yes, i tried format MicroSD as Adoptable Storage for three times, lost data all three times, google shows thpusands compaints of the same matter. So no i want to move apps with classic App2SD method. The problem is that in new Androids they changed something and it App2SD gives me error when i trying to create a mount script.
[Magisk] RootedLee:
@TrueHD pls read this post.

If you're on a low budget, my suggestion to you (and anybody else in this context) is to get a used somewhat older phone with much more storage, and stop messing with old phones with way too little storage. 8GB = not worth the trouble anymore, esp. trying to force making a current Android work on it. That poor old device tells you it's being raped. Better not ignore .. ;)
[Magisk] TrueHD:
@RootedLee

Bro i wouldn't ask if buying new phone would been an option for me. I don't want that. My phone is not so old, about 4 years, i think. And it perfectly satisfy me. Camera, big screen, battery life, and most importantly, it is thin and has a very light weight. Any modern phone with same price would be much heavier, i checked. And thin and light like mine would be much more costy. So no, i would prefer just move apps to my MicroSD card.

Thank you for the link, i checked it out, well i dont need to move obb files, becouse i dont play games. Regular apps with their data would be more then enough. And he claims he did it succesfully with App2SD, but how?

I even tried to write service.d path as he advises, but Apps2SD still gives me an error when i try to create a script.

I have Android 13, Magisk 26.3, BusyBox, first MicroSD partition is Fat32 and the second is f2fs. Kernel supports f2fs.
[Magisk] idkmanimjustlookingforans:
Hi, I'm trying to link a game data folder to my sd card

I've been using link2sd with no issues until I updated to android 12, now if I link the data folder to external using link2sd, the game downloads the data all over again on the internal storage

I use the latest version of magisk, can Fbind remedy this?
[Xperia Z3 Q&A, Help & Troubleshooting] utsav911:
Hey guys,

So I had broken my screen and ordered new one from Etradesupply. And ever since I installed a new one there's flickering going on when ever phone gets hot or for some strange reason.

I contacted Etradesupply and they sent replacement part but it still happens.

I don't know if there is a problem with the phone or their part.

Does anyone have idea why this happens?

[YOUTUBE]CqTTf-KR-_g[/YOUTUBE]
[Xperia Z3 Q&A, Help & Troubleshooting] TechnoFreak750:
I also had this issue.. its a common problem for z3 users. It is related to gpu. when used in cold environment the phone responds exactly like this. just turn off and then turn it on.. phone will get back to normal... else fo proper solution you need to send phone to repair centre. In summer you wont face this problem but in winter it will disturb you tooo much.
[Xperia Z3 Q&A, Help & Troubleshooting] utsav911:
No. I think it is different. As I said it usually happens when the phone gets hot. And I never had this problem on the factory LCD.
[Samsung Galaxy S8+ Questions & Answers] BBRecon:
If I get a factory unlocked US version, I can be sure it will have support for all major bands (and new network features) in major US carriers.

But if I get a factory unlocked International version (because I want dual sim), I know it will work on US carriers, but will it be missing support for some special bands that US carriers use? Will it have full compatibility with US carriers?

I also heard that international version didn't have CDMA support. Is that true?

P.S. Both factory unlocked editions should be bootloader unlocked, yes? I don't see why they wouldn't be.

P.P.S. Would it be possible to flash carrier specific firmware to a factory unlocked phone, that way you can keep your unlocked bootloader and also get carrier specific features (if it has one that is)?
[Samsung Galaxy S8+ Questions & Answers] mdiaz33685:
all the US models bootloaders are Locked... this is the question I'm looking for at this moment... I want to make sure that volte, wifi calling and US bands are all working, I have T-Mobile and refuse to buy a locked bootloader...

I'm looking for the g955f or fd... I see it for 719 + 10 for shipping... T-Mobile can kiss my a$$ for that buy 1 get 1... I have 6 lines and I am supposed to open a new line for each phone... I moved people from metropcs and sprint to tmobile and they treat the loyal customers like poooooop..... really bad business practices.. so I will never buy another phone from T-Mobile directly.
[Samsung Galaxy S8+ Questions & Answers] kavianr:
i have tmobile and i got the FD version of the phone, without root and flashing tmobile CSC VOLTE and WIFIcalling will not work on the stock firmware.

keep in mind flashing and rooting will trip knox and you cannot use samsung pay and secure folder. and warranty is voided.

secondly, tmobile is not having bad business models. it doesn't matter how loyal you are, they are a business. everyone requires one new line for a BOGO, ATT wants one new line and you have to have directTV.
[Samsung Galaxy S8+ Questions & Answers] Greenmule:
does anyone know for sure if the US unlocked version (SM-G955UZKAXAA) supports LTE band 29 for AT&T? according to this, it does not: http://www.droid-life.com/2017/03/08/unlocked-galaxy-s8-plus-s8-fcc-smg950-smg955/

ajsmsg78 answered this and it appears not.
[Samsung Galaxy S8+ Questions & Answers] BBRecon:
From what I've read, T-Mobile has worked specifically with Samsung to make a phone that supports all their network features properly. Furthermore, you need their firmware to support their features (they may make updates and such in the future). Unfortunately, the only way to do this is to buy their model branded phone.

So as far as band support and such, I'm not sure how much band support there is in the factory unlocked editions. Likely the phone will work fine with the carriers, but don't expect certain special network features to be supported, or 100% compatibility (I don't know if flashing their firmware to your phone can fix this part)
[Samsung Galaxy S8+ Questions & Answers] spaniolo:
Hey I have the Galaxy S7 Edge Olimpic edition which is basically the US unlocked version. When I first inserted the Tmobile SIM card it automatically pulled the firmware from T-mobile, and surprise surprise special features that before were imposible on an unlocked phone like wi-fi calling work!!
[Samsung Galaxy S8+ Questions & Answers] BBRecon:
Really!! That's amazing!! Wonder if that'll work with the US unlocked version of S8 as well (sadly not bootloader unlocked though)
[Samsung Galaxy S8+ Questions & Answers] spaniolo:
My understanding is that the US unlocked does support all US carriers features, while the International unlocked does not. And the bonus it is still no carrier's bloatware.
[Elephone P9000 Guides, News, & Discussion] RMcT:
Just updated my Elephone P9000 (not Lite, not US) to Android 7.0 by flashing the 20170418 ROM. To my surprise it now supports 3G on the second SIM. The options now are:

One SIM - 4G/3G/2G

Other SIM - 3G/2G (with Android 6.0 this was 2G only)

I hesitate to say SIM 1, SIM 2, because they can be swapped in software. As more countries shut down their 2G networks this feature will become important.
[Galaxy Tab 3 7.0 Android Development] sscsps:
Hello people,

I am working on this project all alone, if anyone want to help, please do, as I don't have much experience. It's quite tough to work on this without much experience :|

CURRENT STATUS: TESTING

Current Logs: https://gist.github.com/SscSPs/f5505f9aa0ed01651c1579fc342c1e3b

Nolekat logs: https://gist.github.com/SscSPs/2b732f7dd9e9d4de17b265602dd854e8

New Update

(7th Aug 2017):

Looks like the graphics drive is not being loaded at all, the Galcore is not being initialized, may be there's more that's missing, but that is the only thing I can see missing from the Kernel logs.

I've added kmsg from nolekat (till it boots up) so if anyone want to, they can compare the differences. So far, i've seen just the GPU driver not starting.

For Update logs, check Post #2.

For Install Instructions, check Post #3.

Now, I'd like to thank all of you guys for helping me in this, specially, to [MENTION=8420088]Manuehlito[/MENTION] for testing all the builds I've been unable to test by myself.

Thanks everyone :)

XDA:DevDB Information

LineageOS, ROM for the Samsung Galaxy Tab 3 7.0

Contributors

sscsps, gr8nole, laufersteppenwolf, more, list is big(they dont know i am continuing this work)

Source Code: [url]http://github.com/SamsungGalaxyTab3[/URL]

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.4.x

Based On: LineageOS

Version Information

Status: Testing

Created 2017-06-14

Last Updated 2017-12-17
[Galaxy Tab 3 7.0 Android Development] sscsps:
This post will contain list of all the updates and Milestones.

For more frequent updates and builds, join this telegram group: Tab 3 development

https://t.me/SamsungGalaxyTab3

Place for new builds: AndroidFileHost(link removed)

You can check it for new builds as I upload them. It'll probably be having all the non booting ones. I'll clear it up once we get it to boot.

UPDATE: 5 August 2017

Fourth build

I have tried a few things, the log present in op is from a build before this one, i need someone to test this one,

There's a lot of improvement from the last build that I posted here.

GDrive Link(link removed)

STATUS: NOT BOOTING

UPDATE: 23 July 2017

Third Build.

This build have a lot of improvement over the previous ones. I have successfully added SEPolicy v30 support in the kernel, so it is compatible with nougat at least in that aspect and have tried to fix the fstab.unknown issue.

I don't know yet if it boots or not, someone test it and provide logs. Read the first post for instructions of how to get logs.

It is available on the AndroidFileHost folder link provided above, or you can go directly to the file here: AndroidFileHost(link removed)

STATUS: NOT BOOTING

UPDATE: 17 July 2017

Second build.

Added T210 to flashable device list(but the name is yet lt023g/t211)(T210 users can flash it but might have a few extra things that are not needed on that device) This is done just to let users have a try.

Needs testers. I haven't been able to test it yet. Please try and report how it goes.

It is available here: GDrive Link(link removed)

STATUS: NOT BOOTING

UPDATE: 18 June 2017

First build succeeded.

It is available here: GDrive Link(link removed)

STATUS: NOT BOOTING
[Galaxy Tab 3 7.0 Android Development] sscsps:
Reserved

INSTALLATION INSTRUCTIONS:

Okay, I think it is understood that this build is most likely not going to boot. If you want to install it and help me with making it bootable, go ahead and try to run it. Grab Logs and give them to me.

NOTE: it is highly recommended that you create a backup before flashing this. You would need it to recover.

If you have other plans, that's fine too, but I recommend to have a backup.

Steps to create a BACKUP:

1. Go to recovery

2. select backup

3. select all the partitions(if you don't want some partition, then you know better)

4. select storage where you want to save the backup.

5. swipe to backup.

it'll take a little while to back it all up, just wait and it'll be ready

Once you have created the backup, you are ready to Install, for that, you will have to first WIPE the data partition and system.

Steps to WIPE:

1. Go to recovery

2. Go to WIPE section.

3. Select data, and system. (DO NOT SELECT THE PARTITION THAT CONTAINS YOUR BACKUP)

4. swipe to start the WIPE process.

it'll takea little while to complete.

Now that you have wiped your system, follow these

Steps to Install the ROM:

1. Go to recovery, select "INSTALL",

2. find the zip file,

3. flash it.

4. reboot to system.

FETCHING LOGS

After installing the ROM, please explain how it goes, grab a logcat and/or last_kmsg

If the device boots,

Grab LOGCAT by following these steps:

1. connect the device to PC

2. open adb and check if the device is detected(run "adb devices", it should list your device there).

3. run this: adb shell logcat > logcat.txt

this will get the logcat in the file logcat.txt, located in the present working directory, you can change the name of that file if you want.

Provide this file.

grab LAST_KMSG by following these steps:

If the device doesn't boot, i.e. either stays on the SAMSUNG logo, or reboots back to recovery then follow these steps:

Reboot to recovery and follow these steps:

1. If it stayed on the SAMSUNG logo, Reboot to system once again, and let it stay as is for a while. and then reboot back to recovery.

2. connect the device to PC.

3. open ADB and ensure that the device is connected.

4. Run this: adb shell cat /proc/last_kmsg > last_kmsg.txt

this will get the last_kmsg in the file last_kmsg.txt, located in the present working directory, you can change the name if you want to.

provide this file.

After you are done taking logs, you might want to restore your backup, if you know how to, or have other plans, you are good to go, but if you need help,

Follow these steps to restore your system:

1. Go to recovery

2. Go to wipe and wipe system, data, cache

3. After wiping LineageOS off, Select Restore.

4. Select the storage location that you selected while creating the backup.

5. Select the backup that you want to restore(most likely, there will be just 1).

It'll take a while to restore, and after restoration is done, you can just reboot to system and it'll boot back to touchwhiz as nothing happened :)
[Galaxy Tab 3 7.0 Android Development] thetanmaygupta:
Hmmm Well Hello I want to be a tester of your rom and btw what Is the status till now and if you release kernel,vendor,tree i will help sm-t211 community for bringing up many roms waiting for your​ reply
[Galaxy Tab 3 7.0 Android Development] sscsps:
Cool! I'll count you in for testing.

The current state is "not compiling". I am working on the device tree to make it compile for a start.

Yes, I have my device tree, vendor tree and kernel tree on my github, you can take a look if you want. but as i said, they are not working just yet.

If you can help me with making it workable, please do :)

I'll post the roomservice.xml soon so others can have same setup as mine. or can improve it. :)
[Galaxy Tab 3 7.0 Android Development] sameer22:
Can you link me to rooting guide of SM-T211? Is it the same as SM-T210 or any other Tab 3 model?
[Galaxy Tab 3 7.0 Android Development] bierma32:
Here you can find all for the Tab 3 7.0 Version. https://xdaforums.com/showthread.php?t=2755532
[Galaxy Tab 3 7.0 Android Development] rgsoussama:
Hi thanks for your hard work , what about sm-t116 ?
[Galaxy Tab 3 7.0 Android Development] aditrodostress:
thank for dev, i'm already try to install and post the logcat to you and report any bugs later

one question where supose to be i'm post the logcat ?

sorry my languange
[Galaxy Tab 3 7.0 Android Development] sscsps:
upload the file containing it.

or use https://hastebin.com/ and provde link :)
[Galaxy Tab 3 7.0 Android Development] sscsps:
I can work on it, but for start, i just need to get it to boot on one device at least.

I'll call you out once its booting for t211, so we can start working on t116 and other devices.
[Galaxy Tab 3 7.0 Android Development] rgsoussama:
Ohh thanks bro, keep your good work up :good:
[Galaxy Tab 3 7.0 Android Development] aditrodostress:
installing update...
target: samsung/linage_lt023g/lt023g:7.1.2/NHJ47B/2c3386f0cc:userdebug/test-keys
detected filesysytem ext4 for /dev/block/platform/sdhci-pxav3.2/by-name/system
cant install this package on top of incompatible data. Please try another package or run a factory reset

just run wipe data.factory reset , wipe cache parttition and wipe dalvik cache now installation running

installing update...
target: samsung/linage_lt023g/lt023g:7.1.2/NHJ47B/2c3386f0cc:userdebug/test-keys
detected filesysytem ext4 for /dev/block/platform/sdhci-pxav3.2/by-name/system
patching system image unconditionaly
E:unknow comman (log)
E:unknow comman (log)
detected filesysytem ext4 for /dev/block/platform/sdhci-pxav3.2/by-name/system
script succssed result was
install form sdcard complete
[Galaxy Tab 3 7.0 Android Development] sscsps:
Thanks for the logs :)

Initial look says we definitely need to update the kernel.

Current kernel version is 3.4.5, i'll try to update it to 3.4.113 at least and will proceed from there.

Next test build will be available after that.

Will start the work on it from now on.
[Galaxy Tab 3 7.0 Android Development] sscsps:
btw, can you explain the boot process. did it stay stuck on the SAMSUNG flash screen, or rebooted again and again to the same state(SAMSUNG Flashscreen, or rebooted back to recovery?
[Galaxy Tab 3 7.0 Android Development] aditrodostress:
it just stuck on Samsung Galaxy Tab 3 screen.

i just can provide	only last_kmsg.txt
[Galaxy Tab 3 7.0 Android Development] sameer22:
Can't seem to find the rooting tutorial in this link, thanks for the files though :)
[Galaxy Tab 3 7.0 Android Development] Banan PL:
Will it work on 210 variant? Just asking cuz 211 is a 3g variant of 210. Glad to see that someone relesed 7.1 for this device. I tried to port it in past, but my PC is not enough powerful (random reboot), and my hard drive is too small.
[Galaxy Tab 3 7.0 Android Development] PixelBoot:
Any screenshots?

And does it work for the SM-T210?

---------- Post added at 03:23 PM ---------- Previous post was at 03:04 PM ----------

Result: SM-T210

Doesn't work :(

---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------

Don't worry!

After my exams (28/06/2017) I am free!

I have an SM-T210!

So I could easily port it!

---------- Post added at 03:29 PM ---------- Previous post was at 03:24 PM ----------

Here is the Error of ROM on SM-T210
[Galaxy Tab 3 7.0 Android Development] sscsps:
That is because it is not supported atm. I enabled the flash process to be only carried out on t211.

BTW, does it still change the system partition?

Did you loose your system partition after flashing this?
[Galaxy Tab 3 7.0 Android Development] PixelBoot:
I didn't have anything beforehand!

So not really!
[Galaxy Tab 3 7.0 Android Development] Banan PL:
No /system partition isn't touched after all. TWRP display just an error that the package is 211 so we can restore our /data partition and device is as nothing happened.
[Galaxy Tab 3 7.0 Android Development] bierma32:
Search the right Recovery for your Tab, flash it with Odin, boot into Recovery and flash SuperSU.zip.

So your Tab is rooted.

Take an look on these video guides. https://xdaforums.com/showthread.php?t=2459817
[Galaxy Tab 3 7.0 Android Development] A_R_T_Z:
Omg

Omg finally some one is making for smt211 Thanks man best of luck :)
[Galaxy Tab 3 7.0 Android Development] sscsps:
Please don't put off topic questions here...
[Galaxy Tab 3 7.0 Android Development] sscsps:
Luck might help, what we need to do is update the kernel. And it's tough
[Galaxy Tab 3 7.0 Android Development] mspadua:
Any news?
[Galaxy Tab 3 7.0 Android Development] Danil_e71:
I am making lineageos from source. Now in my tab 3(211) always cycle bootanimation. Crash in egl drivers.

youtube
[Galaxy Tab 3 7.0 Android Development] sscsps:
Where is your source?
[Galaxy Tab 3 7.0 Android Development] sscsps:
I'd really love to help build your tree as I'm quite news too :)
[Galaxy Tab 3 7.0 Android Development] Danil_e71:
I will sync my github today
[Galaxy Tab 3 7.0 Android Development] sscsps:
Okay, what's your github handle?
[Galaxy Tab 3 7.0 Android Development] Danil_e71:
vendor

device

kernel
[Galaxy Tab 3 7.0 Android Development] sscsps:
Okay, so I took a look at your device tree and i found out that you are modifying t217's tree, well, there are a lot of Qualcomm related files/flags in your tree, you might want to get rid of them
[Galaxy Tab 3 7.0 Android Development] Yakubeq:
Can't wait for working build. Good luck!
[Galaxy Tab 3 7.0 Android Development] sscsps:
New BUILD online!

check it out and report how it goes.

Dont forget to read first and second post if you haven't already.

#2 post: https://xdaforums.com/showthread.php?p=72719484#post72719484
[Galaxy Tab 3 7.0 Android Development] powermaster1995:
I'm testing 17 July 2017

not boot yet

https://hastebin.com/ovozofotik.go
[Galaxy Tab 3 7.0 Android Development] suburbadroid:
Please could you port this t110? Id very grateful
[Galaxy Tab 3 7.0 Android Development] kelvin781021:
Will the recovery version of which you are using one ?? I still use ... T211.TWRP.2.7.1.0.KK.tar seems to be unable to use the Android 7.1 version ...
[Galaxy Tab 3 7.0 Android Development] powermaster1995:
Same
[Galaxy Tab 3 7.0 Android Development] sscsps:
Try with CWM. should work.