search

google-code-export / openeve

Automatically exported from code.google.com/p/openeve
0 stars 1 forks source link

Non-latin chars are not displayed in USSD requests. #14

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. call *102# to get balance via USSD(Beeline-Russia)

What is the expected output? What do you see instead?
Expected output is balance in russian, sms, contacts & other works with russian 
letters fine.
Got answer full of strange symbols(letters, digits & other stuff).

What version of the product are you using? On what operating system?
latest

Do you have logcat or dmesg ?
 No suitable info in dmesg & logcat can be found

Original issue reported on code.google.com by Fedo...@gmail.com on 12 Apr 2011 at 7:35

GoogleCodeExporter commented 9 years ago 
You can even attach a screenshot with the ddms

Original comment by wkp...@gmail.com on 12 Apr 2011 at 7:40

GoogleCodeExporter commented 9 years ago 
this is screenshot

Original comment by Fedo...@gmail.com on 12 Apr 2011 at 8:39

Attachments:

GoogleCodeExporter commented 9 years ago 
same with openetna and others...
try to call #102# instead of *102#

Original comment by 2gel...@gmail.com on 12 Apr 2011 at 10:24

GoogleCodeExporter commented 9 years ago 
What was your Official Firmware version ?

the last official firmware V20x you used before using custom firmware.

OpenEVE Gingerbread uses some proprietary binaries included in the V20G.
then before you install OpenEVE GB. you have to install fastbootable V20X 
firmware.

Original comment by wkp...@gmail.com on 12 Apr 2011 at 10:49

GoogleCodeExporter commented 9 years ago 
and V20X series firmware include latest Modem Firmware not included in a custom 
firmware.

Original comment by wkp...@gmail.com on 12 Apr 2011 at 10:51

GoogleCodeExporter commented 9 years ago 
my last firmware was openetna-6.3.
Will try to reflash openeve after V20G

Original comment by Fedo...@gmail.com on 12 Apr 2011 at 2:01

GoogleCodeExporter commented 9 years ago 
V20x might have different MODEM firmware.

http://polytn.blogspot.com/2010/07/comparison-of-various-lg-gw620.html says
amss.mbn is modem firmware not part of any custom firmwares.

so It would be better for you to install localized V20x firmware rather than 
V20G.

Original comment by wkp...@gmail.com on 12 Apr 2011 at 10:10

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/openetna/issues/detail?id=213

Original comment by wkp...@gmail.com on 12 Apr 2011 at 10:17

GoogleCodeExporter commented 9 years ago 
thnx, will search for correct firmware.

Original comment by Fedo...@gmail.com on 13 Apr 2011 at 8:17

GoogleCodeExporter commented 9 years ago 
it's sad, but probably russian USSD binded with specific firmware for ril, so 
it requires to install russian v20d firmware via lgutilz, but original rom has 
no fastboot

Original comment by Fedo...@gmail.com on 13 Apr 2011 at 11:29

GoogleCodeExporter commented 9 years ago 
Why don't you try with n2k1's WayBack firmware ?

http://www.n2k1.openetna.mayix.net/firmware/WayBack/v20d_fastboot_read_warnings.
kdz

you can also contact N2K1 directly at http://forum.openetna.com

Original comment by wkp...@gmail.com on 13 Apr 2011 at 11:47

GoogleCodeExporter commented 9 years ago 
already try this steps, but no luck. I can use #102# code to get transliterated 
balance.

Original comment by Fedo...@gmail.com on 13 Apr 2011 at 1:55

GoogleCodeExporter commented 9 years ago

Original comment by wkp...@gmail.com on 5 May 2011 at 5:16

GoogleCodeExporter commented 9 years ago 
i hope this problem to get fixed also :(

Original comment by waddaa.a...@gmail.com on 9 May 2011 at 10:01

GoogleCodeExporter commented 9 years ago 
why don't you try to attach your logcat ?

you can attach more verbose log like as following

 1. adb logcat -c (cleanup logcat)
 2. adb logcat -b radio -v time > radio.txt (logcat radio, with timestamp)
 3. test USSD
 4. ^C to exit adb logcat and attach the obtained "radio.txt"

Original comment by wkp...@gmail.com on 10 May 2011 at 1:54

GoogleCodeExporter commented 9 years ago 
See also Issue #6

Original comment by wkp...@gmail.com on 11 May 2011 at 9:46

GoogleCodeExporter commented 9 years ago

Original comment by wkp...@gmail.com on 11 May 2011 at 9:59

GoogleCodeExporter commented 9 years ago 
the update update-gb-libril.zip didn't fix this issue (for me )

Original comment by justsad.eng@gmail.com on 11 May 2011 at 10:58

GoogleCodeExporter commented 9 years ago

Original comment by wkp...@gmail.com on 9 Sep 2011 at 5:15

GoogleCodeExporter commented 9 years ago 
I'm sorry, what is the solution now?...I'm on Vodafone Egypt with latest beta 
firmware and I still can't read SSD messages

Original comment by zoza...@gmail.com on 5 Oct 2011 at 7:52

GoogleCodeExporter commented 9 years ago 
Issue 172 has been merged into this issue.

Original comment by wkp...@gmail.com on 13 Oct 2011 at 9:41

GoogleCodeExporter commented 9 years ago 
It is very old bug. It was in the OpenEtna and has passed in the OpenEVE. On 
all versions of firmware. I attach radio-log from ADB (modem firmware - V10, 
boot-gb237-111025-224mb-r193, system-gb-20111011-snapshot). Still, the bug is 
shown and on the version of V20 modem firmware.

Original comment by Dementey...@gmail.com on 6 Nov 2011 at 8:49

Attachments:

GoogleCodeExporter commented 9 years ago 
Currently, OpenEVE based on V20G firmware.

some local specific lib/binary like as "rild" and "libril.so" are from V20G 
firmware.

almost all functions are working but some functions are dependent with the AMSS 
modem firmware already installed your GW620.

I think you have to try to change your "rild" and "libril.so" first.

you can extract "rild" and "libril.so" from your origianl firmware like as 
V10x, V20x *.kdz.

Original comment by wkp...@gmail.com on 9 Nov 2011 at 4:46

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Thanks for assistance! I have extract "rild" and "libril.so" from an original 
firmware (V10g, android version 1,5). At installation "rild" all works well, 
but USSD doesn't work сorrectly. At installation "libril.so" GSM/3G network 
falls. But for other people with OpenEVE with the AMSS V20x all the same works 
ONLY Latin USSD.

Original comment by Dementey...@gmail.com on 13 Nov 2011 at 10:19

GoogleCodeExporter commented 9 years ago 
thankyou for your testing~!!

Original comment by wkp...@gmail.com on 14 Nov 2011 at 6:33

GoogleCodeExporter commented 9 years ago 
what files/folders should i extract from the original "v10l arabic"?
shoud i flash the original amss "v10l"? i'm now on v10h amss , and using v20i 
system/boot.
this issue is the most important "non resolved issues in openeve "

Original comment by justsad.eng@gmail.com on 31 Dec 2011 at 11:23