0.1.8 kernel on my AT&T Atrix:
1.3GHz = stuck on moto boot logo
1.2GHz = Stable
could it be hardware limitations?
[Kernel]Atrix-GB/CM7/9[2.6.32.59/56/59](026/024/026)OC~1.45GHz/UV/SLQB/ZRAM[Jun-17]
- Thread starter faux123
- Start date
0.1.8 kernel on my AT&T Atrix:
1.3GHz = stuck on moto boot logo
1.2GHz = Stable
could it be hardware limitations?
What tegrapart do you have?0.1.8 kernel on my AT&T Atrix:
1.3GHz = stuck on moto boot logo
1.2GHz = Stable
could it be hardware limitations?
0.1.8 kernel on my AT&T Atrix:
1.3GHz = stuck on moto boot logo
1.2GHz = Stable
could it be hardware limitations?
same here. using d00
1.3 ghz working fine here with d00.
Working on undervolting now. -50mv seems fine so far...
1.2ghz might be your ceiling.
whoopie for u...i tried uv -25 and getting bootloops...i'm on the less superior 1.2 lol my board is 1100
I tried again using fastboot to push the image and again I was unable to get past the "unlocked" with motoboot logo. Again My phone is a d00 tegra part.
On a side not my experiment is yielding interesting results. The phone is set to 800 min 1200 max on set CPU. I have the under volting set as:
1200=-100mv
1100=-100mv
1000=-50mv
900=-25mv
800=-25mv
After setting for 20 min I noticed the phone was cool to the touch. I thought it may have turned off, but it had not. I checked the setcpu info and the CPU is at 38 c idling at 800Mhz. Checking time in state 800Mhz accounts for 38% while 1200MHz accounts for 29%.
The point of the experiment was two fold. First I am seeing that my phone which gets about 12hr on a battery charge no matter what I do, gets about the same battery life with the CPU set to these high values all of the time. In my rough assessment I would have to say that setting profiles and tweaking UV is only good for maybe 1% per hour difference on discharge rate. I'm all for maximizing both performance and battery life. I have read about how little power these processors use.
The other point of the test is to determine the heat issue. I'm not sure if the under volt is currently what is keep the temp low on my phone, I will have to spend some time with it at stock voltages, but the important part in my opinion is that the only time I see the CPU run very hot is on boot up. It is almost as if it is running hot do to being pegged at 100%. I'm thinking the heat issue on the CPU is due caused by the PoP RAM as the boot process must read/write the RAM a lot. Proof of this is that currently my phone CPU temp is 37c and it is idling at 800MHz.
Two more things to note. The heat we feel through the back of the phone I believe is the Radio, not the CPU. I notice that if I sleep with my phone in my pocket and lay on it, the reduction of signal causes the power to rise and the phone will get hot. If i put my phone in locations in my house with weak signals I again notice it is hot.
The other is that currently with the phone at idle of 800MHz my battery drain over the last hour has been about 5%. Typically I get about 7% per hour. The 7% I have tested and It is the same with the screen on or off, the CPU low or high.
I urge others to attempt similar test, I think you will find that the CPU voltage and frequency is a minor concern other then going for maximum.
*** I performed Stress test for five minutes both with uv and with stock voltages. The uv was 51c when done and the stock 54c. The phone was only slightly warm. When the test stops the processor cools quickly and with in 30 sec was in the mid 40's idling at 800MHz. ***
On a side not my experiment is yielding interesting results. The phone is set to 800 min 1200 max on set CPU. I have the under volting set as:
1200=-100mv
1100=-100mv
1000=-50mv
900=-25mv
800=-25mv
After setting for 20 min I noticed the phone was cool to the touch. I thought it may have turned off, but it had not. I checked the setcpu info and the CPU is at 38 c idling at 800Mhz. Checking time in state 800Mhz accounts for 38% while 1200MHz accounts for 29%.
The point of the experiment was two fold. First I am seeing that my phone which gets about 12hr on a battery charge no matter what I do, gets about the same battery life with the CPU set to these high values all of the time. In my rough assessment I would have to say that setting profiles and tweaking UV is only good for maybe 1% per hour difference on discharge rate. I'm all for maximizing both performance and battery life. I have read about how little power these processors use.
The other point of the test is to determine the heat issue. I'm not sure if the under volt is currently what is keep the temp low on my phone, I will have to spend some time with it at stock voltages, but the important part in my opinion is that the only time I see the CPU run very hot is on boot up. It is almost as if it is running hot do to being pegged at 100%. I'm thinking the heat issue on the CPU is due caused by the PoP RAM as the boot process must read/write the RAM a lot. Proof of this is that currently my phone CPU temp is 37c and it is idling at 800MHz.
Two more things to note. The heat we feel through the back of the phone I believe is the Radio, not the CPU. I notice that if I sleep with my phone in my pocket and lay on it, the reduction of signal causes the power to rise and the phone will get hot. If i put my phone in locations in my house with weak signals I again notice it is hot.
The other is that currently with the phone at idle of 800MHz my battery drain over the last hour has been about 5%. Typically I get about 7% per hour. The 7% I have tested and It is the same with the screen on or off, the CPU low or high.
I urge others to attempt similar test, I think you will find that the CPU voltage and frequency is a minor concern other then going for maximum.
*** I performed Stress test for five minutes both with uv and with stock voltages. The uv was 51c when done and the stock 54c. The phone was only slightly warm. When the test stops the processor cools quickly and with in 30 sec was in the mid 40's idling at 800MHz. ***
Last edited:
Cm7 pre beta 3. 1.2OC works fine. 1.3OC not getting past unlocked moto screen.
Sent from my Atrix running CM7
Sent from my Atrix running CM7
1.3 would not boot for me so installed 1.2 ghz version.
Very fast and zippy but i have had 4 reboots in last hour. Might have to go back to version 1.7
Not sure what tegrapart i have but currently on kens stock 4.5.91
Sent from my MB860 using xda premium
Very fast and zippy but i have had 4 reboots in last hour. Might have to go back to version 1.7
Not sure what tegrapart i have but currently on kens stock 4.5.91
Sent from my MB860 using xda premium
Is it ok to use romracers recovery through rom manager to install zip files?
Sent from my MB860 using xda premium
I had several bootloops with 1.8 at 1,3 oc. But finally it booted and ran smoothly until I got messages FC and rebooted. On reboot all my widgets were gone....
Tried stock and worked nicely.
Will try d000 now....
Sent from my OC'd Motorola™ Atrix®
Tried stock and worked nicely.
Will try d000 now....
Sent from my OC'd Motorola™ Atrix®
anyone facing wifi issues on 1.7 with AT&T Atrix? Wifi connection seems unstable and tend to get disconnected at times. Also takes ages to connect to my home router now
edit: OK nevermind! Just realized that kernel 0.1.8 is out Gonna have a go at it
edit: OK nevermind! Just realized that kernel 0.1.8 is out
Gonna have a go at it
Last edited:
Hi everyone.I had flash 0.1.8 1.3Ghz OC d00 tegrapart kernel.Im on ATT atrix 4g.Right now i cannot get pass moto unlocked screen.Anyone know how to rectify the problem perhaps revert back to 0.1.7 kernel
That happened to me last night... same Tegra .. just flash back to 0.1.7 and it should boot... worked for me.
I also didn't wipe anything before flashing 0.1.8 (never had problems before when I updated kernels) .. im going to try it again tonight, wiping dalvik and cache before flashing 0.1.8. Ill report back with my findings
Sent from my NINJATRIX
I have d00 tegrapart but couldn't get either version of 1.8 past first boot logo. I'm using romracer's CWM. Could that be the issue? Or perhaps my ROM (PiCrust) isn't playing nicely with it? Anyone have success with these or any insight?
*Also, have tried loading 1.8 coming from stock kernel and also tried starting from 1.7...each time I wiped cache and dalvik prior to flashing.
Thanks for the hard work, Faux!!
~Sent from My Unlocked, Rooted, Shady Blued, and Pi-Crusted Atrix 4G~
*Also, have tried loading 1.8 coming from stock kernel and also tried starting from 1.7...each time I wiped cache and dalvik prior to flashing.
Thanks for the hard work, Faux!!
~Sent from My Unlocked, Rooted, Shady Blued, and Pi-Crusted Atrix 4G~
Currently running 0.1.8 on international cherry gb d00 tegra and all smooth. Its the 1.2ghz version.
I was able to boot with the 1.3ghz but suffered widget loss after reboots...several reboots.
Thanks faux!
Sent from my OC'd Motorola™ Atrix®
I was able to boot with the 1.3ghz but suffered widget loss after reboots...several reboots.
Thanks faux!
Sent from my OC'd Motorola™ Atrix®
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
346Here's an official build of a kernel based on Motorola Atrix source code for ATT
(Overclock via PimpMyCPU or SetCPU)
Just a statement regarding kernel source: The Kernel Source is of course covered under GPL version 2. Free software does NOT mean no work or time was spent working on it. I have donated a large sum of my free time to hack this kernel. If you use my modified kernel source in its entirety, I kindly ask you to send me a github pull request or PM whenever you find bugs or think you can help improve my kernel hack further. This way the entire community will truly benefit from the spirit of open source. Thank you
Compatible with: Rooted Stock, Debloated Stock ROMs and CM7 ROMs (Pick the correct version from below) Enjoy!
I have patched in BFQ I/O scheduler and SLQB memory allocator for better I/O and memory performance.
THIS IS ONLY FOR THOSE WHO ARE WILLING to LOAD THIS KERNEL ON THEIR OWN PHONES... IF YOU ARE NOT COMFORTABLE WITH THIS YOU SHOULD NOT FLASH THIS.
[ FROYO Kernel 2.6.32.9 ]
[<{ ATT OLYFR_U4_1.8.3 (Official ATT ONLY) }>]
[ Original Stock Kernel ]
The CWM File ==> ATT original Kernel Version <==
[ Overclock Kernel, Max @ 1.1 GHz ]
The CWM File ==> ATT FR Kernel Version 0.1.0n <==
[ GINGERBREAD (2.3.4/5/6) Kernel 2.6.32.59]
[<{ OLYGB_U4_5.9.1 (ATT, INTL Unified) }>]
[ Original Stock Kernel ]
The CWM File ==> ATT original Kernel Version <==
The CWM File ==> INTL mbr_d00 original Kernel Version <==
The CWM File ==> INTL mbr_1100 original Kernel Version <==
[ Overclock Kernel, Max @ 1.45 GHz version ]
The CWM File ==> Unified GB Kernel Version 026 @ 1.45 GHz <==
md5sum ==> <==
[ Overclock Kernel, Max @ 1.3 GHz ]
The CWM File ==> Unified GB Kernel Version 026 @ 1.3 GHz <==
md5sum ==> <==
[ Enhanced Stock Kernel, Max @ 1.0 GHz ]
The CWM File ==> Unified GB Kernel Version 026 @ 1.0 GHz <==
md5sum ==> <==
[ CYANOGENMOD 7 Kernel 2.6.32.56 ]
[<{ CyanogenMod 7 (ATT, INTL Unified) }>]
[ Original Stock Kernel ]
The CWM File ==> cyanogenmod kernel <==
[ Overclock Kernel, Max @ 1.45 GHz ]
The CWM File ==> Unified CM7 Kernel Version 024_r2 @ 1.45 GHz <==
md5sum ==> <==
[ Overclock Kernel, Max @ 1.3 GHz ]
The CWM File ==> Unified CM7 Kernel Version 024_r2 @ 1.3 GHz <==
md5sum ==> <==
[ Enhanced Stock Kernel, Max @ 1.0 GHz ]
The CWM File ==> Unified CM7 Kernel Version 024_r2 @ 1.0 GHz <==
md5sum ==> <==
[ CYANOGENMOD 7 Kernel 2.6.32.56 ]
[<{ CyanogenMod 9 (ATT, INTL Unified) }>]
[ Original Stock Kernel ]
The CWM File ==> cyanogenmod kernel <==
[ Overclock Kernel, Max @ 1.45 GHz ]
The CWM File ==> Unified CM9 Kernel Version 026 beta 1 @ 1.45 GHz <==
md5sum ==> <==
[ Overclock Kernel, Max @ 1.3 GHz ]
The CWM File ==> Unified CM9 Kernel Version 026 beta 1 @ 1.3 GHz <==
md5sum ==> <==
[ Enhanced Stock Kernel, Max @ 1.0 GHz ]
The CWM File ==> Unified CM9 Kernel Version 026 beta 1 @ 1.0 GHz <==
md5sum ==> <==
[ Installation procedure: ]
[ CWM Method ]
1. reboot to CWM
2. Clear cache
3. install zip from SDcard
4. Reboot
DONE!
[ Bulletin: ]
Version 0.2.3 is OUT!
CIFS+UTF-8... check out CIFS Manager from fellow XDA Developer
[ Bugs: ]
[<{ ATT OLYFR_U4_1.8.3 }>]
None So far....
[<{ ATT OLYGB_U4_5.9.1 }>]
None So far....
[<{ CyanogenMod }>]
webtop issues
[ Change History: ]
See 2nd Post!
Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this ROM or Kernel!!!
My github in Compliance with GPL69[ History: ]
Version 0.0.1 (deprecated)
Added FakeShmoo OC/UV
Compiled with Tegra2 specific VFP optimizations, Tegra2 specific optimizations
Added BFQ I/O Scheduler
Added SLQB memory allocator
Added EXT4 support (NOT ENABLED YET)
Added CIFS + UTF-8 support (for windows shares)
Added TUN/TAP support directly
Added FUSE (file system in user space)
Added AVP overclock (system bus)
Merged WiFi Module into kernel source tree
Version 0.0.2 (deprecated)
Compiled with 1.5.7 config
Version 0.0.3 (deprecated)
Reduced CPU Freq/Voltage table from 7 to 6 slots
Adjusted CPU Freq/Voltage table
Version 0.0.4 (deprecated)
Updated Freq Table to allow for 1.2 GHz OC
Updated WiFi module compilation flags
Version 0.0.5 (deprecated)
Revert "Updated Freq Table to allow for 1.2 GHz OC"
Version 0.0.6 (deprecated)
Re-base on MT870's 2.3.4 Kernel Hack (Credit to edgan for point this out!)
Preserved all previous patches except WiFi (No WiFi module included!)
Version 0.0.7 (deprecated)
Fixed a patch error... Oops... (DOH!)
Version 0.0.8 (deprecated)
Revert back to SLUB from SLQB
Version 0.1.0n (Long Term Stable Release, FR)
[{< OLYFR_U4_1.8.3 >}] (ATT)
Based on latest ATT source OLYFR_U4_1.8.3
Enabled SLQB again
Working WiFi Moudle (Finally)
Overclocking Works! (Finally, use SetCPU latest version)
Version 0.1.1_r2 (deprecated)
Based on latest MT8710 source for China Market
Re-Introducing EXT4 File system
(the file system is formatted as EXT3, but mounted as EXT4. 100% BACKWARDS COMPATIBLE with EXT3)
Overclock option for 1.2 GHz, but system only allows up to 1.1 GHz for now
init.rc optimization
Version 0.1.2 (deprecated, GB)
Cleaned up FakeShmoo Overclocking code in general for future updates
Overclocked 3D engine (350 MHz)
Overclocked SDRAM from 300MHz to 333MHz
Overclocked AVP further (280 MHz)
Enabled Undervolting Support in SetCPU to allow for User Undervolt
Version 0.1.3 (deprecated, GB)
Based on Official Motorola U4_5.91 Source Code Release
Version 0.1.4 (deprecated, CM7)
Based on Official Motorola U4_5.91 Source Code Release
Patched to Linux Kernel 2.6.32.39
Version 0.1.6 (deprecated, GB/CM)
Boot time command line ATAG fix up for all tegra parts. (Thanks to Eval- for patching this )
Version 0.1.7 (deprecated, GB/CM7)
Fixed minor code error in overclocking
Version 0.1.8 (deprecated, GB/CM7)
Introducing 1.3 GHz Overclock :androidwink:
ARM optimized spinlock
THUMP-EE enabled
Version 0.1.9 (deprecated, GB/CM7)
Tweaked voltage table for better 1.3 GHz stability
Version 0.2.0 (deprecated, GB/CM7)
Added AVP processor suspend (this will greatly improve battery life)
Added Fixes from the new Photon 4G source code
Added ARM SWP/SWPB instructions back
Added Several Power management patches
Added CPU sibling code for setting cpu policies for 2nd CPU
Added JHash3
Added 1.0 GHz stock clock
Added RCU optimization
Version 0.2.1 (deprecated, GB/CM7)
Optimized memcpy and memmove
Optimized CRC32 and CRC32c
Updated Binder to latest AOSP version
Updated Low Memory Killer to latest AOSP version
Increased OC to 1.45 GHz stable
Version 0.2.2 (deprecated, GB/CM7)
cpufreq: fix cpu freq issues
block: limit default readahead size for small devices
PM / Suspend: Fix bug in suspend statistics update
mm/vmalloc.c: eliminate extra loop in pcpu_get_vm_areas error path
lockdep: print lock name for lockdep_init_error
init/main.c: execute lockdep_init as early as possible
[PATCH] Input: introduce device properties
[PATCH] input: mt: Add hovering distance axis
input: mt: Break out slots handling
Input: introduce MT event slots
USB: f_mass_storage: Disable write cache support
kernel:sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire
sched: don't call task_group() many times in set_task_rq()
compilation: clean up most warning messages during compile
PM: wakelocks: Don't report wake up wakelock if suspend aborted
aes1750: Suspend fingerprint sensor earlier
rtc alarm: fix bad index when canceling alarms[]
kernel patch: 2.6.32.47 -> 2.6.32.48
mmc:core: revert to pre-2.6.32.40 mmc driver
irq: fix build error due to missing irq_pm_syscore_resume
kernel patch: 2.6.32.9 -> 2.6.32.47
ARM: support XZ compressed kernels
decompressors: add boot-time XZ support
decompressors: add XZ decompressor module
arm: Allow CPU-supported unaligned accesses
PM: wakelocks: Display wakelocks preventing suspend by default
mmc: core: put eMMC in sleep (cmd5) mode before suspend
staging:lowmemkiller add Fudgeswap
Staging:zram: Specify default disksize via menuconfig (in bytes)
zram: Set initial disksize to some default value
zram: Simplify zram disk resizing interface
zram: Kernel config option for number of devices
Staging:ZRAM: Make default zram allocation configurable via menuconfig
zram: Fix sparse warnings
swap: Add swap slot free callback to block_device_operations
Add zram driver
Version 0.2.3 (Short Term Release, GB/CM7)
The CWM File ==> Unified GB Kernel Version 023 @ 1.45 GHz <==
The CWM File ==> Unified GB Kernel Version 023 @ 1.3 GHz <==
The CWM File ==> Unified GB Kernel Version 023 @ 1.0 GHz <==
The CWM File ==> Unified CM7 Kernel Version 023 @ 1.45 GHz <==
The CWM File ==> Unified CM7 Kernel Version 023 @ 1.3 GHz <==
The CWM File ==> Unified CM7 Kernel Version 023 @ 1.0 GHz <==
Fixed Various Gaming issues including Plants Vs Zombies
Fixed Webtop issues (GB version only!)
kernel.h: Add BUILD_BUG() macro.
hugetlb: Replace BUG() with BUILD_BUG() for dummy definitions.
ARM: Add optimised swahb32() byteswap helper for v6 and above
sched/rt: code cleanup, remove a redundant function call
PM / Sleep: Unify diagnostic messages from device suspend/resume
PM / Sleep: Drop pm_op() and pm_noirq_op()
mm: retry page fault when blocking on disk transfer
kernel patch: 2.6.32.48 -> 2.6.32.49
kernel patch: 2.6.32.49 -> 2.6.32.50
overclock: fix freq table derpage at nvrm_clocks_limits.c
PM / Sleep: fixed coding derp from "Drop pm_op() and pm_noirq_op()"
Version 024 (Current, GB/CM7)
switched to fast NoHz tree RCU
Completely rebuilt from scratch based on ATT 4591 baseline
Both Stock and Cyanogen now share the same baseline code base
Patched to latest kernel.org 2.6.32.56
Fixed some warnings during compilation
enabled NETFILTER_XT_MATCH_MAC (for wifi tethering app users)
arm/vfp: vfp_pm_suspend: Use local variable instead of rereading from register
ARM: vfp: clear fpscr length and stride bits on entry to sig handler
ARM: vfp: move user vfp state save/restore code out of signal.c
ARM: vfp: flush thread hwstate before restoring context from sigframe
crc32: Don't reference unnecessary crc32 tables in single-bit mode
ARM: proc-v7.S: remove HARVARD_CACHE preprocessor guards
ARM: net: JIT compiler for packet filters enabled by default
ARM: net: JIT compiler for packet filters
include/filter.h: add missing rcu_types.h for kernel usage
ARM: hwcaps: add new HWCAP defines for ARMv7-A
ARM: hwcaps: use shifts instead of hardcoded constants
mmc: fix deadlock from mmc core when suspend the device
mmc: change mmc_delay() to use usleep_range()
nohz: Remove ts->inidle checks before restarting the tick
Version 026 (Current, GB/CM9)
Incorporated kernel code fix up from Epsylon3
Incorporated kernel code fix up from LGE's v21y kernel source drop
Updated to mainline 2.6.32.59
Incorporated few patches from Android Common
Enabled Early Suspend/Late Resume driver for cpufreq to limit max screen off frequency
-- While Screen is OFF
---- CPU is limited to 503MHz max and 2nd core taken offline.
Enabled kernel version of memcpy instead of userspace copy (to use more efficient kernel memcpy routines)
Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this ROM or Kernel!!!
My github in Compliance with GPL25quick status update:
I have recently patched the kernel to the latest kernel.org version 2.6.32.48 and added a number of patches and enhancements to it. The next weekly CM update should have all the things I just mentioned.
I am re-writing the OC completely from scratch. This will probably miss the next weekly update window. The current OC scheme has some flaws:
1. Unable to control max speed with SetCPU or other OC apps
2. Webtop will always use MAX freq regardless
3. No built-in thermal protection (esp for users of 1.45 GHz version)
I am trying to address ALL of the above in 1 gigantic re-write, but lately I've been dealing with personal life as well and so it has been slow... I should have some time this weekend starting tonight. I will try to squeeze as much in as possible this weekend and hopefully have something workable when the weekend is finished.
