Develop Bugs

Install letter recognizer in a ROM that has it removed

Hi folks,
The rom (Artemis touch 4.0.2) that I have flashed my 3300 is fantastic except for the fact that it doesn't have the letter recognizer as an sip option.
I've searched for a letter recognizer cab and the only links that seem to be the following cabs:
-myprogram.cab (which is supposed to be only for the trinity)
-enableRecognizersNL.CAB
-SIPChange.CAB
-enablerecognizerswwe.cab
All they seem to do is change the registry to default it to the letter recognizer, but it seems that this rom doesn't have it installed at all.
This thread points to this thread which is dead.
I have really gotten used to the letter recognizer.
IMO it is faster and less processor dependant than the transcriber.
Is there an easy way to install this functionality?
Thanks
Laudanum

Nevermind
I ran enablerecognizerswwe.cab again. It seems to have done it.
I'm going to attach the cab so people can find it easier than I did.
sorry folks,
laudanum

+1 Thanks!
Odd that it needs two installs, but it works which is the main thing.
Gone after soft-reset...will keep trying.
Edit:Selectable via QuickMenu (rom is using HTC Touch Input & Swype which stops it appearing in the normal selection for some reason).

Anyone an idea how to save the manilla-player its playlists?

Sugocy said:
Anyone an idea how to save the manilla-player its playlists?
Click to expand...
Click to collapse
Haven't played with the player, I tend to use core player or TCPMP for music. I assume the playlist is kept on soft-reset thus stored somewhere. Try searching for keywords which are in the file names perhaps. Flashing my rom at the moment, but will have a look when I get chance.
HKLM\Software\HTC\Manila\Music\current_playlist_name refers to the name of the selected playlist
HKLM\Software\HTC\Manila\Music\current_playlist gives it an id number i.e. ID1965180
So far unable to find the playlist name or id anywhere else.
Edit: Found it! The playlists are contained within the file below:
Application Data\HTC\AudioManager_Eng\AudioManager_Eng
You can try saving this file and restoring it on a new rom (but you may face issues with different versions of manila). However, perhaps try placing .m3u playlists within the "playlists" folder you never know it may read those too.

[Q] Help with special characters

I saw too many threads, but I dont found any solution.
When I send special characters like, "á,à,é,i,ã,ó,ç", the other phone doesnt see it, or in some cases show garbage. I cant understand it. If someone could help me, I appreciate it.
See the image - i40.tinypic.com/jgqps9.png (I cant put link because of post's limit.)

I had a similar issue both with special characters and other alphabets (Cyrillic one)... In my case it wasn't a problem with my phone but with both service provider (that was strangely resolved very fast) and the recipients phone (which didn't support those characters).
So, have you tried sending this type of messages to other phones and was the result the same?

I send to mate of mine.
My phone - "simão", his phone appears "imo".
Thank you for reply.

I would try to send such a message to some other (models of) phones just to be sure whether this character limitation is imposed by your mobile service provider (which is less probable) or is plain inability of that particular phone you are messaging to encode such special characters...

Impossible to be limitation of my mobile. I have 100% certainty that be ROM's problem. I change it on sunday.
ROM - Runnymede AIO V3.0.5
Last ROM - leedroid. I hadn't any problem until sunday.
I tested swype keyboard, HTC_IME mod, LatinIME. No solution.

Very well then, that clears it up... It could be ROM bound problem... Hopefully you'll solve it by reflashing to another ROM since it appears that your current ROM is faulty in terms of character encoding, it has nothing to do with keyboards...
Although i had run some of the previous versions of the Runnymede AIO and had no problems with texting characters such as č, ć, ž, š etc. Sorry that I can't help you...

While didn't have any solution, I disable special characters (Messages-Settings-SMS-SMS characters-off)
Thank you for all your replys.
Best regards

JJ´s Hybrid 3.3 - Contacs and misc

After lurking for about 3 months on XDA and the Arc forum i finally found the nerve to go beyond just rooting and removing some blotware.
Compared to other hardware, Hifi, PC etc forums I found XDA really difficult as a beginner. There are a lot of guides/tutorials. However they all seem to require a basic understanding of android and the tools surrounding it. Every guide/tutorial I read, always resulted in more questions than answers. I constantly found my knowledge wanting as to fundemental functions of the different tools, drivers etc. Atleast for me, I was long and hard process before I felt comftortable enough to move on.
Anyway I finally found the nerve to unlock my boatloader, install a custom kernel and ROM.
For first time, it went incredible smooth. However I have som questions regarding the JJ hybrid ROM. Since I don´t have +10 posts. I will ask here instead of the developer thread.
- Contacs:
I exported all my contacs to SIM card and imported them again after I was done. However when importing my contacs it seemed to shorten/cut all the names of my contacs.
Is this a problem in this specific ROM or a general issue and what to do about it?
- Trebuchet:
I´m having some problems using some of the features in Trebuchet. I would really like to change the icons and increase the dock size to include more shortcuts. However nothing happens when I press the "Icon" and "Dock" under the Trebuchet menu.
Are those two functions just not working or is it a problem on my end?
Generally I find Trebuchet a little wanting in features compared to GoLauncher I was using before. Is it possible to install another launcher or will it mess up the ROM?
- Camera:
As far as I can tell the are no tweaks in JJ´s ROM to improve the camera/post picture processing and hence increase the image quality. Is there any ROM where this is included?
I think that was it for now. However, I´m sure more questions will follow as I dig deeper in to this ROM.
Thank you in advance.

I don't know about the rest but regarding your contacts, you should have exported them to your memory card instead of the SIM.
Saving numbers to the SIM is really outdated. You'd probably be able to save a maximum of 250 contacts i.e. One contact with a single number. I believe the name field is limited to 8 or 16 characters, so anything longer would be cut short. If you had two numbers for a contact, it would be saved as 2 separate entries.
This is not a limitation of the ROM but of the SIM card. And unfortunately, there's no way of retrieving all your contacts and numbers unless you had them synced with the Google servers.

[Q] Question on [ROM][Cool Sense][5 April]Cool Droid v3|2.3.4|FASTEST|Data++/Stock

First of all I want to thank everybody whos making efforts so that our beloved Desire survive through out these years!!
I am a Desire owner for more than three years and I could say that I have tried nearly anything on my device.
Currently I am using this Rom with the exactly configuration written by the user.
As the user Tonyp has written in the post, that exact setup is working really good and without any major issues. I have only 3 spots that i would like to point out:
1st When I am call directly from the address book a contact that is stored without the national prefix (+30 Greece) the phone adds automatically the prefix +1 (maybe US I don't really know), so this make the call goes wrong.
2nd From Optimo Settings (included in the Rom) I don't have the choise to dissapear the battery icon and leavy only the numbers.
3rd As it already pointed out, in the Rosie Options, the right button choise for the shortcut isn't working if you select anything else bit the internet browser.
I would really like to hear your thoughts about the things that i've pointed out before, and again to thank everyone that is contributing to the development of our device!!

As an addition to the previous post I have found out that some appz that they use the google account to log in such as youtube and quicktime, they sign in feature doesn't work, although I have install the latest google play services and the syncing of the google account works fine.
Thanks in advance and please if some wants to copy my 2 posts to the development thread, be my guest!!!

[Q] Contacts not recognized when first name contains Umlaut (ä, ö, ü) or ß

Hi,
if you want to phone somebody - let's call him Jochen Altmann - you can dial J-O-C... (5-6-2...) and the contacts get checked for matches. The more letters you type, the less possible hits are displayed. This also works when you start by typing the last name A-L-T...
Strangely, this does not work if the first name contains an Umlaut (ä, ö, ü) or a German ß. If that is the case, the contact won't be displayed. E.g. if I wanted to call 'Jürgen Altmann', neither typing J-Ü-R... (5-8-7...) nor A-L-T... makes the contact show up. The contact is totally ignored, as if it didn't exist.
This problem does NOT appear, if only the LAST name contains ä, ö, ü or ß.
Also, the problem does NOT appear, if the first name contains any other special letter like é.
The problem seems to affect a number of people, not only my phone. And it seems to be a Fairphone issue, not an Android issue.
Any solution available?
Best,
smartn

Hi,
smartn said:
Hi,
if you want to phone somebody - let's call him Jochen Altmann - you can dial J-O-C... (5-6-2...) and the contacts get checked for matches. The more letters you type, the less possible hits are displayed. This also works when you start by typing the last name A-L-T...
Strangely, this does not work if the first name contains an Umlaut (ä, ö, ü) or a German ß. If that is the case, the contact won't be displayed. E.g. if I wanted to call 'Jürgen Altmann', neither typing J-Ü-R... (5-8-7...) nor A-L-T... makes the contact show up. The contact is totally ignored, as if it didn't exist.
This problem does NOT appear, if only the LAST name contains ä, ö, ü or ß.
Also, the problem does NOT appear, if the first name contains any other special letter like é.
The problem seems to affect a number of people, not only my phone. And it seems to be a Fairphone issue, not an Android issue.
Any solution available?
Best,
smartn
Click to expand...
Click to collapse
This is really an Android problem. Also because the search only matches the begin of a word you can not search for "rgen" for example.

_keesj said:
Hi,
This is really an Android problem. Also because the search only matches the begin of a word you can not search for "rgen" for example.
Click to expand...
Click to collapse
1. No, as stated before, this is NOT an Android problem - it did not occur on other Android 4.2.2 mobiles that I've tried.
2. You're right, the search term has to match the beginning of a word. But this is the way it works, no matter what specific letters the search term contains, so it's not a bug but the way it's meant to be.

Hello
smartn said:
1. No, as stated before, this is NOT an Android problem - it did not occur on other Android 4.2.2 mobiles that I've tried.
2. You're right, the search term has to match the beginning of a word. But this is the way it works, no matter what specific letters the search term contains, so it's not a bug but the way it's meant to be.
Click to expand...
Click to collapse
I did not look at the code I tried entering a few name containing special chars and once I was able to reproduce the problem searched the web for an answer:
I found the following thread from 2009!
https://code.google.com/p/android/issues/detail?id=3732

Thanks for your effort, _keesje, but after flying over a good portion of the 235 entries on the website which you linked, it seems to me as if they were dealing with another bug in the search function: the problem that a contact search is only limited to the names, so you can't search by company etc.
Surely a problem worth mentioning, but not the least helpful in the matter I'm dealing with - or did I miss anything? If so, please provide the number of the entry.
smartn

In the meantime, Fairphone has replied to my direct request:
"Thank you for your email. Our development team is aware of this issue, and we hope to include a fix the future update.
Cheers,
Rick"
I hope so, too.
But meanwhile, I'm still thankful for any other approach...