Related
Sigh. This phone has given me so many problems, I'm seriously thinking of dropping it for something else like an HTC.
GPS just sucks. It keeps wondering around and loosing satellites. It is actually dangerous driving with this thing. Also battery dies in 8-9 hours. Not cool.
BUT right at the moment I'm finding that I can no longer TEXT my friends. This happened after I came back from a trip outside my local calling area. I was able to text in Quebec but after coming back to Ontario all I can do is see my messages coming in, but when I try and read them by clicking on the message, the balloons with the conversation appear but it then crashes.
Here is the log file that I extracted using adb logcat.
I/AudioHardwareALSA( 2367): Output standby called!!. Turn off PCM device.
V/InputDevice( 2484): ID[0]=0(0) Dn(0=>1)
V/WindowManager( 2484): Dsptch > Window{47f937f8 com.android.mms/com.android.mms.ui.ConversationList paused=false}
V/WindowManager( 2484): Dsptch > Window{47f937f8 com.android.mms/com.android.mms.ui.ConversationList paused=false}
V/InputDevice( 2484): ID[0]=0(0) Up(1=>0)
V/Mms/ConversationList( 4450): onListItemClick: position=4, id=32
I/ActivityManager( 2484): Starting activity: Intent { dat=content://mms-sms/conversations/32 cmp=com.android.mms/.ui.ComposeMessageActivity }
D/Mms/ConversationList( 4450): onSaveInstanceState
D/AudioHardwareALSA( 2367):
D/AudioHardwareALSA( 2367): ALSA OPEN mode 0,device 2
I/AudioHardwareALSA( 2367): Try to open ALSA PLAYBACK device AndroidPlayback_Speaker_normal
I/Mms/compose( 4450): mEncodingType:2
I/AudioHardwareALSA( 2367): Initialized ALSA PLAYBACK device AndroidPlayback_Speaker_normal
D/AudioHardwareALSA( 2367): Set PLAYBACK PCM format to S16_LE (Signed 16 bit Little Endian)
D/AudioHardwareALSA( 2367): Using 2 channels for PLAYBACK.
D/AudioHardwareALSA( 2367): Set PLAYBACK sample rate to 44100 HZ
D/AudioHardwareALSA( 2367): Buffer size: 2048
D/AudioHardwareALSA( 2367): Latency: 46439
V/MmsProvider( 2645): Query uri=content://mms/drafts, match=6
D/Mms ( 4450): [1] setConversation null -> [4162757727;6479667280;+16479294276] (tid 32)
V/MmsSmsProvider( 2645): uri=content://mms-sms/conversations/32
I/Mms/compose( 4450): onResume mEncodingType:2
V/MmsSmsProvider( 2645): uri=content://mms-sms/conversations?simple=true
V/MmsSmsProvider( 2645): getSimpleConversations entered.
V/MmsSmsProvider( 2645): uri=content://mms-sms/undelivered
V/Mms/compose( 4450): message list : message list query is completed
V/Mms/MessageListItem( 4450): bind uri 1 content://sms/661
V/Mms/MessageListItem( 4450): bind uri 3 content://sms/661
I/wpa_supplicant( 2552): WPS-AP-AVAILABLE
I/wpa_supplicant( 2552): CTRL-EVENT-NO-CONNECTION
I/WifiMonitor( 2484): Event [ SCAN-RESULTS ]
I/WifiMonitor( 2484): Event [WPS-AP-AVAILABLE ]
I/WifiMonitor( 2484): Event [CTRL-EVENT-NO-CONNECTION]
I/NetworkStatusReceiver( 3467): action: android.net.wifi.SCAN_RESULTS
I/NetworkStatusReceiver( 3467): action: android.net.wifi.SHOW_AP_LIST_DIALOG
E/WifiManager( 3467): showApDialog
I/WifiService( 2484): isShowingAccessPointListDialog():false
I/WifiService( 2484): setShowAccessPointListDialog():false
V/Mms/MessageListItem( 4450): bind uri 1 content://sms/660
V/Mms/MessageListItem( 4450): bind uri 3 content://sms/660
V/Mms/MessageListItem( 4450): bind uri 1 content://sms/659
V/Mms/MessageListItem( 4450): bind uri 3 content://sms/659
D/dalvikvm( 4450): GC_FOR_MALLOC freed 3752 objects / 250280 bytes in 31ms
V/MmsSmsProvider( 2645): uri=content://mms-sms/conversations/32
V/MmsSmsProvider( 2645): uri=content://mms-sms/undelivered
V/MmsProvider( 2645): Query uri=content://mms/inbox, match=2
D/dalvikvm( 2645): GC_FOR_MALLOC freed 10549 objects / 584392 bytes in 43ms
V/MmsProvider( 2645): Query uri=content://mms, match=0
I/Database( 2794): sqlite returned: error code = 14, msg = cannot open file at source line 25467
I/Database( 2794): sqlite returned: error code = 14, msg = cannot open file at source line 25467
I/Database( 2794): sqlite returned: error code = 14, msg = unable to open database file
E/Database( 2794): CREATE TABLE android_metadata failed
E/Database( 2794): Failed to setLocale() when constructing, closing the database
E/Database( 2794): android.database.sqlite.SQLiteException: unable to open database file
E/Database( 2794): at android.database.sqlite.SQLiteDatabase.native_setLocale(Native Method)
E/Database( 2794): at android.database.sqlite.SQLiteDatabase.setLocale(SQLiteDatabase.java:2059)
E/Database( 2794): at android.database.sqlite.SQLiteDatabase.<init>(SQLiteDatabase.java:1927)
E/Database( 2794): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:883)
E/Database( 2794): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:960)
E/Database( 2794): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:953)
E/Database( 2794): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:597)
E/Database( 2794): at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:203)
E/Database( 2794): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:98)
E/Database( 2794): at com.sec.android.provider.badge.BadgeProvider.update(BadgeProvider.java:124)
E/Database( 2794): at android.content.ContentProvider$Transport.update(ContentProvider.java:216)
E/Database( 2794): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:201)
E/Database( 2794): at android.os.Binder.execTransact(Binder.java:288)
E/Database( 2794): at dalvik.system.NativeStart.run(Native Method)
E/DatabaseUtils( 2794): Writing exception to parcel
E/DatabaseUtils( 2794): android.database.sqlite.SQLiteException: unable to open database file
E/DatabaseUtils( 2794): at android.database.sqlite.SQLiteDatabase.native_setLocale(Native Method)
E/DatabaseUtils( 2794): at android.database.sqlite.SQLiteDatabase.setLocale(SQLiteDatabase.java:2059)
E/DatabaseUtils( 2794): at android.database.sqlite.SQLiteDatabase.<init>(SQLiteDatabase.java:1927)
E/DatabaseUtils( 2794): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:883)
E/DatabaseUtils( 2794): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:960)
E/DatabaseUtils( 2794): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:953)
E/DatabaseUtils( 2794): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:597)
E/DatabaseUtils( 2794): at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:203)
E/DatabaseUtils( 2794): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:98)
E/DatabaseUtils( 2794): at com.sec.android.provider.badge.BadgeProvider.update(BadgeProvider.java:124)
E/DatabaseUtils( 2794): at android.content.ContentProvider$Transport.update(ContentProvider.java:216)
E/DatabaseUtils( 2794): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:201)
E/DatabaseUtils( 2794): at android.os.Binder.execTransact(Binder.java:288)
E/DatabaseUtils( 2794): at dalvik.system.NativeStart.run(Native Method)
W/dalvikvm( 4450): threadid=10: thread exiting with uncaught exception (group=0x4001d7d0)
E/AndroidRuntime( 4450): FATAL EXCEPTION: Thread-19
E/AndroidRuntime( 4450): android.database.sqlite.SQLiteException: unable to open database file
E/AndroidRuntime( 4450): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:158)
E/AndroidRuntime( 4450): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:114)
E/AndroidRuntime( 4450): at android.content.ContentProviderProxy.update(ContentProviderNative.java:506)
E/AndroidRuntime( 4450): at android.content.ContentResolver.update(ContentResolver.java:707)
E/AndroidRuntime( 4450): at com.android.mms.transaction.MessagingNotification.updateBadgeProvider(MessagingNotification.java:1051)
E/AndroidRuntime( 4450): at com.android.mms.transaction.MessagingNotification.blockingUpdateNewMessageIndicator(MessagingNotification.java:218)
E/AndroidRuntime( 4450): at com.android.mms.transaction.MessagingNotification$1.run(MessagingNotification.java:179)
E/AndroidRuntime( 4450): at java.lang.Thread.run(Thread.java:1096)
I/ ( 2484): dumpmesg > /data/log/dumpstate_app_error.log
W/ActivityManager( 2484): Force finishing activity com.android.mms/.ui.ComposeMessageActivity
W/ActivityManager( 2484): Force finishing activity com.android.mms/.ui.ConversationList
I/dumpstate( 4471): beginDoes anyone have any idea what is going on? Your help is greatly appreciated.
A
Model: GT-I9000M
Firmware: 2.2
Baseband: I9000UGJL2
Kernel: 2.7.32.9 shout.lee(at)SEP-09 #3
Build: FROYO.UGJL2
Well, I got it back again. Here is what I did to get it back for those who get in the same situation.
I used Titanium Backup to backup the [SMS/MMS PREFS] Messaging 2.2, wiped the data and restored it. Looks like there was something corrupt in the preferences or that part of the DB. WTF!!! ((
A
I am trying to access System-Settings-Accounts, but cannot find it on my NST rooted w Nook Manager.
I installed one touch Sync Settings from the market, but when I click on it, the NST reboots.
I found AccountAndSyncSettings.apk in the /system/app folder, but installation fails.
I copied the file over to my desktop and did an adb install. [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
logcat info:
D/AndroidRuntime( 4396):
D/AndroidRuntime( 4396): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I/AndroidRuntime( 4396): Heap size: -Xmx64m
D/AndroidRuntime( 4396): CheckJNI is OFF
D/dalvikvm( 4396): creating instr width table
D/AndroidRuntime( 4396): --- registering native functions ---
I/NATIVE-EPD( 4396): framebuffer_handle: 20
D/PackageParser( 3554): Scanning package: /data/app/vmdl13223.tmp
D/dalvikvm( 3554): GC freed 34328 objects / 2066216 bytes in 101ms
E/PackageManager( 3554): Package com.android.providers.subscribedfeeds has no si
gnatures that match those in shared user android.uid.system; ignoring!
W/PackageManager( 3554): Package couldn't be installed in /data/app/com.android.
providers.subscribedfeeds.apk
D/AndroidRuntime( 4396): Shutting down VM
D/dalvikvm( 4396): DestroyJavaVM waiting for non-daemon threads to exit
D/dalvikvm( 4396): DestroyJavaVM shutting VM down
D/dalvikvm( 4396): HeapWorker thread shutting down
D/dalvikvm( 4396): HeapWorker thread has shut down
D/jdwp ( 4396): JDWP shutting down net...
I/jdwp ( 4396): adbd disconnected
D/dalvikvm( 4396): VM cleaning up
D/dalvikvm( 4396): LinearAlloc 0x0 used 631916 of 5242880 (12%)
D/dalvikvm( 3554): GC freed 4440 objects / 255744 bytes in 121ms
Please advise...
You don't install it. The workaround to change sync settings is to use the gmail app to add an account and enter the same account information you already have setup and you will be able to update the sync settings.
RandyB201 said:
I am trying to access System-Settings-Accounts, but cannot find it on my NST rooted w Nook Manager.
I installed one touch Sync Settings from the market, but when I click on it, the NST reboots.
I found AccountAndSyncSettings.apk in the /system/app folder, but installation fails.
I copied the file over to my desktop and did an adb install. [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
Please advise...
Click to expand...
Click to collapse
You don't install apk's in /system/app/ you just put them in /system/app/ and after reboot start working.
Try to access AccountAndSyncSettings using 'NookColorTools'. If NCT does not allow access to these settings try using 'apktool' to decompile package and try to infer correct 'am start' command from the directory structure,filenames and code. Experiment with 'am start' using adb.
This is a Nook Simple Touch. NookColorTools sounds like something from the nook color?
osowiecki said:
You don't install apk's in /system/app/ you just put them in /system/app/ and after reboot start working.
Try to access AccountAndSyncSettings using 'NookColorTools'. If NCT does not allow access to these settings try using 'apktool' to decompile package and try to infer correct 'am start' command from the directory structure,filenames and code. Experiment with 'am start' using adb.
Click to expand...
Click to collapse
please clarify...
If I understand you correctly, I need to:
1) open gmail
2) add an account (btw, when I click the add account button, it just goes back to the inbox...)
3) enter the same account info i already have in there
I am unclear on how I access sync settings after that is done?
straygecko said:
You don't install it. The workaround to change sync settings is to use the gmail app to add an account and enter the same account information you already have setup and you will be able to update the sync settings.
Click to expand...
Click to collapse
RandyB201 said:
If I understand you correctly, I need to:
1) open gmail
2) add an account (btw, when I click the add account button, it just goes back to the inbox...)
3) enter the same account info i already have in there
I am unclear on how I access sync settings after that is done?
Click to expand...
Click to collapse
Add account shouldn't send you back to the inbox. It should work like this:
Open gmail
Open menu, click on accounts
Click on Add account button
Click on the big g on the Add an account screen
Click Next
Click Sign In
Enter your gmail username and password
Click Sign In
Now you should be on the Data & synchronization page with check boxes for Contacts, Calendar and Gmail. Check/uncheck what you want and click on Finish.
If add account continues to send you back to the inbox get a logcat when that happens and post it.
---------- Post added at 12:37 PM ---------- Previous post was at 12:29 PM ----------
RandyB201 said:
This is a Nook Simple Touch. NookColorTools sounds like something from the nook color?
Click to expand...
Click to collapse
Yes but some of the things in NCT work on the NST. But don't bother installing NCT for this as the Account & Sync Settings isn't there. Don't try digging the intent for am start out of the apk either as market tools like one touch sync settings have already figured that out and that's what they do. I tried all this when I put together NTGAppsAttack and could never get Account & Sync Settings to work. IIRC, its a layout issue. There is something funny about what B&N did to Android on the NST that causes some apps to die with layout issues. If I did remember correctly it might be possible to hack the apk up to get it to work but I don't have the time or motivation to do it as the gmail workaround does everything I need.
logcat...
I am still getting a brief flash and a return to the inbox when I puch the Add Account Button.
logcat info:
D/DeviceManagerBroadcastReceiver( 1110): action (com.bn.devicemanager.ACTION_HAN
DLE_CRASH)
I/dalvikvm( 1235): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 1235): Sending signal. PID: 1235 SIG: 9
I/WindowManager( 785): WIN DEATH: Window{4a0b9b38 com.google.android.gm/com.goo
gle.android.gm.MailboxSelectionActivity paused=false}
I/ActivityManager( 785): Process com.google.android.gm (pid 1235) has died.
I/WindowManager( 785): WIN DEATH: Window{4a1a72f8 com.google.android.gm/com.goo
gle.android.gm.ConversationListActivity paused=false}
I/ActivityManager( 785): Start proc com.google.android.gm for activity com.goog
le.android.gm/.ConversationListActivity: pid=1326 uid=10022 gids={3003}
E/TC ( 1134): KPICollector: 1375724620795 platform process_start {"processN
ame":"com.google.android.gm"}
D/SurfaceFlinger( 785): Frame buffer posted; elapsed time = 22 msecs
I/dalvikvm( 1326): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=38)
I/UsageStats( 785): Unexpected resume of com.google.android.gm while already re
sumed in com.google.android.gm
I/dalvikvm( 1326): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=46)
E/TC ( 1134): KPICollector: 1375724621021 ActivityManager foreground {"comp
onent":"com.google.android.gm/.ConversationListActivity"}
I/ActivityThread( 1326): Publishing provider com.google.android.gmail.Suggestion
Provider: com.google.android.gm.SuggestionsProvider
I/ActivityThread( 1326): Publishing provider com.google.android.gm.attachmentspr
eviews: com.google.android.gm.AttachmentPreviewProvider
V/Gmail ( 1326): onCreate(), id=com.google.android.gm.ConversationListActivity
@49fc4e28
D/Gmail ( 833): MailProvider.query: content://gmail-ls/labels/[email protected]
.com(null, null)
D/Gmail ( 1326): SETTING ACCOUNT, USER:[email protected]
D/Gmail ( 833): MailProvider.query: content://gmail-ls/conversations/randyb20
[email protected](, null)
V/Gmail ( 1326): onStart(), [email protected]
49fc4e28
V/Gmail ( 1326): onRestoreInstanceState(), id=com.google.android.gm.Conversati
[email protected]
V/Activity( 1326): performResume()
D/EPD#ActivityResume( 785): resetRegion 4
D/NATIVE-EPD( 785): epd_reset_region: 0x10
D/EPD#ActivityResume( 785): resetRegion 5
D/NATIVE-EPD( 785): epd_reset_region: 0x20
D/EPD#ActivityResume( 785): resetRegion 6
D/NATIVE-EPD( 785): epd_reset_region: 0x40
D/EPD#ActivityResume( 785): resetRegion 7
D/NATIVE-EPD( 785): epd_reset_region: 0x80
D/EPD#ActivityResume( 785): Disable EPD for 350ms!!!!!!!!
V/Gmail ( 1326): onResume()
I/DeviceManagerHandler( 1110): HandleMessage(): msg.what (1)
I/global ( 1110): Default buffer size used in BufferedWriter constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
I/LogcatProcessor( 1110): LOG END MARKER - 1375724621902
D/Gmail ( 833): clearNewUnreadMailForNotificationLabelIfNeeded. Count: 0, lab
el: -5/^^unseen-^i
D/Gmail ( 833): clearNewUnreadMailForNotificationLabelIfNeeded. Count: 0, lab
el: -6/^^unseen-^^vmi
W/InputManagerService( 785): Got RemoteException sending setActive(false) notif
ication to pid 1235 uid 10022
I/ActivityManager( 785): Displayed activity com.google.android.gm/.Conversation
ListActivity: 1530 ms (total 1530 ms)
D/SurfaceFlinger( 785): Frame buffer posted; elapsed time = 27 msecs
D/dalvikvm( 1110): GC freed 4130 objects / 418424 bytes in 145ms
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
D/WindowManager( 785): CALLING monitor
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
D/WindowManager( 785): CALLING monitor
V/Gmail ( 1326): onPause(), [email protected]
49fc4e28
W/Process ( 785): Unable to open /proc/1235/status
E/TC ( 1134): KPICollector: 1375724628487 ActivityManager background {"comp
onent":"com.google.android.gm/.ConversationListActivity"}
E/TC ( 1134): KPICollector: 1375724628496 ActivityManager foreground {"comp
onent":"com.harasoft.relaunch/.AllApplications"}
I/PowerManagerService( 785): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
straygecko said:
Add account shouldn't send you back to the inbox. It should work like this:
Open gmail
Open menu, click on accounts
Click on Add account button
Click on the big g on the Add an account screen
Click Next
Click Sign In
Enter your gmail username and password
Click Sign In
Now you should be on the Data & synchronization page with check boxes for Contacts, Calendar and Gmail. Check/uncheck what you want and click on Finish.
If add account continues to send you back to the inbox get a logcat when that happens and post it.
---------- Post added at 12:37 PM ---------- Previous post was at 12:29 PM ----------
Yes but some of the things in NCT work on the NST. But don't bother installing NCT for this as the Account & Sync Settings isn't there. Don't try digging the intent for am start out of the apk either as market tools like one touch sync settings have already figured that out and that's what they do. I tried all this when I put together NTGAppsAttack and could never get Account & Sync Settings to work. IIRC, its a layout issue. There is something funny about what B&N did to Android on the NST that causes some apps to die with layout issues. If I did remember correctly it might be possible to hack the apk up to get it to work but I don't have the time or motivation to do it as the gmail workaround does everything I need.
Click to expand...
Click to collapse
Do you have B&N apps disabled? If so, reenable and try again. B&N messed with the android authentication stuff and has their own account types. Since you aren't even getting to the page where you select the account type (Google and two generic android) I suspect it might be looking for disabled B&N account stuff and crashing.
The logcat isn't telling me much - is there anything earlier in the log of interest? /data/anr/traces.txt also might help but I'm not optimistic on that one.
Don't try digging the intent for am start out of the apk either as market tools like one touch sync settings have already figured that out and that's what they do.
Click to expand...
Click to collapse
am start -a android.settings.SYNC_SETTINGS
It does not work or you have just missed something?
Got the command from decompiled "AccountAndSyncSettings.apk".
AndroidManifest.xml.
{
"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"
}
osowiecki said:
am start -a android.settings.SYNC_SETTINGS
It does not work or you have just missed something?
Got the command from decompiled "AccountAndSyncSettings.apk".
AndroidManifest.xml.
Click to expand...
Click to collapse
It crashes android and restarts. I was wrong about it being a layout issue. Its a null pointer exception.
Code:
20:43:39.624 Debug AccountSettings 670 added authority com.android.contacts to accountType com.google
20:43:39.624 Debug AccountSettings 670 added authority calendar to accountType com.google
20:43:39.624 Debug AccountSettings 670 added authority gmail-ls to accountType com.google
20:43:39.624 Debug AccountSettings 670 added authority subscribedfeeds to accountType com.google
20:43:39.624 Warning dalvikvm 670 threadid=21: thread exiting with uncaught exception (group=0x4001b170)
20:43:39.624 Error AndroidRuntime 670 Uncaught handler: thread android.server.ServerThread exiting due to uncaught exception
20:43:39.624 Error AndroidRuntime 670 *** EXCEPTION IN SYSTEM PROCESS. System will crash.
20:43:39.624 Error dalvikvm 670 Invalid debug info stream. class Lcom/android/server/ServerThread;; proto ()V
20:43:39.733 Error AndroidRuntime 670 java.lang.NullPointerException
20:43:39.733 Error AndroidRuntime 670 at com.android.settings.ManageAccountsSettings.onSyncStateUpdated(ManageAccountsSettings.java:187)
20:43:39.733 Error AndroidRuntime 670 at com.android.settings.ManageAccountsSettings.onAccountsUpdated(ManageAccountsSettings.java:244)
20:43:39.733 Error AndroidRuntime 670 at android.accounts.AccountManager$10.run(AccountManager.java:826)
20:43:39.733 Error AndroidRuntime 670 at android.os.Handler.handleCallback(Handler.java:587)
20:43:39.733 Error AndroidRuntime 670 at android.os.Handler.dispatchMessage(Handler.java:92)
20:43:39.733 Error AndroidRuntime 670 at android.os.Looper.loop(Looper.java:123)
20:43:39.733 Error AndroidRuntime 670 at com.android.server.ServerThread.run(SystemServer.java:334)
20:43:39.733 Info Process 670 Sending signal. PID: 670 SIG: 9
20:43:39.733 Info ActivityThread 896 Removing dead content provider: subscribedfeeds
20:43:39.733 Info ActivityThread 896 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 1004 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 987 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 1073 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 1066 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 932 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 738 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 724 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 717 Removing dead content provider: settings
20:43:39.733 Info ServiceManager 746 service 'SurfaceFlinger' died
20:43:39.733 Info ServiceManager 746 service 'batteryinfo' died
20:43:39.733 Info ServiceManager 746 service 'entropy' died
20:43:39.733 Info ServiceManager 746 service 'telephony.registry' died
20:43:39.733 Info ServiceManager 746 service 'usagestats' died
20:43:39.733 Info ServiceManager 746 service 'epd' died
20:43:39.733 Info ServiceManager 746 service 'power' died
20:43:39.733 Info ServiceManager 746 service 'activity.senders' died
20:43:39.733 Info ServiceManager 746 service 'activity.services' died
20:43:39.733 Info ServiceManager 746 service 'activity.broadcasts' died
20:43:39.733 Info ServiceManager 746 service 'cpuinfo' died
20:43:39.733 Info ServiceManager 746 service 'content' died
20:43:39.733 Info ServiceManager 746 service 'package' died
20:43:39.733 Info ServiceManager 746 service 'statusbar' died
20:43:39.733 Info ServiceManager 746 service 'activity' died
20:43:39.733 Info ServiceManager 746 service 'meminfo' died
20:43:39.733 Info ServiceManager 746 service 'netstat' died
20:43:39.733 Info ServiceManager 746 service 'account' died
20:43:39.733 Info ServiceManager 746 service 'activity.providers' died
20:43:39.733 Info ServiceManager 746 service 'clipboard' died
20:43:39.733 Info ServiceManager 746 service 'backup' died
20:43:39.733 Info ServiceManager 746 service 'appwidget' died
20:43:39.733 Info ServiceManager 746 service 'audio' died
20:43:39.733 Info ServiceManager 746 service 'permission' died
20:43:39.733 Info ServiceManager 746 service 'input_method' died
20:43:39.733 Info ServiceManager 746 service 'battery' died
20:43:39.733 Info ServiceManager 746 service 'hardware' died
20:43:39.733 Info ServiceManager 746 service 'alarm' died
20:43:39.733 Info ServiceManager 746 service 'sensor' died
20:43:39.733 Info ServiceManager 746 service 'window' died
20:43:39.733 Info ServiceManager 746 service 'wifi' died
20:43:39.733 Info ServiceManager 746 service 'wallpaper' died
20:43:39.733 Info ServiceManager 746 service 'autoshutdown' died
20:43:39.733 Info ActivityThread 811 Removing dead content provider: settings
20:43:39.733 Info ActivityThread 768 Removing dead content provider: settings
20:43:39.733 Info ServiceManager 746 service 'devicestoragemonitor' died
20:43:39.733 Info ServiceManager 746 service 'connectivity' died
20:43:39.733 Info ServiceManager 746 service 'accessibility' died
20:43:39.733 Info ServiceManager 746 service 'location' died
20:43:39.733 Info ServiceManager 746 service 'search' died
20:43:39.733 Info ServiceManager 746 service 'notification' died
20:43:39.733 Info ServiceManager 746 service 'mount' died
20:43:39.733 Info ServiceManager 746 service 'checkin' died
20:43:39.733 Error installd 756 eof
20:43:39.733 Error installd 756 failed to read size
20:43:39.733 Info installd 756 closing connection
20:43:39.843 Info Zygote 663 Exit zygote because system server (670) has terminated
20:43:40.170 Debug AndroidRuntime 1197
20:43:40.170 Debug AndroidRuntime 1197 >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I'm pretty stock. Only rooted with NookManager and NTGAppsAttack. All B&N apps enabled. A few other apps installed but not too much. What kind of customization do you have? Maybe we can track down what makes it work on your device.
some answers...
straygecko said:
Do you have B&N apps disabled? If so, reenable and try again. B&N messed with the android authentication stuff and has their own account types. Since you aren't even getting to the page where you select the account type (Google and two generic android) I suspect it might be looking for disabled B&N account stuff and crashing.
Click to expand...
Click to collapse
Here are the apps in my list:
ADB Konnect
Adding Machine
Appstore
Browser
Calculator
Calendar
ColorNote
Contacts
DeviceRegistrator
FBReader
Gallery
Gmail
Kingsoft Office
Library
Market
MemoryInfo-SwapCheck
Music
News and Weather
NOOK friends
Nook Touch Mod Manager
NookHWTest, version
Search Market
Settings
Shop
Social
Superuser
Swapper 2
Talk
TestCenterService
Zo Reader (This reminded me I want to uninstall this, I like FBReader...)
Tasks running:
ReLaunch com.harasoft.relaunch
SYSTEM(+4) android.process.acore
Gmail com.google.android.gm
Calendar(+1) com.android.calendar
SYSTEM (+2) android.process.media
Appstore com.amazon.venezia
Reader com.bn.nook.reader.activities
Home com.bn.nook.home
Dialer (+1) com.android.phone
ADB Konnect com.rockolabs.adbkonnect
Superuser com.noshufou.android.su
Google Partner Setup com.google.android.partnersetup
Services
Android System system
SYSTEM com.google.process.gapps
DeviceManagerService com.bn.devicemanager
TestCEnterService com.bn.serviceone
Settings com.android.settings
Market com.android.vending
SYSTEM com.bn.cloud.svc:svc
WafeformDownloaderService com.bn.waveformdownloader.svc
Android keyboard com.android.inputmethod.latin
Swapper 2 lv.n30.swapper2
com.bn.nook.affiledownloadservice com.bn.nook.affiledownloadservice
com.bn.demomode com.bn.demomode
Dialer com.android.phone
straygecko said:
The logcat isn't telling me much - is there anything earlier in the log of interest?
Click to expand...
Click to collapse
I will redo and post more lines, but nothing jumped out at me.
straygecko said:
/data/anr/traces.txt also might help but I'm not optimistic on that one.
Click to expand...
Click to collapse
I have ReLaunch set to show hidden files, do not hide known extensions and show all files.
When I tap on the data folder it comes up empty, i.e. there is no folder called anr to check for the traces.txt file.
longer logcat file
longer logcat file
RandyB201 said:
longer logcat file
Click to expand...
Click to collapse
OK, that's more helpful. It says you don't have an apk that handles the Add Account intent. It may have to do with your attempt to install AccountAndSyncSettings.apk from /system/app. Does AccountAndSyncSettings.apk still exist in /system/app? If so, try rebooting your NST and try the gmail work around again. If not, move it back there and reboot then try the gmail work around again.
---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------
RandyB201 said:
I have ReLaunch set to show hidden files, do not hide known extensions and show all files.
When I tap on the data folder it comes up empty, i.e. there is no folder called anr to check for the traces.txt file.
Click to expand...
Click to collapse
Realunch won't see things in that folder. You need to use a file manager tat has an option to explore with root privileges like ES File Explorer. But the logcat you posted was what I needed so no need to post the traces.txt
slogging on...
straygecko said:
OK, that's more helpful. It says you don't have an apk that handles the Add Account intent. It may have to do with your attempt to install AccountAndSyncSettings.apk from /system/app. Does AccountAndSyncSettings.apk still exist in /system/app?
Click to expand...
Click to collapse
yes it is still there
straygecko said:
If so, try rebooting your NST and try the gmail work around again. If not, move it back there and reboot then try the gmail work around again.t
Click to expand...
Click to collapse
I am geeky enough that I had already tried rebooting to fix the problem, but today I powered down the nook. I started it. The only thing I did before trying the gmail trick was start ADBKonnect and connect to the desktop.
The results were the same. My apps, task and service lists are the same with the exception that I uninstalled ZoReader. The task and service lists are identical, but there are a few differences in the "order".
Attaching the logcat file...
---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------
Realunch won't see things in that folder. You need to use a file manager tat has an option to explore with root privileges like ES File Explorer. But the logcat you posted was what I needed so no need to post the traces.txt[/QUOTE]
I installed and used Root File Manager to find the traces.txt file. It was empty.
Just an afterthought... should I use my NookManager microsd card to reinstall GappsAttack?
osowiecki said:
am start -a android.settings.SYNC_SETTINGS
It does not work or you have just missed something?
Got the command from decompiled "AccountAndSyncSettings.apk".
AndroidManifest.xml.
Click to expand...
Click to collapse
I tried adb shell am start -a android.settings.SYNC_SETTINGS.
Starting: Intent { act=android.settings.SYNC_SETTINGS }
Error: Activity not started, unable to resolve Intent { act=android.settings.SYN
C_SETTINGS flg=0x10000000 }
logcat attached...
RandyB201 said:
I tried adb shell am start -a android.settings.SYNC_SETTINGS.
Starting: Intent { act=android.settings.SYNC_SETTINGS }
Error: Activity not started, unable to resolve Intent { act=android.settings.SYN
C_SETTINGS flg=0x10000000 }
logcat attached...
Click to expand...
Click to collapse
On my NST this command works fine because it starts the Gapps Sync_settings (I have NTGAppsAttack installed and configured)
other commands fail because nook does know which intent goes goes to Oobe.apk and which to Google account settings (I guess, based on ddms error messages).
Connect your nook via adb and run 'ddms' from your Android folder.
It specifically informs you when it is trying to run part of Oobe.apk or Gapps and when these commands generate errors.
Tonight I'll try to look closer to this problem.
08-07 18:58:19.476: D/AndroidRuntime(1466): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
08-07 18:58:19.476: I/AndroidRuntime(1466): Heap size: -Xmx64m
08-07 18:58:19.476: D/AndroidRuntime(1466): CheckJNI is OFF
08-07 18:58:19.484: D/dalvikvm(1466): creating instr width table
08-07 18:58:19.539: D/AndroidRuntime(1466): --- registering native functions ---
08-07 18:58:19.562: I/NATIVE-EPD(1466): framebuffer_handle: 21
08-07 18:58:19.632: D/ddm-heap(1466): Got feature list request
08-07 18:58:19.695: I/ActivityManager(1052): Starting activity: Intent { act=android.settings.SYNC_SETTINGS flg=0x10000000 cmp=com.android.providers.subscribedfeeds/com.android.settings.ManageAccountsSettings }
08-07 18:58:19.710: D/AndroidRuntime(1466): Shutting down VM
08-07 18:58:19.710: D/dalvikvm(1466): DestroyJavaVM waiting for non-daemon threads to exit
08-07 18:58:19.710: D/dalvikvm(1466): DestroyJavaVM shutting VM down
08-07 18:58:19.710: D/dalvikvm(1466): HeapWorker thread shutting down
08-07 18:58:19.710: D/dalvikvm(1466): HeapWorker thread has shut down
08-07 18:58:19.710: D/jdwp(1466): JDWP shutting down net...
08-07 18:58:19.718: I/dalvikvm(1466): Debugger has detached; object registry had 1 entries
08-07 18:58:19.726: D/dalvikvm(1466): VM cleaning up
08-07 18:58:19.749: D/dalvikvm(1466): LinearAlloc 0x0 used 642220 of 5242880 (12%)
08-07 18:58:19.765: V/Activity(1052): performResume()
08-07 18:58:19.765: D/EPD#ActivityResume(1052): resetRegion 4
08-07 18:58:19.765: D/NATIVE-EPD(1052): epd_reset_region: 0x10
08-07 18:58:19.765: D/EPD#ActivityResume(1052): resetRegion 5
08-07 18:58:19.765: D/NATIVE-EPD(1052): epd_reset_region: 0x20
08-07 18:58:19.765: D/EPD#ActivityResume(1052): resetRegion 6
08-07 18:58:19.765: D/NATIVE-EPD(1052): epd_reset_region: 0x40
08-07 18:58:19.765: D/EPD#ActivityResume(1052): resetRegion 7
08-07 18:58:19.765: D/NATIVE-EPD(1052): epd_reset_region: 0x80
08-07 18:58:19.765: D/EPD#ActivityResume(1052): Disable EPD for 350ms!!!!!!!!
08-07 18:58:19.773: D/AccountSettings(1052): added authority com.android.contacts to accountType com.google
08-07 18:58:19.773: D/AccountSettings(1052): added authority calendar to accountType com.google
08-07 18:58:19.773: D/AccountSettings(1052): added authority gmail-ls to accountType com.google
08-07 18:58:19.773: D/AccountSettings(1052): added authority subscribedfeeds to accountType com.google
08-07 18:58:19.820: I/ActivityManager(1052): Start proc org.pocketworkstation.pckeyboard for service org.pocketworkstation.pckeyboard/.LatinIME: pid=1476 uid=10084 gids={}
08-07 18:58:19.820: W/InputManagerService(1052): Starting input on non-focused client [email protected] (uid=10026 pid=1115)
08-07 18:58:19.859: I/dalvikvm(1476): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=38)
08-07 18:58:19.867: I/dalvikvm(1476): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=68)
08-07 18:58:19.898: I/ActivityManager(1052): Displayed activity com.android.providers.subscribedfeeds/com.android.settings.ManageAccountsSettings: 203 ms (total 203 ms)
08-07 18:58:19.921: I/PCKeyboard(1476): onCreate(), os.version=2.6.29-omap1
08-07 18:58:19.953: D/SurfaceFlinger(1052): Frame buffer posted; elapsed time = 12 msecs
08-07 18:58:20.023: E/BinaryDictionary(1476): Could not load native library jni_pckeyboard
08-07 18:58:20.031: D/dalvikvm(1476): +++ not scanning '/system/lib/libwebcore.so' for 'openNative' (wrong CL)
08-07 18:58:20.031: D/dalvikvm(1476): +++ not scanning '/system/lib/libmedia_jni.so' for 'openNative' (wrong CL)
08-07 18:58:20.031: D/dalvikvm(1476): +++ not scanning '/system/lib/libexif.so' for 'openNative' (wrong CL)
08-07 18:58:20.031: D/dalvikvm(1476): +++ not scanning '/system/lib/libsrec_jni.so' for 'openNative' (wrong CL)
08-07 18:58:20.031: W/dalvikvm(1476): No implementation found for native Lorg/pocketworkstation/pckeyboard/BinaryDictionary;.openNative (Ljava/nio/ByteBuffer;III)I
08-07 18:58:20.031: W/BinaryDictionary(1476): Failed to load native dictionary
08-07 18:58:20.031: W/BinaryDictionary(1476): java.lang.UnsatisfiedLinkError: openNative
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.BinaryDictionary.openNative(Native Method)
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.BinaryDictionary.loadDictionary(BinaryDictionary.java:145)
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.BinaryDictionary.loadDictionary(BinaryDictionary.java:173)
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.BinaryDictionary.<init>(BinaryDictionary.java:78)
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.Suggest.<init>(Suggest.java:109)
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.LatinIME.initSuggest(LatinIME.java:521)
08-07 18:58:20.031: W/BinaryDictionary(1476): at org.pocketworkstation.pckeyboard.LatinIME.onCreate(LatinIME.java:422)
08-07 18:58:20.031: W/BinaryDictionary(1476): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2780)
08-07 18:58:20.031: W/BinaryDictionary(1476): at android.app.ActivityThread.access$3200(ActivityThread.java:119)
08-07 18:58:20.031: W/BinaryDictionary(1476): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1917)
08-07 18:58:20.031: W/BinaryDictionary(1476): at android.os.Handler.dispatchMessage(Handler.java:99)
08-07 18:58:20.031: W/BinaryDictionary(1476): at android.os.Looper.loop(Looper.java:123)
08-07 18:58:20.031: W/BinaryDictionary(1476): at android.app.ActivityThread.main(ActivityThread.java:4363)
08-07 18:58:20.031: W/BinaryDictionary(1476): at java.lang.reflect.Method.invokeNative(Native Method)
08-07 18:58:20.031: W/BinaryDictionary(1476): at java.lang.reflect.Method.invoke(Method.java:521)
08-07 18:58:20.031: W/BinaryDictionary(1476): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
08-07 18:58:20.031: W/BinaryDictionary(1476): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
08-07 18:58:20.031: W/BinaryDictionary(1476): at dalvik.system.NativeStart.main(Native Method)
08-07 18:58:20.039: E/ActivityThread(1476): Failed to find provider info for com.android.contacts
08-07 18:58:25.132: D/dalvikvm(1115): GC freed 6626 objects / 428208 bytes in 77ms
08-07 18:58:30.117: D/dalvikvm(1132): GC freed 2351 objects / 137136 bytes in 55ms
Click to expand...
Click to collapse
RandyB201 said:
yes it is still there
I am geeky enough that I had already tried rebooting to fix the problem, but today I powered down the nook. I started it. The only thing I did before trying the gmail trick was start ADBKonnect and connect to the desktop.
The results were the same. My apps, task and service lists are the same with the exception that I uninstalled ZoReader. The task and service lists are identical, but there are a few differences in the "order".
Attaching the logcat file...
...
I installed and used Root File Manager to find the traces.txt file. It was empty.
Just an afterthought... should I use my NookManager microsd card to reinstall GappsAttack?
Click to expand...
Click to collapse
Logcat shows the same thing. No apk to handle the android.settings.ADD_ACCOUNT_SETTINGS intent. It really sounds like your AccountAndSyncSettings.apk got mangled along the way somehow. Reinstalling NTGAppsAttack won't fix that as AccountAndSyncSettings.apk is part of the stock B&N stuff. A logcat from Android startup (package manager messages) could help pin down what's wrong with the apk you have but knowing that or not the fix would be the same. Either restore to prior to installing NTGAppsAttack and reinstall NTGAppsAttack. Or you could extract the AccountAndSyncSettings.apk from the B&N 1.2.1 update file, copy it to your /system/app folder, reboot and try the gmail workaround again. The first has the highest probability of success but the second isn't too much work and has a pretty good chance of fixing it.
---------- Post added at 09:12 PM ---------- Previous post was at 09:05 PM ----------
osowiecki said:
On my NST this command works fine because it starts the Gapps Sync_settings (I have NTGAppsAttack installed and configured)
other commands fail because nook does know which intent goes goes to Oobe.apk and which to Google account settings (I guess, based on ddms error messages).
Connect your nook via adb and run 'ddms' from your Android folder.
It specifically informs you when it is trying to run part of Oobe.apk or Gapps and when these commands generate errors.
Tonight I'll try to look closer to this problem.
Click to expand...
Click to collapse
The SYNC_SETTINGS intent is handled by AccountAndSyncSettings.apk which is part of stock B&N and isn't installed by NTGAppsAttack. I think this has something to do with the B&N account stuff they patched into android. Seeing from your profile you're not in the US or UK do you even have your device registered with B&N? Not having a B&N account setup might be what's making your device work as sync settings won't be trying to display a B&N account in its list of accounts.
I have the same issue. I tried multiple ways and apps to get to the sync settings. but my nst just reboots at every attempt.
osowiecki said:
am start -a android.settings.SYNC_SETTINGS
It does not work or you have just missed something?
Got the command from decompiled "AccountAndSyncSettings.apk".
AndroidManifest.xml.
i tried this command in terminal app within nst. and it rebooted right away, after a brief pause.
straygecko said:
The SYNC_SETTINGS intent is handled by AccountAndSyncSettings.apk which is part of stock B&N and isn't installed by NTGAppsAttack. I think this has something to do with the B&N account stuff they patched into android. Seeing from your profile you're not in the US or UK do you even have your device registered with B&N? Not having a B&N account setup might be what's making your device work as sync settings won't be trying to display a B&N account in its list of accounts.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
my device is uk. just bought from argos last month rooted with nookmanager. one issue that i notice is that some dialog boxes display empty, possibly because foreground/background colours are same/similar. i can't remember whether i had this problem before rooting.
moving backward..
straygecko said:
Logcat shows the same thing. No apk to handle the android.settings.ADD_ACCOUNT_SETTINGS intent. It really sounds like your AccountAndSyncSettings.apk got mangled along the way somehow. Reinstalling NTGAppsAttack won't fix that as AccountAndSyncSettings.apk is part of the stock B&N stuff. A logcat from Android startup (package manager messages) could help pin down what's wrong with the apk you have but knowing that or not the fix would be the same. Either restore to prior to installing NTGAppsAttack and reinstall NTGAppsAttack. Or you could extract the AccountAndSyncSettings.apk from the B&N 1.2.1 update file, copy it to your /system/app folder, reboot and try the gmail workaround again. The first has the highest probability of success but the second isn't too much work and has a pretty good chance of fixing it.
Click to expand...
Click to collapse
ok. the second option did not work. so, i am trying to reset the nook and start over.
i erased and deregistered it. after reboot i went through the setup process. then i rebooted with my nook manager card and rooted. rebooted and all looks good.
then i rebooted with the nookmanager card to install gapps attack
after reboot, i am stuck at step 16. Go back to ReLaunch and open the Market
when i do this it shows me the license screen i hit accept, then i just get a server error.
gmail and contacts apps seems to be working fine. when i open calendar, it opens but there is an image of an sd card superimposed over the top of the calendar -- i dont remember it doing htat before. talk will not open, it just briefly flashes the screen and goes back to the applications in relaunch.
I have done this entire process several times now and the results have been exactly the same each time???
update: i just tried this with a new gmail account, and the results were the same...
as i have thought about this most of yesterday and today, it seems to me that something is not getting cleared / deleted in the reset process...
aug-12-13 update: i installed nook color tools, used it to uninstall the market update, rebooted, rebooted w nook mgr card, reinstalled gappsattack. no change...
i am not sure if this is significant, but i noticed something else that supports my theory that not everything is getting erased in the reset process. when i open contacts, my google contacts from my original gmail acct are still in the list even though, i deregistered/erased and used a different gmail acct when i did this yesterday...
back to my original question...
I understand that B&N has modified the AccountAndSyncSettings.apk on the nook to fence it in to their company.
Has anyone tried replacing the AccountAndSyncSettings.apk in their nook with one from another Android 2.1 device?
I assume this would break the B&N apps, but I wonder if it would enable apps that need to access that apk...
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, some information about the device:
1. Samsung Galaxy S5 from TMobile
2. Has Lollipop installed (from OTA update)
3. Factory ROM, not rooted, bootloader still locked, no modifications whatsoever.
For some reason I am getting the "Unfortunately, Phone has stopped" popup continuously. This occurs from the moment I boot up (at lockscreen) and as soon as I press "OK", it comes up about 0.2 seconds later. Makes it very difficult to navigate the device menus.
I have looked at logcats and this exception is what occurs:
Code:
I/Telecom (10435): Call: CallerInfo received for ****: [email protected] { name null, phoneNumber non-null }
I/Telecom (10435): MissedCallNotifier: showMissedCallNotification
D/ScoverManager(10435): serviceVersion : 16908288
D/EcidContact(10435): ECID AOSP VERSION: 2.3.6
D/AndroidRuntime(10435): Shutting down VM
E/AndroidRuntime(10435): FATAL EXCEPTION: main
E/AndroidRuntime(10435): Process: com.android.server.telecom, PID: 10435
E/AndroidRuntime(10435): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
E/AndroidRuntime(10435): at com.android.server.telecom.secutils.TelecomUtils.getPresentationString(TelecomUtils.java:2917)
E/AndroidRuntime(10435): at com.android.server.telecom.MissedCallNotifier.showMissedCallNotification(MissedCallNotifier.java:191)
E/AndroidRuntime(10435): at com.android.server.telecom.MissedCallNotifier$3$1.onCallerInfoChanged(MissedCallNotifier.java:617)
E/AndroidRuntime(10435): at com.android.server.telecom.Call.access$000(Call.java:74)
E/AndroidRuntime(10435): at com.android.server.telecom.Call$1.onQueryComplete(Call.java:165)
E/AndroidRuntime(10435): at com.android.internal.telephony.CallerInfoAsyncQuery$CallerInfoAsyncQueryHandler.onQueryComplete(CallerInfoAsyncQuery.java:343)
E/AndroidRuntime(10435): at android.content.AsyncQueryHandler.handleMessage(AsyncQueryHandler.java:344)
E/AndroidRuntime(10435): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(10435): at android.os.Looper.loop(Looper.java:145)
E/AndroidRuntime(10435): at android.app.ActivityThread.main(ActivityThread.java:5837)
E/AndroidRuntime(10435): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(10435): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(10435): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1388)
E/AndroidRuntime(10435): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1183)
V/ApplicationPolicy( 783): isApplicationStateBlocked userId 0 pkgname com.android.server.telecom
W/ActivityManager( 783): Process com.android.server.telecom has crashed too many times: killing!
I/dumpstate(10454): begin
D/StatusBarManagerService( 783): manageDisableList userId=0 what=0x0 pkg=WindowManager.LayoutParams
D/CrashAnrDetector( 783): processName: com.android.server.telecom
D/CrashAnrDetector( 783): broadcastEvent : com.android.server.telecom system_app_crash
W/ContextImpl( 783): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1701 com.android.server.analytics.data.collection.application.CrashAnrDetector.broadcastEvent:296 com.android.server.analytics.data.collection.application.CrashAnrDetector.processDropBoxEntry:254 com.android.server.analytics.data.collection.application.CrashAnrDetector.access$100:60 com.android.server.analytics.data.collection.application.CrashAnrDetector$1.onReceive:102
I/SurfaceFlinger( 245): id=21 createSurf (49x49),1 flag=4, Application Error: com.android.server.telecom
I/OpenGLRenderer( 783): Initialized EGL, version 1.4
I/OpenGLRenderer( 783): HWUI protection enabled for context , &this =0x9de366f0 ,&mEglDisplay = 1 , &mEglConfig = 8
E/android.os.Debug( 783): [email protected] > sdumpstate -k -t -z -d -o /data/log/dumpstate_app_error
I/ServiceManager( 345): Waiting for service AtCmdFwd...
D/PowerManagerService( 783): [input device light] handleInputDeviceLightOff
It seems to have something to do with telecom. I have removed the SIM card, SD card, etc. No difference. I have tried clearing app data for contacts, contacts storage, phone app, even "com.android.server.telecom" from ADB SHELL PM CLEAR command, but no change.
Does anyone know what the issue could be? What can I try to do (besides factory reset of course) to fix the issue? Thanks in advance. I can post more logcats if needed.
There are numerous bugs with system apps crashing with lolipop on the S5. My contacts app is constantly crashing, vzw, OTA.
Ended up doing a factory reset, which fixed the issue
I really didn't want to factory reset ?
You need to factory reset after upgrading from KK to LP
That's more of a personal preference. I've seen tons of upgrades on this phone that went fine.
Android.Addiction said:
Ended up doing a factory reset, which fixed the issue
Click to expand...
Click to collapse
Android.Addiction said:
That's more of a personal preference. I've seen tons of upgrades on this phone that went fine.
Click to expand...
Click to collapse
___________________
Guys, I did a short analysis on the apps in firmwares 1.2.3 and 1.3.0n. The results were pretty surprising:
The Chinese one is more advanced adn much newer (as was already known)
The Watchfaces app contains the SAME drawings in both versions (except the English one having less watchfaces). That means: The Chinese version does have e.g. English weekdays available (stored at the same locations) as the English version has. It probably was just disabled in the code to use the right coding!
One gets the clear indication that they worked on a joint firmware and then at some 70% got the strategic directions to split the firmware.
I am currently doing some tests to modify the apps and load them on the Chinese version. Maybe a Chinese version with English translation is better than the official English version.
Yes, in this moment i think that the china version with hack is better that English version
Wonder if it's worth flashing Chinese ROM to English version and then changing to English?
or, would you expect English version will catch up soon?
I'm disappointed so far with this watch (or rather the very very simple support from the APP on your phone)
You can't even look at the step or sleep data on your phone?!?!?
Nothing wrong with the hardware but it seems they rushed out this awesome device not really thinking about the supplementary app to go with it.
shayne77 said:
Wonder if it's worth flashing Chinese ROM to English version and then changing to English?
or, would you expect English version will catch up soon?
I'm disappointed so far with this watch (or rather the very very simple support from the APP on your phone)
You can't even look at the step or sleep data on your phone?!?!?
Nothing wrong with the hardware but it seems they rushed out this awesome device not really thinking about the supplementary app to go with it.
Click to expand...
Click to collapse
To sync sleep and steps on phone, you need Chinese Amazfit and MiFit apps, login with same Xiaomi account
Inviato dal mio D6633 utilizzando Tapatalk
Pi3rluigi said:
To sync sleep and steps on phone, you need Chinese Amazfit and MiFit apps, login with same Xiaomi account
Inviato dal mio D6633 utilizzando Tapatalk
Click to expand...
Click to collapse
I saw that tutorial on YouTube but I couldn't get MiFit to show data (it seemed to read it, sync ok but not display anything?)
Need help from app developer
Ok, I decompiled one of the Huami apps ("WearSports"), changed a small text in the resources ("Trail Run" -> "Berg Run"), compiled the app again (using apktool), signed the apk and exchanged the original apk with the modded one.
The watch starts ok. When swiping left, one gets to the Sports app, which does indeed show "Berg Run" instead of "Trail Run" (hurray). But when I want to enter one of the sports, the app force closes with the following error:
Code:
D/HmSport ( 9704): HmSportProvider -- today distance:0.0
I/slog ( 9704): 已经有文件存在于: /sdcard/.springchannel/com.huami.watch.sport , 旧文件可能被覆盖或删除呢.
E/DatabaseUtils( 9128): Writing exception to parcel
E/DatabaseUtils( 9128): java.lang.SecurityException: Permission denial: writing to secure settings requires android.permission.WRITE_SECURE_SETTINGS
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.checkWritePermissions(SettingsProvider.java:313)
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.insertForUser(SettingsProvider.java:1110)
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:801)
E/DatabaseUtils( 9128): at android.content.ContentProvider$Transport.call(ContentProvider.java:370)
E/DatabaseUtils( 9128): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:283)
E/DatabaseUtils( 9128): at android.os.Binder.execTransact(Binder.java:446)
E/AndroidRuntime( 9704): FATAL EXCEPTION: global-work-thread
E/AndroidRuntime( 9704): Process: com.huami.watch.sport, PID: 9704
E/AndroidRuntime( 9704): java.lang.SecurityException: Permission denial: writing to secure settings requires android.permission.WRITE_SECURE_SETTINGS
E/AndroidRuntime( 9704): at android.os.Parcel.readException(Parcel.java:1546)
E/AndroidRuntime( 9704): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:185)
E/AndroidRuntime( 9704): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:137)
E/AndroidRuntime( 9704): at android.content.ContentProviderProxy.call(ContentProviderNative.java:645)
E/AndroidRuntime( 9704): at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:1094)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putStringForUser(Settings.java:3173)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putFloatForUser(Settings.java:3459)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putFloat(Settings.java:3453)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.DataManager.setTodayDistance(DataManager.java:370)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider.updateTodayDistance(SportContentProvider.java:95)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider.access$000(SportContentProvider.java:24)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider$1.run(SportContentProvider.java:57)
E/AndroidRuntime( 9704): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime( 9704): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 9704): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 9704): at android.os.HandlerThread.run(HandlerThread.java:61)
The mentioned permission is in the AndroidManifest.xml (as it was decompiled from the original app).
I need help from an experienced developer. If we could get this fixed, we can setup our own custom ROM, based on the most current Chinese version, including all English translations and what else we want to.
Neuer_User said:
Ok, I decompiled one of the Huami apps ("WearSports"), changed a small text in the resources ("Trail Run" -> "Berg Run"), compiled the app again (using apktool), signed the apk and exchanged the original apk with the modded one.
The watch starts ok. When swiping left, one gets to the Sports app, which does indeed show "Berg Run" instead of "Trail Run" (hurray). But when I want to enter one of the sports, the app force closes with the following error:
Code:
D/HmSport ( 9704): HmSportProvider -- today distance:0.0
I/slog ( 9704): 已经有文件存在于: /sdcard/.springchannel/com.huami.watch.sport , 旧文件可能被覆盖或删除呢.
E/DatabaseUtils( 9128): Writing exception to parcel
E/DatabaseUtils( 9128): java.lang.SecurityException: Permission denial: writing to secure settings requires android.permission.WRITE_SECURE_SETTINGS
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.checkWritePermissions(SettingsProvider.java:313)
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.insertForUser(SettingsProvider.java:1110)
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:801)
E/DatabaseUtils( 9128): at android.content.ContentProvider$Transport.call(ContentProvider.java:370)
E/DatabaseUtils( 9128): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:283)
E/DatabaseUtils( 9128): at android.os.Binder.execTransact(Binder.java:446)
E/AndroidRuntime( 9704): FATAL EXCEPTION: global-work-thread
E/AndroidRuntime( 9704): Process: com.huami.watch.sport, PID: 9704
E/AndroidRuntime( 9704): java.lang.SecurityException: Permission denial: writing to secure settings requires android.permission.WRITE_SECURE_SETTINGS
E/AndroidRuntime( 9704): at android.os.Parcel.readException(Parcel.java:1546)
E/AndroidRuntime( 9704): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:185)
E/AndroidRuntime( 9704): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:137)
E/AndroidRuntime( 9704): at android.content.ContentProviderProxy.call(ContentProviderNative.java:645)
E/AndroidRuntime( 9704): at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:1094)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putStringForUser(Settings.java:3173)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putFloatForUser(Settings.java:3459)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putFloat(Settings.java:3453)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.DataManager.setTodayDistance(DataManager.java:370)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider.updateTodayDistance(SportContentProvider.java:95)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider.access$000(SportContentProvider.java:24)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider$1.run(SportContentProvider.java:57)
E/AndroidRuntime( 9704): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime( 9704): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 9704): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 9704): at android.os.HandlerThread.run(HandlerThread.java:61)
The mentioned permission is in the AndroidManifest.xml (as it was decompiled from the original app).
I need help from an experienced developer. If we could get this fixed, we can setup our own custom ROM, based on the most current Chinese version, including all English translations and what else we want to.
Click to expand...
Click to collapse
UPDATE:
I can grant the app the WRITE_SECURE_SETTINGS permission, and then it indeed works (command "pm grant <package name> android.permission.WRITE_SECURE_SETTINGS"). The question is now, why do I need to grant that manually, when this is in already in the AndroidManifest.xml???
Is possible change millas to km??? Thanks for you work
sakilxda said:
Is possible change millas to km??? Thanks for you work
Click to expand...
Click to collapse
With this approach, yes. I need to get this running first, though...
Perfect, many people hope this
And do you think is possible put the original Chinesse firmware?
Change the English to Chinese after of Chinese to english
Return to previus version again
I am currently working on a "non-intrusive" custom-rom. That is using the Chinese version on the watch, booting with a special (temporary) boot image and running translated (and modded, if needed) apps. So, a simple reboot, and you would have back the original Chinese version.
I think I can get this running. I exchanged one app with this method, so It could be done with all apps. But I am still having some problems to solve first. And I don't have much time (actually, currently, nearly no time at all ).
Neuer_User said:
I am currently working on a "non-intrusive" custom-rom. That is using the Chinese version on the watch, booting with a special (temporary) boot image and running translated (and modded, if needed) apps. So, a simple reboot, and you would have back the original Chinese version.
I think I can get this running. I exchanged one app with this method, so It could be done with all apps. But I am still having some problems to solve first. And I don't have much time (actually, currently, nearly no time at all ).
Click to expand...
Click to collapse
Really appreciate your work for our watch, I'm willing to help in translating this watch into some language, but I'm not a developer, and it would be nice if we can enable language setting in option for our future custom rom, so we can choose the language we want.
big thanks Neuer!
Neuer_User said:
Ok, I decompiled one of the Huami apps ("WearSports"), changed a small text in the resources ("Trail Run" -> "Berg Run"), compiled the app again (using apktool), signed the apk and exchanged the original apk with the modded one.
The watch starts ok. When swiping left, one gets to the Sports app, which does indeed show "Berg Run" instead of "Trail Run" (hurray). But when I want to enter one of the sports, the app force closes with the following error:
Code:
D/HmSport ( 9704): HmSportProvider -- today distance:0.0
I/slog ( 9704): 已经有文件存在于: /sdcard/.springchannel/com.huami.watch.sport , 旧文件可能被覆盖或删除呢.
E/DatabaseUtils( 9128): Writing exception to parcel
E/DatabaseUtils( 9128): java.lang.SecurityException: Permission denial: writing to secure settings requires android.permission.WRITE_SECURE_SETTINGS
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.checkWritePermissions(SettingsProvider.java:313)
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.insertForUser(SettingsProvider.java:1110)
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:801)
E/DatabaseUtils( 9128): at android.content.ContentProvider$Transport.call(ContentProvider.java:370)
E/DatabaseUtils( 9128): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:283)
E/DatabaseUtils( 9128): at android.os.Binder.execTransact(Binder.java:446)
E/AndroidRuntime( 9704): FATAL EXCEPTION: global-work-thread
E/AndroidRuntime( 9704): Process: com.huami.watch.sport, PID: 9704
E/AndroidRuntime( 9704): java.lang.SecurityException: Permission denial: writing to secure settings requires android.permission.WRITE_SECURE_SETTINGS
E/AndroidRuntime( 9704): at android.os.Parcel.readException(Parcel.java:1546)
E/AndroidRuntime( 9704): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:185)
E/AndroidRuntime( 9704): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:137)
E/AndroidRuntime( 9704): at android.content.ContentProviderProxy.call(ContentProviderNative.java:645)
E/AndroidRuntime( 9704): at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:1094)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putStringForUser(Settings.java:3173)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putFloatForUser(Settings.java:3459)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putFloat(Settings.java:3453)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.DataManager.setTodayDistance(DataManager.java:370)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider.updateTodayDistance(SportContentProvider.java:95)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider.access$000(SportContentProvider.java:24)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider$1.run(SportContentProvider.java:57)
E/AndroidRuntime( 9704): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime( 9704): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 9704): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 9704): at android.os.HandlerThread.run(HandlerThread.java:61)
The mentioned permission is in the AndroidManifest.xml (as it was decompiled from the original app).
I need help from an experienced developer. If we could get this fixed, we can setup our own custom ROM, based on the most current Chinese version, including all English translations and what else we want to.
Click to expand...
Click to collapse
So, I now got the the cause of the problem:
Code:
W/PackageManager( 432): System package com.huami.watch.sport signature changed; retaining data.
W/PackageManager( 432): Package com.huami.watch.sport desires unavailable shared library com.google.android.wearable; ignoring!
W/PackageManager( 432): Unknown permission com.huami.watch.companion.permission.READ_SETTINGS in package com.huami.watch.sport
W/PackageManager( 432): Unknown permission com.huami.watch.companion.permission.WRITE_SETTINGS in package com.huami.watch.sport
W/PackageManager( 432): Not granting permission android.permission.WRITE_SECURE_SETTINGS to package com.huami.watch.sport (protectionLevel=50 flags=0x8be45)
W/PackageManager( 432): Not granting permission android.permission.CHANGE_CONFIGURATION to package com.huami.watch.sport (protectionLevel=50 flags=0x8be45)
W/PackageManager( 432): Not granting permission android.permission.DEVICE_POWER to package com.huami.watch.sport (protectionLevel=2 flags=0x8be45)
W/PackageManager( 432): Not granting permission com.huami.watch.permission.READ_USER_SETTINGS to package com.huami.watch.sport (protectionLevel=2 flags=0x8be45)
W/PackageManager( 432): Unknown permission com.huami.watch.companion.permission.READ_SETTINGS in package com.huami.watch.sport
W/PackageManager( 432): Unknown permission com.huami.watch.companion.permission.WRITE_SETTINGS in package com.huami.watch.sport
W/PackageManager( 432): Not granting permission android.permission.WRITE_SECURE_SETTINGS to package com.huami.watch.sport (protectionLevel=50 flags=0x8be45)
W/PackageManager( 432): Not granting permission android.permission.CHANGE_CONFIGURATION to package com.huami.watch.sport (protectionLevel=50 flags=0x8be45)
W/PackageManager( 432): Not granting permission android.permission.DEVICE_POWER to package com.huami.watch.sport (protectionLevel=2 flags=0x8be45)
W/PackageManager( 432): Not granting permission com.huami.watch.permission.READ_USER_SETTINGS to package com.huami.watch.sport (protectionLevel=2 flags=0x8be45)
So, that is why the application is force closing, ok. Now the question is, how to solve this. I would like to have an experienced ROM developer help me here.
OK, if someone is interested: I now understand why the permissions are not granted. It is the signature of the apk (which I needed to resign). For some permissions this signature must be identical with the signature of the platform. This key only Huami has.
So, what can be done? I am currently thinking of patching the PackageManager, so that it will not deny the permission. Not sure, if this is possible, but I will try.
Neuer_User said:
OK, if someone is interested: I now understand why the permissions are not granted. It is the signature of the apk (which I needed to resign). For some permissions this signature must be identical with the signature of the platform. This key only Huami has.
So, what can be done? I am currently thinking of patching the PackageManager, so that it will not deny the permission. Not sure, if this is possible, but I will try.
Click to expand...
Click to collapse
I can't help you to develop, I have no knowledge, but I can be a tester when ready!
Inviato dal mio D6633 utilizzando Tapatalk
Pi3rluigi said:
I can't help you to develop, I have no knowledge, but I can be a tester when ready!
Inviato dal mio D6633 utilizzando Tapatalk
Click to expand...
Click to collapse
Thanks for the offer. Main work currently is getting the knowledge on howto deodex files, mod them, re-odex them. Then I can try to exchange the Package Manager on my watch. All of this is only temporary, so even if nothing will work afterwards, a simple reboot will fix it.
Some more info, on how my planned "non-intrusive" changes will work:
- The watch will need to be booted via a fastboot command. That loads a customized boot image. The boot image will mount all filesystems and then start the processes.
- However, after all filesystems have been mounted, it will mount the custom rom over the system partition. So, instead of using the system image, the watch will use the custom ROM.
- The custom ROM will reside as one single file on the /sdcard. So there are no modifications to the system partition (and neither to the boot partition).
- After a reboot, the normal boot image is booted again, which will also not mount the custom ROM.
- If you reboot via fastboot, the modded boot.img can be booted, which will mount the custom ROM again.
The nice thing with this is, that all modifications are temporary. If something is borked up, the device cannot boot or goes into a boot loop, it doesn't matter. You simply turn the watch off and on again, and everything is back to unmodified.
So far, this seems to be working. I now need to get a working custom ROM. That is, I need to understand how to modify the apps, so deodexing, decompiling, recompiling, signing, etc.
I will probably open an open source GitHub project, as soon as I have something usable. Then people can contribute translating and modding.
Neuer_User said:
Some more info, on how my planned "non-intrusive" changes will work:
So far, this seems to be working. I now need to get a working custom ROM. That is, I need to understand how to modify the apps, so deodexing, decompiling, recompiling, signing, etc.
Click to expand...
Click to collapse
Hi!
I've just translated chinese fw to russian and switched watch to kilometers everywhere and resolve some interface bugs. )) It was easy and i can give some advices if you need.
silver-alx said:
Hi!
I've just translated chinese fw to russian and switched watch to kilometers everywhere and resolve some interface bugs. )) It was easy and i can give some advices if you need.
Click to expand...
Click to collapse
If you could describe, how you did it, that would be very helpful. Maybe even upload your original and modified firmware, so we can take a look at the differences?
Thanks!