yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Original Android Development] micky387:
Hello.

So i have add this commit and other dependencie and all working great. :D thanks.

Just now,i have a problem again with your files. It's very strange but i have this error

I have inspected the source code and this file is present in cm12.1 (android/famework/av/camera) but doent exit in cm13.0 source...

i look in cameraservice.h in cm-13.0 source code and the include files are diff

You dont have this problem ??

regards,
[Galaxy Note 4 Original Android Development] jasopan:
Sorry for the idiotic question - but can someone please link me to an appropriate gapps download? I've found multiple threads with different DPI and different download sizes. I'm a bit confused. I just need something to work with CM and is 'stock'.

Thanks!

edit: think I found it
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Nah, still cant call somehow and also cant install gapps (will crash). So still not very usuable unfortunately. Once that's fixed I'll post a test version.
[Galaxy Note 4 Original Android Development] Mussels84:
call, text, gapps, wifi. get those and a test version makes sense :D

you guys have made some rapid progress.
[Galaxy Note 4 Original Android Development] AzurePanda:
decided to give cm another run and i cannot find the place to edit the model under build prop to fix the sms
[Galaxy Note 4 Original Android Development] Mussels84:
you shouldnt need to do that anymore. i thought that was fixed a while back?
[Galaxy Note 4 Original Android Development] AzurePanda:
still having a failed message error
[Galaxy Note 4 Original Android Development] Mussels84:
check your APN settings? personally i'm against MMS, so i can't remember the specifics of the fixes.
[Galaxy Note 4 Original Android Development] mixailo:
Is there any way to get the camera back after gapps flashing without factory reset? It got replaced by Google camera. Thanks!
[Galaxy Note 4 Original Android Development] Mussels84:
use a smaller Gapps package next time, the smaller ones dont replace the camera and other apps.
[Galaxy Note 4 Original Android Development] fattire:
Heh. The ability to make a phone call might be one of those basic requirements :) Actually, maybe this weekend I'll be in a position where I can really mess with my note4.. the only reason I've been relying on gekke is that he didn't mind trashing his phone for a while, and I needed mine. I am curious how our differences in RIL (I've got tmo, he's got xx) will make a difference..

Awesome!

Just now,

I think I had that error when I tried to build the CameraWrapper-- I thought I had commented that out... I can't remember.. but if it's building still off the top of my head I can think of two solutions:

1. provide the missing header manually for now

2. just don't build it. remove the camerawrapper/hal entirely (make sure that camera.apq8084 is not being added to BUILD_PACKAGES)

That's a small annoying thing to get stuck on at this point-- so do what you need to do to get around it :) You're very close!

ft
[Galaxy Note 4 Original Android Development] micky387:
Thanks fattire.

I have delete yesterday because if i add the cm13 file,lossing lot of header and build failed. It can found the root of this files... So deleted .

For now,i finish to build process.All is all right,it's the end .I report later ;)

P.s. CyanogenMod have updated his repo with the same commit as AOSP Enjoy. Many thing have updated too so the build process is ok now .

Do you want to open new thread in dev section for talking about progress ??
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Hey good to see you have your repo up ! And yes I saw they merged a lot of stuff yesterday related to ffmpeg, maybe that will fix the youtube video issue. Will try today.

Also I wonder if you get telephony to work. Mine actually does seem a RIL issue. Although RIL is up and I even have mobile internet working fine, I saw that Android is receiving some incorrect values from RIL in my case whenever I call the phone. Not sure at this moment why, but it's crashing my RIL whenever I try to call my phone and thus Android outside RIL.JAVA never learns about the phone call.

Also try it first with and then without our sensorservice.cpp workaround/patch and see if you can get it to work. The issue there is similar to the RIL issue I just mentioned: the sensorservice receives weird values. As it's going through binder, I think it might be a general problem in the CM13 code that causes this. But then again, some other phones on CM13 dont seem to experience those problems.

Anyway I talked to CM about it they said, at this time so much stuff is being changed, that you might want to hold off for a while. But then again, it's still interesting to see how far we can get ;)

Oh and last, try installing Gapps and let me know if it works. I tried tons of gapps but they're always crashing with the same issue (related to some permission in the gapps). I asked other CM people, they said they had no problems installing Gapps. So maybe it's Selinux related.

Anyway good luck and let us know about your progress/problems please !
[Galaxy Note 4 Original Android Development] fattire:
First off, congrats on getting to the end! I guess this is an example where we were a little ahead of upstream-- when you build this early, you can expect stuff like that to happen :)

Finally-- we talked about opening a new thread, but I think it's fine to stay here for now- We're all building for different things-- I'm on note 4 tmobile... so may as well just stay here until things get a little more stable...

Hopefully this weekend I'll have a chance to try it with the tmo version and see if it's got the same issue.

I think it very well may be upstream.

Update: For anyone building for tmobile, I created a cm-13.0 tmo device tree branch. Just add this to your repo:

<project name="fat-tire/android_device_samsung_trltetmo" path="device/samsung/trltetmo" remote="github" />

Be sure to remove any other project that would conflict- such as if you're loading trtlemo from cyanogenmod's repo

ft
[Galaxy Note 4 Original Android Development] pt.jcosta:
Why not send link for all to try and give feedback on bugs
[Galaxy Note 4 Original Android Development] ChemoNL:
Because it's far from use able and you must consider it alpha code.

Fatire and gekke explained this some comments back.

We are all as exited as you are but please be patient for the magic of marshmallow
[Galaxy Note 4 Original Android Development] micky387:
Ok,so phone dont boot. reboot into recovery mod....

I try to build with 3 diff kernel with [MENTION=3041959]fattire[/MENTION] commit android 6.0 but same issue.

For your Ril problem,peraps this can help you

https://github.com/AOSP-JF-MM/platform_hardware_ril/commit/bc26995c6ba13bd27b5b975a90d254b18224c2f9

and for my boot problem,this,

https://github.com/AOSP-JF-MM/platf...mmit/2400f313afdc85bfd8b7d70fba3e2b083da7ee2b

I try and report ;)
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Thanks for that RIL idea, I'm going to check my RIL version now.

As far as not booting: I'm not sure if you know this (I didnt) but you should boot into recovery after a crashing kernel (hang at the samsung boot screen) and then see if there's anything in /data/tombstones

If the kernel boots far enough (I think into user space) you'll find logs there !

*EDIT* hmm Ril version 8 (on cm12.1 we were using version 7), so the above RIL patch isnt for us :(
[Galaxy Note 4 Original Android Development] gekkehenkie11:
That's exactly what we dont want :) No need for feedback on bugs, most stuff doesnt work at the moment so the last thing we need is tons of post about what's not working.

Just give it some time. The main code from the CM people is still in full development, I'm sure once they come up with a more stable version it will solve a few things for us too and then we can put up a version to play with.
[Galaxy Note 4 Original Android Development] fattire:
Exactly! we don't need bug reports. We know what the bugs are. There are many, many of them! What we need is your contribution to fixes. If you aren't prepared to help at this point, just know you're doing your part by not asking for ETAs or builds :) And thank everyone in advance for this.

ft

PS- tmo builds with my repo above... if anyone has a tmobile device and wants to contribute :) Also, add these two repopicks:

115814 and 115815.

That is all :)
[Galaxy Note 4 Original Android Development] gekkehenkie11:
and another update: gapps work ! These gapps did it for me: https://www.androidfilehost.com/?fid=24052804347844834 key is that a factory reset after installation was needed.

Also found out that the RIL issue I'm seeing is not even a 6.0 issue, it appears on CM12.1 too with the new kernel and blobs. Investigating ....
[Galaxy Note 4 Original Android Development] gekkehenkie11:
And more good news, [MENTION=3041959]fattire[/MENTION] found a patch yesterday which set this value: ro.sec_ril.version=50

Which didnt make sense to me at first, since that value is not being used in our repo. However I found out that this property is being used in this patch for the Note 3: http://review.cyanogenmod.org/#/c/1...a/com/android/internal/telephony/KlteRIL.java

No time to test it right now, but I'm pretty sure this will solve our issue, because this is patching the exact spot that's causing our problems: " DriverCall.presentationFromCLIP"

It's crashing exactly there and in this patch they use some slightly different code there when on lollipop. So I'm pretty confident this will apply for us too.

Will test later today :) It's theoretically possible that we need more than this but let's hope that this is all we need to get calls going ;)
[Galaxy Note 4 Original Android Development] Mussels84:
it may not matter with CM13, but i think i found the cause for the black-screen freeze - the stock CM camera. Could be the night-mode fix we have, but i've managed to replicate it with my phone and my fiancees.

Basically, we use the stock camera - then within 15 minutes (usually using FB messenger, because we use that a lot) the phone would hard freeze on a black screen.

I changed to open camera off the play store ~2 weeks ago and haven't had one of those crashes UNLESS i opened the stock camera for some reason.

Could explain why it was hard to reproduce, as a lot of people here replace the camera app, moreso since many Gapps packages replace it.
[Galaxy Note 4 Original Android Development] nivron:
Just a quick update on CM13. Confirmed that video is working. Hoping we can get more bugs worked out next week. No network for the CDMA variant at the moment.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Nice ! You must have used a few different blobs than I have, let's talk on IRC.

BTW I've got calling working now on 5.1.1 kernel with 5.1.1 blobs on 5.1.1 ;) The patch I mentioned above indeed fixed it. Going to build 6.0 now again with the 5.1.1 stuff, but I think it will work too ;)
[Galaxy Note 4 Original Android Development] nivron:
I'm not gonna be available until Monday. I was working with fattire this afternoon. He should be able to catch you up on IRC. [emoji1]
[Galaxy Note 4 Original Android Development] gekkehenkie11:
If anything, could you make a zip of the blobs you are using ? I'll compare them against mine and we'll have the youtube video thing sorted out. BTW did you try several youtube vids ? Some worked for me, it's a specific codec that caused problems (only in youtube mobile, not on desktop version).
[Galaxy Note 4 Original Android Development] nivron:
Sure if I get a moment I will. I only used the current blobs for trlte-common plus what is in fattire's wiki. I only tested via YouTube app but a few videos all worked good.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Ok if you have time, please also test from a browser windows, mobile version and test a few youtube video's. Thanks !
[Galaxy Note 4 Original Android Development] Mussels84:
jus a reminder that i had youtube issues with freezing and stuttering if my device name was wrong for my region - so with a 910G in aus, having it shown as 910F would cause all sorts of issues (especially on 1080p 60FPS videos)

changing to the correct model for here of 910G fixed things. makes me wonder how a tourist would fare in countries their model isnt sold :/
[Galaxy Note 4 Original Android Development] saifullah90:
Keep losing Connection lte how to fix
[Galaxy Note 4 Original Android Development] :
Use a 5.0.1 bootloader/modem :good:
[Galaxy Note 4 Original Android Development] Mussels84:
5.0.1? 5.1.1 no good?
[Galaxy Note 4 Original Android Development] agsola:
Current release is based on the 5.0.1 Samsung kernel, that's why.

At least until it is updated (which seems that is going to be soon, according to CM13 updates).

So..., right now Source code is programmed for 5.0.1, so better use compatible with that.
[Galaxy Note 4 Original Android Development] Saarliner:
Which version do you use?
[Galaxy Note 4 Original Android Development] agsola:
See 1st post.

That one.
[Galaxy Note 4 Original Android Development] Narekrocks:
If you get it fixed can you tell me what you used (or anyone else)? i have had this problems and none of the suggestions have fixed it for me. I used the BOB4 modem and bootloader as suggested and lte problem was still there. Flashed zips that the dev had suggested not helping either. I am on 910f btw.

Touchwizz is really terrible so I am on SOKP and 4g is working but I would much rather have CM.
[Galaxy Note 4 Original Android Development] canned_polar_bear:
i'm using http://opengapps.org/ , 5.1 micro package. working great so far.
[Galaxy Note 4 Original Android Development] Mussels84:
i'm on 910G and 5.1.1 modem/bootloader with no issues, but my carrier is only 3G.

If any 910G users have a modem/bootloader download for 5.0.1 that'd be great to share (and have added to the OP)
[Galaxy Note 4 Original Android Development] Andycar:
Hi. I'm currently on N910G Dr.Ketan ROM 5.1.1 and have previously used 3 BL/modem packages from his thread. I hope he doesn't mind if I share my little collection:

http://1drv.ms/1NfWlIl

In that folder there are three 5.0.1 BL/modems.
[Galaxy Note 4 Original Android Development] saifullah90:
i dont know if this fixed the problem but i havent lost lte yet ,

1. download N910F_COI3_Bootloader_Modem

2. go to Acces point , APNs and then press on your celluar brand , go down to '' Bearer '' and change to '' LTE ''

it seems to work just fine :)
[Galaxy Note 4 Original Android Development] pt.jcosta:
here's cm13 for galaxy s5. serves to take away information to the note 4...

Download

https://www.androidfilehost.com/?fid=24052804347849406
[Galaxy Note 4 Original Android Development] fattire:
Heads up for [MENTION=733411]Gekke[/MENTION]/@nivron/@micky387/anyone else who might be building:

I wonder if the RIL issues are related to this commit which doesn't seem to be in cm-13.0's Android.mk yet..

ft
[Galaxy Note 4 Original Android Development] Mussels84:
that is awesome. i hope we can get them added to the OP for 910G users. are they modems and bootloader in the one file?
[Galaxy Note 4 Original Android Development] than33:
I'm using newest available firmware without any single problem. LTE works and I got 70 mbits transfer rate. Mms works.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
I'm sure this must be it. I was wondering why our own RIL code wasnt being included, but this is why :) That's the downside of wanting to be on the bleeding edge: issue's in the CM main code that cause problems like this. But we're getting there :)
[Galaxy Note 4 Original Android Development] fattire:
Yup and you'll also need this one too :)

update: if that doesn't apply nicely, try this diff I made.. With the latest repo sync it builds to the end:

Package Complete: /media/test/lollipop/out/target/product/trltetmo/cm-13-20151101-UNOFFICIAL-trltetmo.zip

Update to my update:

I'm thinking actually we need all of these since March.. Looks like a lovely project for someone, especially this one.

Note that some of these are waiting in gerrit... but still havethe merge conflicts so we'll probably need to reconcile them still.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Hey fattire, I just talked to CM, you can read it in cm-priv chat, they said that a solution would be to just take an AOSP libril and try to get it going. It's a possibility, we could see if we could find a source based RIL for a similar device and adapt it. But depending on how similar that RIL would be to ours, it might become a huge project though. They said that they'll probably still support those patches in the future to extend the RIL.java code, so in that case we wouldnt need a source based RIL. Anyway lets dicuss on IRC later today
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Hmmm is the modem an integrated part of the 810 SoC ? I think it is, right ? In that case we should just search 810 based devices for libril code ?

Hmm I just found this article: http://www.fool.com/investing/gener...nc-impresses-with-snapdragon-810-feature.aspx

Where it says:

So if that's true, lets look at 810 devices like the Nexus 6 and see if any of those has the libril code. If not, let's look at MDM9235 standalone libril code

*EDIT2* hmmm it might be even a bit more complicated than just replacing the libril. I mean the 910F libril is dependent on the MHI driver. And then there's all that qmi/qmux stuff that's hooking into it too ... MHI is open but that qmi/qmux stuff is closed source ...

Having an open source libril is all nice and all but I'm not sure how easy/difficult all this is going to be, so maybe it's better to just go with what we've always used, those RIL.java extensions and then use just Samsung's libril blob. Seems by far the easiest option. Anyway let's discuss on IRC when you're here

*EDIT3* That damn libsec-ril.so is 3 mb ! Reverse engineering that is just not feasible. Doing it for the nightshot mode took me over a month and this is WAY more work. Besides that we're looking at a myriad of possible problems there. Let's forget the whole open source RIL idea and go with those RIL.java extensions ;)

*EDIT4* actually, LOL, the nexus 6 uses AOSP libril too. So if we'd take their libril code + their modem blobs, we should be able to get it going ! But then we'd also need their modem partitions and their modem kernel drivers I guess. And then, how would we get TMO and other brand carriers going ...
[Galaxy Note 4 Original Android Development] gekkehenkie11:
BTW I just did a test to make sure it's actually our *only* ril/audio problem: I just replaced the RIL code in ril.java with our riltrtle.java code. And then I can perfectly call, and receive calls, including audio works fine !

BTW2, Rashed just said: " for RIL, pick changes 114803 114804 114805 114806".

So if we just cherry pick those 4 for the time being in our after-sync script it might work too.

Actually, you know what. Let's just use the modified RIL.java that I made, including our samsung stuff, for the time being so that we have at least a fullly functioning RIL. And then just use that every time until CM has fixed up their RIL stuff. Why waste more time here when it's up to CM to fix in the first place.
[Galaxy Note 4 Original Android Development] Racinghart91:
This is not fully cm related but it has something to do with it.

When I pair my phone to my cars radio, it always starts using Spotify, but I want to listen to the tracks on my sd card most of the time.

Even when I start my music player and push next on my radio it starts to use Spotify.

I love Spotify but I have to drive 2 hours a day for work so my data limit gets burned after 2 weeks, That's why I want to listen to my own music.
[Galaxy Note 4 Original Android Development] Narekrocks:
Sadly didn't work for me. It stops working after a period of use as usual :( My hardware is fine as it works on Touchwizz based ROMs and even on some AOSP based ones. So I don't know what the problem could be besides CM and the Carrier I have (Switzerland, Orange) not working together for some reason when it comes to LTE.
[Galaxy Note 4 Original Android Development] Mussels84:
try a bootloader and modem from your region?
[Galaxy Note 4 Original Android Development] micky387:
Hello.Be careful with this new commit it will break our build process for dt.img
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Man basically whole CM13 is just a mess at this moment. Their RIL isn't working, they have SQL errors (if you enable qcom.location.com) and codec problems. At this point I think most of our stuff is ready and it's just waiting on CM to fix up their stuff. I guess it might take a while ...
[Galaxy Note 4 Original Android Development] micky387:
yes of course.

For me,after 15/20 build succes,i cant boot to cm13.

Try many kernel,commit [MENTION=3041959]fattire[/MENTION]'s kernel but same issue.Or phone reboot into recovery mod after bootloader or after android updating and finish boot,phone bootloop.

I try to use adb but impossible.

-error: insufficient permissions for device
-unauthorized
-no permissions

after try in su adb,i have

- waiting for device -

Of course,i have modified default.prop in ramdisk but no success. Impossible to boot.

and in data/tomstones,there are nothing interesting.

I have commited all RIL stuff and gerrit commit but same thing....
[Galaxy Note 4 Original Android Development] fattire:
If you have a chance, stop by #cm-note4 on freenode.. Good to have everyone who's building in one place.. gekke, nivron, and myself among others are there...
[Galaxy Note 4 Original Android Development] speedyjay:
https://afewe.wordpress.com/android...ith-the-radio-layer-interface-ril-in-android/ for everyone working on android 6.0, just throwing suggestions in their to help :)
[Galaxy Note 4 Original Android Development] fiorellona:
Will the fingerprint work on cm13?
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Not sure what you changed exactly but setting ro.adb.secure=0 works for me. I just changed it in vendor/cm/config/common.mk btw, so I dont have to change it manually after each build ;)
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Eventually it should. But I highly doubt the android part in CM is 100% ready already. And it's going to be a challenge to get it going with Samsung having released their HAL. So don't expect fingerprint too soon.
[Galaxy Note 4 Original Android Development] fattire:
A better place to add it might be system.prop.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
My build just broke on the dt stuff. However I think it's not the commit you just posted, but this one that breaks it:

I think it's this commit: http://review.cyanogenmod.org/#/c/115845/
[Galaxy Note 4 Original Android Development] micky387:
ok i look it later

yes, this is what i have changed

thanks
[Galaxy Note 4 Original Android Development] Mussels84:
Using Open Camera off the play store, it has no silent shutter option.

I contacted the dev and his response was "If the option isn't there, then it means your device doesn't support this through the Android API (the stock camera app may be able to happily ignore that)"

is that something that can be tweaked at the ROM end?
[Galaxy Note 4 Original Android Development] fattire:
The shutter sound may be a legal requirement in the US. I'm not sure of the "upskirt laws" proposed in congress ever got past the committee stage or if it was made law somewhere else (Korea?) but anyway- you can shut it off if you do your own build.

The file/line to change is here.
[Galaxy Note 4 Original Android Development] Mussels84:
as someone totally inexperienced with this, is it possible to just flash a .zip file to change it?
[Galaxy Note 4 Original Android Development] lgumo01:
You can just delate/rename shuter.ogg (or something like that) in system/media/ui

Wysłane z mojego SM-N910F przy użyciu Tapatalka
[Galaxy Note 4 Original Android Development] Mussels84:
thats something i can work with. wonder if that'd work for third party camera apps, i'll poke around.

edit: totally did, seems open camera uses the stock sound file :D