Anyone getting random restarts/shutoff on XWPL7. I'm on Siyad kernel v3.1rc5 and heard that is good but battery life sucks and wifi doesn't turn on sometimes. Kinda regret going to ICS this early.
Stock LP7, none of those issues.
Upgrade to XWLP8 and latest siyahkernel 3.1.1
Issues are solved....well I have no issues.
Otherwise boot into cwm recovery, wipe cache, Dalvik, fix permissions,... helps for some. Other report that problem returns.
Edit: battery life: clear any boot scripts and, use the "battery" profile found on siyahkernel cwm kernel menu. This enables 3 step gpu and gpu UV. Also users battery friendly governor ondemand (siyah modded) with deadline scheduler.
Sent from my GT-I9100 using xda premium
funny! people use custom kernels without tring the officil thing and than the whole OS is crap.
wifi issue doesn't look kernel dependent... see
http://code.google.com/p/android/issues/detail?id=28036
Related
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
Help me, please. I just flashed my Optimus One with Goldenleaf kernel BFS v18c yesterday and it wasn't as good as it is reviewed by the users. It did not boost my performance, doesn't make my battery last longer, doesn't have a better gaming performance and what's worst is :
My camera stopped working.
Everytime I restart my phone, it asked me to force close setting.
It always doesn't read my sd card completely.
My gallery stopped working too.
I cannot connect my phone to the computer anymore. (it does nothing but only charge)
A black and white screen (like those in the television when you does not have signal) appears everytime i try to unlock.
The keyboard reacts vey slowly.
It doesn't auto rotate anymore. (Let's just say it doesn't rotate at all anymore.
So this morning i was trying to "un-flash" the kernel to the old stock kernel and flash it again with another kernel but couldn't find anything in the internet. I got angry and just flashed it with the new kernel (Goldenleaf BFS v18a) without "un-flashing" it first. I flashed it with Goldenleaf BFS v18a because i thought the older version might be more stable.
After i flashed it with Goldenleaf BFS v18a, the same thing still continue to happen.
I couldn't find anything in the internet. I don't know what to do, can anyone help me, please ?! Your help is very much appreciated.
When you flash a kernel different to the default rom, the only way to get back to that default rom kernel is to reflash the rom, in your case my best bet is your using cm7 6.5.8. That being said the latest updated franco kernel is cfs 19.2. Somethings wrong with the brain **** scheduler (bfs)..your best bet, reflash everything and start from scratch, do your backups than wipe everything in recovery, before I ever flash a rom or kernel..I always wipe cache and dalvik cache than flash than wipe cache/dalvik cache..the most important lesson is knowing a .32 kernel (goldenleaf, franco 19.2) are designed for .32 roms ,you can't mix a 35 kernel with 32 RIM or you'll end in a bootlop...read everything you can before you flash anything because those problems you say your experiencing I never once had myself.. don't expect gold, franco and fserve work there asses off trying to her good kernels out. To recap: either use fserves goldenleaf or francos cfs 19.2 but restart everything before you do, get a clean slate...inbox me if you got the same problems, alot of devs are tied up at the moment
Sent from my Optimus One using xda premium
Jrhodes85 said:
When you flash a kernel different to the default rom, the only way to get back to that default rom kernel is to reflash the rom, in your case my best bet is your using cm7 6.5.8. That being said the latest updated franco kernel is cfs 19.2. Somethings wrong with the brain **** scheduler (bfs)..your best bet, reflash everything and start from scratch, do your backups than wipe everything in recovery, before I ever flash a rom or kernel..I always wipe cache and dalvik cache than flash than wipe cache/dalvik cache..the most important lesson is knowing a .32 kernel (goldenleaf, franco 19.2) are designed for .32 roms ,you can't mix a 35 kernel with 32 RIM or you'll end in a bootlop...read everything you can before you flash anything because those problems you say your experiencing I never once had myself.. don't expect gold, franco and fserve work there asses off trying to her good kernels out. To recap: either use fserves goldenleaf or francos cfs 19.2 but restart everything before you do, get a clean slate...inbox me if you got the same problems, alot of devs are tied up at the moment
Sent from my Optimus One using xda premium
Click to expand...
Click to collapse
Can you show me a step by step tutorial? I'm really bad in this. I took 2 days to root my phone, that's how bad i am. And one more thing, it doesn't auto apply my Golauncher theme which i had moved to SD card when i turned it on and the keyboard reacts very slowly.
thanks for solving
Samsung Galaxy SIII GT-I9300
Hi, I just recently installed ARHD 11.2 with the Perseus Kernel onto my S3, and it generally runs very smoothly and the battery life is greatly improved.
However, after a while, the phone starts getting very laggy and unresponsive (it will take more than 5 seconds to recognize any input) and I have to restart the phone. It'll work fine again for a while before it starts getting laggy again. Because of this, I just had to go back to the stock ROM.
Anyone have a similar problem? Note that I haven't used any other performance tweaks, only just the Perseus Kernel.
rustingee said:
Samsung Galaxy SIII GT-I9300
Hi, I just recently installed ARHD 13.0 with the Perseus Kernel onto my S3, and it generally runs very smoothly and the battery life is greatly improved.
However, after a while, the phone starts getting very laggy and unresponsive (it will take more than 5 seconds to recognize any input) and I have to restart the phone. It'll work fine again for a while before it starts getting laggy again. Because of this, I just had to go back to the stock ROM.
Anyone have a similar problem? Note that I haven't used any other performance tweaks, only just the Perseus Kernel.
Click to expand...
Click to collapse
which version of Perseus are you running? because i have heard that the latest perseus kernel has a bug or something, hence, using the v24.x is recommended at the moment..
try this
- Boot to CWM recovery
- wipe cache partition
- wipe dalvik cache (under advanced)
- fix permissions (under advanced)
- reboot system now
Ok, I will try flashing ARHD again with an older version of Perseus. I'm not sure what version it is, but I downloaded the latest version of ARHD very recently, so I'm guessing it comes with the latest version of Perseus.
PS. Noob question, but where can I find older version of Perseus? I can only find 25.3 from the thread in the developers forums.
Oh v25.3 is out maybe he made some bug fixes already.. and it will work great with ARHD v13
Perseus kernel v24.x is already implented in ARHD's Aroma installation
Sent from my GT-I9300 using xda premium
Greetings gentlemen,
I'm here today to ask for your help.
For the last 5 days I am experiencing extreme battery drainage(Android OS nearly 100% Battery Usage ). Back when it began I did not install anything suspicious or battery consuming software. I never go full screen brightness, and all unnecessary apps are either deleted or disabled. I have tried Factory Resetting, Wiping all possible caches, systems, internal/external SD cards. I even tried manually deleting all folders from my PC. I have tried installing custom kernels, roots and even stock ROM. Right now I'm with stock ROM with CF root. Phone state: Model number- GT-i9100; Android 4.0.3; Baseband v. i9100XXLPS, Kernel v. 3.0.15-i9100XXLPQ-CL223505 se,[email protected] #3; Built number IML74K.XWLP7. And here is what I get from the battery report : i41.tinypic(dot)com/1j9nae.png
I have tried full discharge and charge to 100% and calibration. Even cleared the battery stats It just doesn't work. I am using Nova Launcher. Even after going back to TwLauncher I am still getting 98% Android OS usage. I don't use Data Mode and Wi-Fi isn't always on. When charged and calibrated at 100% at 21:00pm, in the morning at 9:00am phone battery is completely empty and shut down.
If you can help me fix this I'd like to use the stock ROM, with a nice battery stable kernel & still with Nova Launcher. NOTE: This is still happening with a NEW battery.
:fingers-crossed: If you could help me I'd be extremely grateful.
Your problem seems like what i had previously
What i think I'd that it is still a kernel problem or that u r facing SODS
Both in my opinion can be fixed by changing kernel
It happened to me that no kernel except dorimanx works for me all other kernel cause sods on samsung based roms
Try dorimanx kernel v8.35 if u r using Samsung based rom
Although that kernel would fix the problem it would slow d phone occasionally
Therefore i recommended u use aosp based rom or even better use all the things that i m using, they r mentioned below
N also follow this guide :
http://forum.xda-developers.com/showthread.php?p=35061392
N see the screenshots below for my battery life n antutu benchmark
Hope this helps u :thumbup:
Rom: carbonrom stable v1.8
Kernel : dorimanx v9.35
Governor: nightmare
No OC or UV
Battery : stock (1650mah)
Sent from i9100
So when I tried my first JB ROM (infection), I started having some pretty significant stability issues. So after a while I assumed it was just the ROM, but after now also trying Liquid, and still having the same issues, I'm wondering if there's something else going on. Specifically, the phone randomly reboots often, and sometimes will just hang when I go to turn the screen on for a minute or more, before finally starting to respond.
When I installed Liquid, I did a system wipe and formatted the cache and delvik cache twice. At this point should I try formatting the data partition, and the SD card? I'm using CWM. Any suggestions?
Jfichtner said:
So when I tried my first JB ROM (infection), I started having some pretty significant stability issues. So after a while I assumed it was just the ROM, but after now also trying Liquid, and still having the same issues, I'm wondering if there's something else going on. Specifically, the phone randomly reboots often, and sometimes will just hang when I go to turn the screen on for a minute or more, before finally starting to respond.
When I installed Liquid, I did a system wipe and formatted the cache and delvik cache twice. At this point should I try formatting the data partition, and the SD card? I'm using CWM. Any suggestions?
Click to expand...
Click to collapse
Try a different ROM. I had stability issues as well, with both of those ROMs.
Freedom First said:
Try a different ROM. I had stability issues as well, with both of those ROMs.
Click to expand...
Click to collapse
Any JB ROMs you've had luck with?
All your issues are caused be the fact that min frequency need to be upped to 384mhz ....I've had best stability with ondemand governor and sio scheduler set on boot under performance in settings...4.1.2 and 4.2.2 based roms have softboot errors straight after install and this fixes most of them...you'll get better stability out of cm9 ICS based ROMs or cm10.2 which is 4.3 based ROMs...still changing your min frequency is a necessity...also when flashing especially new different ROMs...please don't forget to clean flash everything...dirty flashing by only wiping dalvik cache and cache will carry over every issue from precious ROMs...plus its highly recommended in all the original posts....another issue is make sure you use twrp or cwm....amon ra causes many issues on the rezound
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
To add,make sure you are on the latest hboot and radios. Be warned it will require s-off to restore/downgrade the firmware and radios if you do update them.