[Q] DualTouch ->OpenGL error? (slade87) CM6 [MiniCM/CM6v2] - Sony Ericsson XPERIA X10 Mini

Hi there guys im new to xda, i wanted to say first at all thanks for this great work for xperia10 mini pro, im CM user for about 6 months for Milestone and now for mini pro, today i am testing slade87 ROM last vertion, dual touch works incredible cool, as you all shouls already know. thanks for that.
now my issue its with games using Opengl, there is a OpenGL error log
Code:
glError(GLES): 0x500
, for 3d games, i would like to know if i there is any fix for that, my first try was to disable JIT but not succes, the bug is.
at the very beggining of 3d render games crash.
also i read almost all the posts in the main thread for this rom, but as im new i cant post there yet,i see one guy asking about this, i wonder if there is other place where this is exaplained.
Thanks in advance.

run out of ideas
Hi well i tried opengl es examples and they work really well, its really weird this error.
it happens to me with polarbit games.
Edit: Well i decided to continue with post reading, i though it was related with the version fo the rom, also tried erasing data and cache, ... so i decided to start from flashing SEUS and then roms i tried all posible cm6 version i even tried owein94 final version, any way i was not able to play 3d games.
finally i decided to start some debugging after this i find the thing. i dont know if this bug its currently reported, but the main idea i have is that multitouch support for this rom tears down touch for 3d games, i can play the game if i use keyboard, but when i hit the screen game is down.
here is the logcat error result:
Code:
ERROR/AndroidRuntime(11640): java.lang.NoSuchMethodError: android.view.MotionEvent.getSource
ERROR/AndroidRuntime(11640): at com.polarbit.fuse.FuseTouch$Gingerbread.onTouchEvent(FuseTouch.java:206)
ERROR/AndroidRuntime(11640): at com.polarbit.fuse.MainTask$RenderSurface.onTouchEvent(MainTask.java:486)
ERROR/AndroidRuntime(11640): at android.view.View.dispatchTouchEvent(View.java:3812)
ERROR/AndroidRuntime(11640): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:863)
ERROR/AndroidRuntime(11640): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:863)
ERROR/AndroidRuntime(11640): at com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchTouchEvent(PhoneWindow.java:1671)
ERROR/AndroidRuntime(11640): at com.android.internal.policy.impl.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1107)
ERROR/AndroidRuntime(11640): at android.app.Activity.dispatchTouchEvent(Activity.java:2086)
ERROR/AndroidRuntime(11640): at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:1655)
ERROR/AndroidRuntime(11640): at android.view.ViewRoot.handleMessage(ViewRoot.java:1785)
ERROR/AndroidRuntime(11640): at android.os.Handler.dispatchMessage(Handler.java:99)
ERROR/AndroidRuntime(11640): at android.os.Looper.loop(Looper.java:123)
ERROR/AndroidRuntime(11640): at android.app.ActivityThread.main(ActivityThread.java:4627)
ERROR/AndroidRuntime(11640): at java.lang.reflect.Method.invokeNative(Native Method)
ERROR/AndroidRuntime(11640): at java.lang.reflect.Method.invoke(Method.java:521)
ERROR/AndroidRuntime(11640): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
ERROR/AndroidRuntime(11640): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
ERROR/AndroidRuntime(11640): at dalvik.system.NativeStart.main(Native Method)
for me sounds like the new dual touch driver its not for 3d games?
come guys some help here please

Related

[Solved] Compiling Apps Problem

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] LG Optimus One - Orange UK Original ROM

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

[ROM][10/03/12] JetStream_2.03.10_OsiMood - Light gets Lighter

I am very happy to propose you my first custom rom for the HTC JetStream!​ This rom is based on the released rom from AT&T 1.30.502.1 and should work for both American and Canadian tabs. The system has been made as light as possible and all "unnecessary" application has been removed.READ CAREFULLY:
This rom does NOT include any kernel but works exclusively with DoomLord Kernel v1
Installing this rom will WIPE your device but can be done if this feature is needed
You need [URL="http://forum.xda-developers.com/showthread.php?t=1418084"]ClockWorkMOD [/URL]to install this ROM
You are doing this at your own risks
Rom Description:
This rom is my daily driver, I like my tablet, clean without any bloatware or unneccessary app or widgets from AT&T or HTC
Zipaligned / Deodexed
Rooted - latest version
Removed all unnecessary applications - see second post
Latest version 2.03.10:
Careful, this version will WIPE your device, make a backup!​
Careful, the new version will WIPE your phone, make a backup!​
​I am not asking for donation but press the thanks button and please Vote for this thread too​Credits:
DooMLoRD for the kernel and CWM
mendozinas, for his online kitchen
dsixda, for his kitchen
Before asking a question, use this button
{
"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"
}
and watch this , thanks:
v2.03.10
New Boot animation
Roboto fonts included
Battery in %
Ad-Away an No-Frill included
All bloatware removed
Phone functions enabled
Tethering activated
Rooted
Latest Market
Busybox installed
Zipaligned
Fully de-odexed
Frequently Asked Questions:​
Will this rom work with the default kernel?
Most probably yes but...
Wi-Fi will be broken
Can I revert to the default kernel on this rom?
Yes now you can! but follow the steps and I won't babysit
Download the file from my site called: Jetstream_OsiMood_DefaultKernelFiles.rar
Inside you will find 2 files JetStream_OsiMood_DefaultKernel_WiFi_Module.zip and defaultBoot.img
Once those two files unzipped in a folder
Move the zip file to your SD-Card
Once done, reboot in bootloader: adb reboot bootloader
Now time to flash the default kernel: fastboot flash boot defaultBoot.img
Now go in recovery and install the attached zip, the patch will install the correct WiFi module and wipe your cache
Reboot, you have now the default kernel running and WiFi working
Try to reboot in recovery if it does not work just re-install the DooMLoRD recovery
Nice work - looking forward to flashing this tonight!
FYI - Link currently broken on DL page.
tyrannos said:
Nice work - looking forward to flashing this tonight!
FYI - Link currently broken on DL page.
Click to expand...
Click to collapse
I know for the link, working on it... will let you know when back up
it's great to see some movement here. one question - why must it work with doomlords kernel? that thing is quite unstable..
guru_shastri said:
it's great to see some movement here. one question - why must it work with doomlords kernel? that thing is quite unstable..
Click to expand...
Click to collapse
Simply because it is working smoothly for me @1.8ghz and that is more than enough
The link is up
Downloading now, looking forward to trying this one!
Wait, so this will still work with the stock kernel, right?
guru_shastri said:
it's great to see some movement here. one question - why must it work with doomlords kernel? that thing is quite unstable..
Click to expand...
Click to collapse
Gotta agree here, its great to see a custom rom for this device but after spending an hour reverting and wiping back to stock kernel just yesterday because of 2 weeks of rebooting and freezes with the custom kernal, I'd be really hesitant to go back to it.
I would absolutely love to see an option to stick with stock kernel if possible. Thanks for the work on this rom, its great to finally see some movement on this forum!
Sent from my HTC PG09410 using XDA
dcd17 said:
Gotta agree here, its great to see a custom rom for this device but after spending an hour reverting and wiping back to stock kernel just yesterday because of 2 weeks of rebooting and freezes with the custom kernal, I'd be really hesitant to go back to it.
I would absolutely love to see an option to stick with stock kernel if possible. Thanks for the work on this rom, its great to finally see some movement on this forum!
Sent from my HTC PG09410 using XDA
Click to expand...
Click to collapse
I am going to see what I can do for that as it seems I am also facing some random reboots
Market
Hello. Thanks, finally somebody have action, good to see people taking time to work with this great device.
I just download your rom and installed and runs very smooth and clean. One issue tho, the Market aka Google Play is giving me an error FC
D/AndroidRuntime( 3044): Shutting down VM
W/dalvikvm( 3044): threadid=1: thread exiting with uncaught exception (group=0x4001c798)
E/AndroidRuntime( 3044): FATAL EXCEPTION: main
E/AndroidRuntime( 3044): java.lang.NullPointerException
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.Sha1Util.secureHash(Sha1Util.java:46)
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.FinskyLog.scrubPii(FinskyLog.java:57)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.recordPackageInstalled(Reconstructor.java:139)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.reconstruct(Reconstructor.java:109)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.updateFromReconstruct(ReconstructDatabaseService.java:135)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.access$000(ReconstructDatabaseService.java:26)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:68)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:49)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:141)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:40)
E/AndroidRuntime( 3044): at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:113)
E/AndroidRuntime( 3044): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 3044): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 3044): at android.os.Looper.loop(Looper.java:152)
E/AndroidRuntime( 3044): at android.app.ActivityThread.main(ActivityThread.java:4606)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invoke(Method.java:491)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 3044): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 300): Force finishing activity com.android.vending/com.google.android.finsky.activities.TosActivity
W/ActivityManager( 300): Force finishing activity com.android.vending/.AssetBrowserActivity
D/ActivityManager( 300): isSketcherDisabledInCurrentTask():false, ActivityRecord{40a49db8 com.android.vending/com.google.android.finsky.activities.TosActivity}
D/ViewRoot( 300): ## mIsSketcherDisabledInCurrentTask is false
D/WindowManager( 300): call linkToDeath, this=Window{4114a998 Sorry! paused=false}
dcd17 said:
Gotta agree here, its great to see a custom rom for this device but after spending an hour reverting and wiping back to stock kernel just yesterday because of 2 weeks of rebooting and freezes with the custom kernal, I'd be really hesitant to go back to it.
I would absolutely love to see an option to stick with stock kernel if possible. Thanks for the work on this rom, its great to finally see some movement on this forum!
Click to expand...
Click to collapse
You can now roll back to the default kernel
juannicolas said:
Hello. Thanks, finally somebody have action, good to see people taking time to work with this great device.
I just download your rom and installed and runs very smooth and clean. One issue tho, the Market aka Google Play is giving me an error FC
Code:
D/AndroidRuntime( 3044): Shutting down VM
W/dalvikvm( 3044): threadid=1: thread exiting with uncaught exception (group=0x4001c798)
E/AndroidRuntime( 3044): FATAL EXCEPTION: main
E/AndroidRuntime( 3044): java.lang.NullPointerException
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.Sha1Util.secureHash(Sha1Util.java:46)
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.FinskyLog.scrubPii(FinskyLog.java:57)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.recordPackageInstalled(Reconstructor.java:139)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.reconstruct(Reconstructor.java:109)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.updateFromReconstruct(ReconstructDatabaseService.java:135)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.access$000(ReconstructDatabaseService.java:26)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:68)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:49)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:141)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:40)
E/AndroidRuntime( 3044): at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:113)
E/AndroidRuntime( 3044): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 3044): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 3044): at android.os.Looper.loop(Looper.java:152)
E/AndroidRuntime( 3044): at android.app.ActivityThread.main(ActivityThread.java:4606)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invoke(Method.java:491)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 3044): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 300): Force finishing activity com.android.vending/com.google.android.finsky.activities.TosActivity
W/ActivityManager( 300): Force finishing activity com.android.vending/.AssetBrowserActivity
D/ActivityManager( 300): isSketcherDisabledInCurrentTask():false, ActivityRecord{40a49db8 com.android.vending/com.google.android.finsky.activities.TosActivity}
D/ViewRoot( 300): ## mIsSketcherDisabledInCurrentTask is false
D/WindowManager( 300): call linkToDeath, this=Window{4114a998 Sorry! paused=false}
Click to expand...
Click to collapse
No clue why, empty the cache of the app and try again
This is going to sound stupid but how do you boot the device in recovery? I've loaded CWM through adb but any button combo won't work. I would really like to test out this ROM, thanks for any help!
for CWM - reset the device - and after the screen goes black press and hold vol. down.
so to install this rom we need to install the doomlord kernel and then go back to stock? or we can just install it over the stock?
can anyone actually work with the doomlord kernel to improve it? i think it was great at its base..perhapes just removing the voltage control..i think that's the problem it had.
CarpeNoctem said:
You can now roll back to the default kernel
No clue why, empty the cache of the app and try again
Click to expand...
Click to collapse
Tried that but since the app have never being opened there is no clean/clear cache option active for it.
NJFM said:
This is going to sound stupid but how do you boot the device in recovery? I've loaded CWM through adb but any button combo won't work. I would really like to test out this ROM, thanks for any help!
Click to expand...
Click to collapse
the simplest way, install this: https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en
CarpeNoctem said:
I am going to see what I can do for that as it seems I am also facing some random reboots
Click to expand...
Click to collapse
I really don't think the level is the issue. my Jetstream ran the MOST STABLE with Doomlords kernel. I had more random reboots before I ever rooted it or anything. I think Honeycomb just sux or maybe the version of Sense we have over Honeycomb sux and is waaaaay underdeveloped from factory. just my 2 cents....
Sent from my HTC Rezound™ using xda premium
k2trill said:
I really don't think the level is the issue. my Jetstream ran the MOST STABLE with Doomlords kernel. I had more random reboots before I ever rooted it or anything. I think Honeycomb just sux or maybe the version of Sense we have over Honeycomb sux and is waaaaay underdeveloped from factory. just my 2 cents....
Click to expand...
Click to collapse
Now you have the choice at least you, stock or DooMLoRD
its a fact that some devices sufford random reboots only when using the kernel. i think the kernel has a great base, and my device never ran faster - but it still crashed him.
i think it's got something to do with the Voltage control, but i can't really be sure.

[Q] XSola Jelly Bean Greek language Keyboard FC

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.

NoSuchMethodError when running recompiled app

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

Categories

Resources