yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) General] fastjohnson:
I'm not on 14.1 nougat im on 14 theres only 14.1 builds for the oneplus3 device. Part of my post was informing hashbang on the bugs im seeing with the cm 14 I downloaded all 3 files from a site ( trying to find it ) including the boot. Img but if your on 14.1 cm I don't believe itll work. What specifically are you not understanding.

---------- Post added at 11:06 PM ---------- Previous post was at 10:37 PM ----------

Sorry I was wrong there is a 14.1 build trying it now. The site said only style not pure but followed to hashbangs profile and there was quite a few there so my apologies.
[X Style (Pure) General] Ltilt2:
No worries.

---------- Post added at 12:13 AM ---------- Previous post was at 12:12 AM ----------

No Worries.
[X Style (Pure) General] Ltilt2:
that worked. The only issue is the corrupt SD card. Still testing and we will see how it goes throughout the day.
[X Style (Pure) General] Hashbang173:
Any phone issues on today's build?
[X Style (Pure) General] chris_dis:
Nope, no issues yet except the cm setup wizard is still buggy and it says that the sd card is corrupted.
[X Style (Pure) General] HPAR:
no more "com.android.... stopped" :D

camera is ok (I can take a movie) :D

sim card is ok :D

sd card is corrupted :crying:

but no gps :crying:
[X Style (Pure) General] Hashbang173:
VoLTE working on today's build?
[X Style (Pure) General] chris_dis:
Can't test that sorry
[X Style (Pure) General] pizzlewizzle:
Im also getting SD card corrupted. haven't experienced this on any of the AICP12.1 builds but this is my first time trying a CM14.1 build. No issues with phone.
[X Style (Pure) General] lmulli:
Dirty flashed latest version of Cm14.1 over AICP which was giving me constant reboots and appears to have sorted it! Only issue being the SD Card being corrupted as already reported. GPS working fine, no phone errors.
[X Style (Pure) General] LARMYV:
Fyi, I finally was able to build a tesla n rom. The link to it is below. For now, i will post here when ever I build another one. The same issue with camera video remains.

https://www.androidfilehost.com/?fid=312968873555011872
[X Style (Pure) General] capeorigins:
Wait, when you dirty flash, you get to keep the aicp settings right?

---------- Post added at 06:05 PM ---------- Previous post was at 06:05 PM ----------

How's it running?

---------- Post added at 06:06 PM ---------- Previous post was at 06:05 PM ----------

Also, I'm seeing the sdcard issue as well, and I don't think VoLTE is working
[X Style (Pure) General] lmulli:
No, the extra AICP Settings menu disappeared, which is what I would have expected. Never used what was in there anyway, so no issue for me as all I need is an advanced reboot menu and I'm more than happy!
[X Style (Pure) General] capeorigins:
Nice, haha. I'm running a the cm14.1 update right now. Clean flash, working well for me, for now at least.

---------- Post added at 06:59 PM ---------- Previous post was at 06:18 PM ----------

Nvm, I can't seem to use the camera at all "can't connect"
[X Style (Pure) General] Prazaar:
I use my sdcard as intern storage and work fine

Gesendet von meinem XT1572 mit Tapatalk
[X Style (Pure) General] lmulli:
Is it reporting the correct size? I have a 64gb card in and it reports something along the lines of -29gb used and 29 GB available. The card is empty.
[X Style (Pure) General] Hashbang173:
Number of changes present in today's build.

It includes a potential fix for video recording, please report if it is fixed.
[X Style (Pure) General] Prazaar:
In System size -27gb but its work look screenshots:

Gesendet von meinem XT1572 mit Tapatalk
[X Style (Pure) General] HPAR:
Yes, the video record is OK on cm 8/11. Thanks.

But, on aicp 9/11 it isn't.
[X Style (Pure) General] lmulli:
Any update on CM14.1 rom or is this just for the CM14? Thanks.
[X Style (Pure) General] dgadelha:
It killed Camera on XT1572/BR. Every app with Camera support crashes when trying to connect to camera.

I ActivityManager: Displayed com.motorola.camera/.Camera: +670ms
W OpenCameraCallable: Exception in result (dur:215)
W OpenCameraCallable: com.motorola.camera.device.execption.CameraHardwareException: java.lang.RuntimeException: Fail to connect to camera service
W OpenCameraCallable: at com.motorola.camera.device.callables.OpenCameraCallable.openCamera(OpenCameraCallable.java:136)
W OpenCameraCallable: at com.motorola.camera.device.callables.OpenCameraCallable.call(OpenCameraCallable.java:65)
W OpenCameraCallable: at com.motorola.camera.device.callables.CameraCallable.run(CameraCallable.java:47)
W OpenCameraCallable: at com.motorola.camera.device.CameraService$2.handleMessage(CameraService.java:108)
W OpenCameraCallable: at android.os.Handler.dispatchMessage(Handler.java:98)
W OpenCameraCallable: at android.os.Looper.loop(Looper.java:154)
W OpenCameraCallable: at android.os.HandlerThread.run(HandlerThread.java:61)
W OpenCameraCallable: Caused by: java.lang.RuntimeException: Fail to connect to camera service
W OpenCameraCallable: at android.hardware.Camera.<init>(Camera.java:540)
W OpenCameraCallable: at android.hardware.Camera.open(Camera.java:372)
W OpenCameraCallable: at com.motorola.camera.device.callables.OpenCameraCallable.openWrapper(OpenCameraCallable.java:199)
W OpenCameraCallable: at com.motorola.camera.device.callables.OpenCameraCallable.openCamera(OpenCameraCallable.java:173)
W OpenCameraCallable: at com.motorola.camera.device.callables.OpenCameraCallable.openCamera(OpenCameraCallable.java:115)
W OpenCameraCallable: ... 6 more
W ReadParamsCallable: Exception in result (dur:179)
W ReadParamsCallable: java.lang.Exception: Camera isn't opened
W ReadParamsCallable: at com.motorola.camera.device.callables.ReadParamsCallable.call(ReadParamsCallable.java:29)
W ReadParamsCallable: at com.motorola.camera.device.callables.CameraCallable.run(CameraCallable.java:47)
W ReadParamsCallable: at com.motorola.camera.device.CameraService$2.handleMessage(CameraService.java:108)
W ReadParamsCallable: at android.os.Handler.dispatchMessage(Handler.java:98)
W ReadParamsCallable: at android.os.Looper.loop(Looper.java:154)
W ReadParamsCallable: at android.os.HandlerThread.run(HandlerThread.java:61)
W SetParamsCallable: Exception in result (dur:179)
W SetParamsCallable: java.lang.Exception: Camera isn't opened
W SetParamsCallable: at com.motorola.camera.device.callables.SetParamsCallable.call(SetParamsCallable.java:59)
W SetParamsCallable: at com.motorola.camera.device.callables.CameraCallable.run(CameraCallable.java:47)
W SetParamsCallable: at com.motorola.camera.device.CameraService$2.handleMessage(CameraService.java:108)
W SetParamsCallable: at android.os.Handler.dispatchMessage(Handler.java:98)
W SetParamsCallable: at android.os.Looper.loop(Looper.java:154)
W SetParamsCallable: at android.os.HandlerThread.run(HandlerThread.java:61)

Weird af, this lib is present:

E CameraStateInformer: UnsatisfiedLinkError dlopen failed: library "libcamera_client.so" not found
[X Style (Pure) General] zio guiduccio:
I have this same problem right now. Does anyone still suffer from it? In general I can't share any photo to whatsapp (no problem with telegram) nor edit them in photos/gallery, set them as wallpaper and access them from documents activity.
[X Style (Pure) General] garbour:
Go back and look at my previous post, you need to completely wipe everything!
[X Style (Pure) General] capeorigins:
So wiping everything meaning internal too and external? Or
[X Style (Pure) General] garbour:
I don't use an external. I wiped all including data.
[X Style (Pure) General] capeorigins:
Jeepers. Yeah I figured. I probably will soon them xD
[X Style (Pure) General] tech_infinity:
No

Only internal
[X Style (Pure) General] zio guiduccio:
Don't you mean /sdcard too... don't you?
[X Style (Pure) General] garbour:
Internal SD yes
[X Style (Pure) General] Hashbang173:
See if video recording works on today's build (cm-14.1-20161111)
[X Style (Pure) General] chris_dis:
Works for me using google camera, great work!
[X Style (Pure) General] hoppermi:
Seems to record fine. But can't play any mp4.

Edit: video plays with VLC, but not native player. Maybe because I used pico gapps, not sure.
[X Style (Pure) General] dgadelha:
XT1572 camera works now. Recording works fine. :D
[X Style (Pure) General] CJ-Wylde:
Testing this now, tried out the AICP one from today and all is good aside from Video Recording. Loving that this device is still having active Hashbang development, whoot!!!
[X Style (Pure) General] jobski213:
Anyone having issues with the SD card being reported as corrupted?
[X Style (Pure) General] slebit:
Are you using my device/kernel tree? I just updated with some stuff and possible fix for camera.
[X Style (Pure) General] donrojo:
Deleted

---------- Post added at 07:35 PM ---------- Previous post was at 06:52 PM ----------

Around about solution for "Corrupted SD card" error:

- Turn off you phone and remove your microSD card.

- Insert you microSD card to your comptuer and back up whatever foders/files you need into your computer drive (external drive if you have a lot to copy)

- Using a partition software (I used MiniTool Partition Free 9.1) format your microSD card to Ext4 file format (I repartitioned it and formated to Ext4)

- remove you microSD from computer and place it into your phones SIM/MicroSD slot.

- Power ON you phone and once booted you'll be notified "Foun New SD Card". Tap and tap on Setup. Choose Use as external (presuming that those who have opted for internal would not look for this issue here)

- Connect your phone to computer as Transfer Files. Copy whatever backup you saved on your computer drive to your phone External Drive.

There you go!

NOTE: I tested first to format Windows Explorer exFat file format. It worked after booting the phone but Camera could not recognise SD card and so could not save pictures to SD. Ext4 file format is recognised! I tested and saved photos to SD, copied files via CM file manager as well as from computer hard disk to External drive shown on the computer after connecting the phone.

[MENTION=4630246]Hashbang173[/MENTION] : I did some research and found out this was an issue for CM13 in its early days. The renown Daniel Hillnebrand, aka codewokx, did push this:

http://review.cyanogenmod.org/#/c/126277/

to solve the problem (athough in a thread I read about it, people with 128GB microSD continued to complain about the error! Perhaps you can find it helpful. Many thanks for your hard work and dedication.
[X Style (Pure) General] Hashbang173:
FAT32 sdcards don't work right now because of an issue with fsck.msdos

fsck.msdos doesn't play well with SDClang (which is what recent builds are compiled with), and segfaults.

FAT32 sdcards should continue to work after this change is merged: http://review.cyanogenmod.org/#/c/170335/
[X Style (Pure) General] Hashbang173:
See if sdcard works again in today's build (cm-14.1-20161112)
[X Style (Pure) General] gaxander:
Installed 11/12.

Absolute no bluetooth. It doesn't even start.
[X Style (Pure) General] DrunkUncas:
Same here.

Everything else is flawless.

ETA: 11/11 build
[X Style (Pure) General] LARMYV:
Hey, what is your github account name or provide the link and I'll check it out. Right now, I built the rom using Tesla github for the device and muppets for vendor and GZR github for the kernel.
[X Style (Pure) General] slebit:
I am the maintainer for GZR. So you are using my source. ☺️
[X Style (Pure) General] Fabiett83:
Sdcard and video record working!

I ran a logcat just so see what's going on and noticed this line repeating at a very fast rate (10 times in 0.001 sec)

11-13 09:06:23.636 404 430 E QMI_FW : xport_reg Failed for service_id=0x35 version=0x1001 on 14

The top program in emulator shows this 2 processes always running:

PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
404 system 20 0 29M 2.4M 1.6M S 95.0 0.0 18:21.67 pm-service
353 logd 30 10 27M 4.8M 1.3M S 49.3 0.1 9:07.79 logd
[X Style (Pure) General] Ueihtam:
CM14.1 11/12, SDCard seems to work, only shows weird/wrong info when used as internal storage.

It shows 128 KB used of 59 GB as external storage and -29.98 GB used of 29.12 GB as internal storage.
[X Style (Pure) General] LARMYV:
Ok cool. I'll run another build and report back.
[X Style (Pure) General] itslels:
Side question....I saw that Clark is in limbo, status wise, with GZR. Are you going to be continuing to maintain it and build for it?
[X Style (Pure) General] gazisogood:
Hi guys.

I have Moto X xt1572 dual sim (retasia) with stock ROM 6.0.1

I try to install cm14.1 build 1111 and 1112 with pico Gapps 7.1. (flash from TWRP)

Then i boot to bootloader and flash boot.img file.

All works well, but sim not work :(

What I'm doing not right? Why sim not work?
[X Style (Pure) General] Hashbang173:
Don't flash the boot.img, it's outdated.

Re-install the ROM and see if sim works.
[X Style (Pure) General] slebit:
Don't know yet. I have some health issues to deal with right now. So I haven't decided. But I will prolly keep device source updated for a while at least for the ones that want to build from source.
[X Style (Pure) General] PlyshkaJr:
Battery issue

Am I the only one that has a serious problem with the battery in the last 'nightly'? The battery almost burning while charging and in 'battery' menu there is that 'Other' point , that eats my battery in am hour..
[X Style (Pure) General] LARMYV:
deleted

---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------

Sorry to hear about your health issues. I was able to build it today, and yes the video through the camera now works. But there is now a new bug that the phone would lock up when the lockscreen would kick in. I also did a full wipe to see if that would help and it didn't.
[X Style (Pure) General] hoppermi:
Not just you 11/11 would run itself out in about 4 hours of use as a paperweight. 11/12 seems to be sleeping properly.

I still am having SD card issues even on 11/12. It isnt corrupted and shows as mounted, but music players don't see it. I can navigate to it with root explorer, but only using root permissions. Not a huge deal, as I have other devices to use daily.
[X Style (Pure) General] gazisogood:
Not work :/
[X Style (Pure) General] lmulli:
Same here., so not just you.
[X Style (Pure) General] Fabiett83:
For everyone complaining about battery life, i already posted about this but i did some more tests, in 11-11 and 12-11 builds there is a process pm-service always running, this prevents the phone from sleeping properly.

I tried killing it in every way i found but nothing works.

Kernel adiutor shows 3 little cores always stuck at 1440 mhz processing something, the big cores are off or deep sleeping properly.

The TOP -H command shows 2 threads of pm-service each using 50% cpu and 3 threads of logd each using 15/20% cpu.

The QMI_FW : xport_reg Failed for service_id=0x35 version=0x1001 on 14 error filling logcat is present in both version so i can't see anything else useful.

Now i restored AICP but if [MENTION=4630246]Hashbang173[/MENTION] needs some other information i can reflash CM14.1 in a.. flash..
[X Style (Pure) General] drt054:
Loving cm 14.1 from 11/12 and don't want to go back.. Any fix for bluetooth as of yet?

Sent from my Moto X PureNexus
[X Style (Pure) General] zio guiduccio:
Thank you, wiping everything (sdcard included) i solved this problem. Right now the only bugs i suffer from are adaway not patching hosts (can't find the logs) and some soft reboot happening while listening music and preceded by audiofx crash. I'm on 8/11 and haven't tried Bluetooth yet.
[X Style (Pure) General] capeorigins:
I listen with Bluetooth for hours on Aicp 7.1 it works great. If you're looking for Bluetooth. Haha
[X Style (Pure) General] gaxander:
It works on AICP 7.1 with speakers and headphones, but not with car stereos with phone connection.
[X Style (Pure) General] capeorigins:
Yeah, corded still doesn't work(unless you install soundabout). But otherwise its working great!
[X Style (Pure) General] Hashbang173:
See if the speakerphone echo is fixed in the latest build (cm-14.1-20161116)
[X Style (Pure) General] Fabiett83:
Dirty flashed over aicp 7.1 20161116, everything seems good for now!

no strange cpu hungry processes and logcat is finally readable.

I really don't know who to call at 1:00 AM to test speakerphone, i will test tomorrow morning at work!

About this error:

11-17 01:03:14.552 8004 8004 E LocSvc_launcher: E/main:237]: Unrecognized value for GTP WIFI Mode. Setting GTP WIFI to default mode: BASIC
11-17 01:03:14.552 8004 8004 E LocSvc_launcher: E/main:276]: Unrecognized value for GTP CELL Mode. Setting GTP CELL to default mode: BASIC
11-17 01:03:14.552 8004 8004 E LocSvc_launcher: E/main:302]: Unrecognized value for GTP WAA Mode. Setting GTP WAA to default mode: DISABLED
11-17 01:03:14.552 8004 8004 E LocSvc_launcher: E/main:320]: Unrecognized value for PIP Mode. Setting PIP to default mode: DISABLED
11-17 01:03:14.552 8004 8004 E LocSvc_launcher: E/main:337]: Unrecognized value for SAP Mode. Setting SAP to default mode: BASIC
11-17 01:03:14.552 8004 8004 E LocSvc_launcher: E/main:380]: Error opening /etc/izat.conf No such file or directory
11-17 01:03:14.552 8004 8004 E LocSvc_launcher: E/main:861]: Exiting main. ret: -1

i copied /etc/izat.conf from stock MPHS24.107-58-1 and the error stopped, wifi and localization are working as before.

Edit: one last thing about audio, why we can't use the stock configuration? in the stock build.prop ro.qc.sdk.audio.fluencetype is set to none and the audio_platform_info.xml looks like this:

<audio_platform_info>
<acdb_ids>
<!-- Output devices -->
<device name="SND_DEVICE_OUT_VOICE_HANDSET_TMUS" acdb_id="7"/>
<device name="SND_DEVICE_OUT_HEADPHONES" acdb_id="9"/>
<device name="SND_DEVICE_OUT_SPEAKER_AND_HEADPHONES" acdb_id="9"/>
<device name="SND_DEVICE_OUT_SPEAKER_SAFE_AND_HEADPHONES" acdb_id="9"/>
<device name="SND_DEVICE_OUT_SPEAKER" acdb_id="14"/>
<device name="SND_DEVICE_OUT_SPEAKER_REVERSE" acdb_id="14"/>
<device name="SND_DEVICE_OUT_SPEAKER_SAFE" acdb_id="14"/>
<device name="SND_DEVICE_OUT_SPEAKER_AND_HDMI" acdb_id="18"/>
<device name="SND_DEVICE_OUT_VOLTE_NB_HANDSET_TMUS" acdb_id="200"/>
<device name="SND_DEVICE_OUT_VOLTE_NB_ANC_HANDSET" acdb_id="200"/>

<!-- Input devices -->
<device name="SND_DEVICE_IN_HEADSET_MIC_AEC" acdb_id="47"/>
</acdb_ids>
</audio_platform_info>
[X Style (Pure) General] Hashbang173:
The stock motorola audio seems to use fluence even though it is set to false in the build.prop. Since motorola seems to have modified the audio hal, unfortunately it is not that simple.
[X Style (Pure) General] Fabiett83:
Suddenly i do not feel so smart anymore... it is obvious that the starting point was the stock rom!

Maybe that's why you are a developer and i am a "normal user"?

About the speakerphone, I called one of my colleagues this morning and told me that my voice is clearly heard and he felt just a little, but not annoying, echo of his voice.

Edit: i called my wife and she said that there wasn't any echo, she noticed only a more metallic voice.

I noticed a strange thing that happens in youtube, gallery and music:

When you enable display rotation, if you keep the phone portrait or rotated to the left, audio is normal, but if you rotate to the right, the volume get a boost!

This does not happen using headphones
[X Style (Pure) General] lmulli:
I have to say that I find CM14.1 much more stable than AICP at this time. Well done to the Dev who updates both of course, along with a myriad of other devices! Busy lad!
[X Style (Pure) General] capeorigins:
I go back and forth between. But I usually end up back on Aicp generally cuz it gets more updates. Haha. I can't really tell which works better
[X Style (Pure) General] jDally987:
Wow! This is awesome. I haven't tried out AICP so I can't compare, but I must say, this is just like when I used to have my G2 and flashed from its stock Lollipop build to the experimental (at the time) CM13. Literally everything about it was improved, to the point where it felt like a new phone, so buttery smooth and feature-filled and almost impeccably stable.

Well I'm having pretty much the exact same experience with this. Had it for about a day now and no consistent issues, I'm really hoping that trend continues, but for now, wowzers this is stellar. Thanks to the dev.
[X Style (Pure) General] lmulli:
It does get updated more often, but for me it's too unstable and my device reboots itself at random whereas with cm it doesn't.
[X Style (Pure) General] HPAR:
Cm14.1 19.11

https://www.androidfilehost.com/?fid=601275311581036999
[X Style (Pure) General] Hashbang173:
See if in call audio has better adjustments now
[X Style (Pure) General] Fabiett83:
I don'know exactly what changed in 11/19 but now starting and stopping flash with chop chop is much more reliable, like with stock.

Opening camera is faster too but sometimes still gives error.

Audio seems lower than 11/16, rotating phone to the right doesn't boost the volume anymore but audio still hops for a split second, rotating to the left doesn't do that...
[X Style (Pure) General] HPAR:
Hi #bang, the 19.11 battery is awesome. It dropped 0% last night! Wowww
[X Style (Pure) General] joker2mbr:
Other than the small issue already reported with the camera (sometimes it crashes or takes a while to open), the ROM is awesome! Everything that I could test seems to be working properly. Thanks a lot, Hashbang! :D

Best regards,
[X Style (Pure) General] Silarn:
Besides the camera start up issue, the only odd problem I've had so far is a Bluetooth connection to Windows 10. It pairs successfully but the connection immediately drops. I'll have to try a different Bluetooth device to make sure it's just that one-off issue.

Actually, I did notice another thing. I was browsing Tumblr and noticed videos would load and then immediately crash. Sometimes they will play and sometimes not.
[X Style (Pure) General] HPAR:
one more, 20.11 =)

https://www.androidfilehost.com/?fid=313042859668275864
[X Style (Pure) General] joker2mbr:
Any idea on what has been changed on today's build?

Tks!
[X Style (Pure) General] chris_dis:
I think something is messed up, it tells me my phone is encrypted when i boot it up
[X Style (Pure) General] joker2mbr:
Hum... Thanks for the heads up. I'll wait a bit to flash this build then.

Best regards
[X Style (Pure) General] losttaco84:
I just dirty flashed that new cm build and it also told me my phone was encrypted. Luckily the password was password but then it said my data was corrupt and had to reset it. Resetting it did not work, so had to go back to 11/19 build.
[X Style (Pure) General] HPAR:
Same here =(
[X Style (Pure) General] Hashbang173:
Try it with this boot.img: https://www.androidfilehost.com/?fid=601275311581037092
[X Style (Pure) General] joker2mbr:
I just flashed it... It booted fine, but after a minute or so, the phone rebooted... I tested it again for a few minutes and another reboot happened. :(

---------- Post added at 08:57 PM ---------- Previous post was at 08:40 PM ----------

After the second reboot, the new build seems to be working fine. No more reboots... I don't know the reason. Maybe something here, in my end, I think? I'll keep using it! :)

---------- Post added at 09:43 PM ---------- Previous post was at 08:57 PM ----------

Unfortunately, after a few minutes, I couldn't wake the phone after it went to sleep. I had to do a forced reboot to wake the phone up. I never had a single reboot or a problem like that on the previous build...
[X Style (Pure) General] Hashbang173:
Sorry, testing some major kernel changes to get us up to date with CAF
[X Style (Pure) General] joker2mbr:
No problem!
[X Style (Pure) General] capeorigins:
After installing, and flashing the boot.img, it was working. But I wanted to restore to my backup, so I did. During the restoration, it rebooted the recovery. Then I tried again, same. I then tried wiping everything. Same reboot. Had to format the data partition xD