Can you permanently throttle cpu speed, with cpupower or cpufreq, I don’t know which package is available on Ubuntu.
In Windows you can undervolt the CPU. This leads to a lower core temperature and this postpones (or dismisses if you are lucky) the time when the CPU falls back t it’s initial speed. In Ubuntu you would need a special Kernel which would allow this. I have been looking for it but didn’t find any. On Windows however, I could undervold my i7 processor quite a bit, still running stable.
By the way: can you post an ls -la of the output folder? I would like to
check whether we have the same file sizes for the .img files.
You would imagine that in the year 2016 CPU/thermal management should work out of the box without disturbing any integrity… I mean, it’s not 1980 anymore… *shaking the head*
Anyway, cpufreq is available on Ubuntu and I’ve set my i5 it to 900Mhz:
simon@laptop:~$ sudo cpufreq-set -r -u 1GHz
simon@laptop:~$ sudo cpufreq-set -r -d 1GHz
simon@laptop:~$ cpufreq-info | grep "momentane Taktfre"
momentane Taktfrequenz ist 900 MHz.
momentane Taktfrequenz ist 900 MHz.
momentane Taktfrequenz ist 900 MHz.
momentane Taktfrequenz ist 900 MHz.
simon@laptop:~$
(sorry for the German) @USB-2: It seems you don’t need any special kernel or such. And probably better use sha instead of the file size to compare files.
I’ve started another round of compilation but at 900MHz it probably will take a little longer…
[QUOTE]klaus@klaus-virtual-machine:~/fairphone_os/out/target/product/FP2$ ls -la
total 668308
drwxrwxr-x 12 klaus klaus 4096 Jan 1 21:01 .
drwxrwxr-x 4 klaus klaus 4096 Dez 31 16:53 …
-rw-rw-r-- 1 klaus klaus 10 Dez 31 16:16 android-info.txt
-rw-rw-r-- 1 klaus klaus 15257600 Jan 1 17:09 boot.img
-rw-rw-r-- 1 klaus klaus 15255552 Jan 1 17:08 boot.img.nonsecure
drwxrwxr-x 2 klaus klaus 4096 Dez 31 21:43 cache
-rw-r–r-- 1 klaus klaus 12820796 Dez 31 21:43 cache.img
-rw-rw-r-- 1 klaus klaus 61394 Jan 1 20:59 clean_steps.mk
drwxrwxr-x 5 klaus klaus 4096 Jan 1 02:25 data
-rw-r–r-- 1 klaus klaus 5828608 Jan 1 17:08 dt.img
-rw-rw-r-- 1 klaus klaus 549928 Jan 1 17:06 emmc_appsboot.mbn
-rwxrwxr-x 1 klaus klaus 549888 Jan 1 17:06 emmc_appsboot.raw
-rw-rw-r-- 1 klaus klaus 549928 Jan 1 17:06 EMMCBOOT.MBN
drwxrwxr-x 2 klaus klaus 4096 Dez 31 18:58 fake_packages
drwxrwxr-x 5 klaus klaus 4096 Dez 31 20:31 gen
-rw-rw-r-- 1 klaus klaus 111514 Jan 1 17:08 installed-files.txt
-rwxrwxr-x 1 klaus klaus 6601296 Jan 1 17:08 kernel
drwxrwxr-x 21 klaus klaus 4096 Jan 1 03:18 obj
drwx------ 4 klaus klaus 4096 Dez 31 16:18 persist
-rw-r–r-- 1 klaus klaus 5088376 Dez 31 20:11 persist.img
-rw-rw-r-- 1 klaus klaus 328 Jan 1 20:59 previous_build_config.mk
-rw-rw-r-- 1 klaus klaus 2821353 Jan 1 13:19 ramdisk.img
-rw-rw-r-- 1 klaus klaus 1408248 Jan 1 17:08 ramdisk-recovery.img
drwxrwxr-x 3 klaus klaus 4096 Jan 1 17:08 recovery
-rw-rw-r-- 1 klaus klaus 13844480 Jan 1 17:09 recovery.img
-rw-rw-r-- 1 klaus klaus 13842432 Jan 1 17:08 recovery.img.nonsecure
drwxrwxr-x 9 klaus klaus 4096 Jan 1 13:16 root
-rw-rw-r-- 1 klaus klaus 6221312 Dez 31 16:18 splash.img
drwxrwxr-x 5 klaus klaus 4096 Dez 31 21:45 symbols
drwxrwxr-x 14 klaus klaus 4096 Dez 31 19:58 system
-rw-r–r-- 1 klaus klaus 440528764 Jan 1 17:09 system.img
-rw-r–r-- 1 klaus klaus 142911480 Jan 1 17:09 userdata.img
klaus@klaus-virtual-machine:~/fairphone_os/out/target/product/FP2$
[/QUOTE]
But I get this while booting:
[QUOTE]
D/AndroidRuntime( 1166): >>>>>> START com.android.internal.os.ZygoteInit uid 0 <<<<<<
E/JniInvocation( 1166): Failed to dlopen libart.so: dlopen failed: library “libart.so” not found
D/AndroidRuntime( 1166): CheckJNI is OFF
F/libc ( 1166): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 1166 (zygote)
I/mediaserver( 1165): ServiceManager: 0xb58700c0
I/AudioFlinger( 1165): Using default 3000 mSec as standby time.
I/ServiceManager( 1165): Waiting for service batterystats…
I/DEBUG ( 261): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 261): Build fingerprint: 'Fairphone/FP2/FP2:5.1/FP2/klaus12311418:userdebug/test-keys’
I/DEBUG ( 261): Revision: '0’
I/DEBUG ( 261): ABI: 'arm’
I/DEBUG ( 261): pid: 1166, tid: 1166, name: zygote >>> zygote <<<
I/DEBUG ( 261): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
I/DEBUG ( 261): r0 b6f9c4c8 r1 be8c674c r2 be8c5758 r3 00000000
I/DEBUG ( 261): r4 00000023 r5 00010004 r6 be8c5758 r7 00000000
I/DEBUG ( 261): r8 be8c6694 r9 be8c57c4 sl be8c57d8 fp b6f74101
I/DEBUG ( 261): ip b676cf88 sp be8c5740 lr b6f1e4a3 pc 00000000 cpsr a0000010
I/DEBUG ( 261):
I/DEBUG ( 261): backtrace:
I/DEBUG ( 261): #00 pc 00000000
I/DEBUG ( 261): #01 pc 0005c49f /system/lib/libandroid_runtime.so (android::AndroidRuntime::startVm(_JavaVM**, _JNIEnv**)+2286)
I/DEBUG ( 261): #02 pc 0005cae7 /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, android::Vectorandroid::String8 const&)+258)
I/DEBUG ( 261): #03 pc 00001675 /system/bin/app_process32
I/DEBUG ( 261): #04 pc 0000fec9 /system/lib/libc.so (__libc_init+44)
I/DEBUG ( 261): #05 pc 000017b0 /system/bin/app_process32
I/DEBUG ( 261):
I/DEBUG ( 261): Tombstone written to: /data/tombstones/tombstone_08
[/QUOTE]
and of course no successful boot…#
I didn’t have 8GB of free memory at the first run, so I started another one which needed only like 10 minutes to complete. Maybe this interruption caused another file size. Only Deus Ex Machina knows…
*ouch* did you try it on the phone or in an emulator? Can you still reset it to factory defaults or does the original OS get overwritten by flashing it?
Maybe it’s better to wait until the Fairphone Dev’s provide an “official” build, which is guaranteed to run – once the holidays are over…
I can only recommend to everybody: don’t flash anything before you made a Nandroid Backup. I don’t know if this is possible with the Fairphone’s original recvovery as I don’t have my phone yet…
Hi,
I can’t contribute to the programming/compiling issues but I already have the phone so I can at least say that there isn’t any option to do a backup in the original recovery.
The menu shows:
-reboot system now
-apply update from ADB
-wipe data/ factory reset
-wipe cache partition
-reboot to bootloader
-power down
-view recovery logs
-apply update from sdcard
I also tried the reboot-to-bootloader-option but the screen freezed and after 2mins I manually rebooted the phone. Repeated two times trying to enter bootloader with same results.
Finally I want to say that I’m quite excited and thankful that there already are people trying to provide a GMS-free ROM. Keep on!
Happy new year
As I’m an Android noob my idea might be rubbish, but maybe with adb a backup could have been taken with dd? anyway, if it is bricked already, it’s too late now anyway…
edit: obviously one of us could factory reset and then create a backup for you to restore (if there is no problem with serial numbers or such).
You could take a disk image with dd, yes. But right now I fail to see how to restore this image. Might be flashable, but I’m not sure. With TWRP this would be easier, but the fairphone recovery is quite simplistic.Will try a fresh build (which takes some time). So, as long as my device is bricked, I might as well test your builds
edit: or better, not the device is bricked, only system
No idea if adb is of any help there, if you can get into recovery mode and start an adb shell maybe, to restore the image. As I said, I’m new to android…
