+Feb 5+ *SSK 1.2 Stable* {CE OS 21109} Kitchen and ROM

[FormerPalmOS]

Originally Posted by Kamokazi

So what you are saying...would it be beneficial to use as stripped a ROM as possible and install cabs instead of OEMing the files? So they install to Program Files and not Windows? Or is there a way to OEM them in and install to an alternative directory?

Also, can some basic WinMo programs be moved out of the Windows directory and still work?

Most programs originally written to be installed as a cab will install their files to something in \Program Files. When you turn them into OEMs, unless you take the time to build an initflashfiles.txt to move them, they end up in \Windows. I personally strip the ROM and install everything as a cab after the fact. Not to mention that for things that can be updated, it's much easier to update a cabbed in app vs. baked in.

On moving some WinMo apps out of \Windows, a properly written app may require a DLL but should check \Windows for that DLL instead of checking . If it checks ., it may fail unless you also move said DLL to wherever you are moving the app.

I'd look at apps that have a boatload of ancillary files (like HTC Keyboard) as things to move - but then again, HTC Keyboard was never designed to be installed as a CAB - so moving it could have issues.

Sorry - not a terribly useful response.

[Kamokazi]

Originally Posted by FormerPalmOS

Sorry - not a terribly useful response.

Not at all...you pretty much gave me the exact answers I was looking for.

[oldman]

Someone asked about setting up VOIP

Check out this site: http://julien.schapman.free.fr/touch...setup-voip.php

IT says:
SIP settings configuration
Outgoing calls configuration
Enable/disable VoIP over 3G
Automatic language selection (English and French supported for now)

Since I don't use VOIP, I can't tell you whether it works for this ROM or not

Bob

[keaolyen]

Asking again...

Has anyone run this ROM on Sprint?

[oldman]

Originally Posted by bast525

Bob - since you have that nifty software that measures battery usage, I wonder if I could have you test something for me?
I am trying to figure out, for a constant data stream, like when streaming music or youtube videos, does it use less battery to stream over EVDO, or over wifi? Lets assume a good EVDO signal, 3-4 bars, and for the wifi, being very close tothe router, 10-20 feet with a clear line of sight.

I *seem* to get slightly better battery life over wifi, but both methods drain battery very quickly and cause the radio to heat up a lot (I took the back cover off.... the battery was not the main source of the heat). I would love to have some hard data though to know which method is better for battery!

Originally Posted by oldman

I agree, but I'll use the 1.11 anyhow. Check back tomorrow, cause I'll run each mode down to 10% battery, with a charge in between
I'll be looking at CNN News on the MediaPlayer. Bob

Initial Results from WIFI operation - Other than the phone itself, the following items were turned used: Pocket Streamer and WM Media Player. The only other active item is that the TP was operating at FULL BRIGHTNESS....so if you use a dimmer screen, the battery will last longer.
The sawtooth pics of the current are normal....gives the chips a few milliseconds to cool off rather than run at a constant rate.
Pic 18 shows the current draw.
Pic 19 - Battery Drain in the WIFI mode (Data connection OFF entire time)

I'll finish the EVDO test after recharging, and will edit this post to include the results.
Edit 2: Added EVDO test. Same config as above..Except EVDO is the one turned on. I have no explanation why the current graphs #18 and #21) are so much different. Run basically under the same conditions
PIC 20 - Battery Drain in EVDO Mode red-EVDO, Green, WiFi
PIC 21 - Current draw
Bob

[Kamokazi]

Originally Posted by keaolyen

Asking again...

Has anyone run this ROM on Sprint?

Closest I could find:

http://forum.ppcgeeks.com/showpost.p...0&postcount=61

[mojojo]

I'm back in school now, so I do not have that much time to read the forums. 1 comment...1 question:

Comment: If it helps your development at all, I found out that if I disable the password lock in the lock settings, the "Long Press End Key" lock feature starts working again with TF3D! When I set the password lock again, the "Long Press End Key" lock stops working, and the screen just flashes. The "Long Press" lock works in both cases if I disable TF3D. Perhaps it is just a glitch in TF3D.

Question: I installed the latest Opera, and edited the .xml file located in \Application Data\Manila, with the path to "OperaL.exe" per the instructions on fuzemobility, and the TF3D browser button still will not work. Also, when I am in landscape and I press "Bookmarks", I get a message saying "The file 'OperaL' cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. If the problem persists, try reinstalling or restoring this file."

Any thoughts?

[bast525]

Bob - I look forward to seeing the evdo results!

FormerPalmOS - sai understand it, the new drivers are from the most recent Diamond rom, 2.09. I tried to get it out of the Fuze kitchen put put by Da G over on xda. But it is part of xip.

[FormerPalmOS]

Originally Posted by bast525

FormerPalmOS - sai understand it, the new drivers are from the most recent Diamond rom, 2.09. I tried to get it out of the Fuze kitchen put put by Da G over on xda. But it is part of xip.

I have that - dumped the XIP and have all the modules ready to play with. Just need to figure out what hardware is different between diamond and touch pro that affects early boot phase. But I'm reasonably confident that DDI can be switched. Stay tuned - hopefully I will have progress this weekend.

I can't put in the mad hours Scott puts in on these things.

[phattooth]

Originally Posted by TwoDawgs

If you hard reset your device you will need to re-apply the GPS fix. So if you wanted to get rid of it a hard reset would work.

I'm not all the way caught up yet on reading, so maybe this has been answered... but i'm sorry dawg, that is not true.

I hard reset (center button + reset) after every flash. Never had to reapply the GPS fix.



EDIT: Ok, caught up now.... so you're saying that it always clears your GPS, whichever way you hard reset?