Hi!
I have htc one x, and i have a problem with it!
The problems begining, after i cracked the screen. First i have original recovery, original rom etc...
After the accident tha phone work, but do random reboots, than the phonne boot in android, but imediatly rebbot. Im try to do reset deafults from bootloader, but failed, and i also don't can launch recovery from bootloader. The screen was replaced, than i still have the problems. So i flash cwm first. After cwm flash the phone boot, but still do random reboots. So i just flash cyanogenmod. With cyanogen mod i still have random rebbot problem plus services stop working.
Now i flash viper sense 5 rom, and twrp recovery. Now services dosent stop working, but the phone still do random reboots. And now, i don't can launch recovery sometimes. I don't do nothing, and a few hours later i can launch recovery again, but the room reboot after loading animation. So i flash again the rom, and now work, with random reboots. After i flash the sense rom, i don't have problems for a few hours.
And yes im flash with fastboot the boot.img, and erease the chace.
Anyone have idea how can i solve the problem? After the screen replacement, i don't have warranty (i think).
endavour pvt ship s-on rl
hboot-1.39.0000
radio-5.1204.162a.29
update: Here it is a logcat output after random reboot, and the phone stuck at bootanim.
tejeskifly said:
Hi!
I have htc one x, and i have a problem with it!
The problems begining, after i cracked the screen. First i have original recovery, original rom etc...
After the accident tha phone work, but do random reboots, than the phonne boot in android, but imediatly rebbot. Im try to do reset deafults from bootloader, but failed, and i also don't can launch recovery from bootloader. The screen was replaced, than i still have the problems. So i flash cwm first. After cwm flash the phone boot, but still do random reboots. So i just flash cyanogenmod. With cyanogen mod i still have random rebbot problem plus services stop working.
Now i flash viper sense 5 rom, and twrp recovery. Now services dosent stop working, but the phone still do random reboots. And now, i don't can launch recovery sometimes. I don't do nothing, and a few hours later i can launch recovery again, but the room reboot after loading animation. So i flash again the rom, and now work, with random reboots. After i flash the sense rom, i don't have problems for a few hours.
And yes im flash with fastboot the boot.img, and erease the chace.
Anyone have idea how can i solve the problem? After the screen replacement, i don't have warranty (i think).
endavour pvt ship s-on rl
hboot-1.39.0000
radio-5.1204.162a.29
update: Here it is a logcat output after random reboot, and the phone stuck at bootanim.
Click to expand...
Click to collapse
Are you have random reboots when the phone is in wall charger? Trey boot android and connect the phone to wall charger and see if you have random reboots maybe is faulty battery!
Thant said:
Are you have random reboots when the phone is in wall charger? Trey boot android and connect the phone to wall charger and see if you have random reboots maybe is faulty battery!
Click to expand...
Click to collapse
And why solve the problem, if i reninstall the rom? And i don't charge it.
Evening i charge the phone fully, and today i have random reboots, only after i unlock the screen.
tejeskifly said:
And why solve the problem, if i reninstall the rom? And i don't charge it.
Evening i charge the phone fully, and today i have random reboots, only after i unlock the screen.
Click to expand...
Click to collapse
If it is faulty battery when you unlock your phone the battery must give more amperage to to the led and to the system and maybe she go down fast and the phoone reboots and stuck on boot animation. Are you tryed my sudestion or no. To this moment nobody report issue like your with any rom. For this I say to try my method play games and browse in youtube with wall charger connected and if you don't have problem is a faulty battery!
Solve the problems for few hours! In one x have minimum on the battery and after this the phone shut down!
Thant said:
If it is faulty battery when you unlock your phone the battery must give more amperage to to the led and to the system and maybe she go down fast and the phoone reboots and stuck on boot animation. Are you tryed my sudestion or no. To this moment nobody report issue like your with any rom. For this I say to try my method play games and browse in youtube with wall charger connected and if you don't have problem is a faulty battery!
Solve the problems for few hours! In one x have minimum on the battery and after this the phone shut down!
Click to expand...
Click to collapse
I try what you tell now, but my phone stable. I have few rebbot today, with near full batery. Now i just discharge it, with linux in background, runing stress. 4 cpu runing on 100%, but no reboots atm, The phone turn off, after battery level 0%
I try to catch a rebbot, with phone connected to pc, and logcat log errors, and fatalerrors.
The rebbots come most of time, if i unlock the screen, or start app, edit settings (change lang for example)
i can log a reboot with logcat (using adb wifi app)
Fatal errors:
Code:
F/libc ( 1241): Fatal signal 11 (SIGSEGV) at 0x00000008 (code=1), thread 1241 (screen.shortcut) - sent from process 8 (/proc/8/comm)
F/PackageManager( 6853): Unable to backup package manager settings, current changes will be lost at reboot
F/SystemServer( 6853): BOOT FAILURE starting Input Manager Service
F/SystemServer( 6853): java.lang.RuntimeException: Unable to get provider com.android.providers.settings.SettingsProvider: android.database.sqlite.SQLiteException: not an error (code 0): Could not open the database in read/write mode.
F/SystemServer( 6853): at android.app.ActivityThread.installProvider(ActivityThread.java)
F/SystemServer( 6853): at android.app.ActivityThread.acquireProvider(ActivityThread.java)
F/SystemServer( 6853): at android.app.ContextImpl$ApplicationContentResolver.acquireProvider(ContextImpl.java)
F/SystemServer( 6853): at android.content.ContentResolver.acquireProvider(ContentResolver.java)
F/SystemServer( 6853): at android.provider.Settings$NameValueCache.lazyGetProvider(Settings.java)
F/SystemServer( 6853): at android.provider.Settings$NameValueCache.getStringForUser(Settings.java)
F/SystemServer( 6853): at android.provider.Settings$Secure.getStringForUser(Settings.java)
F/SystemServer( 6853): at com.android.server.InputMethodManagerService$InputMethodSettings.getSelectedInputMethod(InputMethodManagerService.java)
F/SystemServer( 6853): at com.android.server.InputMethodManagerService.<init>(InputMethodManagerService.java)
F/SystemServer( 6853): at com.android.server.ServerThread.run(SystemServer.java)
F/SystemServer( 6853): Caused by: android.database.sqlite.SQLiteException: not an error (code 0): Could not open the database in read/write mode.
F/SystemServer( 6853): at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
F/SystemServer( 6853): at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java)
F/SystemServer( 6853): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java)
F/SystemServer( 6853): at com.android.providers.settings.abs.HtcAbsDatabaseHelper.getWritableDatabase(HtcAbsDatabaseHelper.java)
F/SystemServer( 6853): at com.android.providers.settings.SettingsProvider.establishDbTracking(SettingsProvider.java)
F/SystemServer( 6853): at com.android.providers.settings.SettingsProvider.onCreate(SettingsProvider.java)
F/SystemServer( 6853): at android.content.ContentProvider.attachInfo(ContentProvider.java)
Errors:
Code:
E/EmbeddedLogger( 594): App crashed without info!
E/AndroidRuntime( 594): *** FATAL EXCEPTION IN SYSTEM PROCESS: UI
E/AndroidRuntime( 594): android.database.sqlite.SQLiteDiskIOException: disk I/O error (code 778)
E/AndroidRuntime( 594): at android.database.sqlite.SQLiteConnection.nativeExecute(Native Method)
E/AndroidRuntime( 594): at android.database.sqlite.SQLiteConnection.execute(SQLiteConnection.java)
E/AndroidRuntime( 594): at android.database.sqlite.SQLiteSession.endTransactionUnchecked(SQLiteSession.java)
E/AndroidRuntime( 594): at android.database.sqlite.SQLiteSession.endTransaction(SQLiteSession.java)
E/AndroidRuntime( 594): at android.database.sqlite.SQLiteDatabase.endTransaction(SQLiteDatabase.java)
E/AndroidRuntime( 594): at com.android.internal.widget.LockSettingsService.writeToDb(LockSettingsService.java)
E/AndroidRuntime( 594): at com.android.internal.widget.LockSettingsService.writeToDb(LockSettingsService.java)
E/AndroidRuntime( 594): at com.android.internal.widget.LockSettingsService.setLong(LockSettingsService.java)
E/AndroidRuntime( 594): at com.android.internal.widget.LockPatternUtils.setLong(LockPatternUtils.java)
E/AndroidRuntime( 594): at com.android.internal.widget.LockPatternUtils.setLong(LockPatternUtils.java)
E/AndroidRuntime( 594): at com.android.internal.widget.LockPatternUtils.clearLockoutAttemptDeadline(LockPatternUtils.java)
E/AndroidRuntime( 594): at com.android.internal.policy.impl.keyguard_obsolete.KeyguardViewMediator.keyguardDone(KeyguardViewMediator.java)
E/AndroidRuntime( 594): at com.android.internal.policy.impl.keyguard_obsolete.KeyguardViewMediator.keyguardDone(KeyguardViewMediator.java)
E/AndroidRuntime( 594): at com.android.internal.policy.impl.keyguard_obsolete.LockPatternKeyguardView$6.goToUnlockScreen(LockPatternKeyguardView.java)
E/AndroidRuntime( 594): at com.htc.wrap.com.android.internal.policy.impl.HtcWrapKeyguardScreenCallback.goToUnlockScreen(HtcWrapKeyguardScreenCallback.java)
E/AndroidRuntime( 594): at com.htc.lockscreen.HtcLockScreen._goToUnlockScreen(HtcLockScreen.java)
E/AndroidRuntime( 594): at com.htc.lockscreen.HtcLockScreen.goToUnlockScreen(HtcLockScreen.java)
E/AndroidRuntime( 594): at com.htc.lockscreen.HtcLockScreen.goToUnlockScreen(HtcLockScreen.java)
E/AndroidRuntime( 594): at com.htc.lockscreen.HtcLockScreen$4.unlock(HtcLockScreen.java)
E/AndroidRuntime( 594): at com.htc.lockscreen.app.LSState.unlockScreen(LSState.java)
E/AndroidRuntime( 594): at com.htc.lockscreen.app.idlescreen.IdleScreenServiceWrap.onLSCommand(IdleScreenServiceWrap.java)
E/AndroidRuntime( 594): at com.htc.lockscreen.app.idlescreen.IdleScreenServiceWrap$MyUIHandler.handleMessage(IdleScreenServiceWrap.java)
E/AndroidRuntime( 594): at android.os.Handler.dispatchMessage(Handler.java)
E/AndroidRuntime( 594): at android.os.Looper.loop(Looper.java)
E/AndroidRuntime( 594): at android.os.HandlerThread.run(HandlerThread.java)
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
E/BufferQueue( 151): [Idlescreen:com.htc.idlescreen.shortcut] dequeueBuffer: SurfaceTexture has been abandoned!
F/libc ( 1241): Fatal signal 11 (SIGSEGV) at 0x00000008 (code=1), thread 1241 (screen.shortcut) - sent from process 8 (/proc/8/comm)
E/HtcBootAnimation( 6595): SQL error: unable to open database file
E/HtcBootAnimation( 6595): sqlite result: 14, errno: 30, Read-only file system
E/ ( 6595): file /data/data/com.nvidia.NvCPLSvc/files/driverlist.txt: not found!
E/installd( 156): eof
E/installd( 156): failed to read size
E/FrameworkListener( 149): read() failed (Connection reset by peer)
E/InputEventReceiver( 1369): channel '41f34788 com.htc.launcher/com.htc.launcher.Launcher (client)' ~ Publisher closed input channel or an error occurred. events=0x9
E/Sensors ( 1148): SensorEventQueue::waitForEvent error HANGUP
E/Sensors ( 1437): SensorEventQueue::waitForEvent error HANGUP
E/InputEventReceiver( 1295): channel '41f7f9e0 InputMethod (client)' ~ Publisher closed input channel or an error occurred. events=0x9
E/InputEventReceiver( 1148): channel '42296bd8 com.android.systemui.ImageWallpaper (client)' ~ Publisher closed input channel or an error occurred. events=0x9
E/InputEventReceiver( 5197): channel '41ee71a0 com.android.browser/com.android.browser.BrowserActivity (client)' ~ Publisher closed input channel or an error occurred. events=0x9
E/InputEventReceiver( 1148): channel '42293408 StatusBar (client)' ~ Publisher closed input channel or an error occurred. events=0x9
E/Sensors ( 5349): SensorEventQueue::waitForEvent error HANGUP
E/InputEventReceiver( 5970): channel '42071140 com.android.mms/com.android.mms.ui.ConversationList (client)' ~ Publisher closed input channel or an error occurred. events=0x9
E/HtcCameraHal( 6605): [CAM] [Calibration] open file ["/data/factory_main.bin"] failed, errno = 30 (Read-only file system)
E/NvCameraHalBufferNegotiation( 6605): Buffer Manager Preview is initializing to W = 1280, H = 720
E/NvCameraHalBufferNegotiation( 6605): Buffer Manager Still is initializing to W = 3264, H = 1840
E/NvCameraHalBufferNegotiation( 6605): Buffer Manager Video is initializing to W = 1280, H = 720
E/ ( 6605): file /data/data/com.nvidia.NvCPLSvc/files/driverlist.txt: not found!
E/HTC_Acoustic( 6605): failed to open file /system/etc/AIC3008_REG_MFG.csv: No such file or directory (2).
E/HTC_Acoustic( 6605): failed to open file /system/etc/soundimage/Sound_Original_HP_Generic.txt: No such file or directory (2).
E/HTC_Acoustic( 6605): read AIC3008 para from file failed -1
E/HTC_Acoustic( 6605): failed to open file /system/etc/soundimage/Sound_Original_HP_urBeats.txt: No such file or directory (2).
E/HTC_Acoustic( 6605): read AIC3008 para from file failed -1
E/HTC_Acoustic( 6605): failed to open file /system/etc/soundimage/Sound_Original_HP_Solo.txt: No such file or directory (2).
E/HTC_Acoustic( 6605): read AIC3008 para from file failed -1
E/HTC_Acoustic( 6605): failed to open file /system/etc/soundimage/Sound_Original_HP_Pro.txt: No such file or directory (2).
E/HTC_Acoustic( 6605): read AIC3008 para from file failed -1
E/HTC_Acoustic( 6605): failed to open file /system/etc/soundimage/Sound_Original_HP_Studio.txt: No such file or directory (2).
E/HTC_Acoustic( 6605): read AIC3008 para from file failed -1
E/HTC_Acoustic( 6605): failed to open file /system/etc/soundimage/Sound_Original_SPK_Beats.txt: No such file or directory (2).
E/HTC_Acoustic( 6605): read AIC3008 para from file failed -1
E/BatteryService( 6853): wirelessOnlinePath not found
E/BatteryService( 6853): extensionPath not found
E/NFC ( 6853): No such file: /sys/class/NFC_sensor/pn544/nxp_chip_alive
E/UserManagerService( 6853): Error writing user list
E/installd( 156): failed to chown '/data/data/com.adobe.flashplayer': Read-only file system
E/installd( 156): failed to chown '/data/data/com.adobe.reader': Read-only file system
E/PackageManager( 6853): Unable to copy native libraries
E/installd( 156): failed to chown '/data/data/com.ryosoftware.adbw': Read-only file system
E/installd( 156): failed to chown '/data/data/com.google.android.apps.books': Read-only file system
E/installd( 156): failed to chown '/data/data/com.google.android.apps.magazines': Read-only file system
E/installd( 156): failed to chown '/data/data/com.keramidas.TitaniumBackup': Read-only file system
E/installd( 156): failed to chown '/data/data/com.google.android.apps.plus': Read-only file system
E/installd( 156): failed to chown '/data/data/com.google.android.talk': Read-only file system
E/installd( 156): failed to chown '/data/data/com.google.android.marvin.talkback': Read-only file system
E/installd( 156): failed to chown '/data/data/com.google.android.street': Read-only file system
E/installd( 156): failed to chown '/data/data/com.google.android.videos': Read-only file system
E/installd( 156): failed to chown '/data/data/com.google.android.gm': Read-only file system
E/installd( 156): failed to chown '/data/data/com.melodis.midomiMusicIdentifier.freemium': Read-only file system
E/installd( 156): failed to chown '/data/data/com.mxtech.videoplayer.ad': Read-only file system
E/installd( 156): failed to chown '/data/data/com.twitter.android': Read-only file system
E/installd( 156): failed to chown '/data/data/org.adaway': Read-only file system
E/installd( 156): failed to chown '/data/data/tunein.player': Read-only file system
E/installd( 156): failed to chown '/data/data/com.fd.httpd': Read-only file system
E/installd( 156): failed to chown '/data/data/com.nero.android.htc.sync': Read-only file system
E/installd( 156): failed to chown '/data/data/com.google.android.gms': Read-only file system
E/installd( 156): failed to chown '/data/data/com.google.android.googlequicksearchbox': Read-only file system
E/installd( 156): failed to chown '/data/data/com.facebook.katana': Read-only file system
E/installd( 156): failed to chown '/data/data/com.estrongs.android.pop': Read-only file system
E/installd( 156): failed to chown '/data/data/com.google.android.youtube': Read-only file system
E/installd( 156): failed to chown '/data/data/com.google.android.apps.maps': Read-only file system
F/PackageManager( 6853): Unable to backup package manager settings, current changes will be lost at reboot
E/AndroidRuntime( 6853): Error reporting WTF
E/AndroidRuntime( 6853): java.lang.NullPointerException
E/AndroidRuntime( 6853): at com.android.internal.os.RuntimeInit.wtf(RuntimeInit.java)
E/AndroidRuntime( 6853): at android.util.Log$1.onTerribleFailure(Log.java)
E/AndroidRuntime( 6853): at android.util.Log.wtf(Log.java)
E/AndroidRuntime( 6853): at android.util.Log.wtf(Log.java)
E/AndroidRuntime( 6853): at com.android.server.pm.Settings.writeLPr(Settings.java)
E/AndroidRuntime( 6853): at com.android.server.pm.PackageManagerService.<init>(PackageManagerService.java)
E/AndroidRuntime( 6853): at com.android.server.pm.PackageManagerService.main(PackageManagerService.java)
E/AndroidRuntime( 6853): at com.android.server.ServerThread.run(SystemServer.java)
E/SQLiteDatabase( 6853): Failed to open database '/data/data/com.android.providers.settings/databases/settings.db'.
E/SQLiteDatabase( 6853): android.database.sqlite.SQLiteException: not an error (code 0): Could not open the database in read/write mode.
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java)
E/SQLiteDatabase( 6853): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java)
E/SQLiteDatabase( 6853): at com.android.providers.settings.abs.HtcAbsDatabaseHelper.getWritableDatabase(HtcAbsDatabaseHelper.java)
E/SQLiteDatabase( 6853): at com.android.providers.settings.SettingsProvider.establishDbTracking(SettingsProvider.java)
E/SQLiteDatabase( 6853): at com.android.providers.settings.SettingsProvider.onCreate(SettingsProvider.java)
E/SQLiteDatabase( 6853): at android.content.ContentProvider.attachInfo(ContentProvider.java)
E/SQLiteDatabase( 6853): at android.app.ActivityThread.installProvider(ActivityThread.java)
E/SQLiteDatabase( 6853): at android.app.ActivityThread.installContentProviders(ActivityThread.java)
E/SQLiteDatabase( 6853): at android.app.ActivityThread.installSystemProviders(ActivityThread.java)
E/SQLiteDatabase( 6853): at com.android.server.am.ActivityManagerService.installSystemProviders(ActivityManagerService.java)
E/SQLiteDatabase( 6853): at com.android.server.ServerThread.run(SystemServer.java)
E/System ( 6853): ******************************************
E/System ( 6853): ************ Failure starting core service
E/System ( 6853): java.lang.RuntimeException: Unable to get provider com.android.providers.settings.SettingsProvider: android.database.sqlite.SQLiteException: not an error (code 0): Could not open the database in read/write mode.
E/System ( 6853): at android.app.ActivityThread.installProvider(ActivityThread.java)
E/System ( 6853): at android.app.ActivityThread.installContentProviders(ActivityThread.java)
E/System ( 6853): at android.app.ActivityThread.installSystemProviders(ActivityThread.java)
E/System ( 6853): at com.android.server.am.ActivityManagerService.installSystemProviders(ActivityManagerService.java)
E/System ( 6853): at com.android.server.ServerThread.run(SystemServer.java)
E/System ( 6853): Caused by: android.database.sqlite.SQLiteException: not an error (code 0): Could not open the database in read/write mode.
E/System ( 6853): at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
E/System ( 6853): at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java)
E/System ( 6853): at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java)
E/System ( 6853): at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java)
E/System ( 6853): at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java)
E/System ( 6853): at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java)
E/System ( 6853): at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java)
E/System ( 6853): at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java)
E/System ( 6853): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java)
E/System ( 6853): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java)
E/System ( 6853): at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java)
E/System ( 6853): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java)
E/System ( 6853): at com.android.providers.settings.abs.HtcAbsDatabaseHelper.getWritableDatabase(HtcAbsDatabaseHelper.java)
E/System ( 6853): at com.android.providers.settings.SettingsProvider.establishDbTracking(SettingsProvider.java)
E/System ( 6853): at com.android.providers.settings.SettingsProvider.onCreate(SettingsProvider.java)
E/System ( 6853): at android.content.ContentProvider.attachInfo(ContentProvider.java)
E/System ( 6853): ... 5 more
E/SQLiteDatabase( 6853): Failed to open database '/data/data/com.android.providers.settings/databases/settings.db'.
E/SQLiteDatabase( 6853): android.database.sqlite.SQLiteException: not an error (code 0): Could not open the database in read/write mode.
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java)
E/SQLiteDatabase( 6853): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java)
E/SQLiteDatabase( 6853): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java)
E/SQLiteDatabase( 6853): at com.android.providers.settings.abs.HtcAbsDatabaseHelper.getWritableDatabase(HtcAbsDatabaseHelper.java)
E/SQLiteDatabase( 6853): at com.android.providers.settings.SettingsProvider.establishDbTracking(SettingsProvider.java)
E/SQLiteDatabase( 6853): at com.android.providers.settings.SettingsProvider.onCreate(SettingsProvider.java)
E/SQLiteDatabase( 6853): at android.content.ContentProvider.attachInfo(ContentProvider.java)
E/SQLiteDatabase( 6853): at android.app.ActivityThread.installProvider(ActivityThread.java)
E/SQLiteDatabase( 6853): at android.app.ActivityThread.acquireProvider(ActivityThread.java)
E/SQLiteDatabase( 6853): at android.app.ContextImpl$ApplicationContentResolver.acquireProvider(ContextImpl.java)
E/SQLiteDatabase( 6853): at android.content.ContentResolver.acquireProvider(ContentResolver.java)
E/SQLiteDatabase( 6853): at android.provider.Settings$NameValueCache.lazyGetProvider(Settings.java)
E/SQLiteDatabase( 6853): at android.provider.Settings$NameValueCache.getStringForUser(Settings.java)
E/SQLiteDatabase( 6853): at android.provider.Settings$Secure.getStringForUser(Settings.java)
E/SQLiteDatabase( 6853): at com.android.server.InputMethodManagerService$InputMethodSettings.getSelectedInputMethod(InputMethodManagerService.java)
E/SQLiteDatabase( 6853): at com.android.server.InputMethodManagerService.<init>(InputMethodManagerService.java)
E/SQLiteDatabase( 6853): at com.android.server.ServerThread.run(SystemServer.java)
F/SystemServer( 6853): BOOT FAILURE starting Input Manager Service
F/SystemServer( 6853): java.lang.RuntimeException: Unable to get provider com.android.providers.settings.SettingsProvider: android.database.sqlite.SQLiteException: not an error (code 0): Could not open the database in read/write mode.
F/SystemServer( 6853): at android.app.ActivityThread.installProvider(ActivityThread.java)
F/SystemServer( 6853): at android.app.ActivityThread.acquireProvider(ActivityThread.java)
F/SystemServer( 6853): at android.app.ContextImpl$ApplicationContentResolver.acquireProvider(ContextImpl.java)
F/SystemServer( 6853): at android.content.ContentResolver.acquireProvider(ContentResolver.java)
F/SystemServer( 6853): at android.provider.Settings$NameValueCache.lazyGetProvider(Settings.java)
F/SystemServer( 6853): at android.provider.Settings$NameValueCache.getStringForUser(Settings.java)
F/SystemServer( 6853): at android.provider.Settings$Secure.getStringForUser(Settings.java)
F/SystemServer( 6853): at com.android.server.InputMethodManagerService$InputMethodSettings.getSelectedInputMethod(InputMethodManagerService.java)
F/SystemServer( 6853): at com.android.server.InputMethodManagerService.<init>(InputMethodManagerService.java)
F/SystemServer( 6853): at com.android.server.ServerThread.run(SystemServer.java)
F/SystemServer( 6853): Caused by: android.database.sqlite.SQLiteException: not an error (code 0): Could not open the database in read/write mode.
F/SystemServer( 6853): at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
F/SystemServer( 6853): at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java)
F/SystemServer( 6853): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java)
F/SystemServer( 6853): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java)
F/SystemServer( 6853): at com.android.providers.settings.abs.HtcAbsDatabaseHelper.getWritableDatabase(HtcAbsDatabaseHelper.java)
F/SystemServer( 6853): at com.android.providers.settings.SettingsProvider.establishDbTracking(SettingsProvider.java)
F/SystemServer( 6853): at com.android.providers.settings.SettingsProvider.onCreate(SettingsProvider.java)
F/SystemServer( 6853): at android.content.ContentProvider.attachInfo(ContentProvider.java)
F/SystemServer( 6853): ... 10 more
F/SystemServer( 6853): BOOT FAILURE making display ready
F/SystemServer( 6853): java.lang.NullPointerException
F/SystemServer( 6853): at com.android.server.ServerThread.run(SystemServer.java)
E/EmbeddedLogger( 6853): App crashed without info!
My phone is doing the same thing. Plus I am constantly losing service. I was on ViperXL Rom ans then tried to go back to stock with RUU, but I wouldn't work. Now I'm in magiorom and it's doing the same thing. Don't know what the problem is.
rosemaryclements0918 said:
My phone is doing the same thing. Plus I am constantly losing service. I was on ViperXL Rom ans then tried to go back to stock with RUU, but I wouldn't work. Now I'm in magiorom and it's doing the same thing. Don't know what the problem is.
Click to expand...
Click to collapse
I buy a new battery today, i need to wait 3 or 4 week for it...
tejeskifly said:
I buy a new battery today, i need to wait 3 or 4 week for it...
Click to expand...
Click to collapse
Hi, probably I have similar problem, is the problem solved with a new battery?
Thx.
Related
Need Help: EPST, PRL is not working
EPST process is crashing while running ##786#. I can’t read service programming settings in QPST as well, it says “Roaming list receive failed”.
Log file shows that exception is thrown when system is trying to read PRL in EPST process. (##786#)
I tried hard reset without any luck.
I have updated to 2.2 so I can’t root and rollback to factory settings.
Here is the log:
08-11 18:16:37.426 I/ActivityManager( 108): Displayed activity com.google.android.epst/.EPST: 323 ms (total 323 ms)
---------omitted entries-----------------------------
08-11 18:16:39.995 I/Port ( 8075): register translator:com.google.android.epst.translator.PrlIdTranslator and item id:3017 in current send record
08-11 18:16:40.035 V/AlarmManager( 108): Alarm triggering: Alarm{464df068 type 0 com.google.android.gsf}
08-11 18:16:40.035 V/AlarmManager( 108): Adding Alarm{464df068 type 0 com.google.android.gsf} Aug 11 06:46:40 pm
08-11 18:16:40.106 E/DataObject( 8075): received command error, reason is bad parametersand the orginal message is 490000
08-11 18:16:40.106 D/AndroidRuntime( 8075): Shutting down VM
08-11 18:16:40.106 W/dalvikvm( 8075): threadid=1: thread exiting with uncaught exception (group=0x400259f8)
08-11 18:16:40.115 E/AndroidRuntime( 8075): FATAL EXCEPTION: main
08-11 18:16:40.115 E/AndroidRuntime( 8075): java.lang.StringIndexOutOfBoundsException
08-11 18:16:40.115 E/AndroidRuntime( 8075): at java.lang.String.substring(String.java:1579)
08-11 18:16:40.115 E/AndroidRuntime( 8075): at com.google.android.epst.internal.CmdParser.getResult(CmdParser.java:107)
08-11 18:16:40.115 E/AndroidRuntime( 8075): at com.google.android.epst.dmcmd.DM_CMD_CODE_PRL_READ.read(DM_CMD_CODE_PRL_READ.java:79)
08-11 18:16:40.115 E/AndroidRuntime( 8075): at com.google.android.epst.internal.DataObject.receivedReadCommandGeneric(DataObject.java:522)
08-11 18:16:40.115 E/AndroidRuntime( 8075): at com.google.android.epst.internal.DataObjectHandler.handleMessage(DataObjectHandler.java:364)
08-11 18:16:40.115 E/AndroidRuntime( 8075): at android.os.Handler.dispatchMessage(Handler.java:99)
08-11 18:16:40.115 E/AndroidRuntime( 8075): at android.os.Looper.loop(Looper.java:144)
08-11 18:16:40.115 E/AndroidRuntime( 8075): at android.app.ActivityThread.main(ActivityThread.java:4937)
08-11 18:16:40.115 E/AndroidRuntime( 8075): at java.lang.reflect.Method.invokeNative(Native Method)
08-11 18:16:40.115 E/AndroidRuntime( 8075): at java.lang.reflect.Method.invoke(Method.java:521)
08-11 18:16:40.115 E/AndroidRuntime( 8075): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
08-11 18:16:40.115 E/AndroidRuntime( 8075): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
08-11 18:16:40.115 E/AndroidRuntime( 8075): at dalvik.system.NativeStart.main(Native Method)
08-11 18:16:40.155 I/global ( 108): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
08-11 18:16:40.205 W/ActivityManager( 108): Force finishing activity com.google.android.epst/.ListItemsActivity
08-11 18:16:40.357 I/EventLogService( 259): Aggregate from 1281528999926 (log), 1281528999926 (data)
08-11 18:16:40.525 I/global ( 108): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
08-11 18:16:40.705 W/ActivityManager( 108): Activity pause timeout for HistoryRecord{464174f8 com.google.android.epst/.ListItemsActivity}[/SIZE][/SIZE]
Update
Problem:
NV area of memory had been messed up while repairing MEID. (temp solution: I was using NAM2 instated of NAM1)
Solution:
Rescan your phone for valid MEID/ESN addresses and verify that it has valid/current ESN/MEID .
Do it 3-4 times to make sure all addresses has been verified.
In my case there was one address which was messed up and it was the culprit. (It was zeroed out so I wrote my ESN there)
Restart your phone and fire up EPST. If your EPST is working fine then just do reset from EPST menu.
As I don't seem to have permissions to post in the developers' forum.. here goes:
When installing the OTA patch for MIUI 1.9.23 to 1.9.30 on my Desire, a reboot ended being stuck in the Recovery.
logcat showed me the following:
D/AndroidRuntime( 1503):
D/AndroidRuntime( 1503): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 1503): CheckJNI is OFF
D/dalvikvm( 1503): creating instr width table
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/core.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/core.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/bouncycastle.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/bouncycastle.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/ext.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/ext.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/framework.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/framework.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/android.policy.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/android.policy.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/services.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/services.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/core-junit.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/core-junit.jar'
E/dalvikvm( 1503): No valid entries found in bootclasspath '/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar'
W/dalvikvm( 1503): JNI_CreateJavaVM failed
E/AndroidRuntime( 1503): JNI_CreateJavaVM failed
These errors returned in a loop.
Looking on the system itself, /data/dalvik-cache seemed to be missing.
After creating this directory, the phone continued booting.
So this would be a quick-fix.
Yet I didn't take into account the necessary symbol links for the a2sd to work properly yet.
Can someone point me to some docs which symbol links I should apply?
Thx for your help.
According to the logcat, your dalvik-cache is missing. Wipe dalvik cache from recovery.
If that won't help, create the following directory and then wipe:
/data/dalvik-cache
If still does not work, check THIS thread.
Hi davebugyi
Thanks for your answer.
That's what I did, and it fixed the problem.
I wanted to write that in the original thread, but I didn't have enough interaction on this forum (10 posts) to allow me to write there directly.
Cheers!
(I'm terrible at making my posts make sense, so just ask if you're confused with anything I say in here. Sometimes I even confuse myself!)
I was looking through the framework-res.apk and noticed that in the assets folder there's a folder named nookcol_512 with some Nook Color related images, and another folder named gossamer that looks like the booting screen for the NST. I've been comparing the framework-res.apk to one I got from a 2.1 AVD, and the two folders aren't there in the AVD's framework.
I edited the files in the gossamer folder, and they changed the booting screen!
I was wondering if it's possible to change some of the non-image files in the framework-res.apk and change the way some things function.
Can be and has been done. That's how XorZone's mod works.
I've modified the files in assets/images/gossamer
I deleted the entire assets/images/nookcol_512
assets/sounds could probably go too
How would I edit the xml files? Use notepad or something? Or is there a specific program I need?
Googie2149 said:
How would I edit the xml files? Use notepad or something? Or is there a specific program I need?
Click to expand...
Click to collapse
eclipse | xml spy | MS visual studio.
Any of the three will be quite overkill for a simple XML editor...
Would you replace the framework-res.apk with your own? How would you do that?
brendan10211 said:
Would you replace the framework-res.apk with your own? How would you do that?
Click to expand...
Click to collapse
You should be able to replace it with ADB, but that always got me stuck in boot loops, so eded333 made a zip that you run via CWM Recovery that replaces the framework. You can pull the framework from your nook onto the computer with this command with ADB:
Code:
adb pull /system/framework/framework-res.apk
I've never had a problem (knock on wood) with ADB push replacing framework-res.apk
I usually just push it and then immediately do an ADB reboot.
Renate NST said:
I've never had a problem (knock on wood) with ADB push replacing framework-res.apk
I usually just push it and then immediately do an ADB reboot.
Click to expand...
Click to collapse
When I push it, it immediately reboots and gets stuck in a boot loop.
Someone feel like helping in messing with the xml's? These things are confusing, so much referencing to other things...
I have the same problem as Googie, yet I know absolutely nothing about anything.
While I was messing with framework-res, I've had bootloops issues too when replacing the file.
The solution I've found is to replace while android is not running, i.e., with CWM update.zip feature. Just replace the framework-res.apk inside this zip with yours and apply "custom zip" via CWM.
That seems like a good idea, but I can't seem to even boot into CWM. I followed the steps on the CWM post, but they are really vague. Can someone tell me what they did?
Oh, another thing, how do I get that zip that eded33 made? I saw it mentioned way up there, but I don't see a download link or anything.
As long as you're messing with framework-res.apk you might as well fix the list divider.
It was speced at 600 wide because they never thought of landscape.
If you have any lists in landscape the dividers will not extend the full length.
This goes in res/drawable-mdpi/divider_horizontal_bright.png
Oh, dear. I have to put it in a zip or the forums here will try to turn it into a JPEG.
marspeople said:
While I was messing with framework-res, I've had bootloops issues too when replacing the file.
The solution I've found is to replace while android is not running, i.e., with CWM update.zip feature. Just replace the framework-res.apk inside this zip with yours and apply "custom zip" via CWM.
Click to expand...
Click to collapse
When you say custom zip do you mean install zip from SD card? Because that did not work for me.
brendan10211 said:
When you say custom zip do you mean install zip from SD card? Because that did not work for me.
Click to expand...
Click to collapse
Yes, "choose zip from SD card" or something similar. Did you notice output messasges from the script and if it showed any errors?
marspeople said:
Yes, "choose zip from SD card" or something similar. Did you notice output messasges from the script and if it showed any errors?
Click to expand...
Click to collapse
I will now type exactly what happened in CWM.
Code:
-- Installing: /sdcard/framework-update.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
What?
brendan10211 said:
I will now type exactly what happened in CWM.
Code:
-- Installing: /sdcard/framework-update.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
What?
Click to expand...
Click to collapse
That is weird. I've just tested here and it went normally. Are you running CWM from SD Card or via recovery mode?
From the SD card, I have no idea what recovery mode is...
Hey guys. Can someone help me out? When i change framework-res.apk to edited (decompiled-edited-compiled-signed with apk-multi-tool), the whole Android permission thing is falling apart and i lose the ability to launch most apps - only preinstalled Nook system ones are continuing to work. I've tried CWM fix permissions and manual ch... commands, nothing changes, logcat is full of errors like
I/ActivityManager( 798): Start proc android.process.acore for activity org.adw.launcher/.Launcher: pid=5281 uid=10020 gids={}
I/UsageStats( 798): Unexpected resume of org.adw.launcher while already resumed in org.adw.launcher
I/DeviceManagerHandler( 1094): HandleMessage(): msg.what (1)
I/ActivityThread( 5277): Publishing provider mms: com.android.providers.telephony.MmsProvider
I/ActivityThread( 5277): Publishing provider sms: com.android.providers.telephony.SmsProvider
I/ActivityThread( 5277): Publishing provider telephony: com.android.providers.telephony.TelephonyProvider
I/ActivityThread( 5277): Publishing provider icc: com.android.phone.IccProvider
I/ActivityThread( 5277): Publishing provider mms-sms: com.android.providers.telephony.MmsSmsProvider
I/ActivityThread( 5281): Publishing provider org.adw.launcher.settings: org.adw.launcher.LauncherProvider
I/DeviceManagerHandler( 1094): HandleMessage(): msg.what (1)
W/ActivityManager( 798): Permission Denial: setPersistent() from pid=5281, uid=10020 requires android.permission.PERSISTENT_ACTIVITY
D/AndroidRuntime( 5281): Shutting down VM
W/dalvikvm( 5281): threadid=3: thread exiting with uncaught exception (group=0x4001b170)
E/AndroidRuntime( 5281): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 5281): java.lang.RuntimeException: Unable to start activity ComponentInfo{org.adw.launcher/org.adw.launcher.Launcher}: java.lang.SecurityException: Permission Denial: setPersistent() from pid=5281, uid=10020 requires android.permission.PERSISTENT_ACTIVITY
E/AndroidRuntime( 5281): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2496)
E/AndroidRuntime( 5281): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/AndroidRuntime( 5281): at android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/AndroidRuntime( 5281): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/AndroidRuntime( 5281): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 5281): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 5281): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime( 5281): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 5281): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 5281): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 5281): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 5281): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 5281): Caused by: java.lang.SecurityException: Permission Denial: setPersistent() from pid=5281, uid=10020 requires android.permission.PERSISTENT_ACTIVITY
E/AndroidRuntime( 5281): at android.os.Parcel.readException(Parcel.java:1218)
E/AndroidRuntime( 5281): at android.os.Parcel.readException(Parcel.java:1206)
E/AndroidRuntime( 5281): at android.app.ActivityManagerProxy.setPersistent(ActivityManagerNative.java:1389)
E/AndroidRuntime( 5281): at android.app.Activity.setPersistent(Activity.java:1612)
E/AndroidRuntime( 5281): at org.adw.launcher.Launcher.onCreate(Launcher.java:370)
E/AndroidRuntime( 5281): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 5281): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/AndroidRuntime( 5281): ... 11 more
Click to expand...
Click to collapse
What am i to do? I REALLY do want to make changes in framework (built-in png and strings Russian localisation), but this thing is stronger than me.
How did you replace it?
Hello all,
I need some help with my HTC Desire.
I use MIUI V2.4.6. with a2sd.
Baseband : 32.56.00.32U_5.17.05.08
I've got an 1GO EXT4 partition on my SD card Samsung 8 Go SDHC Class 6, made with CW recovery.
I've installed MIUI with the third option for a2sd.
Some times, I have a lot's of FC on almost every apps.
I've to reboot my phone, then it's working until next crash.
In the logcat, I've got this :
Code:
I/ActivityManager( 1193): Start proc com.android.providers.calendar for restart com.android.providers.calendar: pid=2056 uid=10007 gids={3003}
W/InputManagerService( 1193): Window already focused, ignoring focus gain of: [email protected]
I/ActivityThread( 2056): Pub com.android.calendar: com.android.providers.calendar.CalendarProvider2
I/Database( 2056): sqlite returned: error code = 14, msg = cannot open file at line 26054 of [42537b6056]
I/Database( 2056): sqlite returned: error code = 14, msg = unable to open database file
E/Database( 2056): sqlite3_exec - Failed to set WAL mode for [/data/data/com.android.providers.calendar/databases/calendar.db]
I/Database( 2056): sqlite returned: error code = 14, msg = cannot open file at line 26054 of [42537b6056]
I/Database( 2056): sqlite returned: error code = 14, msg = unable to open database file
E/Database( 2056): sqlite3_exec - Failed to set DELETE mode for [/data/data/com.android.providers.calendar/databases/calendar.db]
D/AndroidRuntime( 2056): Shutting down VM
W/dalvikvm( 2056): threadid=1: thread exiting with uncaught exception (group=0x4016e568)
E/AndroidRuntime( 2056): FATAL EXCEPTION: main
E/AndroidRuntime( 2056): java.lang.RuntimeException: Unable to get provider com.android.providers.calendar.CalendarProvider2: android.database.sqlite.SQLiteException: unable to open database file
E/AndroidRuntime( 2056): at android.app.ActivityThread.installProvider(ActivityThread.java:3577)
E/AndroidRuntime( 2056): at android.app.ActivityThread.installContentProviders(ActivityThread.java:3329)
E/AndroidRuntime( 2056): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:3285)
E/AndroidRuntime( 2056): at android.app.ActivityThread.access$2200(ActivityThread.java:117)
E/AndroidRuntime( 2056): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:969)
E/AndroidRuntime( 2056): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 2056): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 2056): at android.app.ActivityThread.main(ActivityThread.java:3703)
E/AndroidRuntime( 2056): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2056): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 2056): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 2056): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 2056): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 2056): Caused by: android.database.sqlite.SQLiteException: unable to open database file
E/AndroidRuntime( 2056): at android.database.sqlite.SQLiteDatabase.dbopen(Native Method)
E/AndroidRuntime( 2056): at android.database.sqlite.SQLiteDatabase.<init>(SQLiteDatabase.java:1849)
E/AndroidRuntime( 2056): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:820)
E/AndroidRuntime( 2056): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:854)
E/AndroidRuntime( 2056): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:847)
E/AndroidRuntime( 2056): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:558)
E/AndroidRuntime( 2056): at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:203)
E/AndroidRuntime( 2056): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:118)
E/AndroidRuntime( 2056): at com.android.providers.calendar.CalendarDatabaseHelper.getWritableDatabase(CalendarDatabaseHelper.java:1143)
E/AndroidRuntime( 2056): at com.android.providers.calendar.CalendarProvider2.onAccountsUpdated(CalendarProvider2.java:3807)
E/AndroidRuntime( 2056): at com.android.providers.calendar.CalendarProvider2.verifyAccounts(CalendarProvider2.java:393)
E/AndroidRuntime( 2056): at com.android.providers.calendar.CalendarProvider2.onCreate(CalendarProvider2.java:407)
E/AndroidRuntime( 2056): at android.content.ContentProvider.attachInfo(ContentProvider.java:806)
E/AndroidRuntime( 2056): at android.app.ActivityThread.installProvider(ActivityThread.java:3574)
E/AndroidRuntime( 2056): ... 12 more
I/Process ( 1193): Sending signal. PID: 2036 SIG: 9
I/Process ( 1193): Sending signal. PID: 2056 SIG: 9
W/ActivityManager( 1193): Process com.android.providers.calendar has crashed too many times: killing!
I/ActivityManager( 1193): Kill com.android.calendar (pid 2036): provider com.android.providers.calendar.CalendarProvider2 in dying process com.android.providers.calendar
W/ActivityManager( 1193): Unable to launch app com.android.providers.calendar/10007 for provider com.android.calendar: launching app became null
W/ActivityManager( 1193): Unable to launch app com.android.providers.calendar/10007 for provider com.android.calendar: launching app became null
I/ActivityManager( 1193): Process com.android.calendar (pid 2036) has died.
I/WindowManager( 1193): WIN DEATH: Window{40808e60 com.android.calendar/com.android.calendar.MonthActivity paused=false}
W/InputManagerService( 1193): Got RemoteException sending setActive(false) notification to pid 2036 uid 10006
How can I solve this issue ?
Thank you !
Regards,
Simon
eI don't even have a clue what all that means, but try to change recovery to 4ext and do a repartitioning of your sd card.
Sent from my HTC Desire using Flashes and Thunders
Thanks, I will give it a try !
I've installed 4ext recovery, created 1GO ext4 partition on my SD card.
Full wipe, install MIUI again.
And I still have the issue. I suspect trouble with the a2sd.
Does someone else have a clue ?
Here is the full log if this can help :
http://pastebin.com/NFD5acBV
Now I've got a black screen when trying wake up the phone.
Here are the logs :
http://pastebin.com/tak6qTM9
Run "Fix Permissions" in recovery and see if it helps.
When I've got some Force Close, I ran fix_permissions from terminal and/or from recovery.
Didn't help but I will try again.
Try to download different MIUI rom directly from the source (like MIUI Great Britain) and flash a2sd script.
Sent from my HTC Desire using Flashes and Thunders
Which one of a2sd script did you recommend ?
All of them work, but the fastest experience I had with a2sd by Darktremmor. I heard that it works good with int2ext+ by Croniccorey.
Sent from my HTC Desire using Flashes and Thunders
Ok, so I install MIUI V2.4.13 from MIUI GB.
Then install CronMod INT2EXT4.
I will keep you in touch.
Thank you !
Hello,
So the week end is almost passed.
Saturday, I've left home and I got one black screen (won't wake up) and some Force Close.
Sunday, I was at home, and he doesn't crash or FC.
I've got Free as provider, with roaming to switch from Free to Orange antenna.
Maybe there is something with the radio card ? Or motherboard ?
Do not use ANY OTHER a2sd script instead of the MIUI comes with.
You right, I see there is already a a2sd script in /etc/init.d
I try to remove the MIUI one, but then all my apps are gone.
I decide to test one thing at a time.
Full wipe then reinstall MIUI from GB source no more apps for now.
I just have a surprise with Play Store, I think he update himslef to the lastest version, then he disappear from the desktop.
I cannot start it, so I reinstall it from apk found on this forum.
One more thing : I saw somewhere that I have to launch this command :
pm setInstallLocation 1 to force internal installation of applications, do I have to launch this command after installing MIUI ?
Use whatever a2sd script you like. I used it with both a2sd (DarkTremmor) and a2sdx (Amarullz), also tried with int2ext4+ (Croniccorey), and everything worked PERFECTLY, just flash it after a clean flash of rom without rebooting.
A fix for Play Store:
-Use titanium backup to clear data and uninstall current play store.
-Rename Play Store app to Vending.apk, use Aroma File Manager by Amarullz (it is used from recovery http://forum.xda-developers.com/showthread.php?t=1646108) to copy it to system/app folder.
-After restart use some file manager with root privileges to change permissions for Vending.app to
[x] [x] [x]
[x] [ ] [x]
[x] [ ] [x]
Ok, so after a few days :
With or without a2sd but without apps installed --> OK working fine !
I will try to install apps one by one to see what happen and when.
Find the defective apps.
Yesterday, first apps installed : Banque --> No issue
Tonight, i will install Maps
I've tried CM10.1 RC5 and yesterday's nightly, with a clean install (clear data and cache) and every app that depends on GoogleTTS gets force closed -- the tts preferences in system settings, duolingo, etc. I would see this in logcat:
Code:
E/AndroidRuntime( 7237): java.lang.UnsatisfiedLinkError: Couldn't load speexwrapper from loader dalvik.system.PathClassLoader[dexPath=/system/app/GoogleTTS.apk,libraryPath=/data/app-lib/GoogleTTS]: findLibrary returned null
E/AndroidRuntime( 7237): at java.lang.Runtime.loadLibrary(Runtime.java:365)
E/AndroidRuntime( 7237): at java.lang.System.loadLibrary(System.java:535)
E/AndroidRuntime( 7237): at com.google.android.tts.network.BufferedSpeexDecoder.<clinit>(BufferedSpeexDecoder.java:17)
E/AndroidRuntime( 7237): at com.google.android.tts.network.NetworkSynthesizer.<init>(NetworkSynthesizer.java:68)
E/AndroidRuntime( 7237): at com.google.android.tts.GoogleTTSService.onCreate(GoogleTTSService.java:45)
E/AndroidRuntime( 7237): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2657)
E/AndroidRuntime( 7237): at android.app.ActivityThread.access$1600(ActivityThread.java:153)
E/AndroidRuntime( 7237): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1329)
E/AndroidRuntime( 7237): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 7237): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 7237): at android.app.ActivityThread.main(ActivityThread.java:5227)
E/AndroidRuntime( 7237): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 7237): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 7237): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
E/AndroidRuntime( 7237): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:562)
E/AndroidRuntime( 7237): at dalvik.system.NativeStart.main(Native Method)
I installed gapps-jb-20130301-signed.zip along with CM10.1.
It looks like /system/lib/libspeexwrapper.so is set to be readable by root only. I set it to be readable by all users, and tts works!
$ adb shell
$ su
# mount -o rw,remount /system
# chmod 666 /system/lib/libspeexwrapper.so
# mount -o ro,remount /system
matth45 said:
I've tried CM10.1 RC5 and yesterday's nightly, with a clean install (clear data and cache) and every app that depends on GoogleTTS gets force closed -- the tts preferences in system settings, duolingo, etc. I would see this in logcat:
Code:
E/AndroidRuntime( 7237): java.lang.UnsatisfiedLinkError: Couldn't load speexwrapper from loader dalvik.system.PathClassLoader[dexPath=/system/app/GoogleTTS.apk,libraryPath=/data/app-lib/GoogleTTS]: findLibrary returned null
I installed gapps-jb-20130301-signed.zip along with CM10.1.
It looks like /system/lib/libspeexwrapper.so is set to be readable by root only. I set it to be readable by all users, and tts works!
$ adb shell
$ su
# mount -o rw,remount /system
# chmod 666 /system/lib/libspeexwrapper.so
# mount -o ro,remount /system
Click to expand...
Click to collapse
Nice one, thanks.
Solved
matth45 said:
It looks like /system/lib/libspeexwrapper.so is set to be readable by root only. I set it to be readable by all users, and tts works!
$ adb shell
$ su
# mount -o rw,remount /system
# chmod 666 /system/lib/libspeexwrapper.so
# mount -o ro,remount /system
Click to expand...
Click to collapse
You are the best man.Really thank you