I was able to build AOSP 10 on my system with 8GB RAM using a HDD - with 
some difficulty.  For your 16GB system it should have easily done.
My guess is that the external SDD is the problem. They mass storage 
protocol is not optimized for build. 

My System was: 
Ryzen 3 3300u Quad Core. 
8GB Dual channel RAM out of which only 5.81 is available for use.
1 TB HDD
OS:  Kubuntu 20.04.1

I found a few things: 
The build process is both I/O and CPU bound. I will write out the steps 
once I aggregate all together. 


On Wednesday, January 20, 2021 at 9:07:06 PM UTC+5:30 fbri...@gmail.com 
wrote:

> Hi, 
>
> I'm working on Linux Mint with a Dell computer with an Intel Core i5-7200 
> and 16 Go of RAM. I downloaded AOSP into my external SSD drive and working 
> on it but when I tried the codelab for AOSP website, when I launch "m" 
> command for build with eoither -j1 or -j4 options, the process 
> "soong_build" consumes up to 300% of my CPU and froze my computer. I'm in 
> no capability to retrieve my interface or my terminal and then forced to 
> hard reset the computer. I have been searching through the web without 
> success and the page about hardware requirements does not speak about 
> processor. 
>
> Can someone help me ? or give me some hints to be able to build AOSP ? 
>
> Thanks and regards
>
> Fabien Brisset
>

-- 
-- 
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/ed7ff387-d086-4641-bffc-1cf6504fa59cn%40googlegroups.com.

Reply via email to