[Q] Broken out Revo 2.0 problems - General Questions and Answers

Hello XDA! I'm an XDA stalker, first time poster, so noob it is. I wanted to post this in the relevant thread, but since I'm such a noob and can't post there...
So I have read through the entire Broken Out Revo thread:
http://forum.xda-developers.com/showthread.php?t=1577423&page=64
I have the same problem as imnotamorningguy (post #795) - my calendar is the only Google app that doesn't work. I was previously on BO1.1 zv8. I have been looking for a calendar.apk that works with the blitzkrieg kernel, and have tried a few options. I think the problem is caused by the lack of CalendarStorage.apk.
To provide a detailed timeline of what I've tried:
1. Upgraded from BO 1.1 to BO 2.01 - calendar failed. (Software update was unfrozen)
2. Tried a few calendar.apk's (downloading, move via Root Explorer, fix permissions). Still get FC's
3. I decided I would try flashing a tot (zv9), re-root, wipe data, reflash BO 2.01. Still FCing.
Whenever I try a different Calendar.apk, I get a com.google.processframework.apk error. Reflashed BO 2.01.
I really like the ROM, and would prefer not to have to do step 3 again... Where's the proper calendar package that would fix this problem? I've tried AOPx rom, and looked for other 2.3.6 GB roms that might have it (CM7)...
The output from logcat:
Code:
07-20 13:06:04.633 18777 18786 E ActivityThread: Failed to find provider info for com.android.calendar
07-20 13:06:04.703 18777 18777 W dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x4001d560)
07-20 13:06:04.703 18777 18787 E Cal : [Event.java:309:loadEvents()] loadEvents() returned null cursor!
07-20 13:06:04.703 18777 18777 E AndroidRuntime: FATAL EXCEPTION: main
07-20 13:06:04.703 18777 18777 E AndroidRuntime: java.lang.NullPointerException
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at android.util.CalendarUtils$TimeZoneUtils$AsyncTZHandler.onQueryComplete(CalendarUtils.java:93)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at android.content.AsyncQueryHandler.handleMessage(AsyncQueryHandler.java:344)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at android.os.Looper.loop(Looper.java:130)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:3683)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at java.lang.reflect.Method.invokeNative(Native Method)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:507)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:647)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at dalvik.system.NativeStart.main(Native Method)
07-20 13:06:04.703 18777 18787 E ActivityThread: Failed to find provider info for com.android.calendar
07-20 13:06:04.753 234 234 W ActivityManager: Force finishing activity com.android.calendar/.MonthActivity
Any help is appreciated.

I resolved this on my own.
I loaded the calendar.apk, ADW launcher, and calendarprovider.apk from BO 1.1 into the BO 2.0 package and reflashed, and that resolved the problem.

rmaltempo said:
Hello XDA! I'm an XDA stalker, first time poster, so noob it is. I wanted to post this in the relevant thread, but since I'm such a noob and can't post there...
So I have read through the entire Broken Out Revo thread:
http://forum.xda-developers.com/showthread.php?t=1577423&page=64
I have the same problem as imnotamorningguy (post #795) - my calendar is the only Google app that doesn't work. I was previously on BO1.1 zv8. I have been looking for a calendar.apk that works with the blitzkrieg kernel, and have tried a few options. I think the problem is caused by the lack of CalendarStorage.apk.
To provide a detailed timeline of what I've tried:
1. Upgraded from BO 1.1 to BO 2.01 - calendar failed. (Software update was unfrozen)
2. Tried a few calendar.apk's (downloading, move via Root Explorer, fix permissions). Still get FC's
3. I decided I would try flashing a tot (zv9), re-root, wipe data, reflash BO 2.01. Still FCing.
Whenever I try a different Calendar.apk, I get a com.google.processframework.apk error. Reflashed BO 2.01.
I really like the ROM, and would prefer not to have to do step 3 again... Where's the proper calendar package that would fix this problem? I've tried AOPx rom, and looked for other 2.3.6 GB roms that might have it (CM7)...
The output from logcat:
Code:
07-20 13:06:04.633 18777 18786 E ActivityThread: Failed to find provider info for com.android.calendar
07-20 13:06:04.703 18777 18777 W dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x4001d560)
07-20 13:06:04.703 18777 18787 E Cal : [Event.java:309:loadEvents()] loadEvents() returned null cursor!
07-20 13:06:04.703 18777 18777 E AndroidRuntime: FATAL EXCEPTION: main
07-20 13:06:04.703 18777 18777 E AndroidRuntime: java.lang.NullPointerException
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at android.util.CalendarUtils$TimeZoneUtils$AsyncTZHandler.onQueryComplete(CalendarUtils.java:93)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at android.content.AsyncQueryHandler.handleMessage(AsyncQueryHandler.java:344)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at android.os.Looper.loop(Looper.java:130)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:3683)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at java.lang.reflect.Method.invokeNative(Native Method)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:507)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:647)
07-20 13:06:04.703 18777 18777 E AndroidRuntime: at dalvik.system.NativeStart.main(Native Method)
07-20 13:06:04.703 18777 18787 E ActivityThread: Failed to find provider info for com.android.calendar
07-20 13:06:04.753 234 234 W ActivityManager: Force finishing activity com.android.calendar/.MonthActivity
Any help is appreciated.
Click to expand...
Click to collapse
I had issues with the calendar FC's. When I flashed 2.0 over 1.1 without wiping. I just Nandroid restored back to 1.1 then wiped totally clean, flashed 2.0 then without wiping flashed 2.0.1 and everything is working fine. From where you are, just wipe and flash 2.0 and see if it works.

arcane spade said:
I had issues with the calendar FC's. When I flashed 2.0 over 1.1 without wiping. I just Nandroid restored back to 1.1 then wiped totally clean, flashed 2.0 then without wiping flashed 2.0.1 and everything is working fine. From where you are, just wipe and flash 2.0 and see if it works.
Click to expand...
Click to collapse
The thing is, I didn't want to wipe data since everything BUT the calendar worked. The only thing now is the fact that smartassv2 cpu governor is no longer available...

Related

[Q] Market FC after system restore

When I got the Nexus S (9023) I went to root it, put on Clockwork recovery and immediately made a backup. Meanwhile I played with different custom roms and today I went back to the original backup. All seems fine but the market does not work
Any idea what happened and how to get it back?
Code:
--------- beginning of /dev/log/system
05-27 06:23:11.792 2322 2322 E AndroidRuntime: FATAL EXCEPTION: main
05-27 06:23:11.792 2322 2322 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.vending/com.android.vending.TosActivity}: java.lang.NullPointerException
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1647)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1663)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at android.app.ActivityThread.access$1500(ActivityThread.java:117)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:931)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at android.os.Looper.loop(Looper.java:130)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:3683)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at java.lang.reflect.Method.invokeNative(Native Method)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:507)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at dalvik.system.NativeStart.main(Native Method)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: Caused by: java.lang.NullPointerException
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at com.android.vending.TosActivity.onCreate(TosActivity.java:47)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1611)
05-27 06:23:11.792 2322 2322 E AndroidRuntime: ... 11 more
05-27 06:23:11.796 106 1905 W ActivityManager: Force finishing activity com.android.vending/.TosActivity
05-27 06:23:11.800 106 1905 W ActivityManager: Force finishing activity com.android.vending/.AssetBrowserActivity
05-27 06:23:12.300 106 119 W ActivityManager: Activity pause timeout for HistoryRecord{40875c60 com.android.vending/.TosActivity}
I had a similar problem today after restoring just "system". Doing a Full restore resolved it.
Phew! got it solved without going the wipe-and-reinstall route. Pushing a current vendor.apk on the phone did not help but then I figured that the latest (CM7) gapps package also has a vendor.apk and this is not the very latest version. So I installed this through adb and this indeed downgraded the market and it could be started again!
Problem solved. Althoug I'm still curious what might have cause the broken market in the backup

Unlocking the bootloader: Help me interpreting this logcat

Hi guys. I've been trying to unlock the bootloader. So far I installed an useful app to open android settings https://m.apkpure.com/hidden-settings-for-android/com.jami.tool.hiddensetting.
I enabled developer settings trough ADB:
Bash:
adb shell settings put global development_settings_enabled 1
But I think I could've also enable it by clicking 5 times the build version... Anyway then I opened the Settings app and Developer Options appeared, unfortunately, when I open it, the whole Settings app crashes. Here is the what I think it is the relevant logcat:
Code:
03-12 22:59:30.047 12645 12645 E ndroid.setting: Can't find memory status under: /sys/block/zram0/
03-12 22:59:30.047 12645 12645 D AndroidRuntime: Shutting down VM
03-12 22:59:30.033 12645 12645 W ndroid.settings: type=1400 audit(0.0:129): avc: denied { read } for name="pagetypeinfo" dev="proc" ino=4026531857 scontext=u:r:system_app:s0 tcontext=u:object_r:proc_pagetypeinfo:s0 tclass=file permissive=0
03-12 22:59:30.047 12645 12645 E AndroidRuntime: FATAL EXCEPTION: main
03-12 22:59:30.047 12645 12645 E AndroidRuntime: Process: com.android.settings, PID: 12645
03-12 22:59:30.047 12645 12645 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.SubSettings}: java.lang.RuntimeException: SysMemInfo read failed
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3279)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3418)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:83)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2025)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7389)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:933)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: Caused by: java.lang.RuntimeException: SysMemInfo read failed
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.os.Debug.getZoneWatermarks(Native Method)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.internal.util.MemInfoReader.readMemInfo(MemInfoReader.java:37)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.applications.ProcStatsData$MemInfo.calculateWeightInfo(ProcStatsData.java:423)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.applications.ProcStatsData$MemInfo.<init>(ProcStatsData.java:383)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.applications.ProcStatsData$MemInfo.<init>(ProcStatsData.java:362)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.applications.ProcStatsData.refreshStats(ProcStatsData.java:156)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.applications.ProcStatsData.setDuration(ProcStatsData.java:128)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.development.MemoryUsagePreferenceController.setDuration(MemoryUsagePreferenceController.java:76)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.development.MemoryUsagePreferenceController.displayPreference(MemoryUsagePreferenceController.java:54)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.dashboard.DashboardFragment.lambda$displayResourceTiles$5(DashboardFragment.java:313)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.dashboard.-$$Lambda$DashboardFragment$Tn5-YvXfafHUTSTeQyMxdmcExvo.accept(Unknown Source:4)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1390)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:604)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:283)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.util.Iterator.forEachRemaining(Iterator.java:116)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:475)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:133)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:236)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:435)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.dashboard.DashboardFragment.displayResourceTiles(DashboardFragment.java:312)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.dashboard.DashboardFragment.refreshAllPreferences(DashboardFragment.java:360)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.dashboard.DashboardFragment.onCreatePreferences(DashboardFragment.java:160)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at androidx.preference.PreferenceFragmentCompat.onCreate(PreferenceFragmentCompat.java:160)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settingslib.core.lifecycle.ObservablePreferenceFragment.onCreate(ObservablePreferenceFragment.java:61)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.SettingsPreferenceFragment.onCreate(SettingsPreferenceFragment.java:133)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.dashboard.DashboardFragment.onCreate(DashboardFragment.java:137)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.dashboard.RestrictedDashboardFragment.onCreate(RestrictedDashboardFragment.java:104)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.development.DevelopmentSettingsDashboardFragment.onCreate(DevelopmentSettingsDashboardFragment.java:145)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at androidx.fragment.app.Fragment.performCreate(Fragment.java:2596)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at androidx.fragment.app.FragmentManagerImpl.moveToState(FragmentManagerImpl.java:831)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at androidx.fragment.app.FragmentTransition.addToFirstInLastOut(FragmentTransition.java:1197)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at androidx.fragment.app.FragmentTransition.calculateFragments(FragmentTransition.java:1080)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at androidx.fragment.app.FragmentTransition.startTransitions(FragmentTransition.java:119)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at androidx.fragment.app.FragmentManagerImpl.executeOpsTogether(FragmentManagerImpl.java:1853)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at androidx.fragment.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManagerImpl.java:1811)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at androidx.fragment.app.FragmentManagerImpl.execPendingActions(FragmentManagerImpl.java:1717)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at androidx.fragment.app.FragmentManagerImpl.executePendingTransactions(FragmentManagerImpl.java:183)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.SettingsActivity.switchToFragment(SettingsActivity.java:600)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.SettingsActivity.launchSettingFragment(SettingsActivity.java:393)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:301)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7825)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7814)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1306)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3254)
03-12 22:59:30.047 12645 12645 E AndroidRuntime: ... 11 more
03-12 22:59:30.033 12645 12645 W ndroid.settings: type=1400 audit(0.0:130): avc: denied { search } for name="zram0" dev="sysfs" ino=46795 scontext=u:r:system_app:s0 tcontext=u:object_r:sysfs_zram:s0 tclass=dir permissive=0
03-12 22:59:30.033 12645 12645 W ndroid.settings: type=1400 audit(0.0:131): avc: denied { search } for name="zram0" dev="sysfs" ino=46795 scontext=u:r:system_app:s0 tcontext=u:object_r:sysfs_zram:s0 tclass=dir permissive=0
03-12 22:59:30.033 12645 12645 W ndroid.settings: type=1400 audit(0.0:132): avc: denied { read } for name="zoneinfo" dev="proc" ino=4026531859 scontext=u:r:system_app:s0 tcontext=u:object_r:proc_zoneinfo:s0 tclass=file permissive=0
03-12 22:59:30.052 1044 4585 W ActivityTaskManager: Force finishing activity com.android.settings/.SubSettings
My first impression is that's related to some kernel build flags. Does someone knows more?
I think it is possible to unlock the bootloader normally with developer options because ro.oem_unlock_supported is set to 1. Bye.
Edit: Here is a relevant stackoverflow issue https://stackoverflow.com/questions...h-when-opening-developer-options-programmatic It may depends on the app used to open the settings.
you can access some settings with SetEdit
SetEdit SettingsDatabaseEditor – Apps bei Google Play
Provides direct access to the Android settings database
play.google.com
here you can shutdown some services:
Download Package Disabler Pro(com.ospolice.packagedisablerpro)11.0 free APK - Android Games_APKsHub
Download Package Disabler Pro(com.ospolice.packagedisablerpro)11.0 free APK - Android Games_APKsHub APKShub
www.apkshub.com
also i think the developer options page just isnt there so it cant load into memory so it cant be read by the os.
even when developer options page is accessible, we only need the OEM unlock option and USB debugging. somewhere in the settingstable is a line for OEM unlock but its a closed table.
also:
huawei had a bootloader mastercodes like 2222222222222222 for example. and some of the indias are hacking the bootloadercode of android phones with some special dongle/software. wouldnt it be possible to get in touch with those (mostly moneymakers)? they have to have some magic knowledge which result is only shared over crypted payed and timelimited programms and/or dongles.
what about the oculus go, it has root isnt that the quest os just for 3DOF?
(i had the feeling that no one tries to get root on the quest, because its so silent here.
if we know the length of the code we can try fastboot bruteforce )
codes are server sided bud....either you hack Facebook private servers or nothing at all.... also bootloader codes ever since Facebook took over, change at random, unspecified intervals, generated by thief servers...hence why you need to mostly setup the device using. an app for on a phone or pc,.....this syncs up each new bootloader code when it changes.... its called Oculus companion server" if you browse running system processes...used to be able to force kill the process but as soon as you did, oculus home would crash and you get a unresponsive blank screen until reboot....
thats why all those legit "unlock" phone providers like SamPwnd, work because the guy running it is either a current samsung employee, former and still has server access, or has an inside guy at samsung.....they dont hack the bootloaader codes...they get them straight from private servers
ok, not thought about it. maybe we dont need an unlocked bootloader, but for that i need someone who can programm android launchers or apps.
wazzu232 said:
codes are server sided bud....either you hack Facebook private servers or nothing at all.... also bootloader codes ever since Facebook took over, change at random, unspecified intervals, generated by thief servers...hence why you need to mostly setup the device using. an app for on a phone or pc,.....this syncs up each new bootloader code when it changes.... its called Oculus companion server" if you browse running system processes...used to be able to force kill the process but as soon as you did, oculus home would crash and you get a unresponsive blank screen until reboot....
thats why all those legit "unlock" phone providers like SamPwnd, work because the guy running it is either a current samsung employee, former and still has server access, or has an inside guy at samsung.....they dont hack the bootloaader codes...they get them straight from private servers
Click to expand...
Click to collapse
We could find a vuln in android to gain root access and then find the code using root like we did on huaweis

Question Text-to-speech on nio with LOS 19 microG

I'm using the latest LOS 19 with microG from here on my nio and I'm trying to get text-to-speech to work (to use it in OSMAnd~). However, non of the TTS engines I tried works (Google Speech Services, flite, RHVoice). They all suffer from the same problem: Once I go to Settings > System > Languages > Text-to-speech output the Settings app jumps back to the System category. If I try navigating there again, it crashes.
Here's the log when the crash happens:
Code:
05-27 14:56:35.644 16812 16812 D SettingsActivity: Starting to set activity title
05-27 14:56:35.644 16812 16812 D SettingsActivity: Done setting title
05-27 14:56:35.644 16812 16812 D SettingsActivity: Switching to fragment com.android.settings.tts.TextToSpeechSettings
05-27 14:56:35.644 16812 16812 D SubSettings: Launching fragment com.android.settings.tts.TextToSpeechSettings
05-27 14:56:35.645 1494 2865 E UserRestrictionsUtils: Unknown restriction queried by uid 1000 (org.lineageos.lineagesettings et al): null
05-27 14:56:35.646 1494 2865 E UserRestrictionsUtils: Unknown restriction queried by uid 1000 (org.lineageos.lineagesettings et al): null
05-27 14:56:35.646 1494 2865 E UserRestrictionsUtils: Unknown restriction queried by uid 1000 (org.lineageos.lineagesettings et al): null
05-27 14:56:35.650 1494 2865 I ActivityTaskManager: START u0 {act=android.speech.tts.engine.CHECK_TTS_DATA cmp=com.github.olga_yakovleva.rhvoice.android/.CheckTTSData} from uid 1000
05-27 14:56:35.655 1202 1202 I android.hardware.power-service-qti: Power setMode: 5 to: 1
05-27 14:56:35.659 16812 16812 D SettingsActivity: Executed frag manager pendingTransactions
05-27 14:56:35.681 16812 16834 D SettingsActivity: No enabled state changed, skipping updateCategory call
05-27 14:56:35.685 1494 7986 W ActivityTaskManager: Tried to set launchTime (0) < mLastActivityLaunchTime (6736388)
05-27 14:56:35.691 1022 12398 I netd : bandwidthAddNiceApp(10263) <0.04ms>
05-27 14:56:35.742 1494 1737 I ActivityTaskManager: Displayed com.android.settings/.SubSettings: +129ms
05-27 14:56:35.743 16812 16812 D CompatibilityChangeReporter: Compat change id reported: 78294732; UID 1000; state: ENABLED
05-27 14:56:35.743 16812 16812 E TextToSpeechSettings: Voice data check complete, but no engine bound
05-27 14:56:35.743 16812 16812 D AndroidRuntime: Shutting down VM
05-27 14:56:35.744 16812 16812 E AndroidRuntime: FATAL EXCEPTION: main
05-27 14:56:35.744 16812 16812 E AndroidRuntime: Process: com.android.settings, PID: 16812
05-27 14:56:35.744 16812 16812 E AndroidRuntime: java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=1230932445, result=1, data=Intent { (has extras) }} to activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.app.ActivityThread.deliverResults(ActivityThread.java:5368)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.app.ActivityThread.handleSendResult(ActivityThread.java:5407)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.app.servertransaction.ActivityResultItem.execute(ActivityResultItem.java:67)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:45)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2253)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7870)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.speech.tts.TtsEngines.parseEnginePrefFromList(TtsEngines.java:510)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.speech.tts.TtsEngines.isLocaleSetToDefaultForEngine(TtsEngines.java:372)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at com.android.settings.tts.TextToSpeechSettings.updateDefaultLocalePref(TextToSpeechSettings.java:524)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at com.android.settings.tts.TextToSpeechSettings.onActivityResult(TextToSpeechSettings.java:507)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at androidx.fragment.app.FragmentManager$9.onActivityResult(FragmentManager.java:3011)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at androidx.fragment.app.FragmentManager$9.onActivityResult(FragmentManager.java:2991)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at androidx.activity.result.ActivityResultRegistry.doDispatch(ActivityResultRegistry.java:362)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at androidx.activity.result.ActivityResultRegistry.dispatchResult(ActivityResultRegistry.java:322)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at androidx.activity.ComponentActivity.onActivityResult(ComponentActivity.java:634)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at androidx.fragment.app.FragmentActivity.onActivityResult(FragmentActivity.java:164)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at com.android.settings.SettingsActivity.onActivityResult(SettingsActivity.java:476)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.app.Activity.dispatchActivityResult(Activity.java:8385)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: at android.app.ActivityThread.deliverResults(ActivityThread.java:5361)
05-27 14:56:35.744 16812 16812 E AndroidRuntime: ... 13 more
05-27 14:56:35.745 1494 2865 W ActivityTaskManager: Force finishing activity com.android.settings/.SubSettings
05-27 14:56:35.745 1494 16960 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
05-27 14:56:35.746 1494 2865 W ActivityTaskManager: Force finishing activity com.android.settings.intelligence/.search.SearchActivity
05-27 14:56:35.747 16812 16812 I Process : Sending signal. PID: 16812 SIG: 9
05-27 14:56:35.789 0 0 I binder : undelivered transaction 2177669, process died.
05-27 14:56:35.790 0 0 I binder : undelivered transaction 2177654, process died.
05-27 14:56:35.799 1494 2865 I ActivityManager: Process com.android.settings (pid 16812) has died: fg TOP
05-27 14:56:35.800 1494 1777 I libprocessgroup: Successfully killed process cgroup uid 1000 pid 16812 in 0ms
05-27 14:56:35.802 1494 5392 I WindowManager: WIN DEATH: Window{4c195a8 u0 com.android.settings/com.android.settings.Settings}
05-27 14:56:35.802 1494 5392 W InputManager-JNI: Input channel object '4c195a8 com.android.settings/com.android.settings.Settings (client)' was disposed without first being removed with the input manager!
05-27 14:56:35.804 1023 1023 I Zygote : Process 16812 exited due to signal 9 (Killed)
05-27 14:56:35.804 1494 6205 W WindowManager: Cannot find window which accessibility connection is added to
05-27 14:56:35.805 1494 6204 I WindowManager: WIN DEATH: Window{e8cb5a7 u0 com.android.settings/com.android.settings.SubSettings}
05-27 14:56:35.805 1494 6204 W InputManager-JNI: Input channel object 'e8cb5a7 com.android.settings/com.android.settings.SubSettings (client)' was disposed without first being removed with the input manager!
05-27 14:56:35.807 1494 1759 W UsageStatsService: Unexpected activity event reported! (com.android.settings/com.android.settings.homepage.SettingsHomepageActivity event : 23 instanceId : 216578729)
Anybody got any hints on what I could do to fix it?
Anybody got an idea against which which project / repo / etc this could be reported (while not playing 'You should report this elsewhere' ping pong? )
I was able to fix my problem by installing Google Speech Services via Aurora, rebooting, installing eSpeak via F-Droid, starting eSpeak and going to 'General TTS settings' via the eSpeak menu. Possibly eSpeak sets itself as the default TTS if none is configured.
Afterwards I was also able to select Speech Services as the default without issues.

Bootloop at Xperia screen (I have the logs but don't understand them)

My XZ is rooted and had many different Magisk modules on it, everything was working perfectly for many months until one night I was browsing the Web, my phone froze, rebooted, and thus began the never-ending boot loop at the Xperia screen, I can shut it down, I can access twrp, but the phone never fully boots, I'm hoping there's a solution without having to reflash.
Code:
--------- beginning of crash
01-28 22:01:46.195 2249 2249 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
01-28 22:01:46.195 2249 2249 E AndroidRuntime: java.lang.IllegalArgumentException: State 6 is not a valid state
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at android.content.om.OverlayInfo.ensureValidState(OverlayInfo.java:141)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at android.content.om.OverlayInfo.<init>(OverlayInfo.java:111)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.server.om.OverlayManagerSettings$SettingsItem.getOverlayInfo(OverlayManagerSettings.java:493)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.server.om.OverlayManagerSettings$SettingsItem.-wrap0(Unknown Source:0)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.server.om.OverlayManagerSettings.-com_android_server_om_OverlayManagerSettings-mthref-1(OverlayManagerSettings.java:177)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.server.om.-$Lambda$VuwDBWerAG9B6xB4Rr4-FeDL3jk$1.$m$0(Unknown Source:2)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.server.om.-$Lambda$VuwDBWerAG9B6xB4Rr4-FeDL3jk$1.apply(Unknown Source:0)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:194)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:176)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1390)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:235)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:501)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.server.om.OverlayManagerSettings.getOverlaysForUser(OverlayManagerSettings.java:176)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.server.om.OverlayManagerServiceImpl.updateOverlaysForUser(OverlayManagerServiceImpl.java:89)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.server.om.OverlayManagerService.onSwitchUser(OverlayManagerService.java:314)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.server.om.OverlayManagerService.<init>(OverlayManagerService.java:280)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.server.SystemServer.startBootstrapServices(SystemServer.java:680)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.java:415)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer.java:281)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
01-28 22:01:46.195 2249 2249 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)
01-28 22:01:46.196 2249 2249 I Process : Sending signal. PID: 2249 SIG: 9

Question WebView on WearOS?

Is it possible to make WebView work on WearOS? I'm trying to login on VancedMicroG to use Youtube ReVanced on the watch, but it keeps crashing when I try to log in... I already sideloaded WebView but it doesn't work. Here's the log:
CSS:
02-26 00:01:19.901 13424 13424 E AndroidRuntime: FATAL EXCEPTION: main
02-26 00:01:19.901 13424 13424 E AndroidRuntime: Process: com.mgoogle.android.gms:ui, PID: 13424
02-26 00:01:19.901 13424 13424 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.mgoogle.android.gms/org.microg.gms.auth.login.LoginActivity}: java.lang.UnsupportedOperationException
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3456)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3612)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:85)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2073)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.os.Looper.loop(Looper.java:246)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7690)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:593)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:995)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: Caused by: java.lang.UnsupportedOperationException
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.webkit.WebViewFactory.getProvider(WebViewFactory.java:242)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.webkit.WebView.getFactory(WebView.java:2576)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.webkit.WebView.ensureProviderCreated(WebView.java:2570)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.webkit.WebView.setOverScrollMode(WebView.java:2638)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.view.View.<init>(View.java:5518)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.view.View.<init>(View.java:5679)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.view.ViewGroup.<init>(ViewGroup.java:698)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.widget.AbsoluteLayout.<init>(AbsoluteLayout.java:56)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.webkit.WebView.<init>(WebView.java:413)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.webkit.WebView.<init>(WebView.java:355)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.webkit.WebView.<init>(WebView.java:337)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.webkit.WebView.<init>(WebView.java:324)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.webkit.WebView.<init>(WebView.java:314)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at org.microg.gms.auth.login.LoginActivity.createWebView(Unknown Source:2)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at org.microg.gms.auth.login.LoginActivity.onCreate(Unknown Source:23)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:8033)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:8013)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1309)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3429)
02-26 00:01:19.901 13424 13424 E AndroidRuntime: ... 11 more
Or maybe GeckoView could work? I'm using running Fennec on the watch with some useful extensions and it works perfectly fine as far as I can tell, I don't use it very often. Anyway, looking forward to hear your suggestions!
So huh... Anyone?
[PORT] YouTube Music (Vanced) on WearOS 2
This is a mod of YT Music Vanced & microG Vanced. Offline mode works as long as you have a YT Music subscription. Requirements • A phone • ADB • Basic knowledge about sideloading • Internet connection...
forum.xda-developers.com

Categories

Resources