make -j8 recoveryimage
and just flash recovery through fastboot
On Thursday, May 4, 2017 at 7:38:05 PM UTC+5:30, yf...@mobvoi.com wrote:
>
> I'm modifying the recovery code to fit some feature, here's my steps:
> build all project with `make -j8`
> build ota package with `make otapackages`
>
Hello ,
You should not edit the fastboot binary , if you do that it will only work
on your pc .
You should change it in the Android Bootloader Sources
platform/bootable/bootloader , and then flash the compiled new bootloader
binary to bootloader partition now your custom commands will work.
But
Take a look how they handle unlabeled policies
https://review.lineageos.org/#/c/19527/
https://review.lineageos.org/#/c/158864/
To be honest there shouldn't be any unlabeled files all.
On Tuesday, August 29, 2017 at 11:15:03 PM UTC+5:30, Mantesh Eksambe wrote:
>
>
> I have added device in
Since this is a bring up i think you should try with selinux permissive at
this stage you can add policies for the denials in the later stage .
in the targets Boardconfig makefile find kernel command line and add to the
end
androidboot.selinux=permissive
On Tuesday, August 29, 2017 at
Hello all,
Here is how i was able to access , read , write to sysfs from an android
application .
Ramdisk / device specific changes
#init.{hardware}.rc
>
> on property:sys.boot_completed=1
>
> #UART5 on my device
> chown root root /dev/ttymxc4
> chmod 0777 /dev/ttymxc4
> #GPIO5_IO14
Wang wrote:
>
> Just adding a line of finishsetup() at the end of the onCreate fails the
> compiling.
>
> Could you elaborate how I use the finishsetup()? Do I have to include
> anything?
>
> Sooraj Sizon於 2018年11月30日星期五 UTC+8上午6時19分23秒寫道：
>>
>> There is an
There is an finishsetup() function in AOSP Setup wizard you may run this
function on onCreate of SetupWizqrd , this would help you finish / skip the
setup process and set default luncher as Luncher3
--
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website:
Hi Paul , Is this a custom peripheral that you are trying to communicate
with using i2c .
or the support have been already added to the board ?
Check for driver in kernel source . If not available you can write your own
android kernel driver to communicate with i2c .
On Thursday, January 24,
