yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] immensemorbid:
I guess it's my first time in years trying to be brave :laugh: Used to own a HD2 and flashed roms everyday just to see whether which one works best. But right now I feel as though I'm a total noob again. LOL.

Okay. I'm still a bit lost. Basically my i9295 has CWM 6045 installed when I decided to root the device some time ago, in efforts of gaining more battery life through the day by tweaking the cpu. I've realised Stock Samsung firmware will still be very power hungry no matter what you do.

So I did a full reset and wipe through CWM and flashed this build

- cm-11-20140824-UNOFFICIAL-jactivelte-nightly.zip

After installing did a reboot, everything worked fine and continued to flash gapps

- gapps-kk-20140606-signed

Everything seems to work fine, phone became fast and responsive since no more samsung bloatwares are available.

But I have trouble getting gmail synched. I downloaded Google Calendar as well, and it still continue to "Synch" without any mail coming in.

And my whatsapp from playstore also gave the same error which that i had some few over thousand hours to wait before i can verify my number again.

Date and time, tried setting manually without relying on cell updates, can't work as well.

I kinda really like this simple rom. Just trying to make it work :)

Thanks

p/s: sorry my CWM is version 6035

---------------

Update

---------------

So i tried flashing gapps from here

[ROM][WIP][AOSP][4.4.4_r2] Google Edition for SGS4A (int'l) 0.9.6

http://xdaforums.com/galaxy-s4-active/orig-development/rom-google-edition-sgs4a-intl-v0-4-t2817383

- pa_gapps-modular-micro-4.4.4-20140818-signed

Results:

- all google services started to work fine

- my whatsapp worked again

- although errors for some apps i.e;Shazam, can't be installed. unknown error -24. Did a search on that and was told to look for data/data folder and delete anything related to the app. Couldn't be found with a root explorer as there was only one data folder.

Call Audio

- Not working. None available. Is there something i'm missing?

On another note (slightly off topic)

i tried flashing the from [ROM][WIP][AOSP][4.4.4_r2] Google Edition for SGS4A (int'l) 0.9.6

but that gave me more problems. Cell services won't start, wireless as well. Phone was practically useless.
[Galaxy S 4 Active Original Android Development] spegelius:
*Sigh* related to AOSP: format the /system, steps are listed on first post... second one missing that tidbit in two days. User error.

As for the call problems, they are known. As the title says, this is experimental, especially now that there have been large changes to device tree, kernel and blobs. As i can't edit the first post, there's no info about current build that's considered at least relatively stable. But even if there were, reading the thread to get an idea of good builds is recommended. So if you want to have working device, 0806 or earlier should work. Call audio problem, spontaneus resets etc. arek now problems.
[Galaxy S 4 Active Original Android Development] immensemorbid:
Thanks Spegelius I will try my best. :)
[Galaxy S 4 Active Original Android Development] moviecut:
Thanks for the hint with aosp. Never thought of flashing that, as i think it lacks much features. But together with gravity box it runs great for me!

Edit: Oh ****, external sd (64gb) doesn't work in aosp for me...maybe i will switch to cm11 again.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm, interesting... flashed latest nightly and suddenly Antutu isn't crashing anymore o.O. Two possibilities:

- i've been trying to get another sdcard working with exfat on AOSP and that card i currently on my phone

- repo sync has brought a fix to some part of the rom.

- magic

Let's call it stable and profit!
[Galaxy S 4 Active Original Android Development] olarf:
Sounds good, I will check if it also can make calls now :)

Edit: still calling don't work. It dial and connect but I hear nothing and the other also not :( Antutu works here also and I have the same SD card then before. It runs until the end but then it closed while it finish the test and I can read the results when I open it again. All tests done without gapps. Later I play with it a bit more.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
I made a test build few days ago with different blobs, NE5 + some from the jflte. Didn't have my work phone with so couldn't test the phone functionality and time was also limited. I'll try to test more today.

Then again i've had no problems with calls, so it's quite hard to debug call problems. I saw a thread about call problems in other section: http://xdaforums.com/showthread.php?t=2431928. Do any of you having call problems have them with Samsung roms or other AOSP based roms? Is it just the newer CM11 builds with new RIL and radio blobs?
[Galaxy S 4 Active Original Android Development] ZeroZorro:
I have only call problems as described by [MENTION=4481095]olarf[/MENTION] with latest builds...returned to 0806 after testing 0827 and no problems in 0806.

If you neef me to test a build in between those just let me know.

BTW thanks for updated Dualpatcher version, works great ;)
[Galaxy S 4 Active Original Android Development] olarf:
Exactly same for me, 0806 works perfect, later builds and also the latest one have call problems.
[Galaxy S 4 Active Original Android Development] spegelius:
Ok, another question: those of you with call problems, have you flashed Samsung KK rom? NE5 or something? Remember, i had NE5 flashed with Odin sometime ago...
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
I have NE5 baseband running with your latest AOSP. Late today I'll test this latest CM for calls and report.
[Galaxy S 4 Active Original Android Development] O-T:
Samdownloads.de - firmware - i9295 - nordic:

I9295XXUCNE4 (NEE) 4.4.2 Modem NE4

This was my choice because I don't stay in Germany (DBT) with modem NE5.

No call audio problem with I9295XXUCNE4 or CM11 up to 0806. Have only tested single, no dual boot CM11
[Galaxy S 4 Active Original Android Development] ZeroZorro:
Yup...

I9295xxucne5
[Galaxy S 4 Active Original Android Development] spegelius:
Allright, i'm assuming whole rom flash and not just modem. Just thinking about the bootloaders and all... also what i'm curious is that how much does the roms locale affect modem functionality; the NG1 modem i tried last week was from a rom meant for Brazil and that didn't work out.

Got a funny idea, i'll fetch latest modem i can easily find meant for jflte and flash it. Since 95% of the kernel is the same on these phones, i'd say there's a good possibility that modems are interchangeable. Or i get a brick and time to buy another phone :p
[Galaxy S 4 Active Original Android Development] olarf:
I flashed NE5 also with Odin. Never flashed any Samsung Rom :)

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
Well had a look in I9505 forum for modems, seems that the modems follow similar naming pattern. Also it seems that the builds with newer blobs and kernel and whatnot are also causing trouble, so it's not isolated to Active... http://xdaforums.com/showthread.php?t=2559336
[Galaxy S 4 Active Original Android Development] O-T:
In case there is a relation between blobs from NE5, jflte or other source and RIL that give no audio when calling.

Att. output made from Terminal on 0806 with modem NE4:

su
getprop | grep -i ril >/sdcard/cm11-20140806-modemNE4.txt

Some snippets from output:

[gsm.version.ril-impl]: [Qualcomm RIL 1.0]

..

[ril.hw_ver]: [MP 0.600]

..

[ril.product_code]: [GT-I9295ZAANEE]

[ril.rfcal_date]: [2013.11.12]

[ril.sales_code]: [NEE]

[ril.sw_ver]: [I9295XXUCNE4]

..

[ro.telephony.ril.v3]: [newDriverCall]

[ro.telephony.ril_class]: [SamsungQualcommRIL]

Before joining CM11 camp I Odin flashed I9295XXUCNE4 (NEE) 4.4.2 ROM+Modem NE4 and have kept NE4 modem.

On spegelius builds 0806 and older phone is working with call audio. The new ones do not.

If any of this is useful then maybe those with other modem, running new builds + working call audio can provide

cm11--modem.txt
[Galaxy S 4 Active Original Android Development] olarf:
Seems then that the Problem exist with ne4 and ne5 and in phones that flash Sammy KK before as on those that never see Sammy KK. Does anyone has calls working on a build later then 0806?

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] O-T:
I was searching changes in CM11 base camp regarding the cleanup of a lot of S4 variants.

This was merged Aug 06 - the day after cm-11-20140806-UNOFFICIAL-jactivelte was made.

The real build date of 0806 is 0805 and is based on inheritance before cleanup.

Spegelius is aware of the commits (as he posted Aug 9.) and need time to dig into it. :good:
[Galaxy S 4 Active Original Android Development] spegelius:
Modem info files attached, from AOSP and 0828 CM11. There are differences, new NE5 ril blobs require new ril handling (code in hardware/ril). Older ril implementation doesn't work with new ril blobs and propably vice versa (api changes). The above msms8960 changes are mostly moving stuff around, actual changes should be minimal. New prop changes for new ril and blobs are in jflte/system.prop.
[Galaxy S 4 Active Original Android Development] O-T:
And when the open commit "msm8960-common: update to kk rilblobs" http://review.cyanogenmod.org/#/c/71679/ get merged hopefully some more pieces fall into place :rolleyes:

"Camera: support HDR" http://review.cyanogenmod.org/#/c/70518/ is also much welcome :) to merge.

This looks promising.

Edit1: bricks fall into place change to pieces... ;) kinda better way thinking of what dreadful feeling bricked has in this world
[Galaxy S 4 Active Original Android Development] allram:
The KK rilblobs have been merged now.. But it seems like we need some sort of java ril file in /ril/telephony/java/com/android/internal/telephony/**

Hopefully we only need that (if we need it) in the jflte folder, and then the jflte guys will fix it for us :)

Making a build now and trying out some new gps blobs to see if the latest commits to msm8960-common have fixed something there :)

Trying with new RIL files also, just to check :)

edit: gps nor new ril files worked :( Seems like we might need some more commits or files..
[Galaxy S 4 Active Original Android Development] spegelius:
Hopefully i'll have some time to spend on this now, i'll have a look during weekend or next week. But i have a bad feeling about relying too much on jflte stuff since it seems that jflte ril stuff causes problems on jactive and we don't have new enough blobs (there are some differences between what files are available on NE5 rom and latest jflte blobs). I wonder if i should maintain another development branch with older kernel and blobs, since they are working very stable on the AOSP build... but that takes time and doesn't contribute on getting this official, since unified kernel etc. is needed.
[Galaxy S 4 Active Original Android Development] allram:
Hopefully you get the time, you are much better at this than me >.<

I think you/we should focus on trying to keep this in the official branch :) Everything builds and runs fine now on official except gps and radio :/
[Galaxy S 4 Active Original Android Development] spegelius:
I tried latest nightly yesterday, phone is a mess. If i call to the phone, it doesn't even show that someone is calling. Didn't even bother to try calling with it, last time i tried the call would start but then the phone app closed but the call was still ongoing or some crap like that.

I also noticed that there are blobs for msm8960-common also on TheMuppets github. So i fetched jflte and msms8960 blobs and made a build. Now it doesn't even ask for pin code. Logcat doesn't show anything out of order... more testing tonight. Btw, managed to break my phones display by dropping it. Still works and there's only one long crack which slightly affects viewing on some angles.

I'm tempted to start reworking on the old device tree and blobs, they work well. Also there's that other roms depending on those aren't building nowadays...
[Galaxy S 4 Active Original Android Development] allram:
I've made a few builds myself just to test, and i get same results as you, but when using NE5 blobs i get the call display up but it hangs at "calling"... Might be a good idea just to go back to the old working device tree :(
[Galaxy S 4 Active Original Android Development] O-T:
I've stayed with 0806 build for some weeks as this is the most stable, yet based on old setup.

Has the move to unified CM source which started early August scrambled the map making it hard to use as base for jactivelte/i9295 ?
[Galaxy S 4 Active Original Android Development] spegelius:
Shot answer, yes. Long answer: CM has been moving everything around; device trees have moved stuff around (from msm8960-common and qcom-common to jflte/other devices and the other way around). Concerning official status, that's mostly ok since we are inheriting most of the stuff from jflte. Biggest problem currently seems to be the blobs and specifically the new KitKat RIL blobs which cause all kinds of problems. Currently the kernel seems to work so that's not a problem anymore (but it's still on the code review phase, they're propably waiting for me to finish all the code! (insert meme here) to approve everything on one go).

Other roms using CM11 device trees: i think those haven't been getting a working build for months. Seems many of them have been relying on my device tree, which was left unattended when the 'official' work started. Now i don't mind people using my stuff from github, but relying on just that doesn't show that good preparation for changes, especially when i'm not aware about such things. With current CM dependencies the 'old' device tree needs to be heavily reworked and all that fancy KK RIL stuff needs to be purged. Or simply fork CM repos from a point before this 'KK new stuff' hulabaloo.

Btw, jflte blobs, without msm8960 blobs and i can receive a call and both sides can hear each other. However, calling doesn't work; phone is dialing, but call doesn't go through. Hang up doesn't work, going back to home and retrying produces error: Call not sent.

---------- Post added at 08:53 PM ---------- Previous post was at 08:03 PM ----------

Can't flash jflte modem files, flash (with Heimdall) always fails with:

Uploading APNHLOS
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: APNHLOS upload failed!

Both modem.bin and NON-HLOS.bin do this. Bootloader screen has a text about SECURE CHECK fail or something...

Downloading NH2 rom now to try those modems.
[Galaxy S 4 Active Original Android Development] spegelius:
NH2 modem installed and seems to work on AOSP. On CM, same problems as with NE5. Going to try NH2 blobs next.
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
I'm probably lost and confused. Insomnia here. I thought you had the NE5 modems in your drive somewhere and was looking for the NH2 ones as we.. Can / would you place them in ./dev?
[Galaxy S 4 Active Original Android Development] spegelius:
Yes, after work. Didn't want to upload them last night before testing them.
[Galaxy S 4 Active Original Android Development] spegelius:
Modems: https://drive.google.com/open?id=0BzJzDM42pkRvVmd0RW5naUt5SEU&authuser=0
[Galaxy S 4 Active Original Android Development] spegelius:
NH2 blobs were even worse about RIL, incoming call doesn't even show in the screen and calling doesn't work... still, with jflte blobs (camera blobs from NE5) i can receive calls and there's audio. Uploading that build, cm-11-20140910-UNOFFICIAL-jactivelte.zip, if someone wants to test.
[Galaxy S 4 Active Original Android Development] elgorra:
Sorry for my ignorance but can the modem be flashed with CWM or is Odin the only way? I never touched my modem since the purchasing the phone. Should I upgrade?
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
Only with Odin. Here are allram instructions from earlier in this post. I think he has the NE5 modems too. I installed NH2 and went from -91 to -86 db at my poor signal house.

http://xdaforums.com/showthread.php?p=54959047&highlight=odin#post54959047
[Galaxy S 4 Active Original Android Development] moviecut:
Edit: Thanks, will try NL2 together with AOSP. Seems to be the best combination so far for s4 active (+ gravity box)
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
Yes in signal strength the bigger negative number is worse that a smaller negative number, so the NL2 is a slight improvement in a weak 3G signal area where I live over the NE5 in the west coast USA. I live close to the ocean and it if often foggy so week signal and fog, or rain or clouds makes a huge difference. Below is a rough idea of signal strenght, depending on the frequencies used by a carrier.

I follow this thread but only use spegelius AOSP rom, to keep up on development and radios like this, except for occasional testing, AOSP has been rock solid daily driver for me for some months now.
[Galaxy S 4 Active Original Android Development] O-T:
The RIL blobs (drivers) need to interact with modem.

Samsung modem naming:

N = year = 2014 (14th letter of alphabet)

E = month of year (May in this case, 5th letter of the alphabet)

A = build # of that month (10th for, "A", as they start 1-9 first, before letters)

NE4 = 2014, May, Build 4

NH2 = 2014, Aug, Build 2

Modem NH2 was released Sept. 1. packed in rom I9506XXUCNH4 for Germany Vodafone Build Datum: 22.08.2014.

Wonder where modem NL2 (2014, Dec, Build 2) came from.... :what:

There can be a mismatch where the RIL blobs (drivers) in the ROM are not in sync with modem version, new rom with old modem. Modem is not included in cm11-* rom.

Is it known what date/version of KK ril blobs that's merged in CM11 device tree?
[Galaxy S 4 Active Original Android Development] allram:
We have been working with our own device tree/blobs, so when Spegelius tryed NE5 blobs, i flashed NE5 modem to use for test :)
[Galaxy S 4 Active Original Android Development] spegelius:
Blobs in cm-11.0-official are mostly from jflte if i remember correctly. Also the last build i made also has most of the blobs from jflte, only camera stuff is from jactive. And those work the best when RIL is considered. No idea from what jflte rom those blobs are. Some earlier blobs were from I9505somthingNF3 rom, but looking at the commits, those have changed few times since then...
[Galaxy S 4 Active Original Android Development] allram:
Looking at the jflte commits and device tree it looks like everyone want to do their thing to it, and they have some trouble trying to unify stuff :-/
[Galaxy S 4 Active Original Android Development] spegelius:
Yes, feels like we are caught in the middle of it. Bad time to offer another device for official evaluation...

---------- Post added at 06:22 PM ---------- Previous post was at 06:05 PM ----------

Well what do you know... yesterday i whipped jf-cmmon as CM devs wanted and made jactivelte inherit it. Made a build and to my amazement calling works both ways :eek:. Uploading now: cm-11-20140912-UNOFFICIAL-jactivelte.zip. Using cm-11.0-official branch blobs
[Galaxy S 4 Active Original Android Development] allram:
Awesome! Was going to try some mix later on, but gonna try your build instead then :D
[Galaxy S 4 Active Original Android Development] dadme:
Calling works on latest build, but no sound on caller when switch to speaker.
[Galaxy S 4 Active Original Android Development] O-T:
+1 for 0912 test :)

Will keep NE4 modem and check before opt for new, even though they are released with ROM for i9505 or i9506.

---------- Post added at 07:30 PM ---------- Previous post was at 07:18 PM ----------

Gdrive has 3 files 0912:

-jactivelte

-jactivelte-nightly

-jactivelte-nightly_dual

I think [MENTION=3876105]spegelius[/MENTION] had good result with the first one. The two others are Jenkins build. Correct me if wrong...
[Galaxy S 4 Active Original Android Development] spegelius:
Yes, nightlies are Jenkins automated builds.

Uploading jf-common for review, fingers crossed...

---------- Post added at 10:51 PM ---------- Previous post was at 10:32 PM ----------

Aha, now the previously seen reboot during Antutu run is back. Hmm... could it be the blobs perhaps?
[Galaxy S 4 Active Original Android Development] allram:
Might try a build with the new NE5 blobs repo you made? :) or, update your manifest for cm-11.0 so that i can make builds and test again :p
[Galaxy S 4 Active Original Android Development] O-T:
CM-0912, NE4 modem, pa_gapps-modular-nano-4.4.4-20140904a:

Antutu no reboot, cam back/front/HDR on-off +video OK, calling with audio & HF speaker, WiFi /APN connect, no battery bar usage marks while not in use, GPS 10/18 sat connect (none Glonass even if visible)

Will try BT call +music in car later.

This looks good :) perhaps better than other S4 siblings ;)
[Galaxy S 4 Active Original Android Development] olarf:
Downloading now, lets See what happen here ;)

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
Good call, i'll update roomservice.xml. I'll upload props with latest jflte stuff also later, have to restructure them a bit....

---------- Post added at 11:55 AM ---------- Previous post was at 11:37 AM ----------

New 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-official" />

<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_jf-common" path="device/samsung/jf-common" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/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>

Couple of notes: for this to work, you need this for jf-common: http://review.cyanogenmod.org/#/c/72877/1. Also, for device props, there are few options for branches: NE5 and NE5dev currently. I'll add newest jflte blobs when i get them sorted out.

Oh and of course jf kernel needs this: http://review.cyanogenmod.org/#/c/67429/ since it's not merged yet. Forgot this since it's been talked about previously...
[Galaxy S 4 Active Original Android Development] allram:
Thanks :) Going to try NE5 branch first :) going to do a clean build, no optimizations, that will come later on when all this things are sorted out :P

edit: Bah... Getting alot of Busybox errors and then build fail... might be some new commits to busybox perhaps?

edit2: hahaha, totaly forgot /vendor/cm ./get-prebuilts command, everything works now.. building with NE5 branch :)
[Galaxy S 4 Active Original Android Development] mythi:
anybody now about this :confused: i am trying the new sammy kernel sources (from scratch with cm defconfing) , the file stated is there but somehow its not working :eek:

/home/mythi/cm/kernel/samsung/jactivelte/arch/arm/include/asm/io.h:30:26: fatal error: mach/msm_rtb.h: No such file or directory
[Galaxy S 4 Active Original Android Development] dadme:
NL2 ,modem. I find only ML2 by now. Could you provide a link?
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
I mis-typed, the are NH2. There is a link above in the last couple days from spegelius. Gotta run off no time to search for you, sorry.
[Galaxy S 4 Active Original Android Development] ZeroZorro:
Seems that ANT+ is not working, correct?

I remember reading about S4 and S4A At&t 4.4 releases supporting it..