mainboard hardware problem reboot / kernel settings solutions? - Xperia Z5 Compact Q&A, Help & Troubleshooting

Hi, I have bought (for a reasonably low price off course) a second hand no warranty E5823 with a defect.. Rebooting.
I thought maybe reinstalling flashing a Rom might solve it, but it appears to be a motherboard problem (I have had battery and display from my other z5c I was working on tested with this motherboard, but same problem)
I have tried flashing lineage os 14.1 and stock roms, now on nougat .378 rooted.
Beside that now the Wi-Fi had low range, everything works, but the reboot error stays.
Sometimes it stays on for a while but then I touch the screen and it freezes and reboots.
Yesterday, it kept rebooting very often, I did adb logcat from Windows (not that I know what to do with these logcats) but it seems when I run adb logcat it won't reboot ....
And so it was rebooting almost immediately, several times in a row, but with adb logcat via USB it just stayed on... No reboot.
So I am wondering, why can I install roms flash with Fastboot or flashtool or twrp without problem, and not just keep a installed Rom running.
My thoughts are, maybe something is wrong with a cpu , GPU, or some other sensor.
Had done a burn in test a few weeks ago that went on for hours with no problem..
Now at this time I installed kernel adiutor, and just change a lot of settings and set on boot, change like heat detection(but back to standard now), delay between shifting cpu speeds etc.
Not max GPU and not min gpu , well, now it does sit on max GPU but min 305.
GPU governor to performance
Changed cpu hotplug to down 18 up 85
Offline delay 500ms
Memory settings (aggressive)
Read ahead a bit more than standard
Etc
I just changed a bunch of things just to try, because I don't know what causes the reboot, and at flash or (adb logcat) or twrp there seems to be settings "possible" that it can work without rebooting
So it looks like at this time with my settings changed and saved for reboot at kernel adiutor, I have a way to keep the phone on.... And still working fine.
Are there any ideas what can be done to find out what really causes the hardware error, that in e.g. Kernel adiutor I can just focus on that part?
And are there better apps than kernel adiutor, as it seems that it won't really listen to or save my commands of the min max big and little cpu's.
(I am now using the stock kernel rooted with rootkernel23 with all options checked on )
I hope someone has a bright idea for me, or maybe someone else with the same problem with a phone outside warranty can keep it working with a partly defective mainboard .... (Because buying a mainboard is too expensive in my opinion/case)
(And of course when I flashed it was complete wipe etc. Different roms from the oldest to the newest. Same problem)

Hi, I have the same issue. I've tried everything, from repairing it with xperia companion to installing very few apps, and I still have some reboots.
Have you had any new reboots? And if you haven't, Could you please list in detail which where the changes that fixed your reboots? I know that is not a definitive fix, but it would be really helpful
Thanks a million

Related

Phone randomly freezes, requiring hard reboot

For a while now, my phone has randomly been freezing, becoming completely unresponsive and requiring either a battery pull or a reboot by holding down the power button. It began a couple months ago while running Task's AOKP ICS with ktoonsez's Fluxi XX kernel. The odd thing is that the phone was stable (ie. no freezes) for the first few months under that setup before it started happening once every few days.
When the frequency of freezes went up to about once a day, I did a full wipe (formatted data and system, cleared cache and dalvik) and flashed Slimbean 2.7 with stock kernel, thinking that maybe something had gotten corrupt in my previous setup. That didn't fix anything, so I flashed ktoonsez's Siyah kernel to see if anything would change. Nothing did, so I kept with that setup (currently on Slim 2.9, Siyah 4.3.3).
The freezing is now occurring anywhere between 1-3 times a day, and I can't for the life of me figure out what is causing it. Sometimes it occurs after interacting with the screen, other times it happens while it's charging and the screen is off. Most recently it occurred around a minute after I changed a volume setting and was in the middle of a Scramble with Friends game.
I pulled the last_kmsg (attached) after rebooting the device; I don't know how to go about recording a logcat due to the random timing of freezing. I also don't know how to interpret the last_kmsg, which is what brings me here.
I did take a perfunctory glance at the file and noticed that the log doesn't seem to be very "clean", in the sense that the output is garbled in several places with random capitalizations and incorrect characters (ex. instead of "ignore request by suspending" on line 30 it reads "ignore bequect bY Suspe&ding"). I don't know if this is indicative of anything, and if it is I would be very curious to know what.
Anyways, if anyone has the time to spare to help me look through this to try to find the cause of my problem, I would be very grateful. Thank you in advance.
nitox.n2o said:
For a while now, my phone has randomly been freezing, becoming completely unresponsive and requiring either a battery pull or a reboot by holding down the power button. It began a couple months ago while running Task's AOKP ICS with ktoonsez's Fluxi XX kernel. The odd thing is that the phone was stable (ie. no freezes) for the first few months under that setup before it started happening once every few days.
When the frequency of freezes went up to about once a day, I did a full wipe (formatted data and system, cleared cache and dalvik) and flashed Slimbean 2.7 with stock kernel, thinking that maybe something had gotten corrupt in my previous setup. That didn't fix anything, so I flashed ktoonsez's Siyah kernel to see if anything would change. Nothing did, so I kept with that setup (currently on Slim 2.9, Siyah 4.3.3).
The freezing is now occurring anywhere between 1-3 times a day, and I can't for the life of me figure out what is causing it. Sometimes it occurs after interacting with the screen, other times it happens while it's charging and the screen is off. Most recently it occurred around a minute after I changed a volume setting and was in the middle of a Scramble with Friends game.
I pulled the last_kmsg (attached) after rebooting the device; I don't know how to go about recording a logcat due to the random timing of freezing. I also don't know how to interpret the last_kmsg, which is what brings me here.
I did take a perfunctory glance at the file and noticed that the log doesn't seem to be very "clean", in the sense that the output is garbled in several places with random capitalizations and incorrect characters (ex. instead of "ignore request by suspending" on line 30 it reads "ignore bequect bY Suspe&ding"). I don't know if this is indicative of anything, and if it is I would be very curious to know what.
Anyways, if anyone has the time to spare to help me look through this to try to find the cause of my problem, I would be very grateful. Thank you in advance.
Click to expand...
Click to collapse
Do you have stock kernel settings? I know underclocking GPU can do that
Sent from my GS4 running CM11 Kandy Kane
I tried to keep all stock settings for the purposes of trying to whittle down the list of possible causes, but I did change the following in ExTweaks:
CPU Step Count: 15 -> 6
Load_H0, Load_L1: 25%, 25% (I think originally was 30%, 23% or something)
Mali Touch Boost level: Step3 -> Disabled
Disabled I/O-Tweaks in Cortexbrain
nitox.n2o said:
I tried to keep all stock settings for the purposes of trying to whittle down the list of possible causes, but I did change the following in ExTweaks:
CPU Step Count: 15 -> 6
Load_H0, Load_L1: 25%, 25% (I think originally was 30%, 23% or something)
Mali Touch Boost level: Step3 -> Disabled
Disabled I/O-Tweaks in Cortexbrain
Click to expand...
Click to collapse
Keep it stock then try
Sent from my GS4 running CM11 Kandy Kane
I should have mentioned that I made these changes a few days after flashing Siyah. During the time that it was stock, freezing still occurred.
My suspicion is that there is some sort of hardware malfunction causing this to happen, considering that it has occurred across both ICS and JB platforms running on different kernels. I would actually be mildly surprised if it is due to ROM or kernel. Still hoping an interpretation of the last_kmsg will reveal more information about this.
nitox.n2o said:
My suspicion is that there is some sort of hardware malfunction causing this to happen, considering that it has occurred across both ICS and JB platforms running on different kernels. I would actually be mildly surprised if it is due to ROM or kernel. Still hoping an interpretation of the last_kmsg will reveal more information about this.
Click to expand...
Click to collapse
Flash stock and factory reset within the ROM after booting up with stock. Just make sure you backup you SDCARD to your PC as it will format your SDCARD. Go from there and see if it happens stock.

[Q] [Question] Problems with CM10?

Hi everyone, if I had the chance to post this problem on the original FXP CM10' post I'm pretty sure I wouldn't be posting this right here, butttttttt....XDa doesn't allow me to reply that original post so I guess I have to post here a few time so I can go to the original post (Lemme know if I'm wrong of what I think about this of posting in Developer's section)
How I was saying, I just installed FXP 149, MB66 Extended ROM and I modified some brightness values (attenuate value from 20 (default) to 10), cus brightness was very high and I was trying to test if I can save some battery. Anyway the main problem came after when my device (Xperia Mini Pro) was USB conected to my PC cus I was transfering some music and I was charging in the meanwhile. The screen turned off after a min (like I confugured it) and then when I tried to turn it on pressing Home button it never turned on, NEVER. I had to remove battery to try restarting it and see if it was a random problem, but nothing happened; the device seeme dto start normally and then when the bootanimation ended it went black again but responding to my attempts to unluck it! Like if the device was runnning normally but with the scren turned off! Real weird stuff. Then I tried rebooting a few times more, nothing happened, tried to resintall ROM; again nothing happened. Then I tried wiping everything (factory reset, caché partition, dalvik caché) and then it turn on again and it booted normally. Now i'm trying to set the attenuate value from 20 to 12 to see if that was the problem or it was a random case of malfunction of undervolt... (cus the ROm is undervolted or the kernel, one of both. The thing is that there is undervolt to extend battery life).
Well, hope I get some support or opinnions or I don´t know
I'm newbie so please be patient with me See you!
problem with attenuate from 20 to 12 persists...only did full wipe and it's back running normally. I won't touch attenuate values again...hope it runs normally from now on

i9300 lock up problems - seemingly at random

Hey guys,
I'm hoping somebody here might have an idea for where I can start to look for this problem, I have had the SGS3 for around a year now, I put CM10 on it initially (from memory), upgraded to CM10.1 when that was released via the nightly releases and I have been running those since.
Recently I updated from a Feb / early March release (cant recall specifically which one) to the next latest (mid to late March I believe) to move from 4.2.1 to 4.2.2. I believe a little after that ( if not that day) I began to very occasionally have small lock up problems with the phone. It would lag out for a short amount of time, or would just completely lock up on the screen its on for a while (if I leave it, it can be between 30 minutes to an hour before it becomes responsive again)
Often I would need to use it so I just end up having to hold the power button in to force a reboot to clear it.
Initially I thought "ok just a bug in a nightly, that's cool, it'll be patched out soon enough", a few days later a nightly came down that fixed a notification bar drop down loop problem I was getting but this other thing has stuck around, depending on how my phone feels its occurring a lot or a little each day, generally seconds / a minute after I start to use it.
I have since jumped around on a few more CM10.1 roms and I have even reverted to the 4.2.1 roms I was using ( I still have them on the phone so I know they are the right ones) to test if its that, but now they are encountering this problem as well.
The phone is completely clear now of user data, I have done a full data clear via CWM and even the original Google "welcome" setup section has locked up more than once in my attempts to set the initial configuration of the phone....
Any thoughts? CWM etc has never had a problem so while it seems to lean toward hardware i'm still thinking its software, maybe a CM10.1 release has updated something else in the phone that's now causing problems, something more firmware related etc?
EDIT: to give some examples, just before I readded my exchange details and started to sync contacts etc, I went into contacts, opened the menu and selected "Settings" to change the first name last name sorting and it just stopped on the settings button, settings was still lit up etc but it was not responsive.
Just now (about 30 minutes later) I have pressed to turn the screen on and its on the lockscreen. Great its back I think, i'll grab the baseband / kernel etc to put in here, I slide it to the unlock and bam, frozen on that now.
more info
I had a play this morning and activated the CPU overlay etc as well as strict mode.
The phone has just done it again in the play store, however the CPU overlay shows nothing out of the ordinary and there was no screen flash to indicate a long run causing a problem.
Interestingly the cursor in the search bar for google play is still blinking, so the phone is still "alive" however i cant control it via the touchscreen or the hardware buttons.
I am trying to dump the log via ADB now however its gotten as far as finding the phone and seems to have stopped (though maybe its still going, i'll see soon hopefully)
Anybody got any ideas? This is driving me crazy and i'm not sure where to go with it now, i guess back to stock is the next option then maybe a warranty claim if thats still possible....
Log collected
Either it was still collecting or it collected after the last event in the log but i've uploaded the log to pastebin here:
http://pastebin.com/Cc20CYZH
The main thing seems to be this:
Code:
W/SQLiteConnectionPool( 6385): Requests in progress:
W/SQLiteConnectionPool( 6385): execute started 646409ms ago - running, sql="COMMIT;"
W/SQLiteConnectionPool( 6385): The connection pool for database '/data/data/com.android.email/databases/EmailProvider.db' has been unable to grant a connection to thread 237 (AsyncTask #2) with flags 0x1 for 646.44104 seconds.
W/SQLiteConnectionPool( 6385): Connections: 1 active, 0 idle, 0 available.
And also this:
Code:
W/InputEventReceiver( 3327): Attempted to finish an input event but the input event receiver has already been disposed.
FYI - that bit at the bottom of the paste about the screen turning off with timeout, the screen has now turned off but i still cant turn it back on etc, soon enough it'll probably reboot (which seems to be what it ends up doing) then it'll be ok again until a problem occurs again.
I'm currently trying a new baseband as recommended here:
http://forum.xda-developers.com/showthread.php?t=2133401
Will post the results after a few days, fingers crossed.
Did you had the same problem on any other aosp or aokp based roms?
Or just try flashing the stock rom
BHARGAV33 said:
Did you had the same problem on any other aosp or aokp based roms?
Or just try flashing the stock rom
Click to expand...
Click to collapse
I actually never ended up changing back, i flashed the new baseband as above, ran the dumm file generator app a few times (letting it lock up as it went), flashed a new rom a few times as well and after all of that it seems to have worked out all the bad sectors.
Definitely seemed like I was a victim of the beginning of the SDS problem, all due to the fact i had flashed this almost immediately after receiving it and had never updated the baseband.
For those with lock up problems, go to http://forum.xda-developers.com/showthread.php?t=2133401 and follow that for installing the baseband, then do the dummy file generator etc, i'm back to a phone that works properly
PS - It took a few weeks after for it to find and remove all the problems, remember your actual ROM install could be written to bad sectors so i would definitely recommend after you run the dummy file generator a few times to update your ROM at least once, it was after 2-3 updates mine had completely settled down.
PPS - If the dummy file gen fills up your storage then crashes, just go to app info (drag from launcher is the easiest way to get here) and clear the data, that'll delete all the dummy data
PPPS - The dummy file gen can make your phone run terribly as it gets close to full, be patient, its not necessarily the lock up problem but even if it is you need to let it sort it out itself, restarting will make it worse not better.

[XP][HELP] Phone restarts very often

Hiyas, I think I need some help with fixing my phone to functionalo state.
It started to restart very often (without user interaction and freshly booted).5 to 10 minute intervals approximately. I can't say exactly what might be wrong the phone doesnot otherwise expose any kind of visual problems (poor performance, apps crashing or nonfunctionality).
Is there any common diagnostics for that situation...to get known what's wrong and remove the culprit. Certainly this can be hw fault also (the worst variant).
The phone uses stock ICS, custom kernel, UBL, rooted.//also in the past I encounter freezes and reboots occassionally but not so often as during last two days. May this be a poorly written application? In most recent time I only installed two new apps (Solo Launcher not default and XPrivacy)
bflmpsvz said:
Hiyas, I think I need some help with fixing my phone to functionalo state.
It started to restart very often (without user interaction and freshly booted).5 to 10 minute intervals approximately. I can't say exactly what might be wrong the phone doesnot otherwise expose any kind of visual problems (poor performance, apps crashing or nonfunctionality).
Is there any common diagnostics for that situation...to get known what's wrong and remove the culprit. Certainly this can be hw fault also (the worst variant).
The phone uses stock ICS, custom kernel, UBL, rooted.//also in the past I encounter freezes and reboots occassionally but not so often as during last two days. May this be a poorly written application? In most recent time I only installed two new apps (Solo Launcher not default and XPrivacy)
Click to expand...
Click to collapse
i have this problem with custom kernel A.1.100 FW Release by @DeathZeroFx
No this is not custom kernel but stock. However it is happening too. Today the phone lasted whole day without a restart however at morning it had restarted about 6 or 7 times in a row, being on charger. This points like the restarts happen under some circumstances only.
Sent from LT22i using Tapatalk 2

Phone keeps freezing at random

Okay, so, I'm using CM 11 M12 on my Galaxy S3 and recently I decided to be a daredevil (like an idiot) and flash Boeffla Kernel on my phone. I flashed it and messed around with some settings, I'll post what settings I changed to what.
CPU: zzmove governor, profile - optimal. Set the max CPU frequency to 1200 MHz.
Enabled zRam, set it to 4 partitions at 800 MB each with swappiness set to 95.
Enabled Boeffla tweaks.
After that, I noticed that the phone would sometimes freeze for a short period of time, which was okay at first, but then the freezes got more annoying so I decided to restore my nandroid backup and use my stock kernel. Well, that didn't fix my problem, in fact, it made them even worse.
My phone now freezes randomly while doing anything (browsing, playing games, opening apps, etc) for 30 seconds to a minute. And during that time period, the phone is pretty much frozen. Can't turn off the screen, can't toggle anything, I can only restart it by holding the power button for 10 seconds after which the phone still continues its weird behavior.
There are some odd things I noticed though:
1. I cannot transfer files to my phone using a USB cable. It stops at about 1/3 of the progress and the phone freezes (can't power up the screen, open apps, etc). I can only reboot it and stop the file transfer process. However, transfering files to my SD Card works, albeit it very, very slowly.
2. At first, the currently open app freezes but not other parts of the system. Let's say I'm using Chrome, i'm browsing and then Chrome freezes. I can still open the notification bar or the power menu, but the app itself doesn't respond anymore. After a few more seconds, the entire system goes unresponsive.
3. Restoring and making backups takes extremely long (using TWRP 2.8.5.0). While restoring a backup, the process sometimes stops for half a minute and then continue which leads me to believe that the CPU is under heavy load all the time.
4. During the freezes, the phone won't reboot itself automatically, but certain aspects of the phone will crash with an error message (like the Settings menu, lockscreen, the wallpaper will change to the default one, etc)
I also tried doing a complete wipe (data, dalvik and cache) and booting up CM 11 again. Right after I selected the language in the "Welcome" screen, the phone went unresponsive and very sluggish. Animations would freeze, get stuck and it was impossible to continue. I decided to restart the phone again by holding the power button after which I got into a bootloop. The only thing I could do is restore my nandroid backup again.
Does anyone know what the problem could be? Do I need to delete certain kernel files left over from Boeffla kernel? Is it a hardware problem? I seriously hope that this is something that can be solved by wiping data (i'm even willing to wipe /data/media) or by deleting certain system files.
Thanks in advance and sorry if this post is in the wrong forum or if it doesn't follow certain guidelines set by XDA.
Emmc nand damage caused by messing with partition, try reading the freezing thread in general forum.
There is no cure, only a partial workaround to teach the operating system to avoid the damaged areas.

Categories

Resources