I try to port Sense from HTC One SV on our Xperia L.
I replaced BOOTCLASSPATCH in Extended stock kernel v2 from original sense kernel. Also I little edited ROM.
But my port freezes on bootanimation.
I need your help...
Last log - http://forum.xda-developers.com/showpost.php?p=47577503&postcount=22
Rom (last build) - https://drive.google.com/file/d/0B5kucJeEvGrGcFFqRmlqSG1uQ0E/edit?usp=sharing
Modified kernel - https://docs.google.com/file/d/0B5kucJeEvGrGTVNCVWhEdVNwYUE/edit
Original ROM - http://fs1.d-h.st/download/00053/hDK/k2u_JB_2.14.401.107_stock_odexed_01_06_13.zip
Logcat Logcat Logcat!!!
The-Superman said:
Logcat Logcat Logcat!!!
Click to expand...
Click to collapse
I know it, but I have some problems with adb, than help needed
like81 said:
I know it, but I have some problems with adb, than help needed
Click to expand...
Click to collapse
Sorry but no one can tell your problem without logcat. We cannot see what causes you to stay on bootlogo just by looking at the image. Try Advanced Logcat Viewer as it includes working adb and an advanced logcat viewer ( http://forum.xda-developers.com/showthread.php?t=2454610)
Sent from my E10i using xda premium
pongnamu said:
Sorry but no one can tell your problem without logcat. We cannot see what causes you to stay on bootlogo just by looking at the image. Try Advanced Logcat Viewer as it includes working adb and an advanced logcat viewer ( http://forum.xda-developers.com/showthread.php?t=2454610)
Click to expand...
Click to collapse
Thanks, i will try to do it.
Okay, I got logs!
It's my logs.
I'm thinking how to fix it...
I really hope to see this rom on our xl
Sent from my C2104
Keeping an eye on this! :good:
Firstly I must fix fatal errors....
F/libc (13914): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 13914 (zygote)
F/libc (13777): Failed while talking to debuggerd: Connection reset by peer
F/libc (13914): Failed while talking to debuggerd: Connection reset by peer
F/libc (13929): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 13929 (zygote)
F/libc (14062): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 14062 (mediaserver)
F/libc (14062): Unable to open connection to debuggerd: Connection refused
Click to expand...
Click to collapse
It's all fatal errors. This problems take place in libc.so, I think...
After few fixes, some errors have disappeared.
New log.
like81 said:
After few fixes, some errors have disappeared.
New log.
Click to expand...
Click to collapse
is it sense 5? If it is, u need ion kernel right?
Tausif Ahmed said:
is it sense 5? If it is, u need ion kernel right?
Click to expand...
Click to collapse
No, it's sense 4+. It doesn't need ION.
P.S. HTC One SV hasn't sense 5
P.P.S. And I have HTC Explorer too)))
As of what I saw in the logcat ,, There are some libs missing..Try to add them or fix them if they exist
Sparksys said:
As of what I saw in the logcat ,, There are some libs missing..Try to add them or fix them if they exist
Click to expand...
Click to collapse
Missing libs... Okay, thanks.
F/libc (12893): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 12893 (zygote)
And what is this error? What is fatal signal?
The new fixes. And a new log
Don't watch to errors with camera and audio_policy, I'll fix it later.
I was thinking few days and I understand that this errors are linked together!!!
E/JNIHelp (10516): Native registration unable to find class 'com/android/internal/os/RuntimeInit', aborting
F/libc (10516): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 10516 (zygote)
Click to expand...
Click to collapse
I think android can't find this class in services.jar. And I think that if I add it to services.jar, errors dissapear!
But I'm not sure...
may be changing in drivers fix some problems
Its not working broo...
Sent by using xda premium
Related
I might have figured out a way to get the LG camera to work. When attempting to launch the LG Camera on this EB1.0.3 build logcat immediately points to system/framework/RES_cappuccino.apk is not a directory or valid path. I will attempt to deodex both the 2.2 framework and 2.3 and see the difference. Anyone willing to help .
Edit: Im currently looking at both frameworks. The Camera from LG is done by Arcsoft.
edit: libamce.so is needed. I pushed this and then it said library missing so i pushed nvmmmcamera.so and then a NV6Camera_ConnectZ was thrown as the exception...
any help greatly appreciated.
Major Update (7/11): LG Camera may work on Gingerbread. I decompiled the libamce.so and found some interesting stuff. I am currently flashing the GB Leak to test the Camera. will Post results.
.plt:000459F4 ;
.plt:000459F4 ; +-------------------------------------------------------------------------+
.plt:000459F4 ; | This file has been generated by The Interactive Disassembler (IDA) |
.plt:000459F4 ; | Copyright (c) 2009 by Hex-Rays, <[email protected]> |
.plt:000459F4 ; | License info: B3-ADA1-9D85-DF |
.plt:000459F4 ; | Licensed User |
.plt:000459F4 ; +-------------------------------------------------------------------------+
.plt:000459F4 ;
.plt:000459F4 ; Input MD5 : 2EBB5FF4C8E8CF34C40FFC3AED9E8042
.plt:000459F4
.plt:000459F4 ; ---------------------------------------------------------------------------
.plt:000459F4 ; File Name : C:\Users\flak0-hpn3\Downloads\libamce.so
.plt:000459F4 ; Format : ELF (Shared object)
.plt:000459F4 ; Imagebase : 8000
.plt:000459F4 ; Needed Library 'libcamera_client.so'
.plt:000459F4 ; Needed Library 'libsurfaceflinger_client.so'
.plt:000459F4 ; Needed Library 'libui.so'
.plt:000459F4 ; Needed Library 'liblog.so'
.plt:000459F4 ; Needed Library 'libcutils.so'
.plt:000459F4 ; Needed Library 'libutils.so'
.plt:000459F4 ; Needed Library 'libhardware.so'
.plt:000459F4 ; Needed Library 'libmedia.so'
.plt:000459F4 ; Needed Library 'libandroid_runtime.so'
.plt:000459F4 ; Needed Library 'libc.so'
.plt:000459F4 ; Needed Library 'libm.so'
.plt:000459F4 ; Needed Library 'libstdc++.so'
.plt:000459F4 ; Needed Library 'libdl.so'
.plt:000459F4 ; Needed Library 'libbinder.so'
.plt:000459F4 ; Needed Library 'libskia.so'
.plt:000459F4 ; Needed Library 'libicuuc.so'
.plt:000459F4 ; Needed Library 'libEGL.so'
.plt:000459F4 ; Needed Library 'libnvomx.so'
.plt:000459F4 ;
.plt:000459F4 ; EABI version: 5
.plt:000459F4 ;
.plt:000459F4
Click to expand...
Click to collapse
UPDATE: 7/6/2011
Here is the latest error on 2.3.4
I/===Camera=== 1.1.0.74( 2609): Performance log:Load so<---2011-07-06 06:41:52.100
W/dalvikvm( 2609): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/android
/camera/CamApplication;
W/dalvikvm( 2609): Class init failed in newInstance call (Lcom/android/camera/CamApplication
D/AndroidRuntime( 2609): Shutting down VM
W/dalvikvm( 2609): threadid=1: thread exiting with uncaught exception (group=0x40015560)
E/AndroidRuntime( 2609): FATAL EXCEPTION: main
E/AndroidRuntime( 2609): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 2609): at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime( 2609): at java.lang.Class.newInstance(Class.java:1409)
E/AndroidRuntime( 2609): at android.app.Instrumentation.newApplication(Instrum entation.java:9
57)
E/AndroidRuntime( 2609): at android.app.Instrumentation.newApplication(Instrum entation.java:9
42)
E/AndroidRuntime( 2609): at android.app.LoadedApk.makeApplication(LoadedApk.ja va:461)
E/AndroidRuntime( 2609): at android.app.ActivityThread.handleBindApplication(A ctivityThread.j
ava:3412)
E/AndroidRuntime( 2609): at android.app.ActivityThread.access$2200(ActivityThr ead.java:123)
E/AndroidRuntime( 2609): at android.app.ActivityThread$H.handleMessage(Activit yThread.java:97
7)
E/AndroidRuntime( 2609): at android.os.Handler.dispatchMessage(Handler.java:99 )
E/AndroidRuntime( 2609): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 2609): at android.app.ActivityThread.main(ActivityThread.jav a:3835)
E/AndroidRuntime( 2609): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2609): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 2609): at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(Zygote
Init.java:847)
E/AndroidRuntime( 2609): at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:605)
E/AndroidRuntime( 2609): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 2609): Caused by: java.lang.UnsatisfiedLinkError: Cannot load library: reloc_libra
ry[1311]: 975 cannot locate '_ZN7android22MediaMetadataRetriever12captureFrame Ev'...
E/AndroidRuntime( 2609):
E/AndroidRuntime( 2609): at java.lang.Runtime.load(Runtime.java:394)
E/AndroidRuntime( 2609): at java.lang.System.load(System.java:534)
E/AndroidRuntime( 2609): at com.android.camera.CamApplication.<clinit>(CamAppl ication.java:27
)
E/AndroidRuntime( 2609): ... 16 more
W/ActivityManager( 1055): Force finishing activity com.android.camera/.ArcCamera
Click to expand...
Click to collapse
Progress: The LG Camera depends on libamce.so which is not part of the android open source project and is not in the LGP-999 source code. The libamce is also dependent on a native android library, if any dev wants to help please chime in.
I already replied to you in the previous thread but anyways that file your talking about is part of LG's framework that is not present in some roms as we took it out. Even when you put it back the camera will not function
Don't give up though I am sure some way to get it working.
tweezit said:
I already replied to you in the previous thread but anyways that file your talking about is part of LG's framework that is not present in some roms as we took it out. Even when you put it back the camera will not function
Don't give up though I am sure some way to get it working.
Click to expand...
Click to collapse
did u see this?
edit: libamce.so is needed. I pushed this and then it said library missing so i pushed nvmmmcamera.so and then a NV6Camera_ConnectZ was thrown as the exception...
I pushed all the camera libs and crashed each time. Keep going though as I am not trying to discourage you as I hope you do get it
Be warned though I did get a blackscreen after pushing all the libs. It would show LG logo then go straight to black screen so I had to cwm it
tweezit said:
I pushed all the camera libs and crashed each time. Keep going though as I am not trying to discourage you as I hope you do get it
Be warned though I did get a blackscreen after pushing all the libs. It would show LG logo then go straight to black screen so I had to cwm it
Click to expand...
Click to collapse
sorry i am answering in both threads but how do we find what libs and apk is dependent on? one wierd thing i noticed is that afrer 2 reboots the original GB camera came back.
I just did a quick look cause kinda had an idea of most. But you need a better person then me for this honestly. I will keep looking though.
tweezit said:
I just did a quick look cause kinda had an idea of most. But you need a better person then me for this honestly. I will keep looking though.
Click to expand...
Click to collapse
thanks buddy
hope ya guys figure this is out. this is the only reason why i havent gone 2.3.3
good luck
Pichingo said:
hope ya guys figure this is out. this is the only reason why i havent gone 2.3.3
good luck
Click to expand...
Click to collapse
Thanks.
Sent from my LG-P999 using XDA App
Pichingo said:
hope ya guys figure this is out. this is the only reason why i havent gone 2.3.3
good luck
Click to expand...
Click to collapse
Same here. The LG camera is amazing compared to the stock android one.
Sent from my G2x running Cyanogen mod.
check androidmanifest.xml for needed libs. logcating it when it fc's will also give u the missing libs
which camera is in the leaked Gingerbread version?
jir591 said:
which camera is in the leaked Gingerbread version?
Click to expand...
Click to collapse
A ****ty one.
It compresses 8mp photos to just about 1 mb = about 75% or more compression (were 4-5 mb in froyo camera). No real HD video (720 - 1080 p).
Hard to believe LG would scrap the better camera on a final update.
gaww said:
A ****ty one.
It compresses 8mp photos to just about 1 mb = about 75% or more compression (were 4-5 mb in froyo camera). No real HD video (720 - 1080 p).
Hard to believe LG would scrap the better camera on a final update.
Click to expand...
Click to collapse
Corret, lot of the times, I got 6-7mb in froyo camera. I only shoot video on 720p though(smoother).
jdaclutch said:
Current, lot of the times, I got 6-7mb in froyo camera. I only shoot video on 720p though(smoother).
Click to expand...
Click to collapse
Yeah - don't really want to give that one up.
I have to agree, Ive never liked this camera. I didn't expect to lose the LG when i flashed eaglesblood 1.0.3
In the mean time is anything better in the market? something with decent options & pictures but quick and easy to use?
Ive never used any from the market but it seems there are many to choose from. would rather not download them all haha
It definitely was a dealbreaker for me. I too loved the lg camera and being able to record in HD was a big thing for me..went back to stock rom from eagleblood GB just for that. I hope you can find a way to get the camera working to its full potential in GB.
Sent from my LG-P999 using XDA App
Maybe a possible avenue to explore would be enomother's work when he ported the htc sense camera into his aosp nexus 1 froyo rom.
Sent from my LG-P999 using XDA Premium App
gaww said:
A ****ty one.
It compresses 8mp photos to just about 1 mb = about 75% or more compression (were 4-5 mb in froyo camera). No real HD video (720 - 1080 p).
Hard to believe LG would scrap the better camera on a final update.
Click to expand...
Click to collapse
I really doubt the gingerbread leak is gonna be the official update that gets pushed out by tmobile. They are not gonna give everybody a camera app that takes away one of the main selling points of the device (HD recording) and also just look at the 4g icon, it's still the one from froyo.
Im 99.9% certain this was just a test build by tmobile and lg to see how gingerbread would work on the g2x
aim1126 said:
Im 99.9% certain this was just a test build by tmobile and lg to see how gingerbread would work on the g2x
Click to expand...
Click to collapse
I agree with this statement from looking through the rom.
This is a repack of the stock ROM for the HTC One S, the most recent release at the time of writing - 1.78.401.2.
Features...
Deodexed
All components Updated to the latest versions
Optimised with the MCR build system for
Rooted with insecure boot image
A kitchen for this will follow shortly. This will also form the basis for my next MoDaCo Custom ROM.
This image is for flashing via ClockworkMod recovery, and is used at your own risk! Always back up before flashing!
Ir2 1.78.401.2 DUO - DOWNLOAD - MD5: d9352b78a9e5df3ccce5aca2c78e1084
Enjoy!
P
"Optimised with the MCR build system"
Can you explain a bit more about this? What are the advantages?...
Should this work on the TMO US Version?
Sent from my HTC One S using Tapatalk 2
ZeppeMan said:
"Optimised with the MCR build system"
Can you explain a bit more about this? What are the advantages?...
Click to expand...
Click to collapse
The download is smaller, the system files take up less space on the device and it gives a slight speed improvement.
cannondale0815 said:
Should this work on the TMO US Version?
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Untested on the T-Mo version!
P
paulobrien said:
The download is smaller, the system files take up less space on the device and it gives a slight speed improvement.
Click to expand...
Click to collapse
Thx for your answer, I allways see that in your "feature list" and wondered what is actually did, now I know
paulobrien said:
The download is smaller, the system files take up less space on the device and it gives a slight speed improvement.
P
Click to expand...
Click to collapse
Is it like a better compression of compressed file?
Thanks for that Paul, sadly I haven't found the newest RUU but this is a great help, thanks!
can be deleted
nevermind.
Azerty keyboard???
m!k3 said:
Azerty keyboard???
Click to expand...
Click to collapse
Sorry but you can't ask everywhere for this feature, it isn't here, you can give the .odex files and we can deodex it for you but please don't ask everywhere for it!
torxx said:
Sorry but you can't ask everywhere for this feature, it isn't here, you can give the .odex files and we can deodex it for you but please don't ask everywhere for it!
Click to expand...
Click to collapse
I don't ask only for the keybord, i search a rom with the keybord!
I send to you an mp with the apk if you want (HTC_IME and CIMEXT9) but not reply ...
Please can some one post their com.htc.resource.apk and rosie.apk of this phone.
i am making a sense 4 theme for go launcher.any help will be appreciated
John XDA fan said:
Please can some one post their com.htc.resource.apk and rosie.apk of this phone.
i am making a sense 4 theme for go launcher.any help will be appreciated
Click to expand...
Click to collapse
Can't you just download the ROM and pull them out yourself?
wastage of time and data please upload them
John XDA fan said:
wastage of time and data please upload them
Click to expand...
Click to collapse
So you want to waste other peoples time. It's not that hard, this is 2012 unless your on a 3g network 400mb aint nothing.
I'm getting a force close on the hold options in messages like copy and paste
Sent from my HTC One S using Tapatalk 2
Same Problem. Can't mark anything in HTC apps
Gesendet von meinem HTC One S mit Tapatalk 2
zeroprobe said:
So you want to waste other peoples time. It's not that hard, this is 2012 unless your on a 3g network 400mb aint nothing.
Click to expand...
Click to collapse
I am not on 3g this time hence i am asking dude i can hardly download 100 MB.My connection is down this time hence i am asking for you to upload.If you want to help then upload or its your choice
+1 Also getting a crash when doing a long-press.
Code:
W/dalvikvm(18126): threadid=1: thread exiting with uncaught exception (group=0x40a97a08)
E/AndroidRuntime(18126): FATAL EXCEPTION: main
E/AndroidRuntime(18126): java.lang.VerifyError: com/htc/quickselection/HtcCheckableImageView
E/AndroidRuntime(18126): at java.lang.reflect.Constructor.constructNative(Native Method)
E/AndroidRuntime(18126): at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
E/AndroidRuntime(18126): at android.view.LayoutInflater.createView(LayoutInflater.java:586)
E/AndroidRuntime(18126): at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:680)
E/AndroidRuntime(18126): at android.view.LayoutInflater.inflate(LayoutInflater.java:466)
E/AndroidRuntime(18126): at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
E/AndroidRuntime(18126): at com.htc.quickselection.HtcQuickSelectionWindow.obtainView(HtcQuickSelectionWindow.java:668)
E/AndroidRuntime(18126): at com.htc.quickselection.HtcQuickSelectionWindow.inflateAction(HtcQuickSelectionWindow.java:198)
E/AndroidRuntime(18126): at com.htc.quickselection.HtcQuickSelectionWindow.addActionSet(HtcQuickSelectionWindow.java:263)
E/AndroidRuntime(18126): at com.htc.quickselection.HtcQuickSelectionWindow.addButton(HtcQuickSelectionWindow.java:296)
E/AndroidRuntime(18126): at com.htc.textselection.HtcTextSelectionManager.prepareHtcPasteWindow(HtcTextSelectionManager.java:192)
E/AndroidRuntime(18126): at android.widget.TextView$HandleView$1.run(TextView.java:11737)
E/AndroidRuntime(18126): at android.os.Handler.handleCallback(Handler.java:607)
E/AndroidRuntime(18126): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime(18126): at android.os.Looper.loop(Looper.java:154)
E/AndroidRuntime(18126): at android.app.ActivityThread.main(ActivityThread.java:4977)
E/AndroidRuntime(18126): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(18126): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime(18126): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
E/AndroidRuntime(18126): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
E/AndroidRuntime(18126): at dalvik.system.NativeStart.main(Native Method)
E/EmbeddedLogger( 424): App crashed! Process: com.google.android.gm
E/EmbeddedLogger( 424): App crashed! Package: com.google.android.gm v360 (4.0.5)
E/EmbeddedLogger( 424): Application Label: Google Mail
W/ActivityManager( 424): Force finishing activity com.google.android.gm/.ComposeActivity
---------- Post added at 06:55 PM ---------- Previous post was at 06:41 PM ----------
John XDA fan said:
Please can some one post their com.htc.resource.apk and rosie.apk of this phone.
i am making a sense 4 theme for go launcher.any help will be appreciated
Click to expand...
Click to collapse
http://dl.dropbox.com/u/24219415/com.htc.resources.apk
http://dl.dropbox.com/u/24219415/Rosie.apk
Hey all your friendly neighborhood tinkerer here.
I have ported and flashed 4.3 from the S4 leak to the I605. So far, the flash went successful using Vramc3 root odexed as a base.
Watching the logcat during install everything goes fine then i run into this:
Code:
I/DEBUG ( 1972):
I/DEBUG ( 1972): memory map around fault addr deadd00d:
I/DEBUG ( 1972): bedf2000-bee13000 [stack]
I/DEBUG ( 1972): (no map for address)
I/DEBUG ( 1972): ffff0000-ffff1000 [vectors]
I/DEBUG ( 1972): [email protected] -k -t -z -d -o /data/log/dumpstate_app_native -m 7340
I/dumpstate( 7458): begin
D/MDnsDS ( 7338): MDnsSdListener::Hander starting up
D/MDnsDS ( 7338): MDnsSdListener starting to monitor
D/MDnsDS ( 7338): Going to poll with pollCount 1
I/ServiceManager( 7339): Waiting for service sensorservice...
I/ServiceManager( 7339): Waiting for service sensorservice...
I/ServiceManager( 7339): Waiting for service sensorservice...
^[I/ServiceManager( 7339): Waiting for service sensorservice...
I/VPNCStarter( 1996): Message channel file directory does not exist
D/VoldCmdListener( 1967): asec list
I/ServiceManager( 7339): Waiting for service sensorservice...
I/dumpstate( 7458): done
The android dev guide doesn't really help out. Just says that its trying to start the device sensor service. Here starts the issue. Which service? Barometer, gyroscope, compass ??????? Anybody seen this before could shed some light on this I would be greatly appreciative.
Or is it that the framework is just not compatible with this phone yet? Let me know what you think.
dragonstalker said:
Hey all your friendly neighborhood tinkerer here.
I have ported and flashed 4.3 from the S4 leak to the I605. So far, the flash went successful using Vramc3 root odexed as a base.
Watching the logcat during install everything goes fine then i run into this:
Code:
I/DEBUG ( 1972):
I/DEBUG ( 1972): memory map around fault addr deadd00d:
I/DEBUG ( 1972): bedf2000-bee13000 [stack]
I/DEBUG ( 1972): (no map for address)
I/DEBUG ( 1972): ffff0000-ffff1000 [vectors]
I/DEBUG ( 1972): [email protected] -k -t -z -d -o /data/log/dumpstate_app_native -m 7340
I/dumpstate( 7458): begin
D/MDnsDS ( 7338): MDnsSdListener::Hander starting up
D/MDnsDS ( 7338): MDnsSdListener starting to monitor
D/MDnsDS ( 7338): Going to poll with pollCount 1
I/ServiceManager( 7339): Waiting for service sensorservice...
I/ServiceManager( 7339): Waiting for service sensorservice...
I/ServiceManager( 7339): Waiting for service sensorservice...
^[I/ServiceManager( 7339): Waiting for service sensorservice...
I/VPNCStarter( 1996): Message channel file directory does not exist
D/VoldCmdListener( 1967): asec list
I/ServiceManager( 7339): Waiting for service sensorservice...
I/dumpstate( 7458): done
The android dev guide doesn't really help out. Just says that its trying to start the device sensor service. Here starts the issue. Which service? Barometer, gyroscope, compass ??????? Anybody seen this before could shed some light on this I would be greatly appreciative.
Or is it that the framework is just not compatible with this phone yet? Let me know what you think.
Click to expand...
Click to collapse
Would it have anything to do with the s4 having sensors the note 2 doesn't? Such as temperature and humidity?
Sent from my SCH-I605 using xda premium
dragonstalker said:
Hey all your friendly neighborhood tinkerer here.
I have ported and flashed 4.3 from the S4 leak to the I605. So far, the flash went successful using Vramc3 root odexed as a base.
Watching the logcat during install everything goes fine then i run into this:
Code:
I/DEBUG ( 1972):
I/DEBUG ( 1972): memory map around fault addr deadd00d:
I/DEBUG ( 1972): bedf2000-bee13000 [stack]
I/DEBUG ( 1972): (no map for address)
I/DEBUG ( 1972): ffff0000-ffff1000 [vectors]
I/DEBUG ( 1972): [email protected] -k -t -z -d -o /data/log/dumpstate_app_native -m 7340
I/dumpstate( 7458): begin
D/MDnsDS ( 7338): MDnsSdListener::Hander starting up
D/MDnsDS ( 7338): MDnsSdListener starting to monitor
D/MDnsDS ( 7338): Going to poll with pollCount 1
I/ServiceManager( 7339): Waiting for service sensorservice...
I/ServiceManager( 7339): Waiting for service sensorservice...
I/ServiceManager( 7339): Waiting for service sensorservice...
^[I/ServiceManager( 7339): Waiting for service sensorservice...
I/VPNCStarter( 1996): Message channel file directory does not exist
D/VoldCmdListener( 1967): asec list
I/ServiceManager( 7339): Waiting for service sensorservice...
I/dumpstate( 7458): done
The android dev guide doesn't really help out. Just says that its trying to start the device sensor service. Here starts the issue. Which service? Barometer, gyroscope, compass ??????? Anybody seen this before could shed some light on this I would be greatly appreciative.
Or is it that the framework is just not compatible with this phone yet? Let me know what you think.
Click to expand...
Click to collapse
Not sure what you did to port it, but there is an app called sensorservifes in the stock s4. Try deleting it to get it booting
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Not sure what you did to port it, but there is an app called sensorservifes in the stock s4. Try deleting it to get it booting
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Ok. i'll try that. I know there is also a libsensorservice.so and a sensorservice file in the bin directory. So didn't know if it was as simple as deleting an apk.
No sensor.apk in the 4.3 download I have. Redownloading it.
Update. replaced sensorservice.apk , reflashed, and still getting same logcat . Clean install, does the dump, then keeps looping saying waiting for service sensorservice.
dragonstalker said:
Ok. i'll try that. I know there is also a libsensorservice.so and a sensorservice file in the bin directory. So didn't know if it was as simple as deleting an apk.
No sensor.apk in the 4.3 download I have. Redownloading it.
Update. replaced sensorservice.apk , reflashed, and still getting same logcat . Clean install, does the dump, then keeps looping saying waiting for service sensorservice.
Click to expand...
Click to collapse
Make sure you add your sensor libs to system/lib/hw
Sent from my SPH-L710 using xda app-developers app
Bimo!
Sent from my SCH-I605 using Tapatalk 2
theres a sensorhubservice and sensor service file in the note 2's /system/bin and libsersorhubservice.so and libsensorservice.so in /system/lib, copy these into your ported rom.
thanks for all the help it if I so far. if anybody is good at coding the link to what I've done so far is posted below.
I605VRAMC3-4.3test3.zip https://www.dropbox.com/s/t1k3p6anae3nvs7/I605VRAMC3-4.3test3.zip
dragonstalker said:
thanks for all the help it if I so far. if anybody is good at coding the link to what I've done so far is posted below.
I605VRAMC3-4.3test3.zip https://www.dropbox.com/s/t1k3p6anae3nvs7/I605VRAMC3-4.3test3.zip
Click to expand...
Click to collapse
Is your source from S4? can you port it to Note II N 7100?
dynamic503 said:
Is your source from S4? can you port it to Note II N 7100?
Click to expand...
Click to collapse
Its the s4 ported using i605vramc3 odexed rooted as a base.
Sent from my SCH-I605 using xda premium
dragonstalker said:
Its the s4 ported using i605vramc3 odexed rooted as a base.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Any update on your progress? I would love to get a stable stock 4.3 or 4.2 on my note 2...
Abrasher said:
Any update on your progress? I would love to get a stable stock 4.3 or 4.2 on my note 2...
Click to expand...
Click to collapse
4.2? There are stable 4.2.2 roms.. I use tegraowners 4.2.2 rom, based on CM. No bugs, faster than a N4 and better batterylife than stock sammy roms.
Gonna be cool when our Note 2 gets 4.3 though.
dragonstalker said:
Its the s4 ported using i605vramc3 odexed rooted as a base.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
I'm trying to do the same thing on my I747 (S3) using the mako 4.3 rip, but I can't get the kernel to finish booting (I'm using CM 10.1 nightly as a base and attempting to use its kernel)
I've pulled the last_kmsg but I don't see anything as obvious as your log. (Can't get ADB to connect during boot, so I'd assume the kernel isn't making it far enough to start up adbd) I've posted the kmsg here: [link] Any tips?
dragonstalker said:
thanks for all the help it if I so far. if anybody is good at coding the link to what I've done so far is posted below.
I605VRAMC3-4.3test3.zip https://www.dropbox.com/s/t1k3p6anae3nvs7/I605VRAMC3-4.3test3.zip
Click to expand...
Click to collapse
most likely I'm wrong here but it sounds like a smiliar issue we had with 4.2.2 in the beginning or am I wrong. Aren't we probably missing the correct files for the sensorhub?
If I'm recalling right it prevented us from booting 4.2.2 too until someone came up with a dirty hacky way and lateron it was done properly by somebody else. (just a far memory though)
dstruct2k said:
I'm trying to do the same thing on my I747 (S3) using the mako 4.3 rip, but I can't get the kernel to finish booting (I'm using CM 10.1 nightly as a base and attempting to use its kernel)
I've pulled the last_kmsg but I don't see anything as obvious as your log. (Can't get ADB to connect during boot, so I'd assume the kernel isn't making it far enough to start up adbd) I've posted the kmsg here: [link] Any tips?
Click to expand...
Click to collapse
doesn't that sound similiar: [ 299.419929] [1: recovery: 111] Sensors unset: 7fff ?
lolmensch said:
most likely I'm wrong here but it sounds like a smiliar issue we had with 4.2.2 in the beginning or am I wrong. Aren't we probably missing the correct files for the sensorhub?
If I'm recalling right it prevented us from booting 4.2.2 too until someone came up with a dirty hacky way and lateron it was done properly by somebody else. (just a far memory though)
doesn't that sound similiar: [ 299.419929] [1: recovery: 111] Sensors unset: 7fff ?
Click to expand...
Click to collapse
That line is just the system unloading the sensors after I issued a hard-reboot command by holding down the power button. I gave it 5 minutes to try and boot (299 seconds according to the kernel, not bad for estimating ) and then rebooted back to recovery to pull the kmsg. The touch event a few lines up was me showing where the reboot command was sent.
The I/DEBUG lines will give you a traceback to where the original error occurred.
Sent from my buttered S3
CNexus said:
The I/DEBUG lines will give you a traceback to where the original error occurred.
Sent from my buttered S3
Click to expand...
Click to collapse
you should check your build.prop as im sure that is part of your problem. You should use the one that came with 4.3 and just change the lines you need
A tip, if not referred to already. You should use an AOSP base not a CM base. It'll be much easier.
emwno said:
A tip, if not referred to already. You should use an AOSP base not a CM base. It'll be much easier.
Click to expand...
Click to collapse
CM is AOSP......
CNexus said:
CM is AOSP......
Click to expand...
Click to collapse
I agree. But you clearly misunderstood what I am saying....
mtk not released source till now, till they release, we have to totally depend on "reverse engineering"....
my attempt here is to provide a directory (collection of mod) for mtk devices....share whatever you got fully working or beta mods & themes... mention your device, processor & android version at the end..you can discuss here regarding any mods..... op will be updated as soon as a new mod is found, providing link to that post....
* Theming status bar by BOND1987
* statusbar close handle for ICS by me
* Soft Reboot on longpress by me
* Lockscreen Mods by me
* Honeycomb Lockscreen Mod by me
* Brightness Slider by Adi Aisiteru Reborn
* Fix the storage problem by khan_frd2002
* APK Tool for MiUI by khan_frd2002
* Transparency Mod by BOND1987
* 4.2 status bar Mod by SpaceCaker
* Add animate collapse to 4.2 status bar Mod by Me
* Generic method to add Toggles to 4.2 mod by bsuhas
* 4.2 LockScreen Clock MOD by Me
* CRT off Animation Mod by thirdzcee
* Quick Panel with lidroid by Me
* Increase Apps Storage Partition In Mediatek Devicesby [email protected]
ps : any suggestion regarding op is welcome
akash akya said:
mtk not released source till now, till they release, we have to totally depend on "reverse engineering"....
my attempt here is to provide a directory (collection of mod) for mtk devices....share whatever you got fully working or beta mods & themes... mention your device, processor & android version at the end..you can discuss here regarding any mods..... op will be updated as soon as a new mod is found, providing link to that post....
ps : any suggestion regarding op is welcome
Click to expand...
Click to collapse
May be brother,
It will help the community or not, I don't know. But first black and transparent message with dual SIM support is in my dev host link in my signature. There are several mods and all are working good.
If you want add it you can brother.
BTW, a good initiatives had been taken by you.:thumbup::thumbup::thumbup:
""Hitting Thanks Don't Cost You Anything, then, Why You All Are Getting Bothered in Doing So. Hitting Thanks Increases My Motivation to Work for this Community....""
BOND1987 said:
May be brother,
It will help the community or not, I don't know. But first black and transparent message with dual SIM support is in my dev host link in my signature. There are several mods and all are working good.
If you want add it you can brother.
BTW, a good initiatives had been taken by you.:thumbup::thumbup::thumbup:
""Hitting Thanks Don't Cost You Anything, then, Why You All Are Getting Bothered in Doing So. Hitting Thanks Increases My Motivation to Work for this Community....""
Click to expand...
Click to collapse
added some...
well, of all the methods ive implemented on my device theyr either done by you (akash), or a guide by adi a****eru reborn, but heres one i made that i havent found yet,
modded MMS.apk
fully transparent if your framework-res.apk has been modded for transparency
enter key is shown on keyboard instead of smiley
sms to mms conversion value was changed so you create long messages without worrying it will be converted to mms
send up to 200 recepients when creating a msg
max mms image resolution increased to 720x1280
and some other stuff i cant remember...
reference to theme it is here http://forum.xda-developers.com/showthread.php?t=1781297 so credit to UBER for his guide
for the other mms edits, i cant quite remember where i picked it up i thinks its from rootzwiki but i cant seem to find i in my browser history
Download link: should work on all mt6577 devices, ive even used ones from a110 so it should work
http://www.mediafire.com/?w1rfp72l9rk1b2w
EDIT : its our MMS.apk so its dual sim, ive been trying to find a way to add emojis but i havent had any reference yet for it
but just to be safe here is my device
Lava Xolo A1000 in france /CM Omega HD in my counry / Imobile IQ-6 in Thailand
MT6577 cpu with powervr sgx531 (i would be surpised if there was another gpu for our device out there)
android version: 4.1.1 Jellybean
kernel version: 3.4.0 [email protected] #1 SM PREEMPT Fri Feb 22 15:50:37 CST 2013
thirdzcee said:
well, of all the methods ive implemented on my device theyr either done by you (akash), or a guide by adi a****eru reborn, but heres one i made that i havent found yet,
modded MMS.apk
fully transparent if your framework-res.apk has been modded for transparency
enter key is shown on keyboard instead of smiley
sms to mms conversion value was changed so you create long messages without worrying it will be converted to mms
send up to 200 recepients when creating a msg
max mms image resolution increased to 720x1280
and some other stuff i cant remember...
http://www.mediafire.com/?w1rfp72l9rk1b2w
EDIT : its our MMS.apk so its dual sim, ive been trying to find a way to add emojis but i havent had any reference yet for it
Click to expand...
Click to collapse
bro, nice to see you here... make a guide like post so that i can add that post to op...
akash akya said:
bro, nice to see you here... make a guide like post so that i can add that post to op...
Click to expand...
Click to collapse
i just edited my post to add some credit on my reference on how i was able to come up with it, cant quite remember all i did on it so i cant make a full guide,
Come On guys, are you not missing Me.
But do give a solution to my problem add well.
I've few links that is applicable for MTK,
But guys do help me to get rid of my problem in that thread.
Akash,
Bro you have good knowledge On smali. Why don't you invest it in Mine.
""Hitting Thanks Don't Cost You Anything, then, Why You All Are Getting Bothered in Doing So. Hitting Thanks Increases My Motivation to Work for this Community....""
thirdzcee said:
i just edited my post to add some credit on my reference on how i was able to come up with it, cant quite remember all i did on it so i cant make a full guide,
Click to expand...
Click to collapse
its kk...
regarding lidroid panel... i dont think its necessary... as we have toolbar... if we some how managed it to be configurable, its enough..
BOND1987 said:
Come On guys, are you not missing Me.
But do give a solution to my problem add well.
I've few links that is applicable for MTK,
But guys do help me to get rid of my problem in that thread.
Akash,
Bro you have good knowledge On smali. Why don't you invest it in Mine.
""Hitting Thanks Don't Cost You Anything, then, Why You All Are Getting Bothered in Doing So. Hitting Thanks Increases My Motivation to Work for this Community....""
Click to expand...
Click to collapse
whats your problem bro... post here.. i will try...
akash akya said:
whats your problem bro... post here.. i will try...
Click to expand...
Click to collapse
Here is the problem.....
Code:
E/AndroidRuntime( 441): FATAL EXCEPTION: main
E/AndroidRuntime( 441): java.lang.NullPointerException
E/AndroidRuntime( 441): at com.android.systemui.statusbar.toolbar.ToolBarView.isStatusBarExpanded(ToolBarView.java:809)
E/AndroidRuntime( 441): at com.android.systemui.statusbar.toolbar.ConnectionSwitchPanel$1.handleMessage(ConnectionSwitchPanel.java:168)
E/AndroidRuntime( 441): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 441): at android.os.Looper.loop(Looper.java:153)
E/AndroidRuntime( 441): at android.app.ActivityThread.main(ActivityThread.java:5086)
E/AndroidRuntime( 441): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 441): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 441): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:821)
E/AndroidRuntime( 441): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:584)
E/AndroidRuntime( 441): at dalvik.system.NativeStart.main(Native Method)
Just let me know if you need any of my files.......
BOND1987 said:
Here is the problem.....
Code:
E/AndroidRuntime( 441): FATAL EXCEPTION: main
E/AndroidRuntime( 441): java.lang.NullPointerException
E/AndroidRuntime( 441): at com.android.systemui.statusbar.toolbar.ToolBarView.isStatusBarExpanded(ToolBarView.java:809)
E/AndroidRuntime( 441): at com.android.systemui.statusbar.toolbar.ConnectionSwitchPanel$1.handleMessage(ConnectionSwitchPanel.java:168)
E/AndroidRuntime( 441): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 441): at android.os.Looper.loop(Looper.java:153)
E/AndroidRuntime( 441): at android.app.ActivityThread.main(ActivityThread.java:5086)
E/AndroidRuntime( 441): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 441): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 441): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:821)
E/AndroidRuntime( 441): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:584)
E/AndroidRuntime( 441): at dalvik.system.NativeStart.main(Native Method)
Just let me know if you need any of my files.......
Click to expand...
Click to collapse
so if you used "toolbarview" twice (in notification bar & quickbar) ... its not possible as both share same id... it conflicts...
akash akya said:
so if you used "toolbarview" twice (in notification bar & quickbar) ... its not possible as both share same id... it conflicts...
Click to expand...
Click to collapse
Now what to do.....
Bcoz if I remove then also, it will Fc.
""Hitting Thanks Don't Cost You Anything, then, Why You All Are Getting Bothered in Doing So. Hitting Thanks Increases My Motivation to Work for this Community....""
BOND1987 said:
Now what to do.....
Bcoz if I remove then also, it will Fc.
""Hitting Thanks Don't Cost You Anything, then, Why You All Are Getting Bothered in Doing So. Hitting Thanks Increases My Motivation to Work for this Community....""
Click to expand...
Click to collapse
that bit difficult, we to add new class same as toolbarview.smali and edit it to be non scroll able....
akash akya said:
that bit difficult, we to add new class same as toolbarview.smali and edit it to be non scroll able....
Click to expand...
Click to collapse
No need to brother. Pretty much simpler.
Just deleted that toolbar lines from expanded.xml.
Now No force close.
""Hitting Thanks Don't Cost You Anything, then, Why You All Are Getting Bothered in Doing So. Hitting Thanks Increases My Motivation to Work for this Community....""
BOND1987 said:
No need to brother. Pretty much simpler.
Just deleted that toolbar lines from expanded.xml.
Now No force close.
""Hitting Thanks Don't Cost You Anything, then, Why You All Are Getting Bothered in Doing So. Hitting Thanks Increases My Motivation to Work for this Community....""
Click to expand...
Click to collapse
i know, but that doesnt make fully working, like non scroll able... its the a same toolbar moved to expanded...
Hello Guys.. Here is My little Guide To fix the storage problem like internal or external sdcard is not showing or mounting to PC On Ported Rom
Things Require :
Winrar
Notepad++
Stock Rom framework-res.apk Of your Device
Click to expand...
Click to collapse
Method : Using Winrar (easiest Way)
extract the framework-res.apk from your Ported rom (which has storage issue) to desktop or another place
Open the framework-res.apk using winrar
Then Go to res/xml....... here you will find storage_list.xml
Just replace the storage_list.xml with your stock rom framework-res.apk
that it close the winrar.... add the framework-res.apk to your ported rom install the rom and enjoy
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Please Note : After Using This Method on Some Rom the internal and external sdcard get swap like internal become external and external become internal.....
to fix this you have to decompile the framework-res.apk using apktool and then edit the storage_list.xml.....
in storage_list.xml ....you have to just rename the sdcard0 and sdcard1 to sdcard1 and sdcard0 vise versa receptively
Click to expand...
Click to collapse
Hello Guys i am Miui fan whenever i recompile Miui apks after decompiling its gave me error..... i cant recompile the apk
so after search a lot on Miui forum...... i got it working... it require special Miui apktool to recompile Miui apk
i have attach the Miui apktool ..... So enjoy
thread updated with more guides...
guys just wanna ask. any of you got tabbed settings with swipe to work???
http://forum.xda-developers.com/showthread.php?t=2273807 i followed this guide. but my settings is still the same, whats worse is i cant even add anything to settings_headers.xml now after apply that mod, i add something, compile it no errors but it doesnt show up when i open settings
thirdzcee said:
guys just wanna ask. any of you got tabbed settings with swipe to work???
http://forum.xda-developers.com/showthread.php?t=2273807 i followed this guide. but my settings is still the same, whats worse is i cant even add anything to settings_headers.xml now after apply that mod, i add something, compile it no errors but it doesnt show up when i open settings
Click to expand...
Click to collapse
hhhmmm i will try...
About the kernel:
This is an almost "stock" kernel for Android 4.2.2 and Sense 5.
Since we don't have any kernel source, i ported One XL 4.2.2 kernel to One S.
I tested it with MaximusHD and everything is working like stock orignal closed-source kernel, so this is a base for future custom kernels
Source:
https://github.com/anoane/ville-4.2.2-sense5-evitaul_porting
Donation:
http://forum.xda-developers.com/donatetome.php?u=2351000
Help me to buy an original HTC MHL Cable and an original HTC One X+ 2100mha battery, i'll try to add full battery support for One S and video-out at [email protected], i read somewhere that FullHD support is crappy
Changelog and dowload:
v0.2: first public version:
http://www.4shared.com/zip/prUybCsg/fabane_ville_13_09_13.html
v0.3: updated all ville-board-* files, fixed usb detection, usb charge and adb are working now
http://www.4shared.com/zip/eHUJyZe8/fabane_ville_13_09_13_v03.html
v0.6: wifi fixed using cyanogenmod/zarboz prima_wlan (compiled from source, now on a new branch)
http://www.4shared.com/zip/y1rp6zNK/fabane_ville_17_09_13_v06.html
v1.0: wifi fixed using flar2 patch (using stock prima_wlan from MaximusHD)
http://www.4shared.com/zip/1brHpu0i/fabane_ville_04_10_13_v10.html
v1.1: fixed incoming call quality issue
http://www.4shared.com/zip/NUW_ieLg/fabane_ville_14_10_13_v11.html
https://mega.co.nz/#!oVdSyJaY!LCxmKX3e6_UOYCIPUgHqJkHcM8pagVvgZTbb6nv8vrc
Did signal break in the process? Or was it already not working?
When I booted it it had no signal, so I guess it's not your fault
usaff22 said:
Did signal break in the process? Or was it already not working?
When I booted it it had no signal, so I guess it's not your fault
Click to expand...
Click to collapse
i'll try to check dmesg and logcat with some app, since usb/adb it's not working
but i have very little spare time now, so i posted my work until now, so someone can continue it
Oh yes, finally!
Great job here..
So you used stock sense 4+ kernel, and patched it with Evita kernel update?
Sent from my One S using Tapatalk 2
Thanks a lot Guy !!!
I'm very happy to see that! :good::good::good:
yes + some ville-board-* files (following evita-board changes) to compile it without errors
Wow ! That's good news
Envoyé depuis mon HTC One S avec Tapatalk 4
Does this mean htc 4.2.2 is not far away? And we will have sense 5 with it? Or it's just experimenting?
Thank you! If you need a tester I'm here for you..
Sent from my HTC One S using xda app-developers app
Good job, cant wait to use Sense 5 + 4.2.2 on my HoS!
good news, usb is detected now, battery charge and adb are working now, so i can get logcat and dmesg and fix problems easily
i think i finished to update board-ville-* files
i'll update git source and post a v0.3 test kernel soon
pirlano said:
good news, usb is detected now, battery charge and adb are working now, so i can get logcat and dmesg and fix problems easily
i think i finished to update board-ville-* files
i'll update git source and post a v0.3 test kernel soon
Click to expand...
Click to collapse
Any idea about the current buglist?
Sent from my One S using Tapatalk 2
RockR172 said:
Any idea about the current buglist?
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
i think we need a ported 4.2.2 rom to check them...
dmesg is pretty good
logcat show errors and crash, maybe rom related, maybe not
pirlano said:
i think we need a ported 4.2.2 rom to check them...
dmesg is pretty good
logcat show errors and crash, maybe rom related, maybe not
Click to expand...
Click to collapse
If you have been following the zenROM thread, me and usaff22 were trying to do the same, but the kernel never booted past the boot animation(technically it did, but nvm) and so we put it on hold until we had a booting kernel..
Now I don't have much time, since I got exams.. So maybe @usaff22 could help in the port of 4.2.2 based Sense..
Sent from my One S using Tapatalk 2
RockR172 said:
If you have been following the zenROM thread, me and usaff22 were trying to do the same, but the kernel never booted past the boot animation(technically it did, but nvm) and so we put it on hold until we had a booting kernel..
Now I don't have much time, since I got exams.. So maybe @usaff22 could help in the port of 4.2.2 based Sense..
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
me too, ****ing exams
btw, cannot use rom because of this error (phone is unusable), error is repeated thousand times:
Code:
E/AndroidRuntime(21591): FATAL EXCEPTION: main
E/AndroidRuntime(21591): java.lang.ExceptionInInitializerError
E/AndroidRuntime(21591): at com.android.providers.telephony.MmsSmsDatabaseHelper.<init>(MmsSmsDatabaseHelper.java:1063)
E/AndroidRuntime(21591): at com.android.providers.telephony.MmsSmsDatabaseHelper.getInstance(MmsSmsDatabaseHelper.java:1072)
E/AndroidRuntime(21591): at com.android.providers.telephony.SearchdbProvider.onCreate(SearchdbProvider.java:93)
E/AndroidRuntime(21591): at android.content.ContentProvider.attachInfo(ContentProvider.java:1085)
E/AndroidRuntime(21591): at android.app.ActivityThread.installProvider(ActivityThread.java:5516)
E/AndroidRuntime(21591): at android.app.ActivityThread.installContentProviders(ActivityThread.java:5097)
E/AndroidRuntime(21591): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5034)
E/AndroidRuntime(21591): at android.app.ActivityThread.access$1300(ActivityThread.java:162)
E/AndroidRuntime(21591): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1432)
E/AndroidRuntime(21591): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(21591): at android.os.Looper.loop(Looper.java:158)
E/AndroidRuntime(21591): at android.app.ActivityThread.main(ActivityThread.java:5751)
E/AndroidRuntime(21591): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(21591): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime(21591): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1083)
E/AndroidRuntime(21591): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:850)
E/AndroidRuntime(21591): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(21591): Caused by: java.lang.NoClassDefFoundError: android.provider.Telephony$MmsSms
E/AndroidRuntime(21591): at com.android.providers.telephony.util.DatabaseMonitor.<clinit>(DatabaseMonitor.java:22)
E/AndroidRuntime(21591): ... 17 more
I/ActivityManager( 792): Start proc com.android.nfc for restart com.android.nfc: pid=21603 uid=1027 gids={41027, 3002, 3001, 1015, 1028}
W/ActivityManager( 792): Process com.android.phone has crashed too many times: killing!
I/ActivityManager( 792): Recipient 21591
I/ActivityManager( 792): Process com.android.phone (pid 21591) has died.
I/ActivityManager( 792): Start proc com.android.phone for restart com.android.phone: pid=21616 uid=1001 gids={41001, 3002, 3001, 3003, 5012, 1026, 5006, 5011, 1028}
D/PhoneStatusBar( 1253): updateIcon slot=nfc index=13 viewIndex=0 old=StatusBarIcon(pkg=com.android.nfcuser=0 id=0x7f020005 level=0 visible=false num=0 ) icon=StatusBarIcon(pkg=com.android.nfcuser=0 id=0x7f020005 level=0 visible=true num=0 ) compareIcon= name=bottom_divider_glow vis=false >> true
D/PhoneStatusBar( 1253): updateIcon slot=nfc index=13 viewIndex=0 old=StatusBarIcon(pkg=com.android.nfcuser=0 id=0x7f020005 level=0 visible=true num=0 ) icon=StatusBarIcon(pkg=com.android.nfcuser=0 id=0x7f020005 level=0 visible=false num=0 ) compareIcon= name=bottom_divider_glow vis=true >> false
basically com.android.phone problem and nfc (we don't have nfc)
maybe @usaff22 already know the problem...how i can fix network signal and remove nfc stuff?
btw v0.3 uploaded on second post
EDIT: commit done
EDIT2: maybe i found the most important problem: sd cards (internal partition of course) seems not mounted, it will not save picture (camera and camcorder should be working): "Unable to save file to storage card due to insufficient file permissions", and i think it's a kernel problem, since i have the same behaviour with Sense 4+ too
I will post logcat and dmesg and try to fix sdcard mount
did you do anything to rom? like any kind of porting?
pirlano said:
EDIT2: maybe i found the most important problem: sd cards (internal partition of course) seems not mounted, it will not save picture (camera and camcorder should be working): "Unable to save file to storage card due to insufficient file permissions", and i think it's a kernel problem, since i have the same behaviour with Sense 4+ too
I will post logcat and dmesg and try to fix sdcard mount
Click to expand...
Click to collapse
The mount error might be from the Rom
I'm going to try with the kernel and stock 4.2.2 to see if I can help in any way nice work
Sent from my HTC VLE_U using Tapatalk 2
Flashalot said:
The mount error might be from the Rom
I'm going to try with the kernel and stock 4.2.2 to see if I can help in any way nice work
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
you left out a bunch of the fuse_sdcard stuff and other things fuse uses
but we dont need to emulate SDcard like other devices do since we have partiiton
rc420head said:
did you do anything to rom? like any kind of porting?
Click to expand...
Click to collapse
no, zero, untouched :silly:
Flashalot said:
The mount error might be from the Rom
I'm going to try with the kernel and stock 4.2.2 to see if I can help in any way nice work
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
i checked with adb and sdcard is mounted correctly, so maybe it's rom related