Hi!
I am experiencing yaffs2 filesystem corruption on the data partition of my Desire.
The errors are always quite similar: Directory entries with empty names that point to the parent directory:
Code:
# ls -lia /data/data/com.android.providers.contacts/lib/databases
total 6
2006 drwxr-xr-x 1 10006 10006 2048 Apr 8 22:30
2006 drwxr-xr-x 1 10006 10006 2048 Apr 8 22:30 .
1737 drwxr-xr-x 1 1000 1000 2048 Apr 9 07:49 ..
It looks very similar to this report.
I've already tried several ROMs (most recently AceSMod007 and RevolutioN v3.0) but both use kernel 2.6.35.14-gingercakes-0.9-avs that maybe doesn't contain the fix.
Can anyone recommend a kernel that includes this patch?
I was wondering where init.d might be located on 5X? Not able to find it in /system/etc/ like most devices.
Basically trying to include a new init.d script but not sure where to put it.
Thanks in advance!
catharsis724 said:
I was wondering where init.d might be located on 5X? Not able to find it in /system/etc/ like most devices.
Basically trying to include a new init.d script but not sure where to put it.
Thanks in advance!
Click to expand...
Click to collapse
Try placing in /su/su.d/ if you're rooted with superSU
Sent from my SHIELD Tablet K1 using Tapatalk
Exile1975 said:
Try placing in /su/su.d/ if you're rooted with superSU
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Might not have that because I have systemless phh Superuser.
Code:
bullhead:/ # ls
...
drwxr-xr-x 3 0 2016-11-28 00:38 res
drwx------ 2 0 2016-11-07 18:55 root
drwxr-xr-x 3 4.0K 2016-11-28 11:20 sbin
lrwxrwxrwx 1 21 2016-11-28 00:38 sdcard -> /storage/self/primary
-rw-r--r-- 1 758 2016-11-28 00:38 seapp_contexts
-rw-r--r-- 1 68 2016-11-28 00:38 selinux_version
-rw-r--r-- 1 203K 2016-11-28 00:38 sepolicy
-rw-r--r-- 1 11K 2016-11-28 00:38 service_contexts
drwxr-xr-x 4 80 2016-11-28 11:20 storage
dr-xr-xr-x 13 0 1971-01-18 11:50 sys
drwxr-xr-x 17 4.0K 2016-11-27 15:50 system
...
Hello,
I just want to compile Lineageos 16.0 for my old HTC10 (PME).
I followed the guide at wiki.lineageos.org/devices/pme/build
I have synced the repo without issues.
Now I have the problem to integrate the proprietary blobs into the source tree.
I have extracted the files from an available ROM.
The files are now stored under
/android/system_dump/system
Code:
[email protected]:~/android/system_dump/system$ ls -al
insgesamt 2720
drwxr-xr-x. 20 root root 4096 Jan 1 2009 .
drwxrwxr-x 6 lineageos lineageos 4096 Sep 14 22:15 ..
drwxr-xr-x. 2 root root 4096 Jan 1 2009 addon.d
drwxr-xr-x. 55 root root 4096 Jan 1 2009 app
drwxr-xr-x. 3 root 2000 8192 Jan 1 2009 bin
-rw-------. 1 root root 7409 Jan 1 2009 build.prop
-rw-r--r--. 1 root root 116235 Jan 1 2009 compatibility_matrix.xml
drwxr-xr-x. 3 root root 4096 Jan 1 2009 customize
drwxr-xr-x. 21 root root 4096 Jan 1 2009 etc
drwxr-xr-x. 2 root root 4096 Jan 1 2009 fake-libs
drwxr-xr-x. 2 root root 4096 Jan 1 2009 fake-libs64
drwxr-xr-x. 2 root root 12288 Jan 1 2009 fonts
drwxr-xr-x. 5 root root 4096 Jan 1 2009 framework
drwxr-xr-x. 6 root root 16384 Jan 1 2009 lib
drwxr-xr-x. 6 root root 16384 Jan 1 2009 lib64
drwx------. 2 root root 16384 Jan 1 2009 lost+found
drwxr-xr-x. 3 root root 4096 Jan 1 2009 media
drwxr-xr-x. 62 root root 4096 Jan 1 2009 priv-app
drwxr-xr-x. 2 root root 4096 Jan 1 2009 product
-rw-r--r--. 1 root root 2524803 Jan 1 2009 recovery-from-boot.p
drwxr-xr-x. 8 root root 4096 Jan 1 2009 usr
drwxr-xr-x. 15 root 2000 4096 Jan 1 2009 vendor
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 xbin
Code:
[email protected]:~/android/system_dump/system/vendor$ ls -al
insgesamt 124
drwxr-xr-x. 15 root 2000 4096 Jan 1 2009 .
drwxr-xr-x. 20 root root 4096 Jan 1 2009 ..
drwxr-xr-x. 3 root 2000 4096 Jan 1 2009 app
drwxr-xr-x. 3 root 2000 4096 Jan 1 2009 bin
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 bt_firmware
-rw-------. 1 root root 6135 Jan 1 2009 build.prop
-rw-------. 1 root root 145 Jan 1 2009 default.prop
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 dsp
drwxr-xr-x. 14 root 2000 4096 Jan 1 2009 etc
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 firmware
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 firmware_mnt
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 framework
drwxr-xr-x. 8 root 2000 20480 Jan 1 2009 lib
drwxr-xr-x. 7 root 2000 12288 Jan 1 2009 lib64
drwxr-xr-x. 5 root 2000 4096 Jan 1 2009 overlay
drwxr-xr-x. 3 root 2000 4096 Jan 1 2009 radio
drwxr-xr-x. 3 root 2000 4096 Jan 1 2009 rfs
-rw-r--r--. 1 root root 23343 Jan 1 2009 ueventd.rc
Which files do I need? To which location must I copy the files so breakfast recognizes them?
Extract script did not work. It's for the old CyanogenMod 14.1. I have tried to edit the path variable to my lineageos source but it is still not working.
./extract-files.sh ~/android/system_dump/
(The extract script wasn't in the source tree so I copied it from github.com/LineageOS/android_device_htc_pme
But it's from the "cm14-1" source tree. I also copied the "setup-makefiles.sh" file)
Launching "breakfast pme" fails.
Code:
[email protected]:~/android/lineage$ source build/envsetup.sh
including device/generic/car/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including device/generic/uml/vendorsetup.sh
including vendor/lineage/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/android/lineage$ breakfast pme
including vendor/lineage/vendorsetup.sh
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_pme".
13:17:58 dumpvars failed with: exit status 1
Device pme not found. Attempting to retrieve device repository from LineageOS (Github github.com/LineageOS).
Found repository: android_device_htc_pme
Default revision: lineage-16.0
Checking branch info
Default revision lineage-16.0 not found in android_device_htc_pme. Bailing.
Branches found:
cm-13.0
cm-14.1
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_pme".
13:18:00 dumpvars failed with: exit status 1
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_pme".
13:18:01 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_pme'
** Do you have the right repo manifest?
What must I do that the proprietary blobs/ firmware filles are working with the "breakfast pme" command?
I would appreciate any help so I could start compiling lineageos 16.0 for my HTC10.
Thank you in advance.
regards
starbuck28
Hey Guys,
i wanted to check what to do, for trying to port a newer Lineage release to this device.
Any hints where to begin?
I luckily compiled the 14.1 branch yesterday.
But what to do next?
Regards for the hints
I've been investigating this recently as well. I started looking at LineageOS 16.0 branch and the Exynos5420 kernal/rom code on github ("https://github.com/exynos5420"), as I am running a build on the tablet from here:-
"https://download.exynos5420.com/LineageOS-14.1-Vanilla/chagalllte/"
BTW, I'm a late/newcomer to android rom development, and I may be off track/incorrect anyways.
I've attempted building branch lineage16.0 with Exynos5420 and currently throws this error :-
bionic/libc/include/bits/fortify/fcntl.h:63:26: error: use of undeclared identifier 'O_TMPFILE'
__clang_error_if(__open_modes_useful(flags), "'open' " __open_too_few_args_error)
The bionic libc wants a definition for O_TMPFILE , I think is to be resolved from the
kernel headers under the kernel device tree at:- kernel/samsung/exynos5420/include/asm-generic/fcntl.h
Of course there is no definition of 'O_TMPFILE' in this header file.
Looks like a later linux kernel version (or patches) to the Exynos5420 kernel code/device is required with headers defining O_TMPFILE.
All I can suggest for porting a newer lineageOs is, get started experimenting/building.
Find/pick up a later device kernel source code tree
For me there is alot to learn and few up-to-date guides
Good luck
bluess57 said:
I've been investigating this recently as well. I started looking at LineageOS 16.0 branch and the Exynos5420 kernal/rom code on github ("https://github.com/exynos5420"), as I am running a build on the tablet from here:-
"https://download.exynos5420.com/LineageOS-14.1-Vanilla/chagalllte/"
BTW, I'm a late/newcomer to android rom development, and I may be off track/incorrect anyways.
I've attempted building branch lineage16.0 with Exynos5420 and currently throws this error :-
bionic/libc/include/bits/fortify/fcntl.h:63:26: error: use of undeclared identifier 'O_TMPFILE'
__clang_error_if(__open_modes_useful(flags), "'open' " __open_too_few_args_error)
The bionic libc wants a definition for O_TMPFILE , I think is to be resolved from the
kernel headers under the kernel device tree at:- kernel/samsung/exynos5420/include/asm-generic/fcntl.h
Of course there is no definition of 'O_TMPFILE' in this header file.
Looks like a later linux kernel version (or patches) to the Exynos5420 kernel code/device is required with headers defining O_TMPFILE.
All I can suggest for porting a newer lineageOs is, get started experimenting/building.
Find/pick up a later device kernel source code tree
For me there is alot to learn and few up-to-date guides
Good luck
Click to expand...
Click to collapse
Add the following lines in the header file kernel/samsung/exynos5420/include/asm-generic/fcntl.h https://github.com/alexenferman/and...mmit/e97a38cefdb63305f85139c4409a597759388081 and you are good to go.
I tried compiling 16.0 for chagallwifi (T800) over the fall and ran into a number of compiler problems, but when I finally got it to compile, the resulting image wouldn't boot. A lot of those problems have now been fixed in gerrit.
I also tried 15.1 last week, but ran into a number of compile problems. Then I noticed a lot of activity on https://github.com/exynos5420 and https://review.exynos5420.com/ wrt to 16.0 so I tried again yesterday and today and I had to make 2 modifications for it to compile, but the result is an image that won't boot. The recovery image won't boot meaning somethings wrong with the boot/kernel stage.
Hopefully the team will make more modifications over the holidays and I will have a bootable 16.0 image?
retiredtab said:
I tried compiling 16.0 for chagallwifi (T800) over the fall and ran into a number of compiler problems, but when I finally got it to compile, the resulting image wouldn't boot. A lot of those problems have now been fixed in gerrit.
I also tried 15.1 last week, but ran into a number of compile problems. Then I noticed a lot of activity on https://github.com/exynos5420 and https://review.exynos5420.com/ wrt to 16.0 so I tried again yesterday and today and I had to make 2 modifications for it to compile, but the result is an image that won't boot. The recovery image won't boot meaning somethings wrong with the boot/kernel stage.
Hopefully the team will make more modifications over the holidays and I will have a bootable 16.0 image?
Click to expand...
Click to collapse
Unpack the recovery and show me the files inside. You might be missing the init files on the recovery, like I did with the Snapdragon Galaxy S3
alexenferman said:
Unpack the recovery and show me the files inside.
Click to expand...
Click to collapse
Code:
$ abootimg -x recovery.img
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
$ ls -al
total 16000
drwxrwxr-x 2 l l 4096 Dec 22 21:11 .
drwxrwxr-x 14 l l 4096 Dec 22 21:11 ..
-rw-rw-r-- 1 l l 167 Dec 22 21:11 bootimg.cfg
-rw-rw-r-- 1 l l 3336396 Dec 22 21:11 initrd.img
-rw-rw-r-- 1 l l 8183825 Dec 22 21:11 recovery.img
-rw-rw-r-- 1 l l 4842048 Dec 22 21:11 zImage
$ cat bootimg.cfg
bootsize = 0x7ce011
pagesize = 0x800
kerneladdr = 0x10008000
ramdiskaddr = 0x11000000
secondaddr = 0x10f00000
tagsaddr = 0x10000100
name =
cmdline = buildvariant=eng
retiredtab said:
Code:
$ abootimg -x recovery.img
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
$ ls -al
total 16000
drwxrwxr-x 2 l l 4096 Dec 22 21:11 .
drwxrwxr-x 14 l l 4096 Dec 22 21:11 ..
-rw-rw-r-- 1 l l 167 Dec 22 21:11 bootimg.cfg
-rw-rw-r-- 1 l l 3336396 Dec 22 21:11 initrd.img
-rw-rw-r-- 1 l l 8183825 Dec 22 21:11 recovery.img
-rw-rw-r-- 1 l l 4842048 Dec 22 21:11 zImage
$ cat bootimg.cfg
bootsize = 0x7ce011
pagesize = 0x800
kerneladdr = 0x10008000
ramdiskaddr = 0x11000000
secondaddr = 0x10f00000
tagsaddr = 0x10000100
name =
cmdline = buildvariant=eng
Click to expand...
Click to collapse
Sorry I meant Ramdisk of the recovery
$ ls -al 16/out/target/product/chagallwifi/ram*
-rw-rw-r-- 1 l l 1766995 Dec 22 17:49 ramdisk.img
-rw-rw-r-- 1 l l 9298176 Dec 22 17:49 ramdisk-recovery.cpio
-rw-rw-r-- 1 l l 3336396 Dec 22 17:49 ramdisk-recovery.img
/media/l/16/16/out/target/product/chagallwifi$
Code:
$ ./unpack_ramdisk ramdisk.img
6493 blocks
$ cd ramdisk/
$ ls -al
total 2248
drwxrwxr-x 16 l l 4096 Dec 22 22:01 .
drwxrwxr-x 3 l l 4096 Dec 22 22:01 ..
drwxr-xr-x 2 l l 4096 Dec 22 22:01 acct
lrwxrwxrwx 1 l l 11 Dec 22 22:01 bin -> /system/bin
lrwxrwxrwx 1 l l 50 Dec 22 22:01 bugreports -> /data/user_de/0/com.android.shell/files/bugreports
drwxrwx--- 2 l l 4096 Dec 22 22:01 cache
lrwxrwxrwx 1 l l 13 Dec 22 22:01 charger -> /sbin/charger
dr-xr-xr-x 2 l l 4096 Dec 22 22:01 config
lrwxrwxrwx 1 l l 17 Dec 22 22:01 d -> /sys/kernel/debug
drwxrwx--x 2 l l 4096 Dec 22 22:01 data
-rw------- 1 l l 1334 Dec 22 22:01 default.prop
drwxr-xr-x 2 l l 4096 Dec 22 22:01 dev
lrwxrwxrwx 1 l l 11 Dec 22 22:01 etc -> /system/etc
-rw-r----- 1 l l 2313 Dec 22 22:01 fstab.universal5420
-rwxr-x--- 1 l l 1637644 Dec 22 22:01 init
-rwxr-x--- 1 l l 1154 Dec 22 22:01 init.environ.rc
-rwxr-x--- 1 l l 29431 Dec 22 22:01 init.rc
-rwxr-x--- 1 l l 1524 Dec 22 22:01 init.samsung.rc
-rwxr-x--- 1 l l 2458 Dec 22 22:01 init.target.rc
-rwxr-x--- 1 l l 26408 Dec 22 22:01 init.universal5420.rc
-rwxr-x--- 1 l l 8107 Dec 22 22:01 init.universal5420.usb.rc
-rwxr-x--- 1 l l 2399 Dec 22 22:01 init.universal5420.wifi.rc
-rwxr-x--- 1 l l 7690 Dec 22 22:01 init.usb.configfs.rc
-rwxr-x--- 1 l l 5646 Dec 22 22:01 init.usb.rc
-rwxr-x--- 1 l l 511 Dec 22 22:01 init.zygote32.rc
drwxr-xr-x 2 l l 4096 Dec 22 22:01 mnt
drwxr-xr-x 2 l l 4096 Dec 22 22:01 odm
drwxr-xr-x 2 l l 4096 Dec 22 22:01 oem
-rw-r--r-- 1 l l 25053 Dec 22 22:01 plat_file_contexts
-rw-r--r-- 1 l l 7212 Dec 22 22:01 plat_hwservice_contexts
-rw-r--r-- 1 l l 7102 Dec 22 22:01 plat_property_contexts
-rw-r--r-- 1 l l 1551 Dec 22 22:01 plat_seapp_contexts
-rw-r--r-- 1 l l 14700 Dec 22 22:01 plat_service_contexts
drwxr-xr-x 2 l l 4096 Dec 22 22:01 proc
lrwxrwxrwx 1 l l 15 Dec 22 22:01 product -> /system/product
drwxr-xr-x 3 l l 4096 Dec 22 22:01 res
drwxr-x--- 2 l l 4096 Dec 22 22:01 sbin
lrwxrwxrwx 1 l l 21 Dec 22 22:01 sdcard -> /storage/self/primary
-rw-r--r-- 1 l l 384688 Dec 22 22:01 sepolicy
drwxr-x--x 2 l l 4096 Dec 22 22:01 storage
drwxr-xr-x 2 l l 4096 Dec 22 22:01 sys
drwxr-xr-x 2 l l 4096 Dec 22 22:01 system
-rw-r--r-- 1 l l 5359 Dec 22 22:01 ueventd.rc
-rw-r--r-- 1 l l 3373 Dec 22 22:01 ueventd.universal5420.rc
lrwxrwxrwx 1 l l 14 Dec 22 22:01 vendor -> /system/vendor
-rw-r--r-- 1 l l 7011 Dec 22 22:01 vendor_file_contexts
-rw-r--r-- 1 l l 1989 Dec 22 22:01 vendor_hwservice_contexts
-rw-r--r-- 1 l l 218 Dec 22 22:01 vendor_property_contexts
-rw-r--r-- 1 l l 0 Dec 22 22:01 vendor_seapp_contexts
-rw-r--r-- 1 l l 0 Dec 22 22:01 vendor_service_contexts
-rw-r--r-- 1 l l 65 Dec 22 22:01 vndservice_contexts
alexenferman said:
Sorry I meant Ramdisk of the recovery
Click to expand...
Click to collapse
Or do you mean the initrd.img inside the recovery.img file?
Here is the initrd.img inside recovery.img
Code:
$ xz -dc < initrd.img | cpio -idmv
acct
bin
bugreports
cache
config
d
data
default.prop
dev
etc
etc/mke2fs.conf
etc/mkshrc
etc/recovery.fstab
fstab.universal5420
init
init.rc
mnt
odm
odm/app
odm/bin
odm/firmware
odm/framework
odm/lib
odm/lib64
odm/overlay
odm/priv-app
oem
plat_file_contexts
plat_hwservice_contexts
plat_property_contexts
plat_seapp_contexts
plat_service_contexts
proc
product
prop.default
res
res/images
res/images/erasing_text.png
res/images/error_text.png
res/images/font.png
res/images/font_menu.png
res/images/ic_back.png
res/images/ic_back_sel.png
res/images/ic_factory_reset.png
res/images/ic_factory_reset_sel.png
res/images/ic_options_advanced.png
res/images/ic_options_advanced_sel.png
res/images/ic_reboot.png
res/images/ic_reboot_sel.png
res/images/ic_system_update.png
res/images/ic_system_update_sel.png
res/images/icon_error.png
res/images/installing_security_text.png
res/images/installing_text.png
res/images/logo_image.png
res/images/loop00000.png
res/images/loop00001.png
res/images/loop00002.png
res/images/loop00003.png
res/images/loop00004.png
res/images/loop00005.png
res/images/loop00006.png
res/images/loop00007.png
res/images/loop00008.png
res/images/loop00009.png
res/images/loop00010.png
res/images/loop00011.png
res/images/loop00012.png
res/images/loop00013.png
res/images/loop00014.png
res/images/loop00015.png
res/images/loop00016.png
res/images/loop00017.png
res/images/loop00018.png
res/images/loop00019.png
res/images/loop00020.png
res/images/loop00021.png
res/images/loop00022.png
res/images/loop00023.png
res/images/loop00024.png
res/images/loop00025.png
res/images/loop00026.png
res/images/loop00027.png
res/images/loop00028.png
res/images/loop00029.png
res/images/no_command_text.png
res/images/progress_empty.png
res/images/progress_fill.png
res/images/stage_empty.png
res/images/stage_fill.png
res/keys
sbin
sbin/acpi
sbin/adbd
sbin/awk
sbin/base64
sbin/basename
sbin/blockdev
sbin/bu
sbin/cal
sbin/cat
sbin/chcon
sbin/chgrp
sbin/chmod
sbin/chown
sbin/chroot
sbin/chrt
sbin/cksum
sbin/clear
sbin/cmp
sbin/comm
sbin/cp
sbin/cpio
sbin/cut
sbin/date
sbin/dd
sbin/df
sbin/diff
sbin/dirname
sbin/dmesg
sbin/dos2unix
sbin/du
sbin/e2fsck
sbin/e2fsdroid
sbin/e2fsdroid_static
sbin/echo
sbin/env
sbin/expand
sbin/expr
sbin/fallocate
sbin/false
sbin/file
sbin/find
sbin/flock
sbin/fmt
sbin/free
sbin/fsck.exfat
sbin/fsck.ext4
sbin/fsck.f2fs
sbin/fsck.ntfs
sbin/fsck_msdos
sbin/getenforce
sbin/getprop
sbin/grep
sbin/groups
sbin/gunzip
sbin/gzip
sbin/head
sbin/hostname
sbin/hwclock
sbin/id
sbin/ifconfig
sbin/inotifyd
sbin/insmod
sbin/install
sbin/ionice
sbin/iorenice
sbin/kill
sbin/killall
sbin/ln
sbin/load_policy
sbin/log
sbin/logname
sbin/losetup
sbin/ls
sbin/lsmod
sbin/lsof
sbin/lspci
sbin/lsusb
sbin/md5sum
sbin/microcom
sbin/mkdir
sbin/mke2fs
sbin/mke2fs_static
sbin/mkfifo
sbin/mkfs.exfat
sbin/mkfs.ext4
sbin/mkfs.f2fs
sbin/mkfs.ntfs
sbin/mknod
sbin/mkswap
sbin/mktemp
sbin/modinfo
sbin/modprobe
sbin/more
sbin/mount
sbin/mount.ntfs
sbin/mountpoint
sbin/mv
sbin/netstat
sbin/nice
sbin/nl
sbin/nohup
sbin/od
sbin/paste
sbin/patch
sbin/pgrep
sbin/pidof
sbin/pkill
sbin/pmap
sbin/printenv
sbin/printf
sbin/ps
sbin/pwd
sbin/readlink
sbin/realpath
sbin/reboot
sbin/recovery
sbin/renice
sbin/resize2fs
sbin/restorecon
sbin/rm
sbin/rmdir
sbin/rmmod
sbin/runcon
sbin/sed
sbin/sendevent
sbin/seq
sbin/setenforce
sbin/setprop
sbin/setsid
sbin/sgdisk
sbin/sh
sbin/sha1sum
sbin/sha224sum
sbin/sha256sum
sbin/sha384sum
sbin/sha512sum
sbin/sleep
sbin/sload.f2fs
sbin/sort
sbin/split
sbin/sswap
sbin/start
sbin/stat
sbin/stop
sbin/strings
sbin/stty
sbin/swapoff
sbin/swapon
sbin/sync
sbin/sysctl
sbin/tac
sbin/tail
sbin/tar
sbin/taskset
sbin/tee
sbin/time
sbin/timeout
sbin/top
sbin/touch
sbin/toybox_static
sbin/tr
sbin/true
sbin/truncate
sbin/tty
sbin/tune2fs
sbin/ueventd
sbin/ulimit
sbin/umount
sbin/uname
sbin/uniq
sbin/unix2dos
sbin/unzip
sbin/uptime
sbin/usleep
sbin/uudecode
sbin/uuencode
sbin/vmstat
sbin/watchdogd
sbin/wc
sbin/which
sbin/whoami
sbin/xargs
sbin/xxd
sbin/yes
sbin/zcat
sbin/zip
sdcard
sepolicy
storage
sys
system
tmp
ueventd.rc
ueventd.universal5420.rc
vendor_file_contexts
vendor_hwservice_contexts
vendor_property_contexts
vendor_seapp_contexts
vendor_service_contexts
vndservice_contexts
18161 blocks
I have a 16.0 SM-T800 build booting now. Now I have to go through and see what works and doesn't work. This will take a couple of days.
I will also document what patches I needed to make this work not only for myself, but for other future builders.
Please join the exynos5420 team to contribute to getting LineageOS 16 fully functional.
retiredtab said:
I have a 16.0 SM-T800 build booting now. Now I have to go through and see what works and doesn't work. This will take a couple of days.
I will also document what patches I needed to make this work not only for myself, but for other future builders.
Click to expand...
Click to collapse
What did you have to fix? I am building Los 16 for a Los 14 device too, kernel appears to be working, but it does not boot.
bluess57 said:
Please join the exynos5420 team to contribute to getting LineageOS 16 fully functional.
Click to expand...
Click to collapse
I will submit gerrit patches once the 16.0 code all settles down. There are camera + sensor + hal changes still to be merged. So far all bugs that I have found seem to be due to the pending or merge changes.
Some of the changes made to chagalllte weren't made to chagallwifi so it was relatively easy to copy them.
alexenferman said:
What did you have to fix? I am building Los 16 for a Los 14 device too, kernel appears to be working, but it does not boot.
Click to expand...
Click to collapse
What device are you building for? Are you building for a tab S platform?
If a device doesn't boot, I find adb logcat very helpful.
I also use this utility.
Install logcat-colorize on Ubuntu using the Snap Store | Snapcraft
Get the latest version of logcat-colorize for on Ubuntu - logcat-colorize
snapcraft.io
retiredtab said:
I will submit gerrit patches once the 16.0 code all settles down. There are camera + sensor + hal changes still to be merged. So far all bugs that I have found seem to be due to the pending or merge changes.
Some of the changes made to chagalllte weren't made to chagallwifi so it was relatively easy to copy them.
Click to expand...
Click to collapse
yeah I only have a chagalllte so some of the other devices get overlooked.
As to what's currently not functioning:-
camera video recording
sensors /sensor hal may not be fully functional
RIL
+ whatever else I can't recall atm
alexenferman said:
What did you have to fix? I am building Los 16 for a Los 14 device too, kernel appears to be working, but it does not boot.
Click to expand...
Click to collapse
by does not boot, do you mean it is stuck at the lineageos 3 rings startup animation?
bluess57 said:
As to what's currently not functioning:-
camera video recording
sensors /sensor hal may not be fully functional
RIL
+ whatever else I can't recall atm
Click to expand...
Click to collapse
What I found so far.
Doesn't work
1. home button doesn't wake up tablet. I think I know what is wrong and I'm compiling another new build, but it will take about 1 hour to complete.
2. screen rotation - which I think is due to pending merge hal/sensor changes
3. MTP, this could be due to my eng build for debugging purposes
4. camera - changes not merged. When I try a repopick -t Camera-Bringup, I get cherry-pick errors so I'm going to wait until it's all merged before I test camera.
Works
1. wifi (5 and 2.4)
2. bluetooth
3. brightness
4. external audio
5. audio through headphones
6. GPS - needs this yet to merged patch
https://review.exynos5420.com/c/exynos5420/android_device_samsung_chagalllte/+/7362
I'm not a git expert. Everytime I use it, I struggle with the commands to upload patches. But most of the problems with chagallwifi are because chagalllte commits aren't applied to it which is understandable if the developers have the LTE version.
it will be very good to switch to Los 16 SM-T800 please guys continue
bluess57 said:
yeah I only have a chagalllte so some of the other devices get overlooked.
Click to expand...
Click to collapse
I also have a SM-T700 klimtwifi which I can build and test for. However, I have more than one SM-T800 so I will build for T800 first and get all the bugs worked out and then build T700 later.
Hi,
My apologies if this post in wrong place.
I already play with adb tool on my pixel 3 xl and I notice me rare directory listing.
Code:
adb shell ls -l
total 68
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 acct
drwxr-xr-x 54 root root 1140 2022-12-10 11:14 apex
lrw-r--r-- 1 root root 11 2008-12-31 22:00 bin -> /system/bin
lrw-r--r-- 1 root root 50 2008-12-31 22:00 bugreports -> /data/user_de/0/com.android.shell/files/bugreports
l????????? ? ? ? ? ? cache -> ?
drwxr-xr-x 4 root root 0 1969-12-31 21:00 config
lrw-r--r-- 1 root root 17 2008-12-31 22:00 d -> /sys/kernel/debug
drwxrwx--x 49 system system 4096 2022-12-02 08:56 data
d????????? ? ? ? ? ? data_mirror
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 debug_ramdisk
drwxr-xr-x 23 root root 6180 2022-12-02 09:02 dev
lrw-r--r-- 1 root root 11 2008-12-31 22:00 dsp -> /vendor/dsp
lrw-r--r-- 1 root root 11 2008-12-31 22:00 etc -> /system/etc
l????????? ? ? ? ? ? init -> ?
-????????? ? ? ? ? ? init.environ.rc
d????????? ? ? ? ? ? linkerconfig
drwx------ 2 root root 16384 2008-12-31 22:00 lost+found
d????????? ? ? ? ? ? metadata
drwxr-xr-x 15 root system 320 1974-03-10 02:54 mnt
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 odm
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 odm_dlkm
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 oem
lrw-r--r-- 1 root root 19 2008-12-31 22:00 persist -> /mnt/vendor/persist
d????????? ? ? ? ? ? postinstall
dr-xr-xr-x 963 root root 0 1969-12-31 21:00 proc
drwxr-xr-x 14 root root 4096 2008-12-31 22:00 product
lrw-r--r-- 1 root root 21 2008-12-31 22:00 sdcard -> /storage/self/primary
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 second_stage_resources
drwx--x--- 4 shell everybody 80 1974-03-10 02:54 storage
dr-xr-xr-x 12 root root 0 1974-03-10 02:54 sys
drwxr-xr-x 12 root root 4096 2008-12-31 22:00 system
drwxr-xr-x 9 root root 4096 2008-12-31 22:00 system_ext
drwxr-xr-x 20 root shell 4096 2008-12-31 22:00 vendor
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 vendor_dlkm
Anyone could light me what mean '??????? ?? ? ? " directory ?
Regards.