Related
I have Galaxy S with Android 2.3.4 JVR and it works like a charm - with this one exception: sometimes (too often) phone, contacts and messages (sms) keep closing. This happens usually within a second or two after opening up them. There's no force close message, it just returns to the home screen without any warning. If I reopen it, it usually does the same a couple of times, but eventually I get it to open.
At first I thought this must be a memory issue. However, I have Autokiller installed (my phone is rooted) and I have usually >100M free memory. Then I thought it must be Autokiller killing the dialer, contacts or messages apps. BUT: this happened also before I had Autokiller installed, so it can't be that either. The strangest thing is that I tried installing GO SMS Pro and GO Contacts + Dialer, and even they do the same thing occasionally (close immediately after I open them), so it isn't a problem with apps either.
I am bedazzled here, could somebody please help me? This starts to get really annoying, since the dialer, contacts and messages are the feature you normally use most in your phone!
I have the exact same problem! Somebody, please help
the phone app and etc. seem to be corrupt or something
try reflashing.If you keep getting the problem then revert back to your previous rom =/
Is there any way to try to replace only the phone etc. apps without flashing the whole rom?
from my experience no but you can try replacing phone.apk sms.apk etc with the previous rom's apps
The funny thing is that I have a stock 2.3.4 JVR, so it should be stable.
Plus, did I mention that this happens only sometimes? Sometimes they work ok. But this happens often enough to be annoying. You know, when you would have to make a quick phone call you have to open the phone app like 3-4 times, only then you're able to make it. I wondered if the the problem could still be in the dialer, contacts and messaging apps even if the problem occurred only sometimes?
In addition, the calendar app has done this a couple of times. Could it be that there's a conflicting app that's causing this? If so, do you have any suggestion what it would be?
Autokiller made my phone do some really funny stuff. After installing it i was having random reboots and apps crashing so i uninstalled and problem solved. You said it was happening before you installed it though so im just guessing that you need to either wipe cache and dalvik then reboot or do a full wipe and reinstall of your rom. When you do the full wipe go into mounts and storage and wipe system too
Hi and thanks for your comment. What are the effects of wiping the cache and the dalvik cache? Do I lose important data? Or can I do it safely? Sorry, I'm a bit of a n00b with android. I suppose you wipe the cache in download mode, right?
I experience exactly the same issue as you-though I am on stock jvu.I come from 2.3.3, stock as well, using chainfire root both times.
Sometimes phone contacts and message s close immediately after opening them, often several times. and sometimes everythings fine
here you can find some information about dalvik and normal cache wipe..your data will be safe-only first boot will take longer.I will try wiping now, too-reporting back then.
Edit:
For now wiping seems to have worked well and fixed the problem here..I need some more testing though-will keep you up to date here
edit 2: damn! The issue's still there.anyone got more ideas?
G'day!
I have the exact same problem with JVU and I had this problem with 2.3.3 but less frequent. I have no choice but to reboot the phone when it happen. I suspect it's caused by one of the widget (email and Go weather) that I put on the desktop. Going to remove the two widgets from desktop and see if it's help.
Whitest said:
I experience exactly the same issue as you-though I am on stock jvu.I come from 2.3.3, stock as well, using chainfire root both times.
Sometimes phone contacts and message s close immediately after opening them, often several times. and sometimes everythings fine
here you can find some information about dalvik and normal cache wipe..your data will be safe-only first boot will take longer.I will try wiping now, too-reporting back then.
Edit:
For now wiping seems to have worked well and fixed the problem here..I need some more testing though-will keep you up to date here
edit 2: damn! The issue's still there.anyone got more ideas?
G'day!
Click to expand...
Click to collapse
earthman5678 said:
I have the exact same problem with JVU and I had this problem with 2.3.3 but less frequent. I have no choice but to reboot the phone when it happen. I suspect it's caused by one of the widget (email and Go weather) that I put on the desktop. Going to remove the two widgets from desktop and see if it's help.
Click to expand...
Click to collapse
Okay, that sounds interesting - though I am not sure wheter a widget could cause this...
I am still running JVU but now with Galaxian Kernel instead of Chainfires root Kernel - flashed with SGS Kernel Flasher and still got root - and it runs very stable and fast 'till now. No more closing of phone, contacts and messages so far -.- since 2 days.
I'll tell you when it happens again, but so far it seemed to be a kernel issue for me...
I've been having the same issues with my Samsung SideKick 4G. messages would keep closing as I was typing them, I would lag and the key I pressed would "press again" like 15 more times, sometimes I just couldn't open a conversation, other times I couldnt answer phone calls cause the UI lagged.
That was all on stock firmware, and I got fed up with it so I tried to flash a custom ROM on it, and before I did that I had it OC'd to 1.2GHz which was actually pretty great. Needless to say, I screwed up on flashing the ROM and now I'm looking for firmware to odin back to stock. =\
Seems to be somewhat common but no fix to be found...
Using CM7.1
Was working perfectly for a month.
Seemed to happen out of no where, no new apps installed or settings changed. The phone will vibrate for incoming calls, haptic, everything except SMS.
Using GoSMS but it does the same with the stock messanging app. Vibration is turned on in all the system and messanging settings. In fact, when I test settings in GoSMS it reports "vibration on".
Tried clearing the dalvik cache and tried installing this app but it won't show anywhere in the app drawer and I can't find it anywhere on the phone despite the market saying its installed. Unfortunate becasue it seems this app was designed for this very issue with desire/insprire.
Anyone have a fix for this or a method I could get the above app to install properly?
Thanks.
edit.....It's looking like an app issue......
never mind on the rom repair part....sorry
mods can delete....g
Gregsarg was actually probably right the first time. It doesn't seem to be an APP issue (as all MMS apps have the same lack of vibrate), but a broader issue.
His suggestion to install CM7 on top of itself is likely the simplest attempt at solution since you haven't found a specific solution through your searches.
I also tried the GoodVibrations.apk and it only shows in airdroid, mybackup, and managing all apps... It doesn't even have the 'open' command on the market menu after installing it >.>
Wulamoc said:
His suggestion to install CM7 on top of itself is likely the simplest attempt at solution since you haven't found a specific solution through your searches.
Click to expand...
Click to collapse
Thanks. Unfortunately I didn't see this suggestion before it was edited out. What exactly is meant by install CM7 on top of itself? Through clockwork I presume?
Yeah, just flash the SAME rom again (after backing up AND without wiping anything), and your settings should stay in place.
There is also a setting in the stock CM sms app that controls vibration, which is turned off by default.
Yeah vibrate in the stock SMS program is on. While I haven't gotten around to reflashing just yet I have noticed a few other things that lead me to believe its a ROM issue. Sometimes when I put the phone on silent it turns off all system vibrations even after coming off silent. I have to go back in and turn vibration back on. This is intermittent. Also, out of the blue the phone started vibrating during calls, come to find out "vibrate every 45 seconds during outgoing calls" was magically turned on.
It WILL vibrate when an SMS arrives if I'm on a call. Swell.
Flashed the new 7.2 nightly and the problem still exists. Everything remained intact after the flash so I figure I'll just do a full wipe/factory reset and flash the new nightly again and start over. Hopefully whatever caused this won't carry over with titanium restoring apps.
Do the full wipe, install the rom... then get a friend to send you text messages BEFORE you restore from Titanium, and then after....
Easy to isolate if you're carrying the issue from ROM to ROM.
Had the same issue, could find no fix. Used vibrate tools from the market and no issues for a week or so now..
*signed
mrrick said:
Had the same issue, could find no fix. Used vibrate tools from the market and no issues for a week or so now
Click to expand...
Click to collapse
That did it thanks! Saved me from having to do a full wipe. Phone is back to vibrating with SMS and I can change the vibration pattern. Nice.
Cool, glad it worked for you. I really wish I knew what happened though, it's kind of bugging me.
Meh, technology..
*signed
Well I'll add this... Out of curiosity I removed the vibrate tools app and everything is still operating as designed. So whatever that app turned on has stuck.
My stock ROM crashes (or auto-reboots) every 9 days 9 hrs 30min like a clock.
It happened for at least third time in a row, or most likely it is going on like this all the time because I only noticed this odd behavior when I installed a little "uptime" app. After 3 times obviously that's not coincidence, something is causing my phone to crash or reboot every 9d 9hrs 30min.
Has anyone else notice or had same problem?
Stock rom, locked/unrooted, with stock apps and very few extra apps installed, after previous crash I removed almost everything I had installed in the past, I kept only AirDroid, ColReader, Google Drive, File Manager, Mobo player, Skype, SPB TV, TeamViewer - nothing else, yet it still crashed. I can't figure out is it ROM or any of the apps.
edit - perhaps I should have posted in ROM development... Moderator, please move it?
I wish I could help but I've never been able to stay on the stock ROM for that long.
But....no, you've posted in the right place. Put it in developement and it'll get moved to HERE.
There's a TMobile app on there that monitors the days until suggested reboot (7 days) and will then proceed to "warn" you consistently when you're over that period. It is possible that this app is clashing with one of your other apps or doing something in the phone - maybe using too much memory? /shrug
My phone does the exact same thing after a week but it doesn't reboot, it just randomly "soft-crashes" after I hit the back or home key while playing a game or backing out of dialer, apps, etc.
It's extremely annoying and happens whether I have few apps or my normal stock of apps; the only time it doesn't happen at all is after a factory reset (if I don't update anything).
The only thing I can do to stop it is to reboot the phone, as suggested on the 7th day...as soon as I see that notification, I reboot and so far so good.
Good Luck.
I had been doing a great deal of tinkering trying to get my phone's battery life back in the last few days, and I made good progress, but I severely jacked up something related to the microphone/speaker/video recording.
PROBLEM:
The problem, as far as I can tell, is that every app that tries to access the microphone can't do it--this shows up when I try to use Google voice input in various text fields with a little "Can't reach Google at the moment." Same with trying to do a search by voice in Google Now--brief brief flash of the microphone red, then back to gray, with "Can't reach Google at the moment". Additionally, my Touchless Input cannot be enabled--the box has automatically unchecked itself, and pressing it makes the button get a little gray, registering the action, but no checkmark will appear.
Additionally, other apps which would use the mic don't seem to have that functionality--Evernote, for example, would crash if I attempted to record an audio clip. This was before I performed a factory data reset last night--and the problem has persisted regardless.
There are two other, seemingly related, issues. First is the inability of the phone to capture videos. The camera opens fine, and I can take fine stills with it, but pushing the video recording button makes the red "record" flash for a moment before a "Not able to record media" message pops up, and the camera returns to the still photo mode.
Second is the inability to play videos. I have tried playing videos in as many formats as I could try, from within several players, including the stock "Photos", "Gallery", and "YouTube" apps. "Sorry, cannot play video" pops up, or the app simply crashes. Similar story for attempting to play music through the stock "Google Play Music" app. And it gets worse. I can't make or receive calls. Actually, let me revise that. I can't hear anything being said on the calls, over the speaker, or through headphones (though I've yet to try BlueTooth). The call appears to connect, but I can't hear anything from them, and they can't hear anything from me.
So--that's the basic summary of the problem--threefold.
1. No audio input through mic
2. No audio output through speakers--my phone doesn't ring when I get a call, although it will vibrate and the options to take the call appear as they normally would.
3. No audio/video playback whatsoever for other media.
I'm running Android 4.4 on a Droid Mini, unrooted, and I just completed a factory reset last night.
ANALYSIS:
Here's the wrinkle. I know this isn't a hardware problem, because I have found a surefire fix that makes all of this work properly if I absolutely need it, it just sucks. Rebooting into safe mode is what does it. Playback resumes as it did before I had the problem. I can play videos, pump music, and Touchless Input works flawlessly--although interestingly, it has me re-enter the catchphrase three times every time I get into safemode, like setting up from scratch.
My consternation comes from the fact that, to my very limited knowledge, all that safe mode is doing keeping any user-added apps from running. Which is all well and good, but I just did a factory reset. Literally when I boot the phone no user installed apps are running, and yet there's a definite difference when I boot into safe mode, cuz everything works there.
So, safe mode must do something more than just disable user-installed apps--and I need to know what that is if I'm going to fix this thing. I have added 4 apps since then-- App Ops, GSAM Battery Monitor, BetterBatteryStats, and Button Savior (Non-root), all of which I know from experience to be very "well-behaved" apps.
Anyone know what safe mode is doing besides disabling user apps? Along those lines, does it revert updated stock apps to their factory state? I ask because very, very briefly, while my phone was slowly trying to upgrade the 40-odd pieces of Bloatware from the Play Store, the microphone was working. Which makes me think that the culprit is one of the system apps in it's updated form. If safe mode runs these apps as they originally appeared on the phone, that might explain it. It would also hopefully let me painstakingly disable these apps, one by one, to find the culprit and disable it.
I say culprit because of something I stumbled across trying to research this--weirdly enough, in a message from the devs of Shazam. devs of Shazam They say that the issue has shown up on 4.4 and the cause appears to be one app somehow monopolizing access to the microphone. I could see this breaking the video as well, and potentially the audio playback if, as I assume, Google uses the mic to help tweak the sound of the speakers.
Anyone know any more about any of the aspects of this? I will be posting back myself as I learn more.
What happens if you factory reset without restoring any apps? In other words, factory reset, choose not to restore your apps (or don't attach to a Google account on initial setup, and do it post-setup). In other words, do you have an app that is blocking this access?
doogald said:
What happens if you factory reset without restoring any apps? In other words, factory reset, choose not to restore your apps (or don't attach to a Google account on initial setup, and do it post-setup). In other words, do you have an app that is blocking this access?
Click to expand...
Click to collapse
Trying this now. Thanks for the suggestion!
Update: Tried this. Did another FDR, signed in to one of my Google accounts afterwards, but haven't updated a thing. The audio/voice/video/bugs seem gone; however, the ****ty battery drain I had before is back. I'm playing around with some settings to find out what can be done. I'm also going down the list and updating the system apps one by one.
Does anyone know a good testing process (ie, should I run the app? do I need to restart after install? run the app and close? etc) that will keep me from getting false negatives (ie thinking an app isn't causing the problem when it is)?
Update again: I'm working down in alphabetical order through the factory apps. However, after the most recent factory reset, it appears that my battery drain is back, and as long as the battery drain is there, the phone works normally. So, not looking good in terms of battery+functionality for me. Went through the 40ish apps that were on the phone stock--after the fresh reset, the phone is working, but the battery life is shot to **** all over again. Not sure what to make of all this, and now back to being frustrated with a 4 hour battery life from the phone that never sleeps. UGH
Update yet once more:
For kicks and giggles, tried unchecking the "Touchless Control" in settings, to see what effect that would have on my battery. But, reasoning that whatever wakelock was keeping my phone up all the time had to be persisting after it was needed, I guessed I needed to reboot to get rid of them. Booting up again, I'm back to battery life without audio/video/etc. Very confused here. Apparently it has nothing to do with the apps installed, period.
Facing the Same problem please someone tell me What should i do
Same problem! No audio call
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Please help me I have this same problem. No audio, cant play video, nd mic isn't working.
Am I alone ?!
Lineage OS works fine, for a couple of days, then, out of nowhere, the homescreen and menu buttons are not responsive. Then, upon reboot, homescreen turns black, showing nothing except the status bar. The status bar can be swiped down, but everything you click is not responsive.
Wiped Dalvik and cache, issue is still there...
* After a reboot, the device shut down inexplicably. Upon next reboot, issue resolved... WTF is going on?!
jfpesant said:
Am I alone ?!
Lineage OS works fine, for a couple of days, then, out of nowhere, the homescreen and menu buttons are not responsive. Then, upon reboot, homescreen turns black, showing nothing except the status bar. The status bar can be swiped down, but everything you click is not responsive.
Wiped Dalvik and cache, issue is still there...
* After a reboot, the device shut down inexplicably. Upon next reboot, issue resolved... WTF is going on?!
Click to expand...
Click to collapse
I have the exact same problem! Installed LOS on Friday evening and it worked great until Monday afternoon. Screen was on and had full notification bar contents - it looked like the phone was working properly. It could even take calls, receive emails and texts, but the rest of the screen was black and the buttons reset to original settings and didn't even work correctly. The Home button did nothing except a double tap would create a brief white border around the edge of the whole screen. A single press did nothing. The back button worked properly. The switcher button did nothing at all. I think it was doing the Google assistant thing. Holding in the power button was setup to press restart and then give restart options, but it was reset to just restart and confirm.
Restarting never worked to correct it. Wiped cache and Dalvik cache, still no go. Letting it sit for over 30 mins did let it recover once and one other time while driving it went from this black state to fully functional for no reason. It was good for a few minutes and then the buttons stopped working again. The soft buttons did not help either. They behaved badly as well.
It seems to have no pattern. I wiped the phone and flashed the newest LOS on Monday evening and it worked great until tonight. I have no idea what is going on!
Glad to know I am not the only one... Just need a permanent fix!
Nice, a brother !
The back button worked properly.
Click to expand...
Click to collapse
Same thing here.
Also, I can't tell if receiving calls work, cause I didn't try, but I can confirm the quick settings tiles keep working. The drop down notifications show up, but clicking an individual notification won't bring up the app it is refering to.
So far, the "shutdown, wait a little and reboot" seems like the only thing resolving the issue temporarely. So yeah, before wiping everything and reflash LineageOS, keep calm and wait !
Also, be sure to do a backup your working OPO/LineageOS phone in TWRP mode, so you don't waste time reflashing OS, restoring apps with Titanium Backup and restoring settings manually, like I did three times over the past two weeks...
Too bad we don't see the changelogs with each weekly LineageOS builds releasing or any bug report compilation.
I am conducting some trial and error testing to help isolate the problem. So far it feel like it is related to profiles, specifically with either a trigger or disabling the lock screen. It seems when I add a profile to unlock and disable my lock screen via a wifi "on connect" trigger, that is when things seem to go down hill. generally shortly after is when I get the black screen. I am using the Pixel launcher and have added a Home profile with triggers for wifi and then set my lock screen to disabled. I am currently using the default profile and have not added any others and the phone seems to work well with no issues. It is still too early to say that is the problem, or even exactly what the specific problem is, but I will continue with the default profiles as-is for the next few days or week to see if it remains stable.
Maybe this will help steer someone else to find a fix...
Also this has just happened to me.
All was working fine for a few days since flashed now have same issue as above
Also had Profiles set up for home network for lock screen and sync etc
Phone is Redmi Note Pro 3 though
Stumbled across this while looking for info on this issue
https://www.nico-maas.de/?p=1537
That link is going down the exact same path as I am. Coming to the same conclusions. Thanks for posting it.
With the default profiles in use, I no longer get the black screen and everything is working fine. I will need to keep an eye on the change logs to see if a profiles fix come down the pipe.
For me, it was changing the Lockscreen to none (from pin) that caused the black screen. That link defiantly helped me out. Only thing I did was edit the "profiles.xml" and changed '<screen-lock-mode>' to 0 instead of 2
Yep, also using System profiles to disable lockscreen at home or in car.
Lately, I get no issue at home, but only in car, where my system profile is also setup to activate hotspot when Bluetooth connected to my radio. As soon as hotspot turns off, issue is resolved.
On another side, I mentioned earlier that LineageOS doesn't list its changelogs. I was wrong. You can find them here : https://www.cmxlog.com/14.1/
Fixed!
I experienced the same problem today with my OnePlus 2. Guess time does heal. I waited for a good half an hour and it seemed to fix itself.
When the screen is off, hold down the power button for a second and you should see the power menu. Select 'restart' and let the phone reboot. Simple as that!
Tell me if the problem still persists.
Still having issues.
Notification cannot be seen , I can only hear them.
I haven't configured any profiles.
Home and recents don't work.
Can't open developer options, its says its not available for this user
Anyone have ideas ?
Help me
I got issues with LO, my back, home, recent buttons not working (capacitive) so I'm using on screen button. But after all happen, now I'm having problems with my volume button, it didn't work at all, already restarting my phone many times, also, chance the system profile to default, sadly, it didn't help. Can someone help me with it.
This is not a new issue. I first encountered on CyanogenMod 3 years ago, and I'm disappointed to find that it still hasn't been fixed in
Lineage os. In CyanogenMod disabling "reduce power consumption" in the adaptive display section resolved it. But now with lineage is there doesn't seem to be any specific setting that causes it.
had the same issue - pretty sure it has something to do with "Profiles" set up. For instance, I set up profiles for turning off Lockscreen when Home - using the WiFi detection.
After a restart, the screen went black, but funny enough, the quick menu and the Bar still showed up. I turned on Airplane mode, to switch to the default Profile - which enables the Lockscreen when not in wifi and restarted. That worked.
So I think something with the Lockscreen + Profiles is a bit buggy.
It only occurs after a reboot.
I am using LineAge OS for M7 14.1 - which runs great!
AD
Have the same problem. Tried to update Lineage OS, but it didn't work out. Can anybody help me?
taalojarvi said:
Still having issues.
Notification cannot be seen , I can only hear them.
I haven't configured any profiles.
Home and recents don't work.
Can't open developer options, its says its not available for this user
Anyone have ideas ?
Click to expand...
Click to collapse
romap0 said:
Have the same problem. Tried to update Lineage OS, but it didn't work out. Can anybody help me?
Click to expand...
Click to collapse
I solved this by clean flashing ( Data wipe + LOS Reflash ).
It's a Known LineageOS source bug ( according to their reddit )
I've started getting this as soon as I tried getting the first time setup to work again. Try this:
adb shell
su
pm enable com.google.android.setupwizard/com.google.android.setupwizard.SetupWizardActivity
2. adb shell settings put secure user_setup_complete 1
and if it doesn't work try adb shell settings put secure user_setup_complete 0
I have a Nexus 10 running the latest 7.1 Lineage image and had the same problem after updating the system and the GApps... here’s how I solved this problem on my tablet... maybe it will help someone else...
1) Use TWRP as your recovery loader
2) Backup your image using TWRP
3) Install the latest GApps - I use the Nano version
4) Wipe the Cache after the install is complete
5) Reboot and wait for the system to settle
6) Reboot into recovery (TWRP)
7) Install the latest Lineage (I use nighties)
8) Wipe the Cache after the install is complete
9) Reboot and wait until everything loads
10) Problem solved.
So... install GApps over the existing install... reboot let it do it's cleanup, then reboot into recovery and install the nightly update... wiping the cache of course... its worked for me three times now.
AlexInvar said:
I've started getting this as soon as I tried getting the first time setup to work again. Try this:
adb shell
su
pm enable com.google.android.setupwizard/com.google.android.setupwizard.SetupWizardActivity
2. adb shell settings put secure user_setup_complete 1
and if it doesn't work try adb shell settings put secure user_setup_complete 0
Click to expand...
Click to collapse
Great! Setting secure user_setup_complete to 1 seems to work for me.
EDIT: Nevermind, the problem only occurs when I connect to wifi with the screen off, which I didn't test. So no solution yet.
hello there! i have a similar bug on lineageos 15.
everything worked fine until today. no new apps installed or settings changed.
i flashed on 1. December and im really happy with this ROM, but today the hardware touch-keys stopped working correctly. The back button is ok, home button don´t work (except the double-tap function which starts splitscreen) and the menu button wich is set to swich last app with a single tap and show all open apps with a long tap opens the app-menu instead (that function that we know from android 4...).
after rebooting everything start to work again but only for a random period of time.
sry for errors or bad english...
i hope it will be patched cause the ROM is really one of the best i had.