yashsingh1/xdaforums huggingface dataset:
[Desire General] starscream.ro:
Ok, do you mind share the name of the software you used to to that? thx in advance :)
[Desire General] flashjordan:
I think he's opened camera.....took a screen shot. Downloaded twonky app (or similar) and is streaming the photo to the TV using an Xbox and wifi.
[G1 Q&A, Help & Troubleshooting] alutastisch:
Hey- my phone runs on WLAN.

so. and I have to verify my self via an Username + password.

But i don't know where i can enter that data in my phone?
[HD2 General] eddie564:
So, I just transfered some music into my HD2, and the songs work but like it plays the begging part of the song and then automatically skips to the next song without even finishing the previous song anyone know whats up? Thanks..:mad:
[Windows Mobile Software Development] zzxq:
[GUIDE] libGLES_CM.dll is deprecated for modern versions 1.x of OpenGL/ES

After investigating this matter myself, and reading some user postings on the internet, I think that there is a widely shared misunderstanding concerning valid OGL/ES 1.x dll's on modern PDA's and phones. In my experience libGLES_CM.dll often does not work, but the combination libGLESv1_CM.dll and libEGL.dll is perfectly compatible with many OGL/ES 1.x apps. This could be due to the fact that libGLES_CM.dll is an old and deprecated dll of OGL/ES versions below 1.1.09.

In an obscure note, khronos.org writes about GLES_CM (and GLES_CL): "These names are deprecated for OpenGL ES 1.1 and beyond and should only be used for a library that includes the EGL entry points in order to support legacy applications.". And about GLESv1_CM (and GLESv1_CL): "These alternate names for GL ES libraries that do not contain the EGL entry points were introduced starting at revision 1.1.09 of the OpenGL ES 1.1 specification.".

In real life, this means that programmers should generally link with libGLESv1_CM.lib and libEGL.lib instead of with libGLES_CM.lib for OGL/ES programs to work on modern OGL/ES 1.x WINCE phones. I tested this on the HTC HD2. Existing apps for libGLES_CM.dll should possibly be recompiled that way to work. It is a very small and effortless adaption.

Please don't build ROM's with custom OGL/ES dll's in ROM that are not compatible with the new 1.1 implementation. The situation is already not so clear, and you may make conforming OGL/ES apps unusable; as I have experienced. For a software upgrade this could be acceptable, but don't put them in ROM.
[Windows Mobile Software Development] Chainfire:
While indeed on a number of newer devices the libGLESv1 / libEGL combo is present, on most older devices it is not. The vast majority of OGL/ES (CM) 1.x apps available on WM are statically linked to libGLES_CM. What is often the case on newer devices is that libGLES_CM in fact proxies to libGLESv1_CM / libEGL, and in case of OGL/ES v2 devices the libGLESv1_CM then translates/proxies v1.x code to v2.x code in libGLESv2.

The modern devices like the HD2 implement all of these. Linking to one or the other should not make a difference, only for legacy/compatibility reasons. In fact, static linking to either of them is a bad idea. A correct modern OGL/ES v1.x app would dynamically try to load libGLESv1_CM / libEGL, and if that fails, dynamically load libGLES_CM. Then it would first try requesting a config with all the wanted attributes, and if that fails try requesting a config without any selected attributes at all, and walk through the resulting available configurations to manually pick the best one.

That ^^^ is the only way to make an OGL/ES v1.x app work on virtually all OGL/ES v1.x supporting devices on Windows Mobile. Due to all the various (also stock) ROM 3D driver issues, and implementation differences between manufacturers, statically linking to one of the libs is always a bad idea - unless you don't mind that it doesn't run on older devices.

As for recompiling existing apps, that just isn't going to happen. Though of course a proxy libGLES_CM driver would be easily buildable.

As for building ROMs, of course all these drivers are interlinked. Unless the chef really knows what he's doing, the entire set ( libGLES_CM, libGLESv1_CM, libEGL, optionally libGLESv2, not to mention all the support drivers, which on the Snapdragon platform are quite a large number of them) should always come from the same OEMDrivers source.
[Windows Mobile Software Development] zzxq:
As I wrote, in my experience with a number of OGLES V1.x applications, this just does not work on the HTC HD2. Interestingly, examples from the Khronos SDK are linked to the new libs and they do work. But in the project file, the Vase example, and probably all examples, is linked with the old lib and does not work when compiled that way. Recompiling it with the new libs works again.

Another example is GLUT|ES; it won't work with libGLES_CM.dll, but it does work with libGLESv1_CM.dll and libEGL.dll.

To be safe, programmers may in general as well link to the newer libs if they know that they are available on devices. If even Khronos does not get it right in the SDK, something is probably wrong with libGLES_CM.dll for many newer v1.x apps.

"A correct modern OGL/ES v1.x app would dynamically try to load libGLESv1_CM / libEGL, and if that fails, dynamically load libGLES_CM."

Given what I wrote above, I doubt that failsafe tests can be done that way. I also think that trying to make libs forward compatible that way probably has more disadvantages than advantages. It is arguably bad practice.
[Windows Mobile Software Development] Chainfire:
I've not run into a widely used OGLES v1.x app that did work on older devices (libGLES_CM) but does not work on my HD2 (also libGLES_CM, but libEGL + libGLESv1 -> libGLESv2 internally). However you should keep in mind that very few use the actual libs provided by Khronos, as they are known to cause issues. Most use custom libs (there are some on XDA) that do work properly. Perhaps there is something wrong with your HD2 / ROM specifically?

It does. I've used GLUT|ES apps on WM, but again, probably not built against Khronos libs.

And get two different executables? No thanks. While indeed it is probably true that the existing libGLES_CM implementations are not completely according to spec, they do work if you know how to handle them (they have their quirks). People have been developing cool and working apps for them for several years.

This is a tested and tried method that works across virtually all OGLES 1.x supporting WM devices, and is relatively easy to implement.

Whether it is bad practise or not is completely irrelevant. It is the only practical way to create compatibility, and is actually in use on several devices and ROMs.

Developers of older apps will not recompile their apps because you want them to, as it would make them incompatible with older devices, and it does work on the newer devices as well, if they did their job right. Nor will ROM chefs change the drivers the way you want them to, because the existing way works if you treat it right, and maintains compatibility with older apps - which is what the users want. It's just simply not going to happen. Not to mention that "WM is dead" and nobody is going to invest in making such grand chances this late in the game.

I know you don't believe it, but the current methods do work if you treat them right, and are widely implemented. I get the distinct impression that your "experience" is large based on your own developments and only tested on the HD2.

Believe me, I have "some" experience across over 40 different devices from various manufacturers and various generations over a period of several years. These methods don't just work, they work well across most apps and devices.
[Windows Mobile Software Development] zzxq:
I assume that you are talking about dll's; not import libs. In my experience, these custom dll's break the libGLESv1_CM.dll / libEGL.dll functionality. Did you test that? That's partly why I wrote this article. Again, the old lib is not supposed to be 1.1. compatible, so I would just leave it as it is.

I understand your reasons; many developers seem to suppose that libGLES_CM.dll is the 1.1 dll. But recompiling is no big deal. I do not care if developers don't recompile existing apps; that was not really the point. They have the option.

Now the false assumption is made by many that libGLES_CM.dll is 1.1 compatible; while on some devices, and officially, it just isn't and libGLESv1_CM.dll / libEGL.dll is. It cost me a lot of time to discover that, and others probably too. Other things being equal, I'd personally rather work according to the offical standard than be dependent on custom dll's that are more compatible in some cases.
[8525, TyTN, MDA Vario II, JasJam ROM Development] mu3taz:
hi guys,

I was flashing my JASJAM normally before i format my computer ,, after formating the computer, once I click on the RUU I get an error

take this snapshot

thanx
[8525, TyTN, MDA Vario II, JasJam ROM Development] eryunt:
Have You already applied all the Updates from "Windows Update"?

Perhaps ".NET Compact Framework 3.5" is not installed on Your machine?
[8525, TyTN, MDA Vario II, JasJam ROM Development] MusikMonk:
eryunt is right. This is definitely a .Net Framwork error.
[8525, TyTN, MDA Vario II, JasJam ROM Development] mu3taz:
where can I get it from ?? give me a link plz :o
[8525, TyTN, MDA Vario II, JasJam ROM Development] MusikMonk:
Installing windows updates will download it, but at any rate, here are two places to download it:

Official Microsoft page

Filehippo Mirror (The download button is on the top right)

Both pages offer an online installer, the installer is about 2.8MBs and then what it downloads during installation differs depending on what updates your system has.

And in the Microsoft page, there's also a link to download a full package (offline installer) which is about 230+MBs.
[Desire General] doinbox:
I emailed orange the other day asking why they hadn't released an ota update here's there answer.

Thank you for your email regarding your HTC Desire phone.

I am sorry to learn that you are unaware of our process regarding updates for Orange phones. Please accept my apologies for any inconvenience this has caused.

I would like to advise that Orange customers are not able to obtain updates direct from HTC themselves, this is due to the Orange branding that you have on your phone that allows you to use this on our network.

Please find below a link to our website where you are able to check in the future if an update via Orange has been released.

http://www2.orange.co.uk/servlet/Sa...96364420640&product=Feature&t=Product&tabid=1

I have also supplied below the required steps that you will need to take in order to organise an update to your phone. Be advised to follow the on-screen instructions as it will give you necessary and required information regarding your phone.

"your phone's features" > "download software updates" > "how do I download the latest software update" > "HTC Desire update"

When a new update is made available by a handset manufacturer they will pass a version of this to Orange so that we can run the required tests to confirm that this update they have released will co-exist with the Orange branding that you are required to use on your phone.

It is possible that the new update that is released may not co-exist with the Orange branding and thus we will not be able to release the update for the HTC Desire, if they can not co-exist and we were to release this to your phone, this could effectively be detrimental to your handset and Orange will not process for this reason.

If the update version can not co-exist with the Orange branding then we will wait for HTC to release a new update to which we will restart the testing process accordingly.

Be aware that it is not possible to advise of any estimated timescale for the testing of this update by Orange, furthermore, we can not guarantee that an update will be released at all regarding the HTC Desire as the updates that could be released may never work alongside the Orange branding on the phone.

Because some of this information is speculative and based on situations regarding the testing of updates that may or may not ever be released by HTC and the time it takes to complete the testing of the new updates, please accept my sincere apologies that we can not be more specific regarding your query.

Please be advised that the answers to many common queries can be found in the Frequently Asked Questions section in the Help and Support option on the Home page of our website.

www.orange.co.uk

I trust this information clarifies your query.

Kind regards

Emma

Orange Online Services
[Desire General] JohnSteveDoe:
What is the purpose of this thread? I'm pretty sure this is common knowledge. Same goes for HTC, they won't release the update to 2.2 until they can get Sense to work with it as well as it does on 2.1.
[Desire General] A|ex:
I dont see ORange or any other network providers with branded software getting the 2.2 before or at the same time as those running stock.

Seems pointless starting a new post for this which has been discussed many times before.
[Desire General] doinbox:
I'm not talking about 2.2 I'm talking about the ota update every one has already received 1.21.405 I think it is. Its still not happened on orange.
[Desire General] JohnSteveDoe:
2.2, 1.21, 1.01, 1.53, it's all the same. This is common knowledge. I still don't get the point of this thread.
[Desire General] doinbox:
I only posted it for people who are on orange and, like myself keep asking for the update. I haven't seen an answer from orange anywhere on here so I thought I'd. Email them myself and post the answer here. Just because you knows how it works doesn't meen everyone else does. I'm sure orange customers would like an answer.

What's your problem.
[Desire General] doinbox:
Sorry! Double posted for some reason.
[Desire General] JohnSteveDoe:
I don't have a problem, I'm just not so sure others didn't know that's how it works.
[Desire General] chandalf:
Orange and updates

Well, I think it's a valid thread and I do know the 'system'. I agree with the OP that a specific answer from Orange has not been posted. He could have added it to one of the [many] other threads but how many of us - who genuinely want to know the situation - would ever see it? This way we get to read the 'official' line. So, what's your problem?

On a more relevant note, I don't read this as being a hopeful sign that we Orange users will ever see the .21 update. And considering it seems to fix some of the annoying bugs with the Desire that is a pain. I don't want to root my device as it would put the warranty in question and I have already had to have it replaced once. So I'm stuck with a 'flawed' device that the supplier doesn't want to fix. Maybe I'll go for an iPhone?

And another thing. The link the Orange Rep gave in her email takes you to a page that doesn't even have the Desire listed on it!
[Desire General] oursoul:
It's definitely a valid thread, that's a very interesting reply from Orange right there.

The emphasis on Branding is shocking. What a load of ****.

I think Orange users will be getting Froyo sometime next year.
[Desire General] mancuk29:
Basically what orange is saying they won't release out that will make your phone run properly orange crap on top if software always screws the phone up or makes it run slower

I always steer clear of orange branded phones they are the worst company out there for network crap
[Desire General] stats101:
At this rate i'm going to end up rooting my phone. No more slow updates. No more Orange crapware.
[Desire General] atomfix:
And this is why I debranded my phone to use froyo. And will be useing HTC's hopefully desire froyo rom once its released :D
[Desire General] oursoul:
You dont actually need to Root, just do a debrand.. its a little easier and a lot more failsafe. You'll need to get your phone unlocked tho to run the latest firmware which is definitely worth it.
[Desire General] stats101:
does debranding it void it's warranty? will i lose my data?
[Desire General] oursoul:
Its a moot point, certainly you will lost your data as you'll be flashing a fresh OS.

As for the warranty, I guess officially yes it does. HOWEVER.

If you were to send the phone off for a hardware problem then it is my opinion that it would be still covered under Orange & HTC's seperate warrantys.

If its a software problem, then a simple re-flash will fix it.

That is my philosophy anyway.

I sent 4 debranded c905's back to orange with no problems last year and more recently had my c905's earpiece mended by Sony in about a week which had been debranded too.

I didn't hesitate to debrand my Desire, did it about 3 hours after unboxing it before I started to set up my homescreens.

So its up to you, you know the risks but if there's a fault at the worst Orange will send it back to you unmended, but then you can send it to HTC. But put yourselves in the mind of the engineers ;) They'll fix it if they can imo.
[Desire General] dgattenb:
its teh reason why I got rid of my Touch HD phone, as Orange would not update it ... If you go to the HTC sight they have Orange UK updates , but none for Froyo :(
[Android Software/Hacking General [Developers Only]] ThugEsquire:
Please forgive the late-night rant...

I hate that customizations like Sense UI are manufacturer-exclusive, and I hate that you can't uninstall them completely without rooting and flashing a new ROM. I hate that HTC's widgets are locked to the Sense UI launcher so that you can't use them with alternative launchers like LauncherPro--or other hardware without Sense UI like the Droid X. I hate that I can't choose the Droid X's not-quite-ninjablur red-and-white-on-black UI skin and combine it with HTC's widgets and Google's vanilla settings and app icons. I hate that HTC changed the app and settings icons in the first place.

Ultimately, I hate that manufacturers are using artificial limitations in software to sell hardware instead of providing better hardware. It's a strategy straight out of Apple's playbook. Why can't HTC Sense widgets work on other launchers? Would it really be that impossible for HTC to make the widgets downloadable to any Android device? Free for HTC owners, $1.99 for everyone else! You'd make money, and it'd be so much easier for people to upgrade to the latest version of the OS!

I also hate these artificial carrier-exclusive handset deals that keep phones like the EVO locked to Sprint and the Incredible locked to Verizon and the Nexus One locked to either AT&T or T-Mobile and the iPhone 4 relegated to AT&T. Why can't these phones come unlocked and with all the necessary radio equipment to work on all of the networks? Then the consumer could pick the hardware he wants, then the network, and have a totally customized experience. Have the phones automatically disable the extra radio bands if they're not using them--it wouldn't be that hard to conserve battery!

And why isn't there a version of the Nexus One car dock for the Incredible? Or the Droid X? You know, a doc that has integrated charging and the like. All you have are these ghetto mounts that require you to string USB charging cables all over the place.

And finally, I hate that no Android hardware manufacturer is making a phone built like iPhone 4. **** Apple's iOS--I want nothing to do with that. But, aside from the antenna, the hardware packed into an iPhone 4 is impressive, like that Retina display in particular. There's no goddamned good reason I shouldn't be able to buy a version of that hardware that runs Android and works on Verizon.

In fact, I hate that the screens in smartphones aren't modular. It'd be so much better if I could switch out my Incredible's annoying PenTile matrix screen for a super-dense S-IPS Retina display. Why can't I do this?

And why aren't phones rooted out of the box? Are casual users even going to notice?

Sorry, I'm just really pissed off about all this bull****. I still love Android.
[Android Software/Hacking General [Developers Only]] CosmicBlue2000:
I'm with you.

I'd like to have a SenseUI-Android and a multi-touch display for my HTC TouchPro2 (Tilt2)
[Android Software/Hacking General [Developers Only]] ThugEsquire:
Thanks. I'd love to be able to build my own phone to run Android. Internally it'd be like a Droid X but smaller with a Retina display with the vanilla Android icons, Motorola's hot red-on-black theme, and Sense UI widgets.
[Android Software/Hacking General [Developers Only]] Szadzik:
The Retina display is not better than say a Super AMOLED.

the only thing is the high resolution, but Android devices have high resolution too.

Apart from that I do not see anything in the hardware of the 4th that is appealing.
[Android Software/Hacking General [Developers Only]] OneTwoPi:
I 2nd (3rd... or... support) this rant.

Regarding the software part, stupid htc sense dependencies and such. Is it not possible for devs/community to replicate the functionality of most htc apps? From what i've seen there are some very talented "chefs" on xda and the interwebs.

My ideal (hero) rom would be a stable, fast, no-crap, release with the phone functionality/longevity in focus (and an alarm clock that does not forget to actually use sound/vibration. A flashing screen just doesn't cut it a 06 in the morning).
[Android Software/Hacking General [Developers Only]] Vdek:
Try designing a phone sometime, all your questions will be answered.

Well, it might be a little hard to just start designing a phone, but you could learn about the processes and technology involved in both the design and manufacture of such devices.
[Android Software/Hacking General [Developers Only]] ThugEsquire:
The Retina display is special because of its high resolution and high pixel density--and the pixel density is the key part. Is there any other Android phone with a resolution as high, or a screen with as great a pixel density?
[Android Software/Hacking General [Developers Only]] ThugEsquire:
Care to back this up?
[Windows Mobile] miniterror:
helle fellow chefs

i have the strangest thing

a few months ago my mobo and proc of my dualcore got burned and my backup hdd failed:(

i lost my kitchen and private suff and my computer:-o

a little later i have bought new components to build up a new computer

since i have build up this computer and rebuilded the kitchen i have the strangest thing

if i make a rom and flash it 60% is corrupted:S

one rom flashes but misses files in the rom

others stay stuck at the smart mobility screen and others work 100% fine

all three roms are made with the except same packages and exact same regsettings so how it is possible the exact same settings can give me three different roms:-o

i replaced my hardware for a asrock a780lm-s

a amdphenom x4 925(8mb chache in total)

2gig crosair memory from the xms2 series

and a western digital green calviere(or something like that) 500gb sata hdd

could it be that the ram cant keep up with the rest the proc is processing and therefore is leaving files out the nbh file? as i have a ram monitor and in idle it stays arround 500mb in use and when i start cooking it goes up to 1.5 gig in use:-o

hope someone can help me out as i am getting crazy of one image being corrupt and the next one with the exact same packages being totally good:S
[Windows Mobile] tomcug:
I bet that your RAM is producing errors, run an app called MemTest 86+ and test you memories.
[Windows Mobile] miniterror:
will test it but i think it cant be corrupt as i only have one 2 gig bank and it isnt even 2 months old:S
[Windows Mobile] WoZZeR999:
I had a Q6600 (quad core) OC'd with 4gigs of ram, and EVK never had a problem, so I don't think it's an issue with extra cores.
[Windows Mobile] tomcug:
Yeah, additional cores are never an issue, I have Phenom II X4 940 and I already cooked many ROM's on this PC, no issues at all :).
[Windows Mobile] icke:
Being observe this issue nearly every day. All things I delete by myself in explorer or going to send to me via inet get written into ram...also in EVK. Whole procedure while cooking rom with EVK...everything is written into ram.:mad:
[Windows Mobile] WoZZeR999:
A lot of it is IMGFS. Using LZX compression requires a large amount of memory (over a gig sometimes, if it's available)