Posts: 57
Joined: Apr 2011
Reputation:
0
I must say, having been previously using XBMC11 that version 12.2 is much slower, less responsive to clicks, and mucks up left/right controls more often than 11 did. I think it's the animations that it's trying to do, swishing and zooming between screens. I've been poking around in the settings (in app) and can't seem to find a way to just disable the animations altogether, which would improve my user experience no end. Is there a trick to it? I've never been a fan of animated interfaces.
If there's a file you have to edit, please let me know the files to edit in. I can generally muddle through a terminal prompt.
I'm running iOS 5.2.1 (tethered boot) and XBMC 12.2 (Git: 20130502-32b1a5e) and the default Confluence skin.
Posts: 31,445
Joined: Jan 2011
Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
What skin? Perhaps you need something lighter.
Posts: 2
Joined: Jul 2012
Reputation:
0
I've had the same experience, on 2 ATV2s. One I upgraded from 12.0, the other from 12.1. Both ran fine on the previous versions, but are now slow and unresponsive to some remote clicks.
Sounds like a common issue
Posts: 57
Joined: Apr 2011
Reputation:
0
what is a debug log going to show you, really? I've started from a complete fresh FIRMWARE. So there's nothing on the device other than what a complete fresh installation that follows the XBMC instructions. The debug log is going to be exactly the same on any atv2 device given that procedure, isn't it? Rather than asking for a debug log, why not post about what YOU would be looking for in such a log if it were uploaded that might lend an idea to why it runs so badly.
Posts: 327
Joined: Feb 2011
Reputation:
3
A debug log will show timings on all steps so at least helpful people on here can look at it and try and help with identifying if anything is sticking at any point.
As for myself, I have 2 ATV2's both running 12.2, one with Confluence skin, one with a WIP skin called Amber - both running fine.
QNAP TS670 NAS - 4x4TB Raided with NFS Support & Central MySQL DB
Pi 3 [Xbian] - Samsung 46" ES7000 Smart TV & HT-E5550 3D BD Sound System
Pi 3 [Xbian] + Hyperion Ambilight- Samsung 48" Curved UE48JS9000 4k
PowerEthernet T1502 Powerline adapters
Posts: 31,445
Joined: Jan 2011
(2013-05-23, 12:12)frumbert Wrote: what is a debug log going to show you, really? I've started from a complete fresh FIRMWARE. So there's nothing on the device other than what a complete fresh installation that follows the XBMC instructions. The debug log is going to be exactly the same on any atv2 device given that procedure, isn't it? Rather than asking for a debug log, why not post about what YOU would be looking for in such a log if it were uploaded that might lend an idea to why it runs so badly.
We're looking for clues. The debug log will not be exactly the same on a fresh device, because YOUR fresh device is broken. It could be a defective hardware issue, a slight difference in the install process (a jailbreak dependency that's on a newer version when it got installed, for example), could be some strange network traffic, who knows. You can't even fix this issue, so what makes you so sure you even know what the logs contain? You are asking us for help, and no one will help you if you refuse such a simple and reasonable request as a debug log. If you think you're smarter than everyone here, then don't ask the question in the first place.
Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
I do get puzzled by people who come here with a problem, then question a simple request for debugging information.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)