We found that some ppl can not access the TapJoy.com in some area , So we change the 5 app limit count to 15.
Fonter is the best font manager on Android,not only support CHANGE SYSTEM FONT also support CHANGE APP's FONT, also have thousands of fonts for you.
Fonter is desigined to change your phone's font, or just change an app's font. It's super easy to use, change every app's font every day!
If you find Fonter is useful, please rate a five star. If you have any problems, please email([email protected]) us or feedback in this thread before rate one star. THANK YOUR !
Help to translate this app to your language
English: http://osvya69.oneskyapp.com/collaboration/project?id=36345
Download
repo.xposed.info/module/git.hub.font
PLEASE NOTE: THIS IS A BETA TEST APP, BACKUP YOUR DEVICES DATA BEFORE CHANGE YOUR SYSTEM FONT.
FEATURES:
<b>* Support to change an app's font</b>
<b>*</b> Support Samsung,OnePlus,part of Color OS phones to change font perfectly (NO ROOT needed)
<b>*</b> Support generate Huawei,Xiaomi theme package, using theme manager to change font on those phones (NO ROOT needed)
<b>*</b> Support HTC,Motorola,Lenovo,Nokia X, Nexus series phones to change font(NEED ROOT)
<b>*</b> Support Flipfont changer system
<b>*</b> Support custom fonts
<b>*</b> Easy to use, no tedious steps
<b>*</b> Support multi THEME
HOW TO CHANGE AN APP's FONT
First you need install Xposed framework( repo.xposed.info ) and enable it. Then enable the Fonter module on the Xposed modules screen and reboot your device.
After that, you can select the "Change app font" menu on the left drawer. Pick the app you want to change, and enable change app font function on the app's settings screen, pick the font you want to use.
That's all, have fun!
HOW TO CHANGE SYSTEM FONT
If you have a phone with Flipfont(Most Samsung, OnePlus, Part of Color os):
FIRST OF ALL
You have to check "unknown sources" option on the Settings
1. Go to home screen > "settings" > "security" , and check "unknown sources".
2. Please note: some Carriers doesn't allow non-market apps (downloaded or copyed) be installed. In such case you should root your device to use this feature.
HOW TO USE?
1. Check if your phone have Flipfont.(Home > Settings > Display, check there has Font or Font style or not). Then run this app, download a font you want to use, after download there have to optinos: CHANGE SYSTEM FONT and CHANGE APP FONT. if you want change system font, pick the CHANGE SYSTEM FONT button; if you want change an app's font, pick the CHANGE APP FONT button(this option nend Xposed framewrok:
If you pick the CHANGE SYSTEM FONT option, will ask you to install the font app. After installed , go to font setting screen (Home > Setting > Display > Font or Font sytle). If everything ok, you will see a new font name on font list.
pick it , enable it and enjoy it.
HOW TO UNINSTALL FONTS?
** Go to 'Home > Setting > Application > Manage Application'
** Select font you want to uninstall
Cool, it works great! But I have a question. I have a font saved here, can you add an option to make the apk file so it's installable? The method I used makes the apk incompatible with KitKat.
Enviado do meu Galaxy S5
Does it work with Sony?
Thanks.
I got error and Fonter crashed when I choose font for an app.
Device: Xperia Z2 D6503 4.4.2
Code:
10-02 16:36:34.184: W/dalvikvm(21801): threadid=1: thread exiting with uncaught exception (group=0x4156cd88)
10-02 16:36:34.184: E/AndroidRuntime(21801): FATAL EXCEPTION: main
10-02 16:36:34.184: E/AndroidRuntime(21801): Process: git.hub.font, PID: 21801
10-02 16:36:34.184: E/AndroidRuntime(21801): java.lang.NullPointerException
10-02 16:36:34.184: E/AndroidRuntime(21801): at git.hub.font.e.f.d(Unknown Source)
10-02 16:36:34.184: E/AndroidRuntime(21801): at git.hub.font.x.a.d.a(Unknown Source)
10-02 16:36:34.184: E/AndroidRuntime(21801): at git.hub.font.x.n.onItemClick(Unknown Source)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AdapterView.performItemClick(AdapterView.java:299)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AbsListView.performItemClick(AbsListView.java:1113)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AbsListView$PerformClick.run(AbsListView.java:2904)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AbsListView$3.run(AbsListView.java:3638)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.os.Handler.handleCallback(Handler.java:733)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.os.Handler.dispatchMessage(Handler.java:95)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.os.Looper.loop(Looper.java:212)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.app.ActivityThread.main(ActivityThread.java:5151)
10-02 16:36:34.184: E/AndroidRuntime(21801): at java.lang.reflect.Method.invokeNative(Native Method)
10-02 16:36:34.184: E/AndroidRuntime(21801): at java.lang.reflect.Method.invoke(Method.java:515)
10-02 16:36:34.184: E/AndroidRuntime(21801): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
10-02 16:36:34.184: E/AndroidRuntime(21801): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:684)
10-02 16:36:34.184: E/AndroidRuntime(21801): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
10-02 16:36:34.184: E/AndroidRuntime(21801): at dalvik.system.NativeStart.main(Native Method)
Does it work with aosp Roms?
Send with Stylus from Pegasus Galaxy by a Boeffla powered slim device
dandroid13 said:
Cool, it works great! But I have a question. I have a font saved here, can you add an option to make the apk file so it's installable? The method I used makes the apk incompatible with KitKat.
Enviado do meu Galaxy S5
Click to expand...
Click to collapse
The Make apk file feature is developing.
Right now, you can using the "Change App Font" function to set custom font.
Andii S. said:
Does it work with aosp Roms?
[/QUOTE}
yes, any 4.0.3+ aosp roms
Click to expand...
Click to collapse
Thank you, RyokoN
This is a bug, just fixed, and published on the xposed repo
RyokoN said:
I got error and Fonter crashed when I choose font for an app.
Device: Xperia Z2 D6503 4.4.2
Code:
10-02 16:36:34.184: W/dalvikvm(21801): threadid=1: thread exiting with uncaught exception (group=0x4156cd88)
10-02 16:36:34.184: E/AndroidRuntime(21801): FATAL EXCEPTION: main
10-02 16:36:34.184: E/AndroidRuntime(21801): Process: git.hub.font, PID: 21801
10-02 16:36:34.184: E/AndroidRuntime(21801): java.lang.NullPointerException
10-02 16:36:34.184: E/AndroidRuntime(21801): at git.hub.font.e.f.d(Unknown Source)
10-02 16:36:34.184: E/AndroidRuntime(21801): at git.hub.font.x.a.d.a(Unknown Source)
10-02 16:36:34.184: E/AndroidRuntime(21801): at git.hub.font.x.n.onItemClick(Unknown Source)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AdapterView.performItemClick(AdapterView.java:299)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AbsListView.performItemClick(AbsListView.java:1113)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AbsListView$PerformClick.run(AbsListView.java:2904)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AbsListView$3.run(AbsListView.java:3638)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.os.Handler.handleCallback(Handler.java:733)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.os.Handler.dispatchMessage(Handler.java:95)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.os.Looper.loop(Looper.java:212)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.app.ActivityThread.main(ActivityThread.java:5151)
10-02 16:36:34.184: E/AndroidRuntime(21801): at java.lang.reflect.Method.invokeNative(Native Method)
10-02 16:36:34.184: E/AndroidRuntime(21801): at java.lang.reflect.Method.invoke(Method.java:515)
10-02 16:36:34.184: E/AndroidRuntime(21801): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
10-02 16:36:34.184: E/AndroidRuntime(21801): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:684)
10-02 16:36:34.184: E/AndroidRuntime(21801): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
10-02 16:36:34.184: E/AndroidRuntime(21801): at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
hassanmahmood said:
Does it work with Sony?
Thanks.
Click to expand...
Click to collapse
I do not have a Sony device, so i have no idea.
But, if you can use xposed on Sony devices, you can use the "Change App Font" function to Change an app's font, or Change System UI font .
goodevh said:
Thank you, RyokoN
This is a bug, just fixed, and published on the xposed repo
Click to expand...
Click to collapse
Great!
Fonter now works perfectly on my Xperia!
I want to translate Fonter to Japanese, but there is no choise for it.
Can you add Japanese to the list of translating languages?
[EDIT]
One question, how can I choose fonts in custom font folder to change system font?
How to change custom font? I have ttf font in my sd card
Thanks! how i can add more font? (i want fonts in hebrew)
Wow thank you for this new apps so easy to use fonts
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
exodius48 said:
How to change custom font? I have ttf font in my sd card
Click to expand...
Click to collapse
Create two floder fonter + fonts and put your TTF fonts in
Japanese is added, thanks again for your support!! :good:
RyokoN said:
Great!
Fonter now works perfectly on my Xperia!
I want to translate Fonter to Japanese, but there is no choise for it.
Can you add Japanese to the list of translating languages?
[EDIT]
One question, how can I choose fonts in custom font folder to change system font?
Click to expand...
Click to collapse
exodius48 said:
How to change custom font? I have ttf font in my sd card
Click to expand...
Click to collapse
Put your ttf files on /Sdcard/fonter/fonts (you can change the folder on the settings screen) folder.
Then when you change an app's font, can pick this folders font.
next release will Support open ttf files and set to system font!
@goodevh can you help me? I have these fonts here, but the app doesn't see them.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enviado do meu Galaxy S5
1910
dandroid13 said:
@goodevh can you help me? I have these fonts here, but the app doesn't see them.
Enviado do meu Galaxy S5
Click to expand...
Click to collapse
Right now the custom font only shows on the "PICK FONT" screen:
the "CHOOSE FONT" button will launch the PICK FONT screen
goodevh said:
Right now the custom font only shows on the "PICK FONT" screen:
the "CHOOSE FONT" button will launch the PICK FONT screen
Click to expand...
Click to collapse
Oh, man, I feel so dumb, I didn't get a notification the first time you quoted me.
Now it works, thanks mate.
goodevh said:
Japanese is added, thanks again for your support!! :good:
Click to expand...
Click to collapse
strings for arrays such as Font install mode selection and Orientation are showed as one long string, so maybe it will cause a problem dividing one translated string to multiple strings.
I also want "Copy source text into translation textarea" since I don't know how to input some characters such as black box for theme selection
If you are OK to change translation manager system, I recommened OneSkyApp.com.
Using OneSkyApp translators can work with PC with usuful functions and you can manage translations easily.
RyokoN said:
strings for arrays such as Font install mode selection and Orientation are showed as one long string, so maybe it will cause a problem dividing one translated string to multiple strings.
I also want "Copy source text into translation textarea" since I don't know how to input some characters such as black box for theme selection
If you are OK to change translation manager system, I recommened OneSkyApp.com.
Using OneSkyApp translators can work with PC with usuful functions and you can manage translations easily.
Click to expand...
Click to collapse
I'm checking the OneSkyApp service,
transcommu also can work on PC, open the url on you browser:
http://transcommu.yasesprox.com/transcommu/Applications/View/185
EDIT:
add on oneskyapp
English: http://osvya69.oneskyapp.com/collaboration/project?id=36345
Chinese: http://osvya69.oneskyapp.com/collaboration/project?id=36343
Related
I've been trying to compile AOSP apps individually and that doesn't seem to work. These are the steps I took:
1. Install GCC and Java
2. The repo commands (sync from android git etc)
3. make Gallery3D
4. push Gallery3D.apk /system/app/
So as you can see, compilation went on fine. And pushing to my phone also went fine (CM 5.0.4.1). However, when I try to run Gallery3D, I got FC. Here's my logcat:
I/ActivityManager( 93): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.cooliris.media/.Gallery }
V/RenderScript_jni( 6329): surfaceDestroyed
V/RenderScript( 6329): setSurface 0 0 0x0
D/ViewFlipper( 6329): updateRunning() mVisible=false, mStarted=true, mUserPresent=true, mRunning=false
D/LocationManager( 6198): removeUpdates: listener = [email protected]
D/NetworkLocationProvider( 93): removeListener(): wallpaper
D/NetworkLocationProvider( 93): enableLocationTracking(): false
E/NetworkLocationProvider( 93): releaseCheckLocationLock: wake lock has already been released
D/SensorManager(18699): found sensor: BMA150 3-axis Accelerometer, handle=0
D/SensorManager(18699): found sensor: AK8973 3-axis Magnetic field sensor, handle=1
D/SensorManager(18699): found sensor: AK8973 Orientation sensor, handle=2
D/SensorManager(18699): found sensor: CM3602 Proximity sensor, handle=4
D/SensorManager(18699): found sensor: CM3602 Light sensor, handle=5
W/ResourceType(18699): Failure getting entry for 0x7f02003a (t=1 e=58) in package 0: 0xffffffb5
D/AndroidRuntime(18699): Shutting down VM
W/dalvikvm(18699): threadid=3: thread exiting with uncaught exception (group=0x4001b178)
E/AndroidRuntime(18699): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime(18699): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.cooliris.media/com.cooliris.media.Gallery}: android.content.res.Resources$NotFoundException: Resource ID #0x7f02003a
E/AndroidRuntime(18699): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2496)
E/AndroidRuntime(18699): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/AndroidRuntime(18699): at android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/AndroidRuntime(18699): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/AndroidRuntime(18699): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(18699): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(18699): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime(18699): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(18699): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime(18699): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime(18699): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime(18699): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(18699): Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x7f02003a
E/AndroidRuntime(18699): at android.content.res.Resources.getValue(Resources.java:891)
E/AndroidRuntime(18699): at android.content.res.Resources.getDrawable(Resources.java:579)
E/AndroidRuntime(18699): at com.cooliris.media.HudLayer.<init>(HudLayer.java:121)
E/AndroidRuntime(18699): at com.cooliris.media.GridLayer.<init>(GridLayer.java:134)
E/AndroidRuntime(18699): at com.cooliris.media.Gallery.onCreate(Gallery.java:78)
E/AndroidRuntime(18699): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime(18699): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/AndroidRuntime(18699): ... 11 more
I/Process ( 93): Sending signal. PID: 18699 SIG: 3
I/dalvikvm(18699): threadid=7: reacting to signal 3
I/dalvikvm(18699): Wrote stack trace to '/data/anr/traces.txt'
I/DumpStateReceiver( 93): Added state dump to 1 crashes
Click to expand...
Click to collapse
Besides this, I noticed that my Gallery3D.apk is smaller size(~500kb) than the one which comes with CM (~700kb).
Any help guys? Been trying to figure this out and googling. What did I miss?
arctu said:
I've been trying to compile AOSP apps individually and that doesn't seem to work. These are the steps I took:
1. Install GCC and Java
2. The repo commands (sync from android git etc)
3. make Gallery3D
4. push Gallery3D.apk /system/app/
So as you can see, compilation went on fine. And pushing to my phone also went fine (CM 5.0.4.1). However, when I try to run Gallery3D, I got FC. Here's my logcat:
Besides this, I noticed that my Gallery3D.apk is smaller size(~500kb) than the one which comes with CM (~700kb).
Any help guys? Been trying to figure this out and googling. What did I miss?
Click to expand...
Click to collapse
Q&A section ma man
I believe this is the right section, it's a question on compiling/development. I believe Gallery3D might be lacking mdpi images, and you're compiling for mdpi devices (may be wrong, not able to check now).
What you can do is to do a search for "PRODUCT_LOCALES", within all your files, I think it's in build.mk or product.mk. You will see that the default is mdpi, follow by <something> (can't remember now) += nodpi. Add a <something> += hdpi after the nodpi line, and compile and push again. I had a similar issue and was able to fix it this way, with advice from cyanogen.
Thanks Wysie. That helps!
To those facing the same problem here are the exact steps I took (using terminal and nano):
1. Open/Edit build/core/product_config.mk:
nano build/core/product_config.mk
Click to expand...
Click to collapse
2. Find:
PRODUCT_LOCALES += nodpi
Click to expand...
Click to collapse
3. Add in after that line:
PRODUCT_LOCALES += hdpi
Click to expand...
Click to collapse
4. Save and Exit: Ctrl+X
5. Run make again:
make Gallery3D
Click to expand...
Click to collapse
If you did everything correctly, and have compiled before, the compiler should write this at the beginning:
*** Build configuration changed: "generic-eng-{mdpi,nodpi}" -> "generic-eng-{mdpi,nodpi,hdpi}"
*** Forcing "make installclean"...
*** Done with the cleaning, now starting the real build.
Click to expand...
Click to collapse
It works now. Hope this helps the others.
arctu said:
Thanks Wysie. That helps!
To those facing the same problem here are the exact steps I took (using terminal and nano):
1. Open/Edit build/core/product_config.mk:
2. Find:
3. Add in after that line:
4. Save and Exit: Ctrl+X
5. Run make again:
If you did everything correctly, and have compiled before, the compiler should write this at the beginning:
It works now. Hope this helps the others.
Click to expand...
Click to collapse
cheers, helped me out
after quick grep to confirm I used sed
Code:
sed s/PRODUCT_LOCALES\ \+\=\ nodpi/PRODUCT_LOCALES\ \+\=\ hdpi/ build/core/product_config.mk -i
Request is in the title - the LG Optimus One from Orange UK contains the Orange Signal Boost (UMA) software that would be useful to get working on other android phones with networks which support UMA. The topic is here but I've cross-posted here in case the topic gets lost in the general forum.
Here you go, This should be the original Orange V10C_00 firmware for your phone:
Code:
csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/AORUBK/V10c_00/V10C_00.kdz
I was thinking maybe someone with the Optimus One could just backup the apk for Orange Signal Boost and post that. I have tried expanding the rom posted in the link and have got as far as the mbn files and boot.img etc but I don't know how to get at the apk's...
Bump
Could any owner of optimus one share that app with us ?
please
Again, please anyone! We just need a backup of the apk to get started!
Sent from my HTC Desire using XDA App
Ok, I managed to unpack the KDZ file but still couldn't find a way extract the Orange Signal Booster apk from boot.img file; so if anyone has backup of the apk it would be greatly appreciated.
I tried the same thing but had no luck. If you had the handset you could use a number of different apps (astro, titanium backup) to make a backup of the .apk file with very little technical knowledge.
It would be god send if we could get this app running on other handsets...
Here is the APK!
OK here is the APK which I have extracted from the ROM image. I tried installing it on my desire and it FCs as soon as I attempt to run it. If anyone else wants to get onboard with this please do!
Hi ballandbiscuit, many thanks for the APK. Tried it on my HTC DHD and had the same FC result as you. As far as I can tell, this is not a hardware restriction but possibly the result of other system services required by the app not installed on the handset.
I really wish someone from Orange with a bit of technical knowhow would get involved and assist us with this much needed feature.
what about some kind of logging? maybe it say something...
Sent from my LG-P500 using XDA App
Here is some data from logcat
Code:
I/ActivityManager( 167): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.kineto/.kineto }
I/ActivityManager( 167): Start proc com.android.kineto for activity com.android.kineto/.kineto: pid=1695 uid=10103 gids={3003, 3002, 3001, 1015}
W/dalvikvm( 1695): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Lcom/android/kineto/kineto;.<clinit>
W/dalvikvm( 1695): Class init failed in newInstance call (Lcom/android/kineto/kineto;)
D/AndroidRuntime( 1695): Shutting down VM
W/dalvikvm( 1695): threadid=1: thread exiting with uncaught exception (group=0x4001d7e8)
E/AndroidRuntime( 1695): FATAL EXCEPTION: main
E/AndroidRuntime( 1695): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 1695): at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime( 1695): at java.lang.Class.newInstance(Class.java:1429)
E/AndroidRuntime( 1695): at android.app.Instrumentation.newActivity(Instrumentation.java:1021)
E/AndroidRuntime( 1695): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2577)
E/AndroidRuntime( 1695): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2679)
E/AndroidRuntime( 1695): at android.app.ActivityThread.access$2300(ActivityThread.java:125)
E/AndroidRuntime( 1695): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2033)
E/AndroidRuntime( 1695): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1695): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1695): at android.app.ActivityThread.main(ActivityThread.java:4627)
E/AndroidRuntime( 1695): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1695): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 1695): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime( 1695): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime( 1695): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 1695): Caused by: java.lang.UnsatisfiedLinkError: Library kineto not found
E/AndroidRuntime( 1695): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/AndroidRuntime( 1695): at java.lang.System.loadLibrary(System.java:557)
E/AndroidRuntime( 1695): at com.android.kineto.kineto.<clinit>(kineto.java:1552)
E/AndroidRuntime( 1695): ... 15 more
W/ActivityManager( 167): Force finishing activity com.android.kineto/.kineto
W/ActivityManager( 167): Activity pause timeout for HistoryRecord{46506b50 com.android.kineto/.kineto}
I/ActivityManager( 167): No longer want com.google.android.apps.uploader (pid 653): hidden #16
I/Process ( 1695): Sending signal. PID: 1695 SIG: 9
W/InputManagerService( 167): Window already focused, ignoring focus gain of: [email protected]
I/ActivityManager( 167): Process com.android.kineto (pid 1695) has died.
Not sure if this is relevant but earlier in the logcat...
Code:
W/PackageManager( 167): Not granting permission android.permission.DEVICE_POWER to package com.android.kineto (protectionLevel=2 flags=0x48444)
W/PackageManager( 167): Not granting permission android.permission.UPDATE_DEVICE_STATS to package com.android.kineto (protectionLevel=2 flags=0x48444)
W/PackageManager( 167): Unknown permission android.permission.INJECT_EVENT in package com.android.kineto
Having looked at some other posts regarding the T-Mobile US UMA app, which is also Kineto based I think it will take a lot of work to get this functioning. It appears to need some libraries such as...
libkento
linganril
librilswitch
and also some changes to the kernel as per this thread
http://forum.xda-developers.com/showthread.php?t=807116
I don't know if this was ever ported to devices other than the N1. It is shame that it requires more than just an app. Orange should be pushing this to all Android handsets. I don't use my phone at home for calls or texts because the signal is too weak, this is a loss for both myself and Orange because they don't get to charge me for calls I don't make. My wife has a Vodafone Sure Signal box which is brilliant but Orange don't offer such a device...
Okay, I just had a little luck with the UMA application.
Not quite there yet though.
BASICALLY, I have come to understand that the application extracted from various Roms FC cuz they are missing other files they depend on from the ROM.
I was using Orange Signal Boost apk from the Orange Desire S rom (am attaching it) on my HTC Legend.
Then I came across stories of someone in US who had extracted an apk from so Tmobile Rom for wifi calling and made it to work on a Nexus 1. I downloaded that files (also attached). This file was a modded version of original apk and had all the dependant files. (and consequently was 3mb vs 600kb of Orange signal boost)
So what I tried was
1. Install tmobile wifi app
2. Install Orange signal boost on TOP of it. It will ask you that this progam will replace another older program on your phone. Clcik okay.
3. What this does is leave old installed files needed from tmobile app and this time LO AND BEHOLD, signal boost app launches without FC
Here comes the problem though, it doesnt work, cuz somewhere hardcoded in the files that the tmobile app installs is the network info and naturally, our sims being orange are recognized as invalid sim.
Me and a LOT of other people would REALLY appreciate it if someone with any knowhow can look at this and figure it out for us
Hi at all guys.
I'm trying to make a kernel manager for my phone (i9070) . I've already made a kernel manager but this time I wanted to change the theme and I tried to do something with fragments...silly
The app is made of a main layout and a sliding menu, swipable from left to right, this has 5 buttons. Each button opens a different fragment.
Well the layout works good but I'm having problems with checkbox in a fragment. When I click on it, the app force close. When I click on the checkbox the app should set a value in a system file but in this case the app fc. I really don't know what to do.
Can anyone take a look on these files? And maybe to say to me what's wrong..help me
Here is the terminal log:
Code:
Process: info.androidhive.slidingmenu, PID: 2458
java.lang.RuntimeException: An error occured while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:300)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:355)
at java.util.concurrent.FutureTask.setException(FutureTask.java:222)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:841)
Caused by: java.lang.RuntimeException: Can't create handler inside thread that has not called Looper.prepare()
at android.os.Handler.<init>(Handler.java:200)
at android.os.Handler.<init>(Handler.java:114)
at android.app.Activity.<init>(Activity.java:765)
at info.androidhive.slidingmenu.Cpu.<init>(Cpu.java:20)
at info.androidhive.slidingmenu.SU.doInBackground(Utils.java:131)
at info.androidhive.slidingmenu.SU.doInBackground(Utils.java:118)
at android.os.AsyncTask$2.call(AsyncTask.java:288)
Hello people. I would like some advice on my problem.
Currently using JB 4.2.1 Ultralight 3.6 ROM along with Experimental V12 Kernel.
Although the keyboard works perfectly otherwise, once I choose Greek language along with the English one,
I get constant FCs. The keyboard won't even open.
I provide the logcat of the error for troubleshooting purposes.
Thanks in advance for all the replies! :good:
Code:
[ 03-11 06:59:19.297 5392: 5392 D/TextInput::Requirement ]
xt9-engine-database-id = 2130968817
[ 03-11 06:59:19.297 5392: 5392 E/AndroidRuntime ]
FATAL EXCEPTION: main
java.lang.RuntimeException: result:10
at com.sonyericsson.textinput.uxp.model.xt9.XT9Engine.XT9Engine_setActiveLanguage(Native Method)
at com.sonyericsson.textinput.uxp.model.xt9.XT9Engine.setLanguage(XT9Engine.java:482)
at com.sonyericsson.textinput.uxp.model.xt9.XT9Engine.initOptional(XT9Engine.java:644)
at com.sonyericsson.collaboration.ObjectBinder.init(ObjectBinder.java:448)
at com.sonyericsson.textinput.uxp.glue.InputMethodServiceGlue.bind(InputMethodServiceGlue.java:445)
at com.sonyericsson.textinput.uxp.glue.InputMethodServiceGlue.onStartInputView(InputMethodServiceGlue.java:393)
at android.inputmethodservice.InputMethodService.showWindowInner(InputMethodService.java:1420)
at android.inputmethodservice.InputMethodService.showWindow(InputMethodService.java:1378)
at android.inputmethodservice.InputMethodService$InputMethodImpl.showSoftInput(InputMethodService.java:422)
at android.inputmethodservice.IInputMethodWrapper.executeMessage(IInputMethodWrapper.java:184)
at com.android.internal.os.HandlerCaller$MyHandler.handleMessage(HandlerCaller.java:61)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4744)
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:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
at dalvik.system.NativeStart.main(Native Method)
I can provide a more extensive logcat if needed but I think that's the main problem described above.
anyone? :3
Turns out the dictionary lib for the greek language was missing. so I just placed it under /usr/xt9. I hope this helps someone in case they have the same problem.
Hi,
Ive decompiled the miui camera (miui 12, Redmi Note 8 Pro) and have recompiled it and included some libs, I have renamed the package and a few permissions (is this the cause of the error?) so as not to cause conflicts with the system camera app. I run into a problem with registerMarshalQueryable.. which from what I can tell is a camera2 method/class, so really it should just be there in the system, unless its looking in the wrong place?
Below is the error
2020-09-06 16:11:26.182 2694-2694/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.android.newcamera, PID: 2694
java.lang.NoSuchMethodError: No static method registerMarshalQueryable(Landroid/hardware/camera2/marshal/MarshalQueryableV in class Landroid/hardware/camera2/marshal/MarshalRegistry; or its super classes (declaration of 'android.hardware.camera2.marshal.MarshalRegistry' appears in /system/framework/framework.jar)
at com.android.camera2.vendortag.struct.MarshalQueryableRegister.preload(MarshalQueryableRegister.java:1)
at com.android.camera.CameraAppImpl.onCreateApplicationDelegate(CameraAppImpl.java:11)
at com.android.camera.CameraAppImpl.onCreateApplicationDelegate(CameraAppImpl.java:1)
at miui.external.Application.attachBaseContext(Application.java:4)
at android.app.Application.attach(Application.java:376)
at android.app.Instrumentation.newApplication(Instrumentation.java:1156)
at android.app.LoadedApk.makeApplication(LoadedApk.java:1222)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6562)
at android.app.ActivityThread.access$1500(ActivityThread.java:230)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1911)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:224)
at android.app.ActivityThread.main(ActivityThread.java:7551)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:539)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:995)
Click to expand...
Click to collapse