8 APR 09 - UPD 25: Mods please lock this thread! - Page 143

oldman · #**1421** (**permalink**) 03-12-2009, 07:05 PM

Quote:

Originally Posted by scrosler

There is no way the GPS chip is dead. Its actually part of the core processor. Its not a sep chip. Granted yes, parts of a chip can burn out in THEORY but I would like to see it happen and not take the rest of the chip with it.

Bob, your an engineer? Is it possible for a GPS section of a chip to fry but the rest of the chip be good and perform all other phone functions? Hell not even GPS, any part of any chip? What are your thoughts. Im just an electronic tech trained by the military so you know I dont know much ;c) But seriously,. what do you think? Is that possible? . .

I believe that the primary failure mode of "Only GPS" would be Infant Mortality due to a weak component. After the device has been "seasoned", a failure would typically be catastrophic, not just limited to the GPS. Any "isolated" failure would be random and rare. Most likely the phone would be "toast".

Bob

keaolyen · #**1422** (**permalink**) 03-12-2009, 07:08 PM

Quote:

Originally Posted by RONMAC

Scott,

Any chance we might see the Touch Pro 2 stuff in a new kitchen or ROM?

Back a couple of hours and all the demands start flowing

Scott,

Already told you in PM but +1 on the TP2 manila...

TouchFlow in landscape is sick!

oldman · #**1423** (**permalink**) 03-12-2009, 07:15 PM

Quote:

Originally Posted by scrosler

EDIT: Also, this is the biggest debate for me. If you note I keep apps seperated into folders in the kitchen and that is how they appear inthe ROM. For example, all GPS apps go intot he GPS folder in programs.

My debate is to wether or not I shoudl leave it or revert it to the default locations of just Programs?
Any thoughts?

My opinion would be only additional folders of GPS, Utilities, and SYSTEM.

If an app falls into one of those three categories, put the folder in...Other items can go under the general heading.

My personal feeling about different apps, is I like the availability of independent CABS. Not burning items i nto ROMS(except essential things) makes changes easier when the developer updates his app, and also allows me to easily delete them if I don't like them.

Bob

DigitalAttic · #**1424** (**permalink**) 03-12-2009, 08:33 PM

Quote:

Originally Posted by scrosler

Thank you much! I will look into 21018. Which build was the best? The one FPOS put on my FTP server or was there another build on rapid share?

You can use the one I packaged up for the kitchen from the link over at XDA: Post#920... it needs an NCF35 OEM update, as I didn't catch that it was a slightly older release when I posted it. I have updated my version in the SSK kitchen I use.

PM me if U need any details.

TTFN - DA

DigitalAttic · #**1425** (**permalink**) 03-12-2009, 08:44 PM

Quote:

Originally Posted by jucytec

21028 is the only one that I can get my hands on...

21032 is supposed even better... 21028 is found in Calu's 21028 Kitchen.

Edit: 21028 > 21018... IMO

Hmmm, until someone actually gets a 21032 build that isn't patched with 21015/18 components, I would not even consider it.

I know Conflipper mentioned he had moved to that build, but I never saw any true post where the OS/Build screen had matching pairs. dres took his 21032 build for PPCK down due to spurious errors that couldn't be resolved, most of them XIP related, leading to unbootable ROMs.

I built and flashed a 21028 ROM using PPCK a few days ago to see what the "din" was all about, but quite frankly, I didn't think it was all that great. My "windows folder test" showed it to be slower than 21018, and the scrolling I did on the 1K+ pic folder I have on my SD didn't seem any faster than 21018 either. Memory usage too was about the same, and the initial leak I thought I saw in 21018 isn't as pronounced as I had thought, though it is about 5-7MB in 24 hours, and I haven't seen any builds that don't have some residual leaking, even stock builds

So for now, 21018 seems to be the best build out there IMHO, and I have been running it since we both ported it to Scott's kitchen a couple weeks ago.

CFN - DA

gman4471 · #**1426** (**permalink**) 03-12-2009, 08:48 PM

Quote:

Originally Posted by scrosler

Missing cab error? OYou mean when you dont select a battery icon?

To use the stock battery you should choose that option. The only thing it does is install a completely empty, non provisioning cab. In other words it does nothing at all. Tricky ****y, hey?

I know its not a hardware issue because the stock icon and the percent over icon work fine, and I'm not talking about the overheating as that seems to be an entirely different ordeal all together.

If the battery.cab file is totally blank when the stock icon is selected in build os then it would seem like something getting installed after that would be messing up the accuracy. Only because when battery.cab is removed and customizations error out, the battery icon works fine.

How can I find out what is installed after this so we can start narrowing down the list of suspects?

Also, I get these problems without installing any 3rd party apps

reigndropz · #**1427** (**permalink**) 03-12-2009, 09:15 PM

Scott , you are THE MAN for answering all those questions, lol. You had your work cut out for you. Thanks for responding about my background issue too. Your rom creation has been great to me. I'd like to try that cab you suggested for the my Sprint TP. If i DO re-install the whole TF3D, will I lose anything I have set so far as far as apps working, battery issues and other tweaks? Or will this only replace the manila files?

Thanks again man. Oh and the curtain removal issue......if anyone wants to disable it, you can do so by going to HKLM\Software\HTC\PHONE\ phonelockenable from 1 to 0.

djsiva · #**1428** (**permalink**) 03-12-2009, 09:17 PM

I'm a little behind on my reading so forgive me if it's already been covered, and also for being a little off topic but the new Rhodium Notification and Menu enhancement cabs are sweet!! (IMHO) I've attached them both and a screenshot for anyone who cares.

jucytec · #**1429** (**permalink**) 03-12-2009, 09:39 PM

Here's the file with 21028/21032 Hybrid SYS and 21018 XIP from former.

Someone Asked for it...

I downgraded SYS folders OS and OSFiles because Menu Enhancement from TP2 would not install properly...

I've ripped out my personal stuff off this ROM.

All the of included OEM's are obviously from Scotts.

CLICK ME I'M Special

jucytec · #**1430** (**permalink**) 03-12-2009, 09:48 PM

Quote:

Originally Posted by DigitalAttic

Hmmm, until someone actually gets a 21032 build that isn't patched with 21015/18 components, I would not even consider it.

I know Conflipper mentioned he had moved to that build, but I never saw any true post where the OS/Build screen had matching pairs. dres took his 21032 build for PPCK down due to spurious errors that couldn't be resolved, most of them XIP related, leading to unbootable ROMs.

I built and flashed a 21028 ROM using PPCK a few days ago to see what the "din" was all about, but quite frankly, I didn't think it was all that great. My "windows folder test" showed it to be slower than 21018, and the scrolling I did on the 1K+ pic folder I have on my SD didn't seem any faster than 21018 either. Memory usage too was about the same, and the initial leak I thought I saw in 21018 isn't as pronounced as I had thought, though it is about 5-7MB in 24 hours, and I haven't seen any builds that don't have some residual leaking, even stock builds

So for now, 21018 seems to be the best build out there IMHO, and I have been running it since we both ported it to Scott's kitchen a couple weeks ago.

CFN - DA

Hmm... I did find SOME 21032 SYS files and I made a Hybrid...

Code:

 5.2.21032 aku 1600   |   BaseApps
 5.2.21032 aku 1600   |   BaseAppsFiles
 5.2.21028 aku 1600   |   Base_DPI_192
 5.2.21028 aku 1600   |   base_dpi_192_resh_480_resv_640
 5.2.21028 aku 1600   |   Base_Lang_0409
 5.2.21028 aku 1600   |   Base_Lang_0409_DPI_192
 5.2.21028 aku 1600   |   Base_Lang_0409_DPI_192_RESH_480_RESV_640
 5.2.21028 aku 1600   |   Bluetooth
 5.2.21028 aku 1600   |   Bluetooth_Lang_0409
 5.2.21032 aku 1600   |   BROWSING
 5.2.21028 aku 1600   |   BROWSINGCORE
 5.2.21028 aku 1600   |   browsingie
 5.2.21028 aku 1600   |   browsingie_LANG_0409
 5.2.21028 aku 1600   |   Browsing_DPI_192
 5.2.21028 aku 1600   |   Browsing_Lang_0409
 5.2.21032 aku 1600   |   BTDUN
 5.2.21028 aku 1600   |   Bth_A2DP
 5.2.21028 aku 1600   |   Bth_A2DP_Lang_0409
 5.2.21028 aku 1600   |   Bth_HID
 5.2.21028 aku 1600   |   Bth_HID_Lang_0409
 5.2.21028 aku 1600   |   CommonNonEA
 5.2.21028 aku 1600   |   DRM
 5.2.21028 aku 1600   |   Dummy SQM
 5.2.21028 aku 1600   |   Enterprise
 5.2.21028 aku 1600   |   Enterprise_DPI_192
 5.2.21028 aku 1600   |   Enterprise_Lang_0409
 5.2.21028 aku 1600   |   Enterprise_Lang_0409_DPI_192
 5.2.21028 aku 1600   |   Entertainment
 5.2.21028 aku 1600   |   Entertainment_DPI_192
 5.2.21028 aku 1600   |   Entertainment_Lang_0409
 5.2.21028 aku 1600   |   Entertainment_Lang_0409_DPI_192
 5.2.21028 aku 1600   |   FWUPDATE
 5.2.21028 aku 1600   |   Fwupdate_Lang_0409
 5.2.21028 aku 1600   |   GPSID
 5.2.21028 aku 1600   |   INTERNETSHARING
 5.2.21028 aku 1600   |   IPSECVPN
 5.2.21028 aku 1600   |   IPSECVPN_DPI_192
 5.2.21028 aku 1600   |   IPSECVPN_Lang_0409
 5.2.21028 aku 1600   |   MediaOS
 5.2.21028 aku 1600   |   MediaOSFiles
 5.2.21028 aku 1600   |   MediaOS_dpi_192_resh_480_resv_640
 5.2.21028 aku 1600   |   MediaOS_Lang_0409
 5.2.21028 aku 1600   |   Metadata
dsm not correct size   |   NetCF3.5
 5.2.21032 aku 1600   |   Office
 5.2.21028 aku 1600   |   Office_DPI_192
 5.2.21028 aku 1600   |   Office_Lang_0409
 5.2.21028 aku 1600   |   Office_Lang_0409_DPI_192
 5.2.21028 aku 1600   |   OneNote
 5.2.21028 aku 1600   |   OneNote_lang_0409
 5.2.21032 aku 1600   |   OS
 5.2.21032 aku 1600   |   OSFiles
 5.2.21032 aku 1600   |   Phone
 5.2.21028 aku 1600   |   PhoneRedist
 5.2.21028 aku 1600   |   PhoneRedist_DPI_192
 5.2.21028 aku 1600   |   PhoneRedist_Lang_0409
 5.2.21028 aku 1600   |   PhoneRedist_Lang_0409_DPI_192
 5.2.21028 aku 1600   |   Phone_DPI_192
 5.2.21028 aku 1600   |   Phone_dpi_192_resh_480_resv_640
 5.2.21028 aku 1600   |   Phone_Lang_0409
 5.2.21028 aku 1600   |   Phone_Lang_0409_DPI_192
 5.2.21028 aku 1600   |   ppgprov
 5.2.21028 aku 1600   |   Redist
 5.2.21028 aku 1600   |   Redist_DPI_192
 5.2.21028 aku 1600   |   Redist_dpi_192_resh_480_resv_640
 5.2.21028 aku 1600   |   Redist_Lang_0409
 5.2.21028 aku 1600   |   Redist_Lang_0409_DPI_192
 5.2.21028 aku 1600   |   RemoteDesktopMobile
 5.2.21028 aku 1600   |   RemoteDesktopMobile_Lang_0409
 5.2.21028 aku 1600   |   RUNTIMES
 5.2.21028 aku 1600   |   Shell
 5.2.21028 aku 1600   |   SMIME
 5.2.21028 aku 1600   |   SMS_Providers
 5.2.21028 aku 1600   |   SQLCE
 5.2.21028 aku 1600   |   SqlCeMobile
 5.2.21028 aku 1600   |   SqlCeMobile_Lang_0409
 5.2.21028 aku 1600   |   Transcriber
 5.2.21028 aku 1600   |   Transcriber_Lang_0409
 5.2.21028 aku 1600   |   Transcriber_Lang_0409_DPI_192
dsm not correct size   |   VoiceCommand
 5.2.21028 aku 1600   |   VoiceCommand_Lang_0409
 5.2.21028 aku 1600   |   WinCENLS_WWE
 5.2.21028 aku 1600   |   WindowsLive
 5.2.21028 aku 1600   |   WindowsLiveIM
 5.2.21028 aku 1600   |   WindowsLive_DPI_192
 5.2.21028 aku 1600   |   WindowsLive_Lang_0409
 5.2.21028 aku 1600   |   WWAN

Unlike other SYS's that are mixed versions from 21013-21028 these are 28 and up ONLY.

I had to Downgrade the OS and OSFiles to 21028 because the TP2 enhancements wouldn't load properly...

but... I have to say that i've settled for this over 21018... this one does not give me the startup issues like the 21018 did... tho i'm sure its one of my personal apps causing this... its nice that this is a bit more stable...