[ROM][SNAPSHOT][8.1.0] AOSP Oreo for Xperia SP
- Thread starter AdrianDC
- Start date
He's probably quite busy at the moment, but I would suggest you to stick around and wait. It will be worth it. Trust me on this.
AOSP 9.0 and AOSP Q are gonna be legendary.
Either way is worth sticking around his version of AOSP,which is so much better than the official lineage one.
Sound levels alone one this one makes the whole difference.
Here he does not have to comply with the super-strict, stupid lineage standards who keep the sound levels ,notifications, and ring abnormally low.
Which is why even though this version of AOSP is "only" 8.1 is still LIGHT YEARS AHEAD and WAY BETTER FOR DAILY USAGE than the official lineage.
I tell you what: this version is blazing fast without any of the gapps installed.
I have Waze and Sygic installed on it running happily BOTH AT THE SAME TIME, unlike that super-bloated crap of google maps that literary bring this phone to its knees trying to get a GPS fix using gapps to eat cycles and power overheating the phone.
EVERYTHING WORKS beautifully on this rom.
It's worth sticking around.
AOSP 9.0 and AOSP Q are gonna be legendary.
Either way is worth sticking around his version of AOSP,which is so much better than the official lineage one.
Sound levels alone one this one makes the whole difference.
Here he does not have to comply with the super-strict, stupid lineage standards who keep the sound levels ,notifications, and ring abnormally low.
Which is why even though this version of AOSP is "only" 8.1 is still LIGHT YEARS AHEAD and WAY BETTER FOR DAILY USAGE than the official lineage.
I tell you what: this version is blazing fast without any of the gapps installed.
I have Waze and Sygic installed on it running happily BOTH AT THE SAME TIME, unlike that super-bloated crap of google maps that literary bring this phone to its knees trying to get a GPS fix using gapps to eat cycles and power overheating the phone.
EVERYTHING WORKS beautifully on this rom.
It's worth sticking around.
I dreamed a dream in time gone by,
When hope was high
And life worth living.
I dreamed that AOSP would never die.
I dreamed that Adrian would keep on givin'.
When hope was high
And life worth living.
I dreamed that AOSP would never die.
I dreamed that Adrian would keep on givin'.
aosp-9* is out
aosp-9-20190422-huashan-adriandc.zip is uploaded gents,
GRAB it while is still hot.
Hurry now and get yours at a discounted price. Promo ends in 3...2...1....0
Oh, well, you've just missed it.
Neah, just joking..
Here you go-------> https://basketbuild.com/filedl/devs...n/AOSP-9/aosp-9-20190422-huashan-adriandc.zip
Thank you @AdrianDC.
aosp-9-20190422-huashan-adriandc.zip is uploaded gents,
GRAB it while is still hot.
Hurry now and get yours at a discounted price. Promo ends in 3...2...1....0
Oh, well, you've just missed it.
Neah, just joking..
Here you go-------> https://basketbuild.com/filedl/devs...n/AOSP-9/aosp-9-20190422-huashan-adriandc.zip
Thank you @AdrianDC.
A bit of feedback for aosp-9-20190422-huashan
Here's a bit of feedback for @AdrianDC.
Apps:
The keyboard seems to be locked on the preset languages and you can not add any other language dictionaries to it, making spellchecking impossible if you don't speak French English Italian Spanish or German, my better half is Romanian and she made me aware she can not use Romanian on the default keyboard.
Of course we can always install the official Gboard but i kinda liked this one, and it's ability to add dictionaries manually.
The recorder.
When trying to share the video created (video only without audio) i get the follwing error from whatsapp: "The file format is not supported"
I checked the resulting file and is an .mp4 indeed so in theory it should be compatible with whatsapp.
Camera App keeps crashing and force closing
Camera is actually OK now. Make sure is a fresh install not a dirty one.
On a fresh install with no extra mods and no gapps ,the camera seems to be working just fine when taking pictures.
When it comes about recording videos it seems to be able to record it just fine , the gallery app can see it but it can not play it. It just turns dark.
Sound Recorder
(com.android.soundrecorder) 254KB
Or better said, traces of it is still there although it's been a while since anybody saw it's icon on the desktop but for some reason, traces of it still gets compiled.
Gallery
When trying to play the resulting video from a recorder session i get i get the follwing error from the Gallery app : "Can't play this video"
Both when the resulting video has been recorded with the sound on or off.
I have installed from F-droid the Simple Gallery Pro (free version ) https://f-droid.org/repo/com.simplemobiletools.gallery.pro_243.apk
and that can't play it either so it's the recorder using a weird encoding format incompatible with both AOSP gallery codecs and the Simple tools Gallery.
Bootbridge
The old 2016 bootbrige is still compatible
Themes
Setting the device theme on dark does not seem to do anything (see the screenshot attached)
Developer options:
Display cutout option works just fine and is quite fun to play with for like 30 secunds.
The option called Advanced Reboot IS NOT THERE ANYMORE.
It was a very useful function although had to be enabled in Developer Options first.
Pressing the pressing volume up whilst the phone is rebooting still works but is a pain as my UP-DOWN button is kind of old and does not work that well anymore.
Sound:
We got sad news for sound. It's back again to the ridiculously low official Lineage levels.
I get some errors reference the speaker gain amp not being applied.
I guess the values have fallen back to the backup_gain: as apparently is the case with the gain in case of an error occurring during ramp. (see the attached screenshot)
Either way the sound levels are really low. Both notifications , media , and ring values.
I am back again at not being able to hear the notifications from phone on the street.
What made AOSP 8.1 really amazing it was those hard coded gain values which circumvented and bypassed the ridiculously low Lineage values and restrictions.
That was one of its best features.
The ability to make full use of the speaker and have very loud notifications/media/ring. To hear it whilst walking on the street.
Whomever tried to use the phone on a very busy street or driving with the windows open [because we're poor and we don't have AC's on our tiny ass Polos will understand what i mean.]
I will keep on playing with it and report any feedback. If you need like Logcats just let me know.
Anyways,
Once again,
Thank you @AdrianDC.
Here's a bit of feedback for @AdrianDC.
Apps:
The keyboard seems to be locked on the preset languages and you can not add any other language dictionaries to it, making spellchecking impossible if you don't speak French English Italian Spanish or German, my better half is Romanian and she made me aware she can not use Romanian on the default keyboard.
Of course we can always install the official Gboard but i kinda liked this one, and it's ability to add dictionaries manually.
The recorder.
When trying to share the video created (video only without audio) i get the follwing error from whatsapp: "The file format is not supported"
I checked the resulting file and is an .mp4 indeed so in theory it should be compatible with whatsapp.
Camera is actually OK now. Make sure is a fresh install not a dirty one.
On a fresh install with no extra mods and no gapps ,the camera seems to be working just fine when taking pictures.
When it comes about recording videos it seems to be able to record it just fine , the gallery app can see it but it can not play it. It just turns dark.
Sound Recorder
(com.android.soundrecorder) 254KB
Or better said, traces of it is still there although it's been a while since anybody saw it's icon on the desktop but for some reason, traces of it still gets compiled.
Gallery
When trying to play the resulting video from a recorder session i get i get the follwing error from the Gallery app : "Can't play this video"
Both when the resulting video has been recorded with the sound on or off.
I have installed from F-droid the Simple Gallery Pro (free version ) https://f-droid.org/repo/com.simplemobiletools.gallery.pro_243.apk
and that can't play it either so it's the recorder using a weird encoding format incompatible with both AOSP gallery codecs and the Simple tools Gallery.
Bootbridge
The old 2016 bootbrige is still compatible
Themes
Setting the device theme on dark does not seem to do anything (see the screenshot attached)
Developer options:
Display cutout option works just fine and is quite fun to play with for like 30 secunds.
The option called Advanced Reboot IS NOT THERE ANYMORE.
It was a very useful function although had to be enabled in Developer Options first.
Pressing the pressing volume up whilst the phone is rebooting still works but is a pain as my UP-DOWN button is kind of old and does not work that well anymore.
Sound:
We got sad news for sound. It's back again to the ridiculously low official Lineage levels.
I get some errors reference the speaker gain amp not being applied.
I guess the values have fallen back to the backup_gain: as apparently is the case with the gain in case of an error occurring during ramp. (see the attached screenshot)
Either way the sound levels are really low. Both notifications , media , and ring values.
I am back again at not being able to hear the notifications from phone on the street.
What made AOSP 8.1 really amazing it was those hard coded gain values which circumvented and bypassed the ridiculously low Lineage values and restrictions.
That was one of its best features.
The ability to make full use of the speaker and have very loud notifications/media/ring. To hear it whilst walking on the street.
Whomever tried to use the phone on a very busy street or driving with the windows open [because we're poor and we don't have AC's on our tiny ass Polos
will understand what i mean.]I will keep on playing with it and report any feedback. If you need like Logcats just let me know.
Anyways,
Once again,
Thank you @AdrianDC.
Attachments
Last edited:
GLONASS satellites are disabled ??
I just had a look around at it seems that on this rom GLONASS sats are disabled.
(Maybe @AdrianDC) could confirm that?
The GPS fix is done only with Navstar satellites and the GLONASS sats are being ignored.
My guess is that this is due to some hard coded commands in gps.h or gps_internal.h but since i am not a developer nor a programmer i could not confirm this.
Since I do not have GAPPS installed, I do get problems unique to this room I guess.
In all fairness the list of the problems is so small you can count it on the fingers of one hand.
BY THE WAY, HAS ANYBODY HAD SUDDEN REBOOTS with this rom? It happened to me an hour ago whilst driving back home and using Waze only.
The only app opened on the phone was Waze.
All of a sudden the phone rebooted. It got emotional for the next 10 minutes until i was able to pull over and stop.
So, yeah, until I modified /system/etc/gps.conf getting the GPS fix was a pain in the neck.
I am using Sygic and Waze for driving, and I always used to have issues with them losing GPS fix in London and around with the arrow going sideways most of the time.
@AdrianDC
Problem with London is , that living here is basically ****.
Tall buildings ,crappy infrastructure , small narrow streets and the signals bouncing everywhere getting absorbed by the walls .
We could really do with a GLONASS fix or if there is something we can enable or uncomment in the gps.conf please let us know.
Kind Regards
Gorilla
I just had a look around at it seems that on this rom GLONASS sats are disabled.
(Maybe @AdrianDC) could confirm that?
The GPS fix is done only with Navstar satellites and the GLONASS sats are being ignored.
My guess is that this is due to some hard coded commands in gps.h or gps_internal.h but since i am not a developer nor a programmer i could not confirm this.
Since I do not have GAPPS installed, I do get problems unique to this room I guess.
In all fairness the list of the problems is so small you can count it on the fingers of one hand.
BY THE WAY, HAS ANYBODY HAD SUDDEN REBOOTS with this rom? It happened to me an hour ago whilst driving back home and using Waze only.
The only app opened on the phone was Waze.
All of a sudden the phone rebooted. It got emotional for the next 10 minutes until i was able to pull over and stop.
So, yeah, until I modified /system/etc/gps.conf getting the GPS fix was a pain in the neck.
I am using Sygic and Waze for driving, and I always used to have issues with them losing GPS fix in London and around with the arrow going sideways most of the time.
@AdrianDC
Problem with London is , that living here is basically ****.
Tall buildings ,crappy infrastructure , small narrow streets and the signals bouncing everywhere getting absorbed by the walls .
We could really do with a GLONASS fix or if there is something we can enable or uncomment in the gps.conf please let us know.
Kind Regards
Gorilla
Attachments
Some more feedback for aosp-9-20190422-huashan
Right,
So I've been playing with it for the last few days and I have noticed few things.
As always the only extra addition to this room is the @AdrianDC bootbridge.
1. The force closings. I get random force closings when I am using Waze, I suspect is because of the aggressive low memory settings , but that's just an educated guess.
2.The reboot The reboot is somewhat weird, if we can describe it that way.
It looks like the phone is experiencing mid-boot crashing. The boot sequence starts normally, it passes the Sony logo and then the Android logo appears...
It hangs around for a while looking for something ,then as the crash begins you can see the colours of the Android logo slowly changing turning from their usual white into shades of grey,brown, red,red-ish and eventually fading out.
Then the boot sequence starts again. Sometimes it loops like that ,even three times until it gets to the final screen.
3. The new HARD CODED dependencies
So in order to understand this better it looks like something borrowed straight from Debian or Ubuntu.
Each Debian package is assigned a priority by the distribution maintainers, as an aid to the package management system. Required: packages that are necessary for the proper functioning of the system.Important,Standard,Optional,Extra and so on...
The Debian package system has a range of package "dependencies" which are designed to indicate (in a single flag) the level at which Program A can operate independently of the existence of Program B on a given system:Depends, Recommends, Suggests, Conflicts,and so on.
And here's the rub, for the last good 8 years the devs on Ubuntu have gone nuts and for almost every package they install on the system they use the flag DEPENDS. They don't want people touching their OS. And that's how you up in the "Dependency hell". You uninstall a seemingly unrelated package and the whole system crashes. That's what we in London call "a **** move".
Trying to uninstall stuff on Ubuntu these days .... Well, it gets emotional because every package you try to eliminate will have the flag "Depends" on it instead of suggest or recommands . Long story short, I just noticed the same trend on this rom.
So, basically on every install I had on AOSP untill now I have used SD Maid to get rid of the unused packages.
Most of the time I even delete 38 of them. I only use and install apps that don't need GAPPS to work, don't require them and are happy to work without.
F-droid is more than enough for my needs . For the rest I use Raccoon to download the APKs and side-load them.So, yeah... I delete the unused stuff. It was never a problem until now.
One of the first things to go on my install, is the useless search apk (the one that looks like a magnifying glass) followed by the radio and music apps.
For music ,video and all that I actually have Mixplorer by Hootan Parsa ( https://mixplorer.com/ )
The list of amazing things that baby can do is waaaay too long to type it here, you can have a look at the website yourselves , but among other things it comes with the VLC codecs meaning it can play all kind of weird media formats including FLAC, ALAC codecs (if you're one of those guys who like the incredible quality of those formats)
So, yeah the music and the radio app get deleted as well.Afterwards I keep going.Never had a problem until yesterday.
Yesterday removing ONLY the above mentioned apps GOT THE CAMERA TO CRASH!
Looks like somebody decided to modify things.
I will reinstall the operating system again and try to narrow it down to see which of the three apps causes the camera to crash but I've got a feeling that somebody has gone full on "Ubuntu" playing with the dependencies flags.
Right,
So I've been playing with it for the last few days and I have noticed few things.
As always the only extra addition to this room is the @AdrianDC bootbridge.
1. The force closings. I get random force closings when I am using Waze, I suspect is because of the aggressive low memory settings , but that's just an educated guess.
2.The reboot The reboot is somewhat weird, if we can describe it that way.
It looks like the phone is experiencing mid-boot crashing. The boot sequence starts normally, it passes the Sony logo and then the Android logo appears...
It hangs around for a while looking for something ,then as the crash begins you can see the colours of the Android logo slowly changing turning from their usual white into shades of grey,brown, red,red-ish and eventually fading out.
Then the boot sequence starts again. Sometimes it loops like that ,even three times until it gets to the final screen.
3. The new HARD CODED dependencies
So in order to understand this better it looks like something borrowed straight from Debian or Ubuntu.
Each Debian package is assigned a priority by the distribution maintainers, as an aid to the package management system. Required: packages that are necessary for the proper functioning of the system.Important,Standard,Optional,Extra and so on...
The Debian package system has a range of package "dependencies" which are designed to indicate (in a single flag) the level at which Program A can operate independently of the existence of Program B on a given system:Depends, Recommends, Suggests, Conflicts,and so on.
And here's the rub, for the last good 8 years the devs on Ubuntu have gone nuts and for almost every package they install on the system they use the flag DEPENDS. They don't want people touching their OS. And that's how you up in the "Dependency hell". You uninstall a seemingly unrelated package and the whole system crashes. That's what we in London call "a **** move".
Trying to uninstall stuff on Ubuntu these days .... Well, it gets emotional because every package you try to eliminate will have the flag "Depends" on it instead of suggest or recommands . Long story short, I just noticed the same trend on this rom.
So, basically on every install I had on AOSP untill now I have used SD Maid to get rid of the unused packages.
Most of the time I even delete 38 of them. I only use and install apps that don't need GAPPS to work, don't require them and are happy to work without.
F-droid is more than enough for my needs . For the rest I use Raccoon to download the APKs and side-load them.So, yeah... I delete the unused stuff. It was never a problem until now.
One of the first things to go on my install, is the useless search apk (the one that looks like a magnifying glass) followed by the radio and music apps.
For music ,video and all that I actually have Mixplorer by Hootan Parsa ( https://mixplorer.com/ )
The list of amazing things that baby can do is waaaay too long to type it here, you can have a look at the website yourselves , but among other things it comes with the VLC codecs meaning it can play all kind of weird media formats including FLAC, ALAC codecs (if you're one of those guys who like the incredible quality of those formats)
So, yeah the music and the radio app get deleted as well.Afterwards I keep going.Never had a problem until yesterday.
Yesterday removing ONLY the above mentioned apps GOT THE CAMERA TO CRASH!
Looks like somebody decided to modify things.
I will reinstall the operating system again and try to narrow it down to see which of the three apps causes the camera to crash but I've got a feeling that somebody has gone full on "Ubuntu" playing with the dependencies flags.
Last edited:
Yes reboots are normal even on my build.
Using kernel from the last working build works OK but isn't recommended since its a huge hack and system may be unstable.
Using kernel from the last working build works OK but isn't recommended since its a huge hack and system may be unstable.
It's all good.
After all, this is only the first release and is the equivalent of an Alpha release.
At this stage it works wonderfully for what it is .Give it an other 3 months and we're gonna have the same impressively stable, nicely working rom , as the last AOSP 8.1.
I got curious though, why are not the GLONASS satellites being used in the fix?
I remember reading somewhere that this was allegedly done to save battery power and that by design they were only used when when a fix could not be obtained with the GPS constellation.
At least that was the explanation given by some Sony moderator back in the day but that was for the stock rom.
And in the stock rom they were actually used from time to time.
Especially when I was going through those parts of London with tall buildings and weird signal bouncing.
This room actually does not uses them, sees them just fine but kind of them ignores them when getting the fix.
All this leads to Waze telling you sometimes to "Pull right" after you passed the junction.
All the extra settings in "Developers" and "Advanced" and scanning for wifi and bluetooth enabled.
After all, this is only the first release and is the equivalent of an Alpha release.
At this stage it works wonderfully for what it is .Give it an other 3 months and we're gonna have the same impressively stable, nicely working rom , as the last AOSP 8.1.
I got curious though, why are not the GLONASS satellites being used in the fix?
I remember reading somewhere that this was allegedly done to save battery power and that by design they were only used when when a fix could not be obtained with the GPS constellation.
At least that was the explanation given by some Sony moderator back in the day but that was for the stock rom.
And in the stock rom they were actually used from time to time.
Especially when I was going through those parts of London with tall buildings and weird signal bouncing.
This room actually does not uses them, sees them just fine but kind of them ignores them when getting the fix.
All this leads to Waze telling you sometimes to "Pull right" after you passed the junction.
All the extra settings in "Developers" and "Advanced" and scanning for wifi and bluetooth enabled.
@AdrianDC - thank you both for aosp-9-20190422 and lineage-16.0-20190422 I've just realized you did it silently and din't tell a word!!! Will try them soon!
@gorillanobka - thnx for such extensive and deep test! Do you use AOSP or LineageOS on a daily basis? Do you face any problems when roaming? I mean manual network selection - it was broken in all Oreo builds as far as I know.
I've just realized you did it silently and din't tell a word!!! Will try them soon!@gorillanobka - thnx for such extensive and deep test! Do you use AOSP or LineageOS on a daily basis? Do you face any problems when roaming? I mean manual network selection - it was broken in all Oreo builds as far as I know.
Last edited:
I do use AOSP as my daily driver. I never had the chance to use it on roaming (student life) but one day maybe...
No, I haven't flashed twrp to the fota partition. I don't understand how I must do it.
I read the "TWRP thread", but I I don't understand what and how I must do.
With Redmi phones and Miui, I have done it many times.
But with Xperia SP and the guides here at XDA, I can't figure it out.
Well, try doing the steps in the TWRP-thread, under HOW TO INSTALL EASILY TO FOTA :. I'm affraid I can't help you more than that.
Have you tried aosp-9 yet @globe79 ? @AdrianDC seems to have uploaded it, but no mention about it yet(?). I'd like to give it a shot, too.
@AdrianDC - thank you both for aosp-9-20190422 and lineage-16.0-20190422
Have you tried aosp-9 yet @globe79 ? @AdrianDC seems to have uploaded it, but no mention about it yet(?). I'd like to give it a shot, too.
Last edited:
Thanks.
So, I flashed TWRP using this guide: https://hoanganhduc.github.io/misc/linux/2018/my-first-experience-with-android-phones/
I enterd TWRP, I copied AOSP ROM to the phone and then flashed it.
Phone rebooted, stuck on android logo for some minutes and then phone entered Android Recovery and gave me 2 options.
Try again or factory reset. I chose factory reset and an error message appeared. I pressed power button, phone closed and when I reopened it, process repeated.
I chose "try again" this time. Same result.
I reset phone by pressing the reset button on the back of the phone, then entered fastboot. I used "fastboot devices" command and now message "PSDN:YT910S24YZ&ZLP fastboot" appears.
What can I do?
Last edited:
@Aurumnus
First of all, I wonder why don't you follow Adrian's instructions?
And 2nd, did you update your device to the latest Sony stock firmware (btw, it's the 12.1.A.1.207 fw) before your try to switch to AOSP? If not, do that before proceeding here.
The next (TWRP) thing is, after fastboot flash boot (Adrian's latest) twrp-3.2.3-20180810-boot-huashan.img and entering it, you have to flash the twrp-3.2.3-20180810-fota-huashan.zip (which you have to place onto your external or internal sd of your Huashan, ofc) and then reboot into recovery. Not till then flash the AOSP rom and GApps. The links to the mentioned TWRP files you'lll find in Adrian's appropriate TWRP-thread in the op in the "DEVELOPMENT DOWNLOADS FOR HUASHAN" section (take the latest [3.2.3] ones).
And if you want root, have a look in the "Q&A - FAQ" section of the op of this thread!
And last but not least a little hint: Read the op exactly, maybe twice or more - then you'll succeed
First of all, I wonder why don't you follow Adrian's instructions?
And 2nd, did you update your device to the latest Sony stock firmware (btw, it's the 12.1.A.1.207 fw) before your try to switch to AOSP? If not, do that before proceeding here.
The next (TWRP) thing is, after fastboot flash boot (Adrian's latest) twrp-3.2.3-20180810-boot-huashan.img and entering it, you have to flash the twrp-3.2.3-20180810-fota-huashan.zip (which you have to place onto your external or internal sd of your Huashan, ofc) and then reboot into recovery. Not till then flash the AOSP rom and GApps. The links to the mentioned TWRP files you'lll find in Adrian's appropriate TWRP-thread in the op in the "DEVELOPMENT DOWNLOADS FOR HUASHAN" section (take the latest [3.2.3] ones).
And if you want root, have a look in the "Q&A - FAQ" section of the op of this thread!
And last but not least a little hint: Read the op exactly, maybe twice or more - then you'll succeed
Last edited:
@nuremberg
Thanks for your reply.
Yes, I had latest Sony stock firmware, the one from COSMOTE (I'm pretty sure it's the worst implementation of stock SONY firmware for this phone).
It took me a lot of time but I managed to found it, so I can try to flash it again.
I believe this clarifies a lot of things for me. I only did the first flash.
I've read the instructions many times.
The problem is with my brain. I can do things I see in pictures or videos, but it's quite difficult for me with only written instructions.
EDIT 1: I can't flash stock firmware with flashtool. Phone disconnects from flashmode a minute after connecting.
EDIT 2: I opened a new thread asking for help, don't want to clutter this thread, since it's for AOSP ROM and not general problem solving.
Thanks for your reply.
Yes, I had latest Sony stock firmware, the one from COSMOTE (I'm pretty sure it's the worst implementation of stock SONY firmware for this phone).
It took me a lot of time but I managed to found it, so I can try to flash it again.
I believe this clarifies a lot of things for me. I only did the first flash.
And last but not least a little hint: Read the op exactly, maybe twice or more - then you'll succeed
I've read the instructions many times.
The problem is with my brain. I can do things I see in pictures or videos, but it's quite difficult for me with only written instructions.
EDIT 1: I can't flash stock firmware with flashtool. Phone disconnects from flashmode a minute after connecting.
EDIT 2: I opened a new thread asking for help, don't want to clutter this thread, since it's for AOSP ROM and not general problem solving.
Last edited:
@Aurumnus
Go to this thread page. Sony is not Samsung nor Motorola - you can get permanent TWRP via FOTA method only, you can't update eg. Magisk as easily as on other devices.
I was using "Flashtool 0.9.25.0" for flashing TWRP img (not zip) as boot image - TWRP overwriting system kernel. It is not permanent as system overwrites it during normal flash, but is useful for debugging. You can flash TWRP that way and prepare all zips on your SD card to flash at once (I flash lineageos.zip, boot bridge modified with magisk, open gapps pico and fota TWRP). Its unlikely to brick Xperia SP! Never give up!
@LaRazón
I had no time this weekend - sorry. I'll try it soon! I'd like to update TWRP to 3.3.0.0 at once.
Go to this thread page. Sony is not Samsung nor Motorola - you can get permanent TWRP via FOTA method only, you can't update eg. Magisk as easily as on other devices.
I was using "Flashtool 0.9.25.0" for flashing TWRP img (not zip) as boot image - TWRP overwriting system kernel. It is not permanent as system overwrites it during normal flash, but is useful for debugging. You can flash TWRP that way and prepare all zips on your SD card to flash at once (I flash lineageos.zip, boot bridge modified with magisk, open gapps pico and fota TWRP). Its unlikely to brick Xperia SP! Never give up!
@LaRazón
I had no time this weekend - sorry. I'll try it soon! I'd like to update TWRP to 3.3.0.0 at once.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
135
Code:#include <std_disclaimer.h> /* * Your warranty is now void. * * I am 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 me for messing up your device, I will laugh at you. */
About the release
My Android 8.0 bring-up started in April with my AOSP Master project.
Master being the mainline public Android development, it helped getting
most of the hardware requirements for the next Android release prepared
and ready for the evolution along the weeks. Though 8.0.0 introduced
more hardware changes and improvements, it was ready for about 75% of the needs.
Full details about the initial boot are explained here : #post73504552
Downloads Links
AOSP 8.x Oreo (Unlocked Bootloader) :
Xperia SP (Huashan) - 8.1.0 / 8.0.0 : https://mega.nz/#F!aotknK6I!H9kNGqNSbUPYbKRdF-EeBg
Google Applications (optional) :
MindTheGapps : https://androidfilehost.com/?w=files&flid=170282 (Use packages for ARM, Android 8.x)
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 8.x, Micro)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recommended Recovery (optional) :
TWRP 3.x : http://forum.xda-developers.com/xperia-sp/orig-development/-t3309938
Configure the default Low-RAM features (optional) :
Low-RAM Property Patcher : http://forum.xda-developers.com/-/-t3737373
Informations and references :
Kernel CVEs : Security patches status https://cve.lineageos.org/android_kernel_sony_msm8960t
About AOSP : Repositories available on https://android.googlesource.com/
Flashing and updating
AOSP clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Install TWRP Recovery to the FOTA partition (Read the TWRP thread)
- (Optional) Wipe the data & cache (Backup to make sure not to lose data)
- Flash the AOSP ROM zip from recovery
- (Optional) Flash a GApps package to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
AOSP update / upgrade :
- (Information) Do not wipe anything unless you want to
- Flash the latest AOSP ROM zip from recovery
- (Optional) Flash a GApps package if you want to, otherwise preserved.
- (Optional) Every additional zip you want to flash
- Reboot
About the builds
Development project : https://github.com/AdrianDC/aosp_development_sony8960_o_mr1
Device tree : https://github.com/AdrianDC/android_device_sony_huashan
Kernel sources : https://github.com/AdrianDC/android_kernel_sony_msm8960t
Vendor blobs : https://github.com/TheMuppets/proprietary_vendor_sony
Issues and reports
- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example
Q&A - FAQ
Q : Is root access included into AOSP ?
A : No but you can now root with my Boot Bridge and a superuser tool.
Q : Is the ROM suited for daily usage ?
A : Yes. Check the list below to decide for yourself.
Q : Where can I change the Quick Tiles and Status Bar ?
A : Long press the Settings icon in the notifications drawer.
> You will have access to the SystemUI Tuner from Marshmallow.
Q : When USB is connected to a computer, I can't access the storage ?
A : The phone is in charge-only mode by default (since Android Nougat),
> due to a stronger security logic regarding unauthorised data access.
> Swipe down the notifications and change the USB mode.
Q : [Oreo] Downloaded files can't be opened directly
A : Normal issue common to all devices, yet to be fixed.
> For now, use "Show internal storage" and open the files directly.
Q : [Oreo] Clean install with OpenGApps - Google services force closes
A : OpenGApps Oreo is not yet finished and stable.
> Ignore the FCs and wait until the Setup Wizard configuration is done.
AOSP available for Xperia Huashan also thanks to :
- Google AOSP
- The LineageOS Team
- CodeAurora Forums
- The CyanogenMod Team
XDA:DevDB Information
AOSP Oreo 8.1, ROM for the Sony Xperia SP
Contributors
AdrianDC
Source Code: https://android.googlesource.com/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Snapshot
Created 2017-09-01
Last Updated 2020-08-1579FEATURES AND ISSUES
Code:- Boot : Ok - GApps : OpenGApps Micro recommended - Partitions (Data, Cache) : Ext4 and F2FS supported - Bluetooth : Ok - WiFi : Ok - WiFi Hotspot : Ok - RIL - Phone - Data : Ok - GPS : Ok - Camera : Ok - Camcorder : Ok - Lights : Ok - MicroSD : Ok - Accelerometer : Ok - Compass : Ok - Gyroscope : Ok - AOSP sensors : Ok - Touchscreen : Ok - FM Radio : Ok - Vibrator : Ok - Microphone : Ok - Audio & music : Ok - Bluetooth audio : Ok - NFC : Ok - Kernel : Ok - Graphics : Ok - 3D Rendering : Ok - Clock : Ok - DRM : Ok - Offline Charging : Ok - USB : Ok - USB OTG : Ok - Encryption : Ok - SEPolicies : Enforcing
ALSO WORKING ON SONY HUASHAN
- Music Lights Effects implementation fully working
- Presentation of the features : https://forum.xda-developers.com/showpost.php?p=73049970&postcount=399
- YouTube Presentation : https://www.youtube.com/watch?v=GHk__DhyL60
IMPORTANT FEATURES TO KNOW
- Boot sequence : Once the LEDs light up :
- Press Volume - to open AOSP Recovery,
- Press Volume + to open the FOTA recovery (TWRP usually) if available - Powered-off alarm : When you have set an alarm
- If you power down the device, it will wake automatically 5 minutes before
- If you let the device charge offline, it will automatically reboot 5 minutes before - Gestures : Events like hand-wave and pocket removal can be enabled in the Settings
- Force reboot : You can reset the device by holding Power and Volume+ 5 seconds
59Changes log
- 21/12 : Upgrade stable release on Android 8.1.0_r52 December
>>> General update against the initial LineageOS 15.1 official release
>>> Manual networks selection resolved
- 05/09 : Upgrade stable release on Android 8.1.0_r46 September
>>> Camera binaries improvements developed for AOSP P to resolve the crash log spam
- 15/08 : Upgrade stable release on Android 8.1.0_r43 August
>>> Multiple Kernel CVE patches and improvements
>>> Media volume now has 25 steps instead of 15, call volume 7 instead of 5
>>> Improvements to trigger the bootanimation earlier on boot
>>> Status bar icons tints resolved: Battery percentage, VPN
- 06/06 : Upgrade stable release on Android 8.1.0_r30 June
>>> CellularTile now has a detail view for Mobile Data
>>> Trebuchet Launcher improvements:
----- Predictive apps switch between day / night / headphones
- 13/05 : Upgrade stable release on Android 8.1.0_r26 May
>>> Maintenance upgrade release
- 06/05 : Update stable release on Android 8.1.0_r20 April
>>> My implementation of FBNotifier backlight in the LEDs kernel driver
----- Resolves backlight always on issues in offline charger
----- Proper low-level solution avoiding deprecated brightness controls
>>> Offline charger boot will reboot the device rather than direct boot
----- Restored the default AOSP behaviour for better support
----- Improves usability for MultiROM users (access to secondary ROMs)
>>> Offline charger LED battery indicator brought back
- 22/04 : Upgrade stable release on Android 8.1.0_r20 April
>>> Evolutions from frameworks/av to support legacy HAL1 Camcorder properly
----- Final solution found with Milos Ratkovic
----- Camcorder running fine on 720p and 1080p
>>> DocumentsUI (Files) showing internal storage by default
>>> Logcat's Diag_Lib spam resolved and silenced
>>> Sources improvements and cleanups related to AOSP P-DP1
>>> Kernel binder 64 bits API
>>> My backuptool in system evolution for future AOSP portability (for P)
----- Upgrades to this release will make the transition, do not jump over it
Recent branches commits
- Devices + common projects: https://github.com/AdrianDC/aosp_development_sony8960_o_mr1/branches/all
Original AOSP 8.0 sources with following relevant additions- Huashan device tree, kernel and vendor
- Bionic: Support for SHIMs (Camera)
- Build: Backup tool full support (GApps)
- NFC: Proper support & removed log spam
- Toybox: Support for init_sony boot selection
- AV: Camera support for Oreo
- AV: Initial camcorder partial support
- Camera2: Fixes for wrongly rotated photos and improvements
- UI: Various efficiency improvements and fixes
- Telephony: Support for older RIL layers
- Audio: 8960 adapted HAL and FM support
- FM: Fully implemented with AOSP FM Radio
- Music: Minor fix to permissions
- Settings: Minor visual rendering improvements
- Healthd: Support for Huashan offline charger
- Core: Disabled flash_recovery service from AOSP
- Sepolicies: Minimal changes and fully enforced ROM
Current local manifestCode:<?xml version="1.0" encoding="UTF-8"?> <!-- [url]https://android.googlesource.com/platform/manifest[/url] --> <manifest> <!-- See [url]https://github.com/AdrianDC/aosp_development_sony8960_o_mr1[/url] --> </manifest>50About the initial public release - 01/09/2017
- I use it as daily since July on Huashan (SP) and Mint (T)
- For now, Camera is removed on purpose as I'm working on it. The initialization fails in the middle
- Bluetooth worked up to July, and since then the list is empty due to timeouts. Being looked at
- Binding with already paired Bluetooth devices like car radio should work but rare user-unfriendly conditions for now
- Installs and works properly with MultiROM current release
35Android Oreo 8.1 - December 8th release for Sony Huashan / Sony Blue devices
>>> Fully rebased and updated projects on the initial Android 8.1 release
>>> Upgrades from 8.0 to 8.1 allowed through backuptool for GApps
>>> Clean installs of OpenGApps zips require install script changes to 8.1 and API 27
>>> Sony Huashan built with normal Android Oreo configurations, Sony Blue with Android Oreo Go
>>> One important difference with Android Go : Multitasking UI is flat on Go. Check Huashan and Blue screenshots
About GApps on AOSP 8.1
>>> I added support in backuptool for "8." instead of "8.0" or "8.1", hence upgrades should not be breaking
>>> Clean installs or flashing updated OpenGApps 8.0 require changes in their zip / installer.sh:
Code:req_android_sdk="27"; req_android_version="8.1";
