Related
Ok guys, so this is my new thread. I will keep information, screenshots, and files updated here.
IT WORKS!! I've been disassembling and reassembling this cab file for a while now. I finally got it pretty stable. I removed some files that are not needed and added the appropriate files to work on the Excalibur. I tweaked shellres.dll so the Storage Card issue is gone! I also tweaked and reinserted the appropriate CPR files. I replaced the thin looking top bar icons in the original tshres.dll to the 96dpi icons. MUCH BETTER! If you are using Kavana's ROM, disable ClockOnTop as it doesn't display properly. The program seems to uninstall just fine as well if you're worried about that.
Version info:
Version 1.70 works on WM6.5 based WWE ROMS
Version 1.6c works on Kavana and Rose based WWE ROMS
NOTE: PLEASE TEST AT YOUR OWN RISK. THIS APP WILL WORK ON MOST WM6.1 WWE (World Wide English) ROMS. I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE OR LOSE DATA. ALL PHONES AND ROMS ARE DIFFERENT AND UNKNOWN CONDITIONS MAY OCCUR (you may lose data). Thanks to lukybandit for the original post and enyone else who contributed.
Directions:
- For WM6.5, run 3VO_96DPI_WM65_v1.70.cab or (1.6c for WM6.1)
- Reboot when it asks
- With 1.6c, if your topbar icons appear as white blocks, try running OOK_96DPI_WM61_Patch.cab (and reboot after install)
- Important: Do not run OOK_96DPI_WM61_Patch.cab if your top bar icons appear fine
- To uninstall, go to Remove Programs and uninstall it then REBOOT
- **Note: If upgrading from a previous version, uninstall it first, REBOOT, then install the new version
If you have custom CPR files in the \Windows directory, back them up. This app installed modified CPR files in the \Windows directory to accomodate for the increased screen size and resolution.
Screenshots below:
UPDATE: 1/17/2009, 10:45PM PST, 1.5b works great on ROSE based ROMS! Fixed background misalignment. Note that background image should be 320x240 or so in size. I edited CPR files in \Windows to fix this. If you have a custom CPR file (due to a weather program or something), back it up and then edit the first line and use these values, <Image ID="Background" Opacity="1.0" Top="-17" Width="320" Height="213"/>. Still have the Comm Manager bug in Rose ROMS, working on it.
UPDATE: 1/18/2009, 12:40PM PST, 1.52b for Kavana and 1.53b for ROSE. Fixed some font issues and resized the Rinku topbar icons to fit 96dpi.
UPDATE: 2/21/2009, 10:20PM PST, 1.54 for ROSE ROMS uploaded. Fixed some call screen background problems.
UPDATE: 2/22/2009, 6:30PM PST, 1.55 for ROSE ROMS uploaded. Fixed Opera Mini font problem and adjusted other font sizes. 1.53 for Kavana WM61 ROMS uploaded and also fixed Opera Mini fonts (good find, fliparsenal).
UPDATE: 5/8/2009, 6:20PM PST, 1.6 for ALL WM6.1 ROMS. Comm Manager still not pretty but working on it.
UPDATE: 5/9/2009, 10:20PM PST, 1.6c for ALL WM6.1 ROMS. Updated InnerCircle DLL for 96dpi icon. Comm Manager NOW works in 1.6c (screenshot below) except for the "settings" soft key. To access settings, use settings/connection menu. Should be fixed by next release.
UPDATE: 5/12/2009, 10:50PM PST, 1.6c still for ALL WM6.1 ROMS. Uploaded OOK_96DPI_WM61_Patch.cab for ROMs that have a problem reading the bitmap resource from the DLLs. This works on Kavana's China ROMs and other ROMS not yet tested on. Please test.
UPDATE: 6/14/2009, 1:45PM PST, 1.70 up for testing on WM6.5. It may have bugs as I kinda slapped it together due to overwhelming requests! Please test and report bugs.
Files:
3VO_96DPI_WM65_v1.70.zip
OOK_96DPI_WM61_v1.6c.zip - With new updated Comm Manager (please test)
OOK_96DPI_WM61_Patch.cab - Patch for China and other ROMs
Please continue bug testing and post your results.
i installed teh 1.55 for rose roms and its really weird now. first i uninstalled 1.53, rebooted, ran the new dpi file, let it go to homescreen, then installed new 1.55. then rebooted. now all my home screen layouts have missing topbar icons when i navigate away from teh home screen. and the in-call screen is not fixed. WORST part is: the 1.55 dpi fix doesnt appear in my remove prgrams OR sktool installed programs for me to uninstall
very bad. i feel i bricked the phone with this. help
renegadedj said:
i installed teh 1.55 for rose roms and its really weird now. first i uninstalled 1.53, rebooted, ran the new dpi file, let it go to homescreen, then installed new 1.55. then rebooted. now all my home screen layouts have missing topbar icons when i navigate away from teh home screen. and the in-call screen is not fixed. WORST part is: the 1.55 dpi fix doesnt appear in my remove prgrams OR sktool installed programs for me to uninstall
very bad. i feel i bricked the phone with this. help
Click to expand...
Click to collapse
Thats bizzare. I am running 1.55 on my Dash right now and no problems. And it appears in the Remove Programs list. Not sure what happened. Are you sure you didn't run the Kavana one by accident? Reboot the phone, run the installer again without running dpi.ccs. It should then appear in remove programs. Then try to remove it as needed.
Also, did you reboot after you uninstalled 1.53? Very important.
ookba said:
Thats bizzare. I am running 1.55 on my Dash right now and no problems. And it appears in the Remove Programs list. Not sure what happened. Are you sure you didn't run the Kavana one by accident? Reboot the phone, run the installer again without running dpi.ccs. It should then appear in remove programs. Then try to remove it as needed.
Click to expand...
Click to collapse
WOW
ok i did that and i got topbar icons back and its in remove programs thanks! ill let u know i f i find any further bugs
okay the in-call screen is fixed. but ending the incoming call froZe my phone. hahaha i think its just my phone not the 96dpifix haha
made my phone a lot slower and the text isn't so clear
try re -installing it again, mine is working perfectly..good job ookba
Possible to get celecmd.exe from you? I'm having trouble finding it
i installed the 1.55 version and it works fine.thanks for the program.you did very good job.
yipcanjo said:
Possible to get celecmd.exe from you? I'm having trouble finding it
Click to expand...
Click to collapse
if you have any of the rose roms celecmd should be included. its called command processor in start menu
run dpi.css and it wont do anything it lookslike but it did.
the only thing now is the wallpaper fix, it doesnt stretch all the way to the bottom of the screen, not a big deal
fliparsenal said:
the only thing now is the wallpaper fix, it doesnt stretch all the way to the bottom of the screen, not a big deal
Click to expand...
Click to collapse
Hmmmmmm, thought I fixed that. Can you post a screenshot?
Everything is good, i like it but I cant get the commanager to appear. It just loads but never comes thru. Also, Windows Media isn't Stretched...
It looks great, but now it's a little slow my dash freezes in the when I access picture & videos. When I try to close then in task manager they will not close. I have to turn off the phone. Also the jogger started dancing around on its own. again I had to soft reset to clear up the problem. These are all issues I did not have on the Rose Rom ( Ricky & Stylez ver )
oh i think its cause i need to edit the .cpr..thing is i cant find it in the windows directory. which files? all i see are the .cpl
I installed the Rose Rom version and everything works great, except that my windows start menu icon does not look like the one in the picture. The icons in my start menu are also a little grainy now and I had to increase my default font size through Accessibility in the settings menu to make the text messages and contacts list larger and readable.
Does anyone know of an easy font changer program to increase font size and pick a different font?
hey i just installed it now...i am having the same problem as when you first came out with it...after i installed it the nrg weather program icons do not work...as i figured since they weren't made for this...i am using kavana's rom 080408 if that's correct...anyways i am being lazy but i thought you guys will know what weather program works with it..thanks
nrgs mini weather works fine, usually i have to reinstall it aftere installing the 96dpi. try that.
@fliparsenal....thanks
i feel like an idiot...
anyone can help me wit editing the cpr files so i can fix the wallpaper issue?
Here is a background creator for manila version 2 and 3. I looked into getting it to work with stock roms such as 1.14 and I couldn't get it to overwrite the files on my device.
You can load any image into it and it will auto stretch the image and retain high resolution. You can add a watermark to a photo with drop shadow and/or glow, to give you a chance to add your own touch to an image.
This was implemented with the help of chainfire's cfc console app.
Anyways enjoy!
Instructions: DO NOT USE MaxTTM unless you want a black line in your BG
Run M3dBackground.exe
click on select file and select an image (it will auto stretch it to full screen)
add text if desired, and hit generate previews to confirm it is what you want. then hit save images and select a folder to save to.
the cfc process takes a good while, so be patient.
shut down manila. (start -> settings (all settings) -> today (under personal tab) -> items tab -> uncheck TouchFLO 3D
find the 4 files that end with manila that were created in the directory you selected, and copy them to your windows directory on your phone.
restart manila. (start -> settings (all settings) -> today (under personal tab) -> items tab -> check TouchFLO 3D
Done!
works with manila v2 and manila v3 for the Touch HD
Requirements:
Touch HD
Manila V2 or V3
.NET 2.0 or higher framework
CONFIRMED WORKING ON THE FOLLOWING ROMS:
-Dutty's HD XTREME series
Program is based on the information provided by Rozenthal.
http://forum.xda-developers.com/showthread.php?t=500178
Oh boy Very nice work! I don't know if you saw it, but someone made a similar application after my presentation of the wallpaper issues in that post.
http://forum.xda-developers.com/showthread.php?t=503511
The principle is the same, but with a few differences - namely, that app uses separate source images for the landscape and portrait, but the sizes have to be exact as the output (480x696 and 800x403).
Perhaps you could team up with Maranello and see if you two can cook up something to solve the fact that these work only with new Manila, and not the v1 stock Manila.
And also, there is still an issue of how to workaround the fact that the images seem to be 1 pixel misaligned (not your fault, Manila is the problem). I think ChainFire (author of CFC) knows something about what's causing this and how to solve it.
In any case, this is very nice contribution and I thank you for the effort!
Thx man, this is my first post, so here are some wallpapers created with your great app. Working on Dutty's_HD_V2.9_XTREME.
I did the above and copied manila files into windows and restarted TF but nothing happened, any advice???
Cheers
danprocter said:
I did the above and copied manila files into windows and restarted TF but nothing happened, any advice???
Cheers
Click to expand...
Click to collapse
Are you running Manila v.3? My version is TouchFLO 3D2.0.37889.1
sad that we can't use animated pic..
great tool... very easy to use! thanks! milosn... used your wave background as a test on my WM 6.5/Manila HD.... thanks for posting and allowing me to use as an example as well.
Working with Dutty 2.8 too! Thanks
cortez.i said:
great tool... very easy to use! thanks! milosn... used your wave background as a test on my WM 6.5/Manila HD.... thanks for posting and allowing me to use as an example as well.
Click to expand...
Click to collapse
Its nice but I am really keen on the backgrounds and as you can see your screen of the colored bg, the lower part is off by few pixel...not so good to use when ur using detailed background design.
Either its slightly off or theres that line again inbetween. (building screenshot)
kieboy said:
Its nice but I am really keen on the backgrounds and as you can see your screen of the colored bg, the lower part is off by few pixel...not so good to use when ur using detailed background design.
Either its slightly off or theres that line again inbetween. (building screenshot)
Click to expand...
Click to collapse
believe me ... no one will notice when it's on my device. a few pixels?? i'll never worry about it! this tool works great!
So my device says "TouchFLO V3.0 build 32567" I guess this is different than the manila version as this does not work for my HD.
Would love to see this compatible with the old manila!!!
Pandemoniumone said:
So my device says "TouchFLO V3.0 build 32567" I guess this is different than the manila version as this does not work for my HD.
Would love to see this compatible with the old manila!!!
Click to expand...
Click to collapse
is the stock 1.14 rom manila 1?
bcrisp82 said:
is the stock 1.14 rom manila 1?
Click to expand...
Click to collapse
I'm not sure. I have the latest from HTC's official roms 1.56 on my HD currently and I don't see any difference in the manila from the shipped rom of 1.14
So my guess is that 1.56 is still the old manila, please correct me if I'm wrong.
HTC hasn't updated the manila in any of their roms yet from what I understand.
Pandemoniumone said:
I'm not sure. I have the latest from HTC's official roms 1.56 on my HD currently and I don't see any difference in the manila from the shipped rom of 1.14
So my guess is that 1.56 is still the old manila, please correct me if I'm wrong.
HTC hasn't updated the manila in any of their roms yet from what I understand.
Click to expand...
Click to collapse
ok, i'll flash a stock rom and make this compatible with v1. thanks for the info
You are my god! Thank you!!
Sorry for the stupid question but i can`t do it!!!
I run the M3dBackground.exe on my desktop PC i choice picture and i save it all is done i recive 4 manila files after that i synhro my Blackstone and i copy and paste this 4 manila files in my windows directory after this nothing heppand! So i don`t understand what you mean by "Shut down the MANILA" and after i copy tha manila files "restart manila" from where i must shut down this and restart?
And the final question is after this how im able to choice witch wallpaper i wana use? right now when i wana change my wallpaper i just click on wallpaper and i choice wallpaper from my Memory Card but for example when i make few direferent wallpapers like this and i copy all the manila files in WINDOWS after this how im able to choice with one i wana use.. and later if i want to switch to another wallpaper!
Please explain me this is very importmantly for me because i really don`t understand how Manila work! Explain me like for a idiot very clear hehehe
So right now i already done few diferent wallpapers but don`t know how to use them right!
Thanks in advance
pity this doesnt work with v1 (stock 1.14) as the app is sweet and works very well. Very glad to hear that this will soon work on 1.14 stock
the app is sweet and works well so look forward to having some of my great photos on my hd
bcrisp82 said:
ok, i'll flash a stock rom and make this compatible with v1. thanks for the info
Click to expand...
Click to collapse
Most excellent!!! Thank you very much, I'll be looking forward to it!
Not working for me also im with Davideuck v5 Room and my Touch FLO is V3.0 build 32567
I did everything and when i set the defaut wallpaper apear Half screen image!
Now i will upload screen shoot`s to see what i mean!
And the second screenshot showing how look my phone befor to copy the manila files!
I use the program to make this croco skin much more clear and Hight Definition.. maybe.. is better to stay this way for now
any chance this will support build 32567 from tmobile ??
2010-06-25 Unless I experiment with the GPS code (or something else) then the kernels here are likely older than the official ones from dzo. Since my GPS code is in the official source tree and we now have NBH editors this thread is more or less obsolete. I will update it when time allows trying to keep it somewhat up to date but make it a habit to look for kernels here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D Use a hexeditor or the NBH Editor to change dzo's NBH's into something that works for you.
Based on the latest source code from http://androidhtc.git.sourceforge.n.../kernel.git;a=shortlog;h=refs/heads/htc-vogue
as of 2010-06-29 (But with an ugly hack that powers off on reboot (since reboot is currently broken)).
Use the included NBH Editor (thanks loserskater) to customize the NBHs to work with your setup.
zImage is for HaRET users.
board-kaiser-keypad.atttilt=0 normal
board-kaiser-keypad.atttilt=1 AT&T tilt
board-kaiser-keypad.atttilt=2 Nordic (Swedish, Norwegian, Danish, Finnish)
board-kaiser-keypad.atttilt=3 azerty (French)
board-kaiser-keypad.atttilt=4 qwertz (German)
Nordic extra mappings
---------------------
Left softkey = [
Shift->Left softkey = {
Right softkey = ]
Shift->Left softkey = }
Fn->Tab = $
Fn->Enter = %
Fn->L = |
Fn->O = "
Fn->Left = ;
Fn->Right = '
azerty & qwertz extra mappings
------------------------------
Fn->Tab = $
Fn->S = "
EDIT: Added a Polaris NBH on request.
EDIT 2010-04-15: Updated both zip files with new NBH files as I found that my tinboot.S was allocating smaller system partitions than the ones provided by DZO
EDIT2 2010-04-15: Updated NBH for Kaiser to include clock parameters (set to their default values) for the daring who wants to do their overclocking in NAND. Hexedit those at your own risk.
EDIT3 2010-04-22: Updated NBH and zImage for Kaiser with the latest GPS fix from jnadke
EDIT4 2010-04-26: Update with latest official code from DZO but also my own experimental GPS code that I hope will reduce the amount of GPS freezes.
EDIT5 2010-04-30: Latest DZO code as of 2010-04-29 and my own Kaiser GPS code that now works and works very well.
EDIT6 2010-05-01: New version again, reverted this code: http://git.linuxtogo.org/?p=groups/...it;h=e31a36fc22b4d122261eb6d99596584854234459 as it broke audio on my Kaiser.
EDIT7 2010-05-01: New version posted! More bugfixes to the SAT data.
EDIT8 2010-05-04: New version based on the official source code which now includes my fixes. No need to update if you used the version I posted on May 1st. I also updated the Polaris NBH with the latest code. Not sure if it uses the Vogue or the Kaiser GPS code.
EDIT9 2010-05-08: Updated with the 2010-05-07 update from DZO. Uploaded new files for both Kaiser and Polaris however the changes are for Polaris only so no need to update for Kaiser users.
EDIT10 2010-05-09: I'm really sorry, uploaded the old Kaiser version yesterday by mistake. It's fixed now.
EDIT11 2010-05-20: New version with the Kaiser Camera fix (Donut only) Also included a Polaris NBH in the same zip file
EDIT12 2010-05-20: I'm not so sure the Kaiser Camera works with my NBH. It seems i mixed up the NBH's and falsely assumed it was working. Please use the official NBH's from DZO if you need a working camera in Donut.
EDIT13 2010-05-22: Kaiser Camera in Donut now works. At least when using NBH. Getting the the new initrd.gz from here may help HaRET users: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
EDIT14 2010-05-24: Updated with latest code from DZO. Improvements in the camera code.
EDIT15 2010-05-27: Touchscreen fixes and GPS fixes. Also rearranged kernel parameters to make it compatible with loserskaters NBH editor.
EDIT16 2010-05-29: Updated to latest code. Changed HEPE calculation to use HDOP*4.5 and also some minor GPS logging changes. Included loserskates's NBHEditors in zip-file.
EDIT17 2010-06-05: Rearranged and optimized a lot of the Kaiser GPS code. Changed HEPE (again) to HDOP*4. Fixed a possible bug that would trigger if PRN 32 was visible.
EDIT18 2010-06-05: Updated with latest DZO updates as of 2010-06-01 (Polaris fixes)
EDIT19 2010-06-06: Some small tweaks to the Kaiser GPS code. My GPS changes has now been pushed to the official source tree.
EDIT20 2010-06-08: Updated with new code from DZO. More tweaking to the Kaiser GPS code. Included Kaiser and Polaris NBHs as someone reported problems when converting Vogue NBH to Polaris NBH.
EDIT21 2010-06-08: New version that should not turn off SD card on suspend like previous version likely did (and caused sleep/wakeup freeze)
EDIT22 2010-06-09: DZO fixed the SD card suspend problem and he also added support for GPU overclocking. Included new, fixed, version of the NBH Editor.
EDIT23 2010-06-21: Finally took the time to compile new kernels. Latest official code + some small changes to the GPS code (Flashing LED on Kaisers when GPS is enabled). I also done an ugly hack to call kernel_power_down from kernel_reboot because I got fed up accidently pressing reboot (which doesn't work anyway). Vogue and Polaris NBH's also have ppp.nostart parameters and clock parameters for easy manipulating.
EDIT24 2010-06-23: Updated with new changes from dzo, more battery saving for us Kaiser users.
EDIT25 2010-06-24: More fixes from DZO.
EDIT26 2010-06-30: Updated the kernels because BT headset for Kaiser is currently broken in the official files (but fixed in source tree)
Compiled a new version this morning with the new Kaiser USB code and updated the zip-file.
Great work dude, I'm sure there are plenty of people who will benefit from this
kallt_kaffe said:
Compiled a new version this morning with the new Kaiser USB code and updated the zip-file.
Click to expand...
Click to collapse
Hi,
How can you compile a new nbh with the latest zImage. I want to make it for Polaris...
Thanks in advance.
Cheers
zenity said:
Great work dude, although it only works for Haret installs I'm sure there are plenty of people who will benefit from this
Click to expand...
Click to collapse
NBH is included... read first post again.
manu33xtro said:
Hi,How can you compile a new nbh with the latest zImage. I want to make it for Polaris...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=5411636&postcount=2
However step 8 is wrong. Only the last instance should be changed.
kallt_kaffe said:
http://forum.xda-developers.com/showpost.php?p=5411636&postcount=2
However step 8 is wrong. Only the last instance should be changed.
Click to expand...
Click to collapse
Thanks I look for that...
But hey I am perhaps not good enough to do that
Cheers.
For those who prefer 320x480, read this...
Native LCD resolution is 240x320, aspect ratio 3:4 and we use LCD density 120 for this.
Running 320x480 give an pixel aspect ratio of 2:3 (although scaled to 3:4) and with this we use LCD density 160. I suppose the reason to run at this res (apart from getting fancy screenshots) is that some applications expect a 2:3 pixel ratio. Before the Market hacks I also suppose it enabled access to more applications but that is not an issue anymore, right? The price we pay for this is a blurry display (due to scaling) and slower performance (due to handling a higher resolution internally)
If the above assumptions are correct then we no longer need a pixel width of 320 pixels but some of us may still prefer the 2:3 ratio to make things fit better.
Right, so what if we use a pixel width of 240 (native) and still 2:3 ratio? That would be 240x360. I'm currently running that resolution (with NAND) by using the hexediting mentioned in the first post. Seems to work fine so far. I haven't compared but it should be less blurry than scaling down from 320x480 and also the performance hit should be smaller.
Remember though that if you go from 320x480 to 240x360 remember to edit /system/build.prop to change density back to 120 (because you propably have it at 160 right now)
Have fun!
kallt_kaffe said:
Right, so what if we use a pixel width of 240 (native) and still 2:3 ratio? That would be 240x360. I'm currently running that resolution (with NAND) by using the hexediting mentioned in the first post. Seems to work fine so far. I haven't compared but it should be less blurry than scaling down from 320x480 and also the performance hit should be smaller.
Have fun!
Click to expand...
Click to collapse
How you use 240x360?
I changed value and load Android, but bottom of apps are invisible because not placed in display.
DmK75 said:
How you use 240x360?
I changed value and load Android, but bottom of apps are invisible because not placed in display.
Click to expand...
Click to collapse
Maybe it's different with a Kaiser? For me it scales 240x360 down to 240x320 which makes everything fit but it looks a bit compressed and blurry. I just changed the height from 320 to 360 in the NBH file (with a hexeditor) and reflashed it.
kallt_kaffe said:
Maybe it's different with a Kaiser? For me it scales 240x360 down to 240x320 which makes everything fit but it looks a bit compressed and blurry. I just changed the height from 320 to 360 in the NBH file (with a hexeditor) and reflashed it.
Click to expand...
Click to collapse
Yes, i get this rescaling effect.
It work only after i changed resolution to 241x360.
All apps fits but clock makes oval
DmK75 said:
Yes, i get this rescaling effect.
It work only after i changed resolution to 241x360.
All apps fits but clock makes oval
Click to expand...
Click to collapse
Yes scaling a 2:3 resolution to 3:4 will have that effect.
You could try 270X360, that should make the clock round as it is 3:4. However you should get the same effect, but less blurry by reverting to 240x320 and set lcd density to 107 (in /system/build.prop)
Hi,
Thanks for upgrade your first post with a nbh for Polaris, but I tested it and impossible to have boot screen : he blocked in the first view !
It's the same comportemnt with the latest dzo's nbh...
I don't know why.
If I've time tonight I wil test with W6.5 and Haret with your latest kernel ...
Cheers.
manu33xtro said:
Hi,
If I've time tonight I wil test with W6.5 and Haret with your latest kernel ...
Click to expand...
Click to collapse
Well : the screen freezes just after the progress bar (of haret screen) ends ...
Impossible to see anything else
Cheers.
New NAND files in first post. The tinboot available is apparently not uptodate with the one DZO uses and I found more differences. My old NAND was not allocating as much space for system parition in NAND as the ones by DZO do.
Updated both Kaiser and Polaris NBH file. Only affects NAND uses that have system in NAND and needs additional space (like when trying the Sense 2.1 build available in the Vogue forums)
kallt_kaffe said:
New NAND files in first post. The tinboot available is apparently not uptodate with the one DZO uses and I found more differences. My old NAND was not allocating as much space for system parition in NAND as the ones by DZO do.
Updated both Kaiser and Polaris NBH file. Only affects NAND uses that have system in NAND and needs additional space (like when trying the Sense 2.1 build available in the Vogue forums)
Click to expand...
Click to collapse
I just updated with Your latest .nbh, but mtd size is the same - should I reinstall android to see it or there is another way to resize visible nand space?
voyteckst said:
I just updated with Your latest .nbh, but mtd size is the same - should I reinstall android to see it or there is another way to resize visible nand space?
Click to expand...
Click to collapse
Yes, you would need to reinstall I think. You should be able to keep data but back it up just to be on the safe side.
Updated the Kaiser NBH. The only difference is that the clock divider and clock frequency kernel parameters have been added. They are set to their default values but can easily be changed using a hexeditor before flashing your device.
This is ONLY for those who are aware of what it means, everyone else, just pretend it isn't there.
EDIT: Done some testing and I'm not sure if those parameters have any effect on the Kaiser, maybe it's for the Vogue only?
kallt_kaffe said:
New NAND files in first post. The tinboot available is apparently not uptodate with the one DZO uses and I found more differences. My old NAND was not allocating as much space for system parition in NAND as the ones by DZO do.
Updated both Kaiser and Polaris NBH file. Only affects NAND uses that have system in NAND and needs additional space (like when trying the Sense 2.1 build available in the Vogue forums)
Click to expand...
Click to collapse
Hi,
Thanks for this new version : I will test it tomorrow and write to you if it's good
Cheers.
kallt_kaffe said:
Updated the Kaiser NBH. The only difference is that the clock divider and clock frequency kernel parameters have been added. They are set to their default values but can easily be changed using a hexeditor before flashing your device.
This is ONLY for those who are aware of what it means, everyone else, just pretend it isn't there.
EDIT: Done some testing and I'm not sure if those parameters have any effect on the Kaiser, maybe it's for the Vogue only?
Click to expand...
Click to collapse
Can You also add to nbh parameter: board-kaiser-battery.battery_capacity=xxxx?
HELP...?
Hi, ive had my HTC Touch HD for like 14 months or so now, (since it was released)
and i CANNOT for the life in me work out the whole CAB, manila, etc thing... i'm generally quit tech minded and consider myself easy to adapt to this stuff... but i've been completely beat...
I just can't work it out..... i managed to brownload that TF3D program to open the files from within but im limited to certain themes with that program.... its in fact the 'Vista' theme that i love and want! but its a CAB and when i download it it downloads as just an 'Attatchment.php' file and i dont know what to do with it!
What am i missing... i've read everything there is to read on this forum... and im STILL totally lost.
Help Me!
Hi there,
let me give you a few definitions
*.CAB = an installer file, it can add items to the regisrty and install files to your device
Manila = the interface that was installed on your device when you got it, there are 3 versions:
Version 2.0, TouchFlo3d = the interface installed on 1st gen devices sucha as the diamond, raphael and blackstone
Version 2.1, TouchFlo3d2 = the interface installed on second gen devices such as the Rhodium and Topaz
Version 2.5, Sense 2.5 = the newst interface from htc, found on the HD2 (Leo, this is a 3rd gen device). HTC have also released for tp2 and diamond 2 users running stock
Resolutions
WVGA = 800X480, HD1, HD2, Pro3, Rhodium, Topaz, Kovsky (XperiaX1), x2
VGA = 640X480, diamond, kaiser, raphael
These are the 2 main rese's you will here about
Porting:
As the HD is a wvga device, chefs have copyed files from the HD2, so you have get ROMs with sense 2.5
Any more descriptions needed, post em here and i'll see what i can do
Hope this helps
xttocx said:
when i download it it downloads as just an 'Attatchment.php' file and i dont know what to do with it!
Click to expand...
Click to collapse
your attachment.php issue suggests your browser is simply not downloading the file, but rather the script that websites have to direct your browser to the file you want (something like that, im not a web guy). make sure you arent right clicking and saving as file/link when you download the file, but are left clicking on the download link. also, try changing browser.
but im pretty sure that the .php isnt the file you want in any form.
Hi,
I propose that my work DIALER (PHONE PAD) FOR HD MINI (PHOTON).
languages ITA AND ENG
Introduction:
The ROM that I use, was cooked by me.
MY ROM (GHOST)_OG69_1.0_ITA – DR_3D
VERS. LAST SYS - 29020
I think it still works on other roms.
This cab OG69_ITA_hdmini_land_dialer allows 360 ° rotation of the dialer pad.
In addition to other applications.
The fluidity of the rotation depends on another program-G-ROTATOR--and its calibration
Vers.1.0 extract the Council as.
I have already tested both vers. 1.4 and 1.3 but should crash.
The 1.0 works very well calibrated.
I recommend this calibration: sentivity 7 - timer duration 500.
MEMORY USAGE: Vers 1.0 occupies about 800KB of memory resident. But I repeat, is very stable!
The vers. 1.3 is immediately after the 1.0 the best. But every now and then go to system crash. The vers.1.3 instead occupies only 230kb of memory resident.
The 1.4 (latest relase) should immediately crash. Very bad.
INSTALLATION MANUAL : G-ROTATOR 1.0 EXTRACT
Extract folder G-ROTATOR - I put in the rar link to the program that you can put in start menu (c: \ windows \ start menu \ programs).
if you want to remain resident in memory to be permanently in-autorun-(c: \ windows \ autorun)
you can use to do this: resco explorer2010 or total commander
(Just a curiosity:
Well balanced, with only the G-Rotator (without dialer cab) I have noticed that already does the first screen dialer pad (screenshot3),but then crashes. but the screen on call and receiving call, do not work.)
.
Point out that I tested only the vers. ita, the vers. eng. I can not because the language on my phone is ITA ROM .
Then accept any bugs.
INSTALLATION:
BACKUP SYSTEM : Board (SPB BACKUP) works very well, never lost any data. Recognizes and upgrade if the ROM version is different.
INSTALL IN MEMORY PHONE: OG69_ITA_hdmini_land_dialer o ENG
soft reset
INSTALL -G-ROTATOR- (COPY OR EVEN SDCARD)
COPY THE LINK (AS ABOVE).
CALIBRATE. SAVE.
SOFT RESET.
If you liked my work is appreciated thanks.
L 'essence of these works are for the sole purpose of research.
To discover the potential of the device PHOTON.
To share with you the fruit of my work.
I accept constructive advice as long as.
Thanks : Laurentius26
APOLOGIZE IF I FORGOT SOMETHING!
great job
I have just flashed back to my original HTC HD Mini WWE 1.36.707.3 rom and it already has landscape mode for dialer by default.
Could it be that your rom does have the latest cprog which doesn't have landscape mode?
If you read my thread above, I already wrote that with only G-.rotator, does the dialer pad, but from my tests, not running, receiving and transmitting calls. You can see that on the HTC site these are the versions for Europe rom:
ROM Version:
Greece: 1.36.482.1, Portugal: 1.36.410.1, France: 1.36.406.1, Denmark: 1.36.403.1, Italy: 1.36.408.1, Europe: 1.36.401.1, Spain: 1.36.412.1, Russian Federation: 1.36.411.1, Sweden : 1.36.413.1, Germany: 1.36.407.1, Nederland: 1.36.404.1, East Europe: 1.36.479.1, Norway: 1.36.409.1. thread: http://www.htc.com/it/SupportDownload.aspx?p_id=314&cat=2&dl_id=980
your rom (1.36.707.3 WWE rom), I think both WWE stock ROM ASIA (not for the European market.) As above, I think it is different to the one I used.
I tested it also NSOURM ROM (plus package from ASIA WWE) and the same result as my ROM ITA.
Hmmm .... I did a testing on my current nsourm WWE 3.0 rom and cprog was able to receive and make call while in landscape mode, maybe it was due to the program used for rotation ..... I'll try it again using g-rotator tonight.
HI Ahinigami,
I do not understand!
IF YOU ALREADY HAD THE SOLUTION TO THE PROBLEM??
IF YOUR ALREADY ROM works perfectly in landscape mode??
WHY DO NOT YOU HAVE GIVEN THIS INFORMATION, THE THREAD: http://forum.xda-developers.com/showthread.php?t=1058967
and YOUR (POST No.10)
You gave information about the program: ChangeScreen ?????? for rotation in LANDSCAPE!!
if YOU already worked, all because you have not said before ??????
I have them talked about the dialer cab!
Keep in mind that if you install my file (OG69 hdmini_land_dialer.cab ITA) and then remove the cab, the application is actually installed. . To take the test you have to give a hard reset first!
p.s. cprog file is always the same ........
In post 6 I did mention about cprog working in landscape mode and at that time I thought it was due to nsourm rom and I was simply suggesting alternative app for rotation in post 10.
So in order to test this dialer pad(cprog), I did a hard reset on my phone and then flash back to my original HTC HD Mini WWE 1.36.707.3 to test out this dialer pad with G-rotator 1.3 and to my surprise, original HTC rom dialer pad also support landscape which I assumed not based on your discussion in this thread http://forum.xda-developers.com/showthread.php?t=1058967.
Currently I flashed to nsourm WWE 3.30 rom and tried to recreate the issue you mention above which is unable to receive and make a call during landscape mode but mine does not encounter this problem.
p.s: I've never install OG69_HDMINI_Eng_Land_dialer.cab as of yet because I'm trying to recreate the issue of unable to make and receive call during landscape.
Hmmmmm,
you keep your good ROM (HD Mini HTC WWE 1.36.707.3 full rotator)
because my rom does not work in landscape without my cab!!
Nothing could be simpler:
You do not need my cab! Simple!
I am happy that at least you used (as indicated by me) G-ROTATOR
P.S. for vers. 3.30 nsourm I think you have to wait ...... because today is the last verse. 3.0