Related
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is the AOSP ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Sony AOSP Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level and the OEM binary got fully implemented, if there is no need for a critical hotfix.
Preview Picures:
https://forum.xda-developers.com/showpost.php?p=77635765&postcount=2
https://forum.xda-developers.com/showpost.php?p=78870686&postcount=436
https://forum.xda-developers.com/showpost.php?p=79450390&postcount=619
https://forum.xda-developers.com/showpost.php?p=79460850&postcount=624
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime) Bootloader issue needs to get fixed to make custom roms bootable on slot B.
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
Click to expand...
Click to collapse
Known Bugs:
Camera is under development.
[TAMA] [AKATSUKI] [CRITICAL??] Speakers clipping and distortion
Bugreport:
A bugreport needs logcat, dmesg and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@nasko_spasko
@laoli0913
@twistedddx
@dhacke thank your for providing a download server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
AOSP, ROM for the Xperia XZ2
Contributors
MartinX3, Sony
Source Code: https://github.com/SonyAosp
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 9
Stable Release Date: 2019-08-08
Created 2018-09-16
Last Updated 2020-10-23
Download & Installation
Download:
https://androidfilehost.com/?w=devices&uid=11410963190603893035
https://www.dhsfileserver.de/ftp/martinx3/ Thank you @dhacke for the second download server
Unzip the *.gz files with 7-zip or Linux.
GCAM (Need GAPPS, but improves the camera a lot):
I usually use the newest Arnova's GCAM
Installation:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash oem oem_*.img
(Optional, but mandatory on first boot) fastboot flash userdata userdata.img -> will factory reset the device.
(Mandatory on dual sim devices) Dual Sim Patcher
(Optional) https://opengapps.org/ or MicroG
News
05.01.2020
this rom is now officially end of life like the omnirom.
Future development happens only on android 10.0 with kernel 4.14.
Of course this doesn't automatically make this rom unusable.
Click to expand...
Click to collapse
27.10.2019
sonyaosp 9.0.0_r46
august security patch
newest sync with sodp code.
Fixed not working touch for the few xz2 (compact) users with tcm touch chip.
(i don't know why the tcm chip got rarely used in the xz2 & xz2 compact hardware).
Ps: The new security updates are only happening on android 10 and require backporting to 9 from developers who know what they are doing to avoid any new (security) bugs.
We sadly don't have this capacity.
Click to expand...
Click to collapse
07.09.2019
dear xz2 compact owners with not working touch.
It seems that we fixed the problem
https://github.com/sonyxperiadev/bug_tracker/issues/351
the code needs to to get refactored and merged into sodp, before i can release new builds.
But anyway, i'm on vacation & studying for exams, so don't expect builds earlier than end of september/october.
To test it
apollo_v8.zip
Code:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
28.08.2019
someone may have seen that in september comes a sodp switch to
1. Android 10 (queen cake)
2. Kernel 4.14 (using 4.9 at the moment)
i won't switch asap to the new stuff and wait until it proofs enough stability to act as a daily driver.
Maybe it is stable directly right release (i don't think it) or it may take ~1-5 months.
(and i don't know how fast sonyaosp switches to q.)
Click to expand...
Click to collapse
26.08.2019
september no new release
reason -> vacation + university exams
Click to expand...
Click to collapse
08.08.2019
sonyaosp 9.0.0_r46
august security patch
new glove mode
Click to expand...
Click to collapse
12.07.2019
sonyaosp 9.0.0_r44
july security patch
Click to expand...
Click to collapse
16.06.2019
sonyaosp with june 2019 security patch level.
Click to expand...
Click to collapse
31.05.2019
sonyaosp with may 2019 security patch level.
Newer, faster, more stable, oemv9 support.
Also i'll only push files to the single sim device section.
The dual sim device section will get a file with a hint to look into the single sim section.
There is also the twrp dual sim patcher. Without it the single sim firmware won't work on a dual sim phone.
That'll save bandwith and server storage.
I linked the patcher on the first page, but use my uploaded v4alpha patcher instead.
It contains my complete overhaul of the patcher and the current v3 in the xda thread doesn't work on tama.
I already made a pull request and the author just needs to merge my changes.
https://git.ix5.org/felix/dualsim-patcher/pulls/3
Click to expand...
Click to collapse
19.05.2019
reworked the thread page
Click to expand...
Click to collapse
14.05.2019
http://www.dhsfileserver.de/ftp/martinx3/ thank you @dhacke for the second download server
Click to expand...
Click to collapse
11.05.2019
next build will hopefully contain the open source chromium browser cherry-picked from omnirom.
(if i didn't it wrong, the builds are at
out/target/product/{devicename}/obj/apps/chromium_intermediates/
and
out/target/product/{devicename}/system/app/chromium/chromium.apk)
so we have at least one browser build in and this should also fix maybe happening webview bug.
Thank you @murrofx and @hingbong for your bugreports!
The next build is on hold (like omnirom and aosp twrp) until we get a new prebuild kernel (prebuild kernels usually ensure that the kernel is working and buildable).
https://github.com/sonyxperiadev/vendor-sony-kernel/tree/aosp/le.um.2.3.2.r1.4
Click to expand...
Click to collapse
02.05.2019
i heard that oemv9 will support the hexagon snapdragon processor.
- longer battery life
- faster device
- real hdr plus for our tama camera
Click to expand...
Click to collapse
22.04.2019
oemv8 (camera) support!
Click to expand...
Click to collapse
22.04.2019
attached oemv8 images at the post
https://forum.xda-developers.com/showpost.php?p=77635765&postcount=2
it is only a current snapshot of the camera development.
Expect further improvements with the upcoming oem blobs.
Ps: Oemv8 compatible builds are getting compiled.
Click to expand...
Click to collapse
12.04.2019
9.0.0_r35 april security update
much fixes
oemv7 support
you should be able to try aosp 10.0 q gsi's with it!
Click to expand...
Click to collapse
07.04.2019
bug & feature tracker
https://github.com/martinx3sandroiddevelopment/bug_tracker
Click to expand...
Click to collapse
21.02.2019
updated the rom for the probably tomorrow released sony oem v6 with updated camera hal!
(beta release, has still a crash with exposure, they are not finished with their work. Don't expect stock like photos "now".)
Click to expand...
Click to collapse
10.02.2019
february 2019 patch level
switch from sony aosp to sonyaosp.
Sony aosp = sonyaosp + additional fixes (like exfat sdcard support)
sonyaosp = aosp + device support fixes for xperias
i excluded the gapps with a bit work and investigation!
Click to expand...
Click to collapse
17.01.2019
january 2019 patch level
Click to expand...
Click to collapse
09.01.2019
moved to android file host.
Added builds for every supported device.
Click to expand...
Click to collapse
22.12.2018
added the xz3 (akatsuki).
Camera still not feature complete.
Please search or report bugs in the bug tracker.
Twrp will follow.
Click to expand...
Click to collapse
29.11.2018
first android 9.0 build.
added the xz2c (apollo).
Should be stable enough for stable use.
Please search or report bugs in the bug tracker.
Click to expand...
Click to collapse
12.10.2018
new build with fixed bugs.
including the fixed display damaging bug.
May may maaaaaaaaay you get graphical/display issues, you should deactivate your device asap with (vol up + power)
Click to expand...
Click to collapse
24.09.2018
build "2018-09-14_15:00+2:00":
Switched back to oem vendor img for android 8.1.
The oem vendor 9.0 img shouldn't be used.
Click to expand...
Click to collapse
16.09.2018
first release of the unstable, bugfull build.
Click to expand...
Click to collapse
Deleted. Reason: wrong thread.
Anyone that has AOSP installed can do me a Favor and run a MicroSD Speed Test?
I.E Androbench and in Settings switch target partition to MicroSD folder.
Haldi4803 said:
Anyone that has AOSP installed can do me a Favor and run a MicroSD Speed Test?
I.E Androbench and in Settings switch target partition to MicroSD folder.
Click to expand...
Click to collapse
The sdcard Support is still missing.
(Look at the bug list)
24.09.2018
Build "2018-09-14_15:00+2:00":
Switched back to OEM vendor img for Android 8.1.
The OEM vendor 9.0 img shouldn't be used.
Click to expand...
Click to collapse
https://github.com/sonyxperiadev/bug_tracker/issues/169#issuecomment-424278920
PLEASE DON'T FLASH TAMA WITH THE CURRENT KERNEL
My Akari's display got permanently damaged.
I repeat, DO NOT FLASH.
Click to expand...
Click to collapse
I planned a new build on thuesday with the new kernel fixes.
But now I will wait.
The AOSP 4.9 kernel is now stable enough to get prebuild by sony.
(Which is inside my TWRP builds)
Nice.
https://github.com/sonyxperiadev/vendor-sony-kernel/tree/aosp/LE.UM.2.3.2.r1.4
My next AOSP ROM will probably get nice fixes. (Should still be tested and confirmed).
But he still need to confirm if the hardware damaging bug got really fixed or only by a workaround.
https://github.com/sonyxperiadev/bug_tracker/issues/166#issuecomment-425406778
HI every1 !
Does any1 know why I am unable to find any Xperia XZ2 rom in the web at all ?
I hate the feeling I can't use Gcam at all because of Cam2 API is not supported .
margee82 said:
HI every1 !
Does any1 know why I am unable to find any Xperia XZ2 rom in the web at all ?
I hate the feeling I can't use Gcam at all because of Cam2 API is not supported .
Click to expand...
Click to collapse
Do you mean Custom ROMs?
The XZ2 was introduced with a brand new kernel.
It took months make it compatible with AOSP to create custom ROMs and even since the compatibility stock update in September, the aosp support needs more work.
After that and my TWRP starts working, the custom creation will start.
Probably I make a new build with synced sources in 3 weeks.
Then the user github user kholk will be back from his 15 days vacation.
(He mentioned the display damage but and created the workaround).
Status Update!
https://github.com/sonyxperiadev/kernel/pull/1688#issuecomment-428714128
kholk said:
MSM8956 Loire stability not impacted by the upstream updates. @oshmoun never saw stability issues due to that.
Tone testing can be started since this platform is stable.
Tama testing will happen soon, after display issues get solved.
Display Issues = The Big Hardware Damaging Bug!
Yoshino, Nile on hold due to stability issues to be solved.
Click to expand...
Click to collapse
Display issues = The Big Hardware Damaging Bug!
It seems that I will make a new AOSP Build this week.
The Sony Developers made a rampage in the XZ2 Bug List on Github and closed important bugs, including the display damaging bug.
MartinX3 said:
It seems that I will make a new AOSP Build this week.
The Sony Developers made a rampage in the XZ2 Bug List on Github and closed important bugs, including the display damaging bug.
Click to expand...
Click to collapse
Are you aware that sony released new binaries for 8.1 ?
im curious what the binary brings for 8.1 roms
hary232 said:
Are you aware that sony released new binaries for 8.1 ?
im curious what the binary brings for 8.1 roms
Click to expand...
Click to collapse
Yeahr and switched to 8.1.0r47
That are the AOSP hardware drivers
MartinX3 said:
Yeahr and switched to 8.1.0r47
That are the AOSP hardware drivers
Click to expand...
Click to collapse
cool. i assume you are planning to release a build soon then (after the build error gets fixed by sony, of course)?
hary232 said:
cool. i assume you are planning to release a build soon then (after the build error gets fixed by sony, of course)?
Click to expand...
Click to collapse
Yes
You saw my reported build error?
MartinX3 said:
Yes
You saw my reported build error?
Click to expand...
Click to collapse
yes! i really look forward for DRS functionality.
i'm monitoring the github from time to time. still not pulling the trigger to unlock the bl tho.
At any case, thank you for your hard work so far.
hary232 said:
yes! i really look forward for DRS functionality.
i'm monitoring the github from time to time. still not pulling the trigger to unlock the bl tho.
At any case, thank you for your hard work so far.
Click to expand...
Click to collapse
Thank you
After storm released the DRMfix (after I gave him the ok) you can use your stock firmware like you had never unlocked the BL
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is the OmniROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on OmniROM Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level and the OEM binary got fully implemented, if there is no need for a critical hotfix.
Preview Picures:
https://forum.xda-developers.com/showpost.php?p=78856251&postcount=2
https://forum.xda-developers.com/showpost.php?p=78856492&postcount=4
https://forum.xda-developers.com/showpost.php?p=79450402&postcount=443
https://forum.xda-developers.com/showpost.php?p=79460796&postcount=456
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime) Bootloader issue needs to get fixed to make custom roms bootable on slot B.
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
Click to expand...
Click to collapse
Known Bugs:
Camera is under development.
[TAMA] [AKATSUKI] [CRITICAL??] Speakers clipping and distortion
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
OmniROM Bugtracker -> If you think the problem is in OmniROM
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs logcat, dmesg and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@oshmoun for his device tree portings
@dhacke thank your for providing a download server
And the OmniROM developers!
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
OmniROM, ROM for the Xperia XZ2
Contributors
MartinX3, Sony, oshmoun, OmniROM
Source Code: https://github.com/omnirom/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: OmniROM
Version Information
Status: No Longer Updated
Current Stable Version: 9
Stable Release Date: 2019-08-10
Created 2019-02-07
Last Updated 2020-10-23
Download & Installation
Download:
https://androidfilehost.com/?w=devices&uid=11410963190603893035
https://www.dhsfileserver.de/ftp/martinx3/ Thank you @dhacke for the second download server
Unzip the *.gz files with 7-zip or Linux.
GCAM (Need GAPPS, but improves the camera a lot):
I usually use the newest Arnova's GCAM
Installation:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash oem oem_*.img
(Optional, but mandatory on first boot) fastboot flash userdata userdata.img -> will factory reset the device.
(Mandatory on dual sim devices) Dual Sim Patcher
(Optional) https://opengapps.org/ or MicroG
In case of touch issues on the XZ2 compact:
Download (try the v10 zip first, if it doesn't work try v9 or v8)
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(Mandatory on dual sim devices) Dual Sim Patcher
If your system apps did loose their permissions (sadly that happens sometime after flashing a boot.img again -> AOSP bug which is maybe fixed in 10.0)
fastboot flash userdata userdata.img (Flashing the boot.img may
(Optional) https://opengapps.org/ or MicroG
News
05.01.2020
i thought pushing a maintenance update would be a good idea.
Sadly it wasn't achievable.
I tried to simply rebuild the old sodp sync with the newest omnirom, also synced the newest sodp stuff wit the newest omnirom.
But that every time resulted into
1. Installing gapps on a fresh system let the device crash into twrp with the message "set_policy_failed:/data/cache/"
2. Upgrading from the previous version resulted into "no web views detected". The webview is needed for some apps to render their content. Without that they would simply crash.
Regardless if the gapps, aosp or bromite webview was installed, none was listed and the logcat throws errors.
3. The audio doesn't route anymore to a connected usb audio 3.5mm adapter.
4. There may be more bugs, but i am too frustrated to with the already occurring bugs and invested hours/days.
Lets look optimistically into the future of android 10.0, kernel 4.14 and which custom roms can be build on it.
Click to expand...
Click to collapse
12.10.2019
https://gerrit.omnirom.org/#/q/topic:asb_2019-09+(status:open+or+status:merged)
https://gerrit.omnirom.org/#/q/topic:asb_2019-10+(status:open+or+status:merged)
omnirom 9 may be deprecated, but it seems that they backport security fixes.
Soooo, we get still security updates.
On the other side i got insulted (called a stupid idiot), warned, kicked and banned at once for asking about the security commits and saying that the insulter has a low emphatic intelligence.
I look if i will continue distributing stuff for this toxic community administration.
Click to expand...
Click to collapse
04.10.2019
it's official announced by the omnirom boss.
Omnirom 9 reached end of life and is now deprecated.
Omnirom 10 for xz2, xz2c, xz3 will come after the sony aosp builds with q and kernel 4.14 are stable enough.
Click to expand...
Click to collapse
07.09.2019
dear xz2 compact owners with not working touch.
It seems that we fixed the problem
https://github.com/sonyxperiadev/bug_tracker/issues/351
the code needs to to get refactored and merged into sodp, before i can release new builds.
But anyway, i'm on vacation & studying for exams, so don't expect builds earlier than end of september/october.
To test it
apollo_v8.zip
Code:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
28.08.2019
someone may have seen that in september comes a sodp switch to
1. Android 10 (queen cake)
2. Kernel 4.14 (using 4.9 at the moment)
i won't switch asap to the new stuff and wait until it proofs enough stability to act as a daily driver.
Maybe it is stable directly right release (i don't think it) or it may take ~1-5 months.
(and i don't know how fast omnirom switches to q.)
Click to expand...
Click to collapse
26.08.2019
september no new release
reason -> vacation + university exams
Click to expand...
Click to collapse
11.08.2019
omnirom 9.0.0_r47
august security patch
new glove mode
Click to expand...
Click to collapse
12.07.2019
omnirom 9.0.0_r44.
July security patch.
Click to expand...
Click to collapse
11.06.2019
omnirom 9.0.0_r40.
June security patch.
Click to expand...
Click to collapse
31.05.2019
omnirom with may 2019 security patch level.
Newer, faster, more stable, oemv9 support.
Also i'll only push files to the single sim device section.
The dual sim device section will get a file with a hint to look into the single sim section.
There is also the twrp dual sim patcher. Without it the single sim firmware won't work on a dual sim phone.
That'll save bandwith and server storage.
I linked the patcher on the first page, but use my uploaded v4alpha patcher instead.
It contains my complete overhaul of the patcher and the current v3 in the xda thread doesn't work on tama.
I already made a pull request and the author just needs to merge my changes.
https://git.ix5.org/felix/dualsim-patcher/pulls/3
Click to expand...
Click to collapse
19.05.2019
reworked the thread page
Click to expand...
Click to collapse
14.05.2019
http://www.dhsfileserver.de/ftp/martinx3/ thank you @dhacke for the second download server
Click to expand...
Click to collapse
02.05.2019
i heard that oemv9 will support the hexagon snapdragon processor.
- longer battery life
- faster device
- real hdr plus for our tama camera
Click to expand...
Click to collapse
22.04.2019
oemv8 (camera) support!
Removed buildin twrp.
Twrp needs to get build as -eng, not as -userdebug.
And we got now a working "fastboot boot twrp.img".
Click to expand...
Click to collapse
22.04.2019
attached oemv8 images at the post
https://forum.xda-developers.com/showpost.php?p=78856251&postcount=2
it is only a current snapshot of the camera development.
Expect further improvements with the upcoming oem blobs.
Ps: Oemv8 compatible builds are getting compiled after i released the oemv8 sonyaosp builds.
Click to expand...
Click to collapse
07.04.2019
bug & feature tracker
https://github.com/martinx3sandroiddevelopment/bug_tracker
Click to expand...
Click to collapse
02.04.2019
omnirom 9.0.0_35.
April security patch.
Needs oemv7 blobs.
Improved stability and fixed bugs.
Now with integrated twrp.
Hopefully fixed ril crash with manually merged upstream code from sony aosp sodp.
Click to expand...
Click to collapse
31.03.2019
omnirom 9.0.0_34.
March security patch.
Needs oemv7 blobs.
Improved stability and fixed bugs.
Now with integrated twrp.
Click to expand...
Click to collapse
22.02.2019
updated the rom for the sony oem v6 with updated camera hal!
(beta release, has still a crash with exposure, they are not finished with their work. Don't expect stock like photos "now".)
Click to expand...
Click to collapse
10.02.2019
february security update release.
Click to expand...
Click to collapse
07.02.2019
finaly xda fixed their blocking website bug and i was able to create this new xdadev project.
First release from 01. February 2019
Click to expand...
Click to collapse
Screenshots
Screenshots
Always great devoted work from you!
You have a small typo in your post:
The stock firmware updates doesn't not update your "android"
Should read
The stock firmware updates doesn't just update your "android"
twistedddx said:
Always great devoted work from you!
You have a small typo in your post:
The stock firmware updates doesn't not update your "android"
Should read
The stock firmware updates doesn't just update your "android"
Click to expand...
Click to collapse
xD Thank you
Great job [emoji6]
How is battery life?
Any lag after a few days if use?
Envoyé de mon H8266 en utilisant Tapatalk
niaboc79 said:
Great job [emoji6]
How is battery life?
Any lag after a few days if use?
Envoyé de mon H8266 en utilisant Tapatalk
Click to expand...
Click to collapse
Thank you
The only thing I see so far is the missing camera.
And the phone uses a bit more energy I thing, but I need to test that.
Together with the sony team we did a great step.
Now we support the exFAT file system on sdcards.
(There still needs work to be done in the sepolicy, will take a bit before code gets merged for my next release build)
PS:
ext4 support for sdcards, too.
Hooo i see interactive governor in the screenshots?
AOSP does not use EAS or does only OMNI rom not use EAS?
Haldi4803 said:
Hooo i see interactive governor in the screenshots?
AOSP does not use EAS or does only OMNI rom not use EAS?
Click to expand...
Click to collapse
erm, maybe the added EAS stuff last month. Hmm.
I asked some devs now.
Edit:
Interactive is used.
And there is no EAS.
Deleted
MartinX3 said:
erm, maybe the added EAS stuff last month. Hmm.
I asked some devs now.
Edit:
Interactive is used.
And there is no EAS.
Click to expand...
Click to collapse
So old HMP is used by Sony for their SD845 devices, or is this "workaround" only applied upon their official shared AOSP sources and blobs?
Could in that case explain the increased power consumption, becausr HMP is a leeching sucker compared to Energy Aware Scheduling / EAS.
xFirefly93 said:
So old HMP is used by Sony for their SD845 devices, or is this "workaround" only applied upon their official shared AOSP sources and blobs?
Could in that case explain the increased power consumption, becausr HMP is a leeching sucker compared to Energy Aware Scheduling / EAS.
Click to expand...
Click to collapse
I ask them if there are EAS plans.
Edit:
No plans, seems they don't like it.
Edit1:
Seems that with the other stuff in the kernel the EAS would lead into a battery drain.
And that the AOSP is battery optimized without it.
Ediit2:
They don't hate EAS.
It was just a decision at a time where other parameters lead to this decision.
Maybe they switch to EAS in the future.
Edit3:
EAM Energy Models are needed.
And because it's very hard to get one EAS may never get implemented.
@MartinX3
When do you plan to release the Omnirom build with the february 2019 patch?
dhacke said:
@MartinX3
When do you plan to release the Omnirom build with the february 2019 patch?
Click to expand...
Click to collapse
The February patch level required a rebuild of my build cache.
It's at 20% since an hour.
I am sure I can upload the stuff this evening.
MartinX3 said:
The February patch level required a rebuild of my build cache.
It's at 20% since an hour.
I am sure I can upload the stuff this evening.
Click to expand...
Click to collapse
Thx for the info.
dhacke said:
Thx for the info.
Click to expand...
Click to collapse
You're welcome. Feel free to ask.
@MartinX3
Besides of the security patch are there any other fixes in the new upcoming build?
dhacke said:
@MartinX3
Besides of the security patch are there any other fixes in the new upcoming build?
Click to expand...
Click to collapse
It has a build in changelog app.
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is the LineageOS ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Code from Sony AOSP & LineageOS and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime)
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
Click to expand...
Click to collapse
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
LineageOS Bugtracker -> If you think the problem is in LineageOS
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
@Raphos for the initial installation manual without a recovery system, after I switched to OTA zips.
@kgvarunkanth for the jenkins build server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
LineageOS, ROM for the Xperia XZ2
Contributors
MartinX3, SODP Team
Source Code: https://github.com/MartinX3-AndroidDevelopment-LineageOS/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Stable Version: 17.1
Created 2020-02-02
Last Updated 2020-10-23
Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
Please use the the OEM build which came before my last release, unless otherwise written.
GCAM Camera App:
Suggested GCams But GCAM's aren't usable at the moment until a camera hardware resource budget bug got fixed in the OEM binary blob.
Installation with a recovery:
fastboot flash oem_a oem_*.img
fastboot flash oem_b oem_*.img
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
Google Apps like Playstore
Dual Sim Patcher
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot -w (Wipes your internal storage and the userdata)
Continue with the normal installation
News
24.08.2020
since we have now an official lineageos based on stock, this rom would be double work.
So i stop the los port.
(sadly unless a dev owns a xz2p or xz3 these phones won't be supported in the official stock based lineageos)
the only difference between the stock and sodp editions are:
Sodp will get gcam support later and has camera2api level 3.
Stock will never support gcam apps and has the limited stock camera2api level.
Sodp uses a 4.14 kernel and probably get mainline support later.
Stock uses the stock 4.9 kernel and will probably be there forever.
Sodp targets to use as much open source as possible.
And livedisplay doesn't work in my sodp version.
Ps: After the september exams in the new semester i look for a rom replacement for the sake of diversity.
It's good to have a choice and with the available official supported sodp based pixel experiment, we have a rom which sadly forces you to use the full gapps (google apps package).
Click to expand...
Click to collapse
13.07.2020
july security patch level
oemv9c support
and any other sodp open source changes since my last build
Click to expand...
Click to collapse
18.06.2020
june security patch level
oemv8 support
and any other sodp open source changes since my last build
fixes for charger, battery, sleep (sideeffect working bluetooth audio) and more!
Click to expand...
Click to collapse
11.05.2020
may security patch level
oemv6 support
and any other sodp open source change since my last build
ps: Camera is work in progress.
Please flash gapps and the dual sim patcher again after applying an ota update.
It seems that the ota zip replaces every partition and deletes the modifications (like gapps).
Also it enforces avb heavily which prevents modifications like gapps from getting loaded.
So i deactivated avb now.
(but since the device bootloader can't be relocked the avb is not really useful anyway)
Click to expand...
Click to collapse
14.04.2020
now android 10.0.0_r33
april security patch level
oemv5 support
and any other sodp open source change since my last build
switched to:
zip files to flash
dual sim patcher instead of dual sim rom files
removed buildin gapps, since you can flash it now via twrp
installing this rom as an update won't remove the installed gapps.
ps: Camera is work in progress.
Click to expand...
Click to collapse
09.03.2020
march 2020 security update
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will get activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
01.03.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
29.02.2020
added support for every sodp supported xperia https://github.com/martinx3-androiddevelopment-lineageos/
(except the loire and tone platform which no one requested.)
the oemv4 rom release will delay a bit.
Was in the need to delete my build cache for aosp and lineageos.
Click to expand...
Click to collapse
25.02.2020
need to take down the builds.
Oemv4 which comes tomorrow got some additional last minute changes today which needs a new rom compilation.
Click to expand...
Click to collapse
24.02.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & volte & other improvements
and an other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Oemv4 maybe comes tomorrow.
Click to expand...
Click to collapse
15.02.2020
feburary security patch level
fixed bugs, now my sony aosp release and this lineageos port should contain the same amount of bugs (aside from the stuff on the lineageos part).
Switched from alpha to beta version.
The only instability i found on my own xz2 is a crash at night in flightmode without charger.
Anything else doesn't crash it here.
Might be various reasons.
If anyone has the same bug, please provide logs in my github issue tracker.
(and please look if your logs contain more informations than my logs).
Click to expand...
Click to collapse
02.02.2020
the first lineageos 17.1 build based on the sodp device trees.
My vanilla sodp release and lineageos should share the same bugs.
Plus bugs / missing features in lineageos and bugs introduced by myself porting sodp to lineageos :silly:
sadly i can't upload it at the moment to android file host.
Their new "stackpath" ddos blocking solution banned me, because i tried to upload the rom in 6 browser tabs. :silly:
fixed
have fun!
Ps: Camera is work in progress.
Twrp 10 is not ready, so i sadly can't start develop one for the xz2, xz2c, xz3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
that's the reason i include opengapps pico for now.
And to use magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
Gcam doesn't work with oemv3.
There is a library missing.
Click to expand...
Click to collapse
02.02.2020
The first LineageOS 17.1 build based on the SODP device trees.
My vanilla SODP release and LineageOS should share the same bugs.
Plus bugs / missing features in LineageOS and bugs introduced by myself porting SODP to LineageOS :silly:
Sadly I can't upload it at the moment to Android File Host.
Their new "Stackpath" DDOS blocking solution banned me, because I tried to upload the ROM in 6 browser tabs. :silly:
Fixed
Have Fun!
PS: Camera is work in progress.
TWRP 10 is not ready, so I sadly can't start develop one for the XZ2, XZ2C, XZ3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
That's the reason I include OpenGapps Pico for now.
And to use Magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
GCAM doesn't work with OEMv3.
There is a library missing.
Click to expand...
Click to collapse
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Orihamburger said:
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Click to expand...
Click to collapse
Thank you
Yes, at least I can use VoLTE in my country with my provider.
You need to test it by yourself. [emoji14]
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Does this crash only happen when someone upgraded his phone to stock 10.0 first or does it also happen with a previously installed stock 9.0 rom?
https://github.com/MartinX3-AndroidDevelopment-LineageOS/bug_tracker/issues/1
MartinX3 said:
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Click to expand...
Click to collapse
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
zhka said:
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
Click to expand...
Click to collapse
Thank you
I'm curious if it is the same issue.
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
nikkdib said:
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
Click to expand...
Click to collapse
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
MartinX3 said:
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
Click to expand...
Click to collapse
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
nikkdib said:
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
Click to expand...
Click to collapse
Gcam should work with OEMv4
There is a library missing to run this application.
The XZ3 Dual file is corrupted. It is only 50MB in size
nickholtus said:
The XZ3 Dual file is corrupted. It is only 50MB in size
Click to expand...
Click to collapse
Thank you, but the dual sim version only contains the files different from the single sim version.
MartinX3 said:
Thank you, but the dual sim version only contains the files different from the single sim version.
Click to expand...
Click to collapse
Ahhh damnn, sorry my fault! Stupid mistake
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Mazurik said:
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Click to expand...
Click to collapse
Thank you
At the moment the source code of TWRP 10.0 is not available/usable, but is needed to create a TWRP with the 10.0 code environment.
Why you can't install omnirom?
The TWRP only work for the 9.0 ROMs at the moment and will be fixed in the future.
The LineageOS 16.0 release wasn't made by me and I can't do anything (except creating my own LineageOS 16.0 but my time/ressources are sadly limited :silly
does anyone know how well gcam works compared to stock camera on locked device?
tb_ said:
does anyone know how well gcam works compared to stock camera on locked device?
Click to expand...
Click to collapse
The camera driver is work in progress
The gcam workarounded missing features on 9.0.
Now on 10.0 we need to wait for OEMv4 for a working gcam.
This is not my build. Credit ny-hardcore for all the hard work on this. I'm just posting it.
Screen call is broken.
This is Lineage 18, Android 11 custom rom for the Pixel 4a Sunfish
If you do not want root, you can stop after step 6
1. Reboot to bootloader
2. fastboot flash --slot all boot recovery.img https://drive.google.com/file/d/1Hh7D_UbnnoTRr1XbC9i0-dvtFgbuFqrP/view?usp=sharing
3. Reboot to recovery
4. factory reset
5. adb sideload lineage-18.0-20201209-UNOFFICIAL-sunfish.zip
https://mega.nz/file/cUlVXApI#NbzUJ6UlyQvyPTitKnW7uJG_tHrsfYor9O0dH4yIiWc
6. Reboot to system
7. Install Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
8. Reboot to bootloader
9. fastboot flash boot magisk_patched.img https://drive.google.com/file/d/1cONN9Ev0jdAHaRSeOeYyeRTONJ-yO_8-/view?usp=sharing
10. Reboot to system
Could you please provide a kernel and device source tree for this? I have an in-progress diff which I am working to get 18 running fully on the device. It doesn't boot yet, and I would like to know what I messed up.
liamwhite said:
Could you please provide a kernel and device source tree for this? I have an in-progress diff which I am working to get 18 running fully on the device. It doesn't boot yet, and I would like to know what I messed up.
Click to expand...
Click to collapse
Based on the fact that this is NOT my work as stated above, I'm NOT at liberty to tell you. No offense. I would contact xda member edmontonchef and ask him. He's the one who sent it to me. I would like to think this wouldn't be a issue because if it was mine, I wouldn't care, but it's not.
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
ny-hardcore said:
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
Click to expand...
Click to collapse
I'm using it right now. Great Rom. Thank you!!! Hope you don't mind I shared it.
Does this support signature spoofing?
Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
Would doubt it, if it's just vanilla LOS
ny-hardcore said:
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
Click to expand...
Click to collapse
Are Gapps included. Looking for a non gapps rom
EggZenBeanz said:
Are Gapps included. Looking for a non gapps rom
Click to expand...
Click to collapse
No gapps. Minimal Google play service function are included in build.
Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
No
TheSayaMan said:
No gapps. Minimal Google play service function are included in build.
Click to expand...
Click to collapse
Actually it contains gapps/Google play.
ny-hardcore said:
Actually it contains gapps/Google play.
Click to expand...
Click to collapse
I guess I assumed wrong. I thought he was referring to having to flash a seperate gapps zip.
Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
i'm working on a microg edition using the notes from the guy who made the microG build for 4a 5G
ny-hardcore said:
i'm working on a microg edition using the notes from the guy who made the microG build for 4a 5G
Click to expand...
Click to collapse
Oh yeah! Would love to see that. I'm ready to hop from my pixel 3xl once there's a non gapps ROM available
New build updated in OP. Thank Senior Member ny-hardcore for this.
Changes: Lineage sources and kernel updated with latest google update. The boot.img was updated in the payload to eliminate a second boot flash after sideloading rom for working WiFi. Please report any bugs that I may have missed. Also, I never dirty flash over anything. They more than likely cause problems. I did a clean install of this. If you are on the previous build of this, I DO NOT recommend dirty flashing it.
TheSayaMan said:
New build updated in OP. Thank Senior Member ny-hardcore for this.
Changes: Lineage sources and kernel updated with latest google update. The boot.img was updated in the payload to eliminate a second boot flash after sideloading rom for working WiFi. Please report any bugs that I may have missed. Also, I never dirty flash over anything. They more than likely cause problems. I did a clean install of this. If you are on the previous build of this, I DO NOT recommend dirty flashing it.
Click to expand...
Click to collapse
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Edmontonchef said:
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Click to expand...
Click to collapse
I haven't been able to check everything out. One thing I just noticed is that I am unable to pass safetynet with it but not a big deal for me.
Edmontonchef said:
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Click to expand...
Click to collapse
The boot in OP will work as well so take your pick and yes I did notice its still November. He's working on another build though.
TheSayaMan said:
The boot in OP will work as well so take your pick and yes I did notice its still November. He's working on another build though.
Click to expand...
Click to collapse
december hasnt been merged in lineage sources
Is the boot.img a twrp recovery or? I am coming from stock, so would i need to touch twrp at all for this?
I'm just curious whether anyone has already compiled the AOSP for A13 and booted it. I noticed it had already been done/tested on OP5/5T, but wasn't sure if it had been done for P6P. I plan on trying my hand at it, but wanting to know what others may have experienced before I commit my slower internet connection to downloading the Repo.
GrapheneOS has test builds up for A13, which should be buildable using the normal approach. Also hardened with some extra security features.
Yes, on ArrowOS, temp issues however that was same day arrow started updating to 13, have not run a build since. Evolution X reboot a few seconds after setup screen loads, does not boot without gapps either.
I have tried for several days, but I'm missing something
It's a custom rom for personal use. A12.1 booted and worked perfectly but 13 reboots to bootloader
RealSchnedi - Repositories
RealSchnedi has 15 repositories available. Follow their code on GitHub.
github.com
Schnedi said:
I have tried for several days, but I'm missing something
It's a custom rom for personal use. A12.1 booted and worked perfectly but 13 reboots to bootloader
RealSchnedi - Repositories
RealSchnedi has 15 repositories available. Follow their code on GitHub.
github.com
Click to expand...
Click to collapse
Stupid question have you flashed both slots with 13 as I know boot loader won't load of you have 12 version and not updated to 13 but also it has an anti roll back in it sorry not much help
liggerz87 said:
Stupid question have you flashed both slots with 13 as I know boot loader won't load of you have 12 version and not updated to 13 but also it has an anti roll back in it sorry not much help
Click to expand...
Click to collapse
I flashed the bootloader and radio on both slots but haven't tried to change the current slot and flash the rom
But if I flash the official 13 release (only in the current slot) it boots, so, not sure if that's the problem. Anyway, I'll try it
Schnedi said:
I flashed the bootloader and radio on both slots but haven't tried to change the current slot and flash the rom
But if I flash the official 13 release (only in the current slot) it boots, so, not sure if that's the problem. Anyway, I'll try it
Click to expand...
Click to collapse
Been looking at our github, you are using anayw2001 repo for your vendor files, remove the below from Android.bp. I had Restless nights with a poop load of testing thinking it was something with a missing lib file or so when i test anay's vendor files with lots of comparison to lineage extract tools that worked. Well if your getting bootonce-bootloader error that is as reason for bootloader load.
prebuilt_apex {
name: "com.google.android.compos",
owner: "google_devices",
src: "system_ext/apex/com.google.android.compos.apex",
prefer: true,
system_ext_specific: true,
}
prebuilt_apex {
name: "com.google.android.virt",
owner: "google_devices",
src: "system_ext/apex/com.google.android.virt.apex",
prefer: true,
system_ext_specific: true,
}
alvin14 said:
Yes, on ArrowOS, temp issues however that was same day arrow started updating to 13, have not run a build since. Evolution X reboot a few seconds after setup screen loads, does not boot without gapps either.
Click to expand...
Click to collapse
Update on this for ArrowOS. After removing connectivitythernmalmanager that fixed the issue as i am getting selinux denials with it, everything works, been testing for a few days.
alvin14 said:
Been looking at our github, you are using anayw2001 repo for your vendor files, remove the below from Android.bp. I had Restless nights with a poop load of testing thinking it was something with a missing lib file or so when i test anay's vendor files with lots of comparison to lineage extract tools that worked. Well if your getting bootonce-bootloader error that is as reason for bootloader load.
prebuilt_apex {
name: "com.google.android.compos",
owner: "google_devices",
src: "system_ext/apex/com.google.android.compos.apex",
prefer: true,
system_ext_specific: true,
}
prebuilt_apex {
name: "com.google.android.virt",
owner: "google_devices",
src: "system_ext/apex/com.google.android.virt.apex",
prefer: true,
system_ext_specific: true,
}
Click to expand...
Click to collapse
I was already using your vendor from gitlab (arrow branch). It did the trick, bootloader not triggered anymore
Still not booting but it must be related to rom sources, will take a look
Thanks a lot
Schnedi said:
I was already using your vendor from gitlab (arrow branch). It did the trick, bootloader not triggered anymore
Still not booting but it must be related to rom sources, will take a look
Thanks a lot
Click to expand...
Click to collapse
Do a logcat during boot, will definitely help with that.
card13 said:
I'm just curious whether anyone has already compiled the AOSP for A13 and booted it. I noticed it had already been done/tested on OP5/5T, but wasn't sure if it had been done for P6P. I plan on trying my hand at it, but wanting to know what others may have experienced before I commit my slower internet connection to downloading the Repo.
Click to expand...
Click to collapse
There is a build of Hentai which is very good. You can even dirty flash from stock
alvin14 said:
Do a logcat during boot, will definitely help with that.
Click to expand...
Click to collapse
Thanks, I'm making some tests, not so sure it's the rom sources
Question, to build Evo and Arrow, are you using your adevtool vendor or the other one?
Schnedi said:
Thanks, I'm making some tests, not so sure it's the rom sources
Question, to build Evo and Arrow, are you using your adevtool vendor or the other one?
Click to expand...
Click to collapse
Adevtool. The other one works as well however i need to clean it up a bit.
hi guys,
@Schnedi what gapps package are you using for prime?
And does udfps work on your raven with your prime base?
Well, after a dozen of test builds, I finally made it work
Still have to fix things tho
Schnedi said:
Well, after a dozen of test builds, I finally made it work
Still have to fix things tho
Click to expand...
Click to collapse
Cool. I got oriole too boot prime yesterday too. Nice work!
What gapps package do you use? Is it on gitlab somewhere?
ny-hardcore said:
Cool. I got oriole too boot prime yesterday too. Nice work!
What gapps package do you use? Is it on gitlab somewhere?
Click to expand...
Click to collapse
I'm using this one: https://gitlab.com/spkal01/android_vendor_gms/-/tree/pyro
But removed some apps that can be installed from the store (drive, youtube, gmail, photos...)
Also, latest commit from fw/b fixes udfps
There's just a few features, I just pick the ones I use, didn't build prime to share it, so I'm not picking all of them. You can always fork the project and pick some features you use, PM me if you need any help with it
Schnedi said:
I'm using this one: https://gitlab.com/spkal01/android_vendor_gms/-/tree/pyro
But removed some apps that can be installed from the store (drive, youtube, gmail, photos...)
Also, latest commit from fw/b fixes udfps
There's just a few features, I just pick the ones I use, didn't build prime to share it, so I'm not picking all of them. You can always fork the project and pick some features you use, PM me if you need any help with it
Click to expand...
Click to collapse
Thanks for the reply, i spark gapps too by the way haha
i picked udfps myself so had it working already
i like your vendor /vendor/extras very clean setup.
i know how to fork, but no need for now