Anyone else experienced this? Ever since I rooted the phone, the default mi file manager has been running at a low frame rate to the point where the lag is easily discrenible. Before rooting it ran smooth at 120fps.
This only happens with file manager, other apps run fine.
But now even after I completely reinstalled the original firmware (MIUI 12.0.3) and locked the bootloader the problem still persists. Totally baffling that it's still happening, even on a completely fresh firmware.
Is there any way fix for this?
Finally found the solution.
Go to developer options, scroll down to logger buffer sizes and set it to off. Done!
This was driving me crazy. It's strange how obscure the solution was.
Related
Hi team...
hit a problem with my evo.. and its frustrating the h$ll out of me..
Bluetooth is coming on "on boot"...
Running rooted stock Sence with plenty of programs in it..
As usual with things new.. tried a heap then yanked plenty out and now down to the basic's.. Running juice defender and Battery saver plus battery Indicator..
K.. as indicated bluetooth is turning itself on on boot and the only way I can turn it off is to go in to "Airplane mode.."
It seems to turn it off.. well it shows turned off...
Note: it wont turn off via a widget and or in the settings.. as when you hit that button it will "grey out" and show.. "turning off" but seems to hang in this mode..
I checked with Battery Indicator and it shows that bluetooth has been using 23% of the battery today... now thats a fair chunk in anyones terms.. considering how much effort we put in to extending the batts life..
O I do run with a extended batt..
ok.. to my way of thinking.. either I got a bug in the system and or its going like something in this thread from years ago on another pc of hardware...
http://forum.xda-developers.com/showthread.php?t=227706
K.. what I would love to do is freeze all bluetooth programs and triggers..
so... i kinda need a list to know which ones to freeze and work backwards from there.. (I got all the tools to do this and as said are "rooted")
Bluetooth.apk?
BrcmBluetoothservices.apk?
or.. is there a "hard" shut down I can do?
any help would be great and I am sure someone has had this problem before.. but at this stage over the last week.. Google it and going through threads has not yielded a fix as yet..
few specs on the software..
Firmware : 2.1 update 1
Baseband version : 2.15.00.07.99
Kernel: 2.6.29-789bf291
Build number: [email protected] test2 (really.. whats this?)
Software number: 1.47.706.1
PRL Version : 1.71_003
PRL version: 00202
Thanks in advance..
Did you ever resolve this issue? I'm now having this same exact issue.
fbazaldua said:
Did you ever resolve this issue? I'm now having this same exact issue.
Click to expand...
Click to collapse
No.. not yet..
As said I have to use the Airplane mode to shut it off... but it still shows up in Batt usage as draining .. so I say its not fully off..
I am wondering if it is a "radio" problem and or some pc of software is calling it on boot..?
anyone else get this problem?
You should be able to freeze both Bluetooth.apk, and BrcmBluetoothservices.apk. That'll stop it for sure, it can be done with titanium backup. Also you can try flashing the radio, and I also assume you have tried rebooting?
I have tried re-booting and it still comes on. I've turned off the phone completely and re-started and it still comes on upon booting up.
I rooted my phone a month ago without any problems. I also installed myn's Warm 2.2 (RLS5) without any problems. Nothing has changed since then. Then just last week my spouse noticed the bluetooth on her phone on boot up. Since yesterday this has also started to happen on my phone as well. All of a sudden this has started to happen on our phones for no apparent reason. Any help would be greatly appreciated.
Have you tried freezing the app in titanium backup?
No I haven't tried freezing the apks in Titanium Backup, but why should I? I want to find out what's causing this so that maybe it can be fixed instead of just turning it off.
Also, I'm already running the latest radios. I didn't have to "update" to the latest radios for myn's because I was already running the latest radios mentioned. Why would I need to re-flash the radios? Since November when we purchased our phones, and for the last month since rooting we've had absolutely no problems with our phones.
Are you running any programs like juice defender or anything? Because it is indeed off for bluetooth to start acting possessed.
No sir. I don't use Juice Defender, task killers, or any custom kernel. All the apks I have I've downloaded since rooting. Like I mentioned, nothing's changed. Just too weird and very frustrating.
Lawlz, no need for sir..., but have you tried re-flashing the rom lately?
No I have not tried re-flashing the ROM, but why would I if I haven't had any problems until now? What would have caused it to become "corrupted" or problematic so as to cause the bluetooth to come on during boot up?
If I can't find a solution within the next couple of days I guess I'll re-flash the myn's ROM. However, I prefer to find the solution to what's causing the problem. I just don't want to continue re-flashing radios, ROM, etc. every time this happens.
Well I don't know exactly what caused it, and it could just be a random bug. Though re-flashing can solve it, and it might not happen again.
If it helps, my signature is below with the setup I'm running. Maybe something isn't "compatible" and it's just manifesting itself now. Nevertheless, I will more than likely just re-flash the ROM if the problem persists. Thanks for your responses. I will update in a couple of days.
Well I was just about to go into Titanium Backup and turn off the bluetooth apks when I noticed it's not listing any of my apps under Backup/Restore!! I've gone to Menu > Setting > Applications > Manage Applications > Titanium Backup and I've cleared data and cache. Forced stopped it, uninstalled, and then re-booted. I then re-installed, downloaded BusyBox, and still my apps won't show up. I wonder if this is part of my problem with Bluetooth turning on at bootup, but now how do I fix TB?
I am having the same problem with mikfroyo 4.5 randomly now also . I went into titanium backup pro and froze the brc Bluetooth file and some Bluetooth widget but didn't see a .apk to freeze mine has used 18% ugh
I was able to fix the bluetooth not turning off problem by clearing data/cache/dalvik and then restoring to my latest backup before I started having problems. I am happy to report that this solved the problem for me without having to re-flash the ROM again. I don't know what might have messed up the bluetooth, but I'm glad it's fixed. I hope this works for anybody else having the same problem.
As for TB it was showing 0 elements in Backup/Restore. I went to Menu > Filters > Clear > Apply, and then closed TB. Next, I went to Astro > sdcard > Titanium Backup folder > Edit > Select All > Delete. After I deleted all the files in that folder I closed Astro and then went back to TB > Backup/Restore and all my apps were there again, even all the frozen ones. For safe measure I froze the bluetooth apps mentioned above, and then I proceeded to perform another batch backup of all my apps and data again.
Thanks for replies crew..i will play around with it the next few days and report back..its been frustrating me for months and as you can see by the time date on the first post i had thought i had something wrong with the phone..
Sent from my HTC evo
I have the d851 T-mobile variant with 3gb, and while I have no issues flashing whatever rom I want, none of them happen to be stable. Originally my phone would just turn off and I would have to perform a battery pull to bring it back. It could happen at anytime, while it's sitting on my desk without being touched, or just browsing facebook. I bit the bullet and installed the official OTA and rerooted the phone and tried a number of other roms. They still crash, however I have been presented with a crash manager that allows me to reboot with the volume key instead of having to do a battery pull. Even the touted Cloudy G3 rom crashes on me. Quite literally, the only rom that works is stock. I have been searching everywhere for an answer and my eyes are about to bleed. I have never seen anything like this...does anyone have any insight?
zidace said:
I have the d851 T-mobile variant with 3gb, and while I have no issues flashing whatever rom I want, none of them happen to be stable. Originally my phone would just turn off and I would have to perform a battery pull to bring it back. It could happen at anytime, while it's sitting on my desk without being touched, or just browsing facebook. I bit the bullet and installed the official OTA and rerooted the phone and tried a number of other roms. They still crash, however I have been presented with a crash manager that allows me to reboot with the volume key instead of having to do a battery pull. Even the touted Cloudy G3 rom crashes on me. Quite literally, the only rom that works is stock. I have been searching everywhere for an answer and my eyes are about to bleed. I have never seen anything like this...does anyone have any insight?
Click to expand...
Click to collapse
Well I recommend a clean TOT or KDZ flash. Hope this will fix your problem. Please do follow this post to flash TOT or KDZ http://forum.xda-developers.com/showthread.php?t=2785089 then flash any other rom. Thanks!
I have an issue that sometimes multitasking Overview doesn't work anymore. When I restart the phone it's back working. the phone itself keeps the applications in the background which I can see when I open them manually but just the overview is not working does anyone else have this issue? I experienced it with the latest stock version and freedom OS
I haven't experienced it yet.
It's really strange.installed cm (march-version) and recently had the same bug again. Was doing a complete wipe. I don't get it:-\
This problem was posted here http://forum.xda-developers.com/oneplus-3/help/recent-app-list-t3429410
I had it a couple of times and solved rebooting into recovery and then rebooting again into system normally.
Hi all, I have tried hard to figure out my camera issues but I'm just going to have to reach out and ask for help. I have wiped/factory rest etc, I have completely reflashed the OEM image, I have flashed twrp and currently am running carbon rom and have root access to try to figure the issue out. When I launch the camera app it launches normally but there is no image just a black screen. If I flip the camera to front facing, same issue and same issue with video. It crashes shortly after launching. I have tried different camera apps and have not had any luck. Is there a permission I need to fix or a file that's corrupt and needs fixed/replaced? I can't seem to find anything about my specific problem. Seems most are third party app issues. Oh, speaking of which, the results are the same in safe mode. Sorry if this is not the right forum, hopefully I'm asking in the right place.
If the black screen occurs in both the stock ROM and custom ROM, then yours is a hardware issue. Otherwise, the custom ROM is the likely culprit.
EDIT: Apparently this was a result of using the wrong setting for enabling hotspot in PropsConfig. Because all that stuff was set during bootup, deleting apps wouldn't change the situation. Setting worked fine on my Pixel XL, but not here. Changed the setting and all is well.
--------------------------
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Might be quicker and easier to back up your required files and just factory reset.
Texan1 said:
Might be quicker and easier to back up your required files and just factory reset.
Click to expand...
Click to collapse
*sigh* I kinda made this post to avoid that step.
somethingsomethingroot said:
*sigh* I kinda made this post to avoid that step.
Click to expand...
Click to collapse
I know, it's just that it sounds like you've already disabled some things that could be causing it, which hasn't helped. If it was me, with something like constant reboots, I'd want to start fresh just to make sure they are eliminated for good
somethingsomethingroot said:
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Click to expand...
Click to collapse
I've seen reports of "random" (=not intentional) reboots after
+ booting up the phone
+ using the FP scanner
+ making videos or shooting photo
+ doing a firmware update (I've seen both reports of ppl that "officially" OTAed & used manual flashing)
+ doing nothing
+ doing something
Some were able to fix their issues by factory resetting, some needed replacement devices. Some reported that even after a factory reset, the issue still persisted, but they were able to fix it by NOT using a backup via cable, some reported that even the Google Drive backup "corrupted" their phone (fix after setting up everything by hand from scratch). Some even reported their issues to get fixed via a software update.
So it seems to be connected to hardware (= replacement device) and/or software simultaneously (=fix via reset).
Strange this is since there are also numerous reports of Samsung owners that upgraded to A12 about random reboots. So it might even be something Android 12 related, or it's just Samsung also implementing similar bugs without it being A12 related (unlikely, since the reports seem to be centered around people using the new A12 update).
I also had the random reboot problem (~ 6 times a day, when doing nothing, it just rebooted when the phone layed on the table in idle). I wasn't able to fix it via a reset, so I got a replacement device.
I also have the "random" reboot problem on my Pixel 3 since upgrading to Android 12 (never had any issues all the years I've been using that phone), so that issue is clearly caused by A12, but I haven't troubleshot it/ tried to solve it, since I don't actively use the phone currently.
Aside from trying a factory reset and minding the backup issue (especially backups that you got from phones that did NOT have Android 12), there is not much more that you can do (ofc you could also use the Pixel repair/android flash tool to do a "clean" install of Android on your phone). Next step would be to contact Google.