Sorry if this has already been posted but I don't see a thread or anything about it yet.
Has anyone figured out how to get the normal Android TV launcher to work on the new Chromecast with GoogleTV? I like the device for our bedroom but I really dislike the interface how it shoves everything in front of you. I just want a plain simple interface like my ShieldTVs have if at all possible.
I've tried some ADB commands on other sites but no luck.
Just wondering if there's an actual way to make this happen or not.
Thank you.
BBalz said:
Sorry if this has already been posted but I don't see a thread or anything about it yet.
Has anyone figured out how to get the normal Android TV launcher to work on the new Chromecast with GoogleTV? I like the device for our bedroom but I really dislike the interface how it shoves everything in front of you. I just want a plain simple interface like my ShieldTVs have if at all possible.
I've tried some ADB commands on other sites but no luck.
Just wondering if there's an actual way to make this happen or not.
Thank you.
Click to expand...
Click to collapse
I used button remaper to just go to the launcher that I want
You can turn the "suggested" content off (well, 90% of it) through the menu. I think it's under your user account settings. It does leave a nag label on the screen saying how you are limiting "your experience". It slims the main page down to a row of your installed apps on the launcher, but does leave a background of suggested content.
Thanks for the suggestion for the key remap, I'll have to try that. Is there any lag or page flipping with the key remap? What app are you using?
BBalz said:
Sorry if this has already been posted but I don't see a thread or anything about it yet.
Has anyone figured out how to get the normal Android TV launcher to work on the new Chromecast with GoogleTV? I like the device for our bedroom but I really dislike the interface how it shoves everything in front of you. I just want a plain simple interface like my ShieldTVs have if at all possible.
I've tried some ADB commands on other sites but no luck.
Just wondering if there's an actual way to make this happen or not.
Thank you.
Click to expand...
Click to collapse
What exactly do you mean by "I've tried some ADB commands on other sites"? What did you try? Where did you find these things to try?
WestonWW said:
You can turn the "suggested" content off (well, 90% of it) through the menu. I think it's under your user account settings. It does leave a nag label on the screen saying how you are limiting "your experience". It slims the main page down to a row of your installed apps on the launcher, but does leave a background of suggested content.
Thanks for the suggestion for the key remap, I'll have to try that. Is there any lag or page flipping with the key remap? What app are you using?
Click to expand...
Click to collapse
The problem is that the Apps only mode disables google assistant and the access to the play store. I'm about to open a new thread to get the device de-bloated. Hopefully others can chime in and we can get it done
Anybody want to try a quick and easy experiment? (note that I haven't had the opportunity to try this yet)
Run under ADB:
$ setprop persist.debug.user.package_whitelist_mode 0
Then reboot.
See if the much preferred android tv launcher decides to work.
Here's the reference for it;
services/core/java/com/android/server/pm/UserSystemPackageInstaller.java - platform/frameworks/base - Git at Google
96carboard said:
Anybody want to try a quick and easy experiment? (note that I haven't had the opportunity to try this yet)
Run under ADB:
$ setprop persist.debug.user.package_whitelist_mode 0
Then reboot.
See if the much preferred android tv launcher decides to work.
Here's the reference for it;
services/core/java/com/android/server/pm/UserSystemPackageInstaller.java - platform/frameworks/base - Git at Google
Click to expand...
Click to collapse
sabrina:/ $ setprop persist.debug.user.package_whitelist_mode 0
setprop persist.debug.user.package_whitelist_mode 0
setprop: failed to set property 'persist.debug.user.package_whitelist_mode' to '0'
I get the above error when I tried that.
Anything else to try ?
I did try and install com.google.android.tvlauncher and com.google.android.tvrecommendations from an official Android TV 10 device but when i disable the stock launcher and select "Android TV Home", I just get a blank screen.
Damn. Thanks for trying it. Apparently you need to have greater privileges for that to work. If there were some way to achieve elevated privileges, even temporarily, or otherwise access the USERDATA filesystem, the property could be set and would remain set (since its a "persist" property).
If anybody's got any idea to get a temporary root or boot the thing on external media...?
Really interested in this -- if anybody has any other idea...
Alexandre-P said:
Really interested in this -- if anybody has any other idea...
Click to expand...
Click to collapse
My next idea would be to modify the apk with a different package name.
I tried the same steps as @Intenti0n described - installing com.google.android.tvlauncher and com.google.android.tvrecommendations and disabling the default launcher. I also get a black screen.
When looking at logcat output you can see that the TV Launcher is starting but it crashes immediately, because it does not have the right permissions:
Code:
12-14 18:22:33.832 3527 3555 I ActivityManager: Start proc 19573:com.google.android.tvlauncher/u0a21 for activity {com.google.android.tvlauncher/com.google.android.tvlauncher.MainActivity}
12-14 18:22:34.129 19573 19661 E AndroidRuntime: FATAL EXCEPTION: pool-2-thread-1
12-14 18:22:34.129 19573 19661 E AndroidRuntime: Process: com.google.android.tvlauncher, PID: 19573
12-14 18:22:34.129 19573 19661 E AndroidRuntime: java.lang.RuntimeException: An error occurred while executing ContentResolver query
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at drg.run(PG:4)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: Caused by: java.lang.SecurityException: Selection not allowed for content://android.media.tv/watch_next_program
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:2071)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2039)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:188)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:140)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at android.content.ContentProviderProxy.query(ContentProviderNative.java:423)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at android.content.ContentResolver.query(ContentResolver.java:944)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at android.content.ContentResolver.query(ContentResolver.java:880)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at android.content.ContentResolver.query(ContentResolver.java:836)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: at drg.run(PG:2)
12-14 18:22:34.129 19573 19661 E AndroidRuntime: ... 3 more
12-14 18:22:34.150 19603 19603 D AndroidRuntime: Shutting down VM
12-14 18:22:34.151 19603 19603 E AndroidRuntime: FATAL EXCEPTION: main
12-14 18:22:33.923 3527 3555 I ActivityManager: Start proc 19603:com.google.android.tvrecommendations/u0a40 for broadcast {com.google.android.tvrecommendations/com.google.android.tvrecommendations.account.TvLauncherAccountReceiver}
12-14 18:22:34.151 19603 19603 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.google.android.tvrecommendations.application.TvRecommendationsApplication: java.lang.SecurityException: Missing permission to control media.
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6465)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.app.ActivityThread.access$1300(ActivityThread.java:219)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1859)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7356)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: Caused by: java.lang.SecurityException: Missing permission to control media.
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:2071)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2039)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1987)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.media.session.ISessionManager$Stub$Proxy.addSessionsListener(ISessionManager.java:816)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.media.session.MediaSessionManager.addOnActiveSessionsChangedListener(MediaSessionManager.java:315)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.media.session.MediaSessionManager.addOnActiveSessionsChangedListener(MediaSessionManager.java:278)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.media.session.MediaSessionManager.addOnActiveSessionsChangedListener(MediaSessionManager.java:257)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at com.google.android.tvrecommendations.application.TvRecommendationsApplication.onCreate(PG:75)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1189)
12-14 18:22:34.151 19603 19603 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6460)
It seems to me that those two apps will only work if they are included as system apps (and thus have system level permissions).
I also tried using adb to grant the permissions manually, but this did not work:
Code:
1|sabrina:/ $ pm grant com.google.android.tvrecommendations android.permission.MEDIA_CONTENT_CONTROL
Security exception: Permission android.permission.MEDIA_CONTENT_CONTROL requested by com.google.android.tvrecommendations is not a changeable permission type
com.google.android.tvlauncher would need the com.android.providers.tv.permission.ACCESS_ALL_EPG_DATA permission to read the Channel data from the com.android.providers.tv provider.
To quote the docs:
Only signatureOrSystem apps can acquire ACCESS_ALL_EPG_DATA permission to access the entire database.
signatureOrSystem = A permission that the system grants only to applications that are in a dedicated folder on the Android system image or that are signed with the same certificate as the application that declared the permission.
As com.google.android.tvlauncher and com.android.providers.tv are signed by two different Google certificates (Serial number 8e02e4498c0a21a8d995f16a28dadd6d53879a27 and fe270bc94d9c0c984c7e3a2f825b6a80055da82c respectively) the TV launcher would only work it it was located in /system/priv-app/ which is not possible without root.
That's some fantastic analysis lfrst05
So it looks like unless we can write to system/priv-app , we would not be able to use the leanback launcher.
Thing is, we are able to use a custom launcher, so what if we copy stock launcher, rename the package and then just select that as a launcher to use?
Custom launcher and stock Android TV launcher are two different things.
To start a launcher, the system looks for an app that can handle the "android.intent.category.HOME" intent (at least on phones, I think it is the same on TV).
On the CCGTV it seems this process has a hardcoded condition in there "if com.google.android.apps.tv.launcherx is enabled, ignore any other launcher" (this might be controlled by the persist.debug.user.package_whitelist_mode property mentioned above). However, if the original launcher is disabled, the normal rules apply and you can use any launcher.
The stock Android TV launcher com.google.android.tvlauncher adheres to the same rules. The system starts it, if it is the only launcher available (or if you select it in the list when prompted). The problem is that it immediately crashes because it expects to have system level permissions (to access all data in the TV/channels content provider). This causes the black screen.
Renaming the package will not solve anything. You would still need Google's private keys to sign the package for the system to accept it as an update for the stock launcher.
The only way I see to solve this would be rooting the device and installing the com.google.android.tvlauncher in the system partition. (but with rooting you most likely loose access to DRM content like Netflix) But I am not 100% sure on all of that. There might be some other way around all of that.
lfrst05 said:
Renaming the package will not solve anything. You would still need Google's private keys to sign the package for the system to accept it as an update for the stock launcher.
Click to expand...
Click to collapse
Not necessarily, but it may be more involved than renaming since, as you've mentioned, its looking for permissions that aren't available. 3rd party launchers don't need to be signed by goog, therefore neither does the atv launcher, AS LONG AS it is stripped of everything that depends on the signature, which CAN be done, but may be more work than its worth.
Its disappointing that goog hasn't provided an open source launcher for atv as they have for phone/tablet and car. I guess because they really really really want to ram advertising down everyone's throat.
Perhaps this issue with the new CCGTV will be enough of a catalyst for a few of us to contribute to such an objective?
This is the ONLY open sourced atv launcher I've been able to find, and it hasn't been updated in 7 years; https://github.com/rharter/Android-TV-Launcher
Any notion of HOW to achieve root? I couldn't care less about DRM trash.
I got rid of the stock launcher and is using Wolf Launcher as described by TechdoctorUK
Use Custom Launcher on Chromecast With Google TV
Atmosphere said:
I got rid of the stock launcher and is using Wolf Launcher as described by TechdoctorUK
Use Custom Launcher on Chromecast With Google TV
Click to expand...
Click to collapse
I followed those steps too but I'm seeing online that the Wolf Launcher isn't legit. Did you happen to see that?
It's just another launcher. You can easily disable it and go back to the stock launcher
Atmosphere said:
It's just another launcher. You can easily disable it and go back to the stock launcher
Click to expand...
Click to collapse
I understand that but was just curious how the community felt about the launcher. It looks very similar to another one in the play store.
MrTeeRocks said:
I understand that but was just curious how the community felt about the launcher. It looks very similar to another one in the play store.
Click to expand...
Click to collapse
wolf launcher is just a modded ATV launcher. techdoctorUK is a very trustable source
Related
I am not sure why I am experiencing this problem. My phone was working fine last week, then I flashed xTHEME v1.2 on cm 4.0.4 and my phone gets stuck at the 2nd bootscreen. I wiped, then flashed 4.0.4 again and I can boot normally, but then it happened again today. Logcat below, hopefully someone can explain the error.
http://pastebin.com/f362fbdc3
Lemme know if you need more information
Code:
E/AndroidRuntime( 4678): Uncaught handler: thread android.server.ServerThread exiting due to uncaught exception
E/AndroidRuntime( 4678): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 4678): java.lang.IndexOutOfBoundsException: Invalid location 1, size is 1
E/AndroidRuntime( 4678): at java.util.ArrayList.get(ArrayList.java:353)
E/AndroidRuntime( 4678): at com.android.server.AppWidgetService.readStateFromFileLocked(AppWidgetService.java:972)
E/AndroidRuntime( 4678): at com.android.server.AppWidgetService.loadStateLocked(AppWidgetService.java:750)
E/AndroidRuntime( 4678): at com.android.server.AppWidgetService.systemReady(AppWidgetService.java:125)
E/AndroidRuntime( 4678): at com.android.server.ServerThread.run(SystemServer.java:346)
uncaught exception there right before everything crashes.... do you have any widgets installed?
The only widgets I use are Weather Widget - Donate + addon, GPS OnOff, and tCalendar.
unknown.soul said:
The only widgets I use are Weather Widget - Donate + addon, GPS OnOff, and tCalendar.
Click to expand...
Click to collapse
Try to disable them, boot up, reenable them one by one to see whats causing it to happen. I can't see anything else in the log that could be the cause of it, but im not an expert
tCalendar seemed to be the culprit and I found out that tCalendar != tCalendarWidget. The former is not for 1.5, but according to the market description it should be compatible. Thanks for isolating the issue from that log.
unknown.soul said:
tCalendar seemed to be the culprit and I found out that tCalendar != tCalendarWidget. The former is not for 1.5, but according to the market description it should be compatible. Thanks for isolating the issue from that log.
Click to expand...
Click to collapse
no problem, glad to see you got it to work. I thought that would be an app problem to cause trouble because I used the other two on cyans exp. builds. Hadn't heard of the tcalendar app.
Thanks for providing links to the app, it makes it much more useful for someone searching for an answer to find one. Also, could you edit the thread title to include [SOLVED] ?
btw it wasnt the tcalendar widget itself, but the tcalendar app? thats weird. does it have a widget of its own packaged with the app?
It's just a name difference, tCalendar is only a widget.
Anyone know what could be causing this? Appmanager Pro is crashing when I try to launch it. Only thigns on my phone are Cyan 4.25 and the navigation_update.zip.
Heres a logcat:
Code:
11-17 22:07:10.156 W/dalvikvm( 665): threadid=15: thread exiting with uncaught exception (group=0x4001e170)
11-17 22:07:10.156 E/AndroidRuntime( 665): Uncaught handler: thread Thread-9 exiting due to uncaught exception
11-17 22:07:10.166 E/AndroidRuntime( 665): java.lang.NullPointerException
11-17 22:07:10.166 E/AndroidRuntime( 665): at com.think_android.appmanagerpro.FileUtils.getDirSize(FileUtils.java:171)
11-17 22:07:10.166 E/AndroidRuntime( 665): at com.think_android.appmanagerpro.FileUtils.getDirSize(FileUtils.java:175)
11-17 22:07:10.166 E/AndroidRuntime( 665): at com.think_android.appmanagerpro.AppManagerPro$ResourceLoaderThread.run(AppManagerPro.java:449)
11-17 22:07:10.196 I/Process ( 143): Sending signal. PID: 665 SIG: 3
11-17 22:07:10.196 I/dalvikvm( 665): threadid=7: reacting to signal 3
11-17 22:07:10.326 I/dalvikvm( 665): Wrote stack trace to '/data/anr/traces.txt'
11-17 22:07:10.866 D/dalvikvm( 515): GC freed 528 objects / 294640 bytes in 128ms
11-17 22:07:12.036 I/Process ( 665): Sending signal. PID: 665 SIG: 9
11-17 22:07:12.066 I/ActivityManager( 143): Process com.think_android.appmanagerpro (pid 665) has died.
11-17 22:07:12.076 I/WindowManager( 143): WIN DEATH: Window{43938b48 com.think_android.appmanagerpro/com.think_android.appmanagerpro.AppManagerPro paused=false}
11-17 22:07:12.126 W/UsageStats( 143): Unexpected resume of com.android.launcher while already resumed in com.think_android.appmanagerpro
11-17 22:07:12.156 W/InputManagerService( 143): Got RemoteException sending setActive(false) notification to pid 665 uid 10038
11-17 22:07:14.886 I/XT9IME ( 351): [finishInput]
11-17 22:07:15.216 D/dalvikvm( 192): GC freed 2925 objects / 133408 bytes in 123ms
Has it been updated for 1.6? NullPointerException usually require looking through the code to troubleshoot lol. its probably not programmed well
B-man007 said:
Has it been updated for 1.6? NullPointerException usually require looking through the code to troubleshoot lol. its probably not programmed well
Click to expand...
Click to collapse
I'm thinking it has something to do with the update_navigation.zip I flashed cause I know it did something with the build.props and whatnot. And it also worked before I flashed this.
I don't use that but how much did it modify your build.prop?
does your phone say android 2.0 or is it still showing 1.6?
B-man007 said:
I don't use that but how much did it modify your build.prop?
does your phone say android 2.0 or is it still showing 1.6?
Click to expand...
Click to collapse
I believe it changed 1-2 lines and yes my phone still shows 1.6. I just looked at my app drawer to and it shows I have 2 settings apps, odd I'm going to restart my phone see if it goes away.
I hate to say this but it's not nav....
And I don't think it's CM4.2.5.
I know this because I was fine on a fresh install until I reinstalled all my other apps. Then I started getting crashes. I think it was a combination of advanced launcher,and google voice that started the misbehavior.
Maybe it's just one of them.
My solution was...
I dropped appmanager. I loved that program, but discovered that Astro can back-up your apk's too. It just doesn't uninstall existing apks.
But... advanced task manager does have an uninstall feature, and it allows me to slap mis-behaving programs around as well as services.
The simplicity of one program, replaced by the combination of 2 more powerful programs.
But hey, what do I care....I have Apps2sd!
[email protected] said:
I hate to say this but it's not nav....
And I don't think it's CM4.2.5.
I know this because I was fine on a fresh install until I reinstalled all my other apps. Then I started getting crashes. I think it was a combination of advanced launcher,and google voice that started the misbehavior.
Maybe it's just one of them.
My solution was...
I dropped appmanager. I loved that program, but discovered that Astro can back-up your apk's too. It just doesn't uninstall existing apks.
But... advanced task manager does have an uninstall feature, and it allows me to slap mis-behaving programs around as well as services.
The simplicity of one program, replaced by the combination of 2 more powerful programs.
But hey, what do I care....I have Apps2sd!
Click to expand...
Click to collapse
I sent a email to the dev with the situation and what not. but Google voice to me never interfered before with app manager. Hopefully I get it figured out soon cause appmanager made my life alot simpler ><, I am willing to try new things but if this gets repaired it would be greater!
i have all 3 google voice..nav..and app manager pro working.. just fine on mine..
Just to clarify...
I am almost certain it's not nav because I had stopped using app manager, before even thinking of adding nav to the system.
That didn't really come out in the first post.
http://code.google.com/p/cyanogenmod/issues/detail?id=744#c0
Issue with the latest mod
did you guys try reinstalling the app? maybe it requires additional permissions after the latest rom upgrade
B-man007 said:
http://code.google.com/p/cyanogenmod/issues/detail?id=744#c0
Issue with the latest mod
did you guys try reinstalling the app? maybe it requires additional permissions after the latest rom upgrade
Click to expand...
Click to collapse
Seems like im not the only one experiencing the issues though >< I guess I'll just try out astro
had the issue also and I had it before I decided to flash the update_navigation zip file so I know its not that... it was working then it stopped after something dont know what it is... didnt have a theme nothing completely fresh install wiped everything didn't have ext partition so its something weird
I got a hold of the dev and gave him a complete catlog. He released an update on the market and problem solved!
I just ran into an interesting problem and was able to solve it, I figured I'd post it here in case anyone else runs into it.
So I got my NC on Thursday and promptly rooted it on Friday morning, everything was smooth sailing until I started installing a bunch of apps and noticed that some things were randomly failing. Specifically baffling was the "Downloads" view in the market app. I used the Log Collector app to take a look at the logs and saw some exceptions like so:
12-21 12:08:54.890 E/AndroidRuntime( 1719): java.lang.RuntimeException: Unable to get provider com.android.providers.media.MediaProvider: android.database.sqlite.SQLiteException: no such table: main.audio: , while compiling: SELECT album_art FROM album_info
12-21 12:08:54.890 E/AndroidRuntime( 1719): at android.app.ActivityThread.installProvider(ActivityThread.java)
Some snooping around revealed that there's a missing sql view in /data/data/com.android.providers.media/databases/internal.db. Sometime during NC startup some app tries to delete the view and rebuild it, but since the view was already gone it couldn't delete and therefore failed:
12-21 13:42:30.475 E/Database( 1867): Failure 1 (use DROP TABLE to delete table audio) on 0x2c50e0 when preparing 'DROP VIEW IF EXISTS audio'.
12-21 13:42:30.475 D/AndroidRuntime( 1867): Shutting down VM
12-21 13:42:30.475 W/dalvikvm( 1867): threadid=3: thread exiting with uncaught exception (group=0x4001b170)
12-21 13:42:30.475 E/AndroidRuntime( 1867): Uncaught handler: thread main exiting due to uncaught exception
12-21 13:42:30.491 E/AndroidRuntime( 1867): java.lang.RuntimeException: Unable to get provider com.android.providers.media.MediaProvider: android.database.sqlite.SQLiteException: use DROP TABLE to delete table audio: DROP VIEW IF EXISTS audio
Solution - pull internal.db off the device, create a dummy view named audio in the database (I used Sqliteman on ubuntu) and push it back to the NC.
Reboot, problem fixed. Hope someone finds some use in this writeup.
Hi guys
There's this app called buienalarm. It's really helpful, but sometimes it works and other times it causes the phone to soft reboot, crash and reboot. Events are happening in this order FYI. I have no idea what is causing this, but I used alogrec for record the logcat. Can someone tell me what's going on?
E/ ( 6050): netstack: STAT_HUB - App org.yoki.android.buienalarm isn't supported
W/dalvikvm( 1016): threadid=11: thread exiting with uncaught exception (group=0x41737658)
D/AdSDK ( 6050): ***** StartLoadContent, url=http://merlin.nakko.com/index.php?count=1&key=6&mcc=204&mnc=08&site=289&resizable=1&ua=Mozilla%2F5.0�%28Linux%3B�%3Bɷ殢❾�.3%3B�nl%3B詗�%2F12.1.A.1.205%29ʚ敹枛⨫�%2F534.30�%28KHTML%2C阩Ỹ果�%29嗪�%2F4.0㊆槶�%2F534.30&zone=1&request_counter=0&package_name=org.yoki.android.buienalarm&uid=WIFIMAC%3A00%3Aeb%3A2d%3A6c%3A79%3A96&android_id=b073a717e4807c87&bucket=%7B%7D
D/AdSDK ( 6050): ***** runWithHttpURLConnection, START HTTP EXECUTION
D/AdSDK ( 6050): ***** headerUserAgent=Buienalarm/121
D/AdSDK ( 6050): ***** runWithHttpURLConnection, END HTTP EXECUTION
E/AndroidRuntime( 1016): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
E/AndroidRuntime( 1016): java.lang.IllegalArgumentException: provider doesn't exisit: null
Another part of the log states:
I/ValueStore( 6050): Creating new value store instance
V/GCMRegistrar( 6050): Registering receiver
D/GCMRegistrar( 6050): resetting backoff for org.yoki.android.buienalarm
V/GCMRegistrar( 6050): Unregistering app org.yoki.android.buienalarm
D/dalvikvm( 6050): GC_FOR_ALLOC freed 2401K, 32% free 8577K/12496K, paused 15ms, total 16ms
Weird case you've got there.
I use Buienrader almost everyday and I have absolutly no issues.
From what I understand from the parts of the logcat it makes the system crash when loading content..
@mrjraider
You're using buienradar or buienalarm? Two different apps can you tell how I can get this back to work? Or who I should contact for this
Haha sorry, I do use both actually and also buienalarm gives no issues..
Can you recommend someone who I can contact with for this log?
I think no one because the buienalarm app hasnt been updated since january 2014
I mean who can figure out exactly what's crashing and how I can fix it
Hi, I would create this topic in "Java for Android" section, but I can't, so I post it here.
To the issue: My app always shutdown in random time interval (mostly from few minutes to something like 20 mins). The "App stopped working" messagebox appears. Biggest problem is, I don't do anything in app (like interacting with it), and it just random shutdown by itself. Here's logcat print:
Code:
07-15 20:34:16.595 27361-27363/test.game D/dalvikvm: GC_CONCURRENT freed 141
9K, 44% free 13902K/24391K, paused 4ms+9ms, total 66ms
07-15 20:34:28.997 27361-27363/test.game D/dalvikvm: GC_CONCURRENT freed 1416K, 43% free 13903K/24391K, paused 3ms+7ms, total 56ms
07-15 20:34:29.418 27361-27361/test.game D/AndroidRuntime: Shutting down VM
07-15 20:34:29.418 27361-27361/test.game W/dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x412b52a0)
07-15 20:34:29.498 27361-27361/test.game E/AndroidRuntime: FATAL EXCEPTION: main java.lang.IllegalStateException: onMeasure() did not set the measured dimension by calling setMeasuredDimension()
at android.view.View.measure(View.java:15293)
at android.widget.RelativeLayout.measureChildHorizontal(RelativeLayout.java:617)
at android.widget.RelativeLayout.onMeasure(RelativeLayout.java:399)
at android.view.View.measure(View.java:15288)
at android.widget.RelativeLayout.measureChildHorizontal(RelativeLayout.java:617)
at android.widget.RelativeLayout.onMeasure(RelativeLayout.java:399)
at android.view.View.measure(View.java:15288)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4876)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at android.view.View.measure(View.java:15288)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4876)
at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1396)
at android.widget.LinearLayout.measureVertical(LinearLayout.java:681)
at android.widget.LinearLayout.onMeasure(LinearLayout.java:574)
at android.view.View.measure(View.java:15288)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4876)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at com.android.internal.policy.impl.PhoneWindow$DecorView.onMeasure(PhoneWindow.java:2397)
at android.view.View.measure(View.java:15288)
at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:1974)
at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1217)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1390)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1113)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:4481)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:725)
at android.view.Choreographer.doCallbacks(Choreographer.java:555)
at android.view.Choreographer.doFrame(Choreographer.java:525)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:711)
at android.os.Handler.handleCallback(Handler.java:615)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4867)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1007)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:774)
at dalvik.system.NativeStart.main(Native Method)
One would say, it's because I didn't write setMeasuredDimension() when overriding method onMeasure(). Also, docs say you have to write this line to your onMeasure, otherwise the IllegalStateException will be thrown (see it here).
But I don't overriding onMeasure anywhere in my whole project, so problem is not here (at least not on my side in this case).
Few things to note:
- this is full logcat log, and any of these lines ("at android. ...") doesn't link to my code, all goes to source - that means all of these links are gray
- this exception always happens only on my S3 Mini (android 4.1.2), but never happened on my old Galaxy Ace S5830i (android 2.3.6) (and yes, I tested it alot - over 20hours on old phone and app still running!).
- never happened in emulator
- there are no "view resizing" operations running in background, which could cause this exception
I would like to post some code, but I have absolutely no idea where this exception could be thrown.
If someone can help, I'd be really, really grateful. I'm lost at this point...