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
___________________
Related
Using the default browser, on JF 1.5, every time I try to open it, I get:
"The application Browser (process com.android.browser) has stopped unexpectedly. Please try again."
This is still happening after numerous reboots. I haven't done anything since this morning when it was working. I don't know what would've changed.
Can I try reinstalling the apk? Or what should I try?
Did you perform a wipe when you installed the update? If not, try that first. If it still persists, then run the update again.
Sorry, guess I should've clarified. I've been running this build since the day it came out with no issues. Then today, out of the blue, it started happening.
I tried to install Browser.apk via apk installer and was told I couldn't install it. When I tried to install via ADB, I got "[INSTALL_FAILED_ALREADY_EXISTS]"
you would have to remove it before reinstalling.... try doing logcat to see why it force crashes. just connect your phone to your computer run adb logcat then on your phone start the browser. when it crashes you should see some type of exception, see what it is complaining about.
If you have your data on sdcard then you could have a stale nfs file handle and you need to get rid of it by mounting your phone in linux and emptying your data directory. When you reboot after that your phone will redo the build the data. Just dont delete the directory. You can just make a new file on the same partition and move the contents of your data directory to the new file. The phone wont look for data in random places so that works.
Just verify this before you do it. I could be wrong. Just a guess.
I have never ran a logcat, but I think I did it correctly.
stogchris81, yes I have apps on SD.
I/ActivityManager( 61): Starting activity: Intent { action=android.intent.acti
on.MAIN categories={android.intent.category.LAUNCHER} data=#Intent;action=#Inten
t;action=#Intent;action=#Intent;action= flags=0x10000000 comp={com.android.brows
er/com.android.browser.BrowserActivity} }
I/ActivityManager( 61): Start proc com.android.browser for activity com.androi
d.browser/.BrowserActivity: pid=887 uid=10026 gids={3003}
D/dalvikvm( 61): GC freed 8835 objects / 452416 bytes in 242ms
I/ActivityThread( 887): Publishing provider browser: com.android.browser.Browse
rProvider
I/ActivityManager( 61): Displayed activity com.android.browser/.BrowserActivit
y: 1561 ms
E/Database( 887): Failure 14 (unable to open database file) on 0x19e9b8 when ex
ecuting 'BEGIN EXCLUSIVE;'
W/dalvikvm( 887): threadid=19: thread exiting with uncaught exception (group=0x
4000fe70)
E/AndroidRuntime( 887): Uncaught handler: thread WebViewCoreThread exiting due
to uncaught exception
E/AndroidRuntime( 887): android.database.sqlite.SQLiteException: unable to open
database file: BEGIN EXCLUSIVE;
E/AndroidRuntime( 887): at android.database.sqlite.SQLiteDatabase.native
_execSQL(Native Method)
E/AndroidRuntime( 887): at android.database.sqlite.SQLiteDatabase.execSQ
L(SQLiteDatabase.java:1496)
E/AndroidRuntime( 887): at android.database.sqlite.SQLiteDatabase.beginT
ransaction(SQLiteDatabase.java:413)
E/AndroidRuntime( 887): at android.webkit.WebViewDatabase.startCacheTran
saction(WebViewDatabase.java:510)
E/AndroidRuntime( 887): at android.webkit.CacheManager.enableTransaction
(CacheManager.java:231)
E/AndroidRuntime( 887): at android.webkit.WebViewCore$EventHub$1.handleM
essage(WebViewCore.java:776)
E/AndroidRuntime( 887): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 887): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 887): at android.webkit.WebViewCore$WebCoreThread.run(
WebViewCore.java:462)
E/AndroidRuntime( 887): at java.lang.Thread.run(Thread.java:1058)
I/Process ( 61): Sending signal. PID: 887 SIG: 3
I/dalvikvm( 887): threadid=7: reacting to signal 3
I/dalvikvm( 887): Wrote stack trace to '/data/anr/traces.txt'
I/DumpStateReceiver( 61): Added state dump to 1 crashes
D/dalvikvm( 426): GC freed 391 objects / 21904 bytes in 167ms
seems like your database file for the browser is corrupted. did you put your /data/data on sd? you should be able to delete it and reboot it should recreate. it should be in /data/data/com.android.browser. try to rename it first just in case... you will lose all your bookmarks though... but I think it's already corrupted so you probably lost it already.
adb shell mv /data/data/com.android.browser /data/data/com.android.browser.OLD
adb shell mkdir /data/data/com.android.browser
adb shell reboot
Ran the first line and got this:
failed on '/data/data/com/android.browser' - No such file or directory
you didn't copy the line correctly.
Well that would make things a little difficult wouldn't it.
Everything seems to be back in working order. Lost all my bookmarks and everything, but at least it's working!
Thank you very VERY much! I really do appreciate it. Is there anything else I need to do now? Now that I have the com.android.browser.old?
if things are working and you don't mind losing those bookmarks you can remove the .old. just do
adb shell rm -r /data/data/com.android.browser.OLD
I don't see any reason not to do it. The bookmarks are toast right? I can't recover them at all?
probably, if you really want to try to recover you can try to recover them. But its complicated, I haven't tried so I can't give you any instructions how you.
Cool, I'll just remove them. Thanks again!
did you happen to try going into application manager and clearing the browser data? i get this issue a lot, and thats real easy to do. you lose your bookmarks, but i regularly back them up with apps that you can get from the market.
That would have been a good thing to try as well. I didn't think of that.
Browser problem
Guys, I have a bit of a strange problem.. i am using JF1.5 but my browser is not working... by that i mean it opens without a problem and shows the homepage ( www.google.com ) in a second but when i open anyother address it just says " web page not available- check your internet connection " but the strange thing is that when i open a link there is no network activity as if the browser aint even trying to connect to the network ....
Now i have installed opera mini and thats working just fine .... i.e opens every page quickly ....
Any Idea whats the problem ?
Thanks
I'm running Stock 4.1.2 with busybox installed, root, and XposedFramework.
Last night my device froze so I had to hard-reboot it. I turned it off then turned it on, it was late so I went to bed. I woke up in the morning went to pick it up and it was still on the boot screen. It was hot and after booting into recovery it said that I had only 15% battery left. I was dumbfounded. I tried to boot again, and it got stuck again. After all the trouble shooting I could think of(Including disabling and removing Xposed), I wiped my /system partition and flashed the Stock /system image. Sadly that didn't help. It seems the problem resides on my /data partition somewhere but obviously if I'm wiping that I might as well start from scratch.
Below is my Logcat. If you can gleam anything from it please let me know. I'm pretty-tech savvy but I still have zero expirience reading Logcats. At the very least I'd like to know what the error is exactly so I can endevor to avoid it in the future.
japzone said:
I'm running Stock 4.1.2 with busybox installed, root, and XposedFramework.
Last night my device froze so I had to hard-reboot it. I turned it off then turned it on, it was late so I went to bed. I woke up in the morning went to pick it up and it was still on the boot screen. It was hot and after booting into recovery it said that I had only 15% battery left. I was dumbfounded. I tried to boot again, and it got stuck again. After all the trouble shooting I could think of(Including disabling and removing Xposed), I wiped my /system partition and flashed the Stock /system image. Sadly that didn't help. It seems the problem resides on my /data partition somewhere but obviously if I'm wiping that I might as well start from scratch.
Below is my Logcat. If you can gleam anything from it please let me know. I'm pretty-tech savvy but I still have zero expirience reading Logcats. At the very least I'd like to know what the error is exactly so I can endevor to avoid it in the future.
Click to expand...
Click to collapse
Hi there ! This seems to be the problem in your case :
Code:
Sending signal. PID: 349 SIG: 9
E/AndroidRuntime( 349): *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
E/AndroidRuntime( 349): java.lang.ArrayIndexOutOfBoundsException: src.length=8192 srcPos=1 dst.length=8192 dstPos=0 length=-1
E/AndroidRuntime( 349): at java.lang.System.arraycopy(Native Method)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.fillBuffer(KXmlParser.java:1489)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.skip(KXmlParser.java:1574)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.parseStartTag(KXmlParser.java:1049)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:369)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:310)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFLOCK(UsageStatsService.java:376)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFromFile(UsageStatsService.java:357)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.<init>(UsageStatsService.java:274)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:1534)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:160)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1405)
E/AndroidRuntime( 349): Error reporting crash
E/AndroidRuntime( 349): java.lang.NullPointerException
E/AndroidRuntime( 349): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
As you can see the lines start with E:/ which stand for error .
V stands for Verbose
I for information
D for Debug.
And some others . more about these.. I suggest you Google. Now you will ask how I found out the error ? Well if you take a closer look to the log you will notice that once the kernel is initialized ( which happens at the Google logo ) the netd framework starts booting by the kernel.
Normal boot sequence is kernel > its init.rd and init.rc then the init.d and then the framework. How I came to know all this ? Take a log of a normally booting ROM
If you again carefully observe the log .. You will notice log re iterates. It goes on an infinite loop. Hence the term boot'loop'.
The start of the loop is
Code:
AndroidRuntime( 369): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 369): CheckJNI is OFF
And this Is the dead / bad code
Code:
ygote ( 369): Exit zygote because system server (508) has terminated
I/ServiceManager( 118): service 'sensorservice' died
I/ServiceManager( 118): service 'entropy' died
I/ServiceManager( 118): service 'power' died
That's roughly how you read a logcat.
And about your problem. I suggest a clean wipe and reflash the ROM. Its always better to keep backing up your data from time to time. I also ensure I wipe clean even during flashing nightlies .
Sent from my HTC using xda app-developers app
Thanks for the reply. Nice crash course on log reading I have gone ahead and flashed a fresh install of PA ROM.
I really just wonder how the error might of happened. It occured at a bad time for me where my External Harddrive died on me taking my backups with it, and leaving me with nowhere to put new ones. My new Laptop with a 1TB drive is coming in August so I was planning on backing up and Flashing a Custom ROM then. But this error took out my device before I could make a backup. Oh well, I managed to scavenge most of my apps and hopefully will be able to restore them. Sadly I lost a day off to resuscitating my Nexus
Red Devil said:
Hi there ! This seems to be the problem in your case :
Code:
Sending signal. PID: 349 SIG: 9
E/AndroidRuntime( 349): *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
E/AndroidRuntime( 349): java.lang.ArrayIndexOutOfBoundsException: src.length=8192 srcPos=1 dst.length=8192 dstPos=0 length=-1
E/AndroidRuntime( 349): at java.lang.System.arraycopy(Native Method)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.fillBuffer(KXmlParser.java:1489)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.skip(KXmlParser.java:1574)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.parseStartTag(KXmlParser.java:1049)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:369)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:310)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFLOCK(UsageStatsService.java:376)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFromFile(UsageStatsService.java:357)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.<init>(UsageStatsService.java:274)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:1534)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:160)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1405)
E/AndroidRuntime( 349): Error reporting crash
E/AndroidRuntime( 349): java.lang.NullPointerException
E/AndroidRuntime( 349): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
As you can see the lines start with E:/ which stand for error .
V stands for Verbose
I for information
D for Debug.
And some others . more about these.. I suggest you Google. Now you will ask how I found out the error ? Well if you take a closer look to the log you will notice that once the kernel is initialized ( which happens at the Google logo ) the netd framework starts booting by the kernel.
Normal boot sequence is kernel > its init.rd and init.rc then the init.d and then the framework. How I came to know all this ? Take a log of a normally booting ROM
If you again carefully observe the log .. You will notice log re iterates. It goes on an infinite loop. Hence the term boot'loop'.
The start of the loop is
Code:
AndroidRuntime( 369): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 369): CheckJNI is OFF
And this Is the dead / bad code
Code:
ygote ( 369): Exit zygote because system server (508) has terminated
I/ServiceManager( 118): service 'sensorservice' died
I/ServiceManager( 118): service 'entropy' died
I/ServiceManager( 118): service 'power' died
That's roughly how you read a logcat.
And about your problem. I suggest a clean wipe and reflash the ROM. Its always better to keep backing up your data from time to time. I also ensure I wipe clean even during flashing nightlies .
Sent from my HTC using xda app-developers app
Click to expand...
Click to collapse
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.
I want to cherry-pick "custom notification led settings" from purity to my aosp build.
So I went ahead and picked up these two commits
https://github.com/KitKatPurity/pla...mmit/c85834ed460ec99e0752f1f13e58cad74abf844e
and
https://github.com/KitKatPurity/pla...mmit/b37fdf4238b11b0232b12f218294131ea77ec309
The framework part ran well and there was no conflict. The settings part returned a small conflict which I solved myself. Now as I go on compiling, everything compiled good but then at the time of Settings.apk compiling it returned this error.
Code:
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:119: cannot find symbol
symbol : variable mDisplayManager
location: class com.android.settings.DisplaySettings
mDisplayManager = (DisplayManager)getActivity().getSystemService(
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:119: cannot find symbol
symbol : class DisplayManager
location: class com.android.settings.DisplaySettings
mDisplayManager = (DisplayManager)getActivity().getSystemService(
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:121: cannot find symbol
symbol : variable mWifiDisplayStatus
location: class com.android.settings.DisplaySettings
mWifiDisplayStatus = mDisplayManager.getWifiDisplayStatus();
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:121: cannot find symbol
symbol : variable mDisplayManager
location: class com.android.settings.DisplaySettings
mWifiDisplayStatus = mDisplayManager.getWifiDisplayStatus();
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:122: cannot find symbol
symbol : variable mWifiDisplayPreference
location: class com.android.settings.DisplaySettings
mWifiDisplayPreference = (Preference)findPreference(KEY_WIFI_DISPLAY);
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:122: cannot find symbol
symbol : variable KEY_WIFI_DISPLAY
location: class com.android.settings.DisplaySettings
mWifiDisplayPreference = (Preference)findPreference(KEY_WIFI_DISPLAY);
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:123: cannot find symbol
symbol : variable mWifiDisplayStatus
location: class com.android.settings.DisplaySettings
if (mWifiDisplayStatus.getFeatureState()
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:124: cannot find symbol
symbol : variable WifiDisplayStatus
location: class com.android.settings.DisplaySettings
== WifiDisplayStatus.FEATURE_STATE_UNAVAILABLE) {
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:125: cannot find symbol
symbol : variable mWifiDisplayPreference
location: class com.android.settings.DisplaySettings
getPreferenceScreen().removePreference(mWifiDisplayPreference);
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:126: cannot find symbol
symbol : variable mWifiDisplayPreference
location: class com.android.settings.DisplaySettings
mWifiDisplayPreference = null;
^
packages/apps/Settings/src/com/android/settings/purity/notificationlight/ApplicationLightPreference.java:170: method does not override or implement a method from a supertype
@Override
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
11 errors
make: *** [out/target/common/obj/APPS/Settings_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
Here are the link of the 2 files where the error is shown:
ApplicationLightPreference.java
DisplaySettings.java
I tried the following combination to solve it:
in ApplicationLightPreference.java, I deleted the line which returned the error.
in DisplaySettings.java I deleted the line which returned the error.
The build compiles fine, boot fines but but when I select display settings, it force closes.
Any help in solving this error is appreciated.
Since this is a question why not post in the section clearly marked for questions??
Sent from my Nexus 4 using xda premium
brajesh.sharma87 said:
I tried the following combination to solve it:
in ApplicationLightPreference.java, I deleted the line which returned the error.
in DisplaySettings.java I deleted the line which returned the error.
The build compiles fine, boot fines but but when I select display settings, it force closes.
Any help in solving this error is appreciated.
Click to expand...
Click to collapse
Find the commit that added the missing variable(s) and method(s)
pull a log for the force close.
MBQ_ said:
Find the commit that added the missing variable(s) and method(s)
pull a log for the force close.
Click to expand...
Click to collapse
Not sure what to do about the first line but here's the log
Code:
I/ActivityManager( 647): Displayed com.android.settings/.Settings: +631ms
I/ActivityManager( 647): START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from pid 9823
D/audio_hw_primary( 170): select_devices: out_snd_device(2: speaker) in_snd_device(0: )
D/ACDB-LOADER( 170): ACDB -> send_afe_cal
D/SubSettings( 9823): Launching fragment com.android.settings.DisplaySettings
D/AndroidRuntime( 9823): Shutting down VM
W/dalvikvm( 9823): threadid=1: thread exiting with uncaught exception (group=0x415adba8)
E/AndroidRuntime( 9823): FATAL EXCEPTION: main
E/AndroidRuntime( 9823): Process: com.android.settings, PID: 9823
E/AndroidRuntime( 9823): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException
E/AndroidRuntime( 9823): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2195)
E/AndroidRuntime( 9823): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2245)
E/AndroidRuntime( 9823): at android.app.ActivityThread.access$800(ActivityThread.java:135)
E/AndroidRuntime( 9823): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1196)
E/AndroidRuntime( 9823): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 9823): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 9823): at android.app.ActivityThread.main(ActivityThread.java:5017)
E/AndroidRuntime( 9823): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 9823): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 9823): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
E/AndroidRuntime( 9823): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
E/AndroidRuntime( 9823): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 9823): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 9823): at com.android.settings.DisplaySettings.onCreate(DisplaySettings.java:134)
E/AndroidRuntime( 9823): at android.app.Fragment.performCreate(Fragment.java:1678)
E/AndroidRuntime( 9823): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:859)
E/AndroidRuntime( 9823): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1062)
E/AndroidRuntime( 9823): at android.app.BackStackRecord.run(BackStackRecord.java:684)
E/AndroidRuntime( 9823): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1447)
E/AndroidRuntime( 9823): at android.app.Activity.performStart(Activity.java:5240)
E/AndroidRuntime( 9823): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2168)
E/AndroidRuntime( 9823): ... 11 more
W/ActivityManager( 647): Force finishing activity com.android.settings/.SubSettings
W/ActivityManager( 647): Force finishing activity com.android.settings/.Settings
W/ActivityManager( 647): Activity pause timeout for ActivityRecord{41e72210 u0 com.android.settings/.SubSettings t14 f}
W/Sidekick_LocationOracleImpl( 2543): Best location was null
I/Process ( 9823): Sending signal. PID: 9823 SIG: 9
V/SearchControllerCache( 2543): creating SearchController
W/Sidekick_LocationOracleImpl( 2543): Best location was null
W/GCoreFlp( 8127): No location to return for getLastLocation()
I/ActivityManager( 647): Process com.android.settings (pid 9823) has died.
I/WindowState( 647): WIN DEATH: Window{419b9318 u0 com.android.settings/com.android.settings.Settings}
D/dalvikvm( 2543): GC_FOR_ALLOC freed 1110K, 57% free 5133K/11704K, paused 27ms, total 27ms
I/MicroHotwordRecognitionRunner( 2543): Starting hotword detection.
D/audio_hw_primary( 170): select_devices: out_snd_device(0: ) in_snd_device(34: voice-rec-mic)
E/ACDB-LOADER( 170): Error: ACDB AudProc vol returned = -8
D/dalvikvm( 2543): GC_CONCURRENT freed 6K, 51% free 5756K/11704K, paused 2ms+3ms, total 32ms
I/SearchController( 2543): #onHotwordDetectorStarted
brajesh.sharma87 said:
Not sure what to do about the first line but here's the log
Click to expand...
Click to collapse
Something is wrong in the onCreate method of DisplaySettings.java
Hi, I checked and you miss the declaration in the Android Manifest in the packages_apps_settings. Go and check my Github commits. You do not need the modifcation in the proguard.flags though.
https://github.com/GeyerA/platform_...mmit/347e74714f0c6efa2dbd3ba49b5612e1cc11bf4f
For completeness also check the commits in the frameworks_base
https://github.com/GeyerA/platform_frameworks_base/commit/a77810164cb1bcb1d449f603f31a97939d9f9b3b
Also, make sure you got these...
https://github.com/PSX-PureSpeed/an...mmit/3e29b10a377f0985ee221aaa4fe10838733ed3df
https://github.com/PSX-PureSpeed/an...mmit/2ae7fbb6134f6831fba8184d0dd1092f5bee1f7a
This should fix your issues, just let me know or PM me as I am not always checking on your thread.
Nice week to everbody. Calo
GeyerA said:
Hi, I checked and you miss the declaration in the Android Manifest in the packages_apps_settings. Go and check my Github commits. You do not need the modifcation in the proguard.flags though.
https://github.com/GeyerA/platform_...mmit/347e74714f0c6efa2dbd3ba49b5612e1cc11bf4f
For completeness also check the commits in the frameworks_base
https://github.com/GeyerA/platform_frameworks_base/commit/a77810164cb1bcb1d449f603f31a97939d9f9b3b
Also, make sure you got these...
https://github.com/PSX-PureSpeed/an...mmit/3e29b10a377f0985ee221aaa4fe10838733ed3df
https://github.com/PSX-PureSpeed/an...mmit/2ae7fbb6134f6831fba8184d0dd1092f5bee1f7a
This should fix your issues, just let me know or PM me as I am not always checking on your thread.
Nice week to everbody. Calo
Click to expand...
Click to collapse
Thanks for the answer. I discarded all the commits which I took from purity.
Started fresh and picked up the commits from your github. There was 1 conflict in DisplaySettings.java, I solved it and compiled. It then gave me error during compile about volume wake. I deleted those lines in question and compiled again. It compiled fine but after installing the output rom I still got FC when clicking on "Display Settings".
I didn't give up. I discarded all the previous commits again and this time picked up the volume wake commits first and then the LED customization commits and then from PSX commits which you advised. Everything ran well, there was not a single conflict this time. Even there was no error at the time of compilation. BUT as always on installing the rom I got the same FC on clicking Display settings.
Now I have deleted the entire out directory and this time will build fresh lets see if that can help, but for that I can only do it after 8-10 days as I am going out of station.
Thanks for all the help.
brajesh.sharma87 said:
Thanks for the answer. I discarded all the commits which I took from purity.
Started fresh and picked up the commits from your github. There was 1 conflict in DisplaySettings.java, I solved it and compiled. It then gave me error during compile about volume wake. I deleted those lines in question and compiled again. It compiled fine but after installing the output rom I still got FC when clicking on "Display Settings".
I didn't give up. I discarded all the previous commits again and this time picked up the volume wake commits first and then the LED customization commits and then from PSX commits which you advised. Everything ran well, there was not a single conflict this time. Even there was no error at the time of compilation. BUT as always on installing the rom I got the same FC on clicking Display settings.
Now I have deleted the entire out directory and this time will build fresh lets see if that can help, but for that I can only do it after 8-10 days as I am going out of station.
Thanks for all the help.
Click to expand...
Click to collapse
Hello, good that you have some progress although you might feel disappointed that it does not work. Here is one reason why I personally do not cherry-pick complex commits as it will also add the lines which are not part of that commit but part of my code.
Anyhow, I believe you missed one small thing which is in android_device_hammerhead. Sorry I forgot that one.
https://github.com/KitKatPurity/pla...mmit/217378d3e6a7a5370e7c1583fcfb4ae1e7a9ac7c
Especially this one in overlay/frameworks/base/core/res/res/values/config.xml
Code:
+ <!-- Is the battery LED intrusive? Used to decide if there should be a disable option -->
+ <bool name="config_intrusiveBatteryLed">true</bool>
+
+ <!-- Does the battery LED support multiple colors? Used to decide if the user can change the colors -->
+ <bool name="config_multiColorBatteryLed">true</bool>
+
I am sure it will work then. Please do not delete everything again when something does not work, post the question first :silly:
GeyerA said:
........I am sure it will work then. Please do not delete everything again when something does not work, post the question first :silly:
Click to expand...
Click to collapse
Thanks but as i said, i wont have access to my laptop for next 8-10 days, will continue once i come back.
Sent from my Nexus 4 using Tapatalk
@GeyerA you're a genius. I've been working on this for last 1 month and finally succeeded.
As I didnt have access to my laptop and the resolution that u you gave was also possible through apk tool, I sent the framework-res.apk to a friend and asked him to just change those two values to 'true' he did so and sent the same to me and boom it worked. Thank you so very much.
Sent from my Nexus 4 using Tapatalk
Hello. I am happy to hear; great satisfaction that I could help. But the credit is Dario's from Kitkatpurity and Martin_Ro's from PSX. They helped me a lot and I suffered much more than you. No biggie but please use the thanks button ....
Sent from my AOSP on HammerHead using xda app-developers app
I'm getting a weird error using the Aviary SDK for some users who are using ART. I'm confused on why this happening (only on 4.4.x obviously) as the app works perfectly when calling this SDK on Dalvik. Any one have any have any ideas to solve this? Aviary claims it's PhoneGap/Cordova issue (our base), but I don't think that's the issue here as it only fires when the activity is launched.
HTML:
06-06 09:45:36.037: D/Aviary(27701): Pictures folder: /storage/emulated/0/Pictures
06-06 09:45:36.037: D/Aviary(27701): show
06-06 09:45:36.037: D/Aviary(27701): VERSION => 3.0.4
06-06 09:45:36.037: D/Aviary(27701): VERSION => 157
06-06 09:45:36.041: I/ActivityManager(741): START u0 {dat=file:///storage/emulated/0/DCIM/Camera/1402062335694.jpg cmp=com.XXXX.app/com.aviary.android.feather.FeatherActivity (has extras)} from pid 27701
06-06 09:45:36.054: W/CursorWrapperInner(27701): Cursor finalized without prior close()
06-06 09:45:36.058: I/CordovaLog(27701): Changing log level to ERROR(6)
06-06 09:45:36.087: I/ActivityManager(741): Start proc com.XXXX.app:standalone for activity com.XXXX.app/com.aviary.android.feather.FeatherActivity: pid=28285 uid=10060 gids={50060, 3003, 1028, 1015}
06-06 16:20:12.473 W/art (188): Could not get current activity
......
06-06 09:45:36.320: E/art(28285): Verification failed on class com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler in /data/app/com.XXXXXXX.apk because: Verifier rejected class com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler due to bad method void com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler.deleteBlobsAndSessions(com.aviary.android.feather.library.external.tracking.LocalyticsProvider)
06-06 09:45:36.320: E/AndroidRuntime(28285): FATAL EXCEPTION: SessionHandler
06-06 09:45:36.320: E/AndroidRuntime(28285): Process: com.XXXXX.app:standalone, PID: 28285
06-06 09:45:36.320: E/AndroidRuntime(28285): java.lang.VerifyError: Verifier rejected class com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler due to bad method void com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler.deleteBlobsAndSessions(com.aviary.android.feather.library.external.tracking.LocalyticsProvider) (declaration of 'com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler' appears in /data/app/com.XXXXXXX.apk)
06-06 09:45:36.320: E/AndroidRuntime(28285): at com.aviary.android.feather.library.external.tracking.LocalyticsSession$SessionHandler.init(LocalyticsSession.java:1427)
06-06 09:45:36.320: E/AndroidRuntime(28285): at com.aviary.android.feather.library.external.tracking.LocalyticsSession$SessionHandler.handleMessage(LocalyticsSession.java:1124)
06-06 09:45:36.320: E/AndroidRuntime(28285): at android.os.Handler.dispatchMessage(Handler.java:102)
06-06 09:45:36.320: E/AndroidRuntime(28285): at android.os.Looper.loop(Looper.java:136)
06-06 09:45:36.320: E/AndroidRuntime(28285): at android.os.HandlerThread.run(HandlerThread.java:61)
06-06 09:45:36.320: W/ActivityManager(741): Force finishing activity com.XXXXXX.app/com.aviary.android.feather.FeatherActivity