yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] yshalsager:
New MIUI Stable Fastboot update available!​

Device: Mi 11i EEA (haydn)

Version: V12.5.2.0.RKKEUXM | 11.0

Release Date: 2021-05-21

Filesize: 5.9 GB

MD5:

3dcd8648db5f610ab9f58b2f042a8597

Download: Here

Incremental update: Unavailable

Changelog:

[System]
New: With custom device model adjustments, any phone becomes faster after the upgrade.
New: Response to gestures is now instant.
New: With 20 times more rendering power, there are now few limits to what you can see on your screen.
Optimization: MIUI became lighter, faster, and more durable.
Updated Android Security Patch to May 2021. Increased system security.
[Notes]
New: Compose mind maps with complex structures.
New: New tools for doodling and sketching.
New: Press and hold a sketch to adjust the strokes automatically.
New: A gesture shortcut now allows you to create notes, tasks, and excerpts anywhere.
New: Excerpts save text, URLs, and images to Notes in a few simple taps.
New: Dynamic layouts bring the typography in Notes to a new level.
All-new Notes.
[Xiaomi Cloud]
New: Location info can be now reported automatically before the device is powered off

Note: Older MIUI updates are available Here
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] yshalsager:
New MIUI Stable Fastboot update available!​

Device: Redmi K40 Pro / Pro+ China (haydn)

Version: V12.5.4.0.RKKCNXM | 11.0

Release Date: 2021-05-20

Filesize: 5.4 GB

MD5:

349b2d09fb3e25664583194673f281b3

Download: Here

Incremental update: Unavailable

Changelog:

[Other]
Optimized system performance
Improved system security and stability

Note: Older MIUI updates are available Here
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] yshalsager:
New MIUI Stable Beta Recovery update available!​

Device: Mi 11X Pro India (haydn)

Version: V12.5.1.0.RKKINXM | 11.0

Release Date: 2021-06-23

Filesize: 3.0 GB

MD5:

6df9f75f411991b049d4057ee0c55f7a

Download: Here

Incremental update: Here

Changelog:

[System]
New: Response to gestures is now instant.
New: With 20 times more rendering power, there are now few limits to what you can see on your screen.
New: With custom device model adjustments, any phone becomes faster after the upgrade.
Optimization: MIUI became lighter, faster, and more durable.
Updated Android Security Patch to June 2021. Increased system security.
[Notes]
New: A gesture shortcut now allows you to create notes, tasks, and excerpts anywhere.
New: Excerpts save text, URLs, and images to Notes in a few simple taps.
New: Dynamic layouts bring the typography in Notes to a new level.
New: Compose mind maps with complex structures.
New: New tools for doodling and sketching.
New: Press and hold a sketch to adjust the strokes automatically.
All-new Notes.

Note: Older MIUI updates are available Here
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] yshalsager:
New MIUI Stable Fastboot update available!​

Device: Mi 11X Pro India (haydn)

Version: V12.5.1.0.RKKINXM | 11.0

Release Date: 2021-06-16

Filesize: 4.0 GB

MD5:

9f19987d96cbc1bbb3e12ecade6cfb92

Download: Here

Incremental update: Unavailable

Changelog:

[System]
New: Response to gestures is now instant.
New: With 20 times more rendering power, there are now few limits to what you can see on your screen.
New: With custom device model adjustments, any phone becomes faster after the upgrade.
Optimization: MIUI became lighter, faster, and more durable.
Updated Android Security Patch to June 2021. Increased system security.
[Notes]
New: A gesture shortcut now allows you to create notes, tasks, and excerpts anywhere.
New: Excerpts save text, URLs, and images to Notes in a few simple taps.
New: Dynamic layouts bring the typography in Notes to a new level.
New: Compose mind maps with complex structures.
New: New tools for doodling and sketching.
New: Press and hold a sketch to adjust the strokes automatically.
All-new Notes.

Note: Older MIUI updates are available Here
[General Topics] Newbie8000:
I have a Google Voice backup(Titanium and TWRP) with my contacts that are lost from my Google account and I've been trying to recover them with all the associated data(pic/birthday/etc). I've had no luck on my own or asking elsewhere.

https://www.reddit.com/r/androidapps/comments/mqeb7n
[General Topics] karandpr:
From the reddit thread you have

--> Disable Sync

--> Restore Backup

You can see your contacts here

--> Go to contacts app

--> Select all contacts

--> Click share button

You will get a .vcf file

--> Download .vcf file

--> Go to contacts on web and import the .vcf file.

--> They should be available on Sync again
[General Topics] Newbie8000:
Contacts are only in Voice not the contacts app
[General Topics] karandpr:
Thats a bit weird. Contacts sync was an issue in older androids that's why I had .vcf backups

Well, I am not sure what DB google voice uses, but if it's not encrypted, you can view it in DB viewer for SQLite and export the contacts as CSV.

and probably import that into you google contacts.
[General Topics] Newbie8000:
Still no luck :(
[General Topics] blackhawk:
You should save a couple copies on multiple hdds/flash drives. People forget to back up these small databases... until they're gone😖

Maybe there's a copy on a old sim card?
[General Topics] Newbie8000:
Yeah never thought to back them up. I just really hate that I can see them but have no idea how to get them to anywhere else. Unfortunately they have only ever been in my Google account.
[General Topics] blackhawk:
I had a similar experience and but had backed them up. For whatever reason chunks of the contacts vanished.

It's important to keep copies that aren't on that device at all. In a blink of an eye a virus or rootkit could destroy them all.

I use multiple hdds that aren't synced at the same time so at least most of my data is safe no matter what happens. Cloud stuff can get wiped or become inaccessible too so I put little faith in it.

Maybe an old phone you have, some is better than none. Backed up on a laptop or by a forgotten app maybe?

Maybe still stored on Google... worth a try? Google backup might take a day or so to restore them and may not even indicate they were saved. May work even if backup has been disabled by enabling it again. Google's a mess.
[General Topics] Newbie8000:
Offer still stands
[General Topics] blackhawk:
You need to search your brain if the Google backup is gone.

Maybe you backed them up long ago on another hdd or flash drive.

Samsung cloud?

A carrier based app?

Think and search. An old laptop or PC hdd?

You can't retrieve what isn't there though...
[General Topics] Newbie8000:
I've looked and no luck unfortunately.

I can see them in the GV app and at this point it isn't a huge deal to retype them from scratch, but at least some of the photos are irreplaceable.
[General Topics] blackhawk:
Not familiar with the GV apk. You can see them but not retrieve them? WTF?
[General Topics] Newbie8000:
Exactly, they are cached somehow/where but no way to export them.
[General Topics] blackhawk:
You're rooted? So you should have full access, right?

Try MIXexplorer to search for them.

[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)

[APP][2.2+] MiXplorer (full-featured file manager) Hello everyone! My name is Hootan. I work on XDA in my free time and this file explorer is my favorite Android project! MiXplorer mix of explorers (SD, FTP, Lan, Cloud and other storage...

xdaforums.com
[General Topics] Newbie8000:
From what I can tell they are buried in some sort of database.
[General Topics] blackhawk:
You will find it then🤗

Maybe in a backup file.
[General Topics] Newbie8000:
Don't know which or how to browse the database :\
[General Topics] blackhawk:
Learn by doing... by file type, size or location.

Play with it until you figure it out.
[General Topics] Newbie8000:
I've been fruitless for months. Doesn't help that I have no clue what I'm actually doing haha
[General Topics] blackhawk:
Well it's there... you need to find out where.

Assuming it's accessible on an unrooted phone.

I've never gotten into that mess. Hopefully someone here has and can give you better advice.
[General Topics] karandpr:
As I mentioned before you can use SQLite Browser https://sqlitebrowser.org/ to view database. Just dump the files with .sqlite or .db extension and view it.
[General Topics] Newbie8000:
My phone is rooted

I tried with an Android database browser but didn't find anything. I need to get my nandroid on a PC to see if I can do more digging.
[General Topics] karandpr:
IIRC Titanium Backup bascks up databases so use it to backup Google Voice data on SD card.

Then transfer the backup and look for db files inside the data. Usually it's .db or .sqlite.
[Touch Cruise ROM Development] SuperJMN:
What you ask IS what we all want to know. Why the Kaiser, but not Polaris?

Is it capable to do it? It is not? Is is a matter of time?
[Touch Cruise ROM Development] bally3:
Putting my thoughts to graphical paper here. it might help someone or it might not.

So when I enquired about whether the 3D driver for the Kaiser from htcClassAction.org would work on the Polaris, the answer was a resounding NO!..

Apparently the Polaris was missing a potential ddi.dll file that was rumoured to be included in WM 6.1.

UDK's Syrius R0 looked promising but the bugs forced me to look elsewhere so I flashed swtos new rom which claims to include the ddi.dll and have "3D Support", though swtos also mentions that there is NO hardware accelerated driver available for the Polaris.

Swtos' Rom included the 3D tests which show the D3DM demo cube actually moving at about average 3.2 fps but the lights program still shows HARDWARE RASTERIZATION: false and "Using system memory".

Athough there are clear speed differences from my UDK R8 rom, video playback is slightly smoother, overall rom speed after installing all programs faster its clear that apart from some tweaking and the ddi.dll file (or tweaking BY the ddi.dll file) this is only software acceleration.

So the question is:

IS THE POLARIS CAPABLE OF HARDWARE ACCELERATED 3D?

From my limited understanding of this, the only way to verify that the Polaris is running on hardware accelerated 3D mode is that the lights test should say "Using Video Memory".

I tried installing the kaiser 3D driver in the hope that now I have the ddi.dll file this may work. no such luck - exception errors etc..

So started looking at the dll files mentioned in the lights program and googled the file named on the first screen which was d3dmref.dll. I found this interesting article at Microsoft:

Failed on Direct3D mobile Test in Test Tools

Apparently d3dmref is a Microsoft D3D reference driver (not hardware accelerated)

(Continued)

------------------------------------------------------------------------------------------------------------------------------------------

Some questions then:

drdmref.dll is a referenced driver. So what is ddi.dll and what does it do specifically?

The ddi.dll performs better than the Samsung Omnio driver which in itself proved to show much improvement than before - why?

If we now have the required ddi.dll, what else needs to be done to make the HtcClassAction Kaiser 3D drivers work with the Polaris?

What other files are we missing?

Time for a break.. and hopefully someone might be kind enough to provide some answers. ;)
[Touch Cruise ROM Development] bally3:
Sure it is.. and here's hoping somehow we get an answer from someone.

Swtos, UDK, these guys must know a little though the actual 3D bit seems to be a carrot dangled to get everyone excited over individuals forthcoming roms.

udk does not directly answer the 3D question, swtos in his defense, has been blunt about the fact that HARDWARE acceleration doesnt exist in his rom which is fairplay.
[Touch Cruise ROM Development] starchildx:
the think is, if the chipset have hardware alleleration, so the polaris have hardware acceleration. we just need the software to unlock it. a time ago i read something about the qualcomm chip and there where standing that the chip have hardware acceleration. i dont think that htc has made a new chip for the polaris so it dont have hardware acceleration. they just used the chip how it was.
[Touch Cruise ROM Development] bally3:
Which would mean it should be capable and we should try to ascertain which, if any files are missing from the Polaris as opposed to the almost identically specced Kaiser which has now seen true hardware acceleration.

Of course it might be some simple tweaking to the registry or the dll files to make the classaction drivers working.

I Found this thread in these forums. Look at the last post:

Can anyone run the D3d Mobile samples?

"i,ve had kinda the same problem trying to get some of the samples to run on my trinity, try changing d3dmpp.AutoDepthStencilFormat = D3DMFMT_D24S8;

Dont know if its the same problem but it helped me out."

Anyone care to venture a thought?
[Touch Cruise ROM Development] bally3:
This is an interesting article:

microsoft.public.win32.programmer.directx.graphics

might be old news, might be new but this Don Crouch guy seems to know his stuff. Of interest is this line:

"Any device manufacturer should be spanked for shipping this driver as it was only designed for generating golden images to test drivers against. MS prohibits it from being shipped on any device."

This is in reference to the d3dmref.dll which IS present in the Polaris!
[Touch Cruise ROM Development] bally3:
Been reading the Kaiser thread to see if I could better understand the issue:

D3D or OpenGL ES hardware acceleration for Qualcomm MSM7200

Reading the last posts we now also have to consider another question if there is a heat issue and HTC were aware of it:

SHOULD we try to hardware accelerate the Polaris??? :(
[Touch Cruise ROM Development] starchildx:
good point. i mean, does anyone have real problems because he dont have the drivers? tomtom could be a little more faster but it works. last time i drove over 350miles and was using tomtom all the time and the device got really hot. so if its true i dont think i will use the drivers....

another question....does the kaiser really have 3d drivers ? i dont read the hole story.
[Touch Cruise ROM Development] bally3:
OK, putting the "should we" question aside I've been doing some more delving into why the HtcClassAction.org kaiser driver doesnt work out of the box (mainly cos we all would still like to see the Polaris doing hardware accelerated 3D - and who could blame us? :)

So heres what I've found out so far:

1. Kaiser driver is compatible with roms which include a ddi.dll file version 3.28 and up - someone mentioned 3.55(my file version in the swtos rom shows 3.13.0.0?)

2. We might be missing some required dll's (anyone fancy doing some digging here plz?)

... I'll investigate further!
[Touch Cruise ROM Development] ouioui01:
thanks bally3 for those news...:)
[Touch Cruise ROM Development] bally3:
You're right welcome! :)

It seems this is the missing link, the wm6.1 that htc officially releases must have a ddi.dll file of 3.28 or above built into it, but I dont know what tweaks are meant to be involved to make a difference.

I'm currently looking for a ddi.dll ver 3.28 as mine is in the Windows directory so I'm assuming its not going to blow up if I try it! (might mean yet another HARD RESET - but it would only be my 10-11th reset since udk's R0 release! - and I always have my current swtos rom on my card ready to flash back if it doesnt boot).

Anyone find this file might want to post it - or brave enough to try it? ;)
[Touch Cruise ROM Development] bally3:
Reading this thread in the Kaiser forum, whilst looking for the illusive dll and its dependencies, I came across this thread which contains a ddi.dll file that I do have as a cab on my ppc and was wondering what it would do:

Tutorial - FIX The ClearType in Landscape

It mentions that any ddi.dll file under 3,28 must be a wm6.0 ddi file.

Seeing that mine happens to be 3.1 in swtos new rom which does seem to show some hardware improvements, am I looking in the wrong place or was the 6.1 rom built with a 6.0 dll simply with some jigger-pokery (sorry my technical expression!) to make it work better?

Will the OFFICIAL WM 6.1 come with the required ddi.dll file?

I think I'll quit my hunt for the dll file for the time being and look for more info on the official WM6.1, which is rumoured for release some time in the very near future...
[Touch Cruise ROM Development] NikMel:
I just want to share my tests

This test is made by Spb Benchmark

I don't think that there is a test like this high.
[Touch Cruise ROM Development] bally3:
Who did these tests? and were they done on the current 6.0 release?
[Touch Cruise ROM Development] NikMel:
These are my test on my polaris wm 6.1 with the latest drivers from o2.

I can share this rom but there is a BIG problem camer is not working and video call too.

I made this rom.
[Touch Cruise ROM Development] bally3:
if you've installed the rom can you tell us what version the ddi.dll is then please?

..and thank you for contributing to this thread :)
[Touch Cruise ROM Development] SuperJMN:
It doesn't really matter!! All we wanna do is TESTING! Please, share that ROM to see if it has some clues for us to carry out research on possible improvements

:)
[Touch Cruise ROM Development] bally3:
hmm.. maybe you're right but the ultimate question about hardware acceleration like the kaiser lies with the version of the ddi.dll. But yes, if the benchmarks are that good its worth testing it so please do share the rom with us, who knows, with different radios the video calling and problems may get fixed and will only help to improve the rom.
[Touch Cruise ROM Development] NikMel:
I made this test after installation of keiser video fix from htc....org

Uploading.....
[Touch Cruise ROM Development] NikMel:
Triangle.exe from htcclass... is an opengl renderer.
[Touch Cruise ROM Development] bally3:
The problem we face here especially with the benchmarks is that no-one and I mean no-one seems to stick to using one particular tried and tested program. furthermore, the results of these test often show improvements that cannot be founded by running any application or game.

I keep reading these posts about 3D performance increases and 2D placebo effects but so far apart from the work of NikMel, Dwardadzyne and other members in this thread (Thanks guys!), no-one has bothered explaining what these performances mean or where they come from.

Whether you want 2D or 3D acceleration - hardware or software based - we can only hope to achieve performance increases by bettering our understanding and collaberatively working to achieve them.
[Touch Cruise ROM Development] bally3:
Today we have finally seen what looks like the "official" WWE 6.1 rom and the comments on that thread speak for themselves.

The much awaited dll file is what we've suspected for a while, a myth.

From what I have read, and I hasten to add, I have not and have no intention of flashing to this rom unless the ddi.dll file version is newer than what we have which is highly unlikely, the rom is the usual upgrade with the same performance increase seen on all the other roms.
[Touch Cruise ROM Development] bally3:
On that point, has anyone managed to find out the ddi.dll version in this rom?

Its probably the same but worth a look.
[Touch Cruise ROM Development] NikMel:
ddi.dll from wwe is same as in o2 rom.
[Touch Cruise ROM Development] bally3:
Hi Neos2007 nice to have you aboard, I'm currently going square-eyed reading some of the info on these sites to get to grips with whats needed here.

At this juncture, I'm sure there are more experienced and technically adept people on here that can inform us on what the dependencies are of these files rather than us having to trial and error to find out.
[Touch Cruise ROM Development] bally3:
Thanks NikMel, saves me time having to reflash again!

I, against my better judgement, flashed back to the R0 rom last night after so many users on here telling me the improvements were better than what i had experienced.

R0 uses the d3dmref.dll hook and of course it contains the same ddi version.

After playing with it all day today, installing the libgles, htcclass driver and te omnio driver I can only conclude that the performance improvements are the pretty much the same as the other 6.1 releases.

I fail to see where there are any particular tweaks or additions apart from the performance increases from the files named above.

Hats off to udk for a great release and the almost seamless integration of the manila 2d and other apps, but here again I saw no speed or performance improvements from the other roms.

I actually feel that the addition of the omnio dll in the roms we have with the cab version of manila yields better performances - but that could just be my experience.
[Touch Cruise ROM Development] bally3:
Dont get me wrong, I would not dare to criticise the efforts of people who are able to do things which are outside of my own abilities, especially when those individuals are doing it for little or no monetary gain and for the sole purpose of sharing with the wider community the fruits of their abilities (dash, that sounded good even for me!) :)

But I think its important to dispel some myths and misplaced perceptions here, there is no magical dll file or driver thats going to give us hardware acceleration out of the box, neither are there any significant performance increases to be had from the next batch of releases unless further progress is made on these forums.
[Touch Cruise ROM Development] bally3:
Point of note, I assume udk took this information from the rom itself:

Base ROM:

New Official HTC Windows Mobile 6.1 release

Radio: 1.59.42.15 - Official Radio

OEM: 3.13.405.0 + 3D Driver

Can anyone explain which one is the 3d driver.. they (htc) cant possibly be talking about the d3dmref.dll that microsoft say was for testing and never meant for production release surely??
[Touch Cruise ROM Development] bally3:
Seems awfully quiet tonight on here.. :rolleyes:

Anyway, to post my findings:

Firstly the ahi2dati.dll file is the only one you need to swap out from the kaiser cab to make the hardware accelerate.

(any explanations here would be useful)

The libgles_CM file whilst making the triangle work, did not actually add any significant improvement elsewhere - apart from that I had a friend with a Polaris which is still on the original o2 rom run doom on his phone fully expecting it to not work or run slow and it worked flawlessly. Funnily enough before I used the libgles_cm file from NikMel, I couldnt get this game start at all on swtos rom.

The RemoteHook method is worth exploring, I tried several variations of this method today - still testing.

Interesting to note was the post earlier about "wrapping the software driver around the hardware driver" or something to that effect?
[Touch Cruise ROM Development] bally3:
I forgot also to mention that the libgles_cm file whilst wrecking the dll checker, and effectively disabling the hardware initiation, worked flawlessly with the omio driver.

I actually felt that this method along with rogro's very useful hookswitcher tool made the system feel very smooth and stable in operation.

At this point, I have smooth test app results, the triangle spins and the cylinder/cube spin at impressive rates.

I wish I could see some fps on the cube which funnily I can if I switch to the jerky d3dmref.dll...
[Touch Cruise ROM Development] bally3:
Can anyone post the Kaiser ddi.dll files please?

3.5 or later of course! :p
[Touch Cruise ROM Development] NikMel:
Driver versions:

Official WWE for polar: 3.13

Official NLD for kaiser: 3.29
[Touch Cruise ROM Development] bally3:
Thanks NikMel.

I'm using the 3.29 from the Kaiser on my phone right now and everything works exactly the same as with the 3.13 from Polaris 6.1!

Its 1k smaller than the polaris but so far I have not seen any difference.

What happened to the later 3.5+ versions?
[Touch Cruise ROM Development] NikMel:
3.5 is an old driver
[Touch Cruise ROM Development] bally3:
older than 3.29?? :confused:

How does that work then??