search

sonyxperiadev / bug_tracker

Empty repository that is used as a bugtracker for Open Devices project
52 stars 13 forks source link

[maple][4.14][10]Recent status about AOSP on XZ Premium #573

Closed mhtvsSFrpHdE closed 4 years ago

mhtvsSFrpHdE commented 4 years ago

Platform: Yoshino Device: maple (g8142) Kernel version: 4.9 Android version: android-10.0.0_r33(Legacy) Software binaries version: 9.0_2.3.2_v9_yoshino

Is your feature request related to a problem? Please describe. https://github.com/sonyxperiadev/bug_tracker/issues/571
https://github.com/sonyxperiadev/bug_tracker/issues/536
https://github.com/sonyxperiadev/bug_tracker/issues/533

Wifi not work, then system will crash after running for a while All are sloved after SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_yoshino
This is a outdated issue

I'm apologize to my bad comment, I now calm down and be patient.

Describe the solution you'd like AOSP 9 or 10 for SONY Xperia XZ Premium

Describe alternatives you've considered Android Project Treble, this new mechanism allow us to install
compiled binary ROM directly from Google,
so compile will not a nightmare anymore.

Another good is with treble, can get system update from Google directly,
without to wait a monkey-patch for specified device.

I hope this will. If Google is not telling a lie.
Because Microsoft Windows certainly can install across device all over the world.
Treble might be the hope to implement same thing on Android.

stefanhh0 commented 4 years ago

I am sorry that you had bad days, hopefully it will get better!

Wi-Fi not works on the device

Open a bug report.

Yes, the overall situation is far from being ideal or perfect. That is live, learn to live with it and if something is no fun to do, but only frustration, leave it behind and do something that is more fun.

This is more a general complaint out of frustration and not a serious enhancement request, while this is understandable and provides feedback for the volunteers involved in this project which has a value by itself, this should nevertheless just be closed.

Cheers Stefan

Paulbouchara commented 4 years ago

Hey there,

I'm the PixelExperience Maintainer, if I understood correctly, you made a maple build on PE based on A10 with the trees I pushed ?

If that's correct, then how did you had display to check if wifi was working ? Because, at the last time I could try / get user feedback (@PixelExperienceSony on telegram btw) the device displayed a nice black screen.

Also, keep in mind that our team on based on free time people working on that project, there's only a small team of sony employees working separately from Sony Stock Team. That means that we have ONE guy doing all the kernel work for : yoshino, nile, ganges, tama, kumano (current dev), tone and loire (mainline work) and upcoming sdm865 platform when it'll come out And that's a LOT even for a skilled guy that is doing that by passion.

Regarding the Android 9 branch, it is indeed weird that this branch doesn't have the exact same features as we had before, if you have time to give us a lil hand on that, it would be greatly appreciated.

If you have any questions, I'm available on git or on the telegram @ I gave upper.

Cheers

Haxk20 commented 4 years ago

Hello,

We are a small team sadly that has a lot of stuff to do. And we have been slowed down even more then usual with the current world situation. We are working very hard to get every device working. Thank you for understanding

mhtvsSFrpHdE commented 4 years ago

@Paulbouchara I use this one
https://forum.xda-developers.com/xz-premium/development/rom-pixel-experience-plus-edition-t4088483

I keep digging it in next few days, it's fun that although this one is AOSP,
but without Camera2API / RAW capture support.

Paulbouchara commented 4 years ago

Hi, This version is an unofficial one which is not supported by me.

Furthermore, this rom (the unofficial version) is based on stock libraries, which have nothing to do with the sodp project.

Hoping it clears some things in your mind, Paul

mhtvsSFrpHdE commented 4 years ago

Hi, This version is an unofficial one which is not supported by me.

Furthermore, this rom (the unofficial version) is based on stock libraries, which have nothing to do with the sodp project.

Hoping it clears some things in your mind, Paul

@Paulbouchara Sure that's nothing to do with official PixelExperience!
For me, that's a method to test things on Android version 10 right now.

I'm looking for how did they fix the Wi-Fi problem.
It seems the kernel is come from LineageOS,
now SODP kernel have a Wi-Fi problem,
but the LineageOS one doesn't.

These in my mind:
if LineageOS kernel based on SODP kernel(if open source, why not)
    they fixed Wi-Fi problem on SODP kernel
    use that fixed kernel to compile unofficial PixelExperience but SODP still have a Wi-Fi problem, fantastic

I'm going to: try use LineageOS kernel to build AOSP, just like they use it to build PixelExperience
(very likely will be failed for tons of reasons) keep waiting for next SODP kernel patch to see if Wi-fi can work, or sumbit a issue grab some book to see if I can get more understand about Android system dev

Before I just use python and javascript to do some lightweight things out there,
can't really say I'm ready to actually "code" on these things instead of
just playing with some magical command line commands.

You tell "based on stock libraries", impressive for me is like dropping a bomb,
I didn't realize that the two can be two different things.
Say Google, their stock with AOSP have very minimal difference, and most are GAPPS.

Paulbouchara commented 4 years ago

Hey there, the unofficial LineageOS build your tried is NOT based on sodp work and will NOT work with SODP build trees whatsoever.

You'll be just using a stock 4.4 kernel over a 4.14 kernel userspace and that won't work at all.

Furthermore, if you compile the latest sodp kernel, I'm pretty sure the wifi works, which is odd because you don't have it working, could you provide some logs for that ?

I also have some builds based on sodp trees that you could try out and report issues

mhtvsSFrpHdE commented 4 years ago

@Paulbouchara So they are different, very different...

The 4.14 kernel are run across many devices,
in my case (Xperia XZ Premium/maple/G8142) can't boot right now,
so I need to back and looking for 4.9.
That's may be why I'm not getting the latest patch.

Other information
When I doing my compile, that was

All SW_binaries downloaded and try flash to device on my computer are

The build date are

These build are use guide on this website: https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/build-aosp-android-android-10-0-0

No any 3rd plugin or patch included, just pure type-and-compile.
It has been 15 days past, it may already fixed in some new commit,
or my compile combination are bad luck, for example,
you will choose an Android branch, a local_manifest branch, then a SW_binaries

Just one failed can lead to the bad results.

I do a compile later to see if I can reproduce same results.
Or I can zip them together to Google Drive for further digging.
Android 10+4.14 build are not boot at all,
9 and 10+4.9 build boot but have Wi-Fi problems.

Paulbouchara commented 4 years ago

If you try the latest head of sod for kernel 4.14, ALWAYS take the latest oem release (as time of writing, v6). The v6 + latest head is still alpha/beta material but it should boot and give you the ability to test few things here and there.

Imma ping @kholk because he's way more knowing what's happening precisely and what works and what doesn't.

mhtvsSFrpHdE commented 4 years ago

@Paulbouchara

https://github.com/sonyxperiadev/bug_tracker/issues/533

Keep in mind that kernel 4.14 is not fully ready for Yoshino yet. While we're working hard it may still take a couple more days.

Perhaps you have more luck using kernel 4.9 and Android 9 from the official sonyxperiadev repositories directly.

This says the kernel still require time to work...

https://github.com/sonyxperiadev/bug_tracker/issues/299

This issue is still present, please reopen

This says it's a "legacy" problem and related issue are closed for unknown reason

The v6 + latest head is still alpha/beta material but it should boot and give you the ability to test few things here and there.

When the day I build, v6a suddenly available after my compile.
But my build is based on v5x, I flash v5 first, not work then v6 directly with v5,
the certain period head of system.
Didn't rebuild with the latest head, that may the reason still not booting.

Paulbouchara commented 4 years ago

Last 2 weeks have been productive for yoshino and especially maple, so you should definitely try out that

MarijnS95 commented 4 years ago

533

Keep in mind that kernel 4.14 is not fully ready for Yoshino yet. While we're working hard it may still take a couple more days. Perhaps you have more luck using kernel 4.9 and Android 9 from the official sonyxperiadev repositories directly.

This says the kernel still require time to work...

Hmm, February 3, its now May 15th.

299

This issue is still present, please reopen

This says it's a "legacy" problem and related issue are closed for unknown reason

The v6 + latest head is still alpha/beta material but it should boot and give you the ability to test few things here and there.

It's a different "legacy" issue, Loire and Tone use brcmfmac, Yoshino is on qcacld.

When the day I build, v6a suddenly available after my compile. But my build is based on v5x, I flash v5 first, not work then v6 directly with v5, the certain period head of system. Didn't rebuild with the latest head, that may the reason still not booting.

Kernel patches became available around that date so you really need to rebuild and flash :wink:

mhtvsSFrpHdE commented 4 years ago

Last 2 weeks have been productive for yoshino and especially maple, so you should definitely try out that

@Paulbouchara I feel... DEJAVU!!
That was Fast a lot than I can ever imagine,
I was just think that maybe I'll wait for eight months that long or something.

Hopefully one day I can also do that kind of amazing programming instead of just ask help...
Contributors defineally more love a pull request!

mhtvsSFrpHdE commented 4 years ago

@MarijnS95 I often list the two issue together because 533 is for maple,
but in the post people tells to following 299, that's not maple.
I can't have more deep understand, but it seems they are finally past.

kgvarunkanth commented on Mar 10

Closing issue Following 299

MarijnS95 commented 4 years ago

Right... That shouldn't be the case though, they are likely distinct problems. We'll get it looked after at some point!

mhtvsSFrpHdE commented 4 years ago

@Paulbouchara I did a successful build, the current problem is,
after boot for a while (after showing launcher or unlock screen), 5 second or 60 second later,
the display will crash and keep black. After more time, every hardware button freeze,
it may reboot itself or not in finally.

The Wi-Fi did work at that moment. It may be still "work in progress",
I feel not inappropriate to start a new issue, this look like "Urge/Hasten" and be very rude.

I'll keep waiting for new patch and do weekly build as possible as I can,
then report new issue if I can feel something new happens.

kholk commented 4 years ago

Don't worry, I don't see having an open issue on the bug tracker as being rude in any way, as long as they're not "just a rant", but describing a problem as per the guidelines.

Yoshino is still a work in progress, I've been bashing my head on it for some days and that's the point that we've reached now: there are still a few issues to solve and I hope to be able to get back to that asap.

The sleep crash issues are related to either a power domain going down and never getting back up or a clock going "a lil crazy"... We will see...... :)))

stefanhh0 commented 4 years ago

after boot for a while (after showing launcher or unlock screen), 5 second or 60 second later, the display will crash and keep black. After more time, every hardware button freeze, it may reboot itself or not in finally.

I can confirm that behavior, there is already an issue open for it: #580:

Other possibly related symptoms I see with k4.14:

  • Waking up the phone from sleep takes sometimes quite some time, I have to push the button several times to get the display up, sometimes I even have to reboot or the phone reboots itself

Not unlikely that the root cause for lilac and maple is the very same.

My workaround is to set the device active in the developer settings, keep the device plugged in and activate screen saver to not let the device fall asleep :-)

mhtvsSFrpHdE commented 4 years ago

SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_yoshino are released!

After my weekly build, it seems everything work and stable in the first impression
Wi-Fi available and no crash! Thank you guys!

Paulbouchara commented 4 years ago

Glad you got your device booting correctly 😄