Related
Hi
I updated my Google Play services to latest and I have been getting this notification when I go to Internet wifi or mobile data.
authorization problem if the problem persists please log in and log out and try it again.
I do not want to make factory reset until CM12 comes out.
here is logcat
Code:
--------- beginning of /dev/log/main
--------- beginning of /dev/log/system
E/wpa_supplicant( 2513): wpa_driver_nl80211_driver_cmd: failed to issue private commands
E/WifiStateMachine( 794): Unexpected BatchedScanResults :null
E/wpa_supplicant( 2513): wpa_driver_nl80211_driver_cmd: failed to issue private commands
E/ConnectivityService( 794): Unexpected mtu value: [email protected]
E/PlayEventLogger( 3088): Invalid device id 9cb3889439509678
E/PhoneMonitor( 3153): onOtaspChanged old =0, new =3
E/AudioManagerAndroid( 3182): BLUETOOTH permission is missing!
E/AudioManagerAndroid( 3385): BLUETOOTH permission is missing!
F/ActivityManager( 794): Service ServiceRecord{42866038 u0 com.google.android.music/.net.NetworkMonitor} in process ProcessRecord{42e61648 3088:com.google.android.music:main/u0a65} not same as in map: null
F/ActivityManager( 794): Service ServiceRecord{427a3950 u0 com.google.android.music/.preferences.MusicPreferenceService$MusicPreferenceServiceBinder} in process ProcessRecord{42e61648 3088:com.google.android.music:main/u0a65} not same as in map: null
E/AuthorizationBluetoothService( 1571): Proximity feature is not enabled.
E/GCoreFlp( 1608): Bound FusedProviderService with LocationManager
E/AudioManagerAndroid( 3758): BLUETOOTH permission is missing!
E/dalvikvm( 3798): Could not find class 'android.app.Notification$Action$Builder', referenced from method f.a
E/dalvikvm( 3798): Could not find class 'android.app.RemoteInput[]', referenced from method f.a
E/SQLiteLog( 3798): (1) no such table: mmsconfig
E/Babel ( 3798): canonicalizeMccMnc: invalid mccmnc nullnull
P.S: I have removed google play services and updated it back still this problem is there. Then when I change my language to English notification stays in my language
EDIT: It is pure stock no Root or anything!
Same error
I have the same error "PlayEventLogger( 3088): Invalid device id" on my Moto G 1st gen
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
CyanogenMod 12.1 is a free, community built distribution of Android 5.1.1 (LolliPop) which greatly extends the capabilities of your phone.
This is the UNOFFICIAL Weekly Build of CM12.1 for the AT&T HTC One XL based on current Nightlies w/ HEAVILY MODIFIED PARTITION SCHEME.
**SWITCHING TO THESE BUILDS WILL REQUIRE A FULL DEVICE WIPE. BACKUP EVERYTHING**
Our /userdata partiton is to small for LP and art opts for apps and fill up quickly. These builds provide a long term solution to this by re-arranging which partitions are used to house which files systems. Here's how it's done:
by-name/fat {~12GB US, ~23GB EU models}(previously our internal_sdcard storage) -> is now used for /data, which will include a /data/media style sdcard like what is used on newer android devices
by-name/userdata {~2.5GB} (previously our /data partition) -> is now used to house /system. This now larger /system dir is big enough to allow for full dex-preopt which will speed up first boot but results in larger zip files
by-name/system {~1.5 GB} previously used for /system is no longer used.
To hear about the latest updates and changes to CyanogenMod as a whole, please follow +CyanogenMod on Google+!
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installation Instructions (These are all required)
FOLLOW THESE STEPS CLOSELY
IF COMING FROM CM-12.1 OFFICIAL BUILDS
SKIP TO STEP 3
THE MODIFIED RECOVERY LISTED BELOW SUPPORTS BOTH LAYOUTS
wiping "by-name/system" as EXT4 or FAT will enable TWRP to swtich back and forth
from EVITA <-> EVITAX
S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
Update to 3.18 RUU or later.
BACKUP EVEYTHING YOU WANT TO KEEP TO A PC/OTG DRIVE WE WILL BE WIPING EVERYTHING
Flash this custom TWRP recovery that supports EvitaX scheme.
Reboot to recovery, From the "WIPE" menu choose "ADVANCED WIPE", then manually change /system to "FAT" format.
Reboot to recovery again to allow TWRP to setup the modified partition layout. From the "WIPE" menu choose FORMAT DATA, then manually wipe from the advanced wipe menu: /system, /cache, /dalvik
Reboot to recovery again to allow TWRP to setup it's storage and configs on the newly formatted /data partition
Download latest build from theflamingskull.com/evita.html .
Locate 5.1 Gapps via a quick Google search.( I prefer opengapps.org )
Use "adb push", "adb sideload", or MTP to trasfer ROM/GAPPS to device
Install ROM and gapps.
Enjoy Quick boot up and usable space for apps.
TO REVERT TO STOCK LAYOUT:
The modified recovery mounts the old "by-name/system" partition as sdcard1 for easy revert.
reboot to recovery
In recovery, wipe /system using the "Advanced wipe" menu. Select "Sdcard1" and use the "Change File System" option to convert /Sdcard1 to EXT4.
reboot to recovery, the standard fstab will load.
Wipe all partitions as instructed above and proceed to flash desired ROM/gapps.
FOR OTHER DEVS:
To build with this new layout you will need
http://review.cyanogenmod.org/#/c/124797/1
If anybody really want's to build recovery on thier own the modded
tree can be found here:
https://github.com/jrior001/twrp-htc-evita/tree/twrp-dm
List all Questions and Off-Topic discussions here
Huge thanks:
h8rift,intervigil, deck, mdmower, invisiblek, flyhalf205 - Great team to work with for the HTC MSM8960 device family.
XDA:DevDB Information
CM12.1 EvitaX Unofficial, ROM for the AT&T HTC One X
Contributors
jrior001
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: hboot 2.14 or higher
Based On: CM
Version Information
Status: Stable
Created 2015-12-17
Last Updated 2016-01-03
Reserved
Revised Partition Layout
You Sir gave my Evita a third life!
Thanks again.
Going to test it out, will report back, using f2fs on data and cache before switching twrp versions and it seems to have kept the partition scheme of that after wiping, hopefully no problems from that
Update: So it installed well, no errors i've seen, installs apks very nice and quick, no freezes of any kind, overall very solid rom
this looks awesome!!!
Sir Is there any way to use /system partition as sd card or for swap.
Toqeer said:
Sir Is there any way to use /system partition as sd card or for swap.
Click to expand...
Click to collapse
Both of those "could" be done in theory.
Its only ~1.2 GB, I didn't really even consider mounting it as sdcard because its so small.
For swap, the zram feature we already added a while back is considerably faster than swap on a ext4 partiton so I wouldn't advise doing this.
Sent from my ASUS_Z00A using Tapatalk
So installed flawlessly without any error after running couple of hours it seems heavy battery draining even 11% within 15 minutes however all other things works like a charm, will be report back after a day. One question sir can I flash torched kernel?
@jrior001 - First of all, awesome work. Evita is one of the best devices around and I've been owning it since 2013. Its so unfortunate that Evita didnt get a partition update like Jewel got. This is simply awesome.
2 questions:
What needs to be done if we decide to switch back to a sense rom?
The 1.2 GB that is free is lost/wasted? Can that be added to the 12GB? Reason i ask is, my Evita has only 16GB, which already is pretty less considering how easy it has become to find 64GB devices.
jrior001 said:
Its only ~1.2 GB, I didn't really even consider mounting it as sdcard because its so small.
Click to expand...
Click to collapse
Haha, only 1.2GB With 16GB in the hood, 1.2GB is like 16%
Can we utilize that 1.2GB space as well? Can it be added to /data so that its added space could be used as well.
:good:
Sam3087 said:
@jrior001 - First of all, awesome work. Evita is one of the best devices around and I've been owning it since 2013. Its so unfortunate that Evita didnt get a partition update like Jewel got. This is simply awesome.
2 questions:
What needs to be done if we decide to switch back to a sense rom?
The 1.2 GB that is free is lost/wasted? Can that be added to the 12GB? Reason i ask is, my Evita has only 16GB, which already is pretty less considering how easy it has become to find 64GB devices.
Haha, only 1.2GB With 16GB in the hood, 1.2GB is like 16%
Can we utilize that 1.2GB space as well? Can it be added to /data so that its added space could be used as well.
:good:
Click to expand...
Click to collapse
1. Flash your old regular twrp back and wipe everything! Reformat sdcard to fat32/vfat and reflash normal build ROM.
2. If anything it would have to be mounted as a separate "internal sdcard" similar to how the old sdcard was mounted. Its possible but its messy and confusing. I was trying to keep this as clean and simple as possible.
There was also some talk of moving cache to that partition but honestly were not gaining enough to any of it all that exciting
2.
Sent from my ASUS_Z00A using Tapatalk
is the TWRP 2.8.7.0 EvitaX version a modified recovery from the original? i already have the regular 2.8.7.0 version installed but wondering if it would accept the 12.1 EvitaX rom?
droydr said:
is the TWRP 2.8.7.0 EvitaX version a modified recovery from the original? i already have the regular 2.8.7.0 version installed but wondering if it would accept the 12.1 EvitaX rom?
Click to expand...
Click to collapse
If you want to use this modified ROM, then the modified EvitaX recovery is required. It is matched to the new partition layout. This is not optional.
Sent from my ASUS_Z00A using Tapatalk
Hi jrior,
First of all, everything is working great! Thank you so much for your efforts!
I've two questions, though.
1. The ROM says that there is an upgrade and suggests what looks like a regular CM12.1 download. If I let it upgrade, it will bootloop, right?
2. What if I want to install another ROM using the same configuration? Would I have to rebuild the entire ROM or would it be enough to replace storage_list.xml, fstab and init.target.rc? I see that there is also a mk file there which implies that something must be built. What if I skip this step?
Thanks!
thelonewolf_pav said:
Hi jrior,
First of all, everything is working great! Thank you so much for your efforts!
I've two questions, though.
1. The ROM says that there is an upgrade and suggests what looks like a regular CM12.1 download. If I let it upgrade, it will bootloop, right?
2. What if I want to install another ROM using the same configuration? Would I have to rebuild the entire ROM or would it be enough to replace storage_list.xml, fstab and init.target.rc? I see that there is also a mk file there which implies that something must be built. What if I skip this step?
Thanks!
Click to expand...
Click to collapse
1. Yes this is a problem I can't work around, luckily my recovery won't let you flash that build.
2. Yes that ROM would need to be rebuilt. The storage.XML gets imbedded in frameworks.jar and can't just be copied ROM to ROM
Sent from my ASUS_Z00A using Tapatalk
jrior001 said:
1. Yes this is a problem I can't work around, luckily my recovery won't let you flash that build.
2. Yes that ROM would need to be rebuilt. The storage.XML gets imbedded in frameworks.jar and can't just be copied ROM to ROM
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Cool, thanks man!
So, there is actually one feature (so far) that I'm missing in the PAC ROM, namely: ambient display. That is, the display would come on whenever I pass my hand over the phone. This was actually very useful for me, and battery penalty was minimal. I remember trying to cook this into some other ROM, and managed to get the options showing in the settings menu, but the thing never actually worked for me. Would you know how to add this feature?
Otherwise, it's a great ROM, everything is super smooth, zero glitches so far.
Hey jrior001 man,
Can I waste a couple of minutes more of your time?
So, I'm trying to get your ROM to have ambient display. I installed xposed and added a module that enables it in settings (effectively, it does the same thing as recompiling SystemUI and framework-res and changing flags like doze_display_state_supported and config_dozeAfterScreenOff. I guess you know what I'm talking about. I looked at the original java code, and all it seems to do is enter the daydream state with some special mode enabled.
So, everything seems to be working great, but instead of getting the dimmed black-and-white display, I get nothing, the display stays blank. Doze is working though, because the moment I touch the screen, it comes up in full color just as it should. So, it does wake up and enter daydream, but just doesn't show anything.
Now, looking at logcats at that time, here's what I see:
Code:
E/qdoverlay( 160): Failed to call ioctl MSMFB_DISPLAY_COMMIT err=Operation not permitted
E/qdoverlay( 160): static bool overlay::eek:verlay::displayCommit(const int&, uint32_t): commit failed
E/qdhwcomposer( 160): hwc_set_primary: display commit fail for 0 dpy!
E/qdoverlay( 160): Failed to call ioctl MSMFB_OVERLAY_SET err=Operation not permitted
E/qdoverlay( 160): MdpCtrl failed to setOverlay, restoring last known good ov info
E/qdoverlay( 160): == Bad OVInfo is: mdp_overlay z=0 fg=1 alpha=255 mask=-1 flags=0x40000 id=-1
E/qdoverlay( 160): src msmfb_img w=736 h=1280 format=0 MDP_RGB_565
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): == Last good known OVInfo is: mdp_overlay z=0 fg=0 alpha=0 mask=0 flags=0x0 id=-1
E/qdoverlay( 160): src msmfb_img w=0 h=0 format=0 MDP_RGB_565
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): MdpCtrl Lkgo ov has id -1, will not restore
E/qdoverlay( 160): Ctrl commit failed set overlay
E/qdhwcomposer( 160): configureLowRes: commit failed for low res panel
E/qdoverlay( 160): Failed to call ioctl MSMFB_OVERLAY_SET err=Operation not permitted
E/qdoverlay( 160): MdpCtrl failed to setOverlay, restoring last known good ov info
E/qdoverlay( 160): == Bad OVInfo is: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x20000 id=-1
E/qdoverlay( 160): src msmfb_img w=736 h=1280 format=13 MDP_RGBA_8888
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): == Last good known OVInfo is: mdp_overlay z=0 fg=0 alpha=0 mask=0 flags=0x0 id=-1
E/qdoverlay( 160): src msmfb_img w=0 h=0 format=0 MDP_RGB_565
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): MdpCtrl Lkgo ov has id -1, will not restore
E/qdoverlay( 160): Ctrl commit failed set overlay
E/qdhwcomposer( 160): configure: configMdp failed for dpy 0
E/qdhwcomposer( 160): hwc_sync: ioctl MSMFB_BUFFER_SYNC failed, err=Operation not permitted
E/qdhwcomposer( 160): hwc_sync: acq_fen_fd_cnt=1 flags=0 fd=15 dpy=0 numHwLayers=3
This repeats many times until the phone goes back to sleep or until I touch the screen and wake it up.
Strangely enough, regular daydreams do work, and clock, for example, displays fine on a dimmed black-and-white screen.
Any ideas where to look?
Thanks in advance!
thelonewolf_pav said:
Hey jrior001 man,
Can I waste a couple of minutes more of your time?
So, I'm trying to get your ROM to have ambient display. I installed xposed and added a module that enables it in settings (effectively, it does the same thing as recompiling SystemUI and framework-res and changing flags like doze_display_state_supported and config_dozeAfterScreenOff. I guess you know what I'm talking about. I looked at the original java code, and all it seems to do is enter the daydream state with some special mode enabled.
So, everything seems to be working great, but instead of getting the dimmed black-and-white display, I get nothing, the display stays blank. Doze is working though, because the moment I touch the screen, it comes up in full color just as it should. So, it does wake up and enter daydream, but just doesn't show anything.
Now, looking at logcats at that time, here's what I see:
Code:
E/qdoverlay( 160): Failed to call ioctl MSMFB_DISPLAY_COMMIT err=Operation not permitted
E/qdoverlay( 160): static bool overlay::eek:verlay::displayCommit(const int&, uint32_t): commit failed
E/qdhwcomposer( 160): hwc_set_primary: display commit fail for 0 dpy!
E/qdoverlay( 160): Failed to call ioctl MSMFB_OVERLAY_SET err=Operation not permitted
E/qdoverlay( 160): MdpCtrl failed to setOverlay, restoring last known good ov info
E/qdoverlay( 160): == Bad OVInfo is: mdp_overlay z=0 fg=1 alpha=255 mask=-1 flags=0x40000 id=-1
E/qdoverlay( 160): src msmfb_img w=736 h=1280 format=0 MDP_RGB_565
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): == Last good known OVInfo is: mdp_overlay z=0 fg=0 alpha=0 mask=0 flags=0x0 id=-1
E/qdoverlay( 160): src msmfb_img w=0 h=0 format=0 MDP_RGB_565
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): MdpCtrl Lkgo ov has id -1, will not restore
E/qdoverlay( 160): Ctrl commit failed set overlay
E/qdhwcomposer( 160): configureLowRes: commit failed for low res panel
E/qdoverlay( 160): Failed to call ioctl MSMFB_OVERLAY_SET err=Operation not permitted
E/qdoverlay( 160): MdpCtrl failed to setOverlay, restoring last known good ov info
E/qdoverlay( 160): == Bad OVInfo is: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x20000 id=-1
E/qdoverlay( 160): src msmfb_img w=736 h=1280 format=13 MDP_RGBA_8888
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): == Last good known OVInfo is: mdp_overlay z=0 fg=0 alpha=0 mask=0 flags=0x0 id=-1
E/qdoverlay( 160): src msmfb_img w=0 h=0 format=0 MDP_RGB_565
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): MdpCtrl Lkgo ov has id -1, will not restore
E/qdoverlay( 160): Ctrl commit failed set overlay
E/qdhwcomposer( 160): configure: configMdp failed for dpy 0
E/qdhwcomposer( 160): hwc_sync: ioctl MSMFB_BUFFER_SYNC failed, err=Operation not permitted
E/qdhwcomposer( 160): hwc_sync: acq_fen_fd_cnt=1 flags=0 fd=15 dpy=0 numHwLayers=3
This repeats many times until the phone goes back to sleep or until I touch the screen and wake it up.
Strangely enough, regular daydreams do work, and clock, for example, displays fine on a dimmed black-and-white screen.
Any ideas where to look?
Thanks in advance!
Click to expand...
Click to collapse
We need like 3 patches for it to work... I'll try to grab them and get another 12.1 evitaX build up tom maybe.
Sent from my ASUS_Z00A using Tapatalk
jrior001 said:
We need like 3 patches for it to work... I'll try to grab them and get another 12.1 evitaX build up tom maybe.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
cool! thanks!
thelonewolf_pav said:
cool! thanks!
Click to expand...
Click to collapse
Build is up w/ambient included. May never see that on official builds though, my patches already got rejected.
Sent from my ASUS_Z00A using Tapatalk
jrior001 said:
Build is up w/ambient included. May never see that on official builds though, my patches already got rejected.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
you just made my day! thanks!
I'm making a CM12.1 ROM port. Every time after compilation, I'm just stuck on the boot screen. My logcat logs always look like this:
Code:
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
I/DEBUG ( 1389): tid 15467 does not exist in pid 15467. ignoring debug request
I/ServiceManager( 1385): service 'media.audio_flinger' died
I/ServiceManager( 1385): service 'media.player' died
I/ServiceManager( 1385): service 'media.camera' died
I/ServiceManager( 1385): service 'media.audio_policy' died
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
I/mediaserver(15513): ServiceManager: 0x2a00b448
I/AudioFlinger(15513): Using default 3000 mSec as standby time.
E/MediaPlayerFactory(15513): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(15513): calling dlsym on pFactoryLib for FACTORY_CREATE_FN
E/MediaPlayerFactory(15513): registering DASH Player factory...
I/CameraService(15513): CameraService started (pid=15513)
I/CameraService(15513): Loaded "BCM21553 Camera HAL" camera module
D/BcmCamera(15513): HAL_get_number_of_cameras: numCameras:1
I/AudioPolicyManagerBase(15513): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
I/AudioFlinger(15513): loadHwModule() Loaded primary audio interface from Samsung BCM21553 audio HW HAL (audio) handle 1
I/AudioFlinger(15513): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
I/AudioMixer(15513): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
I/AudioFlinger(15513): Using module 1 has the primary audio interface
D/AudioPolicyManagerBase(15513): setOutputDevice() changing device from (2) to (2) force (1) delayMs (0) on Output (2)
I/AudioFlinger(15513): AudioFlinger's thread 0x40f53008 ready to run
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
D/audio_hw_primary(15513): call=n, earpiece=n hp=n speaker=y sco=n a2dp=n out_device=2
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
I/audio_a2dp_hw(15513): adev_open: adev_open in A2dp_hw module
I/AudioFlinger(15513): loadHwModule() Loaded a2dp audio interface from A2DP Audio HW HAL (audio) handle 3
I/AudioFlinger(15513): loadHwModule() Loaded usb audio interface from USB audio HW HAL (audio) handle 4
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
E/AudioFlinger(15513): no wake lock to update!
I/r_submix(15513): adev_open(name=audio_hw_if)
I/r_submix(15513): adev_init_check()
I/AudioFlinger(15513): loadHwModule() Loaded r_submix audio interface from Wifi Display audio HAL (audio) handle 5
I/AudioPolicyService(15513): Loaded audio policy from LEGACY Audio Policy HAL (audio_policy)
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
D/AndroidRuntime(15512):
D/AndroidRuntime(15512): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime(15512): CheckJNI is OFF
D/dalvikvm(15512): Unable to stat classpath element '/system/framework/core.jar'
D/dalvikvm(15512): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm(15512): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm(15512): DexOpt: --- BEGIN 'conscrypt.jar' (bootstrap=1) ---
E/dalvikvm(15640): Fatal error: java/lang/Object
E/dalvikvm(15640): VM aborting
F/libc (15640): Fatal signal 6 (SIGABRT) at 0x00003d18 (code=-6), thread 15640 (dexopt)
I/DEBUG ( 1389): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1389): Build fingerprint: 'Samsung/cm_totoro/totoro:5.1.1/KTU84Q/20150211:userdebug/release-keys'
I/DEBUG ( 1389): Revision: '0'
I/DEBUG ( 1389): pid: 15640, tid: 15640, name: dexopt >>> /system/bin/dexopt <<<
[A bunch of seemingly random (at least for such a noob like me) numbers]
W/dalvikvm(15512): DexOpt: --- END 'conscrypt.jar' --- status=0x0006, process failed
E/dalvikvm(15512): Unable to extract+optimize DEX from '/system/framework/conscrypt.jar'
D/dalvikvm(15512): Unable to process classpath element '/system/framework/conscrypt.jar'
D/dalvikvm(15512): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm(15512): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
D/dalvikvm(15512): DexOpt: --- BEGIN 'okhttp.jar' (bootstrap=1) ---
E/dalvikvm(15692): Fatal error: java/lang/Object
E/dalvikvm(15692): VM aborting
F/libc (15692): Fatal signal 6 (SIGABRT) at 0x00003d4c (code=-6), thread 15692 (dexopt)
I/DEBUG ( 1389): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1389): Build fingerprint: 'Samsung/cm_totoro/totoro:5.1.1/KTU84Q/20150211:userdebug/release-keys'
And so on, and so on, until it fails to load everything and starts all over again.
And yes, if you look at the logs, I am porting a ROM to an obsolete device and no, I don't really care that it's "not gonna work". I just want to fix that dex problem.
What I tried so far:
- cleaning up the rom (did nothing)
- changing up a few libraries that had something to do with "dex" (did nothing, but I might have missed something)
- re-unpacked the frameworks (did nothing)
- re-downloaded the rom then re-unpacked the frameworks (also did nothing)
- downloaded another rom and re-unpacked the frameworks (did nothing, what a waste of bandwidth)
- cleared Dalvik cache (did not do anything, I do that every build alongside with a factory wipe in CWM)
- changed the kernel TWICE (did nothing except for making logcat work (it wasn't working for a few builds))
Anyone got any ideas?
knuxfanwin8 said:
I'm making a CM12.1 ROM port. Every time after compilation, I'm just stuck on the boot screen. My logcat logs always look like this:
And so on, and so on, until it fails to load everything and starts all over again.
And yes, if you look at the logs, I am porting a ROM to an obsolete device and no, I don't really care that it's "not gonna work". I just want to fix that dex problem.
What I tried so far:
- cleaning up the rom (did nothing)
- changing up a few libraries that had something to do with "dex" (did nothing, but I might have missed something)
- re-unpacked the frameworks (did nothing)
- re-downloaded the rom then re-unpacked the frameworks (also did nothing)
- downloaded another rom and re-unpacked the frameworks (did nothing, what a waste of bandwidth)
- cleared Dalvik cache (did not do anything, I do that every build alongside with a factory wipe in CWM)
- changed the kernel TWICE (did nothing except for making logcat work (it wasn't working for a few builds))
Anyone got any ideas?
Click to expand...
Click to collapse
Yeah. You need to Deodex both ROM BASE and PORT BEFORE you build. That is the reason you keep getting dex errors. Use ASSAYYED Kitchen or @superR's Kitchen or similar to accomplish this ?
A big thank you to all the devs who made the official rom possible!
I just installed an app (EU Exit: ID Document Check) that needs to use the camera to scan a document. When the app switches to the camera, I only see a black screen. The logs seem to indicate that the app is calling into HAL to use the camera but for some reason the connection fails. Has anyone seen this before? Other apps do not seem to have a problem using the camera.
Code:
01-27 15:42:24.609 3025 3025 E Camera3-Device: Camera 0: waitUntilDrainedLocked: Error waiting for HAL to drain: Connection timed out (-110)
01-27 15:42:24.609 3025 3025 E Camera2Client: notifyError: Error condition 1 reported by HAL, requestId -1
01-27 15:42:24.712 3025 3025 D CameraTraces: Process trace saved. Use dumpsys media.camera to view.
01-27 15:42:24.712 3025 3025 E Camera2Client: stopPreviewL: Camera 0: Waiting to stop streaming failed: Connection timed out (-110)
01-27 15:42:24.718 3025 3499 E Camera3-Device: Camera 0: createDefaultRequest: Device has encountered a serious error
01-27 15:42:24.718 3025 3499 E Camera2-StreamingProcessor: updateRecordingRequest: Camera 0: Unable to create default recording request: Function not implemented (-38)
01-27 15:42:24.718 3025 3499 E Camera2Client: updateRequests: Camera 0: Unable to update recording request: Function not implemented (-38)
I am happy to provide the output from dumpsys media.camera (I have the pastebin link but the rules do not allow me to post it here)
Device: SM-G920F
ROM name: Official
Build number: 14.1-20190126-NIGHTLY-zerofltexx
kernel version and its settings: 2.10.61-gab2e937 [email protected] #1
I have the same problem, do you have a solution to resolve this ?