yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9506 Android Development] DualJoe:
No change. Still no ipconfig.txt.

Just to make sure. The swipe process itself does work here as well (swipe stripes). It just doesn't create any words on screen. It neither shows suggestions nor does the cursor move in any way. As if dictionary would be empty. Dictionary does work for tapping though.

Logcat Main:
E/TemperatureHumiditySensor( 768): mCompEngine is NULL
E/TemperatureHumiditySensor( 768): mCompEngine is NULL
W/GestureStroke( 9438): [0] drop stale event: 961,188|615 last: 973,174|631
W/GestureStroke( 9438): [0] drop stale event: 953,190|627 last: 973,174|631
W/GestureStroke( 9438): [0] drop stale event: 950,190|630 last: 973,174|631
I/LatinIME:LogUtils( 9438): Dictionary info: dictionary = UserHistoryDictionary.en_US.dic ; version = ? ; date = 1409179841
I/LatinIME:LogUtils( 9438): Dictionary info: dictionary = personalization.en_US.dict ; version = ? ; date = 1409179841
I/LatinIME:LogUtils( 9438): Dictionary info: dictionary = PersonalizationPredictionDictio ; version = ? ; date = 1409179841
I/LatinIME:LogUtils( 9438): Dictionary info: dictionary = userunigram.en_US.dict ; version = ? ; date = ?
I/LatinIME:LogUtils( 9438): Dictionary info: dictionary = PersonalizationPredictionDictio ; version = ? ; date = 1409179495
I/LatinIME:LogUtils( 9438): Dictionary info: dictionary = ? ; version = 26 ; date = 1351062238
I/LatinIME:LogUtils( 9438): Dictionary info: dictionary = UserHistoryDictionary.de.dict ; version = ? ; date = 1409179495
I/LatinIME:LogUtils( 9438): Dictionary info: dictionary = contacts.en_US.dict ; version = ? ; date = ?
E/TemperatureHumiditySensor( 768): mCompEngine is NULL

Logcat System:
W/InputMethodManagerService( 768): Ignoring showInputMethodPickerFromClient of uid 10041: com.android.internal.view.IInputMethodClient$Stub$Proxy@43c6b348
W/InputMethodManagerService( 768): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@42f34af0 attribute=null, token = android.os.BinderProxy@42ac1088
[Galaxy S 4 i9506 Android Development] pille1:
Are there a lot of important bugs?
[Galaxy S 4 i9506 Android Development] solk2:
Strange. Please post full logcat from boot up, turning wifi on, connection to AP, turning off and then on.

On my phone swipe works as expected. Swipe line, suggestions and typing words. Please post full log with swipe too. Also which languages is set on keyboard?
[Galaxy S 4 i9506 Android Development] solk2:
This known problem to all recent qualcomm devices.
[Galaxy S 4 i9506 Android Development] solk2:
Not much as I know. Mostly with camera functions. Would be greate if someone could test latest nightly with HDMI. Coz there was some changes.
[Galaxy S 4 i9506 Android Development] WonkyYew:
Has the auto-brightness bug been fixed?
[Galaxy S 4 i9506 Android Development] DualJoe:
Maybe a lib is missing that is shipped with gapps. I haven't installed gapps yet. I've completely wiped the system and installed 28082014 from scratch. No change though.

I currently need to have stock installed. I will come back to that later. My languages for keyboard are 'de' and 'en-us'.
[Galaxy S 4 i9506 Android Development] solk2:
There was no auto-brightness bug. There was bug with manual brightness that caused bootloops. Bootloops fixed. But there still bug that brightness not sets back after reboot.
[Galaxy S 4 i9506 Android Development] solk2:
Maybe. I don't know. Try to install gapps will see if it helps.
[Galaxy S 4 i9506 Android Development] :
arter97 kernel

can you fix [MENTION=4898097]arter97[/MENTION] kernel please :fingers-crossed:
[Galaxy S 4 i9506 Android Development] DualJoe:
Yes, works. When i swap 'libjni_latinime.so' it works properly indeed. Looks like there's something wrong with the built-in one.

Can you add a soundengine like Faux123 or something? Doesn't need a frontend yet. Sysfs interface would be ok. Its just the sound is too loud for quiet places sometimes. I could need a -50% here...

Would also be great if you could implement AndreiLux color engine so we can on-demand raise the minimum OLED voltage (RGB 4,4,4) to get rid of that purple lag and get a proper sRGB profile. They say it brings it on par with I9300. Then we have the option for both worlds, pitch black or purple lag-free.

Also, i've injected an 'ipconfig.txt' from my i9300. But doesn't change anything. Still asks for password every time when trying to connect...
[Galaxy S 4 i9506 Android Development] diegodu27:
i know you ve been busy, but i would like to ask you something, there's a kernel module that adds "knock on" feature (From LG G2) while screen is off, do you think it would be possible to make a flashable zip to this Mod ? :)
[Galaxy S 4 i9506 Android Development] DualJoe:
Bugs (just for informational purpose):

- Something's wrong with compass/cLock. Turning over the device to disable alarm doesn't work. When using 'GPS Status' the compass has very low sampling/update rate.

- Sound quality on speaker is very low (low bitdepth/high aliasing) with high white noise (hiss). DSP Manager doesn't work at all.
[Galaxy S 4 i9506 Android Development] diegodu27:
Information porposes aswell:

Theres something wrong with the last temasek nightlies since after flashing new updates, my phone doesnt even boot, and when i try Solks kernel, it works just great, so dear Solk, you should take a look at last Temasek nightlies :)
[Galaxy S 4 i9506 Android Development] solk2:
I'll see what I can do.
[Galaxy S 4 i9506 Android Development] solk2:
clock uses gyroscope. Now compass. So that's different problems. And I don't have issues with compass updates or gyroscope in any sensor testing apps.

Also I don't have issues with DSP manager its all works fine on my phone.

What bootloader, baseband you have?
[Galaxy S 4 i9506 Android Development] pille1:
Is Bluetooth working on latest nightlies??
[Galaxy S 4 i9506 Android Development] awicks:
I have now been running 11-20140828-UNOFFICIAL-ks01lte for 44 hours and Bluetooth is working fine. I upgraded from a previous version through CM Updater.

Andy
[Galaxy S 4 i9506 Android Development] pille1:
I am only experiencing a minor problem: When I reboot the device, I have to introduce the wifi password again... Is there any solution for this?:confused:
[Galaxy S 4 i9506 Android Development] DualJoe:
1) I'm on 4.4.

2) DSP Manager itself does work indeed but equalizer for speaker has no effect here (or i did something wrong). I've found V4A (Viper4Android) in the meantime. It brings its own driver and works properly so far. When you lower the output volume of the speaker you can hear the bad audio quality more clearly (i also checked without V4A). I'm not sure if this is a software problem at all. It could be cheap DACs or something as well.

3) cLock shaking (alarm off) does work but not turning device over. Maybe i need to calibrate something first or so... I did so with 'GPS Status' already though.

4) I'm currently trying to derive a kernel from cm-hlte to ks01lte as well to hopefully learn something. Theory is to compare the stock kernels variant defconfigs to determine different hardware/drivers and swap them in the cm-hlte repo with i9506 ones so i hopefully end up with a kernel that can be still updated on cm-hlte upstream. I hope i will not fry my phone.

How did you start creating this kernel? Any critical/dangerous parts worth mentioning?
[Galaxy S 4 i9506 Android Development] stxfreak:
at the moment the best or only method seems to be to flash a previous version, you're safe if you take the last snapshot set your wifi and upgrade that version via cm updater.
[Galaxy S 4 i9506 Android Development] DualJoe:
It's probably somehow related to this:

09-01 21:39:28.945 E/wifi_gbk2utf(766): g_pItemList is NULL
09-01 21:39:29.175 E/wpa_supplicant(26022): wpa_driver_nl80211_driver_cmd: failed to issue private commands
09-01 21:39:29.175 E/WifiStateMachine(766): Unexpected BatchedScanResults :null
09-01 21:39:29.175 E/wpa_supplicant(26022): wpa_driver_nl80211_driver_cmd: failed to issue private commands
09-01 21:39:29.875 E/ConnectivityService(766): net.tcp.usercfg.wifi not found in system properties. Using defaults
09-01 21:39:29.875 E/ConnectivityService(766): net.tcp.delack.wifi not found in system properties. Using defaults
09-01 21:39:29.905 E/ConnectivityService(766): Unexpected mtu value: android.net.wifi.WifiStateTracker@42368e68

Maybe we can inject it manually into the database with setprop. I will take a look tomorrow if i can find and compare it with a working setup.

Edit: That value is neither set here nor on another CM11 system (where wifi is working). Maybe that's not the bug... Someone with working WiFi password should check 'getprop net.tcp.usercfg.wifi' as well.
[Galaxy S 4 i9506 Android Development] solk2:
Its not set. Please give me full logcat from boot, turning on WiFi, connecting and turning off and on.

Also I've tried equalizer on speaker on any volumes. Didn't hear any issues. Equalizer works and I clearly heared that. The only minor issue was that volume was resetting to max.

Maybe you have issue with offloaded music (aac and mp3). I tried flac music in Apollo. Try to set audio.offload.disabled to true.
[Galaxy S 4 i9506 Android Development] solk2:
Tried low volumes and didn't hear any noises. As describe above it may be issue with offloaded audio.

My kernel is based on hltes and includes all updates that they have.

I will try one more time alarm gestures in different variants.
[Galaxy S 4 i9506 Android Development] babyplex:
Hi guys.

First post on this and I really wanna feedback on this big issue I've been having on both CM11 port as well as SPL roms. Both are awesome and quick roms that captivate the CM11 experience and advantages but have an issue of not being able to boot back up once the phone is switched off or rebooted 2 days after installation.

I have a post on this which also captures the steps I have taken to zone down on the cause of this problem. I'm no developer but for a layman like me, it would seem to really have something to do with the Knox bootloader protection.

Posting on my experiences as follow:

http://xdaforums.com/galaxy-s4/help/i9506-bootloops-2-custom-roms-t2858956#post55192059

For now, I'm sticking with OEM Rom which has no issues shutting down or rebooting up to 5 days now. :good:
[Galaxy S 4 i9506 Android Development] solk2:
If you use early version or m8 snapshot then this most likely caused by manual brightness setting. Latest nighties don't have this issues.
[Galaxy S 4 i9506 Android Development] solk2:
Tried turning device over to stop alarm and it works on my device. Which cm version you are using and which baseband exactly?
[Galaxy S 4 i9506 Android Development] :
Can You Fix arter97 kernel error is that you can not call and mobile data if you Bover help with anything you can tell me please
[Galaxy S 4 i9506 Android Development] DualJoe:
Wouldn't it be better to factory reset the latest build on your device? You can probably face the problem much better on a live system locally.

Then there's probably something wrong on my side. Maybe my build was too old (22082014). Offload audio disable didn't change anything. Will try DSP again later.

I've seen other people complaining about the same. It's probably related to the high volume issue. I will check headphones later as well. It could be general hardware problem or mixer/resampler issues. I will sample/illustrate the aliasing once I'm on my desktop system again. It's maybe not critical but it's much worse than other systems. It's a very high 'noise floor' (low SNR - Signal-to-Noise-Ratio).

I want to go for a custom kernel. More schedulers, oc/uv, cortex optimized toolchain and such. Mostly simple kang stuff. Maybe i fork your stable kernel later but first i want to migrate/port it myself. Not sure if I'm ready for that yet though.

I'm now on 02092014 (from 22082014) with baseband I9506XXUCNF3 and it seems to work now somehow. I have to turn the device 2-3 times sometimes though. It does not work as good as CM11 on S3. The update rate on 'GPS Status' seems back to normal now (on par with S3). I will test it some more. Do another calibration and such...

Edit: Hmm, there's also a new baseband I9506XXUCNH2 now. I guess i will flash that as well.
[Galaxy S 4 i9506 Android Development] solk2:
Problem that I don't have this issue even after factory reset what I was doing a week ago. So the only reason why could it happen could be coz of cwm recovery 6.0.4.8. I have 6.0.5.0.

Maybe it coz I increased stock speaker volume a bit. I'll revert volume to stock and we'll see what it will be.

You can make your own kernel.

Sensors indeed behave sometimes strange. But the problem that polling is set by HAL. And HAL is binary blob which shipped with stock ROM. I'll update blobs from this new release next week. Maybe they will work better.
[Galaxy S 4 i9506 Android Development] DualJoe:
Hmm, as far as i know cwm should be completely independent.

Do you have anything else in /persist folder? I've seen some people with WiFi problems missing a wifi firmware file there. My /persist is as good as empty indeed. I've tried different language (en-us) and static wifi settings in the meantime. No change... Will try different APs, password, wifi mode (b/g/n) and factory reset with latest build next.

localhost persist # ls -lR
.:
drwx------ 2 root root 4096 Jan 1 1970 lost+found
drwxr-xr-x 3 root root 4096 Jan 3 2014 usf

./lost+found:

./usf:
drwxr-xr-x 2 root root 4096 Jan 3 2014 epos

./usf/epos:

Good idea. Every additional DSP (digital signal processor) could be a potential culprit.

Btw, did you implement some kind of 'smart cover' function yet? Sometimes i have the feeling it reacts when i open the cover especially when i look if alarm was cleared (by turning). Not sure if it interferes here maybe.
[Galaxy S 4 i9506 Android Development] pille1:
Is the wifi password bug still present?
[Galaxy S 4 i9506 Android Development] DualJoe:
Some people have it, others not...
[Galaxy S 4 i9506 Android Development] pille1:
Not working here :(
[Galaxy S 4 i9506 Android Development] solk2:
Thats the way it have to be. All firmware files lies in /system/etc/firmware /system/etc/wifi /firmware /firmware-modem /system/vendor/firmware.

But CWM could be problem. You are right. It is not affecting running ROM. But it can install newer ROMs uncorrectly coz CM updates inpar with recovery. So maybe they've changed update-script a little so older CWM like 6.0.4.8 not executing it correctly and not showing error. So thats why people that update thru cmupdater and have recovery update checkbox set don't have this issue.

Nope. It's not volumes. Its audio effects. Looks like offloaded effects cause some troubles with some formats. I've finally reproduced sound glitches on my phone but only while playing aac. Fixed in newer nighties.

Yes. There is some support. But I don't have smartcase so I can't tune positions for this to get it working correctly. If you can help it will be awsome.
[Galaxy S 4 i9506 Android Development] solk2:
Sorry. But I don't have much time for now to fix others kernels. Maybe things will change in future.
[Galaxy S 4 i9506 Android Development] DualJoe:
I don't have any special smart case. Just a simple vertical flip case. It works properly on stock rom so i guess its ok. I have no clue how it actually works though. I cannot replicate the function "by hand" (holding off sensors and such).

I can help you to tune it if you tell me how (sysfs?) but i hope in the end i'm also able to turn it off completely as i personally don't really like that function in general.

Is the CWM 6.0.5.0 somewhere to download?
[Galaxy S 4 i9506 Android Development] solk2:
Just uploaded here.

To fix smart case I need just to know where I need to move drawable area and its borders. Basicly when you install new version just pm me about non fitting edges. Or just photo.
[Galaxy S 4 i9506 Android Development] DualJoe:
Hmm, i guess we are talking about different things here. You probably mean cases with a "hole" in the cover for dial functions (pickup, hangup). I don't have any one of these.

I rather meant the function that when you open the cover it unlocks automatically (turns display on).
[Galaxy S 4 i9506 Android Development] solk2:
I see. Well then can you post logcat when you close and open yours case. Maybe I can get it work.
[Galaxy S 4 i9506 Android Development] DualJoe:
There's nothing in the logs. It's nothing that should be implemented anyway...

The primary question was if there is something like a "smart cover (open)" function in CM11 already that could interfere with alarm-off gestures (turning device). I noticed several times that alarm goes off (and device unlocks) when i open the cover.
[Galaxy S 4 i9506 Android Development] solk2:
Yes. There is. But I don't know if it interferes with alarm. I think its just cm alarm bug caused by device unlocking. So cover works correctly or not (device locks and unlocks as it should)? And what about WiFi after recovery update?
[Galaxy S 4 i9506 Android Development] DualJoe:
Actually, no. When i open the cover the device does not unlock. That's why i asked if there is something implemented. Its just these strange side-effects with alarm and in very rare cases it seems to work properly nevertheless (then its kinda confusing and i'm always wondering: "Wtf, why is the screen on? Did i unlock the screen? Is something wrong with my home button or did i press the power button accidentally?). :D I will test it some more later especially with alarm. It did work very reliable on stock rom (unlocking) so its maybe just a matter of tweaking.

Not tested yet. Will flash cwm now and test new rom later.
[Galaxy S 4 i9506 Android Development] solk2:
Try to experiment with touchscreen. echo "clear_cover_mode,0", 1, 2 to /sys/class/sec/tsp/cmd . And tell when it will work most stable. I'll set this setting on boot then if it helps.
[Galaxy S 4 i9506 Android Development] DualJoe:
I can't notice any changes. Doesn't react at all when opening/closing the cover.
[Galaxy S 4 i9506 Android Development] solk2:
Hmm. Try echo "1" > /sys/class/sec/sec_touchkey/flip_mode . Maybe this will work. Or maybe with combination with previous ones.
[Galaxy S 4 i9506 Android Development] DualJoe:
Still nothing. CWM V6.0.5.0 didn't help either with WiFi.
[Galaxy S 4 i9506 Android Development] boart:
Noone else got the error or at least has a solution for it??

"unfortunately the process com.android.systemui has stopped".

I already deleted dalvik, factory reset, wiped all.... No success so far:(
[Galaxy S 4 i9506 Android Development] mezo91:
Try redownloading the rom.
[Galaxy S 4 i9506 Android Development] boart:
Thank you. It seemed to work, but the problem still occurred :(
[Galaxy S 4 i9506 Android Development] mezo91:
Will give you my md5 to check with it. What gapps do you use? Maybe thats what causing the problems.

---------- Post added at 07:52 PM ---------- Previous post was at 07:48 PM ----------

Here is md5 a36aec6bf5036cb6a7ebb8cd6cfee675

And this is the gapps that I use. The full modular one.

http://xdaforums.com/showthread.php?t=2397942

Wipe data wipe cache wipe dalvik flash cm11 flash gapps and report back.

I hope this helps.
[Galaxy S 4 i9506 Android Development] boart:
It still occurs. I really dont know how i can solve that :( especially when the rom works on your devices.
[Galaxy S 4 i9506 Android Development] diegodu27:
I'm getting a black screen when I lock my phone, do you have the same problem? If not, what's your bootloader? 4.3 one?
[Galaxy S 4 i9506 Android Development] boart:
Yes, that happens too. Next to the error message i mentioned. I don't know what boot loader i have. I used the pre rooted Version from DeHawks 4.3. I also flashed his 4.2.2 rom again, but it didn't help :/
[Galaxy S 4 i9506 Android Development] mezo91:
4.3 bootloader.
[Galaxy S 4 i9506 Android Development] diegodu27:
So you don't have a black screen when you lock it?
[Galaxy S 4 i9506 Android Development] boart:
I think he means it STAYS black. Although he tries to wake up the device... at least i did understand it that way.
[Galaxy S 4 i9506 Android Development] mezo91:
Try using 4.3 bootloader of you desperately need it. Sometimes bootloader fixes things.
[Galaxy S 4 i9506 Android Development] faffaz:
FC

problem with com.android.systemui. Screen going black and staying black. Redownload of rom, and full-wipe didn't help. Oh, fc in settings app also.
[Galaxy S 4 i9506 Android Development] mezo91:
Is your bootloader 4.3 or 4.2.2? If 4.2.2 we can assume that this bootloader is what causing problems as from the reports received.
[Galaxy S 4 i9506 Android Development] tomogo:
Hi,

I have a same issues:

1. problem with com.android.systemui. Screen going black and staying black. My bootloader is 4.2.2

2. I'm not able to open security settings

3. Not working menu button

4. Min frequency is 1.7GHz
[Galaxy S 4 i9506 Android Development] boart:
First installing original 4.3 (so 4.3 boot loader) solved the problem with system.ui!!
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
Had the same problem. Tap the "problems?" button in bottom right corner of the main view. There's a preferences option available.

Any news on the audio jack problem?
[Galaxy S 4 i9506 Android Development] mezo91:
Im sad to say I went back to tw rom until kind dev can fix these bugs.

Im here for testing mr [MENTION=5291759]solk2[/MENTION]
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
I took a Titanium Backup myself and am also ready for testing. Until then I keep using this ROM, but at some point I will need my audio jack and then I need to do something else.
[Galaxy S 4 i9506 Android Development] mezo91:
the bugs that concern me the headphone jack and the cpu min speed lock. thats what i meant.

as for TB i just put the tb folder in internal memory and restored from there.
[Galaxy S 4 i9506 Android Development] dridri85:
Two issues for me :

- CPU is stuck at 300MHz, everything is extremely laggy

- No sound in headphones, sound still plays in speakers
[Galaxy S 4 i9506 Android Development] solk2:
Looks like I found problem. I am using gapps and passwords restoring from google so I don't have this problem. There was missing option in wpa_supplicant_overlay.conf (update_config). Try today's build. It will be available in 3 hours.

Looks like I need to buy a cover. Then I'll try to fix it.
[Galaxy S 4 i9506 Android Development] DualJoe:
Yep, works properly here now as well. Good work!

Just a minor problem but every time i update the rom the cwm asks at reboot to fix root. No matter what i choose on next boot SuperSU asks for the same ("su binary must be updated"). That's kinda weird since addon.d properly holds the SuperSU script that should keep the su binary.
[Galaxy S 4 i9506 Android Development] solk2:
You don't need SuperSU on CM. You can remove it and I think your problem will go away. Maybe thats coz su binary could be in blacklist.
[Galaxy S 4 i9506 Android Development] DualJoe:
Maybe i should give 'Superuser' a chance again indeed. Its just, i once had (well known) problems with it on some apps like 'Call recorder' and it was solved with SuperSU (like other people confirmed as well).

I haven't tested it lately but i've never used call recorder a lot anyway. On the other hand there's a call recorder built into CM these days that just needs to be enabled by system.prop or something.
[Galaxy S 4 i9506 Android Development] TechTune:
Great port, thank you.

No wifi issues or system crashes, but I can't get on my network.

It shows that I'm connected and 3G/LTE works for packets, but not calling and texting. That's weird right?

So I've been reading and flashed 4 different modems/basebands, still nothing.

I'm downloading the stock 4.4 update now, check that one and head back to CM11 If everything works out.

M