Quote:
Originally Posted by Starfox
Couple of things.
- ROM defaults to English (UK) which I guess is a function of using a WWE OS.
- NueNullKB is selected but never is installed.
- Dialog box is all screwey. The top part shows up properly, but the bottom part is all pixelated. This is regardless of whether RealVGA was run or not.
- Couple of icons for stuff that's not selected (Album, Audio Booster) shows up on my Start Menu.
- After using the ROM for a day or so, it stops responding. It boots fine, shows Manila, but once booted won't launch applications. I can get to some stuff (Memory) via the taskbar, but the Start Menu won't launch, Messaging shows up in tasks but can't switch, etc. Only way out is a hard reset. And I've hard reset like 3 times in the past 3 days.
- Looking for a way to put the Keyguard control panel into 6.5. I like having the 0/5/30 sec delay before auto-keyguard instead of manually locking via 6.5 lockscreen.
- I kind of miss the default phone canvas for Sprint. And I think I've lost keypad-to-dial functionality, this may be because of Manila.
This is my first time cooking, so I'm not all that familiar with Recmodding or importing cabs, etc. I know there is a newer version of Manila (1919 I think) than what's available in the kitchen. I was trying for a bare-bones Manila build (Opera/Office/Manila/Total Commander), and just install the rest via cab (Google Maps, My Phone, Live), but it's not looking that easy to get a stable build so far.
And a couple of things I noticed using RealVGA 96dpi. - You have to run RealVGA after cooking to get 96dpi support. Any way to "cook" it in by default?
- Manila Comm Mgr buttons get buggy when scrolling down under 96dpi.
- Complaints of WLM dlls not having 96.dll support.
- Scroll bar is... ugly, to put it mildly. And very hard to use.
-- Starfox |
1. True, You can change it, it needs a proxml though and I never took the time to figure it out.
2.Well you only notice it is installed because your in screen keyboard shouldnt pop up unless you do it manually
3. I am assuming you have RealVGA installed- This is due to the 96dpi resources
4. if you are using manila 2d these apps need to be installed
5.I believe this might be because of the 96 dpi resources, the lockscreen is from a 6.5.x build so it crashes a 6.5
6. Dont think its possible in 6.5
7. You should always use the sprint canvas...I dont know why you wouldnt, do not disable phone canvas when switching to 96dpi
You can not use a newer version of Manila because it is not compatible with the Treo Pro. As far as recmodding, i wouldnt worry about it...
1. I think BigE figured it out in his ROM but i dont know
2. Ya it does...
3. I fixed it
4. Think I fixed it
So here is an updated RealVGA Resource Pack for WM 6.5