How do I update to the new build keeping the original settings and data? Thanks!
dirty flash if from the same rom, use backup app for different rom (Helium @ Titanium ) will do
You mean reboot?
How do I update to the new build keeping the original settings and data? Thanks!
dirty flash if from the same rom, use backup app for different rom (Helium @ Titanium ) will do
@audahadi welcome to the thread i see you and Ivan working on PA sensor issues to add support for it.Development Build...
What differ from OP
*add performance from omni, remove kernel tweaker
*Bionic from Motorolla (falcon)
*Changes from @feed3 - sensors, - location
https://www.androidfilehost.com/?fid=95747613655050392
What error? Maybe you need to revert commit in hardware/qualcom/media-caf-new..need patch in kernel where we don't have. [emoji30]@audahadi welcome to the thread i see you and Ivan working on PA sensor issues to add support for it.
Good luck buddy. I m trying to build from PA source but dt.img and kernel folders creating alots of compilation error.
Sent from my MI 3W using XDA Free mobile app
What error? Maybe you need to revert commit in hardware/qualcom/media-caf-new..need patch in kernel where we don't have. [emoji30]
What error? Maybe you need to revert commit in hardware/qualcom/media-caf-new..need patch in kernel where we don't have. [emoji30]
Try this commandkatwal@VPCSA35GG:~/android/AOSPA$ . build/envsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/xiaomi/cancro/vendorsetup.sh
including device/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
katwal@VPCSA35GG:~/android/AOSPA$
Please refer the build log file attached here for error details and advise me if I need to manually keep the already build boot.img file at that location.
Try this command
. build/envsetup.sh && brunch cancro
PS : Make sure there's a kernel folder in device tree
trying, I confirmed Kernel folder is there in device tree.
AOSPA -> device -> xiaomi -> cancro -> kernel
trying, I confirmed Kernel folder is there in device tree.
AOSPA -> device -> xiaomi -> cancro -> kernel
---------- Post added at 03:32 PM ---------- Previous post was at 03:28 PM ----------
"brunch" command not available. Only LUNCH is there to use that too without "cancro"
katwal@VPCSA35GG:~/android$ cd AOSPA/
katwal@VPCSA35GG:~/android/AOSPA$ . build/envsetup.sh && brunch cancro
including device/generic/mips/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/xiaomi/cancro/vendorsetup.sh
including device/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
No command 'brunch' found, did you mean:
Command 'branch' from package 'rheolef' (universe)
brunch: command not found
katwal@VPCSA35GG:~/android/AOSPA$ . build/envsetup.sh && lunch cancro
including device/generic/mips/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/xiaomi/cancro/vendorsetup.sh
including device/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
Invalid lunch combo: cancro
katwal@VPCSA35GG:~/android/AOSPA$ . build/envsetup.sh && lunch
including device/generic/mips/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/xiaomi/cancro/vendorsetup.sh
including device/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
You're building on Linux
Lunch menu... pick a combo:
1. mini_mips-userdebug
2. mini_armv7a_neon-userdebug
3. mini_x86-userdebug
4. cm_cancro-userdebug
5. cm_bacon-user
6. cm_bacon-userdebug
7. cm_bacon-eng
8. pa_amami-userdebug
9. pa_aries-userdebug
10. pa_bacon-userdebug
11. pa_condor-userdebug
12. pa_d2lte-userdebug
13. pa_d800-userdebug
14. pa_d801-userdebug
15. pa_d802-userdebug
16. pa_d803-userdebug
17. pa_d851-userdebug
18. pa_edison-userdebug
19. pa_evita-userdebug
20. pa_falcon-userdebug
21. pa_find5-userdebug
22. pa_find7-userdebug
23. pa_find7u-userdebug
24. pa_galaxysmtd-userdebug
25. pa_gee-userdebug
26. pa_geeb-userdebug
27. pa_hercules-userdebug
28. pa_hlte-userdebug
29. pa_honami-userdebug
30. pa_i9100-userdebug
31. pa_i9100g-userdebug
32. pa_i9300-userdebug
33. pa_i9500-userdebug
34. pa_jflte-userdebug
35. pa_ls980-userdebug
36. pa_m4-userdebug
37. pa_m7-userdebug
38. pa_m7spr-userdebug
39. pa_m7vzw-userdebug
40. pa_m8-userdebug
41. pa_maserati-userdebug
42. pa_moto_msm8960-userdebug
43. pa_moto_msm8960_jbbl-userdebug
44. pa_moto_msm8960dt-userdebug
45. pa_n1-userdebug
46. pa_n5100-userdebug
47. pa_n5110-userdebug
48. pa_n5120-userdebug
49. pa_n7000-userdebug
50. pa_n7100-userdebug
51. pa_nozomi-userdebug
52. pa_odin-userdebug
53. pa_p3100-userdebug
54. pa_p3110-userdebug
55. pa_sirius-userdebug
56. pa_skyrocket-userdebug
57. pa_spyder-userdebug
58. pa_taoshan-userdebug
59. pa_targa-userdebug
60. pa_togari-userdebug
61. pa_umts_spyder-userdebug
62. pa_ville-userdebug
63. pa_vs980-userdebug
64. pa_yuga-userdebug
65. pa_cancro-userdebug
Which would you like? [aosp_arm-eng] 65
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.4
TARGET_PRODUCT=pa_cancro
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.13.0-39-generic-x86_64-with-Ubuntu-14.04-trusty
HOST_BUILD_TYPE=release
BUILD_ID=KTU84P
OUT_DIR=/home/katwal/android/AOSPA/out
============================================
katwal@VPCSA35GG:~/android/AOSPA$
after selecting pa_cancro-userdebug in lunch option do this
mka bacon
and it will start to build
Thanks but its similar to ./rom-buildd.sh cancro and generates same error same place
I also tried updating using repo sync but not much difference
build/core/tasks/kernel.mk:63: ***************************************************************
build/core/tasks/kernel.mk:64: * Using prebuilt kernel binary instead of source *
build/core/tasks/kernel.mk:65: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
build/core/tasks/kernel.mk:66: * Please configure your device to download the kernel *
build/core/tasks/kernel.mk:67: * source repository to kernel/xiaomi/cancro
build/core/tasks/kernel.mk:68: * See http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building
build/core/tasks/kernel.mk:69: * for more information *
build/core/tasks/kernel.mk:70: ***************************************************************
make: *** No rule to make target `/home/katwal/android/AOSPA/out/target/product/cancro/kernel', needed by `/home/katwal/android/AOSPA/out/target/product/cancro/boot.img'. Stop.
make: *** Waiting for unfinished jobs....
Install: /home/katwal/android/AOSPA/out/host/linux-x86/bin/acp
katwal@VPCSA35GG:~/android/AOSPA$
DO I need to copy the existing Boot.img from AOSP ROM ??
I will check that once I reached home i guess it should be there
Sent from my MI 3W using XDA Free mobile app
I will check that once I reached home i guess it should be there
Sent from my MI 3W using XDA Free mobile app
---------- Post added at 10:54 PM ---------- Previous post was at 10:27 PM ----------
Yes its there AOSPA -> device -> qcom -> common (inside 4 folders and 2 files)
Hmmm, gapps mini and full doesn't show for me... For some reason there is an add in the way. Wouldn't happen to have another mirror would you? :/
Ah, the derp is strong in me tonight lolYup That is coz AICP is on Lollipop hence they removed KK Gapps You can flash any KK gapps (PA is Perfect)
I have a query regarding these releases.
What is the meaning of posting an unofficial AICP release.
AICP officially has not released for cancro (MI3). Then who does that?
What do they do? Do they compile CM11 specifically for Cancro. Change build.props, system libs, etc.?
How do I trust a release which is unofficial, believing that its specifically for Cancro? Meaning, the sound recorder, the camera, other apps, etc. are aware of the device and can take advantage of the features as Official MI3 ROMs can take.
I don't mind the bugs. as long as there are stuff to choose from. we'll be happy, but we'll be happier is xiaomi releases the source for cancro.