I am working on an open source RTL support for Android and I need help testing...
I have attached a normal app (that should work on any Android 1.5 and up) that runs my method before calling drawText.
The purpose is to make drawText call to it so it will support BiDi.
It reads a file called /sdcard/test.txt from which it gets the test string.
It does not support newlines.
Try it and tell me what you think.
The reason I don't publish the source yet is because knowing how it works would prevent it from being tested properly.
I hope I'm putting this in the right forum...
Hebrew Supported...
Is it also, support the font for Hebrew?
Because in ver 2.1, the have Hebrew but sometimes you see square or ? signs.
TheAgent1982 said:
Is it also, support the font for Hebrew?
Because in ver 2.1, the have Hebrew but sometimes you see square or ? signs.
Click to expand...
Click to collapse
The fonts exist, there's no work necessary on them, you have to push them to the device and that's it...
biditest with Android 2.2 FroYo (FRF50) Arabic test.txt
I tested with Android 2.2 FroYo (FRF50)
without /sdcard/test.txt and with my own text
I don't know about the Hebrew, the Arabic text are not joined (re-shaped) correctly
dudyk said:
The fonts exist, there's no work necessary on them, you have to push them to the device and that's it...
Click to expand...
Click to collapse
I have TP2 running Android 2.1 .
So, any idea how to do it?
Thanks for writing an open source BiDi support.
I did a very short test:
1. It did not render the whole line of text.
2. It looks like it has problems when switching from one language to another. E.g. the closing bracket after the hebrew word is rendered as open.
I attached the original text files and screen shots.
In addition I attache a screen shot of TxtPad Light and how it is rendered there.
TheAgent1982 said:
Is it also, support the font for Hebrew?
Because in ver 2.1, the have Hebrew but sometimes you see square or ? signs.
Click to expand...
Click to collapse
This might be a problem of character encoding.
I did a test with a UTF-8 file and a Hebrew ISO 8859-8. The first rendered the letters correct but the second showed only question marks. (See picture)
As alternative keyboard I recommend using either AnySoftKeyboard or SmartKeyboard.
It is in CM-5.0.8, with a fix on the issue list.
Dear Dudy,
Will your fix work for 2.1 as well? Can you give directions how to apply it to other ROMs? I own an HTC Desire, and would love to implement the fix. So far I just have the common StaticLayout fix.
Thanks,
Ron
EDIT: More specifically, it would be great if you can tell us which files to take from the CM update with the help of baksmali and smali in order to graft them into other distros. That's the way I implanted StaticLayout.smali in MoDaCo roms.
CM 5.0.8 is 2.1. It should apply to any 2.1/2.2 rom, just take my 4 commits from CM's git from framework base repository.
dudyk said:
CM 5.0.8 is 2.1. It should apply to any 2.1/2.2 rom, just take my 4 commits from CM's git from framework base repository.
Click to expand...
Click to collapse
Thanks for the reply, Dudy. I'll be more specific about what I am trying to do: I am trying to pull the files with your patches from the CM-5.0.8 ROM without compiling anything.
With the StaticLayout fix, I used baksmali and smali to disassemble the classes.dex from framework.jar and replace StaticLayout.smali. This worked.
When I look at the page github.com/dudyk/android_frameworks_base/commit/1b0aca31c3e03a5a323276cd15a8df4203a1792c - the one with your commits (is that the right one?) I cannot figure out all the files that I would need to replace. Sorry, I am not a programmer...
I can pretty much figure out that all the files preceeded by core/java/android/ will be found with their exact names in the classes.dex from framework.jar. But I have no idea where to locate the compiled files that resulted from AndroidGraphics2D, the three Canvas files and the ResourceTypes.
If you can point me at the right direction I'll be able to convert a script that was used for the StaticLayout fix so that anyone with a Mac or Linux would be able to easily implement your fix to any none-odexed distro.
Thanks so much in advance!
you didn't add U+0600 support in your Canvas.java @ cyanogen's git
PapaDocta said:
you didn't add U+0600 support in your Canvas.java @ cyanogen's git
Click to expand...
Click to collapse
Why do you say that? I tested for U0590 to U07B1, isn't that enough?
my bad.. i don't know how i overlooked the U07B1.... it's more than enough
Dear Dudy, I really need your help.
Back in the old days (a month ago), before your wonderful work, the best fix we had was Omri Baumer's StaticLayout fix. I was able to use the baksmali and the smali utilities to extract the smali file from framework.jar of CM, and graft it into ANY phone. Another user on the iAndroid forums created a script that automated everything.
I wanted to do the same with your fix. So I compiled a vanilla 2.1 and then applied only your patches, manually, and recompiled. I used baksmali to disassemble all the framework files, and discovered that the changed files were:
android/graphics/Canvas.smali
android/graphics/Canvas$EdgeType.smali
android/graphics/Canvas$VertexMode.smali
android/text/Layout.smali
android/text/SpannableStringBuilder.smali
android/text/Styled.smali
android/widget/TextView$CharWrapper.smali
The two additional Canvas files were tagged as changed, but no textual difference is evident. So altogether we are talking about 5 files that ideally would be easily grafted into ANY device running 2.1, without recompilation.
The problem was that the new Canvas.smali file caused boot loops on my HTC Desire. Logcat caught this:
Code:
D/AndroidRuntime( 103): --- registering native functions ---
W/dalvikvm( 103): Unable to register: not native: Landroid/graphics/Canvas;.drawText (Ljava/lang/String;FFLandroid/graphics/Paint;)V
E/JNIHelp ( 103): RegisterNatives failed for 'android/graphics/Canvas'
E/AndroidRuntime( 103): Unable to register all android natives
This did NOT happen when I tried the vanilla Canvas.smali. So it must be something in your patches. If you can help me figure out how to fix this, your fix will be easily implemented into any un-odexed 2.1 device. The script is all reworked and ready... Just this problem needs ironing out.
Thanks so much - for your wonderful work, and for taking the time to read this.
Ron
ClassicalDude said:
I wanted to do the same with your fix. So I compiled a vanilla 2.1 and then applied only your patches, manually, and recompiled. I used baksmali to disassemble all the framework files, and discovered that the changed files were:
android/graphics/Canvas.smali
android/graphics/Canvas$EdgeType.smali
android/graphics/Canvas$VertexMode.smali
android/text/Layout.smali
android/text/SpannableStringBuilder.smali
android/text/Styled.smali
android/widget/TextView$CharWrapper.smali
The two additional Canvas files were tagged as changed, but no textual difference is evident. So altogether we are talking about 5 files that ideally would be easily grafted into ANY device running 2.1, without recompilation.
The problem was that the new Canvas.smali file caused boot loops on my HTC Desire. Logcat caught this:
Code:
D/AndroidRuntime( 103): --- registering native functions ---
W/dalvikvm( 103): Unable to register: not native: Landroid/graphics/Canvas;.drawText (Ljava/lang/String;FFLandroid/graphics/Paint;)V
E/JNIHelp ( 103): RegisterNatives failed for 'android/graphics/Canvas'
E/AndroidRuntime( 103): Unable to register all android natives
This did NOT happen when I tried the vanilla Canvas.smali. So it must be something in your patches. If you can help me figure out how to fix this, your fix will be easily implemented into any un-odexed 2.1 device. The script is all reworked and ready... Just this problem needs ironing out.
Thanks so much - for your wonderful work, and for taking the time to read this.
Ron
Click to expand...
Click to collapse
My changes add a native method (a C++ one) to the sources, from what I know, it is in the dex file, but maybe smali's files do not extract it, or extract it differently.
I never tried to disassemble files in android and reassemble them, so I have no idea how to help you besides describing the changes to you.
P.S.
Do you think that HebVillian is using my fix this way? I believe that I'm the first to fix this for ROMs above 2.0 (BTW, it's in the froyo branch of CM as well).
I don't know about HebVillain. The maker of the rom was made aware of the way I patched StaticLayout, so it may well be. Perhaps he also read your thread and applied the actual patches...
I noticed that in one of your commits:
http://github.com/dudyk/android_fra...0aca31c3e03a5a323276cd15a8df4203a1792c#diff-5
You added "native" to drawText. It is exactly the function in that line that is throwing the error on boot - about not being native. I tried recompiling with that particular change reversed, but it did not make a difference. Can you investigate the matter? Perhaps the way the Nexus 1 boots is different than that of other devices, and the checks are not as strict. If this is indeed a code problem, perhaps it needs to be addressed for the patch to be viable for other devices.
Take everything I say with a grain of salt - I am no programmer. Just following what I read and understand.
I have no idea if this helps, but googling the words
android registernatives
results in quite a few technical posts complaining about similar problems...
I am sorry for being a nag. But I hope I am getting closer to the source of the problem.
The Android emulator was able to boot up just fine with the patches applied. The logcat stated at the beginning of the runtime:
Code:
D/AndroidRuntime( 29): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 29): CheckJNI is ON
I/ ( 30): ServiceManager: 0xad08
D/AudioHardwareInterface( 30): setMode(NORMAL)
I/CameraService( 30): CameraService started: pid=30
The very same smali files, when applied to the HTC Desire's framework, generated the native error I quoted before. But logcat shows that the beginning of its runtime is indeed different:
Code:
D/AndroidRuntime( 197): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 197): CheckJNI is OFF
D/dalvikvm( 197): Precise GC configured ON
D/dalvikvm( 197): creating instr width table
I/dalvikvm( 197): mlock: /data/dalvik-cache/[email protected]@[email protected], fd=7
So - how do we make the Desire, or any other device, turn on CheckJNI and turn off precise GC?
EDIT: In one of CM's change logs it was written that Precise GC was turned off because of its memory consumption. I am just assuming that this is indeed the cause for my problems. How can we check it?
CheckJNI and Precise GC don't matter.
Repatched and recompiled 2.2 source. The emulator runs beautifully with or without JNI checks. My HTC desire, with a 2.2 rom, still complains about the same function not being native.
The port dudyk did to Omri Baumer's patch works partially - the numbers are not reversed, but the whole line is aligned to the left (with hebrew text appearing to the left of the number, instead of the right).
I have no idea what else to do or to check.
i tried the latest cm6 nightly build and still it won't align Arabic RTL correctly.. it aligns it as LTR and there no reshaping as well....
Hello,
thank you in advance for your help.
Facts: rooted ICS 4.0.3 IMLK74K.DE_epad-9.4.2.15-20120221
Problem: Everytime when i like to open Accounts & Syncronisation (don't know the exact translation in german it's called "Kontakte & Synchronisation") the dialog suddenly quits.
I installed log viewer to check what's going on, you can see the error message in the Screenshot.
So i think the problem is, that i deleted Pcsynclauncher.apk from ASUS, my question is, can anyone tell me how to extract that file from the Stock ROM i downloaded from here or can anyone post the file on the board?
THX
DidierSchnee said:
Hello,
thank you in advance for your help.
Facts: rooted ICS 4.0.3 IMLK74K.DE_epad-9.4.2.15-20120221
Problem: Everytime when i like to open Accounts & Syncronisation (don't know the exact translation in german it's called "Kontakte & Synchronisation") the dialog suddenly quits.
I installed log viewer to check what's going on, you can see the error message in the Screenshot.
So i think the problem is, that i deleted Pcsynclauncher.apk from ASUS, my question is, can anyone tell me how to extract that file from the Stock ROM i downloaded from here or can anyone post the file on the board?
THX
Click to expand...
Click to collapse
I'm guessing you did not unlock the bootloader yet Try extracting the zip I have attached to your "C:\" , install adb on your pc then run the following command
Code:
adb push C:\PCSyncLauncher.apk /system/app
Code:
adb push C:\PCSyncLauncher.odex /system/app
Follow this guide if you need help installing ADB (http://www.theandroidsoul.com/how-to-install-adb-on-windows-full-guide/)
Thank your for your help.
Had some problems with adb push (permission denied, adb remount gave me operation failed), so i copied the files on the prime and "installed" them with the terminal!
problem solved.
DidierSchnee said:
Thank your for your help.
Had some problems with adb push (permission denied, adb remount gave me operation failed), so i copied the files on the prime and "installed" them with the terminal!
problem solved.
Click to expand...
Click to collapse
Great job thinking out-side of the box. This is how a Dev is born, hope you will join us soon
thx, but there is only one problem called time
Sent from my Transformer Prime TF201 using Tapatalk 2
And I still have that problem, even after installing files
Code:
[email protected]:/data/system/dropbox # cat *
Process: com.android.settings
Flags: 0x8be45
Package: com.android.settings v15 (4.0.3-WW_epad-9.2.2.6-20120525)
Build: asus/WW_epad/TF101G:4.0.3/IML74K/WW_epad-9.2.2.6-20120525:user/release-keys
java.lang.IllegalArgumentException: Unknown package: com.asus.pcsynclauncher
at android.os.Parcel.readException(Parcel.java:1331)
at android.os.Parcel.readException(Parcel.java:1281)
at android.content.pm.IPackageManager$Stub$Proxy.getApplicationEnabledSetting(IPackageManager.java:2423)
at android.app.ApplicationPackageManager.getApplicationEnabledSetting(ApplicationPackageManager.java:1153)
at com.android.settings.accounts.ManageAccountsSettings.updateUi(ManageAccountsSettings.java:198)
at com.android.settings.accounts.ManageAccountsSettings.onStart(ManageAccountsSettings.java:105)
at android.app.Fragment.performStart(Fragment.java:1532)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:862)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1032)
at android.app.BackStackRecord.run(BackStackRecord.java:622)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1382)
at android.app.FragmentManagerImpl$1.run(FragmentManager.java:426)
at android.os.Handler.handleCallback(Handler.java:605)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4424)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
at dalvik.system.NativeStart.main(Native Method)
1|[email protected]:/data/system/dropbox # ls -la /system/app/PCSyncLauncher.*
-rw-r--r-- root root 44092 2013-05-26 18:01 PCSyncLauncher.apk
-rw-r--r-- root root 18968 2013-05-26 18:01 PCSyncLauncher.odex
adb push didn't work for me either, so copied files randomly. I tried to find the cause but failed. My guess is that somewhere in the system must be written information about this package, but it isn't and I don't know where it should be.
Ok, now I even tried something else but still have negative result:
Code:
pm install /sdcard/Download/PCSyncLauncher.apk
pkg: /sdcard/Download/PCSyncLauncher.apk
Failure [INSTALL_FAILED_DEXOPT]
need a different version
Hi, I just took the poor decision of uninstalling the com.asus.pcsynclauncher package from my TF201 , so I am getting the same exception when trying to access accounts & sync.
I just tried the APK supplied by MasterZen88, however I get error log entries "Package com.asus.pcsynclauncher has mismatched uid: 10003 on disk, 10053 in settings" and a "dexopt failed on .... [email protected]' res = 65280" when installing, which ends up failing.
I assume it is because my ICS version is different: IML74.WW_epad-9.4.2.28-20120525
What do you think? If my assumption is correct, is there anyone that can supply me with the right APK and ODEX?
Thank you for your help.
I am trying to build an apk file for release. My application lib contains a jar (probably obfuscated) from a third party vendor of one of my company's hard-wares. When I build the apk in debug mode it is successful, but when I try to do it in release mode using "ant release" it throws the following error.
Code:
BUILD FAILED
C:\adt-bundle-windows-x86_64\sdk\tools\ant\build.xml:868: Can't read [D:\Workspace\MyProject\libs\ThirdPartyJarV3.1.jar] (Can't process class [g.class] (Unknown verification type [10] in stack map frame))
I have successfully built apks in release mode for other projects (which doesn't have this jar file.)
It seems to be an issue around proguard not being able to read this class in the jar. I have looked through ProGuard's trouble shooting manual and also on google and found no help with this particular error:
Code:
(Unknown verification type [10] in stack map frame)
I also updated proguard from V4.7 to 4.10, but it still encounters the same error.
To my little mind it seems to be a problem with the jar itself and if so how do I fix it? Any help would be appreciated. TIA!
[P.S: I'm new to android]
Hi guys!
I'm trying to port some package from Samsung ROM to CM following this guide and I'm stuck.
I decompiled the package, removed TW dependency from the manifest and now I'm adding additional classes from TW framework into this package. Everything was smooth so far as I was getting rid of "class not found" and similar messages in logcat by adding the missing class and recompiling the package.
But now I'm facing an issue, which I don't know how to fix:
When I try to run the app, I get the following message in logcat:
Code:
I/dalvikvm(30301): Could not find method com.sec.android.touchwiz.widget.TwAbsListView.isInDialog, referenced from method com.sec.android.touchwiz.widget.TwAbsListView.onHoverDrawableState
W/dalvikvm(30301): VFY: unable to resolve virtual method 9561: Lcom/sec/android/touchwiz/widget/TwAbsListView;.isInDialog ()Z
D/dalvikvm(30301): VFY: replacing opcode 0x74 at 0x006c
TwAbsListView class derives from TwAdapterView (from TwAbsListView.smali):
Code:
.super Lcom/sec/android/touchwiz/widget/TwAdapterView;
TwAdapterView derives from android.view.ViewGroup, which derives from android.view.View, which has a definition for "isInDialog". This what I found when decompiled framework.jar from the stock ROM:
smali\android\view\View.smali
Code:
.method public isInDialog()Z
However, based on official documentation this method does not exist in this class.
If I try to add android.view.ViewGroup and android.view.View from stock framework.jar into the package explicitly, I start getting "multiple definition" messages in logcat, and isInDialog still can't be resolved.
So, I'm currently stuck. Please advise. Is there something I'm doing wrong or not doing?
I guess with my last edit, I answered my own question.
It looks like Samsung decided to change implementation of android.view.View class to include isInDialog() method.
I just tried moving the definition of this method into com.sec.android.touchwiz.widget.TwAdapterView class, which derives from android.view.ViewGroup, and it looks like I no longer getting the message about missing isInDialog method.
There are still a gazillion other methods like this, but at least it's clear now what needs to be done.
Hello, I am trying to port a touchwiz rom but I keep on getting the same error
link_image[1965]: 167 could not load needed library 'libc.so' for '/system/
/sh' (load_library[1120]: Library 'libc.so' not found)CANNOT LINK EXECUTABLE
I took a look at the zip and libc.so is present, I used the libc.so that came with the rom but I still got the same error.
Can anyone help me solve this problem?