Recently in most of the roms i tried, the language was set to "hd" no matter what i select during initial setup or in settings. This also had numerous effects on google navigation and keyboard prediction wouldn't work as it should (since hd is no language).
After some investigation, most of the ROMs contain the following line in their build.prop:
ro.product.locale.language=hdpi
Since language is a 2 char code, android must have been setting it to "hd"
setting that line to
ro.product.locale.language=en
or deleting it completely fixed the issue for me.
And yeah, i assumed [Fixes] are supposed to be posted here
Rick_1995 said:
Recently in most of the roms i tried, the language was set to "hd" no matter what i select during initial setup or in settings. This also had numerous effects on google navigation and keyboard prediction wouldn't work as it should (since hd is no language).
After some investigation, most of the ROMs contain the following line in their build.prop:
ro.product.locale.language=hdpi
Since language is a 2 char code, android must have been setting it to "hd"
setting that line to
ro.product.locale.language=en
or deleting it completely fixed the issue for me.
And yeah, i assumed [Fixes] are supposed to be posted here
Click to expand...
Click to collapse
I know that....have read that some time ago on another forums when trying to optimize ROM settings...and it is already set in my ROM
Related
AppFinder update is in the marketplace!
v1.1 includes a Hot list, New list and Best list. Apps can be filtered to show only free apps.
The apps list shows developer, price, ratings and rank. The lists show the top 1000 apps in each category making browsing hot, new and best apps simple and fast.
When selecting an app from the list, pressing back from the marketplace page will return you to where you were in the app list.
As usual, the app list is displayed nearly instantly as you type, and in the app list there is no waiting for additional results to load as you scroll through the results.
Images are NOT included - I wanted to keep the display and information access absolutely as quick as possible and have traded off loading images.
Please give it a try and let me know what you think
Very nice. Runs smooth and results are displayed quickly. Nicely done. I've rated and reviewed for you too.
Only extra thing that i'd like to see (don't know if it's possible) would be a "highest rated" list that shows apps sorted by rating highest to lowest.
The "best" apps list attempts to order by highest rated.
The main problem is that a 5 star app with 1 rating probably should not out rank a 4 star app with 20 ratings. Best apps uses an algorithm to order apps based on the star rating and rating count.
Hi ebadger,
After this update I don't get any search box. When I start the app I first see a triangle for a second, then I see the search box flash for a split sec. After that I just see a black screen with 6 blinking white dots, like if it is loading. I see the menu too, but it does not matter what ever I choose.
I'm on a Samsung Omnia 7.
Best regards
kjw
do you see anything? the dots should only show while the local data structure is being populated. This should only take a few seconds. Once this completes, you should be able to press on the flames button and see a list of apps. Is this not working?
If not, try uninstalling and reinstalling - sorry for any inconvenience - I can make this more robust to data errors. I'm wondering if perhaps the download is interrupted or corrupted.
ack!
Ok, so it turns out that the behavior of float.Parse is different with German locale.
I just booted my device with German UI language and I can repro in the debugger - luckily it can be fixed with a data update.
I have now updated the data file. Unfortunately you will have to uninstall and reinstall to make it work.
I was trimming leading 0's on prices (i.e. sending .99 instead of 0.99) float.Parse works in English but not in German. Anyway, leading zeros are back.
I'm really sorry for the inconvenience to the German users!
works better and hasn't crashed on me so I will edit my prev. ranking and give it 5 stars. Works great.
ebadger said:
ack!
..
I'm really sorry for the inconvenience to the German users!
Click to expand...
Click to collapse
First of all I did a reisntall of appfinder.
Then I tried to switch to english locale and now appfinder started to work!
But when switching back to Swedish (since I live in Sweden) locale appfinder hangs on the loading dots screen.
So there might be issues with other locales too?
Cheers
kjw
kjw said:
First of all I did a reisntall of appfinder.
Then I tried to switch to english locale and now appfinder started to work!
But when switching back to Swedish (since I live in Sweden) locale appfinder hangs on the loading dots screen.
So there might be issues with other locales too?
Cheers
kjw
Click to expand...
Click to collapse
I think so. I have also seen reports of this problem with French now as well.
I have updated the data file. Would you try uninstalling and reinstalling again and see if it's working with your locale?
ebadger said:
I think so. I have also seen reports of this problem with French now as well.
I have updated the data file. Would you try uninstalling and reinstalling again and see if it's working with your locale?
Click to expand...
Click to collapse
Uninstalled, restarted, installed. But it's a no go, sorry. Same dots...
Have you tried debugging in other locales (swedish for example)?
Cheers
Kjw
crud.
Ok, so there is definitely still an issue.
Any locale that uses the "," as a decimal seperator will cause an exception while loading.
I am converting the data to use scientific notation to work around -- the fix will be a little bit tricky. I think you'll have to switch your locale to english for the first boot - once the updated data file has been downloaded you can switch back to swedish and it should work. ugh!
Well, it looks like I definitely need to do another update to fix this particular problem.
Uninstalled, switch to english locale -> reboot, install. Now appfinder works great.
Switch to swedish locale -> reboot. Now I'm back to the loading dots in Appfinder, not working.
I don't really know what you are doing in the app that is locale dependant, but maybe it could be done in a more generic way? Like convert locale dependent data to english format, do your thing, and then convert back to current locale settings. And try to avoid converting different datatypes to text if it's not relly needed, a decimal variable is not locale dependant until converted to text... Just a thought...
Thanks for your effort, though!
Cheers
kjw,
Ok, I have been debugging in Swedish today. I have updated the data file such that it doesn't use the locale specific delimiter for floating points. I have converted the data over to use scientific notation instead. It's really a simple code fix as I can specify the locale settings to use when parsing - my mistake. I have confirmed that with the new data format (just uploaded), the steps:
1) uninstall
2) switch to English locale
3) run appfinder - wait for the dots
4) wait for the dots again
5) switch locale to Swedish forcing reboot
6) launch AppFinder
this will fix it such that it should just work with Swedish locale.
I'm sorry about the inconvenience - I'm working on an update now to fix this and other issues.
Eric
After following your steps it works in swedish locale!
Great work!
Thanks,
kjw
ROMs affected for sure: iNsertCoin v2.0.0 and RCMixHD v3.5 (both A2SD)
Whenever I type in characters in HTC Dialer to search for a name (e.g. 846 for contacts named 'Tim') the first number gets ignored, resulting in search results starting with characters represented by the numbers '46', e.g. 'Ho...'.
Similarly, when I try to access the test screen via *#*#4636#*#*, the first character '*' gets ignored (it even disappears after putting in the first '#').
If I put in something, then remove it with backspace and start over, it does work.
Don't think it's relevant, but Baseband version is 32.49.00.32U_5.11.05.27.
What is happening here? Tried setting different locale in settings, different keyboards, no change. Thanks in advance.
Ok second post now. Maybe your phone is a little nakered, rom broke a little. It seems your just getting software errors which happen when you flash custom roms.
Posted this here in Q&A after iNsertCoin developer suggested me to do so. He heard of this problem before, but had no solution. Hopefully other ppl have found one, but an extensive search both here and on other forums did not give any result.
Solved
After (quite!) some more research, I've found a similar problem described in the topics below. The presented fix there also solved my problem (see quote):
With great help of some participants of xda forum a workaround for this issue has been found: just remove the dialer shortcut from the dock (set it to "blank") and then add it back in (a shortcut to "Phone" app). This will fix the problem.
Apparently, people who are not experiencing the issue are the people who already recreated their dialer shortcut while customizing the dock. Meanwhile, people who keep the initial dock (or, more precisely, the initial dialer shortcut) all experience this problem. The problem is not limited to Plus version - a plain LaucherPro has it as well.
It looks like LauncherPro, as shipped, uses some unorthodox way to launch the dialer (I wonder why), which is what's causing the latter to act up. Recreating it as an ordinary app shortcut fixes the problem.
Click to expand...
Click to collapse
Sources:
http://www.launcherpro.com/forum/viewtopic.php?f=14&t=5884
http://forum.xda-developers.com/showpost.php?p=10490200&postcount=15
I have tried several different keyboards that include spellcheckers and have been unable to see predictions and spelling suggestions. Since the Nook was not sold as a full android device it's very possible B&N left the necessary files out of the system. Can someone here let me know what files I would need to add to be able to use the spell check function? I've tried with several different keyboards and have installed their respective dictionaries so I believe it's not an app issue but a system issue. Thanks again everybody. Ryan
I installed SlideIt and found that word prediction works. try it. Note: I copied the apk to /system/app and used NookColor Tools to select SlideIT as my keyboard. I then had to actually execute and install the APK in order for it to show up. Once done, it works well. It takes up 1/2 of the screen, though.
Thanks I'll give it a try. I'm not sure if I was clear in my original post so let me try again. I am referring to the circled box where spelling suggestions are offered. I am unable to see the box.
Another way to do this:
- install the keyboard with ADB (and its required dictionaries),
- push all the installed APKs to the /system/app folder,
- change the APKs permissions to 644 (via shell/Root explorer/etc').
- reboot the phone, and select the keyboard through the NookColor tools.
I believe what Ryan mean is there is no word suggestion box on any keyboards installed on the nook ST. This breaks functionality of ALL 9 key keyboards and most language IME keyboards. Is there any way to restore this keyboard functionality? I also have the same problem. No keyboards which require that bar (highlighted in his attachment image) work.
I've tried:
Sougou tablet
Sougou phone
Baidu phone
Smart keyboard plus chinese
etc.
None of them display the spelling selection or character selection boxes, so this appears to be a problem with the android.
Known issue, predictions are there, however not appear. SlideIt works, but it sucks. The best keyboard, which works, is Jelly Bean Keyboard. As always you have to copy it to system/app
NookSimpleTouch/Tapatalk 2
domi.nos said:
Known issue, predictions are there, however not appear. SlideIt works, but it sucks. The best keyboard, which works, is Jelly Bean Keyboard. As always you have to copy it to system/app
NookSimpleTouch/Tapatalk 2
Click to expand...
Click to collapse
Thanks, it appears the only keyboards that were are back-ports of ICS and jelly bean. Possibly this is due to them including necessary dependencies that are not included on the nook? It would be great if someone could isolate the problem and make a patch.
I know it should be the same and we can call it voice action or voice search
but I tryed for example to set the timer and when I say " set timer for 10 minutes " it poped up the google seach and while it should set the alarm
am I missing something here or there a way to do that
I am on MoDaCo rom
It just worked for me by saying set alarm for 8am.
Most Voice Actions don't seem to work unless you have both the phone and voice language settings set to English(US).
Setting the alarm was definitely one of the ones which doesn't work if you're using another language.
Annoying as ****, and I wish Google would fix it. I don't know how they can claim to have launched voice actions in other countries when these basic things don't work. So now I have to put on a faux American accent while talking to my phone!
How are your Elvis impressions?
yes man you are right, finally got it worked:good:
I totally agree with you and hoping this got fixed soon
thanks brother
GodEater said:
Annoying as ****, and I wish Google would fix it. I don't know how they can claim to have launched voice actions in other countries when these basic things don't work. So now I have to put on a faux American accent while talking to my phone!
Click to expand...
Click to collapse
You may be right, but please don't forget that the version we are running is still nothing but a developers *preview* which has not been intended to be supplied to Non-US users to start with.
I am quite confident that by the time Google releases the final version in mid July, the will have implemented voice action- and also cards-support for other languages as well.
Cheers
CT
In my case I didn't need both set to English (US) to work.. following works for me:
OS level - Settings > Language & input > Language = English (US)
Google Now - Settings > Voice > Language = English (Australia)
*confirmed*
Thanks for the tip! I was trying to find a solution for an hour. I have 2 phones running Android 4.2, and I was wondering why one of them will set the timer and alarm correctly, while the other 1 will not. So this is confirmed: you DO need to set both the phone language and voice action language to English (US) for all voice actions to work.
I noticed that the previously used forum font (Open Sans) is somewhat gone in the whole forum since yesterday, instead Arial is used as the built-in fallback font. I had a quick look into the HTML and noticed that the font could get imported at two places, but both are commented out.
(Line numbers are taken from the main page, forum.xda-developers.com)
First part: Line 132
HTML:
<!-- <link href="//fonts.googleapis.com/css?family=Open+Sans:400,600|Hind:400,600,500|Titillium+Web:200,400,300italic,300,400italic,700,700italic" rel="stylesheet" type="text/css"> -->
Commented out.
Second part: A stylesheet.
HTML:
/* XDA Developers 2015 Theme CSS
Generated 05-25-2016 @ 00:24:25 */
/*!
* //fonts.googleapis.com/css?family=Open+Sans:400,600|Hind:400,600,500|Titillium+Web:200,400,300italic,300,400italic,700,700italic
* document here when changing fonts
...
Everything commented out.
I guess it's a bug, and I'm surprised that nobody else noticed it / seems to have it. Arial as the forum font looks ugly as hell.
MrWasdennnoch said:
I noticed that the previously used forum font (Open Sans) is somewhat gone in the whole forum since yesterday, instead Arial is used as the built-in fallback font. I had a quick look into the HTML and noticed that the font could get imported at two places, but both are commented out.
(Line numbers are taken from the main page, forum.xda-developers.com)
First part: Line 132
HTML:
<!-- <link href="//fonts.googleapis.com/css?family=Open+Sans:400,600|Hind:400,600,500|Titillium+Web:200,400,300italic,300,400italic,700,700italic" rel="stylesheet" type="text/css"> -->
Commented out.
Second part: A stylesheet.
HTML:
/* XDA Developers 2015 Theme CSS
Generated 05-25-2016 @ 00:24:25 */
/*!
* //fonts.googleapis.com/css?family=Open+Sans:400,600|Hind:400,600,500|Titillium+Web:200,400,300italic,300,400italic,700,700italic
* document here when changing fonts
...
Everything commented out.
I guess it's a bug, and I'm surprised that nobody else noticed it / seems to have it. Arial as the forum font looks ugly as hell.
Click to expand...
Click to collapse
Working on some site speed enhancements, the relevant part to load the web fonts is not commented out, it comes immediately after the part of the code you quoted Try a hard refresh (CTRL-F5) to be sure.
webworker01 said:
Working on some site speed enhancements, the relevant part to load the web fonts is not commented out, it comes immediately after the part of the code you quoted Try a hard refresh (CTRL-F5) to be sure.
Click to expand...
Click to collapse
Had another look; that's some horrible comment formatting. The fonts "Hind" and "FontAwesome" are being loaded properly as they are not commented out, but the Open Sans font only exists as a commented link without @font-face and all that stuff.
Hard refresh didn't work, and the browser console revealed that there is indeed no Open Sans being loaded. Uncommenting the link tag on the main page (obviously) solved the font problem.
MrWasdennnoch said:
Had another look; that's some horrible comment formatting. The fonts "Hind" and "FontAwesome" are being loaded properly as they are not commented out, but the Open Sans font only exists as a commented link without @font-face and all that stuff.
Hard refresh didn't work, and the browser console revealed that there is indeed no Open Sans being loaded. Uncommenting the link tag on the main page (obviously) solved the font problem.
Click to expand...
Click to collapse
Obviously we're not writing our source code like that and we compress the final output :good:
Attached screenshot reveals Open Sans being loaded and I've tried it out on many browsers. Maybe there's a browser or OS compatibility issue I can look at if you send over those details.
EDIT: I see the problem you're having might be due to Internet Explorer security restrictions. Looking into it
webworker01 said:
Obviously we're not writing our source code like that and we compress the final output :good:
Attached screenshot reveals Open Sans being loaded and I've tried it out on many browsers. Maybe there's a browser or OS compatibility issue I can look at if you send over those details.
EDIT: I see the problem you're having might be due to Internet Explorer security restrictions. Looking into it
Click to expand...
Click to collapse
I'm using Firefox 46.0.1, IE shouldn't be a problem. But the console revealed that the fonts are being blocked ( https://puu.sh/p506Q/8a883d0e62.png )
Rough translation: The CORS-Header "Access-Control-Allow-Origin" is missing. So it's no an IE security restriction but a FX security restriction.
(Why is there no "Manage Attachements" button lol)
MrWasdennnoch said:
I'm using Firefox 46.0.1, IE shouldn't be a problem. But the console revealed that the fonts are being blocked ( https://puu.sh/p506Q/8a883d0e62.png )
Rough translation: The CORS-Header "Access-Control-Allow-Origin" is missing. So it's no an IE security restriction but a FX security restriction.
(Why is there no "Manage Attachements" button lol)
Click to expand...
Click to collapse
Right, same problem different browser. Reverted the one change for now. Thanks for the info!
webworker01 said:
Right, same problem different browser. Reverted the one change for now. Thanks for the info!
Click to expand...
Click to collapse
Ah, it's working again, thanks!
And all you did was uncommenting the one <link> tag. Such an easy way to break everything