[android-building] Re: kernel/manifest for sunfish android 11

[xstefen]

You must have ESP or something, how did you know? 

Regardless, it would be fitting for a sunfish android 11 kernel/manifest to 
be released in my opinion. Despite there being other ways to accomplish the 
same, for such a recent and well rated device I feel its been brushed under 
the rug a bit, as im sure others would agree

Sunfish' need love too.

On Wednesday, November 4, 2020 at 6:19:53 PM UTC-6 jch...@gmail.com wrote:

> Pixel devices in general do have very good support. I'm assuming you're 
> attempting to build the kernel inline with AOSP, which means you'll need to 
> perform subtree merges of the respective modules and other elements in 
> order to be successful.
>
> On Tuesday, November 3, 2020 at 11:11:45 AM UTC-5 xstefen wrote:
>
>> I think this one was missed. And the kernel/msm tag for it does not build 
>> as is. I bought a pixel phone under the assumption that it would have 
>> excellent upstream support, i appreciate your response
>
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/daf7be79-d221-4eca-8a03-feb0c1d424f2n%40googlegroups.com.

[android-building] Re: AOSP sunfish support for eSIM

[xstefen]

Correct, this is a more accurate description, thanks Josh

On Wednesday, November 4, 2020 at 6:19:53 PM UTC-6 jch...@gmail.com wrote:

> No work on the AOSP platform side is required for eSIM. It just requires 
> an extraction of libraries and binaries from the factory images, which 
> allow this functionality to work.
>
> On Tuesday, November 3, 2020 at 11:11:32 AM UTC-5 xstefen wrote:
>
>> AOSP needs further implementation to support eSIM. It works on factory 
>> Pixel Android because they've included proprietary tools to handle it which 
>> are not available in upstream AOSP source
>>
>> On Tuesday, October 20, 2020 at 6:24:03 PM UTC-5 phantom wrote:
>>
>>> Hello,
>>>
>>> I ran into an issue with eSIM, hopefully someone knows the answer.
>>>
>>> I bought a Pixel 4e in the US and has the eSIM activated for Verizon 
>>> Network.
>>>  
>>> When I build and flash android-11.0.0_r5 AOSP sunfish on my Pixel 4e, 
>>> the eSIM is no longer present.   About phone screen does not show the IMEI 
>>> of the eSIM.
>>>
>>> Is there a particular version of sunfish that support eSIM?  Or do I 
>>> need to change any settings to enable it?
>>>
>>> Thx,
>>> Tom
>>>
>>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/86f92ef0-9ab8-4d0b-8c0e-1112c4f16c92n%40googlegroups.com.

[android-building] Re: kernel/manifest for sunfish android 11

[Josh Chasky]

Pixel devices in general do have very good support. I'm assuming you're 
attempting to build the kernel inline with AOSP, which means you'll need to 
perform subtree merges of the respective modules and other elements in 
order to be successful.

On Tuesday, November 3, 2020 at 11:11:45 AM UTC-5 xstefen wrote:

> I think this one was missed. And the kernel/msm tag for it does not build 
> as is. I bought a pixel phone under the assumption that it would have 
> excellent upstream support, i appreciate your response

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/52ed2019-c404-4ede-a495-d5e70a6969c8n%40googlegroups.com.

[android-building] Re: AOSP sunfish support for eSIM

[Josh Chasky]

No work on the AOSP platform side is required for eSIM. It just requires an 
extraction of libraries and binaries from the factory images, which allow 
this functionality to work.

On Tuesday, November 3, 2020 at 11:11:32 AM UTC-5 xstefen wrote:

> AOSP needs further implementation to support eSIM. It works on factory 
> Pixel Android because they've included proprietary tools to handle it which 
> are not available in upstream AOSP source
>
> On Tuesday, October 20, 2020 at 6:24:03 PM UTC-5 phantom wrote:
>
>> Hello,
>>
>> I ran into an issue with eSIM, hopefully someone knows the answer.
>>
>> I bought a Pixel 4e in the US and has the eSIM activated for Verizon 
>> Network.
>>  
>> When I build and flash android-11.0.0_r5 AOSP sunfish on my Pixel 4e, the 
>> eSIM is no longer present.   About phone screen does not show the IMEI of 
>> the eSIM.
>>
>> Is there a particular version of sunfish that support eSIM?  Or do I need 
>> to change any settings to enable it?
>>
>> Thx,
>> Tom
>>
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/1708205b-e064-485b-9735-bdc521cc6f17n%40googlegroups.com.

Re: [android-building] Unable to start emulator

['Frank Yang' via Android Building]

Hi, you'll need to lunch sdk_phone_x86-userdebug

On Wed, Nov 4, 2020 at 7:46 AM Mahnoor Malik  wrote:

> Dear all,
>
> I have built the master branch of android aosp. I have chosen
> aosp_sargo-userdebug with the lunch command. Everything works fine but when
> I start the emulator I get the following error
> qemu-system-aarch64: Could not open
> '/home/hpcc/aosp/out/target/product/sargo/userdata-qemu.img': No such file
> or directory
> Any help will be highly appreciated. Thank you
>
> Regards,
> Mahnoor
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/CABiDw9gLaDTqC_UkmZkPcWt5NrXzijJeu-Lzbsk2n_rjwRMk4w%40mail.gmail.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAEkmjvVAc1Tj2XkEawFS%3DuKguy-5fVcftoFXaz5TH9YCzuLY%2Bg%40mail.gmail.com.

[android-building] Unable to start emulator

[Mahnoor Malik]

Dear all,

I have built the master branch of android aosp. I have chosen
aosp_sargo-userdebug with the lunch command. Everything works fine but when
I start the emulator I get the following error
qemu-system-aarch64: Could not open
'/home/hpcc/aosp/out/target/product/sargo/userdata-qemu.img': No such file
or directory
Any help will be highly appreciated. Thank you

Regards,
Mahnoor

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CABiDw9gLaDTqC_UkmZkPcWt5NrXzijJeu-Lzbsk2n_rjwRMk4w%40mail.gmail.com.