Develop Bugs

Two 4.4 Roms i didn't see around here

As most of you probably are, ever since i've tried CM11, i've been searching for a "stable" KitKat rom. Didn't have much luck, but i thought i'll share my findings
First up is Gummy Rom from Team Gummy, which i didn't even see in the Android Development subforum. They're doing nightlies for the P930, but seem to have some problems right now, as the last nightly is dated 01-05-2014. You can check those out at
http://old.androidfilehost.com/main/Team_Gummy/p930/nightly/
Second one is MoKee, of which navik did a 4.3 build, but they also have KitKat nightlies for the P930.
http://download.mfunz.com/?device=p930
On to what you'll probably want to know.. do these roms work? well... kinda...
The MoKee "Release" from 01-18-2014 is pretty stable, fast and has some neat additions from CM and (possibly) AOKP. You can even finally restore your backups from Titanium, as MoKee lets you choose where to install (!) an apk... change that to internal from default and ALL apps install correctly like they should. Now for the downside... you can probably guess... yup, camera's broken *sad face panda*... you can start up any cam-app and it will show the image from the sensor, but as soon as you take a shot, it will FC and save a 2KB file in your DCIM folder...
oh, and it has some chinese crapware (baidu) installed, but you can easily remove these with Titanium Backup.
On to the second Rom... Gummy Rom from Team Gummy...it's a lean build based on AOSP with a few picks from CM, AOKP and PA, mostly visual stuff from aokp (center clock etc.) and HALO/PIE from PA. It's helluvalot fast and after a quick adb push for the newest adreno drivers, i can even play Asphalt 8 on High Details. Downside on this rom... apk install error galore, no XDA-app, some games don't install, browser crashes often, absolutely not a daily driver...
have fun experimenting, have you found something else? would like to know ^^

thanks for ur support and is like no much user+dev on this device! threads emty to compere to other devices....
dreaming of getting another device:crying:

I will have to try the later one myself, thanks for posting the info. The biggest issue is that cm is not stable so anything built on that rom is bound to have issues. Most people are sticking with jb for the time being until a better KitKat is available.
As far as activity on this forum, this is not a nexus device but it does have a fair following.
Sent using XDA Premium HD app
Nz

I thought I would look at the Mokee kernel, so the camera errors out like
Code:
I/QualcommCameraHardware( 147): stopPreviewInternal: old frame thread completed.
I/QualcommCameraHardware( 147): stopPreviewInternal X: 0
V/QualcommCameraHardware( 147): updatePictureDimension: 3264x2448 <- 960x720
V/QualcommCameraHardware( 147): initRaw E: picture size=3264x2448
V/QualcommCameraHardware( 147): initRaw: initializing mRawHeap.
E/QualcommCameraHardware( 147): ION allocation failed
E/QualcommCameraHardware( 147): do_mmap: Open device /dev/pmem_smipool failed!
E/QualcommCameraHardware( 147): ERROR : initraw , createSnapshotMemory failed
E/QualcommCameraHardware( 147): initRaw failed. Not taking picture.
E/CAM_AndroidCameraManagerImpl( 3247): take picture failed.
W/dalvikvm( 3247): threadid=16: thread exiting with uncaught exception (group=0x4156ec80)
E/AndroidRuntime( 3247): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 3247): Process: com.android.camera2, PID: 3247
E/AndroidRuntime( 3247): java.lang.RuntimeException: takePicture failed
A good picture taken with CM11 looks like
Code:
I/QualcommCameraHardware( 146): stopPreviewInternal: old frame thread completed.
I/QualcommCameraHardware( 146): stopPreviewInternal X: 0
V/QualcommCameraHardware( 146): updatePictureDimension: 3264x2448 <- 960x720
V/QualcommCameraHardware( 146): initRaw E: picture size=3264x2448
V/QualcommCameraHardware( 146): initRaw: initializing mRawHeap.
E/QualcommCameraHardware( 146): bool android::QualcommCameraHardware::createSnapshotMemory(int, int, bool, int) Raw memory index: 0 , fd is 67
E/QualcommCameraHardware( 146): Received following info for raw mapped data:0x44840000,handle:0x121eb48, size:11985408,release:0x405d6941
E/QualcommCameraHardware( 146): Registering buffer 0 with fd :67 with kernel
V/QualcommCameraHardware( 146): use_all_chnls = 0
As you can see the "ION allocation failed" is the obvious fail point, now where that is logged is the next big secret.. qcom/camera/qcamera2/hal/QCameraMemory.cpp has a log with the message in it, but changing the message seems to have no affect..
Other things I have tried, I have tried compiling the mokee with the hardware and kernel folders from CM11 - the camera still fails, so it must be with the device / vendor folders.
nz

[ROM e975] Pure AOSP build based on Google's master branch sources

Gave up trying, this thread is dead
Due to lack of time and due to almost bricking my phone I'm giving up this project and I returned my phone to stock. There are many things that manufacturers configure that are specific to the phone hardwares that all custom ROMs doesn't configure. For example, if battery is too low, phone turns off automatically to avoid reaching 0% as lithium batteries doesn't like to become too empty, if phone is overheating, apps that could cause a high CPU usage bringing more heat, are not executed and, while in high temperatures, you can't increase screen brightness above a calculated percentage. So I think that to maintain my phone's health it's better stock ROM.
Hello everyone! This is my first attempt to build a ROM from the ground up, so it has some problems that I have to address. I could build and boot it successfuly on my e975 device and all hardware seems to work. Currently it's based on platform version 5.0.50.50.50.50
ISSUES:
GApps force closes when you try to create a google account in the smartphone
Phone app is force closing when trying to make or receive calls
Camera
Browser force closes, doesn't start
WORKING
Phone is online for the operator
GPS
Bluetooth
3G
SMS
WiFi
Galery app
Music app
All Google apps, except creating a Google account in the phone
UNTESTED:
NFC (turns on, but don't have any other NFC device to test connectivity)
4G
I would be grateful if the community could help me out to address the ROM issues, pointing me the path to follow. I'm a beginner in ROM development and don't know much of Android's inner parts.
INSTALL INSTRUCTIONS
1 - Download ROM from http://d-h.st/jRme and kernel from http://d-h.st/4tm9
2 - Make a factory reset
3 - Flash the ROM
4 - Flash the kernel (flash it, or won't boot)
5 - Reboot the phone and wait for almost 20 minutes for it's first boot
Sources:
Directly from Google: http://source.android.com/source/downloading.html
Device tree: https://github.com/lollipop-og/android_device_lge_geehrc/tree/aod (thanks to @Kevinjoa)
Kernel binary: Solid_Kernel_V1.5GEE-LP --> http://loller79.altervista.org/ (thanks to @Loller79)

Phone apk issue, some clue?
Well, here is some logcat that I could get from my phone while trying to make a call, here it indicates a null pointer exception, but I don't know the reason. Can someone help me to figure it out?
Code:
01-11 23:37:35.370 628 1733 I ActivityManager: START u0 {act=android.intent.action.CALL dat=tel:xxxx-xxxx cmp=com.android.server.telecom/.CallActivity (has extras)} from uid 10004 on display 0
01-11 23:37:35.444 5296 5296 I Telecom : InCallController: Attempting to bind to InCall com.android.dialer, is dupe? false
01-11 23:37:35.449 5296 5296 I Telecom : CallAudioManager: updateAudioStreamAndMode, mIsRinging: false, mIsTonePlaying: false
01-11 23:37:35.454 5296 5296 I Telecom : CallAudioManager: updateAudioStreamAndMode, mIsRinging: false, mIsTonePlaying: false
01-11 23:37:35.455 5296 5296 I Telecom : CallAudioManager: requestAudioFocusAndSetMode, stream: -1 -> 0
01-11 23:37:35.455 628 1733 I MediaFocusControl: AudioFocus requestAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
01-11 23:37:35.457 203 203 D audio_hw_primary: adev_set_mode: mode 201-11 23:37:35.468 5296 5296 I Telecom : CallAudioManager: changing audio stat
e from [AudioState isMuted: false, route; EARPIECE, supportedRouteMask: EARPIECE, SPEAKER] to [AudioState isMuted: false, route; EARPIECE, supportedRouteMask: EARPIECE, SPEAKER]
01-11 23:37:35.486 628 628 V GpsNetInitiatedHandler: ACTION_NEW_OUTGOING_CALL - false
01-11 23:37:35.491 628 1733 W InputMethodManagerService: Window already focused, ignoring focus gain of: [email protected] [email protected], token = [email protected]
01-11 23:37:35.505 5296 5296 D AndroidRuntime: Shutting down VM
01-11 23:37:35.506 5296 5296 E AndroidRuntime: FATAL EXCEPTION: main
01-11 23:37:35.506 5296 5296 E AndroidRuntime: Process: com.android.server.telecom, PID: 5296
01-11 23:37:35.506 5296 5296 E AndroidRuntime: java.lang.NullPointerException: in == null
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at libcore.io.Streams.readFully(Streams.java:74)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at java.io.DataInputStream.readShort(DataInputStream.java:152)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:2064)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at java.io.ObjectInputStream.<init>(ObjectInputStream.java:371)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.i18n.phonenumbers.prefixmapper.PrefixFileReader.loadMappingFileProvider(PrefixFileReader.java:56)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.i18n.phonenumbers.prefixmapper.PrefixFileReader.<init>(PrefixFileReader.java:48)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.i18n.phonenumbers.geocoding.PhoneNumberOfflineGeocoder.<init>(PhoneNumberOfflineGeocoder.java:43)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.i18n.phonenumbers.geocoding.PhoneNumberOfflineGeocoder.getInstance(PhoneNumberOfflineGeocoder.java:57)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.internal.telephony.CallerInfo.getGeoDescription(CallerInfo.java:561)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.internal.telephony.CallerInfo.updateGeoDescription(CallerInfo.java:546)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.internal.telephony.CallerInfoAsyncQuery$CallerInfoAsyncQueryHandler.onQueryComplete(CallerInfoAsyncQuery.java:315)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at android.content.AsyncQueryHandler.handleMessage(AsyncQueryHandler.java:344)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at android.os.Looper.loop(Looper.java:135)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5223)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:372)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:754)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:644)
01-11 23:37:35.507 628 1658 W ActivityManager: Process com.android.server.telecom has crashed too many times: killing!
01-11 23:37:35.507 628 1658 W ActivityManager: Force finishing activity com.android.server.telecom/.CallActivity

Trying another build using CM device tree to see what I get. Until now build is going well, I adapted their device tree to AOSP, don't know if it will boot or even finish building successfuly

Congratulations, looking forward to seeing your dev skills go from strength to strength

lsrzj said:
Trying another build using CM device tree to see what I get. Until now build is going well, I adapted their device tree to AOSP, don't know if it will boot or even finish building successfuly
Click to expand...
Click to collapse
Stuck at the bootscreen, not able to connect adb to make a logcat during the boot. Compiled gproj kernel from CM, lost recovery mode, it appears a black background screen with an Android open in the chest and no menu appears. So I'm not able to restore my previous backup using CWM, so I had to put phone in download mode and return to stock, then unlock it, root it, install CWM to restore my previous backup!

Gave up trying
Due to lack of time and due to almost bricking my phone I'm giving up this project and I returned my phone to stock. There are many things that manufacturers configure that are specific to the phone hardwares that all custom ROMs doesn't configure, for example, if battery is too low, phone turns off automatically to avoid reaching 0% as lithium batteries doesn't like to become too empty, and if phone is overheating, apps that could cause a high CPU usage bringing more heat, are not executed and, while in high temperatures, you can't increase screen brightness above a calculated percentage. So I think that to maintain my phone's health it's better stock ROM.

Nai Nai, don't give up, but don't dream too much...
Tip: Start with small projects, don't try to do things that don't even great devs accomplished as a beginner, and for the purpose of your project:
Yes you can build AOSP for an unsupported device, but without knowing what you need to take from other custom ROM repos is very difficult and with wrong blobs, very dangerous. AOSP builds straight from the source code are terrible, at least my G2 build was, old school dialer, lot's of broken and junk stuff, that's why there's AOSP custom based ROM, if you know Git you can create very cool projects, much better than AOSP builds.
eg.:
Choose a good source to get based on, like Paranoid if you don't plan to get lot's of features, pick a good optimized toolchain instead of Google's one, enable some optimizations like -O3 and Graphite, strict aliasing for beginners is not recommended, and debloat getting rid of weird and old apps and wallpapers, the result is amazing.
Here's an example you can follow to learn these stuff, https://github.com/SaberSunset, it's not fully implemented yet on PA but within some weeks it will be the way I want it. There are some articles in my manifest you can read, my project is self explanatory, it teaches in the commits and why I did something, it's a good source to learn.
Good learning;
Boa sorte também... podes me mandar MP se precisar de ajuda.

GalaticStryder said:
Tip: Start with small projects, don't try to do things that don't even great devs accomplished as a beginner, and for the purpose of your project:
Yes you can build AOSP for an unsupported device, but without knowing what you need to take from other custom ROM repos is very difficult and with wrong blobs, very dangerous. AOSP builds straight from the source code are terrible, at least my G2 build was, old school dialer, lot's of broken and junk stuff, that's why there's AOSP custom based ROM, if you know Git you can create very cool projects, much better than AOSP builds.
eg.:
Choose a good source to get based on, like Paranoid if you don't plan to get lot's of features, pick a good optimized toolchain instead of Google's one, enable some optimizations like -O3 and Graphite, strict aliasing for beginners is not recommended, and debloat getting rid of weird and old apps and wallpapers, the result is amazing.
Here's an example you can follow to learn these stuff, https://github.com/SaberSunset, it's not fully implemented yet on PA but within some weeks it will be the way I want it. There are some articles in my manifest you can read, my project is self explanatory, it teaches in the commits and why I did something, it's a good source to learn.
Good learning;
Boa sorte também... podes me mandar MP se precisar de ajuda.
Click to expand...
Click to collapse
I understood what you mean, but problem is that there are many other things to check. I like very much custom ROM's functionalities, I tried this pure AOSP to start modifying it and create something. But, first, I needed to understand how make files interact with each other and many other things, like sepolicy files. Other thing is that, with all custom ROM's I already dealt with, my phone was always too hot and I thought it was something normal as it's a Quadcore processor and the phones LED backlight are very strong. But, when I returned my phone to stock, I could see that I was wrong, what happens with all custom ROM's around is that kernels out there, somehow, doesn't work exactly the same as stock ones. Manufacturers configure something more on kernel/driver/software that avoids phone becoming too hot. So I saw that, to do the same as they do, I should understand my phone's hardware in depth to know what are the correct drivers, what is in stock kernel/driver/software that controls better phone's temperature.... and then implement it in my own ROM. The time to learn about it all, I don't have. I tried to download many kernel sources out there to build too, like Loller79's Solid Kernel. But every time I tried to build, it would give me an error message telling that BATT_2100_LGE was undeclared. If Loller built his binaries based on the sources in his GIT, why his builds weren't failing? If I download CM's GPROJ kernel source I can build it without a problem. I tried with his sources because his kernel binary could boot this pure AOSP build successfuly.
The latest build I tried was with CM's device tree and GPROJ kernel, it booted but stuck at bootscreen and lost CWM, when I booted into it no menu was appearing, just a black background with an android with an open chest. When I tried to return it to stock using LGMobile Support Tool putting phone in download mode, something in that build modified, somehow, the Phone's USB PID and the LG software couldn't detect my phone. The last chance I had to return it to stock was using LG Flashtool 2014 that ignored everything and just uploaded the firmware to the phone.
Thanks for your input here @GalaticStryder

Nexus 7 (2013) won't connect to my home Wi-Fi (running Android 6.0.1)

I bought a second-hand Wi-Fi only Google/Asus Nexus 7 (2013), which came wiped, with Android 6.0.1 installed, but it won't connect to my home Wi-Fi router. It will save the details but when it tries to connect I get the message 'Wi-Fi Connection Failure'. I am certain the password is correct.
Other devices connect without problems, and I have successfully connected the Nexus to a work Wi-Fi network, but it's no good to me if it won't connect at home. I previously had another Nexus 7 that would connect fine, but was recently bricked by an Android update.
I have tried all suggested fixes I can find online, including:
- Restarting the router
- Wiping data on the Nexus 7
- Restarting the Nexus (in safe and normal mode)
- Switching Wi-Fi/Airplane Mode on and off on the Nexus 7
- Forgetting and re-entering the network details
- Changing the frequency on the Nexus 7
- Changing the channel and security settings on the router
None has any effect. As far as I know my router is on the latest firmware. It's a Sky Hub, which broadcasts at 2.4 GHz.
Can anyone think of a fix or any known issues? I can return the device free to the retailer but would like to see if I can avoid the hassle. I'm also going to avoid doing anything involving rooting the tablet for now in case that voids the warranty.

Let's see the log:
turn off wifi
run: adb logcat -v time > log.txt
turn on wifi
when you see the error, end adb log with ctrl-c immediately
zip up "log.txt" and attach it here
Be quick because the log gets big fast.
We'll be interested mostly in wpa_supplicant messages:
Code:
03-10 23:35:08.318 I/wpa_supplicant( 1879): wlan0: Trying to associate with SSID 'CC1'
03-10 23:35:08.432 D/Tethering( 561): sendTetherStateChangedBroadcast 1, 0, 0
03-10 23:35:08.436 D/NetworkManagementService( 561): getNetworkStatsSummaryXt:NetworkStats: elapsedRealtime=102015
03-10 23:35:08.436 D/NetworkManagementService( 561): [0] iface=lo uid=-1 set=ALL tag=0x0 rxBytes=0 rxPackets=0 txBytes=0 txPackets=0 operations=0
03-10 23:35:08.438 D/NetworkManagementService( 561): getNetworkStatsSummaryDev:NetworkStats: elapsedRealtime=102019
03-10 23:35:08.438 D/NetworkManagementService( 561): [0] iface=lo uid=-1 set=ALL tag=0x0 rxBytes=0 rxPackets=0 txBytes=0 txPackets=0 operations=0
03-10 23:35:08.441 I/wpa_supplicant( 1879): wlan0: Associated with 00:04:ad:d5:e2:0a
03-10 23:35:08.722 I/wpa_supplicant( 1879): wlan0: WPA: Key negotiation completed with 00:04:ad:d5:e2:0a [PTK=CCMP GTK=CCMP]
03-10 23:35:08.726 I/wpa_supplicant( 1879): wlan0: CTRL-EVENT-CONNECTED - Connection to 00:04:ad:d5:e2:0a completed [id=0 id_str=]

Ok, no idea if I've done this right, but here goes (I'm trying to connect to SSID SKY8DBEF):
Code:
03-11 22:37:49.844 D/WifiService( 597): Connect with config* ID: -1 SSID: "SKY8DBEF" PROVIDER-NAME: null BSSID: null FQDN: null PRIO: 0
03-11 22:37:49.844 D/WifiService( 597): KeyMgmt: WPA_PSK Protocols:
03-11 22:37:49.844 D/WifiService( 597): AuthAlgorithms:
03-11 22:37:49.844 D/WifiService( 597): PairwiseCiphers:
03-11 22:37:49.844 D/WifiService( 597): GroupCiphers:
03-11 22:37:49.844 D/WifiService( 597): PSK: *
03-11 22:37:49.844 D/WifiService( 597): Enterprise config:
03-11 22:37:49.844 D/WifiService( 597): IP config:
03-11 22:37:49.844 D/WifiService( 597): IP assignment: DHCP
03-11 22:37:49.844 D/WifiService( 597): Proxy settings: NONE
03-11 22:37:49.844 D/WifiService( 597): cuid=-1 luid=-1 lcuid=0 userApproved=USER_UNSPECIFIED noInternetAccessExpected=false roamingFailureBlackListTimeMilli: 1000
03-11 22:37:49.844 D/WifiService( 597): triggeredLow: 0 triggeredBad: 0 triggeredNotHigh: 0
03-11 22:37:49.844 D/WifiService( 597): ticksLow: 0 ticksBad: 0 ticksNotHigh: 0
03-11 22:37:49.844 D/WifiService( 597): triggeredJoin: 0
03-11 22:37:49.844 D/WifiService( 597): autoJoinBailedDueToLowRssi: false
03-11 22:37:49.844 D/WifiService( 597): autoJoinUseAggressiveJoinAttemptThreshold: 0
03-11 22:37:49.845 I/chatty ( 597): uid=1000(system) WifiStateMachin expire 26 lines
03-11 22:37:49.850 E/WiFiServiceImpl ( 597): CONNECT nid=-1 uid=1000 name=android.uid.system:1000
03-11 22:37:49.850 D/WifiService( 597): Connect with config* ID: -1 SSID: "SKY8DBEF" PROVIDER-NAME: null BSSID: null FQDN: null PRIO: 0
03-11 22:37:49.850 D/WifiService( 597): KeyMgmt: WPA_PSK Protocols:
03-11 22:37:49.850 D/WifiService( 597): AuthAlgorithms:
03-11 22:37:49.850 D/WifiService( 597): PairwiseCiphers:
03-11 22:37:49.850 D/WifiService( 597): GroupCiphers:
03-11 22:37:49.850 D/WifiService( 597): PSK: *
03-11 22:37:49.850 D/WifiService( 597): Enterprise config:
03-11 22:37:49.850 D/WifiService( 597): IP config:
03-11 22:37:49.850 D/WifiService( 597): IP assignment: DHCP
03-11 22:37:49.850 D/WifiService( 597): Proxy settings: NONE
03-11 22:37:49.850 D/WifiService( 597): cuid=-1 luid=-1 lcuid=0 userApproved=USER_UNSPECIFIED noInternetAccessExpected=false roamingFailureBlackListTimeMilli: 1000
03-11 22:37:49.850 D/WifiService( 597): triggeredLow: 0 triggeredBad: 0 triggeredNotHigh: 0
03-11 22:37:49.850 D/WifiService( 597): ticksLow: 0 ticksBad: 0 ticksNotHigh: 0
03-11 22:37:49.850 D/WifiService( 597): triggeredJoin: 0
03-11 22:37:49.850 D/WifiService( 597): autoJoinBailedDueToLowRssi: false
03-11 22:37:49.850 D/WifiService( 597): autoJoinUseAggressiveJoinAttemptThreshold: 0
03-11 22:37:49.854 D/audio_hw_primary( 195): out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
03-11 22:37:49.887 I/Keyboard.Facilitator( 1008): onFinishInput()
03-11 22:37:49.891 D/AudioFlinger( 195): mixer(0xb4200000) throttle end: throttle time(4)
03-11 22:37:50.021 I/wpa_supplicant( 961): wlan0: Trying to associate with SSID 'SKY8DBEF'
03-11 22:37:51.062 I/wpa_supplicant( 961): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=c0:3e:0f:8e:ea:15 status_code=1
03-11 22:37:51.062 I/wpa_supplicant( 961): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="SKY8DBEF" auth_failures=1 duration=10 reason=CONN_FAILED
03-11 22:37:53.070 D/audio_hw_primary( 195): disable_audio_route: reset and update mixer path: low-latency-playback
03-11 22:37:53.071 D/audio_hw_primary( 195): disable_snd_device: snd_device(2: speaker)
03-11 22:38:01.658 I/wpa_supplicant( 961): wlan0: CTRL-EVENT-SSID-REENABLED id=1 ssid="SKY8DBEF"
03-11 22:38:01.665 I/chatty ( 597): uid=1000(system) WifiStateMachin expire 10 lines
03-11 22:38:16.975 E/ ( 193): invalid crash request of size 4 (from pid=5518 uid=0)
03-11 22:38:17.101 I/chatty ( 597): uid=1000 system_server expire 1 line
03-11 22:38:17.127 E/Diag_Lib( 5816): Diag_LSM_Init: Failed to open handle to diag driver, error = 2
03-11 22:38:17.127 E/Sensors ( 5816): sns_fsa_la.c(386):fsa: fflush failed, 9
03-11 22:38:17.128 E/Sensors ( 5816): sns_fsa_la.c(386):fsa: fflush failed, 9
03-11 22:38:17.154 W/Sensors ( 5816): sns_smr_la.c(446):smr_la: smr_apps_la_thread_main is starting, fd=11, sns_smr.en_rx_msg_ptr=b70009f8
03-11 22:38:17.175 W/Sensors ( 5816): sns_sam_app.c(6827):sns_sam_reg_algo: Registering algo service 16, err 0
03-11 22:38:17.195 E/Sensors ( 5816): sns_debug_main.c(565):Debug Config File missing in EFS!
03-11 22:38:28.381 I/chatty ( 597): uid=1000(system) HeapTaskDaemon expire 1 line
03-11 22:38:49.925 I/Keyboard.Facilitator.LanguageModelFlusher( 1008): run()
03-11 22:38:49.925 I/Keyboard.Facilitator( 1008): flushDynamicLanguageModels()
03-11 22:38:58.429 I/wpa_supplicant( 961): wlan0: Trying to associate with SSID 'SKY8DBEF'
03-11 22:38:59.567 I/wpa_supplicant( 961): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=c0:3e:0f:8e:ea:15 status_code=1
03-11 22:38:59.567 I/wpa_supplicant( 961): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="SKY8DBEF" auth_failures=1 duration=10 reason=CONN_FAILED
[/QUOTE]

mpb39 said:
Ok, no idea if I've done this right, but here goes (I'm trying to connect to SSID SKY8DBEF)
Click to expand...
Click to collapse
It logs:
Code:
wlan0: CTRL-EVENT-ASSOC-[B]REJECT [/B]bssid=c0:3e:0f:8e:ea:15
wlan0: ... id=1 ssid="SKY8DBEF" [B]auth_failures=1[/B]
The router rejects your N7. Can you check the router's own logs?
On your N7 go to WiFi Direct and rename the device. This will re-generate fresh /data/misc/wifi/wpa_supplicant.conf and may fix the problem which really looks like a bad passphrase.

Ok, I renamed it Nexus7, but it didn't have any effect. Exact same problem.
The router logs that I can access aren't detailed enough to show anything about device connections, as far as I can tell. Just router startups etc. And the N7 isn't showing up in the list of attached devices.
Any other ideas?
I'm thinking I should return the N7 to the retailer on Monday since I'm in a 14-day return period, so it doesn't matter if it's actually broken or not. Either way, if I can't connect to my home Wi-Fi the device is really no good to me.
k23m said:
It logs:
Code:
wlan0: CTRL-EVENT-ASSOC-[B]REJECT [/B]bssid=c0:3e:0f:8e:ea:15
wlan0: ... id=1 ssid="SKY8DBEF" [B]auth_failures=1[/B]
The router rejects your N7. Can you check the router's own logs?
On your N7 go to WiFi Direct and rename the device. This will re-generate fresh /data/misc/wifi/wpa_supplicant.conf and may fix the problem which really looks like a bad passphrase.
Click to expand...
Click to collapse

mpb39 said:
I bought a second-hand Wi-Fi only Google/Asus Nexus 7 (2013), which came wiped, with Android 6.0.1 installed...
Click to expand...
Click to collapse
It was wiped but the OS could have been modified. Does it accept OTA now? I'd reflash it with factory image anyway.

i was experienced the same problem with you, that was after i changed its mac address. what i did is i changed it back to the default one and its working fine again.

I suppose that could have been the problem, but would a factory reset not restore the original MAC code if it had been changed?
Anyway, I've returned the device to the retailer for a refund now.

LineageOS 15 on S5 mini and SE Linux enforcement. Doesn't work well together

Hi,
I'm running LineageOS 15 (Android 8) on S5 mini. Everything is fine except one banking app that I really need. They validate on startup, whether the phone is rooted.
They in fact check if SE Linux is in enforcement mode. Here is the log snippet:
Code:
11-23 18:44:54.894 2259 2521 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.fidor.fsw/com.gft.fidor.views.splash.SplashScreenActivity bnds=[350,815][506,994] (has extras)} from uid 10036
11-23 18:44:54.935 2084 2084 I display : [DYNAMIC_RECOMP] HWC_2_GLES by low FPS(0)
11-23 18:44:54.969 2259 4027 I ActivityManager: Start proc 20526:com.fidor.fsw/u0a119 for activity com.fidor.fsw/com.gft.fidor.views.splash.SplashScreenActivity
11-23 18:44:55.190 2084 2084 I display : [DYNAMIC_RECOMP] GLES_2_HWC by high FPS(39)
11-23 18:44:55.229 20526 20540 I vndksupport: sphal namespace is not configured for this process. Loading /system/lib/egl/libEGL_mali.so from the current namespace instead.
11-23 18:44:55.326 20526 20540 D libEGL : loaded /system/lib/egl/libEGL_mali.so
11-23 18:44:55.339 2084 2133 W GrallocMapperPassthrough: buffer descriptor with invalid usage bits 0x400
11-23 18:44:55.356 20526 20540 I vndksupport: sphal namespace is not configured for this process. Loading /system/lib/egl/libGLESv1_CM_mali.so from the current namespace instead.
11-23 18:44:55.362 20526 20540 D libEGL : loaded /system/lib/egl/libGLESv1_CM_mali.so
11-23 18:44:55.586 20526 20540 I vndksupport: sphal namespace is not configured for this process. Loading /system/lib/egl/libGLESv2_mali.so from the current namespace instead.
11-23 18:44:55.588 20526 20540 D libEGL : loaded /system/lib/egl/libGLESv2_mali.so
11-23 18:44:56.455 20526 20526 I putmethod.latin: type=1400 audit(0.0:774): avc: denied { read } for name="/" dev="tmpfs" ino=3689 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=1
11-23 18:44:56.455 20526 20526 W putmethod.latin: type=1300 audit(0.0:774): arch=40000028 syscall=334 per=800008 success=yes exit=0 a0=ffffff9c a1=898ca354 a2=4 a3=0 items=1 ppid=2066 auid=4294967295 uid=10119 gid=10119 euid=10119 suid=10119 fsuid=10119 egid=10119 sgid=10119 fsgid=10119 tty=(none) ses=4294967295 exe="/system/bin/app_process32" subj=u:r:untrusted_app_25:s0:c512,c768 key=(null)
11-23 18:44:56.455 1978 1978 W auditd : type=1307 audit(0.0:774): cwd="/"
11-23 18:44:56.455 1978 1978 W auditd : type=1302 audit(0.0:774): item=0 name="/sbin" inode=3689 dev=00:12 mode=040755 ouid=0 ogid=0 rdev=00:00 obj=u:object_r:rootfs:s0
11-23 18:44:56.455 1978 1978 W auditd : type=1327 audit(0.0:774): proctitle="com.google.android.inputmethod.latin"
11-23 18:44:56.455 1978 1978 W auditd : type=1320 audit(0.0:774):
11-23 18:44:56.527 2259 3192 W ActivityManager: Force finishing activity com.fidor.fsw/com.gft.fidor.views.splash.SplashScreenActivity
Since LineageOS sets SELinux by default into permissive, this check fails and the app crashes. I'm able to set it to enforced with "SE Linux mode changer" or any other app of that kind, but immediately after the change the phone starts eating 100% cpu and modem (neither internet, nor SMS/phone calls) aren't working, which makes me think LineageOS doesn't work really well in enforcement mode of SE Linux. But the app itself launches just fine with SELinux in enforced.
I'm not an expert in Android and SELinux, but would like to know if there is a way:
to workaround the check we see in the logs and work with the app in permissive mode
to make LineageOS work correctly under enforced
PS. It doesn't matter which way to set the SELinux mode. Whatever is done - through kernel, in init.d or in adb shell, the symptoms are exactly the same after the change.
Thanks

bytes85 said:
Hi,
I'm running LineageOS 15 (Android 8) on S5 mini. Everything is fine except one banking app that I really need. They validate on startup, whether the phone is rooted...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Unofficial LineageOS (since there's no Official LineageOS Oreo released yet) thread for your device.
https://forum.xda-developers.com/showthread.php?t=3678205
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

[ROM] [ether] [8.1] [LOS-based] **crDroid**v4.6

this is crDroid for Nextbit Robin
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list
First time installing crDroid to your Robin, or coming from another ROM:
- Make sure you're running a proper working Recovery (CWM or TWRP)
- Copy GApps and crDroid zip to your external SDCard
- Boot into Recovery
- Wipe system,data and cache
- Flash crDroid zip
- Flash GApps zip
- Reboot
Upgrading from earlier version of crDroid:
- Copy crDroid ZIP to your external SDCard
- Boot into Recovery
- Wipe system and cache
- Flash crDroid zip
- Flash Gapps
- Reboot
Don't expect any support if you:
- are not running stock crDroid-kernel
- have installed any mods such as Xposed!
- have modified system files
many thanks to @javelinanddart for device tree
DONATE
crDroid G+ community
https://github.com/crdroidandroid​
XDA:DevDB Information
crdroidandroid, ROM for the Nextbit Robin
Contributors
firebird11
Source Code: https://github.com/crdroidandroid
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2018-03-10
Last Updated 2018-03-10

DOWNLOAD
opengapps
changelog
.

having problems downloading at android file host

cutederf said:
having problems downloading at android file host
Click to expand...
Click to collapse
all works fine
---------- Post added at 09:20 PM ---------- Previous post was at 08:54 PM ----------
firebird11 said:
res
Click to expand...
Click to collapse
everything works except camera

I mean I can't download the ROM file. I'm willing to test and submit log.....
Nevermind. Got it

adam.thomson.one said:
all works fine
---------- Post added at 09:20 PM ---------- Previous post was at 08:54 PM ----------
everything works except camera
Click to expand...
Click to collapse
I can also confirm the camera doesn't work. Also tried a different camera app from the playstore and it also didn't work.

ytsejam1138 said:
I can also confirm the camera doesn't work. Also tried a different camera app from the playstore and it also didn't work.
Click to expand...
Click to collapse
I remember that similar problems were with my nexus 5. When ported android 7. There too, for a long time the camera did not work because of the drivers.
//sorry for english

First Oreo build for ether , I'll try it out

Same here. Camera doesn't work.
Some logs just in case they are useful
Code:
03-11 22:45:28.497 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.497 28323 28323 E QCameraHWI_Mem: traceLogAllocEnd 1221080
03-11 22:45:28.497 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.497 28323 28323 E QCameraHWI_Mem: traceLogAllocEnd 1221080
03-11 22:45:28.499 28323 28323 D QCameraParameters: setSecureMode: Secure mode value: disable
03-11 22:45:28.502 28323 28323 I Thermal-Lib: Thermal-Lib-Client: Registraion successful for camera with handle:1
03-11 22:45:28.503 28323 28323 I QCamera2HWI: [KPI Perf] openCamera: X PROFILE_OPEN_CAMERA camera id 0, rc: 0
03-11 22:45:28.503 28323 28323 I QCamera2HWI: [KPI Perf] close_camera_device: E
03-11 22:45:28.503 28323 28462 I Thermal-Lib: Thermal-Lib-Client: Client received msg camera 0
03-11 22:45:28.503 28323 28323 I QCamera2HWI: [KPI Perf] closeCamera: E PROFILE_CLOSE_CAMERA camera id 0
03-11 22:45:28.513 28323 28323 I QCamera2HWI: [KPI Perf] closeCamera: X PROFILE_CLOSE_CAMERA camera id 0, rc: 0
03-11 22:45:28.513 28323 28323 I QCamera2HWI: [KPI Perf] close_camera_device: X
03-11 22:45:28.514 28323 28323 I QCamera2Factory: :openLegacy openLegacy halVersion: 256
03-11 22:45:28.515 28323 28323 I QCamera2HWI: [KPI Perf] openCamera: E PROFILE_OPEN_CAMERA camera id 1
03-11 22:45:28.638 28323 28323 D QCameraHWI_Mem: traceLogAllocStart : alloc E count=1 size=12080
03-11 22:45:28.638 28323 28323 D QCameraHWI_Mem: traceLogAllocStart : alloc E count=1 size=12080
03-11 22:45:28.639 28323 28323 D QCameraHWI_Mem: allocOneBuffer : ION buffer 1 with size 12288 allocated
03-11 22:45:28.639 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.639 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.671 28323 28323 D QCameraHWI_Mem: traceLogAllocStart : alloc E count=1 size=1221080
03-11 22:45:28.671 28323 28323 E QCameraHWI_Mem: traceLogAllocStart:HeapMemsize 1221080
03-11 22:45:28.671 28323 28323 D QCameraHWI_Mem: traceLogAllocStart : alloc E count=1 size=1221080
03-11 22:45:28.671 28323 28323 E QCameraHWI_Mem: traceLogAllocStart:Memsize 1221080
03-11 22:45:28.672 28323 28323 D QCameraHWI_Mem: allocOneBuffer : ION buffer 1 with size 1224704 allocated
03-11 22:45:28.672 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.672 28323 28323 E QCameraHWI_Mem: traceLogAllocEnd 1221080
03-11 22:45:28.672 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.672 28323 28323 E QCameraHWI_Mem: traceLogAllocEnd 1221080
03-11 22:45:28.675 28323 28323 E QCameraParameters: initDefaultParameters: supported flash modes cnt is 0!!!
03-11 22:45:28.677 28323 28323 D QCameraParameters: setSecureMode: Secure mode value: disable
03-11 22:45:28.681 28323 28323 I Thermal-Lib: Thermal-Lib-Client: Registraion successful for camera with handle:1
03-11 22:45:28.681 28323 28323 I QCamera2HWI: [KPI Perf] openCamera: X PROFILE_OPEN_CAMERA camera id 1, rc: 0
03-11 22:45:28.681 28323 28323 I QCamera2HWI: [KPI Perf] close_camera_device: E
03-11 22:45:28.682 28323 28505 I Thermal-Lib: Thermal-Lib-Client: Client received msg camera 0
03-11 22:45:28.683 28323 28323 I QCamera2HWI: [KPI Perf] closeCamera: E PROFILE_CLOSE_CAMERA camera id 1
03-11 22:45:28.693 28323 28323 I QCamera2HWI: [KPI Perf] closeCamera: X PROFILE_CLOSE_CAMERA camera id 1, rc: 0
03-11 22:45:28.694 28323 28323 I QCamera2HWI: [KPI Perf] close_camera_device: X
03-11 22:45:28.696 28323 28323 I CameraProviderManager: Connecting to new camera provider: legacy/0, isRemote? 0
03-11 22:45:28.697 28323 28323 I CameraProviderManager: Enumerating new camera device: [email protected]/legacy/0
03-11 22:45:28.699 28323 28323 I [email protected]: Opening camera 0
03-11 22:45:28.699 28323 28323 I QCamera2Factory: :openLegacy openLegacy halVersion: 256
03-11 22:45:28.701 28323 28323 I QCamera2HWI: [KPI Perf] openCamera: E PROFILE_OPEN_CAMERA camera id 0
03-11 22:45:28.823 558 558 I chatty : uid=1006(camera) mm-qcamera-daem identical 1 line
03-11 22:45:28.875 28323 28323 D QCameraHWI_Mem: traceLogAllocStart : alloc E count=1 size=1221080
03-11 22:45:28.875 28323 28323 E QCameraHWI_Mem: traceLogAllocStart:HeapMemsize 1221080
03-11 22:45:28.875 28323 28323 D QCameraHWI_Mem: traceLogAllocStart : alloc E count=1 size=1221080
03-11 22:45:28.875 28323 28323 E QCameraHWI_Mem: traceLogAllocStart:Memsize 1221080
03-11 22:45:28.875 28323 28323 D QCameraHWI_Mem: allocOneBuffer : ION buffer 1 with size 1224704 allocated
03-11 22:45:28.875 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.875 28323 28323 E QCameraHWI_Mem: traceLogAllocEnd 1221080
03-11 22:45:28.875 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.875 28323 28323 E QCameraHWI_Mem: traceLogAllocEnd 1221080
03-11 22:45:28.878 28323 28323 D QCameraParameters: setSecureMode: Secure mode value: disable
03-11 22:45:28.881 28323 28323 I Thermal-Lib: Thermal-Lib-Client: Registraion successful for camera with handle:1
03-11 22:45:28.881 28323 28323 I QCamera2HWI: [KPI Perf] openCamera: X PROFILE_OPEN_CAMERA camera id 0, rc: 0
03-11 22:45:28.881 28323 28551 I Thermal-Lib: Thermal-Lib-Client: Client received msg camera 0
03-11 22:45:28.883 28323 28323 I [email protected]: Closing camera 0
03-11 22:45:28.883 28323 28323 I QCamera2HWI: [KPI Perf] close_camera_device: E
03-11 22:45:28.884 28323 28323 I QCamera2HWI: [KPI Perf] closeCamera: E PROFILE_CLOSE_CAMERA camera id 0
03-11 22:45:28.894 28323 28323 I QCamera2HWI: [KPI Perf] closeCamera: X PROFILE_CLOSE_CAMERA camera id 0, rc: 0
03-11 22:45:28.894 28323 28323 I QCamera2HWI: [KPI Perf] close_camera_device: X
03-11 22:45:28.894 28323 28323 I CameraProviderManager: Enumerating new camera device: [email protected]/legacy/0
03-11 22:45:28.895 28323 28323 I CameraProviderManager: Enumerating new camera device: [email protected]/legacy/1
03-11 22:45:28.897 28323 28323 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 28323 (cameraserver), pid 28323 (cameraserver)
03-11 22:45:28.933 28566 28566 F DEBUG : pid: 28323, tid: 28323, name: cameraserver >>> /system/bin/cameraserver <<<
03-11 22:45:28.965 28566 28566 F DEBUG : #01 pc 0000f4bb /system/vendor/lib/[email protected] (android::hardware::camera::device::V1_0::implementation::CameraDevice::getResourceCost(std::__1::function<void (android::hardware::camera::common::V1_0::Status, android::hardware::camera::common::V1_0::CameraResourceCost const&)>)+154)
03-11 22:45:28.965 28566 28566 F DEBUG : #02 pc 0002aebb /system/lib/[email protected] (android::hardware::camera::device::V1_0::BsCameraDevice::getResourceCost(std::__1::function<void (android::hardware::camera::common::V1_0::Status, android::hardware::camera::common::V1_0::CameraResourceCost const&)>)+110)
03-11 22:45:28.966 28566 28566 F DEBUG : #03 pc 000804ed /system/lib/libcameraservice.so (android::CameraProviderManager::ProviderInfo::initializeDeviceInfo<android::CameraProviderManager::ProviderInfo::DeviceInfo1>(std::__1::unique_ptr<android::CameraProviderManager::ProviderInfo::DeviceInfo, android::CameraProviderManager::ProviderInfo::initializeDeviceInfo<android::CameraProviderManager::ProviderInfo::DeviceInfo1>::default_delete<std::__1::unique_ptr>>, android::CameraProviderManager::ProviderInfo::initializeDeviceInfo<android::CameraProv
03-11 22:45:28.966 28566 28566 F DEBUG : #04 pc 0008000b /system/lib/libcameraservice.so (android::CameraProviderManager::ProviderInfo::addDevice(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, android::hardware::camera::common::V1_0::CameraDeviceStatus, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>>*)+406)
03-11 22:45:28.966 28566 28566 F DEBUG : #05 pc 0007f65f /system/lib/libcameraservice.so (android::CameraProviderManager::ProviderInfo::initialize()+754)
03-11 22:45:28.966 28566 28566 F DEBUG : #06 pc 0007da87 /system/lib/libcameraservice.so (android::CameraProviderManager::addProviderLocked(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, bool)+230)
03-11 22:45:28.966 28566 28566 F DEBUG : #07 pc 0007d8a7 /system/lib/libcameraservice.so (android::CameraProviderManager::initialize(android::wp<android::CameraProviderManager::StatusListener>, android::CameraProviderManager::ServiceInteractionProxy*)+122)
03-11 22:45:28.966 28566 28566 F DEBUG : #08 pc 0006ea29 /system/lib/libcameraservice.so (android::CameraService::enumerateProviders()+804)
03-11 22:45:28.966 28566 28566 F DEBUG : #09 pc 0006e683 /system/lib/libcameraservice.so (android::CameraService::onFirstRef()+54)
03-11 22:45:28.966 28566 28566 F DEBUG : #10 pc 00000ddb /system/bin/cameraserver
03-11 22:45:28.966 28566 28566 F DEBUG : #11 pc 00000d47 /system/bin/cameraserver (android::BinderService<android::CameraService>::publish(bool)+62)
03-11 22:45:28.966 28566 28566 F DEBUG : #12 pc 00000c75 /system/bin/cameraserver (main+56)
03-11 22:45:28.966 28566 28566 F DEBUG : #14 pc 00000b5c /system/bin/cameraserver (_start_main+88)
03-11 22:45:29.009 14330 14330 I ServiceManager: Waiting for service media.camera...
03-11 22:45:29.051 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:29.052 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:29.053 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:29.053 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:29.371 28567 28567 I cameraserver: ServiceManager: 0xf2f17940
03-11 22:45:29.371 28567 28567 I CameraService: CameraService started (pid=28567)
03-11 22:45:29.371 28567 28567 I CameraService: CameraService process starting
03-11 22:45:29.375 28567 28567 D vndksupport: Loading /vendor/lib/hw/[email protected] from current namespace instead of sphal namespace.
03-11 22:45:29.402 4332 5692 W CameraBase: CameraService not published, waiting...
03-11 22:45:29.902 4332 5692 I ServiceManager: Waiting for service media.camera...
03-11 22:45:30.010 14330 14330 I ServiceManager: Waiting for service media.camera...
03-11 22:45:30.053 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:30.053 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:30.053 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:30.054 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:30.903 4332 5692 I ServiceManager: Waiting for service media.camera...
03-11 22:45:31.012 14330 14330 W CameraBase: CameraService not published, waiting...
03-11 22:45:31.054 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:31.054 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:31.055 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:31.055 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:31.513 14330 14330 I ServiceManager: Waiting for service media.camera...
03-11 22:45:31.903 4332 5692 I ServiceManager: Waiting for service media.camera...
03-11 22:45:32.055 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:32.056 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:32.056 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:32.057 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:32.515 14330 14330 I ServiceManager: Waiting for service media.camera...
03-11 22:45:32.904 4332 5692 I ServiceManager: Waiting for service media.camera...
03-11 22:45:33.058 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:33.060 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:33.060 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:33.061 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:33.516 14330 14330 I ServiceManager: Waiting for service media.camera...

camera
natefanaro said:
Same here. Camera doesn't work.
Some logs just in case they are useful
Code:
03-11 22:45:28.497 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.497 28323 28323 E QCameraHWI_Mem: traceLogAllocEnd 1221080
03-11 22:45:28.497 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.497 28323 28323 E QCameraHWI_Mem: traceLogAllocEnd 1221080
03-11 22:45:28.499 28323 28323 D QCameraParameters: setSecureMode: Secure mode value: disable
03-11 22:45:28.502 28323 28323 I Thermal-Lib: Thermal-Lib-Client: Registraion successful for camera with handle:1
03-11 22:45:28.503 28323 28323 I QCamera2HWI: [KPI Perf] openCamera: X PROFILE_OPEN_CAMERA camera id 0, rc: 0
03-11 22:45:28.503 28323 28323 I QCamera2HWI: [KPI Perf] close_camera_device: E
03-11 22:45:28.503 28323 28462 I Thermal-Lib: Thermal-Lib-Client: Client received msg camera 0
03-11 22:45:28.503 28323 28323 I QCamera2HWI: [KPI Perf] closeCamera: E PROFILE_CLOSE_CAMERA camera id 0
03-11 22:45:28.513 28323 28323 I QCamera2HWI: [KPI Perf] closeCamera: X PROFILE_CLOSE_CAMERA camera id 0, rc: 0
03-11 22:45:28.513 28323 28323 I QCamera2HWI: [KPI Perf] close_camera_device: X
03-11 22:45:28.514 28323 28323 I QCamera2Factory: :openLegacy openLegacy halVersion: 256
03-11 22:45:28.515 28323 28323 I QCamera2HWI: [KPI Perf] openCamera: E PROFILE_OPEN_CAMERA camera id 1
03-11 22:45:28.638 28323 28323 D QCameraHWI_Mem: traceLogAllocStart : alloc E count=1 size=12080
03-11 22:45:28.638 28323 28323 D QCameraHWI_Mem: traceLogAllocStart : alloc E count=1 size=12080
03-11 22:45:28.639 28323 28323 D QCameraHWI_Mem: allocOneBuffer : ION buffer 1 with size 12288 allocated
03-11 22:45:28.639 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.639 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.671 28323 28323 D QCameraHWI_Mem: traceLogAllocStart : alloc E count=1 size=1221080
03-11 22:45:28.671 28323 28323 E QCameraHWI_Mem: traceLogAllocStart:HeapMemsize 1221080
03-11 22:45:28.671 28323 28323 D QCameraHWI_Mem: traceLogAllocStart : alloc E count=1 size=1221080
03-11 22:45:28.671 28323 28323 E QCameraHWI_Mem: traceLogAllocStart:Memsize 1221080
03-11 22:45:28.672 28323 28323 D QCameraHWI_Mem: allocOneBuffer : ION buffer 1 with size 1224704 allocated
03-11 22:45:28.672 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.672 28323 28323 E QCameraHWI_Mem: traceLogAllocEnd 1221080
03-11 22:45:28.672 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.672 28323 28323 E QCameraHWI_Mem: traceLogAllocEnd 1221080
03-11 22:45:28.675 28323 28323 E QCameraParameters: initDefaultParameters: supported flash modes cnt is 0!!!
03-11 22:45:28.677 28323 28323 D QCameraParameters: setSecureMode: Secure mode value: disable
03-11 22:45:28.681 28323 28323 I Thermal-Lib: Thermal-Lib-Client: Registraion successful for camera with handle:1
03-11 22:45:28.681 28323 28323 I QCamera2HWI: [KPI Perf] openCamera: X PROFILE_OPEN_CAMERA camera id 1, rc: 0
03-11 22:45:28.681 28323 28323 I QCamera2HWI: [KPI Perf] close_camera_device: E
03-11 22:45:28.682 28323 28505 I Thermal-Lib: Thermal-Lib-Client: Client received msg camera 0
03-11 22:45:28.683 28323 28323 I QCamera2HWI: [KPI Perf] closeCamera: E PROFILE_CLOSE_CAMERA camera id 1
03-11 22:45:28.693 28323 28323 I QCamera2HWI: [KPI Perf] closeCamera: X PROFILE_CLOSE_CAMERA camera id 1, rc: 0
03-11 22:45:28.694 28323 28323 I QCamera2HWI: [KPI Perf] close_camera_device: X
03-11 22:45:28.696 28323 28323 I CameraProviderManager: Connecting to new camera provider: legacy/0, isRemote? 0
03-11 22:45:28.697 28323 28323 I CameraProviderManager: Enumerating new camera device: [email protected]/legacy/0
03-11 22:45:28.699 28323 28323 I [email protected]: Opening camera 0
03-11 22:45:28.699 28323 28323 I QCamera2Factory: :openLegacy openLegacy halVersion: 256
03-11 22:45:28.701 28323 28323 I QCamera2HWI: [KPI Perf] openCamera: E PROFILE_OPEN_CAMERA camera id 0
03-11 22:45:28.823 558 558 I chatty : uid=1006(camera) mm-qcamera-daem identical 1 line
03-11 22:45:28.875 28323 28323 D QCameraHWI_Mem: traceLogAllocStart : alloc E count=1 size=1221080
03-11 22:45:28.875 28323 28323 E QCameraHWI_Mem: traceLogAllocStart:HeapMemsize 1221080
03-11 22:45:28.875 28323 28323 D QCameraHWI_Mem: traceLogAllocStart : alloc E count=1 size=1221080
03-11 22:45:28.875 28323 28323 E QCameraHWI_Mem: traceLogAllocStart:Memsize 1221080
03-11 22:45:28.875 28323 28323 D QCameraHWI_Mem: allocOneBuffer : ION buffer 1 with size 1224704 allocated
03-11 22:45:28.875 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.875 28323 28323 E QCameraHWI_Mem: traceLogAllocEnd 1221080
03-11 22:45:28.875 28323 28323 D QCameraHWI_Mem: traceLogAllocEnd : X
03-11 22:45:28.875 28323 28323 E QCameraHWI_Mem: traceLogAllocEnd 1221080
03-11 22:45:28.878 28323 28323 D QCameraParameters: setSecureMode: Secure mode value: disable
03-11 22:45:28.881 28323 28323 I Thermal-Lib: Thermal-Lib-Client: Registraion successful for camera with handle:1
03-11 22:45:28.881 28323 28323 I QCamera2HWI: [KPI Perf] openCamera: X PROFILE_OPEN_CAMERA camera id 0, rc: 0
03-11 22:45:28.881 28323 28551 I Thermal-Lib: Thermal-Lib-Client: Client received msg camera 0
03-11 22:45:28.883 28323 28323 I [email protected]: Closing camera 0
03-11 22:45:28.883 28323 28323 I QCamera2HWI: [KPI Perf] close_camera_device: E
03-11 22:45:28.884 28323 28323 I QCamera2HWI: [KPI Perf] closeCamera: E PROFILE_CLOSE_CAMERA camera id 0
03-11 22:45:28.894 28323 28323 I QCamera2HWI: [KPI Perf] closeCamera: X PROFILE_CLOSE_CAMERA camera id 0, rc: 0
03-11 22:45:28.894 28323 28323 I QCamera2HWI: [KPI Perf] close_camera_device: X
03-11 22:45:28.894 28323 28323 I CameraProviderManager: Enumerating new camera device: [email protected]/legacy/0
03-11 22:45:28.895 28323 28323 I CameraProviderManager: Enumerating new camera device: [email protected]/legacy/1
03-11 22:45:28.897 28323 28323 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 28323 (cameraserver), pid 28323 (cameraserver)
03-11 22:45:28.933 28566 28566 F DEBUG : pid: 28323, tid: 28323, name: cameraserver >>> /system/bin/cameraserver <<<
03-11 22:45:28.965 28566 28566 F DEBUG : #01 pc 0000f4bb /system/vendor/lib/[email protected] (android::hardware::camera::device::V1_0::implementation::CameraDevice::getResourceCost(std::__1::function<void (android::hardware::camera::common::V1_0::Status, android::hardware::camera::common::V1_0::CameraResourceCost const&)>)+154)
03-11 22:45:28.965 28566 28566 F DEBUG : #02 pc 0002aebb /system/lib/[email protected] (android::hardware::camera::device::V1_0::BsCameraDevice::getResourceCost(std::__1::function<void (android::hardware::camera::common::V1_0::Status, android::hardware::camera::common::V1_0::CameraResourceCost const&)>)+110)
03-11 22:45:28.966 28566 28566 F DEBUG : #03 pc 000804ed /system/lib/libcameraservice.so (android::CameraProviderManager::ProviderInfo::initializeDeviceInfo<android::CameraProviderManager::ProviderInfo::DeviceInfo1>(std::__1::unique_ptr<android::CameraProviderManager::ProviderInfo::DeviceInfo, android::CameraProviderManager::ProviderInfo::initializeDeviceInfo<android::CameraProviderManager::ProviderInfo::DeviceInfo1>::default_delete<std::__1::unique_ptr>>, android::CameraProviderManager::ProviderInfo::initializeDeviceInfo<android::CameraProv
03-11 22:45:28.966 28566 28566 F DEBUG : #04 pc 0008000b /system/lib/libcameraservice.so (android::CameraProviderManager::ProviderInfo::addDevice(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, android::hardware::camera::common::V1_0::CameraDeviceStatus, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>>*)+406)
03-11 22:45:28.966 28566 28566 F DEBUG : #05 pc 0007f65f /system/lib/libcameraservice.so (android::CameraProviderManager::ProviderInfo::initialize()+754)
03-11 22:45:28.966 28566 28566 F DEBUG : #06 pc 0007da87 /system/lib/libcameraservice.so (android::CameraProviderManager::addProviderLocked(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, bool)+230)
03-11 22:45:28.966 28566 28566 F DEBUG : #07 pc 0007d8a7 /system/lib/libcameraservice.so (android::CameraProviderManager::initialize(android::wp<android::CameraProviderManager::StatusListener>, android::CameraProviderManager::ServiceInteractionProxy*)+122)
03-11 22:45:28.966 28566 28566 F DEBUG : #08 pc 0006ea29 /system/lib/libcameraservice.so (android::CameraService::enumerateProviders()+804)
03-11 22:45:28.966 28566 28566 F DEBUG : #09 pc 0006e683 /system/lib/libcameraservice.so (android::CameraService::onFirstRef()+54)
03-11 22:45:28.966 28566 28566 F DEBUG : #10 pc 00000ddb /system/bin/cameraserver
03-11 22:45:28.966 28566 28566 F DEBUG : #11 pc 00000d47 /system/bin/cameraserver (android::BinderService<android::CameraService>::publish(bool)+62)
03-11 22:45:28.966 28566 28566 F DEBUG : #12 pc 00000c75 /system/bin/cameraserver (main+56)
03-11 22:45:28.966 28566 28566 F DEBUG : #14 pc 00000b5c /system/bin/cameraserver (_start_main+88)
03-11 22:45:29.009 14330 14330 I ServiceManager: Waiting for service media.camera...
03-11 22:45:29.051 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:29.052 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:29.053 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:29.053 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:29.371 28567 28567 I cameraserver: ServiceManager: 0xf2f17940
03-11 22:45:29.371 28567 28567 I CameraService: CameraService started (pid=28567)
03-11 22:45:29.371 28567 28567 I CameraService: CameraService process starting
03-11 22:45:29.375 28567 28567 D vndksupport: Loading /vendor/lib/hw/[email protected] from current namespace instead of sphal namespace.
03-11 22:45:29.402 4332 5692 W CameraBase: CameraService not published, waiting...
03-11 22:45:29.902 4332 5692 I ServiceManager: Waiting for service media.camera...
03-11 22:45:30.010 14330 14330 I ServiceManager: Waiting for service media.camera...
03-11 22:45:30.053 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:30.053 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:30.053 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:30.054 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:30.903 4332 5692 I ServiceManager: Waiting for service media.camera...
03-11 22:45:31.012 14330 14330 W CameraBase: CameraService not published, waiting...
03-11 22:45:31.054 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:31.054 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:31.055 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:31.055 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:31.513 14330 14330 I ServiceManager: Waiting for service media.camera...
03-11 22:45:31.903 4332 5692 I ServiceManager: Waiting for service media.camera...
03-11 22:45:32.055 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:32.056 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:32.056 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:32.057 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:32.515 14330 14330 I ServiceManager: Waiting for service media.camera...
03-11 22:45:32.904 4332 5692 I ServiceManager: Waiting for service media.camera...
03-11 22:45:33.058 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:33.060 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:33.060 804 843 I CameraManagerGlobal: Connecting to camera service
03-11 22:45:33.061 804 843 E CameraManagerGlobal: Camera service is unavailable
03-11 22:45:33.516 14330 14330 I ServiceManager: Waiting for service media.camera...
Click to expand...
Click to collapse
i fixed camera for ether will bring oreo build soon.

haran2003 said:
i fixed camera for ether will bring oreo build soon.
Click to expand...
Click to collapse
cool news
i'm waiting for it

YouTube is not working plz say how to fix plz help me it's not working on crdroid 8.1..
:silly:

awesome to see this, i'll try it asap

camera issue
pay_omar said:
awesome to see this, i'll try it asap
Click to expand...
Click to collapse
camera not working

camera not working and lagging
i feel the rom is lagging i mean the transition i get it is is in testing but still
---------- Post added at 01:31 PM ---------- Previous post was at 12:32 PM ----------
split screen not working properly

I was unable to make voice calls via jio 4g and in network testing menu, it was showing 'Unavailable' for Volte.
I want to use 8.1 on ether but with voice calls working.
How could I fix this?

Darkstar_Devil17 said:
I was unable to make voice calls via jio 4g and in network testing menu, it was showing 'Unavailable' for Volte.
I want to use 8.1 on ether but with voice calls working.
How could I fix this?
Click to expand...
Click to collapse
didnt have jio sim with me now but checked airtel 4g working fine

Great job!! to be an experimental rom i have found just one bug and it's that when you plug your cellphone to the computer it didn't recognize it, it does when you plug it on recovery mode, but the rom did not recognize it and sometimes it charge really slow. apart from the camera and the things i had already said the rom it's great, some crashes here and there but remember it's an experimental build right now and it's working really well even in this stage i hope you keep working on it becouse it's seems it's going to be a beast of a rom

The youtube app doesnt work, and the battery drains pretty fast, other then that the rom is smooth and worls perfectly

Wich twrp version should work to flash this ROM ....i have 3.1.1.1 is it enough ?