Jump to content

feed back on WP10 Build 10536.1004 with AIDA64 1.1.0.6


xchtl

Recommended Posts

MS just released a new build of WP10, and I tested it with AIDA64 ver. 1.1.0.6.

 

The CPU model is not correct, my Lumia 920 uses MSM8260A instead of MSM8960

 

post-30974-0-12612500-1442468847_thumb.png

post-30974-0-28658500-1442468861_thumb.png

 

and the send buttom will not auto fill the reciever address , but the Submit report link on the About page can,and the mail the app creates now have a .txt attachment.

can you fix this?

 

 

 

 

By the way, MS have a app called Field Medic, which can monitor and gather much more info about the phone. Can AIDA64 do the same?

  • Like 1
Link to comment
Share on other sites

MS just released a new build of WP10, and I tested it with AIDA64 ver. 1.1.0.6.

 

The CPU model is not correct, my Lumia 920 uses MSM8260A instead of MSM8960

Please let me know the "RM" model ID of your phone, and we'll fix it up in the next app update. In your other post I can see "RM-822", but I'm not sure if that's the actual Lumia 920 model you mean.

 

and the send buttom will not auto fill the reciever address , but the Submit report link on the About page can

It works fine this way. The email icon is meant to be used to send the report to your email address of choice, while the other two email submit options are meant to be used to submit a report to us (FinalWire). The report submitted to us helps to fix bugs and improve the capabilities of the app, and that's why those reports include some degree of debug information.

 

and the mail the app creates now have a .txt attachment. can you fix this?

We cannot fix that, actually. The problem is that even though AIDA64 uses the same standard email sending API, Windows 10 (including Windows 10 for PCs and Windows 10 Mobile) fails to pass the whole report to the email client. So if you try to submit a report on a WP8.1 device, the whole report will be passed to the email client; but under Win10 the report will be truncated. Sadly, the same bug plagues universal Windows 10 apps as well. What we can do on our side as a workaround is to attach the report to the emails as a TXT file. That way the report included in the email body will be truncated, but the attached file will have the complete report. We never wanted to attach the report to emails, since we were certain Microsoft would fix this bug in one of the Preview builds. But since both Windows 10 RTM Build 10240 and the latest (and supposedly almost RTM) Windows 10 Mobile Preview build still has this issue, we gave up and attached the report to the emails. As soon as Microsoft fixes the email API bug, we will remove the attachment again.

 

By the way, MS have a app called Field Medic, which can monitor and gather much more info about the phone. Can AIDA64 do the same?

No, I'm afraid it can't. Regular apps have normal access to the API set of WP8.x and Win10 Mobile, while built-in apps like Settings and special apps developed by Microsoft can have special (broader) access to the Windows kernel. What is especially frustrating is that Microsoft doesn't provide a public API (not even a read-only one) to access more system details. The Windows kernel -- including the one used by Win10 Mobile and even WP8.1 -- can do a lot of very interesting tricks like SoC temperature and CPU core clock measurement, but Microsoft doesn't expose those features via a standard API call, so apps cannot access those readings.

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...