The Xplane application release for Android : http://www.x-plane.com/pg_X-Plane_for_Android.html
But for samsung we had a limitation after i had a conversation with the support of laminar research they said :
Thanks for writing in, Sir. OK, we've tracked down the issues that you're seeing here to an improperly sized cache partition on 100% of the samsung devices out there. The partition was sized for a 25MB max application size. Google recently upped the max application size to 50MB and we are the ONLY application right now that's making use of that (X-Plane 9 is 38 MB) which means we are the only application that can't be downloaded. This is NOT a google or X-Plane screwup, this is a Samsung screwup. Google said this is in direct violation with their compatibility agreement with Samsung and they're looking into it immediately. Thus, expect this to be fixed via a software update for your phone issued by Samsung in short order.
Thanks,
Randy Witt
X-Plane, Customer Support
913-269-0976
any one have information about samsung and when they level up the limitation cache for the applications ?
i have tried in Darky 7.0 JPY it seem work but it store i the internal memory phone, don't know if it's was Fixed on the JPY or it's a Darky hack
Related
Similar to the CE5 kernel that we're used to, the CE7 kernel is a 32 bit OS and runs a 4GB Virtual Address space. Similar to CE5, 2GB is reserved for the kernel and 2GB is reserved for user space.
This is where it begins to differ. CE5 handled the user space by splitting the process memory up into 32 slots of 32MB each. (This accounts for 1GB of user space, the rest is used for memory mapped files, fixed up modules, etc.) Any app currently in the foreground was swapped into slot 0 during execution, and swapped back into it's slot while it's backgrounded.
CE7 similarly uses 1GB for the process code, however now it's handled differently. Each running process is mapped to the entire 1GB space, allowing the full 1GB of VM available for use without the trickery needed to accomplish using more than 32MB of VM in CE5. This should allow for much more rich apps to be developed (whenever MSFT decides to allow us to write native code, which is coming at some point...)
This 1GB VM space will be dedicated to the process, and not accessible by any other process. The remaining 1GB of user space has to be utilized for inter-process memory sharing.
There are 256 priority levels as with CE5, for each individual thread within an app. Scheduling is handled on a round-robin basis for threads sharing the same priority level. Priority level 0 functions as a "real time" priority level and any thread running at this level will run through til completion before the scheduler runs another thread. True multitasking will not be accessible to programmers initially, though MSFT intends to unlock that later down the line (presumably around the time native code is allowed). There is no hard limit to the number of threads a program can utilize, it is only limited by the system resources available.
Regarding the limited APIs available to us "normal" programmers - OEMs and MOs will have access to an extended set of Managed APIs and a limited set of Native APIs that "normal" programmers won't get access to. This likely includes things like RIL.
Just give me an ARM build of it that is already ported over to run MSM7x00.
Thank you
Bump for visibility
good bump message too short grrr
Da_G said:
Similar to the CE5 kernel that we're used to, the CE7 kernel is a 32 bit OS and runs a 4GB Virtual Address space. Similar to CE5, 2GB is reserved for the kernel and 2GB is reserved for user space.
Click to expand...
Click to collapse
Are you sure it's CE7 and not CE6? Tweakers.net (which appears to have received the same docs you have) says it's 6 and 6 makes much more sense to me being that CE7 hasn't RTM'd yet.
Yes, i'm sure it's CE7. The docs do in fact say CE6 but the docs are dated, things move fast, and that's no longer the case
CE7 "Chelan" will likely RTM around the same time WP7 does.
Interesting. That's a lot of risk for the WP7 team to take on.
Windows 7, Windows Phone 7, so CE must be 7
What do u mean by "much more rich apps". 3D Games or what? I think that aplications on WM 6.5.5 are good and fast. Can u explain that rich applications?
where do you get this info from.. it does sound interesting
Keep it coming
CE7 supports directx 9 acceleration. XNA & SL 4. Do they sound any familiar?
Awesome information! Thanks and keep it coming; I can't wait for WP7 to be released!
Da_G said:
This should allow for much more rich apps to be developed (whenever MSFT decides to allow us to write native code, which is coming at some point...)
[...]
(presumably around the time native code is allowed).
Click to expand...
Click to collapse
what makes you think that microsoft is going to allow developpers to write native code on windows phone 7?
the whole wp7 sandbox architecture is based on .net, so it's hard to imagine that microsoft would allow native code...
aren't they going to allow it only on windows phone 7 "business edition", which much users won't have ? that would make sense...
if they do that then we are in luck the guys on here will eventually pull it apart and give it to us all, i serously doubt thats going to happen tho, i suspect 6.5 code base will continue side by side until devs support WP7 at which point there wont be such a big outcry.
FWIW I was told by members of the WP7 team that it's CE6. They weren't directly related with that aspect and weren't 100% certain (more like 99%) though.
RustyGrom said:
FWIW I was told by members of the WP7 team that it's CE6. They weren't directly related with that aspect and weren't 100% certain (more like 99%) though.
Click to expand...
Click to collapse
A MS spokesman has confirmed it is running on a hybrid CE6 R3 (meaning CE6 R3 + added features that are from CE7). No doubt in my mind that a update in a year or so after launch they will update it to the full CE7.
According to the OS Version that the device returns, its running CE 7. Check around the 6 minute mark here: http://live.visitmix.com/MIX10/Sessions/CL16
Sangheili said:
According to the OS Version that the device returns, its running CE 7. Check around the 6 minute mark here: http://live.visitmix.com/MIX10/Sessions/CL16
Click to expand...
Click to collapse
It says 7 as in Windows Phone 7.
While this is quite interesting, I have a couple of questions about this. First, since each process is now free to use the entire slice of memory assigned to userspace, does this mean that it now conducts multitasking similar to iPhoneOS and Android where it saves the application's state when backgrounded instead of the entire process itself? How does the OS handle background activities, such as background network transfers and job completions?
This leads me to my second question. Since memory allocation is done on a round-robin basis, does this mean that all backgorund activity (if backgrounded) must be completed within a certain amount of time? (For those unfamiliar with OS concepts, round-robin scheduling is a method some OSes employ where it gives a pool of jobs a set amount of time, a quantum, to complete their work. If some job in the pool doesn't finish by the end of that quantum and another job needs resources, that job is killed off in favor of the new one. More information here.) Or is the activity suspended until whatever process needs the memory is finished using it?
Thanks for the scrutinous research!
If you're referring to 3rd party apps, there is no multitasking for 3rd party apps. Depending on what the user does, the app will be "tombstoned" (application state saved).
RustyGrom said:
It says 7 as in Windows Phone 7.
Click to expand...
Click to collapse
Why would it say "Windows CE" and then append a version number that doesn't apply?
Anyway, even if it runs a WinCE 6 hybrid kernel, I hope there's SMP support there. I'd like to see a Tegra based phone. Such a device however would be a terrible waste of CPU power, if the system can't use both cores.
There you go!
http://wmpoweruser.com/?p=15451
Techticker.co.uk have published this summary of the recently held UK TechDays seminar held by Microsoft to introduce developers to their new mobile OS.
While the 9 minute video by and large cover information we have heard earlier, one issue of note is that apparently each application will only have access to 2 GB of storage on the device, irrespective of the actual size of storage.
Don't really see that as a problem; the main storage hogs are going to be music/videos/pictures, which are handled through accesible libraries without this 2GB limit. Maps for GPS apps could hit the limit, although I think I see the envisaged scenario being more on streamed data with caching.
Yeah I don't see what's the problem here. Just more BS drama from WMPoweruser to generate traffic.
Tito662 said:
Yeah I don't see what's the problem here. Just more BS drama from WMPoweruser to generate traffic.
Click to expand...
Click to collapse
The problem is that it's just heuristic restrictions on the usage of the operating system.
Why would you limit the size of the space an application can use? Is the underlying OS FAT32 and Microsoft is worried that stupid app developers will store everything as one monolithic file and therefore break their app when the store reaches 2GB?
It doesn't make sense, and restrictions that don't make sense -- regardless of what they are -- are a problem.
Yea, this is pretty restrictive, but you guys make it sound like 512MBs. How many apps do you have installed on your device as of now?
Spike15 said:
The problem is that it's just heuristic restrictions on the usage of the operating system.
Why would you limit the size of the space an application can use? Is the underlying OS FAT32 and Microsoft is worried that stupid app developers will store everything as one monolithic file and therefore break their app when the store reaches 2GB?
It doesn't make sense, and restrictions that don't make sense -- regardless of what they are -- are a problem.
Click to expand...
Click to collapse
No, it's Silverlight Isolated Storage for saving stuff 'on disk'. SIS stores have specificed, finite sizes. Who knows, it might be fat32, might be exfat.
Spike15 said:
The problem is that it's just heuristic restrictions on the usage of the operating system.
Why would you limit the size of the space an application can use? Is the underlying OS FAT32 and Microsoft is worried that stupid app developers will store everything as one monolithic file and therefore break their app when the store reaches 2GB?
It doesn't make sense, and restrictions that don't make sense -- regardless of what they are -- are a problem.
Click to expand...
Click to collapse
This is limited by Silvelight...
but i don't think this is a big problem,this limitation can easy change by update
This isn't really accurate. They haven't fully decided on a max space. WP7 uses exFAT and isn't limited to a single file size. I believe this can be configured per app and developers will be able to request more than 2GB if their app needs it for whatever reason. 2GB is just the 'default' and isn't even enforced in the CTP. http://msdn.microsoft.com/en-us/library/ff402541(v=VS.92).aspx
My bigger problem with this isolated storage is that for no reason at all other than bad engineering it's incredibly slow. sviluppomobile.blogspot.com/2010/04/wp7-isolatedstorage-speed.html about 127x slower.
When I posted about this on the msdn forum, some MVP just basically told me to "use a webservice" and if i don't than this is not the platform for me.
I had issues with that when i was making some silverlight apps some time ago. But i figured them out. What microsoft is doing here with windows phone 7 is that they are using the phone to marry apps with their cloud counterparts. Apps like netflix ap mobile nytimes will use if at most 10 mb of local storage on the device. anyone that need more than 512 mb of local storage for their app, is doing something really wrong. in regards to speed of the local storage i have realised that each local storage created is essential a true isolated storage area. meaning its essentially a small partiton formatted in some format (might be fat) and all the process of reading from that and storing to it really gets some painful io problems. But it seems with windows phone 7 the unified storage engine seems to fix that. Essential from my views of the way my programs are working. when an app is launched. all other apps are essentialy frozen in their last state, so only essential apps and stacks are running. during this process the local storage is put into ram and the application access the program at close to the native speed of the ram. when a user hits the back button it essential takes the local storage and saves back to the slower storage medium and saves the state of the application..
hope this makes sense.
What do you plan on installing on your WP7? World of Warcraft?
Imho, you don't need more than 2 gigs per app, hell, even my Tomtom with all Europe installed on it fits on my 2 gigs microSD card.
Remember, it's a freaking phone!
Hi there, I Found an item at the Dutch Tweakers.net.
They say that there is gonna be an update to Android 2.2 which will allow app. installation to micro SD.
google translation:
Google makes it likely in the short term for Android applications on a microSD card to store. Until now, applications can only be in the internal flash memory of a smart phone running on Android are stored.
Since the introduction of the G1 Android smartphone users can not store applications on a flash card into the microSD slot. Owners of an Android phone complained about the lack of opportunity in the Google Android developers, because the flash memory of the phone usually a limited storage capacity of an average 128 to 512MB has to offer. The only possibility for an end to this restriction was "rooten" of the phone.
At the introduction of the Nexus One Android 2.1 let Google know that it was working on a possible solution by Android developers to allow applications to encrypt on a microSD card to store. Meanwhile, a Google employee last Friday have let slip that the microSD storage for apps 'very soon' will be available. Possibly, the new functionality will be introduced at the Google I / O meeting on May 20 and 19 in San Francisco will be held. There are rumors Google will announce Android 2.2 and is expected to issue restrictions in this version of the mobile OS have been removed.
Click to expand...
Click to collapse
source: http://tweakers.net/nieuws/67104/go...-installatie-android-apps-op-microsd-toe.html
extra link: http://code.google.com/p/android/issues/detail?id=1151#c535
So this is good news
About time!
lets hope we get the 2.2 update asap but in meanwhile I'll just wait for the update from HTC
Fu*#in' A! Guess I will skip the rooting hussle for now and wait till the Google I/O in few weeks.
Well, after months of work and weeks of testing NMI V5 is close to ready. The big feature in V5 is the ability to write (export) to FAT partitions. To accommodate this, the Advanced tab has been completely reworked and is now much closer to the file manager everyone wants. There are also a few tweaks to the the UI in other areas.
Anyone who has an existing license and is willing to take a little risk can get the release candidate. I and others have been testing the functionality in alpha code. I can happily say, the code just passed the first round of unit testing and I'm onto the second.
For those unfamiliar with NMI, the app. allows you to connect and access external USB devices from your Nexus 7, 10, Galaxy Nexus, Xoom and most other Android devices that support OTG/USB Host. It allows you to view photos, stream video and audio without copying them to the limited space on your device. The upshot of this is you now have unlimited space for your media! The new release expands this ability to include writing files from the device to FAT partitions on the external device. More info is available on Play: http://play.google.com/store/apps/details?id=com.homeysoft.nexususb.importer
Anyway, private message me if you are interested with your e-mail address and I'll follow up.
Hello everyone,
This is the announcement of our new Gear (Galaxy) watch app. It is basically a full-featured voice assistant using Amazon Alexa voice service running on your watch.
Today, we will be starting a closed beta and hopefully if we can solve all issues, the app will be released in 10-15 days.
The application consists of a GUI on the watch and a companion app which should run on the Android phone. (only Android , no IOS unfortunately)
The Android companion app is released at:
Alexa Gear
Without the watch app, the companion Android application is useless.
We have a few known issues, and before a full release including watch side application, we would like to identify and solve all issues.. That's the reason of this closed beta.
The app supports following Samsung Watches:
Samsung Gear S2
Samsung Gear S3
Samsung Gear Sport
Samsung Galaxy Watch
If you are interested in beta testing, please see below notes for beta testers, and provide your information in the form of following example by sending an email to mrmrmrmr(at)gmail.com
Email Subject: Application for AlexaGear Beta Test
Email body:
Name: John Smith
Email: [email protected] (your email address used to login for Samsung Galaxy/Gear App Store)
Phone Brand/Model: Samsung Note 9
Watch Model: Samsung Gear S3
Phone OS: Android 8.0
Notes for beta testers:
Beta application will be open from now on and will be closed when we believe all required type of users are selected.
Applying for the beta does not guarantee that you will be selected as a beta user. We would like to keep the beta group small with enough sample of various watch/phone models.
Beta process may continue untill the application is released.
Beta download link will be provided to selected users starting later today.
Notes about the current state of the application - also important for beta attendees:
The app is not fully released and this is a closed beta. It may cause application force-close on your phone.
The debug version of the app may cause high battery usage on your phone since it is not optimized.
You may have to install Amazon's official "Amazon Shopping" application on your phone to login, if it is not already installed.
The current version of the app outputs the voice response from Alexa on your phone and not your watch. Voice response will be sent to watch in a later release.
We expect from beta users to share their experience in the form of following only. All other communication attempts may be missed (i.e. different mail subject or wrong form of mail body);
Code:
[B]Email Subject:[/B] AlexaGear Beta Test
[B]Email body:[/B]
[U]Name[/U]: John Smith
[U]Email[/U]: [email][email protected][/email][I][COLOR="Silver"] (your email address used to login for Samsung Galaxy/Gear App Store)[/COLOR][/I]
[U]Phone Brand/Model[/U]: Samsung Note 9
[U]Watch Model[/U]: Samsung Gear S3
[U]Phone OS[/U]: Android 8.0
[U]What is your experience[/U]: what works , what does not work about the application.
[U]What you liked about the app[/U]:
[U]What you did not like about the app[/U]:
[U]Your suggestions:[/U]
[U]Issues found[/U]:
[U]Issue 1[/U]: what did you do ? what happened ?
[U]Issue 2[/U]: what did you do ? what happened ?
...
*** Note that this is a clone of the original thread in Gear S3 forum. This is just for informing users of Galaxy Watch and the thread will be closed shortly.
Please do not reply here. Instead use the original thread at :
https://forum.xda-developers.com/gear-s3/themes/amazon-alexa-samsung-gear-galaxy-watch-t3854747