Database Develop

[Q] Overclock omap4470 Kernel.

Has anyone tried this? Seems to be easy enough.
Code:
@@ -545,6 +546,8 @@
OPP_INITIALIZER("mpu", "virt_dpll_mpu_ck", "mpu", true, 1300000000, OMAP4470_VDD_MPU_OPPNITRO_UV),
/* MPU OPP4 - OPP-Nitro SpeedBin */
OPP_INITIALIZER("mpu", "virt_dpll_mpu_ck", "mpu", false, 1500000000, OMAP4470_VDD_MPU_OPPNITROSB_UV),
+ /*OVERCLOCK*/
+ OPP_INITIALIZER("mpu", "virt_dpll_mpu_ck", "mpu", false, 1600000000, OMAP4470_VDD_MPU_OPPNITROSB_UV),
/* L3 OPP1 - OPP50 */
OPP_INITIALIZER("l3_main_1", "virt_l3_ck", "core", true, 116000000, OMAP4470_VDD_CORE_OPP50_UV),
/* L3 OPP2 - OPP100 */
Not so sure this is needed, but doesn't hurt, I guess.
Code:
@@ -733,7 +736,10 @@
if (!trimmed)
pr_info("This is DPLL un-trimmed SOM. OPP is limited at 1.2 GHz\n");
if (omap4_has_mpu_1_5ghz() && trimmed)
+ omap4_opp_enable("mpu", 1100000000);
+ omap4_opp_enable("mpu", 1300000000);
omap4_opp_enable("mpu", 1500000000);
+ omap4_opp_enable("mpu", 1600000000);
GPU overclock
Code:
@@ -567,13 +570,13 @@
/* SGX OPP2 - OPP100*/
OPP_INITIALIZER("gpu", "dpll_per_m7x2_ck", "core", true, 307200000, OMAP4470_VDD_CORE_OPP100H_UV),
/* SGX OPP3 - OPPOV */
- OPP_INITIALIZER("gpu", "dpll_per_m7x2_ck", "core", true, 384000000, OMAP4470_VDD_CORE_OPP100_OV_UV),
+ OPP_INITIALIZER("gpu", "dpll_per_m7x2_ck", "core", true, 416000000, OMAP4470_VDD_CORE_OPP100_OV_UV),
/* BB2D OPP1 - OPP50 */
OPP_INITIALIZER("bb2d", "dpll_per_m6x2_ck", "core", true, 192000000, OMAP4470_VDD_CORE_OPP50_UV),
/* BB2D OPP2 - OPP100 */
OPP_INITIALIZER("bb2d", "dpll_per_m6x2_ck", "core", true, 307200000, OMAP4470_VDD_CORE_OPP100H_UV),
/* BB2D OPP3 - OPP-OV */
- OPP_INITIALIZER("bb2d", "dpll_per_m6x2_ck", "core", true, 384000000, OMAP4470_VDD_CORE_OPP100_OV_UV),
+ OPP_INITIALIZER("bb2d", "dpll_per_m6x2_ck", "core", true, 416000000, OMAP4470_VDD_CORE_OPP100_OV_UV),
/* FDIF OPP1 - OPP25 */
OPP_INITIALIZER("fdif", "fdif_fck", "core", true, 32000000, OMAP4470_VDD_CORE_OPP50_UV),
/* FDIF OPP2 - OPP50 */
So in making the following changes, if I go to /sys/devices/system/cpu/cpu0/cpufreq
and do a 'cat cpuinfo_max_freq' , I get 1600
a 'cat scaling_available_frequencies' gives:
396800 800000 1100000 1300000 1500000 1600000
I have been unable to test properly because my attempts to make a working boot.img have been unsuccessful.
If anyone could share on how to properly package a zImage and ramdisk.cpio.gz into a flashable boot.img, I would be forever thankful.
I've already extracted the "green loader"/cyanoboot and ramdisk from a working boot.img
I would love to get this working. It would also be fairly easy to tweak the Samsung lpddr ram timings. I also noticed the 'succulent' kernel turned down the core voltage slightly...

OK, so,... are you saying if I go into that folder and make that change it will overclock it?
cuz I'll just go and do that if its that easy.
I don't have any knowlege of compiling kernels so I can't help with that.

I believe it was verygreen who said that he experimented with overclock when building CM and determined it was of little benefit to our devices. That said, I would be most interested in seeing how far we can push the OC on these things, but so far no one with knowledge of Android inner workings wants to build anything for our devices.
Sent from my BN NookHD+ using XDA Premium HD app

I have more questions than answers about it myself.
Nook development seems to be from an "elite" group with closely guarded secrets.
I was actually able to get a "ram console"/last_kmsg
Code:
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.0.31-green+ ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-188) ) #6 SMP PREEMPT Sun Jan 26 09:22:35 EST 2014
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: OMAP4 ovation board
[ 0.000000] Ovation EVT1B detected - selecting Novatek panel
[ 0.000000] android_display: setting default resolution 1920*1280, bpp=4
[ 0.000000] android_display: tiler1d 56623104
[ 0.000000] android_display: setting fb0.vram to 39321600
[ 0.000000] android_display: setting vram to 39321600
[ 0.000000] android_display: ion carveouts: 77594624 tiler2d, 0 nonsecure
[ 0.000000] omap4_total_ram_size = 0x40000000
[ 0.000000] omap4_smc_size = 0x300000
[ 0.000000] omap4_ion_heap_secure_input_size = 0x3000000
[ 0.000000] omap4_ion_heap_secure_output_wfdhdcp_size = 0x1000000
[ 0.000000] omap4_ducati_heap_size = 0x3000000
[ 0.000000] omap4_ion_heap_tiler_mem_size = 0x4a00000
[ 0.000000] omap4_ion_heap_nonsec_tiler_mem_size = 0x0
[ 0.000000] omap4_smc_addr = 0xbfd00000
[ 0.000000] omap4_ion_heap_secure_input_addr = 0xbcd00000
[ 0.000000] omap4_ion_heap_secure_output_wfdhdcp_addr = 0xbbd00000
[ 0.000000] omap4_ducati_heap_addr = 0xb8d00000
[ 0.000000] omap4_ion_heap_tiler_mem_addr = 0xb4300000
[ 0.000000] omap4_ion_heap_nonsec_tiler_mem_addr = 0xb4300000
[ 0.000000] omap_ion_init: secure_input id=2 [bcd00000-bfd00000] size=3000000
[ 0.000000] omap_ion_init: secure_output_wfdhdcp id=5 [bbd00000-bcd00000] size=1000000
[ 0.000000] omap_ion_init: tiler id=1 [b4300000-b8d00000] size=4a00000
[ 0.000000] omap_ion_init: nonsecure_tiler id=3 [b4300000-b4300000] size=0
[ 0.000000] omap_ion_init: system id=0 [0-0] size=0
[ 0.000000] omap_ion_init: tiler_reservation id=4 [0-0] size=0
[ 0.000000] Reserving 39845888 bytes SDRAM for VRAM
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] OMAP4470 ES1.0
[ 0.000000] SRAM: Mapped pa 0x4030d000 to va 0xfe40d000 size: 0x1000
[ 0.000000] SMC: Allocated workspace of 0x300000 Bytes at (0xbfd00000)
[ 0.000000] PERCPU: Embedded 7 pages/cpu @c10a7000 s7136 r8192 d13344 u32768
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 197536
[ 0.000000] Kernel command line: androidboot.hardware=ovation androidboot.serialno=3024550263104319 boot.fb=b2200000
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 256MB 506MB 17MB = 779MB total
[ 0.000000] Memory: 778596k/778596k available, 269980k reserved, 18048K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
[ 0.000000] vmalloc : 0xf0800000 - 0xf8000000 ( 120 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .init : 0xc0008000 - 0xc0083000 ( 492 kB)
[ 0.000000] .text : 0xc0083000 - 0xc06ea000 (6556 kB)
[ 0.000000] .data : 0xc06ea000 - 0xc073ff00 ( 344 kB)
[ 0.000000] .bss : 0xc073ff24 - 0xc089bdf8 (1392 kB)
[ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:410
[ 0.000000] omap_hwmod: dpll_mpu_m2_ck: missing clockdomain for dpll_mpu_m2_ck.
[ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
[ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console [tty0] enabled
[ 0.000915] Calibrating delay loop... 1590.23 BogoMIPS (lpj=6213632)
[ 0.007904] pid_max: default: 32768 minimum: 301
[ 0.031616] Mount-cache hash table entries: 512
[ 0.031616] Initializing cgroup subsys debug
[ 0.031616] Initializing cgroup subsys cpuacct
[ 0.032348] Initializing cgroup subsys freezer
[ 0.032409] CPU: Testing write buffer coherency: ok
[ 0.032928] L310 cache controller enabled
[ 0.032928] l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x5e470000, Cache size: 1048576 B
[ 0.111358] CPU1: Booted secondary processor
[ 0.181396] Brought up 2 CPUs
[ 0.181427] SMP: Total of 2 processors activated (3188.82 BogoMIPS).
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for emif_fw
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l3_instr
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l3_main_1
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l3_main_2
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_abe
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_cfg
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_per
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_wkup
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for mpu_private
[ 0.184814] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for sl2if
[ 0.184814] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for thermal_sensor
[ 0.184906] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for usbhs_ohci
[ 0.184906] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for usbhs_ehci
[ 0.184906] omap_hwmod: l3_div_ck: missing clockdomain for l3_div_ck.
[ 0.184906] omap_hwmod: l4_div_ck: missing clockdomain for l4_div_ck.
[ 0.186859] _omap4_module_wait_ready: Timeout waiting for module enable (mcpdm_fck: clkctrl = 0x30002)
[ 0.189697] omap_hwmod: mcpdm: cannot be enabled (3)
[ 0.194641] print_constraints: dummy:
[ 0.194641] NET: Registered protocol family 16
[ 0.195312] GPMC revision 6.0
[ 0.195312] EMIF0 is enabled with IRQ142
[ 0.196380] EMIF1 is enabled with IRQ143
[ 0.196380] Last reset was cold reset (PRM_RSTST=0x1)
[ 0.196380]
[ 0.196624] OMAP GPIO hardware version 0.1
[ 0.197662] omap_mux_init: Add partition: #1: core, flags: 2
[ 0.199371] omap_mux_init: Add partition: #2: wkup, flags: 2
[ 0.199554] Samsung DDR Memory
[ 0.199645] kxtf9 i2c address = 0xe
[ 0.199920] ovation_touch_init: Registering touch controller device
[ 0.201629] Using Ovation ETV1A wifi configuration
[ 0.206634] OMAP DMA hardware revision 0.0
[ 0.206634] omap_rproc_get_pool: dsp - static memory is unavailable: 0x0, 0x0
[ 0.207031] omap_rproc_get_pool: ipu - carveout memory is unavailable: 0x0, 0x0
[ 0.212768] bio: create slab <bio-0> at 0
[ 0.212951] print_constraints: vdd_lcdtp: 3300 mV normal
[ 0.213531] print_constraints: vwl1271: 1800 mV
[ 0.213531] print_constraints: vsys-wlan: 3875 mV
[ 0.213714] i2c-core: driver [twl] using legacy suspend method
[ 0.213714] i2c-core: driver [twl] using legacy resume method
[ 0.213714] usbcore: registered new interface driver usbfs
[ 0.214172] usbcore: registered new interface driver hub
[ 0.214355] usbcore: registered new device driver usb
[ 0.214935] omap_i2c omap_i2c.1: bus 1 rev4.0 at 400 kHz
[ 0.214935] Skipping twl internal clock init and using bootloader value (unknown osc rate)
[ 0.217071] twl6030: PIH (irq 39) chaining IRQs 368..387
[ 0.218963] print_constraints: LDOUSB: 3300 mV normal standby
[ 0.221466] twl6030_usb twl6030_usb: Initialized TWL6030 USB module
[ 0.224090] print_constraints: VANA: 2100 mV normal standby
[ 0.224731] print_constraints: CLK32KG:
[ 0.225402] print_constraints: CLK32KAUDIO:
[ 0.226318] print_constraints: SYSEN:
[ 0.227203] print_constraints: REGEN1:
[ 0.227630] print_constraints: LDO5: 1200 <--> 3000 mV at 3000 mV normal standby
[ 0.228210] print_constraints: LDO1: 1800 <--> 2500 mV at 1700 mV normal standby
[ 0.228668] suspend_set_state: LDO7: No configuration
[ 0.228881] print_constraints: LDO7: 1800 mV normal standby
[ 0.229858] print_constraints: LDO6: 1800 mV normal standby
[ 0.230651] print_constraints: LDOLN: 1800 mV normal standby
[ 0.231506] print_constraints: LDO2: 1000 <--> 3000 mV at 2800 mV normal standby
[ 0.231903] print_constraints: LDO4: 1800 mV normal standby
[ 0.232696] print_constraints: LDO3: 1800 mV normal standby
[ 0.233123] omap_i2c omap_i2c.3: bus 3 rev4.0 at 400 kHz
[ 0.233825] omap-rproc omap-rproc.0: dsp is available
[ 0.233825] omap-rproc omap-rproc.1: ipu is available
[ 0.233825] Advanced Linux Sound Architecture Driver Version 1.0.24.
[ 0.234588] Bluetooth: Core ver 2.16
[ 0.234588] NET: Registered protocol family 31
[ 0.234588] Bluetooth: HCI device and connection manager initialized
[ 0.234588] Bluetooth: HCI socket layer initialized
[ 0.234588] Bluetooth: L2CAP socket layer initialized
[ 0.234771] Bluetooth: SCO socket layer initialized
[ 0.234771] Switching to clocksource 32k_counter
[ 0.236053] Switched to NOHz mode on CPU #0
[ 0.236083] Switched to NOHz mode on CPU #1
[ 0.241699] musb-hdrc: version 6.0, musb-dma, otg (peripheral+host)
[ 0.242248] musb-hdrc musb-hdrc: USB OTG mode controller at fc0ab000 using DMA, IRQ 124
[ 0.242675] NET: Registered protocol family 2
[ 0.242706] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.243774] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.243774] TCP bind hash table entries: 65536 (order: 8, 1572864 bytes)
[ 0.243774] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.243774] TCP reno registered
[ 0.243774] UDP hash table entries: 512 (order: 3, 32768 bytes)
[ 0.248352] UDP-Lite hash table entries: 512 (order: 3, 32768 bytes)
[ 0.248352] NET: Registered protocol family 1
[ 0.267456] Trying to unpack rootfs image as initramfs...
[ 0.359802] Freeing initrd memory: 1832K
[ 0.812927] omap_init_opp_table: no hwmod or odev for hsi, [26] cannot add OPPs.
[ 0.812927] omap_init_opp_table: no hwmod or odev for hsi, [27] cannot add OPPs.
[ 1.328552] ram_console: got buffer at 90000000, size 200000
[ 1.329376] ram_console: no valid data in buffer (sig = 0x08f9f706)
[ 1.329650] console [ram-1] enabled
[ 1.329650] omap-iommu omap-iommu.0: ducati registered
[ 1.329650] omap-iommu omap-iommu.1: tesla registered
[ 1.337341] highmem bounce pool size: 64 pages
[ 1.337646] ashmem: initialized
[ 1.344177] fuse init (API version 7.16)
[ 1.344787] msgmni has been set to 1489
[ 1.344787] Registering char device tf_driver (122:0)
[ 1.344787] SMCAG01.06p6.0 D
[ 1.346649] io scheduler noop registered
[ 1.346649] io scheduler deadline registered (default)
[ 1.346649] io scheduler cfq registered
[ 1.346771] start plist test
[ 1.350708] end plist test
[ 1.751861] OMAP DSS rev 4.1
[ 1.754333] Keyboard driver not present
[ 1.755004] novatek-panel display0: novatek_probe
[ 1.755065] novatek-panel display0: novatek_probe done
[ 1.755065] dsscomp: initializing.
[ 1.755065] misc dsscomp: display0=novatek-panel
[ 1.755065] misc dsscomp: display1=hdmi_panel
[ 1.755065] misc dsscomp: found 2 displays and 4 overlays, WB overlay 1
[ 1.755859] could not allocate slot
[ 1.756011] omap-rproc omap-rproc.1: powering up ipu
[ 1.756378] virtio_rpmsg_bus virtio0: rpmsg backend virtproc probed successfully
[ 1.756988] virtio_rpmsg_bus virtio1: rpmsg backend virtproc probed successfully
[ 1.756988] omap-rproc omap-rproc.0: powering up dsp
[ 1.757446] virtio_rpmsg_bus virtio2: rpmsg backend virtproc probed successfully
[ 1.757446] omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP UART0
[ 1.758636] omap_uart.3: ttyO3 at MMIO 0x4806e000 (irq = 102) is a OMAP UART3
[ 1.759094] omap_ion_probe: adding heap secure_input of type 2 with [email protected]
[ 1.759094] omap_ion_probe: adding heap secure_output_wfdhdcp of type 2 with [email protected]
[ 1.759552] omap_ion_probe: adding heap tiler of type 4 with [email protected]
[ 1.759552] omap_ion_probe: adding heap nonsecure_tiler of type 4 with [email protected]
[ 1.759704] omap_ion_probe: adding heap system of type 0 with [email protected]
[ 1.759704] omap_ion_probe: adding heap tiler_reservation of type 5 with [email protected]
[ 1.759704] brd: module loaded
[ 1.766052] loop: module loaded
[ 1.766052] usbcore: registered new interface driver ub
[ 1.766052] (stk) :sysfs entries created
[ 1.766052] (stk) : debugfs entries created
[ 1.769134] (hci_tty): inside hci_tty_init
[ 1.769134] (hci_tty): allocated 251, 0
[ 1.799896] tun: Universal TUN/TAP device driver, 1.6
[ 1.799896] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
[ 1.799896] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.799896] usbcore: registered new interface driver usbserial
[ 1.802398] USB Serial support registered for generic
[ 1.802398] usbcore: registered new interface driver usbserial_generic
[ 1.802490] usbserial: USB Serial Driver core
[ 1.802490] USB Serial support registered for GSM modem (1-port)
[ 1.802490] usbcore: registered new interface driver option
[ 1.802490] option: v0.7.2:USB Driver for GSM modems
[ 1.802673] USB Serial support registered for pl2303
[ 1.802673] usbcore: registered new interface driver pl2303
[ 1.802825] pl2303: Prolific PL2303 USB to serial adaptor driver
[ 1.804382] android_usb gadget: Mass Storage Function, version: 2009/09/11
[ 1.804412] android_usb gadget: Number of LUNs=1
[ 1.804412] lun0: LUN: removable file: (no medium)
[ 1.804504] android_usb gadget: android_usb ready
[ 1.804504] musb-hdrc musb-hdrc: MUSB HDRC host driver
[ 1.804504] musb-hdrc musb-hdrc: new USB bus registered, assigned bus number 1
[ 1.804931] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.804931] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.805114] usb usb1: Product: MUSB HDRC host driver
[ 1.805114] usb usb1: Manufacturer: Linux 3.0.31-green+ musb-hcd
[ 1.805114] usb usb1: SerialNumber: musb-hdrc
[ 1.805694] hub 1-0:1.0: USB hub found
[ 1.805694] hub 1-0:1.0: 1 port detected
[ 1.806274] mousedev: PS/2 mouse device common for all mice
[ 1.806854] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 1.807067] input: omap4-keypad as /devices/platform/omap/omap4-keypad/input/input1
[ 1.807800] usbcore: registered new interface driver xpad
[ 1.807861] FTX: ft5x06_module_init(): INFO: Initializing FT I2C Touchscreen Driver (Built Jan 26 2014 @ 09:05:13)
[ 1.807861] 3-0038: FTX: ft5x06_probe(): INFO: probing for ft5x06-i2c @ 3-0038 .
[ 2.079406] 3-0038: FTX: ft5x06_probe(): INFO: focaltech controller with Product ID=0x06 found @ 0x38.
[ 2.138580] 3-0038: FTX: ftx_input_device_initialize(): INFO: Successfully initialzed slots; using Type B protocol.
[ 2.138580] input: ft5x06-i2c as /devices/platform/omap/omap_i2c.3/i2c-3/3-0038/input/input2
[ 2.138580] twl6030_pwrbutton_probe: Enter
[ 2.139739] input: twl6030_pwrbutton as /devices/platform/omap/omap_i2c.1/i2c-1/1-0049/twl6030_pwrbutton/input/input3
[ 2.242523] kxtf9 1-000e: WHO_AM_I = 0x08
[ 2.242523] kxtf9(8) detected
[ 2.243164] input: kxtf9_accel as /devices/virtual/input/input4
[ 2.244049] input: twl6040_hskeys as /devices/platform/omap/omap_i2c.1/i2c-1/1-004b/twl6040-audio/twl6040-hskeys/input/input5
[ 2.247314] using rtc device, twl_rtc, for alarms
[ 2.247680] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
[ 2.247894] i2c /dev entries driver
[ 2.247894] Linux video capture interface: v2.00
[ 2.248321] usbcore: registered new interface driver uvcvideo
[ 2.248321] USB Video Class driver (v1.1.0)
[ 2.248321] dmm: probe base: fd300000, irq 145
[ 2.248321] finish bat_low irq. gpio_bat_low:42
[ 2.250579] bq27x00-battery 1-0055: support ver. 1.2.0 enabled
[ 2.466979] bq2419x driver init
[ 2.467041] bq2419x probe
[ 2.467254] bq24196 1-006b: read_reg=0x2a
[ 2.467254] bq24196 1-006b: identified chip BQ24196_REV_1_3
[ 2.467315] bq24196 1-006b: found chip at 0x6b
[ 2.468292] bq24196 1-006b: omap_get_clk_load: 0x821d6fff
[ 2.468780] bq24196 1-006b: resting registers
[ 2.469787] bq24196 1-006b: INTERRUPT 08=0, 09=0
[ 2.469787] bq24196 1-006b: S: Not Power Good
[ 2.469848] bq24196 1-006b: S: CHARGE STATE = 0 (NOT CHARGING)
[ 2.469879] bq24196 1-006b: S: VBUS STATE = 0 (Unknown)
[ 2.469909] device-mapper: uevent: version 1.0.3
[ 2.469909] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: [email protected]
[ 2.469909] Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0
[ 2.473449] cpuidle: using governor ladder
[ 2.473480] cpuidle: using governor menu
[ 2.478057] Registered led device: omap4:green:debug0
[ 2.479034] usbcore: registered new interface driver usbhid
[ 2.479064] usbhid: USB HID core driver
[ 2.479095] usbip_core: USB/IP Core v1.0.0
[ 2.479370] vhci_hcd vhci_hcd: USB/IP Virtual Host Controller
[ 2.479431] vhci_hcd vhci_hcd: new USB bus registered, assigned bus number 2
[ 2.479888] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.479919] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.479949] usb usb2: Product: USB/IP Virtual Host Controller
[ 2.479980] usb usb2: Manufacturer: Linux 3.0.31-green+ vhci_hcd
[ 2.480010] usb usb2: SerialNumber: vhci_hcd
[ 2.480529] hub 2-0:1.0: USB hub found
[ 2.480560] hub 2-0:1.0: 8 ports detected
[ 2.480895] vhci_hcd: USB/IP 'Virtual' Host Controller (VHCI) Driver v1.0.0
[ 2.481079] usbcore: registered new interface driver usbip
[ 2.481109] usbip_host: USB/IP Host Driver 1.0.0
[ 2.481445] logger: created 256K log 'log_main'
[ 2.481567] logger: created 256K log 'log_events'
[ 2.481689] logger: created 256K log 'log_radio'
[ 2.481811] logger: created 256K log 'log_system'
[ 2.482147] pcb_temp_sensor pcb_temp_sensor.0: pcb_sensor : 'pcb_temp_sensor'
[ 2.485229] SDP4430 SoC init
[ 2.489685] twl6040-codec twl6040-codec: couldn't get VDDHF regulator -19
[ 2.521148] asoc: null-codec-dai <-> MultiMedia1 mapping ok
[ 2.522430] asoc: null-codec-dai <-> MultiMedia2 mapping ok
[ 2.527130] asoc: null-codec-dai <-> Voice mapping ok
[ 2.528259] asoc: null-codec-dai <-> Tones mapping ok
[ 2.529388] asoc: null-codec-dai <-> Vibra mapping ok
[ 2.530212] asoc: null-codec-dai <-> MODEM mapping ok
[ 2.530944] asoc: null-codec-dai <-> MultiMedia1 LP mapping ok
[ 2.532409] asoc: FM Digital <-> omap-mcbsp-dai.1 mapping ok
[ 2.533508] asoc: twl6040-dl1 <-> mcpdm-dl mapping ok
[ 2.535247] asoc: dmic-hifi <-> omap-dmic-dai-0 mapping ok
[ 2.537628] twl6040-codec twl6040-codec: ASoC: Failed to create Aux/FM Stereo In debugfs file
[ 2.538574] asoc: twl6040-dl1 <-> mcpdm-dl1 mapping ok
[ 2.539398] asoc: twl6040-ul <-> mcpdm-ul1 mapping ok
[ 2.540252] asoc: twl6040-dl2 <-> mcpdm-dl2 mapping ok
[ 2.541107] asoc: twl6040-vib <-> mcpdm-vib mapping ok
[ 2.541992] asoc: Bluetooth <-> omap-mcbsp-dai.2 mapping ok
[ 2.542877] asoc: Bluetooth <-> omap-mcbsp-dai.2 mapping ok
[ 2.543762] asoc: FM Digital <-> omap-mcbsp-dai.1 mapping ok
[ 2.544616] asoc: MODEM <-> omap-mcbsp-dai.1 mapping ok
[ 2.545501] asoc: dmic-hifi <-> omap-dmic-abe-dai-0 mapping ok
[ 2.546356] asoc: dmic-hifi <-> omap-dmic-abe-dai-1 mapping ok
[ 2.547210] asoc: dmic-hifi <-> omap-dmic-abe-dai-2 mapping ok
[ 2.548187] asoc: null-codec-dai <-> omap-abe-vxrec-dai mapping ok
[ 2.550445] input: Ovation Line-Out Jack as /devices/platform/soc-audio/sound/card0/input6
[ 2.550781] input: Ovation Headset Jack as /devices/platform/soc-audio/sound/card0/input7
[ 2.553558] asoc: hdmi-audio-codec <-> hdmi-audio-dai mapping ok
[ 2.554046] ALSA device list:
[ 2.554046] #0: TI OMAP4 Board
[ 2.554077] #1: OMAP4HDMI
[ 2.554168] GACT probability NOT on
[ 2.554199] Mirror/redirect action on
[ 2.554229] u32 classifier
[ 2.554229] Actions configured
[ 2.554260] Netfilter messages via NETLINK v0.30.
[ 2.554351] nf_conntrack version 0.5.0 (12194 buckets, 48776 max)
[ 2.555267] xt_time: kernel timezone is -0000
[ 2.556274] IPv4 over IPv4 tunneling driver
[ 2.557647] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 2.557739] TCP cubic registered
[ 2.557769] NET: Registered protocol family 17
[ 2.557800] NET: Registered protocol family 15
[ 2.557922] Bluetooth: RFCOMM TTY layer initialized
[ 2.557952] Bluetooth: RFCOMM socket layer initialized
[ 2.557983] Bluetooth: RFCOMM ver 1.11
[ 2.558013] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 2.558105] lib80211: common routines for IEEE802.11 drivers
[ 2.558135] lib80211_crypt: registered algorithm 'NULL'
[ 2.558166] Registering the dns_resolver key type
[ 2.558197] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 2.558258] ThumbEE CPU extension supported.
[ 2.558288] Registering SWP/SWPB emulation handler
[ 2.561767] >>> setting nvalues for oh = smartreflex_core
[ 2.561828] >>> sr_set_nvalues v = 10145780, sr_efuse_offs = 254
[ 2.561828] >>> sr_set_nvalues v = 10126506, sr_efuse_offs = 257
[ 2.561859] >>> sr_set_nvalues v = 10126506, sr_efuse_offs = 257
[ 2.561889] >>> sr_set_nvalues v = 11198099, sr_efuse_offs = 25a
[ 2.562133] >>> setting nvalues for oh = smartreflex_iva
[ 2.562164] >>> sr_set_nvalues v = 10091001, sr_efuse_offs = 22c
[ 2.562194] >>> sr_set_nvalues v = 10063493, sr_efuse_offs = 22f
[ 2.562194] >>> sr_set_nvalues v = 11202269, sr_efuse_offs = 232
[ 2.562225] >>> sr_set_nvalues v = 11182739, sr_efuse_offs = 235
[ 2.562255] >>> sr_set_nvalues v = 11177602, sr_efuse_offs = 238
[ 2.562408] >>> setting nvalues for oh = smartreflex_mpu
[ 2.562438] >>> sr_set_nvalues v = 10141671, sr_efuse_offs = 240
[ 2.562469] >>> sr_set_nvalues v = 11205796, sr_efuse_offs = 243
[ 2.562500] >>> sr_set_nvalues v = 11190917, sr_efuse_offs = 246
[ 2.562530] >>> sr_set_nvalues v = 11247585, sr_efuse_offs = 249
[ 2.562561] >>> sr_set_nvalues v = 11245013, sr_efuse_offs = 24c
[ 2.562774] Reprogramming LPDDR2 timings to 466666666 Hz
[ 2.563018] sr_init: No PMIC hook to init smartreflex
[ 2.563201] smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
[ 2.563415] smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
[ 2.563598] smartreflex smartreflex.2: omap_sr_probe: SmartReflex driver initialized
[ 2.563903] SmartReflex class 1.5 driver: initialized (86400000ms)
[ 2.564117] cpufreq_interactive_input_connect: connect to ft5x06-i2c
[ 2.564178] 3-0038: FTX: ft5x06_resume(): INFO: driver is resuming.
[ 2.564575] Power Management for TI OMAP4.
[ 2.564727] OMAP4 PM: Static dependency added between MPUSS and DUCATI <-> L4_PER/CFG and L3_1.
[ 2.570953] mmc0: new high speed DDR MMC card at address 0001
[ 2.571380] mmcblk0: mmc0:0001 MBG4GA 29.1 GiB
[ 2.571563] mmcblk0boot0: mmc0:0001 MBG4GA partition 1 2.00 MiB
[ 2.571746] mmcblk0boot1: mmc0:0001 MBG4GA partition 2 2.00 MiB
[ 2.574066] Alternate GPT is invalid, using primary GPT.
[ 2.574188] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10
[ 2.576599] mmcblk0boot1: unknown partition table
[ 2.577514] mmcblk0boot0: unknown partition table
[ 2.579376] clock: disabling unused clocks to save power
[ 2.641052] sr_class1p5_calib_work: iva Stop sampling: Voltage Nominal=950000 samples=12
[ 2.641082] sr_class1p5_calib_work: iva: Calibration complete: Voltage Nominal=950000Calib=835600 margin=0
[ 2.714233] mmc1: host does not support reading read-only switch. assuming write-enable.
[ 2.727020] mmc1: new high speed SDHC card at address 1234
[ 2.727325] mmcblk1: mmc1:1234 SA16G 14.6 GiB
[ 2.728820] mmcblk1: p1 p2 p3
[ 2.729339] Enable wl12xx power
[ 2.821319] 3-0038: FTX: ft5x06_resume(): INFO: driver resumed.
[ 2.950256] mmc2: card claims to support voltages below the defined range. These will be ignored.
[ 2.953399] copying uboot splash: 39321600 bytes from 0xf5000000 to 0xf2000000
[ 2.985473] mmc2: queuing unknown CIS tuple 0x91 (3 bytes)
[ 2.986083] mmc2: new SDIO card at address 0001
[ 2.986694] Disable wl12xx power
[ 3.144378] cannot apply mgr(lcd) on inactive device
[ 3.163330] Console: switching to colour frame buffer device 240x80
[ 3.182678] cannot apply mgr(lcd) on inactive device
[ 3.182769] omapfb omapfb: failed to apply dispc config
[ 3.182861] cannot apply mgr(tv) on inactive device
[ 3.182983] omapfb omapfb: failed to apply dispc config
[ 3.183074] cannot apply mgr(lcd2) on inactive device
[ 3.183197] omapfb omapfb: failed to apply dispc config
[ 3.183258] novatek-panel display0: enable
[ 3.183319] novatek-panel display0: power_on
[ 3.183746] novatek-panel display0: power_on done
[ 3.184326] regulator_init_complete: LDO1: disabling
[ 3.185791] twl_rtc twl_rtc: setting system clock to 2014-01-27 04:13:49 UTC (1390796029)
[ 3.186096] Warning: unable to open an initial console.
[ 3.186218] Freeing init memory: 492K
[ 3.203613] sr_class1p5_calib_work: mpu: Calibration complete: Voltage Nominal=1380000Calib=1316680 margin=0
[ 3.219207] sr_class1p5_calib_work: core: Calibration complete: Voltage Nominal=1190000Calib=1076140 margin=0
[ 3.259979] init: cannot open '/initlogo.rle'
[ 3.280609] init: Unable to open persistent property directory /data/property errno: 2
[ 3.280883] 3-0038: FTX: ft5x06_suspend(): INFO: driver is suspending.
[ 3.289459] 3-0038: FTX: ft5x06_suspend(): INFO: driver suspended.
[ 3.311126] omap-rproc omap-rproc.0: rproc_loader_cont: failed to load tesla-dsp.bin
[ 3.311523] omap-rproc omap-rproc.1: rproc_loader_cont: failed to load ducati-m3.bin
[ 3.330047] HDCP: failed to load keys
[ 3.353820] android_usb: already disabled
[ 3.354064] init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
[ 3.354278] init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
[ 3.354492] init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
[ 3.354766] android_usb: already disabled
[ 3.355957] adb_open
[ 3.355987] adb_bind_config
[ 3.356567] SysRq : Emergency Remount R/O
[ 3.356689] Emergency Remount complete
[ 3.357208] Disabling non-boot CPUs ...
[ 3.357666] CPU1: shutdown
[ 3.563873] 3-0038: FTX: INFO: Shutdown.
[ 3.579956] bq24196 1-006b: bq2419x_charger_shutdown
[ 3.595825] kxtf9: Shutdown.
[ 3.626617] omap_hsmmc omap_hsmmc.1: shutting down mmc
[ 3.667175] novatek-panel display0: disable
[ 3.685577] Restarting system with command 'bootloader'.
[ 3.700927]
[ 3.716278] Restarting Linux version 3.0.31-green+ ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-188) ) #6 SMP PREEMPT Sun Jan 26 09:22:35 EST 2014
[ 3.716278]
0 Corrected bytes, 218 unrecoverable blocks
I believe part of my problem is that (my) toolchain needs to match that with what CM was built with. (Which means I would probably have to build the whole CM package in order for it to work). I have an overclocked recovery, but that doesn't make much sense
There seems to be lots of discussion between conflicts between smartreflex and various governors.
Since these things normally run at 396 or 800 Mhz, I wonder if it would be more advantageous to tweak ram settings and such at those speeds
TBH, my main goal is to get Arch linux on this thing.
To that end, I plan on purchasing a Prolific PL2303 USB to serial adaptor so as to have a console.
This won't help me with any bootloader work, but I don't wish to disassemble my nook to solder in two wires to get a uart console (would still have to purchase a FT232RL USB to Serial breakout board for voltage level shifting).

Success! Check out the attached screenshots. First benchmark is stock CM10.1, second benchmark is with overclocked kernel. CM10.1 doesn't benchmark near as well as CM11 or Carbon, so I imagine I could great results using a Carbon rom.

Awesome man, I'm impressed. Were you modifying voltage as well? Also let us know how far you can take it.

Holy cr$$. Does actual use feel as fast as benchmark indicates? Is your nook hot? Does it crash all over the place? (I guess it's stable enough to finish the benchmark!) What does this do to your battery life?

This was mainly meant as a proof of concept, in trying to elicit kernel development discussion and trying to fish for more information on how to do it.
I was slightly frustrated in that there's overclock kernels available for the kindle fire hd (same proc as ours), but if you follow the links to source, the overclock code is always missing. They have AVAILABLE: CPU up to 1.7 and GPU up to 512. I don't think anyone is actually achieving that.
After playing with it for awhile my take is that these things are maxed out already. I did leave stock voltages alone.
1600 seems to work OK, instead of adding extra stepping, prolly easier just to change the two 1500's to 1600's.
GPU over clock is buggy in that it breaks video playback of certain formats (probably a timings issue). I've heard of people getting up to 440.
No overclock is bug free for me.
Samsung lpddr ram timings are interesting, but again not much leeway.
Here's some info to anyone interested.
I used the gcc-linaro-arm-linux-gnueabihf-4.7-2013.04-20130415_linux.tar toolchain, available on the launchpad linaro toolchain binaries download page (after fighting with crosstool-ng).
A big help for me was using a hex editor, ended up compiling okteta.
Take a working boot.img open it in your hex editor. Cut 0000:0000 - 000F:FFFF, this is your "green loader". (I realize this can be done with dd, have at it).
After this has been cut out, your boot.img can be split into zImage and initramfs.cpio.gz using umkbootimg. This will also give the command to put it back together.
Code:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x80000000 --cmdline 'androidboot.console=ttyO0 console=ttyO0,115200n8 def_disp=lcd2' --pagesize 4096 -o new_boot.img
Then you will need to take your new_boot.img and append the green loader onto the beginning (turn off overwrite mode).
To fix ram_console turn on little endian support in kernel config (missing in official builds to date).
Good luck! I wish I had been given this tutorial....
Edit: I also played around with adding various I/O schedulers, I expect to do the same with governors as time permits.
These would probably make the most difference in battery life and performance.

Wrong boot.img. The one posted has IPv6 disabled in the kernel (as an experiment). Most everything google is broken (although browser still works). It does have some interesting logcat entries (googleconversionpings and such). It actually does a good job if you want a very basic secure tablet.
Here, this should be correct.
(1620/405)
mediafire<dot>com/download/6xjogrrbt1693ps/cm-10.1.3-ovation_OC2.zip
BTW, the config can be found in /proc/config.gz. Also compiled with kexec support.

Third version.
I believe this to be the smoothest, fastest, (and I dare say), most stable rom out there available for the HD+/ovation.
Give it a test run and tell me what you think.
Video playback performance is phenomenal.
mediafire<dot>com/download/6uvpqid45l5s99d/cm-10.1.3-ovation_OC3.zip
(kernel version should read Tue Mar 11 17:14, if I packed it correctly)
my kernel source:
mediafire<dot>com/download/d289cudx4pq6bvm/android_kernel_bn_omap-cm-10.1_v1.tar.gz
extra kernel modules, most users won't need these unless you're trying to set up a vpn or something:
mediafire<dot>com/download/670pzf1r2lu1dy8/extra_modules_ovation_cm10.1.3.tar.gz
A collection of linux tools for .img file work in case someone wants to make their own kernel
mediafire<dot>com/download/ny2209vapfi8ngg/bootimg_tools_ovation_1.tar.gz
What I have for pvr-sgx kernel module source.
mediafire<dot>com/download/04z6o0xlp513h4l/pvr_source.tar.gz
I think the kernel or the pvr source needs a patch (possibly something to do with remoteproc power management), as the versions I've compiled are unstable.
It could possibly be the command line I'm using?
make ARCH=arm CROSS_COMPILE=arm-eabi- BUILD=release TARGET_SGX=544sc
Click to expand...
Click to collapse
Could anyone help me on this? Being able to compile working pvr modules would help greatly with kernel development (so the pvr matches the kernel you're hacking).
Anyway I believe the above ROM is going to be my go-to daily driver.

Took a stab at fixing our ft5x06 touchscreen issues.
This is the result:
http://www.mediafire.com/download/he3reojs86oh0b3/ovation-kernel-cm10.1.3_v1.zip
(just the kernel- to be flashed over one of my previous roms).
Much better touchscreen performance (took out the twitch without using "fuzz", and I haven't experienced any more lockups with random/phantom touches, focus/selecting seems to work better too... but I'm still testing).
Surprisingly enough the issues seem to have been with kernel 3.0 i2c-core bus drivers rather than the touchscreen driver itself.

OCCCC
Although overclocking is obviously against CM policy, I'd love it for our Nooks to have access to modifying our CPU speeds.
But then I read awhile back that verygreen said that ocing the CPU didn't improve much and speculated that ocing the GPU would help more. o.o

I'm continuing to work on it and fine tune the results as time permits (until I'm happy with it).
This is my latest.
http://www.mediafire.com/download/hk136whf6f0ew60/ovation-kernel-cm10.1.3_v2.zip
(again kernel update only- to be flashed over one of my previous roms).
This one has lowered voltages. Slightly modified ram timings.
Same basic overclock and has the touchscreen fixes.
I ran into a problem where my browser was crashing and logs indicated libdrm/dalvik.
Wiping the dalvik cache took care of it. Just FYI, as it took me forever to figure out.
I haven't had a single crash on this kernel yet.
This one should run much cooler than even stock.

Jon Lee said:
I'm continuing to work on it and fine tune the results as time permits (until I'm happy with it).
This is my latest.
http://www.mediafire.com/download/hk136whf6f0ew60/ovation-kernel-cm10.1.3_v2.zip
(again kernel update only- to be flashed over one of my previous roms).
This one has lowered voltages. Slightly modified ram timings.
Same basic overclock and has the touchscreen fixes.
I ran into a problem where my browser was crashing and logs indicated libdrm/dalvik.
Wiping the dalvik cache took care of it. Just FYI, as it took me forever to figure out.
I haven't had a single crash on this kernel yet.
This one should run much cooler than even stock.
Click to expand...
Click to collapse
I flashed this over CM10.1 stable and got a bootloop. What do you mean with "flash over one my previous roms" - which ROMs?
EDIT: My bad, didn't see the links you posted. They weren't red like usual.
I will try it! Thanks!
EDIT2: Wow, it is really stable and fast. But i have extreme touchscreen twitching on the right hand side of the screen. Increasing Fuzz fixed that for me in other builds.
EDIT3: Got random reboot while restoring apps with Titanium Backup. It would be great it you could take a look at the log. I have been getting reboots on every ROM out there, maybe you know the problem.
last_kmsg: https://drive.google.com/file/d/0B5xpEXQcSQncMENxR3lyOXAwNlU/edit?usp=sharing
And do I have to flash the ROM, Kernel v1 and then v2 or does v2 include the changes from v1?

Here's a complete, to-date ROM. (So as to save from flashing multiple files).
http://www.mediafire.com/download/cifx5qa8xvv3u1j/cm-10.1.3-ovation_OC4.zip
Be sure to wipe dalvik cache!
I'm not sure if you can use titanium to restore apps from 10.2 to 10.1 without causing problems.
Just a note, you won't be able to flash my kernel updates on stock CM without being prepared to adb push /system/lib/modules/*
(IE bootloops, etc)
If you continue to have problems with wl12xx, I would take a look at your wireless access point settings (perhaps change encryption type, etc).
I see a lot of deauthenticated, reason 7. I would love to fix this but compiling my own working wl12xx drivers is a major PITA.

Jon Lee said:
Here's a complete, to-date ROM. (So as to save from flashing multiple files).
http://www.mediafire.com/download/cifx5qa8xvv3u1j/cm-10.1.3-ovation_OC4.zip
Be sure to wipe dalvik cache!
I'm not sure if you can use titanium to restore apps from 10.2 to 10.1 without causing problems.
Just a note, you won't be able to flash my kernel updates on stock CM without being prepared to adb push /system/lib/modules/*
(IE bootloops, etc)
If you continue to have problems with wl12xx, I would take a look at your wireless access point settings (perhaps change encryption type, etc).
I see a lot of deauthenticated, reason 7. I would love to fix this but compiling my own working wl12xx drivers is a major PITA.
Click to expand...
Click to collapse
This one has your kernel already in it correct? Any special recovery needed?

Jon Lee said:
Here's a complete, to-date ROM. (So as to save from flashing multiple files).
http://www.mediafire.com/download/cifx5qa8xvv3u1j/cm-10.1.3-ovation_OC4.zip
Be sure to wipe dalvik cache!
I'm not sure if you can use titanium to restore apps from 10.2 to 10.1 without causing problems.
Just a note, you won't be able to flash my kernel updates on stock CM without being prepared to adb push /system/lib/modules/*
(IE bootloops, etc)
If you continue to have problems with wl12xx, I would take a look at your wireless access point settings (perhaps change encryption type, etc).
I see a lot of deauthenticated, reason 7. I would love to fix this but compiling my own working wl12xx drivers is a major PITA.
Click to expand...
Click to collapse
Okay, I will try that.
So what exactly was the reason for my reboot? What is wl 12xx? I am not an expert

Slightly aggravated. Typed a long post, only to be logged out, and lost it, and I continue to have login/password issues.
Calling this project quits.
This is THE FINAL VERSION.
http://www.mediafire.com/download/x4cksy5scvi1874/cm-10.1.3-ovation_OC5.zip
WORKING PVR SOURCE.
http://www.mediafire.com/download/at6yl23jrvpweav/pvr_source_1.tar.gz
Kernel source than matches rom above.
http://www.mediafire.com/download/ohcxmrgz9j4ly8y/android_kernel_bn_omap-cm-10.1_v2.tar.gz
What this lacks.
http://processors.wiki.ti.com/index...1_compat_wireless_implementation_Architecture
Thank you.
Edit: BTW, that was a quick fix from OC4, which was no good (voltages). Working pvr_sgx source opens up a whole can of worms as far as having matching dpll_cascading symbols in the pvr module or not (as far as kernel updates go), which is a good enough reason to call it quits here to save on confusion. Seriously, the above is as good as I'm going to get it.
To put it another way, no other kernels will work on this ROM (pvr missing dpll_cascading symbols), and If I were to make any other kernel updates, they wouldn't work on any other roms (including the first ones I did).

Jon Lee said:
Here's a complete, to-date ROM. (So as to save from flashing multiple files).
cm-10.1.3-ovation_OC4.zip
Be sure to wipe dalvik cache!
I'm not sure if you can use titanium to restore apps from 10.2 to 10.1 without causing problems.
Just a note, you won't be able to flash my kernel updates on stock CM without being prepared to adb push /system/lib/modules/*
(IE bootloops, etc)
If you continue to have problems with wl12xx, I would take a look at your wireless access point settings (perhaps change encryption type, etc).
I see a lot of deauthenticated, reason 7. I would love to fix this but compiling my own working wl12xx drivers is a major PITA.
Click to expand...
Click to collapse
wow I don't know, what was wrong with my device or with CM10.2 (I had a lot of Reboots every day) but this release works like a charm :good:
actually i wasn't intrested in OC (becauce of Battery usage) but if this CM is the only stable release for my device I will keep it
thx man

Thanks, if it wasn't obvious, I was more interested in stability than I was in any overclock... (for me), because I'm wanting to use this too. I did try to take care of several kernel bugs that were common across all ROMS (l3_noc, mmc, I2C), without causing further problems.
That last version does seem stable (especially if you clear dalvik cache after installing). One thing I did notice is that I played with IVA clock a little (as an experiment), and although we don't use DSP/tesla, it seems to have slightly affected the I2C touchscreen bug. Perhaps the IVA clock is somehow connected to the I2C clock. I'm making one now where I reduced it instead of increasing it, and see if that further reduces any I2C jitters. Shouldn't affect performance because we don't use tesla (although as an experiment, I did get a tesla bin to load properly, and even had the rpmsg communication channel and everything).
I also managed to compile a compat.ko module last night. Still doesn't work properly. WIFI is going to kick my butt. That is really the last thing that remains to be done.
Eventually, if I could leave well enough alone, I would like to see how long I could go without a reboot, and we could prove "What is the Most Stable ROM" debate scientifically with a 'cat /proc/uptime', but at the moment I'm continually playing with it, so I'm not going to have a decent uptime.

[BUGREPORT] stock kernel 3.4.0-perf-g32ce454

Hi, i think that there is a network-related bug in stock kernel.
Phone reboots very often, when in stamina mode is on
Here is part oflast_kmsg:
Code:
[ 440.537078] active wake lock mmc1_detect
[ 440.537475] active wake lock msm_hsic_host
[ 440.537689] active wake lock alarm, time left 497
[ 440.589263] [B][COLOR="Red"]skb_under_panic: text:c04dd4e8 len:66 put:6 head:cd3af000 data:cd3aeffa tail:0xcd3af03c end:0xcd3af140 [U]dev:rmnet_usb0[/U][/COLOR][/B]
[ 440.589874] ------------[ cut here ]------------
[ 440.590332] kernel BUG at /home/hudsonslave/root/workspace/offbuild_lagan-1.3_android_matrix/HUDSON_PRODUCT/yuga/HUDSON_VARIANT/user/label/CM-12/kernel/net/core/skbuff.c:146!
[ 440.590789] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[ 440.591247] Modules linked in: wlan(O) texfat(PO) cfg80211
[ 440.592376] CPU: 0 Tainted: P W O (3.4.0-perf-g32ce454 #1)
[ 440.592803] PC is at skb_push+0x6c/0x80
[ 440.593017] LR is at skb_push+0x6c/0x80
"head:cd3af000 data:cd3aeffa" - data before head ??? What might cause that???

[DEV-ONLY] CM12 for XT1085 (Chinese Ver)

I have been successfully port cm12 to XT1085, there is almost no difference between 1095 and 1085, and most work has been done by crpalmer.
Here is the changes I made to XT1085: https://github.com/kghost/android_device_motorola_victara
Newest build:
http://conoha.kghost.info/~kghost/cm-12-20150318-UNOFFICIAL-victara.zip (md5sum e2cdfdf5f0571a38a6887b8cd05a1e99)

Working:
* Adb
* Ambient display
* Audio
* Brightness / Auto-brightness
* Bluetooth
* Camera and camcorder
* GPS
* MTP
* NFC (Android beam)
* Offmode charging
* Radio (GSM Voice/SMS)
* Radio (CDMA Voice/SMS)
* Radio (EV-DO Data)
* Radio (EDGE)
* Radio (LTE)
* Rotator
* Sensors
* USB-OTG (keyboard, mouse)
* Vibrator
* Video playback (youtube)
* WiFi
* SELinux enforcing
Not working:
* USB-OTG (storage)
Not tested:
* DRM / Widevine
Quirks / Improvements needed (by crpalmer):
* Ambient display should use sensors
* DRM is only partially working (V8 not V12)
* Graphic glitches occasionally?
* Hotword detection should use offloaded DSP
* USB-OTG doesn't show storage stats in Settings app
* WiFi: update to a newer version of the wlan driver than what moto ships.
Unknown:
* Everything else

Offmode charhing not working, LTE working

xarcom said:
Offmode charhing not working, LTE working
Click to expand...
Click to collapse
Thank you，I‘m looking on it

off-mode charging is broken because framebuffer driver is not working. I haven't locate the problem yet

zealot0630 said:
off-mode charging is broken because framebuffer driver is not working. I haven't locate the problem yet
Click to expand...
Click to collapse
Actually, I fixed it in the kernel yesterday.

crpalmer said:
Actually, I fixed it in the kernel yesterday.
Click to expand...
Click to collapse
awesome, I'll sync/build asap

sorry, don't notice DEV-ONLY,
DELETE.

crpalmer said:
Actually, I fixed it in the kernel yesterday.
Click to expand...
Click to collapse
Unfortunately, framebuffer still doesn't work in new kernel
I found some fb error in my dmesg
Code:
--
<6>[ 0.512739,1] gpiochip_add: registered GPIOs 444 to 447 on device: pm8841-mpp
<6>[ 0.513691,1] gpiochip_add: registered GPIOs 408 to 443 on device: pm8941-gpio
<6>[ 0.516441,1] gpiochip_add: registered GPIOs 401 to 407 on device: pm8941-mpp
<6>[ 0.517337,1] mdss_mdp_probe: MDP HW Base phy_Address=0xfd900000 virt=0xc5500000
<6>[ 0.517437,1] mdss_mdp_probe: MDSS VBIF HW Base phy_Address=0xfd924000 virt=0xc547c000
<3>[ 0.517581,1] mdss_mdp_parse_dt_prop_len: Error from prop qcom,mdss-clk-levels : spec error in device tree
<6>[ 0.519077,1] mdss_dsi_ctrl_probe: DSI Ctrl name = MDSS DSI CTRL->0
<6>[ 0.519171,1] BL: panel=mipi_mot_cmd_smd_fhd_520, manufacture_id(0xDA)= 0x2 controller_ver(0xDB)= 0x6 controller_drv_ver(0XDC)= 0x1, full=0x0000000000010602, detect status = 0x0
<6>[ 0.519281,1] mdss_dsi_panel_init: Panel Name = mipi_mot_cmd_smd_1080_v1
--
<6>[ 0.541628,1] mdss_register_panel: adding framebuffer device fd922800.qcom,mdss_dsi
<6>[ 0.541840,1] mdss_hw_init: MDP Rev=10020001
<6>[ 0.543735,1] mdss_register_panel: adding framebuffer device qcom,mdss_wb_panel.6
<6>[ 0.544416,1] mdss_fb_parse_dt: split framebuffer left=0 right=0
<6>[ 0.544516,1] mdss_fb_register: FrameBuffer[0] 1080x1920 registered successfully!
<4>[ 0.544660,1] mdss_mdp_pp_resume: Failed to get AD info, err = -112
<7>[ 0.544792,1] Registered led device: lcd-backlight
<6>[ 0.544830,1] mdss_fb_parse_dt: split framebuffer left=0 right=0
<6>[ 0.544962,1] mdss_fb_register: FrameBuffer[1] 1920x1080 registered successfully!
<6>[ 0.545087,1] mdss_dsi_status_init: DSI status check interval:8000
<3>[ 0.559139,1] sps: BAM device 0xf9944000 is not registered yet.
<6>[ 0.559237,1] sps:BAM 0xf9944000 is registered.
--
full dmesg http://pastebin.com/9ifL5aMc
would you please paste dmesg on XT1095 ?

zealot0630 said:
Unfortunately, framebuffer still doesn't work in new kernel
I found some fb error in my dmesg
Code:
--
<6>[ 0.512739,1] gpiochip_add: registered GPIOs 444 to 447 on device: pm8841-mpp
<6>[ 0.513691,1] gpiochip_add: registered GPIOs 408 to 443 on device: pm8941-gpio
<6>[ 0.516441,1] gpiochip_add: registered GPIOs 401 to 407 on device: pm8941-mpp
<6>[ 0.517337,1] mdss_mdp_probe: MDP HW Base phy_Address=0xfd900000 virt=0xc5500000
<6>[ 0.517437,1] mdss_mdp_probe: MDSS VBIF HW Base phy_Address=0xfd924000 virt=0xc547c000
<3>[ 0.517581,1] mdss_mdp_parse_dt_prop_len: Error from prop qcom,mdss-clk-levels : spec error in device tree
<6>[ 0.519077,1] mdss_dsi_ctrl_probe: DSI Ctrl name = MDSS DSI CTRL->0
<6>[ 0.519171,1] BL: panel=mipi_mot_cmd_smd_fhd_520, manufacture_id(0xDA)= 0x2 controller_ver(0xDB)= 0x6 controller_drv_ver(0XDC)= 0x1, full=0x0000000000010602, detect status = 0x0
<6>[ 0.519281,1] mdss_dsi_panel_init: Panel Name = mipi_mot_cmd_smd_1080_v1
--
<6>[ 0.541628,1] mdss_register_panel: adding framebuffer device fd922800.qcom,mdss_dsi
<6>[ 0.541840,1] mdss_hw_init: MDP Rev=10020001
<6>[ 0.543735,1] mdss_register_panel: adding framebuffer device qcom,mdss_wb_panel.6
<6>[ 0.544416,1] mdss_fb_parse_dt: split framebuffer left=0 right=0
<6>[ 0.544516,1] mdss_fb_register: FrameBuffer[0] 1080x1920 registered successfully!
<4>[ 0.544660,1] mdss_mdp_pp_resume: Failed to get AD info, err = -112
<7>[ 0.544792,1] Registered led device: lcd-backlight
<6>[ 0.544830,1] mdss_fb_parse_dt: split framebuffer left=0 right=0
<6>[ 0.544962,1] mdss_fb_register: FrameBuffer[1] 1920x1080 registered successfully!
<6>[ 0.545087,1] mdss_dsi_status_init: DSI status check interval:8000
<3>[ 0.559139,1] sps: BAM device 0xf9944000 is not registered yet.
<6>[ 0.559237,1] sps:BAM 0xf9944000 is registered.
--
full dmesg http://pastebin.com/9ifL5aMc
would you please paste dmesg on XT1095 ?
Click to expand...
Click to collapse
What is that a dmesg of? Just a normal boot? I don't see anything that looks like a real error in your dmesg. The dt errors and the AD error are normal.
Are you having problems with the mdss driver in general or just for the charge_only_mode?

crpalmer said:
What is that a dmesg of? Just a normal boot? I don't see anything that looks like a real error in your dmesg. The dt errors and the AD error are normal.
Are you having problems with the mdss driver in general or just for the charge_only_mode?
Click to expand...
Click to collapse
offmode charging works fine, but framebuffer still don't work in normal boot, I don't know if it is ordinary.

zealot0630 said:
offmode charging works fine, but framebuffer still don't work in normal boot, I don't know if it is ordinary.
Click to expand...
Click to collapse
What exactly doesn't work? I'm not entirely sure what you mean by "framebuffer doesn't work in normal boot". Do you get the boot animation?

crpalmer said:
What exactly doesn't work? I'm not entirely sure what you mean by "framebuffer doesn't work in normal boot". Do you get the boot animation?
Click to expand...
Click to collapse
boot animation works, I can't read/write "/dev/graphics/fb0"

zealot0630 said:
boot animation works, I can't read/write "/dev/graphics/fb0"
Click to expand...
Click to collapse
What isn't working? I am still not understanding what you are trying to fix...

Kernel is not booting at all

Hello,
I tried to build a kernel myself and it just fails to boot. I have UART access (through headphone adapter) and I just get nothing in the serial console.
I have CM 11.0 and I cloned CM's android_kernel_lge_hammerhead repo and checked out stable/cm-11.0 with hammerhead_defconfig.
I used google's arm-eabi-4.8 precompiled toolchain.
To boot:
Code:
ttouch android_kernel_lge_hammerhead> sudo fastboot boot arch/arm/boot/zImage-dtb
creating boot image...
creating boot image - 8583168 bytes
downloading 'boot.img'...
OKAY [ 0.375s]
booting...
OKAY [ 0.123s]
finished. total time: 0.498s
Here is what I get in UART:
Code:
welcome to hammerhead bootloader
[10] Power on reason 81
[10] DDR: elpida
[90] Loaded IMGDATA at 0x11000000
[90] Display Init: Start
[170] MDP GDSC already enabled
[170] bpp 24
[210] Config MIPI_CMD_PANEL.
[210] display panel: ORISE
[210] display panel: Default setting
[340] Turn on MIPI_CMD_PANEL.
[390] Display Init: Done
[390] cable type from shared memory: 8
[390] vibe
[590] USB init ept @ 0xf957000
[610] secured device: 1
[610] fastboot_init()
[660] splash: fastboot_op
FASTBOOT MODE
PRODUCT_NAME - hammerhead
VARIANT - hammerhead D821(E) 16GB
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11k
BASEBAND VERSION - M8974A-2.0.50.1.16
CARRIER INFO - None
SERIAL NUMBER - <blablablabla>
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
[770] splash: start
[1260] splash: bootloader
[1260] Fastboot mode started
[1260] udc_start()
�����l[60660] -- reset --
[60660] -- portchange --
[60820] -- reset --
[60820] -- portchange --
[60990] fastboot: processing commands
��[112660] fastboot: download:0082f800
downloading...
[113140] fastboot: boot
[113150] Found Appeneded Flattened Device tree
[113150] DTB: platform id 126, board id 150, soc rev 20002, board rev 11
[113160] get_display_kcal = 0, 0, 0, x
[113200] vibe
[113300] splash: boot
[113340] splash: unlocked
[113380] cmdline: uart_console=enable lcd_maker_id=primary lge.hreset=off lge.reset=unknown gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 androidboot.laf androidboot.emmc=true fastboot=true androidboot.serialno=<blablablabla> androidboot.bootloader=HHZ11k androidb[113400] Updating device tree: start
[113420] Updating device tree: done
[113420] booting linux @ 0x10008000, ramdisk @ 0x11000000 (0), tags/device tree @ 0x10000100
[113430] Turn off MIPI_CMD_PANEL.
[113430] Continuous splash enabled, keeping panel alive.
[113430] undefined abort, halting
[113430] r0 0x00000000 r1 0x00000000 r2 0x10000100 r3 0x003996e3
[113430] r4 0x10008000 r5 0x0f92607a r6 0x0f925d5b r7 0x0f925f89
[113430] r8 0x0f955652 r9 0x0f9556c7 r10 0x00000001 r11 0x10000100
[113430] r12 0x20000193 usp 0x00000000 ulr 0x00000000 pc 0x1000800c
[113430] spsr 0x40000193

I've never installed a kernel like that (via fastboot) and I had to look up the headphone UART adapter thing.
I don't have much to offer. I always use mkbootimg to link my kernel and ramdisk, then flash it via fastboot. Looking at your serial dump, the only thing I see is that the base, ramdisk, and tags offsets look completely different from the ones I use with mkbootimg.
BASE=0x00000000
PAGESIZE=2048
RAMDISK_OFFSET=0x02900000
TAGS_OFFSET=0x02700000
I'm playing around with my breadboard and an FTDI USB<-->Serial board I have to try and make a working serial console and I'll see what my N5 dumps.

Gene Poole said:
I've never installed a kernel like that (via fastboot) and I had to look up the headphone UART adapter thing.
I don't have much to offer. I always use mkbootimg to link my kernel and ramdisk, then flash it via fastboot. Looking at your serial dump, the only thing I see is that the base, ramdisk, and tags offsets look completely different from the ones I use with mkbootimg.
BASE=0x00000000
PAGESIZE=2048
RAMDISK_OFFSET=0x02900000
TAGS_OFFSET=0x02700000
Click to expand...
Click to collapse
Thanks, I'll try that.
Gene Poole said:
I'm playing around with my breadboard and an FTDI USB<-->Serial board I have to try and make a working serial console and I'll see what my N5 dumps.
Click to expand...
Click to collapse
I guess you're trying to build the N4 cable, but it does not work.
For the N5 to work you need to supply 3V3 and not 1V8 to the VCC
The RX though (serial input to the N5) should be 1V8 (done with a simple voltage divider, try 1K and 1.2K to GND) or there is a chance that you'll fry your serial.

Yeah, my search showed that the N5 version needed no resistors, but I used some anyway just to shunt some voltage. It worked. I got a dump and it does appear that your offsets are not right. Here's my dump up to the kernel taking over:
Code:
welcome to hammerhead bootloader
[10] Power on reason 80
[10] DDR: hynix
[90] Loaded IMGDATA at 0x11000000
[90] Display Init: Start
[170] MDP GDSC already enabled
[170] bpp 24
[210] Config MIPI_CMD_PANEL.
[210] display panel: ORISE
[260] Found Appeneded Flattened Device tree
[260] DTB: platform id 126, board id 150, soc rev 20002, board rev 11
[300] Set panel ON cmds [35]
[420] Turn on MIPI_CMD_PANEL.
[470] Display Init: Done
[470] cable type from shared memory: 8
[470] reboot_mode restart reason = power_on
[520] vibe
[620] splash: boot
[660] splash: unlocked
[700] use_signed_kernel=0, is_unlocked=1, is_tampered=0.
[700] Loading boot image (9226240): start
[1030] Loading boot image (9226240): done
[1030] Found Appeneded Flattened Device tree
[1040] DTB: platform id 126, board id 150, soc rev 20002, board rev 11
[1040] get_display_kcal = 0, 0, 0, x
[1050]
Booting Linux
[1050] cmdline: console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 selinuxt
[1090] Updating device tree: done
[1090] booting linux @ 0x8000, ramdisk @ 0x2900000 (714802), tags/device tree @ 0x2700000
[1100] Turn off MIPI_CMD_PANEL.
[1100] Continuous splash enabled, keeping panel alive.
[ 0.000000] Booting Linux on physical CPU 0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.4.0-hoxnet-gd745771 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #7 SMP PREE5
[ 0.000000] CPU: ARMv7 Processor [512f06f0] revision 0 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
...
I see a fastboot option, -b, for specifying the kernel base address. Try with -b 0x8000.
Edit: maybe it's -b 0. looks like the address gets 0x8000 added by default.

Gene Poole said:
Yeah, my search showed that the N5 version needed no resistors, but I used some anyway just to shunt some voltage. It worked. I got a dump and it does appear that your offsets are not right. Here's my dump up to the kernel taking over:
Code:
welcome to hammerhead bootloader
[10] Power on reason 80
[10] DDR: hynix
[90] Loaded IMGDATA at 0x11000000
[90] Display Init: Start
[170] MDP GDSC already enabled
[170] bpp 24
[210] Config MIPI_CMD_PANEL.
[210] display panel: ORISE
[260] Found Appeneded Flattened Device tree
[260] DTB: platform id 126, board id 150, soc rev 20002, board rev 11
[300] Set panel ON cmds [35]
[420] Turn on MIPI_CMD_PANEL.
[470] Display Init: Done
[470] cable type from shared memory: 8
[470] reboot_mode restart reason = power_on
[520] vibe
[620] splash: boot
[660] splash: unlocked
[700] use_signed_kernel=0, is_unlocked=1, is_tampered=0.
[700] Loading boot image (9226240): start
[1030] Loading boot image (9226240): done
[1030] Found Appeneded Flattened Device tree
[1040] DTB: platform id 126, board id 150, soc rev 20002, board rev 11
[1040] get_display_kcal = 0, 0, 0, x
[1050]
Booting Linux
[1050] cmdline: console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 selinuxt
[1090] Updating device tree: done
[1090] booting linux @ 0x8000, ramdisk @ 0x2900000 (714802), tags/device tree @ 0x2700000
[1100] Turn off MIPI_CMD_PANEL.
[1100] Continuous splash enabled, keeping panel alive.
[ 0.000000] Booting Linux on physical CPU 0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.4.0-hoxnet-gd745771 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #7 SMP PREE5
[ 0.000000] CPU: ARMv7 Processor [512f06f0] revision 0 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
...
I see a fastboot option, -b, for specifying the kernel base address. Try with -b 0x8000.
Edit: maybe it's -b 0. looks like the address gets 0x8000 added by default.
Click to expand...
Click to collapse
Didn't work.
I also tried to build a boot.img, I flashed it (just to be sure) and I get all the same results.
My tags/device tree is different and I don't know how to change it. There is no available option in fastboot or mkbootimg

ttouch said:
Didn't work.
I also tried to build a boot.img, I flashed it (just to be sure) and I get all the same results.
My tags/device tree is different and I don't know how to change it. There is no available option in fastboot or mkbootimg
Click to expand...
Click to collapse
mkbootimg has an undocumented --tags_offset option. I don't know why it doesn't show up in the --help. I found it in the source for mkbootimg (in the AOSP tree) when I first ran the unpackbootimg and noticed that it dumped text files containing info about the offsets.
I have a shell script I use to make boot images. Here it is:
Code:
#!/bin/sh
RAMDISK=ramdisk
KERNEL=zImage
BASE=0x00000000
PAGESIZE=2048
RAMDISK_OFFSET=0x02900000
TAGS_OFFSET=0x02700000
CMDLINE="console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 selinux=1"
echo Making ramdisk image ...
(cd ${RAMDISK} ; mkbootfs . | gzip -9c > ../${RAMDISK}.cpio.gz )
echo Making boot image ...
mkbootimg --kernel ${KERNEL} --ramdisk ${RAMDISK}.cpio.gz --cmdline "${CMDLINE}" -o boot.img --base ${BASE} --pagesize ${PAGESIZE} --ramdisk_offset ${RAMDISK_OFFSET} --tags_offset ${TAGS_OFFSET}
"ramdisk" is a directory containing the unpacked AOSP stock ramdisk (plus my modifications). These offset values were obtained from unpackbootimg executable but I can't remember where I found the source. I'll send you a copy if you want it.

Gene Poole said:
mkbootimg has an undocumented --tags_offset option. I don't know why it doesn't show up in the --help. I found it in the source for mkbootimg (in the AOSP tree) when I first ran the unpackbootimg and noticed that it dumped text files containing info about the offsets.
I have a shell script I use to make boot images. Here it is:
Code:
#!/bin/sh
RAMDISK=ramdisk
KERNEL=zImage
BASE=0x00000000
PAGESIZE=2048
RAMDISK_OFFSET=0x02900000
TAGS_OFFSET=0x02700000
CMDLINE="console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 selinux=1"
echo Making ramdisk image ...
(cd ${RAMDISK} ; mkbootfs . | gzip -9c > ../${RAMDISK}.cpio.gz )
echo Making boot image ...
mkbootimg --kernel ${KERNEL} --ramdisk ${RAMDISK}.cpio.gz --cmdline "${CMDLINE}" -o boot.img --base ${BASE} --pagesize ${PAGESIZE} --ramdisk_offset ${RAMDISK_OFFSET} --tags_offset ${TAGS_OFFSET}
"ramdisk" is a directory containing the unpacked AOSP stock ramdisk (plus my modifications). These offset values were obtained from unpackbootimg executable but I can't remember where I found the source. I'll send you a copy if you want it.
Click to expand...
Click to collapse
My mkbootimg does not have the tags_offset.
When I try to build the boot image with tags_offset, mkbootimg shows me the help message, which means it got no tags_offset option.
EDIT: Nevermind, I cloned and compiled the latest mkbootimg from here. Trying to boot it now...
EDIT2: IT WORKS!!

Since the AOSP build has to create a boot image, it is included in the utilities. I always use the one native to the build tree. It is in:
[aosp_root]/out/host/linux-x86/bin/mkbootimg
and the source is in:
[aosp_root]/system/core/mkbootimg/

Twrp (DEV-ONLY) compiling op6t (NEW-TEST) twrp-op6t-unified-test-0.6.img

I made this thread so all those trying to compile twrp for op6t can come together.
We can share ideas. What we have and have not got to work. What will work and what won't work.
Basically a thread where all information regarding twrp can be found in one location.
###########
#Please pm me #
##########
If using open source built roms and you have issues with twrp we may need to modify source in the rom or our twrp source.
Please report to rom maker as well.
Things to include.
What source 9.0 or 8.1
Compiling errors.
Post #2
Is where the download links are kept and updated.
Post #3 is where the other variations of twrp for source built roms or ports will be available to download if needed.

New test. twrp-op6t-test-0.3.img TEST ONLY!
@Dameon87 & myself have been working on this recovery for a while. We think it will get better. There are still bugs and issues with twrp. We would like your feedback.
Thanks
I am not responsible for anything that can happen to your device.
Rebuilt and fully working mke2fs
Decryption works
Storage works.
Please test and let us know what works and what doesn't.
twrp-op6t-test-0.2.img
https://www.androidfilehost.com/?fid=11410963190603862182
Updated twrp
Added more functionality ability to flash all zips and Ota's
Backup and restore all partitions including data.
Twrp-op6t-test-0.3.img
https://www.androidfilehost.com/?fid=11410963190603871199
New test twrp-unified-0.4.img
Everything working as usual
Cleaned up source and added @mauronofrio notch theme
Twrp-0.4.img
https://www.androidfilehost.com/?fid=11410963190603875438
Twrp installer thanks to @mauronofrio
https://www.androidfilehost.com/?fid=11410963190603876589
Updated twrp to decrypt 9.0.10
Twrp-0.5.img
https://www.androidfilehost.com/?fid=11410963190603879261
Twrp installer
https://www.androidfilehost.com/?fid=11410963190603879262
New test
Fixed screenshot color when taking screen shots in recovery.
Fixed touch vibration.
Please test and report back.
Twrp-0.6.img
https://www.androidfilehost.com/?fid...63190603880512
Twrp installer
https://www.androidfilehost.com/?fid...63190603880513
Device source
https://github.com/TWINNFAMOUS/android_device_oneplus_fajita
Bootable recovery source
https://github.com/OP6T-TWRP/android_bootable_recovery
Hope you all enjoy

This is where I will keep other twrp variations if needed for all source built roms and ports for our device. When available these will only be meant for testing. Thanks

twinnfamous said:
I made this thread so all those trying to compile twrp for op6t can come together.
We can share ideas. What we have and have not got to work. What will work and what won't work.
Basically a thread where all information regarding twrp can be found in one location.
Things to include.
What source 9.0 or 8.1
Compiling errors.
Click to expand...
Click to collapse
You're from the HTC u11 life! You made that phone awesome while I had it. Good to see you here!

I'm trying to build with 8.1 source and I get errors so build doesn't finish.
Is there anyone that's building successfully with 8.1?

Me, can you explain what are you doing exactly? Which source are you using?

mauronofrio said:
Me, can you explain what are you doing exactly? Which source are you using?
Click to expand...
Click to collapse
I'm trying with full omni source on 8.1. I've used the device source from both op6 & op6t without modifying just to see if it would be and it fails. I'll post output error soon as I can.
I don't have issues building with 9.0 source after I modify device source but it won't boot to twrp just stock recovery like it's not selecting the rite slot

twinnfamous said:
I'm trying to build with 8.1 source and I get errors so build doesn't finish.
Is there anyone that's building successfully with 8.1?
Click to expand...
Click to collapse
Make sure if you're using a newer version of Ubuntu with GCC 7+ you do: export LC_ALL=C
That should get you past the initial build errors.

Dameon87 said:
Make sure if you're using a newer version of Ubuntu with GCC 7+ you do: export LC_ALL=C
That should get you past the initial build errors.
Click to expand...
Click to collapse
Thanks for the info. I upgraded to linuxmint19 Recently. Guess I didn't pay attention to the changelog.

You also need to change two lines in the build/tools/buildinfo.sh :
echo "ro.build.version.release=$PLATFORM_VERSION"
echo "ro.build.version.security_patch=$PLATFORM_SECURITY_PATCH"
to:
echo "ro.build.version.release_orig=$PLATFORM_VERSION"
echo "ro.build.version.security_patch_orig=$PLATFORM_SECURITY_PATCH"

Dameon87 said:
You also need to change two lines in the build/tools/buildinfo.sh :
echo "ro.build.version.release=$PLATFORM_VERSION"
echo "ro.build.version.security_patch=$PLATFORM_SECURITY_PATCH"
to:
echo "ro.build.version.release_orig=$PLATFORM_VERSION"
echo "ro.build.version.security_patch_orig=$PLATFORM_SECURITY_PATCH"
Click to expand...
Click to collapse
And you need to increase the PLATFORM_VERSION to 16.1.0 ( in the new pixel 3 TWRPs is used 16 ) in build/core/version_defaults.mk to override Google's anti-rollback features

Dameon87 said:
You also need to change two lines in the build/tools/buildinfo.sh :
echo "ro.build.version.release=$PLATFORM_VERSION"
echo "ro.build.version.security_patch=$PLATFORM_SECURITY_PATCH"
to:
echo "ro.build.version.release_orig=$PLATFORM_VERSION"
echo "ro.build.version.security_patch_orig=$PLATFORM_SECURITY_PATCH"
Click to expand...
Click to collapse
mauronofrio said:
And you need to increase the PLATFORM_VERSION to 16.1.0 ( in the new pixel 3 TWRPs is used 16 ) in build/core/version_defaults.mk to override Google's anti-rollback features
Click to expand...
Click to collapse
The only issue I found was my lack of awareness. Ive been fighting with the 8.1 source all because the newer os I installed. I'm testing things out.
One thing I know is if the security patch level and date doesn't match what's in the phone then decryption won't work.
So I'm starting there.

I pulled this log from the phone it's only a part of it.
I've been trying everything and this is where it fails at in recovery.
e4crypt_initialize_global_de fail
So I started looking at any logs I can find in the phone and found this. Thought it might be helpful.
All the de folder locations are in the log
Also we use keymaster 4 that shows in The log as well.
I'm still using 8.1 source with 9.0 bootable recovery.
I'm thinking of focusing on trying to get get it to work with 9.0 source.
Log.
Mount system_root for mountting system
[ 1.120382] e4crypt_initialize_global_de
[ 1.120509] Keyring created with id 744456481 in process 530
[ 1.126746] I:List of Keymaster HALs found:
[ 1.126902] I:Keymaster HAL #1: Keymaster HAL: 4 from QTI SecurityLevel: TRUSTED_ENVIRONMENT HAL: [email protected]::IKeymasterDevice/default
[ 1.141729] Using Keymaster HAL: 4 from QTI for encryption. Security level:TRUSTED_ENVIRONMENT , HAL: [email protected]::IKeymasterDevice / defaulte4crypt_init_user0
[ 1.147584] Skipping non-de-key .
[ 1.147590] Skipping non-de-key ..
[ 1.152120] I:List of Keymaster HALs found:
[ 1.152266] I:Keymaster HAL #1: Keymaster HAL: 4 from QTI SecurityLevel: TRUSTED_ENVIRONMENT HAL: [email protected]::IKeymasterDevice/default
[ 1.160865] Using Keymaster HAL: 4 from QTI for encryption. Security level:TRUSTED_ENVIRONMENT , HAL: [email protected]::IKeymasterDevice / defaultInstalled de key for user 0
[ 1.160871] e4crypt_prepare_user_storage
[ 1.166977] ensure policy /data/system_de/0
[ 1.167599] I:Found policy 8372743e0b3d7924 at /data/system_de/0 which matches expected value
[ 1.167608] ensure policy /data/misc_de/0
[ 1.168197] I:Found policy 8372743e0b3d7924 at /data/misc_de/0 which matches expected value
[ 1.168206] ensure policy /data/user_de/0
[ 1.169338] I:Found policy 8372743e0b3d7924 at /data/user_de/0 which matches expected value
[ 1.358232] I:FBE enable...
[ 1.358334] Unable to locate gatekeeper password file '/data/system/gatekeeper.pattern.key'
[ 1.358412] (4294937945 ticks)(pid:530)[bootable/recovery/oem/src/main/oem.cpp]tree_init:90:efault password, decrept...
[ 1.358454] Unable to locate gatekeeper password file '/data/system/gatekeeper.pattern.key'
[ 1.358516] Skipping non-key .
[ 1.358549] Skipping non-key ..
[ 1.364930] I:List of Keymaster HALs found:
[ 1.365014] I:Keymaster HAL #1: Keymaster HAL: 4 from QTI SecurityLevel: TRUSTED_ENVIRONMENT HAL: [email protected]::IKeymasterDevice/default
[ 1.373672] Using Keymaster HAL: 4 from QTI for encryption. Security level:TRUSTED_ENVIRONMENT , HAL: [email protected]::IKeymasterDevice / defaultSuccessfully retrieved key
[ 1.373733] Installed ce key for user 0
[ 1.373765] e4crypt_prepare_user_storage
[ 1.377707] ensure policy /data/system_ce/0
[ 1.378426] I:Found policy d0acf3009500dfb4 at /data/system_ce/0 which matches expected value
[ 1.378462] ensure policy /data/misc_ce/0
[ 1.379037] I:Found policy d0acf3009500dfb4 at /data/misc_ce/0 which matches expected value
[ 1.379069] ensure policy /data/data
[ 1.380547] I:Found policy d0acf3009500dfb4 at /data/data which matches expected value
[ 1.380597] Decrypted Successfully!

twinnfamous said:
I pulled this log from the phone it's only a part of it.
I've been trying everything and this is where it fails at in recovery.
e4crypt_initialize_global_de fail
So I started looking at any logs I can find in the phone and found this. Thought it might be helpful.
All the de folder locations are in the log
Also we use keymaster 4 that shows in The log as well.
I'm still using 8.1 source with 9.0 bootable recovery.
I'm thinking of focusing on trying to get get it to work with 9.0 source.
Log.
Mount system_root for mountting system
[ 1.120382] e4crypt_initialize_global_de
[ 1.120509] Keyring created with id 744456481 in process 530
[ 1.126746] I:List of Keymaster HALs found:
[ 1.126902] I:Keymaster HAL #1: Keymaster HAL: 4 from QTI SecurityLevel: TRUSTED_ENVIRONMENT HAL: [email protected]::IKeymasterDevice/default
[ 1.141729] Using Keymaster HAL: 4 from QTI for encryption. Security level:TRUSTED_ENVIRONMENT , HAL: [email protected]::IKeymasterDevice / defaulte4crypt_init_user0
[ 1.147584] Skipping non-de-key .
[ 1.147590] Skipping non-de-key ..
[ 1.152120] I:List of Keymaster HALs found:
[ 1.152266] I:Keymaster HAL #1: Keymaster HAL: 4 from QTI SecurityLevel: TRUSTED_ENVIRONMENT HAL: [email protected]::IKeymasterDevice/default
[ 1.160865] Using Keymaster HAL: 4 from QTI for encryption. Security level:TRUSTED_ENVIRONMENT , HAL: [email protected]::IKeymasterDevice / defaultInstalled de key for user 0
[ 1.160871] e4crypt_prepare_user_storage
[ 1.166977] ensure policy /data/system_de/0
[ 1.167599] I:Found policy 8372743e0b3d7924 at /data/system_de/0 which matches expected value
[ 1.167608] ensure policy /data/misc_de/0
[ 1.168197] I:Found policy 8372743e0b3d7924 at /data/misc_de/0 which matches expected value
[ 1.168206] ensure policy /data/user_de/0
[ 1.169338] I:Found policy 8372743e0b3d7924 at /data/user_de/0 which matches expected value
[ 1.358232] I:FBE enable...
[ 1.358334] Unable to locate gatekeeper password file '/data/system/gatekeeper.pattern.key'
[ 1.358412] (4294937945 ticks)(pid:530)[bootable/recovery/oem/src/main/oem.cpp]tree_init:90:efault password, decrept...
[ 1.358454] Unable to locate gatekeeper password file '/data/system/gatekeeper.pattern.key'
[ 1.358516] Skipping non-key .
[ 1.358549] Skipping non-key ..
[ 1.364930] I:List of Keymaster HALs found:
[ 1.365014] I:Keymaster HAL #1: Keymaster HAL: 4 from QTI SecurityLevel: TRUSTED_ENVIRONMENT HAL: [email protected]::IKeymasterDevice/default
[ 1.373672] Using Keymaster HAL: 4 from QTI for encryption. Security level:TRUSTED_ENVIRONMENT , HAL: [email protected]::IKeymasterDevice / defaultSuccessfully retrieved key
[ 1.373733] Installed ce key for user 0
[ 1.373765] e4crypt_prepare_user_storage
[ 1.377707] ensure policy /data/system_ce/0
[ 1.378426] I:Found policy d0acf3009500dfb4 at /data/system_ce/0 which matches expected value
[ 1.378462] ensure policy /data/misc_ce/0
[ 1.379037] I:Found policy d0acf3009500dfb4 at /data/misc_ce/0 which matches expected value
[ 1.379069] ensure policy /data/data
[ 1.380547] I:Found policy d0acf3009500dfb4 at /data/data which matches expected value
[ 1.380597] Decrypted Successfully!
Click to expand...
Click to collapse
Was this taken from the default/stock recovery or just a standard boot? I've been using the twrp-8.1 branch (Which uses android_bootable_recovery 9.0 branch by default now). I've tried a multitude of things, but I simply just get the e4crypt_initialize_global_de fail error as well. I think the way things are done for the Pixel 3/XL are the way to proceed, but aside the device tree we don't have much else to go on.

Dameon87 said:
Was this taken from the default/stock recovery or just a standard boot? I've been using the twrp-8.1 branch (Which uses android_bootable_recovery 9.0 branch by default now). I've tried a multitude of things, but I simply just get the e4crypt_initialize_global_de fail error as well. I think the way things are done for the Pixel 3/XL are the way to proceed, but aside the device tree we don't have much else to go on.
Click to expand...
Click to collapse
Maybe Fstab files need modifying
The recovery.fstab I pulled out of the boot.Img has a data partition labeled f2fs
And a Data partition labeled ext4

twinnfamous said:
Maybe Fstab files need modifying
The recovery.fstab I pulled out of the boot.Img has a data partition labeled f2fs
And a Data partition labeled ext4
Click to expand...
Click to collapse
Already tried that but I didn't really get anything different. There's a few issues that are happening I think.
Dmesg repeats this over and over and over:
<3>[19700123_15:34:23.729788]@4 FG: fg_psy_get_property: unsupported property 27
<14>[19700123_15:34:26.049860]@4 init: starting service 'boot-1-0'...
<11>[19700123_15:34:26.050060]@4 init: property_set("ro.boottime.boot-1-0", "798060609590") failed: property already set
<11>[19700123_15:34:26.050448]@0 init: cannot execve('/sbin/[email protected]'): No such file or directory
<14>[19700123_15:34:26.051342]@4 init: Sending signal 9 to service 'boot-1-0' (pid 762) process group...
<14>[19700123_15:34:26.051372]@4 init: Successfully killed process cgroup uid 0 pid 762 in 0ms
Then just getting this according to the recovery.log:
I:File Based Encryption is present
e4crypt_initialize_global_de returned fail
e4crypt_initialize_global_de returned fail
e4crypt_initialize_global_de returned fail

Dameon87 said:
Already tried that but I didn't really get anything different. There's a few issues that are happening I think.
Dmesg repeats this over and over and over:
<3>[19700123_15:34:23.729788]@4 FG: fg_psy_get_property: unsupported property 27
<14>[19700123_15:34:26.049860]@4 init: starting service 'boot-1-0'...
<11>[19700123_15:34:26.050060]@4 init: property_set("ro.boottime.boot-1-0", "798060609590") failed: property already set
<11>[19700123_15:34:26.050448]@0 init: cannot execve('/sbin/[email protected]'): No such file or directory
<14>[19700123_15:34:26.051342]@4 init: Sending signal 9 to service 'boot-1-0' (pid 762) process group...
<14>[19700123_15:34:26.051372]@4 init: Successfully killed process cgroup uid 0 pid 762 in 0ms
Then just getting this according to the recovery.log:
I:File Based Encryption is present
e4crypt_initialize_global_de returned fail
e4crypt_initialize_global_de returned fail
e4crypt_initialize_global_de returned fail
Click to expand...
Click to collapse
This is probably why it won't even boot twrp built with 9.0

twinnfamous said:
This is probably why it won't even boot twrp built with 9.0
Click to expand...
Click to collapse
Are you doing a minimal build env, or pulling in the entire Omni tree? There is only a twrp-8.1 branch for the minimal manifest, but that does pull in android_bootable_recovery 9.0 branch. I can get both to compile and boot fine.

Dameon87 said:
Are you doing a minimal build env, or pulling in the entire Omni tree? There is only a twrp-8.1 branch for the minimal manifest, but that does pull in android_bootable_recovery 9.0 branch. I can get both to compile and boot fine.
Click to expand...
Click to collapse
Full sources on both 8.1 and 9.0

twinnfamous said:
Full sources on both 8.1 and 9.0
Click to expand...
Click to collapse
Alright I'm doing a full sync of the omni repo and will give that a try next. I had been just using the minimal manifest.