Thread: iGO NextGen AvicSync - Fast Loading - 3 seconds

Hi

I said that yesterday in skin_DT topic... but nobody seemed to agree...

The car-profile is not the subject but the User-profile, also in skin_Pongo... that does not work anymore if using Avic version

Originally Posted by naab

Is there some list somewhere that explains what all of those UXs do ? I already have some of them but they're too many to try out one by one to see which ones I want.

I am thinking about doing that with the help of other members of course. Create some sort of guide what each ux plug-in do with screen shot from program if possible.

Sent from my SM-N9005 using Tapatalk

Originally Posted by Texas

I am thinking about doing that with the help of other members of course. Create some sort of guide what each ux plug-in do with screen shot from program if possible.

Sent from my SM-N9005 using Tapatalk

That would be very useful.

Originally Posted by osiris4isis

The problem with NextGen releases is that no one know where any of the components (ux, data.zip, .apk, etc...) come from. People take bits and pieces of them to get it working, then posted it for others to use and when there are issues, no one knows why. iGO/Primo uses one .zip file per skin which is nice to manipulate and debug. NextGen uses ux which is a pain in the butt to debug, too many conflicts in their interactions and their testing is always per release (one to one) and never against each another (one to many). We need to tagged and databased each ux, data.zip, etc... based on some sort of signature (crc-32) so we know who has what.

Primo also uses ux. In my installation I have 5-6 of these. But I guess skins were more complete for primo so people didn't need to use many uxs.
It would be nice to have a list to know what each ux is supposed to do. Whether they actually work on not on a particular installation is another matter that is, as you mention, quite complex. But at least if we knew what they're supposed to do we could test them ourselves.