yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze ROM Development] Ahmad__Sami:
Go back to threads and you'll find no comments on sounds before v2.5 (the version I started with of this ROM), and after v2.6 I found three members start complain about sound - pfcsabre himself talk about it - while I were looking in the previouse threads to find if the sound was an issue and been finalized, and found no comments on it, so I joined that discussion and asked pfcsabre about it in his new release.

pfcsabre answer me on it before ur post .... thanks pfcsabre :) ... So, what is ur post for or add?

I'm much grateful pfcsabre and all other great ROM cookers for their unique ROMs which carry out their targets and reflect the group needs (not a personalty needs) ... u think there are other chefs can creat a ROM for me, but I'm sure there are such chefs and I do appreciate all of them and thier arts.
[Touch Pro, Fuze ROM Development] nitroblu:
don't worry, i'll test it for you ;)
[Touch Pro, Fuze ROM Development] Jazz8:
I don't think the sound needs to be changed; Personally I found it a little loud but it was easy enough to fix. If it gets changed on this build, others may want it louder again... 6 of 1, 1/2 dozen of the other.

Is 21009 supposed to be a little quicker; better stability?
[Touch Pro, Fuze ROM Development] pfcsabre:
you'll know soon enough-- I'm uploading it already :)
[Touch Pro, Fuze ROM Development] Reefermattness:
Ive been using this ROM since 1.01 its been this loud since then....

Just because there was no posts on the issue does not mean that it wasn't happening.

I do still have battery issues, but they are WAY better than before... i usually have a battery drop right after i pull it off the charger, but then do a soft reset and the batter will come back up most of the way. Could be a number of different things though. I use S2U2 and even though it is WAY better than previous builds it still seems buggy and i cant help but think it still has some battery drain. As we also know radio can have a huge issue on battery, and even on the way a ROM runs altogether. Im testing BS 1.10.25.25 (SECURITY UNLOCKED ONLY) right now and i can actually go almost a whole day without plugging my phone in. LOL I usually keep my phone up above 75% because i have like 8 different chargers so i have one at every place i go, but for the past couple days i have just let it go all the way down to zero and haven't noticed much battery issues other than when i first pull it off the charger before i soft reset.
[Touch Pro, Fuze ROM Development] pfcsabre:
Link posted!

Happy flashing-- and Fido/Rogers users let me know if it works :)
[Touch Pro, Fuze ROM Development] nitroblu:
i definitely will!

Don't mean to hijack ur thread pfcsabre, but i'm also very interested in finding out from everyone not in Canada who flashes v3 beta to report back on how their caller id function is effected? if any1 can post tehir results that'd be great! i just want to make sure replacing rilphone with the Rogers rilphone.dll file doesn't screw up any other network's caller id function (because we don't know for sure if rogers simply added extra code to the file, or changed some code in the file itself)
[Touch Pro, Fuze ROM Development] pfcsabre:
you're not hijacking the thread, you're helping me :p

It didn't affect anything on my side while I'm testing things out, so I've cooked it anyways.

Oh-- and if someone is waiting for RC2 that'll be for tomorrow :)
[Touch Pro, Fuze ROM Development] fhk:
2.06: Black on black. Anyone have this?

I have this problem in 2.06, in the dialer, that writing is black on a black background several places.. For example on the slide to answer screen, I can't see who's calling because it's written in black. Anyone have this? And most of all, is there a fix?
[Touch Pro, Fuze ROM Development] pfcsabre:
Ah-- I forgot this one to post. As I've said here's the registry keys to change it:

[HKEY_LOCAL_MACHINE\Software\HTC\PHONE]
"CallerNameRGB"=dword:16777215
"CallerNumberRGB"=dword:16777215
"CallStateRBG"=dword:16777215
"highlightColor"=dword:04210752
"highlightTextColor"=dword:16777215
"matchesTextColor"=dword:00065360
"matchesHighlightColor"=dword:02105376
"textForegroundColor"=dword:16777215

To give you a hint, 16777215 is FFFFFF-- which is white :)
[Touch Pro, Fuze ROM Development] ramontrotman:
where did this 21009 build come from? there's alot that doesn't look right here. who got a hold of it first? and where did he/she or it get it from?
[Touch Pro, Fuze ROM Development] fhk:
Thx! Helpful as always...
[Touch Pro, Fuze ROM Development] pfcsabre:
It's in the Diamond forum, it's definitely a beta release as what I always check for beta releases is the future date timebomb. I'm not sure who released the first if it's Da_G or arrupenthal :p
[Touch Pro, Fuze ROM Development] ramontrotman:
....i'd stay away from it. not sure its worth the time and effort for what it is. a more stable and might i point out REAL build will surface really soon.

but hey....you're the chef....i know you start to itch if you don't tweak every few hours.
[Touch Pro, Fuze ROM Development] nitroblu:
tested, caller id now works in Canada :)

but i noticed I didnt' get hte slide to answer screen when i palced a test call to my cell?

also when I pressed the ignore button to hang up, the ignore button became all inverted in colour (probably just a graphics issue)
[Touch Pro, Fuze ROM Development] Trezona:
I cant seem to get windows live to work on this build?

Any one else having this problem?
[Touch Pro, Fuze ROM Development] pfcsabre:
confirmed, working on it :) Along with the XIP and SYS change is Windows Live, I usually don't put in detail the changes in the SYS on the change list.
[Touch Pro, Fuze ROM Development] p50kombi:
pro's and cons?

So is this build faster than 2.06?

Because of beta status..bit worried to update, can't really find any post on the differences..

Speed increase?

Graphics speed increase?

Itching to update though :)

Good work, Lantis...
[Touch Pro, Fuze ROM Development] pfcsabre:
if you're:

- not a flash addict

- not a "hey I want the most updated kick-ass ROM!" type

- not a Fido/Rogers user who wants to have caller id RIL support

- not using MSVC call notification

then might as well stay with 2.06 and wait for 3.01 :) In my opinion if it's faster? yes. Is it stable? yes. Is it MORE or the SAME stable vs. 2.06? not quite (as Trezona pointed out already that Windows Live is not working), that's why it's BETA :)

I'm still using the same OEM apps, and mostly the XIP and SYS (and SYS apps) are the ones getting changed.
[Touch Pro, Fuze ROM Development] p50kombi:
Haha..tnx..

I think I belong to the first two categories :)

But I do use windows Live alot, so guess I'll wait for 3.01 (hihi..any eta?)

Problem I'm having with current windows live is that although I am connected through either WIFI or activesync, my hotmail e-mail account keeps connecting through GPRS or HSDPA.

Any idea what's happening there?

As usual, keep up the good work PFCSabre...looking forward to 3.01...can't wait :D
[Touch Pro, Fuze ROM Development] fhk:
BTW pfcsabre, is the MSVC fix you implemented in 3 applicable to 2.06? If it was I think 2.06 would be a real reference ROM for the TP...
[Touch Pro, Fuze ROM Development] pfcsabre:
yes, but it needs to be cooked, not copied. 2.06 is not final yet, so... :)
[Touch Pro, Fuze ROM Development] fhk:
I hope you find the time to finalize 2.06 then :-)
[Touch Pro, Fuze ROM Development] Trezona:
Man this new build is fast!!!

Tomtom 7 only takes 3 seconds to open :)
[Touch Pro, Fuze ROM Development] p50kombi:
ARGH

After that comment!!!

Can't wait for 3.01 with fixed msn...

WOHOOO

Anyone any ideas on the hotmail/msn problem I mentioned before?

That send/recieve your hotmail account always opens GPRS connection instead of using open WIFI or activesync connection?
[Touch Pro, Fuze ROM Development] nitroblu:
i ran into the same problem. but it's workin now for me :). wat i did was install the official latest release from wl (the one wit no built in msn) over the one built into the rom. the i uninstalled it in "remove programs". then i installed wl build 10.6.0034.0800 (it's the updated version to wat was installed originally in v3..not sure if that matters though). so i can't really say if installing build 10.6.0034.0800 alone over the current build will solve the problem since i took an extra (possibly redundant) middle step lol

also, is anyone having trouble getting a gps lock wit this version? i know it can't be my radio b/c i was able to get a gps lock with it quite quickly before flashing v3. when running gps test, my gps just hangs on trying to start up the gps (ans thus when i run garmin, i just hangs on "searching for satellite")
[Touch Pro, Fuze ROM Development] pfcsabre:
no need for that, it's only some registry settings missing, packing a cab now :)

don't have a problem with the GPS lock-- I'm locking 5 when I started GPS test and I'm in a building...

p50kombi, I'm checking that one right now...
[Touch Pro, Fuze ROM Development] p50kombi:
PFC...your the man...

Thanks man...

Great, this personal service :)

If I can help with anything, or test stuff for you, let me know :D
[Touch Pro, Fuze ROM Development] Ahmad__Sami:
Start>Settings>Connections (tab)>Connecions>Advanced (tab)>Select Networks> from the 1st drop-down list of "Programs that automatically connect to the Internet should connect using" select "My Work Network".

ok ... ok ... ok.

Personaly, I use "My Work Network" choice for both Network Management (Internet & Private Network).
[Touch Pro, Fuze ROM Development] p50kombi:
thanks

Thanks, but that didn't really work for me.

What I want is the behaviour that the WIFI or Activesnc is the 1st to try, if that doesn't work, then connect to 3G.

If I do it your way, I can only send recieve via AS or WIFI, and no more over the air via 3G.

Strange thing is that when you first login to messenger, Hotmail account will update via WIFI or AS if you press send/recieve.

Only when not connected via messenger, it doesn't work via WIFI or AS and connects to the 3G network.

Strange, eh?
[Touch Pro, Fuze ROM Development] pfcsabre:
fix to MSN Live in release post :)

as for the connection thingy I'll check it when I get home-- I don't have a WIFI in the office :rolleyes:
[Touch Pro, Fuze ROM Development] p50kombi:
no worries...

I'll keep my eyes open..

so the fix, does this mean there won't be a 3.01 release planned soon? :)
[Touch Pro, Fuze ROM Development] pfcsabre:
not at the moment :)
[Touch Pro, Fuze ROM Development] p50kombi:
Okiedokie..

Flashing now :)
[Touch Pro, Fuze ROM Development] Reefermattness:
Mirror

Lantis OS 21009 AKU 1.5.0 v3.00 BETA RC1 MIRROR
[Touch Pro, Fuze ROM Development] Jazz8:
Another job well done Pfcsabre!

All is working great for me: Wifi; GPS; Caller id. Fast and stable ROM with no lag, freezing etc. All I have to do now is check battery drain overnight... 2.06 was amazing loosing only a few percentage points during the night (after about 6-7hrs).

When 3.01 is finally released will you be using this or the 2.06 beta as a platform?
[Touch Pro, Fuze ROM Development] rwertz14:
Stock Tab

Just curious, will there be a version released with the stock tab included?
[Touch Pro, Fuze ROM Development] Reefermattness:
RC2 is the version with stock tabs. Still a work in progress. We will both keep our fingers crossed. :)
[Touch Pro, Fuze ROM Development] rwertz14:
I understand that, I was wondering if there was going to be a v3.00 RC2 released is all.
[Touch Pro, Fuze ROM Development] Reefermattness:
Oooooh, this ROM is SMOOTH. I just wish i lived in Canada so i had caller ID now. :)
[Touch Pro, Fuze ROM Development] fhk:
Just to clarify: Is caller-ID broken outside Canada with 3.00?
[Touch Pro, Fuze ROM Development] venelar:
I think it's more Canadian networks have a new caller ID feature. If you are outside Canada it should be the same as always.
[Touch Pro, Fuze ROM Development] pfcsabre:
No bugs? :)

Matt, thanks again for the mirror, I'll put it on the release post as soon as I log to my PC, I'm on my TP right now.

I'll be releasing RC2 this week definitely, I'm just a little bit overwork on my job right now :o just a little bit more patience... :rolleyes:
[Touch Pro, Fuze ROM Development] stixnstownes:
got overposted :P Pfsabre, please help if you have it
[Touch Pro, Fuze ROM Development] nitroblu:
after using it for a day, i gotta say it's a very solid build. I'm still getting some major lag at random places which either fix themselves or require a soft boot, but I think it's a problem with the base build (some of the other new ROMs i've tested have hte same problem).

I got really bad battery drain though? I charged it overnight, walked out this morning at 100%, down to 12% when I got home, and i only have ~2 min talk time, ~1.5 hour 3G surfing/email checking (not all at once)....anyone else getting bad battery life :(?

EDIT: I just charged my phone from 12% to 100%, in less than 2.5 hours. I think it's supposed to take 3 hours for a full charge (if I remember correctly)...so it seems liek it charged faster than it's supposed to LOL. Possible battery meter bug?

BTW, i've attached screens to show the graphic error in the slider that I mentioned before (I know my description wasn't that good LOL)
[Touch Pro, Fuze ROM Development] shortness:
how do i change the registry for black on black in weather and programs
[Touch Pro, Fuze ROM Development] nitroblu:
hope you don't mind pfcsabre, i made a cab to make the changes so it's easier for every1 ;)

if sum1 knows the files that control the graphics for the issue I posted above, i wouldn't mind giving it a shot at fixing it :)

BTW, I tried flashing a different radio onto my phone, just to make sure it wasn't my radio, and my GPS is still not locking. It just keeps hanging on "gps starting up" (in gpstest) and "search for satellite" (garmin)
[Touch Pro, Fuze ROM Development] pfcsabre:
I'll post a cab for it-- the black or the regular one?

I'm not having problems with the GPS or even the slider-- it's still the slider that I've used from 2.06, so it shouldn't be a problem. Maybe the RIL is causing this on fido/rogers? Can anyone other than nitroblu confirm?

For the battery, this has almost the same consumption with 2.06, and I'm using it for 3 days already without a problem.
[Touch Pro, Fuze ROM Development] Jazz8:
I can confirm, battery life is about the same as 2.06 (which was fantastic in my opinion). As far as GPS is concerned, it took me about 5 minutes to initially connect through GPS test but after that all is fine here; I am able to run my Garmin Mobile XT with no problems (so far).

I experienced a similar GPS problem once while I was using NATF's 2.2 and upgraded to 3.2. I inquired and no one else seemed to have the issue. I re-flashed the ROM and eventually it connected (after what seemed like 30 mins); it was so slow that I decided to switch radios (using 1.02.25.28 now).

It may be an issue more related to the radio??? I find Radio's very confusing; Initially battery drain seemed a little high with .28 (when I first used it), after trying several others, I eventually went back to .28 it it was better than ever. This is just my experience but it really makes me wonder (also makes me very hesitant to flash once I have a lightening fast lock and great battery life :)
[Touch Pro, Fuze ROM Development] titan85:
Thank you for making best ROM for Raphael. I really appreciate your work.

However I have question for you: Are you still working on CZE version you promised before ?
[Touch Pro, Fuze ROM Development] pfcsabre:
I am working on it, but since I posted it nobody was really interested (only my friend who has it flashed already and went back to Prague, and also the reason I built it).

There is no SocialNetworks yet though, I'm still asking for some help on translations on the SocialNetwork and it should be good to go.
[Touch Pro, Fuze ROM Development] equinox2355:
Any idea when this will make it into the rom? (or if it even will)

http://xdaforums.com/showthread.php?t=468639
[Touch Pro, Fuze ROM Development] nitroblu:
i guess it just took a lil luck lol. I finally got a GPS lock :). it's weird though, it was really weak at first and kept dropping for about 10 minutes, but i've got a solid signal now :)

@pfcasbre:

i' tihnk i might try a reflash then if no one else is having slider graphics problems. I doubt it has anything to do with the rilphone.dll file though, from what i've been told, it's a very low priority file but is essential to the phoen's function.

if you don't mind me asking, what are the files for the graphics of the slide to answer? maybe i can try and find out wat went wrong with my phone :)
[Touch Pro, Fuze ROM Development] shortness:
can i use this for black on black in the weather and program tab?
[Touch Pro, Fuze ROM Development] nitroblu:
no, it's just to apply the reg fixes to get the right colouring in the dialer
[Touch Pro, Fuze ROM Development] nitroblu:
don't worry about it pfcsabre ;) I did a lil more snooping myself, I simply replaced a .dll file related to the slider, and the graphics work fine now :) I think it may have just been some coding in the dll that applied the graphics improperly. I've made a cab for a simple fix, in case anyone else has the same problem :)

EDIT: I also re-up'ed the cab for quick reg edits to get the white text colour in the dialer (so that it's all in one post)
[Touch Pro, Fuze ROM Development] pfcsabre:
check the attached file shortness and try it out :)

heh, you should try to cook now :p I'll put it in the release post in case someone has a problem :)
[Touch Pro, Fuze ROM Development] nitroblu:
hahah i'm no where near as skilled as you cooks ;)
[Touch Pro, Fuze ROM Development] stixnstownes:
regular one if you can. thanks :)
[Touch Pro, Fuze ROM Development] pfcsabre:
did you reset? :p
[Touch Pro, Fuze ROM Development] shortness:
yup and its the same
[Touch Pro, Fuze ROM Development] pfcsabre:
sent you another pm :)
[Touch Pro, Fuze ROM Development] equinox2355:
Any ideas?
[Touch Pro, Fuze ROM Development] pfcsabre:
*ssssssssshhh* :rolleyes:
[Touch Pro, Fuze ROM Development] Reefermattness:
excellent :)
[Touch Pro, Fuze ROM Development] venelar:
is the MSVC fix working? Looking good
[Touch Pro, Fuze ROM Development] pfcsabre:
ok-- the RC2 with stocks tab is almost ready, sorry for the long wait. It would be anytime today :)

EDIT: RC2 uploaded, but on the last minute I decided to make it private BETA to have more feedback. It seems RC2 users died down already and only seems a handful so it will be a waste of time for me to continue this project if that's the case.

RC2 users, ask for the link, and you shall receive :) In exchange is of course, feedback on how it goes.
[Touch Pro, Fuze ROM Development] _fr0st:
I would be really happy if I could test. Started using the first RC2 at once when you released it, and still am :)
[Touch Pro, Fuze ROM Development] fhk:
Hi pfcsabre. My two cents on this: I think the "dying down" might have to do with your versioning-scheme (Release Candidate 1 and 2... Usually this indicates subsequent versions of the same software, but not in this case...) plus having 2 versions of the ROM going in parallel. I think people are very unsure as to what they give up (or gain) by using RC2 over RC1. I am for one. More bugs in RC2? Less stable? Or is it just the stocks tab that differentiate the 2? I also think you should consider making FINALS in each series... I'm not meaning to criticize, I love your ROMS, just some input from a followers pov :-)
[Touch Pro, Fuze ROM Development] pfcsabre:
ha-- but that was the point of RC2 BETA 1, and the RC1/RC2 merge.

RC1 is always the release that I have

RC2 is RC1 + stocks tab

The whole point of the different release and the merge is if:

- the lag on startup is acceptable vs. speed gained of manila after loading

- "landscape bug" when using the Blackstone engine vs. having a stocks tab

The reason why is it still RC1 and RC2 is that the question was never answered before-- and with the merge some doesn't like the landscape bug but some woudn't mind it since it can be easily resolved. It's easier for me to release just one, and RC2 is my little bit of side project. I don't use the stocks tab, and I do the RC2 release for fun. But then I also have a wife and a job, so I would prefer to concentrate on releasing just one.
[Touch Pro, Fuze ROM Development] fhk:
Certainly qualifies as a good argument! Thx for your hard work and efforts.

BTW: Do you plan on releasing a 3.00 RC1 (not beta)? I'm kind of holding off flashing 3.00 because I'm so happy with 2.06... But I'm kind of at a loss as to what to do now...
[Touch Pro, Fuze ROM Development] pfcsabre:
Current RC2 BETA will be 3.01 RC1 with the normal Manila :) There's nothing to fix anyway except for the MS Live, which is fixed in this version.

_fr0st: sent the link in pm :)
[Touch Pro, Fuze ROM Development] fhk:
Looking forward to it!
[Touch Pro, Fuze ROM Development] gikoz:
Interested on testing RC2

Interested on testing RC2. Can you provide a link?
[Touch Pro, Fuze ROM Development] Trezona:
Cab for latest gps drivers?

pfcsabre, would you mind posting a cab for the latest gps drivers?

Hope this wont be a problem :)
[Touch Pro, Fuze ROM Development] gloom:
Hi pfcsabre

Me again, still want to help testing, so could I help this time for the private RC2? :$
[Touch Pro, Fuze ROM Development] pfcsabre:
I haven't updated the gps drivers since the gps is working flawlessly for me-- you want to try the 2.03 gps drivers?

Sending the link now... :)
[Touch Pro, Fuze ROM Development] drieves1:
I would like to test beta: Lantis OS 21009.1.5.0 v3.00 RC2 Thanks.
[Touch Pro, Fuze ROM Development] drieves1:
Thank you so much
[Touch Pro, Fuze ROM Development] Jazz8:
Just a little confused here... If RC2 Beta is the "3.01 RC1 with the normal manila" then what is meant in post #910 when I read "RC2 = RC1 + Stocks Tab"?

Does this new Beta include the Stocks Tab? If so, will there be an RC1 3.01 released without the stocks tab?? I don't use the stocks tab and it sounds as though it creates some type of landscape issue; on the other hand I am interested in trying these newer 2.03 drivers and having the few needed fixes cooked in.

If the Stocks Tab is not included, I'd be interested in testing this new Beta. If they are included then I'll just wait for now (assuming that a non-stocks tab release will eventually surface). Sorry if I am missing something and asking a stupid question; Thanks in advance, Jazz8.
[Touch Pro, Fuze ROM Development] drieves1:
Great work with that stock tab. Its major step in getting it working right in landscape. Doesnt start on its own but i know the steps to getting it to work.
[Touch Pro, Fuze ROM Development] Jazz8:
Just followed the link on the first page and noticed that this reads 3.00 RC2 so perhaps I am just confused over the 3.00 vs 3.01.

I'm assuming that 3.01 RC2 will include the stocks tab which is not released yet and 3.00 RC2 does not have the stocks tab; I think you explained this in post #1 when you wrote "I've still put this one as 3.00 even though there are driver changes and fixes-- this is for preparation of what's in store for 3.01. RC2 with Stocks Tab will be ready TODAY". If this is correct and 3.00 RC2 doesn't include the stocks tab then I would like to test it if you need more testers.

Sorry again for all the confusion; I am trying to catch up on a bunch of new posts and release announcements and found myself confused... think I got it now :)
[Touch Pro, Fuze ROM Development] pfcsabre:
It's starts up after next reboot :) if I start it up automatically after 1st reboot UC sometimes screws up. I'm still checking it out on how to remedy it.

You got that right! :)

EDIT: a little bit more explanation...

The 3.00 RC2 is the prelude to 3.01 RC1, meaning 3.01 RC1 will be the same as 3.00 RC2 but with the normal Manilla (without the stocks tab).
[Touch Pro, Fuze ROM Development] drieves1:
I just seen that. I mean its great work with it.