Hi, a few days ago my phone camera fault, I get a notice saying "error connecting to camera", so I did a logcat to see what happened but I honestly don't know how to read it and thus can not understand where is the reason for the problem so that's why I put this here so that any experienced user help me and tell me what is the problem... Here is the log http://pastebin.com/print.php?i=rXU9DwAc
Thanks for your time guys!
PS: the front camera and flashlight also don't work, I try flashing another rom but didn't work (CyanogenMod 10.1)
Well at face value, e.g. taking the error literally.. a bug caused a java error keeping the camera app from loading properly. Specifically an empty string value that throws an exception.
Now you have to place that in a context. If it was a one time error.. don't worry about it. If it is repeatable, it could be a bug, conflict, corrupted install, et cetera. A logcat is just a detailed log of what the OS and drivers were doing to provide clues for troubleshooting. Do a search for the CM build you have and see if anyone else is having issues. If so, that suggests a bug. Otherwise you can try disabling other apps that may be conflicting.
You implied that this is a recent problem.. so corruption or a conflict seem more likely. Did this happen after a recent flash or installing a new app? If you flashed a new CM build, did you wipe the cache? If not, I'd suggest that you If not, consider reflashing your ROM, ensuring that you wipe the cache data to see if that resolves the issue. It seems odd if you had a stable configuration and reflashing doesn't resolve the issue.. at least temporarily. Look for a pattern or missed step, like not wiping the cache.
HTH
fffft said:
Well at face value, e.g. taking the error literally.. a bug caused a java error keeping the camera app from loading properly. Specifically an empty string value that throws an exception.
Now you have to place that in a context. If it was a one time error.. don't worry about it. If it is repeatable, it could be a bug, conflict, corrupted install, et cetera. A logcat is just a detailed log of what the OS and drivers were doing to provide clues for troubleshooting. Do a search for the CM build you have and see if anyone else is having issues. If so, that suggests a bug. Otherwise you can try disabling other apps that may be conflicting.
You implied that this is a recent problem.. so corruption or a conflict seem more likely. Did this happen after a recent flash or installing a new app? If you flashed a new CM build, did you wipe the cache? If not, I'd suggest that you If not, consider reflashing your ROM, ensuring that you wipe the cache data to see if that resolves the issue. It seems odd if you had a stable configuration and reflashing doesn't resolve the issue.. at least temporarily. Look for a pattern or missed step, like not wiping the cache.
HTH
Click to expand...
Click to collapse
Well none of those, I was on a stock rom (I flash a few tweaks for improve the net speed and things like that) and suddenly the camera error starts so I flash a cm rom for try to solve the problem but seems to not work ( I make all the wipes correctly)
martin_carpio17 said:
Well none of those, I was on a stock rom (I flash a few tweaks for improve the net speed and things like that) and suddenly the camera error starts so I flash a cm rom for try to solve the problem but seems to not work ( I make all the wipes correctly)
Click to expand...
Click to collapse
The essence of troubleshooting is looking for patterns.. which point us towards the ultimate cause of a problem. If I had a java error, the first thing I would try is simply rebooting the phone. If it continued, I would suspect a conflict (if I had recently installed an app or changed some settings). So.. try reversing those tweaks and see if that clears that error. Less common would be corruption.. and you might test that by flashing back to the same stock ROM if it was working fine before you saw the issue.
Flashing to a different CM ROM wouldn't be a first step. It might work. But you don't gain much knowledge if it doesn't as a new ROM introduces a host of new variables as well. If the cause of the issue is unclear, you want to confront the most obvious suspects first and try to change only one variable at a time. In your place, i'd go back to the stock ROM.. confirm that the camera works properly again. Then restore your tweaks one by one watching to see when the problem recurs.
Good luck
.
Related
The AOKP build works great except for the constant disappearing keyboard that is about to make me kick puppies. I saw the note to install the wingray google apps to avoid the disappearing keyboard that is synonymous with the recommend gapps to use, but my dumb ass forgot and installed the recommenced apps and I surely do have the constant disappearing keyboard issue. I have flashed the "gapps-jb-20130129-P75xx" zip but still have the issue. Do I have to wipe everything and start over? Does flashing the new gapps zip not overwrite the "gapps-4.2.2-jb-3.4.2013-signed" I originally installed? It seems not to, but wanted confirmation before wiping everything again.
You should wipe everything and start over. IMHO.
Full wipe and used the "gapps-jb-20130129-P75xx". Disappearing keyboard will no longer boil my blood.
For reference, never use the "gapps-4.2.2-jb-3.4.2013-signed".
Glad I stumbled onto this thread. Exactly the problem, keyboard, (well one of them anyway) I am having.
Well for me I can't find anything to fix the disappearing keyboard issue. I tried using the suggestions above. No help. After finding more and more posts in the same subject on different boards it seemed only the Wingray gapps is the one that works properly. Just tried that one and it doesn't seem to fix the issue either. Tried several of the newer nightly ROMs too.
One suggestion was to download the Go keyboard. That didn't help either.
Dang how hard can this be? I have flashed and wiped cache so many times lately. lol
The problem why is exactly explained in nakedninja's 4.2.2 thread, you should read before you install anything
DefQoN_BE said:
The problem why is exactly explained in nakedninja's 4.2.2 thread, you should read before you install anything
Click to expand...
Click to collapse
Unfortunately that thread content has not helped in my case. I found that thread early on and have tried to follow the directions. So either I'm missing something or not doing something correctly it appears.
Someone in another forum suggested I try the free Jellibean keyboard.
I had this issue too with AOKP 4.2.2. I have not reflashed another new gapps yet, as I found re-installing a third-party keyboard which I liked from previous use solved the problem.
Andre
Well whatever I did I finally fixed it. I ended up simply formatting the internal SD card. Poof, everything gone. Had to restore from backup default ROM. Once the stock firmware was up and running I followed the procedures again. Wiped, cleared cache multiple times and when it was all done installing there is no more keyboard issue as of now.
I loaded the 4/08/2013 nightly ROM and Wingray gapps(which I've already tried multiple times). So all is well in Tablet land again.
Intro
I don't mean this to be a thread for any specific ROM or problem, but rather a general guide that essentially eliminates all doubt of machine or user error (we all make mistakes). This is generally geared towards the issues users are experiencing when flashing an AOSP ROM, but can also apply to Sense, and even other devices. This covers from downloading a ROM forward, and also making sure that everything gets properly installed with no corners cut, so that everybody can be on the same page when a problem arises. I'm not trying to say anybody's way of doing things is wrong, but I've see a lot of people asking different questions that end up getting solved with the same few answers. This isn't a "how to flash" thread, but rather how to ensure you're getting your device in a clean, fresh state so that everybody can be on the same page when it comes to bugs, otherwise nobody is going to want to help you if you don't try to help yourself first.
I know this is on the longer side, so key points are underlined, with a TL;DR at the bottom
Downloading
Checksums or hashes are a great way to make sure that the *.zip or any other file you're downloading is not only the right one, but that it hasn't been corrupted or tampered in transfer (uploads or downloads). You'll probably need to install something to work with chescksums- personally I like the open-source HashCheck for Windows. It adds a "Checksums" tab to the right-click > Properties dialog that automatically calculates MD5 (most common) and SHA-1 (more advanced) hashes. I encourage anyone posting a file to also post the MD5 with it, for everybody's sake, since it only takes a few extra seconds to eliminate all doubt of a bad upload or download. HashCheck even gives an option to create a *.MD5 file, just like the ones you might get from goo.im. If you're on Linux, Android, or presumably Mac you can check a file's md5 by opening terminal and simply typing "md5sum <filename>" without the quotes. If a file is posted without an MD5, you can download it twice and check it against itself, but just keep in mind you're going to be hitting somebody's server twice as hard, so only do it if necessary. Now that you're sure you have the right files...
Wiping/Flashing
Most people know dirty flashing is at your own risk, and if you have a problem, the first thing anybody's going to tell you is to do a clean flash. No really, just clean flash- that's what backups are for, but that's a whole different topic. Unfortunately, most people consider a clean flash to be just a factory reset, but that only wipes dalvik, cache, and data (except your sdcard), while leaving the system partition intact. To do a proper clean flash you want to go into advanced and make sure that system gets wiped in addition to dalvik, cache, and data. I can't say exactly what (sorry), but there's lots of miscellaneous things that can persist between flashes, especially when you're going to a different ROM. For us DNA owners, there's still a lot of activity in our CM device tree, meaning that even on the same ROM, some of our device files may change between versions which will necessitate a wipe of system. Maybe it's just me, but it seems things go out of line more often on 4.3 so I just always wipe system now.
If you're here, you probably know how to flash a ROM, but always double check the OP or first few posts and see what gapps/settings/etc are recommended. I'm also going to remind you that it takes just a few extra seconds to create a *.md5 file with HashCheck that you can push to your device along with the *.zip and TWRP (probably CWM too) will check the file against it's MD5 before flashing it. After using the Setup Wizard to log in to your Google account, make sure that you uncheck the box to restore settings and data to your phone, otherwise those can cause problems. Now you can be sure that whatever is on your device is clean as can be and as the developer intended, otherwise you're probably not going to get much help.
Narrowing down the problem
Now that you've got a brand spanking new and clean ROM is the best time to try and narrow down a problem, but before you post anything, try the golden rule of IT- "Have you tried rebooting it yet?" Also, you can try booting to recovery to clear just dalvik and cache and/or repair permissions. This is the first time you should consider making a post about your problem, but please, please, please don't make a post that just says something like "Settings FCs." Posts like that don't tell anybody anything- the best thing you can do is pull a log (more on that in a second), and create a post in the appropriate thread which you can determine as follows: Start by seeing if the problem occurs with nothing installed besides the ROM and recommended gapps- do not restore any backups, install any apps, or flash any kernels, even if the OP recommends it. If you're having problems with Settings or any Google app, there's likely a conflict with the gapps package that should go away if you reflash only the ROM, otherwise it's a bug in the ROM itself. Either way, if you can reproduce a problem at this point you should post in the ROM thread. If you want to flash a custom kernel, only do so after you've verified the problem isn't with the ROM or gapps. Flash only the kernel, and if there's any problems after that, post them in thread you got the kernel from, not the ROM thread.
If you're having a problem with an app, once you've completed the above steps, install only that app without restoring any data. If you can't replicate the problem, there's likely an incompatibility any corresponding data you may have restored, and sorry, but there's not really anything you can do about that. If the problem occurs with a freshly installed app, first check the Play Store to see if other users are experiencing the same problem- there may just be something wrong with the app. If it only seems to be you having this problem with a clean install, the ROM thread is the best place to post, although keep in mind other users may not be familiar with app.
Pulling and posting logs
Even now, nobody is obligated to help you (you flashed that ROM at your own risk, remember?), but once you're at this point, you'll have a better chance at getting help. Try to include as much information as possible like what else you were doing, what screen you were on, what button you tried to press, etc. and if you can, try to see if you can replicate it. Like I mentioned above, posting a log is the best way to get help, and they're really easy to get. Not everybody is going to understand every line, but if you know what you're looking for, occasionally the log can tell the developer exactly what the problem is, and bam- easy fix.
First make sure USB Debugging is enabled in Developer Options (if you don't see Developer Options, go into About Phone and tap on the Build Number line 7 times), and make sure that Root Access is set to both Apps and ADB. Now as far as gathering these logs, SysLog is by far one of the easiest ways- download it, open it, and press "Take Log." It pop up a toast message saying that your logs are in /sdcard/SysLog/<DATE_TIME>.zip and it'll even give you the option to share it via email, Dropbox, or anything else you might use. Post that and you'll have even better chances of getting help. For simplicity, I'm not going to details on manually pulling logs, however if you're stuck in a bootloop or something like that and can't run the app, use "adb pull /proc/last_kmsg" and post a link to that file.
TL;DR
Sh*t happens, learn to deal with it or go back to stock
Verify your download with an MD5 Checksum
Wipe system in addition to factory reset (dalvik, cache, & data)
Flash ROM and gapps without installing anything else or restoring any data
Pull a log, it's really easy
Now is the best time to make a post about your problem
Radio/Reception Problems on the DNA?
First things first- Double check your settings in Settings > More > Mobile networks. They should be as follows:
Data Enabled: Yes
Data Roaming: No (unless you're actually roaming)
National Data Roaming: Yes (otherwise you'll probably lose data; this won't get you any roaming fees)
Network Mode (Verizon): LTE/CDMA/EvDO (or Global, which is everything, I've never noticed any difference between the two)
Network Mode (GSM): GSM/WCDMA preferred (depending on the ROM, you may also need to flash the GSM patch courtesy of Flyhalf205 from the 2nd post in the original CM10.1 thread.)
System Select/CDMA Roaming: Automatic
CDMA Subscription: RUIM/SIM
GSM users may also need to manually enter APN settings for your carrier to get things like MMS functioning properly. I'm not going to compile a worldwide list, but if Google fails you, your carrier should have support documentation with these settings. Recently, I noticed this file in the android source lists tons of APNs, so try finding your carrier in there too.
Why do I have 0-1 bars? I got a lot more on Sense
Don't be alarmed if your reception looks low/non-existent. Sense "pads" the signal bar to get it to show bars more "accurately," but AOSP does not, so expect a drop in bars. To get an accurate assessment, you want to be looking at your actual signal in dB before trying to diagnose anything by going to Settings > Interface > Status Bar and changing Signal Status Style to Text, and your signal bars will be replaced with a negative number, therefore a value closer to zero indicates a stronger signal. If you don't like negative numbers, another way of thinking about this is as if the phone was telling you how far you are away from the nearest tower. What would normally be 5 bars on Sense equates to -70dB, and 1 bar equates to -115, but these are approximate values and depending on your location and environment, you might bee numbers outside this range.
I'm still having problems
Unfortunately, our phone is known to have problems with reading the SIM card. Some say it's purely software, some say its purely hardware, but I believe it can be either. I'd first suggest giving your SIM card a cleaning by popping it out and gently rubbing the contacts with a clean rubber eraser, another more risky option is a just drop of isopropyl alcohol on a cotton swab. If you have compressed air, you can give that a small blast into the SIM slot from a few inches away. If the phone is still having issues with reading the SIM after that, it might need to be replaced.
Another possibility is issues with the radio firmware. You can try updating the firmware by following the instructions in this post. Personally, I recommend the most recent version, 2.06.605.1. Some users, myself included, have reported that sometimes a full RUU back to 100% stock is necessary to restore proper radio function. Instructions for that can be found here, but be aware that this can be a lengthy, tedious process. You'll end up having to re-unlock and root your phone before you'll be able to flash anything else again, so I only recommend this as a last resort, but is nonetheless something to bear in mind.
Stickie this?
Sent from my HTC6435LVW using Tapatalk 4
I'm going to stick it for now, it's actually good basic info. But I am moving it to the Q&A forum.
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
pyroguysf said:
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
Click to expand...
Click to collapse
Yeah that makes sense, and I was hoping this would also cut down on unnecessary thread starts.
I think what I'll do is have this in both development forums as a sticky, hopefully this will help out some of the chefs.
If you edit one thread, be sure to edit the clone in the other forum.
I am going to let you clean this up as much as possible over the weekend, then maybe move it to the dev threads Monday as a polished product, see if you can get as much info as possible about GSM to include about the signal issues etc.
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
orangekid said:
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
Click to expand...
Click to collapse
I've noticed this, but I made this in hopes of giving people a place to link back to rather than having to waste time typing out the same things over and over, which is why I also put the link in my sig.
orangekid said:
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
Click to expand...
Click to collapse
Good ideas. I'll try to add a section for apps when I get a chance. I tried to briefly touch on the kernel situation by saying to read the OP for recommended settings, but I'll definitely expand on that.
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
pyroguysf said:
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
Click to expand...
Click to collapse
Sounds good.
Moved to dev forum.
If you want to go ahead and create the same thread and copy / paste the first 2 posts, I can sticky it.
Hi all,
I've probably messed up something with my phone and now I can't call: when I try to call a number a black screen appears and it stops there. The phone still works for few minutes and then it freezes and I have to remove the battery.
My phone is a Samsung Galaxy S2 with CyanogenMod 10.1.
I think this problem is related with some app that overwrote something in the phone, maybe after an update that I did 10 days ago. Is there a way to restore the caller application? Maybe installing again the GApps? I don't exactly know what procedure to follow, could somebody help me, please?
Thanks in advance.
First off, I'd just go into Settings / Applications / All and wipe the cache and data of the Dialer and reboot. See if that will help. Then you can try reinstalling the rom and Gapps while just wiping cache and dalvik cache. If that doesn't do it, then wiping everything, including /system might be in order. Make sure you back up your contacts, apps, messages, etc that you want first in case you end up needing to reset completely.
es0tericcha0s said:
First off, I'd just go into Settings / Applications / All and wipe the cache and data of the Dialer and reboot. See if that will help.
Click to expand...
Click to collapse
I really didn't think of that. Thanks!! I'll give it a try :fingers-crossed:
es0tericcha0s said:
Then you can try reinstalling the rom and Gapps while just wiping cache and dalvik cache. If that doesn't do it, then wiping everything, including /system might be in order. Make sure you back up your contacts, apps, messages, etc that you want first in case you end up needing to reset completely.
Click to expand...
Click to collapse
I would like to avoid this... I have both a full nandroid backup and a titanum backup, but it will take some time to reset and check all the phone. I was looking for a solution that let me understand the problem and deal with it the next time.
Anyway... Thanks! :highfive:
EDIT: Find the dialer in cyanogenmod is not trivial
To figure out what the issue is you would need to run a logcat and then recreate the problem.
I've tried to wipe the data of the dialer without luck
I use Contact+ as contact manager and it has its builtin dialer. Usually, after I press the button "call" another application starts, from which I can see the call options, the speakerphone, terminate call button, ... And now it's always black. For this reason I'm not sure what really is the broken app.
es0tericcha0s said:
To figure out what the issue is you would need to run a logcat and then recreate the problem.
Click to expand...
Click to collapse
I've attached the log taken with logcat, it starts when I make the call.
A little update: while trying to make another call I was able to talk and hear the other person, but with the screen always black. After a while I received a message "Phone activity is not responding"
Well, I'm definitely not an expert in reading logcats (trying to get better...) but I see some stuff that seems important... I'm wondering though, have you removed the original Dialer/Phone app and / or are you using only the other app to dial - the one with your 3rd part Contact app manager? From browsing the logcats it seems like it's trying to connect with another app and something is missing and causing everything to fail. This is more of an educated guess at this point, but if that is the case, it might narrow down the issue a bit more. Curious : Why not make a nandroid backup and flash an updated version of the rom? I know there is a slightly newer stable version of CM for the S2...
Oh yea, which S2, by the way? There are quite a few variants of the S2 and some of them are so different that there is no reason they should even be called the S2 (different screens, bodies, processors, etc) so depending which one, there might be a better rom for it.
es0tericcha0s said:
Well, I'm definitely not an expert in reading logcats (trying to get better...) but I see some stuff that seems important... I'm wondering though, have you removed the original Dialer/Phone app and / or are you using only the other app to dial - the one with your 3rd part Contact app manager?
Click to expand...
Click to collapse
I changed dialer a long time ago, I remember I didn't remove the original one. Also searching in the app list I can see an app that looks like the original dialer. I use only the Contact+ dialer but I think it eventually uses the original one.
es0tericcha0s said:
From browsing the logcats it seems like it's trying to connect with another app and something is missing and causing everything to fail. This is more of an educated guess at this point, but if that is the case, it might narrow down the issue a bit more.
Click to expand...
Click to collapse
What lines are you talking about? The only interesting lines I can see are:
W/ActivityManager( 4082): Launch timeout has expired, giving up wake lock!
W/ActivityManager( 4082): Activity idle timeout for ActivityRecord{42229420 u0 com.android.phone/.SipCallOptionHandler}
They look related to the black screen after the call is started.
There is another interesting line
W/dalvikvm(21477): VFY: unable to resolve static method 1599: Landroid/provider/Telephony$Sms;.getDefaultSmsPackage (Landroid/content/ContextLjava/lang/String;
It can be due to a broken davlik cache after I've updated the apps. I've just cleaned the dalvik cache, I'll try if it works later.
I can also see a problem with the RIL:
E/TinyALSA-Audio RIL Interface( 2356): ril_connect() failed
I changed the RIL about one month ago with the app GetRIL (I am aware I should keep the CM one). I don't remember I've had any problems one month ago because I noticed the dialer not working only few days ago.
es0tericcha0s said:
Curious : Why not make a nandroid backup and flash an updated version of the rom? I know there is a slightly newer stable version of CM for the S2...
Click to expand...
Click to collapse
I want to fix the problem to avoid it next time. I prefer not to reset my phone every time there is only 1 thing that doesn't work!
Anyway I have a clean and fully functional rom backup taken about 2 months ago. If everything fails I'll go for that. It's CM 10.1.3 Stable. Or maybe for the new nightly build of CM11, as you suggested! :good:
es0tericcha0s said:
Oh yea, which S2, by the way? There are quite a few variants of the S2 and some of them are so different that there is no reason they should even be called the S2 (different screens, bodies, processors, etc) so depending which one, there might be a better rom for it.
Click to expand...
Click to collapse
System settings -> About phone
Model: GT-I9100
CPU: ARMv7 Processor rev1 (v7l)
Memory: 804 MB
CyanogenMod version: 10.1.3-i9100
Kernel version: 3.10.0-R93-Siyah-Dorimanx-V9.39-JB-SGII-PWR-CORE
And thanks for the help :highfive:
[0m[38;5;40mI/ActivityManager( 4082): Start proc com.contapps.android:ContactActionProcess for broadcast com.contapps.android/.utils.ContactActionReceiver: pid=21477 uid=10006 gids={50006, 3003, 1015, 1028}
[0m[38;5;75mD/Yamaha-MC1N2-Audio( 2356): yamaha_mc1n2_audio_modem_start()
[0m[38;5;75mD/Yamaha-MC1N2-Audio( 2356): yamaha_mc1n2_audio_route_start()
[0m[38;5;75mD/Yamaha-MC1N2-Audio( 2356): (yamaha_mc1n2_audio_params_route_find): device = 2, direction = 2
[0m[38;5;166mW/Trace (21477): error opening trace file: No such file or directory (2)
[0m[38;5;40mI/dalvikvm(21477): Could not find method android.provider.Telephony$Sms.getDefaultSmsPackage, referenced from method com.contapps.android.utils.GlobalUtils.a
[0m[38;5;166mW/dalvikvm(21477): VFY: unable to resolve static method 1599: Landroid/provider/Telephony$Sms;.getDefaultSmsPackage (Landroid/content/ContextLjava/lang/String;
[0m[38;5;75mD/dalvikvm(21477): VFY: replacing opcode 0x71 at 0x00b6
[0m[38;5;40mI/Crashlytics(21477): Initializing Crashlytics 1.1.10.12
[0m[38;5;75mD/TinyALSA-Audio RIL Interface( 2356): audio_ril_interface_open(0x400e9b50, 2, 0x40ffdc54)
[0m[38;5;75mD/TinyALSA-Audio RIL Interface( 2356): audio_ril_interface_set_route(2)
[0m[38;5;196mE/TinyALSA-Audio RIL Interface( 2356): ril_connect() failed
[0m[38;5;75mD/TinyALSA-Audio RIL Interface( 2356): audio_ril_interface_set_voice_volume(2, 1.000000)
[0m[38;5;40mI/dalvikvm(21477): Could not find method android.provider.Telephony$Sms.getDefaultSmsPackage, referenced from method com.contapps.android.ContactsPlusBaseSettings.b
[0m[38;5;166mW/dalvikvm(21477): VFY: unable to resolve static method 1599: Landroid/provider/Telephony$Sms;.getDefaultSmsPackage (Landroid/content/ContextLjava/lang/String;
[0m[38;5;75mD/dalvikvm(21477): VFY: replacing opcode 0x71 at 0x000a
[0m[38;5;40mI/dalvikvm(21477): Could not find method android.graphics.Bitmap.getAllocationByteCount, referenced from method com.contapps.android.utils.ImageCache.a
[0m[38;5;166mW/dalvikvm(21477): VFY: unable to resolve virtual method 927: Landroid/graphics/Bitmap;.getAllocationByteCount ()I
[0m[38;5;75mD/dalvikvm(21477): VFY: replacing opcode 0x6e at 0x001c
[0m[38;5;75mD/ImageCache(21477): Memory cache created (size = 4915)
[0m[38;5;166mW/ContApps(21477): Setting CallReceiver: false
[0m[38;5;40mI/ActivityManager( 4082): No longer want com.skype.raider (pid 21120): empty #17
That stretch right there seems like it is the culprit. Like it's trying to connect to the main dialer action of the phone and fails.
Could not find method android.provider.Telephony$Sms.getDefaultSmsPackage
That shows up twice in connection to the Contact+ app. Then it errors trying to pull something for the bitmap graphics which would probably explain the black screen part. The RIL part might be important as well, but I think the first thing to try might be something other than Contact+...?
As far as roms, I guess 10.1.3 was the last stable one for that. Thought it would have 10.2 If you get adventuresome, you should check out Slim. It's well supported with some nice features but not one of the everything but the kitchen sink type things.
es0tericcha0s said:
That stretch right there seems like it is the culprit. Like it's trying to connect to the main dialer action of the phone and fails.
Could not find method android.provider.Telephony$Sms.getDefaultSmsPackage
That shows up twice in connection to the Contact+ app. Then it errors trying to pull something for the bitmap graphics which would probably explain the black screen part. The RIL part might be important as well, but I think the first thing to try might be something other than Contact+...?
As far as roms, I guess 10.1.3 was the last stable one for that. Thought it would have 10.2 If you get adventuresome, you should check out Slim. It's well supported with some nice features but not one of the everything but the kitchen sink type things.
Click to expand...
Click to collapse
Cleaning the dalvik cache and installing a new dialer () didn't work. About the dialer... well I think the problem is not the dialer: I can dial! The problem is the application that manages the active call. And I don't know how it's called or I would try to clean or reinstall it! Can it be an activity contained in the app called com.android.phone?
Slim looks nice I can try it after I solve this problem!
My first instinct is to blame Contacts+.
I solved the problem, it was the RIL. I changed it to try different settings and in the end I was able to put back the original one.
Many thanks anyway!
I don't know if others are facing the similar problem but it has turned my life into hell after the new update. I will list down the issues on ALL ROMS after the new OOS 3 update with bootloader in my device.
I had issue in accessing storage, which means gallery, file explorer or literally any app crashes when I try to access from the storage, be it internal or external sd card.
Couldn't use the latest snapchat at all, can't post in story, can't save any snap, can't upload from camera roll. It was just a dead end. However I could only post into story with a older Snapchat version, still due to storage access issue, I couldn't save or upload from Camera Roll
Facebook picture upload would ocassionally crash the app.
Couldn't take more than 1 picture in latest youcam app, storage issue would crash the app.
Gallery apps fail to generate thumbnail previews.
All these above problems caused permanent storage access unavailability until I rebooted device.
Need to charge my device twice as Battery runs faster than Usain Bolt.
So finally after a lot of tingling, I finally downgraded my device to OOS 2.1.3 with TWRP 2.8.7. Trust me it's very stable, bug free and battery friendly. Though I miss the new security patches features and snappy feel from Android 6 & 7.
The above problems are not happening in 2.1.3. I can use latest snapchat, youcam & facebook without any issue at all. Is there any way to prevent these issues on new Android OS in my device ? I believe it's not a device issue as 2.1.3 is running very stable and bug less.
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Exodusche said:
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Click to expand...
Click to collapse
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
arafat_mw said:
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
Click to expand...
Click to collapse
Think I figured it out for you. You are on really old OOS2 build you need to flash 2.2.3 before you update to OOS3. It was made for the update to MM.
Are you sure you gave the good permission. On MM, when you first launch an app, it should ask you for it. Maybe a bug appear at one point.
You should go to menu settings / app / 3 dots menu at the top right an reset app prefs.
Then re open app one by one.
You can try first without your SD inside to see if it happens again.
I've been experiencing random freezes that kick in about two or three days after installing a new custom ROM. Freezes occur, followed by FC prompts, which can be "Wait"ed and the app works again, but after a day or two of use, it just becomes painful waiting for the apps to resume or phone to wake up.
In the course of backing-up I've noticed that TWRP Nandroid backups are running into read errors (code 255). These can be fixed by going through the recovery.log and deleting the files that cause errors and rerunning the backup, repeating until all the corrupted files have been deleted. The phone also runs better after these files have been deleted, but it eventually happens again until the phone is almost useless. What is feels like, is old-time Wintel bad hard drive sector errors and it looks like it too when you see these read errors in TWRP, but everyone assures me Nand/Flash drives don't work like that...are there any other possible hardware issues?
The trouble began after I installed the final Resurrection Remix 5.8.5 (5.8.4 bluetooth didn't work properly). I've now tried also Nougat versions of Resurrection, Lineage and Carbon. Can't bear going back to MM but it might be the only solution.
I've followed installation instructions to the T, installing stock ROMs with Flashtool and then installing ROMs as described in OPs. I've tried both Magisk 14 and SuperSU. I've avoided rooting at all. I've Formatted (rather than Wiped in TWRP) everything except the external SD card. I've restored apps through Titanium. I've fresh installed apps from the market. Nothing works. I haven't tried not installing anything but what's the point of a phone with no apps??
I've followed some solutions posted by others with the same problem but not everyone describes their problem all that well but I still run into the issue. BUT, I keep seeing threads that die and no one says they fixed their issue - common but I'm thinking they gave up.
I haven't tried MM, but I might try Oreo first, if it's stable enough to run. Support in ROM forums is pretty thin though nowadays... (check my other posts).
Anyone got thoughts on how changing kernels might help, and which kernel to use for Nougat?