I really just want to document my experience with Nexus Support and Motorola.
I have been having non-stop issues with my Nexus 6.
Model: Nexus 6
Android version: 5.1
Baseband version: MDM9625_104446.01.02.95R
Kernel version: 3.10.40-geec2459
Build number: LMY47D
Model XT1103 / FCC ID: IHDT56QD1
Basically, I used the Google Developers page to install this firmware version.
Ever since then, I've been having the most bizarre issues.
The phone becomes unresponsive, slow to wake up, slow to type, slow to do ANYTHING
I enabled show screen touches on Dev menu
I can see that the screen knows I'm touching it, but it's not actually computing those changes.
After some time, it kinda wakes up and slowly processes my input.
It is only 'resolvable' by restarting the phone.
incoming call? Nah, you don't get to swipe to answer... call drops before it even responds
My LG G Watch will ring and my phone never will. I can't afford that.
Keyboard will provide haptic feedback that I'm trying to type, and the focus APPEARS to be on the search bar or in a hangouts window, but it never popualtes the text far.
So basically, I have had it.
I chatted with Nexus Support and spoke to Deven who told me that I should contact Motorola, where I purchased my phone. He also told me that the images found on https://developers.google.com/android/nexus/images are not valid for the Motorola purchased Nexus 6. I was very mad about hearing this, I only buy Nexus so I can get these latest updates. He said that the phone Google sales is the "Google Play edition" and the one that Motorola sells, he has no idea but it isn't the same. He told me to downgrade to 5.0 and wait for OTA upgrades to the "correct" version of 5.1. since I told him I installed 5.1 through that site. He told me not to tell Motorola about using the dev.google.com page to install 5.1.
Apathetic to Deven's support, I went to Motorola and chatted with them. Gave them the same story about my device. They escalated me to Level 2. I called Level 2 and the guy did an RMA for my phone because of the kinds of problems.
After the RMA was processed, I asked him if I should be using the Google Developers page to flash my ROM on my phone. He informed me that Motorola is aware of an issue and are addressing it with the factory images (basically confirming to me that using factory images can have problems at this time). I asked if those are being addressed in the 5.1.1 factory image and he confirmed. He said they're not sure on date but expecting 5.1.1 release in July.
I just wish I had a fully functional phone I didn't have to restart every few hours.
My Motorola RMA reference also mentions that the phone is (XT1112, XT1107). From another thread, I noticed that some people saw this from Motorola but also get another US version of their phone (XT1103).
codycook said:
He also told me that the images found on https://developers.google.com/android/nexus/images are not valid for the Motorola purchased Nexus 6
Click to expand...
Click to collapse
He is talking rubbish there.
codycook said:
He said that the phone Google sales is the "Google Play edition"
Click to expand...
Click to collapse
This is also pretty much rubbish,
codycook said:
the one that Motorola sells, he has no idea but it isn't the same.
Click to expand...
Click to collapse
It is EXACTLY the same.
codycook said:
He told me to downgrade to 5.0 and wait for OTA upgrades to the "correct" version of 5.1.
Click to expand...
Click to collapse
Rubbish, they use the same ROM. Also I believe that it Isn't possible, the 5.1 Bootloader cannot be downgraded. Attempts I believe result in what many may have thought to be a brick.
Bought my XT-1100 in a regular local store and i presume they get the devices from Motorola rather then from Google and i haven`t had a problem flashing roms from the Google Developers page. Look here http://www.randomphantasmagoria.com/firmware/nexus-6/ for the XT-1100/1103 firmwares and they should all be comaptible with your device.
I'm curious, did you factory reset from recovery after flashing the factory image?
gee2012 said:
Bought my XT-1100 in a regular local store and i presume they get the devices from Motorola rather then from Google and i haven`t had a problem flashing roms from the Google Developers page. Look here http://www.randomphantasmagoria.com/firmware/nexus-6/ for the XT-1100/1103 firmwares and they should all be comaptible with your device.
Click to expand...
Click to collapse
Basically, same device. Only difference is bought from play = googles honour warranty. Bought from anywhere else = Motorola honour warranty
rootSU said:
Basically, same device. Only difference is bought from play = googles honour warranty. Bought from anywhere else = Motorola honour warranty
Click to expand...
Click to collapse
Off course, there are no seperate Google and Motorola roms. Moto tech. support is realy good
---------- Post added at 11:10 PM ---------- Previous post was at 10:55 PM ----------
Evolution_Tech said:
I'm curious, did you factory reset from recovery after flashing the factory image?
Click to expand...
Click to collapse
Guess not, neither did he flash the userdata.img most likely.
rootSU said:
He is talking rubbish there.
This is also pretty much rubbish,
It is EXACTLY the same.
Rubbish, they use the same ROM. Also I believe that it Isn't possible, the 5.1 Bootloader cannot be downgraded. Attempts I believe result in what many may have thought to be a brick.
Click to expand...
Click to collapse
I know. I haven't tried to downgrade the boot loader but this is just what they were telling me.
gee2012 said:
Bought my XT-1100 in a regular local store and i presume they get the devices from Motorola rather then from Google and i haven`t had a problem flashing roms from the Google Developers page. Look here http://www.randomphantasmagoria.com/firmware/nexus-6/ for the XT-1100/1103 firmwares and they should all be comaptible with your device.
Click to expand...
Click to collapse
I have looked at that page before. That's where I knew that the ROMs should be the same.
Evolution_Tech said:
I'm curious, did you factory reset from recovery after flashing the factory image?
Click to expand...
Click to collapse
Yes. I did both in the ROM and also through Recovery. I tried it all.
gee2012 said:
Off course, there are no seperate Google and Motorola roms. Moto tech. support is realy good
---------- Post added at 11:10 PM ---------- Previous post was at 10:55 PM ----------
Guess not, neither did he flash the userdata.img most likely.
Click to expand...
Click to collapse
Actually, the way I flashed the rom was using the FLASH ALL script built into the factory images.
codycook said:
I know. I haven't tried to downgrade the boot loader but this is just what they were telling me.
I have looked at that page before. That's where I knew that the ROMs should be the same.
Yes. I did both in the ROM and also through Recovery. I tried it all.
Actually, the way I flashed the rom was using the FLASH ALL script built into the factory images.
Click to expand...
Click to collapse
Flash All doesn`t work as it should. Flash the seperate img`s in fastboot and all should be well.
Flash: bootloader.img, radio.img, system.img, userdata.img, boot.img and erase and flash cache.img. Flashing the bootloader and radio are only necessary if you haven`t got the latest ones allready.
gee2012 said:
Flash All doesn`t work as it should. Flash the seperate img`s in fastboot and all should be well.
Flash: bootloader.img, radio.img, system.img, userdata.img, boot.img and erase and flash cache.img. Flashing the bootloader and radio are only necessary if you haven`t got the latest ones allready.
Click to expand...
Click to collapse
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
So from what you're telling me, it doesn't properly extract the image-shamu-xyz.zip, which includes cache.img, boot.img, recovery.img, userdata.img, or system.img? And why wouldn't that be addressed here in the flash all script? isn't this the whole point?
codycook said:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
So from what you're telling me, it doesn't properly extract the image-shamu-xyz.zip, which includes cache.img, boot.img, recovery.img, userdata.img, or system.img? And why wouldn't that be addressed here in the flash all script? isn't this the whole point?
Click to expand...
Click to collapse
They've not worked properly since 5.0 even on the Nexus 5.
Just manually flash again, like suggested.
codycook said:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
So from what you're telling me, it doesn't properly extract the image-shamu-xyz.zip, which includes cache.img, boot.img, recovery.img, userdata.img, or system.img? And why wouldn't that be addressed here in the flash all script? isn't this the whole point?
Click to expand...
Click to collapse
Follow this guide http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008, method 2 and you`re done. Flash-All is flawed atm.
rootSU said:
They've not worked properly since 5.0 even on the Nexus 5.
Just manually flash again, like suggested.
Click to expand...
Click to collapse
That's interesting. I'll try it when I get my RMA since they're expecting this phone back now at Motorola.
gee2012 said:
Follow this guide http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008, method 2 and you`re done. Flash-All is flawed atm.
Click to expand...
Click to collapse
Thanks, will do.
I didn't start a thread here originally because I felt like the issue was related more to that memory leak issue that they've been reporting on 5.1 (which I never saw on 5.0). I figured it was a software bug and I've been waiting endlessly for 5.1.1.
codycook said:
That's interesting. I'll try it when I get my RMA since they're expecting this phone back now at Motorola.
Thanks, will do.
I didn't start a thread here originally because I felt like the issue was related more to that memory leak issue that they've been reporting on 5.1 (which I never saw on 5.0). I figured it was a software bug and I've been waiting endlessly for 5.1.1.
Click to expand...
Click to collapse
You should try it before. We think this will fix phone. I think it's highly unlikely that you developed a hardware fault at the exact time you updated.. If it doesn't fix it, send it back as arranged but it.probably will
rootSU said:
You should try it before. We think this will fix phone. I think it's highly unlikely that you developed a hardware fault at the exact time you updated.. If it doesn't fix it, send it back as arranged but it.probably will
Click to expand...
Click to collapse
I'll see about formatting it tonight. I use my phone for work and am working now and the RMA comes tomorrow to work. I don't know how long it'd take to actually reproduce, I'll just try restoring the profile and see if that helps out.
Thanks again.
As an update for today, phone has been on for 13 hours. I'm going to try and ride the phone out for the rest of the day and then do the swap over tonight with my replacement. I am not seeing the same exact problems at this time, but I'll wait until I get to work to be totally sure.
codycook said:
As an update for today, phone has been on for 13 hours. I'm going to try and ride the phone out for the rest of the day and then do the swap over tonight with my replacement. I am not seeing the same exact problems at this time, but I'll wait until I get to work to be totally sure.
Click to expand...
Click to collapse
If you wiped and flashed correctly the problems should be gone for good
I'm back! The problem is back!
I finally got the chance to get into bug report and run it.
It's like 13 MB of data.
...
<6>[28779.226485] lowmemorykiller: Killing 'ola.service.ims' (13608), adj 1000,
<6>[28779.226485] to free 39280kB on behalf of 'kswapd0' (108) because
<6>[28779.226485] cache 162880kB is below limit 184320kB for oom_score_adj 1000
<6>[28779.226485] Free memory is 47184kB above reserved
<6>[28779.409308] lowmemorykiller: Killing 'lugins.sprintdm' (13625), adj 1000,
<6>[28779.409308] to free 40300kB on behalf of 'kswapd0' (108) because
<6>[28779.409308] cache 157444kB is below limit 184320kB for oom_score_adj 1000
<6>[28779.409308] Free memory is 52268kB above reserved
<6>[28779.496058] lowmemorykiller: Killing 'ogle.android.gm' (13568), adj 1000,
<6>[28779.496058] to free 54636kB on behalf of 'kswapd0' (108) because
<6>[28779.496058] cache 155972kB is below limit 184320kB for oom_score_adj 1000
<6>[28779.496058] Free memory is 55340kB above reserved
<6>[28779.591225] binder: undelivered transaction 15176061
<6>[28780.245170] binder: 810:1538 transaction failed 29189, size 920-0
<6>[28782.771913] lowmemorykiller: Killing 'm.verizon.omadm' (13644), adj 764,
<6>[28782.771913] to free 38968kB on behalf of 'kswapd0' (108) because
<6>[28782.771913] cache 147328kB is below limit 147456kB for oom_score_adj 529
<6>[28782.771913] Free memory is 55180kB above reserved
<6>[28788.029112] binder: release 13124:13124 transaction 15179191 out, still active
<6>[28788.029129] binder: release 13124:13320 transaction 15179411 out, still active
...
<6>[29016.744588] lowmemorykiller: Killing 'id.apps.fitness' (15173), adj 1000,
<6>[29016.744588] to free 52508kB on behalf of 'kswapd0' (108) because
<6>[29016.744588] cache 184220kB is below limit 184320kB for oom_score_adj 1000
<6>[29016.744588] Free memory is 53656kB above reserved
<6>[29016.881597] lowmemorykiller: Killing 'le.android.talk' (15686), adj 1000,
<6>[29016.881597] to free 54468kB on behalf of 'kswapd0' (108) because
<6>[29016.881597] cache 184216kB is below limit 184320kB for oom_score_adj 1000
<6>[29016.881597] Free memory is 55464kB above reserved
<6>[29017.164324] lowmemorykiller: Killing 'roid.music:main' (14991), adj 1000,
<6>[29017.164324] to free 49592kB on behalf of 'kswapd0' (108) because
<6>[29017.164324] cache 183752kB is below limit 184320kB for oom_score_adj 1000
<6>[29017.164324] Free memory is 52200kB above reserved
<6>[29017.303049] lowmemorykiller: Killing 'ndroid.calendar' (15576), adj 1000,
<6>[29017.303049] to free 46048kB on behalf of 'kswapd0' (108) because
<6>[29017.303049] cache 184116kB is below limit 184320kB for oom_score_adj 1000
<6>[29017.303049] Free memory is 52220kB above reserved
<6>[29017.333869] lowmemorykiller: Killing 'oadcastreceiver' (15869), adj 1000,
<6>[29017.333869] to free 41216kB on behalf of 'kswapd0' (108) because
<6>[29017.333869] cache 183528kB is below limit 184320kB for oom_score_adj 1000
<6>[29017.333869] Free memory is 54576kB above reserved
<6>[29018.963012] lowmemorykiller: Killing '.editors.sheets' (15740), adj 1000,
<6>[29018.963012] to free 65164kB on behalf of 'kswapd0' (108) because
<6>[29018.963012] cache 151608kB is below limit 184320kB for oom_score_adj 1000
<6>[29018.963012] Free memory is 54024kB above reserved
...
It looks like it keeps trying to suspend and unsuspend itself.
<6>[28069.451099] PM: suspend entry 2015-06-01 19:49:34.890829433 UTC
<6>[28069.451125] PM: Syncing filesystems ... done.
<7>[28069.485664] PM: Preparing system for mem sleep
<4>[28069.487176] Freezing user space processes ...
<6>[28069.488241] active wakeup source: PowerManagerService.WakeLocks
<6>[28069.488258] active wakeup source: msm_hsic_host
<4>[28069.488282]
<3>[28069.488291] Freezing of tasks aborted after 0.001 seconds (23 tasks refusing to freeze, wq_busy=0):
<4>[28069.488297]
<4>[28069.488303] Restarting tasks ... done.
<6>[28069.489709] PM: suspend exit 2015-06-01 19:49:34.929447037 UTC
<6>[28079.292437] PM: suspend entry 2015-06-01 19:49:44.732152554 UTC
<6>[28079.292477] PM: Syncing filesystems ... done.
<7>[28079.333747] PM: Preparing system for mem sleep
<4>[28079.335442] Freezing user space processes ...
<6>[28079.337167] active wakeup source: PowerManagerService.WakeLocks
<4>[28079.337222]
<3>[28079.337231] Freezing of tasks aborted after 0.001 seconds (23 tasks refusing to freeze, wq_busy=0):
<4>[28079.337236]
<4>[28079.337242] Restarting tasks ... done.
<6>[28079.339108] PM: suspend exit 2015-06-01 19:49:44.778846304 UTC
<6>[28088.655696] PM: suspend entry 2015-06-01 19:49:54.095409009 UTC
<6>[28088.655747] PM: Syncing filesystems ... done.
<7>[28088.688787] PM: Preparing system for mem sleep
<4>[28088.690432] Freezing user space processes ... (elapsed 0.003 seconds) done.
<4>[28088.694397] Freezing remaining freezable tasks ... (elapsed 0.004 seconds) done.
<7>[28088.698662] PM: Entering mem sleep
<4>[28088.698668] Suspending console(s) (use no_console_suspend to debug)
<3>[28088.736025] dpm_run_callback(): platform_pm_suspend+0x0/0x58 returns -16
<3>[28088.736030] PM: Device alarmtimer failed to suspend: error -16
<3>[28088.736035] PM: Some devices failed to suspend
<6>[28088.924950] PM: resume of devices complete after 188.906 msecs
<7>[28088.928486] PM: Finishing wakeup.
<4>[28088.928491] Restarting tasks ... done.
<6>[28088.945588] PM: suspend exit 2015-06-01 19:49:54.385306821 UTC
...
<6>[28585.854223] atmel_mxt_ts_mmi: mxt_set_sensor_state: state change SUSPEND -> ACTIVE
<3>[28588.295545] mdss_mdp_pipe_init: no 3 type pipes available
<3>[28588.295565] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295615] mdss_mdp_pipe_init: no 3 type pipes available
<3>[28588.295621] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295644] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295661] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295680] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295685] mdss_mdp_pipe_init: no 1 type pipes available
<3>[28588.295692] mdss_mdp_overlay_pipe_setup: error allocating pipe. flags=0x60200
<3>[28588.295908] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295927] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295945] mdss_mdp_pipe_init: no 3 type pipes available
<3>[28588.295951] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295969] mdss_mdp_pipe_init: no 3 type pipes available
<3>[28588.295975] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295994] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.296004] mdss_mdp_pipe_init: no 1 type pipes available
<3>[28588.296013] mdss_mdp_overlay_pipe_setup: error allocating pipe. flags=0x60200
<3>[28588.296110] mdss_mdp_pipe_init: no 3 type pipes available
<3>[28588.296118] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.296141] mdss_mdp_pipe_init: no 3 type pipes available
<3>[28588.296149] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.296167] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.296185] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28589.059032] mdss_mdp_pipe_init: no 1 type pipes available
<3>[28589.059044] mdss_mdp_overlay_pipe_setup: error allocating pipe. flags=0x860000
<3>[28589.075860] mdss_mdp_pipe_init: no 1 type pipes available
<3>[28589.075871] mdss_mdp_overlay_pipe_setup: error allocating pipe. flags=0x860000
<3>[28589.092918] mdss_mdp_pipe_init: no 1 type pipes available
<3>[28589.092929] mdss_mdp_overlay_pipe_setup: error allocating pipe. flags=0x860000
<3>[28589.109957] mdss_mdp_pipe_init: no 1 type pipes available
<3>[28589.109969] mdss_mdp_overlay_pipe_setup: error allocating pipe. flags=0x860000
<3>[28589.127331] mdss_mdp_pipe_init: no 1 type pipes available
Adding s'more data.
------ SYSTEM LOG (logcat -v threadtime -d *:v) ------
--------- beginning of crash
05-31 20:27:03.832 326 329 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 329 (BootAnimation)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: FATAL EXCEPTION: main
06-01 15:21:19.714 6246 6246 E AndroidRuntime: Process: com.google.android.gms.persistent, PID: 6246
06-01 15:21:19.714 6246 6246 E AndroidRuntime: java.lang.RuntimeException: Unable to create service com.google.android.location.reporting.service.ReportingAndroidService: java.lang.IllegalStateException: Not in location process
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:2771)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.app.ActivityThread.access$1800(ActivityThread.java:151)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1386)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.os.Looper.loop(Looper.java:135)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5254)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:372)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Not in location process
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at com.google.android.location.reporting.d.b.c(SourceFile:73)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at com.google.android.location.reporting.config.h.a(SourceFile:92)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at com.google.android.location.reporting.service.ReportingAndroidService.onCreate(SourceFile:61)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:2761)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: ... 9 more
here's the part where my navbar vanishes...
06-01 17:34:17.268 810 992 I InputDispatcher: Application is not responding: Window{15501760 u0 NavigationBar}. It has been 5057.5ms since event, 5057.2ms since wait started. Reason: Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 3. Wait queue head age: 5840.2ms.
06-01 17:34:17.271 810 992 I WindowManager: Input event dispatching timed out sending to NavigationBar. Reason: Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 3. Wait queue head age: 5840.2ms.
and where smartcard flips out, making my simcard vanish and kick me off the network
06-01 17:34:20.729 18884 18899 W TRThreadPoolExecutor: Task "GmsLocationReporting[getReportingState]" is a ac. Failures of FutureTask can not be detected and exceptions will not be propagated by the executor
06-01 17:34:20.779 18884 18899 W TRThreadPoolExecutor: Task "p[Get token]" is a o. Failures of FutureTask can not be detected and exceptions will not be propagated by the executor
06-01 17:34:20.822 8392 8414 I SmartcardService ACE ARF: Logical channels are used to access to PKC15
06-01 17:34:20.822 8392 8414 V ACE ARF EF_Dir: Analysing EF_DIR...
06-01 17:34:20.901 8392 8414 D SmartcardService ACE ARF: SelectFile [3*38b]
06-01 17:34:20.901 8392 8414 D SmartcardService ACE ARF: ReadRecord [1/38b]
06-01 17:34:20.921 8392 8414 D SmartcardService ACE ARF: ReadRecord [2/38b]
06-01 17:34:20.941 8392 8414 D SmartcardService ACE ARF: ReadRecord [3/38b]
06-01 17:34:20.965 8392 8414 E SmartcardService ACE ARF: SIM - UICC rules not correctly initialized! [Parser] Cannot retreive type
06-01 17:34:21.012 8392 8414 E SmartcardService: [Parser] Cannot retreive type
06-01 17:34:21.012 8392 8414 I SmartcardService: Deny any access to:SIM - UICC
06-01 17:34:21.012 8392 8414 E SmartcardService: Fail to load rules: Let's try another time (5 remaining attempt
06-01 17:34:21.183 810 838 I Process : Sending signal. PID: 18884 SIG: 3
06-01 17:34:21.183 18884 18893 I art : Thread[5,tid=18893,WaitingInMainSignalCatcherLoop,Thread*=0xb4a17c00,peer=0x32c070a0,"Signal Catcher"]: reacting to signal 3
06-01 17:34:21.383 810 838 I Process : Sending signal. PID: 28578 SIG: 3
06-01 17:34:21.384 28578 28587 I art : Thread[5,tid=28587,WaitingInMainSignalCatcherLoop,Thread*=0xb4a17c00,peer=0x12c000a0,"Signal Catcher"]: reacting to signal 3
06-01 17:34:21.481 18884 18893 I art : Wrote stack traces to '/data/anr/traces.txt'
06-01 17:34:21.482 810 838 I Process : Sending signal. PID: 1452 SIG: 3
06-01 17:34:21.482 1452 1461 I art : Thread[5,tid=1461,WaitingInMainSignalCatcherLoop,Thread*=0xb4a17c00,peer=0x32c070a0,"Signal Catcher"]: reacting to signal 3
06-01 17:34:21.657 1452 1461 I art : Wrote stack traces to '/data/anr/traces.txt'
06-01 17:34:21.657 810 838 I Process : Sending signal. PID: 1222 SIG: 3
06-01 17:34:21.657 1222 1231 I art : Thread[5,tid=1231,WaitingInMainSignalCatcherLoop,Thread*=0xb4a17c00,peer=0x12c000a0,"Signal Catcher"]: reacting to signal 3
06-01 17:34:21.716 28578 28587 I art : Wrote stack traces to '/data/anr/traces.txt'
06-01 17:34:21.742 810 838 E ActivityManager: ANR in com.android.systemui
06-01 17:34:21.742 810 838 E ActivityManager: PID: 27358
06-01 17:34:21.742 810 838 E ActivityManager: Reason: Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 3. Wait queue head age: 5788.5ms.)
06-01 17:34:21.742 810 838 E ActivityManager: Load: 13.92 / 13.68 / 13.22
06-01 17:34:21.742 810 838 E ActivityManager: CPU usage from 3245ms to -4458ms ago with 99% awake:
06-01 17:34:21.742 810 838 I ActivityManager: Killing 27358:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:21.819 810 1486 E JavaBinder: !!! FAILED BINDER TRANSACTION !!!
06-01 17:34:21.828 810 1537 W AudioService: Current remote volume controller died, unregistering
06-01 17:34:21.828 810 1148 I WindowState: WIN DEATH: Window{238d62cd u0 com.android.systemui.ImageWallpaper}
06-01 17:34:21.828 810 1002 D WifiService: Client connection lost with reason: 4
06-01 17:34:21.829 810 1002 D WifiService: Client connection lost with reason: 4
06-01 17:34:21.832 810 825 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ id=22, legacyType=-1, [] ], [email protected])
06-01 17:34:21.832 810 992 W InputDispatcher: channel '3c41bdeb StatusBar (server)' ~ Consumer closed input channel or an error occurred. events=0x9
06-01 17:34:21.832 810 992 E InputDispatcher: channel '3c41bdeb StatusBar (server)' ~ Channel is unrecoverably broken and will be disposed!
Last but not least, a grep from the log of all "bg anr" and what processes they killed.
C:\Users\Cody
λ cat "Google Drive\bugreport-2015-06-01-17-36-25.txt" | grep "bg anr"
06-01 17:34:21.742 810 838 I ActivityManager: Killing 27358:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:26.336 810 838 I ActivityManager: Killing 32592:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:30.768 810 838 I ActivityManager: Killing 32649:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:35.522 810 838 I ActivityManager: Killing 32680:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:40.425 810 838 I ActivityManager: Killing 32709:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:46.032 810 838 I ActivityManager: Killing 32731:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:49.976 810 838 I ActivityManager: Killing 32755:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:54.337 810 838 I ActivityManager: Killing 441:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:59.135 810 838 I ActivityManager: Killing 506:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:03.670 810 838 I ActivityManager: Killing 642:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:07.939 810 838 I ActivityManager: Killing 769:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:12.454 810 838 I ActivityManager: Killing 834:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:20.498 810 838 I ActivityManager: Killing 890:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:25.806 810 838 I ActivityManager: Killing 931:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:31.339 810 838 I ActivityManager: Killing 974:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:36.446 810 838 I ActivityManager: Killing 1016:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:41.876 810 838 I ActivityManager: Killing 1067:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:47.047 810 838 I ActivityManager: Killing 1086:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:52.348 810 838 I ActivityManager: Killing 1106:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:57.114 810 838 I ActivityManager: Killing 1132:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:01.769 810 838 I ActivityManager: Killing 1154:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:07.001 810 838 I ActivityManager: Killing 1184:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:12.497 810 838 I ActivityManager: Killing 1207:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:17.704 810 838 I ActivityManager: Killing 1227:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:23.281 810 838 I ActivityManager: Killing 1272:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:27.638 810 838 I ActivityManager: Killing 1302:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:32.760 810 838 I ActivityManager: Killing 1331:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:37.050 810 838 I ActivityManager: Killing 1405:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:42.110 810 838 I ActivityManager: Killing 1499:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:46.501 810 838 I ActivityManager: Killing 1645:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:51.847 810 838 I ActivityManager: Killing 1713:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:57.029 810 838 I ActivityManager: Killing 1796:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:20:34.507 810 838 I am_kill : [0,20151,com.facebook.orca,0,bg anr]
06-01 17:20:57.425 810 838 I am_kill : [0,4992,com.android.phone,-12,bg anr]
06-01 17:21:07.090 810 838 I am_kill : [0,6150,com.google.process.gapps,0,bg anr]
06-01 17:21:23.924 810 838 I am_kill : [0,28314,com.android.systemui,-12,bg anr]
06-01 17:21:54.441 810 838 I am_kill : [0,4717,com.facebook.katana,8,bg anr]
06-01 17:22:08.164 810 838 I am_kill : [0,21453,com.facebook.orca,0,bg anr]
06-01 17:22:38.877 810 838 I am_kill : [0,21794,com.android.phone,-12,bg anr]
06-01 17:22:51.845 810 838 I am_kill : [0,22025,com.google.process.gapps,0,bg anr]
06-01 17:25:14.145 810 838 I am_kill : [0,23249,com.facebook.katana,8,bg anr]
06-01 17:25:24.330 810 838 I am_kill : [0,23344,com.facebook.orca,0,bg anr]
06-01 17:25:43.528 810 838 I am_kill : [0,24369,com.google.process.gapps,0,bg anr]
06-01 17:25:47.753 810 838 I am_kill : [0,9549,com.google.android.gms.persistent,0,bg anr]
06-01 17:26:08.244 810 838 I am_kill : [0,24180,com.android.phone,-12,bg anr]
06-01 17:26:18.016 810 838 I am_kill : [0,26446,com.google.android.gms.persistent,0,bg anr]
06-01 17:26:26.658 810 838 I am_kill : [0,26315,com.google.process.gapps,0,bg anr]
06-01 17:26:32.981 810 838 I am_kill : [0,22508,com.android.systemui,-12,bg anr]
06-01 17:26:37.034 810 838 I am_kill : [0,26941,com.android.phone,-12,bg anr]
06-01 17:26:44.325 810 838 I am_kill : [0,27147,com.google.android.gms.persistent,0,bg anr]
06-01 17:27:02.016 810 838 I am_kill : [0,27378,com.android.phone,-12,bg anr]
06-01 17:27:23.184 810 838 I am_kill : [0,27806,com.google.android.gms.persistent,0,bg anr]
06-01 17:27:55.398 810 838 I am_kill : [0,28182,com.google.android.gms.persistent,0,bg anr]
06-01 17:28:20.566 810 838 I am_kill : [0,28423,com.google.android.gms.persistent,0,bg anr]
06-01 17:33:03.267 810 838 I am_kill : [0,26054,com.facebook.orca,5,bg anr]
06-01 17:33:19.084 810 838 I am_kill : [0,28129,com.android.phone,-12,bg anr]
06-01 17:33:44.191 810 838 I am_kill : [0,31344,com.android.phone,-12,bg anr]
06-01 17:34:21.742 810 838 I am_kill : [0,27358,com.android.systemui,-12,bg anr]
06-01 17:34:26.336 810 838 I am_kill : [0,32592,com.android.systemui,-12,bg anr]
06-01 17:34:30.768 810 838 I am_kill : [0,32649,com.android.systemui,-12,bg anr]
06-01 17:34:35.522 810 838 I am_kill : [0,32680,com.android.systemui,-12,bg anr]
06-01 17:34:40.425 810 838 I am_kill : [0,32709,com.android.systemui,-12,bg anr]
06-01 17:34:46.032 810 838 I am_kill : [0,32731,com.android.systemui,-12,bg anr]
06-01 17:34:49.976 810 838 I am_kill : [0,32755,com.android.systemui,-12,bg anr]
06-01 17:34:54.337 810 838 I am_kill : [0,441,com.android.systemui,-12,bg anr]
06-01 17:34:59.135 810 838 I am_kill : [0,506,com.android.systemui,-12,bg anr]
06-01 17:35:03.670 810 838 I am_kill : [0,642,com.android.systemui,-12,bg anr]
06-01 17:35:07.939 810 838 I am_kill : [0,769,com.android.systemui,-12,bg anr]
06-01 17:35:12.454 810 838 I am_kill : [0,834,com.android.systemui,-12,bg anr]
06-01 17:35:20.499 810 838 I am_kill : [0,890,com.android.systemui,-12,bg anr]
06-01 17:35:25.806 810 838 I am_kill : [0,931,com.android.systemui,-12,bg anr]
06-01 17:35:31.339 810 838 I am_kill : [0,974,com.android.systemui,-12,bg anr]
06-01 17:35:36.446 810 838 I am_kill : [0,1016,com.android.systemui,-12,bg anr]
06-01 17:35:41.876 810 838 I am_kill : [0,1067,com.android.systemui,-12,bg anr]
06-01 17:35:47.047 810 838 I am_kill : [0,1086,com.android.systemui,-12,bg anr]
06-01 17:35:52.348 810 838 I am_kill : [0,1106,com.android.systemui,-12,bg anr]
06-01 17:35:57.114 810 838 I am_kill : [0,1132,com.android.systemui,-12,bg anr]
06-01 17:36:01.769 810 838 I am_kill : [0,1154,com.android.systemui,-12,bg anr]
06-01 17:36:07.002 810 838 I am_kill : [0,1184,com.android.systemui,-12,bg anr]
06-01 17:36:12.498 810 838 I am_kill : [0,1207,com.android.systemui,-12,bg anr]
06-01 17:36:17.704 810 838 I am_kill : [0,1227,com.android.systemui,-12,bg anr]
06-01 17:36:23.281 810 838 I am_kill : [0,1272,com.android.systemui,-12,bg anr]
06-01 17:36:27.638 810 838 I am_kill : [0,1302,com.android.systemui,-12,bg anr]
06-01 17:36:32.760 810 838 I am_kill : [0,1331,com.android.systemui,-12,bg anr]
06-01 17:36:37.050 810 838 I am_kill : [0,1405,com.android.systemui,-12,bg anr]
06-01 17:36:42.110 810 838 I am_kill : [0,1499,com.android.systemui,-12,bg anr]
06-01 17:36:46.502 810 838 I am_kill : [0,1645,com.android.systemui,-12,bg anr]
06-01 17:36:51.847 810 838 I am_kill : [0,1713,com.android.systemui,-12,bg anr]
06-01 17:36:57.029 810 838 I am_kill : [0,1796,com.android.systemui,-12,bg anr]
I'd consider posting my bugreport if 1) it wasn't so damn huge, and 2) there wasn't so much identifying information in it.
If there really is a memory leak issue as most of the Android 5 news articles mention, and it's something that Google'll address, I'm okay with that, but if it isn't , w...t...f....
p.s. I sent back the Motorola replacement, mainly because they sent me a phone without the screen protector on it (I still have the factory screen protector on my original N6), but it was really because I had hoped I fixed my phone based on these suggestions.
codycook said:
I'd consider posting my bugreport if 1) it wasn't so damn huge, and 2) there wasn't so much identifying information in it.
If there really is a memory leak issue as most of the Android 5 news articles mention, and it's something that Google'll address, I'm okay with that, but if it isn't , w...t...f....
p.s. I sent back the Motorola replacement, mainly because they sent me a phone without the screen protector on it (I still have the factory screen protector on my original N6), but it was really because I had hoped I fixed my phone based on these suggestions.
Click to expand...
Click to collapse
Could be a hardware issue or the HAL
Related
Hey all, this is the CarDock.apk, Dock.apk and dockrunner.apk. I am hoping that these work for you all, I haven't had a chance to test all of them. I backported the weather widget from 2.0 last week and took the same approach to these. These don't work on hero roms, I just tried... But they should be ok for donuts.
Again, Please rename all of these to whatever the file name is ".apk" instead of ".zip" Install all 3 before running. Thanks.
Red
Ps. Second post will be upload of other file... problems with this site.
2nd part with the other file.
Here is the last file.
http://rapidshare.com/files/329036849/Dock.zip.html
This can only be downloaded 10 times. Can someone test this and if it works ok on donuts, please host the file. I would appreciate it, and i'm sure other people would as well. Thank you all!
Red.
The media dock works fine but Car Home force closes.
Trace:
Code:
I/ActivityManager( 145): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.cardock/.CarDockActivity }
W/WindowManager( 145): Exception when adding starting window
W/WindowManager( 145): java.lang.RuntimeException: Binary XML file line #25: You must supply a layout_height attribute.
W/WindowManager( 145): at android.content.res.TypedArray.getLayoutDimension(TypedArray.java:438)
W/WindowManager( 145): at android.view.ViewGroup$LayoutParams.setBaseAttributes(ViewGroup.java:3468)
W/WindowManager( 145): at android.view.ViewGroup$MarginLayoutParams.<init>(ViewGroup.java:3547)
W/WindowManager( 145): at android.widget.LinearLayout$LayoutParams.<init>(LinearLayout.java:1265)
W/WindowManager( 145): at android.widget.LinearLayout.generateLayoutParams(LinearLayout.java:1191)
W/WindowManager( 145): at android.widget.LinearLayout.generateLayoutParams(LinearLayout.java:44)
W/WindowManager( 145): at android.view.LayoutInflater.rInflate(LayoutInflater.java:619)
W/WindowManager( 145): at android.view.LayoutInflater.inflate(LayoutInflater.java:407)
W/WindowManager( 145): at android.view.LayoutInflater.inflate(LayoutInflater.java:320)
W/WindowManager( 145): at android.view.LayoutInflater.inflate(LayoutInflater.java:276)
W/WindowManager( 145): at com.android.internal.policy.impl.PhoneWindow.generateLayout(PhoneWindow.java:2185)
W/WindowManager( 145): at com.android.internal.policy.impl.PhoneWindow.installDecor(PhoneWindow.java:2239)
W/WindowManager( 145): at com.android.internal.policy.impl.PhoneWindow.getDecorView(PhoneWindow.java:1447)
W/WindowManager( 145): at com.android.internal.policy.impl.PhoneWindowManager.addStartingWindow(PhoneWindowManager.java:657)
W/WindowManager( 145): at com.android.server.WindowManagerService$H.handleMessage(WindowManagerService.java:7484)
W/WindowManager( 145): at android.os.Handler.dispatchMessage(Handler.java:99)
W/WindowManager( 145): at android.os.Looper.loop(Looper.java:123)
W/WindowManager( 145): at com.android.server.WindowManagerService$WMThread.run(WindowManagerService.java:475)
I/ActivityManager( 145): Start proc com.android.cardock for activity com.android.cardock/.CarDockActivity: pid=17004 uid=10055 gids={}
W/dalvikvm(17004): VFY: unable to resolve static field 6 (CONTENT_URI) in Landroid/provider/ContactsContract$Contacts;
D/dalvikvm(17004): VFY: replacing opcode 0x62 at 0x0084
D/dalvikvm(17004): Making a copy of Lcom/android/cardock/CarDockActivity;.setUpIntents code (292 bytes)
D/dalvikvm(17004): GC freed 589 objects / 52800 bytes in 90ms
D/dalvikvm(17004): GC freed 160 objects / 7104 bytes in 87ms
I/ActivityManager( 145): Process com.android.alarmclock (pid 16945) has died.
D/AndroidRuntime(17004): Shutting down VM
W/dalvikvm(17004): threadid=3: thread exiting with uncaught exception (group=0x4001e170)
E/AndroidRuntime(17004): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime(17004): java.lang.NoClassDefFoundError: android.provider.ContactsContract$Contacts
E/AndroidRuntime(17004): at com.android.cardock.CarDockActivity.setUpIntents(CarDockActivity.java:261)
E/AndroidRuntime(17004): at com.android.cardock.CarDockActivity.onCreate(CarDockActivity.java:184)
E/AndroidRuntime(17004): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123)
E/AndroidRuntime(17004): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2427)
E/AndroidRuntime(17004): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2480)
E/AndroidRuntime(17004): at android.app.ActivityThread.access$2200(ActivityThread.java:118)
E/AndroidRuntime(17004): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1834)
E/AndroidRuntime(17004): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(17004): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(17004): at android.app.ActivityThread.main(ActivityThread.java:4320)
E/AndroidRuntime(17004): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(17004): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime(17004): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime(17004): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
E/AndroidRuntime(17004): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 145): Sending signal. PID: 17004 SIG: 3
I/dalvikvm(17004): threadid=7: reacting to signal 3
I/dalvikvm(17004): Wrote stack trace to '/data/anr/traces.txt'
W/ActivityManager( 145): Launch timeout has expired, giving up wake lock!
W/ActivityManager( 145): Activity idle timeout for HistoryRecord{43c1c8b8 com.android.cardock/.CarDockActivity}
I/Process (17004): Sending signal. PID: 17004 SIG: 9
I/ActivityManager( 145): Process com.android.cardock (pid 17004) has died.
W/UsageStats( 145): Unexpected resume of com.irrenhaus.advancedlauncher.donut while already resumed in com.android.cardock
W/InputManagerService( 145): Window already focused, ignoring focus gain of: [email protected]
Edit: There seems to be a problem with the clock icon in the media dock app.
Hmm... Looks nice and seems to all work as intended. Until the phone froze up from trying to leave the gallery and I had to pull the battery. I hate it when that happens.
dock.apk rapidshare link died...
Do we need to install all three to have any of them work? Also, could someone post a bunch of pictures of each of these. Thanks
On a side note, could someone tell me what to press to take a screenshot. Once again thanks.
asb123 said:
Do we need to install all three to have any of them work? Also, could someone post a bunch of pictures of each of these. Thanks
On a side note, could someone tell me what to press to take a screenshot. Once again thanks.
Click to expand...
Click to collapse
You need dockrunner to make the dock work, but other than that they are independent
It's the dock from the Droid I'm sure you could find them with a simple google search
Screenshots can be taken by using the Screenshot app in the market (it's a paid app), or if you have the Android sdk, then you may use ddms. In the list of phones click yours, choose device, screencapture and then take the screenshot
DarkFoxDK said:
Edit: There seems to be a problem with the clock icon in the media dock app.
Click to expand...
Click to collapse
This is the dock from the droid, which has a bigger screen- the sizes are messed up for the g1/mt3g
JAguirre1231 said:
This is the dock from the droid, which has a bigger screen- the sizes are messed up for the g1/mt3g
Click to expand...
Click to collapse
I'm not really sure that's the problem..
The alarm clock icon is there, but a lot smaller than the other icons...
Can anyone repost dock.apk from second post?
sshark said:
Can anyone repost dock.apk from second post?
Click to expand...
Click to collapse
http://www.mediafire.com/?2yyimxqfwkg
Can someone who has Dockrunner.zip Please Reupload. Thanks
OP has dockrunner.apk which works.
Thanks for going through the effort of backporting this, it looks beautiful but I don't see much of a purpose for it. Its like a night table clock replacement right? If so I don't think I'd leave my dream's screen on all night long (that can't be good for it)
Meh, here's Dock.apk on rapidshare:
Code:
http://rapidshare.com/files/329600236/Dock.apk
Anybody else getting FC from the Dock Runner app?
I have...
MT3G 32B
Cyanogen 4.2.11.1 (Hero Community Mix Theme)
Any screenshots? thanks
sshark said:
OP has dockrunner.apk which works.
Click to expand...
Click to collapse
Nice, when i tried it wouldn't load the download...
I also get a force close from Cardock and the alarm clock icon in the multimedia dock is also very small.
car dock not working
its not working for me either.
Cyan 4.2.11.1
10 mg memory hack
media center works fine though
First of all sorry for my bad english , second I have a problem with every CM9 based rom and i tried many , tried to change baseband , ril's but I don't have any idea why is this happening . On every gb ( cm7 or miui ) based rom there's no problem ... to be more precise I have network so it's not that i dont have it at all but it's coming and going from 3g to h to without network than again all the time . thanks in advance
Hi,
please state the ROM you are using right now as well as the baseband and RIL. Makes helping you a lot easier...
Right now I am using ParanoidAndroid (great ROM!) In combination with the 218 BB and RIL. Network reception is good.
Some people report having good network stability with other BBs as well: 725 or the new BBs from 2012. It also depends on the country you are living in and the features your network provider supports. (Fast dormancy, etc,) If you are using CM-ROMs then you should usually use a RIL with version number 10(e.g. v10b)
Last but not least: jumps from 3G to H or E or even G are normal when the area where you are in has bad network coverage.
Hope that helps.
Have a nice day!
Now I'm using WajkIUI 2.5.25 with 725 bb and matching ril ( v10d ) but used cm7 builds without problems too , but when I use the same bb with cm9 ( I tried paranoid , nova hd builds , mr hyde's ... with different kernels ) network comes and goes . Thanks
Hi
Normally try to keep RIL and BB separated from the different versions (GB, ICS etc), same with kernels.
You can try to flash new version of WAJK 2.5.25, which is GB based and work wonderfully on our O2X. When you do so, remember to do full wipe (dalvik, cache and factory reset).
let it work with preinstalled settings, before you start to tweak all these little parts of the engine and remember to reboot a few times.
Remember all developers has carefully described how their specific contributions work, so read read read, then try try and enjoy.
BR
Mike
I missed the point in last post ... WajkIUI ( gb based ) is working just fine , cm7 roms too ... it's ics roms i have problem with . I wrote what rom , bb and ril I'm using at the moment but i would like to find a combination of bb , ril , ics based rom and kernel that has no network issues .
best ROM is always subjective. The one, that I am most fond of and works like a charm is NOVA HD 1.1.0 with the NOVA kernel 3.0.36 pure edition. you will have to experiment with the RIL, but when you have a good match, this ROM works like a charm.
It comes with LG UI 3.0 that is real eyecandy and easy to use.
I find batteryconsumption on this one to be low, which is good.
If you like WAJK and MIUI, bihariel has just released his MIUI v4 2.7.20. It is also a real beauty, though I find it too hard on the battery.
Have fun, finding the ones you like and remember to show your appreciation to the developers, they work for us!
BR
Mike
You can try disable automatic time from system settings. I had similar problem at some point with ICS and after I disabled automatic time is all OK. I use SNTP app to sync my clock.
Sent from my LG-P990 using xda premium
beowolf_46 said:
I missed the point in last post ... WajkIUI ( gb based ) is working just fine , cm7 roms too ... it's ics roms i have problem with . I wrote what rom , bb and ril I'm using at the moment but i would like to find a combination of bb , ril , ics based rom and kernel that has no network issues .
Click to expand...
Click to collapse
Hi beowolf_46!
Just try the following:
Use GetRIL to change your RIL to something different. To 218 v10b for example. Never mind if you are using BB 725 and the RIL does not match. As long as you have access to WLan you can always change it again. Then reboot and check whether your network issues are still present. If they are, then change the RIL again to another one and check again.
In case this doesn't help at all:
Backup your system using recovery. Then change the BB completely to something that might work. I recommend the old 218.
After the BB operation: Enter recovery mode. Then do a full wipe and do not forget to format your system partition too. You can find this in the cwm recovery menu where you can also mount/unmount partitions. Then, without reboot, flash the downloaded ICS-ROM of your choice as well as the newest ICS-GAPPS. At the moment I recommend tonyp's ParanoidAndroid #5 and his GAPPS with Google Now included. Then Reboot. Try to avoid to restore anything from backup solutions like Titanium or MyBackup as this complicates finding the error in your system. Don't make any changes to the system. Just check whether your network problems still exist (with a matching Gingerbread RIL - v10x - of course).
Hope this helps.
Have a nice day!
beowolf_46 said:
First of all sorry for my bad english , second I have a problem with every CM9 based rom and i tried many , tried to change baseband , ril's but I don't have any idea why is this happening . On every gb ( cm7 or miui ) based rom there's no problem ... to be more precise I have network so it's not that i dont have it at all but it's coming and going from 3g to h to without network than again all the time . thanks in advance
Click to expand...
Click to collapse
hello,
your problem is generally known.
this device is made in 2 country's: Germany and Korea.
So if your phone is made in korea, you probably have a korean baseband and RIL
this is what you can do:
>shut your phone down.
>remove the battery.
> if you see "Made in Korea" on the label,
you can try to install a su660 ported baseband and RIL
go to this post if you want more information about Baseband, RIL, etc.
http://forum.xda-developers.com/showthread.php?t=1658047
if you want to try to install the Su660 ported baseband, go to this link:
http://forum.xda-developers.com/showthread.php?t=1500443
BUT I HAVE TO WARN YOU: INSTALLING A SU660 BASEBAND CAN LEAD TO LOSING YOUR IMEI, SO FOLLOW THE STEPS !
And please press the "Thanks" button if you found this verry helpful.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
New on xda, but not new on Android
Sorry for my bad English, i'm Dutch
Donate if my post/reply was very helpful.
I'm saving for a new device
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=2T3CLL6G5VRD4
... under battery it says " made in korea " but i couldn't get signal with any of su bb's and tried all of them ( with matchin ril's ) automatic time was of already , unfortunately . right now im on 218 bb with matching ril , nova hd rebuild 1.1.0 with nova kernel and still have the same issue . I don't think it has anything to do with rom itself as long as it's cm9 based problem is there , all cm7 and gb miui roms work just fine ... thanks guys for all the answers .
Then try to reinstall the whole system and use the format system command from cwm as I described it before. It sounds as if you are carrying your problems with you from one ROM to the next. Full wipe and formatting the system will help you to get rid of these problems.
Have a nice day!
After every bb change I did a full wipe ( reset , dalvik , cache , system and data ) and nova hd has aroma installer that offers full wipe before install so it's double wiped and still the same issue ... I evend turned off saving and restoring things from google servers like passwords and prevented installing previously installed app's from market automatically but same old problem . I formated the internal sd card so theres no files from previous roms and apps but that didn't helped .
OK, you did everything. I get that now. Sorry for bothering you with procedures you already knew.
One last idea: Since your network problems are just appearing on ICS and not on GB ROMs maybe it is apn related. Have you checked the apn file on your system? Something might have changed. Check /system/etc/apns-conf.xml Compare the file from GB with the one from ICS. Search for your provider in the file. See, if something changed there. Best way to do this is on a PC and not on the small screen of your smartphone.
Have a nice day!
... well on miui it's apn's version 6 and on cm9's it's version 7 so it is different although lines for my provider are the same maybe version 6 is somehow better ... is ti possible ( probably not , but ... )
sharvan97 said:
hello,
your problem is generally known.
this device is made in 2 country's: Germany and Korea.
So if your phone is made in korea, you probably have a korean baseband and RIL
this is what you can do:
>shut your phone down.
>remove the battery.
> if you see "Made in Korea" on the label,
you can try to install a su660 ported baseband and RIL
go to this post if you want more information about Baseband, RIL, etc.
http://forum.xda-developers.com/showthread.php?t=1658047
if you want to try to install the Su660 ported baseband, go to this link:
http://forum.xda-developers.com/showthread.php?t=1500443
BUT I HAVE TO WARN YOU: INSTALLING A SU660 BASEBAND CAN LEAD TO LOSING YOUR IMEI, SO FOLLOW THE STEPS !
And please press the "Thanks" button if you found this verry helpful.
Click to expand...
Click to collapse
Under my battery is : Made in brazil.. so wich baseband is good for me?
beowolf_46 said:
First of all sorry for my bad english , second I have a problem with every CM9 based rom and i tried many , tried to change baseband , ril's but I don't have any idea why is this happening . On every gb ( cm7 or miui ) based rom there's no problem ... to be more precise I have network so it's not that i dont have it at all but it's coming and going from 3g to h to without network than again all the time . thanks in advance
Click to expand...
Click to collapse
A couple users are having this problem.
I've been trying to track that down for a while now but as I personally don't suffer from it it isn't easy.
But I recently had a talk with the Eaglesblood team who sent me a fix they did at their ROM.
I passed it to XXMrHyde who has already implemented it into his newest build 15.
Please try that and reply if it fixes the issues for you. So far I got some promising feedback.
Hello tonyp.
This is interesting, indeed. What is the solution EB has provided you with? Even more interesting because of the fact that EB doesn't have the p990 for any tests. What an effort! If you don't mind please share the nature of this fix.
Have a nice day and thank you for your time building and maintaining this very nice ROM of yours.
Raum1807 said:
Hello tonyp.
This is interesting, indeed. What is the solution EB has provided you with? Even more interesting because of the fact that EB doesn't have the p990 for any tests. What an effort! If you don't mind please share the nature of this fix.
Have a nice day and thank you for your time building and maintaining this very nice ROM of yours.
Click to expand...
Click to collapse
I posted that fix here: http://forum.xda-developers.com/showpost.php?p=29590907&postcount=482
The fix basically tells the radio to fully reset it's state if it's stuck during connecting instead of trying over and over again.
Thank you tonyp for all the work you're doing for p990 community ... I'm downloading XXMrHyde's rom now and will try it , fingers crossed . I'll post if it works but thanks in advance .
update : had to restart phone 'cause it lost signal , tryed to put it in airplane mode and than in normal again but had to res ... signal drops are still there but it looks like it's picking it up faster so I can live with it ( 'cause it's not on official rom and i don't expect it to be 100% stable ) but it's not complete fix to this anoying problem .
I'm experiencing a very similar problem, however it only occurs in bihariel's MIUIv4 Rom. Any other ICS based Rom works perfectly. i'll try to give as complete a picture as possible.
The network loss issue occurs in versions v2, v3 and v4. However, it was most prominent in Version 3. I've tried numerous Basebands, have done full wipes and formated the /system partition.
Additionally to the network loss over time ("no service" displayed in the status bar, a few bars on the signal indicator), which sorts itself out over a couple of minutes, or is fixed by a reboot, i lose the signal in the following instances:
whenever i make an outgoing call
when i send a SMS
[*]when i enter *#*#4636#*#* in the dial pad and select phone information*
when i select "3G only" in the network options
An oddity of my operator: "3" or "drei" austria only provides a 3g network. In low coverage regions, the 2g network of T-Mobile austria is used. All of the above issues only occur, when i'm connected with 3's 3g network. When i select 2g only, everything is perfectly fine. So the issue could either be related to the operator(-settings) or the network type.
*Here's a logcat of what happens, when i tap on phone information in the *#*#4636#*#* menu:
Code:
--------- beginning of /dev/log/system
W/InputManagerService( 1636): Window already focused, ignoring focus gain of: [email protected]
D/StatusBar.NetworkController( 1711): updateTelephonySignalStrength: mSignalStrength == 5(GSM) 16(CDMA)
--------- beginning of /dev/log/main
W/NvAudioDevice( 1115): @@(Device.cpp-hal)@@ setOutputMute(mute=1)
D/CAT ( 1774): CatService: ril message arrived
D/CAT ( 1774): CatService: SESSION END
D/StatusBar.NetworkController( 1711): updateTelephonySignalStrength: mSignalStrength == 6(GSM) 16(CDMA)
V/PhoneStatusBar( 1711): setLightsOn(true)
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/NvAudioDevice( 1115): @@(Device.cpp-hal)@@ setOutputMute(force unmute)
D/ ( 1107): @@(WM8994)@@ ACWM8994SetPowerMode(), CurrPowerMode = 1, PowerMode = 1
D/TwelveKeyDialer( 4691): Starting query
V/DataCursor( 4691): [0]ms to fillWindow
V/PhoneStatusBar( 1711): setLightsOn(true)
W/InputManagerService( 1636): Starting input on non-focused client [email protected] (uid=10055 pid=4186)
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
D/TwelveKeyDialer( 4691): Starting query
V/DataCursor( 4691): [0]ms to fillWindow
D/TwelveKeyDialer( 4691): Starting query
V/DataCursor( 4691): [1]ms to fillWindow
I/ActivityManager( 1636): Start proc com.android.settings for broadcast com.android.settings/.TestingSettingsBroadcastReceiver: pid=4988 uid=1000 gids={1015, 3002, 3001, 3003, 3006, 3007}
I/ActivityThread( 4988): Pub miui_settings: com.android.settings.provider.MiuiSettingsProvider
D/CAT ( 1774): CatService: ril message arrived
D/CAT ( 1774): CatService: SESSION END
I/ActivityManager( 1636): START {act=android.intent.action.MAIN flg=0x10000000 cmp=com.android.settings/.TestingSettings} from pid 4988
D/OpenGLRenderer( 4691): Flushing caches (mode 1)
V/PhoneStatusBar( 1711): setLightsOn(true)
D/libEGL ( 4988): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 4988): loaded /system/lib/egl/libEGL_tegra.so
D/libEGL ( 4988): loaded /system/lib/egl/libGLESv1_CM_tegra.so
D/libEGL ( 4988): loaded /system/lib/egl/libGLESv2_tegra.so
D/OpenGLRenderer( 4988): Enabling debug mode 0
I/Process ( 1636): Sending signal. PID: 4988 SIG: 3
I/dalvikvm( 4988): threadid=3: reacting to signal 3
I/dalvikvm( 4988): Wrote stack traces to '/data/anr/traces.txt'
I/ActivityManager( 1636): Displayed com.android.settings/.TestingSettings: +550ms
D/OpenGLRenderer( 4691): Flushing caches (mode 0)
W/SurfaceTexture( 1112): freeAllBuffersExceptCurrentLocked called but mQueue is not empty
W/InputManagerService( 1636): Starting input on non-focused client [email protected] (uid=10000 pid=4691)
D/OpenGLRenderer( 4691): Flushing caches (mode 2)
D/OpenGLRenderer( 4691): Flushing caches (mode 0)
I/ActivityManager( 1636): START {act=android.intent.action.MAIN cmp=com.android.settings/.RadioInfo} from pid 4988
D/OpenGLRenderer( 4988): Flushing caches (mode 1)
D/OpenGLRenderer( 4988): Flushing caches (mode 0)
D/phone ( 1774): updateImsRegRequiredState isImsRegRequired()=false
D/phone ( 1774): updateSmsOverImsState isSmsOverImsEnabled()=false
D/phone ( 1774): updateLteRamDumpState isLteRamDumpEnabled()=false
I/phone ( 1774): [RadioInfo] onResume: register phone & data intents
V/PhoneStatusBar( 1711): setLightsOn(true)
W/InputManagerService( 1636): Starting input on non-focused client [email protected] (uid=1000 pid=4988)
I/ActivityManager( 1636): Displayed com.android.settings/.RadioInfo: +479ms
D/OpenGLRenderer( 4988): Flushing caches (mode 1)
D/ConnectivityService( 1636): ConnectivityChange for mobile: DISCONNECTED/DISCONNECTED
D/ConnectivityService( 1636): Attempting to switch to WIFI
D/ConnectivityService( 1636): Attempting to switch to BLUETOOTH_TETHER
D/NetUtils( 1636): android_net_utils_resetConnections in env=0x18f9458 clazz=0x49f00001 iface=vsnet0 mask=0x3
D/ConnectivityService( 1636): resetConnections(vsnet0, 3)
W/Smack/Packet( 4250): notify conn break (IOEx), close connection
I/qtaguid ( 4250): Failed write_ctrl(u 89) res=-1 errno=22
I/qtaguid ( 4250): Untagging socket 89 failed errno=-22
W/NetworkManagementSocketTagger( 4250): untagSocket(89) failed with errno -22
D/ConnectivityService( 1636): handleInetConditionChange: no active default network - ignore
D/OpenGLRenderer( 4988): Flushing caches (mode 2)
D/OpenGLRenderer( 4988): Flushing caches (mode 0)
D/CAT ( 1774): CatService: ril message arrived
D/CAT ( 1774): CatService: SESSION END
D/StatusBar.NetworkController( 1711): updateTelephonySignalStrength: mSignalStrength == 7(GSM) 16(CDMA)
W/NvAudioDevice( 1115): @@(Device.cpp-hal)@@ setOutputMute(mute=1)
D/Tethering( 1636): MasterInitialState.processMessage what=3
D/StatusBar.NetworkController( 1711): updateTelephonySignalStrength: mSignalStrength == 7(GSM) 16(CDMA)
I/ActivityManager( 1636): Start proc com.miui.backup for broadcast com.miui.backup/com.miui.milk.auto.AutoBackupReceiver: pid=5061 uid=9800 gids={1015, 3003}
I/ActivityManager( 1636): Start proc com.cyanogenmod.stats for broadcast com.cyanogenmod.stats/.ReportingServiceManager: pid=5076 uid=10030 gids={3003}
I/dalvikvm( 5076): Turning on JNI app bug workarounds for target SDK version 10...
D/CMStats ( 5076): CONNECTIVITY_ACTION: noConnectivity = true
V/PushService( 4699): onStart() with intent.Action = com.xiaomi.xmsf.push.network_status_changed
E/PushService( 4699): no network, disconnect!
D/AlarmManagerService( 1636): Kernel timezone updated to -120 minutes west of GMT
D/SystemClock( 1774): Setting time of day to sec=1344025625
V/PhoneStatusBar( 1711): setLightsOn(true)
V/PhoneStatusBar( 1711): setLightsOn(true)
W/ActivityManager( 1636): Timeout of broadcast BroadcastRecord{41d24880 com.android.internal.telephony.gprs-reconnect.0} - [email protected], started 10002ms ago
W/ActivityManager( 1636): Receiver during timeout: BroadcastFilter{4151aa48 ReceiverList{41747ca8 1774 com.android.phone/1001 remote:4176c848}}
I/Process ( 1636): Sending signal. PID: 1774 SIG: 3
I/dalvikvm( 1774): threadid=3: reacting to signal 3
I/dalvikvm( 1774): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1636): Sending signal. PID: 1636 SIG: 3
I/dalvikvm( 1636): threadid=3: reacting to signal 3
I/dalvikvm( 1636): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1636): Sending signal. PID: 1711 SIG: 3
I/dalvikvm( 1711): threadid=3: reacting to signal 3
I/dalvikvm( 1711): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1636): Sending signal. PID: 1783 SIG: 3
I/dalvikvm( 1783): threadid=3: reacting to signal 3
I/dalvikvm( 1783): Wrote stack traces to '/data/anr/traces.txt'
D/dalvikvm( 1636): JIT code cache reset in 4 ms (1048496 bytes 1/0)
D/dalvikvm( 1636): GC_CONCURRENT freed 2511K, 20% free 21232K/26503K, paused 4ms+15ms
D/dalvikvm( 1636): GC_EXPLICIT freed 682K, 20% free 21218K/26503K, paused 3ms+5ms
I/Process ( 1636): Sending signal. PID: 4250 SIG: 3
I/dalvikvm( 4250): threadid=3: reacting to signal 3
I/dalvikvm( 4250): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1636): Sending signal. PID: 4691 SIG: 3
I/dalvikvm( 4691): threadid=3: reacting to signal 3
I/dalvikvm( 4691): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1636): Sending signal. PID: 5061 SIG: 3
I/dalvikvm( 5061): threadid=3: reacting to signal 3
I/dalvikvm( 5061): Wrote stack traces to '/data/anr/traces.txt'
E/ActivityManager( 1636): ANR in com.android.phone
E/ActivityManager( 1636): Reason: Broadcast of Intent { act=com.android.internal.telephony.gprs-reconnect.0 flg=0x14 (has extras) }
E/ActivityManager( 1636): Load: 2.16 / 2.65 / 1.6
E/ActivityManager( 1636): CPU usage from 10030ms to 0ms ago:
E/ActivityManager( 1636): 5.9% 1636/system_server: 4% user + 1.8% kernel / faults: 249 minor 1 major
E/ActivityManager( 1636): 3% 353/ksmd: 0% user + 3% kernel
E/ActivityManager( 1636): 2.9% 1711/com.android.systemui: 2.6% user + 0.2% kernel / faults: 825 minor
E/ActivityManager( 1636): 1.1% 1112/surfaceflinger: 0.6% user + 0.4% kernel / faults: 1 minor
E/ActivityManager( 1636): 0.6% 335/cpufreq-dvfsd: 0% user + 0.6% kernel
E/ActivityManager( 1636): 0.2% 11/kworker/u:1: 0% user + 0.2% kernel
E/ActivityManager( 1636): 0.1% 545/tegra_touch_thr: 0% user + 0.1% kernel
E/ActivityManager( 1636): 0.1% 1107/nvrm_daemon: 0% user + 0.1% kernel
E/ActivityManager( 1636): 0.1% 4250/com.google.process.gapps: 0% user + 0% kernel / faults: 2 minor
E/ActivityManager( 1636): 0% 1052/mmcqd/2: 0% user + 0% kernel
E/ActivityManager( 1636): 0% 1710/motion: 0% user + 0% kernel
E/ActivityManager( 1636): 0% 4652/kworker/0:1: 0% user + 0% kernel
E/ActivityManager( 1636): 15% TOTAL: 7.9% user + 6.4% kernel + 0.3% iowait + 0.3% softirq
E/ActivityManager( 1636): CPU usage from 473ms to 993ms later:
E/ActivityManager( 1636): 7.5% 1636/system_server: 1.8% user + 5.6% kernel / faults: 43 minor
E/ActivityManager( 1636): 5.6% 1651/ActivityManager: 0% user + 5.6% kernel
E/ActivityManager( 1636): 1.8% 1643/Compiler: 0% user + 1.8% kernel
E/ActivityManager( 1636): 1.8% 1894/Binder Thread #: 0% user + 1.8% kernel
E/ActivityManager( 1636): 3.4% 353/ksmd: 0% user + 3.4% kernel
E/ActivityManager( 1636): 1.3% 1052/mmcqd/2: 0% user + 1.3% kernel
E/ActivityManager( 1636): 1.5% 4250/com.google.process.gapps: 1.5% user + 0% kernel / faults: 7 minor
E/ActivityManager( 1636): 1.5% 4250/e.process.gapps: 1.5% user + 0% kernel
E/ActivityManager( 1636): 1.5% 4268/MCS WorkerThrea: 1.5% user + 0% kernel
E/ActivityManager( 1636): 1.5% 4691/android.process.acore: 0% user + 1.5% kernel / faults: 16 minor
E/ActivityManager( 1636): 1.5% 4715/Binder Thread #: 0% user + 1.5% kernel
E/ActivityManager( 1636): 1.5% 5061/com.miui.backup: 1.5% user + 0% kernel / faults: 57 minor
E/ActivityManager( 1636): 92% TOTAL: 9.4% user + 15% kernel + 66% iowait + 1.8% softirq
V/PhoneStatusBar( 1711): setLightsOn(true)
W/ActivityManager( 1636): Force finishing activity com.android.settings/.RadioInfo
W/NvAudioDevice( 1115): @@(Device.cpp-hal)@@ setOutputMute(force unmute)
D/ ( 1107): @@(WM8994)@@ ACWM8994SetPowerMode(), CurrPowerMode = 1, PowerMode = 1
I/ActivityManager( 1636): Killing ProcessRecord{416eceb0 1774:com.android.phone/1001}: user's request
W/InputDispatcher( 1636): channel '422ae660 com.android.settings/com.android.settings.RadioInfo (server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 1636): channel '422ae660 com.android.settings/com.android.settings.RadioInfo (server)' ~ Channel is unrecoverably broken and will be disposed!
I/ActivityManager( 1636): Process com.android.phone (pid 1774) has died.
W/ActivityManager( 1636): Scheduling restart of crashed service com.android.stk/.StkAppService in 5000ms
W/ActivityManager( 1636): Scheduling restart of crashed service com.android.phone/.MiuiBluetoothHeadsetService in 15000ms
W/InputDispatcher( 1636): Attempted to unregister already unregistered input channel '422ae660 com.android.settings/com.android.settings.RadioInfo (server)'
I/WindowManager( 1636): WIN DEATH: Window{422ae660 com.android.settings/com.android.settings.RadioInfo paused=true}
D/LBE-Sec ( 2033): Service lbesec.loader.com.android.phone is dead
I/ServiceManager( 1104): service 'sip' died
I/ServiceManager( 1104): service 'simphonebook' died
I/ServiceManager( 1104): service 'isms' died
I/ServiceManager( 1104): service 'phone' died
I/ServiceManager( 1104): service 'iphonesubinfo' died
I/WindowManager( 1636): WINDOW DIED Window{422ae660 com.android.settings/com.android.settings.RadioInfo paused=true}
D/LBE-Sec ( 2033): Unable to locate com.android.phone, retry in 5 seconds
I/ActivityManager( 1636): Start proc com.android.phone for restart com.android.phone: pid=5110 uid=1001 gids={3002, 3001, 3003, 1015}
V/PhoneStatusBar( 1711): setLightsOn(true)
I/ActivityManager( 1636): Start proc com.android.calendar for broadcast com.android.calendar/.widget.CalendarAppWidgetService$CalendarFactory: pid=5122 uid=10006 gids={3003}
W/InputManagerService( 1636): Got RemoteException sending setActive(false) notification to pid 1774 uid 1001
I/ActivityThread( 5110): Pub telephony: com.android.providers.telephony.TelephonyProvider
W/TelephonyProvider( 5110): onCreate: confFile=/system/etc/apns-conf.xml oldCheckSum=-1
I/ActivityThread( 5110): Pub firewall: com.android.providers.telephony.FirewallProvider
I/ActivityThread( 5110): Pub mms: com.android.providers.telephony.MmsProvider
I/ActivityThread( 5122): Pub com.android.calendar.CalendarRecentSuggestionsProvider: com.android.calendar.CalendarRecentSuggestionsProvider
I/ActivityManager( 1636): Start proc com.android.providers.calendar for content provider com.android.providers.calendar/.CalendarProvider2: pid=5142 uid=10007 gids={3003, 1015}
D/MmsSmsDatabaseHelper( 5110): [MmsSmsDb] tableName: threads hasAutoIncrement: CREATE TABLE threads (_id INTEGER PRIMARY KEY AUTOINCREMENT,date INTEGER DEFAULT 0,message_count INTEGER DEFAULT 0,unread_count INTEGER DEFAULT 0,recipient_ids TEXT,snippet TEXT,snippet_cs INTEGER DEFAULT 0,read INTEGER DEFAULT 1,type INTEGER DEFAULT 0,error INTEGER DEFAULT 0,has_attachment INTEGER DEFAULT 0) result: true
D/MmsSmsDatabaseHelper( 5110): [MmsSmsDb] tableName: canonical_addresses hasAutoIncrement: CREATE TABLE canonical_addresses (_id INTEGER PRIMARY KEY AUTOINCREMENT,address TEXT) result: true
D/MmsSmsDatabaseHelper( 5110): [getWritableDatabase] hasAutoIncrementThreads: true hasAutoIncrementAddresses: true
I/ActivityThread( 5110): Pub sms: com.android.providers.telephony.SmsProvider
I/ActivityThread( 5110): Pub mms-sms: com.android.providers.telephony.MmsSmsProvider
I/ActivityThread( 5142): Pub com.android.calendar: com.android.providers.calendar.CalendarProvider2
I/ActivityThread( 5110): Pub icc: com.android.phone.MiuiIccProvider
D/ ( 5110): [ApnContext] set reason as dataEnabled, for type default,current state IDLE
D/ ( 5110): [ApnContext] set reason as dataEnabled, for type mms,current state IDLE
D/ ( 5110): [ApnContext] set reason as dataEnabled, for type supl,current state IDLE
D/ ( 5110): [ApnContext] set reason as dataEnabled, for type dun,current state IDLE
D/ ( 5110): [ApnContext] set reason as dataEnabled, for type hipri,current state IDLE
D/CAT ( 5110): CatService: Running CAT service. STK app installed:true
D/CAT ( 5110): CatService: NEW sInstance
D/CallManager( 5110): registerPhone(GSM Handler (com.android.internal.telephony.PhoneProxy) {41535fd8})
W/ActivityManager( 1636): Unable to start service Intent { act=com.android.ussd.IExtendedNetworkService }: not found
I/ActivityManager( 1636): Start proc com.android.deskclock for broadcast com.android.deskclock/.AlarmInitReceiver: pid=5187 uid=10013 gids={}
D/CAT ( 5110): CatService: SIM ready. Reporting STK service running now...
D/NetworkLocator( 4250): null cell state delivered
D/Bluetooth HSHFP( 5110): Starting BluetoothHeadsetService
D/CAT ( 5110): CatService: ril message arrived
D/CAT ( 5110): CatService: SESSION END
D/MccTable( 5110): updateMccMncConfiguration: mcc=232, mnc=10
D/MccTable( 5110): locale set to de_at
D/MccTable( 5110): WIFI_COUNTRY_CODE set to at
I/WifiService( 1636): WifiService trying to set country code to at with persist set to true
I/ActivityThread( 5187): Pub com.android.deskclock: com.android.deskclock.AlarmProvider
D/dalvikvm( 1636): GC_EXPLICIT freed 1775K, 21% free 21163K/26503K, paused 3ms+8ms
V/AlarmClock( 5187): AlarmInitReceiver finished
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
I/ActivityManager( 1636): START {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.miui.home/.launcher.Launcher} from pid 1636
D/PhoneStatusBar( 1711): disable: < expand icons alerts ticker system_info back home recent clock >
D/OpenGLRenderer( 4988): Flushing caches (mode 0)
V/PhoneStatusBar( 1711): setLightsOn(true)
D/OpenGLRenderer( 4988): Flushing caches (mode 1)
W/InputManagerService( 1636): Starting input on non-focused client [email protected] (uid=1000 pid=4988)
V/SipBroadcastReceiver( 5110): start auto registration
D/CAT ( 5110): CatService: Return current sInstance
I/CalendarProvider2( 5142): Sending notification intent: Intent { act=android.intent.action.PROVIDER_CHANGED dat=content://com.android.calendar }
W/ContentResolver( 5142): Failed to get type for: content://com.android.calendar (Unknown URL content://com.android.calendar)
D/CAT ( 5110): CatService: ril message arrived
D/CAT ( 5110): CatService: SESSION END
W/NvAudioDevice( 1115): @@(Device.cpp-hal)@@ setOutputMute(mute=1)
D/StatusBar.NetworkController( 1711): updateTelephonySignalStrength: mSignalStrength == 4(GSM) 16(CDMA)
D/LBE-Sec ( 2033): Injecting to com.android.phone at pid 5110
D/LBE-Sec ( 2033): Attached to process 5110, original registers
D/LBE-Sec ( 2033): Info: current register set:
D/LBE-Sec ( 2033): R0 =0xFFFFFFFC R1 =0xBEB664F8 R2 =0x00000010 R3 =0x000018F3
D/LBE-Sec ( 2033): R4 =0x0173B1F8 R5 =0x0173B20C R6 =0x00000000 R7 =0x000000FC
D/LBE-Sec ( 2033): R8 =0x00000000 R9 =0x00000014 R10=0x00000000 R11=0xBEB6668C
D/LBE-Sec ( 2033): R12=0x4013C264 SP =0xBEB664D0 LR =0x4013440B PC =0x40033520
D/LBE-Sec ( 2033): CPSR =0x20030010 Orig_R0 =0x00000027
D/LBE-Sec ( 2033): Allocated memory located at 0x50f7a000
D/LBE-Sec ( 2033): Info: new SP for inject code 0x50F7DC00
D/LBE-Sec ( 2033): Injected registers
D/LBE-Sec ( 2033): Info: current register set:
D/LBE-Sec ( 2033): R0 =0xFFFFFFFC R1 =0xBEB664F8 R2 =0x00000010 R3 =0x000018F3
D/LBE-Sec ( 2033): R4 =0x0173B1F8 R5 =0x0173B20C R6 =0x00000000 R7 =0x000000FC
D/LBE-Sec ( 2033): R8 =0x00000000 R9 =0x00000014 R10=0x00000000 R11=0xBEB6668C
D/LBE-Sec ( 2033): R12=0x4013C264 SP =0x50F7DC00 LR =0x4013440B PC =0x50F7DC00
D/LBE-Sec ( 2033): CPSR =0x20030010 Orig_R0 =0x00000027
I/LBE-Sec ( 5110): Successfully loaded from remote process 2033
D/LBE-Sec ( 1104): Added loader service lbesec.loader.com.android.phone, handle 74
I/LBE-Sec ( 5110): bootstrap loaded
D/LBE-Sec ( 2033): Done.
D/StatusBar.NetworkController( 1711): updateTelephonySignalStrength: mSignalStrength == 3(GSM) 16(CDMA)
V/PhoneStatusBar( 1711): setLightsOn(true)
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
D/SystemClock( 5110): Setting time of day to sec=1344025648
W/NvAudioDevice( 1115): @@(Device.cpp-hal)@@ setOutputMute(force unmute)
D/ ( 1107): @@(WM8994)@@ ACWM8994SetPowerMode(), CurrPowerMode = 1, PowerMode = 1
D/PhoneStatusBar( 1711): disable: < expand icons alerts ticker system_info back home recent clock >
D/OpenGLRenderer( 1802): Flushing caches (mode 1)
D/LBE-Sec ( 2033): Registered death notification for lbesec.loader.com.android.phone
D/LBE-Sec ( 2033): notification dead
D/LBE-Sec ( 2033): Injection success
D/OpenGLRenderer( 1802): Flushing caches (mode 0)
W/SurfaceTexture( 1112): freeAllBuffersExceptCurrentLocked called but mQueue is not empty
D/dalvikvm( 1802): GC_EXPLICIT freed 26K, 7% free 21448K/22855K, paused 2ms+33ms
W/InputManagerService( 1636): Starting input on non-focused client [email protected] (uid=10033 pid=1802)
V/PhoneStatusBar( 1711): setLightsOn(true)
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
D/LBE-Sec ( 1636): getcache uid=10055 pid=0 perm=6 map=0x00000000 action=0
D/ ( 5303): 10026 com.lbe.security.miui executing 0 /system/bin/sh
I/InputQueue-JNI( 4186): Sending finished signal for input channel '41705918 AtchDlg:org.jtb.alogcat/org.jtb.alogcat.LogActivity (client)' since it is being unregistered while an input message is still in progress.
I/InputQueue-JNI( 4186): Ignoring finish signal on channel that is no longer registered.
W/InputManagerService( 1636): Window already focused, ignoring focus gain of: [email protected]
*EDIT: oh, and com.android.phone dies
I hope the information was somewhat usefull
Cheers
Hi, for a month or more, my phone restarts when I unlock the screen using the fingerprint. This happens whether I am connected to Wi-Fi or data and in several locations. Also, in the Moto X4 of my wife the same thing happens. I have reset the factory settings and, after a few days, the error replay (10-15 restarts per day). I do not have the bootloader unlocked. Thanks for the help.
Any special app you two are using?
bookworth said:
Any special app you two are using?
Click to expand...
Click to collapse
No special application. Developer options error report shows the following on one of the restarts:
06-19 08:28:22.456 1000 20774 20872 I DisplayManagerService: Display device changed state: "Pantalla integrada", DOZE
06-19 08:28:22.734 1000 20774 20774 V FingerprintService: onAuthenticated(owner=com.android.systemui, id=-1112942340, gp=0)
06-19 08:28:22.743 1000 20774 20774 V FingerprintService: Done with client: com.android.systemui
06-19 08:28:22.744 1000 20774 20774 V FingerprintService: setNavigationState: false
06-19 08:28:22.744 1000 865 1090 I SFPerfTracer: triggers: (rate: 74:1905) (4157093 sw vsyncs) (0 skipped) (0:2687627 vsyncs) (24:6938019)
06-19 08:28:22.746 1000 20774 20774 D StatusBarManagerService: showing navigation bar...
06-19 08:28:22.751 1000 20774 31349 I PowerManagerService: Waking up from dozing (uid 10071)...
06-19 08:28:22.753 1000 20774 31349 I DreamManagerService: Leaving dreamland.
06-19 08:28:22.754 1000 20774 20870 I DreamManagerService: Performing gentle wake from dream.
06-19 08:28:22.754 1000 20774 20870 I DreamController: Stopping dream: name=ComponentInfo{com.motorola.motodisplay/com.motorola.motodisplay.DozeService}, isTest=false, canDoze=true, userId=0
06-19 08:28:22.793 1000 20774 20872 I DisplayManagerService: Display device changed state: "Pantalla integrada", ON
06-19 08:28:22.797 1000 20774 20844 E BatteryStatsService: no controller energy info supplied
06-19 08:28:22.849 1000 20774 20774 V FingerprintService: startAuthentication(com.android.systemui)
06-19 08:28:22.850 1000 20774 20774 V FingerprintService: starting client AuthenticationClient(com.android.systemui), initiatedByClient = true)
06-19 08:28:22.856 1000 20774 20844 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=578489247 mSleepTimeMs=17134 mIdleTimeMs=-51 mTxTimeMs[]=[161, 183, 251, 252, 0] mRxTimeMs=9706 mEnergyUsed=0}
06-19 08:28:22.856 1000 20774 20774 W FingerprintService: client com.android.systemui is authenticating...
06-19 08:28:22.871 wifi 20657 20657 I wificond: Pno scan stopped
06-19 08:28:22.983 1000 20774 20774 V FingerprintService: stop client com.android.systemui
06-19 08:28:23.034 1000 20774 20774 W FingerprintService: client com.android.systemui is no longer authenticating
06-19 08:28:23.043 1000 20774 20774 V FingerprintService: Done with client: com.android.systemui
06-19 08:28:23.043 1000 20774 20774 V FingerprintService: setNavigationState: true
06-19 08:28:23.044 1000 20774 20774 V FingerprintService: handleError(client=com.android.systemui, error = 5)
06-19 08:28:23.071 1000 20774 20992 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: TaskSnapshotPersister
06-19 08:28:23.071 1000 20774 20992 E AndroidRuntime: java.lang.IllegalArgumentException: width and height must be > 0
06-19 08:28:23.071 1000 20774 20992 E AndroidRuntime: at android.graphics.Bitmap.createBitmap(Bitmap.java:1027)
06-19 08:28:23.071 1000 20774 20992 E AndroidRuntime: at android.graphics.Bitmap.createBitmap(Bitmap.java:994)
06-19 08:28:23.071 1000 20774 20992 E AndroidRuntime: at android.graphics.Bitmap.createBitmap(Bitmap.java:944)
06-19 08:28:23.071 1000 20774 20992 E AndroidRuntime: at android.graphics.Bitmap.createBitmap(Bitmap.java:865)
06-19 08:28:23.071 1000 20774 20992 E AndroidRuntime: at android.graphics.Bitmap.createScaledBitmap(Bitmap.java:735)
06-19 08:28:23.071 1000 20774 20992 E AndroidRuntime: at com.android.server.wm.TaskSnapshotPersister$StoreWriteQueueItem.writeBuffer(TaskSnapshotPersister.java:329)
06-19 08:28:23.071 1000 20774 20992 E AndroidRuntime: at com.android.server.wm.TaskSnapshotPersister$StoreWriteQueueItem.write(TaskSnapshotPersister.java:292)
06-19 08:28:23.071 1000 20774 20992 E AndroidRuntime: at com.android.server.wm.TaskSnapshotPersister$1.run(TaskSnapshotPersister.java:226)
06-19 08:28:23.083 1000 20774 20840 I ActivityManager: moveHomeStack, setupComplete:true
06-19 08:28:23.305 10089 21028 21028 E AndroidRuntime: FATAL EXCEPTION: main
06-19 08:28:23.305 10089 21028 21028 E AndroidRuntime: Process: com.android.systemui, PID: 21028
06-19 08:28:23.305 10089 21028 21028 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
06-19 08:28:23.306 10095 22097 22097 E AndroidRuntime: FATAL EXCEPTION: main
06-19 08:28:23.306 10095 22097 22097 E AndroidRuntime: Process: com.google.android.googlequicksearchbox:search, PID: 22097
06-19 08:28:23.306 10095 22097 22097 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
06-19 08:28:23.308 10167 21900 21900 E AndroidRuntime: FATAL EXCEPTION: main
06-19 08:28:23.308 10167 21900 21900 E AndroidRuntime: Process: com.google.android.apps.nexuslauncher, PID: 21900
06-19 08:28:23.308 10167 21900 21900 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
06-19 08:28:23.310 radio 21209 21314 E AndroidRuntime: FATAL EXCEPTION: DcHandlerThread
06-19 08:28:23.310 radio 21209 21314 E AndroidRuntime: Process: com.android.phone, PID: 21209
06-19 08:28:23.310 radio 21209 21314 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
06-19 08:28:23.336 10144 23485 14630 E AndroidRuntime: FATAL EXCEPTION: IntentService[RowWidgetUpdater2]
06-19 08:28:23.336 10144 23485 14630 E AndroidRuntime: Process: com.motorola.timeweatherwidget, PID: 23485
06-19 08:28:23.336 10144 23485 14630 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
06-19 08:28:23.622 wifi 14667 14667 I wificond: wificond is starting up...
06-19 08:28:23.808 wifi 14667 14667 W wificond: No handler for scan result notification from interface with index: 24
I mean that if your and your wife's phone both show this behaviour then it is unlikely that the unit is faulty.
The bootloader is unlocked but have you flashed anything with these phones (root, anlther firmware)?
Do you have any apps installed that are your country specific and present in both phones? Some banking apps or anything that uses security features?
I think the problem is solved. For some reason, Yoosee app doesn't work right now with doze. I have uninstalled it and for 12 hours I haven't had any restarts. Thanks for your interest.
WIP: "De-bloating" the Chromecast with Google TV. Let's get rid of those ads!
Those who like the Chromecast with Google TV UI or wouldn't move a finger to change it can stop reading this thread and move onto something else. No need to leave any comment, xda-developers wasn't created for people who don't like a challenge
If you don't like the UI because the massive ads it brings, then you are welcome to keep reading and help if you can!
METHOD A (EASY) - GET RID OF THE ADS ON THE MAIN SCREEN WITH AN ALTERNATIVE LAUNCHER
Install ATV Launcher or Wolf Launcher and disable the default launcher via adb. If you find a nice wallpaper that's a good option.
METHOD B (HARD) - USE THE APPS ONLY MODE WITH GOOGLE ASSISTANT AND NO ADS
Go to Settings > Accounts & Sign-in > Select your ac**** > Enable "Apps only mode".
Now you removed 90% of the ads but it seems like Google doesn't want us to use the Apps only mode, so they decided to put some hurdles in place disabling google assistant and play store access . We can fix it partially, so keep reading
Get a shortcut to the Google Play Store
Sideload and install this app (created with this site) and now you'll be able to access Google Play Store opening the app even on Apps Only Mode (see here how it looks)
How to use Google Assistant even on Apps Only mode - WIP
Go to Settings > All Apps > "See All apps" > "Show System apps" > Google > click on "Uninstall Updates" & "Disable". Now sideload and install this version
Now you can use Google Assistant to open a YouTube video or ask questions such as "what's the weather today?", but you can't give a voice command to open an app... It will go through a loop trying to setup google assistant.
Get rid of the 3 shows/movies ads that you still get in screen even when Apps Only mode is enabled - WIP
I tried disabling some apps that came pre-installed but I didn't manage to get rid of those last ads. I guess it's integrated within the launcher so we might need to mod it (if possible), live with it or just go back to Option 1 and use a different launcher.
Any help would be appreciated
METHOD C (HARD) - SWITCH TO THE ORIGINAL ANDROID TV LAUNCHER
I disabled the Google TV Launcher com.google.android.apps.tv.launcherx via adb. Then I sideloaded the Android TV Home and Lenback Launcher apks and tried to launch the main activity of those apps but it didn't work. Some activities could be launched but not the main one.
Any help would be highly appreciated as that's what I really wanted to do.
titooo7 said:
METHOD C (HARD) - SWITCH TO THE ORIGINAL ANDROID TV LAUNCHER
I disabled the Google TV Launcher com.google.android.apps.tv.launcherx via adb. Then I sideloaded the Android TV Home and Lenback Launcher apks and tried to launch the main activity of those apps but it didn't work. Some activities could be launched but not the main one.
Any help would be highly appreciated as that's what I really wanted to do.
Click to expand...
Click to collapse
This would be the ideal solution.
The funny thing I notice about this one, however, is that it actually appears to already be installed.
On play store, there are two versions of launcher. The "original":
https://play.google.com/store/apps/details?id=com.google.android.tvlauncher
And "too much advertising":
https://play.google.com/store/apps/details?id=com.google.android.apps.tv.launcherx
But what is interesting about them, is that the original one is apparently already installed on ALL of my Sabrina dongles, as well as on all of my other Android TV devices. The "too much advertising" reports as being installed on the Sabrina dongles, but as incompatible with all of the others.
It seems odd that the original launcher would fail to load while 3rd party launchers would work. I wonder if the packages are somehow being blacklisted?
96carboard said:
But what is interesting about them, is that the original one is apparently already installed on ALL of my Sabrina dongles, as well as on all of my other Android TV devices. The "too much advertising" reports as being installed on the Sabrina dongles, but as incompatible with all of the others.
It seems odd that the original launcher would fail to load while 3rd party launchers would work. I wonder if the packages are somehow being blacklisted?
Click to expand...
Click to collapse
I might be wrong, but I'd swear the original launcher wasn't preinstalled.
In any case if you sideload a shortcut maker then you can launch several activities from the original launcher, but not the main one.
I'm wondering if that could be because I'm missing some other apks that the original launcher need... but it's been a long time since I tried to do "dev" stuff in Android to remember how to diagnose the problem correctly.
titooo7 said:
I might be wrong, but I'd swear the original launcher wasn't preinstalled.
In any case if you sideload a shortcut maker then you can launch several activities from the original launcher, but not the main one.
Click to expand...
Click to collapse
To be a little more precise, I haven't actually checked on the devices themselves, but rather play store *claims* that they're installed.
I'm wondering if that could be because I'm missing some other apks that the original launcher need... but it's been a long time since I tried to do "dev" stuff in Android to remember how to diagnose the problem correctly.
Click to expand...
Click to collapse
If you're missing something it depends on, I'd expect some kind of related crash to be pretty obvious in the logcat.
What's the output of this?
pm query-activities -a android.intent.action.MAIN -c android.intent.category.HOME
96carboard said:
If you're missing something it depends on, I'd expect some kind of related crash to be pretty obvious in the logcat.
What's the output of this?
pm query-activities -a android.intent.action.MAIN -c android.intent.category.HOME
Click to expand...
Click to collapse
Just for your information I sideloadet the following 3 apks as those are installed on my Shield TV (which I don't have access to at the moment, btw) and I thought it mgiht be needed:
com.google.android.tvlauncher 2.2.2-328601804
com.google.android.leanbacklauncher 90.11.5-100-444-948
com.google.android.tvrecommendations 2.2.1-32444148
Unfortunately I couldn't find the apk for the following two, (I wonder if that's why I can't get the original launcher to work):
com.google.android.leanbacklauncher.recommendations 90.1.2.-100-4013131
Anyway, after that I ran the adb command you mentioned in two different ways:
With launcherx (CC GTV launcher) disabled: (pm disable com.google.android.apps.tv.launcherx)
Code:
pm query-activities -a android.intent.action.MAIN -c android.intent.category.HOME
4 activities found:
Activity #0:
priority=1 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=true
ActivityInfo:
name=com.google.android.tungsten.setupwraith.RecoveryActivity
packageName=com.google.android.tungsten.setupwraith
labelRes=0x7f110043 nonLocalizedLabel=null icon=0x0 banner=0x0
enabled=false exported=true directBootAware=false
taskAffinity=com.google.android.tungsten.setupwraith targetActivity=null persistableMode=PERSIST_ROOT_ONLY
launchMode=1 flags=0x220 privateFlags=0x0 theme=0x7f1201e6
screenOrientation=-1 configChanges=0x3 softInputMode=0x0
lockTaskLaunchMode=LOCK_TASK_LAUNCH_MODE_DEFAULT
resizeMode=RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION
ApplicationInfo:
packageName=com.google.android.tungsten.setupwraith
labelRes=0x7f110043 nonLocalizedLabel=null icon=0x0 banner=0x0
processName=com.google.android.tungsten.setupwraith
taskAffinity=com.google.android.tungsten.setupwraith
uid=10035 flags=0x38c83e45 privateFlags=0x24081108 theme=0x7f1201fb
requiresSmallestWidthDp=0 compatibleWidthLimitDp=0 largestWidthLimitDp=0
sourceDir=/product/priv-app/SetupWraithPrebuiltSabrina/SetupWraithPrebuiltSabrina.apk
seinfo=default:privapp:targetSdkVersion=28
seinfoUser=:complete
dataDir=/data/user/0/com.google.android.tungsten.setupwraith
deviceProtectedDataDir=/data/user_de/0/com.google.android.tungsten.setupwraith
credentialProtectedDataDir=/data/user/0/com.google.android.tungsten.setupwraith
enabled=true minSdkVersion=28 targetSdkVersion=28 versionCode=2018111433 targetSandboxVersion=1
supportsRtl=true
fullBackupContent=true
HiddenApiEnforcementPolicy=0
usesNonSdkApi=false
allowsPlaybackCapture=false
Activity #1:
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=true
ActivityInfo:
name=com.google.android.leanbacklauncher.MainActivity
packageName=com.google.android.leanbacklauncher
labelRes=0x7f0a0013 nonLocalizedLabel=null icon=0x0 banner=0x0
enabled=true exported=true directBootAware=false
taskAffinity=com.google.android.leanbacklauncher targetActivity=null persistableMode=PERSIST_ROOT_ONLY
launchMode=2 flags=0x234 privateFlags=0x0 theme=0x0
screenOrientation=0 configChanges=0xf3 softInputMode=0x0
lockTaskLaunchMode=LOCK_TASK_LAUNCH_MODE_DEFAULT
resizeMode=RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION
ApplicationInfo:
name=com.google.android.leanbacklauncher.LauncherApplication
packageName=com.google.android.leanbacklauncher
labelRes=0x7f0a0014 nonLocalizedLabel=null icon=0x7f020095 banner=0x0
className=com.google.android.leanbacklauncher.LauncherApplication
processName=com.google.android.leanbacklauncher
taskAffinity=com.google.android.leanbacklauncher
uid=10096 flags=0x38c8be44 privateFlags=0x24001000 theme=0x7f0c00d7
requiresSmallestWidthDp=0 compatibleWidthLimitDp=0 largestWidthLimitDp=0
sourceDir=/data/app/com.google.android.leanbacklauncher-hX6rlapmfhRj8H_uIDOWAg==/base.apk
seinfo=default:targetSdkVersion=24
seinfoUser=:complete
dataDir=/data/user/0/com.google.android.leanbacklauncher
deviceProtectedDataDir=/data/user_de/0/com.google.android.leanbacklauncher
credentialProtectedDataDir=/data/user/0/com.google.android.leanbacklauncher
enabled=true minSdkVersion=21 targetSdkVersion=24 versionCode=1011102100 targetSandboxVersion=1
supportsRtl=true
fullBackupContent=true
HiddenApiEnforcementPolicy=2
usesNonSdkApi=false
allowsPlaybackCapture=false
Activity #2:
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=true
ActivityInfo:
name=com.google.android.tvlauncher.MainActivity
packageName=com.google.android.tvlauncher
enabled=true exported=true directBootAware=false
taskAffinity=.TvLauncher targetActivity=null persistableMode=PERSIST_ROOT_ONLY
launchMode=2 flags=0x230 privateFlags=0x0 theme=0x0
screenOrientation=0 configChanges=0x3 softInputMode=0x0
lockTaskLaunchMode=LOCK_TASK_LAUNCH_MODE_DEFAULT
resizeMode=RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION
ApplicationInfo:
name=com.google.android.tvlauncher.application.TvLauncherApplication
packageName=com.google.android.tvlauncher
labelRes=0x7f120029 nonLocalizedLabel=null icon=0x7f0f0000 banner=0x7f08012d
className=com.google.android.tvlauncher.application.TvLauncherApplication
processName=com.google.android.tvlauncher
taskAffinity=com.google.android.tvlauncher
uid=10097 flags=0x38c83e44 privateFlags=0xc001000 theme=0x7f130007
requiresSmallestWidthDp=0 compatibleWidthLimitDp=0 largestWidthLimitDp=0
sourceDir=/data/app/com.google.android.tvlauncher-f03AUa5fOy1TItsfaki7Iw==/base.apk
seinfo=default:targetSdkVersion=29
seinfoUser=:complete
dataDir=/data/user/0/com.google.android.tvlauncher
deviceProtectedDataDir=/data/user_de/0/com.google.android.tvlauncher
credentialProtectedDataDir=/data/user/0/com.google.android.tvlauncher
enabled=true minSdkVersion=26 targetSdkVersion=29 versionCode=1010900817 targetSandboxVersion=1
supportsRtl=true
fullBackupContent=true
HiddenApiEnforcementPolicy=2
usesNonSdkApi=false
allowsPlaybackCapture=true
Activity #3:
priority=-1000 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=true
ActivityInfo:
name=com.android.tv.settings.system.FallbackHome
packageName=com.android.tv.settings
enabled=true exported=true directBootAware=true
taskAffinity=com.android.tv.settings targetActivity=null persistableMode=PERSIST_ROOT_ONLY
launchMode=0 flags=0x220 privateFlags=0x0 theme=0x7f1100c0
screenOrientation=-1 configChanges=0x40002ff7 softInputMode=0x0
lockTaskLaunchMode=LOCK_TASK_LAUNCH_MODE_DEFAULT
resizeMode=RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION
ApplicationInfo:
packageName=com.android.tv.settings
labelRes=0x7f100366 nonLocalizedLabel=null icon=0x7f080201 banner=0x7f0800e0
processName=com.android.tv.settings
taskAffinity=com.android.tv.settings
uid=1000 flags=0x28c8be45 privateFlags=0xc501068 theme=0x7f1101d2
requiresSmallestWidthDp=0 compatibleWidthLimitDp=0 largestWidthLimitDp=0
sourceDir=/system/priv-app/TvSettingsGoogle/TvSettingsGoogle.apk
resourceDirs=[/vendor/overlay/ChromecastTvSettingsGoogleOverlay.apk]
seinfo=platform:privapp:targetSdkVersion=28
seinfoUser=:complete
dataDir=/data/user_de/0/com.android.tv.settings
deviceProtectedDataDir=/data/user_de/0/com.android.tv.settings
credentialProtectedDataDir=/data/user/0/com.android.tv.settings
enabled=true minSdkVersion=29 targetSdkVersion=29 versionCode=1 targetSandboxVersion=1
supportsRtl=true
fullBackupContent=true
HiddenApiEnforcementPolicy=0
usesNonSdkApi=true
allowsPlaybackCapture=true
With launcherx enabled:
Code:
sabrina:/ $ pm query-activities -a android.intent.action.MAIN -c android.intent.category.HOME
5 activities found:
Activity #0:
priority=2 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=true
ActivityInfo:
name=com.google.android.apps.tv.launcherx.home.HomeActivity
packageName=com.google.android.apps.tv.launcherx
labelRes=0x7f13025a nonLocalizedLabel=null icon=0x0 banner=0x0
enabled=true exported=true directBootAware=false
taskAffinity=com.google.android.apps.tv.launcherx targetActivity=null persistableMode=PERSIST_ROOT_ONLY
launchMode=2 flags=0x230 privateFlags=0x0 theme=0x7f1401cc
screenOrientation=-1 configChanges=0x3 softInputMode=0x0
lockTaskLaunchMode=LOCK_TASK_LAUNCH_MODE_DEFAULT
resizeMode=RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION
ApplicationInfo:
name=com.google.android.apps.tv.launcherx.LauncherX_Application
packageName=com.google.android.apps.tv.launcherx
labelRes=0x7f1302c0 nonLocalizedLabel=null icon=0x7f0f0001 banner=0x7f0801b0
className=com.google.android.apps.tv.launcherx.LauncherX_Application
processName=com.google.android.apps.tv.launcherx
taskAffinity=com.google.android.apps.tv.launcherx
uid=10037 flags=0x38c83ec5 privateFlags=0xc081018 theme=0x7f14000e
requiresSmallestWidthDp=0 compatibleWidthLimitDp=0 largestWidthLimitDp=0
sourceDir=/data/app/com.google.android.apps.tv.launcherx-eKBpKZxlpw3mSx4rrG8L3w==/base.apk
seinfo=default:privapp:targetSdkVersion=29
seinfoUser=:complete
dataDir=/data/user/0/com.google.android.apps.tv.launcherx
deviceProtectedDataDir=/data/user_de/0/com.google.android.apps.tv.launcherx
credentialProtectedDataDir=/data/user/0/com.google.android.apps.tv.launcherx
enabled=true minSdkVersion=28 targetSdkVersion=29 versionCode=5244 targetSandboxVersion=1
supportsRtl=true
fullBackupContent=true
networkSecurityConfigRes=0x7f170003
category=7
HiddenApiEnforcementPolicy=2
usesNonSdkApi=false
allowsPlaybackCapture=true
Activity #1:
priority=1 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=true
ActivityInfo:
name=com.google.android.tungsten.setupwraith.RecoveryActivity
packageName=com.google.android.tungsten.setupwraith
labelRes=0x7f110043 nonLocalizedLabel=null icon=0x0 banner=0x0
enabled=false exported=true directBootAware=false
taskAffinity=com.google.android.tungsten.setupwraith targetActivity=null persistableMode=PERSIST_ROOT_ONLY
launchMode=1 flags=0x220 privateFlags=0x0 theme=0x7f1201e6
screenOrientation=-1 configChanges=0x3 softInputMode=0x0
lockTaskLaunchMode=LOCK_TASK_LAUNCH_MODE_DEFAULT
resizeMode=RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION
ApplicationInfo:
packageName=com.google.android.tungsten.setupwraith
labelRes=0x7f110043 nonLocalizedLabel=null icon=0x0 banner=0x0
processName=com.google.android.tungsten.setupwraith
taskAffinity=com.google.android.tungsten.setupwraith
uid=10035 flags=0x38c83e45 privateFlags=0x24081108 theme=0x7f1201fb
requiresSmallestWidthDp=0 compatibleWidthLimitDp=0 largestWidthLimitDp=0
sourceDir=/product/priv-app/SetupWraithPrebuiltSabrina/SetupWraithPrebuiltSabrina.apk
seinfo=default:privapp:targetSdkVersion=28
seinfoUser=:complete
dataDir=/data/user/0/com.google.android.tungsten.setupwraith
deviceProtectedDataDir=/data/user_de/0/com.google.android.tungsten.setupwraith
credentialProtectedDataDir=/data/user/0/com.google.android.tungsten.setupwraith
enabled=true minSdkVersion=28 targetSdkVersion=28 versionCode=2018111433 targetSandboxVersion=1
supportsRtl=true
fullBackupContent=true
HiddenApiEnforcementPolicy=0
usesNonSdkApi=false
allowsPlaybackCapture=false
Activity #2:
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=true
ActivityInfo:
name=com.google.android.leanbacklauncher.MainActivity
packageName=com.google.android.leanbacklauncher
labelRes=0x7f0a0013 nonLocalizedLabel=null icon=0x0 banner=0x0
enabled=true exported=true directBootAware=false
taskAffinity=com.google.android.leanbacklauncher targetActivity=null persistableMode=PERSIST_ROOT_ONLY
launchMode=2 flags=0x234 privateFlags=0x0 theme=0x0
screenOrientation=0 configChanges=0xf3 softInputMode=0x0
lockTaskLaunchMode=LOCK_TASK_LAUNCH_MODE_DEFAULT
resizeMode=RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION
ApplicationInfo:
name=com.google.android.leanbacklauncher.LauncherApplication
packageName=com.google.android.leanbacklauncher
labelRes=0x7f0a0014 nonLocalizedLabel=null icon=0x7f020095 banner=0x0
className=com.google.android.leanbacklauncher.LauncherApplication
processName=com.google.android.leanbacklauncher
taskAffinity=com.google.android.leanbacklauncher
uid=10096 flags=0x38c8be44 privateFlags=0x24001000 theme=0x7f0c00d7
requiresSmallestWidthDp=0 compatibleWidthLimitDp=0 largestWidthLimitDp=0
sourceDir=/data/app/com.google.android.leanbacklauncher-hX6rlapmfhRj8H_uIDOWAg==/base.apk
seinfo=default:targetSdkVersion=24
seinfoUser=:complete
dataDir=/data/user/0/com.google.android.leanbacklauncher
deviceProtectedDataDir=/data/user_de/0/com.google.android.leanbacklauncher
credentialProtectedDataDir=/data/user/0/com.google.android.leanbacklauncher
enabled=true minSdkVersion=21 targetSdkVersion=24 versionCode=1011102100 targetSandboxVersion=1
supportsRtl=true
fullBackupContent=true
HiddenApiEnforcementPolicy=2
usesNonSdkApi=false
allowsPlaybackCapture=false
Activity #3:
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=true
ActivityInfo:
name=com.google.android.tvlauncher.MainActivity
packageName=com.google.android.tvlauncher
enabled=true exported=true directBootAware=false
taskAffinity=.TvLauncher targetActivity=null persistableMode=PERSIST_ROOT_ONLY
launchMode=2 flags=0x230 privateFlags=0x0 theme=0x0
screenOrientation=0 configChanges=0x3 softInputMode=0x0
lockTaskLaunchMode=LOCK_TASK_LAUNCH_MODE_DEFAULT
resizeMode=RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION
ApplicationInfo:
name=com.google.android.tvlauncher.application.TvLauncherApplication
packageName=com.google.android.tvlauncher
labelRes=0x7f120029 nonLocalizedLabel=null icon=0x7f0f0000 banner=0x7f08012d
className=com.google.android.tvlauncher.application.TvLauncherApplication
processName=com.google.android.tvlauncher
taskAffinity=com.google.android.tvlauncher
uid=10097 flags=0x38c83e44 privateFlags=0xc001000 theme=0x7f130007
requiresSmallestWidthDp=0 compatibleWidthLimitDp=0 largestWidthLimitDp=0
sourceDir=/data/app/com.google.android.tvlauncher-f03AUa5fOy1TItsfaki7Iw==/base.apk
seinfo=default:targetSdkVersion=29
seinfoUser=:complete
dataDir=/data/user/0/com.google.android.tvlauncher
deviceProtectedDataDir=/data/user_de/0/com.google.android.tvlauncher
credentialProtectedDataDir=/data/user/0/com.google.android.tvlauncher
enabled=true minSdkVersion=26 targetSdkVersion=29 versionCode=1010900817 targetSandboxVersion=1
supportsRtl=true
fullBackupContent=true
HiddenApiEnforcementPolicy=2
usesNonSdkApi=false
allowsPlaybackCapture=true
Activity #4:
priority=-1000 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=true
ActivityInfo:
name=com.android.tv.settings.system.FallbackHome
packageName=com.android.tv.settings
enabled=true exported=true directBootAware=true
taskAffinity=com.android.tv.settings targetActivity=null persistableMode=PERSIST_ROOT_ONLY
launchMode=0 flags=0x220 privateFlags=0x0 theme=0x7f1100c0
screenOrientation=-1 configChanges=0x40002ff7 softInputMode=0x0
lockTaskLaunchMode=LOCK_TASK_LAUNCH_MODE_DEFAULT
resizeMode=RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION
ApplicationInfo:
packageName=com.android.tv.settings
labelRes=0x7f100366 nonLocalizedLabel=null icon=0x7f080201 banner=0x7f0800e0
processName=com.android.tv.settings
taskAffinity=com.android.tv.settings
uid=1000 flags=0x28c8be45 privateFlags=0xc501068 theme=0x7f1101d2
requiresSmallestWidthDp=0 compatibleWidthLimitDp=0 largestWidthLimitDp=0
sourceDir=/system/priv-app/TvSettingsGoogle/TvSettingsGoogle.apk
resourceDirs=[/vendor/overlay/ChromecastTvSettingsGoogleOverlay.apk]
seinfo=platform:privapp:targetSdkVersion=28
seinfoUser=:complete
dataDir=/data/user_de/0/com.android.tv.settings
deviceProtectedDataDir=/data/user_de/0/com.android.tv.settings
credentialProtectedDataDir=/data/user/0/com.android.tv.settings
enabled=true minSdkVersion=29 targetSdkVersion=29 versionCode=1 targetSandboxVersion=1
supportsRtl=true
fullBackupContent=true
HiddenApiEnforcementPolicy=0
usesNonSdkApi=true
allowsPlaybackCapture=true
@titooo7 I'm only getting to messing with this now. (unplugged my Shield as it was the only way to actually start using the CC GTV)
Did you manage to get the vanilla AOSP ATV launcher working?
Has anyone got to the bottom of this ? Ability to lunch the original android tv luncher would be really nice.
I tried myself by installing android tv launcher, android tv services as well as leanback launcher using play store (no need for side loading)...
then tried lunching it by
Code:
am start -n "com.google.android.tvlauncher/com.google.android.tvlauncher.MainActivity" -a android.intent.action.MAIN -c android.intent.category.HOME
It seems to be lunching but it seems to gets killed instantly.
Logcat.
Code:
11-01 02:07:56.898 3840 4772 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.google.android.tvlauncher/.MainActivity} from uid 2000
11-01 02:07:56.951 3840 3869 I ActivityManager: Start proc 22253:com.google.android.tvlauncher/u0a87 for activity {com.google.android.tvlauncher/com.google.android.tvlauncher.MainActivity}
11-01 02:07:57.171 3552 3588 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{aaac495 token=Token{9f8fc4c ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t175}}})/@0xcaf715a - animation-leash#0
11-01 02:07:57.171 3552 3588 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{aaac495 token=Token{9f8fc4c ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t175}}})/@0xcaf715a - animation-bounds#0
11-01 02:07:57.171 3552 3588 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{aaac495 token=Token{9f8fc4c ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t175}}})/@0xcaf715a - animation-leash#0
11-01 02:07:57.172 3552 3588 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{aaac495 token=Token{9f8fc4c ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t175}}})/@0xcaf715a - animation-bounds#0
11-01 02:07:57.185 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: Surface(name=AppWindowToken{aaac495 token=Token{9f8fc4c ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t175}}})/@0xcaf715a - animation-bounds#0
11-01 02:07:57.185 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: Surface(name=AppWindowToken{aaac495 token=Token{9f8fc4c ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t175}}})/@0xcaf715a - animation-leash#0
11-01 02:07:57.185 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: Surface(name=AppWindowToken{aaac495 token=Token{9f8fc4c ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t175}}})/@0xcaf715a - animation-leash#0
11-01 02:07:57.185 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: Surface(name=AppWindowToken{aaac495 token=Token{9f8fc4c ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t175}}})/@0xcaf715a - animation-bounds#0
11-01 02:07:57.233 22253 22300 E AndroidRuntime: Process: com.google.android.tvlauncher, PID: 22253
11-01 02:07:57.248 3840 3856 W ActivityTaskManager: Force finishing activity com.google.android.tvlauncher/.MainActivity
11-01 02:07:57.314 3840 4772 I ActivityManager: Process com.google.android.tvlauncher (pid 22253) has died: vis TOP
11-01 02:07:57.315 3552 4208 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Splash Screen com.google.android.tvlauncher#0
11-01 02:07:57.317 3552 4208 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: ae75549 Splash Screen com.google.android.tvlauncher#0
11-01 02:07:57.318 3552 4208 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: ae75549 Splash Screen com.google.android.tvlauncher#0
11-01 02:07:57.318 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: ae75549 Splash Screen com.google.android.tvlauncher#0
11-01 02:07:57.318 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: Splash Screen com.google.android.tvlauncher#0
11-01 02:07:57.318 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: Splash Screen com.google.android.tvlauncher#0
11-01 02:07:57.318 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: ae75549 Splash Screen com.google.android.tvlauncher#0
11-01 02:07:57.320 3552 4208 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: AppWindowToken{aaac495 token=Token{9f8fc4c ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t175}}}#0
11-01 02:07:57.321 3552 4208 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: AppWindowToken{aaac495 token=Token{9f8fc4c ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t175}}}#0
11-01 02:07:57.327 3552 4339 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Splash Screen com.google.android.tvlauncher#0
11-01 02:07:57.335 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: AppWindowToken{aaac495 token=Token{9f8fc4c ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t175}}}#0
11-01 02:07:57.335 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: Splash Screen com.google.android.tvlauncher#0
11-01 02:07:57.335 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: AppWindowToken{aaac495 token=Token{9f8fc4c ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t175}}}#0
11-01 02:07:57.749 3840 3861 W ActivityTaskManager: Activity top resumed state loss timeout for ActivityRecord{638f47f u0 com.google.android.tvlauncher/.MainActivity t-1 f}
11-01 02:09:39.384 3840 3856 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.google.android.tvlauncher/.MainActivity} from uid 2000
11-01 02:09:39.429 3840 3869 I ActivityManager: Start proc 22323:com.google.android.tvlauncher/u0a87 for activity {com.google.android.tvlauncher/com.google.android.tvlauncher.MainActivity}
11-01 02:09:39.673 3552 4339 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}})/@0x9d7a9e9 - animation-leash#0
11-01 02:09:39.673 3552 4339 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}})/@0x9d7a9e9 - animation-bounds#0
11-01 02:09:39.673 3552 4339 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}})/@0x9d7a9e9 - animation-leash#0
11-01 02:09:39.675 3552 3831 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}})/@0x9d7a9e9 - animation-leash#0
11-01 02:09:39.675 3552 4339 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}})/@0x9d7a9e9 - animation-bounds#0
11-01 02:09:39.687 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: Surface(name=AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}})/@0x9d7a9e9 - animation-bounds#0
11-01 02:09:39.687 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: Surface(name=AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}})/@0x9d7a9e9 - animation-leash#0
11-01 02:09:39.687 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: Surface(name=AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}})/@0x9d7a9e9 - animation-leash#0
11-01 02:09:39.687 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: Surface(name=AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}})/@0x9d7a9e9 - animation-bounds#0
11-01 02:09:39.706 22323 22370 E AndroidRuntime: Process: com.google.android.tvlauncher, PID: 22323
11-01 02:09:39.723 3840 4772 W ActivityTaskManager: Force finishing activity com.google.android.tvlauncher/.MainActivity
11-01 02:09:39.769 3840 7719 I ActivityManager: Process com.google.android.tvlauncher (pid 22323) has died: vis TOP
11-01 02:09:39.772 3552 3588 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Splash Screen com.google.android.tvlauncher#0
11-01 02:09:39.774 3552 3588 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: 1c63bed Splash Screen com.google.android.tvlauncher#0
11-01 02:09:39.774 3552 3588 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: 1c63bed Splash Screen com.google.android.tvlauncher#0
11-01 02:09:39.776 3552 3588 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}}#0
11-01 02:09:39.776 3552 3588 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}}#0
11-01 02:09:39.777 3552 3588 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}}#0
11-01 02:09:39.782 3552 4339 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Splash Screen com.google.android.tvlauncher#0
11-01 02:09:39.787 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}}#0
11-01 02:09:39.787 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: 1c63bed Splash Screen com.google.android.tvlauncher#0
11-01 02:09:39.787 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: Splash Screen com.google.android.tvlauncher#0
11-01 02:09:39.787 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: Splash Screen com.google.android.tvlauncher#0
11-01 02:09:39.787 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: AppWindowToken{c3f9cc3 token=Token{9628072 ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t176}}}#0
11-01 02:09:39.787 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: 1c63bed Splash Screen com.google.android.tvlauncher#0
11-01 02:09:40.224 3840 3861 W ActivityTaskManager: Activity top resumed state loss timeout for ActivityRecord{a9ef97d u0 com.google.android.tvlauncher/.MainActivity t-1 f}
11-01 02:17:43.561 3840 28544 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.google.android.tvlauncher/.MainActivity} from uid 2000
11-01 02:19:00.929 3840 28544 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.google.android.tvlauncher/.MainActivity} from uid 2000
11-01 02:19:20.315 3840 3869 I ActivityManager: Start proc 22503:com.google.android.tvlauncher/u0a87 for activity {com.google.android.tvlauncher/com.google.android.tvlauncher.MainActivity}
11-01 02:19:20.613 22503 22550 E AndroidRuntime: Process: com.google.android.tvlauncher, PID: 22503
11-01 02:19:20.637 3840 28544 W ActivityTaskManager: Force finishing activity com.google.android.tvlauncher/.MainActivity
11-01 02:19:20.714 3840 4099 I ActivityManager: Process com.google.android.tvlauncher (pid 22503) has died: vis+99 TOP
11-01 02:19:20.719 3552 4339 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: AppWindowToken{1813e0b token=Token{85c39da ActivityRecord{c7f9785 u0 com.google.android.tvlauncher/.MainActivity t178}}}#0
11-01 02:19:20.721 3552 4339 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: AppWindowToken{1813e0b token=Token{85c39da ActivityRecord{c7f9785 u0 com.google.android.tvlauncher/.MainActivity t178}}}#0
11-01 02:19:20.735 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: AppWindowToken{1813e0b token=Token{85c39da ActivityRecord{c7f9785 u0 com.google.android.tvlauncher/.MainActivity t178}}}#0
11-01 02:19:20.735 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: AppWindowToken{1813e0b token=Token{85c39da ActivityRecord{c7f9785 u0 com.google.android.tvlauncher/.MainActivity t178}}}#0
11-01 02:19:21.140 3840 3861 W ActivityTaskManager: Activity top resumed state loss timeout for ActivityRecord{c7f9785 u0 com.google.android.tvlauncher/.MainActivity t-1 f}
11-01 02:20:15.881 3840 4099 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.google.android.tvlauncher/.MainActivity} from uid 2000
11-01 02:20:16.007 3840 3869 I ActivityManager: Start proc 22873:com.google.android.tvlauncher/u0a87 for activity {com.google.android.tvlauncher/com.google.android.tvlauncher.MainActivity}
11-01 02:20:16.263 3552 3831 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{bd0b9ac token=Token{58dcb5f ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t180}}})/@0x51f7386 - animation-leash#0
11-01 02:20:16.263 3552 3831 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{bd0b9ac token=Token{58dcb5f ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t180}}})/@0x51f7386 - animation-bounds#0
11-01 02:20:16.266 3552 3831 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{bd0b9ac token=Token{58dcb5f ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t180}}})/@0x51f7386 - animation-leash#0
11-01 02:20:16.266 3552 3831 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Surface(name=AppWindowToken{bd0b9ac token=Token{58dcb5f ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t180}}})/@0x51f7386 - animation-bounds#0
11-01 02:20:16.274 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: Surface(name=AppWindowToken{bd0b9ac token=Token{58dcb5f ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t180}}})/@0x51f7386 - animation-bounds#0
11-01 02:20:16.274 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: Surface(name=AppWindowToken{bd0b9ac token=Token{58dcb5f ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t180}}})/@0x51f7386 - animation-leash#0
11-01 02:20:16.274 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: Surface(name=AppWindowToken{bd0b9ac token=Token{58dcb5f ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t180}}})/@0x51f7386 - animation-leash#0
11-01 02:20:16.274 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: Surface(name=AppWindowToken{bd0b9ac token=Token{58dcb5f ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t180}}})/@0x51f7386 - animation-bounds#0
11-01 02:20:16.318 22873 22927 E AndroidRuntime: Process: com.google.android.tvlauncher, PID: 22873
11-01 02:20:16.337 3840 9090 W ActivityTaskManager: Force finishing activity com.google.android.tvlauncher/.MainActivity
11-01 02:20:16.393 3840 3856 I ActivityManager: Process com.google.android.tvlauncher (pid 22873) has died: vis+99 TOP
11-01 02:20:16.395 3552 3831 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Splash Screen com.google.android.tvlauncher#0
11-01 02:20:16.397 3552 3831 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: cb48eb0 Splash Screen com.google.android.tvlauncher#0
11-01 02:20:16.397 3552 3831 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: cb48eb0 Splash Screen com.google.android.tvlauncher#0
11-01 02:20:16.399 3552 3831 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: AppWindowToken{bd0b9ac token=Token{58dcb5f ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t180}}}#0
11-01 02:20:16.400 3552 3831 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: AppWindowToken{bd0b9ac token=Token{58dcb5f ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t180}}}#0
11-01 02:20:16.406 3552 3588 D SurfaceFlinger: onHandleDestroyed, markLayerPendingRemovalLocked: Splash Screen com.google.android.tvlauncher#0
11-01 02:20:16.407 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: AppWindowToken{bd0b9ac token=Token{58dcb5f ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t180}}}#0
11-01 02:20:16.407 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: cb48eb0 Splash Screen com.google.android.tvlauncher#0
11-01 02:20:16.407 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, layerRemoved, make not visible: Splash Screen com.google.android.tvlauncher#0
11-01 02:20:16.407 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: Splash Screen com.google.android.tvlauncher#0
11-01 02:20:16.407 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: AppWindowToken{bd0b9ac token=Token{58dcb5f ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t180}}}#0
11-01 02:20:16.407 3552 3552 D SurfaceFlinger: mLayersPendingRemoval, release: cb48eb0 Splash Screen com.google.android.tvlauncher#0
11-01 02:20:16.838 3840 3861 W ActivityTaskManager: Activity top resumed state loss timeout for ActivityRecord{c017fe u0 com.google.android.tvlauncher/.MainActivity t-1 f}
PS. To open play store go to apps, click on random app category > then go to settings > apps > recent > google play store > open.
It will open google play store UI where you can see all apps released by google, then you can install android tv launcher, leanback and android tv services.
@yaro014 I'd get rid of my two shields if I could get this sorted
METHOD A (EASY) - GET RID OF THE ADS ON THE MAIN SCREEN WITH AN ALTERNATIVE LAUNCHER
Install ATV Launcher or Wolf Launcher and disable the default launcher via adb. If you find a nice wallpaper that's a good option.
This is what I did:
1. Install Wolf launcher
2. Open Wolf launcher (opens fine)
3. Use ADB to disable stock - pm disable-user --user 0 com.google.android.apps.tv.launcherx
However, as soon as I do 3), the next time I press home, I am not able to navigate around Wolf anymore.
Did I miss a step?
Thank you.
OK, so far in order to use an alternative launcher without problems this is what I had to do:
(1) Install alternative launcher -
Wolf launcher etc
(2) disable stock launcher -
Code:
adb shell
pm disable-user --user 0 com.google.android.apps.tv.launcherx
pm disable-user --user 0 com.google.android.tungsten.setupwraith
(3) Press home button and select the alternative launcher as home app
However, I have tried various versions of the original Leanback Launcher to no avail.
Does anyone have the definitive list of framework/dependancies that Leanback launcher needs?
Thanks
H
Leanback launcher complains a lot about permissions.
Android TV home launcher complains about core services not being installed, however when installed it's being removed on reboot.
There might be some trickery enabled within the system to prevent loading Android TV launcher etc.
seapoint said:
OK, so far in order to use an alternative launcher without problems this is what I had to do:
(1) Install alternative launcher -
Wolf launcher etc
(2) disable stock launcher -
Code:
adb shell
pm disable-user --user 0 com.google.android.apps.tv.launcherx
pm disable-user --user 0 com.google.android.tungsten.setupwraith
(3) Press home button and select the alternative launcher as home app
However, I have tried various versions of the original Leanback Launcher to no avail.
Does anyone have the definitive list of framework/dependancies that Leanback launcher needs?
Thanks
H
Click to expand...
Click to collapse
i follow your step to set atv launcher as my home app, but the physical youtube button on remote didn't work anymore since that, i just wonder disabling com.google.android.tungsten.setupwraith maybe affect that? do u have the same issue?
Here's a challenge. Create a editor for the cloud based google Watchlist to add additional "ways to watch"for individual tv shows. Like mx player. That would be so sweet.
titooo7 said:
Get rid of the 3 shows/movies ads that you still get in screen even when Apps Only mode is enabled - WIP
I tried disabling some apps that came pre-installed but I didn't manage to get rid of those last ads. I guess it's integrated within the launcher so we might need to mod it (if possible), live with it or just go back to Option 1 and use a different launcher.
Any help would be appreciated
Click to expand...
Click to collapse
Here's an idea...
I've seen some screenshots from users in countries where the Chromecast with Google TV is not sold yet. It appears that they don't have the "For you" tab, and instead are having an "Home" tab which looks a bit sleeker. See: My new chromecast 2020 does not have the FOR YOU tab as normally seen in many review videos - Chromecast Community (google.com) . (Though it might not be the same for everyone, as Chromecast with Google TV: "For you", "Movies", "Shows" not showing up - Chromecast Community does have a giant suggestion bar despite having an "Home" tab.)
I've also completely disabled Internet access to my CCwGTV at my router-level. Of course, it's not that useful. But I can observe that once the launcher is loaded, I do have an "Home" tab instead of a "For you" tab. Until I re-enable Internet access...
Could it be possible to block Internet access to the launcher only? And/or trick it to think it's running on a device located in an unsupported country? While leaving all other applications correctly establish the current location -- i.e. still want Netflix to know that I'm at home and offers me what's available here, and not somewhere around Antarctica.
Alexandre-P said:
Could it be possible to block Internet access to the launcher only?
Click to expand...
Click to collapse
A domain specific block may work. Not sure what software you have running on your router, but if openwrt, it wouldn't be too much of a challenge to filter domains based on the device making the request, and even if its making the DNS request direct to 8.8.8.8, you can redirect that at the router back to 192.168.1.1
I had a little bit of progress on my Chromecast, I used TechDoctor UK's launcher manager to be able to choose a new launcher. I side loaded the old Leanback Launcher but for Amazon Fire. I can get it to load right the first time but then when I go back it gets stuck..
Could we take the official Leanback or Android TV home and just change the name so it appears as a different app?
titooo7 said:
WIP: "De-bloating" the Chromecast with Google TV. Let's get rid of those ads!
Those who like the Chromecast with Google TV UI or wouldn't move a finger to change it can stop reading this thread and move onto something else. No need to leave any comment, xda-developers wasn't created for people who don't like a challenge
If you don't like the UI because the massive ads it brings, then you are welcome to keep reading and help if you can!
METHOD A (EASY) - GET RID OF THE ADS ON THE MAIN SCREEN WITH AN ALTERNATIVE LAUNCHER
Install ATV Launcher or Wolf Launcher and disable the default launcher via adb. If you find a nice wallpaper that's a good option.
METHOD B (HARD) - USE THE APPS ONLY MODE WITH GOOGLE ASSISTANT AND NO ADS
Go to Settings > Accounts & Sign-in > Select your ac**** > Enable "Apps only mode".
Now you removed 90% of the ads but it seems like Google doesn't want us to use the Apps only mode, so they decided to put some hurdles in place disabling google assistant and play store access . We can fix it partially, so keep reading
Get a shortcut to the Google Play Store
Sideload and install this app (created with this site) and now you'll be able to access Google Play Store opening the app even on Apps Only Mode (see here how it looks)
How to use Google Assistant even on Apps Only mode - WIP
Go to Settings > All Apps > "See All apps" > "Show System apps" > Google > click on "Uninstall Updates" & "Disable". Now sideload and install this version
Now you can use Google Assistant to open a YouTube video or ask questions such as "what's the weather today?", but you can't give a voice command to open an app... It will go through a loop trying to setup google assistant.
Get rid of the 3 shows/movies ads that you still get in screen even when Apps Only mode is enabled - WIP
I tried disabling some apps that came pre-installed but I didn't manage to get rid of those last ads. I guess it's integrated within the launcher so we might need to mod it (if possible), live with it or just go back to Option 1 and use a different launcher.
Any help would be appreciated
METHOD C (HARD) - SWITCH TO THE ORIGINAL ANDROID TV LAUNCHER
I disabled the Google TV Launcher com.google.android.apps.tv.launcherx via adb. Then I sideloaded the Android TV Home and Lenback Launcher apks and tried to launch the main activity of those apps but it didn't work. Some activities could be launched but not the main one.
Any help would be highly appreciated as that's what I really wanted to do.
Click to expand...
Click to collapse
Do you have a list of apps that can be uninstalled via adb? It would be very useful. Thank you.
So it turns out that the easiest solution to this problem is to buy an ADT-3, which is what CCGTV really should have been. Unlocked and actually up to date (Android 12).
96carboard said:
So it turns out that the easiest solution to this problem is to buy an ADP-3, which is what CCGTV really should have been. Unlocked and actually up to date (Android 12).
Click to expand...
Click to collapse
what's an ADP-3?
pddc said:
what's an ADP-3?
Click to expand...
Click to collapse
ADT-3, apologies.
Just picked one of these up, thanks to your head start, I've got the homescreen looking like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have it running in "Apps Only mode" regular mode looks almost the same, but with a non-functioning Google Assistance icon at the top.
Here is what I did:
Set-up the device as normal, and ran all updates.
Uninstalled all apps I didn't want, and sideloaded the apps I wanted.
Created ATV icon apps for Play Store and Movies as suggested above.
Blocked " androidtvlauncherxfe-pa.googleapis.com " using a pi-hole.
Cleared data for the Google TV app.
Restarted the device, and set to apps-only mode.
Ads are blocked the same way as on the NVIDIA SHIELD. Took me a few times of resetting to pin down the ip address to block. The big error message isn't ideal, I would be fine with the "generic" ads like the SHIELD, but it's better than the alternative.
As far as I am able to tell, everything works as without issue, including casting, except Google Assistant which is fine by me.
Only other downsides: there is sometimes a noticeable delay returning to the homescreen (on boot, returning from settings, rarely when switching apps), and you cannot open the "quick-menu" on the home screen to move apps. The only way to rearrange apps would be to uninstall.
Might not be the most elegant solution, but nothing deal breaking IMHO. Certainly good enough for my uses.
Buoy is an extension to the built in Android Battery Saver
Description
The built-in Android battery saver mode is actually quite powerful. The only disappointment is that none of it is configurable out of the box. That's where Buoy comes in. Buoy makes using the built-in battery saver feasible in any situation. If you want mild savings during the day without impeding performance, it can be done. If you need to squeeze every last ounce of power out of your device, it can be done. If you want anything in between, it can be done!
FeaturesBuoy uses hidden Android settings to specify custom behavior for the built in battery saver. Features include the following toggles:
Advertising to other apps that low power mode is enabled
Android's data saver for metered WiFi or mobile data connections
The built-in dark mode
Launch boost to accelerate app starts
Vibration
Showing window and activity animations
Allowing apps to use the SoundTrigger HAL
Deferring full device backups for later
Deferring app setting backups for later
Using the built-in web firewall to protect against possibly malicious sites
Changing the location access mode restrictions for apps
Reducing the max brightness of the panel
Forcing all apps into standby mode
Forcing all apps to not check data in the background
Disabling unnecessary sensors
Using the Always-On-Display
Putting the device into deep sleep as soon as the screen turns off
Sticky Low PowerBuoy also enables something called "sticky" low power mode. Usually, when the device is plugged in and unplugged, the low power mode is then disabled. However, sticky mode re-applies low power mode afterwards to continue saving battery.
DisclaimersNote that this app requires the WRITE_SECURE_SETTINGS permission that can be granted with EITHER a PC using ADB or root. Root is NOT required for this app, it is optional. Android 8.0+ is supported, with more features enabled on Android 10+.
Uninstalling the app will not reset the battery saver configuration. You must click the Reset button to undo all changes made by Buoy.
Play Store Link: https://play.google.com/store/apps/details?id=com.draco.buoy
GitHub Link: https://github.com/tytydraco/Buoy
tytydraco said:
Buoy is an extension to the built in Android Battery Saver
Description
The built-in Android battery saver mode is actually quite powerful. The only disappointment is that none of it is configurable out of the box. That's where Buoy comes in. Buoy makes using the built-in battery saver feasible in any situation. If you want mild savings during the day without impeding performance, it can be done. If you need to squeeze every last ounce of power out of your device, it can be done. If you want anything in between, it can be done!
FeaturesBuoy uses hidden Android settings to specify custom behavior for the built in battery saver. Features include the following toggles:
Advertising to other apps that low power mode is enabled
Android's data saver for metered WiFi or mobile data connections
The built-in dark mode
Launch boost to accelerate app starts
Vibration
Showing window and activity animations
Allowing apps to use the SoundTrigger HAL
Deferring full device backups for later
Deferring app setting backups for later
Using the built-in web firewall to protect against possibly malicious sites
Changing the location access mode restrictions for apps
Reducing the max brightness of the panel
Forcing all apps into standby mode
Forcing all apps to not check data in the background
Disabling unnecessary sensors
Using the Always-On-Display
Putting the device into deep sleep as soon as the screen turns off
Sticky Low PowerBuoy also enables something called "sticky" low power mode. Usually, when the device is plugged in and unplugged, the low power mode is then disabled. However, sticky mode re-applies low power mode afterwards to continue saving battery.
DisclaimersNote that this app requires the WRITE_SECURE_SETTINGS permission that can be granted with EITHER a PC using ADB or root. Root is NOT required for this app, it is optional. Android 8.0+ is supported, with more features enabled on Android 10+.
Uninstalling the app will not reset the battery saver configuration. You must click the Reset button to undo all changes made by Buoy.
Play Store Link: https://play.google.com/store/apps/details?id=com.draco.buoy
GitHub Link: https://github.com/tytydraco/Buoy
Click to expand...
Click to collapse
Does it make the doze mode kick in directly after screen off? Also without motion and maintenance? Thanks
Goku1992 said:
Does it make the doze mode kick in directly after screen off? Also without motion and maintenance? Thanks
Click to expand...
Click to collapse
It should still wake up, but it will instantly enter sleep again. And yes, doze will enter deep sleep immediately after screen off.
tytydraco said:
It should still wake up, but it will instantly enter sleep again. And yes, doze will enter deep sleep immediately after screen off.
Click to expand...
Click to collapse
Thanks for the feedback mate, will try it
Mate i have one question will it wake up everytime motion sensors register motion? Or is this using light doze (on the go)
This looks great, thanks for sharing!
Hi, may I know how I know if the profile is activated? or the setting is in used? I tap on those profile but no "Reset" button appear in the app
Testing on the massive battery 6A on Samsung galaxy m31
I've noticed the settings not "sticking" on Galaxy S20 FE Android 11 recently ... I can't put my finger on what would be changing the profile settings? Only happens after a long time in Deep Doze ...
tytydraco said:
Buoy is an extension to the built in Android Battery Saver
Description
The built-in Android battery saver mode is actually quite powerful. The only disappointment is that none of it is configurable out of the box. That's where Buoy comes in. Buoy makes using the built-in battery saver feasible in any situation. If you want mild savings during the day without impeding performance, it can be done. If you need to squeeze every last ounce of power out of your device, it can be done. If you want anything in between, it can be done!
FeaturesBuoy uses hidden Android settings to specify custom behavior for the built in battery saver. Features include the following toggles:
Advertising to other apps that low power mode is enabled
Android's data saver for metered WiFi or mobile data connections
The built-in dark mode
Launch boost to accelerate app starts
Vibration
Showing window and activity animations
Allowing apps to use the SoundTrigger HAL
Deferring full device backups for later
Deferring app setting backups for later
Using the built-in web firewall to protect against possibly malicious sites
Changing the location access mode restrictions for apps
Reducing the max brightness of the panel
Forcing all apps into standby mode
Forcing all apps to not check data in the background
Disabling unnecessary sensors
Using the Always-On-Display
Putting the device into deep sleep as soon as the screen turns off
Sticky Low PowerBuoy also enables something called "sticky" low power mode. Usually, when the device is plugged in and unplugged, the low power mode is then disabled. However, sticky mode re-applies low power mode afterwards to continue saving battery.
DisclaimersNote that this app requires the WRITE_SECURE_SETTINGS permission that can be granted with EITHER a PC using ADB or root. Root is NOT required for this app, it is optional. Android 8.0+ is supported, with more features enabled on Android 10+.
Uninstalling the app will not reset the battery saver configuration. You must click the Reset button to undo all changes made by Buoy.
Play Store Link: https://play.google.com/store/apps/details?id=com.draco.buoy
GitHub Link: https://github.com/tytydraco/Buoy
Click to expand...
Click to collapse
I bought your app, but when I gave the permissions on the laptop I get this error and it does not grant them, it is a mi 10t pro 12.5, what is the correct command line to enter?
what does enabling firewall actually block or do?
Does this have the ability to automatically turn off battery saver at a percentage lower than 90% I don't see anything in the screenshots, Idk why Google hasn't made this configurable in the battery saver options.. If it doesn't can you add it please?
Luispacheco2552 said:
I bought your app, but when I gave the permissions on the laptop I get this error and it does not grant them, it is a mi 10t pro 12.5, what is the correct command line to enter?
Click to expand...
Click to collapse
Since it a MI phone you have to enable something in the developer options called "allow granting permissions via adb". The ****ty MIUI blocks all essential ADB commands for important things such as backup.
Hi , i downloaded the app and graved the permission then I clicked on "import" button and app crashed. Now the app didn't open i also tried to uninstall and reinstall but nothing it happened. Please help me :/
NextDaniel said:
Hi , i downloaded the app and graved the permission then I clicked on "import" button and app crashed. Now the app didn't open i also tried to uninstall and reinstall but nothing it happened. Please help me :/
Click to expand...
Click to collapse
Hi, thanks for the report! I'll check this out. Can you send me a logcat if possible?
tytydraco said:
Hi, thanks for the report! I'll check this out. Can you send me a logcat if possible?
Click to expand...
Click to collapse
510 2014 D ConnectivityService: releasing NetworkRequest [ TRACK_DEFAULT id=117, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10226 AdministratorUids: [] RequestorUid: 10226 RequestorPackageName: com.google.android.apps.maps] ] (release request)
09-20 20:31:31.152 874 874 I Zygote : Process 15355 exited due to signal 9 (Killed)
09-20 20:31:31.179 3228 3228 I GsaVoiceInteractionSrv: Handling ACTION_STOP_HOTWORD
09-20 20:31:31.180 20280 20280 D AndroidRuntime: Shutting down VM
09-20 20:31:31.180 20280 20280 E AndroidRuntime: FATAL EXCEPTION: main
09-20 20:31:31.180 20280 20280 E AndroidRuntime: Process: com.draco.buoy, PID: 20280
09-20 20:31:31.180 20280 20280 E AndroidRuntime: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at java.util.Collections$SingletonList.get(Collections.java:4872)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at s0.a.j01)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at s0.a.C2)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at androidx.fragment.app.h.S29)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at androidx.fragment.app.h.Q1)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at androidx.fragment.app.h.R(Unknown Source:47)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at androidx.fragment.app.a.i2)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at androidx.fragment.app.h.D7)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at androidx.fragment.app.h.X(Unknown Source:84)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at androidx.fragment.app.h.B4)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at androidx.fragment.app.h.v(Unknown Source:14)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at j.d.onStart2)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at h.c.onStart(Unknown Source:0)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1435)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at android.app.Activity.performStart(Activity.java:8018)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3457)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7664)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
09-20 20:31:31.180 20280 20280 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
09-20 20:31:31.183 1510 5937 W ActivityTaskManager: Force finishing activity com.draco.buoy/.views.MainActivity
09-20 20:31:31.184 1510 1658 I libprocessgroup: Successfully killed process cgroup uid 10226 pid 15355 in 88ms
09-20 20:31:31.193 1510 5937 I WindowManager: Queue is too deep! Purged item with taskid=63
09-20 20:31:31.201 20280 20280 I Process : Sending signal. PID: 20280 SIG: 9
09-20 20:31:31.223 1510 2014 D ConnectivityService: NetReassign [no changes]
09-20 20:31:31.231 1510 7840 I ActivityManager: Process com.draco.buoy (pid 20280) has died: fg TOP
09-20 20:31:31.232 1510 1658 I libprocessgroup: Successfully killed process cgroup uid 10377 pid 20280 in 0ms
09-20 20:31:31.232 874 874 I Zygote : Process 20280 exited due to signal 9 (Killed)
09-20 20:31:31.246 3228 3228 I GsaVoiceInteractionSrv: Handling ACTION_START_HOTWORD
09-20 20:31:31.246 3228 3228 I GsaVoiceInteractionSrv: disregardVoiceMatch: false
09-20 20:31:31.246 3228 3228 I GsaVoiceInteractionSrv: Cannot start hotword, hotword has been explicitly disabled.
09-20 20:31:31.251 3228 4030 I AssistantForeground: Get launcher package: com.google.android.apps.nexuslauncher
09-20 20:31:31.254 3228 4364 I A : setScreenState
09-20 20:31:31.254 3228 4364 I A : Dropping message not meant for SystemUI.
09-20 20:31:31.256 3117 3117 I GoogleInputMethodService: GoogleInputMethodService.onFinishInput():3446
09-20 20:31:31.256 3117 3117 I GoogleInputMethodService: GoogleInputMethodService.onStartInput():2028
09-20 20:31:31.257 3117 3117 I DeviceUnlockedTag: DeviceUnlockedTag.notifyDeviceLockStatusChanged():38 Notify device unlocked.
09-20 20:31:31.378 1510 1604 W ActivityTaskManager: Activity top resumed state loss timeout for ActivityRecord{25e234 u0 com.draco.buoy/.views.MainActivity t-1 f}}
09-20 20:31:31.413 1510 2186 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.draco.buoy/.views.MainActivity bnds=[440,29][641,354]} from uid 10245
09-20 20:31:31.427 1510 1604 D CompatibilityChangeReporter: Compat change id reported: 135634846; UID 10377; state: DISABLED
09-20 20:31:31.427 1510 1604 D CompatibilityChangeReporter: Compat change id reported: 135754954; UID 10377; state: ENABLED
09-20 20:31:31.427 1510 1637 D CompatibilityChangeReporter: Compat change id reported: 143937733; UID 10377; state: ENABLED
09-20 20:31:31.435 874 874 D Zygote : Forked child process 20304
09-20 20:31:31.444 1510 1637 I ActivityManager: Start proc 20304:com.draco.buoy/u0a377 for pre-top-activity {com.draco.buoy/com.draco.buoy.views.MainActivity}
09-20 20:31:31.453 20304 20304 E com.draco.buoy: Not starting debugger since process cannot load the jdwp agent.
09-20 20:31:31.463 3228 4015 I AssistantForeground: Get launcher package: com.google.android.apps.nexuslauncher
09-20 20:31:31.467 3228 4363 I A : setScreenState
09-20 20:31:31.468 3228 4363 I A : Dropping message not meant for SystemUI.
09-20 20:31:31.472 583 583 E Layer : [Surface(name=Task=1)/@0x9704126 - animation-leash#1] No local sync point found
09-20 20:31:31.472 583 583 E Layer : [Surface(name=Task=1)/@0x9704126 - animation-leash#1] No local sync point found
09-20 20:31:31.474 20304 20304 W com.draco.buoy: JIT profile information will not be recorded: profile file does not exist.
09-20 20:31:31.474 20304 20304 W com.draco.buoy: JIT profile information will not be recorded: profile file does not exist.
09-20 20:31:31.479 20304 20304 D NetworkSecurityConfig: No Network Security Config specified, using platform default
09-20 20:31:31.479 20304 20304 D NetworkSecurityConfig: No Network Security Config specified, using platform default
09-20 20:31:31.481 2525 2525 D RecentsOrientedState: current RecentsOrientedState: [[email protected] [email protected] mDisplayRotation=0 mTouchRotation=0 mRecentsActivityRotation=0 isRecentsActivityRotationAllowed=false mSystemRotation=false mFlags=291]
09-20 20:31:31.481 2525 2525 I chatty : uid=10245(com.google.android.apps.nexuslauncher) identical 2 lines
09-20 20:31:31.481 2525 2525 D RecentsOrientedState: current RecentsOrientedState: [[email protected] [email protected] mDisplayRotation=0 mTouchRotation=0 mRecentsActivityRotation=0 isRecentsActivityRotationAllowed=false mSystemRotation=false mFlags=291]
09-20 20:31:31.484 583 2653 W DisplayIdentification: Invalid EDID: falling back to serial number due to missing display name.
09-20 20:31:31.484 583 2653 W DisplayIdentification: Invalid EDID: falling back to ASCII text due to missing serial number.
09-20 20:31:31.523 20304 20304 D AndroidRuntime: Shutting down VM
09-20 20:31:31.523 20304 20304 E AndroidRuntime: FATAL EXCEPTION: main
09-20 20:31:31.523 20304 20304 E AndroidRuntime: Process: com.draco.buoy, PID: 20304
09-20 20:31:31.523 20304 20304 E AndroidRuntime: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at java.util.Collections$SingletonList.get(Collections.java:4872)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at s0.a.j01)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at s0.a.C2)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at androidx.fragment.app.h.S29)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at androidx.fragment.app.h.Q1)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at androidx.fragment.app.h.R(Unknown Source:47)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at androidx.fragment.app.a.i2)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at androidx.fragment.app.h.D7)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at androidx.fragment.app.h.X(Unknown Source:84)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at androidx.fragment.app.h.B4)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at androidx.fragment.app.h.v(Unknown Source:14)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at j.d.onStart2)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at h.c.onStart(Unknown Source:0)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1435)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at android.app.Activity.performStart(Activity.java:8018)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3457)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7664)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
09-20 20:31:31.523 20304 20304 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
09-20 20:31:31.525 1510 2186 W ActivityTaskManager: Force finishing activity com.draco.buoy/.views.MainActivity
09-20 20:31:31.536 1510 2186 I WindowManager: Queue is too deep! Purged item with taskid=64
09-20 20:31:31.544 20304 20304 I Process : Sending signal. PID: 20304 SIG: 9
09-20 20:31:31.544 3228 3228 I GsaVoiceInteractionSrv: Handling ACTION_STOP_HOTWORD
09-20 20:31:31.564 1510 12194 I ActivityManager: Process com.draco.buoy (pid 20304) has died: prcp TOP
09-20 20:31:31.564 874 874 I Zygote : Process 20304 exited due to signal 9 (Killed)
09-20 20:31:31.565 1510 1658 I libprocessgroup: Successfully killed process cgroup uid 10377 pid 20304 in 0ms
09-20 20:31:31.587 3228 3228 I GsaVoiceInteractionSrv: Handling ACTION_START_HOTWORD
09-20 20:31:31.587 3228 3228 I GsaVoiceInteractionSrv: disregardVoiceMatch: false
09-20 20:31:31.587 3228 3228 I GsaVoiceInteractionSrv: Cannot start hotword, hotword has been explicitly disabled.
09-20 20:31:31.589 3228 4364 I AssistantForeground: Get launcher package: com.google.android.apps.nexuslauncher
09-20 20:31:31.591 3228 4015 I A : setScreenState
09-20 20:31:31.592 3228 4015 I A : Dropping message not meant for SystemUI.
09-20 20:31:31.597 3117 3117 I GoogleInputMethodService: GoogleInputMethodService.onFinishInput():3446
09-20 20:31:31.598 3117 3117 I GoogleInputMethodService: GoogleInputMethodService.onStartInput():2028
09-20 20:31:31.599 3117 3117 I DeviceUnlockedTag: DeviceUnlockedTag.notifyDeviceLockStatusChanged():38 Notify device unlocked.
09-20 20:31:31.647 907 1020 D CHRE : @ 489.060: [ImuCal] Dynamic sensor configuration: high-performance.
09-20 20:31:31.725 1510 2191 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.draco.buoy/.views.MainActivity bnds=[440,36][641,361]} from uid 10245
09-20 20:31:31.742 1510 1604 D CompatibilityChangeReporter: Compat change id reported: 135634846; UID 10377; state: DISABLED
09-20 20:31:31.743 1510 1604 D CompatibilityChangeReporter: Compat change id reported: 135754954; UID 10377; state: ENABLED
09-20 20:31:31.743 1510 1637 D CompatibilityChangeReporter: Compat change id reported: 143937733; UID 10377; state: ENABLED
09-20 20:31:31.749 874 874 D Zygote : Forked child process 20328
09-20 20:31:31.754 1510 1637 I ActivityManager: Start proc 20328:com.draco.buoy/u0a377 for pre-top-activity {com.draco.buoy/com.draco.buoy.views.MainActivity}
09-20 20:31:31.758 20328 20328 E com.draco.buoy: Not starting debugger since process cannot load the jdwp agent.
09-20 20:31:31.764 3228 4363 I AssistantForeground: Get launcher package: com.google.android.apps.nexuslauncher
09-20 20:31:31.772 3228 3895 I A : setScreenState
09-20 20:31:31.772 3228 3895 I A : Dropping message not meant for SystemUI.
09-20 20:31:31.783 583 583 E Layer : [Surface(name=Task=1)/@0x9704126 - animation-leash#0] No local sync point found
09-20 20:31:31.783 583 583 E Layer : [Surface(name=Task=1)/@0x9704126 - animation-leash#0] No local sync point found
09-20 20:31:31.785 20328 20328 W com.draco.buoy: JIT profile information will not be recorded: profile file does not exist.
09-20 20:31:31.785 20328 20328 W com.draco.buoy: JIT profile information will not be recorded: profile file does not exist.
09-20 20:31:31.789 20328 20328 D NetworkSecurityConfig: No Network Security Config specified, using platform default
09-20 20:31:31.789 20328 20328 D NetworkSecurityConfig: No Network Security Config specified, using platform default
09-20 20:31:31.794 2525 2525 D RecentsOrientedState: current RecentsOrientedState: [[email protected] [email protected] mDisplayRotation=0 mTouchRotation=0 mRecentsActivityRotation=0 isRecentsActivityRotationAllowed=false mSystemRotation=false mFlags=291]
09-20 20:31:31.794 2525 2525 I chatty : uid=10245(com.google.android.apps.nexuslauncher) identical 2 lines
09-20 20:31:31.794 2525 2525 D RecentsOrientedState: current RecentsOrientedState: [[email protected] [email protected] mDisplayRotation=0 mTouchRotation=0 mRecentsActivityRotation=0 isRecentsActivityRotationAllowed=false mSystemRotation=false mFlags=291]
09-20 20:31:31.798 583 2653 W DisplayIdentification: Invalid EDID: falling back to serial number due to missing display name.
09-20 20:31:31.798 583 2653 W DisplayIdentification: Invalid EDID: falling back to ASCII text due to missing serial number.
09-20 20:31:31.835 20328 20328 D AndroidRuntime: Shutting down VM
09-20 20:31:31.835 20328 20328 E AndroidRuntime: FATAL EXCEPTION: main
09-20 20:31:31.835 20328 20328 E AndroidRuntime: Process: com.draco.buoy, PID: 20328
09-20 20:31:31.835 20328 20328 E AndroidRuntime: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at java.util.Collections$SingletonList.get(Collections.java:4872)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at s0.a.j01)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at s0.a.C2)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at androidx.fragment.app.h.S29)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at androidx.fragment.app.h.Q1)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at androidx.fragment.app.h.R(Unknown Source:47)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at androidx.fragment.app.a.i2)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at androidx.fragment.app.h.D7)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at androidx.fragment.app.h.X(Unknown Source:84)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at androidx.fragment.app.h.B4)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at androidx.fragment.app.h.v(Unknown Source:14)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at j.d.onStart2)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at h.c.onStart(Unknown Source:0)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1435)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at android.app.Activity.performStart(Activity.java:8018)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3457)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7664)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
09-20 20:31:31.835 20328 20328 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
09-20 20:31:31.838 1510 2191 W ActivityTaskManager: Force finishing activity com.draco.buoy/.views.MainActivity
09-20 20:31:31.847 1510 2191 I WindowManager: Queue is too deep! Purged item with taskid=65
09-20 20:31:31.855 20328 20328 I Process : Sending signal. PID: 20328 SIG: 9
09-20 20:31:31.855 3228 3228 I GsaVoiceInteractionSrv: Handling ACTION_STOP_HOTWORD
09-20 20:31:31.872 1510 7840 I ActivityManager: Process com.draco.buoy (pid 20328) has died: prcp TOP
09-20 20:31:31.872 874 874 I Zygote : Process 20328 exited due to signal 9 (Killed)
09-20 20:31:31.872 1510 1658 I libprocessgroup: Successfully killed process cgroup uid 10377 pid 20328 in 0ms
09-20 20:31:31.892 3228 3228 I GsaVoiceInteractionSrv: Handling ACTION_START_HOTWORD
09-20 20:31:31.892 3228 3228 I GsaVoiceInteractionSrv: disregardVoiceMatch: false
09-20 20:31:31.892 3228 3228 I GsaVoiceInteractionSrv: Cannot start hotword, hotword has been explicitly disabled.
09-20 20:31:31.897 3228 4015 I AssistantForeground: Get launcher package: com.google.android.apps.nexuslauncher
09-20 20:31:31.898 3117 3117 I GoogleInputMethodService: GoogleInputMethodService.onFinishInput():3446
09-20 20:31:31.898 3117 3117 I GoogleInputMethodService: GoogleInputMethodService.onStartInput():2028
09-20 20:31:31.899 3117 3117 I DeviceUnlockedTag: DeviceUnlockedTag.notifyDeviceLockStatusChanged():38 Notify device unlocked.
09-20 20:31:31.900 3228 3895 I A : setScreenState
09-20 20:31:31.901 3228 3895 I A : Dropping message not meant for SystemUI.
09-20 20:31:32.026 1510 1604 W ActivityTaskManager: Activity top resumed state loss timeout for ActivityRecord{e9dd48d u0 com.draco.buoy/.views.MainActivity t-1 f}}
09-20 20:31:32.038 15920 18207 V NativeCrypto: SSL shutdown failed: ssl=0xb400007cd966d2d8: I/O error during system call, Software caused connection abort
09-20 20:31:32.340 907 1020 D VSC : @ 489.753: [WO] isFlat() nearest_rotation: 2, flat_angle: 65
09-20 20:31:32.340 907 1020 D VSC : @ 489.753: [WO] orientation angle 175, orientation 2
09-20 20:31:32.359 907 2625 I sensors-hal: [ssc_utils]get_qmi_debug_flag:244, support_qmi_debug : false
09-20 20:31:32.380 907 1020 W ASH : @ 489.793: Unhandled msg ID 999: line 1277
09-20 20:31:32.380 907 1020 E ASH : @ 489.793: No pb callback assigned
09-20 20:31:32.380 907 1020 E ASH : @ 489.793: Nanopb error: callback failed:1588
09-20 20:31:32.902 908 983 I [email protected]: skin-therm-monitor: 36.26
Thanks, found it. I'll fix it asap
tytydraco said:
Thanks, found it. I'll fix it asap
Click to expand...
Click to collapse
thanks <3
I ask the dev if there any news to my problem of opening the app
tytydraco said:
Thanks, found it. I'll fix it asap
Click to expand...
Click to collapse
Is there a way to automate the profiles? I took a look at tasker but couldn't seem to figure it out. Would like to turn on extreme when screen is off or overnight.