yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro General] chris_khho:
The problem is that VGA skin is not for true VGA skin I think.....

See the attached picture.

Thanks for your reply...

Cheers,
[JASJAR, XDA Exec, MDA Pro General] buzz_lightyear:
thanx Chris,

now i know what you mean...

buzz
[JASJAR, XDA Exec, MDA Pro General] seal:
I had a play around with the files from the dialer and took them into Corel Photo Paint and made them 4 times the size and it worked the button was 4 times the size, but it is under the top layer, where is the file for the top layer of the phone, I can't work it out, I don't know enough. Please someone we need a large phone skin.

Cheers
[JASJAR, XDA Exec, MDA Pro General] vijay555:
Guys, I've fixed the dialler.

eg

Before

After:

Post and tell me how it goes. It's beta and for the English version only!

VJBigPhone

V
[JASJAR, XDA Exec, MDA Pro General] chris_khho:
But the video call button?

Hi V,

But the video call button is lost?

Thanks a lot and I'm looking forward to your modified one.

Cheers,
[JASJAR, XDA Exec, MDA Pro General] vijay555:
:) I didn't know there was a video call button. I never installed anything from the ext rom and I guess it was from there.

I'm working on it right now.

V
[JASJAR, XDA Exec, MDA Pro General] szandokan:
Video Call button is different

Fantastic work V!

Just an observation that may help improve this further...

I noticed that the Video Call button, both before and after the resize fix, renders differently to all the other buttons. It scales well to VGA. That is, the corners are not cut off, before the resize, and after the resize, the text gets resized perfectly as well as positioned well. What is different about this button? Can this be used as a clue to resize the other buttons the same way too?
[JASJAR, XDA Exec, MDA Pro General] steverae:
Been playing around with the reg settings described by my good friend Buzz_Lightyear...

Defo works better than ozvga... However, the .96 is a bit too small for narmal use SO

tryed buzz's choice of 128 but this looks a bit aquashed, so has anyone tried any dfferent values to get a slightly larger screen size that looks in proportion and with not hard on the old eyes....

.96 - true vga (640x480)

.128 - dunno what res this is, a bit better but not in proportion

.196 - qvga (320x240)

will have to get some calculators out to work out a stepping progress to exxperiment.... How VJ's dialpad will work with different resolutions....
[JASJAR, XDA Exec, MDA Pro General] vijay555:
VJBigPhone should work at any DPI I hope.

It's not hardcoded, it repositions stuff according to the native DPI. However, that's the theory! Give it a go and tell us how it goes.

Note that the current version, 0.5, uses a slightly different and more generic technique to fix the dialler (so that I can later make an international version). However, this may cause it's own foobar, so hold on to the v0.4 cab just in case! Also, by accident, 0.5 doesn't work with the smart dialler. I'll hopefully fix that tonight, but disable it for your test.

V
[JASJAR, XDA Exec, MDA Pro General] magpie2000k:
BUZZ

can I just try any numbers ie 124 142 181 etc to see which settings work best for my display..

are there any issues ie do the numbers have to be specified multiples

let me know cheers
[JASJAR, XDA Exec, MDA Pro General] buzz_lightyear:
i'd go for 144 dpi.

:o)

buzz
[JASJAR, XDA Exec, MDA Pro General] magpie2000k:
cheers for that buzz

I have run reg edit and changed all to 144 and renamed all files to 144 as the thread sais..

However all I get is to a screen where when booting up i have the two soft keys one reads select and the other reads exit..

strange but clicking either doe nothing..

anyone any ideas or am i into another hard reset.

pLus reason for failure would be good.

I find 128 just a bit too small so thought this might be about spot on for mehave also tried 142 and it does the same thing..

any ideas anyone plus Buzz

cheers in advance
[JASJAR, XDA Exec, MDA Pro General] BrettS:
I would *love* to get 144 to work, but the reason I haven't spent too much time trying is that Pocket IE still does it's crazy pixel doubling with 144. I've played around with it a bit, but it seems like the only way to keep IE from pixel doubling is to actually use 192. Since 'fixing' IE is 90% of the reason I want to use VGA mode.

::sigh:: Otherwise I think that 144 is the perfect compromise.

Brett
[JASJAR, XDA Exec, MDA Pro General] Pyrofer:
Why is it that MS were so S**T with vga?

Evey app doubles to make it only 320x240 Except the one we want!

Media player leaves 320x240 vids in a little box in the middle of the screen.

So, IE, we want 640x480 and MS make it 320x240 only

WMP we want 320x240 (with option of vga, no doubt) and it only works in 640x480 when playing fullscreen!

its crazy.

What was up with MS thinking its ok to release the OS like this?

If they make PIE and Terminal Services both work in actual VGA mode there is no need for the VGA hack at all.

Come on MS! you know what we all want!
[JASJAR, XDA Exec, MDA Pro General] vijay555:
Hey, you want to try speaking to the phone dialler as well. That's expressly written NOT to take account of higher DPIs. In this day and age that's crazy.

V
[JASJAR, XDA Exec, MDA Pro General] BrettS:
True, but you already fixed that for us, so we don't have to worry about it anymore ;)

Brett
[JASJAR, XDA Exec, MDA Pro General] vijay555:
:wink:

Anyone tried VJBigPhone at any johnny foreigner DPIs?

V
[JASJAR, XDA Exec, MDA Pro General] Carnivor:
A theory I have is that the hardware vendors push M$ to provide a working o/s so that they are able to sell stock and recuperate invested funds, even if this means the consumer has to suffer.
[JASJAR, XDA Exec, MDA Pro General] BrettS:
I just revisited the 'non-standard' DPI issue and I've been spending a bit more time playing around. I discovered that Pocket IE *does* turn off pixel doubling at anything under 144DPI, so obviously that's what I've been spending the most time playing around with.

Since I do like 144DPI so much I first tried 142DPI. I renamed the 96 DPI files to *.142.* and copied them into the Windows directory and reset my phone. That does appear to work and things are reasonably large and readable, but some things didn't appear normal either...

For example, all of the Calculator buttons were a very odd green color. I have the Calendar set to show the half hours, and it just showed a strange black mark instead of 30 for each half hour. Radio buttons and Check boxes didn't appear. You could still select an option by clicking on the text, but you couldn't see what was currently set. In addition, the icons like the flag by the start menu and the OK and X in the top right were rather pixelated. Also, the SIP Keyboard did not appear correctly, nor did it work correctly... you could tap it and it would produce letters, but the letters that appeared weren't the ones you clicked on.

I dropped down slightly to 140dpi and experienced essentially the same problems, however, while the icons still appeared pixelated they seemed more pleasing and didn't bother me so much.

I also tried 128dpi and that fixed the issue with the radio buttons and check boxes, however, the icons were back to their less pleasing pixelated state.

Finally, I tried 136dpi and it was more like 140dpi... more pleasing icons, but all the other problems still existed.

I'm still playing around a bit, but it looks like 128dpi might be our best bet. It's a bit smaller than I'd prefer, but still much better than 96DPI. Most importantly, however, the radio buttons and check boxes appear normally... I tried to use 140dpi briefly, but there are a lot more radio buttons and check boxes than you would expect and it made actually using the device a bit difficult.

I think the problem with the SIP will be correctable. The problem, as near as I can tell, is that it's not displaying the correct bitmap. The keyboard that's being displayed is much smaller than the spot where the keyboard should go. When you tap on the screen it looks like it's picking up the letter that should be in the spot where you tap. I'm assuming (hoping) that there must be some way to edit and enlarge the keyboard bitmap to match the 128dpi setting.

I'm also hoping that it may be possible to manually edit the DLL files and change the icons so that they will display normally at 128dpi. I think it's just trying to stretch or shrink the icons that are there and it's not doing a very good job of it.

Unfortunately I think both of those tasks are beyond my ability, so hopefully there is someone else out there who can do this.

Also, Vijay, I'm afraid that VJBigPhone didn't appear to work at all at any of the DPI's I tried. VJBigPhone started, but it didn't change the dialer screen at all.

Brett
[JASJAR, XDA Exec, MDA Pro General] jpa:
hy,

Could someone provide me those 3signed dll :

msimfr.192.dll , pptres.192.dll and trares040c.192.dll

I need it as I have a french rom...

Many thanks
[JASJAR, XDA Exec, MDA Pro General] steverae:
Ok, further from bretts findings above, i thought i'd check what files are being used in the .192 dpi setting and found that they are only 19 files with which we skin the higher resolutions but 25 at .192dpi

Where did the original 19 files come from.... why are they 6 files missing, could these 6 files be responsible for the missing icons, radio buttons etc.....

just a thought, i'll leave it up the clever people like Buzz and the gang to suss this out.
[JASJAR, XDA Exec, MDA Pro General] Carnivor:
the stuff that was missed out i think if i remember correctly, the intro rubbish about alignment and cut+paste an appointment tutorial. no real point if that is right.

ive been side tracked lately making a xp operating system on a 512mb compact flash card, i got xp down to 340mb complete install now, with my required apps installed, yes it boots fast, no need for a hdd now purrfect for the car :)

If anyone wants to investigate further, freely check here for info

http://www.windowsdevcenter.com/pub/a/windows/excerpt/CarPCHacks_Chap1/index.html?page=3

and http://www.linitx.com for the kit
[JASJAR, XDA Exec, MDA Pro General] buzz_lightyear:
cool... ;o)))

now make it please for ARM processor... ;o)))

buzz
[JASJAR, XDA Exec, MDA Pro General] jpa:
As no one seems to have the 3 signed french dll, could you please tell me how i can solve my issue : i don't see the keyboard (with 96, or 128 dpi) ....

thanks
[JASJAR, XDA Exec, MDA Pro General] dreamtheater39:
Hi,

could someone clarify whats the best way to move into VGA mode??? There are so many posts out here, with two different ways to do it (using ozVGA and just a reg hack method).....question -

1. Which method is the best way to get into vga mode

2. Advantages and disadvantages of each method

3. And how to do it ;)

I've seen posts where 192.* files need to be renamed to some 96.* and all of it....where do i find these files? Why should i rename it to 96.*? If i have my reg setting at 144, do i need to rename it to 144.*?? Again where are these files??? :D

Thanks again!

San
[JASJAR, XDA Exec, MDA Pro General] Mikee4fun:
Great Job! Now lets hope for the phone app to work right

Mike
[JASJAR, XDA Exec, MDA Pro General] jpa:
hi,

is there someone who can explain me how i can change the bitmaps ressources on msim.96.dll (i have an azerty keyboard and the actual bitmaps are for a querty keyboard) ? I have tried with pe ressources but it doesn't run : the dll is not loaded..

thanks
[JASJAR, XDA Exec, MDA Pro General] universaldoc:
If it isn't too much to ask, can someone perhaps post a screenshot of their "today" screen and also with an sms being written?

Appreciate it.
[JASJAR, XDA Exec, MDA Pro General] buzz_lightyear:
@176 dpi

buzz
[JASJAR, XDA Exec, MDA Pro General] universaldoc:
Hi Buzz,

Thanks for the screenshots. I am sorry, i wasn't clear enough. I wanted screenshots posted in VGA mode using the VGA files posted here. I find the fonts to be extremely tiny and very difficult to read. I was wondering if its the same with you guys or are there some changes that i am yet to make.

Cheers.
[JASJAR, XDA Exec, MDA Pro General] vijay555:
universaldoc: I think I've posted VGA screenshots on page 2 or so.

V
[JASJAR, XDA Exec, MDA Pro General] SiliconS:
Solution for the pixel-doubling problem?

Stumbled across this page while browsing for WM5 VGA topics on the Interweb:

http://www.aximsite.com/boards/showthread.php?t=103786&page=1&pp=20

Seems too good to be true. The post was made at the beginning of November. Has nobody here seen this info, or doesn't it apply to our Universals? I guess it doesn't apply cos surely someone would have posted in these forums if it worked for people who just wanted things like Adobe or PIE in true VGA mode.

I haven't tried this (and I don't plan to) because I'm running very happily in full VGA mode. This hack might be useful for people who want QVGA-sized fonts but without pixel-doubling in PIE.
[JASJAR, XDA Exec, MDA Pro General] chris_khho:
Wonderful. Will give it a try later...
[JASJAR, XDA Exec, MDA Pro General] BrettS:
Re: Solution for the pixel-doubling problem?

This works for some apps, but not for PIE.

Brett
[JASJAR, XDA Exec, MDA Pro General] SiliconS:
Re: Solution for the pixel-doubling problem?

Damn. Once again Satan drops a banana skin on the footpath of opportunity and Old Man Possibility slips and breaks his neck.
[JASJAR, XDA Exec, MDA Pro General] jpa:
here's the hack for our qtek 9000 FR with azerty keyboard : :D
[JASJAR, XDA Exec, MDA Pro General] belfast-biker:
Damn, gorgeous....
[JASJAR, XDA Exec, MDA Pro General] lbendlin:
Re: Video Call button is different

The video call button gets added when you execute the Enable_VT_RTPlugin_0727_2_signed.CAB from the Extended ROM. The setup XML states something like

<characteristic type="HKLM\Security\Phone\Skin" translation="filesystem" >
<parm name="ext" datatype="string" value="phcanhtc.dll" translation="filesystem" />
<parm name="Enabled" datatype="integer" value="1" />
</characteristic>

not sure if that helps
[JASJAR, XDA Exec, MDA Pro General] vijay555:
Taken appropriately into account by VJBigPhone already I hope!

V
[JASJAR, XDA Exec, MDA Pro General] youmeus:
missing icons in VGA mode!

hello all,

I would like to start by saying great work on this VGA hack. I however am getting problems running it on my XDA EXEC, some icons are missing in the today screen and other icons are mixed up; not being referenced correctly. Please can anyone give me some hints as to fixing this problem.

Thanks :D

P.S. I have read the thread several times and tried all suggested tips about missing icons but they did not work on my device.[/b]
[Nexus 5 Q&A, Help & Troubleshooting] BoscoTM:
With all the rumors getting thrown around, and the newest saying Oct. 15th, does Google announcing the Nexus 5 mean its going to be released that day? By release, I mean available to buy from a carrier, mine's being T-Mobile. I upgraded to a LG G2 two days ago and I'm hoping the Nexus 5 gets released within 12 days so I can go return the G2 and get the N5 instead.
[Nexus 5 Q&A, Help & Troubleshooting] Gorjira:
Not necessarily. Most of the time smartphones are "announced" first and then they are "released" at a later date. Rumors have been pointing to an end of this month release. If anything, that G2 is a great phone in of itself. Just throw Nova Launcher on it and you got yourself a make-shift Nexus 5. :)
[Nexus 5 Q&A, Help & Troubleshooting] SHAWDAH:
Google is following Apple's "release at announcement", so when its announced you'll be able to order it.
[Nexus 5 Q&A, Help & Troubleshooting] abalosmusic:
I got my tmo note 3 on oct 2nd... im hopeing... i mean wishing they release the n5 before nov 1 as it is within my 30 days return policy... i love how when i got the note 3 it was 0 down :)

Except taxes :sly: stupid thing is i bought a case and screen protector for it already :banghead: and if i do return my note 3 i will be charged a return stocking fee.. in the end i lose money.. all for this damn google phone... buying/selling/trading/collecting phones is an expensive hobby. I hope i can just get the n5 pay it off and not upgrade for awhile... i upgrade fkin every 6-8 months. S2, s3, note 2, s4, and npw note 3.. fml
[Nexus 5 Q&A, Help & Troubleshooting] Alien987:
http://en.wikipedia.org/wiki/Nexus_4#History
[Nexus 5 Q&A, Help & Troubleshooting] AndreaCristiano:
I just want them to get to it already this is just dragging on. I mean honestly I'm tired of bloatware and tired of the rooting process. I just want a phone that works with great updates and great specs. This nexus 5 will fit the bill so just drop it already goggle
[Windows RT General] hisoft:
It readable for backer only. Did they have any rule about telling the other people?

update: now audio come to VLC Metro (http://xdaforums.com/showpost.php?p=47650624&postcount=19). After the video part pass validation. (http://xdaforums.com/showpost.php?p=46405311&postcount=2)
[Windows RT General] cx1:
We've been quite busy lately (VLC 2.1.0 release), but we have quite good news: we've finally been able to pass the validation for the Application, as you can see here:

As you might see, we did that a couple of weeks ago, but we wanted to fix an important issue before sharing it with you. We were not able to do as fast as we wanted, so we do the update anyway :)

We were able to integrate a new networking layer, without violating the Store guidelines, work-around the threading limitations (with a hack, though) and rewrite some more code.

So far, the main issue is that to pass the validation, we had to cut the audio completely.

Who needs audio to play a movie anyway? :D

We have a theoretical solution, but it still fails for unknown reasons.

We are working on fixing this audio issue and we will share a build to you backers, as soon as it is done.

Thanks for the support.

VLC team

PS: we've received some goodies back, because of wrong addresses, so if you have not received yours, mail us!
[Windows RT General] BIade:
Hello my friends :)

I contacted the vlc-devs via E-Mail and they allowed me to post their answer :D

My Mail:

Their answer:

I was sooo happy that they answered me, and I wanted to share it with you :)

Please delete my post if this is not the right place to post...
[Windows RT General] GoodDayToDie:
Thanks for sharing, though there's actually nothing new in there... it's been known for months now (ever since the kickstarter was funded) that RT and WP8 ports were planned, following the "Metro" (WinRT) build.

A much more interesting question, although one much less likely to get an affirmative answer, would be "any chance you could provide, or at least enable us to buid for ourselves, a version of VLC which is compiled for WoA (Windows RT) desktop?". Jailbreak obviously required, but screw "Metro" anyhow...
[Windows RT General] hisoft:
cx1, Blade. Thank you for sharing.
[Windows RT General] Myriachan:
Hmm. I wonder what currently stops VLC from compiling for jailbroken Windows RT systems right now.
[Windows RT General] BIade:
Just send a new email with that request :)
[Windows RT General] GoodDayToDie:
Cool, thanks. Alternatively, they could share the .APPX for any working versions they have, even if they use prohibited APIs and therefore aren't allowed in the store. It's not like the rest of us give a <REDACTED> for Microsoft's restrictions...
[Windows RT General] alucard_xs:
damn it, still no release date for my surface RT ...
[Windows RT General] domboy:
That would be pretty awesome if they would release such a build!
[Windows RT General] BIade:
My mail:

Their answer:

As far as I know, we got a tutorial for compiling with targeting ARM. Should I send them our tutorial? If yes, then plz give me the proper URL for the post, which could help them the most.

thanks mates :)

Blade
[Windows RT General] kitor:
VLC is using MinGW, and MinGW has no support for RT. Only VisualStudio, and this will not work.
[Windows RT General] BIade:
Awww sad to hear, but thank you soo much for your answer. VLC for RT would have been tooo awesome :D

thats why i got in contact with the vlc-devs...

And btw thank you so much for your Notepad++ port ;)
[Windows RT General] SixSixSevenSeven:
Surprised you havent given in and paid for one of the other apps by now :P
[Windows RT General] Globalrebel:
I'm surprised that this is not going to happen. I was always under the assumption that the VLC player for the kickstarter was for RT? How is this not going to happen now?
[Windows RT General] SixSixSevenSeven:
Follow the thread. They didnt say it wasnt going to happen.

These things take time.
[Windows RT General] hisoft:
Thank to ffmpeg port. :D But now I upgrade to Windows RT 8.1. I don't sure what will done before. RT 8.1 hacked, WinRT VLC or I paid for some app. :p
[Windows RT General] SixSixSevenSeven:
I am looking forward to VLC launching for WinRT and ARM too. Not top of my list though seeming as I am using a normal laptop with VLC on desktop and a regular desktop PC too.
[Windows RT General] hisoft:
Latest update: Now VLC Metro have audio

https://twitter.com/videolan/status/402479234695712768
[Windows RT General] cx1:
Saw this a couple days ago. They did not add any updates to the Kickstarter page.
[Samsung Epic 4G Touch] mands386:
It's there any way to get mms working on the new dirty unicorn 4.3 for virgin mobile??
[Samsung Epic 4G Touch] Gil81:
You will need to change you're mmsc URL to VM ... There are a bunch of guides for changing APN settings..
[Samsung Epic 4G Touch] mands386:
Can you give me a link I can't seem to find one thanks a lot man
[Samsung Epic 4G Touch] Gil81:
Second post in this thread.. http://xdaforums.com/showthread.php?t=1794956

I've never did it this way...I use dialer codes and my msl to change apns..only touchwiz based ROMs...on cm/aosp/aokp based ROMs I change them with the voice dialer...say apns...input new APN or change current one...

That post has the working VM APN setting in it also...unless its been updated and I missed it..
[Samsung Epic 4G Touch] mands386:
Thanks again bro I greatly appreciate it
[Samsung Epic 4G Touch] Gil81:
NP and if you hit a speed bump...just hit me up...
[Samsung Epic 4G Touch] queendd1980@gmail.com:
Same Problem

I have the E4GT on Virgin Mobile also. I love the Dirty Unicorn 4.3 Rom but I have the same problem I cant get MMS to work. Here is what I am doing. I am using the FJ12 Modem.

1. Wipe data and factory reset, cache, and dalvik cache.

2. Flash the Dirty Unicorn Rom.

3. Reboot into the rom.

4. Reboot into Recovery.

5. Flash GAPPs.

These are the fixes I have tried.

I open APNs and add the Virgin Mobile APNs. This is what I am using:

Name: Virgin Mobile

APN: Sprint

Proxy: <not Set>

Port:<not Set>

User Name: Sprint

Password: *

Server: <not Set>

MMSC:h t t p : / / m m s c . v m o b l . c o m : 8 0 8 0 / m m s ? (without the spaces)

MMS Proxy: 205.239.233.136

MMS Port: 81

MCC: 310

MNC: 00

APN Type: default,supl,mms

I then go to menu and hit save. The original Sprint APNs are there but the APNs I entered are not there.

I have also tried flashing the VMD710MMS+VisualVoicemailFix

However I am still unable to get MMS to work.

Edit:

I tried the Go SMS Fix also - that did not work.

I also noticed the my roaming settings wont stick. I am in an area where I must roam to get 3G data
[Samsung Epic 4G Touch] ChrisMills83:
I am having the same problem, although I opted for the GO SMS fix since I already use it. I will try the first set of instructions when I have time later and report back.

Edit:

Tried both ways and no dice.

Additionally, I have tried the MMS/Visual Voicemail Fix and it only causes a system process on my phone to stop working.

Any ideas?
[Samsung Epic 4G Touch] mands386:
I'm going to be trying this out a little later to see if it works just wanted to share it to see if it helps anyone