Database Users

[ROM]Find 5] "Metallium OS" Unofficial builds

Hello Guys,
These are my Unofficial builds of MetalliumOS for Find5​
Spike Laboratory - Metallium​
ABOUT Spike Laboratory - Metallium
Spike Laboratory - Metallium >>SPLM is an after market firmware based latest "Android Lolly-Pop 5.X.X. This firmware is designed By Spike Laboratory .This firmware suits specially for those people who like,Multitasking performance,optimum speed. In-addition to This the firmware has Inbuilt options and settings to make customization of your Device the way you like.
Features , changelogs and screenshots can be found on Spike Laboratory - WEB
SUPPORT FOR SPLM RELATED ISSUES :
We spend an astonishing amount of time developing this firmware.
We can't spend much time on XDA as a result, so if you need support, please try the following:
Ask a question in your device forum in XDA. Someone will no doubt try to help you.
Our device maintainers are going to help you so pm them.
Any bugs or any other issues report to the device maintainers.
If you want to contribute or join to the device maintainer team contact either team leaders or device maintainers.
We expect that users help each other, well xda is a ll about it.
OFFICIAL LINKS & INFORMATIONS :
Official Web-Page
SPLM ROMS
Recommanded gapps
DOWNLOADS
(Please do not mirror Download links or Mention Link in any of your posts )
INSTALLATION STEPS:
Minimum Requirements To Install SPLM:
Your Device Should be Rooted with Unlocked Boot-loader & Latest Custom recovery Installed.
Recommended Custom Recovery TWRP : Click Here to View TWRP Offical supported devices
Installation Procedure:
(A)If you are making a Fresh Installation(or coming from any other rom other than SPLM) :
Boot Into Recovery Mode
Wipe Data,System,Cache,Dalvik
Flash provide latest SPLM ROM Zip
Again Wipe Cache and Dalvik
Reboot To System
Now again Reboot into Recovery Mode
Flash latest G-Apps
Wipe Cache and Dalvik....and Reboot To System.
Have always this zip in your sd in case od sim unlock issue Find5 is exeperiencing since Lollipop, just flash it in recovery if needed.
Click to expand...
Click to collapse
(B)If you are already Running SPLM Rom But you want to update with latest version:
Boot Into Recovery Mode
Flash provided Updates of SPLM ROM(latest weekly)
Again Wipe Cache and Dalvik
Reboot To System.
Click to expand...
Click to collapse
SOURCE:
SPLM ROM SOURCE
SPLM DEVICES SOURCE
Kernel Sources
CREDITS:
ALL SPLM team
CM
AOSPA-L
SlimRom
CrDroid
DU
Omnirom
Click to expand...
Click to collapse
WHO ARE WE AND WHAT ARE WE DOING?:
TEAM SPIKE LABORATORY
​
XDAevDB Information
Metallium OS, ROM for the Oppo Find 7
Contributors
Schneiderle, a1krab
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2015-09-14
Created 2015-09-14
Last Updated 2015-09-15

reserved

reserved

New build
Hello Guys,
First release is available :
metallium_find5-1.0-20150914.zip
Download:
https://www.androidfilehost.com/?fid=24052804347815860
Next builds will have changelog.
Enjoy & Cheers

jejecule said:
Hello Guys,
First release is available :
metallium_find5-1.0-20150914.zip
Download:
https://www.androidfilehost.com/?fid=24052804347815860
Next builds will have changelog.
Enjoy & Cheers
Click to expand...
Click to collapse
Feedback are really appreciated
Sent from my Nexus 6 using XDA Free mobile app

New build Metallium
Hello new build is up: see op download link to basketbuild or normal way: https://www.androidfilehost.com/?fid=24052804347817647
Cheers

Here comes the feedback:
- Autorotation doesnt work. Maybe kernel related.
- Some lag and instability but this could very (most definitely) well be the bidji kernel. (Havent tested on stock kernel)
- Everything else works fine.
- Betterylife is fine, nothing crazy.
- Botton backlight works
Will test tomorrow with stock kernel a few minutes to confirm sone issues maybe. But I like the battery life of bidji kernel too much to not use it.
What does this rom do different compared to other cm like roms? I couldnt really find any major pros or cons. Just very cm like but not from cm I guess. I really hate that they have edited the default launcher with their own ugly app drawer icon and removed the launcher options. Luckily we have an appstore with other launchers. I will change rom to DU again probably because of the auto rotate (but button backlight doesnt work there if i recall correctly).
Still really loving all your builds to test compare and tinker with. And the new bidji kernel makes the tinkering and fiddling even more interesting . Hope this feedback helps.
Verstuurd vanaf mijn Find 5 met Tapatalk

boertjeg said:
Here comes the feedback:
- Autorotation doesnt work. Maybe kernel related.
- Some lag and instability but this could very (most definitely) well be the bidji kernel. (Havent tested on stock kernel)
- Everything else works fine.
- Betterylife is fine, nothing crazy.
- Botton backlight works
Will test tomorrow with stock kernel a few minutes to confirm sone issues maybe. But I like the battery life of bidji kernel too much to not use it.
What does this rom do different compared to other cm like roms? I couldnt really find any major pros or cons. Just very cm like but not from cm I guess. I really hate that they have edited the default launcher with their own ugly app drawer icon and removed the launcher options. Luckily we have an appstore with other launchers. I will change rom to DU again probably because of the auto rotate (but button backlight doesnt work there if i recall correctly).
Still really loving all your builds to test compare and tinker with. And the new bidji kernel makes the tinkering and fiddling even more interesting . Hope this feedback helps.
Verstuurd vanaf mijn Find 5 met Tapatalk
Click to expand...
Click to collapse
Ik dank je voor uw feedback!
Autorotation: well still a mistery only DU is working, kernel is the same, so frameworks must be the culprit.
For the rest, I just jump into this project cause I found it interesting and different from others but i'm slowly think I was wrong.
Anyway,yes it not cm but device trees are so, bugs will remain mainly the same .
To be honest, not sure I'll keep on long time with this one except if users are happy
At least om my AFH I have some 30 downloads, in their basketbuild, 0...
Een prettige end of weekend!
Jeje
Sent from my Nexus 6 using XDA Free mobile app

(I lolled a bit because of you typing Dutch )
Tested again on stock kernel, same issues as before with auto rotate. Something to add why this is different compared to other roms: it is not so much in options but everything that is there is done well. Like all icons and stuff are all good and done and there are no wierd looking menus. So it is a very slick experience IMHO (except the boot logo ugh).
Cheers

Hello Guys,
With Metallium team members, we decided to make those builds "unofficials". This won't change anything for you, builds with remain the same with same quality and improve progressively.
This is a good team and i'm proud to build for them, last post from my dutch mate proves it.
Reasons why this change: i prefer to keep my liberty, to build myself, to post my builds where i used to post it, and so on. Furthermore, i'm official member of crDroid team and it takes me lot of time, and i want to keep the same quality for them too.
So expect new Metallium build at least weekly.
I wish you a nice evening.
Cheers,

Any signs of lvm support on the ROM?
Sent from my X9076 using Tapatalk

New Find5 Metallium
piyush7243 said:
Any signs of lvm support on the ROM?
Sent from my X9076 using Tapatalk
Click to expand...
Click to collapse
Only one chinese mate is doing it without publishing his sources, so really difficult.
By the way: new build is up: metallium_find5-1.0-20150921.zip
Download: https://www.androidfilehost.com/?fid=24052804347820446
Cheers

jejecule said:
Only one chinese mate is doing it without publishing his sources, so really difficult.
By the way: new build is up: metallium_find5-1.0-20150921.zip
Download: https://www.androidfilehost.com/?fid=24052804347820446
Cheers
Click to expand...
Click to collapse
I think the sources are here
https://github.com/feelingfree-me/android_device_oppo_apq8064-common/tree/5.1.1-lvm
Sent from my X9076 using Tapatalk

piyush7243 said:
I think the sources are here
https://github.com/feelingfree-me/android_device_oppo_apq8064-common/tree/5.1.1-lvm
Sent from my X9076 using Tapatalk
Click to expand...
Click to collapse
i will check then guys!
I suppose some special twrp are required too?
Cheers

There you go. This is support LVM
https://www.androidfilehost.com/?fid=24052804347760547

piyush7243 said:
There you go. This is support LVM
https://www.androidfilehost.com/?fid=24052804347760547
Click to expand...
Click to collapse
Thanks mate, appreciated, i will try a build today, hope you'll test it, don't worry i'll test it first
Cheers

The TWRP works fine and can unify the storage. The CM build posted on the oppo forums seems to work no worse than any other CM-derived rom. An LVM aware build of Dirty Unicorns would be awesome. I'm happy to test things because my Find 5 isn't my primary device anymore so I don't rely on it.

jejecule said:
Thanks mate, appreciated, i will try a build today, hope you'll test it, don't worry i'll test it first
Cheers
Click to expand...
Click to collapse
I am already running a CM version having LVM and its good apart from Auto rotate which seems to be a bug in CM12.
But another ROM with proper support would be awesome and feel free to get back to me to test the same
P.S: enabling selinux enforce by default seems to be a but flaky

piyush7243 said:
I am already running a CM version having LVM and its good apart from Auto rotate which seems to be a bug in CM12.
But another ROM with proper support would be awesome and feel free to get back to me to test the same
P.S: enabling selinux enforce by default seems to be a but flaky
Click to expand...
Click to collapse
Unfortunately, CM12 has the autorotate issue in all my builds except DU. So what i propose is, first make a test on metallium to see if LVM works then try to adapt to DU, new DU version should come within one day or two.
Thanks for your support.
Cheers

Guys,
If you wanna test a lvm compatible build: go there: metallium_find5-1.0-20150923.zip
https://www.androidfilehost.com/?fid=24052804347821013
Cheers

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.

Bake AOSP Pie for Xperia XZ?

Hi all!
As Sony has posted instructions on how to compile Android Pie for our XZ (among others), I just wondered if anyone here has tried it?
The posted guide looks quite straight forward, but as I have no experience on using fit-repost and such I'm not sure I'm up for the challenge of taking this project on.
If tried, what could be expected to work? I know that for all previous Xperia devices, camera and wifi components has always been weak-points in AOSP-roms..
Please discuss and advice!
Regards, Static.

I'm currently trying to build android P for XZ with the guide from Sony.
I'm downloading the code ATM.
I'll give you feedback about my journey to Pie ^^

Awesome!
I'm eager to hear about your endeavors in this!

L'ily said:
Hey me too, do you have a single- or dual-SIM variant?
Click to expand...
Click to collapse
I have a single sim variant

L'ily said:
Nice, I have the F8332 so we can test on both models. I have no idea what I'm doing though and whilst an unofficial GApps 9 build is available (albeit only in Stock) it doesn't appear Sony have released the vendor images yet so even if we successfully build I'm disinclined to believe they'll boot, although I'm going to try with the last release anyway.
Click to expand...
Click to collapse
Didn't Sony released beta vendor images for kernel 4.9 ?
I thought that would be compatible with pie.
That being said, it should be bootable without it. We will just have to check the kernel version and flash the vendor image accordingly.

@L'ily and I have been trying to build Pie for F8331 and F8332 but sadly it didn't work ...
The first issue we had was with the repo syncing. On my end it took an incredible 48h (@400KB/s peak) and also failed 3 times but by relaunching it I made it to the end. My partner however had a worst yet faster time with syncing. Maybe it is due to localisation (Australia and France) . We think it is simply because the repos weren't ready. I mean they are still no vendor files for Pie.
Second issue was with building. None of us could get through it. We kept having an error (see screen shot). It seams like it is a file missing but we didn't know we're to look for it as the sync was complete.
We tried both engendering build and userdebug. Same error.
@L'ily also tried build Oreo but it didn't work either ...
If anybody has an input on what we could do we would be grateful
Cheers,
Ickule

Here is the screenshot I mentioned in my previous post.
I forgot to include it ...

Ok so I managed to get through the building process. The missing files have matching name with files in an other folder (4.4 instead of 4.9).
That being said it sadly didn't boot.
That was kind of expected if you ask me ^^'
Still I don't get why i didn't had the files in the first place ...
Any input guys ?

I'm currently trying to build Pie myself (for the 309234023492094th time in the last two days) with other errors every time I set up a new machine. But what I can say about the error with the missing kernel file is that there's a script in the sony repos that looks like it'd be building the missing file, although I'm not sure if we have to call it manually first

31, so single-sim and unfortunately, I don't have the logs anymore as I always started with fresh machines.
I'm currently checking the other forums because I'm not really satisfied with the solution of using 4.4 kernel binaries with a 4.9 build
Edit: I might have achieved something, I compiled the kernel from 4.9 sources I hope and it's now building. Fingers crossed ?
Edit 2: It boots!

I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.

Ickule said:
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Click to expand...
Click to collapse
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331

Magic-Fabi said:
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Click to expand...
Click to collapse
So you managed to get Pie working or only compiling the kernel ?
Thanks for clarifying the 31 thing

Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait

Xperia z1 has carbon Android pie and gapps link
This may help you.

Magic-Fabi said:
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Click to expand...
Click to collapse
That's awesome !
Did you dio anything special aside from the instructiosn sony gave ?
I try to build Pie and the Kernel by the books but i always seam to fail for some reason ^^'
I'm usung Ubuntu 18.04 for the building OS.

No, all I used was Sony's guide and referenced Google's build instructions for the libraries I have to install. For the missing kernel file I used their (manual!) Kernel compilation guide
I used Ubuntu 18.04 LTS as well, the only "unusual" thing I did was that I didn't install any openjdk version and even deleted the one preinstalled as they have openjdk bundled with aosp ?*
Edit: Note that you have to copy and rename the compiled kernel file in arch/arm64/boot/Image.gz-dtb to kernel-dtb-kagura in /kernel/sony/msm4.9/common-kernel. You can easily read past that as I did in the beginning

Well let's assume I had a bad syncing time or something cause I followed the very same instructions ^^'
Anyway, it seam like we still miss the vendor files from sony so ...
I'll give it another shot when they'll be out.

Just a curious thing, will GCam work on Pie like it did on AOSP Oreo?

I believe the requirement for GCam is Camera API 2 and raw support which is built into AOSP.
It surely will be compatible.

[ROM][OS][pre alpha]PostMarket OS.[Help Appreciated]

First Of all.THIS IS NOT A QUESTION OR A CALL FOR ACTUAL HELP.I have seen a few replacements for AOSP and Postmarket OS is one of them.Being in early stages it is very useful if being ported or compiled for Devices with stylus or phablet factor.I am Currently working on the OS after I read the Documentation.I as of Now have managed to Run the Test UI on it.All functions(except GPS ril Bluetooth thermal and maybe MTP)Do work Properly.The Main UI is still un-bootable.I would post it as soon as Possible.The Main Feature of this is THAT IT USES THE MAINLINE LINUX KERNEL.A little crazy to say it but it says it does that and it may take a week to do it.I have compiled it 37 times and it takes a very little time on my machine But the number of fatal errors are in hundreds or Thousands which are all Related to compatibility.
A huge thanks to xda-Website and a shoutout to PMOS(as I would call it) for doing such a great thing.
Again I can't do it myself The only thing I can't seem to make it work is to boot the rootfs for unknown reasons.As Soon as I achieve something I will Post Links.
kernel that works https://github.com/LineageOS/android_kernel_samsung_msm8974
kernel that's official
https://github.com/CyanogenMod/android_kernel_samsung_hlte
zImage that boots(with halium rootfs that works with any rootfs)
https://drive.google.com/file/d/17ksmUn5FTqOuL9mKsOCqrhe3W3mqGwUe/view?usp=drivesdk
the latest linaro 7.3.x toolchain arm for note 3
https://drive.google.com/file/d/1Ld5Nb7rekgbFLAcyW16721_1GITP_2wv/view?usp=drivesdk
zImage that get's to testing
https://drive.google.com/file/d/12sQbEzl4nfK7E3IXwbpxIYy_mKcZ6Q4W/view?usp=drivesdk
common kernel zImage built on nexus 5 model doesn't boot.
https://drive.google.com/file/d/1GyJKCKn9DxynOeTx8Ea4wHSxHm7S1nd1/view?usp=drivesdk
and again help is appreciated.
Sent from my Pixel 3 XL using Tapatalk

Regarding Android 10 on the HP Touchpad

Hello
For the past couple (weeks) I've been trying to compile Android 10 for tenderloin using the Android 9 sources but it's not going so well. First thing I ran into multiple sepolicy errors and I feel as if I fixed them in inappropriate ways but the errors went away. Other errors regarding camera and audio and such, that are regarding that tenderloin no longer uses the legacy audio format. Made me confused because I used the device sources form Evervolv and DIrty unicorns and if i'm correct they built it exactly the same way they uploaded it. After these errors were wrapped up, I got a error at zipping the rom that it could not zip due to failure of being able to read build.prop. This made me believe that the sources are not correctly formatted. If anyone can help me find a manifest, I can build for all you guys. Please keep tenderloin alive!
Now, I did something and I'm getting plenty of perl errors. Maybe I'm just very unlucky. I'm gonna attempt to reinstall on a fresh drive on my server.
If its anyone's concern, I was building lineage 17.1. I noticed for example, Lineage's "qcom-device" repo was shaped completely differently than Evervolvs qcom-device repo.
This led me to thought that Android 10 is going to be extremely difficult because of all the upstream dev changes that was pushed to Q. If any of you would like, I could probably push out March patches Pie rom because over there I'm mostly safe of complying with the source.
My manifest shape
DirtyUnicorn's device-tree
DirtyUnicorn's device-tree-common
DirtyUnicorn's htc-msm8960-kernel
Evervolv's vendor
And dirty unicorn's atheros wlan driver
I have been changing up the device tree so much, it almost looks ridiculous . From what I heard lots of properties on the device tree haven't been touched for years. Maybe tomorrow I can try Evervolv's Q rom. If you guys can help me build up my manifest, we can push out a fully working Q rom for tenderloin. And it would be just in time when Android 11 comes out. Thank you everyone!

I wish that I could offer any help, but I never tried to compile any Android ROM or for the HP_TP.
To my knowledge the only users that I know that could offer some insight on the process would be:
 @flintman
 @elginsk8r
Also the LuneOS project could offer some help:
https://pivotce.com/tag/luneos/
If Android Q(10) can not be ported to the HP_TP, then at least P(9) is a good ROM to keep updating that could provide many years of App support.

Theres no reason why exactly it cant,, because lots of roms I hear were built off the original TP sources (From 2011!). It was only around 2016 when guys around here had to change it up so much that they should've been so surprised that it worked. I can try and temporarily maintain P roms until the boys around here push out sources for Q!

djared704 said:
Theres no reason why exactly it cant,, because lots of roms I hear were built off the original TP sources (From 2011!). It was only around 2016 when guys around here had to change it up so much that they should've been so surprised that it worked. I can try and temporarily maintain P roms until the boys around here push out sources for Q!
Click to expand...
Click to collapse
To my limited knowledge is all about Hardware -->> Drivers -->> ( Kernel ).
The reason that Bluetooth and camera does not work on newer Android version is due to the old (proprietary drivers) and the Kernel. That takes more dedication and work than the ROM. The same rules applies to the desktop, older processors does not support certain features and the Operating System will not run. It is possible to disable the features in the kernel so that it does not check the hardware and make it run, but it will be unstable.
Everything could be possible with plenty of time, knowledge and dedication.

HP_TOUCHPAD said:
To my limited knowledge is all about Hardware -->> Drivers -->> ( Kernel ).
The reason that Bluetooth and camera does not work on newer Android version is due to the old (proprietary drivers) and the Kernel. That takes more dedication and work than the ROM. The same rules applies to the desktop, older processors does not support certain features and the Operating System will not run. It is possible to disable the features in the kernel so that it does not check the hardware and make it run, but it will be unstable.
Everything could be possible with plenty of time, knowledge and dedication.
Click to expand...
Click to collapse
When I look at the tenderloin source, the script to gather the camera driver is disabled. Camera isnt a huge deal though because its only 1.3 MP. However we use the MSM 8960 kernel from HTC and that is the one m7,, but the one m7 is a SD 600 device so it loses sense. I was gonna get some help with one of my kernel developer buddies to dev a kernel for android 10 for tenderloin. If you see the one m7 has Lineage 17.1 available and even though it doesnt have same chipset, if im correct both chipsets went off of the same assembly line process. Lineage 17.1 for the one m7 also packages it as a "uimage" which is what we use. I believe this was only a very small select of devices. Yeah about that ive been getting so many complaints during build about "mkimage" which should've been a prebuilt tool in the lineage source. Don't know why they removed it, or if our developers added it in by their selves, etc. Anyways I fixed that error by just "allowing" mkimage in one of the permission files in my environment. But yeah i went as far as the build packaging the ROM and it complaining it cannot read build.prop. Note the build.props are generated by the environment , not the source (even though the device data is gathered by the source, its not what im talking about). I even go to the directory it was complaining about and it was all there. One of my friends suggested a permission error. I changed permissions to 777 (rw to all users) and it would still output that error. By that point I trashed my build meaning I may of done something wrong early on. I will let someone else continue building 10 but I will continue building 9 with latest patches.

It will be extremely impressive if any kernel developer will update the HP Touchpad Kernel or tweak it for future release, well everything will stop once Android becomes 64 only.
I am sure you are very well aware, but I will suggest using this built:
https://forum.xda-developers.com/hp-touchpad/development/rom-evervolv-hp-touchpad-t3923512
I was able to do the following playing around recompiling the Kernel. I recompile almost all the ROM and incorporated the same kernel changes.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
The Ramdisk is also very easy to unpack and repack:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
There is no need to get the original Camera or Bluetooth working, only sound and WiFi.

HP_TOUCHPAD said:
It will be extremely impressive if any kernel developer will update the HP Touchpad Kernel or tweak it for future release, well everything will stop once Android becomes 64 only.
I am sure you are very well aware, but I will suggest using this built:
https://forum.xda-developers.com/hp-touchpad/development/rom-evervolv-hp-touchpad-t3923512
I was able to do the following playing around recompiling the Kernel. I recompile almost all the ROM and incorporated the same kernel changes.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
The Ramdisk is also very easy to unpack and repack:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
There is no need to get the original Camera or Bluetooth working, only sound and WiFi.
Click to expand...
Click to collapse
I think I probably stated somewhere, but Evervolvs "device" tree would just spit out hundreds of errors, and I fixed this by switching to Dirty Unicorns device tree. I also tried flintman's device tree and it didn't spit out many errors. Thanks for this though.

djared704 said:
I think I probably stated somewhere, but Evervolvs "device" tree would just spit out hundreds of errors, and I fixed this by switching to Dirty Unicorns device tree. I also tried flintman's device tree and it didn't spit out many errors. Thanks for this though.
Click to expand...
Click to collapse
I have only recompile the Kernel and all of them work, but the correct branch must be use. I can not say about building a ROM, never done it.
But Evervovs Pie by elginsk8r works very well and stable as it uses the same kernel, but the framework is different. I guess elginsk8r will be the only that can guide you on the right direction or flintman.
Have fun learning, it takes a lot of TIME!