yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] spegelius:
Great, good to hear it's working well. The camera problem is an elusive one, i need to flash TW KK once more to get detailed logcat's to see what commands are sent to camera when doing different things, like when toggling HDR, toggling flash and taking picture. I do have some old logcats, but i think they are in one or two files which make it hard to deduct what lines are caused by which action etc. I need to clear some time for it someday...

The CM dev's i've been in contact respond kinds slow, last time i was asking kinda same thing, what is needed to get things rolling regards official status. Currently there are two commits on Gerrit which are needed and the device tree needs to added to CM github. Also i asked about the camera problems, but so far no answer.

---------- Post added at 09:49 AM ---------- Previous post was at 09:44 AM ----------

Oh and i got Jenkins set up on my home servers, i set it up to make builds from SlimKat and AOSP during night, i'll add CM11 today. I need to add build publishing to gdrive. I haven't figured out how to check if there's any changes, i.e. is build even needed. Also somekind of changenote would be nice, maybe get that from CM gerrit somehow... but at least the builds are going to be done.
[Galaxy S 4 Active Original Android Development] ZeroZorro:
Same for me...3 days running as 2nd ROM and using it more as Primary ;)

Fast, smooth, no bugs other than stated above...

Some testing to do cause some earlier ROMs seems to have trouble with Runtastic/Endomondo etc

It's GPS related I guess.

Overall a keeper for me!

Thanks [MENTION=3876105]spegelius[/MENTION] and [MENTION=4630187]allram[/MENTION] for your work on the S4A ROMs!
[Galaxy S 4 Active Original Android Development] olarf:
Here just a short impression about battery time in daily use (3,2h Screentime, WiFi always on BT sometime, phonecalls, a bit gaming...

38h and 34% left is not that bad I think :)

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] O-T:
Thanks [MENTION=3876105]spegelius[/MENTION] 2907 was the bate to lure me back from the dark ages of stock, bloat, and barriers. :p

First hours just some tweaking and restore appdata (Helium).

Balanced power profile, snappy UI, APN and provider info OK, have hopes for BT (tomorrow), camera is less jerky :D

:thumbup: Congrats! This is Sisu from the land of a thousand lakes.
[Galaxy S 4 Active Original Android Development] ir.malik:
Thanks for the link. BTW whats NE5 and NE5 dual boot?
[Galaxy S 4 Active Original Android Development] spegelius:
Test builds with proprietary libs from Samsung kk NE5 rom. All features aren't working as i recall... like phone and gps
[Galaxy S 4 Active Original Android Development] SamuTnT:
Hi guys, sadly i have to say that BT is still bugged for me on 2907, i've tested a BT GPS antenna and it clearly loose connection for a while, then it's back, then loose connection again and so on, i've tested with different GPS softwares and the problem is the same..i can see the map moving following my position until it loose connection and stay freezed for some minutes, then it refresh to exact position and stay connected for a while until loose connection and "freezes" again..

..anyone else can test this?
[Galaxy S 4 Active Original Android Development] O-T:
BT connect OK as it has done earlier. Somewhat less disconnect, only one time when GPS voice directing in car audio start. Connected ~20sec later and stayed. Call out and music playing didn't drop out.

<guess on> Suspect someone missed some coding when Bluetooth MAP was introduced in CM11/AOSP 444... </guess off>

24 hours and still 50% battery :D

Changed theme to MIOS seeing no error.

Trying my best to hunt down other flaws - so far none ;)
[Galaxy S 4 Active Original Android Development] olarf:
I got also one BT disconnect today with my car system while starting a call. It reconnect then by itself and stay. All days before it works perfect in 2 different cars. So the BT itself seems to need also a bit improvement while mostly it works fine.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
It seems Jenkins has finally got few builds made, there's 20140806 and 20140807 available on gdrive. Do note that there was some problems with repo sync earlier as jflte got new gps sources, which might break something, dunno if the gps stuff need newer gps blobs or something, haven't looked at the code. Anyways, i haven't tested the builds so have your backups ready.
[Galaxy S 4 Active Original Android Development] olarf:
OK, will give it a try and report then.

Edit: I try 07.08 AS dort flash an it boot up to the lock screen in wrong DPI (everything is micro small) and the it reboot and so on. So dirt flash don't work. Should I try a clean flash or did someone tryed it?

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] O-T:
Clean cache +dalvik cache. 0806 applied dirty over 0729. No surprises =Daily driver :D

Format dalvik cache passes suspicious quick in cwm6050. It was also this way in 6047, but that should be reported in a different thread.
[Galaxy S 4 Active Original Android Development] olarf:
I will try now, cleaned also cache and dalvik for 0807

Edit: I confirm that 0806 work, 0807 not as described 2 post above. GPS work fine in 0806.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
There was some commits to display-caf yesterday which broke my AOSP build and i haven't looked at them, but i suspect they are the culprit. I'll check this during the weekend.

And it seems last night CM11 build has failed.

---------- Post added at 08:36 AM ---------- Previous post was at 07:40 AM ----------

Also there's some major changes in jf kernel, seems i need to redo all my jactive unification work since CM has apparently updated whole kernel to newer version or something... sigh. Well no new builds for a while then.
[Galaxy S 4 Active Original Android Development] ZeroZorro:
[MENTION=4481095]olarf[/MENTION] which settings do you use with your camera with 0806 cause no matter how my camera freezes when taking a picture. Changing settings makes the app break and i have to reboot to access the camera again. (Using google-camera).
[Galaxy S 4 Active Original Android Development] O-T:
I'm using gapps customized by [MENTION=2478576]Tsjoklat[/MENTION] http://xdaforums.com/showthread.php?p=50632468

He repair a lot of flaws compared to goo.im/gapps. In addition this doesn't replace Launcher, Calendar or Camera.

Mini version is OK - the rest can be downloaded from GPlay.

Camera doesn't freak out when using this.

Edit1. Or pick from the shelf of PA gapps

http://xdaforums.com/showthread.php?p=44417509

They are nice and explain what apps are replaced for each gapps type pack.

Sent from my GT-I9295
[Galaxy S 4 Active Original Android Development] olarf:
In 0806 I had same trouble today, every change in settings brake it even I use the pa gapps micro version. In 29.07 it was much more stable with same gaps. So some reboots today while a Enter Shikari show :)

I will do a more serious test later today.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] snadge:
So I've kinda been away for a while and probably picked a bad time to install recovery, backup my device and compile from current source. :silly:

Anyway, after borrowing some stuff from jftle's boardconfig relating to audio and some similar stuff. It appears there has been quite a few updates that need to be caught up on. My first boot is crashing and complaining that it is missing "/system/lib/libnetcmdiface.so", which from quickly Googling appears to be an issue with libcrypto.so. Fail. I might need to start with someone elses build whilst I try to sort things out.
[Galaxy S 4 Active Original Android Development] spegelius:
There's been lot of changes in msm8960-common and jflte lately. Also i've been doing the official version, inheriting from jflte instead of jf-common (which isn't used anymore). I haven't updated my jf-common or jactive-common for a while, so current roomservice won't work. Also to use official branch of jactive, one needs to have few unmerged commits in CM gerrit (or make the changes manually). Also as there have been alo otf changes to jf-kernel lately, the unified kernel changes aren't working anymore, so the using the jactive kernel is recommended.

It's bit of a mess curently... i'm trying to find the energy to start debugging the camera and not really interested in fixing this as CM devs aren't responding and no way to know if i'm doing it for nothing.
[Galaxy S 4 Active Original Android Development] snadge:
Okay, so it is business as usual in Cyanogenmod land. ;) I have installed cm-11-20140806-UNOFFICIAL-jactivelte.zip, with latest gapps(gapps-kk-20140606-signed) from goo.im, and am restoring my apps and settings etc currently. So far it seems to be working okay. Took some photos, recorded a video with the default google camera app. Too early to say if there are any significant issues. I'll roll with this for now. With good fortune, some of these patches will get merged, and any remaining nigglies might even get some attention.

I'm liking this so far!
[Galaxy S 4 Active Original Android Development] O-T:
1.) Bluetooth

disconnect and bad behavior is still happening in builds up to latest cm-11-20140807. In CM Jira there is a CYAN-3481 Bluetooth disconnecting and poor connectivity This is slooowly progressing since Feb 15. and latest post has positive result with a custom kernel.

2.) Camera

@spegelius has focus on fixing camera issues. When it comes to the selection of gapps we can choose from a large library of flavors: goo.im/gapps , repaired , PA and others. Most of the gapps replace CM camera = com.android.camera2 v2.0.002 with Google Camera = com.google.android.GoogleCamera v2.3.019

The buttons and layout look like this in both:

I've may got this wrong and it does'nt matter what camera we use. Just pointing out to make sure we are not "barking up the wrong tree" :fingers-crossed:
[Galaxy S 4 Active Original Android Development] olarf:
Form my experience the camera issue is a General one, not a cm11 cam one. Im just sure about the 10min Video limit.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] ZeroZorro:
I replaced the gapps as O-T mentioned and my camera is working now. Just flashed the mini-gapps after clering cache and dalvik and working fine so far...
[Galaxy S 4 Active Original Android Development] spegelius:
Most of the camera issues are general, the app shouldn't matter. But then again, CM11 has lot of changes in camera code vs original AOSP code and there's lot of Qualcomm related stuff so cannot tell for sure. Like some kind of callback handling which is completely missing on AOSP camera. Didn't know that gapps contain camera app, if it really overwrites the one that comes with the rom... no wonder the settings aren't working.

There's lot to do related to Active camera; first find out what is the main reason for it hanging and then implementing those features, preferably not in the camera app itself but on the camera wrapper code... man, i deal with easier stuff at my day job and i get paid helluva lot more than with this. Oh well :)
[Galaxy S 4 Active Original Android Development] snadge:
I'm unable to reproduce any problems with the camera so far. What specifically am I looking for? I'm using the standard gapps camera, and it seems to take pictures and record video. Am I missing something?
[Galaxy S 4 Active Original Android Development] O-T:
0729, Tsjoklat gapps mini, Google camera installed from Play (replace CM camera).

Tried different settings before switching camera HDR: size 8M/6M , flash on/off/auto. Flash =auto will freeze camera. A reboot is needed to get camera up again.
[Galaxy S 4 Active Original Android Development] spegelius:
Flash and HDR (or HDR in conjuction with flash). Also i got camera to freeze when camera was autofocusing on persons face.
[Galaxy S 4 Active Original Android Development] spegelius:
Not much progress with camera, only thing i've confirmed is that the kernel isn't responsible of the problems (copied most of the camera stuff from Samsung KK kernel). And currently no time to debug the camera since got reply from CM devs and i'm updating the unified kernel stuff. I left a build baking last night, hopefully it has finished so i can get to testing. I'll propably need to use NE5 blobs because some of the kernel changes are about the ril and gps, which weren't working on old kernel.
[Galaxy S 4 Active Original Android Development] snadge:
For what its worth. I fired off a build thats based on the new jflte branch (cm11.0-official), with the NE5 props, and dirty flashed it over the 0806 build (last one that works well), and it boots with display. It complained loki.sh was missing after I flashed it, so clearly there's at least a few small things that are probably easy enough to fix, and it was crashing repeatedly on startup. Dirty flashed 0806 back.

Also it might be worth noting, that on the 0806 build (clean flashed), with standard goo.im gapps, I'm able to take multiple HDR photos with auto flash enabled.

At least its useable enough for me not to want to bother going back to stock. For the few months I was quiet, I was just on the NE5 rom, using my phone as.. you know.. a phone.. ;)
[Galaxy S 4 Active Original Android Development] O-T:
[MENTION=2205086]snadge[/MENTION]

Been there for a while. Couldn't stand the itch. Welcome back. :)
[Galaxy S 4 Active Original Android Development] spegelius:
Did you use jactive kernel of jf kernel? I had some major bad experiences with jf-kernel with stuff copied from TW KK kernel (with jf kernel, VARIANT_DEFCONFIG isn't working so i was building jf kernel and when i got that sorted out, jactive failed to multiple build errors and kernel build bugs... blergh). Then again, i think you couln't have used jf kernel and get working display. Was just thinking that what if i take the jf-kernel and build it with jactive config (as it has one already), without merging stuff from TW kernel...
[Galaxy S 4 Active Original Android Development] Jhon998:
Really bad dpi on the 07 Aug, switched back to 06 Aug and dpi is good, please fix
[Galaxy S 4 Active Original Android Development] spegelius:
Dunno about that, propably CM upstream changes which have caused this... after that date the whole jactive build was broken in many, many places.

Anyways, after quite intensive struggle i got the kernel sorted out and a build made. Didn't test much, getting late and i need my phone in working order, but here's few notes:

no sim card detected, propably (hopefully) blob problem

flash, hdr and everything seemed to work with camera, except had one crash after switching some modes. But camera didn't hang, so it's not the drivers. niice...

no other crashes or anomalies

I'm using NE5 blobs, all of them. If someone is interested to test different blobs, get latest jflte blobs from TheMuppets github and make a build (replace jactive camera NE5 blobs before that). Uploaded my builds, if someone wants to test... but remember, phone doesn't work

To build, here's roomservice.xml:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="spegelius/android_device_samsung_jactivelte.git" path="device/samsung/jactivelte" remote="github" revision="cm-11.0-official" />
<project name="spegelius/device-props_jactiveltexx.git" path="vendor/samsung/jactivelte" remote="github" revision="cm-11.0-NE5" />

<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/android_device_samsung_jflte" path="device/samsung/jflte" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_jf" path="kernel/samsung/jf" remote="github" />
</manifest>

Also needed are these commits from gerrit to get the device tree and jf kernel work:

http://review.cyanogenmod.org/#/c/67428/

http://review.cyanogenmod.org/#/c/67429/
[Galaxy S 4 Active Original Android Development] spegelius:
Tried jflte blobs instead of NE5 blobs, no sim detected still. Now as the kernel is new and device tree is new, it's hard to tell which is the problem... it could a simple change in device makefile which i haven't seen, or it could be something missing in kernel. Logcat and dmesg don't show any crashes or missing files (well one firmware file, keymaster.something, but that shouldn't matter...).
[Galaxy S 4 Active Original Android Development] Jhon998:
I can' send sms messages, but only able receive them,

I also disabled voice + and messages encryption...

06 aug btw
[Galaxy S 4 Active Original Android Development] O-T:
0729 is working SMS. Clear cache +dalvik and flash. Using this as daily. Known issues BT disconnecting and some camera HDR mode switching.
[Galaxy S 4 Active Original Android Development] spegelius:
Got the RIL problem sorted out, CM has changed stuff in device tree so that build.prop was missing a lot of values. But now camera crashes... wtf. Oh well, i think it's time to repo sync and make clean...
[Galaxy S 4 Active Original Android Development] allram:
Its good News to hear that the ril problem have sorta been solved ;) thats with the new ne5 blobs, right? :)

Im back from vacation tomorrow and have some catching up to do on my work. But hopefully i will be able to help debug some this week ;)
[Galaxy S 4 Active Original Android Development] spegelius:
Yes, NE5 blobs. jflte blobs work also (except camera of course) and it might good idea to check differences if there;s files missing or something.

Uploading todays build to test. Got camera working, had some mixups with repo sync and not update roomservice... took several HDR pictures and switched flash on/off/auto without problems.
[Galaxy S 4 Active Original Android Development] O-T:
0815

Phone will call out. When call start the UI drop back to 1st screen of phone, not display of call is ongoing.
[Galaxy S 4 Active Original Android Development] olarf:
I will soon Start testing the new build (vor the next ;) ). The last 10 days the 0805 made me realy happy, especially battery live:

More then 50h is just amaizing!!!

And its so fast :)

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] Jhon998:
It damaged everything and the 271 apps that I had became 79

Now going back to 4.4.2 and will flash pac the real stable....
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm, seems like it works as when i first tried to get NE5 blobs to work... i wonder if something is missing from the blobs. NEed to get a logcat of that.
[Galaxy S 4 Active Original Android Development] spegelius:
Also Youtube playback is so broken... comparing to jflte blobs, some files are missing and some files and some don't exist on jflte. Remixing these...
[Galaxy S 4 Active Original Android Development] FORC3:
hey guys,

i have some serious problems right now with my device.

Since today i got the problem that i cant activate wifi and bluetooth anymore.

I tried all kind of builds from allram, spegelius, darkman and also some stockroms.

Nothing helped, tried to flash modem.bin and NON-HLOS.bin versions ubmk3 and ucne5...nothing changed sadly.

Does anybody else has similiar problems?

Any ideas how to get this to work again? :silly:

Have to go to the hospital in 2 days and i really need my phone working again.

cheers c3po
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
Well. damn, you got me! :)

I'm not a fan of CM, though I have used it off and on, just seems too bulky and complex, that is why Ilike AOSP. However, I have been following this thread since it directly relates to your work on the AOSP 4.4.4 version. So Installed this just to see how it runs, and the camera working was what tipped me over the edge.

I have to say, this runs very well, it might be smoother than anything I have tried in some time. I especially notice the smooth scrolling in Twitter, G+, etc. Nice work!

The only two issues have been You Tube as you know, and I cannot toggle between battery save and high accuracy with the GPS tile in Quick Settings. The tile does not report correctly how the location choice is set. This is probably why GPS Status and Toolbox force closes when I try to open it. https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2&hl=en (I also have the Pro key).In spite of that, GPS works fine and is accurate and gets a lock very quickly.

I guess it is time to look at seting up dual boot with this and your AOSP.
[Galaxy S 4 Active Original Android Development] olarf:
Did you flash original ROM by Odin already?

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] FORC3:
DOH

Jupp, the last ROM i have tried was: "I9295XXUCNE5_I9295DBTCNE1_I9295XXUCNE5_HOME" from sammobile.com.

I flashed it via Odin 3.09 - nothing changed

I also tried different basebands: UBMK3, UCNE4, UCNE5. Nothing changed... Its very weird
[Galaxy S 4 Active Original Android Development] O-T:
And now you can not activate WiFi or BT.

This is not a problem reported by any other in this CM11 experimental dev. thread - as you would have found by check what's posted here last weeks. I understand your concern for your device and use stock Samsung ROM is best choice to "play safe".

Please keep this thread on topic and discuss your issue in General or Q&A section of XDA.
[Galaxy S 4 Active Original Android Development] patzyalex:
Did you try this easy trick?

https://www.youtube.com/watch?feature=player_detailpage&v=CKAFcJ1GbPg

Read the description of the vid.

It worked 4 me.
[Galaxy S 4 Active Original Android Development] spegelius:
New build up with mix of blobs from jflte and NE5 (well, only camera blobs are from NE5).

Video playback fixed, also phone seems to be working.
[Galaxy S 4 Active Original Android Development] allram:
Downloading for test now ;)
[Galaxy S 4 Active Original Android Development] spegelius:
New blobs on branch cm-11.0-official
[Galaxy S 4 Active Original Android Development] O-T:
@spegelius, @snadge

There has been merged lot of fixes to CWM recovery since 6047. 6050 posted by mythy (extracted from CM11-20140713-UNOFFICIAL-jactiveltexx) does not include latest fixes up to Aug 15

When checking recovery.log there is a lot of lines related to recovery.fstab and where to mount.

W:Unable to get recovery.fstab info for /sdcard during fstab generation!

...

I:using /data/media for /sdcard

If save log from CWM 6045/6047/6050 it will not be stored in /sdcard/clockworkmod but /data/media/clockworkmod

Not sure if CWM backups end up in /data/media (I use other tool for backup) or if both locations for dalvik-cache is cleaned (clear dalvik-cache) to test latest build of CM11 jactivelte.

Can it be that this issue is solved in Fix datamedia detection

I do not have a build box or experience to build jactivelte. I propose a wish for recent recovery.img (CWM) that include latest fixes.
[Galaxy S 4 Active Original Android Development] O-T:
0817 build :

Phone calling confirm working.

Video recording has blue tint and jagged mosaic in all resolutions. HDR, flash, color switching, delete data of camera app did no difference. Photo has right color and show no sign of crash when switching modes.
[Galaxy S 4 Active Original Android Development] ZeroZorro:
Same for me except recorded video is ok, only jittering while recording, no jittering in result.
[Galaxy S 4 Active Original Android Development] spegelius:
Old preview resolution problem has resurfaced. I wonder why CM has changed the Camerawrapper to not use the previous settings (like aforementioned preview size parameter). I'd prefer not to have to change the CAmera app settings...

Uploaded fresh CWM, ver 6.0.5.0. It's built every time rom is built so uploading it along the rom is possible... need to create tar.m5 and rename it so it's bit of extra step but with scrip no biggie.