What is the chance of using this thread to start a glossery of tearms so that new people like myself who get the plot but just want to learn a little more and new people tha learn stuff on here can share it.. for instance
how regedit is used... what is a dword ECT,ECT
in other words can we start a learning base for PLANKS just like ME
Anyone wanna start the ball rollin??
ROM - Read Only Memory
RAM - Random Access Memory
Flash - to change the operating system (like installing Windows on a normal PC)
USPL - Unlock phone so it is not locked to a country
Unlock - remove Network lock
PPC - Pocket Personal Computer
USB - Universal Serial Bus
WM - Windows Mobile
just some simple ones
Well its a start i suppose lol Nice one how about
a definition of...
Cooked Rom
Baked Rom
Extended Rom
Page Pool
Vanilla
And Regedit basics...
Anyone.........?
for regedit it's easy, just search on google. Other people already explained it, no point in doing it again. For example, read these:
http://en.wikipedia.org/wiki/Regedit
http://www.akadia.com/services/windows_registry_tutorial.html
and a DWORD means an integer (that's a natural number, no fractions or decimals) between 0 and 4,294,967,296.
EDIT:
Also, wikipedia has this to say about Vanilla:
Vanilla is also commonly used to mean "plain" or "conventional," derived from the use of vanilla extract as the most popular flavoring for ice cream.
Click to expand...
Click to collapse
So, in this context, it would mean the original software that came with the phone, no changes. Or the original WM6, for example.
Hi all, I have been following HTCclassaction etc and have done extensive googling to find out the state of an open GL driver for our Vogue (MSM 7500).
The closest hope I had is NFSFAN's roms and post's at PPCHaven.
NFSFAN, you stated you are working on this, any updates so far? Also when (not if, I greatly respect your amount of talent) you finally come up with a workable driver will you release it to the comunity as a whole as well as in your ROMS?
Thanks for the update, and thank you very much for all your work to date. It is very much appreciated.
I found this document on BREW forums (Qualacom). It is about software solutions for msm7500 chipsets regarding openGL es.
It's a little over my head but maybe someone on here can use it.
I can't upload it because it is over the forums limits. I've never used rapidshare or megaupload before but i'll try. Here is some previews of the header so you know what it's about:
3D Performance
Optimization
Angus Dorbie
Staff Engineer (3D)- Gaming Technologies Group
MSM7500 – Major Carriers FFAs NOW
MSM7500 Graphics Pipeline Overview
• Licenced integrated OpenGL® ES solution
• Hardware accelerated vertex and pixel processing
• Integrated in MSM processor
• OpenGL ES 1.0 Common profile + all major 1.1 features
• Extension: OES_vertex_buffer_object,
EGL_QUALCOMM_color_buffer, ATI_TC Compression, Texture
Combiners, Texture Crossbar, Alternative Texture
Coordinate Formats, Matrix Palette, DrawTexture, Point
Sprites
• Java JSR-184, D3D, SKT’s GIGA, HI’s V4, Superscape’s
Swerve APIs support implemented on top of OpenGL ES
pipeline
etc etc,
shows some neat graphics of what can be attained, detailed analysis of the chipset etc.
Well that was easy, here it is:
http://http://rapidshare.com/files/182666655/Prog-401_Dorbie_v05.pdf.html
Couldnt open the page. Can you try again?
Ooops, first time radipshare user mistake.
edited the link, it should work now I just tested it myself.
I reached the d/l limit so I will try in about 15 minutes. I am not a developer, but I am really interested in getting 3d workiong on our phones and am feeling inclined to learn alot and then perhpas get involved via htcclassaction.org. I'm more of an activitst than anything else! But I do really appreciate everything that people do on here and am more than happy to be a guinnea pig with my phone.
No, fully accelerated Hardware Direct3D is not possible on the Vogue. The DDI doesn't have the required calls it takes for Hardware Accelerated D3D. The closest I ever got was porting standalone OpenGL and a faster Software Accelerated D3D driver, but it is nowhere near the performance of a true Hardware D3D driver.
"The closest I ever got was porting standalone OpenGL and a faster Software Accelerated D3D driver"
That's still closer than most people have ever gotten. The only phone htcclassaction has a driver for is the Kaiser. You seem to be the only one that was able to develop this for the Vogue. The effort is appreciated, I remember when you were the only Dev interested in releasing Bell ROMS.
Any chance of releasing the 2 (your stand alone OpenGL and software driver) to the community as cab files?
Thanks again
Jason
You will need a patched XIP with a diamond wce_rex.dll and mmmap.dll. Then you will need clkregim.dll in the ROM. I can't release a community pack, because I doubt any other vogue rom that you will find other than mine has these files.
Thanks for the reply,
Guess I might have to flash again sometime soon.....Darn!!
Hello everyone,
Simple question(s), the new ROMs, 23089/21876/21609, does anyone have a change log? I mean 23089 at least follows the naming convention of 23XXX which has been going on for a bit now.
But 21876 & 21609? Where did these come from? And don't say they just feel magically from the Sky from China or Russia. Someone's got to know a bit more.
Anyone?
agovinoveritas said:
Hello everyone,
Simple question(s), the new ROMs, 23089/21876/21609, does anyone have a change log? I mean 23089 at least follows the naming convention of 23XXX which has been going on for a bit now.
But 21876 & 21609? Where did these come from? And don't say they just feel magically from the Sky from China or Russia. Someone's got to know a bit more.
Anyone?
Click to expand...
Click to collapse
COM1- Builds 217**, the development build will be stop.
COM2 - Builds 218**: GUI is 1st stage of finger friendly features implemented. This is the only official WM6.5 released to public. All other COM* Builds are leaked test builds (not even classified as alpha or beta). In this range, the GUI introduces softer corners to various dialogs, the new start menu (Very early builds had a honeycomb theme but although the hexagons have been removed, the icon alignments remain), and the taskbar and menubar have been slightly modified to allow for further skinning.
COM3 - Builds 230**: GUI from 23001 to 23021 looks the same as COM2. 23022+ introduced the new shorter/expanding taskbar and finger friendly text-based buttons on taller bottom menubar and ever since its been called wm6.5.1 rather than 6.5..
23047+ introduced icon-based buttons.. New checkboxes and scroll bars and recently (from 23069 i think) a magnifier in the taskbar are amongst the newer gui elements introduced in the latest builds..
At some point (im not sure when, kinetic scrolling was introduced..
It appears that COM4 elements are being introduced into this branch such as the new contact application, a slightly modified sms application, and possibly a slightly modified calender application..
COM4 - Builds 234**: Seems to have stopped at 23420. The newer contact application and possibly the modified sms and calender applications were first introduced in this branch but have since been incoorperated into latest builds of COM3
COM5 - Builds 235**: At the moment little is known of this branch. 23502 is the first build leaked that Im aware of. It seems to have been compiled at about the same time as 23060 but with superior stability, speed, memory management, Newer COM3 builds 23071 and above have been reported to be superior in terms of stability and speed. However the latest COM5 23506 compared to COM3 23088 (build date is identical) seem equally fast and stable. COM5 builds have the new Contact app and Magnifier, as in latest COM3 Builds, but lack kinetic scrolling.
Apparently, the new internet explorer has been modified as well (but Bikertibi Builds have the old internet explorer from wm6.1 because new one does not handle well on our device)
Other branches you might or might not come to see:
AKU1 - Builds 212**
SAM1 - Builds 215**
MD1 - Builds 219**
WMD - Builds 28***: The First Build leaked is 28002 (build date 17th November 2009). As of this branch Windows Mobile is at WM6.5.3. This branch is to continue from COM3 23090 and is believed to carry improvements to the New Internet Explorer Mobile as well as overall speed
Builds 216**: leaked builds that have been played with by the team over at HTC but not officially used on any handset as yet
Builds 236**: Recently came across these builds but have no further info on them.
Cheer.
Great post TAI...Very educative...A thousand thanks...You have cleared my wondering about these build numbers.
How come when i google for explanation of build numbers i can't find any stuff that's worth reading?Maybe you could
give us some advices about how to google it or give some links with infos about builds...
Thanks again!
Thanks Tai, answered all my questions.
I appreciate it.
Cheers,
nice information.... thanks Tai!!!!!!!
Hi there,
since i'm searching for a fast and customisable ui since months (90% of them use sense what makes them kind of slow). So I decided to start such a Project on my own.
My main targets are:
- Speed (!!!)
- User-friendly design
- Customizable Widget support
- High built in application support (native support of different music players, browsers and more)
I am going to use .NET Framework 3.5 and delop it using the WM home plugin system.
Since this UI is going to be freeware i'm going to try out this graphics libary (WMGL):
http://www.mobilityflow.com/products/wmgl/
The following shows the current progress and prioritys for planned features.
Current information:
- 2010/10/08 -
I will start development this weekend, for the beginning this will be a solo project. After development of the base system I would be glad about some help, but at that time there will already be progress that shows work on this project really makes sense
- 2010/10/10 -
Spent almost the whole weekend with coding and it was worth it! For now there are already 3 Desktops (configurable via XML) with different wallpaper modes (raw, fit, panorama). In panorama mode the image will be scaled (keeping proportions) over all 3 desktops. Basic widget engine is almost done, already got a first button widget that displays a free scalable graphical button (you can define a border width that will not be completely scaled). Also there is a label element to output text on a widget (the button label).
Here a few seconds of demonstration with 3 different scaled and positioned button widgets and a 1024x768 default windows desktop in panorama mode:
http://www.youtube.com/watch?v=OZ2zCN2BNno
And it will be independent to the device's resolution, like seen here it already works with other today plugins together:
http://www.youtube.com/watch?v=22f3GClKC94
- 2010/10/11 -
Finished and optimized a lot of things today, most important changes are lots of font settings (color, bold, underline, italic, size, h-align, v-align), basic mouse events (down, up, click) and a few actions for those events (show/hide image, open url/file, open ui-dialog). Here a short video of the current version: http://www.youtube.com/watch?v=Zk1Mgmj4HAg
- 2010/10/20 -
Debugged and cleaned the whole code, couldn't find any problems with the current features anymore. Also improved the performance a bit. Added icon's as source for widget images for application shortcuts (icon not scalable! size depends on the device, the wm5 emulator uses 32x32 modern phones usally 64x64). Added a small pager that displays the active desktop. Replaced the button graphics by high-res one's (I know they're not that beautyful ). Here's a video snapshot of that version: http://www.youtube.com/watch?v=c4KQ5s-NxtQ
- 2010/10/24 -
Done some pretty effective performance optimizations and increased the desktop scroll speed some. Replaced the button graphics again but I'm still not that happy with it. Added the most common status widgets (calls, texts/sms, mails) including the matching shortcut. Added a first small digital clock widget (160x80) somehow the clock was not correct when using the emulator, when using my own phone it works perfectly. Here's the video: http://www.youtube.com/watch?v=h2Ur4PrBsSA (reuploaded video, working now)
- 2010/11/03 -
Replaced the graphics again, this one will be the base for the first (stock) skin. The battery icon will be replaced by a black one later. Further added 3 status widgets showing the battery state, signal strength and memory usage. To give a better view (without problems caused by the emulator) I made a video of it running on my HTC Touch Diamond 2 (Topaz). Here's the video: http://www.youtube.com/watch?v=_cIdAYtKnPA
Implemented features:
Desktops
3 Desktops (configured using xml) with independed wallpapers. (Still some todo's)
Widgets
Alert widgets (Calls, Texts, Mails)
Status widgets (Battery, Radio, Memory)
Digital clock widget (One small and one large)
Graphic button widget with text label and/or icon. (URLs, files, applications and a few system functions)
Planned features:
Desktops
(HIGH) 3 freely editable desktops with unlimited widget count / variation.
Widgets
(HIGH) Alert widgets (Calls, Texts, Mails, News!)
(HIGH) Contact widget (different layouts, supporting displaying multiple contacts and filtering)
(MID) Mail- and text-widget (incl. browsing and marking them read)
(MID) News widget (RSS)
(MID) Music widget (with multiple player support)
(LOW) Social widgets (Facebook, twitter, ....)
Tools
(HIGH) Tool for layout backups
(LOW) Update checker
PS: I know there are already many UI's out of there and coding a new one won't make sense for some of you, but imho there is still no really good one out there (at least not for a reasonable price). The most close one is MaxSense, but that mod still drains tonns of memory for sense and is also a bit buggy and limited. (e.g. there is no way to add the same widget twice)
Since i'm not expecting a fast port of WM7 to older devices this is going to be optimized for WM6. Anyway all WM5+ devices should be capable of running this UI.
Best regards
Forsaken
Developer Notes
In this section i will write down things that experienced users (and developers) might want to know.
XML structure definitions
desktop.xml
Code:
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<config>
<desktop>
<wallpaper file="relative\path.jpg" mode="raw|fit|panorama" />
<widgets>
<!-- If posx, posy, width or height are set to 0 these values
are taken from the widget.xml if available -->
<widget file="widgets\widget.xml" posx="0" posy="0" width="0" height="80" />
</widgets>
</desktop>
<desktop>
<wallpaper file="relative\path.jpg" mode="raw|fit|panorama" />
</desktop>
<desktop>
<wallpaper file="relative\path.jpg" mode="raw|fit|panorama" />
</desktop>
</config>
widgets\widget.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<widget width="80" height="20">
<images>
<!-- Images are currently not positionable, if another mode than raw is
set the image will be scaled to fit the widget size.
The border attribute is optional and will only be used for fit_border -->
<image file="relative\path.png" mode="raw|fit|fit_border" border="8" />
</images>
<labels>
<!-- Labels are currently not positionable, too. ;)
The text is just centered into the widget. -->
<label text="About" />
</labels>
<events>
<!-- Coming soon ... -->
</events>
</widget>
+1 for sqvga!
This sounds great!
Looking forward to see your work
I wouldn't say they are slow because they "use" Sense (though I personally hate this tendency to write UIs emulating Sense... not everyone has an HTC phone!) they are slow because they are .NET/C# and unoptimized. If you ask me C# isn't fit for anything that needs to be fast or run permanently... Nothing beats native code in terms of performance. If you want optimization you'll have to go with C/C++... Good code eliminates the need for exaggerated phone specs.
As for renders RawFramebuffer seems to be the best generic bet (GDI is slow) it's not optimal there's no consensual best... Intel Xscale is the best for phones with good old CPUs (not HTC) and OpenGL ES is the best in most new phones.
Homescreen++ is C/C++ but renders in GDI... AFAIK it's the only free today screen plugin in native code (making it one of the lightest) while still being very flexible (though lacking some of the recent features in this sort of UI... which Mortscript can somewhat compensate for). One of my all-time favorite free apps (together with Mortscript, TCPMP, GSFinder+ and WKTask).
Just my 2 cents anyway...
Good luck.
..so this topic is about another manila/spb bs?
shame.
for conscoius users i can recommend: hs++ + mortscript.
rest - go and buy iphone/android.
I am going to use .NET Framework 2
Click to expand...
Click to collapse
dude, wake up. you must be fresh or kidding for bump.
regards,
nothin.
pupakota said:
..so this topic is about another manila/spb bs?
shame.
for conscoius users i can recommend: hs++ + mortscript.
rest - go and buy iphone/android.
forsaken said:
I am going to use .NET Framework 2
Click to expand...
Click to collapse
dude, wake up. you must be fresh or kidding for bump.
regards,
nothin.
Click to expand...
Click to collapse
You're right about .NET 2.0, i will definitly need 3.5. And i won't use only .NET libarys, of course i will try to say native
About iPhone...
About Andoid, i dont have money for a new phone yet And it's about time for a free powerful ui
Only the behavior of the desktops is like andoid, i will definitly not just copy another system. Especially the widgets will be a lot different than those i saw so far.
Anyway coding is my hobby and i'm really motivated for this project. It's fun so far and I'm already making some progress. I got already 3 smoothly slideable desktops with a hard-coded wallpaper, even there is nothing on it yet
I also decided to support any possible resolution, maybe i will even get it working with other (smaller) today plugins together.
Since 2AM here i'll take a rest for now
Wish me luck for tomorrow, I will start to implement a XML-Parser for the desktop-configs and widgets.
Best regards
Forsaken
Good luck, then
And sorry for tone of my previous post.
Have you thought about your project license? If you decide to go open-source you could find TodayLife a big help for ideas/examples/code...
frmariam said:
Have you thought about your project license? If you decide to go open-source you could find TodayLife a big help for ideas/examples/code...
Click to expand...
Click to collapse
Hmm it will definitly be freeware, personally I would like to go open-source but first I will have to check out the licenses of the two libarys I am going to use.
WMGL, a very fast graphics libary: http://www.mobilityflow.com/products/wmgl/license
Free to use with a linked hint that the app uses it. (For freeware)
A small native C++ XML Libary unter CPOL: http://www.codeproject.com/info/cpol10.aspx
I would be glad about an advise, regarding licensing I really don't have a clue yet
PS: Some first videos of my current status above The progress already exceed my expectations for those 2 days of work ^^
I'm wondering how you want to use .NET 4+, when for WinMo is available only .NET CF 3.5 (and something called 3.7?).
For this stuff, I'd really drop any .NET part and do it purely in native code. On the other hand, .NETCF isn't slow actually. What is slow, even in native code, is the GDI+. You MUST use OpenGLES, otherwise you'll fail pretty hard. TouchXPerience is all built in .NETCF using OpenGLES and it runs quite fast.
You can take a look at TigreSDK, but I found out that with few objects on screen, it runs slower (2D text object). I had working physics engine for that though. That's where I ended because of the speed of rendering. Next time I will go for native even myself.
OndraSter said:
I'm wondering how you want to use .NET 4+, when for WinMo is available only .NET CF 3.5 (and something called 3.7?).
For this stuff, I'd really drop any .NET part and do it purely in native code. On the other hand, .NETCF isn't slow actually. What is slow, even in native code, is the GDI+. You MUST use OpenGLES, otherwise you'll fail pretty hard. TouchXPerience is all built in .NETCF using OpenGLES and it runs quite fast.
You can take a look at TigreSDK, but I found out that with few objects on screen, it runs slower (2D text object). I had working physics engine for that though. That's where I ended because of the speed of rendering. Next time I will go for native even myself.
Click to expand...
Click to collapse
Yeah you're right it's going to be 3.5 ^^ I started to mix up the .NET Framework and .NET Compact Framework. The project is set to the 3.5 version. I just corrected it in the main thread, too. Thx for the hint
good Luck!
Forsaken,
Good luck on this! I don't code, so feel like a leach sometimes. BUT, I am willing to sacrifice (dont tell the wife) my phone for testing, and have helped a few guys over here and currently am doing some testing as well with thier themes and UI's.
I am too old of a dog to learn a new trick (my last one was called COBOL!), but at least I can offer testing information.
With that said, if you ever need a tester for another phone, I am running an HTC Imagio with Stock Verizon ROM, running WM6.5 and Sense 2.1 on a WVGA screen.
Good luck, and looking forward to what you can come up with!
JerryA said:
Forsaken,
Good luck on this! I don't code, so feel like a leach sometimes. BUT, I am willing to sacrifice (dont tell the wife) my phone for testing, and have helped a few guys over here and currently am doing some testing as well with thier themes and UI's.
I am too old of a dog to learn a new trick (my last one was called COBOL!), but at least I can offer testing information.
With that said, if you ever need a tester for another phone, I am running an HTC Imagio with Stock Verizon ROM, running WM6.5 and Sense 2.1 on a WVGA screen.
Good luck, and looking forward to what you can come up with!
Click to expand...
Click to collapse
Thanks for your kind offer, I will come back to that for sure
But for now testing won't make much sense, it's just too early.
-- Update:
I just finally finished another chapter (extracting the icon of other applications for shortcuts) and spent much time with cleaning and commenting the code.
Also added a more detailed update to the first post, for lazy one's here a video of the current state: http://www.youtube.com/watch?v=c4KQ5s-NxtQ
Like the updates. Like I said, its just cool that you guys can do this stuff!
Thanks for keeping me in mind, drop me a PM whenever your ready. If I cange phones or anything, I will be sure to let you know!
Here I go again, did some bugfixes causing a high system load and made some new graphics again . Added 3 status widgets showing the battery level, signal strength and memory usage.
For more details see the first post, here the video: http://www.youtube.com/watch?v=_cIdAYtKnPA
At the current rate I will release the first beta version in a few weeks. Until that I will have to figure out a problem that occurs after unloading / loading the interface a lot (desktop process crashes, regular restart needed to get it working again). While testing the normal usage this didn't happen so far. Further i will implement the remapping of application buttons before releasing a beta version.
For now those shortcuts are set up using the xml configuration file.
Hi, really appreciate your efforts, and I encourage you.
What I can tell as a user of TG01 and Acer S200 phones : WVGA phones with 256mo of ram doesn't run well because of lack of memory.
Everybody knows that WM built-in startmenu is very very RAM hungry, on WVGA devices, it can easily hit the 20-35mb of ram usage due to icons caching and other things... thats incredible!!!!
So in my mind, the must have of your UI is a complete WinMo UI replacement, that completely overhads startmenu and kills his memory usage, this would make your UI the best one.
looking good!
Forsaken said:
Here I go again, did some bugfixes causing a high system load and made some new graphics again . Added 3 status widgets showing the battery level, signal strength and memory usage.
For more details see the first post, here the video: http://www.youtube.com/watch?v=_cIdAYtKnPA
At the current rate I will release the first beta version in a few weeks. Until that I will have to figure out a problem that occurs after unloading / loading the interface a lot (desktop process crashes, regular restart needed to get it working again). While testing the normal usage this didn't happen so far. Further i will implement the remapping of application buttons before releasing a beta version.
For now those shortcuts are set up using the xml configuration file.
Click to expand...
Click to collapse
Looking good! Like the speed and smooth transitions. Again, keep up the good work!
May be too flippin early for this, and again, I can't code. But here is a sugestion regarding the battery and signal meters. What about making certain widgets or icons 'lockable' so that whenever you switch screens, they remain (like the signal meters or clocks?).
Like the advances so far, and really like that background image. Great to see how far you have come along!
any update for this great UI? is there posible to get rid the winmo bottombar later?