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.
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
Hi.
Summary: the AndroidRuntime process fails when starting the Connectivity Service, causing my phone into a boot loop.
Sorry for the very verbose post.
Background: I've spent quite a bit of time trying to resolve a problem that causes my Sony Ericsson Xperia X10 Mini (from O2) to go into a boot loop. I've rooted the phone some time ago using this process: (sorry the forum prevents me from posting link, please copy and paste this: android.doshaska.net/x10miniroot).
I then proceeded to remove some of the redundant programs from /system/app.
Everything worked fine for several weeks until the phone started complaining about the storage being filled up. I could see that /data was getting full and I suspected that the K9 email client I had installed was using lots f space to keep the IMAP folders synced.
I can't remember if the phone rebooted itself or if I did it manually, but it never managed to boot up again, and is ever since stuck at the Sony Ericsson logo.
adb logcat tells me that the AndroidRuntime process fails when starting the Connectivity Service. It's stuck in this loop, but I've isolated one single loop in the attachment logcat.txt. The crash file references has been attached as 1279210811.txt.
The final fatal crash is:
I/SystemServer( 1297): Starting Connectivity Service.
W/dalvikvm( 1297): threadid=51: thread exiting with uncaught exception (group=0x2aac9a28)
E/AndroidRuntime( 1297): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception
E/AndroidRuntime( 1297): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 1297): java.lang.NullPointerException
E/AndroidRuntime( 1297): at android.app.ActivityThread.getProvider(ActivityThread.java:3938)
E/AndroidRuntime( 1297): at android.app.ActivityThread.acquireProvider(ActivityThread.java:3967)
E/AndroidRuntime( 1297): at android.app.ApplicationContext$ApplicationContentResolver.acquireProvider(ApplicationContext.java:1527)
E/AndroidRuntime( 1297): at android.content.ContentResolver.acquireProvider(ContentResolver.java:579)
E/AndroidRuntime( 1297): at android.content.ContentResolver.query(ContentResolver.java:147)
E/AndroidRuntime( 1297): at android.provider.Settings$NameValueCache.getString(Settings.java:476)
E/AndroidRuntime( 1297): at android.provider.Settings$Secure.getString(Settings.java:1701)
E/AndroidRuntime( 1297): at android.provider.Settings$Secure.getInt(Settings.java:1741)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.getPersistedNetworkPreference(ConnectivityService.java:182)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:123)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:47)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:87)
I've had a look at the JavDoc for android.app.ActivityThread.getProvider, but I've not been able to find any useful information. I have to guess that the start-up process fails to read the provider (network) specific settings for some reason. I don't have a clue whether the source is a file, database or something else.
A wild guess is that something got corrupted when the data partition filled up. There are some upset earlier in the log (line 180) when the PackageManager is reading an XML file that relates to the PackageManager settings that seems to have been corrupted:
E/PackageManager( 1297): Error reading package manager settings E/PackageManager( 1297): org.xmlpull.v1.XmlPullParserException:
Premature end of document. (position:line -1, column -1) caused by:
org.apache.harmony.xml.ExpatParser$ParseException: At line 1, column 0: no element found
I've seen a few similar posts, but nothing exactly like this nor anything that I could use to resolve it.
Stupid section
I've got myself into this through a combination of stupidity and bad luck. I've backed up all .APK that I've removed and created a log of what I removed (that I'm still looking for). I thought this was all that I needed and I don't have a full backup.
Unfortunately, the root access now gives me a segmentation fault and the root process requires the GUI to work, so I can't repeat the process. I don't want to try another root process before I've tried what I can to get the phone back in a reasonable state.
Fortunately, I still have full adb access, so I have visibility and some control over the phone.
Any help on this would be much appreciated. At least I've saved you the time pointing out that I'm an idiot not doing a full backup
Regards,
Dan
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
ParanoidAndroid build from sources with the new 2.6.53 kernel from TheWhisp; see more detail about this project on http://www.paranoid-rom.com/
please, when you have a problem, attach a logcat
-How to install:
Transfer the .zip file to your SD card
Reboot into ClockworkMod, choose the option Install zip from sdcard -> choose zip from sdcard. Select the current release, and confirm the update by selecting Yes.
Reboot and enjoy!
Remember: if you come from any other version of android that isn't PA jb (or PA jb based) you'll have to wipe data from CWMR
-Gapps:
use jb-20121017-KonstaKANG on modaco
http://www.mediafire.com/?qscnhfuadsujki1
-How to check file's hash:
i recommed you to install hashtab, so just right-click on the file, click propriety and go to hash file tab
-2.99:
updated to android 4.2
it uses modified libstagefright from Rashed97
built whit gcc 4.6 + some trick to reduce apk size
hash: [md5sum] 3f572d3b240ad124f35e93bd0aa240e1
http://depositfiles.com/files/4m6sx4gre
-2.55:
first release, see what works/not works down here
http://depositfiles.com/files/spbfpz8xj
Working:
2D & 3D acceleration with triple-buffering (Butter UI)
Camera (Barcode Scanner mode also works)
GPS
Headset
Lights
Sensors
Touchscreen
USB Mass Storage
keys
Not Working:
Telephony (calling, mobiledata & messaging)
bluetooth
wifi
sdcard isn't recognized
Partially working:
Video camera (can capture video, but saved media will have artifacts/low FPS)
OMX video encoders/decoders
Not working:
USB tethering
Wifi tethering
Thanks to:
Motafoca
TheWhisp, squadzone & all contributors associated with the shared Samsung msm7x27 jellybean kernel & device config used as a base for the galaxy5 port
nend for MAD Manager & general assistance
KonstaT for his reduced gapps-jb package
Rashed97 for his modified libstagefright
richie161cfc (madteam) for testing many test build
All other testers for your patience & support - thank you.
Good work and thanks! :thumbup:
Sent from my GT-S5360 using xda premium
XdaNoob98 said:
Good work and thanks! :thumbup:
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
thanks; did you tested it? if yes can you attach a logcat?
thenks. currently downloading
---------- Post added at 06:03 PM ---------- Previous post was at 05:04 PM ----------
First of all checked wifi but was not able to find my network. Now when I tried to dial a number it just dropped the call after 10 secs without connecting. There is also no ringing tone on incoming call. Cancel call button long press is not showing the boot menu so I don't know how to reboot it without a battery pull. Pressing home button is doing nothing. Rebooted by battery pull but same issues.
---------- Post added at 06:51 PM ---------- Previous post was at 06:03 PM ----------
Well, now I am unable to reboot into recovery for a nand restore as reboot is not working and I cannot do it with odin as I have installed ubuntu and removed windows. Can you help me with this?
sixline said:
thenks. currently downloading
---------- Post added at 06:03 PM ---------- Previous post was at 05:04 PM ----------
First of all checked wifi but was not able to find my network. Now when I tried to dial a number it just dropped the call after 10 secs without connecting. There is also no ringing tone on incoming call. Cancel call button long press is not showing the boot menu so I don't know how to reboot it without a battery pull. Pressing home button is doing nothing. Rebooted by battery pull but same issues.
---------- Post added at 06:51 PM ---------- Previous post was at 06:03 PM ----------
Well, now I am unable to reboot into recovery for a nand restore as reboot is not working and I cannot do it with odin as I have installed ubuntu and removed windows. Can you help me with this?
Click to expand...
Click to collapse
thanks for reporting, to fix button problem you can try to substitute the folder usr inside system with the one from psyke's cm10
for wifi try substitude the folder wifi with the one from psyke's cm10
next update will fix them all; can you attach a logcat?
manuel100 said:
thanks; did you tested it? if yes can you attach a logcat?
Click to expand...
Click to collapse
Perhaps (I think its "perhaps" or is it "unfortunately" ) my G5 is actually bricked but i'll get it back soon and i'll give logcat asap ok?
Sent from my GT-S5360 using xda premium
Yeah sure I can try those but I have a very slow internet connection.Can you upload these folders? And I am still trying to get into recovery...
XdaNoob98 said:
Perhaps (I think its "perhaps" or is it "unfortunately" ) my G5 is actually bricked but i'll get it back soon and i'll give logcat asap ok?
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
ok
Yeah sure I can try those but I have a very slow internet connection.Can you upload these folders? And I am still trying to get into recovery...
Click to expand...
Click to collapse
here: http://depositfiles.com/files/0edassb32
i need a logcat for the sound problem
updated the rom to pa 2.99 (4.2), i need some testers and many logcats
Like i said i will test it a give logcats in six days if it isn't too long?
Sent from my GT-S5360 using xda premium
I tested your rom, stuck on boot animation, after 10 minutes repeating the boot animation, the phone finally booted, a android phone fc notification appears, and when i press ok, it's appears again, here is a logcat.
IDntKnwHowUse said:
I tested your rom, stuck on boot animation, after 10 minutes repeating the boot animation, the phone finally booted, a android phone fc notification appears, and when i press ok, it's appears again, here is a logcat.
Click to expand...
Click to collapse
thanks fro testing, i'm trying to undestand why it fc; any information is useful
@XdaNoob98; don't worry, attach it when you can
here's the error with phone, extracted from IDntKnwHowUse's logcat:
E/AndroidRuntime( 2510): FATAL EXCEPTION: main
E/AndroidRuntime( 2510): java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.android.internal.telephony.SamsungMSMRIL
E/AndroidRuntime( 2510): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4384)
E/AndroidRuntime( 2510): at android.app.ActivityThread.access$1300(ActivityThread.java:145)
E/AndroidRuntime( 2510): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1271)
E/AndroidRuntime( 2510): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 2510): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 2510): at android.app.ActivityThread.main(ActivityThread.java:4978)
E/AndroidRuntime( 2510): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2510): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 2510): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 2510): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime( 2510): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 2510): Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.android.internal.telephony.SamsungMSMRIL
E/AndroidRuntime( 2510): at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:155)
E/AndroidRuntime( 2510): at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:59)
E/AndroidRuntime( 2510): at com.android.phone.PhoneApp.onCreate(PhoneApp.java:470)
E/AndroidRuntime( 2510): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:999)
E/AndroidRuntime( 2510): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4381)
E/AndroidRuntime( 2510): ... 10 more
E/AndroidRuntime( 2510): Caused by: java.lang.ClassNotFoundException: com.android.internal.telephony.SamsungMSMRIL
E/AndroidRuntime( 2510): at java.lang.Class.classForName(Native Method)
E/AndroidRuntime( 2510): at java.lang.Class.forName(Class.java:217)
E/AndroidRuntime( 2510): at java.lang.Class.forName(Class.java:172)
E/AndroidRuntime( 2510): at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:148)
E/AndroidRuntime( 2510): ... 14 more
E/AndroidRuntime( 2510): Caused by: java.lang.NoClassDefFoundError: com/android/internal/telephony/SamsungMSMRIL
E/AndroidRuntime( 2510): ... 18 more
E/AndroidRuntime( 2510): Caused by: java.lang.ClassNotFoundException: com.android.internal.telephony.SamsungMSMRIL
E/AndroidRuntime( 2510): at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:61)
E/AndroidRuntime( 2510): at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
E/AndroidRuntime( 2510): at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
E/AndroidRuntime( 2510): ... 18 more
W/ActivityManager( 1494): Process com.android.phone has crashed too many times: killing!
I/Process ( 2510): Sending signal. PID: 2510 SIG: 9
I/ActivityManager( 1494): Process com.android.phone (pid 2510) has died.
Click to expand...
Click to collapse
OK I'm so exited because paranoid is the best rom for me:thumbup:
Sent from my GT-S5360 using xda premium
Paranoid Android doesn't work! It boots after 10 minutes. FC's on telephony every second
Sent from my GT-I5500 using xda premium
manuel100 said:
thanks fro testing, i'm trying to undestand why it fc; any information is useful
@XdaNoob98; don't worry, attach it when you can
here's the error with phone, extracted from IDntKnwHowUse's logcat:
Click to expand...
Click to collapse
You have to point the RIL to boardconfig. As I said here:
Paul L. said:
Is the RIL working? You can make it work by pasting the propietary RIL java class to the optional telephony package and pointing it out in the boardconfig by using the example from the lastest commit from codeworkx to the CM10.1 staging branch
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Which, by the way, it's not enough. You will have to adapt SamsungMSMRIL to Android 4.2
Why don't you ask some other developers to help you? Or simply post it to madteam?
Sent from my superphone in 2000 BC
How on earth has this been released IV never seen such a mess of a rom, the most important parts don't work and people are flashing this when its unusable really and your asking them to logcat for you lol if your going to make a rom use cm7 there isn't any faults and its a good easier starting block for adding and customizing I would remove this rom or at least the download link until the faults are fixed
Sent from my GT-S5830 using xda premium
brewy said:
How on earth has this been released IV never seen such a mess of a rom, the most important parts don't work and people are flashing this when its unusable really and your asking them to logcat for you lol if your going to make a rom use cm7 there isn't any faults and its a good easier starting block for adding and customizing I would remove this rom or at least the download link until the faults are fixed
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Well, the dev's doing the right thing. He is building the ROM from source code, not change/theming someone else's work!. He is doing the right thing asking for logcats. That is how its actually done!.
You might not have been here when development on cm7 started. It was pretty bad. Everything was broken/not working. Psyke eventually fixed everything and made it what it is now.
So stop your nonsense talk and try contributing to the development.
Sent from my GT-I9300 using xda-developers app
Hello thanks for your work bro why not you come to madteam , there you will get more tester and your development goes more fast.
Hey guyz having a doubt,
If i try to port a rom of a single camera smartphone to a dual camera phone
what are the changes to be made to the files???
is it relared to modules or kernel changes??
Also tell what are the files needed to be replaced from base to port??
i tried replacing the libs and i personally think some issue with boot.img if so tell me what are the changes to be made to init.rc of the boot.img??
thx in advance !!!
This is the logcat when i tried opening camera
Logcat :
E/CameraClient(111): Invalid setDisplayOrientation degrees=40
E/AndroidRuntime(1593): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime(1593): java.lang.RuntimeException: set display orientation failed
E/AndroidRuntime(1593): at android.hardware.Camera.setDisplayOrientation(Native Method)
E/AndroidRuntime(1593): at com.mediatek.camera.AndroidCamera.setDisplayOrientation(AndroidCamera.java:111)
E/AndroidRuntime(1593): at com.android.camera.CameraManager$CameraHandler.handleMessage(CameraManager.java:199)
E/AndroidRuntime(1593): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(1593): at android.os.Looper.loop(Looper.java:153)
E/AndroidRuntime(1593): at android.os.HandlerThread.run(HandlerThread.java:60)
E/AppErrorDialog(489): Failed to get ILowStorageHandle instance
Main culprit :
E/IspHal(111): [init]Err( 461):mpMcuDrv->init() fail