yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] Magnetox:
in regards to bluetooth if we're testing/making a driver can we make one that supports playstation controllers?

i started a thread here with some options for adding playstation bluetooth support, BlueZ seems like a good option? I don't know if simply BlueZ would work, it might, without need for anything else.

http://xdaforums.com/nexus-6p/help/bluetooth-hid-profile-update-t3281253

Thank you

and here is a PPA for bluez with sixaxis support (for linux):

https://launchpad.net/~nadia-xy/+archive/ubuntu/ppa

and here is an HID file for sony controllers:

http://lxr.free-electrons.com/source/drivers/hid/hid-sony.c

Source:

At the time of writing, mainstream Linux distributions do not explicitly support the SIXAXIS in wireless mode. Hence, the following customizations are required.

linux-2.6.21 or later . Earlier kernels do not support Bluetooth HID devices in "Report Protocol" mode.

patch-hidd-3.9-pabr3 or patch-hidd-3.19-pabr3 . This patch causes the Linux Bluetooth HIDP daemon (hidd) to send a special command to the SIXAXIS when it connects. Sony already published a similar patch for enabling reporting in USB mode.

sixpair.c. (Only required if the SIXAXIS is to be used with a non-PS3 Bluetooth master.) The SIXAXIS apparently does not support the standard Bluetooth pairing procedure; instead, pairing is done over USB, which is arguably simpler and more secure. This command-line utility searches USB buses for SIXAXIS controllers and tells them to connect to a new Bluetooth master.

Alternatively, it might be possible to support the Bluetooth HID "Report Protocol" on older kernels by using bthid instead of hidd, with a similar patch.

Besides, the new "input service" (bluetoothd-service-input), which replaces hidd in recent versions of bluez-utils, should support the SIXAXIS without any patch. However, since it does not accept connections from unknown Bluetooth devices, authorizations must be set-up by another utility, such as a udev plugin, as suggested in this discussion. - sixaxis and BlueZ

Note. Bluetooth experts use the word "controller" to refer to the Bluetooth network adapter inside the host or the PS3, whereas everybody else thinks "game controller" (a.k.a. joystick). This sometimes causes confusion.
[Nexus 6P Original Android Development] jgcaap:
Very big thanks man. :) very grateful. I'll do my best to make you all happy here. Remember that together we can make a great rom for our device. Thanks!!
[Nexus 6P Original Android Development] jgcaap:
Test build to see if Bluetooth improves on test folder available soon
[Nexus 6P Original Android Development] jgcaap:
5min
[Nexus 6P Original Android Development] ripv2:
Is the test build F2FS compatible? Any idea on the live lockscreen missing wallpaper?
[Nexus 6P Original Android Development] Magnetox:
bug volume rockers not changing song when screen is locked
[Nexus 6P Original Android Development] jgcaap:
Can you test Bluetooth the test build?
[Nexus 6P Original Android Development] Magnetox:
ill test tonight with multiple devices in an hour or two if you want to make some more changes
[Nexus 6P Original Android Development] jgcaap:
Is not that type of driver :p basically I'm trying to see if with Google sources works well.
[Nexus 6P Original Android Development] buddwm:
I'll download and test tonight in a few hours. Gonna see if I can get Project Fi working on this. If successful, I'll post instructions.
[Nexus 6P Original Android Development] jgcaap:
I've checked pure nexus. I'll making slowly some changes to work for angler. Should work fine.
[Nexus 6P Original Android Development] tibere86:
Bluetooth worked perfectly with my Toyota on the test build. Not sure if it's a placebo effect or not, but audio seemed clearer :D
[Nexus 6P Original Android Development] jgcaap:
Alright. If everyone confirms that then I know the solution. :)
[Nexus 6P Original Android Development] buddwm:
Still testing out Project Fi. Two things I've noticed:

1. Not sure if this is a bug, but CM File Manager cannot be switched into Root Access Mode even though SuperSU grants it permissions.

2. Normally when using Project Fi, in an AOSP rom, the carrier will always be listed as 'Project Fi', but for some reason carrier is listed to the actual carrier I am connected to (Sprint or T-Mobile depending on which one it switches to).

I did manage to get Wifi calling to work, though it crashed the first time I attempted, but seems ok now. Will report more later on.

EDIT: Another issue I see - Wifi at 5GHz is slow. I can get max maybe 300KB/s, and normally I should be able to get 1MB/s. Don't see this behavior on AOSP. Gonna try another CM variant to see if it's CM related.
[Nexus 6P Original Android Development] senthil.ck:
Yap root is broken in CM File Manager, I also noticed Google Camera Fails to load in the new build.
[Nexus 6P Original Android Development] akapu01:
Sorry for the delay... Just tested the test build but Bluetooth issue still present for me... Same as before... Whenever Bluetooth of WiFi scan happens on the device sound just shutters...
[Nexus 6P Original Android Development] ahoslc:
Turn off bluetooth and wifi scanning ;)
[Nexus 6P Original Android Development] buddwm:
Just tested with the latest DU test rom (another CM variant) and confirm that:

1. Carrier label is properly reported as 'Project Fi.'

2. Wifi at 5GHz is at the speed I expect.

3. DU doesn't use CM File Manager by default. I found a flashable version which seems to work fine.
[Nexus 6P Original Android Development] ahoslc:
DU is actually aosp based on our device.
[Nexus 6P Original Android Development] akapu01:
Why would I wanna do that...? Location is important to me...

And it's not just location... If I use WiFi for browsing/download... Bluetooth shutters for that too...

---------- Post added at 11:15 AM ---------- Previous post was at 11:13 AM ----------

DU is AOSP based not CM...
[Nexus 6P Original Android Development] ahoslc:
I still use location just fine WiFi and BT scanning constantly turned off makes no difference on my location.
[Nexus 6P Original Android Development] buddwm:
Ah ok - I seem to recall getting a DU rom on the HTC One M8 that was CM based. Ah well - then this would be an unfair comparison. Anyway, still stands that there is something funky going on with 5GHz network speeds - it ceilings at 300KB/s for me. I suppose the carrier labeling is specific to CM then. Maybe I'll test with RR to compare.

---------- Post added 13-02-2016 at 12:35 AM ---------- Previous post was 12-02-2016 at 11:44 PM ----------

Ok - tested both Temasek's and RR. I don't see the slow wifi issue on 5GHz on either of these, nor do I see the issue with the CM File Manager. Carrier label switches to Sprint or T-mobile on these as well (minor complaint - I can manually write in the carrier label).

It would seem every feature works with Project Fi, at least as far as I'm able to test tonight. Here are the steps I used - this should work for any CM based rom:

1. Install the CM based rom.

2. Install Google Dialer from here (from the Pure Nexus thread).

3. Install Gapps - make sure your Gapps has Project Fi and GCS. I use the Aroma version of OpenGapps.

Doing this gets me a working Project Fi activation during the setup wizard on first boot (make sure you don't turn off mobile data if prompted - else it will cause Project Fi activation to error out, but no biggie as you can go into the Project Fi app and do it manually later on). It also gives me working Wifi calling. You can test Wifi calling by putting your phone into airplane mode and then connecting to a Wifi network - then attempt to call with the dialer.

Anyway, to recap, the bugs I see on jgcaap's that I am not seeing on other CM roms:

1. Wifi on 5GHz is slower than expected, about a 300KB/s cap for me.

2. Can't enable root access on CM File Manager.

I'd like someone else to confirm the Wifi 5GHz issue if possible. Could have just been a fluke for me, but I installed this rom twice and saw it both times. I'll test more in the coming days, hope that helps!

EDIT: Some typos.
[Nexus 6P Original Android Development] jgcaap:
Well you won't loose anything. There is a marshmallow bug. I'll convert all sources to the same as pure nexus and see if works well for everyone then. Thanks
[Nexus 6P Original Android Development] kenbrownstone:
5ghz is just as fast as the other on mine.65mpbs
[Nexus 6P Original Android Development] buddwm:
Thanks for checking. I'll test again today.
[Nexus 6P Original Android Development] bill3508:
Do we have a new fixed recovery for f2fs, or is it still reverting system and cache to ext4?
[Nexus 6P Original Android Development] Magnetox:
afaik twrp 3.0.0 is working with f2fs on this rom just not for cache (as of yet)

also, I don't think bluetooth is working completely yet as some people reported issues on the test build others it worked fine.
[Nexus 6P Original Android Development] jgcaap:
I'll put sources of pure nexus for you guys to give a try. Just need some time to review which parts I need to change.
[Nexus 6P Original Android Development] xSilas43:
Cache cannot be f2fs because it is 94mb, f2fs requires a minimum size of 100mb, forcing f2fs on a 94mb cache would almost cut it in half because of the way f2fs works.
[Nexus 6P Original Android Development] buddwm:
Does this mean we'll never have a solution for f2fs on cache with the 6P? I don't see the benefit of f2fs if we're forced to stay with ext4.
[Nexus 6P Original Android Development] xSilas43:
Unless there is like a symlink to /cache that is located in another area, because we have a separate partition for cache. I'm sure there may be a work around in the future but ATM we will not be able format cache to f2fs.
[Nexus 6P Original Android Development] jgcaap:
Bingo. :p I need time to see how to do that.
[Nexus 6P Original Android Development] xSilas43:
my skills are limited but my theory would be to delete the /cache partition and then crate a larger folder in /system/cache and have /cache redirect there. or my second theory but probably unlikely doable would be resizing the cache partition.
[Nexus 6P Original Android Development] ahoslc:
Anyone else notice how bad snapcam is in low light compared to Google cam? Also is 1080p recording still broken on snap cam?
[Nexus 6P Original Android Development] bobbarker2:
I mean.. you can resize partitions parted very easily, but whether the device will accept it or not is entirely different. OEMs use custom partition tables so you'd need to find the parttable format for the 6P/5X which I'm sure is posted somwhere or obtainable but simply gathering the info off the device. But it's very easy to screw things up and need to know what type of checking the devices are doing and possibly modify that. That is to say, if it expects /cache partition to be located at blocks 0-900 ajnd you want to increase the size to lets say 1000 blocks, you'd need to find where it looks for partition structure and either alter the expectations of the code to look for cache at block 0-1000 or specify a different partition table so it knows to look for cache partition at your new block locations.

I have no clue whether this is feasiable, I'm speaking just out of general knowledge, but I do know people have successfully changed partition sizes in the past. So in theory, why wouldnt it be possible to do now on the 6P/5X? A quick google produced this: https://gist.github.com/zhuowei/79b6fbcd9ba9f1726163
[Nexus 6P Original Android Development] buddwm:
I tested wifi again and not seeing the issue this time. Maybe there was an issue with my provider at the time of initial testing. So disregard. Only obvious bug that I've noticed is the CM File Manager not allowing root.
[Nexus 6P Original Android Development] xSilas43:
Looks like cache in located right in the middle of the blocks so based on my knowledge it would likely be safer and easier to try placing it inside the system partition or at another location than simply resizing, but I could be wrong.
[Nexus 6P Original Android Development] jgcaap:
Try changing the configs first you have alot of customization options. I'll try see if cm changed anything related to quality.
[Nexus 6P Original Android Development] jgcaap:
https://github.com/jgcaaprom/android_packages_apps_Snap/commits/cm-13.0

From what I see they didn't change anything that affects quality. Please try explore a bit the option. Turn on de noise, change the contrast. Etc.
[Nexus 6P Original Android Development] ahoslc:
All I did was a test same shot snap had a ton of noise.
[Nexus 6P Original Android Development] jgcaap:
With denoise on?
[Nexus 6P Original Android Development] ahoslc:
We getting a new build today?
[Nexus 6P Original Android Development] xSilas43:
if you build one today sure ;) ETAs are simply rude.
[Nexus 6P Original Android Development] bill3508:
Bluetooth is broken on the current build correct?
[Nexus 6P Original Android Development] anmar21:
Hi [MENTION=2040569]jgcaap[/MENTION],

Loved your Rom on my OPO. I was wondering if you plan to work on AOSP roms as well.

Thanks for your work!
[Nexus 6P Original Android Development] jgcaap:
Hello guys. Sorry delay on builds but have been putting efforts to put lz4 working. There are some ingredients missing which I'll discover later. I'll make a build today with CM sources. This week you'll have a stable Bluetooth. Just a bit tired with the investment I put on bacon this weekend.
[Nexus 6P Original Android Development] jgcaap:
Will be exodus maintainer which is aosp based :)
[Nexus 6P Original Android Development] buddwm:
Is there any way to bake in a lock homescreen option - that is, an option that will "freeze" the widgets on the screen and prevent moving/resizing while using the phone? I've searched high and low for an option, either manually or via Xposed for Trebuchet, and can't find any. This feature used to exist in older CM releases.
[Nexus 6P Original Android Development] farfromovin:
Nova...
[Nexus 6P Original Android Development] buddwm:
Eh, that's not really a solution. I'd rather stick with Trebuchet.
[Nexus 6P Original Android Development] jgcaap:
Not broken. Just not perfect. Starting tomorow will be perfect. ;)
[Nexus 6P Original Android Development] ahoslc:
Why not nova?
[Nexus 6P Original Android Development] buddwm:
There's nothing wrong with Nova, but I could turn the question around and ask why not Trebuchet? It's besides the point. I guess the answer is no solution at this point for Trebuchet. Ah well...
[Nexus 6P Original Android Development] theROMinator:
Each time I reboot my phone, the first sound played by the speaker is distorted. Has anyone else experienced this? Seems to happen on all CM based ROMs.
[Nexus 6P Original Android Development] akapu01:
I have the same issue as well... also if my phone is in idle mode for few hours and i get a phone call the ring tone is distorted too...

I think this is also CM13 bug which is present in all CM13 based ROMs...
[Nexus 6P Original Android Development] mohammed510:
I'm using f2fs on my Nexus 5X right now. It's worth to mention that I get an Antutu benchmark score of 104k due to disk and i/o speed. So, ya, f2fs should make a difference.

I have both(6p and 5x) BTW.

On the 5x I can reformat data and cache to f2fs!

When I do the same on the 6p it gives me an error. Or it bootloops...
[Nexus 6P Original Android Development] mohammed510:
View attachment 3648207

This is from f2fs formated (data/cache) nexus 5x.

On the 6p I get: 90MB/s max writing speed!

[MENTION=225651]op[/MENTION] I have tested your ROM for the 5x and it works fine. Many thanks..
[Nexus 6P Original Android Development] jgcaap:
Question guys. With new build you are having heat issues and battery drain?
[Nexus 6P Original Android Development] tibere86:
I'm having no issues with your 2/15 build + AK kernel :good:

---------- Post added at 09:19 AM ---------- Previous post was at 09:11 AM ----------

We cannot format cache to F2FS yet on the Nexus 6P due to the /cache being <100MB. I'm sure talented developers will figure it out :p
[Nexus 6P Original Android Development] jgcaap:
cm made a change on bacon, which i'm trying to track the bug...
[Nexus 6P Original Android Development] jgcaap:
Problem solved, was latest blobs of location. Reverted them. In 10 min a stable rom will be replaced. Should be more battery friendly. Inserted a setting for interactive to be more conservative. At night w after work will release the kernels.

New interactive settings need opinions. I believe is smooth, keep the the phone cool. and is also very fast.

Have fun guys.
[Nexus 6P Original Android Development] jgcaap:
Ups. I have to appologize. I've mentioned to post this on bacon thread. This one will be available one with purenexus stuff and mixed with CM problably tonight. Sorry about it. Hehehe
[Nexus 6P Original Android Development] jgcaap:
Today I'll be putting efforts to put the rom to work. Will need testers.
[Nexus 6P Original Android Development] akapu01:
I am ready to go...!
[Nexus 6P Original Android Development] mohammed510:
Me too. For both(bullhead and angler)
[Nexus 6P Original Android Development] jgcaap:
you have bull head? Could you test if my rom works well there and if there is any bugs? I opened a thread but no one read...

I'm still checking the best set.

Again this is inofensive as we'll be using stable parts of purenexus.
[Nexus 6P Original Android Development] drshorty:
Quick question about "UPDATE SCRIPT" when I install the ROM I format system to f2fs but the script say "EXT4" I think that is why it change it back from "f2fs to ext4"
[Nexus 6P Original Android Development] jgcaap:
System is not supported for now. Only data.

Ext4 sequential read is way faster then F2FS . You do not write on System partition only when you flash :)
[Nexus 6P Original Android Development] jgcaap:
building.

Basically what i did was. Slightly modified CM device tree while using Blobs and kernel of nexus.

So i'll need to know if NFC and camera works.

Is building. :)
[Nexus 6P Original Android Development] buddwm:
I'll test tonight on mine. I saw an issue in CM where if I make a call in Skype, after about 5 min on the call, the person on the other end can no longer hear me. Even if I mute/unmute the mic, it doesn't resolve it. Only recourse is to re-call, but always around the 5 min mark it'll happen again. Doesn't happen in AOSP. Curious to see if it's fixed on this rom.
[Nexus 6P Original Android Development] jgcaap:
I've just got a build error. This will take a bit of time to put it work.. .But i'll put it work :D
[Nexus 6P Original Android Development] jijishthomas:
Good work
[Nexus 6P Original Android Development] xSilas43:
Thinks ROM looks interesting I might have to give the new build a flash (:
[Nexus 6P Original Android Development] jgcaap:
I'll continue this tomorow guys have to do a pause today :) ok?

Will release with CM sources today.
[Nexus 6P Original Android Development] xSilas43:
Thanks a lot! Going to give this a shot now.
[Nexus 6P Original Android Development] jgcaap:
It's online.

Thetr should only be issue with Bluetooth.
[Nexus 6P Original Android Development] redbullman:
Is the test 17 Feb build the same as the 17 build in the main folder?
[Nexus 6P Original Android Development] jgcaap:
Added FAQ to helpout after many people calling me unorganized politely on bacon ehehehehe :

http://xdaforums.com/showpost.php?p=65127153&postcount=3

Tomorow i'll continue puting purenexus sources working!
[Nexus 6P Original Android Development] jgcaap:
yes was my mistake on the script as i was building with purenexus stuff but after came errors and I've decided to update. :)
[Nexus 6P Original Android Development] xSilas43:
Running the new build so far so good, only bug I've noticed is the distorted first sound upon boot, but had that with every cm ROM. On F2FS very fast and smooth so far :good:
[Nexus 6P Original Android Development] jgcaap:
Will do my best to put purenexus sources working well. I want you guys to have stable stuff. Sorry for beeing slow but I've done some studying on bacon as both devices would benefit I'll do soon here also. :)
[Nexus 6P Original Android Development] xSilas43:
No rush, so far the build is rock solid and very smooth with AK kernel.
[Nexus 6P Original Android Development] mohammed510:
It works very well. I haven't noticed any bugs so far.
[Nexus 6P Original Android Development] jgcaap:
On bullhead? Can I open a thread there then? :) test everything if possible. Big thanks!
[Nexus 6P Original Android Development] xSilas43:
One minor issue I found so far, i believe someone stated earlier, when I install an app I find my screen hangs and lags quite a bit, happens when uninstalling an app too.

EDIT: I am running EAS kernel so im going to try using a normal one and see if that solves the issue.

Edit2: Normal kernel, same issue.
[Nexus 6P Original Android Development] mohammed510:
Absolutely.. Go ahead. And thank you!..

I will also test any new builds.

Edit: stock cm kernel doesn't support f2fs AFAIK. That's why it didn't boot unless i flash jolla kernel, which does support f2fs.
[Nexus 6P Original Android Development] jgcaap:
On bullhead Also? I need to add that. :p
[Nexus 6P Original Android Development] xSilas43:
If you'd like, here's an incredible kernel that aligns with similar values of yours, and supports f2fs, it is just lacking the fstab for f2fs, which can be attained from for example AK kernel.

Here's the link https://github.com/DespairFactor/angler

P.s. I just wanted to thank you and [MENTION=3814731]katinatez[/MENTION] for bringing f2fs to my angler, I don't run benchmarks but it seems noticeable snappier!!
[Nexus 6P Original Android Development] jgcaap:
I provide custom fstab for angler.

I'll build also one for the other device.

Today had a very full day with University. But I am going to bring a new toolchain which is very improved. Should provide nice performance. :)
[Nexus 6P Original Android Development] marioemp2k7:
I second that. This is very snappy and composed. It's the first time I see the CAF task manager in action. Also, the first time I see a rom with all 3 animations set on 0.92x (care to comment on this?). I'm on F2FS (data&cache)+Phasma kernel+DarkSpice R5.

As for F2FS, if you already have a kernel with it updated, you can use the fstab.bullhead from the Jolla kernel.

Thank you and I'm hoping to see you on the bullhead forums soon!

Edit: [MENTION=4475938]mohammed510[/MENTION] : Does the camera work for you? I get the "Can't connect to the camera" error. Maybe the kernel needs something extra in order to play nice with the Snapdragon camera.
[Nexus 6P Original Android Development] mohammed510:
Yes it does.
[Nexus 6P Original Android Development] ahoslc:
I did notice 1080P video record on cam is broken
[Nexus 6P Original Android Development] jgcaap:
http://xdaforums.com/nexus-5x/devel...-cm-13-0-jgcaaps-builds-t3318323#post65409107

Opened. Will build soon.

------

Angler users i wasnt able yet to build with purenexus resources I didn't had time today because of classes and exodus. Will try at night. Ok? :) I want to find the best solution so that you guys are happy.
[Nexus 6P Original Android Development] jgcaap:
if possible, after you test, leave feedback on that thread. I'll add F2FS later also. Thanks :D
[Nexus 6P Original Android Development] xSilas43:
IMHO the ubermallow sources would be a better source than purenexus I have tries both and found ubermallow to be much more stable, faster, and net me more battery life. https://github.com/UBERMALLOW

camera worked for me with kylo kernel but the app seems a little glitch on tablet dpi
[Nexus 6P Original Android Development] jgcaap:
I'll check. That dev is very good.