Database Info

[SCRIPT] 32A - 32B detection script

Hi,
I don't know how-to detect if a device is 32B or 32A automatically.... Logically, if we do a free command during recovery install, we can AUTOMATICALLY check if it's a 32B/A, then, we create a gile on sdcard called 32B/A, or a prop, and when it flash kernel, or wifi module or sound things, we include this prop in the script
Can anyone create this script?
[EDIT]
Many Thanks to Firerat who mades the script, and a little to me, who has the idea!
So the script is here:
Code:
#!/sbin/sh
# Idea : Artifex14
# script : Firerat => THE BEST!
# 28.06.10
ram=`free|awk '/Mem/ { print $2 }'`
if [ "ram" -gt "97884" ];
then
model=32a
echo "32a"
else
model=32b
echo "This device is a 32b"
fi
if [ "model" = "32a" ];
then
ln -s /tmp/boot.img /tmp/boot32a.img
ln -s /dev/null /tmp/boot32b.img
else
ln -s /tmp/boot.img /tmp/boot32b.img
ln -s /dev/null /tmp/boot32a.img
fi

I thought about this too. It could be done at the time the rom is flashed, but up to now I only know how to make update-script, not updater-script or update-binary. You could pack all sorts of boot images, and then, say, a system-dream, system-sapphire, and system-magic folder and depending on the board version property, flash the appropriate versions of files, at least in theory that should work, plus it prevents you from having to flash extra files just for cross-device compatibility.

jubeh said:
I thought about this too. It could be done at the time the rom is flashed, but up to now I only know how to make update-script, not updater-script or update-binary. You could pack all sorts of boot images, and then, say, a system-dream, system-sapphire, and system-magic folder and depending on the board version property, flash the appropriate versions of files, at least in theory that should work, plus it prevents you from having to flash extra files just for cross-device compatibility.
Click to expand...
Click to collapse
Can you do the script? For the updaterscript, it's OK!

et a script to run
Code:
free|awk '/Mem/ { print $2 }'
and test that, e.g.
Code:
#!/sbin/sh
# KernelPrep.sh
ram=`free|awk '/Mem/ { print $2 }'`
if [ "ram" -gt "97884" ];
then
model=32a
else
model=32b
fi
if [ "model" = "32a" ];
then
ln -s /tmp/boot.img /tmp/boot32a.img
ln -s /dev/null /tmp/boot32b.img
else
ln -s /tmp/boot.img /tmp/boot32b.img
ln -s /dev/null /tmp/boot32a.img
fi
get your updater script to run that, then copy your kernels to /tmp/
Code:
package_extract_dir("kernels", "/tmp");
or
Code:
copy_dir PACKAGE:kernels TMP:
next you can
Code:
write_raw_image("/tmp/boot.img", "boot"),
or
Code:
write_raw_image TMP:boot.img BOOT:
edit:
ps, you don't really need the second if statement, but its easier to read like that
oops , nearly forgot about the kernel modules
Code:
mount /system
install -d /system/lib/modules
ln -s /system/lib/modules /tmp/modules32a
ln -s /dev/null /tmp/modules32b

Firerat said:
et a script to run
Code:
free|awk '/Mem/ { print $2 }'
and test that, e.g.
Code:
#!/sbin/sh
# KernelPrep.sh
ram=`free|awk '/Mem/ { print $2 }'`
if [ "ram" -gt "97884" ];
then
model=32a
else
model=32b
fi
if [ "model" = "32a" ];
then
ln -s /tmp/boot.img /tmp/boot32a.img
ln -s /dev/null /tmp/boot32b.img
else
ln -s /tmp/boot.img /tmp/boot32b.img
ln -s /dev/null /tmp/boot32a.img
fi
get your updater script to run that, then copy your kernels to /tmp/
Code:
package_extract_dir("kernels", "/tmp");
or
Code:
copy_dir PACKAGE:kernels TMP:
next you can
Code:
write_raw_image("/tmp/boot.img", "boot"),
or
Code:
write_raw_image TMP:boot.img BOOT:
edit:
ps, you don't really need the second if statement, but its easier to read like that
oops , nearly forgot about the kernel modules
Code:
mount /system
install -d /system/lib/modules
ln -s /system/lib/modules /tmp/modules32a
ln -s /dev/null /tmp/modules32b
Click to expand...
Click to collapse
I'll try that, THANK!

oops typo
if [ "ram" -gt "97884" ];
should be
if [ "$ram" -gt "97884" ];

Problem with oprofile on htc desire (bravo)

Hi All.
I have been trying to get oprofile to work on an htc desire. I am running an unlocked phone purchased in the fall of 2010. I have built a custom kernel based on a snapshot of the dream team kernel (also from fall 2010). Android infrastructure layer is cyanogenmod 6.0.1. I know most of this is pretty old and I may be updating in the next few months, but for the most part this combination has been working for me so I plan to keep it until I find a compelling reason to change (broken feature I need that is fixed in a newer version etc).
My goal at this point is to profile a custom Linux application (no java involved, no NDK) we have developed for the phone. The application runs, but we need to improve performance of the 'system'. gprof has given us a lot of information but now we want the data you get from oprofile (valgrind gives us a pretty clean bill of health).
The process so far:
I have ported critical changes from the latest opcontrol that properly set file permissions etc.
Rebuilt kernel with profiling support turned on
fixed a set of bugs in cpuid processing. The Cortex-A8 CPU on the HTC desire reports a cpuid of 0x510f00f2 which was not supported in perf_event.c. FYI, arch/arm/kernel/setup.c has a very different mechanism for determining CPU type.
When I run opcontrol to setup and start oprofile(d), everything seems to be working. oprofilefs loads up properly and oprofiled is running but I get no samples.
I instrumented the kernel code (pmu.c etc) to see where things go wrong and found that there are no calls to pmu_device_probe which is the only code that sets up the pmu_devices array.
Sample output of instrumented code:
<6>[ 5.424957] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
<6>[ 160.288909] PMU: reserve_pmu: pmu_devices[device] is NULL. device - 0
<4>[ 160.289001] hw perfevents: unable to reserve pmu
At this point I am at a loss for where to look next. Does anyone know what code on the HTC Desire is supposed to call pmu_device_probe? I can only assume that some function is being told about potential hardware and calling probe functions to validate that the hardware is actually present and functioning. I do not know where to find this code on the desire (I come from a custom hardware world where we used ltib). Can anyone point me in the right direction? Has anyone gotten oprofile to work on the HTC Desire?

Problem with oprofile on htc desire (bravo) - Resolved
I have gotten oprofile to work on a 2.6.35 based teamdesire kernel. I have included the sed lines from my scripts and a set of files I added to arc/arm/kernel.
In essence, the stock kernel does not recognize the scorpion cpu and the init.bravo file does not create an arm-pmu device to manage the Qualcomm PMU hardware. In early March Qualcomm published a patch to the 2.6.38 kernel that added partial scorpion support. That patch plus other changes is included in the attached files and implemented in the sed script snippets I have included here.
When the scripts are done you can control builing oprofile support by using the .config.oprofile vs .config.no.oprofile kernel config files
Here is what I do to create a report. NOTE: In my architecture I do not use opimport. It seems that opreport in ubuntu 10.04 LTS can read the arm files just fine. NOTE2: In my system adb is disabled so I cannot use adb pull (or I would).
set up the profiler
opcontrol --setup --event=CPU_CYCLES:15000:::1:1
start the profiler
opcontrol --start
stop the profiler - saves samples to ram
opcontrol --stop
copy the samples to the sdcard
cd /sdcard
mkdir oprofileSamples
cp -r /data/oprofile /sdcard/oprofileSamples/oprofile
move the files to the build machine (It MUST be the machine on which the files where built)
turn off the phone and move the sdcard to a computer
cp -r /sdcard/oprofileSamples/oprofile /someplaceOnTheBuildMachine/oprofileSamples/oprofile
Open up the update file and extract the Android environment to a single area. There are instructions on the web telling you how to do this
now get your report
cd /someplaceOnTheBuildMachine/oprofileSamples/oprofile - In this directory you should have a samples subdir and you should have an abi file.
opreport --symbols -g --session-dir=. -R /LocationOnTheBuildMachineYouHaveYourOutput/android/debug/image
###############################
# changes to the Android SDK to support oprofile
sed -i 's/ARM V7 PMNC", "arm\/armv7", CPU_ARM_V7, 5 },/ARM V7 PMNC", "arm\/armv7", CPU_ARM_V7, 5 },\
{ "ARM V7 SCORPION", "arm\/scorpion", CPU_ARM_V7, 5 },\
{ "ARM V7 SCORPIONMP", "arm\/scorpionMP", CPU_ARM_V7, 5 },/g' $SYSTEM_PATH/external/oprofile/libop/op_cpu_type.c || exit
sed -i 's/if (mkdir(OP_DATA_DIR, 755)) {/if (mkdir(OP_DATA_DIR, 0755)) {/g' $SYSTEM_PATH/external/oprofile/opcontrol/opcontrol.cpp || exit
sed -i 's/if (mkdir(OP_DATA_DIR"\/samples", 644)) {/if (mkdir(OP_DATA_DIR"\/samples", 0755)) {/g' $SYSTEM_PATH/external/oprofile/opcontrol/opcontrol.cpp || exit
sed -i 's/if (mkdir(OP_DRIVER_BASE, 644)) {/if (mkdir(OP_DRIVER_BASE, 644)) {\
if( EEXIST != errno )\
{/g' $SYSTEM_PATH/external/oprofile/opcontrol/opcontrol.cpp || exit
sed -i 's/if (system("mount -t oprofilefs nodev "OP_DRIVER_BASE)) {/}\
\
system("umount "OP_DRIVER_BASE);\
if (system("mount -t oprofilefs nodev "OP_DRIVER_BASE)) {/g' $SYSTEM_PATH/external/oprofile/opcontrol/opcontrol.cpp || exit
echo "Got here"
sed -i 's/python2.4 -E/python2 -E/g' $SYSTEM_PATH/external/oprofile/opimport_pull || exit
sed -i 's/\[-s serial_number\] \[-r\]/\[-s serial_number\] \[-i indir\] \[-r\]/g' $SYSTEM_PATH/external/oprofile/opimport_pull || exit
sed -i 's/serial_number: the device being profiled"/serial_number: the device being profiled"\
print " -i indir: directory on the host from which to read sample data"/g' $SYSTEM_PATH/external/oprofile/opimport_pull || exit
sed -i 's/"x86_64"/"x86_64_IgnoreMe"/g' $SYSTEM_PATH/external/oprofile/opimport_pull || exit
sed -i 's/arch_path = ""/arch_path = ""\
\
raw_samples_dir = "raw_samples"/g' $SYSTEM_PATH/external/oprofile/opimport_pull || exit
sed -i 's/if sys.argv\[1\] == "-s":/if (sys.argv\[1\] == "-s"):/g' $SYSTEM_PATH/external/oprofile/opimport_pull || exit
sed -i 's/os.makedirs(output_dir)/os.makedirs( output_dir + "\/" + raw_samples_dir )/g' $SYSTEM_PATH/external/oprofile/opimport_pull || exit
sed -i 's/if sys.argv\[argv_next\] == "-r" :/if sys.argv\[argv_next\] == "-i" :\
input_dir = "%s" % sys.argv\[argv_next+1\]\
print " input dir = ", input_dir\
skip_pull = 1\
argv_next = argv_next + 2\
else:\
skip_pull = 0\
input_dir = ""\
\
if sys.argv\[argv_next\] == "-r" :/g' $SYSTEM_PATH/external/oprofile/opimport_pull || exit
sed -i 's/output_dir = sys.argv\[argv_next+1\]/output_dir = sys.argv\[argv_next+1\]\
argv_next = argv_next + 1/g' $SYSTEM_PATH/external/oprofile/opimport_pull || exit
sed -i 's/get the samples off the phone/\
if (skip_pull == 1) :\
result = os.system("cp -r %s\/* %s\/raw_samples"\
" > \/dev\/null 2>\&1" % (input_dir, output_dir))\
if result != 0:\
print "failure to copy %s\/* %s\/raw_samples\/." % (input_dir, output_dir)\
sys.exit(1)\
else:/g' $SYSTEM_PATH/external/oprofile/opimport_pull || exit
sed -i 's/f -name \\\*all")/f -name \\\*\\\.\\\*\\\.\\\*")/g' $SYSTEM_PATH/external/oprofile/opimport_pull || exit
# end changes to the Android SDK support oprofile
###############################
###############################
# changes to the 2.6.35 team desire kernel support oprofile
sed -i 's,return "arm/armv7-ca9";,return "arm/armv7-ca9"; \
case ARM_PERF_PMU_ID_SCORPION: \
return "arm/scorpion"; \
case ARM_PERF_PMU_ID_SCORPIONMP: \
return "arm/scorpion-mp"; ,g' $KERNEL_PATH/arch/arm/oprofile/common.c || exit
sed -i 's/ARM_PERF_PMU_ID_CA9,/ARM_PERF_PMU_ID_CA9, \
ARM_PERF_PMU_ID_SCORPION,\
ARM_PERF_PMU_ID_SCORPIONMP,/g' $KERNEL_PATH/arch/arm/include/asm/perf_event.h || exit
cd $BUILD_OUTPUT_PATH || exit
svn export -N svn+ssh://[email protected]/common/svn/repos/infrastructure/vendor_src/android/$ANDROID_VERSION/$KERNEL_VENDOR-$MODEL-perf_event-patch >> /dev/null || exit
cd $KERNEL_PATH/arch/arm/kernel || exit
rm -f perf_event.*
tar -xf $BUILD_OUTPUT_PATH/$KERNEL_VENDOR-$MODEL-perf_event-patch || exit
cp $KERNEL_PATH/.config $KERNEL_PATH/.config.no.oprofile || exit
cp $KERNEL_PATH/.config $KERNEL_PATH/.config.oprofile || exit
sed -i 's/# CONFIG_PERF_EVENTS is not set/CONFIG_PERF_EVENTS=y/g' $KERNEL_PATH/.config.oprofile || exit
sed -i 's/# CONFIG_PERF_COUNTERS is not set/CONFIG_PERF_COUNTERS=y\
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set/g' $KERNEL_PATH/.config.oprofile || exit
sed -i 's/# CONFIG_PROFILING is not set/CONFIG_PROFILING=y\
CONFIG_OPROFILE=y/g' $KERNEL_PATH/.config.oprofile || exit
sed -i 's/# CONFIG_HIGHMEM is not set/# CONFIG_HIGHMEM is not set\
CONFIG_HW_PERF_EVENTS=y/g' $KERNEL_PATH/.config.oprofile || exit
sed -i 's/CONFIG_HAVE_FUNCTION_TRACER=y/CONFIG_HAVE_FUNCTION_TRACER=y\
CONFIG_RING_BUFFER=y\
CONFIG_RING_BUFFER_ALLOW_SWAP=y/g' $KERNEL_PATH/.config.oprofile || exit
# end changes to support oprofile
###############################
Good luck and happy tuning.

TWRP recovery image with my porting kernel for Xiaomi Redmi 3S

Test only!
Don't flash to phone.
Try with "fastboot boot recovery.img".
Pure TWRP:
https://github.com/yangyangnau/andr....0.2-with-linux-3.18.20-g39aa441-for-redmi-3s
TWRP with cofface‘s patch:
https://github.com/yangyangnau/andr...face-with-linux-3.18.20-g39aa441-for-redmi-3s
Please rename to recovery.img after download.
If you want remove dm-verity, you can cook twrp yourself or look here http://en.miui.com/thread-310923-1-1.html.
I'm porting kernel for redmi 3s.
https://github.com/yangyangnau/android_kernel_xiaomi_msm8937
http://forum.xda-developers.com/redmi-3/development/port-linux-kernel-source-xiaomi-redmi3s-t3469965

get stock ROM adb root shell for kernel testing
boot.img from stock ROM.
kernel wlan.ko from your kernel.
twrp-recovery.img from TWRP.
mkboot script from https://github.com/xiaolu/mkbootimg_tools.
Code:
#!/bin/sh
[ -f boot.img ] || exit 0
[ -f kernel ] || exit 0
[ -f wlan.ko ] || exit 0
[ -f twrp-recovery.img ] || exit 0
mkboot boot.img myboot
cp -a kernel myboot/
sed -i -e '/ro.adb.secure=/s+1+0+' \
-e '/ro.secure=/s+1+0+' \
-e '/security.perf_harden=/s+1+0+' \
-e '/ro.allow.mock.location=/s+0+1+' \
-e '/ro.debuggable/s+0+1+' \
-e '/persist.sys.usb.config=/s+none+adb+' \
-e '/ro.secureboot.devicelock/s/^/#/' myboot/ramdisk/default.prop
#echo 'persist.service.adb.enable=1' >> myboot/ramdisk/default.prop
#echo 'persist.service.debuggable=1' >> myboot/ramdisk/default.prop
cat ~/.android/adbkey.pub >> myboot/ramdisk/bin/adb_keys
sed -i "/cmd_line=/s/'$/ androidboot.selinux=permissive'/" myboot/img_info
sed -i -e 's+,verify++g' \
-e 's+forceencrypt+encryptable+g' myboot/ramdisk/fstab.qcom
mkboot myboot myboot.img
fastboot flash boot myboot.img
mkboot twrp-recovery.img twrp-recovery
cp -a twrp-recovery/ramdisk/supersu/su .
fastboot boot twrp-recovery.img
sleep 10s
adb shell mount /system
adb push su /system/bin/su
adb push su /system/xbin/su
adb shell mv /system/lib/modules/wlan.ko{,-}
adb push wlan.ko /system/lib/modules/wlan.ko
adb shell mv /system/bin/install-recovery.sh{,-}
adb shell umount /system
rm -rf myboot twrp-recovery
#adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
get adb root shell
Code:
adb shell
su -

Someone had tested? Its ok?

plz port Radon kernal for redmi 3s

how to boot into recovery? is it same twrp by flour_mo

Tried to boot the both versions. It boots, but wants some password to encrypt data. TWRP I have installed can decrypt data without wanting me to enter password (and I don't know what password should it be)

Plz bring custom kernel for land # devs

Good news. We finally booted a 4.9 on land

build error

I' m trying to build resurrection remix oreo rom for moto c plus, I'm getting error when I give input .build/envsetup.sh && brunch m_e_arm-userdebug
Code:
[592/1070] including ./packages/apps/ResurrectionOTA/Android.mk ...
cp: illegal option -- u
usage: cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file target_file
cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file ... target_directory
[739/1070] including ./system/sepolicy/Android.mk ...
./system/sepolicy/Android.mk:99: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
[1070/1070] including ./vendor/rr/prebuilt/common/Android.mk ...
[100% 1/1] build bacon
FAILED: bacon
/bin/bash -c "(mv /Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/.zip ) && (mv /Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/system/etc/RR/Changelog.txt /Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/-Changelog.txt ) && (md5 -q /Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/.zip | sed \"s|/Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/||\" > /Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/.zip.md5sum ) && (echo \"Package Complete: /Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/.zip\" >&2 ) && (./vendor/rr/tools/rr.sh )"
usage: mv [-f | -i | -n] [-v] source target
mv [-f | -i | -n] [-v] source ... directory
ninja: build stopped: subcommand failed.
15:48:04 ninja failed with: exit status 1
#### failed to build some targets (09:51 (mm:ss)) ####

Android build error

I'm trying to build android from the Google AOSP source code, but I get this error. Somebody please help
```
[100% 1/1] out/host/linux-x86/bin/soong_build out/soong/build.ninja
FAILED: out/soong/build.ninja
cd "$(dirname "out/host/linux-x86/bin/soong_build")" && BUILDER="$PWD/$(basename "out/host/linux-x86/bin/soong_build")" && cd / && env -i "$BUILDER" --top "$TOP" --soong_out "out/soong" --out "out" -o out/soong/build.ninja --globListDir build --globFile out/soong/globs-build.ninja -t -l out/.module_paths/Android.bp.list --available_env out/soong/soong.environment.available --used_env out/soong/soong.environment.used.build Android.bp
error: test/vts-testcase/vndk/Android.bp:19:1: "vts_vndk_utils" depends on undefined module "vndk_lib_lists"
10:45:14 soong bootstrap failed with: exit status 1
#### failed to build some targets (25 seconds) ####
```