Recent content by Untitled87

When trying to make the GSM work on the Omni, I found a easy solution for this issue: Just copy the GSM lib (in /system/blobs/gsm/*) of the Omni ROM to /system/, and it worked. For those who are afraid of flashing a T-mobile ROM, flash this update and enjoy your GSM! I tested on Omni but it may...

I'm using the stock Kit kat NAE on my Sprint L720. So, can I flash the kernel on it?

RenderBroken: I saw that you updated the toolchain to Linaro 201401. Would you tell me where to get the prebuilt of this toolchain. I've tried to build this one but it failed.... I found a prebuilt verion here, Christopher83's Toolchain, but dont know whether it is the right one?

It's improved the Antutu score a bit for me. I've test it for a while, I will tell you more in tomorrow...

I've built my homemade with: - Sabermod arm-linux-androideabi-4.8.3 201311 Toolchain for the ROM code - Linaro arm-eabi-4.7 201311 toolchain for the kernel. - add the zzmoove governor... Is there any interest in trying this? omni-4.4.2-20140226-i777-HOMEMADE_ROM.zip...

Android-Andi: I've testes the 2nd way, it does not work.... Because the file https://github.com/omnirom/android_kernel_samsung_smdk4412/blob/android-4.4/arch/arm/configs/custom_i777_defconfig is somehow different from your defconfig file, it doesn't contain the field like...

Android-Andi: I'm building a Omni homemade for my S2 I777 and got the issue that the hardware keyboard auto enabled after every reboot. So, would you tell me how to solve this kind of problem? Thanks....

infected_: I'm building the Omni for my I777. When I changed the toolchain from 4.7 to 4.8 for compiling the ROM (like you), it works fine with Dalvik but stucks in the Omni logo if I switch to ART. Would you tell me how to find out what causes that problem? I keep everything as default, just...

Here is my built of Render's kernel with SM 4.7 (tested on my I777). I just tune the zzmoove a bit RenderKernel_CM11TWRP RenderKernel_OmniTWRP RenderKernel_CM11CWM RenderKernel_OmniCWM

From now, I haven't test your kernel with my tuned zzmoove. Maybe tomorrow we have the result... I've also test three versions of the SM toolchain (2 4.8 verions and 1 4.7 version), and the only one work successfully is the arm_sabermod-arm-eabi-4.7. So, anyone who attempt to build Render's...

Lolz, I just do this type of these things for fun, man... BTW, is it OK if I reuse the lights.exynos4.so in your CM11 (I built it before) in your kernel, Render?

I've found out that the Toolchain causes this problem. My mistake is set the Toolchain to the sabermod-arm-linux-androideabi-4.8 instead of the android_prebuilts_gcc_linux-x86_arm_sabermod-arm-eabi-4.8 (with the AOSP patches) Update: I rebuilt the kernel with the SM 4.7 and it sucessfully boot...

I dont know. In the next time, can you flash the kernel and after that clear cache, dalvil without reboot into the recovery? Maybe I should check the different betweent the CM11 CWM and the Omni TWRP Update: I added mr-cook 's kernel cleaner to the kernel install script. Hope it woks...

Which version did you flash the Omni_CWM or the CM11_CWM, royahaun? I myself install the Omni_TWRP but it stucked at the splash screen

razen_kain, I tried myself on my I777, it also stuck at the flash screen. This kind problem is out of my knowledge. Maybe because the SM 4.8 Toolchian, or the missing of lights.exynos4.so (not sure) Render, would tell me which gcc compiler should be used in the SM 4.8 among...