IntoMobile » Stefan Constantinescu

Brief: Bharti Airtel finally getting the iPhone 3GS; no date or price given

Stefan Constantinescu — Fri, 19 Mar 2010 14:02:15 +0000

Bharti Airtel, India’s largest operator with over 124 million customers, has announced that they’re going to carry the iPhone 3GS. They’ve been selling the iPhone 3G since August 2008, and the iPhone 3GS was released internationally during the summer of 2009, so people there are probably a bit anxious.

Will they get the new iPhone, as in the one after the 3GS? Too early to tell. There’s almost no information in this article from The Wall Street Journal.

There is a splash page for the 3GS however: http://www.airtel.in/iphone3gs/

[Via: Mobile Burn]

Related News from IntoMobile:

Copyright © 2005-2010 IntoMobile. All rights reserved. Use of this feed is limited to personal use. Portions of this feed may be used with attributions, however, publishing of this feed in its entirety for public or commercial use and/or misrepresentation by a third party is not allowed. p9jxMDO3f0KB

Share this:

Review: TinyPlug MicroUSB Charger [The Smallest Charger In The World!]

Stefan Constantinescu — Thu, 18 Mar 2010 12:35:38 +0000

On February 17, 2009 the GSMA issued a press release announcing that “17 leading mobile operators and manufacturers” agreed to standardize the interface to charge the devices they’d sell in the future to microUSB by the year 2012. Now I’ve been a Nokia (NYSE: NOK) man my whole life, until February of this year that is when I purchased a Google Nexus One, but before I switched to Android I had a Nokia charger, and so did all my other friends.

If you’re thinking Finland is “Nokia-land”, and that those who don’t support Nokia get rocks thrown at them while old ladies scream obscenities, then you’re right. If you’re visiting a friend’s flat, hell even if you’re at a bar or a night club, chances are you can find a charger for topping up your mobile device. The same can’t be said about Sony Ericsson (NYSE: SNE), Motorola (NYSE: MOT), LG, Samsung, and other mobile phone manufactures, which meant that if you ever switch vendors, you’d suddenly have a stash of mobile phone chargers that were useless. You’d also have to carry your charger around everywhere you went, because no one could give you some juice.

More worrisome is that in rich western countries, places where people buy a new mobile phone every 12 to 18 months, people accumulate a bunch of chargers that they’ll probably never use. When I left Finland for 45 days, and thought I wasn’t going to come back, I gathered up all the technology in my apartment and noticed that I had at least 5 Nokia chargers with me, all with an EU plug, therefore all useless to me where I was going. I handed them out like candy to my friends, but it got me thinking, why can’t phones be sold without chargers?

Rubber isn’t cheap to produce, copper is expensive as it becomes more and more precious, and the amount of fuel used to ship a charger from China to some warehouse in Germany, before finally reaching my closest retail store in Finland, is absolutely ridiculous. By 2012, when all mobile phones use microUSB, I hope mobile phones start shipping without chargers, and I really hope phone manufactures stop including those abysmal headphones that are often bundled.

Anyway, hippie bullshit aside, about 3 weeks ago I found myself back in Finland with a Nexus One, two laptops, and only one USA to EU power converter. Now I love my mobile phone, but if you made me choose between my laptop, which rarely leaves my flat, and the ability to text and call from anywhere in the world, I’d take my laptop any day of the week. The laptop won exclusive rights to the power converter, so I was tasked with a mission to find a charger!

I didn’t even bother looking for HTC chargers, first thing I did was buy a Nokia charger, the AC-10E. It’s Nokia’s only microUSB charger you can buy in Finland, and I think the only one the company makes. It’s big, it’s bulky, but hey, it charged my Google (NSDQ: GOOG) Nexus One without any issues. Why would there be any issues, a standard is a standard, right?

Fast forward to a few days ago, and I’m browsing around Verkkokauppa, Finland’s largest chain of electronic stores, on a boring Saturday afternoon. I stumble across the TinyPlug MicroUSB” charger and knew I had to have it. It’s smaller, much smaller, than the official Nokia charger, and for a guy like me who’s on an airplane at least once every 3 months, reducing weight and volume is critical. It’s also convenient to have one charger in the bedroom and one in the kitchen/living room.

Since it’s microUSB it just works, it also appears to be charging my Nexus One at the same speed as my Nokia charger, and according to the online product page it has an idle power draw of 0.3 watts. Using the image below, a photo I took of the back of the packaging that housed my Nokia AC-10E, the TinyPlug has a 2 star power efficiency rating while the Nokia has a 5 star. If I was really green I’d care about that, but the fact that I no longer have a car, and have dramatically cut down on my consumption of meat since it’s crazy expensive in this country, I’ll forget about such small things as star ratings.

The best part about the charger is the price. While the Nokia AC-10E cost me 20 EUR, the TinyPlug was only 9.90 EUR! If you’re in Finland, and have a new mobile phone, I’d highly recommend you pick one up. Assuming you’re in another country, then you’ll probably see the TinyPlug in shop near you at some point, most likely under a different brand.

This product was obviously made by some no name Chinese manufacturer, and I’m alright with that. Thank you GSMA.

Related News from IntoMobile:

Share this:

NPD Group: 3 out of every 10 mobile phones purchased in the USA during Q409 were smartphones

Stefan Constantinescu — Thu, 18 Mar 2010 11:06:11 +0000

The NPD Group, which uses monthly survey results from over 150,000 consumers, has released some interesting numbers. They say that 31% of all mobile phones purchased in the United States during Q409 were smartphones, compare that to only 23% in Q408. Two out of every three of those smartphones cost consumers $150 or less, compared to one out of two smartphones purchased in Q408. Do the increased volumes make up for the increased penetration of cheaper smartphones? According to NPD, not really. They say that smartphone revenues rose only 21 year on year, compared to 37% the year prior.

“Although we are seeing more expensive models among the best-selling handsets, carriers are now offering some popular smartphones for less than $100,” said Ross Rubin, executive director of industry analysis for NPD. “As the average price of these highly capable devices continues to fall, the price of data plans and ease of use will emerge as more significant factors to limiting consumer sales growth.”

Shameless plug here, one of my predictions for 2010 was “one in three people will end up owning a smartphone by the end of next year, but sadly the smartphones of 2010 will be nothing more than the smartphones of 2009, except in different packaging with different colour plastic.” As we saw with the HTC Legend, and as we’re going to see as the year progresses, phone manufactures are pushing the industry into two categories: cheap, and premium smartphones.

Sure, 7 out of 10 Americans bought phones that can’t do anything more than talk and text, but those are Q409 numbers, how much you want to bet that figure drops down to 5 out of 10, or even 4 out of 10, still buying the lowest of the low end in Q410?

[Via: PR Web]

Related News from IntoMobile:

Share this:

Nokia CEO Olli-Pekka Kalasvuo dodges questions about Qualcomm based phone; the answer is maybe

Stefan Constantinescu — Thu, 18 Mar 2010 10:26:03 +0000

A little over a month today, Qualcomm (NSDQ: QCOM) CEO Paul Jacobs told Finnish newspaper Helsingin Sanomat that by the end of this year there will be a Nokia product out on the market using the company’s well known Snapdragon processor, and that it would run Symbian. When Business Week asked Nokia (NYSE: NOK) CEO Olli-Pekka Kalasvuo about the possibility of such a product, he replied:

I cannot comment on that one. All I can say is that Qualcomm definitely is a potential partner going forward. The companies did fight a long time in court, and now we see them as a potential partner.

No comment is code for “yes, but if I said something then corporate communications would kill me.” I’m sure after he accidentally announced “Leevi and Gadget” in a conference call almost 2 years ago, he got a lesson about what he can, and can’t, say in public.

Read the whole interview to hear about what he has to say about Palm (NSDQ: PALM), Nokia’s partnership with Microsoft (NSDQ: MSFT), and the same tired description of how Nokia is working hard to make themselves relevant in the North American market once more.

Related News from IntoMobile:

Share this:

Video: Google Maps 4.1 for Android [Maps Live wallpaper, Latitude widget]

Stefan Constantinescu — Thu, 18 Mar 2010 09:28:30 +0000

Google (NSDQ: GOOG) has just released Google Maps 4.1 for Android devices running 1.6 or higher, and it’s a pretty minor update. New features include:

New search results page that shows everything you need all in one place. You can also go through the different search results by swiping left to right versus having to go back to the search results list, scrolling, and selecting another location.
Google Latitude widget, which I demo in the video above, that allows you to see at a glance the three people nearest to you.
Google Maps Live wallpaper, which I also demo in the video above, is a feature that only works on Android 2.1 devices. It basically makes your wallpaper a map of where you currently are. You can switch between normal, satellite, and terrain maps, and there’s also an option to show traffic.
Multiple account support, for those of you who have more than one Gmail account and have different locations starred in different locations, or different Latitude friends on different accounts.

Not anything that makes me go “wow”, but then again Google Maps already does practically everything I need it to do. The only feature I’d really want is offline maps support. It shouldn’t be that hard for Google to solve this problem. My Latitude account is tied into Google Maps, so the company already knows where I spend most of my time. Using that information they can cache the map tiles for every zoom level in that specific geographic area. Each map tile can have a serial number that’s checked against the latest values stored in the Google cloud. It would solve the problem of minimizing the amount of space mapping data occupies on my memory card, and it would also solve bandwidth issues since I’d only be downloading new tiles when the old tiles are considered out of date.

Come on Google, you can do it!

Oh and before you ask, I don’t have an estimated release date for Maps 4.1 for other platforms. Sorry.

[Via: Google Mobile Blog]

Related News from IntoMobile:

Share this:

HTC flat out says “Apple, you’re wrong” and presents their history as a company as proof of innocence

Stefan Constantinescu — Thu, 18 Mar 2010 07:18:26 +0000

When Apple sued HTC earlier this month, you could hear mobile phone geeks around the world going “that’s not right.” HTC’s software innovations, mainly Sense UI, bear almost no resemblance at all to Apple (NSDQ: AAPL)’s iPhone user interface. Does their hardware look a bit like the iPhone? Maybe, but then again just look at what’s out there on the market and it’s painfully obvious that after Apple introduced the iPhone in the summer of 2007, everyone followed with their own touch screen slate form factor device.

Later on we’d find out that HTC didn’t even know about the lawsuit until Apple published a public press release saying that they’ve been sued, and that’s just plain nasty. Apple’s legal department appears to be rotten to the core, and even Nokia (NYSE: NOK), which is also in a legal argument with Apple, have said that the “legal alchemy” Apple lawyers are using is filled to the brim with “revisionist history, misleading characterizations, unsupported allegations and flawed and contradictory legal theories”.

Today HTC issued a statement titled “HTC DISAGREES WITH APPLE’s Actions”, which leads us to believe that the person writing said press release only realized they had capslock enabled towards the end of that headline. In it they cite the praise they’ve been awarded by Fast Company, MIT Technology Review, and the recognition the GSMA has given the HTC Hero by calling it the “Best Phone of 2009″. They further go on to list that they made the first Windows PDA in 1998, first Windows Phone in 2002, first 3G (EVDO) smartphone in 2005, first gesture based smartphone in 2007, first Android smartphone in October 2008, and first WiMAX phone during November 2008.

Now a judge can look at this and say “so what?” It doesn’t matter what HTC has done in the past, nor what the press are saying about HTC, if there are clear patent violations then it’s an open and shut case. Do I, with an incredible lack of legal expertise, and unpaid speeding tickets in several states, think what Apple is doing can somehow be justified? Absolutely not. Patents slow us, and by us I mean humanity, down. Ideas are only as good as their implementation, and if HTC did something better than Apple then they deserve more sales, and visa versa.

You can read HTC’s full statement after the jump.

[Photo above is from Geek.com and is of the HTC T-Mobile (NYSE: DT) Pocket PC Phone Edition, which HTC say is "the first 3.5-inch color touch screen smartphone in the United States in 2002".]

HTC DISAGREES WITH APPLE’s Actions
Seattle – March 17, 2010 – HTC Corporation today outlined its disagreement with Apple’s legal actions and reiterated its commitment to creating a portfolio of innovative smartphones that gives consumers a variety of choices. Founded in 1997 with a passion for innovation and a vision for how smartphones would change people’s lives, HTC has continually driven this vision by consistently introducing award-winning smartphones with U.S. mobile operators.
“HTC disagrees with Apple’s actions and will fully defend itself. HTC strongly advocates intellectual property protection and will continue to respect other innovators and their technologies as we have always done, but we will continue to embrace competition through our own innovation as a healthy way for consumers to get the best mobile experience possible,” said Peter Chou, chief executive officer, HTC Corporation. “From day one, HTC has focused on creating cutting-edge innovations that deliver unique value for people looking for a smartphone. In 1999 we started designing the XDA[i] and T-Mobile Pocket PC Phone Edition[ii], our first touch-screen smartphones, and they both shipped in 2002 with more than 50 additional HTC smartphone models shipping since then.”
The industry has recognized HTC’s contributions through a variety of awards including Fast Company’s 2010 Top 50 Most Innovative Companies and MIT Technology Review’s 2010 50 Most Innovative Companies. The GSMA also recently awarded the HTC Hero as the “Best Phone of 2009.” Some of HTC’s technology firsts include:
First Windows PDA (1998)
First Windows Phone (June 2002)
First 3G CDMA EVDO smartphone (October 2005)
First gesture-based smartphone (June 2007)
First Google (NSDQ: GOOG) Android smartphone (October 2008)
First 4G WIMAX smartphone (November 2008)
In 2009, HTC launched its branded user experience, HTC Sense. HTC Sense is focused on putting people at the center by making phones work in a more simple and natural way. This experience was fundamentally based on listening and observing how people live and communicate.
“HTC has always taken a partnership-oriented, collaborative approach to business. This has led to long-standing strategic partnerships with the top software, Internet and wireless technology companies in the industry as well as the top U.S., European and Asian mobile operators,” said Jason Mackenzie, vice president of HTC America. “It is through these relationships that we have been able to deliver the world’s most diverse series of smartphones to an even more diverse group of people around the world, recognizing that customers have very different needs.”
For more information on HTC’s history of innovation, please visit: www.htc.com/history.

Related News from IntoMobile:

Share this:

Dear Opera: Why are you showing doctored screenshots of your product?

Stefan Constantinescu — Tue, 16 Mar 2010 17:32:32 +0000

Opera is one of my favorite companies, ever. Because of their Opera Mini product I decided to purchase a smartphone, the Nokia (NYSE: NOK) E61, not because it ran Symbian, but because it had a 320 x 240 pixel resolution screen, had WiFi, and it let me see more of the internet. This was back in 2006 when American 3G was still a joke, and the iPhone was a year away from launch. I blogged about that device, a lot, and about Nokia, and because of it I got a job at IntoMobile in June 2007, found myself in Finland a month later, and then eventually found a job within Nokia.

After I was let go by Nokia in April 2009, a friend of mine said I should talk to a friend of his at Opera. We had our first interview in Helsinki, and then a second in Oslo, Norway [Disclosure: flight + hotel was paid for by Opera]. I really wanted to work on the Opera Mini team, but unfortunately I didn’t get the position.

Still, that doesn’t change how much I love the product, and the company itself. I’ve always been, and always will be, a notorious Opera Mini fanboi. While I was attending University, I’d often show my fellow students a few demos, and go so far as to install the application on their devices whether or not I had their permission. Which is why I’m a little sad to see this screenshot appear on http://www.opera.com/mobile/features/

That’s beautiful, crisp, clear, but it’s not real. Here’s what The New York Times really looks like with Opera Mini 5 Beta for Android:

This is with graphics quality set to high, and the font cranked down to small. Notice how “Try Times Reader 2.0″ appears all the way on the right side in Opera’s official shot, yet it’s on a different line all together with Opera Mini Beta 5 running on my Nexus One. Also look at how the official shot has the “Last Update: 5:16 AM ET” fit on one line, while my time doesn’t even appear. The text “Home Page” is black in the official photo, yet blue in my version.

Is there some custom super small font option that’s hidden from users? Are you just rendering these official shots in Photoshop? I was one of the fortunate people who got to see Opera Mini run on an iPhone in Barcelona at Mobile World Congress, and it looked way better than the Android version does today. I know the Android version is still in beta, so I have high hopes that it will eventually be on par with the other platform specific versions, but these font rendering issues I’ve highlighted are really frustrating. Maybe it’s because the stock browser in Android 2.1 is just so damn good?

I don’t really know, I just hope it gets fixed.

Related News from IntoMobile:

Share this:

Nexus One sales after 74 days: 135,000 vs 1 million for the iPhone and 1.05 million for the Droid

Stefan Constantinescu — Tue, 16 Mar 2010 13:48:15 +0000

Remember when Apple (NSDQ: AAPL) sent out that press release saying they sold 1 million of their highly anticipated iPhone? Where were you when it hit the newswire? It took 74 days for Apple to do it, and that’s the benchmark that most new phones will be measured against. Flurry, an application analytics firm that claim at least 80% of applications running on the iPhone and Android devices have their tracking software embedded, says that after 74 days of being on sale, the Nexus One has had only moved 135,000 units.

Take this number in context. The Nexus One went on sale after the holiday shopping season, it only ran on one network: T-Mobile (NYSE: DT), and you could only buy it online. I’m personally responsible for two of those sales (the other Nexus One went to a friend of mine in Finland) and our newest Editor Blake brings that number up to three. Will has one, but he got it for free because he went to some Google (NSDQ: GOOG) event. Bastard.

So is it right to call the Nexus One a failure? We don’t know what benchmarks Google internally, and we don’t know how many Nexus Ones they have sitting in some warehouse collecting dust. It’s a tough call. The fact that the Droid sold 50,000 more units in 74 days compared to the iPhone says that people like Android, so that’s not the issue here. The platform is sound.

Most people who will be using a Nexus One by the end of this year are not going to be using the “Nexus One” straight from Google, they’ll have the HTC Desire, otherwise known as the “Nexus One with HTC’s secret sauce”. I’m more interested to see how those units move rather than the stock (read: bland) Android 2.1 packing Nexus One.

Oh and one more thing … The iPhone 3GS, which went on sale globally, sold 1 million units in 3 days.

Related News from IntoMobile:

Share this:

StarHub becomes first South East Asian operator to roll out 42.2 Mbps HSPA+ [Hey AT&T, learn!]

Stefan Constantinescu — Tue, 16 Mar 2010 10:08:51 +0000

Singaporean operator StarHub, using equipment from Chinese vendor Huawei, has successfully completed trials using dual carrier HSPA technology to achieve peak download speeds of 42.2 Mbps. Now forget about the fact that this sort of technology isn’t yet available in mobile phones, much less USB sticks, but the sheer fact that they switched to dual carrier technology is yielding StarHub an extra 20% worth of capacity due to increased spectral efficiency. The upgrade is expected to be completed by Q3 of this year and is mainly just a software update, minimal additional hardware is required.

How does dual carrier technology work? You’ll want to read this 5 page PDF, or this blog post, to get a better grasp of the idea. Basically it’s like drinking a beverage using two straws versus one, you simply get more.

AT&T can learn a lot from this, as well as the other American operators, who currently have issues giving their customers service with the limited amount of spectrum they have. Now yes, America is huge, and has 300 million people, and most of it is filled with corn fields, but that excuse only goes so far. Increasing capacity by 20%, even if just for cities like New York and San Francisco, can go a long way at improving public perception about your network.

Learn AT&T, it’s your duty. As MG Siegler from TechCrunch said, whatever you did in Austin for SXSW, you should be able to do for the entire country.

[Via: Cellular News, Straits Times, MIS Asia]

Related News from IntoMobile:

Share this:

Windows Phone 7 Series build 7.0.0.6077 extracted, will only run on x86, but let’s see where this goes

Stefan Constantinescu — Tue, 16 Mar 2010 09:20:27 +0000

XDA-Developers, the wild children of our day who have all the free time in the world to poke and prod at mobile operating systems at a level that mere mortals such as you and I can’t even begin to fathom, have dumped build 7.0.0.6077 of Windows Phone Series 7 from the emulator that was given to developers yesterday at MIX. It has a build date of March 02, 2010, only runs on x86 compatible devices at the moment, and comes with a huge list of files that’s available after the jump. Will these tinkerers find a way to make this run on mobile devices? Will they find something that Microsoft (NSDQ: MSFT) doesn’t want to talk about just yet?

Who knows, we have until the end of this year to get devices in our hands so a lot can happen between now and then. Keep your eye on this thread to see what, if anything, will happen with this build.

xde_nk\33e56942-4f86-4b44-a9cd-1b2a84b508a8.dsm – xde_nk – 7.0.0.6077
OEMXIPKERNEL\19d4441e-9352-8e98-266c-f387d94e0f4f.dsm – OEMXIPKERNEL – 7.0.0.6077
MSXIPKERNELLTK\42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm – MSXIPKERNELLTK – 7.0.0.6077
MSXIPKERNEL\b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm – MSXIPKERNEL – 7.0.0.6077
BaseDrivers_NK\eebbabb2-0689-4692-9e80-5eb9a62126d1.dsm – BaseDrivers_NK – 7.0.0.6077
XNA\828622a1-0c9f-4565-ba79-9eb0be1bbb58.dsm – XNA – 7.0.0.6077
XmlLite\099208f2-993f-443c-afd9-1994628c5870.dsm – XmlLite – 7.0.0.6077
XDE_AppProv\5ba3eeff-f8bc-4c43-8175-bf218e964aa0.dsm – XDE_AppProv – 7.0.0.6077
WindowsLiveIDUI_Lang_0409\91920d4b-5895-af4f-5035-cb7487ae2978.dsm – WindowsLiveIDUI_Lang_0409 – 7.0.0.6077
WindowsLiveIDUI\be95ad85-199c-45fd-a84b-5e68c0698af8.dsm – WindowsLiveIDUI – 7.0.0.6077
WindowsLiveIDINT\7c5b3e47-9c8f-4650-a6bf-087d5eac75ed.dsm – WindowsLiveIDINT – 7.0.0.6077
WindowsLiveID\c5e18d8a-6fa7-49c0-a5f0-a5940e2dbfbe.dsm – WindowsLiveID – 7.0.0.6077
WinCENLS_0804\5419450c-789f-485a-a829-f1b95003013c.dsm – WinCENLS_0804 – 7.0.0.6077
WinCENLS_0412\1abf8906-6b79-43af-bb48-4364b10e8061.dsm – WinCENLS_0412 – 7.0.0.6077
WinCENLS_0411\c52c0779-0b15-46d1-9a21-181445cd792d.dsm – WinCENLS_0411 – 7.0.0.6077
WinCENLS_0404\ce3f7f50-c71c-45e7-9e8e-1bfc189788d5.dsm – WinCENLS_0404 – 7.0.0.6077
WinCENLS\7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm – WinCENLS – 7.0.0.6077
WebSearch_Lang_0409\8cd9ad7f-f3fe-7365-5763-fc2f11c1f240.dsm – WebSearch_Lang_0409 – 7.0.0.6077
WebSearch\b86400e0-6d0e-4c29-bac8-a856dffd13a4.dsm – WebSearch – 7.0.0.6077
Watson_Lang_0409\654ec3ba-3997-dfa7-fd72-736e32a2e02e.dsm – Watson_Lang_0409 – 7.0.0.6077
Watson_Core\4c09c376-dc94-4033-9277-b6732fe19069.dsm – Watson_Core – 7.0.0.6077
Watson\8ba872a2-01d5-44d4-98a7-ddf561744635.dsm – Watson – 7.0.0.6077
TouchInput_Lang_0409\c4be93b0-a48c-6411-0188-eec5b43538d9.dsm – TouchInput_Lang_0409 – 7.0.0.6077
TouchInput\b09fc8eb-7304-4563-8741-3bcadfc27787.dsm – TouchInput – 7.0.0.6077
ToolConnectivityShared\1f7cf92b-dfc5-4249-815e-9d3bd1f4c733.dsm – ToolConnectivityShared – 7.0.0.6077
Timezones_Lang_0409\0b30073b-a639-0a26-22b0-75cbd0752a18.dsm – Timezones_Lang_0409 – 7.0.0.6077
Timezones\cfd1c0ff-6ba9-4752-bfa9-a79bdd4cb74b.dsm – Timezones – 7.0.0.6077
TaskScheduler\33b6aa65-facc-449c-b9e9-f5d4edb768af.dsm – TaskScheduler – 7.0.0.6077
SyncPlatform_Lang_0409\45d69177-7829-af34-172e-404805313539.dsm – SyncPlatform_Lang_0409 – 7.0.0.6077
SyncPlatform_DPI_262\7ba0c0df-491d-ffd8-6425-bb07e37b3f3a.dsm – SyncPlatform_DPI_262 – 7.0.0.6077
SyncPlatform\61a090cf-c246-4065-b12e-66c22ce83ac1.dsm – SyncPlatform – 7.0.0.6077
SyncApps_Lang_0409\0552eaa7-4321-b577-7216-37bb38d38dda.dsm – SyncApps_Lang_0409 – 7.0.0.6077
SyncApps\3d9ac40c-bcc2-49fd-a5fb-0abe3e5da50d.dsm – SyncApps – 7.0.0.6077
Start\bdaa2dd3-8d92-4994-b468-2f0fb4da9c9d.dsm – Start – 7.0.0.6077
SSPI\36f0218d-c900-43f4-ac08-7fc437844ec6.dsm – SSPI – 7.0.0.6077
SQM\a4ded16e-eadb-4ced-97ee-3af7ecfc6796.dsm – SQM – 7.0.0.6077
SQLCEPROV_Lang_0409\c00f3e63-1c73-d801-34c7-250512fd1c71.dsm – SQLCEPROV_Lang_0409 – 7.0.0.6077
SQLCEPROV\591eaaa4-6de6-43cb-9aee-5b7c353454f6.dsm – SQLCEPROV – 7.0.0.6077
SQLCE\7ab11bc8-e753-4a4b-b56a-c39c993cbcda.dsm – SQLCE – 7.0.0.6077
Splash_Lang_0409\1117efb9-69ea-1922-8df8-f33ae2f37d19.dsm – Splash_Lang_0409 – 7.0.0.6077
Splash\0958644d-55f7-47c1-a200-75c109d9f936.dsm – Splash – 7.0.0.6077
Speech_UX_Core_Lang_0409\1540e604-ff97-a7d9-b651-dafd0558c1dc.dsm – Speech_UX_Core_Lang_0409 – 7.0.0.6077
Speech_UX_Core\1753ef60-fa74-48d6-a76c-1394da517adb.dsm – Speech_UX_Core – 7.0.0.6077
Speech_Core_Lang_0409\4ae82341-ec84-c283-99fc-9c9623996992.dsm – Speech_Core_Lang_0409 – 7.0.0.6077
Speech_Core\855094f4-bd1b-41f9-8cd0-c6da3240eb8d.dsm – Speech_Core – 7.0.0.6077
Sounds_Lang_0409\eeb789b6-1b72-cabd-38bc-f3739797dc57.dsm – Sounds_Lang_0409 – 7.0.0.6077
Sounds\c6f7de6a-d62a-49a4-9ae0-840888c20edc.dsm – Sounds – 7.0.0.6077
SNTransports\c0c4eef3-b207-41e2-9052-acfc417b8519.dsm – SNTransports – 7.0.0.6077
Skybox_Lang_0409\009a8a9c-2776-1a09-1067-996496c2eb7a.dsm – Skybox_Lang_0409 – 7.0.0.6077
Skybox\34b951c4-691b-417b-bc9e-07e79da8af78.dsm – Skybox – 7.0.0.6077
SILVERLIGHT\e6e6978a-455d-4cd6-9a22-2b05d9e11164.dsm – SILVERLIGHT – 7.0.0.6077
Shell_Lang_0409\00b17e69-7f60-43ff-c446-e2494b0e4093.dsm – Shell_Lang_0409 – 7.0.0.6077
Shell_DPI_262\73915d26-e190-42ef-889d-7e8d544639b2.dsm – Shell_DPI_262 – 7.0.0.6077
ShellServices_Lang_0409\9e96ac54-2b4b-0099-a954-745a00adcd97.dsm – ShellServices_Lang_0409 – 7.0.0.6077
ShellServices\c5f302af-97f8-42b0-a119-8ffc5433d02d.dsm – ShellServices – 7.0.0.6077
ShellDogfood\eaf0c4bf-c7c0-4c61-8ea6-9de1e51bda41.dsm – ShellDogfood – 7.0.0.6077
ShellCore_Lang_0409\eb0f3766-905f-f3b7-7372-0b23db590b28.dsm – ShellCore_Lang_0409 – 7.0.0.6077
ShellCore_DPI_262\67f9a05b-efc2-26bb-6851-2576f6544e2e.dsm – ShellCore_DPI_262 – 7.0.0.6077
ShellCore\29b2075f-6ab3-4581-8f83-57bffd606049.dsm – ShellCore – 7.0.0.6077
ShellApps_Lang_0409\39a086a5-e065-6df5-7916-f282b75d9da7.dsm – ShellApps_Lang_0409 – 7.0.0.6077
ShellApps\a8d4a143-572c-4969-a6a1-93f26728a039.dsm – ShellApps – 7.0.0.6077
Shell\c7a3d8a1-73a0-4245-b11d-48e40e8dd4b1.dsm – Shell – 7.0.0.6077
Settings_Lang_0409\e175e1af-94ac-dd81-a4c1-2a4077c91db8.dsm – Settings_Lang_0409 – 7.0.0.6077
Settings\8c9c0c34-b77d-45fb-9e4e-d53ac5900244.dsm – Settings – 7.0.0.6077
SECURITYSERVICES\8184b7c0-4746-4d2e-8676-3797fd01315f.dsm – SECURITYSERVICES – 7.0.0.6077
SecurityCore\d62f1cfd-4536-4a6f-bc6b-84a89db28cc1.dsm – SecurityCore – 7.0.0.6077
SearchPlatform_Lang_0409\050b8fe8-4b94-3d02-81a8-53742ea96b44.dsm – SearchPlatform_Lang_0409 – 7.0.0.6077
SearchPlatform\3ae1871c-08c1-43e8-af2f-ae9e2a51744f.dsm – SearchPlatform – 7.0.0.6077
SampleAppPkg\b10f0e53-36f0-40d4-a7e3-9af3b18ef2a1.dsm – SampleAppPkg – 7.0.0.6077
RPC\949420e8-3574-41dd-9573-f1f663a21247.dsm – RPC – 7.0.0.6077
RMS\ff940ad8-7a8b-492a-ac5c-063a3debb7c2.dsm – RMS – 7.0.0.6077
PPGPROV\4f90fb0d-3173-464b-9e60-e5925a044950.dsm – PPGPROV – 7.0.0.6077
PolicyMerged\c7b6e4d6-1deb-4ebb-b457-e64ba340c891.dsm – PolicyMerged – 7.0.0.6077
Phone_Lang_0409\7951a8f9-a7b7-0bed-d218-42e656dd33d7.dsm – Phone_Lang_0409 – 7.0.0.6077
Phone_DPI_262\2522760d-1e0b-c5c4-8e6e-ccdb3fffc8dc.dsm – Phone_DPI_262 – 7.0.0.6077
Phone\542b4166-5323-4f10-a701-1ef28b5708be.dsm – Phone – 7.0.0.6077
OS\d5ab0034-8aac-4a19-b5c4-a8b01b5bbe87.dsm – OS – 7.0.0.6077
OpenMPCE\495ffbda-0c86-467b-b3a4-606f8f0bcd4c.dsm – OpenMPCE – 7.0.0.6077
OFFICE_WORD_Lang_0409\74121de4-928c-13ca-8025-ffc2e91377bb.dsm – OFFICE_WORD_Lang_0409 – 7.0.0.6077
OFFICE_WORD\554d6561-1634-4956-a12a-1c5c7eb2f6ec.dsm – OFFICE_WORD – 7.0.0.6077
OFFICE_SPMC_Lang_0409\07764450-ac17-79af-9708-234d0e415782.dsm – OFFICE_SPMC_Lang_0409 – 7.0.0.6077
OFFICE_SPMC\fd0c030c-89a4-4618-8208-2b6a4b87cf4e.dsm – OFFICE_SPMC – 7.0.0.6077
OFFICE_POWERPOINT_Lang_0409\4e025bc6-db96-e24d-da6e-7d27e19f4b2d.dsm – OFFICE_POWERPOINT_Lang_0409 – 7.0.0.6077
OFFICE_POWERPOINT\64f6f2a3-2c1f-4435-b2ed-d6f44117de98.dsm – OFFICE_POWERPOINT – 7.0.0.6077
OFFICE_ONENOTE_Lang_0409\b55e45a9-1017-248a-5a3d-8cf37cb5462c.dsm – OFFICE_ONENOTE_Lang_0409 – 7.0.0.6077
OFFICE_ONENOTE\ae838993-ed1a-453f-924a-ea35a0737575.dsm – OFFICE_ONENOTE – 7.0.0.6077
OFFICE_OMHUB_Lang_0409\0b2ae811-a031-f435-6ba1-bfe5dcbbb348.dsm – OFFICE_OMHUB_Lang_0409 – 7.0.0.6077
OFFICE_OMHUB\1bb897b0-e94b-4af0-a18d-d5fcae684bde.dsm – OFFICE_OMHUB – 7.0.0.6077
Office_Lang_0409\75bf5ce5-7b57-d527-b59c-5ae85c548c45.dsm – Office_Lang_0409 – 7.0.0.6077
Office_Excel_Lang_0409\02c9689b-e1b6-f0f3-b705-c598b79bd2c0.dsm – Office_Excel_Lang_0409 – 7.0.0.6077
OFFICE_EXCEL\43f3380a-ff6e-444e-a31f-32584fa88488.dsm – OFFICE_EXCEL – 7.0.0.6077
Office_DPI_262\76bd990c-4b0a-7431-f488-268ee5f30f82.dsm – Office_DPI_262 – 7.0.0.6077
OfficeCore_Lang_0409\15a21a99-e30a-fb20-ca04-907860075694.dsm – OfficeCore_Lang_0409 – 7.0.0.6077
OfficeCore\c470575f-1798-4def-9f54-626f23ebbc29.dsm – OfficeCore – 7.0.0.6077
Office\a5f15312-2e67-4c03-a5d0-21a982bb0721.dsm – Office – 7.0.0.6077
NetWlanCore\bc7f7897-2b2d-4338-8f25-66e99a4ab865.dsm – NetWlanCore – 7.0.0.6077
NetServices\d7299380-e070-44d5-86ea-e060894697a2.dsm – NetServices – 7.0.0.6077
NetFeatRedir\950ce956-00cf-4cd1-b6a5-26cdb1094bfc.dsm – NetFeatRedir – 7.0.0.6077
NETCORE_Lang_0409\123640b9-9ef1-d4fe-1f18-ed0cae2e7536.dsm – NETCORE_Lang_0409 – 7.0.0.6077
NetCore\e58cb45d-b3fe-405d-85cf-4d19c2ae80be.dsm – NetCore – 7.0.0.6077
NETCF\fee507c4-1f41-46f2-a341-62b4bc1a9d80.dsm – NETCF – 7.0.0.6077
MTPZ\d224b788-d34a-4727-b83f-6882c2e6091c.dsm – MTPZ – 7.0.0.6077
Metadata\034e7cf6-8a37-40ad-85bd-6851b921866a.dsm – Metadata – 0.0.0.0
MediaApps_Lang_0409\913faa25-a01b-520f-2e8a-a554f8279e4c.dsm – MediaApps_Lang_0409 – 7.0.0.6077
MediaApps\717f7343-370c-49b8-a03b-9336de016048.dsm – MediaApps – 7.0.0.6077
Location_Lang_0409\8fba7df0-e442-d04f-4e46-fe0265169cfd.dsm – Location_Lang_0409 – 7.0.0.6077
Location\64ebc3ee-b241-46a5-9d2a-ee839a123589.dsm – Location – 7.0.0.6077
LoaderVerifierTestCerts\351e592a-de64-4c40-a551-e1b8ce080674.dsm – LoaderVerifierTestCerts – 7.0.0.6077
LASS_Lang_0409\b5445a23-1ce0-1be0-6bb0-8e2f838de3ac.dsm – LASS_Lang_0409 – 7.0.0.6077
LASS\771e4aba-7258-4e60-8211-8b10bf1d02ce.dsm – LASS – 7.0.0.6077
LAPS_Lang_0409\ce9c5acd-9498-3ed8-b88e-affd33c40831.dsm – LAPS_Lang_0409 – 7.0.0.6077
LAPS\496167c7-d26b-4501-a313-a774188e77ad.dsm – LAPS – 7.0.0.6077
LANGIDBOOT_Lang_0409\6b8c3822-1d0d-4a8d-9408-fd682f335c40.dsm – LANGIDBOOT_Lang_0409 – 7.0.0.6077
LANGIDBOOT\5886ec51-1811-4a23-9030-5aa0c56d5423.dsm – LANGIDBOOT – 7.0.0.6077
KDCore\a1613f82-8a40-4107-b54d-42f608591eaa.dsm – KDCore – 7.0.0.6077
KBDLAYOUT_Lang_0409\11ac7193-3b86-4e5b-8a01-2767a1d6c091.dsm – KBDLAYOUT_Lang_0409 – 7.0.0.6077
KBDLAYOUT_INPUT_LANG_0409\23b9c36a-2592-480b-b184-ca08175fd1fa.dsm – KBDLAYOUT_INPUT_LANG_0409 – 7.0.0.6077
IULIBS\b0439020-f770-4a57-9195-386c732239f4.dsm – IULIBS – 7.0.0.6077
IME_Lang_0409\f8c6f46f-8506-695a-e0cf-38c4d911266f.dsm – IME_Lang_0409 – 7.0.0.6077
IME\ec61528d-b0fd-4be8-8bd5-32938403d1fb.dsm – IME – 7.0.0.6077
HWComposition\07557c62-08ef-4288-a1c8-ec1e01efd12c.dsm – HWComposition – 7.0.0.6077
HeroAppPkg\002f8bc4-29e5-4c59-a688-7a9b40eaad88.dsm – HeroAppPkg – 7.0.0.6077
GWES_Lang_0409\559bddc8-41bf-8ce9-eff9-104254da4f2f.dsm – GWES_Lang_0409 – 7.0.0.6077
GWES\95e4e653-133e-4529-9387-19b4756d82b4.dsm – GWES – 7.0.0.6077
GPSID\992427c4-1e39-4175-afea-ba57fad835e5.dsm – GPSID – 7.0.0.6077
GDIEX\db526d91-03dc-488f-b154-1f696b055f32.dsm – GDIEX – 7.0.0.6077
FontWingding\e3e69126-ae16-4d50-8bcc-92895d9e3ed8.dsm – FontWingding – 7.0.0.6077
FontSegoe\c006c26d-21f3-4761-afd3-64c769fc4352.dsm – FontSegoe – 7.0.0.6077
FontBrowserR\c1c74c24-f2b6-4b91-82e0-d698088192ca.dsm – FontBrowserR – 7.0.0.6077
FontBrowserI\184ee663-f5b0-4632-9a11-4f8146f8d84a.dsm – FontBrowserI – 7.0.0.6077
FontBrowserBD\eb2ce1ee-df5e-4b1c-8770-0559a14fc23a.dsm – FontBrowserBD – 7.0.0.6077
FmStubPdd\1fbb0a6b-4784-4626-967c-f854eb014585.dsm – FmStubPdd – 7.0.0.6077
FailedStorageUI_Lang_0409\73f75ac3-e36f-0309-fb33-ebce65bce8d0.dsm – FailedStorageUI_Lang_0409 – 7.0.0.6077
FailedStorageUI\20b9ca15-d26b-44d9-8fc6-00866f902901.dsm – FailedStorageUI – 7.0.0.6077
DxG\2645f831-1eac-4373-bee7-675cc2fbdb70.dsm – DxG – 7.0.0.6077
DShowSWCodecsInternal\d9873f60-cc64-404e-9f9f-ab662a344cf4.dsm – DShowSWCodecsInternal – 7.0.0.6077
DMOSSvcs_Lang_0409\c93c20fe-78d5-082c-dad7-0e9e0800082f.dsm – DMOSSvcs_Lang_0409 – 7.0.0.6077
DMOSSvcs\bfcc0130-b02d-4b5a-bf04-089c93073d97.dsm – DMOSSvcs – 7.0.0.6077
DMApps_Lang_0409\213f0232-3819-2574-c8b1-06fb001e0a3e.dsm – DMApps_Lang_0409 – 7.0.0.6077
DMApps\36f324b9-6355-436a-b205-100d53e4b914.dsm – DMApps – 7.0.0.6077
DeviceUpdateAgent_Lang_0409\1dc198ec-d2c3-6510-9ce1-9d9842a0c0f1.dsm – DeviceUpdateAgent_Lang_0409 – 7.0.0.6077
DeviceUpdateAgent\45402052-3d22-4b95-8f59-d9e564fadb0c.dsm – DeviceUpdateAgent – 7.0.0.6077
DeviceFeedback_Lang_0409\fe4a9a84-b560-19be-18b0-96481f875e1e.dsm – DeviceFeedback_Lang_0409 – 7.0.0.6077
DeviceFeedback\24a8d3bf-3337-478b-988a-1bb2bec11ea1.dsm – DeviceFeedback – 7.0.0.6077
Default\148e4e63-3300-47b0-9563-09f1e6ed9b5e.dsm – Default – 7.0.0.6077
DDraw\a65e6992-8061-41fb-a17d-ac99e0dc349f.dsm – DDraw – 7.0.0.6077
DCOM\5a7e04f9-7c54-4df9-8ce2-c0752c088f97.dsm – DCOM – 7.0.0.6077
CRYPTO_Lang_0409\0fd287ce-8add-06ee-b6db-98a90f19567a.dsm – CRYPTO_Lang_0409 – 7.0.0.6077
CRYPTO\f8cab746-7678-46f1-bad5-b1091dde2e48.dsm – CRYPTO – 7.0.0.6077
CoreSecurityModelCSP\b1b1d4b0-96a2-4727-8111-569cce19587a.dsm – CoreSecurityModelCSP – 7.0.0.6077
CoreOSDogfood\7c22dfb5-2cf3-4c4f-9500-70e8103d0a84.dsm – CoreOSDogfood – 7.0.0.6077
CoreOS\7ec2228d-591f-412b-9b64-fae866d8db0f.dsm – CoreOS – 7.0.0.6077
ConnMgrCore\00106172-b307-4ca4-a22f-cd94a80c6f72.dsm – ConnMgrCore – 7.0.0.6077
ConnMgrCfg\d06bc043-88f0-40e1-acae-07edcbd9a788.dsm – ConnMgrCfg – 7.0.0.6077
ConnectivityUX_Lang_0409\e73e36dd-4fde-5369-dc1e-910e8c51a028.dsm – ConnectivityUX_Lang_0409 – 7.0.0.6077
ConnectivityUX_DPI_262\66590462-6f0f-94ef-cce0-58b06f42b131.dsm – ConnectivityUX_DPI_262 – 7.0.0.6077
ConnectivityUX\c4bab662-20c3-48ff-94f2-0cc3cc62a98f.dsm – ConnectivityUX – 7.0.0.6077
CommsPlatform_Lang_0409\bd734d06-e581-c2f7-b8f0-c744d8a910b2.dsm – CommsPlatform_Lang_0409 – 7.0.0.6077
CommsPlatform_DPI_262\40b99ac2-3b77-f3e0-33b9-3a38e86188ad.dsm – CommsPlatform_DPI_262 – 7.0.0.6077
CommsPlatform\59dedb92-ab0e-4775-8f48-3d7c8bb5f8b5.dsm – CommsPlatform – 7.0.0.6077
CommsApps_Lang_0409\a380ff28-ad62-0873-fdf5-3d50f9437cd8.dsm – CommsApps_Lang_0409 – 7.0.0.6077
CommsApps_DPI_262\45c49c4b-0be6-0c6e-1f3a-acda8815245a.dsm – CommsApps_DPI_262 – 7.0.0.6077
CommsAppsXMule\26358e53-4993-4be9-9f55-a9b5a4ffd31a.dsm – CommsAppsXMule – 7.0.0.6077
CommsApps\47124c2d-f925-48e2-a1e5-a5428f8994ab.dsm – CommsApps – 7.0.0.6077
CodeSigningCert\8314b832-8d03-444f-9a2a-1ef6fadcc3b8.dsm – CodeSigningCert – 7.0.0.6077
CertInstaller_Lang_0409\39301fc6-d8be-ca95-653b-2172251bbd56.dsm – CertInstaller_Lang_0409 – 7.0.0.6077
CertInstaller\a73150cc-5910-4045-966c-bd39f923848a.dsm – CertInstaller – 7.0.0.6077
CellSmsProv\65535b11-4342-47aa-8b6e-71dc391ce1d8.dsm – CellSmsProv – 7.0.0.6077
CellDrvWwan\a39455be-b17f-4a98-9441-f42f50de1134.dsm – CellDrvWwan – 7.0.0.6077
CellDrvRilFake\97f2476c-c71e-4fea-8b36-8b248a35033d.dsm – CellDrvRilFake – 7.0.0.6077
Cellcore\cb659c75-eac9-4db7-afd8-055632acf233.dsm – Cellcore – 7.0.0.6077
CECONFIG\c8c87e6b-9535-42a0-bc26-81b6cb323d62.dsm – CECONFIG – 7.0.0.6077
CCFGSVC\1a4c638a-ecb1-48ad-9efa-92d6859ac1bf.dsm – CCFGSVC – 7.0.0.6077
CameraNullPdd\43bce8a7-3ad2-4877-be0b-cefc35dcf5b1.dsm – CameraNullPdd – 7.0.0.6077
BuildInfo\6010fdf9-3bc1-4d33-b12d-6153222b180b.dsm – BuildInfo – 7.0.0.6077
BthCore\bc43fcb9-aa3e-4d2a-81de-8b0fedcafed9.dsm – BthCore – 7.0.0.6077
BthApps\a3993948-8427-4f4d-ae4e-be7d17a8293c.dsm – BthApps – 7.0.0.6077
BROWSING_Lang_0409\c65e5d25-5198-ae09-6b62-e9ebfb7a2309.dsm – BROWSING_Lang_0409 – 7.0.0.6077
BROWSING_DPI_262\47c239c2-8714-34c9-e1e7-1157b83f48a8.dsm – BROWSING_DPI_262 – 7.0.0.6077
BROWSINGCORE_Lang_0409\77026cc9-5204-e7e7-bbf2-bbbf681f0f0a.dsm – BROWSINGCORE_Lang_0409 – 7.0.0.6077
BROWSINGCORE\4262b78f-4503-4436-ac35-dad37bca1427.dsm – BROWSINGCORE – 7.0.0.6077
BROWSING\42dff48a-939a-457b-ada7-3098c46cdb61.dsm – BROWSING – 7.0.0.6077
BootRGU\020d29c8-e454-41d6-a0d2-413a40bf6258.dsm – BootRGU – 7.0.0.6077
BattStub\21e1f928-cc59-4d24-8b4c-bb428aa4fe9e.dsm – BattStub – 7.0.0.6077
BASE_Lang_0409\01913b65-87e8-40e1-9fb3-eb7d128379cc.dsm – BASE_Lang_0409 – 7.0.0.6077
BASE_DPI_262\4ba6306d-0497-4d49-aaef-6ca17ae5c93b.dsm – BASE_DPI_262 – 7.0.0.6077
BaseAudio\1302a4ed-8a1f-4112-9152-d3257415e842.dsm – BaseAudio – 7.0.0.6077
BASEAPPS\7790d42f-9141-429d-aa0f-78fd9c7424f6.dsm – BASEAPPS – 7.0.0.6077
AvTuner\1129cd2b-1b3e-4e96-afa7-b4f85a5f2bf6.dsm – AvTuner – 7.0.0.6077
AvCore_Lang_0409\468b286e-eba6-eaf6-96a4-113c8d01df13.dsm – AvCore_Lang_0409 – 7.0.0.6077
AvCore\0889bcd2-6269-4828-b179-4941c977f84d.dsm – AvCore – 7.0.0.6077
APPPLTSVC\969eb155-55ff-4884-9ecb-241c8a4b6e09.dsm – APPPLTSVC – 7.0.0.6077
APPPLATFORM\e3e0b8b1-fc16-4023-8711-25522737dfb6.dsm – APPPLATFORM – 7.0.0.6077
xde_os\c25a84d1-6da1-4442-b913-776cb45b6b7f.dsm – xde_os – 7.0.0.6077
OEM_Lang_0409\2ecfcf8d-fe71-4bed-9148-1a6882568a9c.dsm – OEM_Lang_0409 – 7.0.0.6077
OEM_DPI_262\8956922c-9e61-4105-9bb8-6b40b041f929.dsm – OEM_DPI_262 – 7.0.0.6077
OEMMISC\e458745b-8ce1-4fa6-9b4d-697d8827128a.dsm – OEMMISC – 7.0.0.6077
OEMDrivers\9ba80faf-05de-47ea-ae62-62de2804587e.dsm – OEMDrivers – 7.0.0.6077
OEMCommonNonEA\0d4e362f-ebf6-4999-95aa-404097b2b919.dsm – OEMCommonNonEA – 7.0.0.6077
MSNKDiagnostics\616527ab-86bc-4454-a4b0-6353caa79aa7.dsm – MSNKDiagnostics – 7.0.0.6077
BaseDrivers_OS\d4da41bf-794e-4513-849f-40e874d83bf6.dsm – BaseDrivers_OS – 7.0.0.6077
16550\5fd28aff-ff0e-44a0-99a2-6b2a132617ef.dsm – 16550 – 7.0.0.6077

Related News from IntoMobile:

Share this: