yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
What!?!?! This is too about jactivelte! Looks at your CM-11 S4 Active bulld.prop! [MENTION=4630187]allram[/MENTION] is one of the official CM-11 release builders of this ROM you are scolding.
[Galaxy S 4 Active Original Android Development] snadge:
Official nightly? I thought people were tripping. I was going to be a complete spanner and ask what the current build instructions are, because my roomservice.xml is a bit all over the place.

I pointed my source tree at the official jactivelte sources, and only left the repo for the device props in /vendor/samsung/jactivelte, and Bob's your uncle, a rom that boots and works etc as has already been mentioned above.

Bravo! I can't believe at one point I was considering going back to stock. Disgusting! ;)

I can't thank you guys, particularly Spegelius, enough for the effort that has been put in. It is refreshing to see effort paying dividends for once, instead of wasted (like it usually is for me).
[Galaxy S 4 Active Original Android Development] O-T:
If [MENTION=4630187]allram[/MENTION] like to help [MENTION=5150212]mythi[/MENTION] compile anything based on his and [MENTION=3876105]spegelius[/MENTION] work, it's up to himself to decide. Some deviated off-topic post happen now and then in every thread - it's life.

Can you elaborate "looks at your bulld.prop"?

This http://xdaforums.com/showthread.php?p=55537220 was my feedback on build 0918 made by [MENTION=3876105]spegelius[/MENTION] to debug the rom developed in this thread. I wasn't asking for help to pull blobs to do my own dirty build.
[Galaxy S 4 Active Original Android Development] spegelius:
Yes, finally official :). Had few doubts along the way but here we are. Thread could be edited to reflect that status?
[Galaxy S 4 Active Original Android Development] mythi:
Ive done as many tests as I could with any mixture I get the same issues , in cm and lac from source and my last option is to change the baseband to NH2/others and see what would happen , RIL works absolutely right as I can messages and receive them but the issue is in calls .

Mr [MENTION=2997552]O-T[/MENTION] I fully respect you and your words , I am abdoning all other projects in favor of PAC and what relates to it , I know quite a few people in PAC team I could send the patch for gerrit and get a positive response , the same goes for others until they get stable enough
[Galaxy S 4 Active Original Android Development] olarf:
Indeed some PAC dev agree to help us to bring it to official status once a official cm11 exist. For sure mythis request is a bit off topic but its logic to ask here as allram and/or spegelius can help him to fix his bug at least. So need to attack mythi again, he just try to work now focused on one project following your hints. Thanks allram for support!

Beside this I will move back to NE5 now, NH2 works good but it has the bad behaviour to skip the connection while very low signal. NE5 seems to try to keep the connection as long as possible. As I live in a bad signal area, it affects me to much.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] O-T:
Glove mode (high sensitivity) has been in jflte* devices since Aug 28. http://review.cyanogenmod.org/#/c/65553/

Really hard to find when option is put in 'language & input' [emoji15] Strange logic.

More like a display or availability option.

Long press recent apps to switch to last used app

is working when soft buttons enabled by adding 'qemu.hw.mainkeys=0' to build.prop. Not able to get this to work with hardware button.

Nightly 0922
[Galaxy S 4 Active Original Android Development] allram:
Long press recent apps to switch to last used app Works fine for me.. Nightly 23.
[Galaxy S 4 Active Original Android Development] whizz:
My date and time are wrong upon reboot, do you guys have that too? (currently on nightly of today 0925)

Congrats on getting the ROM to official Nightlies by the way! I've donated a few beers to [MENTION=4630187]allram[/MENTION] and [MENTION=3876105]spegelius[/MENTION] :)
[Galaxy S 4 Active Original Android Development] spegelius:
I did some testing with glove mode setting last spring and didn't notice any difference. Haven't tested it on latest kernel, though... and yeah, maybe the setting isn't on most logical place. But that's up to CM devs to decide.

And Long press for last app doesn't seem to work. I get the recent apps menu if that's configured, but not the last app.

Thanks :). Time problem is a known one, i've submitted a push request to TheMuppets repo for proper time blobs, but it hasn't been accepted yet. I'll probably make a Jira ticket about it, go through the real process...
[Galaxy S 4 Active Original Android Development] Grinface:
I'm still on version as of 09-22. Can anybody confirm that every time after a reboot the phone has lost compass direction?
[Galaxy S 4 Active Original Android Development] O-T:
0922, NE4 modem: Compass align point north.

Not sure if there is a *# code to do calibration. You can try to enable compass and rotate all 3 directions (x, y, z) 360°. AndroiTS GPS app has this suggestion as intro to Compass.

Btw, US+Glonass satellites quick connect and stable giving 3m precision [emoji108]

Most Bluetooth functions seems to be working since Official started. Still there's a lot to do.

Check out this massive commits to repair Bluetooth by Scott Mertz : http://review.cyanogenmod.org/#/q/owner:"Scott+Mertz"+Bluetooth,n,z

[emoji106]

Hopefully they will be merged in short time.
[Galaxy S 4 Active Original Android Development] baaldfg:
Searching for network operators not possible?

Hi there,

Since the 0915 unofficial up to the current nightly, I have the problem that I cannot manually select a network operator. Searching for network operators always results in an error and doesn't yield any operators to choose from.

Furthermore the battery drain seems quite high with Google Play services directly after the Screen on normal usage.

Anyone else noticed these two things?

I am on the NH2 baseband.

Best wishes, Christian
[Galaxy S 4 Active Original Android Development] O-T:
0925, NE4

Manual search network operators give a toast msg. "An error occurred while searching". Same msg. when roaming is ticked.

Not able to identify anything related to this in Logcat filtering up to Debug level. My contract allow only one provider but the visibility of all available should appear when manual searching.

Automatic selection is connecting to my provider network (APN+telephone).
[Galaxy S 4 Active Original Android Development] baaldfg:
OK, this is the same error message I get. Therefore it doesn't seem to be caused by the NH2 baseband. On the 0806 (and before) this was working.

Is there an option in Android to prohibit roaming (not just prevent the data roaming, this option I know)? If I could prevent the phone from connecting to the foreign network it would be ok for me.

Best wishes, Christian
[Galaxy S 4 Active Original Android Development] olarf:
You can find an app in the Playstore (Roaming Control) that can do stuff like that (its build for people that live close to a border I guess) but it cost some Euros :( But you can test it for free for 7 days, maybe enough time to fix the bug in cm11 ;)
[Galaxy S 4 Active Original Android Development] O-T:
I have only Data roaming to select on/off.

Also tested with same result on all LTE/3G/2G setting.
[Galaxy S 4 Active Original Android Development] baaldfg:
Unfortunately the app roaming control doesn't do the trick. It can only disable/enable the data connection or put the phone into flight mode if on the wrong network. The phone still conntes to the wrong one ?
[Galaxy S 4 Active Original Android Development] olarf:
Ah to bad, so they just workaround it. Then to wait for the fix Wii be the only option I think.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] O-T:
0926, NE4

Quick Access band or tiles:

-enable WiFi

-enable BT

This set WiFi locked and refuse to shut down. In System Options the on/off button jump to On when set Off.

Same appearance reported 0918.
[Galaxy S 4 Active Original Android Development] olarf:
Not happen on NH2 (send via wifi while BT is also on, I also switch WiFi off an on)

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] Devo7v:
On 0922:

None of the hardware buttons vibrate when pressed. The "Vibrate on touch" option is enabled under Settings-> Sound. Any ideas?
[Galaxy S 4 Active Original Android Development] naveenmat98:
The hardware buttons can't vibrate haha. The settings are just there because of jf-common.
[Galaxy S 4 Active Original Android Development] Devo7v:
I guess my question then is can this be implemented for the Active branch? This was a nice feature from stock ROMs.
[Galaxy S 4 Active Original Android Development] 4cr0ph3t:
On version 09.27 on pushing history tab in dialer, force closes dialer.

I don't know if this happens in previous versions, as I haven't tried this before.
[Galaxy S 4 Active Original Android Development] olarf:
In 09.26 dialer history works. I will test 09.27 now.

Sorry, as 09.28 was already online, I try that one. I switch a lot around in the dialer without any problems. I can see history and statistic.

So please update to 09.28 and if it still happen, describe exactly what you do to crash the dialer.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm, stock roms vibrate when pushing hardware buttons? Sounds strange since ive understood that vibrating is a way to give haptic feedback when pressing a touchscreen button. So in stock rom it gives feedback that you know you have pressed an actual button :)? Sounds very Samsung to me...

Can it be implemented? Everything can be implemented. Just dont know how easily, id wager that in CM it is set up to dismiss vibrate when hw buttons are defined.

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

On 09.26, its working fine.
[Galaxy S 4 Active Original Android Development] O-T:
Tested today Manual Select telephony network;

Toast error msg. Only auto select

Affecting only latest jactivelte, or entire jf* family?
[Galaxy S 4 Active Original Android Development] 4cr0ph3t:
I updated to 09-28. Still a force close of dialer when I push the left bottom button to show the recent calls.

Tried a clear dalvic-cache and a clear cache, didn't do nothing.

Will try a clean install, when I got some time this week.

Till then I will use another dialer app from Plaistow.
[Galaxy S 4 Active Original Android Development] upD8R:
Running 2209, received a call this morning. As I needed to put the mobile away I switched on the speaker. It seems the mic turned off immediately, so the other site couldn't hear me. After turning speaker off, everything went back to normal.

Could anybody try this, please?
[Galaxy S 4 Active Original Android Development] naveenmat98:
Yes! This bug is also in my paranoid android build which inherits its device tree for cm. I thought it was isolated to paranoid android but looks like its not. :D
[Galaxy S 4 Active Original Android Development] Tazzmanien:
Yes, I have the same error on 2209 nightly NH2. Speaker is not working! :(
[Galaxy S 4 Active Original Android Development] Devo7v:
I understand, I don't think vibration should be enabled then. I have found a bug related to the hardware buttons on 09.28. When the screen is off, holding down the menu button

or

the back button causes the phone to wake up.

"Home button to wake" and "volume buttons to wake" options are disabled and "Long press back to kill app" is enabled under Developer options. I only just noticed it on 09.28 after updating from 09.23, it's very likely it occurred on 09.23 as well.
[Galaxy S 4 Active Original Android Development] olarf:
I can confirm the speakerbug still exist in 09.28 while this nightly is hungry for Batteries ;)

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] O-T:
1)

Lock screen - Screen security - Automatically lock = X sec

2)

Press pwr or dbl. tap Status bar to activate lock screen.

3)

Wait >X sec before press Home /Menu

Edit:

It is working as intended? (not sure) here since Official started.

If press Home /Menu <5sec after screen off, it will wake screen no matter what value of X.

Also recommend to check the latest link I posted some days back regarding merged/open CM11 changes. review.cyanogenmod.org filtered to exclude htc, sony, oppo, motorola,... related commits. I might have missed some project folders in use for jactivelte (@spegelius could fill in?) but really can't see anything new added the last week that's related to hardware buttons.
[Galaxy S 4 Active Original Android Development] spegelius:
I took a look about Menu and Back buttons waking the device. Didn't find any overlay's, only for displaying the home wake in menu options. But, on jactive keylayout/gpio-keys.kl:

key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 172 HOME WAKE
key 528 FOCUS WAKE
key 766 CAMERA WAKE
key 139 MENU WAKE
key 158 BACK WAKE

Soo propably changing MENU and BACK to something else than WAKE... i wonder if this can be done dynamically, like in conjuction with the Home Wake option in settings... well have to look into this when i have more time.
[Galaxy S 4 Active Original Android Development] Devo7v:
Just to recap:

Home button to wake: Disabled

Volume buttons to wake: Disabled

Volume buttons Playback control: Enabled

Automatically lock: 5 seconds after sleep

Power button instantly locks: Enabled

Kill app back button: Enabled

No matter how the phone locks, whether I double tap the status bar, press the power button, or wait for the phone to timeout (I've waited up to 5 minutes) the Menu button and Back button will wake the phone and show the lock screen. The Home button and Volume buttons will NOT wake the phone.

---------- Post added at 01:23 PM ---------- Previous post was at 01:18 PM ----------

Personally, I would either have independent options to wake the device for Menu and Back or I would have them permanently disabled. I find it a lot easier to accidentally hit the Menu or Back when pulling the phone out of my pocket and less so with the Home button. This is just a personal preference, it's really up to you and whatever is easiest to implement.
[Galaxy S 4 Active Original Android Development] 4cr0ph3t:
I found out, the force close of dialer app, was caused by a call log recovery I made from a backup made by 3c toolbox.

I deleted the recent calls list with another dialer app and everything is fine now.
[Galaxy S 4 Active Original Android Development] spegelius:
Last time i tested this, it was working fine. Ill do some retesting someday...

---------- Post added at 08:57 AM ---------- Previous post was at 08:55 AM ----------

Easiest is probably to disable Menu and Back WAKE altogether. To add individual options would need changes to Settings app and framework code and i dont know what CM devs think about that. One can always make a bug report to CM Jira and hope.
[Galaxy S 4 Active Original Android Development] O-T:
I was happy with Home /Menu button not wake screen and had the keys disabled since not remember. Options - Lock screen - Button action = Menu/Home off.

When ticked both ON they still don't wake screen if wait >5sec after lock/screen off.

+1 for [MENTION=3047491]Devo7v[/MENTION] discover unresponsive button settings System Options.
[Galaxy S 4 Active Original Android Development] spegelius:
Ok, im getting confused here: what works wrong way and what works ok? We are talking about waking the phone and unlocking, which are two different things. Currently, Menu and Back wake the phone. Also Home button if options is selected in Settings - Buttons. For unlocking, there are options for Menu and Home in Settings - Lockscreen.

In my opininion, only Menu and Back wake are jactive specific, others go to CM development. Unless we are forking, which im not going to do.
[Galaxy S 4 Active Original Android Development] O-T:
Button actions is unresponsive to hardware buttons when ticked on/off.

att. pic1

Disabled soft keys, still unresponsive.

Please note that I've mostly /cache +dalvik clear (dirty flash) since Official first. [MENTION=3047491]Devo7v[/MENTION] may have done a clean install if that matters.

Edit1:

Wake up buttons Home & Volume +- is responding to on/off setting.

Thanks [MENTION=3876105]spegelius[/MENTION]. I got lost in CM UI layout.
[Galaxy S 4 Active Original Android Development] spegelius:
Unlock options for Menu and Home seem to be working fine for me.
[Galaxy S 4 Active Original Android Development] O-T:
Me too. Edit1 last post.

Manual network search error isn't seen lately in i9505 CM11 thread, possibly only jactivelte. Any known bugs related to this?
[Galaxy S 4 Active Original Android Development] Grinface:
For me also the menu and back buttons waking up the phone while option is disabled. On opposite side, home button didn't wake up the phone while the option is enabled...

I'm still on version as of 09-22 (with a clean install)
[Galaxy S 4 Active Original Android Development] spegelius:
Dont know if theres open bugs about that. Id this doesnt happen on jflte, i wonder where the problem is. One possibility could be that the modem image on jactive is different and needs jactive specific RIL blobs. Last time i tried those, phone had serious problems...
[Galaxy S 4 Active Original Android Development] O-T:
Could someone perhaps binary compare modems?

GT-i9505 MODEM: I9505XXUGNE5

vs

GT-i9295 MODEM: I9295XXUCNE5

available from http://www.sammobile.com (region Germany)

GSM modem = modem.bin

LTE modem = NON-HLOS.BIN

Reccomend to check this thread about modems: [REF] GALAXY S4 (I9500/I9505) GSM / NON-HLOS - MODEM'S Collection (Odin/CWM/TWRP)

and "Phone INFO" from Play Store to identify bootloader. This post say its best when LTE modem version is same as bootloader,

[MENTION=5457071]Murthick[/MENTION] in this post

"...Flashing a modem doesn't trip KNOX as the modem file is official and unmodified.

The LTE modem doesn't have to match your bootloader exactly, it just has to match the same Android version. e.g. 4.4 LTE modem with 4.4 Bootloader, 4.3 LTE modem with 4.3 Bootloader and 4.2 LTE modem with 4.2 Bootloader. (With a few exceptions on 4.2)

This is how it works as I understand from personal experience"
[Galaxy S 4 Active Original Android Development] spegelius:
I dont know about binary comparison... if that can tell us the differences on function level then ok. But simply to check if they are different? Yes, they are, cant flash jflte modem to jactive, tried that.

Good info about bootloaders, have to read those later. I have KK bootloaders as i had NE5 rom installed few months ago, still the network search fails. I remember trying to get a log out of that error, but if i remember correctly there wasnt anything about it on logcat...
[Galaxy S 4 Active Original Android Development] spegelius:
Tried the speaker during call and mic does seem to be turned off. I'll have to check some things in kernel, other place could be the jactivelte/audio/snd_soc_msm_2x_Fusion3.
[Galaxy S 4 Active Original Android Development] O-T:
+1 no Handsfree mic in, only speakers sound out.

CM11 0926,

[ro.boot.bootloader]: [I9295XXUCNE4]

LTE modem: [I9295XXUCNE4] (NON-HLOS.BIN)

GSM modem: [I9295XXUCNE4] (MODEM.BIN)

According to 40 or more posts I've read in S4 modem thread this bootloader/LTE/modem combo is safe. It is not the only possible for i9295. Please read, remember you have a i9295 and select wisely because wrong combo can influence KNOX, WiFi and sound in addition to cell network reception.

Identify your bootloader (harmless) :

Terminal: getprop |grep -i bootloader

Samsung bootloader/modem/ROM letter ID - I've posted it earlier http://xdaforums.com/showthread.php?p=55386522
[Galaxy S 4 Active Original Android Development] allram:
Uploaded NH2 bootloader here, for those who want:

https://drive.google.com/folderview?id=0BwwLmYElvFOmM2NpaGdmWTBxTTQ&usp=sharing

Flash at

your own risk

, flashed it myself and it works. but i give no guaranties...

It might fix some bugs people are having? :)

edit: tell me if you want another and i can fix it :)
[Galaxy S 4 Active Original Android Development] spegelius:
I saw a post (maybe in general, cant remember) from someone saying that newer than NE5 bootloaders have KNOX. I dont know for sure as i have flashed only NH2 modem and dont have much knowledge about KNOX, but this post tells interesting details: http://xdaforums.com/showthread.php?t=2447832. Mainly the KNOX warranty void flag and not able to return to older non-KNOX bootloaders...

Personally my phone doesnt have warranty anymore so i just might try it, but then again not sure how this affects further development on it... not buying another one if this dies. If someone already has NH2, would be nice to hear some comments.

Edit: the post i mentioned: http://xdaforums.com/showpost.php?p=55313778&postcount=24
[Galaxy S 4 Active Original Android Development] allram:
I got "kernel is not seandroid enforced" in red text at boot screen after this (but everything works), for me it doesn't have anything to say since i don't have warranty anymore. But i don't see any difference either, so maybe people should just stick to their current bootloaders.

Seems like it is plenty of fixes to that, just reflash stock rom and then the text should be gone...

Some KNOX info
[Galaxy S 4 Active Original Android Development] 6783:
I can confirm. On ne5 stock I was able to downgrade to 4.2. With newer it's impossible.
[Galaxy S 4 Active Original Android Development] Tazzmanien:
XXUCNH2 and version nightly 2209

I have tested/tried Allram's NH2 baseband fix :)

Used Odin 3.09 - There was no issue during flashing - everything went well :)

Call's is working fine - On Speaker mic is not working. :(
[Galaxy S 4 Active Original Android Development] spegelius:
The issue with speaker is propably in the snd_soc_msm_2x_Fusion3 file. Had a look at the kernel and jf kernel's sound code is pretty much same with Active's kernel. I tried using snd_soc_msm_2x_Fusion3 same file from NH2 rom, which caused no audio during call and finally phone reset itself, propably ALSA failed because could not find matching section to direct the audio to/from. Comparing CM one to NH2 one reveals that the files are very different; different device sections and use cases. I'm trying to find matching sections and see if the actual enable sequences differ, i made some python code to parse the files and display differences. But that's quickly getting a big project so propably gonna try to manually seek the correct sections...
[Galaxy S 4 Active Original Android Development] moviecut:
A new nightly is up (20141001) after some days without a new build... Did someone already flash it?

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] allram:
Have you tried diffchecker.com? Might be useful :)