yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Android Development] NZStevenC:
I feel I might be encountering the end of this phone... I've gone back to WizCyan v3 and my phone is still getting hot and chewing through my battery within half a day. I'm wondering whether it's actually a hardware issue that I won't be able to fix.

What I've run over the last couple of weeks:

10 to 18 June: WizCyan v3 with OB4 firmware, modem and kernel. Was running CPU Tuner and in the final days encountered the high heat and battery usage issue

18 to 21 June: Stock I9295XXUDOE8 (KSA). Continued running CPU Tuner and the high heat and battery usage continued

21 to 22 June: Stock I9295XXUDOE8 (KSA). Ensured that CPU Tuner was not installed and the high heat and battery usage continued

22 June to date: Installed WizCyan v3 with OB firmware, OC3 modem and kernel (as the conversation here suggests OC3 is most efficient). Ensured that CPU Tuner was not installed and the high heat and battery usage continued

Oddly, despite me flashing the WizCyan ROM, OB firmware, OC3 modem and OC3 kernel, the Phone Info app is still showing OE8 bootloader. I'm not sure if that is to be expected given the flash history I've taken, or whether there's something I've done hasn't worked?

Last ditch effort here... I'm not sure whether there is any weird CPU config that is enduring my full system & data wipes and that there's anyway to calm it all down again. Any views here?

Or failing that... can anyone suggest a good ~5" Android device with SD card slot and decent firmware for stable radio performance and no CPU/heat issues? I think I'm done with Samsung.
[Galaxy S 4 Active Android Development] AtomicAardvark:
Hi Steven,

I use to get overheating when I am not on Wifi with 3G on. Especially when using Google Maps Navigation (I do not use my phone much for social sites and music). My battery would also drain quite quickly (up to -10%/h). This was on both 4.4.2 and 5.0.1 StockyRom.

I then flashed 5.0.1 WizCyan with OC3. I went further and installed Xposed with Wanam Xposed Lollipop...all good.

Then under Device Control (I think it comes with the ROM otherwise get in the Play Store) under Thermal Driver I have Core Control and MSM-Thermal enabled. She is running much cooler now and my battery is doing so much better.

I have only run this ROM for 3 days now, but I am very happy so far.

I hope this helps.

P.S. Jason, thank you for this ROM. I still need to try out ANT+.
[Galaxy S 4 Active Android Development] JASONRR:
Thanks, let me know how it goes
[Galaxy S 4 Active Android Development] JASONRR:
Heating issues are common with qualcomm devices which is why there are rumors that Samsung is planning to ditch qualcomm for exynos.

Generally the phone heats up when the processor is running. You can check if there are any apps installed that are running in the background causing the phone to heat up.Turning power saving mode from quick settings may help as this restricts cpu performance. Additionally if you want you can backup your internal sd card and do a phone factory reset (from settings-->backup & reset--> Factory data reset) then flash the ROM (without addons) and check if the heating issue is still present.
[Galaxy S 4 Active Android Development] NZStevenC:
Thanks for your advice. I just installed Device Control and at first use, I found that under Thermal Driver I had Core Control enabled and MSM-Thermal disabled.

Have enabled MSM-Thermal now so I'll see how I go :)

---------- Post added at 06:17 PM ---------- Previous post was at 06:11 PM ----------

Thanks. Whenever I've installed a new ROM I've used both "format /system" and "format /data and /data/media (/sdcard)" from the storage menu in CWM before flashing. Would that have achieved the same thing as a factory data reset?
[Galaxy S 4 Active Android Development] JASONRR:
Some apps and custom kernels (if installed) will leave some settings on the internal sdcard that will go away only when you either delete the app specific folder or wipe the internal sdcard. Taking a backup and doing a factory data reset is one way of clearing it.

Just recollected on a previous post on kitkat with respect to proximity sensor which could also be a cause of phone heating up and battery drain not sure if this is fixed in 5.0.1. http://xdaforums.com/showthread.php?p=59082854
[Galaxy S 4 Active Android Development] NZStevenC:
OK... so it seem that I can enable MSM-Thermal in Device Control and adjust the preferences to reapply on boot. However, when I reboot, the switch has reverted to off. I have the same issue as Paul Beetge here:

https://play.google.com/store/apps/details?id=org.namelessrom.devicecontrol&hl=en

Soooo... I did some hunting around around and located /sys/module/msm_thermal/parameters/enabled which contained a N. I edited it to a Y (and checked that it successfully saved) however after reboot, something reverts it to N agian :(

Sooooo... I'm wondering whether this setting might be the root cause of my issue and wondering what is forcing to N. I've just taken a full list of installed apps from Titanium and have attached. I made a categorised version of the same list so I can sense check which types of app might be making such a change. While I haven't had any other CPU controlling apps for the last few ROMs... I might start by uninstalling everything in the 'Managing my Phone' category (with the exception of ES File Explorer!) and seeing if that lets me set and keep the MSM_Thermal setting.

Any other ideas from anyone?
[Galaxy S 4 Active Android Development] NZStevenC:
Uninstalled...

Device Control 0.8.2 (org.namelessrom.devicecontrol)

File Tools 4.1 (cyb.satheesh.filerenamer)

GSam Battery Monitor 3.25 (com.gsamlabs.bbm)

gTabSiMiClock 2.6.6 (com.th.android.widget.gTabsimiClock)

Llama 1.2014.11.20.2330 (com.kebab.Llama)

Phone INFO 3.3.2 (org.vndnguyen.phoneinfo)

SMS Backup+ 1.5.8 (com.zegoggles.smssync)

Speedtest 3.2.12 (org.zwanoo.android.speedtest)

Terminal Emulator 1.0.70 (jackpal.androidterm)

Toggle Network Type 5.0 1.1.4.0 (com.cygery.togglenetworktype.xda)

Wakelock Detector 1.6.1 (com.uzumapps.wakelockdetector)

Then rebooted, then changed the value in /sys/module/msm_thermal/parameters/enabled to Y, then rebooted again. The value had been reverted and the date modified for 'enabled' updated to the boot time. So I suspect there is something happening at boot that is setting the value to N.

I had a look at the files in /etc/... and I don't see anything containing 'thermal' apart from the names of the following:

thermal-engine-8064.conf

thermal-engine-8064ab.conf

thermal-engine-8930.conf

thermal-engine-8960.conf

thermald-8064.conf

thermald-8064ab.conf

thermald-8930-qrd.conf

thermald-8930.conf

thermald-8930ab.conf

thermald-8960.conf

thermald-8960ab.conf
[Galaxy S 4 Active Android Development] JASONRR:
Unfortunately that is a kernel configuration which would need a custom kernel built from source. There is a test kernel posted by walter79 somewhere ahead which you can try and check (has some issues and ensure lockscreen type is ser to swipe before installing)

Edit: This is a informative thread that I came across on msm_thermal https://github.com/gokulnatha/GT-I9...n/devicetree/bindings/arm/msm/msm_thermal.txt

Also are you having weak cellular signal as this can also have an impact as the phone will constantly keep searching for signal. One way to debug is to switch network mode to either WCDMA only or GSM only (or maybe even turn on flight mode) to check if the heating persits.

Did you try turning power saving on?
[Galaxy S 4 Active Android Development] NZStevenC:
Thanks, just picked up your message on my way to work. Will try the network mode and power saving mode today, then perhaps a new kernel later on.
[Galaxy S 4 Active Android Development] NZStevenC:
Battery lasted 5.5 hours with power save mode switched on, wifi on and mostly stayed on GSM only. Still very hot. Then I flashed the hulk kernel, which was just as bad.

Then I decided to try flashing pure stock OB4 firmware/ROM... still had huge amounts of heat in power save mode and msm_thermal setting was N and I could not switch it on.

As a final try I've just installed pure stock 4.4.2 (NE4) to see whether that firmware along with CyanWiz 5.0.1 will behave itself.

Failing that... I checked out LG G4 and Huawel P8 in the phone shop this morning... both look good :)
[Galaxy S 4 Active Android Development] JASONRR:
Just one last trick. After you remove phone from charger, wait for 3-5 minutes then reboot your phone and see how it goes. If this does not work you can try the kitkat version from post#3 and check as well.
[Galaxy S 4 Active Android Development] NZStevenC:
On Thursday I thought I'd gotten somewhere with the KK firmware but as soon as I was off wifi and playing Spotify I was draining 40% an hour :( So I ordered a LG G4 (H815) on Thursday night and received it on Friday. I'm delighted so far.

Thanks to everyone who provided input in trying to iron out my i9295 issues :)
[Galaxy S 4 Active Android Development] Grinface:
[MENTION=5266778]JASONRR[/MENTION]: There's a file "WizCyan_LP_gpsv04_Update4_v02.zip" located at your GDrive. What is it used for?

Grinface
[Galaxy S 4 Active Android Development] JASONRR:
That was for V02 to remove the location notification and icon from status bar. This is already incorporated in version 03 in rom control under General UI.
[Galaxy S 4 Active Android Development] Chigga:
Phone calls not working

I've installed V03 but am now having issues with phone calls. When I make or receive a call, neither side can hear each other. I don't hear the phone dialling, but it does make a tone when the call connects. I've tried using a bluetooth and wired head set but I get the same issue. I've tested the mic by running recorder and it works fine. I'm using the I9295XXUDOB4 modem. Has anyone else had this issue?
[Galaxy S 4 Active Android Development] tofanpc:
happened after flashing stock I9295XXUDOD3 and when testing stockyrom, but bluetooth headset worked for me and was the only way to make/receive calls. fixed after reverting to UDOB4 bootloader, modem and v3 wizzcyan.
[Galaxy S 4 Active Android Development] tofanpc:
Photo studio has stopped working when trying to select Drawing. Tried all other edit tools and all are working.
[Galaxy S 4 Active Android Development] JASONRR:
Have you installed s-pen from addons?
[Galaxy S 4 Active Android Development] tofanpc:
yep. thanks again. that was the cause.
[Galaxy S 4 Active Android Development] JASONRR:
Beta Kernel Port Imperium

Anyone interested in testing a beta Kernel built from the S4 Imperium kernel sources having Kexec HardBoot support, FauxSound Audio/Sound Control support, SELinux set to "Permissive" and more features as stated in http://xdaforums.com/galaxy-s4/i9505-develop/kernel-imperium-ll-kernel-v1-0-t3058867

Edit:

Bugs: Same as Hulk kernel - PIN and Password lock does not work (Does not work with OE8 bootloader as well-need to figure it out)

New Thread created for Kernel and you can get it from http://xdaforums.com/galaxy-s4-active/orig-development
[Galaxy S 4 Active Android Development] JASONRR:
Firmware and modems

The 5.0.1 firmware and modems on my drive have been revamped, this is updated in OP as well

The firmware' now also includes the respective modems and the modems (modem.bin & NON-HLOS.bin) have been clubbed together in a single tar.md5 file for ease of flashing.

Link: https://drive.google.com/folderview?id=0ByY8uLVuRKD2QW9KNUlXN0RhLWc&usp=sharing
[Galaxy S 4 Active Android Development] wanakamura:
Hi I have constant problem with DCMProvider. It freeze quite offen. So I remove it manualy but it come back from :/

Help :)
[Galaxy S 4 Active Android Development] izeeqo:
Can anyone help me to tell me what Xposed works with this ROM please? And give me the link of the Framework and APK please? Thanks
[Galaxy S 4 Active Android Development] JASONRR:
Not sure but it has got something to do with categories / face detection used by Gallery or used by SHealth / GearFit.

You can delete it manually and wipe dalvic/art immediately and if this does not work then freeze it.
[Galaxy S 4 Active Android Development] izeeqo:
Jason, have you got a list of applications that can remove or freeze without any problems?
[Galaxy S 4 Active Android Development] JASONRR:
All of the known one's are already removed from the ROM and the useful one's included in the addons
[Galaxy S 4 Active Android Development] wanakamura:
I deleted file APK but it shown again :/ don't know how :) this is why I wrote.
[Galaxy S 4 Active Android Development] JASONRR:
My observation in lollipop is that the app stays loaded in memory even after uninstalling until you reboot your device (maybe this is the way it is handled by ART).

Did you delete the entire folder and reboot into recovery and wiped cache and dalvic /ART cache and check?
[Galaxy S 4 Active Android Development] ZeroZorro:
[MENTION=5266778]JASONRR[/MENTION] Did you format Sytem/Cache and/or Data with the F2FS filesystem?

I am planning to install

[KERNEL][TW][Lollipop][I9295][Linux 3.4.108] Imperium LL Kernel port for Active Intl followed by

[ROM][I9295][5.0.1] Super WizCyan [debloated, deodexed, rooted + Addon Package]

After re-reading most of the posts i figured those steps:

* Flash Multirom TWRP 2.8.5 and make backup of current stock ROM

* Format Cache (f2fs), Data (f2fs) and System (ext4)

* Flash SuperWiz CyanROM

* Flash Imperium Kernel

* Run Aroma Addon Package if needed (i do)

* Reboot...

Any suggestions about this?

Thanks...!
[Galaxy S 4 Active Android Development] JASONRR:
Though the imperium kernel supports f2fs, please remember that the ROM is based on stock TW that does not support f2fs.

You will need to flash imperium kernel after the ROM and no need to flash TW-Modded_SGS4A-5.0.1-stock-OC3_150613.zip as that is only a stock kernel to support OC3 modem for working wifi.
[Galaxy S 4 Active Android Development] ZeroZorro:
Thanks [MENTION=5266778]JASONRR[/MENTION] , i changed the steps and will flash ROM before KERNEL.

F2FS is not an option for this combination at the moment so filesystem remains EXT4.

Removed TW-Modded_SGS4A-5.0.1-stock-OC3_150613.zip from the to-do list, don't get that completely but i presume that the Imperium Kernel will take care.

#Crossedfingers
[Galaxy S 4 Active Android Development] JASONRR:
Just an update on f2fs ...

f2fs is working only for cache and data. System has to be in ext4, if you format /system to f2fs, it won't boot. You can get benefit of f2fs for /cache and /data where most of the read/write takes place
[Galaxy S 4 Active Android Development] wanakamura:
Hi J.

I have a problem with power consumption. My com.android.contacts. android process.acore and com.sec.android.provider take to much power. and work constantly over 1h also other android processes take lot of effort to drain my new battery to zero in less than 10h.

I made cache cleaning but it help only for some time. HELP :)
[Galaxy S 4 Active Android Development] izeeqo:
have you got Kitkat version or Lollipop ?
[Galaxy S 4 Active Android Development] tofanpc:
used v3 until yesterday when suddenly this or this problem appeared again.

Reset and clean install doesn't fix it so I installed kk I9295XXUCNE5. After 3 calls the problem appeared so I recorded a log when I was in a call. Also when someone calls me and I answer, neither I or the other person are hearing anything. But if I start my bt headset the sound is there.
[Galaxy S 4 Active Android Development] JASONRR:
Is the attached log taken while on WizCyan ROM and if so then is it on 4.4.2 or on 5.0.1?
[Galaxy S 4 Active Android Development] tofanpc:
with 442. but the problem it's the same with wizcyan or 501. If you want I can flash wiz and then I'll take the log again.
[Galaxy S 4 Active Android Development] JASONRR:
On a quick look I found a couple of errors in the log. One relates to a service disabled in V3 WizCyan 5.0.1 (in the kernel) and a repeated error related to SCover which does not apply to our phone which is strange - null pointer exception on com.android.phone.PhoneGlobals.isCoverClosed. I feel the error would be related to SCover one as you do not have the issue with Bluetooth calls.

If I could get a log on WizCyan 5.0.1, I could check it out. Also check in /system/etc/permissions if there are any xml with cover in it.
[Galaxy S 4 Active Android Development] tofanpc:
No sign of cover in files name in that folder. Flashed v3 and ob firmware/modem and then this logs
[Galaxy S 4 Active Android Development] JASONRR:
This seems to be stock and not WizCyan ROM and I cannot find any errors in the logs attached.

If you are having issues with the ROM and send me logcat while the error is encountered I can try and fix it. You could also try the custom imperium kernel to check if the issue still persists on stock 5.0.1
[Galaxy S 4 Active Android Development] tofanpc:
Both logs we're taken when the problem occurred. If you look at timestamp, the second one was taken like this: start log recording, initiate call and no sound in phone, started bt headset and the sound is there, stoped bt and no sound in ear or back speaker, stoped log record.
[Galaxy S 4 Active Android Development] JASONRR:
Could not find any errors in the logs, will take a look again when I have some more time. In the meantime can you either flash the stock kernel from my drive or the imperium kernel and check if the issue persists.

Edit: Please format boot manually before flashing the custom kernel

Also would like to know if you have any wake locks disabled or have frozen any apps or services
[Galaxy S 4 Active Android Development] tofanpc:
Flashed imperium with boot format. Problem is still there.

flashed clean v3 rom without add-ons. 3or4 calls we're OK but then that incall silence appeared.

log taken with v3,some add-ons and some restored apps. When recording log I was making a 10 sec call with no sound on both sides. If I'll start bt when this problem occur I will be able to make normal conversation.

LE: just tested something. I give it a try to oc2-phn firmware with modem files included. same problem. but I made a new log (the one with rar extension). After dialing the number and clicked on Dial I hear the sound for connection and after that silence. when the recording key became active I started to record the conversation. after 15 seconds I stoped everything (call and log recording) and I checked the .m4a file saved in phone memory. Everything is saved there: voices from both sides.

Added a log taken with OB4 firmware and good audio on both sides.
[Galaxy S 4 Active Android Development] JASONRR:
Just a few questions

- Have you installed Drive Mode and if so have you also installed TTS voices. Try uninstalling Drive Mode if installed as well and check.

- Can you confirm if you have not installed any audio mods as audiopolicy states that dualmic_enabled

I AudioPolicyManager_legacy: getAudioPolicyConfig: audioParam;dualmic_enabled

- Have you disabled wakelock for contacts, Telecom, TeleService, phone, incallui
[Galaxy S 4 Active Android Development] tofanpc:
none of this. just flashed clean v3 rom. without addons. sometimes I have incall sound and sometimes I don't. just like if I had addons or restored apps....or stock rom. interesting that it's not only my problem. And i don't think it's a hardware problem.
[Galaxy S 4 Active Android Development] moviecut:
Hey JASONRR! I just flashed the newest modem from poland (I9295XXUDOF6 -> Link!) and now i have problems with wifi not working...in your first post, you have this in the addon-discription: "Added wifi fix for NH1, NH2, NE5 & NF2 modems"

will that also work with newer modems, like the OF6? Or should i reflash an older modem or wait for a new fix from you ;)

Thank you!

EDIT: I fixed the problem by flashing your imperium kernel v2.4! Now the new modem and wifi are working!
[Galaxy S 4 Active Android Development] JASONRR:
The incall sound issue is there in stock firmware as well or only with WizCyan ROM? Also is this issue faced in speaker mode as well or only with the front speaker? As you said that you were able to record the call even while there was no sound indicates that the issue is with the phone (hardware or software) Which app did you use to record?

Not many users have reported this issue and therefore I would say that this seems to be some isolated issue. I could not find anything in the logs provided (maybe it is beyond me:confused:) and would suggest that in Philz recovery there is an option to format firmware and firmware-mdm, try formatting both and flash the entire firmware and check if the issue still persists.
[Galaxy S 4 Active Android Development] ZeroZorro:
Does anyone have a problem with the auto-dim/brightness? Mine is way too dark and I can't change settings in Powersave settings in this ROM (I read somewhere that would do the trick)

Maybe it is not rom related but I think it is cause no problems on Stock ROM.

The problem occurs not always...maybe it takes a very long time to trick the adjust event?
[Galaxy S 4 Active Android Development] JASONRR:
Powersaving is enabled by default in the ROM and this is mentioned in the OP under tips section. You can use the powersaving quicktile to disable it.
[Galaxy S 4 Active Android Development] tofanpc:
Issue appeared after flashing wizcyan (never on stock before). After that is on stock, wiz or stocky (not tested cm). Both speaker and front speaker affected. Recorded with wizcyan default recorder in phone mode. When flashing stock, the issue apeear after 2 or 3 days of normal usage. With wizcyan the issue is there after first boot.

PLease, can you provide some steps to format/flash entire firmware?
[Galaxy S 4 Active Android Development] JASONRR:
I am on WizCyan ROM ever since and I have not faced this issue.

The firmware and mdm-firmware are just virtual folders and not the actual firmware. These can be formatted using Philz Recovery by going to format -> custom format --> then choosing firmware and firmware-mdm individually.

To flash firmware

1. Download the firmware from Sam Mobile

2. Extract the downloaded file.

3. Run Odin as an Administrator.

5. Power off your phone and boot into Download mode with volume down + power button (release power button on vibrate)

6. Connect your phone via USB. Wait until Odin detects your phone.

7. Click on AP then browse to the extracted .tar.md5 file.

8. Leave Auto-Reboot and F.Reset Time checked and Click on Start

9. Wait till it finishes, you phone will boot automatically (may take some time)

If you are prepared to wipe your internal SD card (beware to back it up) then you could try the Factory data reset from settings-->backup and reset. This is also known to solve corruption issues.
[Galaxy S 4 Active Android Development] tofanpc:
yep....that's the steps I made every time I flashed stock. (except format firmware from recovery). I'll do this again tomorrow with UDOF6.

LE: same thing with latest firmware. but I tryed something. Flashed clean V3 (format cache, data, system, firmware from recovery) and with no addons the sound was missing after 3 calls. But I've noticed some hot point right under flash led. I presume that there is the processor located. So I took off the back cover and with finger I felt the sdcard slot unusual hot. Removed the sdcard from him and from then all calls are with sound. Tested the sdcard and it passed every test. Will use the phone without card for now to see whats happen next. :)
[Galaxy S 4 Active Android Development] JASONRR:
Great!!! It seems that you somewhat figured out the problem. From your post it seems to be some speaker connection issues when the phone heats up with the SD card in the slot.

You could try the imperium kernel with my setting attached to this post as the phone does not heat up as much for me with these settings. Just extract default.profile and replace it with the file in /data/.imperium folder or copy the contents from this one to the one already available.

P.S. I have power savings turned on which is good for battery and performance is also good.