Related
There is a new version out there now - http://phones.crackflashers.com/glacier/recoveries/glacier-cwm3src3.0.0.5-1-22-11.img ..
Anyone know what is different then the 1-16-11 version?
Probably not much. I dont remember seeing anything about it being merged in github. And nothing official will come out until we have a RC1 build of CM.
option94 said:
Probably not much. I dont remember seeing anything about it being merged in github. And nothing official will come out until we have a RC1 build of CM.
Click to expand...
Click to collapse
It is there (see below) - but would like to know what are the changes (someone put it there for a reason, but....).
Name Size Date Uploaded
glacier-cwm3src-2.img
4.12 MB 05 January 2011
glacier-cwm3src3.0.0.5-1-16-11.img
4.10 MB 16 January 2011
glacier-cwm3src3.0.0.5-1-16-11.zip
4.08 MB 16 January 2011
glacier-cwm3src3.0.0.5-1-22-11.img
4.10 MB 22 January 2011
glacier-cwmsrc3.0.0.2.img
4.12 MB 05 January 2011
glacier-cwmsrc3.0.0.2.zip
4.10 MB 05 January 2011
Has anyone flashed this yet?
gaww said:
It is there (see below) - but would like to know what are the changes (someone put it there for a reason, but....).
Name Size Date Uploaded
glacier-cwm3src-2.img
4.12 MB 05 January 2011
glacier-cwm3src3.0.0.5-1-16-11.img
4.10 MB 16 January 2011
glacier-cwm3src3.0.0.5-1-16-11.zip
4.08 MB 16 January 2011
glacier-cwm3src3.0.0.5-1-22-11.img
4.10 MB 22 January 2011
glacier-cwmsrc3.0.0.2.img
4.12 MB 05 January 2011
glacier-cwmsrc3.0.0.2.zip
4.10 MB 05 January 2011
Click to expand...
Click to collapse
I know its there, but that doesn't mean anything was changed. Look through r.cyanogenmod.com or github.com/cyanogen and you wont find any relevent changes for out phones.
I think I have good news for some of you
There are some hints, that there will be official AOSP support from sony for our devices soon.
For all of you, who don't know: There is a official AOSP project for a few sony devices.
Our problem: Our devices aren't supported (yet?).
But there are good news:
1. The Sony Xperia Developer World github account has forked the rhine-common device tree from FreeXperia/Cyanogenmod. That means they are not uninterested.
2. It gets better: Alin Jerpelea, a member of the Sony Xperia Open Source team and member of FreeXperia, will give a talk about the future of the Sony AOSP support at xda devcon in half a month.
3. And now the best: The github repositority for Sony AOSP kernel recently got a new branch, which is at the same caf tag like our 14.4.A.108 kernel
I am really hoping this becomes truth in near future
Sources:
http://developer.sonymobile.com/201...-mobile-innovation-with-us-at-xdadevcon-2014/
https://github.com/sonyxperiadev/kernel-copyleft/commits/14.4.A.0.xxx
https://github.com/sonyxperiadev/kernel/tree/aosp/LNX.LA.3.5.1-01110-8x74.0
https://github.com/sonyxperiadev/android_device_sony_rhine-common
UPDATE: the latest git commits are proving it, we will get official aosp support
UPDATE: the latest commits prove that z2 and it's variants will also get official aosp(with the same kernel sources as us, congrulations)
That would be great :good:
Does this mean better camera drivers and stuff?
rob rich said:
Does this mean better camera drivers and stuff?
Click to expand...
Click to collapse
Potentially, lets hope so!
CoolDevelopment said:
I think I have good news for some of you
There are some hints, that there will be official AOSP support from sony for our devices soon.
Click to expand...
Click to collapse
First 4.3" high-end device and now official AOSP? Sony, you might just make me a Sony fanboy
Does that mean that it could be possible to flash aosp based roms with locked bootloader? Or am I completely wrong here?
AFAIK the repository for current AOSP devices from sony does not contain camera drivers (and others). So don't expect to much from this news.
vriz27 said:
Does that mean that it could be possible to flash aosp based roms with locked bootloader? Or am I completely wrong here?
Click to expand...
Click to collapse
Unfortunately not
See the latest commits at the git. They are proving the new kernel branch is for sony devices
CoolDevelopment said:
See the latest commits at the git. They are proving the new kernel branch is for sony devices
Click to expand...
Click to collapse
If I'm reading the commits right, and I'd like to think that I am, then we are witnessing the official AOSP bring-up for the rhine-platform!
There's over a thousand lines of new camera code here: https://github.com/sonyxperiadev/kernel/commit/f721c1a0585ab6b9d3eb75a84bc2cf79a7813741
Get excited guys!
Rekoil said:
If I'm reading the commits right, and I'd like to think that I am, then we are witnessing the official AOSP bring-up for the rhine-platform!
There's over a thousand lines of new camera code here: https://github.com/sonyxperiadev/kernel/commit/f721c1a0585ab6b9d3eb75a84bc2cf79a7813741
Get excited guys!
Click to expand...
Click to collapse
That are the same drivers as from the stock kernel, don't expect these commits to increase our camera.
TheQwertiest said:
First 4.3" high-end device and now official AOSP? Sony, you might just make me a Sony fanboy
Click to expand...
Click to collapse
:laugh:
The newest commits are hinting on aosp for z2 aswell
Holy $h13!
How did i not see that before!?
I wasn't interested in devcon all that much. However, now since i know something like official aosp support might be announced there, I can't wait!
SONY GIB UNS AOSP UNTERSTÜTZUNG JETZT!
Sorry, couldn't handle the excitement
Its now official for Z1 and Z2 ! :laugh:
Xperia™ Z2 and Xperia™ Z1 added to AOSP for Xperia on GitHub
And somes good news for our Z1 compact plus other devices :
Xperia Z1 and Z2 added to AOSP for Xperia project; plus unified kernel announced
official ground for AOSP, sweet
I have a question.
Is there any benefits from this for people who has phone with locked bootloader and with -no allowed status? Or i just can congrats people who has unlocked bootloader?
mosespl said:
I have a question.
Is there any benefits from this for people who has phone with locked bootloader and with -no allowed status? Or i just can congrats people who has unlocked bootloader?
Click to expand...
Click to collapse
Only for unlocked bootloaders.
Nice , Tat is a good news.
Thanks for this share. Looking forward for this!
Something it's moving.. https://github.com/sonyxperiadev/device-sony-amami
I created a Website to gather FTF for all version Xperia since models generally doesn't have xda thread or other websites to share FTF.
http://www.wroid.ir/index.php/tool/ram/sony-r
At the moment there are all models and versions since I couldn't find others...
If someone has FTF not listed on the Website, please post here.
I'll add it on the Website.
XPERIA 2010
XPERIA 2011
XPERIA 2012
XPERIA 2013
XPERIA 2014
XPERIA 2015 (Is complete)
XPERIA 2016 (Is not complete)
Edit for New Collection & Web Address 4.10.2016
Add:
-Add Full XPERIA 2015 Firmware (Is complete)
-Add Full XPERIA 2016 Firmware (Is not complete)
-New UI Web Address
-Edit Again All Xperia Device Download Link
Edit for New Download Link 4.12.2016
-Update Download Link Xperia Z5 Line to 32.1.A.1.185
-Update Download Link Xperia Z4/Z3+ Line to 32.1.A.1.185
Edit for New Added Last Firmware models 4.13.2016 :
Xperia Z5 (E6683)
Xperia Z5 Premium (E6883)
Edit for New Added Last Firmware model 4.14.2016 :
Xperia M4 Aqua (E2333)
WRoid.ir The best and most complete server firmware free:fingers-crossed:
How do i switch the Language of the Page to english? Not fond of google translator.
it is arabic.
Haldi4803 said:
How do i switch the Language of the Page to english? Not fond of google translator.
Click to expand...
Click to collapse
cimihendriks said:
it is arabic.
Click to expand...
Click to collapse
it's not Arabic, it's Persian
naheel azawy said:
it's not Arabic, it's Persian
Click to expand...
Click to collapse
well, it's not english, that is the problem.
cimihendriks said:
well, it's not english, that is the problem.
Click to expand...
Click to collapse
Well,description in that page is Persian/Farsi but links are obviously in English nevertheless description isn't important, anyway it's better to be translated by OP.
@hussein1
cimihendriks said:
well, it's not english, that is the problem.
Click to expand...
Click to collapse
Use the "Google Chrome" browser and right-click web page and select translate to english.
So there is no problem
hussein1 said:
Use the "Google Chrome" browser and right-click web page and select translate to english.
So there is no problem
Click to expand...
Click to collapse
Some people has their browser, i mean some people doesnt want install chrome and thats problem to see your web
Its very kindly if u want to use English version as default if u want more people visit your web
No offense :good:
Latest firmware version for E1 is not ....13, it is .19 (only the end numbers changed)
Edit for New Collection & Web Address 4.10.2016:fingers-crossed:
Add:
-Add Full XPERIA 2015 Firmware (Is complete)
-Add Full XPERIA 2016 Firmware (Is not complete)
-New UI Web Address
-Edit Again All Xperia Device Download Link
@ hussein1
hi.will you add Z5 new mm update? .185
josephnero said:
@ hussein1
hi.will you add Z5 new mm update? .185
Click to expand...
Click to collapse
Edit for New Download Link 4.12.2016
-Update Download Link Xperia Z5 Line to 32.1.A.1.185
-Update Download Link Xperia Z4/Z3+ Line to 32.1.A.1.185
No Z5 Dual E6683
Z5 dual e6683 is missing
devilmaycry2020 said:
No Z5 Dual E6683
Click to expand...
Click to collapse
karrouma said:
Z5 dual e6683 is missing
Click to expand...
Click to collapse
4.13.2016 Added Last Firmware:
Xperia Z5 (E6683)
Xperia Z5 Premium (E6883)
@hussein1 Hi
1- sony xperia m4 aqua ( e2333 ) is missing please add it
2- please add the rom country for all of phones
whe should know which roms we want to used
thanks
Hamidreza2010 said:
@hussein1 Hi
1- sony xperia m4 aqua ( e2333 ) is missing please add it
2- please add the rom country for all of phones
whe should know which roms we want to used
thanks
Click to expand...
Click to collapse
Edit for New Added Last Firmware model 4.14.2016 :
Xperia M4 Aqua (E2333)
hussein1 said:
4.13.2016 Added Last Firmware:
Xperia Z5 (E6683)
Xperia Z5 Premium (E6883)
Click to expand...
Click to collapse
These aren't your links, you are just taking these links from Xperia Blog's Firmware Resource page.
Stop this or you will be reported.
Aripex said:
These aren't your links, you are just taking these links from Xperia Blog's Firmware Resource page.
Stop this or you will be reported.
Click to expand...
Click to collapse
yes
This site has been created just for quick access to firmware link
No registration Needless ...
hussein1 said:
yes
This site has been created just for quick access to firmware link
No registration Needless ...
Click to expand...
Click to collapse
There is no need for quick access, as you can get it just as quickly on XB. Registration is a 2 second job.
Also, you’ve not mentioned anywhere – either on your site or the first post here – that these links are from Xperia Blog. You’ve masqueraded as if you are downloading the firmware and uploading it for everyone to share. You need to be upfront on where these are sourced from.
Source: https://blogs.sonymobile.com/2017/08/31/xperia-android-8-0-oreo/
Got nearly 2 years of updates, but not quite.
On a related note, official XZ1 Compact website is up. I'm thinking about getting one for my wife to replace her Z5C, UFS sounds delicious.
The list of devices in the blog is not final and it is possible that we will see Oreo on our device.
Even though stock will not support Oreo, Custom firmwares will usually always outlast stock
(Lineage and Carbon are using stock blobs on the Z5 Lineup so custom roms are nearly the same quality, if not better, then stock anyway)
nzzane said:
Even though stock will not support Oreo, Custom firmwares will usually always outlast stock
(Lineage and Carbon are using stock blobs on the Z5 Lineup so custom roms are nearly the same quality, if not better, then stock anyway)
Click to expand...
Click to collapse
I was wondering about this myself. Are the stock blobs sdk version specific, so in order to make a custom Oreo rom a stock Oreo ftf is needed first? Or should the nougat blobs potentially be used in an Oreo firmware? Same with hardware drivers that are unique to our device, like WiFi?
cyberwytch said:
I was wondering about this myself. Are the stock blobs sdk version specific, so in order to make a custom Oreo rom a stock Oreo ftf is needed first? Or should the nougat blobs potentially be used in an Oreo firmware? Same with hardware drivers that are unique to our device, like WiFi?
Click to expand...
Click to collapse
From memory, as long as the source is configured right it should be fine (Wifi drivers shouldn't be changing as its still the same hardware, same for screen and all) - Carbonrom and Lineage source are currently being updated to Oreo, along with some of the sony files being configured for it so hopes are high.
nzzane said:
From memory, as long as the source is configured right it should be fine - Carbonrom and Lineage source are currently being updated to Oreo, along with some of the sony files being configured for it so hopes are high.
Click to expand...
Click to collapse
Awesome sauce! I love your Lineage 14, can't wait to see what's next!
nzzane said:
Even though stock will not support Oreo, Custom firmwares will usually always outlast stock
(Lineage and Carbon are using stock blobs on the Z5 Lineup so custom roms are nearly the same quality, if not better, then stock anyway)
Click to expand...
Click to collapse
That's awesome news, I'll add "official" to the thread title for clarification.
They said it was because Qualcomm aren't great at after market support.
so we couldn't get 3.18, but, what would be interesting to do would be to make some interface to act like a middle man.
I'm currently doing something similar for my laptop running Server 2016, and am slowly making it run like a Desktop OS, by enabling all the other stuff left out that I can find
---------- Post added at 16:25 ---------- Previous post was at 16:21 ----------
nzzane said:
...
Click to expand...
Click to collapse
which linux kernel is LOS running?
NeoBeum said:
They said it was because Qualcomm aren't great at after market support.
so we couldn't get 3.18,
Click to expand...
Click to collapse
Where was this said, and why would we need 3.18 for the Z5 family?
A lot of the reporting being done on this has been bad (whatever happened to reading comprehension, especially in reporters??). According to the source being cited, only SoCs produced prior to 2017 (which the Snapdragon 810 is) AND that are being launched in new devices (which the Z5 series is NOT) are required to run on 3.18. Existing devices already designed and sold before the launch of Oreo (which, having launched in 2015, I think the Z5 family would qualify as) "can continue to use their original base kernel version if desired."
-- Nathan
nlra said:
Where was this said, and why would we need 3.18 for the Z5 family?
A lot of the reporting being done on this has been bad (whatever happened to reading comprehension, especially in reporters??). According to the source being cited, only SoCs produced prior to 2017 (which the Snapdragon 810 is) AND that are being launched in new devices (which the Z5 series is NOT) are required to run on 3.18. Existing devices already designed and sold before the launch of Oreo (which, having launched in 2015, I think the Z5 family would qualify as) "can continue to use their original base kernel version if desired."
-- Nathan
Click to expand...
Click to collapse
on github somewhere,
actually, ask and tag greyleshy, he was the one that asked about final kernel for us, and I found the convo somewhere trying to get Bluetooth junk sorted
there might be some msm8994 thing that sony needs but cant use for oreo or something. I dont know
NeoBeum said:
on github somewhere,
actually, ask and tag greyleshy, he was the one that asked about final kernel for us, and I found the convo somewhere trying to get Bluetooth junk sorted
there might be some msm8994 thing that sony needs but cant use for oreo or something. I dont know
Click to expand...
Click to collapse
Hmm, 'k; thanks. I'll do some more digging. But if true this would flatly contradict Google's own public statements (though I realize it's not like this would be a first for that kind of thing).
-- Nathan
NeoBeum said:
They said it was because Qualcomm aren't great at after market support.
so we couldn't get 3.18, but, what would be interesting to do would be to make some interface to act like a middle man.
Click to expand...
Click to collapse
Android Oreo supports Kernel 3.10, but need to patch the kernel (example: patch 1, patch 2).
It would be nice if msm8994 supported kernel 3.18 or 4.4, but it is not.
Apparently QCOM has not provided drivers for 3.18+ and therefore CodeAurora kernel was not released because of compatibility issues.
NeoBeum said:
which linux kernel is LOS running?
Click to expand...
Click to collapse
3.10, CAF kernel
nlra said:
Where was this said, and why would we need 3.18 for the Z5 family?
A lot of the reporting being done on this has been bad (whatever happened to reading comprehension, especially in reporters??). According to the source being cited, only SoCs produced prior to 2017 (which the Snapdragon 810 is) AND that are being launched in new devices (which the Z5 series is NOT) are required to run on 3.18. Existing devices already designed and sold before the launch of Oreo (which, having launched in 2015, I think the Z5 family would qualify as) "can continue to use their original base kernel version if desired."
-- Nathan
Click to expand...
Click to collapse
correct,
actually 4.4 kernel, it's only needed for newer SoCs
so we can go on with 3.10 kernel for now but we need to wait for (potential) CAF changes
GreyLeshy said:
Android Oreo supports Kernel 3.10, but need to patch the kernel (example: patch 1, patch 2).
It would be nice if msm8994 supported kernel 3.18 or 4.4, but it is not.
Apparently QCOM has not provided drivers for 3.18+ and therefore CodeAurora kernel was not released because of compatibility issues.
Click to expand...
Click to collapse
well, there's still Linux mainline / vanilla upstream support for msm8994 since 4.10 kernel in a very rough state with terminal only (AOSP)
and there's the (close to complete) bringup of msm8994 on 3.18 kernel sauce: https://github.com/sonyxperiadev/kernel/pull/972 (for AOSP)
yeah I basically read it as qualcomm have bad after market support
zacharias.maladroit said:
and there's the (close to complete) bringup of msm8994 on 3.18 kernel sauce: https://github.com/sonyxperiadev/kernel/pull/972 (for AOSP)
Click to expand...
Click to collapse
I might have something interesting to build then and I can stop lounging around
any news for official aosp 8.0 release for z5?
Enviado desde mi SGP712 mediante Tapatalk
Months, and still couldn't get the lineageos 15.1. But maybe someone could do something for Lineageos 16.Reason is xperia z1 compact get 9.I'm sure it has difficulties but why not?
Because Z5 is dead , deeeead forever
Lineageos 15.1 is there for the Xperia Z. Hopefully the Z5 & older series to.
Or a port of a good time
Z5 already abandoned m8.
When I told that some of friends here told that '' no you wrong we will release 8 for Z5'', than same guy wrote here that he bought a new phone and he will not work for Z5 anymore
( https://forum.xda-developers.com/xperia-z5/general/oreo-experimental-rom-t3788575/page21 - #202 )
Development for z5 is more harder than z1c but development for x64 cpu have more problems. Cpu with x32 is more lighter
ı m so sad because of this when ı got this phone everybody was already gone and ı stıll have waranty till 1/9/19 ıhope it was alive
I'm planning to upgrade my phone this year. Either Z2 or Z5 series. But when I look into this forum, it seems that Z5 is a dead device. No sign of development, not even a custom oreo ROM.
This is so sad.
Buy than a OnePlus 7T or a Nokia 10.
This is my last Sony... NEVER a iPhone or Samsung.
SONY is History
Ohhhh... Why its "dead" , i dont understand , i saw the android 9 on a goddamn Xperia Z1 Compact (!) and i think its a nice idea to port this rom from there. It is LINEAGE 16 rom.
BrazzerHead said:
Ohhhh... Why its "dead" , i dont understand , i saw the android 9 on a goddamn Xperia Z1 Compact (!) and i think its a nice idea to port this rom from there. It is LINEAGE 16 rom.
Click to expand...
Click to collapse
That's not how custom rom development works
BrazzerHead said:
Ohhhh... Why its "dead" , i dont understand , i saw the android 9 on a goddamn Xperia Z1 Compact (!) and i think its a nice idea to port this rom from there. It is LINEAGE 16 rom.
Click to expand...
Click to collapse
Android 9 Port to your Z5 is not the problem, but you can not found an developer for this. There are to many devices on the market. Thats the problem and the z5 device is not the yellow from the egg with the drm problem and so on....
I try it to build an android 7.1.2 rom for my z5 device, but the tutorials and manuals are not the best from google and sony aosp tutorial.
I saw that Nexus 6P has a kinda simillar hardware and has a Android P custom roms, so , why we would not just take them and start porting? I am not much into that , but i know that for that actions we have to edit boot.img ramdisk and other things... so.....
aguilucho said:
Android 9 Port to your Z5 is not the problem, but you can not found an developer for this.
Click to expand...
Click to collapse
Hmmm, here is one!
I'm the one who built an experimental LineageOS 15.1 ROM for (my) z5c...
...and I'm trying to build a LineageOS 16.0 ROM too...
...but, unfortunately I failed with two crashes, that I can't fix:
While building this rom, first hiddenapi crashes with a signal 4 and, when commenting this out in the build process, profman crashes with the same error! This is because in both tools the "inserting in an unordered set" failed reproducible:
Code:
/home/bernhard/los16/out/host/linux-x86/bin/hiddenapi --light-greylist=/home/bernhard/los16/out/target/common/obj/PACKAGING/hiddenapi-light-greylist.txt --dark-greylist=/home/bernhard/los16/out/target/common/obj/PACKAGING/hiddenapi-dark-greylist.txt --blacklist=/home/bernhard/los16/out/target/common/obj/PACKAGING/hiddenapi-blacklist.txt --dex=/home/bernhard/los16/out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi/classes.dex
Illegal instruction (core dumped)
kern.log:
Oct 2 14:50:12 arbeit-lin-win kernel: [13163.700934] perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
Oct 2 14:51:44 arbeit-lin-win kernel: [13256.081375] do_trap: 10 callbacks suppressed
Oct 2 14:51:44 arbeit-lin-win kernel: [13256.081379] traps: hiddenapi[21659] trap invalid opcode ip:55cdbedec8e9 sp:7ffc0e81ccf0 error:0 in hiddenapi[55cdbede6000+c000]
Oct 2 14:54:11 arbeit-lin-win kernel: [13403.173464] traps: hiddenapi[23647] trap invalid opcode ip:559ce87c18e9 sp:7ffc3c297090 error:0 in hiddenapi[559ce87bb000+c000]
Berni-0815 said:
Hmmm, here is one!
I'm the one who built an experimental LineageOS 15.1 ROM for (my) z5c...
...and I'm trying to build a LineageOS 16.0 ROM too...
...but, unfortunately I failed with two crashes, that I can't fix:
While building this rom, first hiddenapi crashes with a signal 4 and, when commenting this out in the build process, profman crashes with the same error! This is because in both tools the "inserting in an unordered set" failed reproducible:
Code:
/home/bernhard/los16/out/host/linux-x86/bin/hiddenapi --light-greylist=/home/bernhard/los16/out/target/common/obj/PACKAGING/hiddenapi-light-greylist.txt --dark-greylist=/home/bernhard/los16/out/target/common/obj/PACKAGING/hiddenapi-dark-greylist.txt --blacklist=/home/bernhard/los16/out/target/common/obj/PACKAGING/hiddenapi-blacklist.txt --dex=/home/bernhard/los16/out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi/classes.dex
Illegal instruction (core dumped)
kern.log:
Oct 2 14:50:12 arbeit-lin-win kernel: [13163.700934] perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
Oct 2 14:51:44 arbeit-lin-win kernel: [13256.081375] do_trap: 10 callbacks suppressed
Oct 2 14:51:44 arbeit-lin-win kernel: [13256.081379] traps: hiddenapi[21659] trap invalid opcode ip:55cdbedec8e9 sp:7ffc0e81ccf0 error:0 in hiddenapi[55cdbede6000+c000]
Oct 2 14:54:11 arbeit-lin-win kernel: [13403.173464] traps: hiddenapi[23647] trap invalid opcode ip:559ce87c18e9 sp:7ffc3c297090 error:0 in hiddenapi[559ce87bb000+c000]
Click to expand...
Click to collapse
This is sooooo sad((( :crying:
BrazzerHead said:
This is sooooo sad((( :crying:
Click to expand...
Click to collapse
As I've seen an answer to my post, my 1st thought was: Yeah, a solution for the problems...
...but... :silly:
Berni-0815 said:
As I've seen an answer to my post, my 1st thought was: Yeah, a solution for the problems...
...but... :silly:
Click to expand...
Click to collapse
Is there any chance that this will be released? Also , is there any progress?
BrazzerHead said:
Also , is there any progress?
Click to expand...
Click to collapse
Unfortunately no.
Berni-0815 said:
Hmmm, here is one!
I'm the one who built an experimental LineageOS 15.1 ROM for (my) z5c...
...and I'm trying to build a LineageOS 16.0 ROM too...
...but, unfortunately I failed with two crashes, that I can't fix:
While building this rom, first hiddenapi crashes with a signal 4 and, when commenting this out in the build process, profman crashes with the same error! This is because in both tools the "inserting in an unordered set" failed reproducible:
Code:
/home/bernhard/los16/out/host/linux-x86/bin/hiddenapi --light-greylist=/home/bernhard/los16/out/target/common/obj/PACKAGING/hiddenapi-light-greylist.txt --dark-greylist=/home/bernhard/los16/out/target/common/obj/PACKAGING/hiddenapi-dark-greylist.txt --blacklist=/home/bernhard/los16/out/target/common/obj/PACKAGING/hiddenapi-blacklist.txt --dex=/home/bernhard/los16/out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi/classes.dex
Illegal instruction (core dumped)
kern.log:
Oct 2 14:50:12 arbeit-lin-win kernel: [13163.700934] perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
Oct 2 14:51:44 arbeit-lin-win kernel: [13256.081375] do_trap: 10 callbacks suppressed
Oct 2 14:51:44 arbeit-lin-win kernel: [13256.081379] traps: hiddenapi[21659] trap invalid opcode ip:55cdbedec8e9 sp:7ffc0e81ccf0 error:0 in hiddenapi[55cdbede6000+c000]
Oct 2 14:54:11 arbeit-lin-win kernel: [13403.173464] traps: hiddenapi[23647] trap invalid opcode ip:559ce87c18e9 sp:7ffc3c297090 error:0 in hiddenapi[559ce87bb000+c000]
Click to expand...
Click to collapse
You Can Ask This Developer . He Replies To Your Queries ASAP.. He Will Sure To Solve Your Problem..
Ask in This Thread : https://forum.xda-developers.com/android/general/guide-how-to-build-custom-roms-kernel-t3814251
BrazzerHead said:
Is there any chance that this will be released? Also , is there any progress?
Click to expand...
Click to collapse
The main problem (hiddenapi crashes) has been fixed.
Actually I'm building a rom for my z5c. We'll see... :fingers-crossed:
Berni-0815 said:
The main problem (hiddenapi crashes) has been fixed.
Actually I'm building a rom for my z5c. We'll see... :fingers-crossed:
Click to expand...
Click to collapse
This is fantastic, maybe I could help with the development, if you are OK, because my Z5 E6655 ,stock with Unlocked Bootloader, is not being my daily phone more. I think that we can play with it and I would install and test software you develope, I'm not a developer. I never unlock the bootloader for not loosing the good camera, that is important for me. I have pre-ordered a Nokia 9 PureView.
Then, for me the objective would be to have an stable working Android 9 pie in my Z5, keeping the 23mb camera, and with the best available camera app.
Please, let me know...