yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] manolo-mm:
Hi...

I'm looking forward for the stable version. Do you have a release date?

BR
[Galaxy S 4 Active Original Android Development] nasaprinsloo:
Big LOL!
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm i haven't any ANT+ compatible devices to test this with... all i've tried is pairing with my work laptop so far :).

Hehe, i would like a stable version too :). But no ETA, there are few larger bugs and my time is limited for this kind of development (busy time at work, coding there and at home tends to get too intensive).

I've received few bug reports and found few bugs on my own:

camera has some problems, most of them are only annoying, but there's a bug that causes the camera to hang and only reboot fixes that. Happens on all roms i've used (even Sammy rom did this when to phone was new). Fix: absolutely no idea

compass is missing

i've had the phone to shutdown on two occasions: first was when camera hanged, other was when i was running Antutu (also Antutu score is almost 3000 lower than with CM 10.2?)

I've also tried contacting [MENTION=2205086]snadge[/MENTION] about the development and thread maintenance, but nothing to report on that front yet.

I'll do a repo sync and make a new build when i get some time. Also i've been meaning to have a look at the camera settings, but last time i did that on AOSP i got stuck on some Java build problem that i couldn't solve.
[Galaxy S 4 Active Original Android Development] allram:
Been using this for some days now, and it Works well for a daily rom. But it seems that if i turn off wifi, it still uses battery on the battery usage meters..

Just the one small bug i've found :)

Really good Job you have done here ;)
[Galaxy S 4 Active Original Android Development] ZeroZorro:
I can't test ANT+ too for the same reason, but latest Endomondo supports ANT+ but when i try to enable this it says no hardware support on this device.

Maybe just wait for the Sammy Kitkat for S4A and see if it supports ANT+ on the stock ROM.
[Galaxy S 4 Active Original Android Development] dks21:
I have been testing the rom for almost a week now, and I have to say that it's a real improvement! I was running the cynogen 10.2 and it was really less stable. Now the GPS fix is much much better, the bluetooth seems to be more stable, and the general experience is improved.

Anyway, I have had some issues:

- some problems with the camera (picture quality still poor), random crash

- sometimes the device freezes, black screen, etc etc

- sometimes there is a problem, the ring tones don't work (no alarm, sms sound...): rebooting solves the problem.

Anyway, that's a really good job, thanks!
[Galaxy S 4 Active Original Android Development] marcelser:
I guess you still believe in Santa Claus if your really think there will be a sammy KitKat port for the S4A anymore, remember there isn't even a recent jelly bean 4.3 build of a sammy rom. I mean there's a reason why at&t built their own 4.3 rom for the US S4A version because they are exclusive seller in the US.

I think samsung simply doesn't care about the S4A as they have not sold enough devices. I guess they won't provide any new roms for this device anymore. It started with 4.2.2 and will stay on this forever. Especially as the S5 has quite the same features as the S4A and they will concentrate on the S5 now.

Which tells me one thing: Never buy a special version of the Samsung S-Roms, like mini, active, zoom. Just buy the the normal one if you wan't to have good rom support or be prepared to say goodbye to rom support. Count yourselves lucky if samsung releases some minor updates for devices of these types.
[Galaxy S 4 Active Original Android Development] frater:
I think it's a bit early to come to this conclusion. Having a special version does make it less likely to receive early updates. I flash ROMs on my devices and friend's devices. The Sony Xperia Z and the LG G2, both flagships, don't have KitKat yet. We all want 4.4 and 4.3 is frowned upon like Windows Vista. But 4.3 was still a newer version. I now have to flash another KitKat ROM on my LG G2. It's still on 78% battery after 23 hours...

Cheers
[Galaxy S 4 Active Original Android Development] djentleman:
This rom is awesome! Ive been using it as a daily rom since a week now and the sole bug i experienced is the mentioned camera bug! Hope this gets fixed soon! Any progress on that?

Cheers...

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
I did have a look at camera settings and they have changed since CM10.2. At the moment it seems there isn't such easy way to change those as before, so i can't really say when it will be fixed. Oh and for the camera freeze + needing reboot, that is a big unknown...
[Galaxy S 4 Active Original Android Development] silberstein242:
Love your work spegelius, thank you very much for your time and effort.

I built with sources from 03/15 and had an issue with notification audio; no matter the setting or volume the notification sounds always played. Problem seems to be resolved with the 03/17 sources.

No freezes or reboots here, it's pretty damned usable – I can definitely live with the low res video preview.
[Galaxy S 4 Active Original Android Development] qwodge:
Thx alot spegelius for your work, also on CM 10.2.

Could somebody link an updated daily from the rom? Spegelius Drive folder has still the version from two weeks ago.

Would be really appreciated!
[Galaxy S 4 Active Original Android Development] spegelius:
Thanks guys, glad to hear you like it. I had some problems with my build env, kernel wanted some binary from jf folders even though no jf stuff was there and libtime_genoff was missing... started from scratch and now i got a build made. Also fixed the video preview and sub-1080p video recording. However, i have some problems with gallery at the moment, i'm going to do a factory reset and start clean, hopefully it'll fix things. I'll post the build later if it seems to work properly.

I have no objection of someone posting a build if working one is available. More the merrier :). But do give a short description, like when last repo sync is done, did you modify something etc. Fixes welcome of course :)

---------- Post added at 10:09 PM ---------- Previous post was at 09:09 PM ----------

Seems to be working ok now that i did a wipe and reinstalled. Previous install was the first working version, so no suprise that something was borked.

cm-11-20140319-UNOFFICIAL-jactiveltexx.zip build uploading now. Changes:

- repo sync done today

- camera preview fixed

- camera 720p and 480p recording works

- HDR doesn't crash camera

Do note that the first time camera is used, 720p might record crap video. Restarting camera app seems to sort this out.

Also compass is still missing. I'll have to backtrack my kernel changes. CM10.2 has working compass so kernel problem is my bet.
[Galaxy S 4 Active Original Android Development] silberstein242:
Nice!

For the future, I can upload the builds I do – I usually run a repo sync and build every other day or so.

(I did get a fatal error with roomservice.xml – had to pull your sources manually and move them into devices/samsung, that worked a charm though)

Thanks for the hard work!
[Galaxy S 4 Active Original Android Development] spegelius:
Yeah there might've been some errors with the roomservice.xml. I uploaded newer yesterday, it has the blobs repo, so no need to run ./extract_files.sh. Unfortunately, there's a bug with the prop makefiles and build will complain about no rule to make target libtime_genoff. For some reason, PRODUCT_PACKAGES += libtime_genoff doesn't have effect when it's defined in jactiveltexx blobs and not int jf-common blobs. Might be something related to the order how makefiles are read... maybe move that line to jactiveltexx makefile.

The roomservice.xml can be found from here: https://github.com/spegelius/manifests

And :good: for the build upload, i can concentrate on development :)
[Galaxy S 4 Active Original Android Development] silberstein242:
Ok, I haven't updated roomservice.xml in a while, I'll get the new one and try it out. I did encounter the libtime_genoff.so error – I think I fixed it by getting the sources manually from your repository.
[Galaxy S 4 Active Original Android Development] moviecut:
Wow, that sounds awesome, spegelius!

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] mythi:
TIME FOR PORTS :D:D

[MENTION=535343]all[/MENTION]/Guys ask which aosp rom you:D would like to be ported ?:victory::victory:
[Galaxy S 4 Active Original Android Development] spegelius:
Here are the links for builds made by [MENTION=1724170]silberstein242[/MENTION], thanks mate :

https://www.dropbox.com/sh/x4rpgukdfb8ucc5/d1thBtPKt3

and

https://drive.google.com/folderview?id=0B6OcLgaQ56ZwWFJzSGZ2dEU1Xzg
[Galaxy S 4 Active Original Android Development] mythi:
https://drive.google.com/folderview?id=0BzJzDM42pkRvVmd0RW5naUt5SEU&usp=drive_web
[Galaxy S 4 Active Original Android Development] dadme:
Thanks, i find it.
[Galaxy S 4 Active Original Android Development] mythi:
[MENTION=3876105]spegelius[/MENTION]

please merge the pull request i sent it made slam my head in the wall googl times :eek:
[Galaxy S 4 Active Original Android Development] spegelius:
Done
[Galaxy S 4 Active Original Android Development] O-T:
[MENTION=5150212]mythi[/MENTION]

Last time you compiled ports you didn't have S4 Active i9295 to test before release.

http://xdaforums.com/showpost.php?p=54982229&postcount=110

Please inform if this is still the status.

[MENTION=3876105]spegelius[/MENTION] has the phone and does test before release in respect of the users of his work. Have you considered what happen if you start spreading several untested ports for i9295 based on [MENTION=3876105]spegelius[/MENTION] CM11 work?
[Galaxy S 4 Active Original Android Development] mythi:
i made am no longer maintainer for vanir :( but they i dont think they dropped their support for the jactive AND I HAVE THE jactive :)

BTW [MENTION=3876105]spegelius[/MENTION] could you look at the error i posted back ... its also happening with the jf kernel :(
[Galaxy S 4 Active Original Android Development] spegelius:
The msm_rtb.h error? Haven't seen that. Have you applied this to jf kernel? http://review.cyanogenmod.org/#/c/67429/. I forgot to mention that on the roomservice.xml notes, but since it's been mentioned few times on this thread, i kinda assumed everybody knows it's needed and that none of my CM commits have been merged so far... (apart from one to msms8960 camerawrapper...).
[Galaxy S 4 Active Original Android Development] O-T:
Good, the progress to Official jactivelte CM will probably accelerate if more users give feedback here instead of asking how/why in multiple dirty port threads. It is hard to debug when core CM11 get cluttered by added features in ports.
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
I agree 1000%

In my long and frustrating efforts with the two primary devs of VanirAOSP on G+, they never had a jactivelte maintainer and never heard of you [MENTION=5150212]mythi[/MENTION]. Most of your links to email, donations, G+ and other things do not even work. Please do not start posting your builds unless you TEST, TEST, TEST, and don't screw up the great work of [MENTION=3876105]spegelius[/MENTION] and [MENTION=4630187]allram[/MENTION]. Thank you.

Sorry to sound harsh, but I put a huge amount of effort into trying to donate $100 USD to you, and thank goodness could not do it and waste my money, but I did waste a HUGE amount of time and energy. We don't need more of your buggy one hit wonders floating here, please. You did far more harm than good to this XDA SGS4 Active community.
[Galaxy S 4 Active Original Android Development] allram:
[MENTION=3876105]spegelius[/MENTION] Don't know if you've got time to test yet, but tried a build with the NE5 props, and then it just load and load and load the rom. So that's not working :(

Trying with NE5dev props now. The NE5dev is pure NE5blobs from jactive, right? :)

Btw, your latest build works fine with calling and NH2 modem ;)
[Galaxy S 4 Active Original Android Development] O-T:
0912, NE4 modem

... continued from last report

BT audio in car connect and play fine :D
[Galaxy S 4 Active Original Android Development] mythi:
Ok guys gotta move on for now , you won't see me for sometime , bit heart shattered :(
[Galaxy S 4 Active Original Android Development] spegelius:
Actually can't remember if NE5 branch was ever working properly with new CM11 RIL stuff etc. The fact that it doesn't finish boot is familiar, had that few days ago and then it was missing liblocationservice.so, which crashed all system services, in endless loop. I added it but apparently more is needed. Didn't test more though. NE5dev was working a few weeks back, i made it using jflte prop file list. But had problems with calls... Actually can't remember if all of the blobs are from NE5. Was kinda fed up about the whole RIL stuff and after i got the 'mix' done, i left it rot a week or so and can't remember what the contents are :o.

Oh and there's at least one bug not reported yet with current official blobs: time offset isn't written and in boot, system time is something way off... had this with AOSP, but in there it was missing code from framework. But during debugging, i learned that NE5 libtimegenoff.so doesn't work, there's some error, can't remember what. Older version works.

---------- Post added at 08:22 PM ---------- Previous post was at 08:08 PM ----------

Don't go away forever, you have enthusiasm which is good. But as i've been developing software for almost 10 years now as my day job, i've learned that rushing stuff out of the door is never a good thing. And you must follow it through, i.e. provide support. Now i'm not the best example when it comes to testing, but i've seen worse and i never put out a build if i haven't tested it myself or specifically mentioned that it's untested. Well the nightly builds aren't tested but that's bit different. Talking about nightlies, need to update roomservice on build machines...

Also the amount of ROMS... well, personally i'd like to go around and get all interesting looking roms, clone repos, modify device tree for each them , build and release. But the amount of time i'd have to spend maintaining is just something i can't do. Currently i have my AOSP, CM11 and SlimKat (which i just provide nightlies) and that's more than enough for me. CM11 has been lagging because of some problems i wanted to straighten out with AOSP. And there's more stuff still to be done, so trying something new just isn't possible.
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
I don't want you to quit and go away, just understand that you need quality, not quantity. I think you have plenty of talent, just learn the other things about follow up and testing and being responsible for what you produce and give it some support.
[Galaxy S 4 Active Original Android Development] olarf:
Just flashed 0912 and for the Moment it looks fine. Antutu run here and give highest score we had so far. Also phone works fine. Tomorrow I can test BT and GPS. I did dirt flash from 0806 and still use NE5.

Many thanks for bring us back to new working updates!

Today I test BT and GPS and both worked also pretty good. All over voice quality is better then before.

I'm now a bit unsure if I should switch to NH2 modem, can someone confirm serious advantages for NH2 in Germany?
[Galaxy S 4 Active Original Android Development] Tazzmanien:
I have been using the 0912 with NH2(Denmark) for a couple of days - it seems okay in day to day use.

However i think the power consumption is a bit high. :) Iam trying to use the profile battery save to see if it

has any effect :angel:
[Galaxy S 4 Active Original Android Development] allram:
I've been using NH2 in Norway now, seems stable and fine with me, even got better reception on 4G/LTE :)
[Galaxy S 4 Active Original Android Development] spegelius:
Well seems i've lost audio during calls. And can't be sure wat caused it. Two possibilities:

1. when i redid the jactive device tree, i copied some audio setup values from jflte. Reverted those changes and doing another build

2. during weekend, i updated official blobs with jflte blobs. Turns out the blobs are the same as before, but i had located some files differently in previous version. New version has some files in different directories, so this could be the reason. Seems that the locations matter, at least with some blobs

3. I also tried NH2 blobs, they are on their own branch in github now. Not good related to RIL, call starts but is ended almost instantly. Except, the call goes out on the backround, ui just doesnt know it :eek:. Receiving calls: no indication of call incoming.

I need to provide some blobs for a pull request to TeMuppets repo and i'm going with the official branch. I suppose further updates are going to be accepted faster if we get this to at least some kind of official status.
[Galaxy S 4 Active Original Android Development] olarf:
Just updated to NH2. Phone still works fine on 0912. Now I'm excited if my signal is slightly stronger then before as it seems to be for some of my European neighbours :)

Good luck Spegelius to sort out the files, 09.12 was such a great shot!

Gesendet von meinem unknown mit Tapatalk
[Galaxy S 4 Active Original Android Development] O-T:
0912, ne4, pa-gapps nano, CWM 6.0.5.0 spegelius

This was dirty flash (cache +dalvik clear) from 0806 +format /system. Had some apk disabled, as I had used to when dirty flash earlier (to save battery) . The upgrade to 0912 went fine and all system apk (including disabled) & Play apk had functions intact. Still there was a high battery drain.

As I like aCalendar best this app require latest Google Calendar to properly sync, so I added Google Calendar. Despite Calendar in CM11 and SyncAdapter in pa-gapps. The battery drain seemed to cool down. Still there was not like 0806.

So I tried to dirt flash back to 0806 using same way as to 0912.

Next start 0806 after sim pin phone and acore system popped up repeated crash. This stopped when I activated flight mode. Tried to clean data in apps with no luck.

Factory reset & 0806 swinged me back in game. Tried to make a logcat, reserved to give away any private info in file.
[Galaxy S 4 Active Original Android Development] spegelius:
Those builds have different blobs and different RIL-setup, so apparently something is left on the system even though system is formatted. Maybe something in the cache, if data was cleared?

Also, new build: cm-11-20140915-UNOFFICIAL-jactivelte.zip uploading now. Repo sync + blobs which i'm gonna offer to CM. Calls seem to work, but Antutu crashes again, it was working during weekend :eek:. These blobs have changes where files are, so it's possible that the battery drain might be fixed. Or not.
[Galaxy S 4 Active Original Android Development] O-T:
cm-11-20140915-UNOFFICIAL-jactivelte.zip =195Mb

Usually 221Mb

Corrupted upload / not finished ?
[Galaxy S 4 Active Original Android Development] allram:
Was Just Going to ask the same thing :P maybe not finished yet. Should be 220+
[Galaxy S 4 Active Original Android Development] spegelius:
It might be that the flaky Linux GDrive implementation has failed, again, with error about 'resource busy'. I've seen that few times in Jenkins build jobs, where build itself has finished ok, but the copy failed to that error. I have to re-upload after work. Or if the latest nightly has finished, it has the latest stuff so it might even work? Someone brave enough could try :)?
[Galaxy S 4 Active Original Android Development] allram:
No nightly yet, i can try it when it get's uploaded :)
[Galaxy S 4 Active Original Android Development] spegelius:
If there's no nightly for today, it has failed. Should been done about 5 hours ago.

I uploaded again, no erros this time. Yay for unlmited mobile data and ssh client on phone.
[Galaxy S 4 Active Original Android Development] O-T:
0915, NE4

Logcat has this line (1)every ~3sec when not doing anything on phone :

1)

09-16 11:51:50.849 624 798 E lights : write_int failed to open /sys/class/leds/button-backlight/brightness

i9295 has hardware buttons with no backlight, not like i9506. The /E was also present in 0806.

2)

All "kickstart EVENT" are listed as type E/

3)

Adreno-EGL looking healthy

4)

Many /E listings when bluetooth activate, not yet tested what happens when connected to car audio.

5)

A short info on first boot d.flash from 0806 said like "phone book updated". Call out working with audio incl hands-free speaker.

6)

Screen rotation not working. On-off quick tile "rotate" give no output in logcat.
[Galaxy S 4 Active Original Android Development] spegelius:
1. Yes, liblights does try to set key lights. I have modified version on old jactivelte-common tree, but didn't add it to jf-common just yet. Once it get's accepted to CM i'll try to add it

2. I think this has been like that always... looking through old logs i got stored and lot of those start with E/. Dunno why...

3. :good:

4. In general, i've seen lot of E/ listings for different services. I don't usually look at them unless the particular app/service/whatever is causing problems. I'd never gotten any rom done if i'd wanted to fix every E/ print... for example when camera is running, some of the prints are E/, but the message doesn't clearly say that something has gone wrong. I suspect it's wrong type of logging used of leftover debug stuff.

5. CM stuff

6. Have to check this
[Galaxy S 4 Active Original Android Development] allram:
[MENTION=3876105]spegelius[/MENTION] yeeeeeey! All your commits got accepted @CM :laugh: Now things might get better for us :)
[Galaxy S 4 Active Original Android Development] spegelius:
Wohoo! I was bit weary about the amount of gerrit emails this morning, but everything went better than expected :). Also the blobs were accepted and now there's a commit about adding jactive to nightlies :victory:
[Galaxy S 4 Active Original Android Development] allram:
Making a new build now, started totaly fresh, with everything from CM - official's.. Will let you know how it goes :) almost finished...
[Galaxy S 4 Active Original Android Development] spegelius:
Good, some testing is needed before i'll give the ok to the nightly-commit. Seems they are ok with jflte already.
[Galaxy S 4 Active Original Android Development] O-T:
0915

GPS connect and find position but Glonass sat is only visible. Compass is designed for Jack Sparrow. Known jf-common issue here http://review.cyanogenmod.org/#/c/53635/

4.4.2 fix here http://xdaforums.com/showthread.php?p=55480459

3% battery usage while not in use over night :thumbup:
[Galaxy S 4 Active Original Android Development] allram:
Build is up:https://drive.google.com/folderview?id=0BwwLmYElvFOmZkhIbTlaVGlaaWc&usp=sharing

edit: Gps works, GLONASS i don't know how to test..

radio works, haven't testet if anyone hear me yet, but i can make outgoing calls atleast.

Screen rotation - Not working
[Galaxy S 4 Active Original Android Development] spegelius:
- Calling works, can hear both ways; during receiving a call and making a call

- GPS Status shows green dots, green squares, grey dots and grey squares. GLONASS working?

- camera Exposure crashes camera, but can be opened again. I know why this happens, need to fix it on CM sources

- and yes, rotation seems to broken. Can anyone remember when this was last working? There's an error in log:

W/OrientationEventListener(11038): Cannot detect sensors. Invalid disable
[Galaxy S 4 Active Original Android Development] SamuTnT:
I'm on 0912 and it rotates!