I've got a question about Windows Mobile in general that might be better answered elsewhere. I know the basic Microsoft response to this question, but I was wondering if anyone had any particular insight on this or knew of a similar post (even on other forums).
What does Microsoft do with those Windows error reports that pop up all the time on my Windows Mobile 6.1 device? Are they given any special priority over the regular Windows Error Reporting on the desktop OS versions (perhaps due to the smaller user base for WM devices compared with their main OS)? Does anyone know how many you have to submit before it becomes a "blip" on their error reporting radar? And the main question - does it make a difference if error reporting is on or off in the grand scheme of Microsoft development and patching? (Right now I submit the reports, but I suspect it's like one person clapping at a football game - unless everyone does it about the same thing it isn't going to make much difference.)
Just curious if there's any (non-company-line) info out there on this, especially for Windows Mobile but not necessarily limited to that.
my bet is they just use it for statistics
the typicaly info in normal windows error reports is not
close to being enough to reproduce and as such fix an error
Related
My question is really simple for many of you.
What exactly is AKU? I've seen that word gets thrown alot on this forum, and i figureed it's like a operating system or soemthing. so what's the difference between say AKU2.3 and the default Dopod 818 Pro WWE rom? is AKU2.3 more recent than the dopod rom?
Also, when i download those ROMs, there are alway sthree numbers, what are those numbers? ie. 2.13.xxxx 2.09.2222 2.07.1111, something like that? are those IPL, SPL, and Radio firmware versions respectively? I'm uberly confused.
thanks
What Is An AKU
Microsoft creates updated builds of the Windows Mobile operation system called Adaptation Kit Updates (AKU). These releases are rarely intended directly for consumers, and are usually a result of some extra features or fixes required by a particular Windows Mobile device. For example, if an OEM (Original Equipment Manufacturer) decides to add a new kind of external keyboard to a Windows Mobile Pocket PC, then some extra driver code will be required - in that case, Microsoft creates an AKU to drive the hardware.
Developer impact
It is rarely the case that developers need to know which device is running which AKU. The goal is that every device running Windows Mobile 5 runs every application. When a developer takes into account different screen sizes and orientations, either by design or programmatically, then the application should run on all Windows Mobile hardware.
End user impact
The end user of a device doesn't need to know anything about AKU builds. Perhaps a particular model of device will be updated to have new features (for example, push email) but that depends on whether the OEM and the operators decide to implement those features.
Source:
Channel9
This question prompted me to add a thread to the encyclopedia section, but then I noticed that those nifty auto links no longer work.
Now far be it for me to argue with Channel9 but:
These releases are rarely intended directly for consumers
Click to expand...
Click to collapse
So far there have been no AKU releases intended directly for the consumers nor can there be given the current format which requires flashing the whole image.
I also disagree with their assessment of the end user impact.
Not all but most people care if the brand new device they bought can do push mail, is secure or has the newest messenger version.
I'm with you Levenum
mccune said:
What Is An AKU
Microsoft creates updated builds of the Windows Mobile operation system called Adaptation Kit Updates (AKU). These releases are rarely intended directly for consumers, and are usually a result of some extra features or fixes required by a particular Windows Mobile device. For example, if an OEM (Original Equipment Manufacturer) decides to add a new kind of external keyboard to a Windows Mobile Pocket PC, then some extra driver code will be required - in that case, Microsoft creates an AKU to drive the hardware.
Developer impact
It is rarely the case that developers need to know which device is running which AKU. The goal is that every device running Windows Mobile 5 runs every application. When a developer takes into account different screen sizes and orientations, either by design or programmatically, then the application should run on all Windows Mobile hardware.
End user impact
The end user of a device doesn't need to know anything about AKU builds. Perhaps a particular model of device will be updated to have new features (for example, push email) but that depends on whether the OEM and the operators decide to implement those features.
Source:
Channel9
Click to expand...
Click to collapse
This sucks bigtime.
I'm not even sure this is possible and I'm in no way tech savvy enough to do it on my own but I'll at least ask.
I have a truck that i race alot and it has some fuel management software to set up fuel maps, timing, etc... I have an old laptop that i keep around the house solely for this vehicle tuning. I was wondering how/if i can run the software on my phone for 3 reasons..1 - i can give the wife the laptop, 2 - it would eliminate the need for the laptop in the truck, 3 - it would just be pretty damn cool.
The software is very basic so i think the phone could handle it, it's just a matter of getting it to the phone.
Any tips would be appreciated, or you can crash my dreams and tell me to move on if it's not possible.
Thanks
It depends on what OS your app was written for. If it is a DOS program then your are in luck.
You can use an emulator like Pocket DOS and run the program "as is" on your PPC (unless it has to connect to some special hardware or something).
If it is a windows app then to port it you would need the source code. Otherwise there are only two things you can do:
a) Rewrite the whole thing from scratch.
b) Search for an app for PPC that does the same thing or similar, chances are it already exists and may even be freeware.
depending on the application complication level... if it's only calculating som data, maybe (providing you know the rules it uses) it would be easy to prepare excel spreadsheet? Excel is capable of some really cool calculations. believe me ;]
Guys and gals, don’t forget to check out my brand new, MS-DOS / x86 emulation-related article at http://forum.xda-developers.com/showthread.php?p=1276884
(Sorry for flooding – IMHO, this article certainly deserves attention because it answers ALL the questions a Windows Mobile user may want to EVER ask about emulating MS-DOS. Make sure you read it!)
Disclaimer: I don't want a flame war.
There are so many glaring common sense issues with Windows Mobile. For example:
The fact that an application like nueDynamicClock exists and drastically increases batter life. This functionality should be built in Winmobile in every stock ROM.
Lack of default Winmobile alt-tab. HTC adds this, but shouldn't such a basic functionality be native to the OS?
Mediaplayer on WinMobile, lacks codecs, lacks an interface which makes it easy to casually use a WinMobile phone as a MP3 player (a la iPhone)
Lack of a basic slide lock functionality (which doesn't require a pincode)
Scrollbars, really? WM6.5 finally brings more whole screen scrolling, but that took awhile
I've thought of many other things besides this over the months, but that should be enough to demonstrate my point
Let me be clear. I am not saying WinMobile should become a clone of the iPhone. The range of devices which run WinMobile impresses. The open platform status (not bound to an app store) is a further big advantage. It has many more advantages. However the above shortcommings I mentioned seem so glaring to me. What about the Windows Mobile development team/process allows such problems to persist across multiple versions?
Is it in fact the OEMs that are responsible for these issues? Certainlly, they play a huge role in memory bloat in stock ROMs. Are they also responsible for the slow adoption of more user friendly changes to WinMobile? Is the Windows Mobile development team some kind of committee which started with a Microsoft directive to make a small screen version of Windows. Perhaps they just don't have a single person who will push for the changes which would make WinMobile much more user friendly?
Again, I'm not asking for a radical overhaul of Windows Mobile internals or architecture. Customizations which address all of the above mentioned problems are in fact standard fare, on both stock ROMs and popular cab files here at XDA-developers.
Opinions, ideas, disagreements? Alternatively, if you want to tell me why I'm totally wrong and flame me to a crisp, that's fine as well.
PS. I looked around for a thread which addressed this topic, but didn't find any. I found some close matches but nothing which really addressed this Q.
I cannot help but agree with you. The size and success of XDA-Devs is itself a testament to the inadequacies of Windows Mobile.
Furthermore, the time between OS releases is quite staggering. If Microsoft wants to take/maintain the lead (depending on your perspective) in OS design then they really should be more proactive in providing maintenance releases and bugfixes for their software.
The drive in OS design is towards useability and deskilling so anyone can use a device. To use even the basic functions of WM requires a skill level many people simply don't have.
Profile management is another conspicuous absentee.
Hi People,
Here is an extract from smartphone mag that has some bad news in it, It seems M$ is starting a fresh and non of your programs will run on WM7. Plus there will be no updates for any current phones, so I dont see much prospects for cooking WM7 that will be of any use for us. Anyway I shall let you read it yourself
Jay
Jim Karpen,
your Web Guide
Read New Windows Mobile Content Every Week day at Smartphonemag.com
Web Guide: Windows Phone 7 Won’t Run Old Apps, Won’t Work on Current Phones
Shocking news this past week about the forthcoming Windows Phone 7 Series. Not only will it not run current apps, but also current phones such as the forthcoming HTC HD2 from T-Mobile may not be upgradeable. This week, I'll point you to more information about this, as well as additional detail about Windows Phone 7 and videos of this software in action.
Current Phones Won't Run Windows Phone 7
windows Phone 7 Series Won't Run Current Apps
The other bit of news was somewhat expected, but still something of a shock: none of your current software will work on a Windows Phone 7 device. According to a post by a Microsoft executive, making a clean break from the past will allow the new phones to be as powerful and user-friendly as possible.
What does that mean? That the developers will need to rewrite their software to work on the new phones. The exec did say that Microsoft will continue to work with partners who plan to deliver Windows Mobile 6.5 devices, and that it will continue to support these products.
The big question is, Will developers bother to rewrite their software? Given that so much of the smartphone action is in the Android and iPhone arenas, they may simply choose to focus on those platforms rather than rewrite their software for Windows Phone 7. An indication of the declining interest in Microsoft's platform may be the recent announcement by Skype that they were pulling their Windows Mobile version of Skype and have ceased development of it.
It is known for quite some time, just say goodbye to our clients to finally kato no one wants their products, they are great clowns of silent men like this Seventh, very ugly and totally sure that will become famous shows blue screen, as gathered from XP
Short version: Hi, I need help to install paint.net on my Surface RT (running Win8.1RT, no jailbreak), been reading the threads around here but having absolutely no luck and I'm lost, many threads have deleted comments and I'm not sure on the continuity or lost content, if someone could guide me I will be really thankful.
Long version:
Hi, I'm late to the Surface RT party but I've been a reader of this website for years finding solutions and guidance to solve diff device issues. Found several sources (including this forum) explaining Paint.net (and other apps) can be somehow installed and run on the Surface RT, but honestly I'm lost with the "how". I'm not lazy, I do read and do my research before asking, it's just... the threads don't seem complete.
- Several threads have broken (download) links
- Several threads have deleted comments and I'm not clear on the continuity of the conversation
- I'm really confused on the jailbreak(s) and conflicts with update packages from Microsoft (producing interferences)
- Found some zip downloads identified for RT here and on other places with no instructions except "download" but the app paint.net does not run on my Surface RT, and after trying on my Win10 machine they do run on X86 (dual code? or probably not ARM after all)
- Found videos about what to do to install and run "untrusted apps" but that didn't help, and the videos have lots of comments stating it doesn't work and how it makes no sense the "untrusted" mention regarding instructions for apps found on the Store
- Found a list of ported apps (here) but I think it's quite outdated, the packages don't work or are broken and 404 not found, etc.
- The instructions regarding an alternate Store don't sound complete to me, it didn't work (I couldn't even execute the exe on my RT) and besides I just need paint.net (and this doesn't appear on the Microsoft Store, so sideload using the tool sounds confusing to me)
I'm really lost, honestly the info seems broken, well, I understand it's been years and I'm late to the party. My main interest goes to paint.net, perhaps notepad ++ and that's it. MyTube does work on my device. Interesting because when I tried several times it didn't appear on the MS Store, but somehow one day it was there and I was able to install it, I like it and does what I need.
Why playing with a Surface RT on 2020? I like it, specially the battery life, it's a nice device and does what I need (except simple image manipulation and sure, no modern internet browsing).
On a sidenote: updating to Windows 10? (RT / ARM)??? It's been a couple of months of reading and researching and I'm not sure, I don't see lots of people genuinely happy. It is not a risk I'm comfortable taking, the instructions are long and technical (I could put effort on that) but I see too many people complaining on issues, bricked devices, some report the instructions not working and some reporting the work wasn't really worth it at the end. Besides in my case when I tried came across a message stating bitlocker being active (yet it's not applied to the disk), there was an option stating "skip this drive" but I decided to stop and didn't continue, I'm not sure what does that mean, "skip?" would I loose space on the disk?. Well I'm not making two questions on one thread, just discarding the options to have a better RT, and updating to Windows 10 still doesn't feel safe to me. If anyone could share some experiences, freedom to install some additional apps, better browsing or performance, I will be happy to read.
Thanks in advance.
I cannot provide any assistance but I want to add that I am too on the same road. I have a functional RT and wouldn't mind meeting it up but I would like to have a fighting chance. Unfortunately, like you said, the info is incomplete or outdated.
If anyone has knowledge of the complete requirements to put a Windows 10 on this, or make it otherwise more useful again, it would be highly appreciated.
Danacy said:
I cannot provide any assistance but I want to add that I am too on the same road. I have a functional RT and wouldn't mind meeting it up but I would like to have a fighting chance. Unfortunately, like you said, the info is incomplete or outdated.
If anyone has knowledge of the complete requirements to put a Windows 10 on this, or make it otherwise more useful again, it would be highly appreciated.
Click to expand...
Click to collapse
Exactly. I've seen great effort from old forum members over this, but I guess many are retired and others are tired of talking about the topic, and yes, many bits of info are missing or outdated, some threads are impossible to follow, specially now after the forum upgrade (removing the dead messages).
Regarding upgrading to Windows 10, you can check here
and here:
How to install Windows 10 on the Surface RT - Alexenferman
www.alexenferman.com
Beware, it might not work and as stated by the author: you could end up with a bricked device.
There are lots stating they could do it and now have Windows 10 on their Surface RT. There is even a guy right now selling one locally already with W10 (but way too expensive). Just as this topic on installing stuff, I also found the same in regard to W10: lots of messages but little meat, and rarely a detailed or serious report on how it went, while there are also reports of bricked and failed devices.
This might be of your interest:
Being that said... I can tell you I tried, but it didn't work, my story was posted here:
Windows 10 on Surface RT working (edited thread)
Read carefully, this is about the installation of Windows 10 ARM32 on the Surface RT1. Previously tried the Elektrohax tutorial (video on youtube and also posted at Alexenferman.com) but I was unlucky on my attempts. This is the mentioned...
forum.xda-developers.com
BUT... I got lucky, my device is not bricked and I managed to install and keep the patched version of Windows 8.1 for the RT, I have that one now, applied the patches just as if I was going to install again Windows 10, but I didn't, it remains as it is in that step.
What I have now is the same device with a different W8.1 RT, more space, everything works, and I can run ported apps (I now have Paint.Net, Filezilla and others). I still don't have a better internet exprience but I like things as they are right now. The speed of W8.1 RT with the extension of new apps.
Perhaps this is helpful to you, of perhaps you get to overcome the obstacles I found and get W10 on your device, good luck, whatever happens: confirm, this is useful to new people trying.
Updated: it works, finally got W10 installed based on the video tutorial and the steps described at Alexen Ferman website. Some details here:
Windows 10 on Surface RT working (edited thread)
Read carefully, this is about the installation of Windows 10 ARM32 on the Surface RT1. Previously tried the Elektrohax tutorial (video on youtube and also posted at Alexenferman.com) but I was unlucky on my attempts. This is the mentioned...
forum.xda-developers.com
Good luck.