[Completed] Need help to debug bootloop logcat caused by enabling navbar - XDA Assist

Hi guys
I wanna enable navigation bar on a stock based custom rom.
There are several stock based custom roms (KitKat) for lg optimus g, but they (stock based roms& stock rom) have no problem with navbar.
But on this particular stock based custom rom, you can enable navigation bar with Xposed modules (but I think Xposed itself is a problem.)
& If you enable it with build.prop (qemo.hw.mainkeys=0), strangely you will face bootloop!
I've checked the logcats I guess the difference between a successful boot & navbar enabled boot starts from here:
E/AndroidRuntime( 874): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 874): java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.USER_SWITCHED flg=0x50000010 (has extras) } in com.android.internal.policy.impl.PhoneWindowManage [email protected]
But I don't know what cause this fatal error.
Please check the logcats, & help me to find the related error.
Thanks

Hi,
This is not a Q&A forum. It is more to guide NEW users to the best place on the site for their problem .
Please read the OPENING THREAD and the Second one , too.
Thank you for your attention in this matter.
malybru
Senior Moderator

Related

Converting a Dream ROM for 32B - JACxHERO - can anyone (particularly dazcox51) help?

I'm trying to get JACxHERO 1.1 from over on the Dream boards running on my 32B. So I've been trying to follow the procedure that dazcox51 described in his post below
http://forum.xda-developers.com/showthread.php?t=539052
(for those who can't be bothered to take the jump, it's basically a case of unpacking the boot.img, renaming init.trout.rc to init.sapphire.rc, and then packing it all up again, resigning the update.zip, and flashing)
I've managed to flash, it starts to boot - and then I get a reboot loop.
Logcat shows the following. There's more, but I think the pertinent part is:
Code:
I/SystemServer( 137): Starting NetStat Service.
I/SystemServer( 137): Starting Connectivity Service.
W/dalvikvm( 137): threadid=23: thread exiting with uncaught exception (group=0x4000fe70)
E/AndroidRuntime( 137): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception
E/AndroidRuntime( 137): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 137): java.lang.NullPointerException
E/AndroidRuntime( 137): at android.app.ActivityThread.getProvider(ActivityThread.java:3689)
E/AndroidRuntime( 137): at android.app.ActivityThread.acquireProvider(ActivityThread.java:3718)
E/AndroidRuntime( 137): at android.app.ApplicationContext$ApplicationContentResolver.acquireProvider(ApplicationContext.java:1473)
E/AndroidRuntime( 137): at android.content.ContentResolver.acquireProvider(ContentResolver.java:576)
E/AndroidRuntime( 137): at android.content.ContentResolver.query(ContentResolver.java:144)
E/AndroidRuntime( 137): at android.provider.Settings$NameValueCache.getString(Settings.java:472)
E/AndroidRuntime( 137): at android.provider.Settings$Secure.getString(Settings.java:1759)
E/AndroidRuntime( 137): at android.provider.Settings$Secure.getInt(Settings.java:1799)
E/AndroidRuntime( 137): at com.android.server.ConnectivityService.getPersistedNetworkPreference(ConnectivityService.java:186)
E/AndroidRuntime( 137): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:127)
E/AndroidRuntime( 137): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:51)
E/AndroidRuntime( 137): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:91)
Does anyone have any bright ideas?
There is more, but unfortunately the board won't let me post it. I'll put it in a second post, just in case it's relevant.
It's not letting me post the entire logcat, it tells me the post is too long. I'm pretty sure I've got the relevant bit. If anyone wants the whole thing, drop me a PM and I'll mail it. To be it looks network related but must confess I'm just fumbling around here.
Just out of curiosity, I flashed the original Dream ROM without changing it. I got the same reboot loop so I think I'm missing something fundamental and/or obvious.
Am no geewiz as this stuff but have you tried using the kernel from the existing hero roms and use it for the jacxhero port?
If its happening even with an untouched download i think you downliad is bad.
If your on osx did you replace cpio maybe that codrupted some files?
Ive tried all the drizzy/jacxhero releases with no issues
bhav007 said:
Am no geewiz as this stuff but have you tried using the kernel from the existing hero roms and use it for the jacxhero port?
Click to expand...
Click to collapse
I think I will try that as an experiment, but I don't really want to do that as a "release" ROM, as the whole point of this is to see if we can get a decent Compcached version of Hero running on the Magic. If I just whack in (for example) Qtek's boot.img I suspect that, if it worked, we'd end up with a ROM that has the same shortcomings (i.e. unreliable texts due to memory shortages, and a kernel that runs Compcache slower than a swap!).
dazcox5181 said:
If its happening even with an untouched download i think you downliad is bad.
If your on osx did you replace cpio maybe that codrupted some files?
Ive tried all the drizzy/jacxhero releases with no issues
Click to expand...
Click to collapse
Yep, on OSX but did replace cpio. Brand new SD card, 8Gb class 6, partitioned with the latest Amon Ra recovery image.
Will try a new download but I'd be surprised if it was that, because I can unzip/rezip it all just fine.
I don't believe this - it looks like it's my new SD card. Qtek's ordinarily working ROM dies with the same error (albeit before it gets to the Hero loading screen) if I try to boot it with that card in. Have tried with a single fat32 partition and also with the usual three partitioned fat32/ext2/swap scenario.
The card seems to work fine plugged into my Mac and also from within the recovery image on the Magic. I think I'll start a new thread on this as it has naff all to do with JACxHERO it seems.

[Q] Why the phone always restart?

Hello, everybody. I am a developer from Giayee ( Android Phone OEM/ODM ). We are now designed an android phone for a client. I come accross a difficult problem during developing. Our phone always restart from android logo after running for a few hours. And the log is:
E/dalvikvm-heap( 933): 28900-byte external allocation too large for this processE/ ( 933): VM won't let us allocate 28900 bytes
D/skia ( 933): --- decoder->decode returned false
...
E/AndroidRuntime( 933): android.view.InflateException: Binary XML file line #123: Error inflating class java.lang.reflect.Constructor
...
Please help me analyze this log. Thanks! Waiting for your answers, thanks!!!
First things first:
-hardware of the phone?
-which firmware version are you running?
Are you using modded rom?
Regards

[Xposed]Workaround for Netflix on CM10/CM10.1 for Dinc (and maybe 4.1/4.2 in general)

Well, thanks to Entropy512's help, I was able to modify his Xposed hack to work on CM10 (based on Android 4.1) and CM10.1 (based on Android 4.2) for the Incredible. Using the newest Netflix app and it's working well without issue. It's easy to install. You just need two files:
Xposed Installer:
https://www.dropbox.com/s/c57cbz2pjoayj4l/XposedInstaller_2.1.3.apk
XposedCM10-10.1 Netflix Hack:
https://www.dropbox.com/s/d5ifqqwh0zylj5g/XposedCM10-10.1NetflixWorkaround-Dinc.apk
In order to install:
1. Download both files to the root directory of your SD Card. Install the Xposed Installer apk
2. Once Installed, open it up. Press the Install/Update button to install the Xposed Framework. Allow Superuser Permissions. Once it's done, reboot.
3. Install the Xposed Netflix Workaround apk.
4. Open up the Xposed Installer and select the Modules button. You should see the Xposed Netflix Workaround option. Tap the checkbox. Reboot.
5. Open up Netflix. Enjoy.
The background of the app will be white, which is weird, but video will work.
Tested on Tiny's CM10 and CM10.1 ROM, as well as Neo's Infection CM10.1 ROM. Also tested on Zach's P.A.C.Man [Paranoid+AOKP+CM10] ROM. I don't see why it wouldn't work on other ROMs based on Jelly Bean, but I can't guarantee that it will unless other testers come forward.
We have proof now that this can indeed work on other devices, such as the Nook Color. If the original workaround doesn't work, this might be the ticket, since it's more compatible with older devices. Again, I cannot guarantee that this will work and I cannot test this on other devices, but you have nothing to lose by trying. If it doesn't work, simply follow the directions above in reverse.
About 95% of the credit goes to Entropy512, so be sure to thank him in this thread:
http://forum.xda-developers.com/showthread.php?t=2101525
Re: [Xposed]Workaround for Netflix on CM10.1 for Dinc (and maybe Android 4.2 in gener
Works great!
Can finally use the latest version. Thank you both for your hard work.
Question will this work on future releases?
Sent from my NookColor using xda app-developers app
It should work fine. The biggest reason it won't work without the workaround is that the Netflix app detects JB and uses a different player. Our devices simply aren't compatible with that player because the devices are older and the kernels simply don't support the drivers necessary for it to work. They weren't originally meant to run JB. The workaround should work fine as long as they don't change anything drastic and the app supports Gingerbread, which it should for a long while.
Can confirm that since the recent update. Netflix still works fine with the workaround.
Well, after messing with CM10 for a bit, I noticed that the workaround.apk isn't compatible with Jelly Bean 4.1, which can be a bummer for some. I've modified it to work on both CM10 and CM10.1 (4.1 and 4.2 respectively).
Running Tiny's CM10.1 build date 3/29/2013
Love this ability this mod provides, as I've seriously been missing Netflix.
Running into a bit of a problem with another of my apps, however. It manifests when the Netflix Workaround module is activated in Xposed. If the module is unchecked, the app launches fine. It isn't the end of the world, but given the lower performance as the OS stabilizes I'd love to figure out a way to get things working concurrently.
Here is the relevant logcat for trying to launch the app when the module is activated:
Code:
I/ActivityManager(23802): Start proc jp.gungho.padEN for activity jp.gungho.padEN/.AppDelegate: pid=25568 uid=10060 gids={50060, 3003, 1015, 1028}
E/Trace (25568): error opening trace file: No such file or directory (2)
D/dalvikvm(25568): Trying to load lib /mnt/asec/jp.gungho.padEN-2/lib/libopenal.so 0x41c418a8
D/dalvikvm(25568): Added shared lib /mnt/asec/jp.gungho.padEN-2/lib/libopenal.so 0x41c418a8
D/dalvikvm(25568): Trying to load lib /mnt/asec/jp.gungho.padEN-2/lib/libpad.so 0x41c418a8
D/Xposed (25582): Starting Xposed binary version 32, compiled for SDK 17
D/Xposed (25582): Phone: ADR6300 (HTC), Android version 4.2.2 (SDK 17)
D/Xposed (25582): ROM: cm_inc-userdebug 4.2.2 JDQ39 eng.drew.20130329.203232 test-keys
I/Xposed (25582): -----------------
I/Xposed (25582): Added Xposed (/data/xposed/XposedBridge.jar) to CLASSPATH.
D/AndroidRuntime(25582):
D/AndroidRuntime(25582): >>>>>> AndroidRuntime START de.robv.android.xposed.XposedBridge <<<<<<
D/AndroidRuntime(25582): CheckJNI is OFF
D/dalvikvm(25582): Trying to load lib libjavacore.so 0x0
D/dalvikvm(25582): Added shared lib libjavacore.so 0x0
D/dalvikvm(25582): Trying to load lib libnativehelper.so 0x0
D/dalvikvm(25582): Added shared lib libnativehelper.so 0x0
I/Xposed (25582): Found Xposed class 'de/robv/android/xposed/XposedBridge', now initializing
I/Xposed (25582): -----------------
I/Xposed (25582): Apr 26, 2013 8:51:11 PM UTC
I/Xposed (25582): Loading Xposed (for com.android.commands.pm.Pm)...
I/Xposed (25582): Loading modules from /data/app/edu.cornell.atd7.xposedcm101netflixworkaround-1.apk
I/Xposed (25582): Loading class edu.cornell.atd7.netflixcm101fix.CM101NetflixPatcher
D/AndroidRuntime(25582): Calling main entry com.android.commands.pm.Pm
D/dalvikvm(25582): Note: class Landroid/app/ActivityManagerNative; has 157 unimplemented (abstract) methods
D/AndroidRuntime(25582): Shutting down VM
W/dalvikvm(25582): threadid=1: thread exiting with uncaught exception (group=0x417a2930)
E/AndroidRuntime(25582): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime(25582): java.lang.SecurityException: 25582 does not have permission:android.permission.CLEAR_APP_USER_DATA to clear datafor process:edu.cornell.atd7.xposedcm101netflixworkaround
E/AndroidRuntime(25582): at android.os.Parcel.readException(Parcel.java:1425)
E/AndroidRuntime(25582): at android.os.Parcel.readException(Parcel.java:1379)
E/AndroidRuntime(25582): at android.app.ActivityManagerProxy.clearApplicationUserData(ActivityManagerNative.java:3112)
E/AndroidRuntime(25582): at com.android.commands.pm.Pm.runClear(Pm.java:1156)
E/AndroidRuntime(25582): at com.android.commands.pm.Pm.run(Pm.java:119)
E/AndroidRuntime(25582): at com.android.commands.pm.Pm.main(Pm.java:77)
E/AndroidRuntime(25582): at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
E/AndroidRuntime(25582): at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
E/AndroidRuntime(25582): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:108)
E/AndroidRuntime(25582): at dalvik.system.NativeStart.main(Native Method)
E/JavaBinder(25582): Unknown binder error code. 0xfffffff7
D/dalvikvm(23972): GC_CONCURRENT freed 384K, 65% free 2701K/7712K, paused 5ms+4ms, total 110ms
E/AndroidRuntime(25582): Error reporting crash
E/AndroidRuntime(25582): android.os.RemoteException: Unknown binder error code. 0xfffffff7
E/AndroidRuntime(25582): at android.os.BinderProxy.transact(Native Method)
E/AndroidRuntime(25582): at android.app.ActivityManagerProxy.handleApplicationCrash(ActivityManagerNative.java:3341)
E/AndroidRuntime(25582): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime(25582): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
E/AndroidRuntime(25582): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
E/AndroidRuntime(25582): at dalvik.system.NativeStart.main(Native Method)
I/Process (25582): Sending signal. PID: 25582 SIG: 9
I/ActivityManager(23802): Process jp.gungho.padEN (pid 25568) has died.
D/dalvikvm(25592): Late-enabling CheckJNI
D/Zygote (23588): Process 25568 exited cleanly (1)
I/ActivityManager(23802): Start proc jp.gungho.padEN for activity jp.gungho.padEN/.AppDelegate: pid=25592 uid=10060 gids={50060, 3003, 1015, 1028}
E/Trace (25592): error opening trace file: No such file or directory (2)
D/dalvikvm(25592): Trying to load lib /mnt/asec/jp.gungho.padEN-2/lib/libopenal.so 0x41c42708
D/dalvikvm(25592): Added shared lib /mnt/asec/jp.gungho.padEN-2/lib/libopenal.so 0x41c42708
D/dalvikvm(25592): Trying to load lib /mnt/asec/jp.gungho.padEN-2/lib/libpad.so 0x41c42708
D/Xposed (25606): Starting Xposed binary version 32, compiled for SDK 17
D/Xposed (25606): Phone: ADR6300 (HTC), Android version 4.2.2 (SDK 17)
D/Xposed (25606): ROM: cm_inc-userdebug 4.2.2 JDQ39 eng.drew.20130329.203232 test-keys
I/Xposed (25606): -----------------
I/Xposed (25606): Added Xposed (/data/xposed/XposedBridge.jar) to CLASSPATH.
D/AndroidRuntime(25606):
D/AndroidRuntime(25606): >>>>>> AndroidRuntime START de.robv.android.xposed.XposedBridge <<<<<<
D/AndroidRuntime(25606): CheckJNI is OFF
D/dalvikvm(25606): Trying to load lib libjavacore.so 0x0
D/dalvikvm(25606): Added shared lib libjavacore.so 0x0
D/dalvikvm(25606): Trying to load lib libnativehelper.so 0x0
D/dalvikvm(25606): Added shared lib libnativehelper.so 0x0
I/Xposed (25606): Found Xposed class 'de/robv/android/xposed/XposedBridge', now initializing
I/Xposed (25606): -----------------
I/Xposed (25606): Apr 26, 2013 8:51:12 PM UTC
I/Xposed (25606): Loading Xposed (for com.android.commands.pm.Pm)...
I/Xposed (25606): Loading modules from /data/app/edu.cornell.atd7.xposedcm101netflixworkaround-1.apk
I/Xposed (25606): Loading class edu.cornell.atd7.netflixcm101fix.CM101NetflixPatcher
D/AndroidRuntime(25606): Calling main entry com.android.commands.pm.Pm
D/dalvikvm(25606): Note: class Landroid/app/ActivityManagerNative; has 157 unimplemented (abstract) methods
D/AndroidRuntime(25606): Shutting down VM
W/dalvikvm(25606): threadid=1: thread exiting with uncaught exception (group=0x41bbb930)
E/JavaBinder(25606): Unknown binder error code. 0xfffffff7
E/AndroidRuntime(25606): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime(25606): java.lang.SecurityException: 25606 does not have permission:android.permission.CLEAR_APP_USER_DATA to clear datafor process:edu.cornell.atd7.xposedcm101netflixworkaround
E/AndroidRuntime(25606): at android.os.Parcel.readException(Parcel.java:1425)
E/AndroidRuntime(25606): at android.os.Parcel.readException(Parcel.java:1379)
E/AndroidRuntime(25606): at android.app.ActivityManagerProxy.clearApplicationUserData(ActivityManagerNative.java:3112)
E/AndroidRuntime(25606): at com.android.commands.pm.Pm.runClear(Pm.java:1156)
E/AndroidRuntime(25606): at com.android.commands.pm.Pm.run(Pm.java:119)
E/AndroidRuntime(25606): at com.android.commands.pm.Pm.main(Pm.java:77)
E/AndroidRuntime(25606): at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
E/AndroidRuntime(25606): at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
E/AndroidRuntime(25606): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:108)
E/AndroidRuntime(25606): at dalvik.system.NativeStart.main(Native Method)
I/Process (25606): Sending signal. PID: 25606 SIG: 9
E/AndroidRuntime(25606): Error reporting crash
E/AndroidRuntime(25606): android.os.RemoteException: Unknown binder error code. 0xfffffff7
E/AndroidRuntime(25606): at android.os.BinderProxy.transact(Native Method)
E/AndroidRuntime(25606): at android.app.ActivityManagerProxy.handleApplicationCrash(ActivityManagerNative.java:3341)
E/AndroidRuntime(25606): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime(25606): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
E/AndroidRuntime(25606): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
E/AndroidRuntime(25606): at dalvik.system.NativeStart.main(Native Method)
I/ActivityManager(23802): Process jp.gungho.padEN (pid 25592) has died.
D/dalvikvm(25616): Late-enabling CheckJNI
D/Zygote (23588): Process 25592 exited cleanly (1)
Which app is giving you problems? I have heard of Power Amp becoming problematic with someone using the original exposed hack, but I haven't had any problems like that here. Well, so far anyway.
ZOPO zp950 (not plus or H)
First of all: Thank You for your hard work everyone!
The ZOPO zp950 (not plus or H) people have been dying for this fix.
It worked for me. I don't know if it will work on stock rom because I have this rom from www.needrom.com.
Link to ROM Page ===> http://www.needrom.com/mobile/zopo-zp950-5/#comment-3913
I'll be linking to this thread from the zp950 thread.
Again, Thanks a Ton,
Shinguki
Kaepernick said:
Well, thanks to Entropy512's help, I was able to modify his Xposed hack to work on CM10 (based on Android 4.1) and CM10.1 (based on Android 4.2) for the Incredible. Using the newest Netflix app and it's working well without issue. It's easy to install. You just need two files:
Xposed Installer:
https://www.dropbox.com/s/c57cbz2pjoayj4l/XposedInstaller_2.1.3.apk
XposedCM10-10.1 Netflix Hack:
https://www.dropbox.com/s/d5ifqqwh0zylj5g/XposedCM10-10.1NetflixWorkaround-Dinc.apk
In order to install:
1. Download both files to the root directory of your SD Card. Install the Xposed Installer apk
2. Once Installed, open it up. Press the Install/Update button to install the Xposed Framework. Allow Superuser Permissions. Once it's done, reboot.
3. Install the Xposed Netflix Workaround apk.
4. Open up the Xposed Installer and select the Modules button. You should see the Xposed Netflix Workaround option. Tap the checkbox. Reboot.
5. Open up Netflix. Enjoy.
The background of the app will be white, which is weird, but video will work.
Tested on Tiny's CM10 and CM10.1 ROM, as well as Neo's Infection CM10.1 ROM. Also tested on Zach's P.A.C.Man [Paranoid+AOKP+CM10] ROM. I don't see why it wouldn't work on other ROMs based on Jelly Bean, but I can't guarantee that it will unless other testers come forward.
We have proof now that this can indeed work on other devices, such as the Nook Color. If the original workaround doesn't work, this might be the ticket, since it's more compatible with older devices. Again, I cannot guarantee that this will work and I cannot test this on other devices, but you have nothing to lose by trying. If it doesn't work, simply follow the directions above in reverse.
About 95% of the credit goes to Entropy512, so be sure to thank him in this thread:
http://forum.xda-developers.com/showthread.php?t=2101525
Click to expand...
Click to collapse
Kaepernick said:
Which app is giving you problems? I have heard of Power Amp becoming problematic with someone using the original exposed hack, but I haven't had any problems like that here. Well, so far anyway.
Click to expand...
Click to collapse
Whoops, sorry, thought I had mentioned it in my original post. It's a game, called Puzzle and Dragon. For whatever reason, it just sits at the app loading screen, with the requisite ADB output in my original post (the relevant bit seeming to be "E/AndroidRuntime(25582): java.lang.SecurityException: 25582 does not have permission:android.permission.CLEAR_APP_USER_DATA to clear datafor process:edu.cornell.atd7.xposedcm101netflixworkaround")
I was able to figure out a workaround; evidently it's just unhappy running off the SDCard with the workaround installed; moving the app back into main phone memory fixed the problem.
Thanks again for the work ya did on this mod! Loving Netflix again.
Just recreated your issue and yeah, it has a problem working from the sd card with the workaround activated. Not sure why exactly. There may not be anything I can do, but I'll check into it. This sounds similar to that Power Amp issue that someone had and I don't know if even Entropy can fix it. Glad you found a workaround though.
works great
Kaepernick said:
Well, thanks to Entropy512's help, I was able to modify his Xposed hack to work on CM10 (based on Android 4.1) and CM10.1 (based on Android 4.2) for the Incredible. Using the newest Netflix app and it's working well without issue. It's easy to install. You just need two files:
Xposed Installer:
https://www.dropbox.com/s/c57cbz2pjoayj4l/XposedInstaller_2.1.3.apk
XposedCM10-10.1 Netflix Hack:
https://www.dropbox.com/s/d5ifqqwh0zylj5g/XposedCM10-10.1NetflixWorkaround-Dinc.apk
In order to install:
1. Download both files to the root directory of your SD Card. Install the Xposed Installer apk
2. Once Installed, open it up. Press the Install/Update button to install the Xposed Framework. Allow Superuser Permissions. Once it's done, reboot.
3. Install the Xposed Netflix Workaround apk.
4. Open up the Xposed Installer and select the Modules button. You should see the Xposed Netflix Workaround option. Tap the checkbox. Reboot.
5. Open up Netflix. Enjoy.
The background of the app will be white, which is weird, but video will work.
Tested on Tiny's CM10 and CM10.1 ROM, as well as Neo's Infection CM10.1 ROM. Also tested on Zach's P.A.C.Man [Paranoid+AOKP+CM10] ROM. I don't see why it wouldn't work on other ROMs based on Jelly Bean, but I can't guarantee that it will unless other testers come forward.
We have proof now that this can indeed work on other devices, such as the Nook Color. If the original workaround doesn't work, this might be the ticket, since it's more compatible with older devices. Again, I cannot guarantee that this will work and I cannot test this on other devices, but you have nothing to lose by trying. If it doesn't work, simply follow the directions above in reverse.
About 95% of the credit goes to Entropy512, so be sure to thank him in this thread:
http://forum.xda-developers.com/showthread.php?t=2101525
Click to expand...
Click to collapse
Works great for my Atrix 4g 4.1.2
Thanks, this works on the Rikomagic MK802 IV
Tried this with Samsung Galaxy S3 + CM10.1 nightly (2013-06-22) + Netflix 2.3.2 and its not working.
Should I use an older version of Netflix?
Success!
After months and months being deprived of portable Netflix,
I stumbled upon this thread and this method worked absolutely perfectly for me!
Running:
Samsung Galaxy SII [Sprint] Epic 4G Touch
ver 4.2.2 | PACman v23.0.0 | All-In-One | PA-3.6 | AOKP-MR1 | CM10.1
:good: Thank you, sir(s). :good:
Kaepernick said:
Well, thanks to Entropy512's help, I was able to modify his Xposed hack to work on CM10 (based on Android 4.1) and CM10.1 (based on Android 4.2) for the Incredible. Using the newest Netflix app and it's working well without issue. It's easy to install. You just need two files:
Xposed Installer:
https://www.dropbox.com/s/c57cbz2pjoayj4l/XposedInstaller_2.1.3.apk
XposedCM10-10.1 Netflix Hack:
https://www.dropbox.com/s/d5ifqqwh0zylj5g/XposedCM10-10.1NetflixWorkaround-Dinc.apk
In order to install:
1. Download both files to the root directory of your SD Card. Install the Xposed Installer apk
2. Once Installed, open it up. Press the Install/Update button to install the Xposed Framework. Allow Superuser Permissions. Once it's done, reboot.
3. Install the Xposed Netflix Workaround apk.
4. Open up the Xposed Installer and select the Modules button. You should see the Xposed Netflix Workaround option. Tap the checkbox. Reboot.
5. Open up Netflix. Enjoy.
The background of the app will be white, which is weird, but video will work.
Tested on Tiny's CM10 and CM10.1 ROM, as well as Neo's Infection CM10.1 ROM. Also tested on Zach's P.A.C.Man [Paranoid+AOKP+CM10] ROM. I don't see why it wouldn't work on other ROMs based on Jelly Bean, but I can't guarantee that it will unless other testers come forward.
We have proof now that this can indeed work on other devices, such as the Nook Color. If the original workaround doesn't work, this might be the ticket, since it's more compatible with older devices. Again, I cannot guarantee that this will work and I cannot test this on other devices, but you have nothing to lose by trying. If it doesn't work, simply follow the directions above in reverse.
About 95% of the credit goes to Entropy512, so be sure to thank him in this thread:
http://forum.xda-developers.com/showthread.php?t=2101525
Click to expand...
Click to collapse
Something is wrong
Hello!!
I installed Xposed. After i'd update it, i rebooted my tablet. And now it's just stuck when i start it up. I cannot unluck it or anything, it doesn't happen anything.
I have a chuwi v88 on JB OMA 4.2.2 SDK2.0 v4.2
Not working
Tried this on the T-mobile Note 2 and now I am stuck on the boot loader.
I am using the MIUI Rom with Jelly Bean 4.2.2
Works like a charm
I felt the need to register and post something, i hated Netflix so much (never worked), but now i finally can watch some movies. Thanks!
Kaepernick said:
Well, thanks to Entropy512's help, I was able to modify his Xposed hack to work on CM10 (based on Android 4.1) and CM10.1 (based on Android 4.2) for the Incredible. Using the newest Netflix app and it's working well without issue. It's easy to install. You just need two files:
Xposed Installer:
https://www.dropbox.com/s/c57cbz2pjoayj4l/XposedInstaller_2.1.3.apk
XposedCM10-10.1 Netflix Hack:
https://www.dropbox.com/s/d5ifqqwh0zylj5g/XposedCM10-10.1NetflixWorkaround-Dinc.apk
In order to install:
1. Download both files to the root directory of your SD Card. Install the Xposed Installer apk
2. Once Installed, open it up. Press the Install/Update button to install the Xposed Framework. Allow Superuser Permissions. Once it's done, reboot.
3. Install the Xposed Netflix Workaround apk.
4. Open up the Xposed Installer and select the Modules button. You should see the Xposed Netflix Workaround option. Tap the checkbox. Reboot.
5. Open up Netflix. Enjoy.
The background of the app will be white, which is weird, but video will work.
Tested on Tiny's CM10 and CM10.1 ROM, as well as Neo's Infection CM10.1 ROM. Also tested on Zach's P.A.C.Man [Paranoid+AOKP+CM10] ROM. I don't see why it wouldn't work on other ROMs based on Jelly Bean, but I can't guarantee that it will unless other testers come forward.
We have proof now that this can indeed work on other devices, such as the Nook Color. If the original workaround doesn't work, this might be the ticket, since it's more compatible with older devices. Again, I cannot guarantee that this will work and I cannot test this on other devices, but you have nothing to lose by trying. If it doesn't work, simply follow the directions above in reverse.
About 95% of the credit goes to Entropy512, so be sure to thank him in this thread:
http://forum.xda-developers.com/showthread.php?t=2101525
Click to expand...
Click to collapse
:good:
This one absolutely works perfect. Thank you.
Reporting in that this worked on my Nook Color running CM10.1 stable. Needed a recent APK for Netflix so I could have Chromecast support. This worked flawlessly.
like to put post of Nook Color forum
Kaepernick said:
Well, thanks to Entropy512's help, I was able to modify his Xposed hack to work on CM10 (based on Android 4.1) and CM10.1 (based on Android 4.2) for the Incredible. Using the newest Netflix app and it's working well without issue. It's easy to install. You just need two files:
Xposed Installer:
https://www.dropbox.com/s/c57cbz2pjoayj4l/XposedInstaller_2.1.3.apk
XposedCM10-10.1 Netflix Hack:
https://www.dropbox.com/s/d5ifqqwh0zylj5g/XposedCM10-10.1NetflixWorkaround-Dinc.apk
In order to install:
1. Download both files to the root directory of your SD Card. Install the Xposed Installer apk
2. Once Installed, open it up. Press the Install/Update button to install the Xposed Framework. Allow Superuser Permissions. Once it's done, reboot.
3. Install the Xposed Netflix Workaround apk.
4. Open up the Xposed Installer and select the Modules button. You should see the Xposed Netflix Workaround option. Tap the checkbox. Reboot.
5. Open up Netflix. Enjoy.
The background of the app will be white, which is weird, but video will work.
Tested on Tiny's CM10 and CM10.1 ROM, as well as Neo's Infection CM10.1 ROM. Also tested on Zach's P.A.C.Man [Paranoid+AOKP+CM10] ROM. I don't see why it wouldn't work on other ROMs based on Jelly Bean, but I can't guarantee that it will unless other testers come forward.
We have proof now that this can indeed work on other devices, such as the Nook Color. If the original workaround doesn't work, this might be the ticket, since it's more compatible with older devices. Again, I cannot guarantee that this will work and I cannot test this on other devices, but you have nothing to lose by trying. If it doesn't work, simply follow the directions above in reverse.
About 95% of the credit goes to Entropy512, so be sure to thank him in this thread:
http://forum.xda-developers.com/showthread.php?t=2101525
Click to expand...
Click to collapse
Would you mind my putting up a post with link to this on the Nook Color forum. having the same problem there and this works great. Even better is then running Liquid64's zip to make it persist past updating nightly rom. Will of course give you, Entropy512 and Liquid64 the credit. Just want to help others find the Info.

[Completed] The new Pixel Launcher crashing on 5.0.2

I've got a problem with the new pixel launcher, whenever i launch it it will immediately crash and delete default launcher preferences. I pluged the phone to my computer and try to launch it with android monitor in andoid studio. I get the following error:
Code:
E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.google.android.apps.nexuslauncher, PID: 6087
java.lang.NoSuchMethodError: No virtual method getColor(I)I in class Lcom/android/launcher3/Launcher; or its super classes (declaration of 'com.android.launcher3.Launcher' appears in /data/app/com.google.android.apps.nexuslauncher-1/base.apk)
at com.android.launcher3.allapps.AllAppsTransitionController.<init>()
at com.android.launcher3.Launcher.onCreate()
at android.app.Activity.performCreate(Activity.java:5976)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1105)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2251)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2358)
at android.app.ActivityThread.access$800(ActivityThread.java:144)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1278)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5219)
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)
Any idea how to fix this?
The Pixel Launcher will only work on Android 6.0+ devices
Trafalgar Square said:
The Pixel Launcher will only work on Android 6.0+ devices
Click to expand...
Click to collapse
I used to have CM 12.1 and it worked
I have checked again and every site says that Google Pixel Launcher needs Android 6.0.
So, I can't help you. You may ask here:
http://forum.xda-developers.com/android/help

cannot set lock screen pin, pattern or password on my samsung galaxy tab

hello guys
so i started flashing custom roms on my samsung galaxy tab s6 lite with lineage 17, 18, gsi and after that I noticed that the I cannot set a PATTERN, PIN, PASSWORD screenlock except for swipe. so what I did was a clean flash of the STOCK ROM through odin with relocked bootloader but the problem still persists where I cannot set any screenlock type except swipe and none. last thing to do was log it. so here are some logs. do you guys know a way to fix this?
Code:
2021-12-12 08:36:24.725 4657 20641 system E AndroidRuntime : FATAL EXCEPTION: AsyncTask #2
Process: com.android.settings, PID: 4657
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:415)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Caused by: java.lang.IllegalStateException: Fail to enroll user password when creating SP for user 0
at android.os.Parcel.createExceptionOrNull(Parcel.java:2381)
at android.os.Parcel.createException(Parcel.java:2357)
at android.os.Parcel.readException(Parcel.java:2340)
at android.os.Parcel.readException(Parcel.java:2282)
at com.android.internal.widget.ILockSettings$Stub$Proxy.setLockCredential(ILockSettings.java:1208)
at com.android.internal.widget.LockPatternUtils.setLockCredential(LockPatternUtils.java:660)
at com.android.settings.password.ChooseLockPattern$SaveAndFinishWorker.saveAndVerifyInBackground(ChooseLockPattern.java:922)
at com.android.settings.password.SaveChosenLockWorkerBase$Task.doInBackground(SaveChosenLockWorkerBase.java:138)
at com.android.settings.password.SaveChosenLockWorkerBase$Task.doInBackground(SaveChosenLockWorkerBase.java:134)
at android.os.AsyncTask$3.call(AsyncTask.java:394)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 4 more
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.locksettings.SyntheticPasswordManager.createPasswordBasedSyntheticPassword(SyntheticPasswordManager.java:779)
at com.android.server.locksettings.LockSettingsService.initializeSyntheticPasswordLocked(LockSettingsService.java:2688)
at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1741)
at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1663)
at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:537)
2021-12-12 08:36:58.370 4317 4997 system E BufferQueueProducer : [com.android.settings/com.android.settings.password.ChooseLockPatternSize#0](id:10dd000000a7,api:0,p:-1,c:4317) disconnect: not connected (req=1)
Did you ever find a solution to this?
I have the stock and the LineageOS ROM (19.1) ROMS working fine, but a custom build of the eOS (https://e.foundation) for the S20+ (y2s) has this issue.

Categories

Resources