yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] :
New kernel sources and new blobs

I've worked the last two nights on the L sorces and blobs.

I van't get the new kernel to boot. The device get stuck on Samsung logo. I can't get logs at that time, cause abdroid havn't even start to boot.

I have pushed the new sammy kernel source code in my kernel git as branch BOCC. I have tested rebasing our current soirce on that, but it won't boot. So I started from scratch and made only the needed chanhes to build kernel inline: branch 12-work. But that also won't boot.

To build cm-12 with new kernel sources you also need to patch hardware/samsung_slsi/exynos:

From b1bb19a9e5cb178d57731657e38091732b73822b Mon Sep 17 00:00:00 2001
From: nvertigo <nvertigo67@gmail.com>
Date: Mon, 6 Apr 2015 08:40:48 +0200
Subject: [PATCH] includes: add videodev2_exynos_media_ext.h.

Change-Id: Ib92ee5fd0fa40f0c0350f397f3709d4c12ecee53
---
include/exynos_v4l2.h | 1 +
1 file changed, 1 insertion(+)

diff --git a/include/exynos_v4l2.h b/include/exynos_v4l2.h
index ed26397..ba86108 100644
--- a/include/exynos_v4l2.h
+++ b/include/exynos_v4l2.h
@@ -43,6 +43,7 @@ extern "C" {
#include <stdbool.h>
#include <linux/videodev2.h> /* vendor specific videodev2.h */
#include <linux/videodev2_exynos_media.h>
+#include <linux/videodev2_exynos_media_ext.h>

/*! \ingroup exynos_v4l2 */
int exynos_v4l2_open(const char *filename, int oflag, ...);

You can use "git am" to apply this.

Withoit this patch cm12 refuses to build against the L sources.

Lollipop blobs are in my vendor git, branch 12-work.

What I have not tested so far: build kernel stand alone and flash i over the not booting rom. Flash the new bootloader from lollipop sammy rom, and see if that will boot. I've also not tested if a permissive build will solve the problem.

Cause I really need to sleep again, I won't do anything the next days. It would be really nice if somone could test the above and report back.
[Galaxy Tab S Android Development] schrodinger56:
I'm experiencing similar issues with build 12-20150403 in that when the Tab S has been turned off for a few minutes then there is a noticeable lag between pressing the power button or the Home button to activate the screen. I'll try reflashing 20150331 to see if the lag persists.
[Galaxy Tab S Android Development] dawmail333:
I experience the same thing.

Also, camera app crashes on opening on my device.
[Galaxy Tab S Android Development] schrodinger56:
Just tried re-flashing build 0331 but despite no lag when the Power button is pressed the Camera and Calendar crash!!! I'll go back further and try build 0319 to see if we can get everything to work.

Update:- Just flashed the 0319 build and this one seems to work ok. No lag when Power button is pressed and Camera and Calendar both work.
[Galaxy Tab S Android Development] lionheartk:
Todays build is up!

cm-12-20150407-UNOFFICIAL-lionheartk-chagallwifi.zip 238.3 MB

cm-12-20150407-UNOFFICIAL-lionheartk-chagallwifi.zip.md5sum 142 B

All commits from CM12 and Nvertigo's "current-12.0" branch are in.

For those experiencing the miscellaneous problems described above, such as camera crash, etc etc, try and do a Very clean flash as described here.

As i said before, I dirty flash all mine and Nvertigo's builds one on top of another, and It's running fine here.

Enjoy!
[Galaxy Tab S Android Development] schrodinger56:
Can I ask as a novice to this flashing business what does the cm-12-20150407-UNOFFICIAL-lionheartk-chagallwifi.zip.md5sum 142B do?
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
It's to check if the download is good.

-DUHA
[Galaxy Tab S Android Development] schrodinger56:
How do you carry out the check?

Thanks.

---------- Post added at 07:19 PM ---------- Previous post was at 07:01 PM ----------

Still having issues with camera & Calendar with 0407 :(
[Galaxy Tab S Android Development] lionheartk:
http://lifehacker.com/247262/how-to-use-md5-sums-to-verify-downloaded-files

Did you do a very clean flash?
[Galaxy Tab S Android Development] Bushcrafter:
Thanks guys for 0407! Seems everything is working fine.:D
[Galaxy Tab S Android Development] Levistras:
Happy to donate to whoever gets CM12 working on the 805's first.
[Galaxy Tab S Android Development] :
Please read the thread - I have answered this at least three times. Last time only a few days ago.
[Galaxy Tab S Android Development] :
On camera and Calendar issue:

Though the last builds were working for some people bit crashing for others, I would suggest to examine the installations. I.e. I remember Calendar crashing, when using themes. So seemingly unrelated apps and/or extensions may or may not have an impact on the rom.

Please refer to #3. Also after clean flashing only install the recommended gapps (and - if needed - SuperSU; for init.d and Titatnium SuperSU is no longer needed!).

If the difference between working and crashing camera/calendar is not the installation itself, one of the remaining possibilities is a difgetence in the devices itself - which would be difficult and time intensive to debug, and I won't have the time for that till November.

[MENTION=1409248]lionheartk[/MENTION]: my friend, thanx for your builds! Please don't tell the users, if a dirty flash works for you or not: I know that that only means, that it works for you. But users i.e with themes and exposed, or other extensions and root-apps installed, won't realize, that changes in frameworks/base from cm can break a dirty flash with all kinds of side effects.

[MENTION=535343]all[/MENTION]: before reporting issues ALWAYS do a clean flash with only recommended gapps. Refer to #3 before posting. Thank you.
[Galaxy Tab S Android Development] schrodinger56:
Can I just ask as a novice what do you mean by "only install the recommended gapps"? I installed the pa pico gapps as per Post#1 and was getting camera & Calendar crashes.
[Galaxy Tab S Android Development] dawmail333:
Wiped absolutely everything as per the clean install instructions, flashed the new build, the camera app still crashes. Kernel version is "3.4.106-nvertigo-g211c746", build date is Apr 7.

Any information worth providing?

EDIT: I can't bring the camera up in any other app either. Could it be possible it's at a level the ROM itself doesn't exactly cover? Could an inappropriate version of TWRP cause issues?
[Galaxy Tab S Android Development] lionheartk:
Did you do the very clean install and NOTHING else, and tried the camera? Make sure you dont restore your apps or backups when setting up your tablet. Try the camera without installing anything except whats on the rom.

If that fails, then yes its the rom. But I don't think it will happen since others don't have this issue?
[Galaxy Tab S Android Development] dawmail333:
So, this is what I've done now:

Formatted my SD card (in the device)

Put on cm-12-20150407-UNOFFICIAL-lionheartk-chagallwifi.zip

Booted in TWRP v2.8.6.0 (latest I could find)

Ran the built in TWRP wipe across everything except the MicroSD card (advanced wipe)

Ran a standard wipe on top of that

Flashed cm-12-20150407-UNOFFICIAL-lionheartk-chagallwifi.zip

Wiped cache/dalvik again when prompted

Rebooted

Ran through the minimal install process (did not connect to WiFi etc)

Camera app immediately crashes upon trying to open it

I will add one final thing - I didn't test my camera before flashing CM on, so there's a chance it was always faulty. I will test that tomorrow night to be certain.

Tell me if logcat or something similar will help, I just don't understand how to use it on any app that I haven't tinkered on myself.

EDIT:

Decided I didn't need to sleep (thankfully, because the Samsung flash had me optimizing 194 apps on a fresh install!). I just flashed the Lollipop image from this thread: http://xdaforums.com/galaxy-tab-s/general/samsung-lollipop-range-tab-s-t3021612 (the Canadian version, IIRC), and I can confirm the camera works fine. This did basically overwrite everything though, including recovery, so all I can say with certainty is that something in my previous stack was causing issues.

So, tomorrow, I will reinstall TWRP, this CM build, and I'll hold off on flashing GApps etc. til later. I also just found the logcat instructions, will follow those if the camera continues to play up.
[Galaxy Tab S Android Development] :
Status update:

I've tested flashing the booloader (sboot.bin) from the BOCC France rom. No advance: stuck on samsung logo.

This time I manged to take a lookmat last_kmsg from the frozen boot (idiotically I forgot to copy it away):

First error was discarding service surfaceflinger, 'cause /system/bin/surfaceflinger wasn+t found... so I guess the system fs wasn't mounted. In twrp I was able to mount system, so I'm sure fs (ext4) and content (/system/bin/surfaceflinger was there) of system is ok. I also triple checked defconfig for EXT4 - everything seems to be ok.

I've run out of ideas. Perhaps [MENTION=3511708]UpInTheAir[/MENTION] for the kernel, or [MENTION=2346758]eousphoros[/MENTION] for the roms initing has an idea, where I can't see any light....
[Galaxy Tab S Android Development] eousphoros:
dumb question. Do you a mount statement for /system in your init scripts And is it pointing to the correct /dev path?
[Galaxy Tab S Android Development] eousphoros:
If you want to try a complete hack

download cf autoroot for the device

extract the recovery.img and the initram.cpio.gz file

modify the /sbin/recovery so it doesnt start cfautoroot but insteads starts up adb

add in a /adb_keys file just in cause you need to authorize

replace zImage with your kernel

Flash the modified recovery.img and poke things with adb.
[Galaxy Tab S Android Development] :
Wow. Had to read that twice before I got the idea. Great, man. I will try that and report back - it will take a few days before I find the time. (And thanx for the adb_keys tip - before even trying, I'm sure this saved me hours of frustration!)
[Galaxy Tab S Android Development] dawmail333:
Reflashed TWRP, wiped everything (except SD), did minimal setup for your 20150407 build, same issue. I did some preliminary checking in the logcat, found a permission denied error about opening a file (/data/cameraID.txt), created and chmod 0777'd the file, didn't fix the camera crash (although that error didn't reappear).

A wild guess, but perhaps the reason it works on your system because you did a dirty flash and something's missing in this version? That's the only reason I could see it working for you and not I, unless it is somehow related to something else in the stack.

Either way, I've attached logcat logs from both before and after creating that cameraID.txt file. Starting at line 2188 in the first logcat is:

--------- beginning of crash
E/AndroidRuntime( 4886): FATAL EXCEPTION: RequestThread-0
E/AndroidRuntime( 4886): Process: com.android.camera2, PID: 4886
E/AndroidRuntime( 4886): java.lang.RuntimeException: startPreview failed
E/AndroidRuntime( 4886):	at android.hardware.Camera.startPreview(Native Method)
E/AndroidRuntime( 4886):	at android.hardware.camera2.legacy.RequestThreadManager.startPreview(RequestThreadManager.java:275)
E/AndroidRuntime( 4886):	at android.hardware.camera2.legacy.RequestThreadManager.doPreviewCapture(RequestThreadManager.java:317)
E/AndroidRuntime( 4886):	at android.hardware.camera2.legacy.RequestThreadManager.access$1600(RequestThreadManager.java:61)
E/AndroidRuntime( 4886):	at android.hardware.camera2.legacy.RequestThreadManager$5.handleMessage(RequestThreadManager.java:756)
E/AndroidRuntime( 4886):	at android.os.Handler.dispatchMessage(Handler.java:98)
E/AndroidRuntime( 4886):	at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 4886):	at android.os.HandlerThread.run(HandlerThread.java:61)
W/ActivityManager( 2742): Force finishing activity com.android.camera2/com.android.camera.CameraLauncher
W/InputMethodManagerService( 2742): Focus gain on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@c19e7ab (uid=10024 pid=4886)
D/mali_winsys( 4886): new_window_surface returns 0x3000
W/InputMethodManagerService( 2742): Focus gain on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@c19e7ab (uid=10024 pid=4886)
I/Timeline( 4886): Timeline: Activity_idle id: android.os.BinderProxy@1eb91bb2 time:117517
I/WindowManager( 2742): Screenshot max retries 4 of Token{34327af2 ActivityRecord{204dfd u0 com.android.camera2/com.android.camera.CameraLauncher t5 f}} appWin=Window{20b148ee u0 com.android.camera2/com.android.camera.CameraLauncher} drawState=3
E/ActivityManager( 2742): Invalid thumbnail dimensions: 840x840
...

As before, anything else I can provide, let me know.
[Galaxy Tab S Android Development] lionheartk:
Im mashing my head here trying to understand why it Isn't working. Meanwhile, did you test the Google Camera app to see if it works?
[Galaxy Tab S Android Development] schrodinger56:
Sadly I've had to return to Stock because I bought the Samsung Bluetooth Keyboard for the Tab S and unfortunately only a few of the Functions Keys would work with CM12, so to get the full benefit of the keyboard I had to return to stock.

Hopefully in the future this will be resolved as I loved CM12 for the Tab S.
[Galaxy Tab S Android Development] :
If I've read all the complains and presume that ALL clean flashers have this issue since 0331-nvertigo build, but ALL cleanflashers does not have this issue with 0319, it's either an upstream change or the "don't overwrite init.rc"-commit. I will revert that commit. [MENTION=535343]all[/MENTION]: Please clean flash the friday build.

That's the problem with twice a weak builds and to many dirty flashers. If we would have only bi-weekly builds and fotrce a clean flash every time, we would better know, when this regression occured.
[Galaxy Tab S Android Development] FearlessSpiff:
Last time I checked there were only like 3 keys not working. Did that change? Fortunately I don't use the keyboard a lot. I got it for free with the Tab S.
[Galaxy Tab S Android Development] schrodinger56:
The keys that don't work properly for me are the Calendar and Browser keys, for some reason the Email app is opened instead!! However now I've gone back to 4.4.2 all keys work as they should. I'll email or ring Samsung to see if they intend fixing this anomaly.
[Galaxy Tab S Android Development] lionheartk:
Should we change to Wednesday only builds perhaps? And when there is a major change, an extra build.
[Galaxy Tab S Android Development] Bushcrafter:
Sounds good to me.:good: :D
[Galaxy Tab S Android Development] Zootopia:
Makes sense to me. [emoji106]
[Galaxy Tab S Android Development] dawmail333:
Here's a log file from when I try to open the built in camera, and then try to open Google Camera (once again, does not work). Just in case it helps you find the issue.

I'll try flashing the older build and then dirty flash this one, see how it goes.
[Galaxy Tab S Android Development] :
Let's see if the todays build fixes the "clean-flash-camera"-issue. (I have reverted the questionable commit.)

The root of the problem is a lack of time on my side: I made a set of guesses on when this problem occurs and that all cleann flashes since at least 0331 have this prob in my last post. I really hoped at least the users with this probs would confirm this.... So if I want to do solid development, I would have to clean flash all builds since 0319. At the same time I try to get the new kernel sourves and blobs running. I just do not have the time to spent 70 h a week an development, like I had in the winter season....

I have no solution or even a suggestion for this. I'm not really sure if publishing only once a week is a good idea.
[Galaxy Tab S Android Development] dawmail333:
Would it help if I found the first problematic version by clean flashing all between 20150319 until issue reproducible?
[Galaxy Tab S Android Development] :
Samsung surely won't fix somthing for cm12.
[Galaxy Tab S Android Development] :
Let's wait for today's build - perhaps I've guessed right... ;)

It would be great, if you clean flash todays build. And if the issue persists, then I would really like to come back to your offer, 'cause it would be a great help to see, when this was inzroduced upstream. Thanx for your help!
[Galaxy Tab S Android Development] lionheartk:
And here it is!

cm-12-20150410-UNOFFICIAL-lionheartk-chagallwifi.zip 238.3 MB

cm-12-20150410-UNOFFICIAL-lionheartk-chagallwifi.zip.md5sum 142 B

Hopefully will fix the issues. We maintain the twice a week builds then! Have fun!
[Galaxy Tab S Android Development] barth2:
dirty flashed and tried camera: OK

clean flashed and tried camera: OK :)

small regression: ~15 seconds black screen after samsung logo is back.
[Galaxy Tab S Android Development] :
Thanx for thentests and the feedback.

[MENTION=535343]all[/MENTION]: can someone confirm these three observation?

I did a build for myself earloer today, and can confirm cera working on clean flash, but my cm boot animation shows up after <1s after sammy logo... (on clean flash, I havn't checked onmdirty flash.
[Galaxy Tab S Android Development] My Public:
Dirty flashed over build from april 07. Boot animation appeared < 1s after sammy logo.
[Galaxy Tab S Android Development] Bushcrafter:
+1 :) Camera works too.
[Galaxy Tab S Android Development] d3xtr0:
What are the main bugs for latest release? Does mhl works?

Thanks for your great work devs.

Sent from my MI 4W
[Galaxy Tab S Android Development] barth2:
Sorry my bad. I adb sideload an old version instead of today's build (damn you, file name auto complete).

Everything ok on new build. No bootanimation delay. Camera works with clean flash. Continues working after restoring backed up /data. [emoji106]
[Galaxy Tab S Android Development] dawmail333:
Haven't found any issues. Thanks guys!
[Galaxy Tab S Android Development] d3xtr0:
Have you tried mhl? Thanks
[Galaxy Tab S Android Development] maxal:
No sorry I don't use it.
[Galaxy Tab S Android Development] d3xtr0:
Thanks. Could you please tell me which version of gapps did you used?

I feel a bit laggy in windows switching animations. Did you too? I've change the I/O to deadline and seems better.

Bluetooth mouse it's laggy. Any one experienced that?
[Galaxy Tab S Android Development] maxal:
Have a read of this thread http://xdaforums.com/android/software/gapps-consolidated-gapps-thread-t3064693
[Galaxy Tab S Android Development] Retiredfinally:
Dirty flashing was no good, youtube and Google play error but clean flashed and golden! Thanks for all the hard work NVertigo!!
[Galaxy Tab S Android Development] schrodinger56:
Camera and Calendar fixed but the Samsung Bluetooth keyboard for the Tab S 10.5 still not fully functioning w.r.t some Hotkeys so sadly despite loving this ROM had to go back to stock .:(
[Galaxy Tab S Android Development] :
I'm not sure, but I think I've said before: my priority is porting 5.1 and getting new kernel sources and blobs booting and running - fixing some hotkeys on bt keyboard is not on my list.
[Galaxy Tab S Android Development] :
Lollipop 5.1

Good news:

I've made the first cm-12.1 (5.1 based) build. It seems to run stable and as far as I can tell at the moment delibers no regressions.

I wil do a few mor checks and propably publish this tomorrow - if everything is ok.

Bad news:

I will not have the time to check on new kernelsources and blobs for the next 10 days. On the other hand: even wwoth KK kernel and blobs this rom is stable and nearly full functional.
[Galaxy Tab S Android Development] Zootopia:
No worries mate. [emoji106]

Thanks for keeping us updated... Definitely things are coming together and on the best track regarding 5.1... Thanks! [emoji2]
[Galaxy Tab S Android Development] schrodinger56:
It wasn't a request more of an aspiration. ;)
[Galaxy Tab S Android Development] tids2k:
[MENTION=3456089]nvertigo[/MENTION] could you help me find the sources for exynos 5420 on git ? I'm going to build a rom from your sources for SM-t805y
[Galaxy Tab S Android Development] lionheartk:
https://github.com/CyanogenMod/android_kernel_samsung_exynos5420 ?
[Galaxy Tab S Android Development] tids2k:
thanks for the the link.
[Galaxy Tab S Android Development] :
Official exynos5420 kernel sources for cm: github.com/cyanogenmod/android_kernel_samsung_exynos5420 (why not just google "github cyanogenmod exynos5420"?)

But I don't think they will work with 805y. Take a look at [MENTION=2346758]eousphoros[/MENTION] kernel source for 705.
[Galaxy Tab S Android Development] :
UPDATE: NVertigo/cm goes 5.1

Build 20150413

Updated from cm-12.0 to cm-12.1 - cm-12.1 is based on AOSP 5.1. Remeber to update your gapps package to 5.1. I recommend pa gapps pico: http://xdaforums.com/paranoid-android/general/5-1-x-5-0-x-4-4-x-pa-gapps-mirror-t3069879

ROM: http://162.220.240.98/ftp/nvertigo/cm-12.1-20150413-UNOFFICIAL-nvertigo-chagallwifi.zip

MD5: bdc8dc0937ac7416bad5314a45896719

Fpr all the home- and crossbuilders: reread #4. The patch contained in repackrom will throw an offset message - that does not matter. No time to adjust the patch.
[Galaxy Tab S Android Development] lionheartk:
Thanks nvertigo. WIll update all sources!

Next build will be the SEX build then!
[Galaxy Tab S Android Development] eousphoros:
Github cyanogenmod klimtwifi will work for you. Just copy the defconfig over after you clone
[Galaxy Tab S Android Development] My Public:
- install ROM: check

- install gapps pico: check

- install Super-SU: check

- install xposed framework (for 5.1): check

No problems at the moment! :)

Thanks [MENTION=4405529]nvertigo67[/MENTION] for the great work!
[Galaxy Tab S Android Development] Zootopia:
Much appreciated guys... Thanks!

There are a number of modules still not working in 5.1...

I'm eager to try, but greenify for i.e. is a big lost. Servicely seems to be a great alternative though, if not best...
[Galaxy Tab S Android Development] d3xtr0:
Awesome ! Any major bug?

Sent from my MI 4W
[Galaxy Tab S Android Development] My Public:
I use only 'Never sleep' (for a newsletter app) at the moment. Works fine.
[Galaxy Tab S Android Development] maxal:
I would like to add I have just done a clean install of 5.1 and all appears to be working just fine, thanks very much:good:
[Galaxy Tab S Android Development] barth2:
Clean flashed 5.1 build. Everything seems ok except for one bug: when turning off auto rotate, it always switches to landscape no matter what current orientation is. I've enabled all rotation modes (0,90,180,270). I prefer using portrait most of the time which is probably why I'm the first to catch this bug :)
[Galaxy Tab S Android Development] :
Thanx for reminding me: I have only tested a clean flash - and would recommend to do so.
[Galaxy Tab S Android Development] :
Never tried that. Was it ok on 12.0?

What happens if you only allow 90°?

EDIT: if you configure only 90° and/or 270° you get what you want.
[Galaxy Tab S Android Development] barth2:
Yes it was working on 12.0. Yes configure it to 90 and 270 is a workaround but then it's locked into portrait and to unlock you need to go into settings. I guess I'll leave it on auto rotate.

Btw I notice the stock browser as well as several other stock apps like camera and gallery are missing. Except possibly for the browser, it's easy to get the stock apps or equivalent from play store so it's no big deal. Just wondering whether this is deliberate or you forgot or CM changed their policy or something else.
[Galaxy Tab S Android Development] Hannibal226:
What gapps u flashes?

Some packages replace the apps with the gapp version. For example aokp browser with chrome or gallery with Foto.

CHEERS!
[Galaxy Tab S Android Development] sgarrand:
Did a dirty flash from 12.0 and everything works well, FYI. I did do a full backup just in case I needed to go back. Thanks for the great rom.
[Galaxy Tab S Android Development] lionheartk:
Compiled my own build and did a Very Clean flash. Everything working smoothly, thanks nvertigo!
[Galaxy Tab S Android Development] barth2:
PA pico. It only has play services and play store, I think.
[Galaxy Tab S Android Development] gyrex:
Just flashed the rom - really like it! Found an issue though.

When you add a new user and set it up, you can't change the user's name, it says 'the contact doesn't exist' when you click on their name. Also, you can't change keyboards, you're stuck on aosp keyboard.