Woohoo! Voice Speed Dialer working in DCD's ROM - Mogul, XV6800 ROM Development

Ok, so, I spent all day trying to get my Cyberon Voice Speed Dial working again. I just dont like MS Voice Command or any other program. I like that the fact that the stock voice dialer on my XV6800 is simple, uses trained voice tags so its super accurate, and takes up minimal memory.
Step 1, download attached file.
Step 2, install the cab to your main memory, not an SD card!
Step 3, open up your registry editor, navigate to: HKLM\SOFTWARE\OEM\VoiceCommand and make sure VoiceCMDEnable is set to 1
Assign the button #5 to your voice speed dial
Presto! Back in business.

Thanks so much..I like the simplicity of the built in dialer also and it was the only thing I really missed. thanks again.

Looks like you got it from the link I gave you. I did not have to update the registry at all to get mine working. Chad

Related

Functionality Wish List

Thanks to xda-developers, Jeff's kitchen, T-Mobile's ridiculous data rate plans, and nPOP, my XDA is nearly approaching perfect status where it does everything I want almost exactly perfectly. Not sure who's responsible for the mic mute button in the phone interface, but that was a huge deal for me too.
So, what's left? Not much! Here's some annoyances though:
1. I wish you could copy phone numbers in some places. In SIM Manager or in the Phone call log, you cannot copy a phone number for pasting into an existing contact. You can create a new contact, but you can't just copy a phone number onto the clipboard.
2. The XDA is the only phone I've ever seen from any manufacturer in any country where the battery level is not part of the interface. Lots of shareware options available, but can't understand why this isn't part of the interface.
3. Would like to be able to record voice notes more easily. It's one button press on an iPaq, requires several pen clicks on the XDA.

Microsoft Voice Command launched

For those of you who are interested, just saw on handango.com their new release.
I will wait for the first reports to pay the $40.- though. No trial.
Gear
So far so good..
Well just installed it a couple of hours ago and I have to admit so far this is pretty nice. No training needed, seems to work pretty good and has been dead on accurate so far.
Couple of initial thoughts on it:
1. Can't assign the button to activate the voice to the volume button, this seems to be an limit of the phone or OS and not the application. Basically you have to press a button that activates the voice command software before you speak, it works well but you can only use the calendar or contact button. Personally I would like to the volume button as I never use it for anything, and it is easily accessible via the thumb.
2. Can't seem to adjust the voice talking to you. I would have personally liked to adjust the ladies voice a little. Its ok though sounds ok though like all computer voices kinda blotchy and stuff.
All in all it is accurate and seems to do what it says. Easily launch applications, find contacts and dial stored contacts or a new number just by speaking.
I tried it, and not impressed.
For some things its accurate, however if all your contacts are english sounding names then its easier. If you have non english names, there is problems with recognition.
Additionally it seemed not to recognise anything with the earphones plugged in, and worse still with any kind of background noise, like in the car, no recognition.
Ive found fonix voicedial to be better.
I had fonix voicedial for a long time and IMO voice command is far superior if you have a lot of contacts. No training needed, from command to dialing the process is much much faster. Plus being able to control media player and view contacts verbally is great!
Does fonix voicedial work with an O2 XDAII ?
I haven't found the answer on there site... or perhaps didn't look well
Free Trial, DL and try it. Should work. It runs PPC2003
Thanks

Cingular ROM users: PTT function hacked!

This little app replaces the Cingular PTT service and adds customizable launch capabilities back to that useless PTT button on your Cingular ROM equipped Hermes. This patch initially maps the PTT button to the built in Voice Dialer, but you can re-map the push as well as the hold functions to the application of your choice.
Version History
v1.07 09/20/07
Now compatible with the latest AT&T WM6 ROM!
v1.06 06/05/07
Now compatible with the latest AT&T AKU3.5 ROM!
Smartdialer issue fixed
Phone Settings lockup issue fixed
v1.05 02/26/07
Smartdialer functionality restored on AKU3.x ROMs.
v1.04 02/21/07
PTTFix now disables the built in PTTServiceWrapper on Cingular AKU3.x ROMs. Backward compatability with AKU2.x ROMs has been maintained. Warning: this version also disables smart dialing on aku3.x ROMs. Will be fixed in v1.05
v1.03 02/16/07
Bugfix: PTTFix now de-registers PTTServiceWndClass before attempting registration. This corrects a timing issue on the new AKU3.3 ROM where the Cingular built-in PTT subsystem was registering this at boot time.
v1.02 11/14/06
Most of the built-in features have been implemented. PTTFix now handles everything except <Left Softkey>, <Right Softkey> and <Context Menu>
v1.01 11/10/06
<Start Menu> feature implemented. Choosing this option for any button 5 setting in the button editor will now launch the start menu.
v1.0 11/03/06
ButtonPressLaunchValue and ButtonHoldLaunchValue registry settings have been de-implemented because....
Full integration with the existing button editor in personal settings->buttons (button 5 settings are back!) has been implemented. No need to use a registry editor to change settings any more
Enhancement 10/24/06
For all you brand new 8525 owners: the whole shebang is now a simple CAB based installation!
I also streamlined PTTStart.exe to run much faster. Before, you would see a blank window displayed momentarily while your device was starting. Now you cannot even tell when it runs.
Enhancement 10/23/06
I've attached a new zip file called PTTStart for early implementors who can't get the service to start automatically. Copy this file to your windows\startup directory and it will automatically start the PTTFix service whenever you soft reset!
bugfix 10/17/06
The ButtonHoldLaunchValue value would revert to "windows\\sddialer.exe" after a reset if the length of the ButtonPressLaunchValue string was shorter than the length of the ButtonHoldLaunchValue string..... Who'd have guessed it
v0.2
Added an additional Registry setting:
Pressing and holding the PTT button now launches the applicaton stored in HKLM\Services\PTT\ButtonHoldLaunchValue
If this value doesn't exist, it is created with an initial value of "windows\sddialer.exe" when the service is launched.
v0.1
Pressing the PTT button now launches the application stored in HKLM\Services\PTT\ButtonPressLaunchValue
If this value doesn't exist, it is created with an initial value of "windows\sddialer.exe" when the service is launched.
Thanks to all the early implementors here who helped me to work through the security issues and de-implement the "undocumented features"!
Installation Instructions
1. copy the attached PTTFix.cab to your Hermes device.
2. Using File manager, tap on the cab file to install PTTFix.
note: when asked, you must install this to your Device. The service dll will not load if installed to your storage card!
3. Reset your Hermes device
4. Use personal settings->Buttons to customize Button 5 settings if necessary.
Upgrade Instructions
1. Remove "Sleuth255's PTTFix" using Settings->System->Remove Programs (It may ask you to reset your device)
2. Install PTTFix by following the Installation Instructions above.
Microsoft Voice Command
In Button Manager, simply customize the preferred Button 5 setting (I like to set press&hold to this) by choosing "Voice Command" from the dropdown. Voice Command sets itself onto the Messaging button by default. If you don't change this first, the button manager will remind you that only one button can be set for a given function....
Enjoy!
Wow, very nice work!
I ll setup your fix right now; this is just marvelous
As always, nicely done Sleuth255
ok, so I've completed the message map decode.
For developers, the PTT button event comes in with a message value of 0x312. When this message occurs, lParam is 0x1000 for the release event and something else for the press event. Essentially, my code in the message handler to trap a PTT press event is this:
Code:
LRESULT __stdcall KeyboardProc(HWND hWnd,UINT nCode,WPARAM wParam,LPARAM lParam)
{
switch (nCode)
{
case WM_COMMAND:
break;
case WM_CREATE:
break;
case WM_PAINT:
break;
case WM_DESTROY:
PostQuitMessage(0);
break;
case WM_ACTIVATE:
break;
case WM_SETTINGCHANGE:
break;
case 0x312:
if (lParam != 0x1000)
CreateProcess(_T("\\windows\\sddialer.exe"),NULL,NULL,NULL,FALSE,0,NULL,NULL,&StartupInfo,&ProcessInfo);
break;
default:
return DefWindowProc(hWnd, nCode, wParam, lParam);
}
return DefWindowProc(hWnd, nCode, wParam, lParam);
}
Later on, when any bugs are ironed out (doubtful 'cause it compiled cleanly heheheh) and I have a few minutes, I'll pull the process-to-execute out of the registry and give everyone a little foreground app that lets you map whatever you want.
Excellent, we will be waiting for the little program.
Sleuth255, Thankyou so much, it works perfectly!
You've just fixed my biggest headache with the 1.34 ROM upgrade
Thanks a lot!
Is it possible to make another dll, but with MS VoiceDialer please?
sure. what's the full path executable name for MS Voicedialer?
I've gotta get this app I guess.... everybody raves about it.
markw996 said:
Sleuth255, Thankyou so much, it works perfectly!
You've just fixed my biggest headache with the 1.34 ROM upgrade
Click to expand...
Click to collapse
Good to hear this... Now there's two. You're helping to prove out my theory that the fix will work on all 3 Cingular ROMS. What device do you have btw?
Sleuth255 said:
sure. what's the full path executable name for MS Voicedialer?
I've gotta get this app I guess.... everybody raves about it.
Click to expand...
Click to collapse
Program Files\Voice Command\voicecmd.exe
Thanks!
Drop me a PM
Sleuth,
Nicely done! Now see what you can do about the videocall button....
You may just be able to convince me to try one of these Cingular ROM's...
Actually it's: "\Program Files\Voice Command\VoiceCmd.exe"
Heh... No thanks needed. I love this stuff. I'll set up the voicecmd specific dll tomorrow.
Speaking of tomorrow...hopefully I'll still have a job left to go to after spending the last two days on this ....
@Sleuth255,
We are thanking you not just because you love this stuff but because you are willing to devote your knowledge and effort at helping us, the community, etc... I am very thankful you have resolved this issue, but I am also hoping you can help us with the Video Call button.
Any how, I personally appreciate all of the efforts thus far.
Thanks again.
The videocall button will be problematic... Unlike the PTT button where at least a whimpy dialog was displayed by an identified program when it was pressed, there's nothing that actually works with it on a Cingular ROM. I'll need to flash back to a ROM that has a working video call function to work on it. Quite truthfully, I won't begin this until I load up the next HTC ROM update, whenever that comes out (soon, I hope).
However, what I can do ITMT is load up the relevant video call cab in the HTC extended rom to see what's there and maybe try a bit of disassembly work....
man i read the title of this thread and got all excited, lol
Does not work for me.
Hi Sleuth,
I've made everything as described, but when i try to start the service from TaskMgr (last step) the device completely hangs. Only reset helps.
:-(
Nice try Sleuth265. !!!
Video CAlling is not supported because it needs QoS service to be introduced
and the Ericsson and Lucent UMTS infrastructure do not support it yet. All data services are best effort.
@eeter:
Thanks for the info on that! I was wondering why Cingular decided not to support Video Calling..... Your post won't stop these guys though because they don't want me to actually make video calls work on Cingular's network. Their problem is that pressing the video call button no longer brings up the video call feature. You get the video call feature itself back if you load the TyTN ExtRom after aborting the Cingular customization run. People in Europe on video capable networks are already using this function on their Cingular ROM equipped Hermes devices I believe. If I fix this they will once again be able to bring up the video call app by simply pressing the video call button.
Of course, others simply want yet another mappable button and the thought of something that's useless on their TyTN bugs them (I'm in this camp btw....)
@baudy2:
Ok, what device do you have? What Cingular ROM are you using? My first thought is that you've got a device where your operator has locked down excecution to only signed apps. Since my dll is unsigned, it won't run. Hard to believe that it would hang your Hermes tho... Could you export your PTT registry key and PM it to me please? I'll have a look.
edit: oops all I needed to do was to check your sig for the above two answers. Sorry.
I believe the SPV M3100 from Orange is one of the signed app locked devices. I'm checking into this. I'd still like to see your PTT key export tho...
@everybody else:
As promised, I've added a dll to the first post that launches Microsoft Voice Command when you press the PTT button. Enjoy
Sleuth255 said:
@eeter:
As promised, I've added a dll to the first post that launches Microsoft Voice Command when you press the PTT button. Enjoy
Click to expand...
Click to collapse
Thank you very much!

General and 6.1 Upgrade Tips from a Titan Noob. :3

This used to be a post about things that were broken, I have solved the majority of them. Keep these tips in mind when upgrading. :
Phone Programming
Make absolutely sure you backup your MSID from ##778# before performing any Radio flashes.
Your MSID should not be the same as your MDN on a Sprint device.
Sprint prints your ESN and MDN on their reciepts.
Your MDN is your Phone Number. (It took me a while to figure this one out.)
If you lose your MDN, your voicemail will still work, just call your phone from your phone. The MDN entry is at a different location than ##778# and does
not require an unlock code to edit. A Sprint rep gave me the number, but I forgot it.. It was something along the lines of ##0264788#? If someone knows it, feel free to post it and I'll try to edit it in.
Backup Issues
E-MAIL BACKUPS from WM6.0 will disable your TEXT MESSAGING if you restore them on to WM6.1; Keep your emails backed up via some other method.
SOFTWARE
S2U2 May be problematic with WM6.1, All tests so far have led to a black screen. It is supposedly repairable by using DirectDraw, Another alternative is to use the locker in PointUI.
TouchFlo is not an incredible advancement in the way we use PDAs, it is a problematic finger gesture system. You're better off binding some sort of launcher to your now unused voice calling key. There are also shell extensions which allow you to add secondary actions for holding down a hard key.
Avoid using:
HTC Audio Booster - Doesn't Work
HTC Equalizer - Doesn't Work
(SRS WoW does seem to work.)
HTC Plus - Doesn't Uninstall if you hate it, HTC Home is better.
HTC Quick Launcher - Functionality included in HTC Home
HTC Audio Manager Today - Function in HTC Home
If you have a spare buck, or a keen sense of evading the law, SPB's application suite is a pretty dandy thing to have. I'm an avid promoter of open source software, but Diary, Home, and Plus offer a lot of extra usability.
PointUI is freaking sweet, no question, but the application navigation and task management aren't very user friendly. Hopefully the PointUI team continues adding to their great app. There seem to be some random half-crashes of the app when using the replacement taskbar.
Some SPB Extensions are causing lockups. Could not pin it down, but it was something in Plus! or Phone Suite
BATTERY LIFE
AGILE MESSENGER uses 33% of your processor at ALL TIMES on WM 6.1, If you are having battery issues, try switching to something a little more lightweight. Fring is a pretty lightweight app, and it supports Skype and GoogleTalk voice calling, too. This alone should save you having to purchase an extended battery.
Enabling your GPS Chipset doubles your Idle power consumption.
There are several Extended Battery models you can use with your Titan, two of them which portrude from the enclosure. In general messaging and internet use I find that the regular battery is down to about 40% in my day, about two hours of which I can actively use the device, not including talk time or music listening. I usually take about 10 non-flash panoramas or photos a day from boredom.
The extended battery with the rounded portrusion makes holding the device more comfortable, however, in landscape mode, I often feel myself rubbing over the camera lense for better grip. It also makes it impossible to fit in the included holster, and incompatible with any protective shells, My battery life with Agile Messenger running (which remember eats more battery power than GPS) was at about 50% on the end of each day, and I used the device for about a 50 minute extra period due to bus travel and bus stop boredom.
The largest extended battery will probably allow even the most bored of employees keep entertained, but this battery's casing nearly doubles the size of the phone, costs as much as the phone with a service agreement, and it's rough edges look like they would make the phone the most uncomfortable device to use for anything. Try not to grab this one up for only a 400mah boost, with too much extra portrusion to keep it in the same pocket as your wallet.
if your voicemail isnt working I'd guess that your MDN number is wrong, your MSID and MDN number should both be your phone number.
Scrufdog said:
if your voicemail isnt working I'd guess that your MDN number is wrong, your MSID and MDN number should both be your phone number.
Click to expand...
Click to collapse
Not always, the msid seems to be the first number they give you, but if your like me, the mdn well be the number that you transfered from your "old" contract
In regards to GPS make sure it's enabled. Go to Settings > Phone > Services > Location Settings and make sure it's set to Location ON (or whatever is not 911 ONLY).
As far as MSID/MDN... MDN is always your current number. MSID can vary.. call your carrier for the MSID. You might just want to tell them you did a hard reset and now your phone isn't working. They will walk you through EPST.
Alright, I'll try calling them for the reprogramming and stuff, hopefully they don't get all crazy on me. :3
Scrufdog said:
if your voicemail isnt working I'd guess that your MDN number is wrong, your MSID and MDN number should both be your phone number.
Click to expand...
Click to collapse
If you have sprint your msid is diffrenet
Two things:
One, did you try playing with the directdraw in s2u2? I know when it's on (in wm6) it would lead to a blackscreen for me.
Two, Awesome job man, Being a "titan noob" and figuring **** out yourself is what it's all about. This write up just might help other "noobs" on their way to becoming more experienced users.
Just to let people know
DTMFVibrate does work on WM6.1.
You can back up your contacts, calendars, tasks, notes on Outlook
For those who do not have Outlook I will enclose some apps that help with back ups ( I am not the creator of these apps but they do work )
[email protected]$ said:
Just to let people know
DTMFVibrate does work on WM6.1.
You can back up your contacts, calendars, tasks, notes on Outlook
For those who do not have Outlook I will enclose some apps that help with back ups ( I am not the creator of these apps but they do work )
Click to expand...
Click to collapse
How did you get DTMF Vibrate working? Is there some newer or different version that I don't know of?

NEON 400 Windows Mobile 6.5 ROM

For NEON 400 users only!
Please do not even consider flashing this rom unless your device is a NEON 400. That's the Canadian Telus/Bell version of the HTC Touch Dual. If you don't know how to find out the model number... then I suggest you do some more reading before you consider flashing any roms.
Hey All,
My old phone died so I recently became the proud owner of the HTC Touch Dual NEON 400. Long story short I unlocked it (Thanks to jockyw2001) and found that there are no Chefs out there with this device. There's a couple dedicated dudes out there trying to help all of us NEON 400 users (Talking about you Rataplan, deepankerjha), but since they don't actually have this device it's pretty tough for them to prepare and test a rom for us.
So, I took the plunge. With Rataplan's help (thanks a lot buddy, couldn't have gotten this far without you're help) I've been cooking away and have a solid WM 6.5 ROM here for us. It's based on the Telus stock ROM and WM 6.5 build 21914. I haven't yet cleared all the extra's (so it's a bit fat) but in my testing so far it's 100% functional and bug free (well, as bug free as WM can be )
I can't guarantee how well it'll work on the Bell NEON 400's, but if you have a Telus device, this should do the trick. I'm using it right now on mine.
Please leave feedback if you try this ROM out. I am still a novice chef, but I'll take feedback to heart, and I'll continue cooking and optimizing roms for the NEON 400 as I learn more and get better.
Happy Flashing!
I'll post updates as they come.
UPDATE:
Sorry all, but in my quest to migrate to the Android OS I've ditched my Neon in favour of the Vogue. I'll upload the Lite ROM I was working on for those who want it. The only thing I was having trouble with was the GPS, apart from that the ROM runs very nicely with the extra weight of the cube and other fat removed. Feel free to PM me if you have questions, I'll do my best to help if I can.
Give me a few days to do a fresh build of the Lite ROM and to take one more stab at getting the GPS working.
Okay my final roms are up. Hopefully Rataplan will have the links posted below shortly.
Lite Version: 1.01 - 1.03
-WM 6.5 Build 21914
-TouchFlo Cube removed
-A bunch of other bundled HTC/Telus packages removed
-GPS is still flaky
Version: 2.01
-WM 6.5 Build 21914
-Nothing removed, All stock HTC and Telus packages remain
EDIT I can't post links just yet, so Rataplan's going to help me out with that, check his post below for the download links.
Here are the links:
NEON400_201 Added 19th August
NEON400_Lite_101 Added 9th November
NEON400_Lite_102 Added 9th November
NEON400_Lite_103 Added 9th November
Loaded on my Bell NEON400. Took a while to get to setup and made a few bleeps along the way, now it's at the "Customization" part. Will update as I finish setup and test it out.
EDIT: Finished installation, looks pretty good, will test calling and texting as we go. Any chance we can strip the Telus crap out of it though? Hate seeing "Telus" everywhere when it's not even a Telus phone.
EDIT 2: Trying to set up ActiveSync to sync with my Google Account - it freezes every so often for a short while and won't respond to taps or key presses. Seems to be common in all applications. Also, the keys operate but the backlight never turns on for them (disregard that - they do work, see Edit 4).
EDIT 3: Hitting the X to close a window doesn't kill the app like it did in WM 6.1. Not sure if this normal behaviour or not (first time flasher).
EDIT 4: After a reboot the key backlight is working again. When I try changing the keyboard however to a full QWERTY layout the setting never saves and always reverts to the "touch keypad" or whatever it is (same problem in WM 6.1 so it's a setting issue not a ROM issue - disregard please).
If you could get rid of the Telus branding everywhere and see what's up with the freezing this ROM would be perfect!
Nice job.
got_milk, Thanks for testing on your Bell device. Like I said in the post I wasn't sure what to expect on a Bell phone. I'm working on a lite version right now with the Telus stuff stripped out. I'm also trying to remove the added weight from HTC like the touchflo cube (I really hate that thing...)
I've noticed the problem with the X button not closing apps. It seems in WM 6.5 it just sort of minimizes them. Although if I recall there's a setting somewhere that lets you set it so you can close an app by holding the X instead of just tapping it. I'll look into that some more.
In regards to the responsiveness one thing I've noticed is that when memory is low I sometimes have to tap and hold the buttons for a moment before they register. I initially thought it just wasn't reading the hits but found by accident that I could make it work by holding it for an extra moment. Hopefully this won't be a problem once I get my Lite version working.
I highly recommend downloading and installing Finger Keyboard. It's my favourite by far. I can't post links yet, but the thread where I found it is titled:
\\\\\\\\\ F i n g e r K e y b o a r d 2 ///////// v2.1 - NOW ONLINE - all resolutions
One other thought: If you could hook me up with the ROM you're using as the stock Bell ROM I could recreate this 6.5 ROM using it as the base. This might solve some of your problems too.
Thanks again for testing!
Not a problem, thank you more for doing this! I really hate how we're limited to WinMo 6.1, when we clearly have a 6.5 capable device.
I'm using the stock Bell ROM from jockyw2001's HardSPL post (stickied at the top of this forum).
Looking forward to the lite edition, I will certainly test it when you release it.
So, I couldn't stay away (Software Engineering student...lol). I set up my own kitchen and started to cook using a stock Bell ROM. I've managed to strip all the Bell crap + the HTC cube and make a nice clean ROM.
However!
I've encountered one bug so far. On the home screen, where "Text" should be, it's simply blank and clicking it gets me to the main Outlook menu (where I choose Text Messages or Outlook E-mail). I can also not create text messages or reply to them. I know we've hit this roadblock before but no one's said how they got around it.
I also don't have data working at all - it's not being configured automatically (I think the Bell customization wizard does this, but it's disabled).
EDIT: Okay, it's as I suspected. There's a connection.xml file that's part of the Bell scripts that is added to handle data access. Anyone know how I can add data as part of the ROM package?
For sms take a look at this post from 88fingerslukee,
http://forum.xda-developers.com/showpost.php?p=6961719&postcount=49
Regards,
That registry edit is just enabling/disabling threaded SMS...in my case SMS doesn't work at all (I can receive and view SMS') but I can't create any new ones or reply to them.
got_milk said:
That registry edit is just enabling/disabling threaded SMS...in my case SMS doesn't work at all (I can receive and view SMS') but I can't create any new ones or reply to them.
Click to expand...
Click to collapse
Okay, did you select webview in the sys-part of your kitchen.
Rataplan said:
Okay, did you select webview in the sys-part of your kitchen.
Click to expand...
Click to collapse
Yes, it's essential anyway so I get prompted if it's not included. It's not part of WM build 21914 however...
So I've tried with a bunch of different WM builds, new kitchen setups, and everything I can think of under the sun.
Data works out of the box - it's just not enabled by default. If you go into the comm manager and enable data it seems to work.
SMS is still broken. When it's not highlighted right above the text 'Text' it displays 'No notif...'. Highlighting 'Text' gives you absolutely no text at all and your option for that is 'View', which takes you to your call list.
I've cooked all day and yet I cannot get this to work at all. I'm rolling back to WM 6.1 until I can find a solution.
got_milk said:
So I've tried with a bunch of different WM builds, new kitchen setups, and everything I can think of under the sun.
Data works out of the box - it's just not enabled by default. If you go into the comm manager and enable data it seems to work.
SMS is still broken. When it's not highlighted right above the text 'Text' it displays 'No notif...'. Highlighting 'Text' gives you absolutely no text at all and your option for that is 'View', which takes you to your call list.
I've cooked all day and yet I cannot get this to work at all. I'm rolling back to WM 6.1 until I can find a solution.
Click to expand...
Click to collapse
got_milk, way to go bud! Glad to have another new chef in the kitchen. I wont bother cooking a Bell ROM as you're already on track. My Lite ROM is gonna be a while anyway. Between wife, kids, job, and house... I just don't have a whole lot of time to tinker.
In regards to your SMS problem, I might be able to help. I too had problems getting SMS to work when I started working on my Lite ROM. After some trial and error what I found fixed it was to include two files from the OEMAPPS pkg.
Strip out all the crap from OEMAPPS you don't want and make sure that these two files remain, then include the package in your next build:
234f3319-55a2-46a3-be32-24530a643a0f.dsm
234f3319-55a2-46a3-be32-24530a643a0f.rgu
I'll be honest, I didn't do any research on the significance of these files, I just happened upon it by chance.
Good Luck!
Aha! I shall do another cook tonight and see if that does the trick.
EDIT: You sir, are a brilliant genius. I didn't have the .rgu version but the .dsm was there. Deleted everything out of OEMAPPS but that, cooked and flashed, and texting works now.
Thanks a ton!
Excellent! Glad I could help
So, my two bugs I've noticed so far...
No data. EV-DO is available, looks like it has to be set up manually. Anyone know how we can incorporate this into the cooking? I've tried ADC but it doesn't work, says it's not a valid Pocket PC application every time the phone boots up.
Also, the buttons along the top (sound, data, etc) work normally in the home screen, but enter any app and while the icons remain the same their functions have now been shifted one to the left. (Volume becomes Close, Data becomes Volume, etc).
When I first started a Lite ROM I stripped my Operator EXT packages. That killed my data. I put'em back to work on the OEM pkg's. I haven't had time to dissect the EXT packages yet to find the pieces we need for data. Whichever one of us figures that out first will have to share it with the other
For now I'm still picking through the OEM packages finding all the pieces I want/need to keep.
Not sure about your taskbar buttons, might be related to that handy tasks dropdown item that's usually on the far right (like a quickview task manager you can use to close running apps) I don't know if that's a WM feature, or something HTC bundled in.
That's an HTC bundled application (TaskManager.exe in OEMApps). I removed it and the bug's still there. You don't have this problem?
Data is handled via Connection.xml which is injected - somehow - during the "Customization" process. You CAN do it yourself manually - simply add a new connection and have it dial #777.
There's not much in the EXT packages - and what's there is impossible to tell for now, I'll dissect more and see what's there.
Strange, when I hit any of the buttons along that top taskbar it just opens up a bubble with icons for each of the options available, and then select an item from the bubble. Individually the icons along the top don't actually do anything for me, they all just open this bubble.
Right, which is the normal behaviour - it's when you actually select an icon from that bubble that everything appears to have shifted one position to the left.
Try it at the home screen and then in an application.
Also, looks like data is handled via "Connection.xml" which is placed inside the Windows folder (I'm back to stock 6.1 to check file locations). If I try to put that inside OEMApps or whatever and have that copy over though it doesn't end up in the Windows folder as far as I can tell.
I'm also trying to strip out the more unnecessary stuff, however, the camera always breaks and says the app is missing files to run. I can get rid of the cube, and everything else, but I'd like to leave the camera function behind (strips 30MB off the ROM if I clean everything else out). But the camera doesn't work.
got_milk said:
Right, which is the normal behaviour - it's when you actually select an icon from that bubble that everything appears to have shifted one position to the left.
Try it at the home screen and then in an application.
Also, looks like data is handled via "Connection.xml" which is placed inside the Windows folder (I'm back to stock 6.1 to check file locations). If I try to put that inside OEMApps or whatever and have that copy over though it doesn't end up in the Windows folder as far as I can tell.
I'm also trying to strip out the more unnecessary stuff, however, the camera always breaks and says the app is missing files to run. I can get rid of the cube, and everything else, but I'd like to leave the camera function behind (strips 30MB off the ROM if I clean everything else out). But the camera doesn't work.
Click to expand...
Click to collapse
Ok it seems that you found each other, hopefully it will result in a perfect NEON400 rom, whish you guy's all the best and if I can help, just ask.
Some usefull links:
http://forum.xda-developers.com/showthread.php?t=564130
http://winbreak.com/winmo/voguegoodies/
Greetz,

Categories

Resources