Related
I'm very sorry to ask this question as it has been asked so many times before.
All the forums that I found from searching were people saying that they found bluetooth stack patches and then a great deal of arguement if those patches worked or not.
I have 2 simple questions: (not yelling just for attention)
1) HAS ANYONE GOTTEN THE BLUE ANGEL TO WORK DEPENDABLY WITH A BLUETOOTH HEADSET?
2) HOW?
Headset make/model, stack update + link, ROM update, anything and everything on your divice that makes it work.
Let's try to keep this simple - if your answer to #1 is "no" then don't reply. I'm really not trying to be rude, but I've been trying for hours to figure this out and the forums that I have found are too full of "trying this and that might work" type statements that I figure that there are people other than myself who also need a quick and easy solution to these questions without all the discussion.
Thnx (if there are any replies)
:roll:
Read the solution to my problems with bluetooth on here http://forum.xda-developers.com/viewtopic.php?t=13590&start=25
Thanks for trying, but no use.
Does yours really "work", or is it just tolerable?
Anyone else?
because not here???
can you compress it and to ascend??
Greetings
I leave you my msn, [email protected]
we connect ourselves and I give you a ftp
greetings
Must admit to being suprised not to find a thread about this. Apparently this is possible with the Kaiser, but has anyone released a CAB to activate it yet?
(While I'm at it a VoIP Dial Plan wizard is also a sorely missed feature from all WM6 devices - wink wink )
Anyone?
Any news on this.... I'm very interested!
Lookat this thread:
http://forum.xda-developers.com/showthread.php?t=348000&highlight=VoIP
As I understood it's not possible to use VoIP with the front speaker, only rear speaker or headset.
Greetz,
Hans Olo
EDIT: In the last posts of the linked thread it's mentioned that it will work with one of dutty's ROMs...
The way I read it that thread says the opposite - it says it is working in the Kaiser. I also read elsewhere that the Kaiser hardware will allow it, whilst older phones like the Wizard would not.
I have now pledged money to the first developer to fix it:
http://forum.xda-developers.com/showthread.php?t=355062&goto=newpost
Have you still got your money? (Im hoping that someone has provided the goods)
Ifso, please let me know!
Subscribe to the other thread to find out when someone delivers the fix.
I have owned my Tilt for about 7 months and have always stuck with the stock ROMs. Extremely poor signal strength in my area has led me to try new radios, which, basically, entailed that I go all in on the ROMs. Ultimately, I had to revert to the current WM6.0 AT&T Stock ROM because there were just too many problems.
I have been with XDA Developers a long time, and find it invaluable. I have also found that it now the new trend to flame rather than answer. Bottom line, it IS possible to search and not find; and, regardless, 103 page posts are not going to be of any use to anyone. Its unfortunate.
So this message is really for those who control the Wiki and for those who control Post # 1 in their threads. There is so much information I could have used which might have made my transition a success. I provide this info in hopes that each individual in possession of editing ability might consider updating their threads.
1) HardSPL - Jaberwok has a solution for the White Screen. One of the MIDDLE powered-on steps is to remove your SIM and SD Cards. It is not possible on a Tilt (at least) to remove the sim while the unit is on. I would respectfully as that Jaberwok update his Page 1 to clarify when the SIM Card should be removed. As a note, the problem is that if you unlock the sim card slot the unit freezes and tells you it will reboot when you lock it. If you leave it unlocked the unit wont boot. If there the SIM card really needs to be out, it would be great if the instructions were reshuffled so that they don't give the impression that the SIM card is to be removed from any state other than a power off, with the door of the empty chamber locked.
2) AT&T Settings - I had decided to settle on Dutty's WM6.1 Hybrid ROM as it seemed to be one of the newer ones. The AT&T connectivity customization which runs was not correct (for the United States at least). The web might connect ok via MEdia Net, but nothing else would - preferring to go to ISP (which had isp.cingular). Attempting to change these settings to mirror the Stock AT&T settings did not provide any relief. There was no way to check messages. Perhaps part of the Wiki could explain how to take anyone's custom ROM, and get it to work on the AT&T network. Checking messages would result in a "dialing error" (no matter whether the advanced connection settings were set to MEdia Net for all uses, or the values were changed to mirror the wap.cingular settings).
3) Diamond - The master ROM sticky from the Wiki is a great resource. I was afraid to try Dutty's Diamond ROM because I had no idea if Diamond was a new phone, which would then cause me to brick mine.
4) Hard Resets - All of the installation instructions, whether on the individual cooker's Post 1, or in the Rom Wiki, are fairly inconsistent on when a Hard Reset is needed. Many posts on the forum indicate Problem X -> oh did you hard reset -> yeah that worked. An example of the vagueness is: Should I hard reset before I flash HardSPL? before I flash a Radio? before a flash a ROM? and then all of the above but using "after". Unless you are a cook, cooking your favorite apps into a rom, a Hard Reset is an awful bitter pill. If there are steps which do not require a Hard Reset, it would be of great benefit to know those.
5) Radio - Would love to know if I can flash a radio without a Hard Reset afterwards. Would also love to know if I can flash a radio into the stock AT&T ROM.
6) HardSPL Post 1 - Would love to see a line about whether you need to do anything different if you already have a different HardSPL installed.
Anyway, these are the questions which I believe would be wonderful additions to the various wiki posts, etc. While I anticipate the necessary flames (gotta keep those post counts up, I guess), I believe anyone in control of these threads will note these omissions. I ask that THOSE people understand that everyone is new at flashing at least once, regardless of how experienced they are, and these omissions have tangled at least one poor soul up.
Of course, if anyone out there is also honestly willing to help with the underlying problem, I would love for some help ... I just want to get the best radio I can on my phone. If there is a ROM out there which is right for the AT&T Tilt (meaning, the AT&T connectivity settings are correct, and the keyboard is properly mapped), which has a better radio, I would dearly love to know about it.
Thanks for reading.
Re Hard resets.
Most cooked roms require you to do an additional hard reset after the device has been flashed and restarted.
This is simply something that people have learnt from experience.
The only other times you hard reset after:
1) Phone simply won't respond after trying everything
2) You've installed something and it has screwed your settings beyond any chance of recovery
3) Your rom has got cluttered after loads of installs and uninstalls... and you need to "clean" your rom but still want to keep the same one.
(But I agree that "first post" maintenance would be really handy - but the rom chefs are busy cooking - someone else should volunteer to update their first three posts.
OK But to Start all my answers were learned FROM reading and searching. Just FYI.
1) I can't really answer this. I didn't have the write screen problem.
2) If I recall correctly just about the majority of people here use MEdiaNet for their connection. There are a couple people I remember saying that they use the ISP, and they just simply changed the setting manually. If you get it to work, I'd be happy to help you create a CAB for it.
3) Rest assured that even though the Diamond is a new phone if the ROM is posted in the Kaiser Forum. Its "ok to use it on your phone. If you are worried you can wait until a couple people try it and say "This Works great" Then you can look at their signature and see they are using a Kaiser.
4) The most common answer it After a ROM flash right at when you See the "Tap to Begin" Screen.
5) I never Hard Reset after I flash a radio. I flash so much though. People recommend you flash the radio first, I've done it both ways. I Personally don't notice a difference. Questions about What radio will work with Stock AT&T ROMs, Which I believe are still WM 6.0, are toroughly answered in AllTheWays Ultimate radio Thread.
6) That would be nice. Would get more notice by the Ones in the KNow about those things if this qustion was posting in that specific thread.
7) Anyone should feel free to edit and add to the WIKI.
8) IIRC shogunmark's Death is an AT&T Tilt based ROM. But the Tytn II based Roms work fine on the Tilt. You just have to install the Tilt Keyboard Fix and Soft Reset.
jdmba said:
I have been with XDA Developers a long time, and find it invaluable. I have also found that it now the new trend to flame rather than answer. Bottom line, it IS possible to search and not find; and, regardless, 103 page posts are not going to be of any use to anyone. Its unfortunate.
Click to expand...
Click to collapse
I too have been a Tilt owner for 8 months, first came across this site last Nov. At that point, the Kaiser forum consisted of speculation on when the Tilt would appear in the US. I was a lurker for 6 months before I joined and posted my first question. Until then I searched ( Forum and Google ) for all my info and never, I mean never did I not find an answer to my questions.
Yes it took time and perseverance but the information was ALWAYS there.I will steadfastly stand here and argue with anyone who says " I searched and found nothing " and tell them " you searched, got bored, it was too much trouble, and you wanted instant gratification ", that is why you are posting. ( Except genuine questions on newly released items ).
That is the real reason why it is so difficult to search. Redundant posts and lazy people who think their time is too valuable to search. Want an example?
JimmyMcGee, over 1000 posts, 0 new threads
Harkadenn, 330 posts over forty new threads, 36 in one month alone, before he finally sold his phone. He had a problem, started a thread
One person, multiply that times 1000 people who think that we should just answer their questions as they come up, and not flame them to search.
I will do the math, 36000 new threads per month, you think it is impossible to search through crap now? It was not always like this, it was made like this.
So this message is really for those who control the Wiki and for those who control Post # 1 in their threads. There is so much information I could have used which might have made my transition a success. I provide this info in hopes that each individual in possession of editing ability might consider updating their threads.
Click to expand...
Click to collapse
Everyone has the ability to edit the Wiki. The information in this site evolves. ( see the new info about how different Spls affect your phone)The problem with the Wiki is that the people with the info mostly don't use it, the people looking for info do. Do not leave it up to everyone else. Every member has the ability and thus the responsibility to correct or update any information they feel is wrong or misguiding in the Wiki.
Anyway, these are the questions which I believe would be wonderful additions to the various wiki posts, etc. While I anticipate the necessary flames (gotta keep those post counts up, I guess), I believe anyone in control of these threads will note these omissions. I ask that THOSE people understand that everyone is new at flashing at least once, regardless of how experienced they are, and these omissions have tangled at least one poor soul up.
Click to expand...
Click to collapse
Yes we were all new at one time. Many of us searched (eight months, 200 posts, 2 new threads ) any too many didn't ( which is why we are talking about this ) . But don't blame the people flaming redundant thread starters( the people padding their post counts as you put it ). The remedy starts with you and me.
Now take the answers you get in this thread and add them to the Wiki for all others.
Hi guys/
Been reading your site for a while now and thought I'd try my hand at re-flashing my old tytn ii with a new windows mobile 6.5 rom to take advantage of new features and speed, etc.
I followed your noob guide and all seemed to go well until I started playing about with it and realised that that the sound was not working....
I have the volume set to normal, but nothing seems to actually make any sound. Not ringtones, not music, not notifications, not alarms, nothing.
Does anyone have any ideas what could have done this and a possible solution?
I used the following rom:
2010-03-08 ROM 3.34.721.5 -KAISER CE OS 5.2.21895 PVthread Build:21895.5.0.90
Any help would be appreciated.
Thanks in advance
slick
Same thing happened to me. All you need is the right radio for the audio to work. Unfortunately I'm unable to post you the link to the radios since i'm a new member.
But you can find it by googling "kaiser radio xda" click the first link and when you get to the next page click the link that the original poster posted. There you will find the radios.
Good Luck Man
Of course a simple search or follow the "you must check the Sitckies and Wickies" part of the forum rules would have given you the link and the info.
Got the radio working now. Thanks for the help.
But it still seems to be riddled with problems. It is bone slow, a lot of programs stop working suddenly for no reason and every time I soft reset the phone, it has the effect of a hard reset and wipes all my data.
I don't think my tytn ii can handle 6.5....I will go back to 6.1
on the contrary, the tytn2 can handle the ROMs cooked for it just fine including the WM6.5(.x) ones. its just that YOU, the user, cannot handle the concept of reading the wiki and FAQs of the ROM you are flashing before attempting the flash. hard reset after soft reset is a common problem and the solution is simpler than you think and is detailed in nearly all the FAQs of nearly all the WM6.5(.x) ROMs for the kaiser.
its just sad how many threads people start here about painfully common and well investigated issues without bothering to do any reading. in the end, it just clutters up the forum and erodes the whole concept of a forum which has just the following basic rules IMHO:
"read and search and read and search before doing anything with your expensive device. in case of a problem, read and search and read and search some more before starting a new thread and/or asking a question. respect others (don't treat them like your own personal tech support) and don't post warez/illegal software."
simple eh? i know you're a noob and i'm sorry to sound so harsh but its the bitter truth. please go ahead and read the stickies and the wiki and the FAQs next time. 'nuff said...
I bought this phone after careful research. I found out that the Voice Command could be downloaded. Then I found out that it might not work. Then I found out if could if I just had the right CAB. Then I found my way here. Now I have read and read for the last two weeks when ever possible and some times for over 8 hours. Here is where I am and I would love some help. I am up against a time frame that is un-movable at this point. Here I am copying and pasting:
I have read a ton of stuff and what I finally have come to is that the CAB to operate and download the BTAG is available and I found it. It is with, this, http://forum.xda-developers.com/showthread.php?t=588882 I just don't know if I have to do a hard SPL or a Soft and or if I do one where to find the directions. I have read a ton of directions but it is not clear if they are necessary for this CAB and the CAB I believe is with Windows 6.5. I have 6.1. So if anyone can answer my questions it would be really wonderful....
should be closed by me for being duplicate...but I will leave it for this time so you can get your phone in gear, but in the future pls refrain from double posting/redundant thread opening, thx
I will also move the thread to general, it is not dev related
I already posted in backup thread, to add info on your h-spl question:
for cabs you don't need h-spl, that's only required for stock roms
so if this cab is only working on 6.5 you would need h-spl to get a 6.5 custom rom on your phone, but only for that
best
I appreciate your leaving it for me. You are obviously not used to working with newer people though. I posted the cab link so that it could be seen in order to ask the question. I am also packing, washing clothes, have my other phone listed on eBay, getting things ready for my garage sale, trying to be quiet while my boyfriend sleeps, feeding the dogs, trying not to upset them.....
In between that read any responses so that I know how to answer the offer on my other phone that I have listed on eBay. Download a backup for the Xperia so that I can load the CAB and if it doesn't work I can restore the backup....
Basically, I am trying to do a lot of things at once. That is why I am trying to cover everything in my posts. I have very limited time.
So, again thanks, I am still unclear as to whether or not this cab that is 6.5 or at least that is the ROM that it is in. I think, I am not very experienced in this.... ergo the link to his info. Back to what I said, I still am not clear on if it will work or I have wasted even more time??
I'm used to, nearly daily, but I don't like them posting all over the forum, especially not doing duplicates or starting new threads for anything
I understand your need but still: there are rules and they apply to everyone here, independent of them being in a hurry or not, having to do a lot of other things in parallel or not,...
I'm sure you noticed and read them during your research here, so pls abide by them
I am not quite sure what your post is even about - too much info all piled and mixed together. If you want an answer, you need to ask a question properly. So what is it that you need to know?
If any .CABs don't work, they can be uninstalled, no need to back up, restore and/or flash the entire phone just to get rid of the unworking .CABs
As far as Voice Command is concerned, I have it running on my X1 and it should run regardless of the ROM you have. I tried versions 1.6.0, 1.6.2 etc - all worked fine. The only difficulty is mapping the buttons with X1. I would recommend mapping left soft key, simply because I have the necessary functions on the screen, so didn't need a soft key to repeat the same, making the key reduntant and available for MS VC.
As far as ROM flashing is concerned, there is an excellent guide for flashing, just look for recommended stickies in ROM Development, but first it feels you are not really up to speed with the terminology - CABs, ROMs etc.
Mod, actually when I have so much to do, even though I read a lot of stuff I have not really completely become familiar with this site. If I had read that I certainly would not have posted it twice. That is why I did not PM the OP of the ROM that I have been referring to. Because what I did read was that no body wanted a lot of questions asked without someone reading.
As to the person who posted about my lingo. Thanks for your comments. I tried finding the folder for the cab on my phone. It is a new phone. Could not find it. Not sure what app it is in. I am familiar with my old phone. This is the 2nd of this one I have had to order now and the first one had so much wrong with it. I spent about a week alone just figuring out that that phone was definitely a lemon. The seller on eBay was not being truthful to me about it. That is a question I asked just recently.
.CABs are small installable programs, in order to have them on your phone, they need to be placed there by you, either to the phone itself or to the storage card, then you can install the program by clicking on the .CAB. There is no folder for the .CAB or app it can be in if you didn't have it placed there to begin with. Again, as I suspect, you are not quite familiar with terminology, you are using the right terms but in the wrong context somehow.
Not sure what you were looking for and not finding on your phone. Again, your descriptions make no sense. Just because you can't find the .CAB you never placed on the phone, doesn't make a phone a lemon, rather you having no idea how to use a phone or how to install anything on it in order for you to be able to use it.
No, I know that does not make a phone a lemon. It's a really long story. Just wanted to thank you for coming back and leaving me a more detailed answer. I am not stupid, I just have way too much too do and limited time so it is a combination of that and not enough sleep and trying to move internationally in 3 days. Thanks again!
Okay, I got it on my phone. But I can't get the bluetooth heaset to work. I read in many different places about assigning a button. I did that. I also say about doing a soft reset. I did that. I don't want to do either of those again for fear that I will loose everything I have at this point. Pleae anyone.....
You need to go to settings, open Voice Command and tick the appropriate option to use bluetooth with it.
Unless, of course, you are talking about general bluetooth connection. In which case i suggest you get settled, give yourself time and have a good read of the instruction booklet, section discussing bluetooth connection.
There are a whole bunch of choices. I am using a plantronics PRO and I saw the information about A2DP. So I tried that and it did not work....
beachinmoney said:
There are a whole bunch of choices. I am using a plantronics PRO and I saw the information about A2DP. So I tried that and it did not work....
Click to expand...
Click to collapse
what didn't work, your headset or A2DP? A2DP is a stereo format for stereo headsets and headphones. Is your headset stereo?