Database Info

[MOD] Settings.apk with ext partition info (for HD roms)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've modify standart Settings app from HD Rom, now Phone Storage Info is more friendly
It will work on Insert Coin or RCMixS or other Roms with 2.36.405.8 framework.
Here is 6 versions with different suffixes:
withCRT - with CRT TV animation switch
withoutCRT - without CRT TV animation switch
datasd - if ext partition mounted in /data/sd
systemsd - if ext partition mounted in /system/sd
sdext - if ext partition mounted in /sd-ext
Download and rename needed apk in Settings.apk and push in /system/app folder
Also Modified HTCAlbum, HTCMusic, Camera 3.0 and WeatherWidget here
*NOW ALL SIGNED))))

m0narx: have FC by tapping on Device Memory:
Code:
12:59:16.239 Info ActivityManager 528 Starting activity: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.deviceinfo.Memory } from pid 2416
12:59:16.348 Error 2416 statfs /mnt/asec/sd-ext failed, errno: 2
12:59:16.348 Debug AndroidRuntime 2416 Shutting down VM
12:59:16.348 Warning dalvikvm 2416 threadid=1: thread exiting with uncaught exception (group=0x4001d5a0)
12:59:16.348 Error AndroidRuntime 2416 FATAL EXCEPTION: main
12:59:16.348 Error AndroidRuntime 2416 java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.deviceinfo.Memory}: java.lang.IllegalArgumentException
12:59:16.348 Error AndroidRuntime 2416 at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2434)
12:59:16.348 Error AndroidRuntime 2416 at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2455)
12:59:16.348 Error AndroidRuntime 2416 at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1842)
12:59:16.348 Error AndroidRuntime 2416 at android.app.ActivityThread.access$1500(ActivityThread.java:132)
12:59:16.348 Error AndroidRuntime 2416 at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1033)
12:59:16.348 Error AndroidRuntime 2416 at android.os.Handler.dispatchMessage(Handler.java:99)
12:59:16.348 Error AndroidRuntime 2416 at android.os.Looper.loop(Looper.java:143)
12:59:16.348 Error AndroidRuntime 2416 at android.app.ActivityThread.main(ActivityThread.java:4196)
12:59:16.348 Error AndroidRuntime 2416 at java.lang.reflect.Method.invokeNative(Native Method)
12:59:16.348 Error AndroidRuntime 2416 at java.lang.reflect.Method.invoke(Method.java:507)
12:59:16.348 Error AndroidRuntime 2416 at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
12:59:16.348 Error AndroidRuntime 2416 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
12:59:16.348 Error AndroidRuntime 2416 at dalvik.system.NativeStart.main(Native Method)
12:59:16.348 Error AndroidRuntime 2416 Caused by: java.lang.IllegalArgumentException
12:59:16.348 Error AndroidRuntime 2416 at android.os.StatFs.native_setup(Native Method)
12:59:16.348 Error AndroidRuntime 2416 at android.os.StatFs.<init>(StatFs.java:32)
12:59:16.348 Error AndroidRuntime 2416 at com.android.settings.deviceinfo.Memory.updateMemoryStatus(Memory.java:451)
12:59:16.348 Error AndroidRuntime 2416 at com.android.settings.deviceinfo.Memory.onResume(Memory.java:199)
12:59:16.348 Error AndroidRuntime 2416 at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1266)
12:59:16.348 Error AndroidRuntime 2416 at android.app.Activity.performResume(Activity.java:3917)
12:59:16.348 Error AndroidRuntime 2416 at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2424)
12:59:16.348 Error AndroidRuntime 2416 ... 12 more
12:59:16.348 Warning ActivityManager 528 Force finishing activity com.android.settings/.deviceinfo.Memory
12:59:16.348 Warning ActivityManager 528 Force finishing activity com.android.settings/.framework.activity.HtcSettings

m0narx said:
View attachment 613891
I've modify standart Settings app from HD Rom, now Phone Storage Info is more friendly
It will work on Insert Coin or RCMixS or other Roms with 2.36.405.8 framework.
Just push Settings.apk in /system/app folder
Click to expand...
Click to collapse
Just want to ask if it is the one with crt on/off switches ?
Muxeu said:
m0narx: have FC by tapping on Device Memory:
Click to expand...
Click to collapse
hehe you was quick to test

Sorry, im forgot, about different mountpoints, now uploading)))

m0narx said:
Sorry, im forgot, about different mountpoints, now uploading)))
Click to expand...
Click to collapse
Hmm. Tried "sdext - if ext partition mounted in /sd-ext" with CRT:
Code:
15:30:39.918 Warning PackageParser 535 No actions in intent filter at /system/app/Settings.apk Binary XML file line #829
15:30:39.918 Info PackageManager 535 /system/app/Settings.apk changed; collecting certs
15:30:39.918 Debug dalvikvm 535 GC_CONCURRENT freed 213K, 37% free 4639K/7303K, external 0K/0K, paused 3ms+5ms
15:30:40.027 Error PackageParser 535 Package com.android.settings has no certificates at entry AndroidManifest.xml; ignoring!
15:30:40.027 Warning PackageManager 535 Failed verifying certificates for package:com.android.settings

Well, I signed pk and it works now
Thanks, man

Can you make a version for stock Sense FroYo ROMs?

Yes)) If you give framework and Settings.apk

Interesting!!!
Would you be able to make one for the HD2?!?!
I'm using the latest Bravo CyanogenMod-7 ROM (Nightly-91) - Slightly modded to run on the HD2 (Mods don't affect the framework-res.apk or Settings.apk).
My Ext3 Partition shows up as sd-ext.
I could provide whatever files you needed and test it willingly
A feature like this is always useful and now that i've seen it, I realise that it has always been missing!!!!
Thanks in advance

robocik said:
Just want to ask if it is the one with crt on/off switches ?
hehe you was quick to test
Click to expand...
Click to collapse
hey robo,
which one to choose for rcmix s
and how to apply it

nice work, i posted a link to your thread in my nightly build

That's awesome !
Why anybody didn't think of it previously?

This for the Cool Kingdom v4 would be nice.
Could you do that for it?
Just say what you need

ali_loly10 said:
hey robo,
which one to choose for rcmix s
and how to apply it
Click to expand...
Click to collapse
I'm using the CM7 version and have applied Settings.withoutCRT.systemsd.apk
You just replace rename it and replace settings.apk in the rom

KennyDumah said:
This for the Cool Kingdom v4 would be nice.
Could you do that for it?
Just say what you need
Click to expand...
Click to collapse
com.htc.resources.apk, framework-res.apk and Settings.apk)))

randomelements said:
I'm using the CM7 version and have applied Settings.withoutCRT.systemsd.apk
You just replace rename it and replace settings.apk in the rom
Click to expand...
Click to collapse
how to push the system app?
i've never tried using the adb push thingy. so i do not know how to push the settings.apk to system/app
can anyone teach me how to push this system apk and what app do i need?

Hey, monarx..
Are there additional dependencies for Settings.apk of GB Sense other than com.htc.resources.apk and framework-res.apk? I even tried Rosie.apk, but still a lot of values fail to decode

hi senior
thanks for great Mod
but i have HD2 and in hd2 don`t have edext partitions all HD2 with android have sd-ext
now in settings its work perfectly but free size for ext = system
for data and system is correct but value for sd-ext not correct,
please fix it (or set correct address for ed-ext )for me thank you very much

need help analyzing log

I'm trying to troubleshoot a problem I'm having where my phone will randomly switch from vibrate to audio on. so that's my first problem, can someone help me analyze my log to determine what is causing it? it started after updating my kernel. the second thing is that i'm seeing a bunch of lines I don't recognize:
??? this gets repeated excessively.
08-16 19:54:02.741 D/RecurrenceProcessor( 2688): RRULE := FREQ=WEEKLY;WKST=MO;BYDAY=MO,TU,WE,TH,FR
why is TouchPal dialer crashing? I don't notice anything
08-16 19:54:45.348 W/ActivityManager( 1344): Scheduling restart of crashed service com.cootek.smartdialer/.SmartDialerService in 5000ms
08-16 19:54:50.365 I/ActivityManager( 1344): Start proc com.cootek.smartdialer for service com.cootek.smartdialer/.SmartDialerService: pid=19378 uid=10094 gids={1007, 1015, 3003}
what is this?
08-16 19:54:50.615 I/PROFILE ( 1344): Group: Gmail containing : com.android.systemui : false
08-16 19:54:50.615 I/PROFILE ( 1344): Group: Phone containing : com.android.systemui : false
08-16 19:54:50.615 I/PROFILE ( 1344): Group: Calendar containing : com.android.systemui : false
08-16 19:54:50.615 I/PROFILE ( 1344): Group: Email containing : com.android.systemui : false
08-16 19:54:50.615 I/PROFILE ( 1344): Group: SMS containing : com.android.systemui : false
08-16 19:54:50.615 V/ProfileManager( 1641): No active group, returning default: Other
08-16 19:54:50.615 V/AudioManager( 1641): shouldVibrate, group: Other mode: DEFAULT

1. What rom are you using?
2. What kernel were you trying to flash?
Sent from my Inspire 4G using XDA Premium App

dooyoo222 said:
1. What rom are you using?
2. What kernel were you trying to flash?
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
1. cm7. unsure what nightly it corresponds to. the dev is alienmind over in the DHD forums.
2. lordmod 6.9
never had this issue with 6.8 and previous. I already reported to the kernel thread but i'm trying to dissect the issue myself.

Well I can't be much help since I don't use either of those two. Maybe try using the 6.8 kernel again and see what happens?
Sent from my Inspire 4G using XDA Premium App

Facebook 1.8 Force Close when trying to update status - other fb account works...

Hi there,
i got some strange problem with the facebook app of a friend. We have both Samsung Galaxy SII with same ROM/Kernel and Baseband (2.3.6 XWKK5 with CF-Root CWM5). My Facebook app works flawless, but the fb app of my friend does not - which is very strange. everytime if the button for status update or location sharing is touched, the fb app force closes immediately.
i tried some debugging with logcat and got this exception here:
Code:
13:01:38.342 Error AndroidRuntime 18381 java.lang.RuntimeException: Unable to start activity ComponentInfo{com.facebook.katana/com.facebook.katana.ComposerActivity}: java.lang.NumberFormatException: 1788360882834,2060337282074
13:01:38.342 Error AndroidRuntime 18381 at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1651)
13:01:38.342 Error AndroidRuntime 18381 at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1667)
13:01:38.342 Error AndroidRuntime 18381 at android.app.ActivityThread.access$1500(ActivityThread.java:117)
13:01:38.342 Error AndroidRuntime 18381 at android.app.ActivityThread$H.handleMessage(ActivityThread.java:935)
13:01:38.342 Error AndroidRuntime 18381 at android.os.Handler.dispatchMessage(Handler.java:99)
13:01:38.342 Error AndroidRuntime 18381 at android.os.Looper.loop(Looper.java:130)
13:01:38.342 Error AndroidRuntime 18381 at android.app.ActivityThread.main(ActivityThread.java:3691)
13:01:38.342 Error AndroidRuntime 18381 at java.lang.reflect.Method.invokeNative(Native Method)
13:01:38.342 Error AndroidRuntime 18381 at java.lang.reflect.Method.invoke(Method.java:507)
13:01:38.342 Error AndroidRuntime 18381 at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:907)
13:01:38.342 Error AndroidRuntime 18381 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:665)
13:01:38.342 Error AndroidRuntime 18381 at dalvik.system.NativeStart.main(Native Method)
I tried everything... wiping data of fb app, wiping cache/dalvik cache,... but the problem still occurs.
Now, something really strange: I wiped data of the fb app, and logged in with MY account, not his... and now with my account it works flawlessy. but after i wiped data again and used the login data of my friend again => force close when trying to update status or location.
my fb account on my and his device: works
his fb account on my and his device: force close when updating status
someone any ideas ?
quite strange?
resolved:
for other users with the same problem:
problem occurs if you are using more than one custom list in the privacy settings, specially for the default posting permissions.
To check that goto the privacy settings, click on custom in the "Control your Default Privacy" Section.
For make this visible select "Friends" or "Specific People or Lists". If you use "Specific People or List", than more than ONE person or lists will cause the ForceClose. So just enter only ONE list/person.
For "hide this from" there is no limit of lists/persons, all working...

Solution confirmed working, had the same issue, fixed it by leaving just one list of people to share to... Thanks!

[ACKNOWLEDGED BUG] Android 5.1 Camera can't connect... ever

It appears this is long-running problem plaguing N5's for some time. I saw sporadical "Can't connect to camera" on 5.0.1 but after update to 5.1 (I flashed the stock image) I literally cannot get the camera working for more than 1 unlock session.
I did have root but I thought it might be a problem so I unrooted and reflashed stock, but no help. The only other thing I can imagine to do is factory reset, but I have a few security apps that will need some time to be setup again (mostly banking and 2 factor stuff), plus I am not sure if I can restore data w/o Titanium using Google's new 'Restore', so I'm keeping the factory reset as last option.
Any ideas what I can do here? Is it happening to anyone else on 5.1? Can I somehow verify it's not a HW issue? (although, it was working on 5.0.1 so it's unlikely HW issue).
The only apps which *may* be accessing camera are Trusted face unlock, Whatsapp and Hangouts. Nothing special I'd say
Click to expand...
Click to collapse
Acknowledged bug by google https://code.google.com/p/android/issues/detail?id=160609

cthulu said:
It appears this is long-running problem plaguing N5's for some time. I saw sporadical "Can't connect to camera" on 5.0.1 but after update to 5.1 (I flashed the stock image) I literally cannot get the camera working for more than 1 unlock session.
I did have root but I thought it might be a problem so I unrooted and reflashed stock, but no help. The only other thing I can imagine to do is factory reset, but I have a few security apps that will need some time to be setup again (mostly banking and 2 factor stuff), plus I am not sure if I can restore data w/o Titanium using Google's new 'Restore', so I'm keeping the factory reset as last option.
Any ideas what I can do here? Is it happening to anyone else on 5.1? Can I somehow verify it's not a HW issue? (although, it was working on 5.0.1 so it's unlikely HW issue).
The only apps which *may* be accessing camera are Trusted face unlock, Whatsapp and Hangouts. Nothing special I'd say
Click to expand...
Click to collapse
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?

zagorteney said:
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
Click to expand...
Click to collapse
I did reflash stock without wiping (to actually get the 5.1 upgrade - I didn't want to wait for OTA). If you wipe you start with clean phone, which I didn't want
So my problem manifests like this:
boot phone
camera seems to be working (opening camera app doesn't crash but actually allows taking pics)
after few screen locks/minutes, camera doesnt work anymore - opening camera either immediately crashes or shows "Can't connect to camera"
reboot fixes it for another few minutes

cthulu said:
I did reflash stock without wiping (to actually get the 5.1 upgrade - I didn't want to wait for OTA). If you wipe you start with clean phone, which I didn't want
So my problem manifests like this:
boot phone
camera seems to be working (opening camera app doesn't crash but actually allows taking pics)
after few screen locks/minutes, camera doesnt work anymore - opening camera either immediately crashes or shows "Can't connect to camera"
reboot fixes it for another few minutes
Click to expand...
Click to collapse
That's why i was asking this. Data partition can also cause problems. Flash completely and it will fix it.

zagorteney said:
That's why i was asking this. Data partition can also cause problems. Flash completely and it will fix it.
Click to expand...
Click to collapse
I also have this issue. I flashed 5.1 with the flash-all script, which did wipe my data. Any suggestions?

PHPanos said:
I also have this issue. I flashed 5.1 with the flash-all script, which did wipe my data. Any suggestions?
Click to expand...
Click to collapse
And this was happening immediately after booting your phone? Then must be hardware. ?

It works fine everytime I reboot, for xx minutes. It's difficult to say for how long but not too long. I see that "Trusted face" unlock stops working and that's a signal the whole camera subsystem is gone. Everything else works just no camera access from any app is possible.

zagorteney said:
And this was happening immediately after booting your phone? Then must be hardware. ��
Click to expand...
Click to collapse
No. It works at first. Then after a few times of locking/unlocking the phone and opening the camera app and switching to front camera it shuts down. The problem goes away after a reboot but it comes back again after a while.
cthulu: We have both the same problem.

Same here for me since upgrading to 5.0 every now and then i must reboot my phone in order to fix it.This is really annoying maybe we should wait for a new camera app by google ?

Same issue
Hi guys,
This has been the problem for me since 5.0 . I thought maybe its just me. But after a while, the camera stops working. I assume this is a s/w issue since the phone was fine in Kitkat. Even in 5.1 the issue persists.

I am also getting frequent "can't connect to camera" since 5.1. Nexus 5.

Do you know if there's an issue for this in Google's issue tracker? I'm sure they won't check xda forums for bug reports.
I've clicked a few times to send the error to Google when starting the camera but I honestly don't think they're checking those...
I hoped full wipe will fix this but as it happens to the folks who did full wipe I'm rather not going to do it yet...

Already reported here https://code.google.com/p/android/i... Owner Summary Stars&groupby=&sort=&id=160609

zagorteney said:
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
Click to expand...
Click to collapse
Flashing system image does not mean factory reset. You can flash just the system and boot images without wiping data.

THRUSTer said:
Flashing system image does not mean factory reset. You can flash just the system and boot images without wiping data.
Click to expand...
Click to collapse
You are on a right direction. Just start to read a little more careful.

Happens the same for me.
Some days ago i see that the face Trusted face have Stop. So, now i desible the Trusted face, clear data of camera app e until now (about 2 hours) the camera works fine, without any shut up.
Try you too, i think that the problems are in the Smart lock.

Many people have this issue since they moved to 5.1
'Hardware defect' and 'no full wipe' were told to be the culprit straight away, but looking at the bug report that seems unjustified, especially given the number of reports with exactly this issue.
The issue arises when using face unlock. It somehow breaks the camera and the face unlock itself after a short while until you reboot it. I'm not sure if this happens with everyone or only with specific configurations, but for sure disabling face unlock has solved this for me.
zagorteney said:
Flash completely and it will fix it.
Click to expand...
Click to collapse
zagorteney said:
Then must be hardware. ?
Click to expand...
Click to collapse
So please be a bit more thorough in your advice....

Can't connect to camera error Nexus 5 Android 5.1
Hi gays, I am new here. I keep getting the ' can't connect to camera' error on my Nexus 5 Android 5.1, and I tried everything that is suggested here and it did not help. I turned off Face unlock, uninstall Viber and install again, cleared cache of the camera and force stop and everything else. Only help restart the device. I succeeded to catch the logcat with the error. Here is the logcat:
04-02 21:19:26.744 724-2687/? I/ActivityManager﹕ START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.GoogleCamera/com.android.camera.CameraLauncher bnds=[849,1532][1050,1784] (has extras)} from uid 10019 on display 0
04-02 21:19:26.747 724-2687/? V/WindowManager﹕ addAppToken: AppWindowToken{2498ae08 token=Token{83da7ab ActivityRecord{3a47c5fa u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher t32}}} to stack=1 task=32 at 0
04-02 21:19:26.751 724-819/? V/WindowManager﹕ Based on layer: Adding window Window{15bd6123 u0 Starting com.google.android.GoogleCamera} at 3 of 9
04-02 21:19:26.824 724-1360/? I/ActivityManager﹕ Start proc 22932:com.google.android.GoogleCamera/u0a42 for activity com.google.android.GoogleCamera/com.android.camera.CameraLauncher
04-02 21:19:26.837 1361-3270/? W/GsaThreadFactory﹕ Not creating another thread for Background Blocking because there are already 30
04-02 21:19:26.876 22932-22932/? W/ResourcesManager﹕ Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
04-02 21:19:26.935 22932-22932/? W/CAM_Log﹕ Tag SessionStatsCollector is 2 chars longer than limit.
04-02 21:19:26.989 22932-22932/? I/CameraManagerGlobal﹕ getCameraService: Reconnecting to camera service
04-02 21:19:27.254 22932-22979/? I/CAM2PORT_AndCamAgntImp﹕ Opening camera 0 with camera1 API
04-02 21:19:27.266 193-1682/? W/AudioFlinger﹕ acquireAudioSessionId() unknown client 22932 for session 116
04-02 21:19:27.268 193-1682/? I/AwesomePlayer﹕ setDataSource_l(<no-scheme URI suppressed>)
04-02 21:19:27.289 193-1682/? W/AudioFlinger﹕ acquireAudioSessionId() unknown client 22932 for session 117
04-02 21:19:27.290 193-1682/? I/AwesomePlayer﹕ setDataSource_l(<no-scheme URI suppressed>)
04-02 21:19:27.301 193-1682/? I/Camera2ClientBase﹕ Camera 0: Opened. Client: com.google.android.GoogleCamera (PID 22932, UID 10042)
04-02 21:19:27.302 22932-22992/? W/CAM_PhotoData﹕ Zero dimension in ContentResolver for /storage/emulated/0/DCIM/Camera/IMG_20150402_180439.jpg:0x0
04-02 21:19:27.303 193-1682/? D/mm-camera-intf﹕ mm_camera_open: dev name = /dev/video1, cam_idx = 1
04-02 21:19:27.304 206-206/? I/mm-camera-sensor﹕ module_sensor_start_session:583 session 1
04-02 21:19:27.305 206-206/? E/mm-camera-sensor﹕ csiphy_open:126 VIDIOC_MSM_CSIPHY_IO_CFG failed
04-02 21:19:27.305 206-206/? E/mm-camera-sensor﹕ module_sensor_init_session:335 failed rc -1
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ sensor_close:2499 VIDIOC_MSM_SENSOR_CFG failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_init_session:500 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_start_session:612 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_start_session:617 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ sensor_get_capabilities:1632 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_query_mod:2421 failed rc -4
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_hardware_process_command:254: failed, subdev not opened
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_query_mod:268: failed
04-02 21:19:27.307 206-206/? E/mm-camera﹕ pproc_module_query_mod:1697] error in cpp query mod
04-02 21:19:27.307 206-206/? I/mm-camera-sensor﹕ module_module_set_session_data:2666 max delay 2 report dSelay 1
04-02 21:19:27.307 206-206/? E/mm-camera﹕ isp_set_session_data: Session could not be found!
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_get_params_for_session_id:178, failed, session_id=0x1
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_set_session_data:329, failed
04-02 21:19:27.307 206-206/? E/mm-camera﹕ pproc_module_set_session_data:1928] error in cpp set_session_data
04-02 21:19:27.307 206-206/? D/mm-camera﹕ module_faceproc_set_session_data:1836] Per frame control 2 1
04-02 21:19:27.307 206-206/? I/mm-camera-sensor﹕ module_sensor_stop_session:636 session 1
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_deinit_session:526 ref count 0
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_stop_session:664 failed
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_stop_session:669 failed
04-02 21:19:27.307 206-206/? I/mm-camera﹕ cpp_module_stop_session:462, info: stopping session 1 ...
04-02 21:19:27.307 206-206/? I/mm-camera﹕ cpp_module_stop_session:504, info: session 1 stopped.
04-02 21:19:27.307 206-206/? I/mm-camera﹕ c2d_module_stop_session:322, info: stopping session 1 ...
04-02 21:19:27.307 206-206/? I/mm-camera﹕ c2d_module_stop_session:361, info: session 1 stopped.
04-02 21:19:27.308 206-206/? E/mm-camera﹕ main: New session [1] creation failed with error
04-02 21:19:27.308 193-1682/? D/mm-camera-intf﹕ mm_camera_open: opened, break out while loop
04-02 21:19:27.308 193-1682/? E/mm-camera-intf﹕ mm_camera_open: cannot open control fd of '/dev/video1' (Bad address)
04-02 21:19:27.308 193-1682/? E/mm-camera-intf﹕ camera_open: mm_camera_open err = -1
04-02 21:19:27.308 193-1682/? E/QCamera3HWI﹕ camera_open failed.
04-02 21:19:27.308 193-1682/? E/Camera3-Device﹕ Camera 0: initialize: Could not open camera: No such device (-19)
04-02 21:19:27.308 193-1682/? E/Camera2ClientBase﹕ initialize: Camera 0: unable to initialize device: No such device (-19)
04-02 21:19:27.308 193-1682/? E/CameraService﹕ connectFinishUnsafe: Could not initialize client from HAL module.
04-02 21:19:27.308 193-1682/? I/Camera2Client﹕ Camera 0: Closed
04-02 21:19:27.309 193-1682/? I/Camera2ClientBase﹕ Closed Camera 0. Client was: com.google.android.GoogleCamera (PID 22932, UID 10042)
04-02 21:19:27.313 193-1682/? W/AudioFlinger﹕ session id 116 not found for pid 22932
04-02 21:19:27.317 193-1682/? W/AudioFlinger﹕ session id 117 not found for pid 22932
04-02 21:19:27.318 22932-22979/? W/CameraBase﹕ An error occurred while connecting to camera: 0
04-02 21:19:27.318 22932-22979/? E/CAM2PORT_AndCamAgntImp﹕ RuntimeException during CameraAction[OPEN_CAMERA] at CameraState[1]
java.lang.RuntimeException: Fail to connect to camera service
at android.hardware.Camera.<init>(Camera.java:497)
at android.hardware.Camera.open(Camera.java:342)
at com.android.ex.camera2.portability.AndroidCameraAgentImpl$CameraHandler.handleMessage(AndroidCameraAgentImpl.java:370)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
04-02 21:19:27.371 22932-23015/? D/OpenGLRenderer﹕ Use EGL_SWAP_BEHAVIOR_PRESERVED: true
04-02 21:19:27.377 22932-22932/? D/Atlas﹕ Validating map...
04-02 21:19:27.381 724-1360/? V/WindowManager﹕ Adding window Window{312f9c81 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher} at 3 of 10 (before Window{15bd6123 u0 Starting com.google.android.GoogleCamera})
04-02 21:19:27.387 22932-22932/? W/CAM_CameraActivity﹕ Camera open failure: HIST_ID0_-1_1_HEND
04-02 21:19:27.387 22932-22932/? E/CAM_Util﹕ Show fatal error dialog
04-02 21:19:27.402 724-2689/? V/WindowManager﹕ Adding window Window{302ae167 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher} at 4 of 11 (before Window{15bd6123 u0 Starting com.google.android.GoogleCamera})
04-02 21:19:27.406 22932-22932/? D/WearableClient﹕ WearableClientImpl.onPostInitHandler: done
04-02 21:19:27.431 22932-23015/? I/Adreno-EGL﹕ <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 01/14/15, ab0075f, Id3510ff6dc
04-02 21:19:27.432 22932-23015/? I/OpenGLRenderer﹕ Initialized EGL, version 1.4
04-02 21:19:27.444 22932-23015/? D/OpenGLRenderer﹕ Enabling debug mode 0
04-02 21:19:27.487 22932-22932/? I/CAM_UsageStats﹕ PlayLogger.onLoggerConnected
04-02 21:19:27.512 724-2689/? D/WifiService﹕ acquireWifiLockLocked: WifiLock{NlpWifiLock type=2 [email protected]}
04-02 21:19:27.516 22932-22932/? I/CAM_PhotoModule﹕ onPreviewUIReady
04-02 21:19:27.516 22932-22932/? I/CAM_PhotoModule﹕ attempted to start preview before camera device
04-02 21:19:27.518 724-851/? E/WifiStateMachine﹕ WifiStateMachine CMD_START_SCAN source 10007 txSuccessRate=0.00 rxSuccessRate=0.00 targetRoamBSSID=10:fe:ed:4e:a3:ae RSSI=-47
04-02 21:19:27.574 724-819/? I/ActivityManager﹕ Displayed com.google.android.GoogleCamera/com.android.camera.CameraLauncher: +790ms
Please HELP, it's really annoying
Best regards.

meranto said:
The issue arises when using face unlock. It somehow breaks the camera and the face unlock itself after a short while until you reboot it. I'm not sure if this happens with everyone or only with specific configurations, but for sure disabling face unlock has solved this for me.
So please be a bit more thorough in your advice....
Click to expand...
Click to collapse
Nope..
https://code.google.com/p/android/i... Owner Summary Stars&groupby=&sort=&id=160609
has a lot of people who didn't use face unlock and still experienced the issue.

Replay
Hi meranto,
thanks for the replay. I did not use face unlock and the issue still show up

Porting CM to new device system_server crash

Hi !
I'm trying to port CM10 (old system) to Galaxy Fame Lite (old and cheap phone). I may try to port a later version of CM if I succeed for CM10...
Right now the system boots but remains blocked in the boot animation. I've managed to use adb shell (this has not been easy). What happens right now is that system_server commits suicide with the following message in /data/system/[email protected]<time>.txt
Code:
Process: system_server
Build: samsung/cm_nevisnvess/nevisnvess:4.1.2/JZO54K/eng.grenie.20160927.110731:eng/test-keys
android.view.InflateException: Binary XML file line #71: Error inflating class android.widget.ScrollView
at android.view.LayoutInflater.createView(LayoutInflater.java:613)
at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
at android.view.LayoutInflater.onCreateView(LayoutInflater.java:660)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:746)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:275)
at com.android.internal.app.AlertController.installContent(AlertController.java:240)
at android.app.AlertDialog.onCreate(AlertDialog.java:336)
at android.app.Dialog.dispatchOnCreate(Dialog.java:351)
at android.app.Dialog.show(Dialog.java:256)
at com.android.server.am.ActivityManagerService$2.handleMessage(ActivityManagerService.java:910)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1431)
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.constructNative(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
at android.view.LayoutInflater.createView(LayoutInflater.java:587)
... 17 more
Caused by: android.content.res.Resources$NotFoundException: Resource is not a Drawable (color or path): TypedValue{t=0x1/d=0x10804f4 a=1 r=0x10804f4}
at android.content.res.Resources.loadDrawable(Resources.java:1921)
at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
at android.view.View.initializeScrollbars(View.java:3859)
at android.view.View.<init>(View.java:3493)
at android.view.ViewGroup.<init>(ViewGroup.java:427)
at android.widget.FrameLayout.<init>(FrameLayout.java:101)
at android.widget.ScrollView.<init>(ScrollView.java:161)
at android.widget.ScrollView.<init>(ScrollView.java:157)
... 20 more
Anybody knows what goes wrong?
Thanks!

Is there any custom recovery and rom for this device??