Related
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?
Dear jellaxy developers,
I'm not allowed to ask this one in the development section, because I am a noob with less then 10 posts. Obviously I have to post 10 posts.....
CM10 2012-11-04: GIO:
Great Release, no Problems so far. For me faster and more memory efficient than cm9.
But BLN does not work. In earlier CM9 releases I managed to get some liblights.so to get it running. In a later post I found erikcas mentioning that the lights.so have to be deleted... Neither works. My /system/lib/hw looks like:
localhost hw # ls -l
total 1177
-rw-r--r-- 1 root root 58768 Aug 1 2008 audio.a2dp.default.so
-rw-r--r-- 1 root root 5524 Aug 1 2008 audio.primary.default.so
-rw-r--r-- 1 root root 50692 Aug 1 2008 audio.primary.gio.so
-rw-r--r-- 1 root root 75324 Aug 1 2008 audio_policy.default.so
-rw-r--r-- 1 root root 75320 Aug 1 2008 audio_policy.gio.so
-rw-r--r-- 1 root root 17800 Aug 1 2008 camera.gio.so
-rw-r--r-- 1 root root 9552 Aug 1 2008 copybit.msm7x27.so
-rw-r--r-- 1 root root 9608 Aug 1 2008 gps.goldfish.so
-rw-r--r-- 1 root root 60788 Aug 1 2008 gps.msm7x27.so
-rw-r--r-- 1 root root 9888 Aug 1 2008 gralloc.default.so
-rw-r--r-- 1 root root 18104 Aug 1 2008 gralloc.msm7x27.so
-rw-r--r-- 1 root root 42348 Aug 1 2008 hwcomposer.msm7x27.so
-rw-r--r-- 1 root root 9572 Aug 1 2008 keystore.default.so
-rw-r--r-- 1 root root 9748 Aug 1 2008 lights.msm7x27.so
-rw-r--r-- 1 root root 5464 Aug 1 2008 local_time.default.so
-rw-r--r-- 1 root root 5416 Aug 1 2008 power.default.so
-rw-r--r-- 1 root root 84112 Aug 1 2008 sensors.gio.so
-rw-r--r-- 1 root root 9568 Aug 1 2008 sensors.goldfish.so
I tried to delete the lights.msm7x27, but I think this ones for the brightness of the display....
Any hints?
Best Regards
K
Rename from .zip to .so and put it in /system/lib/hw (rw-r--r--)
konstantin12 said:
Rename from .zip to .so and put it in /system/lib/hw (rw-r--r--)
Click to expand...
Click to collapse
Thanks, I tried this. It looked like that:
localhost home # mount -o rw,remount /system/system
localhost home # cd /system/lib/hw/
localhost hw # mv /data/lights.gio\(1\).zip .
localhost hw # mv lights.gio\(1\).zip lights.gio.so
localhost hw # chmod 644 lights.gio.so
localhost hw # mount -o ro,remount /systemnt /system
localhost hw # ls -l
total 1193
-rw-r--r-- 1 root root 58768 Aug 1 2008 audio.a2dp.default.so
-rw-r--r-- 1 root root 5524 Aug 1 2008 audio.primary.default.so
-rw-r--r-- 1 root root 50692 Aug 1 2008 audio.primary.gio.so
-rw-r--r-- 1 root root 75324 Aug 1 2008 audio_policy.default.so
-rw-r--r-- 1 root root 75320 Aug 1 2008 audio_policy.gio.so
-rw-r--r-- 1 root root 17800 Aug 1 2008 camera.gio.so
-rw-r--r-- 1 root root 9552 Aug 1 2008 copybit.msm7x27.so
-rw-r--r-- 1 root root 9608 Aug 1 2008 gps.goldfish.so
-rw-r--r-- 1 root root 60788 Aug 1 2008 gps.msm7x27.so
-rw-r--r-- 1 root root 9888 Aug 1 2008 gralloc.default.so
-rw-r--r-- 1 root root 18104 Aug 1 2008 gralloc.msm7x27.so
-rw-r--r-- 1 root root 42348 Aug 1 2008 hwcomposer.msm7x27.so
-rw-r--r-- 1 root root 9572 Aug 1 2008 keystore.default.so
-rw-r--r-- 1 root root 6170 Nov 8 07:59 lights.gio.so
-rw-r--r-- 1 root root 9748 Aug 1 2008 lights.msm7x27.so
-rw-r--r-- 1 root root 5464 Aug 1 2008 local_time.default.so
-rw-r--r-- 1 root root 5416 Aug 1 2008 power.default.so
-rw-r--r-- 1 root root 84112 Aug 1 2008 sensors.gio.so
-rw-r--r-- 1 root root 9568 Aug 1 2008 sensors.goldfish.so
localhost hw # exit
BLN Control still shows an error.
Maybe I should try a fresh install, since I upgraded from a CM9. Hmmm.
D859 has 2sims, I can't use other g3 template, right
I already read a loi of information from cm wiki about hout to build a cm,
but I still have any clue yet,
I got D859 official rom scr code yesterday from opensource.lge.com,
I don't know how can I start for building cm,
I need some help, thank you!:laugh:
Here is the list of the files
LGD859_Lollipop_LGD859_V20a_Android_opensource/android/external: $ ls -al
drwxr-xr-x 17 578 brctl
drwxr-xr-x 21 714 dnsmasq
drwxr-xr-x 44 1496 e2fsprogs
drwxr-xr-x 7 238 ebtables
drwxr-xr-x 12 408 gcc-demangle
drwxr-xr-x 25 850 iproute2
drwxr-xr-x 21 714 iptables
drwxr-xr-x 31 1054 iputils
drwxr-xr-x 15 510 junit
drwxr-xr-x 41 1394 libexif
drwxr-xr-x 20 680 libnetfilter_conntrack
drwxr-xr-x 16 544 libnfnetlink
drwxr-xr-x 18 612 libnl
LGD859_Lollipop_LGD859_V20a_Android_opensource/android/vendor/lge: $ ls -la
drwxr-xr-x 3 102 apps
drwxr-xr-x 3 102 build
drwxr-xr-x 5 170 external
drwxr-xr-x 3 102 factory
drwxr-xr-x 4 136 frameworks
drwxr-xr-x 3 102 prebuilt
drwxr-xr-x 4 136 system
LGD859_Lollipop_LGD859_V20a_Android_opensource/kernel: $ ls -al
-rw-r--r-- 1 5935 AndroidKernel.mk
-rw-r--r-- 1 18693 COPYING
-rw-r--r-- 1 94984 CREDITS
drwxr-xr-x 237 8058 Documentation
-rw-r--r-- 1 2536 Kbuild
-rw-r--r-- 1 252 Kconfig
-rw-r--r-- 1 210475 MAINTAINERS
-rw-r--r-- 1 53855 Makefile
-rw-r--r-- 1 364155 Module.symvers
-rw-r--r-- 1 17459 README
-rw-r--r-- 1 3371 REPORTING-BUGS
drwxr-xr-x 31 1054 arch
drwxr-xr-x 38 1292 block
drwxr-xr-x 89 3026 crypto
drwxr-xr-x 112 3808 drivers
drwxr-xr-x 55 1870 firmware
drwxr-xr-x 149 5066 fs
drwxr-xr-x 26 884 include
drwxr-xr-x 14 476 init
drwxr-xr-x 17 578 ipc
drwxr-xr-x 133 4522 kernel
drwxr-xr-x 150 5100 lib
drwxr-xr-x 79 2686 mm
drwxr-xr-x 62 2108 net
drwxr-xr-x 14 476 samples
drwxr-xr-x 91 3094 scripts
drwxr-xr-x 18 612 security
drwxr-xr-x 28 952 sound
drwxr-xr-x 14 476 tools
-rw-r--r-- 1 37204 tuxera_update.sh
drwxr-xr-x 9 306 usr
drwxr-xr-x 3 102 virt
and its readme file said
1. Android build
- Download original android source code ( L 5.0 ) from source.android.com
- Untar opensource packages of LGD859_L_V20a_Android.tar.gz into downloaded android source directory
a) cat LGD859_L_V20a_Android.tar.gza* | tar zxvpf -
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) lunch 1
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain) into the android directory.
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Uncompress using following command at the android directory
tar xvzf LGD859_L_V20a_Kernel.tar.gz
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain) into the android directory.
- Run following scripts to build kernel
a) cd kernel
1) D859
b) make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi- g3-ctc_cn-perf_defconfig zImage -j4
* "-j4" : The number, 4, is the number of multiple jobs to be invoked simultaneously.
- After build, you can find the build image(zImage) at arch/arm/boot
3. how to build chromium34_lge (vendor\lge\external\chromium34_lge\src),
please refer to README.txt at the folder mentioned above.
I built AOSP 9.0.0_r2, targeting aosp_marlin-user to try and make a custom ROM for my phone. When I flashed it and booted into Android my cell service was not working, so I figured it must be some sort of mis-configuration or missing files.
I did download and run the extract scripts and I flashed with `fastboot flashall`.
The files in the root of my build directory:
Code:
$ ls -la
total 219148
drwxr-xr-x 30 gudenau gudenau 4096 Aug 28 16:18 .
drwxr-xr-x 6 gudenau gudenau 4096 Aug 27 21:11 ..
lrwxrwxrwx 1 gudenau gudenau 19 Aug 27 13:29 Android.bp -> build/soong/root.bp
drwxr-xr-x 30 gudenau gudenau 4096 Aug 27 13:29 art
drwxr-xr-x 13 gudenau gudenau 4096 Aug 27 13:29 bionic
drwxr-xr-x 3 gudenau gudenau 4096 Aug 27 13:29 bootable
lrwxrwxrwx 1 gudenau gudenau 26 Aug 27 13:29 bootstrap.bash -> build/soong/bootstrap.bash
drwxr-xr-x 6 gudenau gudenau 4096 Aug 27 13:29 build
drwxr-xr-x 3 gudenau gudenau 4096 Aug 27 13:29 compatibility
drwxr-xr-x 12 gudenau gudenau 4096 Aug 27 13:29 cts
drwxr-xr-x 10 gudenau gudenau 4096 Aug 27 13:29 dalvik
drwxr-xr-x 5 gudenau gudenau 4096 Aug 27 13:29 developers
drwxr-xr-x 20 gudenau gudenau 4096 Aug 27 13:29 development
drwxr-xr-x 7 gudenau gudenau 4096 Aug 27 13:29 device
drwxr-xr-x 289 gudenau gudenau 12288 Aug 27 13:32 external
-rwxr-xr-x 1 gudenau gudenau 109763273 Jul 25 13:15 extract-google_devices-marlin.sh
-rwxr-xr-x 1 gudenau gudenau 8633919 Jul 25 13:15 extract-qcom-marlin.sh
drwxr-xr-x 17 gudenau gudenau 4096 Aug 27 13:33 frameworks
drwxr-xr-x 14 gudenau gudenau 4096 Aug 27 13:33 hardware
drwxr-xr-x 4 gudenau gudenau 4096 Aug 27 13:33 kernel
drwxr-xr-x 20 gudenau gudenau 4096 Aug 27 13:33 libcore
drwxr-xr-x 8 gudenau gudenau 4096 Aug 27 13:33 libnativehelper
-r--r--r-- 1 gudenau gudenau 92 Aug 27 13:29 Makefile
drwxr-xr-x 9 gudenau gudenau 4096 Aug 28 15:41 out
drwxr-xr-x 9 gudenau gudenau 4096 Aug 27 13:33 packages
-rw-r--r-- 1 gudenau gudenau 31047680 Aug 28 16:05 patched_boot.img
drwxr-xr-x 6 gudenau gudenau 4096 Aug 27 13:33 pdk
drwxr-xr-x 9 gudenau gudenau 4096 Aug 27 13:33 platform_testing
drwxr-xr-x 27 gudenau gudenau 4096 Aug 27 13:38 prebuilts
drwxr-xr-x 7 gudenau gudenau 4096 Aug 27 21:58 .repo
drwxr-xr-x 25 gudenau gudenau 4096 Aug 27 13:39 sdk
drwxr-xr-x 29 gudenau gudenau 4096 Aug 27 13:39 system
drwxr-xr-x 7 gudenau gudenau 4096 Aug 27 13:39 test
drwxr-xr-x 5 gudenau gudenau 4096 Aug 27 13:40 toolchain
drwxr-xr-x 13 gudenau gudenau 4096 Aug 27 13:40 tools
drwxr-xr-x 4 gudenau gudenau 4096 Jul 25 13:15 vendor
Did I miss something stupid, or can I just not use the modem with AOSP?
(I do plan on making releases at some point if I get it working and get the things I want in)
gudenau said:
I built AOSP 9.0.0_r2, targeting aosp_marlin-user to try and make a custom ROM for my phone........
Click to expand...
Click to collapse
I don't have this device but, you should be able to obtain some member guidance within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3489005
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Ibuprophen said:
I don't have this device but, you should be able to obtain some member guidance within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3489005
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Click to expand...
Click to collapse
Woops, could you move this? That is my bad.
gudenau said:
Woops, could you move this? That is my bad.
Click to expand...
Click to collapse
I'm not able to move threads but, a Moderator would be more than happy to move it for you.
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Does nobody have any idea about this issue?
Why did you build from the r2 revision? If you look at the factory images, you can see build PPR1.180610.010 is for Telus, and PPR1.180610.009 is for other carriers. When you compare this to the Android release tag list, you will see the correct revision (if not targeting Telus) is the android-9.0.0_r1.
In addition, did you include proprietary vendor files (typically in vendor/google_devices/marlin) in your build? You can pull these from a factory image, or just clone from another developers repos (for example from BenzoRom repo).
jisoo said:
Why did you build from the r2 revision? If you look at the factory images, you can see build PPR1.180610.010 is for Telus, and PPR1.180610.009 is for other carriers. When you compare this to the Android release tag list, you will see the correct revision (if not targeting Telus) is the android-9.0.0_r1.
In addition, did you include proprietary vendor files (typically in vendor/google_devices/marlin) in your build? You can pull these from a factory image, or just clone from another developers repos (for example from BenzoRom repo).
Click to expand...
Click to collapse
I used that one because it was the latest that said "Pixel XL". I did use the vendor scripts they had the Google and QCom blobs.
I'll have to try r1.
I tried r1 and I still have no cell modem access.
gudenau said:
I tried r1 and I still have no cell modem access.
Click to expand...
Click to collapse
Ok, what about the blobs then? How are you extracting these, there may be bits missing.
Also could be a selimux issue. One thing I like to do is turn selinux permissive until I've got the main bugs cleared up and phone in a usable state.
jisoo said:
Ok, what about the blobs then? How are you extracting these, there may be bits missing.
Also could be a selimux issue. One thing I like to do is turn selinux permissive until I've got the main bugs cleared up and phone in a usable state.
Click to expand...
Click to collapse
These Google ones and these Qualcomm ones from Google Developers.
gudenau said:
These Google ones and these Qualcomm ones from Google Developers.
Click to expand...
Click to collapse
Google lies. Those blobs don't have everything you need.
You really need to use blobs which have been extracted from the actual factory images.
I suggest either the ones Lineage or BemzoRom uses.
Just make sure you use the correct branch.
jisoo said:
Google lies. Those blobs don't have everything you need.
You really need to use blobs which have been extracted from the actual factory images.
I suggest either the ones Lineage or BemzoRom uses.
Just make sure you use the correct branch.
Click to expand...
Click to collapse
That's ridiculous, how could I use the ones that come from the factory images? I'd prefer to use those over some on GitHub with some instructions on how to set it up when I eventually do more with this.
gudenau said:
That's ridiculous, how could I use the ones that come from the factory images? I'd prefer to use those over some on GitHub with some instructions on how to set it up when I eventually do more with this.
Click to expand...
Click to collapse
He's right, the ones from google doesn't have everything you need (ridiculous ) The repos he linked are extracted from the factory image.
These are the blobs that are missing that cause no ril (thank you @xanaxdroid for pointing this out to me)
I would use benzo's if I were you, since aosp requires a patch if you don't include the entire vendor
shagbag913 said:
He's right, the ones from google doesn't have everything you need (ridiculous ) The repos he linked are extracted from the factory image.
These are the blobs that are missing that cause no ril (thank you @xanaxdroid for pointing this out to me)
I would use benzo's if I were you, since aosp requires a patch if you don't include the entire vendor
Click to expand...
Click to collapse
Where would I put these?
gudenau said:
Where would I put these?
Click to expand...
Click to collapse
vendor/google_devices/marlin is the path where the device tree looks for the relevant makefile, so make sure you have the same directory structure.
jisoo said:
vendor/google_devices/marlin is the path where the device tree looks for the relevant makefile, so make sure you have the same directory structure.
Click to expand...
Click to collapse
Code:
[936/936] including vendor/google_devices/sailfish/Android.mk ...
build/make/core/tasks/vendor_module_check.mk:82: error: Error: Product "aosp_marlin" cannot have overlay in vendor tree: vendor/google_devices/marlin/overlay.
Any idea how to fix this?
gudenau said:
Code:
[936/936] including vendor/google_devices/sailfish/Android.mk ...
build/make/core/tasks/vendor_module_check.mk:82: error: Error: Product "aosp_marlin" cannot have overlay in vendor tree: vendor/google_devices/marlin/overlay.
Any idea how to fix this?
Click to expand...
Click to collapse
It was one of the below 3 commits for android_build which fixes that error, but I am honestly not smart enough to know which one...
add support for overriding build.prop settings
Add support for PRODUCT_COPY_FILES_OVERRIDES
Allow prebuild APK's in Vendor
I'm not a real dev, so you want to review the commits and determine yourself.
jisoo said:
It was one of the below 3 commits for android_build which fixes that error, but I am honestly not smart enough to know which one...
add support for overriding build.prop settings
Add support for PRODUCT_COPY_FILES_OVERRIDES
Allow prebuild APK's in Vendor
I'm not a real dev, so you want to review the commits and determine yourself.
Click to expand...
Click to collapse
I applied all of them and they don't seem to have done anything. :-/
gudenau said:
I applied all of them and they don't seem to have done anything. :-/
Click to expand...
Click to collapse
I think you need to comment this out, but I can't remember if that's the one it checks for overlays..
shagbag913 said:
I think you need to comment this out, but I can't remember if that's the one it checks for overlays..
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well, that is an interesting thing to have happen.
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.