yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] kofe:
Hehe, thought u would get rid of me?! No chance! :p

I've thought of something. I've copied the nwk_info.db u provided for me for my old S3 in same folder location, and surprise: the fast_dormancy wakelock dropped to couple of minutes (30-40) per a battery cycle, compared to 2-2.5 hours before :D

And now after i`ve copied the nwk_info.db file the Fast dormancy app from playstore works :D

Anyway, now i have another problem, and i wanted to ask you and anyone who knows: i am experiencing signal drops :( I get almost one drop per hour... Could it be related to this nwk_info.db file? I`ve tried changing the modem to a newer one, but no luck. I even tried another rom (still AOSP) and still same result... What else can i do?
[Galaxy S 4 i9505 Original Android Development] davtse:
more likely to be a modem problem. I havent experienced any signal drop, but then again i'm on tw, not aosp.
[Galaxy S 4 i9505 Original Android Development] fabiienb:
I just want the txt please

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] Formhault:
I was kind of hoping that these powerhouse smartphones no longer do that... thing with their antennas when the signal is low :) :cyclops: :( .
[Galaxy S 4 i9505 Original Android Development] Formhault:
You lazy moth... Here's some jaypegs.
[Galaxy S 4 i9505 Original Android Development] Formhault:
Kofe, I'm keeping an eye out for when our carrier pushes a new one OTA, so until then, hold on tight to it XXUEMKF (GSM only, I don't give a crap about LTE and neither should you).
[Galaxy S 4 i9505 Original Android Development] fabiienb:
Thanks, I have a problem with it I have 900mhz stock and default !!! I don't know why

I don't have same voltage 50 less

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] Formhault:
What I use is default -50mV (for all frequency steps). Have not encountered any issues for a pretty long period of time.
[Galaxy S 4 i9505 Original Android Development] fabiienb:
Stock / default I have this :

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] Formhault:
Well... Perhaps your phone is not JFLTEXX? I know mine is JFLTETMO, since it came with a T-Mobile boot animation, but I treat it as a JFLTEXX regardless. The voltages may be different, although the SoC is the same so WHAT THE HELL.

Or... perhaps it's the ROM...? But then again, the SoC is the same so WHAT THE HELL.

Are you sure those are defaults? Cause I've been going haywire on this "Load defaults" button and my values are not matching yours :confused:.
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
These are (or at least should be) the correct defaults for CPU. I too own the jfltetmo variant.
[Galaxy S 4 i9505 Original Android Development] Formhault:
I have no idea what phone I have, by the way. All I know is it's a I9505 that came with a seemingly T-Mobile branded firmware. So I went on to assume it's a jfltetmo AND a jfltexx at the same time. Regardless... I hear running jfltetmo ROMs on jfltexx and vice-versa ain't gonna hurt so...

Oh and [MENTION=4325945]ktoonsez[/MENTION] do the CPU / GPU voltages differ across the different I9505 models out there (jfltetmo, spr, vzw etc.)?
[Galaxy S 4 i9505 Original Android Development] fabiienb:
Yes it's default I dont' touched voltage...

What's the difference into jftexx and jfltemo?

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] Formhault:
Two radiofrequency bands for the 4G differ. So the jfltexx has two more (or less, I don't really know) 4G bands than the jfltetmo (or the other way around).

You live in France. The difference between jfltexx and jfltetmo does not concern you :D:D:D. Nothing to worry about.
[Galaxy S 4 i9505 Original Android Development] fabiienb:
Oh ok thanks so for the voltage what I can do?

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] Formhault:
Could you be a bit more explicit what the problem really is? Cause you didn't really give any specifics...

Oh and it should be brought to your attention that this website sports a "THANKS" button. :good:
[Galaxy S 4 i9505 Original Android Development] fabiienb:
The problem is I don't know what is the default voltage for my cpu, and when I push every gov my phone sod by the settings of the cpu, now I just can load default....

I go to bed now, I will see tomorrow if my phone rebooted...

Thanks

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] Spacemonkie4207:
Anybody live in the Kitchener/Cambridge/Waterloo area?
[Galaxy S 4 i9505 Original Android Development] Mussels84:
i was going to say the only time i've seen battery calibration matter, was when changing between different capacity batteries.

had one phone that went from extended to normal and had reboot issues, but a calibration fixed that.

---------- Post added at 05:11 PM ---------- Previous post was at 05:09 PM ----------

i get -0.4% an hour as well

3G, wifi on. fast dormancy off.

use wakelockdetector (advanced mode!) or betterbatterystats and find out where the drain is. for example the 4.4.2 GE rom i'm on, has issues where NLPcollector wakelocks screw battery really hard... so i disabled the wifi location assist stuff to fix it. 'bad' battery life rom is suddenly great.
[Galaxy S 4 i9505 Original Android Development] davtse:
i wish calibration actually fixed it... about giving up after a month.. the battery still goes down at about the same rate as the stock battery, and then when it hits 1-2% it stays for a longggg time. lol
[Galaxy S 4 i9505 Original Android Development] N!KE26:
Which kernel version on KT should I flash with CM11 I9505?
[Galaxy S 4 i9505 Original Android Development] Tylog:
Aosp 4.4

Tapatalk Team SlimRoms
[Galaxy S 4 i9505 Original Android Development] Formhault:
Well... the default voltages for your CPU should be the ones you get after loading defaults... :confused:
[Galaxy S 4 i9505 Original Android Development] -sandro-:
OK so this is what I did I set an alarm two hours before the actual alarm :D I took the phone off the charger and kept 3G data on. I have the apps I don't use greenified. The ones that are with sync on (push notifications only, no background downloads/refresh) are whatsapp, gmail, facebook messenger, twitter, earthquakes. I lost 4% in 2 hours, the screen was off all time as you can see and the signal was high (full bars about -70dbm). Explain to me what it's draining the battery now :! This is when the phone was steady in my room sleeping. Imagine the loss when I move or drive. The only thing odd to me is msm_hsic_host.

I have SRV profile and balanced reloaded script set.
[Galaxy S 4 i9505 Original Android Development] Mussels84:
screenshot from WLD in advanced would be more helpful. make sure to not let it sleep uninterrupted to get a proper idle (i have my LED disabled at night, for example)
[Galaxy S 4 i9505 Original Android Development] hawkerpaul:
Audiomix seems to be the culprit.

I've heard reports that turning off "Touch Sounds" and "Screen Lock" sounds can cure it, but I'm not convinced, as this usually cures "AudioOut", but perhaps this is different now we are on 4.4, so it may be worth you giving that a try for now.

Also, if you have Viper installed, make sure you are using the current version (2.3.2.2)
[Galaxy S 4 i9505 Original Android Development] -sandro-:
That wouldn't explain why on Wi-Fi the drop is about 0.4%/h. I will try wakelock detector
[Galaxy S 4 i9505 Original Android Development] -sandro-:
What wakelocks did you control? During these two hours did you get any email/notification/anything? when I see your stats it seems to me like the phone has been in airplane mode LOL

UPDATE: end of the day on 3G data only (full bars always with 30 minute drive) battery is now at 3%, Screen on time: almost 2H...ridiculous.. less than half that you what you get. I think the only explanation is the network that has different settings, there's no other way to explain it. Even though from the service mode I do see the connection status going DCH->FACH->PCH so fast dormancy does work. Anyway if I remember correctly having fast dormancy enabled on the phone should give fastdormancy wakes locks (but saves a LOT of power on the MODEM) but I don't see any :| and the app "fast dormancy i9300" doesn't do anything since KK. Did maybe Samsung change how fast dormancy is enabled and I have it off thus the high drain?
[Galaxy S 4 i9505 Original Android Development] andyjg247:
Anyone find that the toast setting is fixed on enabled?
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
I literally NEVER use airplane mode. As you can see from the shots I only lost 2% over night off a full charge, which was nearly 7 hours on standly with nothing but LTE on the entire cycle.

This was based on light to moderate usage with your basic tasks, including web browsing, texts, Hangouts, Facebook, music, tethering, etc..

I Always leave auto syncing of apps ON with no additional mods installed, just Greenify for apps I rarely use and a fairly decent amount of RAM consumption for some of the apps I frequently use. I did receive some notifications over the course of my run but still slept like a baby though.
[Galaxy S 4 i9505 Original Android Development] -sandro-:
6H of screen on data, I'm seriously laughing (a mental breakdown LOL :D). Anyway I'm really starting to think wakelocks have nothing to do with the drain I have, it's the network and the ROM (KK GE) that doesn't have fast dormancy and I can't seem to enable it!

Let's not talk about the fact that you get more SOT on LTE than people do on Wi-Fi
[Galaxy S 4 i9505 Original Android Development] Matt-24:
What ROM are you using?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
Sadly, you may just be right.. It quite possibly could just be due to your network. Then again, BBS could help in me having a much better analysis on this. Care to pm me some screens?

EDIT: And don't even get me started on WiFi LOL! :D

Mahdi (4.4.2) v2.4 running Sleeping Dragon Dual Core Test profile.
[Galaxy S 4 i9505 Original Android Development] -sandro-:
Tonight I'm gonna leave the phone on 3G idle on another network that seems to have other settings and see the results.

The ROM you mentioned is CM11 based? The profile only uses 2 cores with any task?
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Ya, I just noticed it too, it will be fixed in next release :good:
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
No. Mahdi is based on straight AOSP.

Yes, the profile utilizes only 2 cores.
[Galaxy S 4 i9505 Original Android Development] -sandro-:
Well that could definitely help in battery life. I wonder if this kernel I could use only two cores only when NOT on wifi :P

Can you try force the network on 3G and see if with the screen off (after opening a web page maybe to trigger data transfer) you get fast dormancy (or something similar with "FD") kernel wakelocks?
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
No need to. As I mentioned previously, I along with many others are already plagued with this wakelock but it doesn't have a HUGE hit on battery for me.
[Galaxy S 4 i9505 Original Android Development] -sandro-:
I didn't ask thinking it is the cause, I don't have fast dormancy wakelocks and that's bad, it means FD is not on while on the network I know it's enabled. As I said on GE KK I can't find how to enable it. I asked many devs and nobody helped me
[Galaxy S 4 i9505 Original Android Development] davtse:
Check if you have the nwk.dB file in /data/data/android.something.telephony

If you have the nwk.dB file you can still enable fast dormancy. If you don't, I think you can copy the nwk.dB file from TW. It doesn't work for full aosp ROMs although it might work with GPE ROMs. This works for sure on TW ROMs, both 4.3 and 4.4(leak)
[Galaxy S 4 i9505 Original Android Development] track909:
I have a problem with this and others kernels under KK 4.4

I have a i9505 with new bootloader and new baseband XXUFNA5

With AOSP roms when phone is in power off charging don't work.

On screen there is a static battery image with circle freezed.

Otherwise, in TW roms charging in power off works well.

I think that this is a kernel problem.

Is it right?
[Galaxy S 4 i9505 Original Android Development] -sandro-:
Unfortunately that has no effect. I went back to 4.3 where FD is working but nwk.info.db is identical to the 4.4.2 one! Basically to have it ON you don't have to have a row about your network, if you want it off you need to create a row and set it to ON. Something must have changed on 4.4 GE :( Are you sure FD is working on 4.4 TW leak?
[Galaxy S 4 i9505 Original Android Development] s3icc0:
Small ad for those who wanna try version 2 of SRV profile with SRV script.

http://xdaforums.com/showpost.php?p=49896679&postcount=3391&nocache=1&z=7557878287769240
[Galaxy S 4 i9505 Original Android Development] wonsky21:
Testing it now ;)

GT-I9505 | SlimBean 4.4.2 WEEKLY 2.4
[Galaxy S 4 i9505 Original Android Development] HaGii:
Hey [MENTION=4325945]ktoonsez[/MENTION]

I don't know, if someone ever asked you, but there is the option of swipe 2 wake in your kernel...

Is it possible to get LG G2s Knock Knock/Knock On feature implemented i your kernel? Or maybe that u can also swipe 2 lock? :P

Thanks for answer in advance
[Galaxy S 4 i9505 Original Android Development] s3icc0:
Think it should be renamed to swipe to unlock instead
[Galaxy S 4 i9505 Original Android Development] HaGii:
'Cause it isn't for waking up the phone but fpr unlocking when screen is on? :/
[Galaxy S 4 i9505 Original Android Development] wonsky21:
Nope. It is a feature, originally developed by kernel developer fluxxi for S1 or S2 (I can't remember). When your phone's screen is off you swipe your finger from left to right to wake up your device ;)
[Galaxy S 4 i9505 Original Android Development] s3icc0:
Nope ... Wjen your screen is on you swipe over capa buttons and phone will unlock ;)
[Galaxy S 4 i9505 Original Android Development] rauschkugl:
No, you swipe over the screen to wake it up and that's why it's called like that.

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] HaGii:
+1 for s3icc0

It's not like the feature in many HTC One kernels. ;)

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] wonsky21:
You are wrong my friend. You don't have to swipe a finger over any button, just over screen, when it's off.

True.

Edit: Original developer is called myfluxi, sorry :)

First hit in google: http://xdaforums.com/showthread.php?t=1777352

first line tells you what is slide2wake.
[Galaxy S 4 i9505 Original Android Development] HaGii:
No, tried it several times now. ;)

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] rauschkugl:
You can try it a hundred times. It's not implemented. But that's still the feature which is meant with the setting.

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] HaGii:
Okay, so that's the answer. Didn't know that it isn't implemented. :P But why isn't it implemented? :P Would be great.:)

Thanks for answer. ;)
[Galaxy S 4 i9505 Original Android Development] wonsky21:
If you missed my edit, here's what s2w is: http://xdaforums.com/showthread.php?t=1777352
[Galaxy S 4 i9505 Original Android Development] rauschkugl:
Because it wasn't possible on the s4 as far as I know. Or kt didn't have enough time yet but I don't think so.

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Shocky2:
Any update on compatibility with Foldermount on GE roms?
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
[MENTION=3855065]s3icc0[/MENTION] is correct. When this feature is set, you slide through the capacitive buttons on your phone as if you are sliding the screen to unlock. This is done in order to bypass the step of pressing the power or home keys to wake the phone to lockscreen and then unlock the phone.

KT hasn't had the chance to add in the code in order to get it working so it's still currently a non-functional feature.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
Whooooaaa :) all the credit to ktoonz :)

Anyway the easiest way is to enable the function and try it :)
[Galaxy S 4 i9505 Original Android Development] wonsky21:
Well then, I guess s3icco knows better than original developer of this feature? ;)
[Galaxy S 4 i9505 Original Android Development] rauschkugl:
Then you'll sure be able to explain why it already was in ktweaker for the nexus 10 which had no capacitive buttons at all.

He is not correct. Swipe to wake is from fluxi and you Swipe the screen as already linked by somebody.

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] wonsky21:
By me :) Twice already.
[Galaxy S 4 i9505 Original Android Development] Formhault:
Hah... I thought the HTC Evo 3D was the first to have s2w :silly:
[Galaxy S 4 i9505 Original Android Development] rauschkugl:
Check play store. Foldermount was updated and says in changelog that it should be fixed.

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Formhault:
Regardless... I thought s2w in KTweaker is not working because I'm doing it wrong. :D
[Galaxy S 4 i9505 Original Android Development] -sandro-:
[MENTION=5082757]LuigiBull23[/MENTION] this is for you. Going crazy, you do 6h of screen on data I can't almost do that on stand-by!!
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
Not quite sure I understand what you're trying to say here. I'm not stating he knows better than the dev. All I'm saying is that that is the functionality of the Swipe 2 Wake feature and fluxi mentions nothing of actually swiping the screen to wake the phone. When he says "Slide from far left to far right" I'm assuming he's referring to the bottom of the screen where the capacitive buttons are located.

KT uses the same code for Ktweaker across the N10, S3, and S4 devices so the feature was on the N10 because it was already implemented on the S3.

It's just like our LED options that were available in Ktweaker for the S3 but do not function on that device.
[Galaxy S 4 i9505 Original Android Development] rauschkugl:
Yes only problem is that the one for the n10 was there when he introduced the app and the others followed. And no, it's not the same. All other options aren't there on the n10. You can't use one apk on another device.

Look at the s2 kernel thread from gokhanmoral. I used it myself and you swipe the screen not capacitive buttons. Read the changelogs, search on YouTube or whatever. There is nothing with capacitive buttons and also fluxi doesn't refer to it.

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] wonsky21:
I made a deeper research and it seems to be 2 ways s2w works: for HTC phones and Samsung (S2 at least). For HTC phones you need to swipe over capative buttons from left to right to wake up the device. For Samsung you do the same but you can do it anywhere over screen (but still from left to right). So it seems we both have right ;)
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
I was just judging based on how I remember the feature to function on the HTC phones. So there are 2 types then huh? No wonder the confusion LOL

Thanks for the clarification. :thumbup:
[Galaxy S 4 i9505 Original Android Development] rauschkugl:
Changelog 12.15 on the nexus 10 kernel thread if you still don't believe it. Says ktweaker is born and sweep to wake implemented with the explanation which was called swipe2wake in ktweaker app. It was in the app for the n10 because it worked there and it was the first device where the app was introduced.

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] wonsky21:
Perhaphs more than 2 types. However I can't imagine how "HTC type" could work on Samsung smartphones, as most of them has a physical button between touch buttons... So only way s2w could work on S4 is the way fluxxi made it.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
Guys why are you argueing? Just go to KTweaker on your S4 enable s2w and try it ... I did the same month ago

Ofc there are probably more versions on different phones ... But s4 is over buttons to unlock only
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
The Ktweaker app itself came to the S3 long before KtweakerT was born on the N10. See post below. I get your point on S2W though. There was a misunderstanding on how the feature functions on Samsung phones compared to HTC.

http://xdaforums.com/showpost.php?p=30682012&postcount=2622
[Galaxy S 4 i9505 Original Android Development] rauschkugl:
So tell us how it worked if it isn't implemented. It's a placeholder!

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] s3icc0:
Read my previous posts ...
[Galaxy S 4 i9505 Original Android Development] HaGii:
It doesn't work. ;) You can only unlock the phone when in lock screen and screen is in by holding or tapping menu key... It's a Google edition bug... ;)

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] s3icc0:
:( just tried it again and it is not working ... but it worked for me month ago or so ...
[Galaxy S 4 i9505 Original Android Development] Shocky2:
Yes I've seen that and it still doesn't work.
[Galaxy S 4 i9505 Original Android Development] Raiken_:
At times, since flashing the 01-23-14 KT Kernel, my phone goes unresponsive at times, then reboots. Wiped Cache and Dalvik Cache also, then turned off Xposed, same result.. Anyone experiencing the same thing? ROM is Google Edition 4.3.
[Galaxy S 4 i9505 Original Android Development] andyjg247:
Does anyone else see apparent corruption on the I/O scheduler adjustments page when using bfq? I seem to see that regularly. If I switch to another and then back it looks better, although the very bottom still looks condensed. Can't seem to tie down a guaranteed way to cause it unfortunately. I have checked my profile and tried a new one with results being the same after some time unfortunately. I 'believe' I also get poor battery life when it is corrupted too.
[Galaxy S 4 i9505 Original Android Development] Formhault:
Yes. Disregard it. You don't have to tinker with that line anyway. :p
[Galaxy S 4 i9505 Original Android Development] andyjg247:
Ok , thanks. Is this just aesthetic corruption then?
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Delete lol

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] bastardociccio:
I tested AOKP (that is AOSP) and with that rom the charging on power off works! (aokp kernel)

I tested all other roms from Google Edition and charging with power off doesn't work

I have found a workaround: I use dualboot

primary rom: TW rom

secondary rom: GE 4.4.2

I use GE4.4.2 and when i want to power off to recharge:

-with apk, switch to primary rom (without reboot...)

-turn off phone

-recharge

-turn on phone (the phone boot to primary rom -> switch to secondary rom->reboot to secondary rom)*

*I use a script to switch to secondary rom and reboot that is executed onboot

It works well

;)
[Galaxy S 4 i9505 Original Android Development] Formhault:
No. It is a sign that your phone is dying. OF COURSE it is aesthetic corruption.
[Galaxy S 4 i9505 Original Android Development] Lucius1972:
Lol, don't make him sweat.
[Galaxy S 4 i9505 Original Android Development] Formhault:
Haha :silly:.

[MENTION=5248691]andyjg247[/MENTION]

If you go in and out of the "I/O Adjustments" page, you'll see that the corruption goes away. It's random, anyway. Ktoonsez made it somewhat clear, that option is not for us to tinker with (well, I think he said something like "blah blah DON'T EVEN LOOK AT IT GO AWAY blah blah"). :D