yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] tiny4579:
Forgot to mention the important part:

http://review.cyanogenmod.org/#/c/121002/
[ONE Android Development] katinatez:
Us devs talk thru pm too. Already know how to fix data. BUT I'm already on the road traveling and did not bring laptop.
[ONE Android Development] suaverc118:
Good to know. All of y'all are doing a great job. Safe travels
[ONE Android Development] danieldmm:
For me even with this commit it's a no go for mobile data. Clean build, clean install. No mobile data at all. It sucks using only wifi...

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] geekynoob:
Guess this should bring an end to the Super su issue..

https://github.com/PureNexus/androi...mmit/d502eb337d26692f33b7fd0f0f168081e89375bf
[ONE Android Development] Karel VH:
Made a build with this included if you're interested: https://www.androidfilehost.com/?fid=24269982087002837

Changelog:

Switching from WiFi to data fixed

SELinux enabled

SuperSU working with SELinux enabled

Long click tiles to go to settings

CMFileManager root fixed

Removed daynight theme
[ONE Android Development] lombyzgz:
Full wipe or not needed?

Enviado desde mi A0001 mediante Tapatalk
[ONE Android Development] Karel VH:
Should be able to dirty flash if your wipe telephone db. Anyway a clean flash would be better for this build.
[ONE Android Development] captive:
Self building my CM 13, stuck on boot logo

Hi everyone,

'm pretty sure I am missing something stupid, but since a week or so, when I build my cm 13 (using standard repo and the manifest from the second post), the rom simply won't boot. The problem is in the boot.img, because if I replace it with one from another custom built rom, the phone boots normally.

Any hint?
[ONE Android Development] piddlpiddl:
This worked. More precisely I did the following:

Boot to recovery

Open adb shell

rm -rf /data/data/com.android.providers.telephony

Quit shell

Flash zip

Place a call so the data for telephony is being recreated
[ONE Android Development] anuraag.neo:
Official cm13 started

http://download.cyanogenmod.org/get/jenkins/136120/cm-13.0-20151124-NIGHTLY-bacon.zip

http://download.cyanogenmod.org/?device=bacon

http://www.cyanogenmod.org/blog/a-marshmallowy-cm
[ONE Android Development] tiny4579:
Doubt it has this merged:

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

So may have the radio issue. However, might be worth it for the firmware updates (if any exist yet).

EDIT: No firmware updates. Recovery logs say already up to date. But modem might have to be flashed manually due to TWRP 2.8.7.0 so there may be an update for that.
[ONE Android Development] tiny4579:
Due to data issues in the official nightly,

I'm posting mine.

https://www.androidfilehost.com/?fid=24269982087003355

Merged commits up to date +

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

http://review.cyanogenmod.org/#/c/118590/
[ONE Android Development] zaphodbeeb:
I just built with these, and also the supersu change but still have the same old data problems. :crying:
[ONE Android Development] jgcaap:
Didn't miss any commit?
[ONE Android Development] tiny4579:
I got all the commits I intended to have in. It was synced as of last night as well.
[ONE Android Development] jgcaap:
Isn't working for me yet.
[ONE Android Development] AcmE85:
Data works fine here in Germany. Thanks for your build.

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

This should only fix the switch from wifi to data right?

I had no issues with data prior to this commit though.

I am really wondering how they could release a first nightly the way they did. :confused:

What is also bugging me since kitkat is this issue which Sultan fixed in his build:

*Fixed rare cares of touchscreen not working when it's supposed to (ex. you wake up the phone and touchscreen doesn't work)

Could you maybe cherrypick it for your upcoming build?

https://github.com/sultanxda/androi...mmit/f8cb5100e85937f29d6415af5d7e17931955587c
[ONE Android Development] Santhosh M:
Does anyone know the fix for this ? I could see this earlier in the thread and hence thinking someone might be having an idea

11-24 20:50:04.405 3125 3125 E AndroidRuntime: Process: com.android.systemui, PID: 3125

11-24 20:50:04.405 3125 3125 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'com.android.systemui.assist.AssistOrbView com.android.systemui.assist.AssistOrbContainer.getOrb()' on a null object reference
[ONE Android Development] ch-vox:
Hi,

I've just installed your build and I'm quite surprised not having a single FC ! :good:

I've tested a few MM Roms before yours, and I've always encountered FC's or reboot....

the only thing that I'm missing for now is the ability of changing screen DPI in UI settings. But I'm pretty sure CM will implement it in the next days.

Did you modify anything from CM 13.0 (except the quoted commits) or is it a "pure CM13.0" ROM ?:cool:
[ONE Android Development] AcmE85:
In the meantime you can create a local.prop file under root/data

and add the following line: qemu.sf.lcd_density=400

400 is my desired dpi, you can change it of course.

permissions need to be set to 0644 (rw-r--r--).

This also survives dirty flashing the nightlies or other builds.
[ONE Android Development] ~KV:
Negative. Not possible with the latest CM13 Nightly.

This is mainly because of the SELinux being Enforcing....

You can in no way create local.prop OR edit build.prop.

The only way to change DPI is via adb.
[ONE Android Development] AcmE85:
I would never suggest things which do not work on my device.

I'm running [MENTION=3500210]tiny4579[/MENTION] latest build which has SELinux enforced by default

and my described method works.

System can't be mounted as RW of course, but data works fine.

I'm creating multiple files under data just as I type this...
[ONE Android Development] Lord*Andre:
Did you guys tried app Le DPI Changer to change DPI. I have tried it on marsh 1.3 and changed DPI without problem.
[ONE Android Development] :
Negative again!

Local.prop is working for me since the first unofficial cm13 nightlies have started, and it's working fine with today's official and unofficial nightly too, as it did with cm12.1.
[ONE Android Development] ch-vox:
thank you for that tip.

I don't have the time to test what you wrote, but anyway I'll do it ASAP.

did you encounter any bug with the apps you're using with this res ?
[ONE Android Development] AcmE85:
No issues so far.
[ONE Android Development] :
For me the same, I'm running 320 dpi "for ages" now without any single issue so far
[ONE Android Development] ch-vox:
I was asking about the tip for MM. I usually run 400 dpi (KK then LP) but set by UI settings.
[ONE Android Development] royr719:
Wouldn't this method cause problems with apps not showing in the play store?
[ONE Android Development] abhibnl:
Play store ususally tracks dpi from build.prop. So this method will not affect play store apps.

Sent from OnePlus One
[ONE Android Development] ~KV:
How weird that it ain't working for me....[emoji20]
[ONE Android Development] :
Mmmh, there should be no reason that it doesn't work for you too.

Let's check:

Have you set the correct permission (0644) for the new "local.prop" file based in data?

File content:

qemu.sf.lcd_density=320

After a restart, all should be fine.

Good luck!
[ONE Android Development] ~KV:
Have you tried with the official nightlies?

If I'm not mistaken, that is the default permission.
[ONE Android Development] :
The system doesn't provide a file called "local.prop", you have to create one and set up the right permission.
[ONE Android Development] AcmE85:
Exactly. I'm on today's nightly and it still works (why shouldn't it).

Once again, the file has to be created under root/data
[ONE Android Development] ~KV:
What I meant by "default" is that, upon creating the local.prop file under root/data, the permissions get set to 0644 by default...

Why it shouldn't work?

As SELinux enforcing is preventing to modify or change build.prop

But I'll try again with the latest nightly...[emoji106]?
[ONE Android Development] :
You're not modifying or changing build.prop ... [emoji6]
[ONE Android Development] AcmE85:
No, the default permissions get set to 0666 (rw-rw-rw-).

You

do not

have to modify build.prop under root/system/

you have to create -> root/data/local.prop

Either you don't read or you are trolling. Regardless I'm happy with 400 DPI, so are others

so clearly the fault is on your end. I really hope you can make it :fingers-crossed:
[ONE Android Development] jgcaap:
Whoever needs busy box : https://drive.google.com/file/d/0BzsULouX5bb3MmQ1THB2S0RuS3c/view?usp=docslist_api
[ONE Android Development] tilaksidduram:
Uploaded a new build dated Nov 25th with all latest fixes and updates.

* added DPI changer to Settings -> display

*added quick reboot toggle to developer settings

*Added long click tile support.

*Cm already merged editable tiles

*Backlight settings can now be changed no more FC.

Note : turning data on is still not fixed. Cm is aware of this issue and will be fixing it soon.

http://downloads.codefi.re/houstonn/tilak/bacon/mm
[ONE Android Development] vinman12:
Looking good.

Yea I'm sick of hearing about data lol
[ONE Android Development] tilaksidduram:
It's about data every where, every other forum that talks about cm13 on OPO the only complaint it toggling data is broken.

New issue I am seeing with the draggable tiles. Clicking the tiles does nothing, user need to click on the tile name for that tile to activate.
[ONE Android Development] ~KV:
[ALPHA][WIP][ROM][6.0] CyanogenMOD 13 [UNOFFICIAL]

I know I know

I changed the dpi with the help of a flashable zip and that worked...

Later on, as I said, I will try again with local.prop and this time see the permissions properly[emoji1][emoji106]?

EDIT: So I tried it after all and it seemed like Root Explorer couldn't change/save permissions properly. Tried with ES File Explorer and it worked!

Thanks.
[ONE Android Development] AcmE85:
I am using root Explorer btw, but I'm glad it worked out for you in the end.
[ONE Android Development] matssa:
Yup, this issue is known : http://review.cyanogenmod.org/#/c/120339/

---------- Post added at 07:10 AM ---------- Previous post was at 07:06 AM ----------

Anyways, the latest CM version has the DPI changer ;) A lot simpler :)
[ONE Android Development] jgcaap:
This version odexed is amazing
[ONE Android Development] AcmE85:
At least on 400 DPI the new DPI setting results in misaligned graphics.

E.g. the switches in the settings menu and Root Explorer as a whole look wrong.

The issues are gone with local.prop back in root/data so I'm sticking to it.
[ONE Android Development] varund7726:
The Issue with clicking tiles is because you added long click tiles

revert it and you’ll be fine

Also has anybody Noticed ,keyboard doesn’t appear while adding broadcast Tile?
[ONE Android Development] tilaksidduram:
Yes I am seeing it on my builds, keyboard does not show up when trying to add a broadcast tile.
[ONE Android Development] varund7726:
One more thing.do lockscreen bottom shortcuts disappear randomly ?

It looks like this now
[ONE Android Development] matssa:
On a unrelated subject, how did you show the weather on the lockscreen? Option in CM13 or an extra Xposed module?
[ONE Android Development] varund7726:
Not cm13

Its RR MM based on cm13

I never use xposed :PP

Anyways .anybody with the randomly dissapearing bottom shortcuts?
[ONE Android Development] matssa:
Ack crap, I would like to have this weather info on the lockscreen with CM12/CM13 (official ^^).

Concerning the shortcuts, did you verify the settings? Other than that, I can't help you more ^^'
[ONE Android Development] AcmE85:
Possible fix for the System RW mount issue

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

If someone is actually still building...
[ONE Android Development] katinatez:
I spotted it just now and started a new build, but going to bed. I'll post build tomorrow.
[ONE Android Development] vinman12:
Running it on my build now

Confirmed working.
[ONE Android Development] varund7726:
I can confirm mobile data switching on immediately after WiFi is switched off without using airplane mode

Works like a charm now with the newer blobs and device tree clean ups :good:
[ONE Android Development] Arju:
Stop teasing us haha :silly: thank you for letting us know. Looking forward to test your RR marshmallow build in hopefully near future ;)
[ONE Android Development] matssa:
It has been fixed in the newer CM13 build, or directly in your ROM? Didn't want to try out CM13 until this was fixed ^^
[ONE Android Development] ch-vox:
this is fixed in latest CM13 nightlies.
[ONE Android Development] matssa:
Thanks! Can you link the commit? I can't seem to find it ^^
[ONE Android Development] ch-vox:
Yeah sure ! http://review.cyanogenmod.org/#/c/122027/

source : http://xdaforums.com/showpost.php?p=64063586&postcount=311
[ONE Android Development] matssa:
Ah thanks! I saw this commit but didn't think it was gonna repair the data issue. But it seems as it still got some location problems, but I guess there is a commit on the way (saw one talking bout this).
[ONE Android Development] jgcaap:
Guys I tried to compile stock cm with stuff from git and data situation is still not solved for my compilation. Anyone know if is something not available at github?

---------- Post added at 03:50 PM ---------- Previous post was at 02:57 PM ----------

And I have this included..
[ONE Android Development] zaphodbeeb:
me too. Data is working perfectly with nightlies, but not built versions from github. The only pick I have included is 113774 which is the java fix for ubuntu. I guess there is something not up to date on github.:confused:
[ONE Android Development] AcmE85:
[MENTION=2040569]jgcaap[/MENTION] [MENTION=3874152]zaphodbeeb[/MENTION]

Did you include the updated blobs?

https://github.com/TheMuppets/propr...mmit/2dea41127731d9d8141ca5d7706065361cb4137a
[ONE Android Development] jgcaap:
Yes... Just repo sync... That's why is weird. Is working for everyone?

---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------

Did work for you properly? Any changes needed ? Thanks
[ONE Android Development] jgcaap:
Which java fix?
[ONE Android Development] tilaksidduram:
No more data failing to connect issue, i can confirm that after the recent commits to the oneplus device tree and the blobs all is working fine now. i can connect to data even after turning off wifi.
[ONE Android Development] jgcaap:
So strange... I have a source only of cm where gets directly everything from their git doesn't work.

Can you share me your source to compare? Thanks.
[ONE Android Development] varund7726:
I have GPS.location issues on gmaps now.

Nope all stock cm bacon sources
[ONE Android Development] vinman12:
So maybe its in framework av that's where the sound trigger lies and all those other errors I c in that log
[ONE Android Development] fards:
Did you try the new lib from muppets?

The errors look lower level than framework
[ONE Android Development] vinman12:
I have synced up to date with TM yes.

I still believe its in the audiopolicy just my thoughts right now, I remember having to do this before I think just trying to remember
[ONE Android Development] toyota86:
whoa... that 3D effect search bar is like going back to Gingerbread. is this real?
[ONE Android Development] tilaksidduram:
[MENTION=5291611]CraZY_BoY^[/MENTION], [MENTION=4406894]vinman12[/MENTION] and All, the no audio in call bug has been fixed now. There is a driver by named libaudcal.so which was missing in the vendor oneplus repo. Steve fixed it a few hours ago.

You dont have to rebuilt the rom. Just download this file frrom the below link and copy it into the "system/vendor/lib" folder using a file explorer. While copying the file the file explorer will say that the file already exist just over write. And change permission of the copied file to 0644 or rw-r--r--. Reboot the phone once for the new file to take effect. Enjoy making call now.

https://github.com/TheMuppets/propr...mmit/2b4530edaf34de5e7770b07f9d85825f7962f11f

---------- Post added at 08:08 AM ---------- Previous post was at 08:06 AM ----------

The new lib called libaudcal.so fixes the audio issue. I have tested it already.
[ONE Android Development] jaywithag:
Where is the link?
[ONE Android Development] vinman12:
So i missed that when i synced lol, ty sir

---------- Post added at 11:30 PM ---------- Previous post was at 10:47 PM ----------

Now to fix sending pics in mms thats a must
[ONE Android Development] jaywithag:
Try going to developer options and turning on cellular network always on.
[ONE Android Development] tilaksidduram:
Sorry forgot to add the link in my previous post. Here is it.https://github.com/TheMuppets/propr...mmit/2b4530edaf34de5e7770b07f9d85825f7962f11f
[ONE Android Development] vinman12:
here is a updated build guys

replace lib in vendor to fix incall audio (FINALY)

picked enable doze

picked remove storage list

picked LockClock update pro guard for play services

picked SetupWizzard update pro guard for play services

picked SetupWizzard missing dependency

picked update playservices

say bye to that ugly search bar

link

https://www.androidfilehost.com/?fid=24052804347845014

---------- Post added at 11:50 PM ---------- Previous post was at 11:46 PM ----------

hey who turned that off ? lol

thanks for that.
[ONE Android Development] vinman12:
Ahh hello google search bar.

Why not put marshmellow name in the kernel lol
[ONE Android Development] itslels:
Amazing work guys. Thank you for what you do!
[ONE Android Development] suaverc118:
On the latest builds, does on tap work with soft keys or so we have to enable the on screen keys for it to work?
[ONE Android Development] kalpik:
Great work! So what's still broken on the builds now?
[ONE Android Development] itslels:
All hardware works now. Just software related things left. Built in root broken, now on tap doesnt work with hardware keys, etc. Its rather stable though and the bugs are fairly minor
[ONE Android Development] renaltosonylevi:
Try it for your self. Apart from some gapps issues so far so good. Still haven't got contacts synch. Also notixed aosp keyboard had no dictionary. Installing Google keyboard fixed that. Decided to do a full install and see how it goes as daily. Have seen no deal breaking issues so far, everything else seems to just work.

This has nothing to do with the 'm' build but has anyone else having issues trying to insert a quote using taptalk or XDA premium, being having issues for the last 2 hours.:(
[ONE Android Development] itslels:
Anyone else tried AK kernel with it? Seems to break DT2W for me..
[ONE Android Development] stryker09:
the only issue im having is with titanium backup not allowing me to restore my apps :/ but other than that everything seems perfectly fine! any bugs from here on are minor and not deal-breakers for me
[ONE Android Development] jaywithag:
I use backup + beta. It works well to restore apps.
[ONE Android Development] fards:
Gps not working on build I made late last night.
[ONE Android Development] zaphodbeeb:
Nope. still not working for me. Just to make sure I did a complete rebuild from source. What are you building on? Im on Ubuntu.
[ONE Android Development] jgcaap:
Ubuntu also.
[ONE Android Development] katinatez:
For devs this is what is missing for data to work!

Dont forget you need this source at your local_manifests.xml:

<project path="vendor/qcom/opensource/dataservices" name="CyanogenMod/android_vendor_qcom_opensource_dataservices" remote="github" revision="cm-13.0" />
[ONE Android Development] jgcaap:
Without you what is bacon? Thanks bro
[ONE Android Development] varund7726:
Umm i dont have this and i never knew about it

and yet

And my data switching works like a charm

strange lol
[ONE Android Development] tiny4579:
That should have been automatically added by room service.
[ONE Android Development] zaphodbeeb:
Works like a charm. Thanks. I didnt know it was required.:good:
[ONE Android Development] frosty)):
It's amazing I'll test it on my note 4 thanks for rom Bro
[ONE Android Development] Arju:
I hope you're trolling. :silly:
[ONE Android Development] tilaksidduram:
CM is updating their sources to 6.0.1, there are build errors currenlty and fixes for those errors are still not available on github nor gerrit.

Beware if you plan to start a build using the current sources
[ONE Android Development] katinatez:
Thanks for the heads up, was going to repo sync but I changed my mind.
[ONE Android Development] Toasted Meat:
Is anyone else having issues where files aren't showing up on Windows until you reselect MTP in developer options?
[ONE Android Development] matssa:
Not an issue, the default choice is the charge only. Before, the default option was to mount on the PC. You can always change the USB notification to MTP. CM will (I hope) make a setting for this, but not can't be considered as a bug imo.
[ONE Android Development] jgcaap:
Anyone here having random reboot issues with new update?
[ONE Android Development] luisflorit:
I'm trying Cyanogenmod 13 (Android 6.0.1) in a Samsung Galaxy Tab 8.4 pro (mondrianwifi). I have an external SD card formatted as ext4. The system mounts it quite weirdly as:

/dev/block/vold/public:179,65 62251740 32992224 29259516 53% /mnt/media_rw/ee73c607-8f33-4eab-867b-b11aae3a6571

I can see the contents as root both in ADB shell and Terminal Emulator, but nothing else. An icon appears showing the sdcard, but when clicked a window flashes and disappear.

I tried the usual /data/local/userinit.sh and the sdcard command, but could not make it to work.

Any suggestions?

Thanks!

L.
[ONE Android Development] Erwin1477:
I'd first want to say, I really enjoy this rom, everything works perfectly as it should be. Though there's one annoying bug: I got many random reboots.
[ONE Android Development] CallmeReaz:
Great.... Hope will get the version for Samsung Galaxy S 3 Mini GT-i8190
[ONE Android Development] wistlo:
There's a thread in the cyanogenmod.org forums where others are having same issue with official nightlies after 20151208 (when 6.0.1 appeared).
[ONE Android Development] Toasted Meat:
I'm runnning CM13 12/22. Having random reboots, music stopping on every music player, and 2 hour on-screen time. MTP
[ONE Android Development] nak0604:
I just clean flashed the 12-22 build and I have no sound at all. The volume is maxed and still no sound at all. Notifications are fine haven't tried a call
[ONE Android Development] Toasted Meat:
Just dirty flashed 12-25 nightly and random reboots as usual...
[ONE Android Development] fards:
There shouldn't be any changes between 24 and 25

Builds.
[ONE Android Development] Toasted Meat:
Flashed 12/30. Random reboots as usual and lock screen music visualizer ended up breaking.
[ONE Android Development] Toasted Meat:
Just a warning that 12/29-12/31 that the Clock app is crashing so your alarm may not ring. My alarm didn't ring for 3 days.
[ONE Android Development] gerciolisz:
Seems your problem.. Mine on 31.12 works well

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Android Development] Toasted Meat:
Did you clean or dirty flash?

Just flashed 01/01 and Clock is still crashing.

I'm using OpenGapps 6.0 ARM mini after every cm flash.
[ONE Android Development] gerciolisz:
Damn sry im not on that rom anymore XD sry but try different gapps and dont flash them everytime if rom have gapps survival script.

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Android Development] nartan:
I'm in 01/01 in my N9005 and everything seems to work fine.

Happy New Year, for all who participate in this wonderfull community.
[ONE Android Development] tiny4579:
Just wondering why this thread is open. It seems to be a less active nightlies thread at this point. We already have one for nightlies.
[ONE Android Development] PlayersHeaders:
Hello i and other users have the issue that it dont work to disable the heads up, they appear by some apps like telegeam, facebook... . pls fix it, heads up are really annoying.