Related
Radio (BP): OLYMPUSBP_01.92.00R
Release Date: Apr 29, 2011
Webtop version : EMARA Retail generic: OSHWT_U1_6.54.0
http://forum.androidfan.ru/index.php?showtopic=8052
Are there any details about the origin of this file?
Sent from my MB860 using Tapatalk
going to try as soon as its downloaded hopefully works okay...OLYEM U4 1.4.2 worked hope OLYEM U4 2.1.1 works
be cool if it was gingerbread
Is this for bell or att?
Sent from my Motorola Olympus
Flashing as we speak...
Flash was successful. Default language was set to French. Motoblur register was able to be skipped.
Just trying to root right now.
thgi you are on a bell atrix probably, by the name of the flash file it suggests that its for the bell versions and not for the att versions... what is the kernel and android version tho thgi?
I'm downloading now, just curious as to what it is before I flash.. Tghi, look forward to what this sbf does... and of course if it is for Bell I wouldn't but I figure doesn't hurt to download
crnkoj said:
thgi you are on a bell atrix probably, by the name of the flash file it suggests that its for the bell versions and not for the att versions... what is the kernel and android version tho thgi?
Click to expand...
Click to collapse
Yes, I am on a Bell Atrix.
Root (permanent) was successful: http://forum.xda-developers.com/showthread.php?t=1045634
build.prop and default.prop for this ROM is as follows:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=OLYEM_U4_2.1.1
ro.build.display.id=OLYEM_U4_2.1.1
ro.build.version.incremental=4009634
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.2
ro.build.date=Fri Apr 29 00:01:01 CST 2011
ro.build.date.utc=1304006461
ro.build.type=user
ro.build.user=e13392
ro.build.host=zch68lnxdroid46
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=MB860
ro.product.model.internal=MB860
ro.product.brand=MOTO
ro.product.name=MB860_RTFR
ro.product.device=olympus
ro.product.board=olympus
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=fr
ro.product.locale.region=FR
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=olyem
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=olympus-user 2.2.2 OLYEM_U4_2.1.1 ota-rel-keys,release-keys
ro.build.fingerprint=MOTO/MB860_RTFR/olympus/olympus:2.2.2/OLYEM_U4_2.1.1/4009634:user/ota-rel-keys,release-keys
# end build properties
#BEGIN ikolympus-145 ndkj78 04/29/10 add properties for RIL
rild.libpath=/system/lib/libmoto_ril.so
#ikolymp-874 increment channels to support EFEM
persist.ril.mux.noofchannels=9
persist.ril.mux.ttydevice=/dev/ttyHS3
#Begin IKOLYMP-2372 jqc837 31.aug.10 Short music file set as ringtone does not play in loop when receiving incoming call
#Begin IKOLYMP-425 jqc837 31.aug.10 ro.cdma.home.operator.numeric should not be set
ro.telephony.call_ring.multiple=false
#End IKOLYMP-2372 IKOLYMP-425
#added property for modem ikolympus-203
persist.ril.modem.ttydevice=/dev/ttySPI0
#added property for default RIL mode to be UMTS ikolymp2180
persist.ril.modem.mode=2
#IKOLYMP-4257 add feature GENERIC_OEM_HOOK flag
#IKOLYMP-4894 add feature MUX_PANIC_NOTIF flag
#IKOLYMP-5747 add feature BDTSE_FOR_DTMF flag
#IKOLYMP-7714 Remove feature BDTSE_FOR_DTMF. Revert to DTSE for DTMF
#IKOLYMP-8033 Restore BDTSE_FOR_DTMF. Remove GENERIC_OEM_HOOK (no longer used)
persist.ril.features=0x24
#IKOLYMP-9894 Increase the PPP max failure threshold to 12
#IKOLYMP-10006 Increase the PPP max failure threshold to 16
persist.ril.pppd.start.fail.max=16
#end
#IKOLYMP-9157 libgps send_rds retry number+1
persist.libgps.send.rds.retry=4
ro.hdmi.mirror.enable=false
ro.hdmi.default.app=
hw.overlay.path.config=
# temporary enable AT&T NSUI feature from system prop.
# This should be removed once Flex is enabled in Olympus.
ro.mot.FTR.NSUI=false
# for larger screen support
# 3.75" WVGA == 248dpi
# 4.0" qHD == 275dpi
ro.sf.lcd_density=240
dalvik.vm.heapsize=32m
# Enable FP sensor
ro.mot.hw.fingerprint.enable=1
# required for UDD backup tcmd
ro.mot.hw.calibratedImager=1
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
#For enabling Wispr Feature
#disable att wifi hotspot, IKOLYEM-254
ro.mot.wifi.hotspot=0
# To enable Google Froyo Tethering (USB & WIFI hotspot)
ro.tether.denied=false
# To set wifi (AP) driver's firmware path
ro.wifi-ap.fw-path=/system/etc/firmware/wifi/sdio-g-cdc-roml-reclaim-wme-apsta-idsup-idauth.bin
# Enabling EONS feature IKOLYMP-1962
persist.cust.tel.eons=1
ro.opengles.version = 131072
# For docked touchpad keyboard map
android.keylayout.evfwd=/system/usr/keylayout/evfwd.kl
android.keychar.evfwd=/system/usr/keychars/evfwd.kcm.bin
# To send 70 touch events per second
windowsmgr.max_events_per_sec = 70
debug.mot.extwmlog=0
debug.mot.extamlog=0
#proximit sensor screen off delay
mot.proximity.delay=450
#proximit sensor disable touch distance
mot.proximity.distance=60
# Enable HAC support
ro.mot.hw.HAC=1
# BEGIN Motorola, w30250, 4-Nov-2010, IKOLYMP-6198 turn on entitlement check
# BEGIN Motorola, e13085, 9-Dec-2010, IKOLYHKTW-1 turn off entitlement check
ro.mot.entitlement_check=false
# END
# END
# The property "ro.camera.sound.forced" is defined by google.
# Use this property to decide whether camera shutter tone is forced: 1 forced; 0 not-forced.
# BEGIN Motorola, e7482c, 1-Dec-2010, IKOLYEM-76
ro.camera.sound.forced=0
# BEGIN Motorola, w30495 IKOLYMP-9553, add property to control maximum number of hidden apps
ro.MAX_HIDDEN_APPS=50
# END
# BEGIN Motorola, e7482c IKOLYEM-486, add property to control if disable background data when making call
ro.mot.background_data.disabled=false
# BEGIN Motorola, w20919 IKOLYEM-993, add property to control if email auto config after skip the blur setting
ro.mot.auto.email=true
# END
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=false
ro.default_usb_mode=0
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.2_r9
ro.config.sync=no
ro.browser.useragent=0
gsm.sim.mot.simswap=1
ro.config.sync=no
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.wma.enabled=1
ro.media.enc.hprof.file.format=3gp
ro.media.enc.hprof.aud.hz=44100
ro.media.enc.hprof.aud.ch=2
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.hprof.aud.bps=128000
ro.media.enc.hprof.vid.bps=4000000
ro.media.enc.hprof.vid.width=1280
ro.media.enc.hprof.vid.height=720
ro.media.enc.hprof.codec.vid=h264
ro.media.enc.hprof.vid.fps=30
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientid=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/MotoMB860/profile/MotoMB860.rdf
ro.build.version.full=Blur_Version.4.2.11.MB860.Retail.en.FR
ro.config.ringtone=Piano.ogg
ro.config.notification_sound=Kinetic_Bell.ogg
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.locationfeatures=1
ro.com.google.clientidbase.ms=android-motorola
thanks for the info thgi, i got one more little question/request if you got the time. Could you please copy the three wifi driver binarys from /system/etc/firmware/wifi/ zip them up and upload them somewhere/pm me with a link or something, i would really like to try if they fix the wifi issue that some of us see on unlocked att devices.
what languages are there?
Here is the wifi drivers.
aleve1983 said:
what languages are there?
Click to expand...
Click to collapse
Languages are: German, English, Spanish, French, Italian, Portugese
Thank you very much!
edit:
just checked them it seems they are the same version as on the att roms , anyhow thanks for the effort
is it flashable to att atrix
will it help with enabling GPRS outside america ?
http://gititbit.ch/ogsd1 mirror
does anyone know to import a language firmware?
more info on new features? bugs? and such?
Carrier name still in notification bar?
android 2.2.2 or 2.2.1?
For some weeks I've been trying to set up an environment in which I'm able to compile the stock kernel for my LG2X on my own. Following various tips and hints were unsuccessful and several restarts were required until a kernel which was compiled on my own box was running on my phone. Since I had to patch together all the information because there was no complete guide available/findable, I'd like to list here all the steps from the beginning which I had to perform to boot my own compiled kernel. Maybe this is also useful for others. Note: again, this approach is for compiling STOCK kernel sources which are based on the public sources from LG. (The build process for CM is different and cannot be applied to stock kernels)
I began with a freshly installed Ubuntu 11.10 32bit (http://www.ubuntu.com/download/ubuntu/download) running in a VMware virtual machine. In it I entered a shell and switched to root to be able to perform the required actions:
Code:
sudo su -
The next step was to add the package-sources for the cross-compiler toolchain (see next step) and to bring the system up to the latest state.
Code:
add-apt-repository ppa:linaro-maintainers/toolchain
apt-get update
apt-get upgrade
This takes some time but after it's finished I installed the cross-compiler toolchain to be able to compile applications for the LGs ARM platform
Code:
apt-get install gcc-linaro
apt-get install gcc-linaro-arm-linux-gnueabi
After this I've been ready to begin with the source-works. I closed the root-shell and opened up a new one (required to make sure that all paths are correctly set and recognized again). Test it by executing
Code:
arm-linux-gnueabi-gcc --version
When this executed without error I started with downloading the sources for version 20q from http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP990 into a new directory.
When the file 'LGP990_Android_Gingerbread_V20Q.zip' had finished downloading I unzipped the complete package by
Code:
unzip LGP990_Android_Gingerbread_V20Q.zip
resulting in three files. A README, one .tar.gz with the ROM sources and finally one .tar.gz with the kernel sources. To unpack the kernel sources I issued
Code:
tar xvzf P990_Stardop_IFX_GingerBread_V20Q_KERNEL.tar.gz
and the complete LG 20q kernel sources were finally located in a new 'kernel' subdirectory.
The kernel sources themselves are not yet ready to be compiled. This is because LG most probably has a different/special build environment and our standard environment produces errors and unbootable kernels. Some patching is required to succeed to a running kernel.
Firstly the compilation options for the wireless module have to be tweaked as the default settings break compilation at some unused variables in the source. This is set to be just treated as warnings for the wireless-module by applying following patch:
Code:
diff -u -r original/kernel/drivers/net/wireless/bcm4329/Makefile kernel/drivers/net/wireless/bcm4329/Makefile
--- original/kernel/drivers/net/wireless/bcm4329/Makefile 2012-01-31 04:36:22.000000000 -0800
+++ kernel/drivers/net/wireless/bcm4329/Makefile 2012-02-14 11:41:59.972467559 -0800
@@ -53,7 +53,7 @@
-DBCMLXSDMMC \
-DBCMPLATFORM_BUS \
-DSDIO_ISR_THREAD \
- -Wall -Wstrict-prototypes -Werror \
+ -Wall -Wstrict-prototypes -Werror -Wno-unused-but-set-variable -Wno-array-bounds \
-I$(SRCROOT) \
-I$(SRCROOT)/include \
-I$(SRCROOT)/shared \
Also the main Makefile requires tuning to contain the proper compilation options to produce code which correctly runs on the phone (thanks to spica1234 for providing me with the correct options).
Code:
diff -u -r original/kernel/Makefile kernel/Makefile
--- original/kernel/Makefile 2012-01-31 04:36:21.000000000 -0800
+++ kernel/Makefile 2012-02-28 13:21:20.038003539 -0800
@@ -323,12 +323,12 @@
CHECKFLAGS := -D__linux__ -Dlinux -D__STDC__ -Dunix -D__unix__ \
-Wbitwise -Wno-return-void $(CF)
-MODFLAGS = -DMODULE
-CFLAGS_MODULE = $(MODFLAGS)
+MODFLAGS = -DMODULE -mfloat-abi=softfp -mfpu=vfpv3-d16 -mtune=cortex-a9 -march=armv7-a -fno-common -fsingle-precision-constant -fno-gcse -funsafe-math-optimizations -ffinite-math-only -fgcse-las -fgcse-sm -fivopts -fbtr-bb-exclusive -fvect-cost-model -fmodulo-sched -fmodulo-sched-allow-regmoves
+CFLAGS_MODULE = $(MODFLAGS)
AFLAGS_MODULE = $(MODFLAGS)
LDFLAGS_MODULE = -T $(srctree)/scripts/module-common.lds
-CFLAGS_KERNEL =
-AFLAGS_KERNEL =
+CFLAGS_KERNEL = -mfloat-abi=softfp -mfpu=vfpv3-d16 -mtune=cortex-a9 -march=armv7-a -fno-common -fsingle-precision-constant -fno-gcse -funsafe-math-optimizations -ffinite-math-only -fgcse-las -fgcse-sm -fivopts -fbtr-bb-exclusive -fvect-cost-model -fmodulo-sched -fmodulo-sched-allow-regmoves
+AFLAGS_KERNEL = -mfloat-abi=softfp -mfpu=vfpv3-d16 -mtune=cortex-a9 -march=armv7-a -fno-common -fsingle-precision-constant -fno-gcse -funsafe-math-optimizations -ffinite-math-only -fgcse-las -fgcse-sm -fivopts -fbtr-bb-exclusive -fvect-cost-model -fmodulo-sched -fmodulo-sched-allow-regmoves
CFLAGS_GCOV = -fprofile-arcs -ftest-coverage
# 20100705, [email protected],[LGE_START]
@@ -544,7 +544,8 @@
ifdef CONFIG_CC_OPTIMIZE_FOR_SIZE
KBUILD_CFLAGS += -Os
else
-KBUILD_CFLAGS += -O2
+KBUILD_CFLAGS += -Ofast
+KBUILD_CFLAGS += $(call cc-option, -Wno-unused-but-set-variable)
endif
We're not finished yet. We've to create the correct kernel configuration and (again) apply some patches. I'm not so sure about these changes but the kernel refused to boot on my phone without them. It is again provided by spica1234 and contains a number of changes. I did not research which of these changes allowed to boot since most of them are generally useful and I didn't do the work trying them out one-by-one.
Code:
make ARCH=arm star_ifx_defconfig
Code:
--- .config.orig 2012-02-28 13:22:09.322001449 -0800
+++ .config.spica_working 2012-03-02 08:41:21.757696988 -0800
@@ -1,7 +1,7 @@
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.32.9-HP_2X_Xtreme_RC12-RevOTF
-# Tue Feb 28 13:22:09 2012
+# Tue Feb 28 13:24:15 2012
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
@@ -56,16 +56,16 @@
CONFIG_LOG_BUF_SHIFT=18
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
-# CONFIG_RT_GROUP_SCHED is not set
+CONFIG_RT_GROUP_SCHED=y
# CONFIG_USER_SCHED is not set
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_CGROUP_NS is not set
-CONFIG_CGROUP_FREEZER=y
-CONFIG_CGROUP_DEVICE=y
+# CONFIG_CGROUP_FREEZER is not set
+# CONFIG_CGROUP_DEVICE is not set
# CONFIG_CPUSETS is not set
-CONFIG_CGROUP_CPUACCT=y
+# CONFIG_CGROUP_CPUACCT is not set
# CONFIG_RESOURCE_COUNTERS is not set
# CONFIG_SYSFS_DEPRECATED_V2 is not set
CONFIG_RELAY=y
@@ -121,7 +121,8 @@
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
-# CONFIG_SLOW_WORK is not set
+CONFIG_SLOW_WORK=y
+# CONFIG_SLOW_WORK_DEBUG is not set
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
@@ -146,10 +147,10 @@
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
-# CONFIG_DEFAULT_DEADLINE is not set
-CONFIG_DEFAULT_CFQ=y
+CONFIG_DEFAULT_DEADLINE=y
+# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
-CONFIG_DEFAULT_IOSCHED="cfq"
+CONFIG_DEFAULT_IOSCHED="deadline"
CONFIG_FREEZER=y
#
@@ -1676,16 +1677,25 @@
# File systems
#
CONFIG_EXT2_FS=y
-# CONFIG_EXT2_FS_XATTR is not set
-# CONFIG_EXT2_FS_XIP is not set
+CONFIG_EXT2_FS_XATTR=y
+# CONFIG_EXT2_FS_POSIX_ACL is not set
+# CONFIG_EXT2_FS_SECURITY is not set
+CONFIG_EXT2_FS_XIP=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_DEFAULTS_TO_ORDERED=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
-# CONFIG_EXT4_FS is not set
+CONFIG_EXT4_FS=y
+CONFIG_EXT4_FS_XATTR=y
+# CONFIG_EXT4_FS_POSIX_ACL is not set
+# CONFIG_EXT4_FS_SECURITY is not set
+# CONFIG_EXT4_DEBUG is not set
+CONFIG_FS_XIP=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
+CONFIG_JBD2=y
+# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
@@ -1769,7 +1779,22 @@
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
-# CONFIG_NETWORK_FILESYSTEMS is not set
+CONFIG_NETWORK_FILESYSTEMS=y
+# CONFIG_NFS_FS is not set
+# CONFIG_NFSD is not set
+CONFIG_SMB_FS=m
+# CONFIG_SMB_NLS_DEFAULT is not set
+CONFIG_CIFS=m
+# CONFIG_CIFS_STATS is not set
+# CONFIG_CIFS_WEAK_PW_HASH is not set
+# CONFIG_CIFS_UPCALL is not set
+# CONFIG_CIFS_XATTR is not set
+# CONFIG_CIFS_DEBUG2 is not set
+# CONFIG_CIFS_DFS_UPCALL is not set
+# CONFIG_CIFS_EXPERIMENTAL is not set
+# CONFIG_NCP_FS is not set
+# CONFIG_CODA_FS is not set
+# CONFIG_AFS_FS is not set
#
# Partition Types
After these patches, were finally ready to compile the kernel
Code:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- STAR_TMUS_REV=TMUS_10 TARGET_STAR_HWREV=TMUS_E TARGET_MODEM=ifx
Now go grab some coffee. This takes a while. When it's finished, the compressed kernel-image is found in
arch/arm/boot/zImage
For the experienced kernel-hackers this might be enough. It wasn't for me and I wanted to have it easily installable like other kernels from the forum. So I downloaded a kernel zip package, eg. the one from spica1234 at http://forum.xda-developers.com/showpost.php?p=18253696&postcount=1
Any version will do as long as the kernel is contained in a .zip archive and installable via CWM. In my case I downloaded the kernel zip in a new directory 'build' and unpacked it.
Code:
unzip HP_2x_RC12-RevOTF-PRO.zip
This creates the subdirectories 'data', 'kernel', 'META-INF' and 'system'. Here we now have to replace the kernel and the kernel-modules with our self-compiled versions.
Code:
cd ~build/kernel
rm zImage
cp ~kernel/arch/arm/bootzImage ./zImage
cd ../system/lib/modules
rm *.ko
find ~kernel/ -name "*.ko" -exec cp '{}' . \;
cd ../../..
One last step, creating the zip which carries the new kernel:
Code:
zip -r -FS new_kernel.zip data/ kernel/ META-INF/ system/
This new_kernel.zip can now be flashed with CWM and should boot without problems.
For easier usage, I've attached the three patched files in the build_set.zip attachment so you don't have to patch the stock files by hand. Just extract it in the kernel directory and overwrite the existing files.
I hope I did not make any error in the compilation of this information and that it can be helpful for the interested reader.
Thanks goes especially to spica1234 and the material which he provided me to come through to a successful boot.
Very good explanation. I wish such useful info available b4 an year for me while i published 1st kernel at samdroid for my older device
Sent from my LG-P990 using Tapatalk
Bloody hell! I never realised it took so much to simply compile!!!! (I build JEE systems at work, but we scripted most of it, stuff that used to take a day and half now takes a few minutes).
Excellent guide Kosi! I'm a linux and kernel n00b and I understand your instructions pretty well.
Ubuntu 11 is not the best choice though I currently use it myself. v11 can cause problems, especially when not compiling kernels but compiling Android ROMs.
Ubuntu 10 is the better choice.
Also there is a VMware Android Developer Environment available for download, providing nearly all the necessary tools for compilation preinstalled and set-up.
http://forum.xda-developers.com/showthread.php?t=1386918
You can compile your kernel directly in the virtual machine p.ex. on your Windows 7 PC. That's the way I do it for my kernel. VMware Player is available for free, so you can just run the image.
Also install VMware tools, so you can set up a directory for exchanging files between your Windows Host and the virtual Machine Ubuntu. In this directory I usually paste the compiled kernel for further use under Win7 (making the CWM update ZIPs).
Just note that you should have a dual/quadcore CPU strong enough to host the linux and compile the kernel in an acceptable time (usually it takes me 1-2 minutes for complete kernel compilation under virtual machine ubuntu using -j24 option on make).
Can u guys add a bit in this tutorial, example, at which file / folder need to edit for OCUV, add swap function, enable ext4, etc.. seriously like this thread..
Sent from my LG-P990 using XDA
ghadap said:
Can u guys add a bit in this tutorial, example, at which file / folder need to edit for OCUV, add swap function, enable ext4, etc.. seriously like this thread..
Click to expand...
Click to collapse
As the topic of this thread is just how to get the stock kernel compiling I won't step into modifying it. Please open a separate thread for that.
Small hints though, OCUV requires deeper code changes, swap and ext4 can just be enabled in the kernel config.
Hey,
I follow the guide, but ubuntu (11.04 64 bit) doesn't find the pack
Code:
apt-get install gcc-linaro
so I can't install the pack
Code:
apt-get install gcc-linaro-arm-linux-gnueabi
Edit: With Ubuntu 11.10, it works.
Has anyone compiled and booted a kernel successfully with this guide? Can't get mine to boot, so before I look any further I'd thought I'd check if anyone else has gotten a workable kernel out of it.
TrymHansen said:
Has anyone compiled and booted a kernel successfully with this guide? Can't get mine to boot, so before I look any further I'd thought I'd check if anyone else has gotten a workable kernel out of it.
Click to expand...
Click to collapse
Which version it shows "arm-linux-gnueabi-gcc --version"
If its 4.6.2?
Sent from my LG-P990 using Tapatalk
Stefan Gündhör said:
Ubuntu 11 is not the best choice though I currently use it myself. v11 can cause problems, especially when not compiling kernels but compiling Android ROMs.
Ubuntu 10 is the better choice.
Also there is a VMware Android Developer Environment available for download, providing nearly all the necessary tools for compilation preinstalled and set-up.
http://forum.xda-developers.com/showthread.php?t=1386918
You can compile your kernel directly in the virtual machine p.ex. on your Windows 7 PC. That's the way I do it for my kernel. VMware Player is available for free, so you can just run the image.
Also install VMware tools, so you can set up a directory for exchanging files between your Windows Host and the virtual Machine Ubuntu. In this directory I usually paste the compiled kernel for further use under Win7 (making the CWM update ZIPs).
Just note that you should have a dual/quadcore CPU strong enough to host the linux and compile the kernel in an acceptable time (usually it takes me 1-2 minutes for complete kernel compilation under virtual machine ubuntu using -j24 option on make).
Click to expand...
Click to collapse
Ubuntu 11.xx is still a good choise if you want to build ROMs it is very easy to set it up (it is just one step more then on 10.xx)
i also use ubuntu 11.10 and it is working fine for me with building android ROMs
and of course it can take 1-2 minutes but it also can take up to an hour for a kernel to compile
it all depends on how good your computer is
on my home computer i build a kernel in a matter of seconds (clobber builds)
but when i am at my girlfriend my build (also clobber) on her craptop will take up to 20 minutes
nice guide kosi2801!
spica1234 said:
Which version it shows "arm-linux-gnueabi-gcc --version"
If its 4.6.2?
Click to expand...
Click to collapse
Yap. This
Code:
arm-linux-gnueabi-gcc (Ubuntu/Linaro 4.6.2-14ubuntu2~ppa1) 4.6.2
to be specific.
Trymhanson, Try to downgrade with 4.5.3. 4.6.2 is causing this unable to boot issue which was not happening earlier with 4.6.1
try this
apt-get install gcc-4.5-arm-linux-gnueabi
apt-get install g++-4.5-arm-linux-gnueabi
rm /usr/bin/arm-linux-gnueabi-gcc
ln -s /usr/bin/arm-linux-gnueabi-gcc-4.5 /usr/bin/arm-linux-gnueabi-gcc
Thanks, that did it. I also had to change the -Ofast flag back to -O2 as -Ofast wasn't recognized by the 4.5.3 version. So now I'm thinking maybe the -Ofast flag was to blame, so I'll try a fresh 4.6.2 install with -O2. Thanks again.
TrymHansen said:
Thanks, that did it. I also had to change the -Ofast flag back to -O2 as -Ofast wasn't recognized by the 4.5.3 version. So now I'm thinking maybe the -Ofast flag was to blame, so I'll try a fresh 4.6.2 install with -O2. Thanks again.
Click to expand...
Click to collapse
no may be ofast is not to blame but 4.6.2. Ofast was introduced with 4.6.0 and doesnt work with < 4..6. 4.6.2 doesnt even work with o2. And IMHO kernel compiled with 4.5.3 ismore stable
Sent from my LG-P990 using Tapatalk
http://db.tt/jN4fU9Vz
Thisis my recent sr3r2 patch created against original v20Q sourceswith Full OTF V2.0. Anybody interested can use it. It will transform to fully noo oc version of SR3r2
It wont work with CM but only stock v20q
Sent from my LG-P990 using Tapatalk
For anyone interested, currently I'm building with
arm-linux-gnueabihf-gcc (Ubuntu/Linaro 4.6.1-7ubuntu2) 4.6.1
For my usage patterns the kernel works pretty well, but YMMV.
Thanks spica for the updated patch!
kosi2801 said:
For anyone interested, currently I'm building with
arm-linux-gnueabihf-gcc (Ubuntu/Linaro 4.6.1-7ubuntu2) 4.6.1
For my usage patterns the kernel works pretty well, but YMMV.
Thanks spica for the updated patch!
Click to expand...
Click to collapse
Use my recent cflags its most stable and used in sr3r2
As you are using gnueabihf relace mfloat-abi=softfp with mfloat-abi=hard
Sent from my LG-P990 using xda premium
spica1234 said:
Use my recent cflags its most stable and used in sr3r2
As you are using gnueabihf relace mfloat-abi=softfp with mfloat-abi=hard
Click to expand...
Click to collapse
Thanks for the tip. I already thought about that some time ago but forgot again. Gained some additional performance points
Can someone upload a compiled stock v20q kernel flashable zip? Thanks!
Sony Xperia ZR - Official Firmware
Android 4.3
Here's the download link for the Russian version of 4.3 (XPERIA ZR C5503 PCT 10.4.B.0.569)
Link 1
Link 2
Here's the Build.prop
##### Merging of the /util/data/semc_kernel_time_stamp.prop file #####
ro.build.date=Thu Nov 28 10:50:01 2013
ro.build.date.utc=1385632201
ro.build.user=BuildUser
ro.build.host=BuildHost
##### Final patch of properties #####
ro.build.product=C5503
ro.build.description=C5503-user 4.3 LAGAN-1.2-RELEASE-131202-1528 6 test-keys
ro.product.brand=Sony
ro.product.name=C5503_1272-9018
ro.product.device=C5503
ro.build.version.incremental=xr3_rQ
ro.build.tags=release-keys
ro.build.fingerprint=Sony/C5503_1272-9018/C5503:4.3/10.4.B.0.569/xr3_rQ:user/release-keys
######################## Customized property values #########################
ro.semc.version.cust=1272-9018
ro.semc.version.cust_revision=R2C
ro.somc.customerid=108
#############################################################################
ro.config.ringtone=xperia.ogg
ro.config.notification_sound=notification.ogg
ro.config.alarm_alert=alarm.ogg
ro.semc.content.number=PA2
################# Updating of the SW Version #################
ro.semc.version.fs_revision=10.4.B.0.569
ro.build.id=10.4.B.0.569
ro.build.display.id=10.4.B.0.569
##### Values from product package metadata #####
ro.semc.product.model=C5503
ro.semc.ms_type_id=PM-0330-BV
ro.semc.version.fs=GLOBAL-LTE
ro.semc.product.name=Xperia ZR
ro.semc.product.device=C55
ro.product.model=C5503
# begin build properties
# autogenerated by buildinfo.sh
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.type=user
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=xhdpi
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
# Do not try to parse ro.build.description or .fingerprint
ro.build.characteristics=nosdcard
# end build properties
#
# from device/qcom/msm8960/system.prop
#
#
# system.prop for surf
#
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
persist.actionsafe.maxwidth=20
persist.actionsafe.maxheight=20
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
dalvik.vm.heapsize=36m
debug.enable.wl_log=1
persist.hwc.mdpcomp.enable=true
debug.mdpcomp.logs=0
# Start in LTE/WCDMA/GSM mode
ro.telephony.default_network=9
#
# system props for the cne module
#
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.feature=1
ro.hdmi.enable=true
lpa.decode=false
tunnel.decode=true
tunnel.audiovideo.decode=true
lpa.use-stagefright=true
qcom.hw.aac.encoder=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
mm.enable.smoothstreaming=true
media.aac_51_output_enabled=true
#33395 is sum of supported format flags in AAL
#Formats: AVI AC3 ASF AAC QCP DTS 3G2
mm.enable.qcom_parser=33395
encoder.video.profile=high
# system props for content protection
#
# (level3=1 means TZ is not used)
persist.gralloc.cp.level3=1
# VIDC: debug_levels
# # 1:ERROR 2:HIGH 4:LOW 0:NOlogs 7:AllLogs
vidc.debug.level=1
#
# system props for the data modules
#
ro.use_data_netmgrd=true
#system props for time-services
persist.timed.enable=true
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=analog
persist.audio.lowlatency.rec=false
persist.audio.hp=true
# System prop to select audio resampler quality
af.resampler.quality=255
# System prop to select MPQAudioPlayer by default on mpq8064
mpq.audio.decode=true
#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0
#system prop for switching gps driver to qmi
persist.gps.qmienabled=true
# System property for cabl
ro.qualcomm.cabl=1
# System props for telephony
# System prop to turn on CdmaLTEPhone always
telephony.lteOnCdmaDevice=0
#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true
#
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.crypto.fuse_sdcard=true
ro.hwui.text_cache_width=2048
# Fontrenderer cache size (initial small texture)
ro.hwui.text_small_cache_width=2048
# System props for external display
hw.trueMirrorSupported=1
ro.hwui.external_width=1920
ro.hwui.external_height=1080
# Texture cache size (in MB)
ro.hwui.texture_cache_size=128.0f
#
# Supports warmboot capabilities
#
ro.warmboot.capability=1
# Default values/Locales for the hiding languages feature
ro.product.locale.excluded=ar_EG ar_IL fa_IR iw_IL
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=none
ro.qc.sdk.camera.facialproc=true
ro.qc.sdk.gestures.camera=false
ro.qc.sdk.sensors.gestures=true
#property to force camera shutter sound on speaker
#ro.camera.sound.forced=1
# Modem power save enabled
persist.radio.add_power_save=1
# Interactive governor
ro.cpufreq.governor=interactive
#property to check if dynamic resolution change is supported in framework
ro.streaming.video.drs=true
#property to enable user to access Google WFD settings.
persist.debug.wfd.enable=1
#property to choose between virtual/external wfd display
persist.sys.wfd.virtual=0
#system prop for setting rmnet mux mode
persist.rmnet.mux=disabled
# Disable OEM SOCKET
persist.radio.oem_socket=false
#
# from device/sony/dogo/system.prop
#
# USB
ro.usb.pid_suffix=197
# System props for SOLS
ro.semc.sols.product-code=118
ro.semc.sols.company-code=5
# NFC
ro.nfc.on.default=true
ro.nfc.se.sim.enable=true
ro.nfc.se.smx.enable=false
ro.nfc.icon.enable=false
ro.nfc.vendor.name=nxp
ro.nfc.limitation.camera=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product-res-path=framework/SemcGenericUxpRes.apk
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.com.android.dataroaming=false
ro.com.google.clientidbase=android-sonyericsson
ro.com.google.clientidbase.ms=android-sonymobile
ro.somc.clearphase.supported=true
ro.semc.xloud.supported=true
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.3_r1
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.vendor.extension_library=/system/lib/libqc-opt.so
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=0
ro.qc.sdk.izat.service_mask=0x4
persist.gps.qc_nlp_in_use=0
ro.gps.agps_provider=1
ro.service.swiqi2.supported=true
persist.service.swiqi2.enable=1
ro.sony.irremote.protocol_type=2
ro.drm.active.num=5
ro.drm.active.0=marlin,1
ro.drm.active.1=playready,1
ro.drm.active.2=dtla,1
ro.drm.active.3=marlin_import,1
ro.drm.active.4=ckb,1
ro.sony.fota.encrypteddata=supported
Click to expand...
Click to collapse
C5502 Android 4.2.2: DOWNLOAD
C5503 (UPDATE)
Note: The firmware for C5503 can be flashed on C5502 as well without any problems.
Android 4.2.2.
version 10.3.1.A.0.244
Nordic - **DOWNLOAD**
Russian - **Download**
4.2 CHANGELOG:
1. Screen, the contrast is much higher, black text on a light background looks very good.
2. Camera, the quality and speed of focusing even when shooting movies is better.
The camera is much faster is focussing and taking a picture. The quality is also better than before. Colour calibration is much much better this time around.
Can't really comment on the low light performance, Is slightly better but can't really be sure.
Overall the phone seems much faster. The radio is also better as I get much better 3G signal than on 4.1.2. WiFi performance is also better.
"Photo Sphere" panorama photos
Keyboard with gesture typing (this feature is also available for Android 4.0 and later via the Google Keyboard app)
Lock screen improvements, including widget support and the ability to swipe directly to camera
Notification power controls ("Quick Settings")
"Daydream" screensavers, showing information when idle or docked
Multiple user accounts (tablets only)
Support for wireless display (Miracast)
Accessibility improvements: triple-tap to magnify the entire screen, pan and zoom with two fingers. Speech output and Gesture Mode navigation for blind users
New clock app with built-in world clock, stop watch and timer
All devices now use the same interface layout, previously adapted from phones on 4.1 for smaller tablets (with centered software buttons, the system bar at the top of the screen, and a home screen with a dock and centered application menu), regardless of screen size
Increased number of extended notifications and Actionable Notifications for more apps, allowing users to respond to certain notifications within the notification bar and without launching the app directly
SELinux
Always-on VPN
Premium SMS confirmation
Group Messaging
Fixed a bug in the People app where December was not displayed on the date selector when adding an event to a contact
Added Bluetooth gamepads and joysticks as supported HID
Fixed Bluetooth audio streaming bugs
Long-pressing the Wi-Fi and Bluetooth icons in Quick Settings now toggles the on/off state
New download notifications, which now shows the percentage and estimated time remaining for active app downloads
New sounds for wireless charging and low battery
New Gallery app animation allows faster loading
USB debug whitelist
Bug fixes and performance enhancements
To keep root capability in 4.2.2
You CANNOT flash using flashtool. You need to UPDATE over the air only.
If you use flashtool, everything gets formatted completely (the /system partition), thus root capability is permanently lost.
If you need to preserve root you need to wait till you have the OTA Update in your region, and then update.
Never flash via flashtool if you want to preserve your root capability.
Android 4.1.2:
C5503
Version: 10.1.1.A.1.310
Russia - docs.google.com
Hong Kong - docs.google.com
Global - docs.google.com / pan.baidu.com / system partition - drive.google.com
C5502
Android 4.1.2
Version: 10.1.1.A.1.310
India - docs.google.com / 4shared.com
Flashtool: DOWNLOAD
Flashtool is a flashing software that can be used to :
Flash original Images (Android 1.6, 2.1, 2.3 Images)
Root your phone
Install Recovery, Busybox, custom kernels
Clean your Rom (remove /system/apps apps of your choice) (Be careful, unless you really know what you do, do not modify the default list. This can make your phone stuck at the SE Logo)
Clear dalvik cache
Optimize (install of JIT v2) (Disabled in 0.4, will readd it as a plugin for 2.1 phones only)
Customize (installs apps found in the custom/apps folder of the flashtool)
Clean uninstalled (remove any references to system apps removed in the Clean (root needed) step)
Edit any text file on the device
Rebrand your device
Flashing Instructions.
FAQ'S:
Q: How do I know the region, which is programmed for this device (modification of software)?
A: Type the command * # * # 7378423 # * # * ( * # * # SERVICE # * # * ), select " Service info ", then - " Software info ". Under the line " Customization Version : "the version of the update - search for it in the following table.
Q: After update / reinstall the device after a few seconds of the first issue as a question in the image below - "[POWER OFF] or [Use phone]". What is it?
A: This is caused by the fact that before (re) installing the software has been requested data and reset the device is now trying to establish the factory settings. For their complete installation, you must select the [POWER OFF], otherwise the request will be repeated after every reboot your device and as long as you have selected the [POWER OFF]
Thanks
Thanks a lot bro
This is very helpful.
waiting for ROMS to flash now
C5503
New ROM 4.2.2. version 10.3.1.A.0.244 Nordic
There - https://docs.google.com/file/d/0ByFJDQjqIe_qdktCQ3IxdnJNVm8/edit?usp=sharing
St_Ranger said:
New ROM 4.2.2. version 10.3.1.A.0.244 Nordic
There - https://docs.google.com/file/d/0ByFJDQjqIe_qdktCQ3IxdnJNVm8/edit?usp=sharing
Click to expand...
Click to collapse
Thanks a lot for this!
Is this unbranded Nordic ROM?
hendriksan said:
Is this unbranded Nordic ROM?
Click to expand...
Click to collapse
Yes, of course
St_Ranger said:
Yes, of course
Click to expand...
Click to collapse
Is there english version with this? Also is this simlocked?
gmengass said:
Is there english version with this? Also is this simlocked?
Click to expand...
Click to collapse
Regardless of where the ROM originally from, you will still get option for using English language.
I have done in the past with my xperia Z, to flash different country such as Belgium, etc.
This is just a matter of different country where they get it from.
hendriksan said:
Regardless of where the ROM originally from, you will still get option for using English language.
I have done in the past with my xperia Z, to flash different country such as Belgium, etc.
This is just a matter of different country where they get it from.
Click to expand...
Click to collapse
Should I use flashtool to flash it? My ZR is just rooted without custom recovery. I'm new to Sony phone so I don't know what to do with the FTF files.
I guess I just need to follow the instructions in this thread...
itandy said:
Should I use flashtool to flash it? My ZR is just rooted without custom recovery. I'm new to Sony phone so I don't know what to do with the FTF files.
I guess I just need to follow the instructions in this thread...
Click to expand...
Click to collapse
Yes that's the correct link, just follow as instruction to flash the ftf file.
hendriksan said:
Yes that's the correct link, just follow as instruction to flash the ftf file.
Click to expand...
Click to collapse
Did you have data wiped or a clean flash? Does the DoomLord rooting toolkit works in this ROM?
itandy said:
Did you have data wiped or a clean flash? Does the DoomLord rooting toolkit works in this ROM?
Click to expand...
Click to collapse
You can choose either to wipe the data or keep it including with all the settings, as per instructions written there.
I found this from xperiablog web which is for Z and ZL, it seems you won't be able to root if you flash it.
"Update: DooMLoRD from xda-developers has got in touch to let users know not to flash this latest update directly or you will lose root. Sony has patched the perf_event exploit in the newer kernel source. @xperiaBlog word of advice rooted users SHOULD NOT FLASH THIS DIRECTLY. use OTA RootKeeper or something. perf_event root exploit is patched."
Can I flash that Nordic ROM of C5503 on to my C5502?
Sent from my C5502 using xda app-developers app
Question?!
Can we flash the C5503 firmware onto the C5502 model? Has anyone tried?
4.2 CHANGELOG:
Screen, the contrast is much higher, black text on a light background looks very good.
Camera, the quality and speed of focusing even when shooting movies is better.
Update added.
The Android 4.2.2 update has been merged into the first post.
Does anyone have link to download latest flashtool and the driver for ZR?
hendriksan said:
Does anyone have link to download latest flashtool and the driver for ZR?
Click to expand...
Click to collapse
Check 2nd post here.
http://forum.xda-developers.com/showthread.php?t=2384590
hendriksan said:
Does anyone have link to download latest flashtool and the driver for ZR?
Click to expand...
Click to collapse
Please check out the other thread.
Should be able to. The only difference is the LTE versus no LTE. Will check it out this evening and keep you posted
Sent from my C5502 using Tapatalk 2
bkhuraijam said:
Can I flash that Nordic ROM of C5503 on to my C5502?
Sent from my C5502 using xda app-developers app
Click to expand...
Click to collapse
Yes!! I flashed the firmware of C5503 to my C5502 and it works fine!!! Yeahh! Finally have Android 4.2.2.!
Annoying fact is that the screenshot option in the power menu is now gone!
akash4357 said:
Yes!! I flashed the firmware of C5503 to my C5502 and it works fine!!! Yeahh! Finally have Android 4.2.2.!
Annoying fact is that the screenshot option in the power menu is now gone!
Click to expand...
Click to collapse
I guess no root, right? I'd definitely flash it once root method is available!
This is an EXPERIMENTAL Kernel that continues the work of @pengus77, but with some additions i make. That means a huge thank to pengus77! Please check his thread http://forum.xda-developers.com/showthread.php?t=2097788
This kernel is completely based on his latest release.
This kernel only supports newbl and will only work on roms with 3.1 support (these are atm only 4.4 (aka KitKat) Roms and tonyps TheRom that is compatible with the 3.1 kernel
Features:
Features from the kowalski kernel:
3.1.10 Kernel Version
bcmdhd wifi driver
Dynamic FSync
Overclock to 1.5 GHz (Not all phones work well with 1.5 Ghz!)
Undervolting
MultiCore Sched PM
Auto Hotplug
Fast charge
Wifi PM
and many more ...
Features added by me:
PKSM as enhanced KSM module
Built in ZRAM Modul (that makes it possible to use the android default zram solution)
Possibility to use deferred_timer for (P)KSM
0, 16 or 32 MB Ramhack
Support for extra free kbytes tunable (more a ROM dev feature)
Custom vibration force/strength through sysfs
120MHz and 168 MHz frequencies for more battery savings during wakelock
Known bugs:
Camera Bug
Gyro does not work properly
If you want to report a new kernel bug, you must describe your problem in detail, post your kmsg and last_kmsg (if available) (you can found them under /proc/kmsg and /proc/last_kmsg) otherwise the rule is: no log = no issue
Downloads:
This is more a personal kernel build. I have built these kernels for weeks for myself and used them in private. Now i just want to share them with you guys!
You can download the kernels here: https://s.basketbuild.com/devs/firtecy/p990/kernel/3.1/ They are labeled like this: firtecy_kernel_X-N.zip where X is either exp for an experimental kernel release and stable for a stable kernel and where N is the build number (this number is always incremental!)
Sourcecode:
You can find the sourcecode at github: https://github.com/Firtecy/kowalski/ the branch is exp. The config file is: "kowalski_defconfig"
The intention of this thread is to continue the 3.1 kernel development pengus started. Development related questions or discussions are appreciated
Have fun!
And to quote pengus77:
On a side note... i'm not really responsible if you decide to test it and your phone melts... right?
Thanks to:
@hjunii for bringing up 3.1 Kernel
@pengus77 for the kowalski kernel
XDA:DevDB Information
Firtecy Kernel - a modified Kowalski Kernel, Kernel for the LG Optimus 2x
Contributors
Firtecy, pengus77, hjunii, djnoxd
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 3.1#5
Beta Release Date: 2014-08-25
Created 2014-10-31
Last Updated 2014-10-31
Changelog:
firtecy_kernel_exp-5 - 25.8.2014
Added intellactive governor (thanks to @faux123) and powersave
Some bug fixes
Added sync framework and exfat support (but not active for the moment)
Added a "kowalski touch driver" and dt2w files (since they are not stable enough for now, they are disabled)
The reason why I disabled those things is that I didn't had the time to test them. If you want to test them you have to build your own version. Especially for other developers that can be interesting.
Click to expand...
Click to collapse
firtecy_kernel_exp-4 - 25.6.2014
minor updates/fixes from other kernels
Added the min screen on freq back
Added a sysfs attribute to change the min screen on freq
when disabling pksm, it will be disabled completely
Screen on min freq
If your screen is on, this frequency is the lowest that will be used. If your screen goes off for whatever reason the cpu will go to the normal min frequency.
Note: It seems like 120MHz and 168MHz are stable even for screen on, but since there was the question if i can add it, here you go:
How to change the value:
Code:
echo [value] > /sys/module/cpu_tegra/parameters/cpu_screen_on_min_cap
You have to use a value that is in the frequency table, but you have to echo the frequency in KHz, so 120MHz -> 120000KHz:
Code:
echo 120000 > /sys/module/cpu_tegra/parameters/cpu_screen_on_min_cap
This option does not stick after a reboot
According to @BS86 this release should be more stable than exp3 and thanks for testing!
Click to expand...
Click to collapse
firtecy_kernel_exp-3 - 13.6.2014
tons of updates to zram/zcache (picked from faux123 tegra kernels)
crypto: added optimized AES and SHA1 routines
added permission checker for binder IPC
tegra video driver updates
Fixed the voltage table -> all values below 770 MHz are not supported by the regulator chip (thanks to all who helped researching! )
Click to expand...
Click to collapse
firtecy_kernel_exp-2 - 8.6.2014
Added the possibility to change the vibration force (or vibration strength)
Added 120MHz and 168MHz as cpu frequencies
Enabled 600 mV as lowest undervolting value (undervolting is very dangerous if you go too low! Better stay at defaults)
Fixed a nvidia or lg cpu derp.
For security reasons it is not possible that the cpu will go underneath 216MHz when screen is on!
Option to use: No ramhack, 16Mb Ramhack or 32 Mb Ramhack!
Vibration force:
to change the vibration force echo a number between 0 and 127 to /sys/module/tspdrv/parameters/vibration_force. Where 127 is the highest and the default. 20 seems to be the last noticeable value.
Code:
echo [force] > /sys/module/tspdrv/parameters/vibration_force
This option does not stick after a reboot. Rom support will be available (hopefully) soon. I'm preparing a patch for tonyps Rom, so that it is possible to change it in the Rom settings.
120 and 168Mhz:
These values are useful for the case where the phone helds a wake lock. This means because of the wake lock it won't enter deepsleep. The phone would run at 216MHz even if it isn't needed. Running at 168Mhz or even 120MHz should result in a better battery life.
If you experience any problems, try to raise the voltage at this frequencies to a higher value and test again. If it is still unstable report it (with a description of the problem) and change the minimum frequency to 216Mhz.
Click to expand...
Click to collapse
firtecy_kernel_exp-1 - 1.6.2014
Initial release
Base source: kowalski kernel
Added built in ZRam (no need to use zram.ko for longer)
Added PKSM as replacement for ksm (http://code.google.com/p/pksm/)
Enabled deferred timers for pksm and ksm
Notice: Since there is no ksm available, but pksm you will not find the options for ksm in any app. All configurations are no longer under: /sys/kernel/mm/ksm/ , but under: /sys/kernel/mm/pksm/
To deativate pksm run this command as root:
Code:
echo 0 > /sys/kernel/mm/pksm/run
This option does not stick after a reboot
Click to expand...
Click to collapse
How to build your own kernel:
You need a Linux PC with either 32 or 64Bit. I'm using Linux Mint Debian Edition 64Bit. And you will need the following packages:
build-essential kernel-package libncurses5-dev bzip2
For example to install them run:
Code:
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
Hint: If you run into troubles with installing packages, check this post
1. Create a new directory for your kernel building (for example: ~/kernel_p990)
Code:
mkdir ~/kernel_p990
2. cd to your kernel dir
Code:
cd ~/kernel_p990
3. Run this command to download the source code for compiling:
Code:
git clone https://github.com/Firtecy/kowalski
4. Now we need to download the toolchain for compiling: Download it from here: http://www.linaro.org/downloads/ under the Bare-Metal section. It is labeled GCC ARM Embedded. Version: 4.7-2013.q3 ; Release: 13.11
5. Now extract the toolchain to a new dir, for example: ~/kernel_p990/toolchain
6. Now we have to define some values for the build enviroment:
Set the CROSS_COMPILE var to your path where you have downloaded your toolchain. For example:
Code:
export CROSS_COMPILE=~/kernel_p990/toolchain/gcc-arm-none-eabi-4_7-2013q3/bin/arm-none-eabi-
Notice at the end you find this prefix: arm-none-eabi- this is not a dir, but the prefix for all files inside the bin directory(for example: arm-none-eabi-gcc)
7. Set the architecture (processor architecture) for which the kernel should be build. So in our case arm:
Code:
export ARCH=arm
and
Code:
export SUBARCH=arm
8. The next step defines the configurations for the kernel (in this case the configuration is named kowalski_defconig)
Code:
make kowalski_defconfig
Notice: this takes the configuration from the file located under arch/arm/configs and will write it to .config
9. Now we can finally build the kernel :victory: Run:
Code:
make
You will find the kernel under: arch/arm/boot/zImage. You just have to copy the zImage and replace the one found in the flashable zip (e.g. my downloads) under kernel/zImage with your own.
Troubleshooting:
Before you can build or run any from step 8 or 9 you have to make sure that all three vars are set correctly (so ARCH, CROSS_COMPILE and SUBARCH). You can check it by running:
Code:
echo $ARCH
for ARCH (for CROSS_COMPILE and SUBARCH it is the seem, but you have to change the name)
If they are not set correctly repeat step 6 and 7.
If you get a compile error first try to run:
Code:
make clean
and try to build the kernel again.
How to diff 2 files or directories in linux
If you are running linux and have two files on your computer and you want to find the differences you can run the diff command in the terminal.
Let's say you have a file "hjunii/traps.c" and "kowalski/traps.c", this is how you compare them:
Code:
diff -u hjunii/traps.c kowalski/traps.c
The command will compare both and will print an output to the terminal that will be similar to this:
Code:
@@ -27,6 +27,7 @@
#include <linux/delay.h>
#include <linux/init.h>
#include <linux/sched.h>
+#include <linux/slab.h>
#include <linux/atomic.h>
#include <asm/cacheflush.h>
@@ -483,25 +484,38 @@
static inline void
do_cache_op(unsigned long start, unsigned long end, int flags)
{
- struct mm_struct *mm = current->active_mm;
- struct vm_area_struct *vma;
-
if (end < start || flags)
return;
+ return flush_cache_user_range(start, end);
+}
+
+static inline int
+do_cache_op_iov(const struct iovec __user *uiov, unsigned long cnt, int flags)
+{
+ int i, ret = 0;
+ unsigned long len = cnt * sizeof(struct iovec);
+ struct iovec *iov = kmalloc(len, GFP_KERNEL);
- down_read(&mm->mmap_sem);
- vma = find_vma(mm, start);
- if (vma && vma->vm_start < end) {
- if (start < vma->vm_start)
- start = vma->vm_start;
- if (end > vma->vm_end)
- end = vma->vm_end;
+ if (iov == NULL) {
+ ret = -ENOMEM;
+ goto out;
+ }
- up_read(&mm->mmap_sem);
- flush_cache_user_range(start, end);
- return;
+ if (copy_from_user(iov, uiov, len)) {
+ ret = -EFAULT;
+ goto out_free;
}
- up_read(&mm->mmap_sem);
+
+ for (i = 0; i < cnt; ++i) {
+ unsigned long start = (unsigned long __force)iov[i].iov_base;
+ unsigned long end = start + iov[i].iov_len;
+ do_cache_op(start, end, flags);
+ }
+
+out_free:
+ kfree(iov);
+out:
+ return ret;
}
/*
@@ -550,6 +564,10 @@
do_cache_op(regs->ARM_r0, regs->ARM_r1, regs->ARM_r2);
return 0;
+ case NR(cacheflush_iov):
+ do_cache_op_iov((const struct iovec __user *)regs->ARM_r0,
+ regs->ARM_r1, regs->ARM_r2);
+
case NR(usr26):
if (!(elf_hwcap & HWCAP_26BIT))
break;
Each line starting with a "+" are lines that were added, for example:
Code:
+#include <linux/slab.h>
On the other side lines starting with a "-" are lines that were deleted, for example:
Code:
- struct mm_struct *mm = current->active_mm;
A line like the following should just show you were you find the changes:
Code:
@@ -550,6 +564,10 @@
with the following syntax:
Code:
@@ -[line number in 1. file],[number of lines that were printed from 1.file] + [line number in 2. file], [number of lines that were printed from 2.file] @@
But the basic syntax is the following:
Code:
diff -u [base file] [file containing the changes you want to display]
You can also compare whole directories!
ProTip: Install the program "colordiff". It will color the console output, that means the output is more readable!
Syntax:
Code:
diff -u [base file] [file containing the changes you want to display] | colordiff
Example:
Code:
[COLOR="Plum"]@@ -1,8 +1,8 @@[/COLOR]
[COLOR="Red"]-VERSION = 2
-PATCHLEVEL = 6
-SUBLEVEL = 39
-EXTRAVERSION = .4
-NAME = Flesh-Eating Bats with Fangs[/COLOR]
[COLOR="RoyalBlue"]+VERSION = 3
+PATCHLEVEL = 1
+SUBLEVEL = 10
+EXTRAVERSION =
+NAME = "Divemaster Edition"[/COLOR]
Nice New kernel!
will try that one as soon as possible.
thanks for the work.we dont let the 2x die!
Will this work on Mokee rom?
If you don't understand the subconscious you will always bump into it calling it fate...
themistoklisv said:
Will this work on Mokee rom?
If you don't understand the subconscious you will always bump into it calling it fate...
Click to expand...
Click to collapse
Which kernel is included by default in the Rom or can you paste a link?
Gesendet von meinem LG-P990 mit Tapatalk
[email protected]#126
If you don't understand the subconscious you will always bump into it calling it fate...
themistoklisv said:
[email protected]#126
If you don't understand the subconscious you will always bump into it calling it fate...
Click to expand...
Click to collapse
Then I am sorry, but it is not compatible.
The 3.1 kernel differs too much to be compatible with ROMs that are build for an 2.6 kernel
Gesendet von meinem LG-P990 mit Tapatalk
Oh my God, amazing! Finally some serious development! Great work Firtecy. Time to bust CM11 back on my device and try this ramhacked wonder
Oh...i see...this why no ksm settings
Btw...i would suggest a higher ramhack like 32mb like m1 ramhack...but this kernel works great so far...just classic low ram problem exist (well...obviously) need to set an aggresive value (i'm using swap without zram)
Do i need to post a logcat?
Sent from my LG-P990
Will this work with cm 10.1?
Wysłane z mojego LG-P990 przy użyciu Tapatalka
No, it has a different wifi driver, sorry for my english
Sent from my ME173X using XDA Free mobile app
Okey
Wysłane z mojego LG-P990 przy użyciu Tapatalka
The first change:
Okay since there was the wish that there should be a 32 MB ramhack version and the poll showed the same i built one. You can find it at my basketbuild https://s.basketbuild.com/devs/firtecy/p990/kernel/3.1/.
So the 32 MB Ramhack version is labeled: firtecy_kernel_exp-1_32MB-RH.zip and the previous one is labeled: firtecy_kernel_exp-1_16MB-RH.zip
I have flashed it and in the settings app, I had 372MB available (Settings > About)
The second change:
Since i have been asked to explain how to build my kernel from source code i wrote a small how to in the third post of the thread. Check it and maybe try to build it for your own.
If you wish i can also write how to change the kernel by your own. (So add new stuff or something similiar)
Great job firtecy...downloading asap
--------------------++-
Very fluid ui with 32rh and with performance control app i can set lmk on boot (dunno..the one come with rom 0527 always reset after reboot)
So far...no bugs for me (except known bugs)
Btw i'm using swap only..no zram but zram works too (i turned it off)
Sent from my LG-P990
Would like to know if random reboot and phone always waking is a kernel related or rom?
Sent from my LG-P990 using Tapatalk 2
mkchan said:
Would like to know if random reboot and phone always waking is a kernel related or rom?
Sent from my LG-P990 using Tapatalk 2
Click to expand...
Click to collapse
I haven't got random reboots or always waking phone in fact on 3.1 kernel there's a bug for waking phone (need press power button twice or thrice)
Maybe your memory full ocupied and still lot queued job to do...that's sometimes happen to me...that's why i need to set lmk a bit aggresive...
Well as dev always said...log or it's not happen
Sent from my LG-P990
Firtecy said:
How to build your own kernel:
You need a Linux PC with either 32 or 64Bit. I'm using Linux Mint Debian Edition 64Bit. And you will need the following packages:
build-essential kernel-package libncurses5-dev bzip2
For example to install them run:
Code:
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
Click to expand...
Click to collapse
I have even had to install libc6-dev-i386 in my 64bit vbox image, then the make seems to have started working :good:
If you wish i can also write how to change the kernel by your own. (So add new stuff or something similiar)
Click to expand...
Click to collapse
+1 (if you don't mind and have time for it )
Thanks!
Thx for your dev. but can you build this kernel for su660?
나의 LG-P990 의 Tapatalk에서 보냄
Overview
I'm going to discuss forking CM11-based configs to OmniROM, I will not dicuss adapting device configs to TWRP because it's been done to death and most devices do have TWRP.
I'm not going to discuss how to move device, kernel and vendor configs into their proper folders, work at this level is very basic and I'm writing this under the assumption folks have a general understanding of how to build CM11 outside of just using 'breakfast' on an officially supported device. I will be writing this guide assuming you know where to put what, but just don't know how to structure them.
I'll be writing this guide under the assumption that you are using 'moto_msm8960', which I'll be using as an example; however this should apply to any device generally.
Rename the following file from:
cm.mk -> omni_moto_msm8960.mk
https://github.com/CyanogenMod/android_device_motorola_moto_msm8960/blob/cm-11.0/cm.mk
full_moto_msm8960.mk (will be merged into omni_moto_msm8960.mk)
https://github.com/CyanogenMod/andr...oto_msm8960/blob/cm-11.0/full_moto_msm8960.mk
If your device config file does not follow this format it's fine. If you have a "Full_device.mk" you will need to import it into your newly made omni_moto_msm8960.mk
I realize you're told to not do this, It's ok hold my hand and we'll walk into the darkness together.
Both files have "device Identifier" values and when using two makefiles with Omni this will cause compile issues 90% of the time unless the entry:
PRODUCT_NAME := full_moto_msm8960
Is above all the other Product_values. (but PRODUCT_value entries must be at the very END of the makefile)
If your Omni has built but has an under 100MB size, do not use dual-makefiles.
Let's construct the omni_moto_msm8960.mk:
#---------------------------#
# Moto_msm8960 unified #
# - OmniROM 4.4 - #
#---------------------------#
# Main product makefile
#---------------------------#
# First revision, everything is good here.
#---------------------------#
# Define screen resolution #
#---------------------------#
# * Change this for HDPI devices like Razr M
TARGET_SCREEN_WIDTH := 720
TARGET_SCREEN_HEIGHT := 1280
#---------------------------#
# Phone-specific config #
#---------------------------#
$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)
#---------------------------#
# Build for a CDMA phone #
#---------------------------#
$(call inherit-product, vendor/omni/config/cdma.mk)
#---------------------------#
# Use generic Omni configs #
#---------------------------#
$(call inherit-product, vendor/omni/config/common.mk)
#---------------------------#
# Phone-specific config #
#---------------------------#
$(call inherit-product, device/motorola/moto_msm8960/device_moto_msm8960.mk)
#---------------------------#
# Product [name] values #
#---------------------------#
PRODUCT_NAME := omni_moto_msm8960
PRODUCT_DEVICE := moto_msm8960
PRODUCT_BRAND := motorola
PRODUCT_MODEL := MOTOROLA MSM8960
PRODUCT_MANUFACTURER := motorola
Click to expand...
Click to collapse
Of course some things will vary; If you use a GSM phone you will not use Omnis CDMA config file, but will ALWAYS use common.
The product-values should reflect what is found in your makefile and PRODUCT_NAME should always be at the very top, screen resolution should be the very first thing specified followed by device specific telephony configs, everything inbetween does not matter as much.
Now we must edit Androidproducts.mk to reflect such a dramatic change, as we're now only using a single makefile.
#---------------------------#
# Moto_msm8960 unified #
# - OmniROM 4.4 - #
#---------------------------#
# Product Root makefile
#---------------------------#
PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/omni_moto_msm8960.mk
Click to expand...
Click to collapse
Modify this file in the following way, also make sure entries point to build paths and not something on Github.
cm.dependencies -> omni.dependencies
If not present, add a 'vendorsetup.sh' file containing the following entry
# ----------------------------------------
# Moto_msm8960 unified configuration
# - OmniROM 4.4 -
# ----------------------------------------
# Enable support for 'brunch' command
# ----------------------------------------
add_lunch_combo omni_moto_msm8960-userdebug
add_lunch_combo omni_moto_msm8960-eng
Click to expand...
Click to collapse
With your kernel and supporting device configs & vendor files intact, Omni will now be able to build functionally.
IF you recieve config.xml error, simply remove that line in config.xml or delete your Overlay folder.
If OmniROM builds but does not seem to boot; use Logcat, do you have this error?
E/Fence ( 220): sync_fence_info returned NUL
If so find the following commit in your kernel:
msm: mdp: Update sync pt. behaviour
and revert it.
Is this possible for cm13 and omnirom 6.0.1 too?
I tried to follow your guide, but it seems cm has changed a lot... I couldn't find the lines you have in your config files in the cm13 .mk files. And I could not find all the files.
I try to port omnirom 6.0.1 to S4 mini aka GT-I9195 aka serranoltexx.