Been lurking on here for a while but now I've run into an issue that just straight up boggles me, and I'm not sure what (if any) actions will fix it.
I just recently upgraded my phone from rooted/lagfixed JFD Stock Firmware to JI5, and then subsequently to JI6. Of course I had to de-root and lagfix before I did that. I was able to upgrade to JI5 and JI6 just fine. Everything works great.
Then I put One-Click Lag Fix on.
I can apply the root and all of the fixes. The phone boots back up, and in general works fine. I can also notice an increase in performance. But the drawback is, for some reason I now can no longer have vibrations of any kind. No Haptic Feedback, no vibrate for phone calls or notifications. No vibrations of any kind.
I'm stuck between a rock and a hard place here. I work in a company that would prefer I keep my phone on silent (vibrate) mode, so really I can't be missing that functionality. But I do want to benefit from the OCLF performance boost.
Has anyone else experienced this issue? Any one have ideas of how to fix this?
Here's as much detail as I can give you about the phone:
*Vibrant with 2.1 T959UVJI6 - downloaded from here: forum.xda-developers.com/showthread.php?t=798125&highlight=JI6
*Applied RyanZA OCLF 2.1.2
*Rooted/EXT2 Tools/One-Click Lagfix 2.1+
Hopefully that's enough information. As I said, if I de-lagfix it, the vibration comes back, so there's no doubt that it is directly correlated to OCLF in some way. If there aren't any good options, then I'll probably just de-lagfix and keep it with JI6 stock. At least the GPS works.
One last thing, I also tried the oft mentioned Sound Manager workaround... to no avail.
Thanks to anyone who can help. Sorry for posting a book.
I would like to know also. I was on JI6, and applied the OCLF. I reverted back since I really really, missed vibrations.
I really don't know why that would trigger the vibration to go off. weird.
Yeah, it doesn't make much sense to me either. I know when I did the older Lagfix on JFD my phone vibrated and everything worked fine. I've heard that JI2 is fine too, though I never tried it. I'm hesitant to go back down to JI2 though because from what I heard that requires a flash and re-partition, and I've already had to do that a couple times.
i have the same problem, but i didn't know this was caused by the OCLF.
I had a couple of people mention to me that it was something dealing with a library change that OCLF makes. Not sure if that's true or not. I haven't gotten any answers about what I could do though, so if I don't hear anything soon, I'm just going to de-lagfix it.
I am also having this issue. I went from stock JFD to JI5 and then back to stock JFD to JI6. Vibrate stopped working in JI5 and JI6 when OCLF v2 was applied. Version 1 of the lag fix seems to work fine and the only difference is supposed to be that v1 uses symlinks and v2 use bind mounts.
I have also noticed this in my logcat.
Code:
E/HardwareService( 2288): RuntimeException occured at doCancelVibrateLocked().
W/System.err( 2288): java.lang.RuntimeException: VIBE_E_NOT_INITIALIZED
W/System.err( 2288): at com.immersion.android.ImmVibe.StopAllPlayingEffects(Native Method)
W/System.err( 2288): at com.immersion.android.ImmVibe.stopAllPlayingEffects(ImmVibe.java:323)
W/System.err( 2288): at com.android.server.HardwareService.doCancelVibrateLocked(HardwareService.java:516)
W/System.err( 2288): at com.android.server.HardwareService.vibratePattern(HardwareService.java:350)
W/System.err( 2288): at android.os.Vibrator.vibrate(Vibrator.java:69)
W/System.err( 2288): at com.android.internal.widget.LockPatternView.detectAndAddHit(LockPatternView.java:471)
W/System.err( 2288): at com.android.internal.widget.LockPatternView.onTouchEvent(LockPatternView.java:557)
W/System.err( 2288): at android.view.View.dispatchTouchEvent(View.java:3765)
W/System.err( 2288): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:822)
W/System.err( 2288): at com.android.internal.widget.LinearLayoutWithDefaultTouchRecepient.dispatchTouchEvent(LinearLayoutWithDefaultTouchRecepient.java:54)
W/System.err( 2288): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:822)
W/System.err( 2288): at com.android.internal.widget.LinearLayoutWithDefaultTouchRecepient.dispatchTouchEvent(LinearLayoutWithDefaultTouchRecepient.java:57)
W/System.err( 2288): at com.android.internal.policy.impl.UnlockScreen.dispatchTouchEvent(UnlockScreen.java:376)
W/System.err( 2288): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:822)
W/System.err( 2288): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:822)
W/System.err( 2288): at android.view.ViewRoot.handleMessage(ViewRoot.java:1716)
W/System.err( 2288): at android.os.Handler.dispatchMessage(Handler.java:99)
W/System.err( 2288): at android.os.Looper.loop(Looper.java:123)
W/System.err( 2288): at com.android.server.WindowManagerService$PolicyThread.run(WindowManagerService.java:582)
I have this problem too. I just used Odin to go to the JI6 and I thought it was still laggy especially in Touchdown. Did root and OCLF 2.1 and no longer have vibration. Any news?
Thanks!
fF
I just wiped and installed up to JI6 and after installing oclf I am now without haptic feedback as well. Used the market app to apply the fiix.
You can use the first version and you will have lag fix and also your vibration back.
Sent from my SGH-T959 using XDA App
What first ver are you refering too? Mine happen after I applied lag fix!
Thanks, I've been looking all over for this! Never thought about OCLF because vibration was fine before the update. Undoing V2 now...
I am using JI6 with OCLF v2+ and the haptic feedback is working for me. It didn't work when I left the EXT Size option at the default, but I tried increasing it to about a Gig and it now works fine. I'm not sure if this is why it was fixed, though. Can anyone else try and confirm?
Related
Hi, after installing the latest update, the camera in my X10 does not work. After returning to 2.1 also does not work. After root and uploading the software from Wolf, the camera still does not work. Maybe someone has a fix for the camera? Do you have any suggestions?
radzix said:
Hi, after installing the latest update, the camera in my X10 does not work. After returning to 2.1 also does not work. After root and uploading the software from Wolf, the camera still does not work. Maybe someone has a fix for the camera? Do you have any suggestions?
Click to expand...
Click to collapse
What exactly do you mean "does not work"?
Does it FC? Does it freeze? Any other error message?
Can you post a log?
When I try to use the camera, the phone says that the camera is not available , other apps like camera 360 or viginette also doesn't work, it says An error has occurred ..etc. How i can make log?
radzix said:
When I try to use the camera, the phone says that the camera is not available , other apps like camera 360 or viginette also doesn't work, it says An error has occurred ..etc. How i can make log?
Click to expand...
Click to collapse
Install LogCat from the Market!
Then post the log here.
I suspect you have broken camera drivers.
Some people had the same issue when updating from 1.6->2.1
and if I remember correctly Bin4ry had made a fix.
Hi, Bin4ry fix didn't help im my case. Also after dwongrade to 2.1 it wasn't help me. Any other suggestion? Maybe any 1 have right camcorder driver, that i could replace?
don't know if this is helpfull or if it will work but have you tried repairing your phone with pc companion?
Problem
I think i have the same problem. But i havent downgraded from 2.3.3.
My mobile was in service until today and some hours playing with 2.3.3 i tested the camera and it didnt work.
I have also reseted the phone in SEUS.
It can be beacuse of bad service when they switched the motherboard but i post an log here if you can see if its the drivers,
Sorry for my crappy english!
08-09 18:11:05.349 W/IInputConnectionWrapper(2147): showStatusIcon on inactive InputConnection
08-09 18:11:05.639 D/dalvikvm(1323): GC_CONCURRENT freed 198K, 49% free 3358K/6471K, external 10111K/12159K, paused 2ms+4ms
08-09 18:11:07.819 I/ActivityManager(1151): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10100000 cmp=com.sonyericsson.android.camera/.CameraActivity bnds=[238,431][351,589] } from pid 1151
08-09 18:11:10.911 E/SemcCameraApp(1980): SemcCamera:Open camera device failed: exit.
08-09 18:11:10.969 E/SkLayout_wtle(1980): layout error:106 width:0 ellipsizedWidth:0
08-09 18:11:10.969 E/SkLayout_wtle(1980): layout error:106 width:0 ellipsizedWidth:0
08-09 18:11:10.969 E/SkLayout_wtle(1980): layout error:106 width:0 ellipsizedWidth:0
08-09 18:11:10.969 E/SkLayout_wtle(1980): layout error:106 width:0 ellipsizedWidth:0
08-09 18:11:10.989 E/SkLayout_wtle(1980): layout error:106 width:0 ellipsizedWidth:0
08-09 18:11:17.189 I/InputDispatcher(1151): Dropped event because of pending overdue app switch.
08-09 18:11:17.259 I/InputDispatcher(1151): Dropping event because the pointer is not down.
08-09 18:11:17.269 D/dalvikvm(2147): GC_CONCURRENT freed 733K, 60% free 2860K/7047K, external 2224K/2778K, paused 2ms+3ms
08-09 18:11:18.093 I/ActivityManager(1151): Starting: Intent {
I have a similar problem.
When I open the camera for the first time I get Unknown Error.
After I close it and open it again it works fine.
This is my log file. Maybe someone can see what's up...
i have the same problem :S...i installed wolfs rom yesterday the camera was fine infact its good then before ...but now it keep sayin camera not available or unkown error...but camera 360 is working fine but im wondering why my default camera application is not working ...
need help plz...
I had same problem. Delete all pics and videos from your sd card and it will be sorted.
Sent from my X10i using XDA App
curtis1982 said:
I had same problem. Delete all pics and videos from your sd card and it will be sorted.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
ahan so then Can i put all my pics and videoz back ?...then camera will be oki ?
curtis1982 said:
I had same problem. Delete all pics and videos from your sd card and it will be sorted.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
ahan,If i will delete all pics and videos then camera will be oki?...Can i copy my whole data of memory card and format memory card then restore back to it ?
Hello.can any one reply me back :s...
Sent from my X10i using XDA Premium App
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
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?
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