yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] spegelius:
Not yet, but now: https://www.diffchecker.com/gjhtzcwi :). Same results as with Meld (Linux diff sw) i use for diffing. As you can see, there's too much differences: sections are named differently and are in different locations...

But anyhow, i got the problematic section narrowed to

SectionDevice
Name "Speaker DMIC Endfire"
Comment "Dual MIC Endfire Tx device"

EnableSequence
'SLIM_0_TX Channels':0:Two
'SLIM TX7 MUX':0:DEC2
'DEC3 MUX':0:ADC4
'ADC4 Volume':1:100
'DEC3 Volume':2:67.7%
'SLIM TX8 MUX':0:DEC3
'DEC2 MUX':0:ADC5
'ADC5 Volume':1:100
'DEC2 Volume':2:67.7%
'MICBIAS3 CAPLESS Switch':1:1
'MICBIAS4 CAPLESS Switch':1:1
'TX3 HPF cut off':0:MIN_3DB_150Hz
'TX4 HPF cut off':0:MIN_3DB_150Hz
'TX5 HPF cut off':0:MIN_3DB_150Hz
'ES325-AP Tx Channels':0:eek:ne
'Internal Route Config':1:3
'ES325 TX1 Enable':1:1
EndSequence

DisableSequence
'SLIM TX7 MUX':0:ZERO
'DEC3 MUX':0:ZERO
'DEC3 Volume':1:0
'ADC4 Volume':1:0
'SLIM TX8 MUX':0:ZERO
'DEC2 MUX':0:ZERO
'DEC2 Volume':1:0
'ADC5 Volume':1:0
'MICBIAS3 CAPLESS Switch':1:0
'MICBIAS4 CAPLESS Switch':1:0
'TX3 HPF cut off':0:MIN_3DB_4Hz
'TX4 HPF cut off':0:MIN_3DB_4Hz
'TX5 HPF cut off':0:MIN_3DB_4Hz
'Internal Route Config':1:6
'ES325 TX1 Enable':1:0
EndSequence

ACDBID 11:2

EndSection

The corresponding section in NH2 config should be Call Samsung Dualmic SPK:

SectionDevice
Name "Call Samsung Dualmic SPK"
Comment "Call Samsung Dual Tx device"

EnableSequence
'SLIM_0_TX Channels':0:Two
'SLIM TX7 MUX':0:DEC2
'DEC2 MUX':0:ADC5
'ADC5 Volume':1:100
'DEC2 Volume':2:67.7%
'SLIM TX8 MUX':0:DEC3
'DEC3 MUX':0:ADC4
'ADC4 Volume':1:100
'DEC3 Volume':2:67.7%
'MICBIAS3 CAPLESS Switch':1:1
'TX3 HPF cut off':0:MIN_3DB_150Hz
'TX4 HPF cut off':0:MIN_3DB_150Hz
'TX5 HPF cut off':0:MIN_3DB_150Hz
EndSequence

DisableSequence
'SLIM TX7 MUX':0:ZERO
'DEC2 MUX':0:ZERO
'ADC5 Volume':1:0
'SLIM TX8 MUX':0:ZERO
'DEC3 MUX':0:ZERO
'ADC4 Volume':1:0
'MICBIAS3 CAPLESS Switch':1:0
'TX3 HPF cut off':0:MIN_3DB_4Hz
'TX4 HPF cut off':0:MIN_3DB_4Hz
'TX5 HPF cut off':0:MIN_3DB_4Hz
EndSequence

ACDBID	35:2

EndSection

But with latter settings, no sound either direction when speaker is on. There's other Mic definitions to try if someone is interested ;) (don't copy Name and Comment, only other stuff!). I'm calling it a day
[Galaxy S 4 Active Original Android Development] olarf:
I flashed the 10.01 PAC nightly which based on the same cm sources and it runs fine and provide the highest antutu score I ever had on cm11 (29993). So it should be fine.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] O-T:
This is CM11, not PAC thread?

Antutu score CM11 0913 was same http://xdaforums.com/showthread.php?p=55417686 if that's more appealing than known issues in Telephony.

Last 3-4 nightly has fixes for macloader, man cam focus, sqlite race, bash patch, clickjacking superuser. Mostly string cleanup, APN/vendor addition and translation. Still waiting for CM approval of the massive Bluetooth commits added Sept 23-25.

Thanks [MENTION=3876105]spegelius[/MENTION] [MENTION=4630187]allram[/MENTION] for digging into jactivelte side of the story.

Oh, and 'switch to last used app' is working with hardware buttons when Menu is set to this for long press. Home long press is occupied for last app list.
[Galaxy S 4 Active Original Android Development] mythi:
Dude its all cm11 based and this is a development thread anything related to cm11 is discussed here i don't see the point of you being so ...:eek:
[Galaxy S 4 Active Original Android Development] naveenmat98:
Exactly. Just because the problems originate from a ROM other than cm doesn't mean its irrelevant. We're all using the same device tree and whatever problems found on another ROM using the same device tree will most probably exist in cm too.
[Galaxy S 4 Active Original Android Development] noskojv:
gt-i9505 cm11 m9
[Galaxy S 4 Active Original Android Development] olarf:
Beside from what already was stated, it was a simple answer about the question if 10.01 cm nightly would be worse a try. So my answer was 100% cm11 related.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] snadge:
So I flashed the latest recovery.img from the current sources. It still has the stupid bug where the device won't turn on if the USB is plugged in (stuck in off charge mode). Even better, now I can't run adb when the device is in recovery either. :good:

So that leave me kinda wondering if there is an "official" recovery for this device. Someone correct me if I'm wrong, but it seems like there kinda isn't.

What is everyone else usingfor a recovery currently?
[Galaxy S 4 Active Original Android Development] olarf:
Cm11 provide a official recovery (6.0.51 they provide actually I think). But it has the same problems :) I think (but I'm not sure) that I could switch on my phone while it was plugged with 6.0.47 but I'm not sure.

At least there is a Setting to flash always latest official cm recovery when updating cm11. This option is in dev settings but I prefer to keep my cwm as long as it works good. (More or less :) )

Beside this the 6.0.51 switch the phone off when you want to restart it. All over those days the ROM has less bugs then the recovery ;)

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] Tazzmanien:
I am running CM11 0110 and NH2 everything works except the "on speaker" functinality

I am not sure that i get this right. Since I am still interested to get the speaker working - Is there a way to get the "on speaker" functinality working again?

Do i have to downgrade the firmware fx. NE5. and then reflash CM11 newest build or what can i do?

Thx..
[Galaxy S 4 Active Original Android Development] O-T:
ADB functionality depend on kernel version 3.10: http://review.cyanogenmod.org/#/c/72131/

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

CM11 jactivelte 0110 has kernel 3.4 and this is probably the kernel in CWM built after the commits I linked. [MENTION=4630187]allram[/MENTION] or [MENTION=5150212]mythi[/MENTION] can confirm/decline this for the CWM they have built.

Reboot ceased to work July 11, between 6.0.5.0 and 6.0.5.1

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

The thing is that CWM menu item is still 'Reboot' :confused:

I agree with you that ADB need to work in CWM. This is last resort to undo messed up OS before download mode flashing.
[Galaxy S 4 Active Original Android Development] olarf:
It is a Problem in CM11 and they work in it but the Problem seems to be located in an area that offer a Billion of options so it will need a while I guess. You can't fix it with up/downgrade firmware or change the modem, sorry.

gesendet via PAC 4.4.4 (10.04)
[Galaxy S 4 Active Original Android Development] spegelius:
No solution for the speaker yet. I tried some settings in sound config, but only managed to disable sounds altogether. So need to dig more later, possibly try other RIL blobs also...
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm seems i got speaker mic working; i swapped some MUX channels to Speaker DMIC Endfire-config from the DMIC Enfire-config and now mic works. But i'm still bit worried that the dualmic isn't working properly... oh well, as long as it works :). Uploading build to test here: https://www.dropbox.com/sh/cfyyhwwm8pgrg4o/AAA_04KHr3LUZvr2X7iV9nO3a?dl=0 (mobile connection, takes a while...). Repo sync done this morning.

Edit: this build also has fix for wrong time in boot. CM devs haven't accepted my pull request to TheMuppets so it's not on offical builds yet.
[Galaxy S 4 Active Original Android Development] spegelius:
A question for you users: should Menu and Back keys wake the phone? In this regard Active differs from it's regular sibling as it has actual buttons instead of capacitive buttons and in I9505, one can't wake the phone with Menu and Back since those keys are disabled when screen is off (at least that's how it's on S3, don't have S4 to test).

Being able the wake the phone with Menu and Back might have some uses, but one inconsistency raises when user disables screen wake by Home button; Menu and Back are still active and the behavior is inconsistent.

Easiest solution is to disable wake for Menu and Back altogether. Other, one that needs more implementation and probably consent from CM devs is to make Home wake disable function to disable wake for Menu and Back also. Adding individual settings for Menu and Back is too much clutter in my opinion, but is still and option.
[Galaxy S 4 Active Original Android Development] Devo7v:
I've thought about this for awhile and as much as I'd like to be able to individually set the menu and back button to wake the phone, I don't think it's necessary at all. We can already set the home button to wake and the menu and back button can already be configured to do things when on the lock screen.

There are only two cases where I think it could be beneficial:

Reduce wear on the home button and power button.

Set a long press of the menu or back to turn on/off the flashlight. It was a nice feature in TouchWiz, but I don't think CM had the code to do this.

I recommend just disabling wake for the menu and back button, it's easier and there's only one super specific case where it's find it useful that may not even be possible.
[Galaxy S 4 Active Original Android Development] spegelius:
Yeah i'm thinking that disabling is probably the best choice for now. If there's demand for more options then we'll make a feature request to CM.
[Galaxy S 4 Active Original Android Development] O-T:
Wake buttons status currently:

Pwr =always screen off/wake.

Home or Vol+- =System - Buttons - toggle possible

Menu or Back =will wake ONLY if pressed < 5sec after screen off. After 5sec they are unresponsive.

When phone is in pocket an unintended pressed physical button will wake screen when Menu/Home/Back are enabled. And as screen time usually is the winner of battery consumers it makes sense to disable Menu, Home, Back wake.

I do support [MENTION=3047491]Devo7v[/MENTION] point of wear to few buttons and system options provide toggle to avoid this.

Current options are fine with me.
[Galaxy S 4 Active Original Android Development] Devo7v:
That's not what I'm seeing. I have both Home to wake and volume buttons to wake disabled. If I press the power button to lock the phone, no matter how long I let it sit there with the screen off, as soon as I press the back or menu button, it wakes the phone up.

Just to be sure, I locked the phone and let it sit on the table for about 5 minutes. As soon as I pressed the back button the phone woke up and the lock screen was presented. Unless I have done random setting turned on somewhere that I'm not aware of, this seems like a bug.
[Galaxy S 4 Active Original Android Development] spegelius:
New build, cm-11-20141006-UNOFFICIAL-jactivelte, on dropbox https://www.dropbox.com/sh/cfyyhwwm8pgrg4o/AAA_04KHr3LUZvr2X7iV9nO3a?dl=0. Menu and Back wake disabled + repo sync.
[Galaxy S 4 Active Original Android Development] Tazzmanien:
[MENTION=3876105]spegelius[/MENTION] - thanks for the ROM with the speaker modification - it works like a charm. I have chosen to use the ROM on daily basis. :)

A question:

- Will this solution be a part of a new CM build?

Thanks for making this possible :)
[Galaxy S 4 Active Original Android Development] Devo7v:
The keys work properly now, great work. Will this change get pushed to official CM? If not can you create a flashable zip of just the modified file so that when CM updates I can use the official updater and just fix the keys afterward? It would probably save you a ton of bandwidth on your dropbox account too.
[Galaxy S 4 Active Original Android Development] mythi:
two heads better than one ... is there any difference between these and your build ??
[Galaxy S 4 Active Original Android Development] silberstein242:
None whatsoever; I just plan to build daily to keep us up to date with the CM11-tree. Somebody upthread asked for a more recent build and I figured I'd help with what I can.
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm, i made another build, this time i'm using CM10.2 kernel and props. Seems to work, but still no compass. Makes me go hmmm... oh well, now it's evident that the kernel is not the culprit. No point using this older kernel, it's even slower than the new kernel.

Oh and i got the device props fixed; now https://github.com/spegelius/device-props_jactiveltexx/tree/cm-11.0 should work as part of the roomservice and build shouldn't complain about libtime_genoff.
[Galaxy S 4 Active Original Android Development] vanyel:
Dirty flashed your latest build. Wiped cache and dalvik... looks pretty good so far. no hiccups yet... :)
[Galaxy S 4 Active Original Android Development] 6783:
Have been using this rom for a week, everything works good. Just one annoing "bug", people complaine that they don't hear me good, like low volume. Is there any solution for it?
[Galaxy S 4 Active Original Android Development] allram:
Have tried both spegelius and silberstein's newest builds.

Both of them have problems with notification sounds? clean install on both roms, Spegelius's 5.march build is working fine tho :/
[Galaxy S 4 Active Original Android Development] snadge:
Yesterday I tried to build using the latest roomservice.xml, and I couldn't get it to build unless I reverted the following commit: working cm11 props

I tried copying the files referenced in the above commit from jf-common. It starts the boot animation, but corrupts display then reboots. Didn't care enough to try and figure out why.

My direction sensor is working fine (compass, gyros, accelerometers both linear and gravity). Notification sounds also seem to be working fine. For anyone who hasn't updated their baseband for a while, I know this can cause issues with at least the direction sensor. I'm running I9295XXUBMK3 on mine.
[Galaxy S 4 Active Original Android Development] sam.crowther:
[MENTION=3876105]spegelius[/MENTION], dirty flashed over 03.05 (secondary rom) and compass is working in google maps.
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm, what kind of problems? Volumes or something else? I usually turn off all other notifications sounds except phone and sms...

My bad, some of the changes from my CM10.2 kernel tryout had slipped on the commit. I reverted those, currently building to see if it works...

About the compass; only thing i've tried the compass with is some old 3D comapss i had a Titanium backup of. I'll try with maps. I have MH2 baseband, maybe it's timeto upgrade.
[Galaxy S 4 Active Original Android Development] allram:
Even tho i change notification sounds, They all play the same sound. Atleast with the 19.march build...
[Galaxy S 4 Active Original Android Development] mythi:
[MENTION=3876105]spegelius[/MENTION]

I don't want to fill your mind with silly things ...but been trying to port the latest slim bean weekly with one of your latest build 19th one to be exact , i followed my tradition of copying files messing up with bootclasspaths etc ... but the ported rom DOESN'T boot , the issue isn't with the boot.img but in the modules/libs because if i use the rom with your new image it boot up but when i copy the modules/libs it sticks at the gs4a bootsplash ...logcat isnt working at this state (adb shows device offline) so i can't debug anything also when i use the older rom as a base for the modules it boots normally every single function works !!! ... so i wondered wether the new camera changes broke dirty porting or something since you only changed in the camera department :confused: hope you help me find a solution :angel::D:D .

thanks
[Galaxy S 4 Active Original Android Development] spegelius:
That's strange, the kernel and the props should be the same as with the previous build. All the camera stuff is built into the java stuff, which is used only after the camera app has started.

Then again, the newer build was done from new clone of CM repos so it is possible that something has changed in jf-common device tree... the fact that it doesn't go past the bootsplash would indicate something wrong with bot.img, but could be a kernel module thing?
[Galaxy S 4 Active Original Android Development] mythi:
Ohh that's strange ... MMMMMMMMMMM... i thought the same thing but i don't think so since using the old modules with the new boot.img works like a charm ... could you make a repo sync and build a build and post a link (if you are free no pressure) i will try again .
[Galaxy S 4 Active Original Android Development] spegelius:
Newest build available in Google drive. Built today.

---------- Post added at 09:33 PM ---------- Previous post was at 09:31 PM ----------

Oh and i tried updating my baseband to MK2 (only one i could find from these forums?). Odin said everything flashed ok, but phone still shows MH2...
[Galaxy S 4 Active Original Android Development] mythi:
BaseBand ...i have mk3 if u wish i will make an odin flashble pda with the basehand and non-hols.bin

and pm the link to you .
[Galaxy S 4 Active Original Android Development] sam.crowther:
I've got working MK3 for odin if you want it...
[Galaxy S 4 Active Original Android Development] spegelius:
Yes please, i'd like to test if updating the baseband fixes the compass.

Nope, i can't update OP. Latest roomservice.xml is here: https://github.com/spegelius/manifests/tree/cm-11.0
[Galaxy S 4 Active Original Android Development] allram:
The sound problem i had a few days ago, have become better, now i get vibration on t.ex email notifications.

I run ML3 baseband and compass i working fine here for me :)
[Galaxy S 4 Active Original Android Development] spegelius:
Both speaker fix and keys change are in review state: http://review.cyanogenmod.org/#/c/74708/ and http://review.cyanogenmod.org/#/c/74567/. Let's see how they work out.
[Galaxy S 4 Active Original Android Development] O-T:
I have same button response as nightly described in my last post, ( > 5sec) . Also when Home set to wake. Dirty flash may play a role? Others done clean flash can share experience.

The build.prop date of cm-11-20141006-UNOFFICIAL-jactivelte is 20141001. :confused:

Not tested call mic yet.

---------- Post added at 08:14 PM ---------- Previous post was at 08:11 PM ----------

Not sure if man. cell provider search issue is only i9295 or also higher up in cm device tree. Not seen much of it reported in i9505 thread.
[Galaxy S 4 Active Original Android Development] spegelius:
Might be due to dirty flashing... dunno. Build prop date is because i didn't make clean before building. Saves time.

No idea about cell provider search. Logcat doesn't show a thing.
[Galaxy S 4 Active Original Android Development] O-T:
Superuser - Options crash:

is fixed in upstream cm commit latest nightly.

Anyone tested encryption of phone?
[Galaxy S 4 Active Original Android Development] FORC3:
Same question over here. Can i encrypt my device when using a custom Rom? Do i lose any significant options (ability to use recovery?) when encrypting my device?
[Galaxy S 4 Active Original Android Development] Grinface:
Just read, S4A in official CM Milestone release :) Thanks Spegelius

http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m11

But there's a note:

What does it mean in detail? Is the M release based on code as of 09/30, so Mic and button wakelock problem still present?

Grinface
[Galaxy S 4 Active Original Android Development] O-T:
... so interested in keeping this thread alive according to Original Development Forum Rules:

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

"That's fine. But as rule 15 states, then keep this thread on topic. If you want to talk about other ROMs, take it to the suggested General section. Maybe a lot of other users want to try this and discuss their experience and issues...instead they find a couple of pages of people talking about other ROMs. So please keep this thread on topic. [MENTION=3125148]KennyG123[/MENTION] (Moderator)

"

Other ROMS forked/ported/piggyback ... from CM have features added or modified. It makes it hard to identify root cause.
[Galaxy S 4 Active Original Android Development] mythi:
I am going to contact a moderator and prove you that it is legimate , I see nobody (users I mean) care about our questions which are on topic of dissucion , you won't understand .
[Galaxy S 4 Active Original Android Development] allram:
[MENTION=5150212]mythi[/MENTION]
[MENTION=2997552]O-T[/MENTION]

Guys, everything that can help us make the jactivelte more stable / Fix bugs is welcome here. Sometimes it's good to know that the problem ocours across multiple forks. Just then can we be sure that it isn't some build fault.

And same way around, if the problem ocours on different forks, and they fix it. We can also try to use the same fix for CM11 base. Questions regarding base cm11 / pure cm11 forks i see no problem in discussing here, but discussing other rom related stuff does not belong in this thread, but in the respective rom thread.
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
Sorry to come off like that. I'll be quiet now.
[Galaxy S 4 Active Original Android Development] O-T:
A quick survey in i9505 CM11 thread confirm same manual search 'Network operators' error as i9295 CM11.

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

Not sure how to report this in upstream CyanogenMod as root cause is pointing in that direction when CM11 i9295 and i9505 have same issue.
[Galaxy S 4 Active Original Android Development] spegelius:
Ill see if i can get a hold of CM devs in irc and ask how bugs are reported with nightly builds. If i remember correctly, theres different reporting procedure for nightlies...
[Galaxy S 4 Active Original Android Development] spegelius:
CM Jira for Nightlies: https://jira.cyanogenmod.org/browse/NIGHTLIES.

There seems to have been an issue about network operator problem (among others): https://jira.cyanogenmod.org/browse/NIGHTLIES-86?jql=project = NIGHTLIES AND text ~ jflte, which was moved to here:

https://jira.cyanogenmod.org/browse/CYAN-5379 as it was a problem in M10 releaseon jflte. So what i got out that is that updating modem fixed most of the No Service problems people were having, but apparently Network Provider search is still open, couldn't find a ticket about it...
[Galaxy S 4 Active Original Android Development] O-T:
A separate thread has been created in Q&A:

Q&A for [ROM][Official Nightly][Android 4.4] CyanogenMod 11.0 for SGS4A (int'l)

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

My previous posts (attacked by some) stay aligned with moderators and xda rules to keep this thread clean and focused on debug and keep progress of pure CM11 jactivelte.
[Galaxy S 4 Active Original Android Development] O-T:
Network operator scan not working can be traced back to beginning of August on M8 snapshot and still an open issue two months later in M11. Description of the issue in CYAN-4902 (with exception of different qcom device) is exactly how it still appear on jactivelte. 4902 got an added comment about this reported Oct 11. Issue is assigned to invisiblek.

https://jira.cyanogenmod.org/browse/CYAN-4902

Some issues take time to solve. This one may have impact on the phone bill when automatically connected to Network operator without option to choose the one offering best price. Any way to elevate this issue?
[Galaxy S 4 Active Original Android Development] spegelius:
Well for jactive (and propably for jflte) the problem started when new K RIL and blobs were introduced. So propably something not implemented/broken in RIL-implementation... The above Jira-ticket is made for HTC M8 so it's not jf-family only problem. Most likely something in Qualcom support code that's not up to date or something.

Dunno how to elevata, propably post more detailed info about the problem
[Galaxy S 4 Active Original Android Development] 2stardiver:
Is there option or app to use volume up button as led light like in original rom?
[Galaxy S 4 Active Original Android Development] O-T:
System settings - Lock screen - Custom widgets ENABLE.

On lock screen swipe down from clock. Swipe left where you have + sign.

Add any widget... or the one you ask for - Torch.

Remove custom widget by pressing beside on same page.

OR

Lock screen - Button actions - long press Home/Menu/Back.