Hi.
I'm facing a "hard to solve" issue with my Atrix 4G...
It is a non-ATT (international). Using RSD Lite, I flashed the Retail SBF and it worked OK, battery life was "normal" and the phone was cold most of time.
I then unlocked the bootloader flashing the IHOP SBF then using moto_fastboot method. Installed Clockworkmod Recovery and flashed the HomeBase rom with the updates.
What happen is: The phone starts to get very warm and the battery is drained very quickly (couple of hours).
Using the SetCPU, I could verify that the CPU does not scale down automatically. It's always at 1300Mhz, it doesn't matter if the phone is idle or not.
I can reduce the CPU speed using the SetCPU but the processor is with the two cores active all the time and it never reduces the speed below the limit set in SetCPU.
I thought it may be a problem with my phone, so I flashed the retail SBF again and I could verify that, bakc with the retail rom, CPU is scaling down correctly. It goes up to 1000Mhz when requested but stays ~300Mhz when phone is idle.
I did the BL unlock/motofastboot/clockwordmod/ procedure again and tried with different roms (Aura, Alien, RedPill, etc) always cleaning up the Cache/UserData/Dalvik and using the faux 1.3Ghz unified kernel but got no result, on every 2.3.4 rom I flash, the CPU is always at the maximum speed set by the kernel or limited by the SetCPU.
I've found a similar problem on this thread: http://forum.xda-developers.com/showthread.php?t=1190634. and did the same investigation but I was not able to identify any aplication that is making the CPU usage to be constantly high (even tried killing all Apps, not result).
Any ideas what I can do/try to solve this issue?
Thanks a lot.
That happened to me too!! I just reflash the rom wiping everything and the cpu started acting normal
Try to use fastboot to wipe if ur using CWM
Sent from my CM7 Motorola Atrix 4G
For me turning off the phone and back on worked, if not for you then try wiping the usual stuff before reflashing a rom or back up
Feom what I've seen, this is often caused by the webtop. Most ROMs don't touch the webtop, and it seems for some people, this causes problems. I fixed my issue by installing a ROM that (I believe) wiped the webtop. That ROM was deprecated a long time ago so I don't know if it's still available. I'd take a look at the Developer forum. There are some webtop files you can download that reportedly fix the issue. You might also try using fastboot to erase the webtop.
Sent from my MB860 using XDA App
@vibrantuser
Thanks. Yes, I tried flashing and re-flashing couple of times, no luck whatsoever...
@Ilkinansr92
Thanks for the tip. Will try that and see how it goes.
@ronii1123
Will try that this weekend I'll report about progress.
@frelnik
Thanks for the tip. It makes sense as the retail SBF re-flashed the Webtop area and all roms I tried doesn't touch it. I'll try to get a webtop image and flash it using the fastboot or the CWM method. If you can point a link to any that may work, I'll really appreciate it.
Thanks a lot.
I installed the ROM from here to fix my issues. Every ROM thereafter was fine:
http://briefmobile.com/download-android-2-3-4-gingerbread-for-motorola-atrix-4g
I believe I've heard some people had success with the webtop CWM from here:
http://forum.xda-developers.com/showthread.php?t=1169457
I do wonder if erasing the webtop would be enough. You could try
fastboot erase webtop
faux123 said:
Just a quick Info dump:
Just going through the code and realized why SetCPU failed to keep the clock frequencies set properly. SetCPU has NOT been designed to work with dual core properly. It only sets the scaling_max_frequency for cpu0 (master CPU) and not for cpu1 (slave). When under load, cpu1 gets awaken by the system, but it's frequencies are still the old 1.3 GHz and since Tegra2 is a synchronous SMP design, the scaler would use the highest frequency again (this case 1.3 GHz). This is why after playing games, or apps that needed the 2nd cpu would cause the system clock to revert to original default 1.3 GHz even when you set it via SetCPU to something lower.
This is not easy to fix, when SMP is involved. I have tried a few hax already and still unable to tame the 2 headed beast. I will continue to work on it or find an alternative solution to SetCPU's issues
Click to expand...
Click to collapse
quoted from Faux himself, there's a bug in his kernel that prevents us from underclocking it. should be fixed in the next release.
Alcapone263 said:
quoted from Faux himself, there's a bug in his kernel that prevents us from underclocking it. should be fixed in the next release.
Click to expand...
Click to collapse
That's a separate problem, I think. My understanding is that the OP's issue is the CPU is always running at the maximum speed. It never clocks down to the slower speeds when idle. The issue with Faux's kernel and SetCPU is that no matter how you set it, when stressed, the CPU runs at the maximum speed the kernel is capable of, not the speed you set in the app. The CPU does clock down when idle, but will ramp up to 1.3 GHz even if you set it to only 1 GHz in SetCPU. I've experienced both issues.
You have to set it at 800 mhz for it to stick. For some reason setcpu only recognizes under clocking under 1 GHz, otherwise it presumes that it's running at the 1 GHz stock speed without registering the overclock, therefore thinking the stock is 1.3 GHz! I'm not sure but I would have a guess and say that it's something to do with the unchangeable governors? Hope this makes sense lol
Sent from my OC Atrix running homebase 4.7, simplicity themed using xda premium
[SOLVED] CPU not Stepping Down - Warm Phone
frelnik said:
I installed the ROM from here to fix my issues. Every ROM thereafter was fine:
http://briefmobile.com/download-android-2-3-4-gingerbread-for-motorola-atrix-4g
I believe I've heard some people had success with the webtop CWM from here:
http://forum.xda-developers.com/showthread.php?t=1169457
I do wonder if erasing the webtop would be enough. You could try
fastboot erase webtop
Click to expand...
Click to collapse
Hey freinik.
I cleaned up the webtop and reflashed the Home Base rom I was using.
Perfect!
CPU is now scaling correctly. Your suggestions was exactly what was needed.
After cleaning the webtop (using the fastboot erase webtop) the issue was solved.
Thanks a lot.
Think in having the same issue with my international atrix alien rom.
Can you provide clear instructions on how to remove webtop and what will it affect if any by removing it?
Hope you can help.
Sent from my mobile
@ultim
Hi, Thanks for asking.
I erased my webtop using the moto fastboot command line, you can get it here:
http://forum.xda-developers.com/showthread.php?t=1138092&highlight=fastboot
After installing, reboot you phone and enter the "fastboot" mode (holding volume down until the "fastboot" text appears, then press volume up.
Once on fastboot mode, connect your phone to the USB port and run:
moto_fastboot erase webtop
It should erase your webtop partition.
It normaly helps to clean the cache/data, you can do that by running:
moto_fastboot -w
You can then, reboot the phone.
moto_fastboot reboot
If you're using Linux, moto_fastboot should be run as superuser, you can do that by using sudo, ie. sudo moto_fastboot reboot.
Hope this helps.
@Nyx_ Thank you for the instructions. My battery life is so much better now. Before application 'X' (i assume its webtop) would use about a third of my battery all the time.
Thanks for this. I recently discovered the same thing was happening to my phone and deduced that the webtop was causing this. I was using faux's newest kernel. I then related the stock kennel and everything was file after that, no cleaning of the webtop was needed.
Sent from my MB860 using xda premium
Related
Google just moved out the 2.6.32 kernel from the experimental git repo to the msm repo. This means that google thinks they are stable now.
There are currently two 32 branches:
android-msm-2.6.32-nexusonec
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32-nexusonec
android-msm-2.6.32
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32
I've compiled both and I'm finding the nexusonec branch more stable than the 32 branch. The 32 branch causes issues with the gallery and camera app not recognizing the sd card. Everything seems to work fine in the nexusonec branch (sdcard, wifi, BT, camera, etc). Speed is definitely faster than 29.
For those who are interesting in flashing the 32 zimage, they can d/l it here:
http://drop.io/xdp6104#
Right now the kernel is just a stock config, meaning no tethering or anything else. Only change I've made from stock is to use the deadline I/O scheduler. I'm sure cyanogen will add those other goodies when he releases a new version.
Very nice: cant wait for a Enomther rom with this new Kernel
nice....
ive compiled a nice cyanogen kernel 2.6.32 already
just need to get the wifi module compiled correctly and we are gtg!
Does this mean that they've fixed some of the power saving regressions people were seeing with 2.6.32 before?
Installed on my Nexus with enomther 1.61: works nicely
Tot mem 395448K, Free 265916K
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
eug89 said:
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
Click to expand...
Click to collapse
86% now and charging..
eug89 said:
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
Click to expand...
Click to collapse
It wasn't an issue per-se it was a 'feature'
The problem was caused by downgrading to older kernels after using 2.6.32. Certain hardware states that were set by the new kernel telling the battery not to charge weren't being un-set by the new kernel, and the older kernel didn't even know about them. They patched the newer kernel pretty quickly after getting feedback so that it removes the hardware state when shutting down, I believe. So, yes, it's 'fixed'
FettsVett said:
It wasn't an issue per-se it was a 'feature'
The problem was caused by downgrading to older kernels after using 2.6.32. Certain hardware states that were set by the new kernel telling the battery not to charge weren't being un-set by the new kernel, and the older kernel didn't even know about them. They patched the newer kernel pretty quickly after getting feedback so that it removes the hardware state when shutting down, I believe. So, yes, it's 'fixed'
Click to expand...
Click to collapse
Thanks, i called it issue because i didn't know how to call it but i knew that it was meant to be a sort of new feature of the 2..6.32 kernel and I wanted to write above 90% and not under 90%... did a bit of a mess
woahhh its way faster
thanks dwang
will do some thorough testing and post back soon.
edit: Hmmm having some trouble with fastboot... unable to push wifi via adb?
anyone else encountering this?
Are you trying to push the ko module on fastboot mode?
This kernel is FAST and SNAPPY! HIGHLY RECOMMENDED!
boqonx said:
Are you trying to push the ko module on fastboot mode?
This kernel is FAST and SNAPPY! HIGHLY RECOMMENDED!
Click to expand...
Click to collapse
yeah. iirc thats where you do it right?
Let the OS run, then push through adb. Can't do it when it's on recovery either because the /system/lib is not mounted. Wifi should work even without a restart.
yep just did that
i think i was just confused on where to use adb
it still works so all good. this kernel is zippy.
Damn right This thing flies now! Scrolling through messages is MUCH smoother. Seen a lot of tearing when scrolling on CM's kernel.
I released my undervolted version of CM's in the other thread. He changed the scheduler from anticipatory to deadline as well.
Will try! Had any reports on instabilities yet?
Dwang: great job on the deadline scheduler suggestion. It really does make the whole experience smoother.
Can someone write the exact adb command to push it?
Code:
adb remount
adb push ./bcm4329.ko /system/lib/modules
himmatwala said:
Can someone write the exact adb command to push it?
Click to expand...
Click to collapse
Okay I've posted about this before, but still can't figure it out...
My issue is this: When I install a GB rom, everything runs fine until my screen goes off.... its even fine if it goes off for a second, but if it sits for more than one second it reboots. A full reboot. I've tried both GB kernels, as well as MR 2 and 2.5. I've also tried using setcpu to set the minimum all the way up to 1.4GHz with no help.
Can someone help me fix this screen off issue? PLEASE?
Seems to have something with the dip in processor speed because when my phone is downloading from the market or signing in to google, or doing anything for that matter... the problem doesnt occur.
I don't really accept that I can't use Gingerbread because of this... there HAS to be a fix.
Thanks yall
What gingerbread roms have you tried? Also, what kernels were you using?
Sent from my ADR6400L using Tapatalk
don't have this issue on Synergy 3.0 running the latest ziggy kernel
I've tried every GB rom on here, as well as both kernels
also, Ziggy kernel? You in the right section?
I would try wiping, then installing the setup in my signature, but don't restore any apps at first or sync with Google so they're downloaded automatically. I think that you've got an app and a kernel that's interfering with one another. Try the ROM bone stock before you start restoring apps and see if the problem is there.
Rooted Thunderbolt on BAMF Sense 3.0 RC 4 with MR2 radio and latest dreamKernel.
Silentdawn3 said:
I've tried every GB rom on here, as well as both kernels
also, Ziggy kernel? You in the right section?
Click to expand...
Click to collapse
when you say both kernels are you referring to the radios? cause mr2 and mr.5 are radios not kernels
Silentdawn3 said:
Okay I've posted about this before, but still can't figure it out...
My issue is this: When I install a GB rom, everything runs fine until my screen goes off.... its even fine if it goes off for a second, but if it sits for more than one second it reboots. A full reboot. I've tried both GB kernels, as well as MR 2 and 2.5. I've also tried using setcpu to set the minimum all the way up to 1.4GHz with no help.
Can someone help me fix this screen off issue? PLEASE?
Seems to have something with the dip in processor speed because when my phone is downloading from the market or signing in to google, or doing anything for that matter... the problem doesnt occur.
I don't really accept that I can't use Gingerbread because of this... there HAS to be a fix.
Thanks yall
Click to expand...
Click to collapse
I share your pain with this exact problem. I have been doing all types of testing these last two days to see if there is any combination of ROMS and Kernals that would work for me.
I can flash any ROM I want, and the only Kernal that I can successfully use is this one:
Imoseyan GB Stock Kernal
With this Kernal, I can use my phone all I want, let the screen go black, hit the lock screen button and I have never had a reboot.
I have run Thunderstick, BAMF 2.1, BAMF 3.0, Gingertheory, with this kernal and it will run fine.
When I change to any of these Kernals, I get the constant reboots when my screen goes off, just like the OP described.
* Imoseyon Lean Test
* Imoseyon 184mhz
* Imoseyon USBfix
* Imoseyon 2.5.3 test 7
* Nerozehl's dreamkernal 2.3.2
Of course, when flashing any ROMS and Kernal combinations, I would do a complete wipe before doing so. I should also mention that I am using MR2 radio. I can also use MR2.5 with the GB Stock Kernal and it runs fine.
So like the OP, it seems to be something to do with the kernal that my phone does not like and can't figure out. Anything other than the stock kernal, and my phone will constantaly reboot after the screen goes black.
I should also mention that I have used the speektweah.sh in terminal emulator and tried all of the different voltage settings and it had no effect. Also disabled it and tried using SetCPU and no luck either.
I have also tried all of the ROMS without allowing any apps to update by skipping the google account sign in. So basically all of the ROMS were running in their native state, and the outcome would be the same.
FOR THE OP
Try running the stock kernal and let us know if that works for you. You should just be able to flash it in CWM, reboot and you will know right away if it is working correctly.
The real question I need to figure out is this. What is different about the GB Stock Kernal from all the others that would be having this impact on our phones?
I've tried all of this except installing the above kernel. I'll give that a shot, thanks.
As for installing without apps, I've tried that. Tried everything. Lets hope the stock kernel works!
I've been running Das BAMF Gingerstripped with Imo's kernel and never had this issue. It sounds like maybe something is bad with the cpu profiling becoming unstable when screen-off profiles kick in.
sg1dan said:
don't have this issue on Synergy 3.0 running the latest ziggy kernel
Click to expand...
Click to collapse
I can confirm that this one worked for me too. Synergy 3.0 running Ziggy's Kernal and everything works well.
Anyone know where to grab just the Kernal? Can't seem to find the latest download.
I should also add, that when I do flash the Stock GB kernal so that my ROM will be stable.... my camera freezes everytime I try to take a picture. Happens in every ROM I mentioned above. However, it works fine before I flash the stock kernal.
running "stock kernel" it looks to be fixed. Looks like I tried this before as I already had the file but.... works now for some reason
Thanks.
Will report back if it ****s up
I'm on Gobstopper 2.3.4 and I've recently been modding my phone with faux123's OC kernel, juwe11's ram optimizer, the Webtop hdmi hack and so on, but I recently ran into a problem. Whenever I reboot my phone the widgets don't load and just display as "Problem Loading Widget" in LaucherPro. It might not be because of any of the mods, but it only started happening after I installed them so it's lead me to believe it might be one of them. Please help!!
lexx210 said:
I'm on Gobstopper 2.3.4 and I've recently been modding my phone with faux123's OC kernel, juwe11's ram optimizer, the Webtop hdmi hack and so on, but I recently ran into a problem. Whenever I reboot my phone the widgets don't load and just display as "Problem Loading Widget" in LaucherPro. It might not be because of any of the mods, but it only started happening after I installed them so it's lead me to believe it might be one of them. Please help!!
Click to expand...
Click to collapse
Fix permissions with Rom Manager, or in CWM under advanced, then set up your widgets again. You shouldn't have problems after doing that.
I Also noticed in ADW if I installed a backup configuration within ADW I ran into this problem. If I loaded my widgets after re-loading ADW I did not run into this problem. Caelan's post is also spot on!
I just tried doing that and it came back up as "Problem Loading Widget". I'm using romracer's CWM. Would that make a difference? Should I flash tenfar's? Also, when it boots it seems to almost freeze for a second as my internal storage and sd card are being mounted and then I can slide the bar to unlock.
lexx210 said:
I just tried doing that and it came back up as "Problem Loading Widget". I'm using romracer's CWM. Would that make a difference? Should I flash tenfar's? Also, when it boots it seems to almost freeze for a second as my internal storage and sd card are being mounted and then I can slide the bar to unlock.
Click to expand...
Click to collapse
Fix permissions, reboot, then set up widgets again if you lose them. You shouldn't have any more problems unless you flash another ROM, and possibly another kernel.
Then just do the same thing again if you happen to do that.
This is probably stupid, but you don't have the Widgets installed on the sdcard do ya?
No I have nothing installed to SD. I just tried to fix my permissions and it didn't work CaelanT. They still don't show on a reboot. If I reflash my Gobstopper or another ROM would that work? Should I try fixing the permissions with tenfar's CWM instead of romracer's? Oh and there's a little vibration I feel when the phone boots up right before it displays the lockscreen. Is that normal?
UPDATE: I just noticed that every time I reboot my appwidgets.xml file gets reset!! Please someone help, nothing seems to be working...
lexx210 said:
No I have nothing installed to SD. I just tried to fix my permissions and it didn't work CaelanT. They still don't show on a reboot. If I reflash my Gobstopper or another ROM would that work? Should I try fixing the permissions with tenfar's CWM instead of romracer's? Oh and there's a little vibration I feel when the phone boots up right before it displays the lockscreen. Is that normal?
UPDATE: I just noticed that every time I reboot my appwidgets.xml file gets reset!! Please someone help, nothing seems to be working...
Click to expand...
Click to collapse
Same problem here and only after faux's kernel...I tried all the fixes (fix permissions, wipe cache first before flashing kernel) and the only the thing that worked is to go back to the stock kernel.
Oh man, you may be on to something because EVERYTHING was working fine before last night when I flashed faux123's OC kernel. I'm gonna try and go back to stock and see. Thanks man!
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
lexx210 said:
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
Click to expand...
Click to collapse
Last couple of posts on his thread already mention it.
Sent from my MB860 using XDA Premium App
Swiftks said:
Last couple of posts on his thread already mention it.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ok perfect then I'll just wait for his next version and hope that fixes the problem. I need his kernel to flash ROM's since I'm on a international phone. It's weird saying that since I'm just in Canada...
lexx210 said:
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
Click to expand...
Click to collapse
No problem man....yeah I've made some comments on the the kernel thread about the issue. Hopefully it gets fixed in an updated version.
in the kernel thread (dev) faux is asking INTL users about this issue, for INTL users on his 1.6 unified kernel. some report the widget issue, others do not. its the kernel causing. I am using unified OC 1.6 kernel and am lucky enough to have no issues, and WAY better batter life then stock kernel.
I also encountered this issue, however I don't have an international version of the Atrix.
Using 2.3.4 (pudding version for AT&T) with Alien ROM #4 and faux123's 1.6unified kernel.
Also using Launcher Pro.... I just reinstalled everything after doing a hard reset to try and isolate the problem, and it did occur after the kernel flash.
Same problem here, luckily I just reboot my phone few time a month..(why do I need a reboot, anyways?)
The widget is left blank white with Problem loading widget warning..
I'm not using an INT Atrix, only AT&T (I don't know if there's any other Atrix version) using faux123 1.6, piecrust, romracer cwm ..
any luck, guys?
would there be an update of 1.8 of faux?
I think I'm going partially nuts over this problem. I have tried every thing mentioned in any post. Fix permissions with different CWM's.
I thought was going to win today today when I formatted everything, installed gobstopper 2.3.4 w/ deodex update then setting up my screens with ADW it glitched and would go to the screen preview whenever I touched the screen. a reboot and those damn black boxes are all over the place.
Order of operations:
- format internal/external
- factory reset
- fastboot flashed tenfars CWM which wouldn't mount the internal sd so I couldn't flash
- fastboot erase/flash romracers CWM
- installed Gobstopper 2.3.4
- reboot and used it for an hour or so to let it level out
- installed the deodex update
- reboot and another hour of use with a bunch of reboots to make sure everything was cool (it was)
- used Diviances EXT4 User Journal script
- used it for a few more hours without issue
- installed ADW Ex and while setting up my screens it glitches and goes to the screen preview with every touch.
- reboot... no widgets with a string of expletives
so now what...
Same problem here. I am using latest Aura Rom with latest faux Kernel for International users.
I did everything: Wiped cache, reseted factory, installed rom again, changed kernel to older versions, stock versions, fixed permissions and always lose my widgets configs after a reboot.
Chroid flashes over your current kernel to an android kernel. This disables your overcloking in govnah. Govnah will not allow you to over clock. You will also not be able to flash a different kernel over it, even if you do remove chroid. So be forewarned. Only way to be able to change kernels is WebOS Doctor.
Have a safe pleasnt and positive day.
someone delete this ...click around dude this crap has been posted a million times already
only reason why the OP had problems is because he opened GOvna after installing chroid.
If you don't open govna, when you uninstall chroid ur OC kernel is restored.
The OC kernel can be restored however I noticed unusual high idle battery drain(about 15-20% overnight) with chdroid so I uninstalled it.
I apologize for restating that, even if it was posted everywhere.
p.s. I realized that it is possible to change the kernel if you first flash the stock kernel from preware then flash the kernel you'd like. It should work flawlessly
I’ve flash about 20 different ROMS since I got my SGS2
I’m running checkromHD 4.0 every two days or so my phone seem to turn off or go into a sleep mode and cant be woken up, my friend running the same ROM (which I installed for him) and has got no problems
Ive tried wipe / format data cache and factory reset, tried flashing a stock ROM, then Checkrom 4.0 still the same problem
Can too much rom flashing affect the phone?
Any help would be appreciated
No
Problems are usually user error or rom error .
jje
I agree, I flashed mi phone like 32 times and still rocking
long ago i rested counter and at the moment i have like 50 flashes and i think im gonna flash again tonight...when sth is wrong its either the rom or the users fault...nothing against u but mostly its the users fault
raidenuk said:
I’ve flash about 20 different ROMS since I got my SGS2
I’m running checkromHD 4.0 every two days or so my phone seem to turn off or go into a sleep mode and cant be woken up, my friend running the same ROM (which I installed for him) and has got no problems
Ive tried wipe / format data cache and factory reset, tried flashing a stock ROM, then Checkrom 4.0 still the same problem
Can too much rom flashing affect the phone?
Any help would be appreciated
Click to expand...
Click to collapse
this sounds like too much undervolting, or playing with set cpu settings, very common issue, had it like millions times, either flash a different kernel, or increase voltages of the sleep/wake frequency ([email protected])
with some kernels my voltage for 200mhz was at 825 and was running fine at some kernels i was having no wake issues, so had to put it up to 850-875 or change governor hope this helps
Flash durability
Flash memory durability depends of type. You can expect to be able to flash your phone at least 10,000 times. You will find that the connector which is also rated for 10,000 connections, would wear out first.
Regards,
John.