Here's the stock rooted YNG1TAS17L ROM. Includes root(enable in Developer options) and the rest is untouched, so it's OTA update safe
Stock Rooted YNG1TAS17L ROM
md5 - b98a809b18ab26679cffda230ab09f68
YNG1TAS17L Radio, etc - Same as YNG1TAS0YL
md5 - 6d5db5af6c92b814b9a0ebd18341dd8e
F2FS users - Attached zip includes a modified updater-script that needs to be added to the ROM(overwrite updater-script in META-INF\com\google\android folder), which will format the system partition as F2FS. You will also need to overwrite the boot.img with a F2FS compatible one or you can flash it after flashing the ROM
Downloading... I'll make a try on multirom.
Thanks..I like your works!
Thank you for your regular work and effort calkulin !
Sent from my A0001 using XDA Free mobile app
Great job! Thanks
changelog?
what bugs have been fixed
Flypants101010 said:
what bugs have been fixed
Click to expand...
Click to collapse
They fixed the SystemUpdateService wakelock
Added Voice Wakeup
And I imagine a few more things
Thanks @Calkulin..
Looking for email and exchange email apks if anyone has them or has a link thanks.
The radio link seems to be offline mate.
Edit: Its up again.
Thank you for all the hard work mate! Awesome!
Sent from my A0001 using Tapatalk
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Calkulin are you going to work your magic on this release soon?
I dirty flashed today's update over Calkulin's stock, rooted CM12s from the original roll-out and now, when I try to open developer's options in settings I get the "Unfortunately settings have stopped" message. I did install SuperSU when TWRP prompted me and root is working. I tried clearing data in Settings and re-enabled developer's options and it still crashes. Everything else seems to work fine. Fixing permissions didn't help either. Anyone else having this issue? Is there a fix?
Here is the log that appears when I click report:
java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NumberFormatException: Invalid int: "3
"
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2980)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3011)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2394)
at android.app.ActivityThread.access$900(ActivityThread.java:147)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1296)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
Caused by: java.lang.NumberFormatException: Invalid int: "3
"
at java.lang.Integer.invalidInt(Integer.java:138)
at java.lang.Integer.parse(Integer.java:410)
at java.lang.Integer.parseInt(Integer.java:367)
at java.lang.Integer.parseInt(Integer.java:334)
at java.lang.Integer.valueOf(Integer.java:525)
at com.android.settings.DevelopmentSettings.updateRootAccessOptions(DevelopmentSettings.java:733)
at com.android.settings.DevelopmentSettings.updateAllOptions(DevelopmentSettings.java:637)
at com.android.settings.DevelopmentSettings.setPrefsEnabledState(DevelopmentSettings.java:512)
at com.android.settings.DevelopmentSettings.onResume(DevelopmentSettings.java:543)
at android.app.Fragment.performResume(Fragment.java:2096)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:928)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1049)
at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:1879)
at android.app.Activity.performResume(Activity.java:6029)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2969)
... 11 more
ynnek63 said:
I dirty flashed today's update over Calkulin's stock, rooted CM12s from the original roll-out and now, when I try to open developer's options in settings I get the "Unfortunately settings have stopped" message. I did install SuperSU when TWRP prompted me and root is working. I tried clearing data in Settings and re-enabled developer's options and it still crashes. Everything else seems to work fine. Fixing permissions didn't help either. Anyone else having this issue? Is there a fix?
Here is the log that appears when I click report:
java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NumberFormatException: Invalid int: "3
"
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2980)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3011)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2394)
at android.app.ActivityThread.access$900(ActivityThread.java:147)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1296)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
Caused by: java.lang.NumberFormatException: Invalid int: "3
"
at java.lang.Integer.invalidInt(Integer.java:138)
at java.lang.Integer.parse(Integer.java:410)
at java.lang.Integer.parseInt(Integer.java:367)
at java.lang.Integer.parseInt(Integer.java:334)
at java.lang.Integer.valueOf(Integer.java:525)
at com.android.settings.DevelopmentSettings.updateRootAccessOptions(DevelopmentSettings.java:733)
at com.android.settings.DevelopmentSettings.updateAllOptions(DevelopmentSettings.java:637)
at com.android.settings.DevelopmentSettings.setPrefsEnabledState(DevelopmentSettings.java:512)
at com.android.settings.DevelopmentSettings.onResume(DevelopmentSettings.java:543)
at android.app.Fragment.performResume(Fragment.java:2096)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:928)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1049)
at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:1879)
at android.app.Activity.performResume(Activity.java:6029)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2969)
... 11 more
Click to expand...
Click to collapse
why not try a clean instalation? full wipe
ynnek63 said:
I dirty flashed today's update over Calkulin's stock, rooted CM12s from the original roll-out and now, when I try to open developer's options in settings I get the "Unfortunately settings have stopped" message. I did install SuperSU when TWRP prompted me and root is working. I tried clearing data in Settings and re-enabled developer's options and it still crashes. Everything else seems to work fine. Fixing permissions didn't help either. Anyone else having this issue? Is there a fix?
Here is the log that appears when I click report:
java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NumberFormatException: Invalid int: "3
"
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2980)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3011)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2394)
at android.app.ActivityThread.access$900(ActivityThread.java:147)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1296)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
Caused by: java.lang.NumberFormatException: Invalid int: "3
"
at java.lang.Integer.invalidInt(Integer.java:138)
at java.lang.Integer.parse(Integer.java:410)
at java.lang.Integer.parseInt(Integer.java:367)
at java.lang.Integer.parseInt(Integer.java:334)
at java.lang.Integer.valueOf(Integer.java:525)
at com.android.settings.DevelopmentSettings.updateRootAccessOptions(DevelopmentSettings.java:733)
at com.android.settings.DevelopmentSettings.updateAllOptions(DevelopmentSettings.java:637)
at com.android.settings.DevelopmentSettings.setPrefsEnabledState(DevelopmentSettings.java:512)
at com.android.settings.DevelopmentSettings.onResume(DevelopmentSettings.java:543)
at android.app.Fragment.performResume(Fragment.java:2096)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:928)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1049)
at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:1879)
at android.app.Activity.performResume(Activity.java:6029)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2969)
... 11 more
Click to expand...
Click to collapse
I experienced this too, when dirty flashed, root permissions were not found by any app and trying to get into developer options caused a force close. After full wipe and reinstall, root permissions were still not working right out of the box,which was the case on previous release of yours if i remeber right, but i could get into developer options and enable it myself. I was able to hide developer options again without losing root access by cleaning data of settings app.
Th3DaRk_Vampire said:
why not try a clean instalation? full wipe
Click to expand...
Click to collapse
Well, this was a clean install when I flashed COS12 from the original release. Prefer not to have to do that again. But it is an option. Thanks!
RADIO
Hi, thanks for the update i just got it in my phone but i did not try it...
Can i have some informations for the radio thing, cause i don't know what can i do with it ?
Thanks
The radio file link posted here is for the previous version. Kould you note it down in the OP that they are the the same in case there is actually no difference between the two versions.
Or maybe this is a mistake to fix.
ynnek63 said:
Well, this was a clean install when I flashed COS12 from the original release. Prefer not to have to do that again. But it is an option. Thanks!
Click to expand...
Click to collapse
Mine was working fine for couple of days in the previous version before it started doing this FC on Dev ops and then I OTAed to YNG1TAS17L but the issue was still there. Funny thing is that I made a nandroid afterwards did a clean flash of this ROM but the problem didn't go away.
So I tried replacing the boot.img from the signed zip file and removing the SU binary. Rebooted flashed SuperSU but the problem didn't go away. I was thinking isn't there anyway we can completely revert the built-in root? even though what I did above was more or less the same thing
I'm going to try removing the SU binary again and before flashing SuperSU check whether I can access Dev ops or not.
From the error code posted above shouldn't the integer be without quotes .
3 instead of "3"?
Sent from my A0001 using XDA Free mobile app
ynnek63 said:
I dirty flashed today's update over Calkulin's stock, rooted CM12s from the original roll-out and now, when I try to open developer's options in settings I get the "Unfortunately settings have stopped" message. I did install SuperSU when TWRP prompted me and root is working. I tried clearing data in Settings and re-enabled developer's options and it still crashes. Everything else seems to work fine. Fixing permissions didn't help either. Anyone else having this issue? Is there a fix?
Click to expand...
Click to collapse
Flash this and then you'll have to re-enable root in developer options
Am trying to make this rom F2FS in one zip, but cant find boot.img from another LP 5..0.2 F2FS rom, any suggestion? Perhaps anyone has it done already and willing share it? (Which I`d do when I make it)
EDIT: is it enough to flash any F2FS compatible kernel to change the boot.img?
Related
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!
So since installing CM12, I've been running into both "Unfortunately camera has stopped", and "Cannot connect to camera" errors. It's strange because when I flash a fresh install after wiping cache/dalvik/data/system...everything, then boot up, the camera works fine. It's not until a day or two later that I realize it just breaks itself and stops working.
This has happened multiple times now, and what I have to do to temporarily fix is wipe everything (including internal storage and sd card...yes on purpose), and then sideload CM12 and GApps back onto the phone. Once I do this and boot up, again, the camera is working fine...but sure enough a day or two later *poof*, it commits suicide...
This is the runtime exception that is being thrown:
Code:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at android.app.ActivityThread.performLaunchActivity(A ctivityThread.java:2329)
at android.app.ActivityThread.handleLaunchActivity(Ac tivityThread.java:2391)
at android.app.ActivityThread.access$900(ActivityThre ad.java:147)
at android.app.ActivityThread$H.handleMessage(Activit yThread.java:1296)
at android.os.Handler.dispatchMessage(Handler.java:10 2)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.jav a:5256)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(ZygoteInit.java:898)
at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:693)
Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at com.android.camera.one.OneCameraManager.isCamera2S upported(OneCameraManager.java:107)
at com.android.camera.one.OneCameraManager.create(One CameraManager.java:84)
at com.android.camera.one.OneCameraManager.get(OneCam eraManager.java:71)
at com.android.camera.CameraActivity.onCreate(CameraA ctivity.java:1352)
at android.app.Activity.performCreate(Activity.java:5 933)
at android.app.Instrumentation.callActivityOnCreate(I nstrumentation.java:1105)
at android.app.ActivityThread.performLaunchActivity(A ctivityThread.java:2282)
... 10 more
I seem to be the only one facing this issue, and google is no help whatsoever. It can't possibly be hardware related, because each time I wipe internal storage and adb sideload the rom back on, the camera works great...EVERY TIME...and I've done it about 5 times now, but it's getting old, tedious, and inconvenient... Can anyone offer any insight at all, or does anyone have *any* idea what could be causing this?? Thanks in advance, and I appreciate all help...
Are you on the latest TWRP and the latest firmware? People have had that issue and that was the culprit. Read the first few pages of the CM12 thread santod made in the development section.
Sent from my HTC6500LVW using XDA Free mobile app
For anyone who is an avid user of Handcent, the most recent update introduced ads at the top of the message list, effectively "disguised" as the first message in your inbox.
While Handcent has had ads for quite some time, the placement of this particular ad has caused an uproar in the feedback section of the Play Store, and rightfully so.
As a developer, I understand the need for ads to support development (and as such, do not use ad blockers), but this particular style of ad is a bit distasteful for most, requiring not the purchase of a paid version to remove, but rather, an annual ongoing subscription.
So, I first set out to modify the app directly, to see if I could remove JUST this ad, and once I figured it out, figured it made more sense to create as an Xposed module, so that you can continue to receive app updates should they decide to change things. Again, this leaves any other ads (that were already there) untouched. A general ad blocker may or may not address this, but I am not sure, since, as mentioned, I do not use them.
As with all Xposed modules --> install the linked APK --> make the module active --> reboot --> profit.
Note: This module has no front-end UI, so there is nothing to do but install and make active.
Thanks to Rovo89, et al, for the amazing framework.
Download Link --> Xposed Repository - v1.5.1
EDIT: 01-Apr-2015 --> Original Release (v1.0)
EDIT: 02-Apr-2015 --> Updated version for KitKat compatibility (v1.1)
EDIT: 03-Apr-2015 --> Updated version for compatibility with Handcent 6.5.1 (v1.2)
EDIT: 29-Apr-2015 --> Updated version for compatibility with Handcent 6.5.5 (v1.3)
EDIT: 15-May-2015 --> Updated version for compatibility with Handcent 6.5.7 (v1.4)
EDIT: 27-May-2015 --> Updated version for compatibility with Handcent 6.5.9 (v1.5)
EDIT: 31-May-2015 --> Minor update (v1.5.1)
Great idea but the AD keeps popping back up after awhile. But then handcent did update today. So maybe that's why.
DevXen said:
Great idea but the AD keeps popping back up after awhile. But then handcent did update today. So maybe that's why.
Click to expand...
Click to collapse
Hmm, no, I'm on the latest version (6.5) available to me and all running well for the last 48 hours. What version of Android are you running (I'm on LP 5.0.1).
If after installing and rebooting, check to see the module successfully loaded via the Xposed Logs. If so, then a logcat would help during the opening of Handcent. You can send me a PM if you're interested, and I can provide some debug code to use for more verbose logging / output as well.
I'm on Kitkat 4.4.4 - Note Edge - Sprint.
I'm not sure about getting the logcat as he never done that. But I'd assume that would only be good when it actually shows the ad at the top. Which seems to be at least at this point to be random. It's not always there. But sometimes it is.
DevXen said:
I'm on Kitkat 4.4.4 - Note Edge - Sprint.
I'm not sure about getting the logcat as he never done that. But I'd assume that would only be good when it actually shows the ad at the top. Which seems to be at least at this point to be random. It's not always there. But sometimes it is.
Click to expand...
Click to collapse
A logcat would be useful regardless, as when you launch the app and/or navigate in / out of the inbox, it would show any errors the Xposed module may be having in hooking the correct method that gets called. The behavior you are describing is the default / stock behavior they have implemented, which means the module, for you, is not functioning at all.
I may restore KK to my phone this evening to try and test as well.
Also, if you want to test to compare if the issue is related to Xposed, or the mod itself, while on KK, attached is the original Handcent APK I modified while working to determine how to pull this off.
To test, you would need to uninstall your current version of Handcent, as this will not install over top.
If you no longer see the ad in the inbox stream, it would isolate the issue as being related to Xposed on KK versus LP.
EDIT: APK removed as test confirmed issue was with module.
I'm on 4.4 and having the same issue. I tried your apk and the ad disappeared; I then reinstalled from the market and the ad stayed gone until I force closed it and reopened. I'll try to get a logcat when I have a moment.
Sent from my SCH-I535 using XDA Free mobile app
Demonius_Jackson said:
I'm on 4.4 and having the same issue. I tried your apk and the ad disappeared; I then reinstalled from the market and the ad stayed gone until I force closed it and reopened. I'll try to get a logcat when I have a moment.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Perfect, thanks for checking. So this does confirm the technique is good on KK as well, but the module is, for some reason, not hooking correctly to replicate the direct mod.
Also, even before a logcat, can you post the output of your Xposed log when the phone starts up? This will show if the module is successfully loading in the first place.
Thanks.
I hadn't posted previously, but I'm experiencing the same thing. It worked for a bit, then stopped working.
my xposed log shows the following, but I'm always open to the possibility I'm doing something wrong
Code:
Apr 2, 2015 8:24:45 PM UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'KTU84P release-keys' with fingerprint 'htc/sprint_wwe/htc_m8whl:4.4.4/KTU84P/393205.2:user/release-keys'
Loading modules from /data/app/ca.pr0ps.xposed.entrustunblocker-1.apk
Loading class ca.pr0ps.xposed.entrustunblocker.Unblocker
Loading modules from /data/app/com.elesbb.snapchatfullcaption-1.apk
Loading class com.elesbb.snapchatfullcaption.Xposed
Loading modules from /data/app/com.logika.noinboxads-1.apk
Loading class com.logika.noinboxads.MainActivity
java.lang.IllegalAccessError: Class ref in pre-verified class resolved to unexpected implementation
at dalvik.system.DexFile.defineClassNative(Native Method)
at dalvik.system.DexFile.defineClass(DexFile.java:222)
at dalvik.system.DexFile.loadClassBinaryName(DexFile.java:215)
at dalvik.system.DexPathList.findClass(DexPathList.java:322)
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:54)
at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
at de.robv.android.xposed.XposedBridge.loadModule(XposedBridge.java:421)
at de.robv.android.xposed.XposedBridge.loadModules(XposedBridge.java:386)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:120)
at dalvik.system.NativeStart.main(Native Method)
ffttgghh said:
I hadn't posted previously, but I'm experiencing the same thing. It worked for a bit, then stopped working.
Click to expand...
Click to collapse
That's the standard behavior, meaning the module isn't working at all on KK.
ffttgghh said:
my xposed log shows the following, but I'm always open to the possibility I'm doing something wrong
Code:
Apr 2, 2015 8:24:45 PM UTC
Loading Xposed v54 (for Zygote)...
Loading modules from /data/app/com.logika.noinboxads-1.apk
Loading class com.logika.noinboxads.MainActivity
java.lang.IllegalAccessError: Class ref in pre-verified class resolved to unexpected implementation
at dalvik.system.DexFile.defineClassNative(Native Method)
at dalvik.system.DexFile.defineClass(DexFile.java:222)
at dalvik.system.DexFile.loadClassBinaryName(DexFile.java:215)
at dalvik.system.DexPathList.findClass(DexPathList.java:322)
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:54)
at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
at de.robv.android.xposed.XposedBridge.loadModule(XposedBridge.java:421)
at de.robv.android.xposed.XposedBridge.loadModules(XposedBridge.java:386)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:120)
at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
That's the error. It is failing to load all together on the KK version of Xposed. Need to investigate further. Thanks for the logs.
KK Test Build
Okay, KK users, please give the attached test build a try and let me know if it works for you (be sure to first uninstall the current xposed module before installing the attached). The issue should hopefully be fixed.
Once confirmed, I will upload a new version compatible with both KK & LP to the Xposed repository for re-download / installation.
Confirmed. Attachment removed, OP updated with link to new version in Xposed repository.
JsChiSurf said:
Okay, KK users, please give the attached test build a try and let me know if it works for you (be sure to first uninstall the current xposed module before installing the attached). The issue should hopefully be fixed.
Once confirmed, I will upload a new version compatible with both KK & LP to the Xposed repository for re-download / installation.
Click to expand...
Click to collapse
tried it, works fine, no ads, no ads after reboot, no errors in xposed log!
ffttgghh said:
tried it, works fine, no ads, no ads after reboot, no errors in xposed log!
Click to expand...
Click to collapse
Great. Link in OP has been updated to point to updated version (v1.1) in Xposed repo.
JsChiSurf said:
Great. Link in OP has been updated to point to updated version (v1.1) in Xposed repo.
Click to expand...
Click to collapse
Working like a champ now, thanks.
Sent from my SCH-I535 using XDA Free mobile app
Demonius_Jackson said:
Working like a champ now, thanks.
Click to expand...
Click to collapse
Great. Thanks for the confirmation.
Fyi... Handcent just updated again in Google Play to 6.5.1 and it appears to break the functionality of the module (perhaps intended). I had to revert to the last version (6.5.0) in order to get the module working again. Just informing...
PerCompLLC said:
Fyi... Handcent just updated again in Google Play to 6.5.1 and it appears to break the functionality of the module (perhaps intended). I had to revert to the last version (6.5.0) in order to get the module working again. Just informing...
Click to expand...
Click to collapse
That was fast. Thanks for the heads up. Just enough changed to affect functionality. OP has been updated with new version for compatibility with v6.5.1.
Note: New version of module will break backwards compatibility, so do not update module unless updating Handcent as well.
JsChiSurf said:
That was fast. Thanks for the heads up. Just enough changed to affect functionality. OP has been updated with new version for compatibility with v6.5.1.
Note: New version of module will break backwards compatibility, so do not update module unless updating Handcent as well.
Click to expand...
Click to collapse
Thank you so much for the quick response and fix! Works perfectly!
I have yet to update Handcent to 6.5.x cause of this new ad placement (Still on v6.4.9). Might have to update and give this a go. Huge thanks for this!
Hippie459MN said:
I have yet to update Handcent to 6.5.x cause of this new ad placement (Still on v6.4.9). Might have to update and give this a go. Huge thanks for this!
Click to expand...
Click to collapse
Be sure to keep a pre-6.5 backup just in case things change in the future that prevent the module from working for some reason, so you can easily revert if necessary.
After doing so, you should be safe to upgrade and install the module.
My solution: I just flashed a new kernel and it seems like it fixed my problem with the newest Messenger. The kernel I flashed is Thunderstorm. Now I don't have to use the old version anymore
OG POST:
Hello!
First post here, so hoping this is the right place to post.
On to the problem:
I rooted and installed a custom os for my Samsung S7 flat and everything seems to be working fine except for Facebook Messenger. The app won't open and just crashes before even actually opening without any clear error message (Messenger has stopped). Funny thing is that Facebook Messenger Lite works without any problem. I've Googled around a bit and seen that people have the same issue but none of the fixes have worked for me..
I am currently running Black Diamond os (Pie) but I have tried two other os' with the same result.. I have also tried to flash back to stock and then again to custom but that didn't work either.
Other things I've tried:
- Core only mode in Magisk
- Hide messenger in Magisk
- Delete .odex file in data/facebook.ocra folder
- Wipe dalvik, cache etc.
- Uninstall / reinstall messenger
I even tried to debug the log with adb. One thing caught my eye in the log which might explain the crash (I'm not an Android dev tho):
HTML:
AndroidRuntime: java.lang.RuntimeException: Unable to instantiate application com.facebook.messenger.app.MessengerApplication: java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.String.length()' on a null object reference
Anyone have any idea how to fix this? Thanks!
Happens to me as well on the Pixel XL Pie semi-GSI on the Redmi Note 5 Global (whyred).
It's actually a problem in the latest versions of the app, you can revert to an older version from APKMirror and it works just fine...
I haven't been able to figure out the problem either.
xezrunner said:
Happens to me as well on the Pixel XL Pie semi-GSI on the Redmi Note 5 Global (whyred).
It's actually a problem in the latest versions of the app, you can revert to an older version from APKMirror and it works just fine...
I haven't been able to figure out the problem either.
Click to expand...
Click to collapse
Ok thanks! Hopefully they'll fix it soon. I'm gonna try an older version for now and see if it'll work.
Edit: and it indeed did work. Disabled autoupdates so I'll be rolling with this for now!
Hi guys!
I accidently erased all my messages and wanted to do a cloud sync, dont know why I couldn't get it done, so I tried titanium backup to backup the messages but it wasn't able to. Something happened and now the stock app is crashing. I tried installing every existing version of it but the TB backup is a 9.0.0.65 ver which is nonexistent on the internet (the oldest is 9.1.0.69 or something like that) :/ now the cloud sync is blocked and I can't get my head around it. thinking about flashing the rom again. I'm running miui 9 global 7.10.12. here is the log from the crash. please help
EDIT:
maybe installing and older version would help. Any one have one prior to 9.0.0.65??
java.lang.SecurityException: Permission Denial: opening provider com.android.providers.telephony.MmsSmsProvider from ProcessRecord{61117d5 842:com.android.mms/u0a30} (pid=842, uid=10030) that is not exported from uid 1001
at android.os.Parcel.readException(Parcel.java:1683)
at android.os.Parcel.readException(Parcel.java:1636)
at android.app.ActivityManagerProxy.getContentProvider(ActivityManagerNative.java:4237)
at android.app.ActivityThread.acquireProvider(ActivityThread.java:5611)
at android.app.ContextImpl$ApplicationContentResolver.acquireUnstableProvider(ContextImpl.java:2281)
at android.content.ContentResolver.acquireUnstableProvider(ContentResolver.java:1531)
at android.content.ContentResolver.query(ContentResolver.java:516)
at android.content.ContentResolver.query(ContentResolver.java:473)
at com.android.mms.util.SqliteWrapper.query(Unknown Source)
at com.android.mms.data.Conversation.loadThreadsFromCursor(Unknown Source)
at com.android.mms.data.Conversation.cacheAllThreads(Unknown Source)
at com.android.mms.data.Conversation.-wrap2(Unknown Source)
at com.android.mms.data.Conversation$1.run(Unknown Source)
at java.lang.Thread.run(Thread.java:760)
Click to expand...
Click to collapse