Related
Any roms that aren't running with the Navigator but instead just using it through the maps. (Vanilla roms, Legend roms, etc.)
This doesn't use SenseUI so you should be able to incorporate it with any rom. So, if you are a dev please feel free to put it into your rom
I used root explorer for this so if anyone knows the adb commands please feel free to post them. (im too lazy)
chmod 766 HtcNaviPanel.apk (you can try without chmod to see if it works, it may)
copy and paste into /system/app
***remember to have the latest maps installed***
you can also voice search, "Navigate to (Address of Location)" Not sure if that works without HtcNaviPanel.apk or not but the app will give u your most recent destinations
sweet. thanks!
andrew8806 said:
Any roms that aren't running with the Navigator but instead just using it through the maps. (Vanilla roms, Legend roms, etc.)
This doesn't use SenseUI so you should be able to incorporate it with any rom. So, if you are a dev please feel free to put it into your rom
I used root explorer for this so if anyone knows the adb commands please feel free to post them. (im too lazy)
chmod 766 HtcNaviPanel.apk (you can try without chmod to see if it works, it may)
copy and paste into /system/app
***remember to have the latest maps installed***
you can also voice search, "Navigate to (Address of Location)" Not sure if that works without HtcNaviPanel.apk or not but the app will give u your most recent destinations
Click to expand...
Click to collapse
I needed to get the HtcNaviPanel-signed.apk for it to load. It is under the Desire forum themes and apps, under HtcNavipanel.
crash report
FYI:
W/PackageManager( 87): Exception reading apk: /system/app/HtcNaviPanel.apk
W/PackageManager( 87): java.io.IOException: /system/app/HtcNaviPanel.apk
W/PackageManager( 87): at dalvik.system.DexFile.isDexOptNeeded(Native Method)
W/PackageManager( 87): at com.android.server.PackageManagerService.performDexOptLI(PackageManagerService.java:2153)
W/PackageManager( 87): at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2531)
W/PackageManager( 87): at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2087)
W/PackageManager( 87): at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:1983)
W/PackageManager( 87): at com.android.server.PackageManagerService.<init>(PackageManagerService.java:584)
W/PackageManager( 87): at com.android.server.PackageManagerService.main(PackageManagerService.java:335)
W/PackageManager( 87): at com.android.server.ServerThread.run(SystemServer.java:133)
hoban_eris said:
FYI:
W/PackageManager( 87): Exception reading apk: /system/app/HtcNaviPanel.apk
W/PackageManager( 87): java.io.IOException: /system/app/HtcNaviPanel.apk
W/PackageManager( 87): at dalvik.system.DexFile.isDexOptNeeded(Native Method)
W/PackageManager( 87): at com.android.server.PackageManagerService.performDexOptLI(PackageManagerService.java:2153)
W/PackageManager( 87): at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2531)
W/PackageManager( 87): at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2087)
W/PackageManager( 87): at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:1983)
W/PackageManager( 87): at com.android.server.PackageManagerService.<init>(PackageManagerService.java:584)
W/PackageManager( 87): at com.android.server.PackageManagerService.main(PackageManagerService.java:335)
W/PackageManager( 87): at com.android.server.ServerThread.run(SystemServer.java:133)
Click to expand...
Click to collapse
Im not sure if this makes a difference... but i didn't think it would but try chmod 777 (in which I originally did but wouldnt think it'd matter) I also copied and pasted the .odex here
Please let me know if this works you all or not...
If it that doesn't work... below is linked to the HtcNaviPanel mod for the desire... I have tried both and they have the same outcome as above.
hello all
i tried port jb to wildfire
but touch screen not work, i don't know, i try use my devices idc
can somebody help me?
This is logcat
KoolSavas95 said:
Did u replaced all hw folders in lib folder? Maybe need to edit framework.jar
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
i will try
I think there are some permissions missing also from etc/permissions
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.mail in package com.android.contacts
W/PackageManager( 316): Unknown permission android.permission.ADD_SYSTEM_SERVICE in package com.android.phone
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.providers.calendar
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.cl in package com.android.providers.calendar
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.mail in package com.android.calendar
W/PackageManager( 316): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.browser (protectionLevel=2 flags=0x9be45)
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.providers.contacts
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.cp in package com.android.providers.contacts
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.settings
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD in package com.android.development
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.development
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES in package com.android.development
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser in package com.android.development
W/PackageManager( 316): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x8be45)
Click to expand...
Click to collapse
deba1994 said:
I think there are some permissions missing also from etc/permissions
Click to expand...
Click to collapse
oh no,it is not related to touch screen
it here:
Code:
D/EventHub( 316): No input device configuration file found for device 'compass'.
D/EventHub( 316): No input device configuration file found for device 'curcial-oj'.
I/SystemServer( 316): Bluetooth Service
I/EventHub( 316): New device: id=2, fd=105, path='/dev/input/event6', name='curcial-oj', classes=0x9, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false
D/EventHub( 316): No input device configuration file found for device 'lightsensor-level'.
D/EventHub( 316): No input device configuration file found for device 'buzz-keypad'.
I/EventHub( 316): New device: id=5, fd=107, path='/dev/input/event3', name='buzz-keypad', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/buzz-keypad.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=true, usingSuspendBlockIoctl=false, usingClockIoctl=false
D/EventHub( 316): No input device configuration file found for device 'proximity'.
D/AK8973 ( 113): HRET = AKSC_HOF_DSS_START
E/filemap ( 316): mmap(0,4096) failed: No such device
E/OMXCodec( 109): mediacodec list instance returned NULL
E/AudioCache( 109): Error 1, -2147483648 occurred
E/SoundPool( 316): Unable to load sample: (null)
I/EventHub( 316): New device: id=7, fd=108, path='/dev/input/event1', name='atmel-touchscreen', classes=0x55, configuration='/system/usr/idc/atmel-touchscreen.idc', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false
D/EventHub( 316): No input device configuration file found for device 'h2w headset'.
D/AK8973 ( 113): HRET = AKSC_HOF_DSS_REQUEST
I/EventHub( 316): New device: id=8, fd=98, path='/dev/input/event0', name='h2w headset', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/h2w_headset.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false
D/AK8973 ( 113): HRET = AKSC_HOF_DSS_REQUEST
I/BluetoothProfileState( 316): Message:Entering Stable State
I/InputReader( 316): Device added: id=-1, name='Virtual', sources=0x00000301
I/InputReader( 316): Device added: id=8, name='h2w headset', sources=0x00000101
I/InputReader( 316): Touch device 'atmel-touchscreen' could not query the properties of its associated display 0. The device will be inoperable until the display size becomes available.
I/InputReader( 316): Device added: id=7, name='atmel-touchscreen', sources=0x00001503
I/InputReader( 316): Device added: id=0, name='buzz-keypad', sources=0x00000101
D/AK8973 ( 113): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 113): HRET = AKSC_HOF_DSS_REQUEST
I/InputReader( 316): Device added: id=2, name='curcial-oj', sources=0x00002103
E/Trace ( 316): error opening trace file: No such file or directory (2)
Code:
I/SystemServer( 316): Accessibility Manager
I/InputReader( 316): Reconfiguring input devices. changes=0x00000004
I/InputReader( 316): Device reconfigured: id=7, name='atmel-touchscreen', surface size is now 240x320, mode is 1
I/ActivityManager( 316): Config changed: {1.0 0mcc0mnc en_US sw320dp w320dp h401dp smll port ?uimode ?night finger -keyb/h/h -nav/h s.2}
Ok i'm not that good at this but will try to help....how did you port JB??did you compile from source?
i try port jb of heroc here
i port it by replace my zImage and ramdisk
I think u could try porting from here
and i think as koolsavas95 said..u may need to replace your hw folder in lib with what i am not sure....maybe u can try to use ics build as base ?
EDIT : that last mediafire link that i attached was wrong..sry dont download that !!!
thank you, deba1994
i will try
Best of luck and maybe if you are good at compiling u can maybe contact that x10 mini dev for help
tathanhlam66 said:
hello all
i tried port jb to wildfire
but touch screen not work, i don't know, i try use my devices idc
can somebody help me?
This is logcat
Click to expand...
Click to collapse
Any luck with the port?
I can not port it
my kernel does not work touch screen
If you are able to fix compiling errors you can try to build jb from source, just use sympnotic github: repo init -u git://github.com/sympnotic/android.git -b jellybean
I've tried to build from here but i got errors while compiling and i'm not able to solve them
I am downloading and compiling now from sympnotic. Let u know if it works
edit:
I could get past the bionic error, but the egl and external packads error are too much. Will try another time again.
*delete*
OK so I have Magic 2014 on my tablet, version 1.2.0. I installed it from Amazon Appstore because it worked, whereas Play Store kept throwing errors at me while downloading the extra content. And hence, the in-app content purchases I've made have also been through Amazon.
This evening I tried upgrading the app to 1.4.0 from Amazon. It went through the entire 1.5 GB download, commenced the install... and then promptly rebooted. The app is still sitting at version 1.2.0.
I found the apk file cached in /sdcard/Android/data/files/apks. So I attempted to install from there. Again after about a minute it rebooted.
So, next, I monitored with adb logcat while doing the install. There was a lot of gunk in the log from other apps, so I tried again while enabling Developer Options "Don't keep activities". It was still too much text to monitor in a Command Prompt window, so I tried one more time using:
adb logcat > magic-crash.txt
to save in a text file. Here are the critical moments:
I/ActivityManager( 8603): START u0 {act=android.intent.action.VIEW dat=file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk typ=application/vnd.android.package-archive cmp=com.android.packageinstaller/.PackageInstallerActivity} from pid 17478
I/ActivityManager( 8603): Start proc com.android.packageinstaller for activity com.android.packageinstaller/.PackageInstallerActivity: pid=17705 uid=10044 gids={50044, 1028}
I/ActivityManager( 8603): START u0 {dat=file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk cmp=com.android.packageinstaller/.InstallAppProgress (has extras)} from pid 17705
I/ActivityManager( 8603): Start proc com.android.defcontainer for service com.android.defcontainer/.DefaultContainerService: pid=17730 uid=10013 gids={50013, 1028, 1015, 1023, 2001}
W/ActivityManager( 8603): No content provider found for permission revoke: file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk
I/ActivityManager( 8603): Start proc com.android.vending for broadcast com.android.vending/com.google.android.vending.verifier.PackageVerificationReceiver: pid=17744 uid=10047 gids={50047, 3003, 1028, 1015}
I/PackageManager( 8603): Verification timed out for file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk
I/PackageManager( 8603): Continuing with installation of file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk
W/Watchdog( 8603): *** WATCHDOG KILLING SYSTEM PROCESS: Blocked in handler on PackageManager (PackageManager)
W/Watchdog( 8603): PackageManager stack trace:
W/Watchdog( 8603): at android.os.BinderProxy.transact(Native Method)
W/Watchdog( 8603): at com.android.internal.app.IMediaContainerService$Stub$Proxy.copyResource(IMediaContainerService.java:290)
W/Watchdog( 8603): at com.android.server.pm.PackageManagerService$FileInstallArgs.copyApk(PackageManagerService.java:7953)
W/Watchdog( 8603): at com.android.server.pm.PackageManagerService$PackageHandler.doHandleMessage(PackageManagerService.java:960)
W/Watchdog( 8603): at com.android.server.pm.PackageManagerService$PackageHandler.handleMessage(PackageManagerService.java:593)
W/Watchdog( 8603): at android.os.Handler.dispatchMessage(Handler.java:102)
W/Watchdog( 8603): at android.os.Looper.loop(Looper.java:137)
W/Watchdog( 8603): at android.os.HandlerThread.run(HandlerThread.java:61)
W/Watchdog( 8603): *** GOODBYE!
Does this give any clues to why this won't install without rebooting?
Incidentally I also tried to copy the 1.5 GB apk to my desktop and use "adb install -r". However I get this:
could not allocate buffer for 'magic140.apk'
rm failed for /data/local/tmp/magic140.apk, No such file or directory
Incidentally, I also tried taking a Titanium Backup of the 1.2.0 app and restoring the same version over top of itself. This, too, prompted a reboot with a similar logcat message.
Sent from my Nexus 5 using Tapatalk
Any advice would be appreciated. The same apk has no trouble installing on Nexus 5.
Sent from my Nexus 5 using Tapatalk
Update: I ended up going the brute force route. In TWRP recovery I replaced the existing APK version in /data/app/ with the new one, renamed it appropriately, applied chmod 644 and chown system.system to match. Starting it up now to see if that did the trick. Appears to work.
First of all:
model: i9505
My phone is still knox free (and I want it to be like that xD)
my CSC code: PHE (spain)
I was having problems with my cm11 so i flashed the stock rom (I9505XXUBMF5_I9505OXXBMF2_PHE) later as i allways have problems with the signal y flashed the modem.bin of the XXUGNK4, not the NON-HLOS.bin 'cause the ones after the knox bootloader release breck the camera anhd other things.
Later i realize that the alarms weren't working, i found the logcat part on cm that shows my problem (or so i think)
CM11 logcat part showing permissions errors
Code:
W/PackageManager( 645): Unknown permission android.permission.REAL_GET_TASKS in package com.google.android.googlequicksearchbox
W/PackageManager( 645): Unknown permission com.google.android.apps.googlevoice.permission.AUTO_SEND in package com.google.android.googlequicksearchbox
W/PackageManager( 645): Unknown permission android.permission.MANAGE_VOICE_KEYPHRASES in package com.google.android.googlequicksearchbox
W/PackageManager( 645): Unknown permission com.android.chrome.PRERENDER_URL in package com.google.android.googlequicksearchbox
W/PackageManager( 645): Unknown permission com.google.android.launcher.permission.CONTENT_REDIRECT in package com.google.android.googlequicksearchbox
W/PackageManager( 645): Not granting permission android.permission.DELETE_PACKAGES to package com.svox.pico (protectionLevel=18 flags=0x8be45)
W/PackageManager( 645): Unknown permission com.google.android.gms.permission.CAR_SPEED in package com.google.android.apps.maps
W/PackageManager( 645): Unknown permission com.cyngn.cmstats.SEND_ANALYTICS in package com.android.dialer
W/PackageManager( 645): Not granting permission android.permission.BIND_APPWIDGET to package com.anddoes.launcher (protectionLevel=18 flags=0x58be44)
W/PackageManager( 645): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.anddoes.launcher
W/PackageManager( 645): Unknown permission com.htc.launcher.permission.READ_SETTINGS in package com.anddoes.launcher
W/PackageManager( 645): Unknown permission org.adw.launcher.permission.READ_SETTINGS in package com.anddoes.launcher
W/PackageManager( 645): Unknown permission org.adwfreak.launcher.permission.READ_SETTINGS in package com.anddoes.launcher
W/PackageManager( 645): Unknown permission com.fede.launcher.permission.READ_SETTINGS in package com.anddoes.launcher
W/PackageManager( 645): Unknown permission com.cyanogenmod.trebuchet.permission.READ_SETTINGS in package com.anddoes.launcher
W/PackageManager( 645): Unknown permission com.teslacoilsw.launcher.permission.READ_SETTINGS in package com.anddoes.launcher
W/PackageManager( 645): Not granting permission com.google.android.gallery3d.permission.PICASA_STORE to package com.google.android.apps.photos because it was previously installed without
W/PackageManager( 645): Unknown permission android.permission.WRITE_SYNC_STATS in package com.google.android.apps.docs
W/PackageManager( 645): Not granting permission android.permission.ACCESS_SURFACE_FLINGER to package com.teamviewer.quicksupport.addon.samsung (protectionLevel=2 flags=0x8be44)
W/PackageManager( 645): Not granting permission android.permission.READ_FRAME_BUFFER to package com.teamviewer.quicksupport.addon.samsung (protectionLevel=18 flags=0x8be44)
W/PackageManager( 645): Not granting permission android.permission.INJECT_EVENTS to package com.teamviewer.quicksupport.addon.samsung (protectionLevel=18 flags=0x8be44)
W/PackageManager( 645): Not granting permission android.permission.CAPTURE_SECURE_VIDEO_OUTPUT to package com.teamviewer.quicksupport.addon.samsung (protectionLevel=18 flags=0x8be44)
W/PackageManager( 645): Not granting permission android.permission.CAPTURE_VIDEO_OUTPUT to package com.teamviewer.quicksupport.addon.samsung (protectionLevel=18 flags=0x8be44)
W/PackageManager( 645): Not granting permission org.thialfihar.android.apg.permission.READ_KEY_DETAILS to package com.fsck.k9 because it was previously installed without
W/PackageManager( 645): Not granting permission android.permission.READ_LOGS to package org.blackmart.market (protectionLevel=50 flags=0x8be44)
W/PackageManager( 645): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.google.android.onetimeinitializer
W/PackageManager( 645): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.google.android.onetimeinitializer
W/PackageManager( 645): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.cyanogenmod.trebuchet
W/PackageManager( 645): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.cyanogenmod.trebuchet
W/PackageManager( 645): Not granting permission com.google.android.gallery3d.permission.PICASA_STORE to package com.google.android.apps.plus because it was previously installed without
W/PackageManager( 645): Unknown permission android.permission.REAL_GET_TASKS in package com.android.vending
W/PackageManager( 645): Unknown permission android.permission.SEND_SMS_NO_CONFIRMATION in package com.android.vending
W/PackageManager( 645): Unknown permission android.permission.USE_FINGERPRINT in package com.android.vending
W/PackageManager( 645): Unknown permission android.permission.GET_PACKAGE_IMPORTANCE in package com.android.vending
W/PackageManager( 645): Unknown permission android.permission.GET_ACCOUNTS_PRIVILEGED in package com.android.vending
W/PackageManager( 645): Unknown permission android.permission.INSTALL_GRANT_RUNTIME_PERMISSIONS in package com.android.vending
W/PackageManager( 645): Unknown permission android.permission.GRANT_RUNTIME_PERMISSIONS in package com.android.vending
W/PackageManager( 645): Unknown permission android.permission.REVOKE_RUNTIME_PERMISSIONS in package com.android.vending
W/PackageManager( 645): Unknown permission android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST in package com.android.vending
W/PackageManager( 645): Unknown permission com.google.android.partnersetup.permission.WRITE_APP_PROVIDER in package com.android.vending
W/PackageManager( 645): Not granting permission android.permission.BIND_WALLPAPER to package com.google.android.GoogleCamera (protectionLevel=18 flags=0x583c44)
W/PackageManager( 645): Not granting permission android.permission.REBOOT to package eu.chainfire.supersu (protectionLevel=18 flags=0x83e05)
W/PackageManager( 645): Not granting permission android.permission.READ_DREAM_STATE to package com.google.android.gsf (protectionLevel=2 flags=0x40083e45)
W/PackageManager( 645): Unknown permission android.permission.CANCEL_NOTIFICATIONS in package org.cyanogenmod.voiceplus
W/PackageManager( 645): Unknown permission org.fdroid.fdroid.privileged.USE_SERVICE in package org.fdroid.fdroid
W/PackageManager( 645): Not granting permission android.permission.MEDIA_CONTENT_CONTROL to package com.andrew.apollo (protectionLevel=18 flags=0x18be65)
W/PackageManager( 645): Unknown permission com.baidu.permission.QCCLOUD_PROVIDER in package com.android.contacts
W/PackageManager( 645): Unknown permission com.android.vending.billing.IBillingAccountService.BIND2 in package com.google.android.gsf.login
W/PackageManager( 645): Unknown permission android.permission.USE_FINGERPRINT in package org.telegram.messenger
W/PackageManager( 645): Not granting permission android.permission.ACCESS_SURFACE_FLINGER to package com.teamviewer.quicksupport.market (protectionLevel=2 flags=0x18be44)
W/PackageManager( 645): Not granting permission android.permission.READ_FRAME_BUFFER to package com.teamviewer.quicksupport.market (protectionLevel=18 flags=0x18be44)
W/PackageManager( 645): Not granting permission android.permission.INJECT_EVENTS to package com.teamviewer.quicksupport.market (protectionLevel=18 flags=0x18be44)
W/PackageManager( 645): Unknown permission com.android.remotecontrolservice.REMOTE_CONTROL in package com.teamviewer.quicksupport.market
W/PackageManager( 645): Unknown permission android.permission.READ_MEDIA_STORAGE in package com.keramidas.TitaniumBackup
W/PackageManager( 645): Not granting permission android.permission.WRITE_MEDIA_STORAGE to package com.keramidas.TitaniumBackup (protectionLevel=18 flags=0x8be44)
W/PackageManager( 645): Not granting permission android.permission.BROADCAST_SMS to package com.keramidas.TitaniumBackup (protectionLevel=2 flags=0x8be44)
W/PackageManager( 645): Not granting permission android.permission.BROADCAST_WAP_PUSH to package com.keramidas.TitaniumBackup (protectionLevel=2 flags=0x8be44)
W/PackageManager( 645): Unknown permission android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS in package com.google.android.gms
W/PackageManager( 645): Not granting permission android.permission.READ_DREAM_STATE to package com.google.android.gms (protectionLevel=2 flags=0x40483e45)
W/PackageManager( 645): Unknown permission android.permission.PROVIDE_TRUST_AGENT in package com.google.android.gms
W/PackageManager( 645): Unknown permission com.google.android.apps.enterprise.dmagent.permission.AutoSyncPermission in package com.google.android.gms
W/PackageManager( 645): Unknown permission android.permission.MANAGE_VOICE_KEYPHRASES in package com.google.android.gms
W/PackageManager( 645): Unknown permission android.permission.REAL_GET_TASKS in package com.google.android.gms
W/PackageManager( 645): Unknown permission android.permission.READ_WIFI_CREDENTIAL in package com.google.android.gms
W/PackageManager( 645): Unknown permission android.permission.SCORE_NETWORKS in package com.google.android.gms
W/PackageManager( 645): Unknown permission android.permission.CONTROL_INCALL_EXPERIENCE in package com.google.android.gms
W/PackageManager( 645): Unknown permission android.permission.USER_ACTIVITY in package com.google.android.gms
W/PackageManager( 645): Unknown permission android.permission.MODIFY_AUDIO_ROUTING in package com.google.android.gms
W/PackageManager( 645): Unknown permission com.google.android.wearable.READ_SETTINGS in package com.google.android.gms
W/PackageManager( 645): Unknown permission android.permission.INTENT_FILTER_VERIFICATION_AGENT in package com.google.android.gms
W/PackageManager( 645): Unknown permission android.permission.LOCAL_MAC_ADDRESS in package com.google.android.gms
W/PackageManager( 645): Unknown permission android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST in package com.google.android.gms
W/PackageManager( 645): Unknown permission android.permission.BODY_SENSORS in package com.google.android.gms
W/PackageManager( 645): Unknown permission android.permission.NOTIFY_PENDING_SYSTEM_UPDATE in package com.google.android.gms
W/PackageManager( 645): Unknown permission com.android.voicemail.permission.READ_VOICEMAIL in package com.google.android.gms
W/PackageManager( 645): Not granting permission android.permission.READ_LOGS to package org.uguess.android.sysinfo.pro (protectionLevel=50 flags=0x9be44)
W/PackageManager( 645): Not granting permission android.permission.SET_PREFERRED_APPLICATIONS to package com.kms.free (protectionLevel=2 flags=0x83e04)
W/PackageManager( 645): Not granting permission android.permission.WRITE_APN_SETTINGS to package com.kms.free (protectionLevel=18 flags=0x83e04)
W/PackageManager( 645): Not granting permission android.permission.MODIFY_PHONE_STATE to package com.kms.free (protectionLevel=18 flags=0x83e04)
W/PackageManager( 645): Not granting permission android.permission.READ_LOGS to package com.kms.free (protectionLevel=50 flags=0x83e04)
W/PackageManager( 645): Not granting permission android.permission.BATTERY_STATS to package com.kms.free (protectionLevel=18 flags=0x83e04)
W/PackageManager( 645): Unknown permission android.permission.WRITE_SYNC_STATS in package com.google.android.apps.docs.editors.docs
W/PackageManager( 645): Not granting permission android.permission.WRITE_SECURE_SETTINGS to package eu.chainfire.pryfi (protectionLevel=50 flags=0x8be44)
W/PackageManager( 645): Not granting permission android.permission.WRITE_MEDIA_STORAGE to package com.android.soundrecorder (protectionLevel=18 flags=0x8be45)
W/PackageManager( 645): Unknown permission com.android.launcher.permission.PRELOAD_WORKSPACE in package com.google.android.partnersetup
W/PackageManager( 645): Not granting permission android.permission.BIND_ACCESSIBILITY_SERVICE to package net.cyl.notlog (protectionLevel=2 flags=0x18be44)
W/PackageManager( 645): Unknown permission com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY in package net.cyl.notlog
W/PackageManager( 645): Unknown permission android.permission.REGISTER_CONNECTION_MANAGER in package com.google.android.talk
W/PackageManager( 645): Unknown permission com.cyanogenmod.filemanager.permissions.READ_THEME in package com.cyanogenmod.filemanager
W/PackageManager( 645): Unknown permission com.amazon.device.messaging.permission.RECEIVE in package com.skype.raider
W/PackageManager( 645): Unknown permission com.nokia.pushnotifications.permission.RECEIVE in package com.skype.raider
W/PackageManager( 645): Unknown permission com.sec.android.provider.badge.permission.READ in package com.skype.raider
W/PackageManager( 645): Unknown permission com.sec.android.provider.badge.permission.WRITE in package com.skype.raider
W/PackageManager( 645): Unknown permission com.htc.launcher.permission.READ_SETTINGS in package com.skype.raider
W/PackageManager( 645): Unknown permission com.htc.launcher.permission.UPDATE_SHORTCUT in package com.skype.raider
W/PackageManager( 645): Unknown permission com.sonyericsson.home.permission.BROADCAST_BADGE in package com.skype.raider
W/PackageManager( 645): Unknown permission com.majeur.launcher.permission.UPDATE_BADGE in package com.skype.raider
W/PackageManager( 645): Unknown permission android.permission.MMS_PUSH in package org.codeaurora.bluetooth
W/PackageManager( 645): Not granting permission android.permission.READ_LOGS to package com.SystemCleanup.Inteks.org (protectionLevel=50 flags=0x8be44)
W/PackageManager( 645): Not granting permission android.permission.MANAGE_USERS to package com.SystemCleanup.Inteks.org (protectionLevel=18 flags=0x8be44)
W/PackageManager( 645): Not granting permission android.permission.READ_LOGS to package cc.madkite.freedom (protectionLevel=50 flags=0x18be44)
W/PackageManager( 645): Unknown permission com.google.android.email.permission.READ_ATTACHMENT in package com.google.android.gm
W/PackageManager( 645): Unknown permission com.google.android.email.permission.ACCESS_PROVIDER in package com.google.android.gm
W/PackageManager( 645): Unknown permission com.google.android.gm.exchange.BIND in package com.google.android.gm
W/PackageManager( 645): Unknown permission android.permission.CANCEL_NOTIFICATIONS in package org.cyanogenmod.theme.chooser
W/PackageManager( 645): Unknown permission android.permission.WRITE_INTERNAL_STORAGE in package com.orange.miorange
W/PackageManager( 645): Unknown permission android.permission.READ_INTERNAL_STORAGE in package com.orange.miorange
W/PackageManager( 645): Not granting permission android.permission.MANAGE_DOCUMENTS to package com.orange.miorange (protectionLevel=2 flags=0x8be44)
W/PackageManager( 645): Not granting permission android.permission.MANAGE_DOCUMENTS to package com.google.android.youtube (protectionLevel=2 flags=0x583e44)
W/PackageManager( 645): Unknown permission htc.socialmanager.permission.USE_SOCIALSERVICE in package com.tumblr
W/PackageManager( 645): Unknown permission htc.socialmanager.permission.READ_SOCIAL_DATABASE in package com.tumblr
W/PackageManager( 645): Unknown permission htc.socialmanager.permission.WRITE_SOCIAL_DATABASE in package com.tumblr
W/PackageManager( 645): Unknown permission htc.socialmanager.permission.USE_SOCIALCOMPONENT in package com.tumblr
W/PackageManager( 645): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x48be45)
W/PackageManager( 645): Unknown permission com.android.deskclock.worldclock.permissions.WRITE_DATABASE in package com.android.deskclock
W/PackageManager( 645): Unknown permission com.google.android.gm.exchange.BIND in package com.google.android.calendar
W/PackageManager( 645): Unknown permission com.chrome.permission.DEVICE_EXTRAS in package com.android.chrome
W/PackageManager( 645): Unknown permission com.sec.enterprise.knox.MDM_CONTENT_PROVIDER in package com.android.chrome
W/PackageManager( 645): Unknown permission archos.permission.FULLSCREEN.FULL in package org.ppsspp.ppsspp
That was when i have everything back (apps, supersu, configs, etc)
So I blame some configs on the system and after wipe system, cache, data, Int Storage and dalvik I installed a fresh cm11 onto the phone (cm-11-20160410-NIGHTLY-jflte), didn't install supersu neither the open-gapps, only CM.
but the problem with the permisions wasn't gone (almost the same logacat part, if not the same)
As my last resort, I flashed another stock ROM (I9505XXUBMGA_I9505OXXBMH1_PHE [the last knox-free from spain wich I now])
with the following odin config:
PIT file loaded
Auto Reboot: unticked
Re-Partion: ticked
F.Reset Time: ticked
Nand Erase All, Phone EFS Clear and Phone Bootloader Update ticked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
with the hope that some black magic happend and the problem would be gone andd the flash Cm
This is the log of odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
And this is the phone's one:
Code:
ODIN MODE
PRODUCT NAME: GT-I9505
CUSTOM BINATY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL (notice that i'm flashing this after the actual flash to make this post)
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
START [224,1440]
ERASING USERDATA PARTITION.
BAR [240,1440]
END [240,1440]
I took off the battery for a minute or so, the put it back
boot the phone, let it boot recovery a fill the first start statusbar
the phone reboots, i enter recovery, wipe data and cache
And then let the phone boot the system
Every seems nice, the phone boots in no time and ask pinof the sim, i get trhough the initial setup with no pain and then got to settings and enable debugging, reboot the phone and pipe the logcat exit to a file throught abd, set an alarm tho ring on the next few minutes and power off the phone and see logcat.
This is it:
https:// drive.google.com/file/d/0B4Ox1zTG7d5feGpnUFl2QlVueWM/view?usp=sharing (XDA don't let me put links TTwTT
As you can see, the problem is still there
Code:
W/PackageManager( 782): Unknown permission com.android.launcher.permission.PRELOAD_WORKSPACE in package com.google.android.partnersetup
W/PackageManager( 782): Unknown permission android.permission.ACCESS_DEV_STORAGE in package com.sec.android.app.camera
W/PackageManager( 782): Unknown permission com.sec.chaton.TOKEN_74e548bcd7dc013c8f8b585ba11ad16b271ceebb0acbe6c001c0aecdae65f37b366963990139710b4b5c3238053d25b7940d90c9f30e04a119c6c3dd94c276d32ec19cc4a4906ccbae88b80158ce08440ba5b1d7e14b864a076e31fa3e478f51ff186b2e995cc4d9503987cc3b80efdc331d7626ae145ce1810604514abd5fd9 in package com.sec.android.app.camera
W/PackageManager( 782): Unknown permission android.permission.ACCESS_DEV_STORAGE in package com.sec.android.app.myfiles
W/PackageManager( 782): Unknown permission com.samsung.android.app.episodes.permission.IMPORT_STORYALBUM in package com.sec.android.app.myfiles
W/PackageManager( 782): Unknown permission com.sec.android.app.gallery3d.READ in package com.sec.chaton
W/PackageManager( 782): Unknown permission com.acrodea.samsung_avatar_maker.AvatarMaker_Select in package com.sec.chaton
W/PackageManager( 782): Unknown permission com.sec.android.app.gallery3d.WRITE in package com.sec.chaton
W/PackageManager( 782): Unknown permission com.sec.android.homesync.EXCLUSIVE_APP in package com.osp.app.signin
W/PackageManager( 782): Unknown permission com.samsung.android.providers.context.permission.READ_PROFILE in package com.sec.android.app.controlpanel
W/PackageManager( 782): Unknown permission com.sec.android.dualclockanalog.permission.READ_DATA in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.dualclockanalog.permission.WRITE_DATA in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.daemonapp.ap.accuweather.permission.ACCU_DAEMON_ACCESS_INTENT in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.daemonapp.ap.yahoostock.stockclock.permission.YAHOO_DAEMON_ACCESS_INTENT in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.daemonapp.ap.yahoonews.permission.YAHOO_DAEMON_ACCESS_INTENT in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.daemonapp.ap.kweather.permission.KW_DAEMON_ACCESS_INTENT in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.widgetapp.ap.edaily.stockclock.permission.EDAILY_DAEMON_ACCESS_PROVIDER in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.widgetapp.ap.edaily.stockclock.permission.EDAILY_DAEMON_ACCESS_INTENT in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.daemonapp.ap.yonhapnews.permission.YONHAP_DAEMON_ACCESS_PROVIDER in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.widgetapp.ap.yonhapnews.permission.YONHAP_DAEMON_ACCESS_INTENT in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.daemonapp.ap.sinaweather.permission.SINA_DAEMON_ACCESS_INTENT in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.widgetapp.ap.sinastock.stockclock.permission.SINA_DAEMON_ACCESS_PROVIDER in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.widgetapp.ap.sinastock.stockclock.permission.SINA_DAEMON_ACCESS_INTENT in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.daemonapp.ap.sinanews.permission.SINA_DAEMON_ACCESS_PROVIDER in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.widgetapp.ap.sinanews.permission.SINA_DAEMON_ACCESS_INTENT in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.daemonapp.ap.camobile.permission.CAMOBILE_DAEMON_ACCESS_PROVIDER in package com.sec.android.app.clockpackage
W/PackageManager( 782): Unknown permission com.sec.android.app.sbrowser.operatorbookmarks.permission.READ_OPERATOR_BOOKMARKS in package com.samsung.sec.android.application.csc
W/PackageManager( 782): Unknown permission com.sec.android.app.sbrowser.operatorbookmarks.permission.WRITE_OPERATOR_BOOKMARKS in package com.samsung.sec.android.application.csc
W/PackageManager( 782): Unknown permission com.sec.android.permission.READ_MEMO in package com.samsung.sec.android.application.csc
W/PackageManager( 782): Unknown permission com.sec.android.permission.WRITE_MEMO in package com.samsung.sec.android.application.csc
W/PackageManager( 782): Unknown permission com.sec.android.widgetapp.q1_penmemo.permission.READ in package com.samsung.sec.android.application.csc
W/PackageManager( 782): Unknown permission com.sec.android.widgetapp.q1_penmemo.permission.WRITE in package com.samsung.sec.android.application.csc
W/PackageManager( 782): Unknown permission com.sec.android.permission.VIDEOHUB in package com.sec.android.app.videoplayer
W/PackageManager( 782): Unknown permission android.permission.SYSTEM_ALERT in package com.sec.android.app.videoplayer
W/PackageManager( 782): Unknown permission com.sec.android.permission.READ_MEMO in package com.sec.android.app.DataCreate
W/PackageManager( 782): Unknown permission com.sec.android.permission.WRITE_MEMO in package com.sec.android.app.DataCreate
W/PackageManager( 782): Unknown permission com.sec.android.widgetapp.q1_penmemo.permission.READ in package com.sec.android.app.DataCreate
W/PackageManager( 782): Unknown permission com.sec.android.widgetapp.q1_penmemo.permission.WRITE in package com.sec.android.app.DataCreate
W/PackageManager( 782): Unknown permission android.permission.ACCESS_DEV_STORAGE in package com.samsung.android.app.episodes
W/PackageManager( 782): Unknown permission com.diotek.penmemo.util.PenMemoProvider.permission.READ in package com.samsung.android.app.episodes
W/PackageManager( 782): Unknown permission com.diotek.penmemo.util.PenMemoProvider.permission.WRITE in package com.samsung.android.app.episodes
The alarm of course never rang
So what should I do
I was also faced that problem..then I sold my phone.
Sent from my GT-P3100 using Tapatalk
sagar0835 said:
I was also faced that problem..then I sold my phone.
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
Mine is still on warranty (2 years left) so today I amy go to the technical support guy of the store to know if he can do something.
The only problem is knox, I shouldn't let them flash anything without me knowing it.
I also thought of selling the phone, but I'm not totally sure of that, 'cause now its value may have decreased and i cannot get anything better or equal with the money i can get from it
Thanks for the reply ^_^
I had sold it to around $200.
I didn't knew how to solve that problem..you should try to make it solve.
Sent from my GT-P3100 using Tapatalk
Darkangeel_hd said:
Mine is still on warranty (2 years left) so today I amy go to the technical support guy of the store to know if he can do something.
The only problem is knox, I shouldn't let them flash anything without me knowing it.
I also thought of selling the phone, but I'm not totally sure of that, 'cause now its value may have decreased and i cannot get anything better or equal with the money i can get from it
Thanks for the reply ^_^
Click to expand...
Click to collapse
do you have a warranty left if it will show you've been flashing things via odin, probably not. never heard of knox bootloaders breaking things before. hundreds of users have used them happily enough as far as I'm aware. flashing the latest firmware is the most likely thing they'll do in a service centre, you need to mention that upfront and even stick a note on your screen saying you don't want this done.
sorry I've nothing more helpful to add...
3mel said:
do you have a warranty left if it will show you've been flashing things via odin, probably not. never heard of knox bootloaders breaking things before. hundreds of users have used them happily enough as far as I'm aware.
sorry I've nothing more helpful to add...
Click to expand...
Click to collapse
I don't have knox, so no knox-flags here ^_^
and about counters, triangle away do the trick, so my phone is seen untouched and official
knox is bad, knox will rape your children and burn your cats!!! xD
oh yeah, didn't think of that. it's been so long since I had things that way myself.
I wonder if you'd have those errors going back to a cm10 ?
3mel said:
oh yeah, didn't think of that. it's been so long since I had things that way myself.
I wonder if you'd have those errors going back to a cm10 ?
Click to expand...
Click to collapse
The error keep apearing with every Rom y tried, stock ones included, I've been flashing and flashing all the weekend, but nothing seems to work.
I tried disabling SELinux, fixing permisions with TWRP, and I don't know what more could I do
Does anyone knows how android permissions are managed? The problems seems to be that some types of permissions have disapear, and that causes that when an app try to request that particular permisions, is treated as unknow an therefore rejected.
Well, I came form the Tech service, the selfproclaim theirselves "Geek Squad"
The "Geek Guy" asked me what a logcat is.........
And it seems that they are no longer allowed to use Odin, and also said that the only thing they could do is send the phone to Samsung, and that means knox being installed.
I got two ways, keep the phone as it is, with more than 2 years of warranty and always having the posibility of using Triangle Away to restore it; or send the phone to Samsung and let them curse it with knox, and in the moment i flash CM I lose my entire warranty.
What I choose is obvious, i keep the phone and I'll be trying to fix it during the warranty period ( I go two entire years ) and If i see that theres no way out of this situation, as my last resort, I'll let the phone to Samsung.
I will post any update i get.
If anyone have a clue on the matter, plase post it.
*****************************************************************************
PS:
If I will keep something from this day.... it will be: The thech support guy saying: "What is a logcat?"
what was that BEST BUY ? there's no reason for shop workers to know this kind of stuff.
you're dead against it I know but I'd say bite the bullet and stop caring about the warranty. marshmallow AOSP or CM is so dope I could never even consider going back to lollipop. from my very limited knowledge I'd guess your outdated bootloader as the #1 suspect behind your troubles, that's why I was curious if CM10 or maybe jellybean was better for you. with a baseband to match too...
3mel said:
what was that BEST BUY ? there's no reason for shop workers to know this kind of stuff.
you're dead against it I know but I'd say bite the bullet and stop caring about the warranty. marshmallow AOSP or CM is so dope I could never even consider going back to lollipop. from my very limited knowledge I'd guess your outdated bootloader as the #1 suspect behind your troubles, that's why I was curious if CM10 or maybe jellybean was better for you. with a baseband to match too...
Click to expand...
Click to collapse
He wasn't a shop worker, and I don't demand shop workers to know geeky stuff, but that guy was supposed to be a professional service technician, thats the reason.
I was expecting that a technician will know more than what i really known, he didn't event suggest me to wipe the data.... he did nothing.
I have a S4 Intl i9505 and I'm currently using CM12.1 snapshot, my phone works perfectly, other than some minor bugs with Bluetooth audio. Couldn't be happier now, I grew to hate the stock Samsung bloat Android.
My vote is load TWRP and flash the CM12.1
missioner said:
I have a S4 Intl i9505 and I'm currently using CM12.1 snapshot, my phone works perfectly, other than some minor bugs with Bluetooth audio. Couldn't be happier now, I grew to hate the stock Samsung bloat Android.
My vote is load TWRP and flash the CM12.1
Click to expand...
Click to collapse
The problem is that the permission error was in every single thing I flashed. I tried from CM 10 to 13 and form stock 4.2.2 to 4.3 from even diferent regions.
But I thing I may have came aout with a solution and why is this happening.
I'm actually working on it.
Thanks, and i thinbk like you, I came to a point when i don't even look the stock rom, I get in download mode, flash TWRP, boot TWRP and flash a CM version xD
thanks for the reply.
3mel said:
what was that BEST BUY ? there's no reason for shop workers to know this kind of stuff.
you're dead against it I know but I'd say bite the bullet and stop caring about the warranty. marshmallow AOSP or CM is so dope I could never even consider going back to lollipop. from my very limited knowledge I'd guess your outdated bootloader as the #1 suspect behind your troubles, that's why I was curious if CM10 or maybe jellybean was better for you. with a baseband to match too...
Click to expand...
Click to collapse
Cm10 gave me the same problems, and I actually update the baseband so that way it match with the system as much as posible
I think that I fixed my issue.
After reflashing a whole bunch of times I realized that my problem was almost solved, and knowing the nature of it.
After some research I found that the permissions on android are some xml files stored in "/etc/permissions" these files are the ones that contains every permission that could be requested in the system, and they're updated when you install an app that add a permision.
So I knew where the problem was, so by flashing any rom that overwrite the permissions correctly it should be solved (and yes, you only need to do that).
But the problem was still present in the logcat. So to compare, i asked a friend to hang me his permissions folder, he has an HTC with Cm12, but the thing is pretty much the same, and the first part of his logcat.
After comparing and reading mine and his from the beggining to the en line by line, I noticed what was happening.
The errors wile still present weren't the same, the part when the clock permission to power on the device was rejected wasn't present anymore, and so on with otheres; but there were also a lot of "Unknown permission error".
after sesearching another time about how android apps work, i ended up with the following conclusion:
Apps are made so that they can ask permissions from other apps, even if they are not present in the system, thus resulting in a "Unknown permission error" 'cause that especific permission from that especific app, that is not installed, is therefore not present in /etc/permissions
So there error is the stock ROM of Samsung are "normal" up to a certain extent; cuase the own apps on the clean samsung ROM request permissions from apps that the rom itself didn't have (i.e. the some galery3d ones)
there are errors but they are not critical ones, so everything works "fine".
Summarizing: the Samsung ROM apps request permissions that the Samsung ROM itself cannot provide, ending up in some "Unknown permission" errors, but they are not significant, since they apps that request then can actually work without then in most of the cases.
So we can say that is a problem of "inconsistency" on the stock ROM itself that don't provide the permission that it request.
Also I should point out that this last time I didn't restore my apps with a backup, i installed all of them another time, just to be sure that the permissions were created correctly.
Only once i have everything working as it should, I restored the data of some cherrypicked apps (of course not system ones xD).
Hello
I recently got a new phone (Xperia 10 III)
I wanted to pair my watch (Casio F20A) to it...
Problem, after reset I was unable to pair my watch again, it get stuck during "Updating informations" step.
I eventually found like 6 other case reported for this exact same problem and watch.
So I did some ADB log and finally found the problem, the app connection break at this exact moment
04-08 11:50:24.864 27178 29358 I CwSetup.CreateConfig: re-enabling connection
04-08 11:50:24.865 24198 26679 E WearableService: enableConnection is no longer supported. Use enableDeviceConnection instead.
04-08 11:50:24.867 27178 29358 E CwSetup.CreateConfig: Unable to enable connection.
04-08 11:50:24.870 27178 29358 I CwSetup.CreateConfig: finished creating ConnectionConfiguration: CreateConfigTask.Result{ isSuccess=false, mConfig=null }
04-08 11:50:24.870 27178 29358 E CwSetup.SetupJob: Failed to create ConnectionConfiguration
04-08 11:50:24.872 27178 27178 E PairingController: pairing failed
04-08 11:50:24.880 27178 29358 I BluetoothDevice: cancelBondProcess() for device 08:00:74:6F:E0:47 called by pid: 27178 tid: 29358
04-08 11:50:24.881 5803 8710 D bt_btif_config: btif_get_device_type: Device [08:00:74:6f:e0:47] type 3
04-08 11:50:24.881 5803 8710 I bt_btif_dm: get_cod remote_cod = 0x00080704
04-08 11:50:25.773 1096 6033 I [email protected]_handler: DeviceSleep: TX Awake, Sending SLEEP_IND
04-08 11:50:25.773 1096 6033 D [email protected]_handler: SerialClockVote: vote for UART CLK OFF
04-08 11:50:25.923 1096 5891 D [email protected]_lock: Release wakelock is released
I guess there was some update with some back compatibility mistake on WearableService.
And I need to figure which componets I should update on the Watch/Downgrade on Phone.
Any help is appreciated
Thanks
Complete details:
https://www.reddit.com/r/CasioSmartwatch/comments/uddypf