yashsingh1/xdaforums huggingface dataset:
[Xperia Z5 Premium Android Development] moonbutt74:
K, Z,

Quick note, the mac address in "stock" MM does not randomize. Meaning mac filter entry in router remains valid/correct across reboot.

So this is build or kernel. would appreciate the commit kernel side if you come across it that "makes it so" or modification to build system that achieves the same. Thanks.

m

derp, nvm i can just script it, init.d or service

root@E6853:/ # ifconfig -a | grep HWaddr
wlan0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
dummy0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
root@E6853:/ # ifconfig wlan0 down
root@E6853:/ # ifconfig wlan0 hw ether 00:11:22:33:44:55
root@E6853:/ # ifconfig wlan0 up
root@E6853:/ # ifconfig wlan0 | grep HWaddr
wlan0 Link encap:Ethernet HWaddr 00:11:22:33:44:55

Only posting because privacy is NOT an issue for my situation, so i need mac to stay the same.

[MENTION=3037651]zacharias.maladroit[/MENTION] the twrp build in my kernel thread.
[Xperia Z5 Premium Android Development] krabappel2548:
I'm still in training for the army, and my gf needs the laptop this week. But I'll try to fix some bugs after next week :)
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Thanks M !

Perhaps I didn't do it correctly the last time I tried,

what Recovery did you use for this ? TWRP ?

yeah, that is an annoyance when you're working with a MAC filter,

https://github.com/sonyxperiadev/kernel/commit/6ad557733ff801d6ba70fdba3af9a64a9819c9a4 is one related

but I had a different commit (or configuration) in mind, will notice you once I stumbled upon it again

Meanwhile git blame path/to/file is your friend that way you could trace down the offending commits of the changes in the files

Can you host those changes somewhere, once you do ? That way it would be easier to fix issues across the devices (Z5, Z5P and Z5C)

I've just read that the flash of the cam doesn't appear to work (and the colors are off - perhaps that improved from the last time I tested due to recent kernel changes)

---------- Post added at 02:31 PM ---------- Previous post was at 02:20 PM ----------

Found the commits:

the oldest one is probably that one that you seek,

didn't know that Apple with iOS8 also started to implement that "feature"
[Xperia Z5 Premium Android Development] moonbutt74:
exfat card mount manual approach

K, Z, [MENTION=6584695]CTXz[/MENTION]

Okay got my exfat card to mount, but it's sort of funky here goes

first in your device tree make sure you have the following option set/defined

TARGET_KERNEL_HAVE_EXFAT := true

Patch in exfat support in kernel

OKay now,

cat /proc/partitions
major minor #blocks name
[ snip snip ]
[COLOR="Red"]179 64 124868608 mmcblk1[/COLOR]

Warning: slightly goofy example!

mkdir /storage/nubby
mount.exfat -d -o rw /dev/block/mmcblk1 /storage/nubby

which results from an adb shell in running output as:

FUSE exfat 1.2.3
FUSE library version: 2.9.3
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.23
flags=0x0001f7fb
max_readahead=0x00080000
INIT: 7.19
flags=0x00000031
max_readahead=0x00080000
max_write=0x00020000
max_background=0
congestion_threshold=0
unique: 1, success, outsize: 40
unique: 2, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 6363
getattr /
unique: 2, success, outsize: 120
unique: 3, opcode: OPENDIR (27), nodeid: 1, insize: 48, pid: 6363
unique: 3, success, outsize: 32
unique: 4, opcode: READDIR (28), nodeid: 1, insize: 80, pid: 6363
readdir[0] from 0
unique: 4, success, outsize: 464
unique: 5, opcode: READDIR (28), nodeid: 1, insize: 80, pid: 6363
unique: 5, success, outsize: 16
unique: 6, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 6363
getattr /
unique: 6, success, outsize: 120
unique: 7, opcode: LOOKUP (1), nodeid: 1, insize: 56, pid: 6363
LOOKUP /.android_secure
getattr /.android_secure
NODEID: 2
unique: 7, success, outsize: 144
unique: 8, opcode: LOOKUP (1), nodeid: 1, insize: 48, pid: 6363
LOOKUP /Android
getattr /Android
NODEID: 3
unique: 8, success, outsize: 144
unique: 9, opcode: LOOKUP (1), nodeid: 1, insize: 45, pid: 6363
LOOKUP /DCIM
getattr /DCIM
NODEID: 4
unique: 9, success, outsize: 144
unique: 10, opcode: LOOKUP (1), nodeid: 1, insize: 49, pid: 6363
LOOKUP /Download
getattr /Download
NODEID: 5
unique: 10, success, outsize: 144
unique: 11, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 6363
LOOKUP /Movies
getattr /Movies
NODEID: 6
unique: 11, success, outsize: 144
unique: 12, opcode: LOOKUP (1), nodeid: 1, insize: 49, pid: 6363

and so on, each LOOKUP is a directory on my external sdcard [exfat format]

this is in my cm13 build

and so

mount -o bind /storage/nubby /sdcard/nubby/
ls /sdcard/nubby/
Android DCIM Download Movies Pictures TWRP Tunes apkbak customized-capability.xml video

So, nubby rules !!! :silly:

What doesn't happen is the registering of the media files on the now mounted and readable/writeable external sdcard [exfat]

my guess is groups and permissions, as even manual launching of a media file does not pick up via cm's media player or mxplayer, but copying files to and from work.

m

derp, okay so with the above it appears to be vold being the problem and not format support on the kernel-side
[Xperia Z5 Premium Android Development] moonbutt74:
Mounted External sdcard [exfat]

K, Z, [MENTION=6584695]CTXz[/MENTION]

Okay, continuing from my previous post on mounting your exfat external sdcard,

This works in CM13 and should in AOSP, admittedly it's a little sloppy but hey.

Changes in boot.img as follows:

/sbin/<name of script>

Script contents:

#!/system/bin/sh
mount -o rw,remount /
mkdir /mnt/media_rw/sdcard1
mount.exfat -o uid=1023,gid=1023 /dev/block/mmcblk1 /mnt/media_rw/sdcard1
mkdir /storage/sdcard1
mount -o bind,uid=1023,gid=1023 /mnt/media_rw/sdcard1 /storage/sdcard1
mount -o ro,remount /

/init.environ.rc

add the following line below

export SECONDARY_STORAGE /storage/sdcard1

/init.rc

make sure media_rw is 755

mkdir /mnt/media_rw 0755 root media_rw

AT THE VERY BOTTOM OF init.rc <just to make sure everything else is already in place,

add the service which will fire the script

service <name of script> /sbin/<name of script>
class main
oneshot

repack the boot.img and flash, recognition should be instant though some apps will still not register

the existence of the card, haven't tested on a full factory reset yet.

Again from my previous post, you must have exfat support patched into kernel,

you must make sure to include in boardconfig.mk

TARGET_KERNEL_HAVE_EXFAT := true

so your rom-side support will compile, all the exfat stuff.

m

K, i will make the mod to your build and test it out in a bit. I did not utilize the fstab in this so your external card will not be picked up as a candidate for adoptable storage.

[MENTION=4340984]krabappel2548[/MENTION]

Okay, yeah you don't have the rom-side exfat support, you're kernel's good.

You're missing:

/system/bin/exfatck
/system/bin/exfatinfo
/system/bin/exfatlabel
/system/bin/exfatvsn
/system/bin/fsck.exfat
/system/bin/mkexfat
/system/bin/mkfs.exfat
/system/bin/mount.exfat

/system/lib64/libexfat.so
/system/lib64/libfuse.so

I've attached the above mentioned files for convenience.

The above files i pushed into your build from cm13. Although vold still seems to accuse the card of being corrupt.

After pushing the above mentioned files in conjuction with the modifications to boot.img mentioned previously i do get my card to mount @ an alternate point. /sdcard1 , and it does pick up as storage in totalcommander file manager. but still doesn't get past the vold smell test so no other apps looking for "proper" mount point see it.

Okay final round,

after factory resetting, with your original boot.img modified only with the bootrec setup for booting into recovery, and the aforementioned files for exfat support rom-side:

The card initially comes up as corrupt,

Format for Portable storage succeeds , card useable normally.

Format for internal storage corrupts, I am guessing it to be an issue with the size of the card [128gb]

as two additional partitions are created but neither readable, i don't have a 32gb card to test/verify..

Card format as portable storage seems to survive across reboots so :good: ?

So adoptable storage option for this size card seems to be broken.

m
[Xperia Z5 Premium Android Development] zacharias.maladroit:
on closer look - this is an issue of the naming scheme of devices:

if devices e.g. are attached, not properly unmounted and then another one attached

the previous device name is already taken - so a "simple" script will fail

You could either see whether it works

1) with regular expressions:

mounting it via mmcblk1p*

(don't ask how to do it - I haven't done it yet ;) )

2) with persistent naming:

/dev/disk/by-id , by-label (does exFAT use these ?), by-uuid

https://wiki.archlinux.org/index.php/persistent_block_device_naming

http://unix.stackexchange.com/questions/86764/understanding-dev-disk-by-folders

http://unix.stackexchange.com/quest...a-way-to-change-a-device-id-in-dev-disk-by-id

http://unix.stackexchange.com/questions/86764/understanding-dev-disk-by-folders
[Xperia Z5 Premium Android Development] Rubensss:
I flashed via fastboot files and reboots the phone screen only Sony ... why this happens ?
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Make sure you really flash all:

(recovery is not necessarily needed for the AOSP to boot up)

otherwise you'll get into a loop during boot,

otherwise:

do an emergency off,

flash again and see whether that helps (it did once or twice for me)
[Xperia Z5 Premium Android Development] Rubensss:
I try to flash it again without recovery.img No I have to do before flashing wipes ?
[Xperia Z5 Premium Android Development] zacharias.maladroit:
formatting /cache, wiping dalvik cache

might help, yes

Not sure what else you have in mind :confused:

Backup your data since this will surely wipe internal storage (userdata.img)
[Xperia Z5 Premium Android Development] Rubensss:
I have tried again , this time making full and wipes without flashing recovery.img but when you start the phone gets directly to the TWRP recovery ... I've flashed 2 times and does the same. I think I 'll wait to see if they make a flashable file TWRP , thank you very much anyway zacharias.maladroit . By the way , I have installed in your kernel v.2.2 and will RomAur luxury . a greeting
[Xperia Z5 Premium Android Development] engineer000:
I'm having bootloops as well. I cleared the system, cache and dalvik using TWRP. Model is 6833
[Xperia Z5 Premium Android Development] frostmore:
May I know what is the difference between your build and fxp's aosp?
[Xperia Z5 Premium Android Development] zacharias.maladroit:
There are FXP Marshmallow builds ?

Link please :)
[Xperia Z5 Premium Android Development] engineer000:
I searched and I see this:

http://fxpblog.co/aosp/aosp-6-0/

http://uploaded.net/f/53n94q

AOSP_M_160416_satsuki.zip seems to be the latest. What do you think? [MENTION=3037651]zacharias.maladroit[/MENTION]

I might be wrong but you can check guys! :D
[LG V10 Q&A, Help & Troubleshooting] praveen5344:
With help of this great forum, i could get this far, getting below things done on my phone.

1. Unlocking Bootloader

2. Installing a Custom Recovery

3. Rooting

Can someone help me how to do network unlock for LG V10 T-mobile H901 model please?

Is there any patch i can use to get this done.?

Thanks in advance.
[LG V10 Q&A, Help & Troubleshooting] ryanzurlo88:
how long have you had the phone? I had mine about 2 weeks after signing up with T-Mobile and I used the device unlock app that comes on the phone and its unlocked.

the one pic says unlock failed only because its already been unlocked. that's why the 2nd pic says unlocked approved
[LG V10 Q&A, Help & Troubleshooting] praveen5344:
I got this phone over craigslist, i am actually not a t-mobile customer. so T-mobile couldnt unlock this phone.

I tried few paid services, but all of them refunded me back that they were unable to unlock the device remotely.
[LG V10 Q&A, Help & Troubleshooting] ryanzurlo88:
Do you have any friends with T-Mobile that would let you borrow their SIM card to try and use the device unlock app? I'm just throwing a fart in the wind here hoping it catches in a net for you.

---------- Post added at 05:03 AM ---------- Previous post was at 05:02 AM ----------

I mean it is an awesome phone. Just sucks you can't use it right now.
[G 2014 Q&A, Help & Troubleshooting] wallywalters:
I'm a complete newbie to Android, so I ask your forebearance in advance if I've broken any forum guidelines or posted in the wrong place or anything.

When I rooted my Moto G (2nd gen) I saved my backup to a microSD card, but that card is corrupted/inaccessible and I now wish to restore the stock firmware so as to upgrade to Android 6.0. To complicate matters further, my Windows 7 PC does not recognize the phone when connected by USB cable -- though the phone charges -- so I can't follow "restore" procedures like the ones at the Moto G Tips blog (goo.gl/NCWR7q).

Is there any other way to (procure a copy of the XT1063 files and) restore them, hopefully from a (working) microSD card? Thank you.
[XDA Assist] XDA Visitor:
iam using Asus Zenfone 2 ZE500CL

I do not have any rock cook for it

XDA,either

i really want to experience a rom **** !!

can you produce a rom **** for me???

please please!!!

my email:dunganhroyal@gmail.com
[XDA Assist] Trafalgar Square:
Hello,

XDA Assist is not for requesting ROMs. XDA Assist if for newbies finding their way around on XDA.

Thread closed.

There are ROMs:

ZenFone 2 Android Development
[Galaxy S6 Q&A, Help & Troubleshooting] randika171:
So I just got the marshmallow update

for my S6 G920I and the mode icon has this weird border which makes it look ugly. Anyway to fix this weird bug? Also when I click the mode icon the info icon on top also has this weird border.
[Galaxy S6 Q&A, Help & Troubleshooting] MasterPH:
Try clearing camera app data. If it doesnt work maybe a reset?
[Galaxy S6 Q&A, Help & Troubleshooting] randika171:
Tried the camera reset didn't work. Can't do a factory reset too much valuable data. Oh well guess I'll have to live with it :)
[Shield Android TV Q&A, Help & Troubleshooting] Umisguy:
I have a MOGA pocket bluetooth controller somewhere , but it's nowhere near as nice as the nvidia shield controller. I have sideloaded a couple apps that want to use a moga controller , and while I'm sure I could attach a moga controller to the Shield Android TV, it seems ridiculous to have to do that when a superior controller exists as standard. Some games (I own the Need for speed game) only allow touch, motion, or moga.. and it would not allow me to use the shield controller. Anyone got any ideas? there are apps that make the moga work on games not made for it, but I've yet to find a way for the shield controller to pretend to be a MOGA
[Shield Android TV Q&A, Help & Troubleshooting] Slayerkodi:
This would be very useful for what i need it for too, i want to play NOVA 3 and it has moga support and sort of recognises the shiled controller as moga wierdly, but again the issue with the right analog stick being a mouse and not being able to map the buttons. So the app to make shield tv think shield controller is MOGA would work for a lot of games we otherwise would not be able to play. very useful
[Shield Android TV Q&A, Help & Troubleshooting] Umisguy:
is there anywhere I should request such a thing be made? I mean, I can't donate toward it right now... but I'd be interested in proving there is interest for such a feature or app made available to shield devices.
[Shield Android TV Q&A, Help & Troubleshooting] Sub-Negro:
Yeah I think it has to do with the Shield being Wi-Fi direct instead of Bluetooth. Im pretty sure someone could hack it via root.
[Galaxy S III General] Hawaii_Beach:
QnA:

The questions are kinda copied from the old guide.

Q: Why is /cache a large partition?

A: It's because stock software updates saves in the partition. The partition was extended(CN) when upgrading to Android 4.3, as the update was so large, the cache partition had to be as well. AOSP does NOT use the partition when updating.

Q: What is the /preload partition for?

A: It's only really used if you bought the phone locked. Many mobile operators put in extra apps, and bloatware too in the partition only utilized in stock firmware; and even then... There's some random Samsung crap too. REPIT minimizes the partition.

Q: Any consequences of flashing?

A: Yes, you will NOT be able to install stock firmwares (assuming that you're not running stock). A undo is easy as the script is so flexible.

You will also burn a lot of eMMC life cycles using REPIT so don't do it often, and I hope you've read 1. where I covered the buggy eMMC chip thingy.

Q: Something went wrong with flashing the zip file!

A: Please upload the REPIT log usally found in the folder where you placed the flashable zip file to dropbox, or https://paste.tinyw.in; apparently pastebin doesn't like long logs. Can also be in /tmp. Otherwise you can copy the whole TWRP log found in /tmp/recovery.log, /cache/recovery/log or /cache/recovery/last_log. NEVER copy the whole log and make a post out of it, you're spamming the thread by doing so. Issues with REPIT should NOT be reported here, instead go to the REPIT GitHub page here.

Q: I want to undo these changes!

A: Since [MENTION=4141005]Lanchon[/MENTION] is taking over this thread :laugh:, ask him. Sorry for me not doing my homework.

Q: How about the x GB model?

A: They all work, REPIT is designed to assign any leftovers to the partition we use.

More questions? Bring them on.
[Galaxy S III General] Hawaii_Beach:
Reserved #2
[Galaxy S III General] nicesoni_ash:
May be it's better to give proper credits too considering it was a big mess up in past.

Sent from my "i9300/1+2" powered by Carbon/Temasek

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III General] Hawaii_Beach:
Woops, I made the guide in notepad++, and accedently removed some lines when editing it; including a better credit to [MENTION=4141005]Lanchon[/MENTION]; adding in a new one now.
[Galaxy S III General] nicesoni_ash:
I meant in your op too.

Sent from my "i9300/1+2" powered by Carbon/Temasek

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III General] Sincci:
Btw, is it possible to modify this script somehow so that you can reformat the /cache partition to f2fs? Afaik the minimum size is 100mb.
[Galaxy S III General] Hawaii_Beach:
No, I'm sorry. It is already known, on GitHub: #8.

The minimum size of /cache? The script sets /cache to 32240kB which is 32MB..
[Galaxy S III General] Hawaii_Beach:
OP?
[Galaxy S III General] nicesoni_ash:
After I read your conversation with [MENTION=4141005]Lanchon[/MENTION] on git, it seems to me that there is no need to wipe data and it will still work, it's that right?

OP - Original Post basically referred to first post.

Sent from my "i9300/1+2" powered by Carbon/Temasek

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III General] Hawaii_Beach:
Yes, you don't need to wipe /data. It just makes things faster; as you wont have to move the content around. Without wiping, it will take a longer time to re-partition.

The script will NOT wipe /data except you add +wipe to -data=max (-data=max+wipe-i9300)

OP has so many meanings, it's f***ed.
[Galaxy S III General] Lanchon:
hi, thanks for the guide!

actually, the external sdcard will always be slower than the internal eMMC. also, the extra free space gets auto-TRIMmed in /data, making the whole eMMC (and thus your phone) faster. also, adopted storage diminishes the total reliability of your phone and data (more devices can fail).

in all, i'd recommend anybody with less than 2 or 3GB free space in /data to REPIT; it's safe and easy.

---------- Post added at 05:35 PM ---------- Previous post was at 05:22 PM ----------

REPIT does not support f2fs for now.

(future support will not include wipe without resizing, as f2fs does not support that yet.)

but you can get what you want anyway:

"-cache=0.03125+wipe"

actually means

"-cache=0.03125+wipe+ext4"

given that ext4 is the default FS for "cache".

"wipe" means format, and never mind what was there before. even if it was something that wasn't ext4 at all, it will succeed.

so you can use:

"-cache=0.0976+wipe"

to get exactly 100MiB-sized cache (in ext4)

then, afterwards, use TWRP to format cache in F2FS

and you'd get what you want.

but...

DON'T!!!

dont use F2FS in ANY partition besides /data! it makes NO sense!

F2FS has an overhead of about 100MB, so basically you would be creating a /cache that is unable to hold any files at all. (ext4 has 5MB overhead.)

and why have a dysfunctional /cache? what for? to have problems? incompatibilities?

certainly not performance, because cache is NEVER used in android. so why do it?

it's soft of a crazy fad, like /system in f2fs.

/system, the one partition we never write to, lol :)

---------- Post added at 05:39 PM ---------- Previous post was at 05:35 PM ----------

thanks! :)

no credit required!!! the GPL allows him to do as he pleases, as long as he doesn't remove the license or claims copyright.

but anyway, thanks for the credit :) appreciated!

and thanks for invaluable help to port to i9300!!

---------- Post added at 05:43 PM ---------- Previous post was at 05:39 PM ----------

btw, i should start thanking the people who helped with the ports in the comments of the device port file. so far 2. i will back-credit when i get the time.

and i9305 and others are probably trivially supported, i just need the dumps done.
[Galaxy S III General] Hawaii_Beach:
The thing is that not only could REPIT be ported to i9300, but any other Samsung device, right? They all run TouchWiz; for example s4, s5, s6? Have anyone even checked partitions on those devices?

The thing with partitions and the Android community is that almost no one discusses it. If you do a google on partitions on Android; very Little information / threads exist.
[Galaxy S III General] Hawaii_Beach:
To be honest, I never cared about storage speed (same goes for trim), not a heavy user on my phone, and have never been, just doesn't go well when I'm the operator. As long as it doesn't take 1 year to copy my secret .mp4's (ransom.mp4 and many more), there's no worries.

About failure, it's like running a computer. If you shut down a computer without sending signals (unplug from wall etc), it may damage the harddrive; right? Same here. Right?

Any how, If I ever run out of space on my i9300, I'd just add a sd-card. I don't save anything important on my device that doesn't get backed up via TWRP. But..

that's never going to happen! Because my OnePlus One is coming back from RMA service! (finally after 4 months (not kidding)). kinda off topic, but hey; it's my thread right :D :confused: :cool: :good:
[Galaxy S III General] Lanchon:
lol about the quote :)

besides the name playing on samsung's PIT files, REPIT can actually work on any device with TWRP support. but the partition layout in most newer devices is friendly enough not to bother. even the stock i9300 layout is sort of friendly. highly problematic are only the devices that shipped before ICS with android 2.x (galaxy S2) or devices that shipped with non-emulated internal sdcard.

discussion is low volume because partitioning is considered 'dangerous'. and it can be, you can brick if you mess up. the idea of REPIT was to make it safe by encapsulating a bit of knowledge of each device in the device port file. motivation was that S2 users suddenly all needed to repit: their devices stopped working after a nightly flash because of /system being too small, it was a mess, lol.

btw, since you asked before, that's the reason why porting is needed: because you can't trust users not to make mistakes with full freedom. users that want full freedom have other tools: gdisk, parted, mkfs.xxx, resize2fs, etc.