I am running Slim Bean 3.1.0 by Kayant (Defy+), and I noticed using the Watchdog Lite application that "Mediaserver" is stuck using around 20% CPU all the time.
Using CatLog with a log-level of "verbose," I see the following message which appears approximately 35 times PER SECOND, non-stop:
AudioHardwareMot - Output bufSize from kernel = 8192
The phone is idle, and not playing ANY sound at all, so why is this spam happening? Is there anything I can do to track this down or make it stop?
PS: This happens even if the phone is set to silent and airplane mode with wifi/mobile-data disable, and right after boot, with no other applications running. Also, I recently wiped the sdcard, so there aren't really any media files in it.
Should I just try reinstalling my ROM? :/ Or maybe change the kernel to JellyX (is that related?)
EDIT: Solved. Apparently, the media-scanner had changed some ringtone indexes, and Llama was still pointing to the old values, so my sound profiles were attempting to use invalid data as ringtone/notification tone, which caused the media-server to loop infinitely trying to set that up.
Related
I've been using FreshToast for a few weeks now, the latest one.
I have it OC'ed with OC Widget as I was having issues with SetCPU as others are.
One thine I notice is that when I wake my phone up sometimes the CPU usage is very very high, for upto about a minute after waking the phone up. To the point where it is unusable.
I have been using "SeePU" for a while, which puts a nice CPU activity monitor at the taskbar. It uses VERY LITTLE to NO CPU usage (confirmed with the adb shell "TOP" command) never more than 2%.
The other issue I'm having is once or twice a day when I get a phone call, the screen comes on but to the HTC Lock screen. When I pull the lock screen down, its usually a blank screen with a FC dialog saying com.android.phone or something is busy. The ring tone keeps ringing and ringing and ringing. I have to do a battery pull.
I've even ran the phone with NO DOWNLOADED APPS to rule out any variables. Its definitely a bug in the ROM.
Are you getting any of the problems I've listed?
The symptoms you describe have been noticed by others using setCpu. Another cause that has been discovered is that when using OC Widget DO NOT enable a different setting when the screen is off as this has been proven to cause the wake-up and phone call problem you described.
system_server is being a real pain for me. I found it may have something to do with the location services.
I had too many problems so I installed the normal Fresh Rom
http://forum.xda-developers.com/showthread.php?t=681856
and then I flashed the OC kernel over that
http://forum.xda-developers.com/showthread.php?t=690238
That combo has been working great for me and is basically what Fresh Toast should be.
I have moved over to Fresh and have been extremely pleased. I think it actually runs faster than Fresh Toast even with correct overclocking(on fresh toast that is). Just remember not to put OC programs on, or it will actually underclock.
Hi all, I know there are threads already created for questions etc but I've an extensive list of them and I don't think its appropriate to spam them in someone else's thread. And I'll update the first post of the answers and replies I've received for the questions I've posted!
My phone's information: will5's MIUI ROM 2.5.25 GB 2.3.7
My list of questions
Android OS
::Hard rebinding hard keys::
Is that possible? My power button recently got damaged and its really tough to press the power button now which is quite a problem, is there any way to rebind the power button to say the camera button? (specifically the 2nd-click of the camera button, not the first click (focus)) MS2Toolbox is able to wake screen with the camera button but thats just soft-sided and I need to hard bind for turning on the phone and using the recovery etc... :crying:
::Allow app to stay active when screen-off and when not in foreground:: http://forum.xda-developers.com/showpost.php?p=29658020&postcount=95
I want to let my app, specifically Opera Mobile, to be constantly active as I run a script (user javascript) on it which repeats its function periodically. Is there a way to keep it active throughout deep-sleep, or when in the background? Currently its working well when I switch the screen off as long the app was in the foreground. The script and Opera Mobile still runs perfectly and I do not experience battery drain (weird). I have been doing so for the past few months and it takes probably only 30% of my battery overnight when I sleep despite the periodic data connection. However, this didn't happen on the MIUIv4 ROM when I tested it. The app is 'frozen' or suspended, it seems, the moment I switch the screen off. Tried apps which disabled deep sleep etc but didn't work. Any ideas?
Overclocking
::What are the default VSELs for the respective frequency for MS2?::
I know there's one here http://forum.xda-developers.com/showpost.php?p=11620994&postcount=1 by santiemanuel, but it gives VSELs WAY above those I'm using or the defaults from MS2Toolbox. Say, for 300MHz, the stock vsel is 33 and 30 is considered unstable. How ever the default in MS2Toolbox for that frequency is 17 if I'm not wrong. I'm using that at the moment and it seems to be running fine (used powersave governor to enforce 300MHz to test it out). Just to confirm, should I really follow that table?
WiFi
::Changing Milestone 2's WiFi MAC address::
Hi guys, I've been trying to look for a way to change my M2's MAC address but have not been able to get it to work.
I've googled up for methods but the common ones do not work.
Tried so far:
- The nvram.txt file
Can't find it in the usual folders stated.
- busybox ifconfig tiwlan0 hw ether <MAC>
- busybox ip link set dev tiwlan0 addr <MAC>
Tried these two commands but didn't work either in terminal emulator. Even did the off-on-immediately spam commands but no luck.
Unsorted
Code:
http://forum.xda-developers.com/showpost.php?p=29675172&postcount=905
::SOLVED::
Overclocking
::How do I check the current VSEL and frequency at any point in time?::
I'm trying to underclock and ultra-undervolt to save as much battery as possible and want to know how's the selected governor working in order to manually optimize the settings to my preferences.
::How do I know its an unstable VSEL?::
Q: Quite vague a question but... as said in the first question, I'm running 300MHz at a VSEL of 17 instead of 33, nearly half of the stock. How would I be able to tell if its unstable? When I'm running in powersave governor, it shows that the 'system' process stopped responding at boot and I've the wait/close option, but after selecting wait the dialog disappears and the phone still works as per usual. However its very sluggish, clearly because of the underclock. Regardless, does the system process being unresponsive at the start shows it is unstable?
A: djlooka via PM
djlooka said:
...My suggestion is: try with that setvsel app for defy (see my answer in the CM9 thread) which comes with a useful mini-stress tester app (you can install it from within the main OC app). It can stress test every single freq step, so you can find its 'sweet-spot-vsel'.
One could also think that there's some advantage in fine tuning the middle steps. IMHO it's wasted time
After some days of tweaking, I realized that our phone will stay in the two the middle steps (combined) for less than 5% of the time. So even if you could save some % of the power by losing 1 or 2 vsel points (let's say 10% of the original vsel), the "on the road" gain would be infinitesimal (10% x 5% = 0.5%).
Anyway it's fine to OCD a bit even about those 2 steps
My final word is: find the lowest possible vsel for both the top and bottom freqs by stress testing. To be extra careful, raise them by one point for rock solid.
E.g.: 300-22 is the best combo for my lowest step -> I put 300-23, and so on.
Click to expand...
Click to collapse
::3 steps shown in the bootloader but 4 shown in MS2Toolbox::
Q: This has been bugging me recently. I've read recently that the M2 has 4 steps for its CPU. So the CPU actually follows the 4 steps shown in MS2Toolbox or the 3 in the bootloader? Note: When I change the values in the bootloader, the values changes respectively in MS2Toolbox for the 2nd,3rd,4th rows (did not tick auto apply in M2T to prevent overlaps with bootloader settings). But the 1st row shows values lower than the one in the 2nd row automatically.
A: djlooka @ http://forum.xda-developers.com/showpost.php?p=29806494&postcount=908
djlooka said:
...Our phone, instead has 4 steps (300, 600, 800, 1000 MHz - the same as the Defy+).
AFAIK, when you set a configuration which allows only 3 steps (in the bootmenu), the hw internally adjusts to have the last 2 steps equal (e.g. 300, 600, 800, 800 MHz).....
Click to expand...
Click to collapse
Applications
MX Player - Does not require codecs. If it requests for ARMv7 NEON codec, get the NEON version of the player instead.
Hello guys,
I did something stupid.
Couple of days ago I decided that I am sick with this constant freezes of the GSM module on my defy. The core problem was that sometimes when the GSM radio is making rach-reselect of the current cell, and I am making/receiving a call in this exact moment, the Phone process is freezing. If I kill it and then kill the rild, the signal bar is empty, and my phone is declared as switched off to everyone who gives me a call. I am also unable to make outgoing calls.
Anyway long story short. I was running Froyo kernel with CM7 ontop on Defy (Red Lense). The hardware is MBM525.
Decided to give a chance to CM11 by quarx2k. Made a full dd image of all my eMMC partitions and followed the guide on quarx2k website. Flashed the bootstrap and the tried to resize, but nothing. I was just locked with frozen Google/CM7 logo.
Got into stock recovery, wiped data/cache partitions. Again I was locked with the logo.
No adb, no TWRP, no nothing. So I did flashed the original SBF with RSDLite, that my phone was comming with. Nothing, just black screen and white led. Looked here and there and found a ROM that will definately power up the device:
Code:
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
True. The Defy powered, and the red Moto logo showed up (flashing this SBF was not the smartest thing I've ever done for my phone, this SBF was for MBM526).
The Android GB started and I was happy. Red a bit further on the CM11 thread and it turned out that I was with incorrect kernel, and that is why I got issues flashing the bootstrap in the first place. Now I got the correct one, so I rooted the phone with this SBF:
Code:
DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
Installed SndRecovery and Custom recovery, got adb interface before android and flushed the bootstrap image to mmcblk (where /system is located). Installed the resize.zip. Rebooted, got into nice looking interface, flushed cm11 from a zip file to the newly repartiioned eMMC... etc.
Finished with CM11 Kitkat on my Defy. Wonderfull!!! Realy amazing.
However I've some issues with this version:
1) my battery is lasting less than 10hours, if I use my phone as usual (on froyo with cm7 the mileage was between 2 and 3 days, depending how many calls I made). If I have 2-3 calls for average of 15minutes (45min total GSM calls, no 3G etc), the battery life is less than 6 hours.
Tried to disable every fancy animation, downclock the CPU to 300MHz.. etc. No luck. I got around:
* 20 hours with no calls at all
* 8 hours with 5 calls, 3 minutes each.
and the Phone UI is not working correctly (the bug with the keypad not showing up).
I checked the reasons for this and with ssh did found that systemui is consuming a lot of CPU cycles.
Check with the battery applet, and com.android.systemui is taking around 40% of my battery time, Screen is 20%, AndroidOS 23%, Cell Standby 10%.
On CM7 it was something like Cell Standby 20%, Screen 40%.
Perhaps the problem is related with the fact that the battery is not charging to more than 4160V
2) The video playback using hardware decoder is not working correctly in my opinion. When I run a movie with MX player with h/w decoder the /system/bin/mediaserver is taking around 60%-80% of the CPU (same config - MX player with hw decoder, took around 5%-10% on CM7). If I go to S/W decoder, the CPU usage is the same but in favor of MX player process.
3) When I receive calls and the screen is in Landscape mode, I do not have the Phone UI where I can pick up the call. It simply does not show. There's two solutions:
* Wait 'till the end of the ringing, the person calling me hangup - I've missed call.
* Assign custom hardware key for pickin'up of incomming calls.
The second one is working, but I am unable to view who is calling me. Sometimes this is critical, since I am on a meetings and I should know who is calling me (I can ignore my coleagues, but not my boss).
I do use landscape alot. This is the only normal way for me to write on this small screen.
4) When I am starting outgoing call, It takes 2-4 seconds before the Phone UI shows up on screen. Tried various solutions. No luck.
5) Heavy RAM usage. With CM7 I got something like 200-250MB free ram, I was able to load more than 60tabs in Opera, and having FBreader loaded in Background. Now I've less than 94MB Free, and on Opera tab number 20, the app simply crashes. I know that this is not something that could be corrected. Android is a heavy OS, quite normal. Java is very heavy in terms of resources.
6) When I press and hold the Home button in order to display the recently opened applications, it is not showing right away. The lag is between 5 to 6 seconds. This means holding the home button for 3 seconds, releasing, waiting for another 6 seconds before the list shows up.
Apart from these, the UI is very responsive, and fast. I would say it is much faster than CM10 and CM9. The system is behaving wonderfull, realy nice. In some circumstances even better then CM7.
Right now on my questions:
What are the chances to go back to CM7 with GB kernel or Froyo kernel?
I know that I've flashed non-fixed SBF, which is BL7 (my bootloader version is 9.10), but I red that there's a CM7 runing with GB kernel. Where can I find this?
Is it possible to run CM7 on quarx2k kernel?
Is it possible to modify the bootstrap process so that it can run various kernel versions?
Perhaps too much talk for a single post
Phone:
SM-G900R7 (rooted) | SDK 21/Lollipop 5.0 stock
History:
Unintentionally nuked OS via TWRP's "Fix Permissions" (big no-no), then used "Advanced Wipe" when I shouldn't have (was desperate to get Xposed working). Eventually got everything back up with this ROM[1] (same build identifier as on the other GS5s purchased at the same time as mine/under the same plan as me). I had no such audio problems before with this phone, but ever since flashing back to stock, my audio experience is doomed to have its immersion broken by way of little split-second hitches, driving me bonkers with wanting to just know why, why, why. In a recent attempt to fix this problem, I did a backup through Titanium, then TWRP, then Advanced Wiped Dalvik/ART, System, Data, and Cache, but was too chicken to wipe "internal." Perhaps I should have wiped internal too? Dunno.
Behavior:
My audio will hitch for a split second randomly (sometimes five minutes apart, often a moment after turn my screen off, or in shorter 20/30-second intervals here and there, but nothing 100% reliable). Happens with any app. Stitcher. Recorder (playback). Text-to-Speech reader. Audible. Spotify. OGYouTube. VLC. Any audio will behave as described.
Questions:
I've been trying to correlate what the problem might be with OS Monitor (root enabled), looking at the system messages. I'll often see E LightSensor: Light old sensor_state 0, new sensor_state : 512 en : 1 and E/Zygote (26507) MountEmulatedStorage() appear in red (along with some others), but can't find useful reference to what these might mean (are there E/Blastocyst errors as well?). I'm just looking for aaany kind pointer or direction on what to look for, what to disregard, or how one should go about troubleshooting this surprisingly frustrating problem. Is OS Monitor what I should use? I don't even know if the error'd items in Red are even what's causing the problem. Could just be meaningless correlation, since correlation is all I've got right now.
Thanks for any suggestions...
[1] shipped-roms (dot) com/download.php?model=Galaxy%20S5&file=ACG-G900R7WWU3BOH1-20150921182030.zip (can't post external links, apparently, so this mess will have to suffice until I reach 10 posts)
Hello, I have a galaxy s5 that I am trying to fix for my grandfather because it fell. So far I have installed TWRP but all ROMS have the same issue. Inside TWRP the device works flawlessly: screen, vibrator, touch, buttons, everything. The problem is that whenever I boot into any ROM, after the first 15 seconds or so it freezes. The weird thing is that it works perfectly up until the freeze. So far no ROM has worked. I have done a full wipe of all partitions, even formatted the data. Any suggestions to fix this?
EDIT: I was able to try using crDroid which has adb enabled by default which allowed me to get a logcat. Something very interesting was that I tried swiping the app drawer up and down without ever letting go and it kept working the whole time. Exactly as soon as I let my finger go and stopped touching the screen it froze and gave this error. It happened exactly when I let go, but I'm not sure how I could fix it.
Code:
2018-09-25 17:41:34.325 423-655/system_process E/ActivityManager: Sending non-protected broadcast null from system uid 1000 pkg com.android.settings
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:19236)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:19836)
at com.android.server.am.ActivityManagerService.broadcastIntentInPackage(ActivityManagerService.java:20000)
at com.android.server.am.PendingIntentRecord.sendInner(PendingIntentRecord.java:357)
at com.android.server.am.PendingIntentRecord.sendWithResult(PendingIntentRecord.java:240)
at com.android.server.am.ActivityManagerService.sendIntentSender(ActivityManagerService.java:7814)
at android.app.PendingIntent.send(PendingIntent.java:874)
at com.android.server.AlarmManagerService$DeliveryTracker.deliverLocked(AlarmManagerService.java:3213)
at com.android.server.AlarmManagerService.deliverAlarmsLocked(AlarmManagerService.java:2611)
at com.android.server.AlarmManagerService$AlarmThread.run(AlarmManagerService.java:2734)
EDIT2: I'm pretty sure that it is related to CPU throttling and thermal control/manager from the logs. I am able to keep it going by continuous swiping which probably is because of the touch input boost. Using that I was able to set the mode under battery to performance to stop the extreme throttling and it worked fine until I was messing with CPU hotplug and thermal in Kernel Adiutor. When I enabled and disabled MDP decision I think.
EDIT3: Seems like its related to the CPU cores. After turning on performance mode which locks all cores to max speed it works just fine. Lowering it to quick or balanced will automatically freeze the phone. I was able to get the minimum frequency to 1245mhz and it still works but setting minimum to 1190 instantly freezes again.