Database Users

[Q] how to flash from AOSP builded images?

Hello!
Im currently trying to build a vannila froyo 2.2 rom from the source! How do i flash the images when im ready? Is there something like fastboot on the g1 or htc magic?
Landroid

I haven't had the time to try to build myself, but wouldn't you be better off starting with the Samsung open source for your carrier/model rather than trying to figure out all the changes you'd need to make to get AOSP to run on the Tab?

BuglessFan said:
I haven't had the time to try to build myself, but wouldn't you be better off starting with the Samsung open source for your carrier/model rather than trying to figure out all the changes you'd need to make to get AOSP to run on the Tab?
Click to expand...
Click to collapse
Erhh - Samsung open source only contains the kernel. You need the rest of Android, which is what the AOSP is for!
Regards,
Dave

Don't know about the others, but the one for the SCH-I800 on VZW is not just the kernel. All of the things like the custom notification bar/settings for white and black levels, et cetera, go well beyond vanilla android in the Tab. I haven't gone through the platform.tar, but it has notices about stuff for, TouchWiz, et cetera (now whether it can actually run as built directly from what they've made available all bets are off, I know a direct compile of the kernel code didn't work for me, but I haven't had time to do more than a simple straight attempt to build and may have screwed something simple up). It's around 85MB for the DJ11 code for Verizon.
Edit: I'd understand if you needed most of it from AOSP though for a full build, and stand corrected.

And how do i flash the created system.img and data.img? The kernel will be in the zImage format as im going to build the kernel from samsung's opensource files!

Landroid said:
And how do i flash the created system.img and data.img? The kernel will be in the zImage format as im going to build the kernel from samsung's opensource files!
Click to expand...
Click to collapse
You don't. Samsung uses different partition layout and formats.
Use the Samsung tar files to overlay over AOSP as described in their readme file.

Ah ok! Thank you

from Readme file:
How to build:
< Kernel >
1. Unzip SPH-P100_Kernel.tar.
( You can find SPH-P100_Kernel.tar in the same directory with this README.txt . )
2. Refer another "README.txt" in the tar file to build the kernel source code.
< Platform >
* NOTICE *
Galaxy Tab is launched in many countries, including Europe and North Amarica.
S/W is almost the same but there are some differences between the European version(GT-P1000) and the US Sprint version(SPH-P100).
The open source codes to be open here are only the differences.
1. Get Android open source code:
: version info - Android froyo 2.2 (android-cts-2.2_r2)
( Download site : http://source.android.com )
2. Get GT-P1000 open source code
: GT-P1000_OpenSource.zip
( Download site : http://opensource.samsung.com )
Unzip it, then you will see the file GT-P1000_Platform.tar.bz2 which includes the platform source code.
3. Overwrite GT-P1000 Platform OpenSource to the Android open source.
4. Get SPH-P100 open source code:
: SPH-P100_OpenSource.zip
( Download site : http://opensource.samsung.com , version info : DJ14 )
5. Overwrite SPH-P100_Platform_DJ14 OpenSource to the Android + GT-P1000(European) Platform open source code.
6. Overwrite the Platform source code that comes from the Sprint version(SPH-P100_Platform_DJ30).
7. Do "make"
Click to expand...
Click to collapse

Landroid said:
And how do i flash the created system.img and data.img? The kernel will be in the zImage format as im going to build the kernel from samsung's opensource files!
Click to expand...
Click to collapse
If I understand correct. (for the kernel at least) You could just take a package like monks then swap out the zImage and *.ko files for the samsung ones. resign the zip. Then flash it from the clockworkmod recovery.

I believe we need repo init -b android-cts-2.2_r2 ... and overlay the Samsung tar contents on top of it.

[UTILITY][GIT][SCRIPT] Automatize Your Git Workflow

Automatize Your Git Workflow​
General:
Hi XDA,
I created a Windows batch script that helps you to automatize your Git workflow. This batch script includes the most important git commands, new ones will be added with time.
Additionally, I added selfmade git workflows (currently 2) which runs serveral commands in one row. Suggestions for new ones are welcome.
At the moment there's just a Windows version available. Since I don't have any Linux experience, it might be great if someone could port it.
NOTE: Instead of using the Dropbox download link you can always get the files from GitHub. "Master" brench is always the newest one.
Click to expand...
Click to collapse
Functions:
Init repo
Clone Git
Add repo
Get status
Get changes of tracked files
Add file(s) to staging area
Commit file(s)
Change last commit
Get commit log
Get commit log of specified file
Push changes
Pull changes
Fetch changes
Remote info
List remotes
Add remote repo
Discard all local changes
Discard local changes in file
List branches
Switch HEAD branch
Create branch
Delete branch
Push branch
Add tags
Merge branch into HEAD
Rebase HEAD onto branch
Custom made workflows (2)
Click to expand...
Click to collapse
Windows Download:
Download
Click to expand...
Click to collapse
GitAutomating on GitHub:
MyGithub
Click to expand...
Click to collapse
Newest Version:
25.09.2016: v1.1
Click to expand...
Click to collapse
Screenshots in "Screenshots" section available
Please report bugs and give feedback
XDA:DevDB Information
Git Automating, Tool/Utility for all devices (see above for details)
Contributors
Lars124
Version Information
Status: Testing
Created 2016-09-19
Last Updated 2016-09-19

Changelog:
25.09.2016:
- Added "tag" function
- Added "own command" function
- Other minor imporvements
19.09.2016:
- Initial Release
Click to expand...
Click to collapse

Update with new functions comes this week!
Sent from my Moto G 2014 using Tapatalk

UPDATE v1.1 is online
25.09.2016:
- Added "tag" function
- Added "own command" function
- Other minor imporvements

Android Oreo 8.0 / Lineage 15.0 Dev Discussion

Currently on hold due to working on Nougat first.
I've got a booting or should I say bootlooping build of Lineage 15.0 for I9000. (galaxysmtd)
I've had to use crazy hacks like adb binary from 7.1 in ramdisk.
Just to get `adb logcat` working.
For now it's stuck at bootlogo. I've attached the logcat here.
I'm looking into it to figure out what needs to be done.
Sources:
manifests and patches I've used.
https://github.com/galaxys1-resurrected/local_manifests
https://github.com/galaxys1-resurrected/android_patches
Kernel:
https://github.com/galaxys1-resurrected/android_kernel_samsung_aries
Device Tree:
https://github.com/galaxys1-resurrected/android_device_samsung_aries-common
https://github.com/galaxys1-resurrected/android_device_samsung_galaxysmtd
Thanks:
@rINanDO for backporting kernel side of things to 3.0
@xc-racer99 and @Coldwindofnowhere for getting the device upto android 7.1
And all others who had worked from beginning till now on this device.

Is there anyone still working on this?
I was curious if anyone this was still being developed? I'm totally newbie in the android scene but have some knowledge of operating systems and am interested in resurrecting my i9000.
I went through the logs and a couple of things jumped out:
1) Surface flinger returning non zero exit status because it needs OpenGL ES v2.0 or greater. I believe i9000's GPU PowerVR SGX540 supports OpenGL ES 2.0, so this issue could be solved.
2) Media extractor crash: /system/bin/mediaextractor: libminijail[1291]: prctl(PR_SET_NO_NEW_PRIVS): Invalid argument, whatever the heck it means.
3) activity_recognition HAL is deprecated, so ActivityRecognitionHardware class's init does not do anything.
For 3 , I got to android_hardware_location_ActivityRecognitionHardware.cpp's source where it comments out activity_recognition.h with the following comment:
Code:
// #include <hardware/activity_recognition.h>
// The activity recognition HAL is being deprecated. This means -
// i) Android framework code shall not depend on activity recognition
// being provided through the activity_recognition.h interface.
// ii) activity recognition HAL will not be binderized as the other HALs.
I believe more work has been done since this post based on git commits lasting upto Nov'17. Would be great if someone could post logs for an updated build. I feel that android oreo with go optimizations would be a really good fit for i9000 and uphold this device's legendary support. I mean a device running from eclair all the way to oreo would be amazing.
Even if this might not work out, I would like to thank @(°_o), @xc-racer99 , @Coldwindofnowhere and @rINanDO for bringing i9000 upto nougat. I believe even i9000's nexus sibling nexus s does not have a working nougat rom.

a1shakes said:
I was curious if anyone this was still being developed? I'm totally newbie in the android scene but have some knowledge of operating systems and am interested in resurrecting my i9000.
I went through the logs and a couple of things jumped out:
1) Surface flinger returning non zero exit status because it needs OpenGL ES v2.0 or greater. I believe i9000's GPU PowerVR SGX540 supports OpenGL ES 2.0, so this issue could be solved.
2) Media extractor crash: /system/bin/mediaextractor: libminijail[1291]: prctl(PR_SET_NO_NEW_PRIVS): Invalid argument, whatever the heck it means.
3) activity_recognition HAL is deprecated, so ActivityRecognitionHardware class's init does not do anything.
For 3 , I got to android_hardware_location_ActivityRecognitionHardware.cpp's source where it comments out activity_recognition.h with the following comment:
Code:
// #include <hardware/activity_recognition.h>
// The activity recognition HAL is being deprecated. This means -
// i) Android framework code shall not depend on activity recognition
// being provided through the activity_recognition.h interface.
// ii) activity recognition HAL will not be binderized as the other HALs.
I believe more work has been done since this post based on git commits lasting upto Nov'17. Would be great if someone could post logs for an updated build. I feel that android oreo with go optimizations would be a really good fit for i9000 and uphold this device's legendary support. I mean a device running from eclair all the way to oreo would be amazing.
Even if this might not work out, I would like to thank @(°_o), @xc-racer99 , @Coldwindofnowhere and @rINanDO for bringing i9000 upto nougat. I believe even i9000's nexus sibling nexus s does not have a working nougat rom.
Click to expand...
Click to collapse
Unfortunately, no one is really actively working on Oreo. As you've found out, it's an issue with the graphics drivers that is holding everything back. No device (that I've found) that uses a PowerVR graphics chip (we use the PowerVR SGX 540) has working graphics drivers on Oreo. There were rumours that someone had found newer working blobs, but weren't able to release them publicly due to intellectual property laws that they were trying to figure out (but this was months ago).
Our GPU does support sufficient enough OpenGL, but only using BGRA8888 as opposed to RGBA8888. BGRA hasn't officially been supported in Android since ~4.2, but there's been a hack used to make things work. Come Oreo, things have changed and the hack no longer applies cleanly. However, I think the really issue is that the gralloc blobs was extended by PowerVR (see https://github.com/xc-racer99/andro...6.0/exynos3/s5pc110/include/hal_public.h#L119) but with the binderized HALs/VNDK/other low-level Oreo changes something has broken. I had a go at trying to work around things, but failed too.
There are a few ways I can think of getting working graphics:
1) Someone finds some updated blobs for the PowerVR SGX 540 for ARM (I've found x86 ones, but they don't work for obvious reasons)
2) Someone hacks around the source code so that the blobs work - but I'm not sure if it's PowerVR "extension" of the gralloc interface that is causing issues or not...
3) We simply use software rendering, but this would be so slow with our ancient CPU that I haven't bothered to try
4) We work on porting a newer kernel so we have the Samsung DRM kernel driver, use the Linux PowerVR blobs coupled with drm_gralloc/drm_hwcomposer and maybe a wrapper like https://github.com/TexasInstruments/dri3wsegl and somehow cobble together working support
In terms of the mediaextractor crash, that's due to the kernel missing seccomp support. There's a whole bunch of different backports, some more successful than others. Due to our ancient kernel, backporting is no longer very easy...
If we could somehow get the graphics drivers working, we'd have a pretty good base as there are free implementations of all HALs/drivers except for GPS and TV-Out (and, of course, graphics....).

Are you really working on porting oreo on the i9000?
How do you deal with the small amount of ram?
Are you using the 'low end device' oreo feature?

nailyk said:
Are you really working on porting oreo on the i9000?
How do you deal with the small amount of ram?
Are you using the 'low end device' oreo feature?
Click to expand...
Click to collapse
No, no one (that I know of) is actively working on Oreo for the first-gen Galaxy S devices. There were attempts, the kernel got in good enough shape that everything wasn't immediately crashing, but due to the graphics driver issues described a couple posts ago nobody has managed to get a fully booting build.

xc-racer99 said:
No, no one (that I know of) is actively working on Oreo for the first-gen Galaxy S devices. There were attempts, the kernel got in good enough shape that everything wasn't immediately crashing, but due to the graphics driver issues described a couple posts ago nobody has managed to get a fully booting build.
Click to expand...
Click to collapse
Thanks for fast anwser. Yes, the graphic driver problem exist on another of my exynos device.
Anyway I wasn't able to boot the 7.1 (not able to boot something else than 2.3.6 )
Will attempt to see that post you are talking about but am probably not smart enough to deal with graphics drivers
Thanks for your time.

nailyk said:
Thanks for fast anwser. Yes, the graphic driver problem exist on another of my exynos device.
Anyway I wasn't able to boot the 7.1 (not able to boot something else than 2.3.6 )
Will attempt to see that post you are talking about but am probably not smart enough to deal with graphics drivers
Thanks for your time.
Click to expand...
Click to collapse
If you're serious about trying to mess with graphics drivers, it might be interesting to check out the blobs from https://www.renesas.com/pt-br/produ...ion-boards/renesas-starter-kit-for-rzg1e.html as it's an ARM-based device with the SGX540. It's possible that they're new enough to not run into the same issues as the older blobs (but equally possible that even the kernel part is closed source). The binary blobs are only semi-SoC specific as I've managed to use the OMAP blobs with only having hardware decoding being broken.

Is it for real???
I9000 !!

Apparently, some new SGX540 and SGX544 DDK blobs for OMAP4 have appeared:
https://gerrit.unlegacy-android.org/#/c/Unlegacy-Android/proprietary_vendor_ti/+/10525/
https://gerrit.unlegacy-android.org/#/q/topic:omap-ddk-1.14+(status:open+OR+status:merged
In fact, (Barnes and Noble's) hummingburd and ovation are both based on SGX544 and have gotten an Oreo ROM (using the new blobs).
https://forum.xda-developers.com/showpost.php?p=77526206&postcount=2490

Use android go it will be better.

MYEUHD said:
Apparently, some new SGX540 and SGX544 DDK blobs for OMAP4 have appeared:
https://gerrit.unlegacy-android.org/#/c/Unlegacy-Android/proprietary_vendor_ti/+/10525/
https://gerrit.unlegacy-android.org/#/q/topic:omap-ddk-1.14+(status:open+OR+status:merged
In fact, (Barnes and Noble's) hummingburd and ovation are both based on SGX544 and have gotten an Oreo ROM (using the new blobs).
https://forum.xda-developers.com/showpost.php?p=77526206&postcount=2490
Click to expand...
Click to collapse
Yep, I've seen the blobs, they've been there for awhile now. Just haven't had a chance to run a build with the blobs to see if they work. It's on my to-do list when I find the time

xc-racer99 said:
Yep, I've seen the blobs, they've been there for awhile now. Just haven't had a chance to run a build with the blobs to see if they work. It's on my to-do list when I find the time
Click to expand...
Click to collapse
Alright, I've had a chance to look at the blobs now. I have a build, but unfortunately it looks as if we need to adjust our hwcomposer as well We use a relatively old hwc 1.0 but the new gralloc blob doesn't appear to keep the framebuffer open which is a requirement for a hwcomposer this old. There is a prebuilt blob that is used by omap4 devices but it doesn't work on s5pc110 due to the fact that it uses some DSS stuff which is OMAP-specific. Still plenty of work to do, without even trying to figure out all the Oreo/Pie changes (I'm testing on KitKat as that's the build environment I have setup right now).

xc-racer99 said:
Alright, I've had a chance to look at the blobs now. I have a build, but unfortunately it looks as if we need to adjust our hwcomposer as well We use a relatively old hwc 1.0 but the new gralloc blob doesn't appear to keep the framebuffer open which is a requirement for a hwcomposer this old. There is a prebuilt blob that is used by omap4 devices but it doesn't work on s5pc110 due to the fact that it uses some DSS stuff which is OMAP-specific. Still plenty of work to do, without even trying to figure out all the Oreo/Pie changes (I'm testing on KitKat as that's the build environment I have setup right now).
Click to expand...
Click to collapse
We need a newer hwc anyway, as Pie requires at least hwc 1.3:
ChronoMonochrome said:
In 9.0, to get graphics to work, device is required to support HWC2 (or use either HWC2on1 or HWC2onFb adapters).
Click to expand...
Click to collapse
ChronoMonochrome said:
Yes, HWC has to be at least 1.3, to work with one of aforementioned adapters. With one of those adapters it will work like it was HWC 2 (but actually not exactly same).
Click to expand...
Click to collapse
As a reference, the galaxy S3's hwc was updated from 1.0 to 1.4: Thread
hardware/samsung

MYEUHD said:
We need a newer hwc anyway, as Pie requires at least hwc 1.3:
As a reference, the galaxy S3's hwc was updated from 1.0 to 1.4: Thread
hardware/samsung
Click to expand...
Click to collapse
Was unaware of the fact. Are you volunteering to make the patches?
I've uploaded my changes to https://github.com/xc-racer99/proprietary_vendor_samsung/tree/ddk-1.14 https://github.com/xc-racer99/android_hardware_samsung/tree/ddk-1.14 https://github.com/xc-racer99/android_kernel_samsung_aries/tree/ddk-1.14 https://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd/tree/ddk-1.14 https://github.com/xc-racer99/android_device_samsung_aries-common/tree/ddk-1.14 but I think this might be the last I work on this as I don't really have the motivation to work on it anymore. Note the patches are against a custom version of Unlegacy Android 4.4 so you'll need to cherry pick the changes to your ROM of choice if desired.
The changes build, the EGL appears to initialize, but I always get
Code:
E/libEGL ( 471): validate_display:254 error 3008 (EGL_BAD_DISPLAY)
And in dmesg:
Code:
[ 8.509291] init: computing context for service '/system/vendor/bin/pvrsrvinit'
[ 8.509601] init: starting 'pvrsrvinit'
...
[ 8.601890] PVR_K: UM DDK-(4081762) and KM DDK-(4081762) match. [ OK ]
...
[ 8.765955] init: process 'pvrsrvinit', pid 99 exited
...
[ 55.560021] PVR_K:(Error): PVRSyncIOCTLCreate: Failed to find unused fd (-24)
[ 55.563491] PVR_K:(Error): PVRSyncIOCTLCreate: Failed to find unused fd (-24)
[ 55.597577] s3cfb s3cfb: [fb0] video memory released
Whether the issue is in the HWC or the gralloc blob that we've stolen from OMAP, I have no idea.

xc-racer99 said:
Was unaware of the fact. Are you volunteering to make the patches?
Click to expand...
Click to collapse
Will try to do my best!
BTW, do I really need jdk-7 to compile kitkat? or does it simply work with jdk-8??

MYEUHD said:
Will try to do my best!
BTW, do I really need jdk-7 to compile kitkat? or does it simply work with jdk-8??
Click to expand...
Click to collapse
You really do need jdk-7... I used the "reference implementation" available at http://jdk.java.net/java-se-ri/7 and made sure the java executables were in the PATH before the java I actually have installed.
Note that my Unlegacy Android trees will not work for the i9000 (well, they might, but you'd need to install u-boot as well at a bare minimum...)

It's kinda Insane that people are trying to get an 8 year phone to run oreo

@xc-racer99 Do you still have the AOSP 7.1 source code on your computer?

MYEUHD said:
@xc-racer99 Do you still have the AOSP 7.1 source code on your computer?
Click to expand...
Click to collapse
I've got the .repo folder, but don't have the individual files expanded as I don't have the disk space Could run a repo sync and look at things but don't have the disk space for a full build.

The_Pacific_gamer said:
It's kinda Insane that people are trying to get an 8 year phone to run oreo
Click to expand...
Click to collapse
its kinda insane that people are still using this phone.

[ROM][DEV] Porting Halium to Galaxy S6

In the interest of bringing convergence of linux operating system in phones and desktops after canonical abandoned the project, the halium.org project and ubports took the baton. Halium project's objective is to create a standard way to wrap all the android code necessary for a OS to talk to hardware so one can build a linux operating system on top of android (no java code getting in the way). It could be used by any number of OS's like sailfish, ubuntu touch or new mobile distributions, like archlinux on the phone (yeah, I'm an arch guy). It is based on the hybris library, whitch is kind of a wrap so the glibc can be interface with android libc (called bionic, which is a little bit off standard).
A lot of you know all that (specially the ones likely to help), I just giving some contest in case someone it's not tunned in.
So I'm on the endevour of porting it to galaxy S6 taking advantage of the work of TeamNexus (which is a working in progress), whom work on the device specific code made it possible to undertake this task and LinageOS for the rest of android code (Thank you both!).
So, for anyone who wants to coordinate efforts to make this port, or for anyone who wants to help me troubleshoot some of the problems I'm having, fell free to come aboard. Here are useful links:
Halium.org - Project homepage
porting documentation
TeamNexus git repository
Local Manifests: device code and repo manifest.
Here is a patch on all the modifications I had to do to so the device specific code
fixup-mountpost for the zerofltexx device (It is used to modify the fstab file so systemd can mount it without udev) apperantly there might be a format error on my part here. That is what the devs said, but I can't figure it out. I followed the instructions in the documentation... (I didn't wanted to push it with questions.)
progress so far:
- [x] Manifest with kernel, vendor, device tree
- [x] Setup kernel defconfig for hybris-boot (using mer-kernel scripts and zerofltexx kernel as reference)
- [x] Fix mountpoints
- [p] Build
- - [x] systemimage
- - [x] mkbootimg
- - [ ] hybris-boot
- [ ] Flash and test with reference rootfs
- - [ ] Get LXC working
- - [ ] Get wifi working
- - [ ] Halium tests
-- - [ ] test_vibrate
-- - [ ] test_lights
-- - [ ] test_vibrate
-- - [ ] test_hwcomposer
-- - [ ] test_audio
-- - [ ] test_camera
- - [ ] Clean up and share my manifest and sources and stuff
Testing rootfs:
- [ ] halium 7.1 reference
- [ ] Plasma Mobile (boots! Graphics! Wifi!)
- [ ] UBports rootfs
This first post is going to be updated with any information needed for porting Halium for galaxy s6 from source and its progress.
I will post the problems I had in another post, but I got to get going now. So I will just post the make error I'm getting

Hello Alkis05,
We are 2 young developers and we are interested in porting Ubuntu Touch for a Samsung device (Galaxy Tab A6 2016 10.1” : gtaxllte).
We were very excited to see that you are interested too in this project and, even if you are not porting it for the same device, we would be very happy to get in touch with you for this project.
We saw that you are at a quite advanced step of the project. As for us, we are trying to write the correct manifest in order to build Halium. We have lots of difficulties with this file because I don’t know how to include the correct repositories.
We would be very thankful if you could help us with this step, as we saw that you successfully did it for your device.
Would you be able to help us ?
As for the for the steps of the project, we would be very happy to participate. Would you accept to work with us on this project ?
Of course, we would continue the port on the two devices, yours and ours.
Finally, we would like to present ourselves :
We are two young teenagers : Nyell Xade Jean (15 years old, St Lucia) and Jean-Baptiste Amade (16 years old, France). We are very good friends and we have been working on lots of projects together.
Xade is a specialist of android devices, he has a dedicated YouTube channel about this subject (Pops Productions Tech).
As for me (Jb), I’m very interested in Linux (I’m using Ubuntu every day) and that’s why i decided to port Ubuntu Touch to my tablet.
Concerning the device we are working on, it’s a Samsung Galaxy Tab A6 2016 10.1” (manufacturer code name : gtaxllte). On GitHub I found different repositories related to this device but the difficulty I’m facing is that I can’t fill correctly the Halium manifest.
If you accept to help us, I’ll explain you more precisely my problem.
We hope that you’ll accept to work with us on this project.
Thank you in advance
Xade(@pops) and Jb
---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------
Hello Alkis05,
We are 2 young developers and we are interested in porting Ubuntu Touch for a Samsung device (Galaxy Tab A6 2016 10.1” : gtaxllte).
We were very excited to see that you are interested too in this project and, even if you are not porting it for the same device, we would be very happy to get in touch with you for this project.
We saw that you are at a quite advanced step of the project. As for us, we are trying to write the correct manifest in order to build Halium. We have lots of difficulties with this file because I don’t know how to include the correct repositories.
We would be very thankful if you could help us with this step, as we saw that you successfully did it for your device.
Would you be able to help us ?
As for the for the steps of the project, we would be very happy to participate. Would you accept to work with us on this project ?
Of course, we would continue the port on the two devices, yours and ours.
Finally, we would like to present ourselves :
We are two young teenagers : Nyell Xade Jean (15 years old, St Lucia) and Jean-Baptiste Amade (16 years old, France). We are very good friends and we have been working on lots of projects together.
Xade is a specialist of android devices, he has a dedicated YouTube channel about this subject (Pops Productions Tech).
As for me (Jb), I’m very interested in Linux (I’m using Ubuntu every day) and that’s why i decided to port Ubuntu Touch to my tablet.
Concerning the device we are working on, it’s a Samsung Galaxy Tab A6 2016 10.1” (manufacturer code name : gtaxllte). On GitHub I found different repositories related to this device but the difficulty I’m facing is that I can’t fill correctly the Halium manifest.
If you accept to help us, I’ll explain you more precisely my problem.
We hope that you’ll accept to work with us on this project.
Thank you in advance
Xade(@pops) and Jb

fixup-mountpoints file
Looks like your fixup-mountpoints entry need to be adjusted a little bit. It needs to be like this (like the entries already in that file):
Code:
"zerofltexx")
sed -i \
-e 's block/platform/15570000.ufs/by-name/SYSTEM sda15 ' \
-e 's block/platform/15570000.ufs/by-name/EFS sda3 ' \
-e 's block/platform/15570000.ufs/by-name/CACHE sda16 ' \
-e 's block/platform/15570000.ufs/by-name/USERDATA sda18 ' \
-e 's block/platform/15570000.ufs/by-name/PERSISTENT sda11 ' \
-e 's block/platform/15570000.ufs/by-name/HIDDEN sda17 ' \
"[email protected]"
;;

any update? I want to give it a try

Device Tree, Kernel, Vendor for TB-8504f?

Looking for the Device Tree, Kernel, and Vendor for this tablet.
I am just learning. Is there a process for getting these from an existing tablet?
Thank you!
Darran

I found the device tree for the a similar tablet here:
https://github.com/Matshias/twrp_android_device_tb_8504x

Someone on reddit told me this:
If you can find something with similar specs and the same processor you can try adapting it to your device. The Samsung Note 4 and the S5 use the same sources with some minor adjustments. I've had good luck getting some kernel sources from Samsung just by contacting them and asking, but they're the only brand I have any experience with.
For vendor files you can try TheMuppets found here: https://github.com/TheMuppets
Or you can try to extract them yourself using this guide- https://wiki.lineageos.org/extracting_blobs_from_zips.html
Best of luck to you.
Click to expand...
Click to collapse
Is this sound advice?

drizzle123 said:
Someone on reddit told me this:
Is this sound advice?
Click to expand...
Click to collapse
Device tree and vendor are not the problem. Kernel source code is the thing that is required. Was going to buy tab4 10 but won't if lenovo is not willing to release the kernel source. I've repeatedly asked them to do so in the forums but they never reply. Maybe try mailing lenovo support and see if that helps...

thank you - do you know if they have a dev support e-mail or is it the standard support e-mail?

Your kernel sources are already available. Its included in the kernel of Tab 4 8 Plus.

yener90 said:
Your kernel sources are already available. Its included in the kernel of Tab 4 8 Plus.
Click to expand...
Click to collapse
Is a seperate defconfig specifically for tab4 8 available ?

skoar said:
Is a seperate defconfig specifically for tab4 8 available ?
Click to expand...
Click to collapse
Yes.

yener90 said:
Yes.
Click to expand...
Click to collapse
Nice. I never downloaded the source to check. Then doing a bringup should be easy

Where is the source that you all reference?
Probably part of this? https://forum.xda-developers.com/th...m-lineageos-16-0-lenovo-tab-3-8-plus-t3923143

drizzle123 said:
Where is the source that you all reference?
Probably part of this? https://forum.xda-developers.com/th...m-lineageos-16-0-lenovo-tab-3-8-plus-t3923143
Click to expand...
Click to collapse
Some things will match others need to be modified as per the non plus model. Vendor files can be extracted from the device and the device tree can be set up by referencing the plus model since they are not too different. As per the kernel try prebuilt first and see if it boots

drizzle123 said:
Where is the source that you all reference?
Probably part of this? https://forum.xda-developers.com/th...m-lineageos-16-0-lenovo-tab-3-8-plus-t3923143
Click to expand...
Click to collapse
Bad choice. You need a device tree from a device with Snapdragon 425 (MSM8917)

yener90 said:
Bad choice. You need a device tree from a device with Snapdragon 425 (MSM8917)
Click to expand...
Click to collapse
This device tree looks to have a Snapdragon 425 (MSM8917)

drizzle123 said:
This device tree looks to have a Snapdragon 425 (MSM8917)
Click to expand...
Click to collapse
Tab4 8 plus has snapdragon 625. Go to gsmarena and search by snapdragon 425 and you'll get a few devices then go from there and see if they have a custom rom. If they do then find the device tree for that device from github and modify it as required. For vendor extract it from the device. There are quite a few tutorials on xda. As for kernel download the one provided by lenovo for tab4 8 plus (it'll work for non plus model as well). As for defconfig extract it from boot.img again there are tutorials available.
I'll probably try to get los running on the tab4 10 later

I found the kernel and some associated files here:
https://pcsupport.lenovo.com/us/en/...ntent=20190613_20190613184825&linkId=68972849
I found a similar an MSM8917 Device Tree here:
https://github.com/redmidevs/android_device_xiaomi_rolex
I looked through muppets and didn't find any vendor files for the TB-850 or any TB devices. Will work on extracting the vendor files and getting them up on muppets. Can I use the extract-files.sh file from lineage to extract the vendor files for the TB-850?
https://github.com/TheMuppets/proprietary_vendor_lge

drizzle123 said:
I found a similar an MSM8917 Device Tree here:
https://github.com/redmidevs/android_device_xiaomi_rolex
I looked through muppets and didn't find any vendor files for the TB-850 or any TB devices. Will work on extracting the vendor files and getting them up on muppets. Can I use the extract-files.sh file from lineage to extract the vendor files for the TB-850?
https://github.com/TheMuppets/proprietary_vendor_lge
Click to expand...
Click to collapse
A good choice. Vendor files should be from the same device like device tree.
Use this one:
https://github.com/redmidevs/android_vendor_xiaomi_rolex/tree/lineage-15.1
You need just the camera blobs blobs from your device. But you can do this later.
More important are the firmware files because those are unique for every device.
Replace thos files with the one on your device:
https://github.com/redmidevs/androi...tree/lineage-15.1/proprietary/vendor/firmware
I suggest you to build Lineage15.1 first. The kernel works with Android 8.1.

Thank you for the guidance - looking to give this a try today

@highwaystar_ru @yener90 @codeworkx
I know this is not the place to ask but I haven't gotten any response from the places I was supposed to ask so bear with me
I'm building los 16 for lenovo tab4 10
I've setup the the device tree and vendor and am using prebuilt kernel but while building it stops at 69% with the following error
[ 69% 65628/93948] //vendor/lineage/build/soong:generated_kernel_includes generate
FAILED: /home/skoar/android/lineageos/out/soong/.intermediates/vendor/lineage/build/soong/generated_kernel_includes/gen/.dummy_dep
/home/skoar/android/lineageos/out/soong/host/linux-x86/bin/sbox --sandbox-path /home/skoar/android/lineageos/out/soong/.temp --output-root /home/skoar/android/lineageos/out/soong/.intermediates/vendor/lineage/build/soong/generated_kernel_includes/gen --copy-all-output -c 'make -j CFLAGS_MODULE="-fno-pic" -C O=__SBOX_OUT_DIR__ ARCH=arm64 CROSS_COMPILE="/usr/bin/ccache aarch64-linux-androidkernel-" CROSS_COMPILE_ARM32="arm-linux-androideabi-" headers_install' && touch /home/skoar/android/lineageos/out/soong/.intermediates/vendor/lineage/build/soong/generated_kernel_includes/gen/.dummy_dep
make: *** O=/home/skoar/android/lineageos/out/soong/.temp/sbox985711399: No such file or directory. Stop.
sbox command (make -j CFLAGS_MODULE="-fno-pic" -C O=/home/skoar/android/lineageos/out/soong/.temp/sbox985711399 ARCH=arm64 CROSS_COMPILE="/usr/bin/ccache aarch64-linux-androidkernel-" CROSS_COMPILE_ARM32="arm-linux-androideabi-" headers_install) failed with err "exit status 2"
[ 69% 65635/93948] //frameworks/base:gen-platform-proto-constants generate
ninja: build stopped: subcommand failed.
11:35:26 ninja failed with: exit status 1
Soooo any ideas ???

Here are the repositories I am setting up
https://github.com/darran-kelinske-fivestars/android_device_lenovo_tb8504f
https://github.com/darran-kelinske-fivestars/android_vendor_lenovo_tb8504f
https://github.com/darran-kelinske-fivestars/android_kernel_lenovo_tb8504f

tb8504 kernel looks like can be built with this config https://github.com/HighwayStar/andr...rm64/configs/msm8937_p3588_pcb-perf_defconfig Changes after splitting can be intergrated in 8953 kernel from lenovo-devs org.
vendor blobs and common device tree can be used from here https://github.com/lenovo-devs only some hals has to be renamed or replaced with ones name msm8937 instead of msm8953