yashsingh1/xdaforums huggingface dataset:
[Sony Xperia T, TL, TX, V] AdrianDC:
Reserved

Changes log

17/08 : Initial public release on Android 9.0.0_r46 August

2018: Initial AOSP 9 ports, internal bringup

>>> Kept private for development purposes

Recent branches commits

Devices + common projects: https://github.com/AdrianDC/aosp_development_sony8960_p/branches/all

About Sony Blue devices

You can cross-reference with Huashan: http://xdaforums.com/-/-t3958464

I work on both platforms in parallel as they are now equal in terms of functionality and stability

Original AOSP 9 sources with following relevant additions

Blue devices trees, 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 Pie

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 manifest

<?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_p[/url] -->

</manifest>
[Sony Xperia T, TL, TX, V] MichaBit:
Runs perfectly :good: thank you [MENTION=2233641]AdrianDC[/MENTION].
[Sony Xperia T, TL, TX, V] Soul_Gamerz:
Hi [MENTION=2233641]AdrianDC[/MENTION], are you planning to do an Android Go version for this devices? If so then it would be great!
[Sony Xperia T, TL, TX, V] xperanto:
He already did in some way. If you define Android Go as "The Android Go operating system is based on the regular version of Android but it’s optimized to run on smartphones with 512 MB to 1 GB of RAM", adriandc already povided a patch based on it with the Low-RAM Property Patcher, as stated above.

When you follow the link https://xdaforums.com/android/software-hacking/mod-low-ram-property-patcher-android-t3737373 you will find the following statement:

and

As adrian mentioned the low-ram patch in this Pie-ROM description, it should work for this release, too, not only for Oreo. (s.Edit)

The solution provided by adriandc with a patch is even better than a whole standalone ROM, because you can switch it on or off and in the end it is up to the user if he wants to use it or not.

The idea behind it is very well done by adriandc.

To answer your question: He already did!

Edit, clarification:

As stated above: "Configure the default Low-RAM features" means, that it is already enable by default. The low-ram-enabler is only needed to reenable it, if you used the disable-patch, as stated in this thread

https://xdaforums.com/showpost.php?p=80492509&postcount=15
[Sony Xperia T, TL, TX, V] MichaBit:
Where can I find the last update from 2019-10-13? :confused:

There is no link or download available.
[Sony Xperia T, TL, TX, V] theunlucky:
Hi,

I wanted to give my Xperia T the joy of PIe, but am encountering a few issues:

coming from 8.1 (also AOSP, without Gapps), i did

- install the newest TWRP-image (3.3.1-0, came from 3.3.0-0)

- deleted dalvik, data and cache,

...after that, TWRP couldn't read from ext. SD-card anymore.

booted up the old system, copied the new image and gapps to the internal storage.

- redone the dalvik/data/cache-wipe

- installed AOSP-image, installed Gapps and the low-ram-thingy.

...after reboot, the assistant starts up, lets me connect to my WLAN (i get asked for the sim-pin), then comes the "search for updates"-dialog, where it stucks (got it running for 60 minutes)

...i connected to "my" wlan, passphrase's correct, the XT gets an IP, all as it should be.

redone the whole process with just AOSP (to get the option to upload the lineage-image to the internal storage, as there's still no ext. sd-card available)

Is there a way to skip the update-search? (can't use UMTS, as i'm running a prepaid-card)

(if not: how to get the lineage-image on the phone? can connect the cable and it starts charging the battery, but I need to set it to "transfer files" which isn't possible as the assistant doesn't let me access the info-bar - system is responding when trying to change volume)

Edit: was able to activate the mtp-mode in TWRP, giving lineageOS a shot right now, will update if solved or not

Edit2: was able to install lineageOS (and mindthegapps) and set it up without error...

...is above mentioned issue common? how could i switch to AOSP without re-encountering the setup-problem?
[Sony Xperia T, TL, TX, V] xperanto:
On AOSP of Xperia SP huashan, some users encountered the same issue.

The solution as mentioned in this thread https://xdaforums.com/xperia-sp/orig-development/rom-aosp-pie-xperia-sp-t3958464 by user fsw_informatrix is simply to remove the SIM-card first, and to not connect to wlan during the first setup.

Also make sure to use mindthegapps and not opengapps. Hope this helps.
[Sony Xperia T, TL, TX, V] theunlucky:
Well I had the Sim-Card in, but I tried to NOT configure WLAN - it was mandatory (assistant starts, asks for either WLAN or UMTS, there's no way to work around that)

Where's the difference between mindthegapps and opengapps?
[Sony Xperia T, TL, TX, V] xperanto:
Again, please read the thread from above, espacially this post

https://xdaforums.com/showpost.php?p=80377565&postcount=10

Mindthegapp and Opengapp is also discussed somewhere in the thead.
[Sony Xperia T, TL, TX, V] eternalcookie:
I used mindthegapps instead of opengaps and the sign in problem went away :good:

But i have a problem; the phone doesn't stay off after shutdown and turns back on. I have flashed latest TWRP twice via fastboot but the problem is still there. However if i connect the phone to charger right after shut down it will stay off and recharge :confused:

I used Nova launcher instead of the built-in UI and the phone runs fine and smooth. Unfortunately Xperia V doesn't support notification access for external apps and I'm looking for a workaround for that too. In general, i like the OS and the user experience is good so I'm going to keep it. Props to the dev :)
[Sony Xperia T, TL, TX, V] skytorch:
It there future releases plan for AOSP version? Or will not release anymore?
[Sony Xperia T, TL, TX, V] gnewer:
I really appreciate the work done by AdrianDC to keep xperia v alive. I am running this ROM for a week now after using official jelly bean by Sony for years.

Most of the time it works good without problem and I want to keep it for daily usage.

But I encountered some bugs :

1. Shut down function don't work. It actually restarts after 5 or 10 seconds of black screen.

2.some times during some medium to heavy work the screen freezes and the phone restarts itself.

3.some times during some medium to heavy work the CPU temperature goes up to 65 Celsius and the phone shut down.

4.battery usage and charging time increased comparing to last official ROM . an important notice is that I first installed gapps and the battery drain was a disaster and it showed charging takes 22 hours to complete ! But then I flashed and reinstalled ROM with mindtheapps and it is far better and charging takes 2.5 hours to complete.

And with full usage it goes empty after 3 hours. Poor 1700 battery after all.

5.in telegram and wattsapp videos won't play in app. I should use 3rd app to open video via files manager .
[Sony Xperia T, TL, TX, V] skytorch:
Is anyone know what is the build instruction for this AOSP version?
[Xperia SP Original Android Development] AdrianDC:
Reserved

FEATURES AND ISSUES

- 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 : Not tested yet
- SEPolicies : Permissive, enforcing is a work in progress

ALSO WORKING ON SONY HUASHAN

​

Music Lights Effects implementation fully working

Presentation of the features : https://xdaforums.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
[Xperia SP Original Android Development] AdrianDC:
Reserved

Changes log

17/08 : Initial public release on Android 9.0.0_r46 August

2018: Initial AOSP 9 ports, internal bringup

>>> Kept private for development purposes

Recent branches commits

Devices + common projects: https://github.com/AdrianDC/aosp_development_sony8960_p/branches/all

Original AOSP 9 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 Pie

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 manifest

<?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_p[/url] -->

</manifest>
[Xperia SP Original Android Development] globe79:
I woke up in the morning and decided for a short walk around the internet - and to my surprise I found new builds of both AOSP and Lineage suitable for my favourite backup phone :) Thank you so much [MENTION=2233641]AdrianDC[/MENTION] - I know it is harder to withstand people than hardware ;)
[Xperia SP Original Android Development] ze7zez:
Thank you for LTS for our Xperia SP. :good:

Is it possible for miracast to work in LOS 16 as it does in LOS 15.1?
[Xperia SP Original Android Development] AdrianDC:
Sadly Google has removed support for Miracast in AOSP P.

An attempt to revive the abandoned code for LineageOS 16.0 is ongoing and on review.
[Xperia SP Original Android Development] jurko217:
Experience, first stable build

Hello, i want to share my critic experience with you and this rom.

(C5303, Clean flash, Data and cache FS changed to F2FS, without gapps, magisk)

1. Music - i had good experience, led controls work good, but after day of using phone and some restarts, it shows only 2 from my 600 songs.

So i installed Sony music app, no difference. Cleared data, cache for both apps, but still no difference.

2. AOSP Browser - After some succesful launches, FC every launch time, other browsers OK

3. After day usage, system started drain battery as fck...

4. At same time as battery and music, system going slowly

5. And biggest issue - phone cannot turn off - it restarts. So i have 2 go 2 recovery and turn off here.

I have been without gapps, because i wanted pure system, so i installed yalp store (some 404 client errors, but logged succesfully) and with magisk 19.3 bootbridge (Modules: V4A 2.7.1.0, Audio compatibility and modification patches, Pixelarity, SF-Font, Busybox, all modules works flawlessly)

I must give big + and thanks for developers, because 6 y.o. phone still breaths for today with the new system, but stable work must have itself finality. Check this things on your phones and please fix it for stable, pure AOSP experience.

And add please full dark mode.

Edit:

I have tried new Lineage 16 and same issues with different music players, browser and newly - gallery doesnt show anything and camera not working.
[Xperia SP Original Android Development] ze7zez:
For amoled display only. Huashan doesn't have it.
[Xperia SP Original Android Development] ze7zez:
sorry, another thread
[Xperia SP Original Android Development] fsw_informatrix:
Hi,

First of all, I want to thank again AdrianDC for bringing Android Pie on our lovely SP (that I'm keeping as a backup phone and can't let it go), man, you just rock :)

But I'm really surprised not to read anything here about the setup problems I've encountered, because for me, it was Hell on Earth !!!

It has NOTHING to do with the ROM or the work of AdrianDC, but it seems to be purely Google's fault :(

So, I thought I will share how I got through it, perhaps helping some of you not getting nearly insane, like me yesterday...

First one was "Stuck on "Checking for updates..", so I found first here : https://www.reddit.com/r/GalaxyS9/comments/aqa384/t_mobile_s9_stuck_on_checking_for_updates_after/ this reply : "I had to completely disconnect from wifi, took the sim out so it would skip that process. Its finally working fine now." method confirmed in this XDA thread here : https://xdaforums.com/nokia-7/help/stuck-screen-checking-updates-hard-reset-t3767866/page2 in the post #15 : "Try without SIM card inserted. It should work."

Alternatively, in this thread : https://xdaforums.com/2015-moto-g/help/reset-stuck-checking-updates-t3571496 the method explained in post #4 worked well also :

"On the TWRP Terminal:

echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop

this will skip the first setup!

edit: may need to mount /system"

And then came the second bug : "Phone stuck on Preparing for Setup after factory reset of Android Pie"

I read a lot of threads about it :

https://xdaforums.com/mi-a2/help/phone-stuck-preparing-setup-t3870469

https://forums.oneplus.com/threads/android-preparing-for-setup-prompt-always-appearing.1083942/

https://forums.oneplus.com/threads/stuck-with-android-setup-issue-on-oneplus-6t.953686/

https://forums.lenovo.com/t5/motorola-one-motorola-one-power/Preparing-for-Setup-you-can-finish-your-motorola-one-power-soon/m-p/4391471#M4710

https://www.reddit.com/r/tmobile/comments/9uj9vw/cannot_get_android_setup_app_updates_are_ready/e94uow3

https://uk.community.huawei.com/mate-20-series-20/app-updates-is-not-moving-preparing-for-setup-2591

https://uk.community.huawei.com/mate-20-series-20/android-setup-keeps-telling-me-that-app-updates-are-ready-and-that-i-should-connect-to-wifi-5687

And so on, but nothing in all this posts helped :mad: so I ended disabling the notification AND the Android Setup app !!!

Some of those reports are more than a year old and I've rooted and flashed custom ROMs on 5 differents devices / brands over the years, but I never encountered such a mess !

Google, what's wrong with you ?!?

So I hope this will help a bit, I wish you all a nice Sunday...
[Xperia SP Original Android Development] fsw_informatrix:
For completion's sake, I forgot to add that I've made a clean install and did follow exactly these steps to do it :

- having made the TA backup years ago and finding LineageOS Oreo a bit too lagy to my taste, I took the occasion to try (for the first time) to restore the TA partition (with success), this locking back again the bootloader and then, restored with Flashtool the original ROM that was shipped with the SP;

- so I find myself back with the original DRM keys :D and the original Jelly Bean :crying:, played a little bit with it (a real trip down Memory Lane) and confirmed forever to myself that I really don't miss anything of Sony's crap (Bravia Engine, Track-ID, whatever...), but to each his own;

- I used fastboot and Sony's code to unlock the bootloader again, then boot twrp.img, flashed the FOTA.zip and erase EVERYTHING, but the SD card !

- I just flashed the 20190817 build and the OpenGapps Micro, one after the other from the SD Card and let the BootBridge.zip with Magisk inside for a later time...

- I rebooted and then, all Hell broke loose :mad:

- Hours (and a lot of swearing) later, I flashed BootBridge.zip with Magisk and could finaly enjoy how mean and lean is Android 9 on this 2013 device :D again, bravo !!!

So, I honestly don't think that any of those steps described above could have been the cause of the 2 bugs (and the numerous threads I've read seem to confirm it), but I would be glady corrected if I'm wrong...

Really, nobody here had to go through this whole hassle, seriously ? You've all got a smooth ride with a clean install ?

I would really like to know if it's me or if, in this case, Google is having two left hands, and just with thumbs :silly:
[Xperia SP Original Android Development] TechnoSparks:
Sometimes opengapps can cause errors given how itself is like a rolling Nightly packages generated on demand when you hit download. I recommend trying MindTheGapps as it went smoothly for me using that one.

Not a setup issue, but an issue nonetheless: During my attempt to flash this ROM, I had free space errors with Opengapps. Even on pico package!

Ninja Edit: I found out on the LOS pie thread that Pico is the only one that fits. I still however stand by the authenticity of my story
[Xperia SP Original Android Development] fsw_informatrix:
Thank you again :) didn't thought about that one, I will give MindTheGapps a try, next time...
[Xperia SP Original Android Development] fsw_informatrix:
OMG, my second try was so quick & easy with MindThe Gapps, thanks again [MENTION=5765352]TechnoSparks[/MENTION] :D

I did a Nandroid backup and couldn't resist to give it another try, so from TWRP in the FOTA :

1) I manually erased all partitions, but recovery, SD Card and USB-OTG, just to be sure.

2) I queued and installed from the first post (and in this order) aosp-9-20190817-huashan-adriandc.zip, android_lowram_enabler.zip and MindTheGapps-9.0.0-arm-20190615_031401.zip, without any errors.

That was the right call to flash the android_lowram_enabler.zip in between, because I've noticed a message from the MindTheGapps installer :

"Low ressource device detected, removing large extras", which is lovely and exactly what I needed, no Google bloatware...

3) I rebooted and didn't met any of the bugs I had with OpenGapps, not even an initial setup :laugh: just had to pick manually language and Wi-Fi (location and date/hour too, as there is no SIM inside).

4) I got back to TWRP and flashed BootBridge-SonyELF.zip with Magisk19.3 inside, rebooted and updated Magisk Manager (Note: strangely, I had to reflash BootBridge-SonyELF.zip a second time, after the Magisk Manager update, to get it working back).

Now, it's all set up and I can finally test it further ;)

Hope this helps somebody and keep up the good work, M. AdrianDC...
[Xperia SP Original Android Development] AdrianDC:
Thank you for your report.

For information, I'll remind something for everyone : My Sony Huashan & Blue releases are all using the Go low RAM configs.

Flashing android_lowram_enabler is not required, it's a no-op, however android_lowram_disabler will bring back disabled features per user choice.

The android_lowram_enabler tool serves a purpose only to come back from a disabler and for any other devices not using Go low RAM configs.
[Xperia SP Original Android Development] mirhl:
I see and I could report this is the case in the system...

But I swear I don't understand why the status bar still is transparent on the homescreen and in various programs.

Btw did you investigate using the ro.config.small_battery flag? I'm not sure if huashan would fit the bill (even though, assuming you still have the original battery it may as well do) but perhaps tsubasa could qualify.
[Xperia SP Original Android Development] abiyyu_b:
sir can i do dirty flash if i want to downgrade to aosp oreo or nougat? i got a bit unresponsive on pie

i want to keep my app data if it possible
[Xperia SP Original Android Development] LaRazón:
Not really expecting an answer at this point but here goes...

I am using a really early build of this rom (4/2019), but it works really well.

I've also installed the latest version of Magisk using Bootbridge. My problem is that I can't seem to make it pass the safetynet check, says false on both CTS Profile and Basic Integrity.

I've tried a lot of things, but nothing seems to work. Is it just because of the build, and something that has been repaired in later builds?
[Xperia SP Original Android Development] feromgar:
No version of this room pases CTS profile without a magisk module helping it to fool Safetynet. Basic Integrity failing is a weird error that does happen from time to time. Usually just reflashing everything fixes it. Keep in mind, that there have been some changes in safetynet that could be breaking it for you.
[Xperia SP Original Android Development] Vladried9:
HI AdrianDC, thank you for all you work, i think its amazing, i Tryed this rom from yesterday, and everything is going perfect, navigation on this emviroment is smooth, i instaled the lastest GAPPS, no issue found, even i installed FB , Instagram and another social apps, works fine to me.

But i may find some kind of bug or something, some apps that i use has a media pleyer inside to play micro- video tutorial, but i cant see them, looks like buffering only, even videos played from chrome , like news videos i cant see them, only seems buffering, maybe its only me, or i did something wrong, can you or anyone help me?, please

regards!
[Amazfit] siimot:
Hi all

Quick question should the lo-fi mode on the pace go back to normal when you raise your wrist?

Mine used to when you raised the wrist it would go back to full res but after wiping the watch it no longer does until the screen is unlocked, what's correct?
[Amazfit] Holydao:
You should activate it in options/general menu again.View attachment 4807226
[Amazfit] siimot:
Hi sorry that's not what I mean, before when I raised my wrist the resolution of the watch face would increase but keep the light off, should the resolution increase when I raise my wrist I don't want the light coming on.
[Amazfit] Holydao:
Then, could it be about auto light switch on/off option?View attachment 4807248
[Amazfit] siimot:
It's always set to 1, not sure if you can see in the image this was before it stopped doing it but you can see that watch face res has changed just from flicking my wrist up, it's no longer doing it.
[Amazfit] siimot:
It's working again after a full charge, I think it's where the battery was getting low
[Amazfit] dersie:
I have a Stratos and it change to high res when flicking the wrist mainly on the Amazfit original faces. On my 3rd faces the res stay low when flicking the wrist.
[Amazfit] Holydao:
Oh, now I see... The backlight doesn't work when charge is below %10.
[Android Head-Units] jezmondo:
Hi - I'm unsure which to buy so any advice is really appreciated!

I'm about to buy my first HU and all those I'm looking at have same spec: 8 core 4Gb 64Gb with DSP TDA785

The FunRover has a Spreadtrum SC9853I-IA chip, whereas the others have Rockchip PX5/PX30

Is Joying better in any way than the lesser know brands? Is FunRover respected (they say they have a European warehouse too). Most seem to use PX5 - is it good? Does anyone have any experience with the Spreadtrum?

I'd really appreciate any advice or opinions. I'll post a review once I get my HU.

Thanks!
[Android Head-Units] marchnz:
Neither. Recommend Dasaita.