Hello guys,
I searched for this issue on the forum but it seems that nobody encountered anything like this before.
To begin, I would like to mention that I am running the latest CyanogenMod 11 nightly on an HTC One X (Tegra version).
Since somewhere right after the latest M release, I've been having a couple of issues with the phone:
#1: From time to time, I get a "Lockscreen" isn't responding dialog and it asks whether I want to "Wait" or "Close". Well, if I click on "Wait" the phone becomes unresponsive, as if something was running in the background so hard that it would eat up all the ram and would choke the CPU;
If I click on close, it's a hit or miss situation: sometimes it restarts the lockscreen and takes me back to it, even though I previously unlocked the device and sometimes the phone becomes unresponsive as before.
#2: Besides what I mentioned above, the phone sometimes becomes unresponsive without warning and every time this happens, it always looks and feels as if something is chocking the ram and CPU.
Have any of you guys encountered something like this before and if yes, what can I do to fix it?
If not, is there a way in Android, to pull up a log similar to the Windows Task Manager, that would tell me exactly what was running in the background at a given time and how much memory/CPU cycles it was actually using?
Thank you in advance.
Try your stock rom for a while.
Mr Hofs said:
Try your stock rom for a while.
Click to expand...
Click to collapse
Thank you for your reply however, I haven't used sense roms in a while now, plus, it's a downgrade from KitKat, which is why I am not that fond of this option.
On a different note, I just installed the latest nightly "clean", namely with a full factory reset from recovery, flashed boot.img in fastboot and installed the latest GApps from PA.
I don't get the "Lockscreen is not responding" dialog anymore, but from time to time, the lockscreen still closes and now it either resets on its own, or it forces the OS to reset, after which com.android.systemui starts force closing indefinitely and the phone afterwards requires a hard reset.
Has anyone else encountered something similar? Any help?
I'm saying to use the stock rom for a while just to rule out hardware issues !
Mr Hofs said:
I'm saying to use the stock rom for a while just to rule out hardware issues !
Click to expand...
Click to collapse
Cool, will try that. Thanks.
What kind of hardware issues do you think could cause an issue like this?
Not sure but why stick to a rom that is not working properly, go for safe and go for stock if the issue is gone you can search for the issue that is caused by a rom !
Mr Hofs said:
Not sure but why stick to a rom that is not working properly, go for safe and go for stock if the issue is gone you can search for the issue that is caused by a rom !
Click to expand...
Click to collapse
Fair enough! Thank you!
Related
First of all, I would like to thank everyone involved in making our Defy's so awesome.
Thanks to you all, as after getting all the info and help, I was successfully able to
upgraded to CM7 1.0-RC1.5-jordan-signed, and after few initial hiccups everything is working fine. Except the battery drainage issue. And I have been loving the new look and feel of my Defy ever since.
Today Morning. I've started getting a new problem. Whenever I want to call someone and I go to contacts, it force closes itself with following error:-
"The Process android.process.acore has stopped unexpectedly. Please try again."
I have restarted the phone and no respite from the problem.
Help please....
Did you change something or install a new app immediately before this started to happen ? Did you restart your phone while it was still connected to the PC or so? Some other people solved this problem by doing a factory reset. But you need to find the specific reason or cause in your case and correct that.
tdlr said:
Did you change something or install a new app immediately before this started to happen ? Did you restart your phone while it was still connected to the PC or so? Some other people solved this problem by doing a factory reset. But you need to find the specific reason or cause in your case and correct that.
Click to expand...
Click to collapse
Well, the last thing I did last night was that I installed two ADW themes. and also downloaded few wallpapers.
Do you think, the themes could have created this problem?
mandhir.s.bajwa said:
Do you think, the themes could have created this problem?
Click to expand...
Click to collapse
As there is, according to my information, no standard cause for this problem, everything could be the reason. Other people reported this error on different devices too and the reasons were diverse.
Some have had the problem after installing a new app, others due to rebooting the phone while it was still connected to the pc. Others made a factory reset and then it worked again and the true reason was never found.
It won't kill you to try and disable/uninstall the new themes or wallpapers (if they are live wallpapers).
Maybe there is another specific well known reason for that out there. In this case I simply don't know one.
If you're lucky, others had the same problem and have identified a more precise cause. Then they will answer hopefully.
I would try to undo the last things you changed before and find out the true cause.
tdlr said:
As there is, according to my information, no standard cause for this problem, everything could be the reason. Other people reported this error on different devices too and the reasons were diverse.
Some have had the problem after installing a new app, others due to rebooting the phone while it was still connected to the pc. Others made a factory reset and then it worked again and the true reason was never found.
It won't kill you to try and disable/uninstall the new themes or wallpapers (if they are live wallpapers).
Maybe there is another specific well known reason for that out there. In this case I simply don't know one.
If you're lucky, others had the same problem and have identified a more precise cause. Then they will answer hopefully.
I would try to undo the last things you changed before and find out the true cause.
Click to expand...
Click to collapse
Thanks for the suggestions.
Will uninstall the new themes.
And as you said, Factory reset. If I do that, what exactly will happen.
Asking this because as mentioned before, I'm no longer on the version which came with phone and I am on CM7. so Factory reset will take me to which phase?
mandhir.s.bajwa said:
And as you said, Factory reset. If I do that, what exactly will happen.
Click to expand...
Click to collapse
Have a look here: https://motorola-global-en-uk.custh...00/~/defy---master-reset-/-factory-data-reset
You may also try fixing permissions before with Rom manager.
tdlr said:
Have a look here: https://motorola-global-en-uk.custh...00/~/defy---master-reset-/-factory-data-reset
You may also try fixing permissions before with Rom manager.
Click to expand...
Click to collapse
well the link tells me what will happen on a stock rom. My question is. If I factory reset on CM7, will it take me to the original state or the default settings of CM7.
Flash cm7 again! maybe it helps.
guys,do i need cyanogen 7.1 installed on my device to install cyanogen 7.5?
Make a backup and try wiping via CWM. Both data and cache partition.
Sent from my ME525+ using Tapatalk
yashank said:
guys,do i need cyanogen 7.1 installed on my device to install cyanogen 7.5?
Click to expand...
Click to collapse
You can flash any CM7 directly via recovery menu if yer on Froyo.
Sent from my ME525+ using Tapatalk
Recenty started getting few more issues.
1.> Phonebook crashing because of FC's. I'm hardly able to use my phonebook now
2.> Last night, messages stopped working. Again FC's.
3.> Today morning the native camera application stopped working.
And I have done following to overcome all the issues with no luck:-
wipes all cache including devik.
Did factory reset
reflashed with CM7 jordon 1.5
All failed to give me any respite from the errors.
Now I have downloaded cm7-110923-0710-Nightly.
Do let me know if this is an OK one. I've faced way too many errors and afraid of showing it off to anyone now as It might crash anytime.
Much to my disappointment, even flashing to newer nightly, I'm still getting the same errors.
Can someone provide me the 3.4.3-36-1.7 SBF? the one in the link provided earlier is not working.
Or any other solution.
The errors are way too much to ignore, and if this continues then I have to go back to Froyo. But I seriously love the new feel of the phone. All thanks to CM7.
need assistance ---defy just rebooting and rebooting after 2ndinit install
need assistance ---defy just rebooting and rebooting
i installed the rom amanger premium
after that i installed the 2ndInit from market for android and installed the latest version .....and after that i uncheck the usb debugging and restarted the defy
since then its auto rebooting from logo to black screen and back to logo ....
please help me i am new to this and really pissed off .......
Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
If you updated from 4.1 to 4.2 without a full wipe there's potential for a lot to go wrong. There could be some app running as a service that isn't fully compatible with 4.2 causing your issues.
With that being said, I would try fully resetting the device, no need to re-flash the stock image because it's already in place on the device anyway.
Install apps that are known to work on 4.2 ONLY. Then, you can begin testing to see if it becomes stable. After that, do what you want.
mortenmhp said:
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Click to expand...
Click to collapse
Thanks, I'll give a try!
cymru said:
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
Click to expand...
Click to collapse
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
g8who said:
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
Click to expand...
Click to collapse
Yeah, it's as if someone should add a search button to the forum :silly:
cymru said:
Yeah, it's as if someone should add a search button to the forum :silly:
Click to expand...
Click to collapse
But searching takes time...
And it's not like you can make it through a page in either General or Q&A without tripping over a 4.2 whine thread.
g8who said:
Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Click to expand...
Click to collapse
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
jpildave said:
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
Click to expand...
Click to collapse
This guy is correct MMuzzy has been the most stable for Vzn Gnex. I only have a qualm with the GPS, but that's every phone
Sent from my Galaxy Nexus using xda premium
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Only bluetooth problem
LeBaldi said:
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Click to expand...
Click to collapse
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again Also... sometimes when the phone goes into sleep mode it disconnect the connection with handset... It never happen in 4.1.
I downloaded the factory image of 4.2.1 from Google and flash it... still the same. I saw people saying a clean install... Should I do another kind of install other than I did?
Can someone please tell me if got this kind of bluetooth problem and have solved it? How?
Thanks
abcorp said:
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again
Click to expand...
Click to collapse
i have also encountered that behaviour, gets greyed out while "Turning off".
all the viperx version reboots while receiving calls! but sometimes it wont reboots....
i've changed it with other rom problem solved,but i love viperx more.... anyone know how to fix it?
Which one are you on now, the JB ? And if you are using the aosp lockscreen mod in the venom tweaks....turn it off and use the standard lockscreen. Might solve your issue
Also Make sure you have deleted the OTA update file from downloads folder.
Apparently recovery goes hyper if you dont (according to viperx thread )
A noobs solution
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
webDing said:
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
Click to expand...
Click to collapse
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Mr Hofs said:
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Click to expand...
Click to collapse
Wow, 3.7.0 (my version) is very old...well at least I didn't post a stupid question, just a stupid answer...
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Mr Hofs said:
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Click to expand...
Click to collapse
No, that was no sarcasm, I'm completely new to rooting phones and I thought progress was very quick and that my version had become obsolete very fast, or that I downloaded an old version.
I still have the problem, well not after disabling the setting...
I did a full wipe.
...but I flashed an old version, noticed my mistake, and then flashed 3.7.0.
The problem is that I know I did a full wipe before flashing the old version, but I'm not 100 per cent sure that I did it the second time. It sounds like missed it. So starting all over again would solve my problem? No short cuts?
Sorry about the misunderstanding!
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Mr Hofs said:
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Click to expand...
Click to collapse
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Hmm buggers, i can't really help you on this because i can't reproduce the reboots. Weird ! But at least thanks for testing
webDing said:
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Click to expand...
Click to collapse
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
webDing said:
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
Click to expand...
Click to collapse
I’ve been a Beta tester for a an American software company during a period of 7-8 years and I’ve written some simple plug-ins for their web design software. So, I tried to use that experience to do some testing and trying to minimize the number of factors that could trigger the problem.
What I did was a factory reset, a wipe and then I installed 3.7.0.
Before installing any apps, launchers and whatnot, I tried running the phone with both pin code and Viper screen lock enabled.
The result was the same every time.
I then tried to enabled the two settings in different orders, first pin code, then Viper and vice versa, but to no avail.
My conclusion, whatever it’s worth, is that it’s easy to get a problem when two pieces of code are trying to manage the same event. Maybe it’s possible to find the line/lines in the code that might trigger the conflict..?
…or maybe Viper just don’t like Sweden/Swedes?
Well, with a little (bad) luck maybe some other people run into this problem, but there might be very few of us who use Viper in this type of configuration…
I don’t think I can add anything more than this, so I’ll leave this issue in the competent hands of those who wrote Viper.
Thanks!
Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?
cainman said:
Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?
Click to expand...
Click to collapse
Might help to post which update you received.
reTARDIS said:
Might help to post which update you received.
Click to expand...
Click to collapse
D85110r
cainman said:
D85110r
Click to expand...
Click to collapse
Try disabling hw overlays in developers options to help with that redraw stutter. Remember you have to set it everytime you boot, unless you're booted with xposed installed, then you could download the module that keeps it active at all times.
This seems to have helped a lot of people with your issue.
Thank you.
It's sadly still doing it.
cainman said:
Thank you.
It's sadly still doing it.
Click to expand...
Click to collapse
Did you take the ota or download one of the twrp upgrades floating around? Either way in your situation you probably need to do a factory reset. Alternatively follow the twrp method HERE if you haven't already and I can personally guarantee a better than ota install. If you want it to be done correctly to fix any problems you need to wipe the system and data partitions before flashing. Also don't forget to download super su if you want to keep root (linked in guide). There is another upgrade twrp file in the development section I think that is not a perfect 1:1 image and could give problems. Not saying that particular rom is bad or that it is the problem, its just not a 1:1 like the guide I linked you to it is directory/installer script dependent. The one I made transfers the whole untouched partition over and inside has all the symlinks and permissions preset by LG.
Factory Reset
Guys I don't know if there's something wrong with my phone or not. Whichever rom or kernel I try, there is an abnormal shut down of my device. Like I'm using it and I leave it for a few minutes or so and it shuts down. I'm not sure if it had something to do with deep sleep or anything, but I need help. Please guys anyone
on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)
YasuHamed said:
on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)
Click to expand...
Click to collapse
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.
promiscuss said:
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.
Click to expand...
Click to collapse
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)
YasuHamed said:
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)
Click to expand...
Click to collapse
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps
promiscuss said:
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps
Click to expand...
Click to collapse
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display
promiscuss said:
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display
Click to expand...
Click to collapse
sir, which custom ROM + kernel + anrdoid version are you on ?
YasuHamed said:
sir, which custom ROM + kernel + anrdoid version are you on ?
Click to expand...
Click to collapse
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.
promiscuss said:
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.
Click to expand...
Click to collapse
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?
YasuHamed said:
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?
Click to expand...
Click to collapse
Thanks for all your effort, the problem seems to have resolved on its own. I'm not sure what it was.
now it's happening to me but it's much more severe. First it started slowly now it's so frequent that the phone might shut down even on boot. This is really frustrating.
I had the same problem with my redmi note 7, flashed stock rom with MI flash tool, fixed everything for me