Hi all,
I'm following the guide at CM wiki to build for samsung n7100:
**tp://wiki.cyanogenmod.org/w/Build_for_n7100 (sorry)
While executing device/samsung/n7100/extract-files.sh, I note that some files are missing from my device (running CM version 11-20140505-SNAPSHOT-M6-n7100):
Code:
/system/bin/bcm4334_semco.hcd
/system/bin/lpm
/system/lib/libaudiosa.so
/system/vendor/lib/liblvverx.so
/system/vendor/lib/liblvvetx.so
/system/vendor/lib/mediadrm/libwvdrmengine.so
The build fails with make complaining about no rules to make these files.
What makes me confused is that the stock system.img does not contain these files either. So why are they listed as dependencies, or why does the script try to extract them? How can I carry out a successful build?
Dears,
I apologize if same kind of topic already exist. I searched but did not find anything.
I want to build my own image for Pixel (sailfish) from AOSP.
I built it and flashed it, but my Pixel is now blocked and reboot continuously.
I would like to know what is wrong in my procedure:
repo init https://android.googlesource.com/platform/manifest -b android-8.0.0_r30
repo sync
Extract binaries from qcom-sailfish-opr3.170623.013-e4997420.tgz and sailfish-opr3.170623.013-factory-bdc49b40.zip
source build/envsetup.sh
lunch aosp_sailfish-userdebug
make
Then to flash:
First flashed official ROM : sailfish-opr3.170623.013
then
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash system_other system_other.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
Did I made something wrong ?
any thanks I advance for your support
Something tells me that if it were that easy, there would be 100s of Oreo roms, not just 1.
If you have TWRP installed you can get a console-ramoops from it.
If you do I am guessing you will be running into this error:
Code:
[ 2.875998] c2 1 init: /system/bin/secilc: Failed to resolve typeattributeset statement at /system/etc/selinux/mapping/26.0.cil:561
[ 2.876026] c2 1 init: /system/bin/secilc: Failed to compile cildb: -2
[ 2.876116] c2 1 init: /system/bin/secilc exited with status 254
[ 2.876159] c2 1 init: panic: rebooting to bootloader
The commits to fix this can be found here:
https://review.carbonrom.org/#/q/topic:stock_vendor
or here:
https://gerrit.omnirom.org/#/q/topic:stock_vendor
thank you, I will try
I finally found a workaround, let me explained.
I am not satisfied, but at least it works...
I downloaded the google factory image corresponding to android-8.0.0_r30 from
https://developers.google.com/android/images
OPR3.170623.013, Nov 2017
Inside there is a zip with .img files
I replaced those files with mine, and used flash-all
Now it works...
the problem is that there are many files, an dI am able to generate/update only few of them...
aboot.img -> ??
android-info.txt -> ok
apdp.img -> ??
boot.img -> ok
bootlocker.img -> ??
cmnlib32.img -> ??
cmnlib64.img -> ??
devcfg.img -> ??
hosd.img -> ??
hyp.img -> ??
keymaster.img -> ??
list.txt -> ??
modem.img -> ??
pmic.img -> ??
ramdisk-recovery.img -> ok
ramdisk.img -> ok
rpm.img -> ??
system.img -> ok
system_other.img -> ok
tz.img -> ??
userdata.img -> ok
vendor.img -> ok
xbl.img -> ??
So, what does your new rom have over the factory versions? 8.1 just dropped a few hrs ago.
I think his mission is learning. Not supplying you with an l33t firmware.
Sent from my Pixel using Tapatalk
maulich said:
I think his mission is learning. Not supplying you with an l33t firmware.
Click to expand...
Click to collapse
Didn't want one. I was genuinely wondering what his customizations were, Stock 8.x on the Pixel, is quite close to AOSP, and now that 8.1 is out with all the bug fixes that 8.0 needed...
I was able to build 8.0.0 for Pixel without issues. Make sure to disable the jack server when building, otherwise you'll likely have errors:
Code:
make ANDROID_COMPILE_WITH_JACK:=false
edit: for 8.1.0 you need to do
Code:
export ANDROID_COMPILE_WITH_JACK=false
before compiling for the option to have an effect
edit: also you should flash the images with fastboot flashall -w
8.1.0 Sources are also available now at android-8.1.0_r1, I'm currently downloading them.
However even with a successful build, there are minor issues I had, see here:
https://forum.xda-developers.com/android/help/compiled-aosp-8-0-0-source-pixel-dialer-t3714890
Hello,
I just realized that when I build the aosp for sailfish, the vendor.img partition is not built.
it uses a prebuilt image, located in
/vendor/google_devices/sailfish/proprietary/vendor.img
Does anybody knows how to generate our own vendor.img file ?
thanks in advance
maulich said:
I think his mission is learning. Not supplying you with an l33t firmware.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yes right, mission is learning.
zongojim said:
Hello,
I just realized that when I build the aosp for sailfish, the vendor.img partition is not built.
it uses a prebuilt image, located in
/vendor/google_devices/sailfish/proprietary/vendor.img
Does anybody knows how to generate our own vendor.img file ?
thanks in advance
Click to expand...
Click to collapse
The vendor partition contains proprietary things from the hardware manufacturers, things like device drivers and photo processing for example. Since the source code for those isn't freely available, you cannot build the image yourself.
HeavyHDx said:
The vendor partition contains proprietary things from the hardware manufacturers, things like device drivers and photo processing for example. Since the source code for those isn't freely available, you cannot build the image yourself.
Click to expand...
Click to collapse
yes I know this. But in previous Nexus images, we can use the binaries delivered by Google from:
https://www.google.com/url?sa=t&rct...roid/drivers&usg=AOvVaw314pNmO5TDKaw5H1b3pyYS
Then we could build vendor.img partition including these binaries.
For Pixel, I also retrieved the binaries, and now would like to build the new vendor.img partition.
vendor.img contains other information than only binaries, that I am interested to change (for instance sepolicy files, or init rc files)
Alright, 8.1.0 seems to work perfectly without any crashes this time. I'll sign it real quick and do a bit of testing and then I'll make a thread and upload the ROM.
HeavyHDx said:
Alright, 8.1.0 seems to work perfectly without any crashes this time. I'll sign it real quick and do a bit of testing and then I'll make a thread and upload the ROM.
Click to expand...
Click to collapse
I'm also trying to build AOSP for 8.1.0. However, my ultimate goal would be building it with the new Android GO configuration, any ideas how to approach this?
ka-la said:
I'm also trying to build AOSP for 8.1.0. However, my ultimate goal would be building it with the new Android GO configuration, any ideas how to approach this?
Click to expand...
Click to collapse
No idea, I'm also new to to this all. I discovered that the dialer does crash when making or receiving phone calls, however. I'm currently making my post.
HeavyHDx said:
No idea, I'm also new to to this all. I discovered that the dialer does crash when making or receiving phone calls, however. I'm currently making my post.
Click to expand...
Click to collapse
Did you make... the Dialer app your default Phone app under Settings -> Apps -> Advanced -> Default Apps -> Phone app?
ka-la said:
Did you make... the Dialer app your default Phone app under Settings -> Apps -> Advanced -> Default Apps -> Phone app?
Click to expand...
Click to collapse
Yup.
Thread is up now:
https://forum.xda-developers.com/pixel/development/rom-aosp-8-1-0-sailfish-t3715557
ka-la said:
I'm also trying to build AOSP for 8.1.0. However, my ultimate goal would be building it with the new Android GO configuration, any ideas how to approach this?
Click to expand...
Click to collapse
Man, I'd love to see that. I asked the Nova guys last night if they could enhance their Google Assistant tool to let you pick what app, so I could have it open Google Go (search lite) and I sideloaded YoutubeGo and it works good.
Hi, ran my 8.0.0 AOSP build without issues on the dialer. Have a look at the AOSP fixes which I collected from developers.
https://github.com/GeyerA/device_google_marlin/commit/dd78aff040dccef47ba0a77a84f1bc2b2373c468
Here also the content of aosp_fixes.mk which I kept in the vendor_tree (credit to PureNexusProject).
Code:
# Copyright (C) 2017 The Pure Nexus Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Google property overides
ifeq ($(filter marlin sailfish,$(TARGET_PRODUCT)),)
PRODUCT_PROPERTY_OVERRIDES += \
keyguard.no_require_sim=true \
ro.control_privapp_permissions=enforce \
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html \
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html \
ro.com.google.clientidbase=android-google \
ro.error.receiver.system.apps=com.google.android.gms \
ro.setupwizard.enterprise_mode=1 \
ro.com.android.dataroaming=false \
ro.atrace.core.services=com.google.android.gms,com.google.android.gms.ui,com.google.android.gms.persistent \
ro.setupwizard.rotation_locked=true \
ro.config.notification_sound=Chime.ogg \
ro.config.alarm_alert=Flow.ogg \
ro.config.ringtone=Zen.ogg
ro.carrier=unknown
endif
I also built the gapps directly with the ROM which might make a difference. Maybe this is of help.... Also, what does logcat say?
Hi All,
Just want to make everyone aware that CalyxOS is available for the Pixel 5. It has a lot to offer for anyone security or privacy-focused.
MicroG is baked right in and is actually part of the setup process. I've been running this ROM for weeks and it runs flawlessly.
calyxos.org
WaxysDargle said:
Hi All,
Just want to make everyone aware that CalyxOS is available for the Pixel 5. It has a lot to offer for anyone security or privacy-focused.
MicroG is baked right in and is actually part of the setup process. I've been running this ROM for weeks and it runs flawlessly.
calyxos.org
Click to expand...
Click to collapse
microg did not work for me..maybe they will fix that on the next update.
vinicioh23 said:
microg did not work for me..maybe they will fix that on the next update.
Click to expand...
Click to collapse
you have to dial *#*#CHECKIN#*#* on the dialer and then reboot to activate microg push notifications.
Hi, I would love to use calyxos on my Pixel 5 but on flashing it keeps saying that there is no space on the device to extract system.img:
extracting product.img (1008 MB) to disk...ziparchive W 11-13 12:05:40 2186 2186 Zip: unable to write 32768 bytes to file; No space left on device fastboot: error: failed to extract 'product.img': I/O error
What shoudl I do?
TheOriginalDude said:
Hi, I would love to use calyxos on my Pixel 5 but on flashing it keeps saying that there is no space on the device to extract system.img:
extracting product.img (1008 MB) to disk...ziparchive W 11-13 12:05:40 2186 2186 Zip: unable to write 32768 bytes to file; No space left on device fastboot: error: failed to extract 'product.img': I/O error
What shoudl I do?
Click to expand...
Click to collapse
Someone helped me in another forum: the parameter TMPDIR (capital letters) should point to a folder with more than 3 GB of memory. Then, the flasher will work.