[ROM][AOSP 7.0][T700/T705/T800/T805]

[shepliu]

Not really ; wait for the video ( and ril if Tx05 ) bugs to be corrected ; then it will be the same .

The rest are the new features from aosp 7 of course ( multiwindow, ...)

Any plan to update it to 7.1.1?

Sent from my SM-T805 using XDA-Developers mobile app

 

[amateurhack]

I am currently using Schischu's MM ROM as my daily driver for my T800 and am having no issues with it., in fact quite the opposite. Is it worth switching to this?

There are lots of little bugs. read the thread and proceed with caution. Only you know if its worth the risks and hassles. I'm using it as my daily, but it's not without compromises.

 

[Kholargol]

I am currently using Schischu's MM ROM as my daily driver for my T800 and am having no issues with it., in fact quite the opposite. Is it worth switching to this?

It's a same with a few bugs fixed (like rotation one) and hope for future updates. So I would say YES, it's worth switching..

 

[Orphee]

My build of TWRP supports raw partition backup for several partitions as well as normal backup. The same you would get using the DD command.
If you want a 1-1 backup you can use the system image backup option. More info on this can be found in the twrp thread.

Could you add data IMAGE partition to the list ?
Thanks

Edit : I had to install busybox on the TabS and Cygwin / NetCat package on the PC :
http://xdaforums.com/showthread.php?t=1744584

DD backup in progress

 

[malosasha]

Any plan to update it to 7.1.1?

Sent from my SM-T805 using XDA-Developers mobile app

Yeah sure , i m just waiting for official aosp support for the google reference tablet , pixel C. It should be pushed next month. so either in December or January i ll migrate to 7.1 . Would be cool to fix the RIL and HW Video dec/enc bugs in the meantime.

 

[M9x3mos]

Is there any way to keep the key lights from being on all the time? I have a t700 and they never seem to shut off. Also I don't get 5ghz Wi-Fi. How do I change the region?

 

[chibot75]

Is there any way to keep the key lights from being on all the time? I have a t700 and they never seem to shut off. Also I don't get 5ghz Wi-Fi. How do I change the region?

Settings - display - button backlight

 

[bieltv3]

AOSP 7.0

Hello guys,
I'm bieltv3 and I used to be an android developer a few years back, when porting Ice Cream Sandwich to a legacy device was tendency you can find my works at my threads!
Suddenly, I just had in my hands a Galaxy Tab S 8.4 T700 and, as a good XDA and Android developer, I hate the bad software expierence Samusng offers to their products. The thing is, I am an expierenced guy with Samsung Android development and I was looking forward to any development here... and I just found this!
I haven't installed yet the ROM as I have some questions for the developer or any user that can help. ln my expierence with Android development, bringing CyanogenMod / AOSP to a device with proprietary SoC is not the easiest in Android Development. That's why, here at XDA, we recommend supporting Qualcomm devices as they release the code for their SoC's. When I worked on CM, we made a working ROM for Broadcom chips using propietary pre-compiles libraries (.so) from stock devices with the same chipset. That's not a good workaround but it is better than not working HW drivers (= software rendering expierence). As a consequence, we had the green screen issue you guys are facing... so I'm wondering, do you compile from source the code for the EXYNOS SoC? Did Samsung ever release the code for this chip? I have curiosity as T700 was once supported by official CM team, when CM used to support Qualcomm based chips, such as the 4g model of this tablet. Can anyone explain to me how you guys managed to get HW (Video encoders and decoders) drivers work on this tablet? As far as I knew, Exynos chips were closed source, that's why I am impressed on the works here!

Thanks for reading this, and well... Like to see Android ROM development isn't dead yet! (Pixels are coming...)

 

[M9x3mos]

Settings - display - button backlight

Thanks. Didn't see that when poking around there before. Now I wonder if I can get adoptable storage working on this

 

[subaquatic]

Here's a possible fix if you lost mirroring. Edit the build.prop according to this post:

http://xdaforums.com/showpost.php?p=54516532&postcount=16

I rolled back to stock until the video issues and battery burn down are resolved, but the problem persisted. Adding the one line to the build.prop fixed it. Don't forget to chmod 644 after you write to the file. Nice to see dedicated work on this tablet.

Sent from my KIW-L24 using XDA-Developers mobile app

 

[malosasha]

Here's a possible fix if you lost mirroring. Edit the build.prop according to this post:

http://xdaforums.com/showpost.php?p=54516532&postcount=16

I rolled back to stock until the video issues and battery burn down are resolved, but the problem persisted. Adding the one line to the build.prop fixed it. Don't forget to chmod 644 after you write to the file. Nice to see dedicated work on this tablet.

Sent from my KIW-L24 using XDA-Developers mobile app

I just tested with a miracast wifi dongle (emtec mirror dongle) but it does'nt work. The issue is not related to hdcp i think but to openmax avc encoder that is broken.

 

[malosasha]

Hello guys,
I'm bieltv3 and I used to be an android developer a few years back, when porting Ice Cream Sandwich to a legacy device was tendency you can find my works at my threads!
Suddenly, I just had in my hands a Galaxy Tab S 8.4 T700 and, as a good XDA and Android developer, I hate the bad software expierence Samusng offers to their products. The thing is, I am an expierenced guy with Samsung Android development and I was looking forward to any development here... and I just found this!
I haven't installed yet the ROM as I have some questions for the developer or any user that can help. ln my expierence with Android development, bringing CyanogenMod / AOSP to a device with proprietary SoC is not the easiest in Android Development. That's why, here at XDA, we recommend supporting Qualcomm devices as they release the code for their SoC's. When I worked on CM, we made a working ROM for Broadcom chips using propietary pre-compiles libraries (.so) from stock devices with the same chipset. That's not a good workaround but it is better than not working HW drivers (= software rendering expierence). As a consequence, we had the green screen issue you guys are facing... so I'm wondering, do you compile from source the code for the EXYNOS SoC? Did Samsung ever release the code for this chip? I have curiosity as T700 was once supported by official CM team, when CM used to support Qualcomm based chips, such as the 4g model of this tablet. Can anyone explain to me how you guys managed to get HW (Video encoders and decoders) drivers work on this tablet? As far as I knew, Exynos chips were closed source, that's why I am impressed on the works here!

Thanks for reading this, and well... Like to see Android ROM development isn't dead yet! (Pixels are coming...)

The hardware based codec lib are closed source and taken from LL rom. Actually the omx layer is wonky and lead to multiple bugs
*Camera video encoding broken(mpeg4)
*Some youtube vids in h264 do not work (avc)
*Screen cast is broken (avc)

Ths lib are located here
*

Actually the libstagfrighthw has in fact not been updated either from the aosp 6.0 schiscu rom. So i was planning to update it ; use the hw codec blobs from MM and then adapt the new api changed between MM et Nougat. Was just busy since the last release and could not afford 10 mins on this project .

Glad if you can help Pm me if you need more details.

 

[rookie12]

Here's a possible fix if you lost mirroring. Edit the build.prop according to this post:

http://xdaforums.com/showpost.php?p=54516532&postcount=16

I rolled back to stock until the video issues and battery burn down are resolved, but the problem persisted. Adding the one line to the build.prop fixed it. Don't forget to chmod 644 after you write to the file. Nice to see dedicated work on this tablet.

Sent from my KIW-L24 using XDA-Developers mobile app

You are saying that You added one line in build prop and it fixed battery drain and heat issue if so where is this line?

Sent from my SM-T700 using XDA-Developers mobile app

 

[subaquatic]

You are saying that You added one line in build prop and it fixed battery drain and heat issue if so where is this line?

Sent from my SM-T700 using XDA-Developers mobile app

No, it fixed the mirroring issue, but according to @malosasha this fix may not work on this rom.

See post 171.

Sent from my SM-T700 using XDA-Developers mobile app

 

[malosasha]

No, it fixed the mirroring issue, but according to @malosasha this fix may not work on this rom.

See post 171.

Sent from my SM-T700 using XDA-Developers mobile app

I ll still keep the idea for when h264 encode will be fixed. Thanks for the tip, thats the exact kind of post that give me faith for the future of this rom

 

[bieltv3]

The hardware based codec lib are closed source and taken from LL rom. Actually the omx layer is wonky and lead to multiple bugs
*Camera video encoding broken(mpeg4)
*Some youtube vids in h264 do not work (avc)
*Screen cast is broken (avc)

Ths lib are located here
*

Actually the libstagfrighthw has in fact not been updated either from the aosp 6.0 schiscu rom. So i was planning to update it ; use the hw codec blobs from MM and then adapt the new api changed between MM et Nougat. Was just busy since the last release and could not afford 10 mins on this project .

Glad if you can help Pm me if you need more details.

Hi, thanks for the response. As I can see this was the standar way used also in CyanogenMod. As I can see, in official cm12.1 releases they also used prebuilt HW decoders libs as I can see HERE but it is also true that CM call's the MakeFiles of Exynof5420-common which does compile the Gralloc libraries. I've spoken with some friends developers involved in CM for the Exynos Devices and we talked about the origin of Exynos Sources. What I see HERE though is that exynos5420 has the order to build libstatgefrighthw from source, so the thing is to make compatible source libraries with prebuilt ones: this require some reverse engineer which is not easy at all. Hopefully, CM team will update its exynos hardware repo's and then we can use their work to adapt the new statgefright libraries for the prebuilt OMX ones. As always, building CM for a device is much more easy than pure AOSP, that's why I may get inside buidling an unofficial CM 14 Rom for it later this year. I am really happy that someone took the time to see which stock libraries were compatible with gralloc and some Open Source libraries that ODROID provided in their EXYNOS motherboards. Unfortunatly this didn't happen beyond KitKat. Android stories Anyway, I will try to keep me updated in github to see the progress made. Updating the stock libraries to MM could make some important changes... but this needed to be done when CM13 porting was going on... not on Nougat! We first should have a MM AOSP fully funcitonal ROM with the MM stock SAMSUNG libraries, then move on to Nougat... Anyway, this is an amazing work! As said, I do preefer CM ROM because, as I can see, you had to edit the native AOSP frameworks to adapt the exynos device tree, and that made your github grow... As CM supports other devices, we can use their framework and just modify the exynos device tree, klimtwifi device tree and kernel device tree, as well as update the blobls.
Keep up the good work and I'll stay tuned. Any questions here I will try to answer or elsewhere give some support. Remember this thread is to keep the topic on Development of the ROM, not spamming the thread with bugs report, nougat is still in Beta Stage, so expect this to be an ALPHA release.

 

[malosasha]

Hi, thanks for the response. As I can see this was the standar way used also in CyanogenMod. As I can see, in official cm12.1 releases they also used prebuilt HW decoders libs as I can see HERE but it is also true that CM call's the MakeFiles of Exynof5420-common which does compile the Gralloc libraries. I've spoken with some friends developers involved in CM for the Exynos Devices and we talked about the origin of Exynos Sources. What I see HERE though is that exynos5420 has the order to build libstatgefrighthw from source, so the thing is to make compatible source libraries with prebuilt ones: this require some reverse engineer which is not easy at all. Hopefully, CM team will update its exynos hardware repo's and then we can use their work to adapt the new statgefright libraries for the prebuilt OMX ones. As always, building CM for a device is much more easy than pure AOSP, that's why I may get inside buidling an unofficial CM 14 Rom for it later this year. I am really happy that someone took the time to see which stock libraries were compatible with gralloc and some Open Source libraries that ODROID provided in their EXYNOS motherboards. Unfortunatly this didn't happen beyond KitKat. Android stories Anyway, I will try to keep me updated in github to see the progress made. Updating the stock libraries to MM could make some important changes... but this needed to be done when CM13 porting was going on... not on Nougat! We first should have a MM AOSP fully funcitonal ROM with the MM stock SAMSUNG libraries, then move on to Nougat... Anyway, this is an amazing work! As said, I do preefer CM ROM because, as I can see, you had to edit the native AOSP frameworks to adapt the exynos device tree, and that made your github grow... As CM supports other devices, we can use their framework and just modify the exynos device tree, klimtwifi device tree and kernel device tree, as well as update the blobls.
Keep up the good work and I'll stay tuned. Any questions here I will try to answer or elsewhere give some support. Remember this thread is to keep the topic on Development of the ROM, not spamming the thread with bugs report, nougat is still in Beta Stage, so expect this to be an ALPHA release.

This is the same here ; only the hw decoder blobs are closed source ; the other layer are open source and in fact forked from CM
chekc the manifest here : https://github.com/alexmaloteaux/android_chagall_klimt/blob/nougat-release/default.xml
libstagefrighthw is built from here : https://github.com/alexmaloteaux/android_hardware_samsung_slsi_exynos
gralloc from here : https://github.com/alexmaloteaux/android_hardware_samsung_slsi_exynos5420
omx core lib from here : https://github.com/alexmaloteaux/android_hardware_samsung_slsi_openmax

All are the same as on the aosp 6.0 rom from Schischu, as i told you ; i plan to upgrade those to 14.0 cm then follow with the blobs and then look at the required adaptations. I already implemented shims mechanism from android X86 while upgrading gpsd blob from LL to MM if it will be required. (Not yet pushed)
Btw what is the history background between this repo hardware_samsung_slsi_exynos5420 and the insignal one ? : hardware_samsung_slsi_exynos5-insignal.
Do you have any idea ?

 

[C0derbear]

Is there any way to keep the key lights from being on all the time? I have a t700 and they never seem to shut off. Also I don't get 5ghz Wi-Fi. How do I change the region?

re:WiFi

I don't recall the precise path, but it's like this ...

Settings -> WiFi -> Advanced

And there's an option to set the region, once I did that the 5 ghz network at home started showing up on my T700.

Good luck.

 

[malosasha]

re:WiFi

I don't recall the precise path, but it's like this ...

Settings -> WiFi -> Advanced

And there's an option to set the region, once I did that the 5 ghz network at home started showing up on my T700.

Good luck.

It is Settings->Wifi->Settings->Wifi country code right ? I added it like this in the Tip&Tricks sections Don''t have 5ghz ap to test atm

 

[C0derbear]

Settings->Wifi->Settings->Wifi country code

Correct, thanks!