Re: [Ubuntu-phone] Connect to phone from Mac
OS X doesn't have a native MTP implementation, that's why it doesn't work. You could try Android Filetransfer though, which uses MTP. http://www.android.com/filetransfer/ Am Dienstag, den 19.11.2013, 21:17 + schrieb Jouni Helminen: > Doesn't work for me either - mtp usb seems to only works in ubuntu > vm, not OSX. Would be nice if it did > > > On Tue, Nov 19, 2013 at 7:29 PM, Jason Felice > wrote: > > Does anyone have a way to do this? I can connect from within > an Ubuntu VM just fine, but this takes more effort to get > photos and other files off the phone. > > > Thanks, > -Jason > > -- > Mailing list: https://launchpad.net/~ubuntu-phone > Post to : ubuntu-phone@lists.launchpad.net > Unsubscribe : https://launchpad.net/~ubuntu-phone > More help : https://help.launchpad.net/ListHelp > > > -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-phone] Qt5 and touch performance issue
In case my mail didn't get through, the way I intended it, again: You are making it sound easier than it actually is. The effort that would be required to have a decently working Android-compatibility layer is not worth the hassle IMO, since it would put us in the same category as Windows 8, where you have 2 completely different types of apps (Desktop & "Metro" apps : Ubuntu SDK & Android apps). I would not want to have 2 completely different types of apps with completely different ways of navigation and fundamental technical differences on my smart phone. What value does app compatibility bring if the user experience is crap? Am 2013-06-21 15:16, schrieb leon lee: To merge two systems together, we need to know more about the ARCH of both, or we would be lost. I think you must be very familiar with the ARCH of touch, why not introduce it to us. Or show us where to find the infomation. -- Original -- *From: * "Thomas Vo "; *Date: * Fri, Jun 21, 2013 09:00 PM *To: * "leon lee"; *Cc: * "ubuntu-phone"; *Subject: * Re: [Ubuntu-phone] Qt5 and touch performance issue On Fri, Jun 21, 2013 at 2:52 PM, leon lee mailto:llr...@qq.com>> wrote: activity manager: like the name says, manage the activity, and also some memory management. When an activity starts, the activity manager would request zygote( the mother of almost everything in android ) to fork a thread, and then the activity manager manages this activity/thread. When the activity stops, the thread is not killed. So next time when the same activty is being started, the thread can be used for it at once, so to save time. But when the memory is not enough, the thread with no activity running would be killed first. This is the major part of memory management. So you can say activity manager just manages the thread, and this should be the basic module of touch. For android 2.3, the code locates in framework/base/services/java/com/android/server/am/, in case you want to look into it. Content provider: from comment of ContentProvider.java: Content providers are one of the primary building blocks of Android applications, providing content to applications. They encapsulate data and provide it to applications through the single ContentResolver interface. A content provider is only required if you need to share data between multiple applications. For example, the contacts data is used by multiple applications and must be stored in a content provider. If you don't need to share data amongst multiple applications you can use a database directly via android.database.sqlite.SQLiteDatabase. For more information, read Content Providers. When a request is made via a ContentResolver the system inspects the authority of the given URI and passes the request to the content provider registered with the authority. The content provider can interpret the rest of the URI however it wants. The UriMatcher class is helpful for parsing URIs. leon: I think Content provider is just the abstract class for data sharing between multiple applications, data like contacts. For android 2.3, the code locates in frameworks/base/core/java/android/content/, in case you want to look into it. also: http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/2.3.4_r1/android/content/ContentProvider.java Thanks for the summary, I'm aware of the purpose and the internals of both ActivityManager and ContentProvider. Again, the level of detail we would require to get started is much higher and I do not think that the approach of picking two components at random and summarizing their \brief-documentation helps. Thanks, Thomas -- Original -- *From: * "Thomas Vo "mailto:thomas.v...@canonical.com>>; *Date: * Fri, Jun 21, 2013 07:17 PM *To: * "leon lee"mailto:llr...@qq.com>>; __ *Cc: * "ubuntu-phone"mailto:ubuntu-phone@lists.launchpad.net>>; __ *Subject: * Re: [Ubuntu-phone] Qt5 and touch performance issue On Fri, Jun 21, 2013 at 1:03 PM, leon lee mailto:llr...@qq.com>> wrote: If we look at the ARCH of android, I think we need change the framwork, expecially activity manager, window manager, content providers, view system. If touch has such an ARCH chart, it would be easier to know what to do from the ARCH aspect. We don't have an activity manager, content providers or a view system (the latter is a toolkit btw, so roughly the equivalent of Qt/QML & HTML5/JS). A window manager is there of course, but not in the sense that android exposes it. As much as I'm a fan of block diagrams, I'm afraid that we need to dive a lot deeper into the details of the Android SDK to really map individual components. Again: Help with that is greatly appreciated :-) Than
Re: [Ubuntu-phone] Qt5 and touch performance issue
How were Apple and Android successful if everything regular people used up until the breakthrough of consumer touch devices were old-style candy bar and clamshell dumb-phones? I don't know how much experience you have with developing apps for Android. I'm an Android app developer, and navigation WITHIN apps is different from Ubuntu Touch. Android: emphasis on the Action Bar and the new side-bar approach, hardware/always-on-screen back button... Also, multitasking has its quirks the way you can set different flags for activities. Ubuntu Touch: swipe gestures, tool bar, generally a more tab-based approach, HUD etc. I want Ubuntu Touch to be great (and I'm just an enthusiast). That requires some understanding in how regular users interact with devices. And regular users don't want to be overwhelmed by having apps that always look and behave differently. Being better than Android requires leaving its legacy behind and start from scratch, that also implies: no Android compatibility layer by default. You know what I kinds of apps I hate on Android? Those that look and behave like iOS apps. Am 2013-06-21 15:54, schrieb leon lee: If ways of navigation are completely different, then I would doubt how touch would be successful in the market. People are familiar with android and ios, how would people go choose one thing that's completely different, and with just a few apps. Unless touch is as innovative as ios in 2007, and the marketing people are as good as Jobs. I hope the marketing people have thought about this. -- Original ------ *From: * "Alfred Neumayer"; *Date: * Fri, Jun 21, 2013 09:22 PM *To: * "ubuntu-phone"; *Subject: * Re: [Ubuntu-phone] Qt5 and touch performance issue You are making it sound easier than it actually is. The effort that would be required to have a decently working Android-compatibility layer is not worth the hassle IMO, since it would put us in the same category as Windows 8, where you have 2 completely different types of apps (Desktop & "Metro" apps : Ubuntu SDK & Android apps). I would not want to have 2 completely different types of apps with completely different ways of navigation and fundamental technical differences on my smart phone. What value does app compatibility bring if the user experience is crap? Am 2013-06-21 15:16, schrieb leon lee: To merge two systems together, we need to know more about the ARCH of both, or we would be lost. I think you must be very familiar with the ARCH of touch, why not introduce it to us. Or show us where to find the infomation. -- Original -- *From: * "Thomas Vo "; *Date: * Fri, Jun 21, 2013 09:00 PM *To: * "leon lee"; *Cc: * "ubuntu-phone"; *Subject: * Re: [Ubuntu-phone] Qt5 and touch performance issue On Fri, Jun 21, 2013 at 2:52 PM, leon lee mailto:llr...@qq.com>> wrote: activity manager: like the name says, manage the activity, and also some memory management. When an activity starts, the activity manager would request zygote( the mother of almost everything in android ) to fork a thread, and then the activity manager manages this activity/thread. When the activity stops, the thread is not killed. So next time when the same activty is being started, the thread can be used for it at once, so to save time. But when the memory is not enough, the thread with no activity running would be killed first. This is the major part of memory management. So you can say activity manager just manages the thread, and this should be the basic module of touch. For android 2.3, the code locates in framework/base/services/java/com/android/server/am/, in case you want to look into it. Content provider: from comment of ContentProvider.java: Content providers are one of the primary building blocks of Android applications, providing content to applications. They encapsulate data and provide it to applications through the single ContentResolver interface. A content provider is only required if you need to share data between multiple applications. For example, the contacts data is used by multiple applications and must be stored in a content provider. If you don't need to share data amongst multiple applications you can use a database directly via android.database.sqlite.SQLiteDatabase. For more information, read Content Providers. When a request is made via a ContentResolver the system inspects the authority of the given URI and passes the request to the content provider registered with the authority. The content provider can interpret the rest of the URI however it wants. The UriMatcher class is helpful for parsing URIs. leon: I think Content provider is just the abstract class for data sharing between multiple applications, data lik
