As most of you probably are, ever since i've tried CM11, i've been searching for a "stable" KitKat rom. Didn't have much luck, but i thought i'll share my findings
First up is Gummy Rom from Team Gummy, which i didn't even see in the Android Development subforum. They're doing nightlies for the P930, but seem to have some problems right now, as the last nightly is dated 01-05-2014. You can check those out at
http://old.androidfilehost.com/main/Team_Gummy/p930/nightly/
Second one is MoKee, of which navik did a 4.3 build, but they also have KitKat nightlies for the P930.
http://download.mfunz.com/?device=p930
On to what you'll probably want to know.. do these roms work? well... kinda...
The MoKee "Release" from 01-18-2014 is pretty stable, fast and has some neat additions from CM and (possibly) AOKP. You can even finally restore your backups from Titanium, as MoKee lets you choose where to install (!) an apk... change that to internal from default and ALL apps install correctly like they should. Now for the downside... you can probably guess... yup, camera's broken *sad face panda*... you can start up any cam-app and it will show the image from the sensor, but as soon as you take a shot, it will FC and save a 2KB file in your DCIM folder...
oh, and it has some chinese crapware (baidu) installed, but you can easily remove these with Titanium Backup.
On to the second Rom... Gummy Rom from Team Gummy...it's a lean build based on AOSP with a few picks from CM, AOKP and PA, mostly visual stuff from aokp (center clock etc.) and HALO/PIE from PA. It's helluvalot fast and after a quick adb push for the newest adreno drivers, i can even play Asphalt 8 on High Details. Downside on this rom... apk install error galore, no XDA-app, some games don't install, browser crashes often, absolutely not a daily driver...
have fun experimenting, have you found something else? would like to know ^^
thanks for ur support and is like no much user+dev on this device! threads emty to compere to other devices....
dreaming of getting another device:crying:
I will have to try the later one myself, thanks for posting the info. The biggest issue is that cm is not stable so anything built on that rom is bound to have issues. Most people are sticking with jb for the time being until a better KitKat is available.
As far as activity on this forum, this is not a nexus device but it does have a fair following.
Sent using XDA Premium HD app
Nz
I thought I would look at the Mokee kernel, so the camera errors out like
Code:
I/QualcommCameraHardware( 147): stopPreviewInternal: old frame thread completed.
I/QualcommCameraHardware( 147): stopPreviewInternal X: 0
V/QualcommCameraHardware( 147): updatePictureDimension: 3264x2448 <- 960x720
V/QualcommCameraHardware( 147): initRaw E: picture size=3264x2448
V/QualcommCameraHardware( 147): initRaw: initializing mRawHeap.
E/QualcommCameraHardware( 147): ION allocation failed
E/QualcommCameraHardware( 147): do_mmap: Open device /dev/pmem_smipool failed!
E/QualcommCameraHardware( 147): ERROR : initraw , createSnapshotMemory failed
E/QualcommCameraHardware( 147): initRaw failed. Not taking picture.
E/CAM_AndroidCameraManagerImpl( 3247): take picture failed.
W/dalvikvm( 3247): threadid=16: thread exiting with uncaught exception (group=0x4156ec80)
E/AndroidRuntime( 3247): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 3247): Process: com.android.camera2, PID: 3247
E/AndroidRuntime( 3247): java.lang.RuntimeException: takePicture failed
A good picture taken with CM11 looks like
Code:
I/QualcommCameraHardware( 146): stopPreviewInternal: old frame thread completed.
I/QualcommCameraHardware( 146): stopPreviewInternal X: 0
V/QualcommCameraHardware( 146): updatePictureDimension: 3264x2448 <- 960x720
V/QualcommCameraHardware( 146): initRaw E: picture size=3264x2448
V/QualcommCameraHardware( 146): initRaw: initializing mRawHeap.
E/QualcommCameraHardware( 146): bool android::QualcommCameraHardware::createSnapshotMemory(int, int, bool, int) Raw memory index: 0 , fd is 67
E/QualcommCameraHardware( 146): Received following info for raw mapped data:0x44840000,handle:0x121eb48, size:11985408,release:0x405d6941
E/QualcommCameraHardware( 146): Registering buffer 0 with fd :67 with kernel
V/QualcommCameraHardware( 146): use_all_chnls = 0
As you can see the "ION allocation failed" is the obvious fail point, now where that is logged is the next big secret.. qcom/camera/qcamera2/hal/QCameraMemory.cpp has a log with the message in it, but changing the message seems to have no affect..
Other things I have tried, I have tried compiling the mokee with the hardware and kernel folders from CM11 - the camera still fails, so it must be with the device / vendor folders.
nz
Related
Hi guys, me again,
i just fixed Navigon Select to work with Gingerbread. It needs the replacement of libmedia because some interfaces got incompatible. Now i can finally use onboard Navigation on my CM7
Download
Just replace the file in /system/lib
cheers
Nice job, i don't use navigon just copilote, but I must congratulated you because you are making hardcore coding for HD2 scene.
Thanks
Cooooooooool !!! THX !!!
Ok, doesn't work for me ... :-/
Sent from my HTC HD2 using XDA App
cheezusweezel said:
Ok, doesn't work for me ... :-/
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Tell me what you get on logcat when Navigon starts up.. Using aLogcat from Market for example. And of course.. Update your Navigon Select to the latest version..
pack21 said:
Nice job, i don't use navigon just copilote, but I must congratulated you because you are making hardcore coding for HD2 scene.
Thanks
Click to expand...
Click to collapse
+1 your out of control, dude. Your an 86, just one more than me and you are making some major breakthroughs.. It makes me think I am really doing nothing with my life, lol.. But yeah, keep up the god work, man
Edit: I meant to say "good" work but swype has no problem also praising you it seems
Sent from my HTC HD2 using XDA App
Cool man, you rock!
Going to try to get Navigon to work following your instructions, now that you already fixed GPS.
[OT]:
Do you by chance also know how to fix camcorder for [email protected]?
I'm playing with PPC_SHIFTPDA_V2 [RAM] which i really like. Camcorder is one of the last issues i would like to fix.
[/OT]
Thanks! But no luck for me either!
gauner1986 said:
Tell me what you get on logcat when Navigon starts up.. Using aLogcat from Market for example. And of course.. Update your Navigon Select to the latest version..
Click to expand...
Click to collapse
Sure, latest version installed and logcat is:
I/ActivityThread( 1773): Pub com.navigon.navigator_select.provider.naviprovider: com.navigon.navigator_select.provider.NaviProvider
D/NaviApp ( 1773): pn: com.navigon.navigator_select
D/NaviApp ( 1773): NaviKernel hasn't been started yet, ignore...
D/dalvikvm( 1773): Trying to load lib /data/data/com.navigon.navigator_select/lib/libNavinative.so 0x4051cc28
I/System.out( 1773): Cannot load library: reloc_library[1311]: 147 cannot locate '_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i'...
I/System.out( 1773): Trying NavinativeD...
I/System.out( 1773): Couldn't load NavinativeD: findLibrary returned null
D/NaviKernelConnector( 1773): NaviKernelConf.ini pkg_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini ins_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini is up-to-date
I/ActivityManager( 187): Displayed com.navigon.navigator_select/.hmi.CheckExistingRegistrationActivity: +384ms
W/dalvikvm( 1773): threadid=9: thread exiting with uncaught exception (group=0x4001d560)
Awesome, it worked for me even with the old Navigon version. Thanks!
EDIT: nope, sorry. wrong information. it's not working. I guess, my GPS is not working either. Is there a gps test app? The one in market Force Closes when open in gingerbread
Could you guys try again with the file i attached? Maybe i uploaded the wrong one.
gnash.s said:
Awesome, it worked for me even with the old Navigon version. Thanks!
EDIT: nope, sorry. wrong information. it's not working. I guess, my GPS is not working either. Is there a gps test app? The one in market Force Closes when open in gingerbread
Click to expand...
Click to collapse
Use GPS Status from Market.
Nope, also the new file won't work (for me) ...
cheezusweezel said:
Sure, latest version installed and logcat is:
I/ActivityThread( 1773): Pub com.navigon.navigator_select.provider.naviprovider: com.navigon.navigator_select.provider.NaviProvider
D/NaviApp ( 1773): pn: com.navigon.navigator_select
D/NaviApp ( 1773): NaviKernel hasn't been started yet, ignore...
D/dalvikvm( 1773): Trying to load lib /data/data/com.navigon.navigator_select/lib/libNavinative.so 0x4051cc28
I/System.out( 1773): Cannot load library: reloc_library[1311]: 147 cannot locate '_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i'...
I/System.out( 1773): Trying NavinativeD...
I/System.out( 1773): Couldn't load NavinativeD: findLibrary returned null
D/NaviKernelConnector( 1773): NaviKernelConf.ini pkg_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini ins_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini is up-to-date
I/ActivityManager( 187): Displayed com.navigon.navigator_select/.hmi.CheckExistingRegistrationActivity: +384ms
W/dalvikvm( 1773): threadid=9: thread exiting with uncaught exception (group=0x4001d560)
Click to expand...
Click to collapse
So it has to work now.. I checked the .so file, the symbol is definetly present:
Code:
gauners-MacBook-Pro:~ gauner$ strings libmedia.so | grep "_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i"
_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i
_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_ii
Be sure to replace /system/lib/libmedia.so !
cheezusweezel said:
Nope, also the new file won't work (for me) ...
Click to expand...
Click to collapse
Could you check logcat again please?
Anyway.. I'll release a ROM based on CM7 soon.
Could you check logcat again please?
Anyway.. I'll release a ROM based on CM7 soon.
Click to expand...
Click to collapse
New logcat:
I/ActivityThread( 2812): Pub com.navigon.navigator_select.provider.naviprovider: com.navigon.navigator_select.provider.NaviProvider
D/NaviApp ( 2812): pn: com.navigon.navigator_select
D/NaviApp ( 2812): NaviKernel hasn't been started yet, ignore...
D/dalvikvm( 2812): Trying to load lib /data/data/com.navigon.navigator_select/lib/libNavinative.so 0x4051d788
I/System.out( 2812): Cannot load library: reloc_library[1311]: 147 cannot locate '_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i'...
I/System.out( 2812): Trying NavinativeD...
I/System.out( 2812): Couldn't load NavinativeD: findLibrary returned null
D/NaviKernelConnector( 2812): NaviKernelConf.ini pkg_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 2812): NaviKernelConf.ini ins_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 2812): NaviKernelConf.ini is up-to-date
W/dalvikvm( 2812): threadid=9: thread exiting with uncaught exception (group=0x4001d560)
I/Process ( 2812): Sending signal. PID: 2812 SIG: 9
And your ROM will be much appreciated !!!
gauner1986 said:
Anyway.. I'll release a ROM based on CM7 soon.
Click to expand...
Click to collapse
I read on mdj's thread that alot of ppl are complaining about lag in CM7, would you consider as AOSP release? Thanks soo much!!!
Had a FC when starting Navigon Select before applying the fixed library.
Replaced with your library now NS (&GPS) works without any problem!
Thx again!
Hopefully you guys did not forget to reboot? Otherwise i don't know!
another tip...
if you got a FC while starting Navigon Select, just remove the Navigon and reinstall it again
Should work afterwards.
Sounds like permission issues, check that the new files have the same permissions as others in the same folder.
Just tried this update with Navigon MobileNavigator on a Nexus S with Gingerbread(2.3.1) It's let me get past the spash screen without a FC. Just downloading the maps now. Hope the rest of the app doesn't have any other problems.
Many thanks for this fix.
(I did change the permissions and ownership of libmedia.so with these commands
chown root.root libmedia.so
chmod 644 libmedia.so
)
Rob
EDIT: Confirmed that this is working on my device. Thanks for a great fix.
Hi all,
Does anyone managed to compile latest CM 6.2 (froyo) sources?¿?¿. I get errors when compiling CMParts and if I choose not to compile CMParts, I get a package that gets me in to crash loops on first start.....
Many Thanks in Advance,
Perdita2000
perdita2000 said:
Hi all,
Does anyone managed to compile latest CM 6.2 (froyo) sources?¿?¿. I get errors when compiling CMParts and if I choose not to compile CMParts, I get a package that gets me in to crash loops on first start.....
Many Thanks in Advance,
Perdita2000
Click to expand...
Click to collapse
You need CMParts. Can you post the compilation errors?
These are my compile errors...
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:72: cannot find symbol
symbol : variable config_enableScreenOffAnimation
location: class com.android.internal.R.bool
getResources().getBoolean(com.android.internal.R.bool.config_enableScreenOffAnimation) ? 1 : 0) == 1);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:83: cannot find symbol
symbol : variable ACCELEROMETER_ROTATE_180
location: class android.provider.Settings.System
Settings.System.ACCELEROMETER_ROTATE_180, 0) == 1);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:96: cannot find symbol
symbol : variable ELECTRON_BEAM_ANIMATION_ON
location: class android.provider.Settings.System
Settings.System.ELECTRON_BEAM_ANIMATION_ON, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:102: cannot find symbol
symbol : variable ELECTRON_BEAM_ANIMATION_OFF
location: class android.provider.Settings.System
Settings.System.ELECTRON_BEAM_ANIMATION_OFF, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:108: cannot find symbol
symbol : variable ACCELEROMETER_ROTATE_180
location: class android.provider.Settings.System
Settings.System.ACCELEROMETER_ROTATE_180, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/UIActivity.java:125: cannot find symbol
symbol : variable OVERSCROLL_EFFECT
location: class android.provider.Settings.System
Settings.System.OVERSCROLL_EFFECT, 1);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/UIActivity.java:196: cannot find symbol
symbol : variable OVERSCROLL_EFFECT
location: class android.provider.Settings.System
Settings.System.putInt(getContentResolver(), Settings.System.OVERSCROLL_EFFECT,
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
11 errors
make: *** [out/target/common/obj/APPS/CMParts_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Many Thanks for you Help!!!
Perdita2000
I'm not modifyng any code because first compilation of any CM sources I always use source as is, then I try this created CM-untouched-sources rom and start to make changes (I am developing on CM7 and would like to have my own CM6.2 too...)
Many Thanks,
Perdita2000
I would check two things:
A. That you updated all the repositories. Do another "repo sync" to make sure everything is up to date. If you are using some repositories which you forked (or someone else) they also need to be updated "manually".
B. Do a clean build, by totally removing the "out" directory and then try to recompile it.
If you are still having trouble I can try to look into it, maybe even tonight.
Download froyo_stable CMParts,then it is no problem to compile,or I upload my modified CMParts 6.2.0 with setcpu etc... if you want that
This should fix the issue:
Code:
cd packages/apps/CMParts && git checkout 69613a248519fed7d971bd6292013d36097d0107
- taken from http://forum.cyanogenmod.com/topic/15353-froyo-compile-cannot-find-symbol-error/
At least, that fixed the issue for me.
erasmux said:
I would check two things:
A. That you updated all the repositories. Do another "repo sync" to make sure everything is up to date. If you are using some repositories which you forked (or someone else) they also need to be updated "manually".
B. Do a clean build, by totally removing the "out" directory and then try to recompile it.
If you are still having trouble I can try to look into it, maybe even tonight.
Click to expand...
Click to collapse
I have done A and B yet a few days ago, but nothing was solved and I found k0ner solution too, but It seems to solved compilation issue (can't find what patch 69613a248519fed7d971bd6292013d36097d0107 do?¿?¿, don't know how to search this code on git...) but ROM compiled doesn't boot (boot loop, but don't have error now, I will reproduce it and send logcat...).
Where can I find CMParts stable?¿?¿
Many Thanks to ALL,
Perdita2000
Elelinux, do you mean use froyo-stable branch for CMParts??
Many Thanks,
Perdits2000
perdita2000 said:
Where can I find CMParts stable?¿?¿
Many Thanks to ALL,
Perdita2000
Click to expand...
Click to collapse
Here https://github.com/CyanogenMod/android_packages_apps_CMParts/tree/froyo-stable
perdita2000 said:
Elelinux, do you mean use froyo-stable branch for CMParts??
Many Thanks,
Perdits2000
Click to expand...
Click to collapse
Yes as you see in post above,download it and replace it with that CMParts you have now.
A fully up to date CM6 ROM? I sincerely hope this works out! I think this would be the ideal ROM for our HTC Hero. Gingerbread's a bit slow on the Hero, but Froyo has always worked well.
I'm just writing this to let you know I'd be hugely appreciative of any ROM that you end up producing here!
I am getting same boot loop as when I applied mentioned patch....
I have synced CMParts git with froyo-stable brunch and compile again (clean before new compile) and no errors (typical VM cores from out of memory .... I always get one or two during compilation on CM7 but everything works fine... not enough memory for compilations ( ), but after flash new rom it loops on HTC HERO with following errors...
I/dalvikvm( 161): System server process 164 has been created
I/Zygote ( 161): Accepting command socket connections
I/dalvikvm( 164): Unable to dlopen(/system/lib/libandroid_servers.so): Cannot load library: link_image[2033]: failed to link libandroid_servers.so
I/dalvikvm( 164):
D/AndroidRuntime( 164): Shutting down VM
W/dalvikvm( 164): threadid=1: thread exiting with uncaught exception (group=0x400207e0)
E/AndroidRuntime( 164): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 164): java.lang.UnsatisfiedLinkError: Library android_servers not found
E/AndroidRuntime( 164): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/AndroidRuntime( 164): at java.lang.System.loadLibrary(System.java:557)
E/AndroidRuntime( 164): at com.android.server.SystemServer.main(SystemServer.java:592)
E/AndroidRuntime( 164): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 164): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 164): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime( 164): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime( 164): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 164): Error reporting crash
E/AndroidRuntime( 164): java.lang.NullPointerException
E/AndroidRuntime( 164): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 164): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:887)
E/AndroidRuntime( 164): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:884)
E/AndroidRuntime( 164): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 164): Sending signal. PID: 164 SIG: 9
I/Zygote ( 161): Exit zygote because system server (164) has terminated
D/AndroidRuntime( 172):
D/AndroidRuntime( 172): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I/AndroidRuntime( 172): Heap size: -Xmx16m
D/AndroidRuntime( 172): CheckJNI is OFF
D/AndroidRuntime( 172): --- registering native functions ---
I/SamplingProfilerIntegration( 172): Profiler is disabled.
I/Zygote ( 172): Preloading classes...
D/dalvikvm( 172): GC_EXPLICIT freed 824 objects / 47648 bytes in 7ms
D/dalvikvm( 172): GC_EXPLICIT freed 368 objects / 19104 bytes in 7ms
I/bluetooth_ScoSocket.cpp( 172): Entry name = MY-CAR ScoTypes = 0x7f
I/bluetooth_ScoSocket.cpp( 172): Entry name = Motorola HF850 ScoTypes = 0x7
D/dalvikvm( 172): GC_EXPLICIT freed 319 objects / 18080 bytes in 8ms
D/dalvikvm( 172): GC_EXPLICIT freed 464 objects / 28864 bytes in 9ms
D/dalvikvm( 172): GC_EXPLICIT freed 2096 objects / 108592 bytes in 13ms
I'm going to take a look at /system/lib/libandroid_servers.so compilation because I think is the problem...
Many Thanks to All,
Perdita2000
Hi all,
I have tried a couple of times with no luck, can't find if there is some problem with repos or just a code error, because it compiles without any error...
Have tried to sync froyo-stable but no luck too....
Syncing work tree: 4% (9/210) error: revision master in CyanogenMod/android_device_advent_vega not found
Perdita2000
perdita2000 said:
Hi all,
I have tried a couple of times with no luck, can't find if there is some problem with repos or just a code error, because it compiles without any error...
Have tried to sync froyo-stable but no luck too....
Syncing work tree: 4% (9/210) error: revision master in CyanogenMod/android_device_advent_vega not found
Perdita2000
Click to expand...
Click to collapse
In your /android/system/.repo/manifest/ you find default.xml edit the file and remove the path for advent_vega then run repo sync again
Many Thanks Elelinux ... and sorry about "my newbie questions" .... I'm starting to use github today (more than repo init/sync ... etc)..
Perdita2000
Checked out the "froyo" branch, did a "repo sync", added HTC proprietary files and ROM Manager and started the compile.
Ran into the same compilation error from the start of this thread.
Then applied bjk's fix from here (added the diff files there so you can apply then automatically with "git apply"), then compilation completed smoothly. Boots up just fine here.
What exactly is the error you are getting?
Boot error is posted thread . Did you tried stable or current branch?
Many thanks,
Sent from my Hero using XDA App
perdita2000 said:
Boot error is posted thread . Did you tried stable or current branch?
Many thanks,
Sent from my Hero using XDA App
Click to expand...
Click to collapse
Ok, sorry didn't see it. Doesn't make much sense to me. I used the "froyo" branch (not "froyo-stable"). But this shouldn't matter.
From where did you take your proprietary libs? Try taking them from here: https://github.com/koush/proprietary_vendor_htc/tree/froyo (notice the froyo branch).
I always use device propietary files from device itself. Do you mean they could be wrong?, in fact extract-files.sh didn't pull every needed file (I thought it was wrong because haven't got any issue compiling CM7?¿?¿?).
I will try device files from koush and let you know!!!
Many Thanks to Everyone!!!
Perdita2000
hi there.
So i've asked a dev related questions here before but didnt get an answer... hoping to get one now!
--i didnt ask it in the DEV related forums because it doesnt seem like the place to ask a question--
and i've also searched for an answer, many times, but havent reached a solution
anyway, ...
I took the Dice_ml.apk from the sensation ROM and put it on my 2.3.3 deodexed (near to)stock-ROM, yet i get a 'Force Close'. i deodexed the dice_ml file and added the classes.dex file to the apk.
I 'logcat'ed and found that its missing a .so file, so i found it in the sensation ROM and copied it to the /system/lib folder, yet i still get the error, this is what it says:
I/ActivityManager( 1343): Start proc com.htc.dice.ml for activity com.htc.dice.m
l/.DiceActivity: pid=2762 uid=10130 gids={}
I/DiceActivity( 2762): onCreate()
I/DiceActivity( 2762): onResume()
D/DiceActivity( 2762): [onResume] mView is Null and postDelay
E/Dice ( 2762): Couldn't load libdice_ml.so!
W/dalvikvm( 1443): disableGcForExternalAlloc: false
D/DiceActivity( 2762): [DiceLib::getInstance] Null State
W/dalvikvm( 2762): No implementation found for native Lcom/htc/dice/ml/DiceLib;.
setResourcePath (Ljava/lang/String; )V
D/AndroidRuntime( 2762): Shutting down VM
W/dalvikvm( 2762): threadid=1: thread exiting with uncaught exception (group=0x4
001d5a0)
E/AndroidRuntime( 2762): FATAL EXCEPTION: main
E/AndroidRuntime( 2762): java.lang.UnsatisfiedLinkError: setResourcePath
E/AndroidRuntime( 2762): at com.htc.dice.ml.DiceLib.setResourcePath(Nativ
e Method)
Click to expand...
Click to collapse
The AndroidRuntime Error still goes on. What could be the problem (im kinda new to this moving from one ROM to the next)
And could i also ask how one changes the Resolution of an apk?
//----------------------------
Also, alot of people have this issue, which is that, after rooting, the headphone mic, and buttons dont work.
i also 'logcat'ed it, and sometimes the buttons send a signal to the OS, sometimes it takes a while for the OS to process the signal (or maybe get it?) and sometimes it doesnt receive it at all!(or maybe its taking to long to send the signal).
Anyway, when it does get a signal, it also says that a certain file is missing, heres the log:
W/KeyCharacterMap( 1443): Can't open keycharmap file
W/KeyCharacterMap( 1443): Error loading keycharmap file '/system/usr/keychars/h2
w_headset.kcm.bin'. hw.keyboards.65540.devname='h2w headset'
I/KeyCharacterMap( 1443): Using default keymap: /system/usr/keychars/qwerty.kcm.
bin
E/BroadcastReceiver( 1713): BroadcastReceiver trying to return result during a n
on-ordered broadcast
E/BroadcastReceiver( 1713): java.lang.RuntimeException: BroadcastReceiver trying
to return result during a non-ordered broadcast
E/BroadcastReceiver( 1713): at android.content.BroadcastReceiver.checkSynchr
onousHint(BroadcastReceiver.java:451)
E/BroadcastReceiver( 1713): at android.content.BroadcastReceiver.abortBroadc
ast(BroadcastReceiver.java:374)
Click to expand...
Click to collapse
and also the BroadcastReceiver Error continues in the log.
So i checked the 1.32 original stock rom(my buttons were working on that ROM before i rooted it), and i didnt find the 'h2w_headset.kcm.bin' file, so i thought maybe its from the 'qwerty.kcm.bin' file, thus i replaced it with the same file from 1.32, (and without restarting the phone) i tested the file and still, had the same problem.
My question for this part is ... Is that error normal? and can it be fixed?
and sorry for all this stuff!!!
Hoping for a reply!
"Failed to find provider info for telephony" after exchange Phone.apk in custom ROM
Hi
i try to customize some apps and then create a custom ROM, but get errors like "Failed to find provider info for telephony" afterwards.
here is what i have tried:
got the original jelly bean binaries (4.1.1 JRO03C) from the android developers site
unzipped it and imported it into the Android-Kitchen (i tried it odexed and deodexed)
downloaded the original android source (4.1.1_r1) and compiled it for maguro (i tried full_maguro-userdebug and full_maguro-user)
replaced some apps (e.g. phone or mms) in the kitchen with the ones from the android source build (i also tried to replace just one at a time)
created the ROM and flashed it to the phone
the phone boots up, but in case of the phone app i get this error every 10 - 20 seconds:
Code:
Failed to find provider info for telephony
FATAL EXCEPTION: main
java.lang.IllegalArgumentException: Unknown URL content://telephony/carriers/current
at android.content.ContentResolver.insert(ContentResolver.java:860)
at com.android.internal.telephony.gsm.GSMPhone.updateCurrentCarrierInProvider(GSMPhone.java:1346)
at com.android.internal.telephony.gsm.GSMPhone.handleMessage(GSMPhone.java:1171)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4745)
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)
in case of the mms app the almost identical error:
Code:
Failed to find provider info for sms
FATAL EXCEPTION: SmsReceiverService
java.lang.IllegalArgumentException: Unknown URI content://sms/outbox
at android.content.ContentResolver.update(ContentResolver.java:986)
at android.database.sqlite.SqliteWrapper.update(SqliteWrapper.java:79)
at com.android.mms.transaction.SmsReceiverService.moveOutboxMessagesToFailedBox(SmsReceiverService.java:402)
at com.android.mms.transaction.SmsReceiverService.handleBootCompleted(SmsReceiverService.java:378)
at com.android.mms.transaction.SmsReceiverService.access$200(SmsReceiverService.java:72)
at com.android.mms.transaction.SmsReceiverService$ServiceHandler.handleMessage(SmsReceiverService.java:209)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.os.HandlerThread.run(HandlerThread.java:60)
i de-assembled the phone app from the original binaries to see if it registers itself with the given content URL, but it doesn't. so i am kinda clueless right now about what is going on here.
btw: i can open the apps for a sec when clicking on their icon. the main screen opens and then they crash right away.
thanks
Simon
[Q&A] [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)
Q&A for [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
alarm clock
Recently discussed the problem that the included headphones alarm clock rang only from external speakers. Now it rings only from the headphones. But it would be optimal to it when headphones are connected rang simultaneously and external speakers and headphone out. So it is correct and it is so sold on the official firmware.
Sorry for my bad English.
Del
---------- Post added at 03:30 AM ---------- Previous post was at 03:24 AM ----------
Hi, will snapshot m12 for LTE?
Do you just dirty flash the nightlife? I tried going the update route but it doesn't work.
Hi all!
First of all thank you for the Roma and the whole tutorial is perfect on my side on my "tab pro lte"
I would like to know how to overclock the processor above its Standard power?
sorry for the mistakes, I'm French and I use google translation ... oO
thank you!
No mobile data
Thanks to the dev for his continuous efforts on this rom, keep up the good work. However, i noticed that mobile data doesn't work for 2g networks. I've tried using the "preferred network type" and even changing the sim but it still won't work. When i get into 3g or LTE zonse the mobile data begins to work. Please could you suggest a fix. I'm currently limited to 2g so it would be a big help. Thanks
Any hints on building CM12 for this device ? I'm willing to do it if there is any documentation help.
Firmware crude
CM-12 test
Deleted
DensonX said:
Sorry if this is off-topic, but I have seen a lot of people requesting CyanogenMod 12 for this device. I managed to build CM-12 for the mondrianlte, however it does not flash on my device. I get an error saying E: error executing binary in zip. I suspect this may be due to the fact that I have a european Tab Pro, so if anyone with a US Tab Pro LTE wants to try to install it here's a file. https://drive.google.com/file/d/0Bxf2YUR9_3hDX3JUbnJYbWVfTTA/view?usp=sharing
Do NOT forget to backup before attempting to install this, as it likely will not work.
Also if anyone knows how to solve my problem with flashing this please let me know.
Click to expand...
Click to collapse
Please do not post links to other builds in my thread. Especially ones that you can't even flash because it doesn't work for you!
This only adds confusion.
I will try to release something soon. It may have a broken camera (the camera is broken on picassolte and if I can't figure it out I'll have to just leave it broken for both mondrianlte and picassolte for now) but otherwise has been working well for me on picassolte.
SM-T325, CM12 and encryption
Hello,
First Thank you crpalmer for your great work on mondrianlte. I've been using for roughly one month and did not encounter any serious issue, it is working so much better than stock Samsung ROMs ! I only got into problems when trying to encrypt the tablet (with cm-12-20150321-UNOFFICIAL-mondrianlte).
Once the process was started it rebooted very quickly and got stuck on the boot cyanogenmod screen. A forced off/on cycle was able to restore the tablet normal operation, but it had not been encrypted.
Relevant portions of the adb log seem to be :
(just after the beginning of the encrytion process)
Code:
E/Cryptfs ( 243): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
D/Cryptfs ( 243): Just asked init to shut down class main
and later when the tablet reboots :
Code:
D/Cryptfs ( 243): unmounting /data succeeded
D/QSEECOMAPI: ( 243): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 243): App is not loaded in QSEE
E/QSEECOMAPI: ( 243): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 243): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 243): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 243): App is not loaded in QSEE
E/QSEECOMAPI: ( 243): Error::Cannot open the file /firmware/image/keymaste.mdt
E/QSEECOMAPI: ( 243): Error::Loading image failed with ret = -1
E/QCOMKeyMaster( 243): Loading keymaster app failed
E/Cryptfs ( 243): could not open keymaster device in keystore (Operation not permitted)
E/Cryptfs ( 243): Failed to init keymaster
--------- beginning of crash
F/libc ( 243): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3c in tid 315 (vold)
F/libc ( 243): Unable to open connection to debuggerd: Connection refused
I/Vold (26973): Vold 2.1 (the revenge) firing up
D/Vold (26973): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold (26973): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs (26973): Check if PFE is activated on Boot
E/Cryptfs (26973): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs (26973): Error getting crypt footer and key
files /vendor/firmware/keymaster/keymaster.* have permission 644, user/group root, and are symlinks into /firmware/image/. In /firmware/image/, keymaste.* files have permission 440, user system, group drmrpc. Based on the QSEECOMAPI errors above, I am unable to determine whether these access rights are correct. I assume that even if they were, some incorrect SElinux configuration could cause access problems ?
Is anyone able to figure out what is happening ? Is it useful that I post a full log of the process ?