[N910C/H][DEV] AOSP sources

[RaymanFX]

*omg, thread updating needed*

Hey guys, as some of you might know, I was donated a Galaxy Note 4 (N910C) and am now working on AOSP for it.
The sources required to build a ROM are hosted at GitHub currently:

device: https://github.com/teameos/device_samsung_treltexx/
kernel: https://github.com/raymanfx/kernel_samsung_trelte/
vendor: https://github.com/raymanfx/vendor_samsung_treltexx/

If you want to give this a shot, you should be familiar with git and repo and be able to sync the TeamEos source yourself.

If anybody feels brave enough, give it a try yourself, all the required bits are posted above

TODO/BROKEN:

• Bluetooth headset calls (RX works, TX is broken)
• Open source AVC (H.264) Encoder is broken (Videos recorded in portrait are rotated by 90° counter clockwise, and there's artifacts all over the place)

Everything else should be pretty much working.

 

[thiagoribeirorj]

hopefully watching all your work. congratulations.

 

[ddaharu]

hey! any progress on this? I'm really excited!

Sent from my SM-N910C using XDA Free mobile app

 

[invisiblesushi]

+1

 

[calj17]

Congratulations

 

[RaymanFX]

First success:

The phone is booting and the adb server is starting.
I'm still missing some sensor blobs from stock which causes the sensor layer not to start and thus prevent various other init tasks (such as display, EGL) to crash.
I'm going to work on getting at least display up this weekend.
No promises though.

 

[thiagoribeirorj]

This is great news. Thanks for this hard work. Thank you for making our donation future experience CM12.

 

[cooldoc007]

someone was trying to port CM11 to galaxy alpha.. i guess its a similar kernel..
http://forum.xda-developers.com/note-4/development/exynos-543x-android-development-t2949478
dats d link.. jus posting, if it helps u in anyways..

 

[betoberno]

Good luck!

 

[SUNUN]

Superb!!!

 

[Ausboy 2011]

Awesome work looking forward to seeing it on my N910U... hopefully

 

[Danilo Pantelić]

Great :good:

 

[andrew.mackew]

Awesome!

 

[RaymanFX]

More progress today:

The device partially boots now, boot animation shows but that's where it loops.
Sensors are fully working and storage handling (internal storage, external sdcard and usbdisk) have been fixed.
I'm still missing some camera blobs which I believe keep the device from booting up (because it crashes other init services).
I'll look into that tomorrow probably.
All the latest fixes have been pushed to my github repos, so if anyone in here feels like experimenting a bit, let me know how it goes

 

[thiagoribeirorj]

More progress today:

The device partially boots now, boot animation shows but that's where it loops.
Sensors are fully working and storage handling (internal storage, external sdcard and usbdisk) have been fixed.
I'm still missing some camera blobs which I believe keep the device from booting up (because it crashes other init services).
I'll look into that tomorrow probably.
All the latest fixes have been pushed to my github repos, so if anyone in here feels like experimenting a bit, let me know how it goes

These words cause many joys.

 

[MrAlez]

@RaymanFX , great work, update the first post with every progres, and for the other guys this a dev thread, dont spam with greets otherwise im sure a mod is gonna close the thread, keep it dev related or someone can open a thread in the general options for this project

 

[Chaffa]

Go go go

 

[thiagoribeirorj]

Progress?

 

[sephkateno]

+1

 

[RaymanFX]

Well, as stated on the first post, it'd probably make more sense to watch my github for progress instead of asking in this thread.. Just saying.

Big progress has been made in terms of audio, as I finally got around to configuring proper mixer paths for audio devices here: https://github.com/RaymanFX/device_samsung_trelte/commit/c5954750b5c13ce9bf27992f145a18a837099e12.
I had to do lots of research because there is little to no documentation on these mixer_paths.xml configs, so I ended up creating it from scratch based on Samsung's UCM config.
The device still doesn't boot further than the bootanimation, but I still have some interesting lines in the logs to solve, for example it still reports invalid input/output devices in audioflinger, which clearly is an issue.
At least the issues preventing us from booting are no actual display issues, but init services crashing.
Also, it looks like the RIL is starting up after adding Samsung's cbd daemon to early init execution (ramdisk), but I don't expect telephony/mobile data to work just yet.