I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
I have the same problem with craching and rebooting on both Tab2`s in the house.
One completly stock and one with CM11.
Mabye an faulty app ?
Steveh8204 said:
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
Click to expand...
Click to collapse
Well, it is happening with everyone, the apps have become memory hungry and our devices lack RAM, andoid L, and our device kernel is full of bloatwares, our devs are trying very hard to overcome this, and we hope they will succeed in this too.
many people are of the view that android M has better management of ram, and I have seen in other devices that have confirmed they are experiencing better stability than lollipop. well on our device it's still in alpha stage, so wait and watch. till then keep your tab less burdened.
Steveh8204 said:
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
Click to expand...
Click to collapse
Try changing SElinux to enforcing.
It helped me in my P3110.
HIT THE THANKS BUTTON IF I HELPED YOU
Zte blade l said:
Try changing SElinux to enforcing.
It helped me in my P3110.
HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Hi, thanks for the reply but how the hell do you do that lol
Sent from my GT-P5110 using Tapatalk
Steveh8204 said:
Hi, thanks for the reply but how the hell do you do that lol
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
No need for that, just follow the original thread, bugs have been squashed. There are no more random reboots on latest builds.
Related
Ok so it is like this:
I bought my galaxy r here in sweden 1 year and 3 months ago, it was working perfectly for around 1 year.
At the one year mark i started to have some problems with the touchscreen where the phone would feel a pressure in the middle of the screen, to get rid of this i simply locked and unlocked the phone or rubbed a bit with a cloth on the screen.
Recently when I saw there was a cm10.1 rom with nightlies I rooted my phone and later installed the cm10.1 rom. Now the most anoying thing. I have a problem with my battery where the phone just shuts down randomly (mostly when playing games) even though it sometimes have up too 80% battery remaining. Then when I restart the phone it usually have 0% battery left and therefore shuts itself down again, sometimes it restarts with just a 20-30% batteryloss. This have occured more often recently and it shuts itself of 3-4 times a day. I can't remember if it was like this when i was on stock, before I started to flash and root, but i think it was.
A few days ago i flashed stock ics from odin and I confirmed that both of these problems still were there, so i have hard to belive that it is the modding of the software that have caused this.
Do you guys have any suggestions to how i can be able to use my phone normally again?
Im just a poor student so i don't want to waste money on a new phone after just 1 year :/
wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta
Will this help with the battery?
kataria.vikesh said:
wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Will this help the crashing/battery?
DippN said:
Will this help the crashing/battery?
Click to expand...
Click to collapse
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.
kataria.vikesh said:
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.
Click to expand...
Click to collapse
Nope, im not takeing backup of anything.
And one other thing i forgot to mention earlier, the phone now also thinks it is charging itself evrn when it is not. It think the usb cable is still connected.
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.
DippN said:
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.
Click to expand...
Click to collapse
paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Both of you install CM10.1 using Procedure no 2 from OP.
kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Will try that when i get home, thx.
kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.
paKS7 said:
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.
Click to expand...
Click to collapse
Sadly, I can confirm that this did not change anything.
The problems are still there :/
DippN said:
Sadly, I can confirm that this did not change anything.
The problems are still there :/
Click to expand...
Click to collapse
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?
DippN said:
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?
Click to expand...
Click to collapse
May be hardware or software too..when you will vanish all data & cache then Software issue may be gone but if problem still persist, means you have hardware problem.
Also, root will be lost after flashing Stock ROM from ODIN.
I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!
paKS7 said:
I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!
Click to expand...
Click to collapse
Well, we are not on the same baseband. I'm on I9103XXLQ3.
About the cm verison im not quiet sure, the latest i flashed was "20130406" but since the problem were there the time before that when i flashed cm I cant answer exacly but i have a cm version "20130305" on my desktop and it could be that one that I used.
I never used cm before it was on nightlies so the modem file flashing i dont know anything about.
The thing you mention about that it shuts of when the phone gets busy and touchscreen gets unresponsive I can kind of confirm too.
I will flash GB now, will report back in an hour how it went.
kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.
DippN said:
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.
Click to expand...
Click to collapse
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?
DippN said:
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?
Click to expand...
Click to collapse
Wipe data again.. If possible after wiping data Just reflash the GB.
Does anyone have a problem with random "pauses" while using apps? It's totally not noticeable for applications that aren't continually running animations (ie: kindle, text scrolling) but becomes evident when doing thins such as:
- recording video (the "pause" will cause the recording to stop randomly for both continuous and time lapse)
- playing games (will cause the game to go to the pause screen)
- tasker programming (I think this is affected because tasker will randomly close itself without a FC dialog, profiles and tasks seem okay)
I turned on debugging to see if it was a dirty screen or anything, but the touch coordinates don't change at all when the "pause" happens. Anyone have an idea how I can fix this? It is rather crippling to the N5.
I am rooted and I have seen this problem on all roms (and I believe I noticed it on stock too...)
I use a ballistic case, if anyone else has had problems with it...
Thanks in advance!
Using N5 on Carbon + Franco kernel
I guess no one's ever had this problem before? =[
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
mistahseller said:
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Click to expand...
Click to collapse
I've tried out a few roms (factory reseting and cache clearing between each one) to see if it was any one problem, but whether AOSP or CM based, I still have the problem =/
Bruce Lee said:
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do you mean stock + unrooting? I think I remember having the problem back then, but I don't quite remember before I rooted...I'll try going back to stock w/ root first and see if it's still happening. Thanks!
Do you mean stock + unrooting? I think I remember having the problem back then, but I don't quite remember before I rooted...I'll try going back to stock w/ root first and see if it's still happening. Thanks!
Click to expand...
Click to collapse
Yes follow the link in the general to go back to complete stock and that will eliminate anything and everything that could be an issue related to software.
For what it is worth, what method did you use to root?
mistahseller said:
Yes follow the link in the general to go back to complete stock and that will eliminate anything and everything that could be an issue related to software.
For what it is worth, what method did you use to root?
Click to expand...
Click to collapse
I used the Chainfire's autoroot (http://forum.xda-developers.com/showthread.php?t=2507211) on Windows.
mistahseller said:
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Click to expand...
Click to collapse
Bruce Lee said:
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm, I think it worked. I haven't tested it out for lengthy periods of time but I haven't noticed any pausing anymore! =]
I followed the unroot instructions to return to stock. Although I didn't relock the bootloader.
Then I booted up stock and it seemed like it works fine.
I reinstalled CWM recovery through adb (same as I did the first time) and proceeded to reflash
It seems like the problem is gone now on custom ROM as well. Interestingly enough, if I nandroid restore my old backup, I do get the problem again.
Is there something different between reflashing stock part and wiping from factory/data reset + system partition format + wipe cache + wipe davalik?
Thanks for your help guys! I was sure before that it was hardware since I had the problem on stock w/ root, but thankfully it's not a hardware problem! =]
Hello I have a Galaxy S7 and since the update to Android Nougat 7.0, my phone restarts randomly, it can stay an entire week without restart and it can also restart 2 days in a row. It's totally random. I have reset to the factory settings and I have reinstalled only the most important applications (facebook messenger, viber, yahoo mail) but unfortunately about ten days after reset, the problem has reappeared. What could be the cause of this problem? For info, the firmware version installed on my phone is: G930FXXU1DQBO. Also, I saw on SamMobile that the countries that received the update later, had a new version. Could the problem come from that? Is this a bug in the firmware installed on my Galaxy S7. Thank you in advance for your help.
Have the same problem, I'm on G935FXXU1DQB1.
Sent from my SM-G935F using Tapatalk
Vichenec said:
Have the same problem, I'm on G935FXXU1DQB1.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply Do you reset your phone too? And what is the average frequency of restarts?
Didn't do anything as it doesn't bother me that much.
Sent from my SM-G935F using Tapatalk
Vichenec said:
Didn't do anything as it doesn't bother me that much.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
It is still binding Once I had this problem while I was on call!
I have a thread about this, it was unusual for me too, theese random reboots.
After the third reinstall, (first one everyday rebooting, second one reinstall marshmallow, upgrade to nougat, happened the same reboots, I made again a factory reset and now no reboots and way better battery life) everything is ok for now.
hekermeker said:
I have a thread about this, it was unusual for me too, theese random reboots.
After the third reinstall, (first one everyday rebooting, second one reinstall marshmallow, upgrade to nougat, happened the same reboots, I made again a factory reset and now no reboots and way better battery life) everything is ok for now.
Click to expand...
Click to collapse
Thank you for your reply I received the update in OTA. To reinstall I have to go through Odin? I can not simply reinstall the current firmware (Nougat) via Smart Swith for PC?
I have the same issue guys even if did an hard reset after nougat update. I experienced some reboots after the update (1 March) but very often in these last days. I enabled the pin code for the sim in this way we can see if it happens when don't "monitor" the phone.
I was getting random reboots at one point due to a kernel panic (something to do with Samsung's zswap implementation). It hasn't been happening for a while though. I think they probably fixed it in newer versions. I'm on DQCF currently.
rikiko1g said:
I have the same issue guys even if did an hard reset after nougat update. I experienced some reboots after the update (1 March) but very often in these last days. I enabled the pin code for the sim in this way we can see if it happens when don't "monitor" the phone.
Click to expand...
Click to collapse
I think this is a software bug. Hopefully Samsung will quickly realize and deploy a corrective update. For my part, I reported this problem by sending an error report via the application "Samsung Members".
CurtisMJ said:
I was getting random reboots at one point due to a kernel panic (something to do with Samsung's zswap implementation). It hasn't been happening for a while though. I think they probably fixed it in newer versions. I'm on DQCF currently.
Click to expand...
Click to collapse
I'm on DQBO, this may be why I still have this problem. Did you directly receive Android Nougant in DQCF or was it a patch update?
GeekTN said:
I'm on DQBO, this may be why I still have this problem. Did you directly receive Android Nougant in DQCF or was it a patch update?
Click to expand...
Click to collapse
Flashed full image from SamMobile and setup from scratch. I'm too impatient to wait for patches
having random freeze / reboot on a g930fd (dual sim) as well , since a few weeks
flashed several times, factory reseted several times, root or no-root ....
no solution ...
basile said:
having random freeze / reboot on a g930fd (dual sim) as well , since a few weeks
flashed several times, factory reseted several times, root or no-root ....
no solution ...
Click to expand...
Click to collapse
This may be a software bug. What is your firmware version?
build NRD90M G930FXXU1DQB7 is the latest rom
with the latest samsung security update
meanwhile I left root aside, as I noted a strange thing while working under twrp that being 'unable to mount' /data map
problem occurs after filling up the memory (yes a 32gb version) and making more and more apps working (under root)
so, considering the above, might it be a physical ram problem ?
reading searching the net I noticed that many people are having this problem
basile said:
build NRD90M G930FXXU1DQB7 is the latest rom
with the latest samsung security update
meanwhile I left root aside, as I noted a strange thing while working under twrp that being 'unable to mount' /data map
problem occurs after filling up the memory (yes a 32gb version) and making more and more apps working (under root)
so, considering the above, might it be a physical ram problem ?
reading searching the net I noticed that many people are having this problem
Click to expand...
Click to collapse
No, I do not think that's what caused the problem. If the problem appeared after the Andoid Nougat update, it is that it is a software bug. I have a Galaxy S7 duos (SM-G930FD) me too and my firmware version is the G930FXXU1DQBO and I also have a problem of random restarts that persists even after a factory reset. Apperently the latest firmwares do not have this problem. It is necessary to wait for the next corrective update. Otherwise, what is the frequency of the random reboots of your phone? My phone is once a week.
there is no linearity ... can happen once a day, a week or several times in one day
sometimes it completely gets stuck and I have to wait for the battery to fully discharge before being able to reboot to a working phone ...
basile said:
there is no linearity ... can happen once a day, a week or several times in one day
sometimes it completely gets stuck and I have to wait for the battery to fully discharge before being able to reboot to a working phone ...
Click to expand...
Click to collapse
Have you tried restarting your phone in secure mode to see if the problem is from an application that you have installed?
Same here, I though that was Fleksy that sometimes load the phone and I had to shut it down manually (Power button + volume - for 7 sec) for a restart. Sometimes it restart itself.
Very frustrating, I'm on G930FXXU1DQB1 (German model), and when i search for update it says "up to date : DQB3 / DQA8 / DQB1."
Irritating as well !
Greg2Lu said:
Same here, I though that was Fleksy that sometimes load the phone and I had to shut it down manually (Power button + volume - for 7 sec) for a restart. Sometimes it restart itself.
Very frustrating, I'm on G930FXXU1DQB1 (German model), and when i search for update it says "up to date : DQB3 / DQA8 / DQB1."
Irritating as well !
Click to expand...
Click to collapse
This problem of random reboots often happens to your phone? What is the frequency of these restarts?
Good day everyone. So I recently started to experience weird freezes and crashes of most of the apps. Like facebook, instagram, some games. Not all of the apps do this. It all started about a month ago. I tryed using multiple diffrent ROM's. Although that ROM did work correctly for another month before these errors came up. Now I am using Global Elite rom: https://forum.xda-developers.com/galaxy-s6/development/sm-g920f-sm-g925f-griffin-t3435461
I always do a clean flash. Rooted with magisk, even though I was using SuperSU for other roms. Any help will be aprecieted. I am suspecting hardware failure (anyway to test that?). Thanks in advance.
Bumping this thread. Things getting worse... Please anyone. I am desperate...
Why don't you revert to your initial ROM, the one that never caused any issues?
RossTeagan said:
Why don't you revert to your initial ROM, the one that never caused any issues?
Click to expand...
Click to collapse
Problem is that every rom I've tried do same things. What is left to try is stock official firmware. But I will have to try it later as I am currently on the go.
Try to do a factory reset and see if the problem persists.
I've been using Lineageos 14.1 (and Xposed) on my Nexus 5 for yesrs and am happy with it. But in the last week I've been having crashes, usually when waking the phone from sleep. When that happens I can sometimes just reboot but other times I was faced with repeated bootloops and I've had to go into twrp recovery and "reboot system" to get back to a working phone.
To resolve the crashes and boot loops the first few times this happened, I deleted the Davlic cache and cache. The problem persists.
I updated lineageos to the latest Jan 3, 2019 even though I don't think this has anything to do with linesgeos which has worked for years, but the crashes continue.
I just don't know "how" to troubleshoot this problem beyond what I tried. What should I do to find out what is causing the phone to crash?
Any troubleshooting suggestions appreciated.
To determine if it a software issue, I suggest flashing the latest stock Google ROM. If the crashes stop, you'll know it is a custom ROM issue.
audit13 said:
To determine if it a software issue, I suggest flashing the latest stock Google ROM. If the crashes stop, you'll know it is a custom ROM issue.
Click to expand...
Click to collapse
Thank you for replying . I'll try that although the problems started without my having upgraded from the same rom I've used for a long time.
Would some kind of log help?
Thanks again.
A log would certainly help the developer.
Have you posted your query in the ROM thread?
Yes and got no reply so far.