yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
Agree is weird... But seems a few of us were experiencing sudden battery drain with the 627th and/or 628th nightly. Never had that problem before. Also I was on PAGAPPS previously and never any issues until few days ago. But for me the 629 nightly is seems all OK now (w latest Slim GAPPS). Not sure if it was the latest nightly or GAPPS that fixed it, but at least my dreaded battery drain gone. :thumbup:
[Galaxy S 4 i9505 Original Android Development] vedko:
Well, the nighties are the "place" for the CM team to try new stuff and sometimes things break and have unexpected consequences, e.g. battery drain. If someone wants stability then the M releases are the way to go.
[Galaxy S 4 i9505 Original Android Development] v00d007:
You're kidding, right? So far there are ONLY Nightlies available for the 9505....
[Galaxy S 4 i9505 Original Android Development] John_wba:
Lmao not true at all, there is two M versions available. M6 and M7
[Galaxy S 4 i9505 Original Android Development] Ritvars:
Any speculated dates on which the stable version might be available?
[Galaxy S 4 i9505 Original Android Development] John_wba:
Use the cmupdater, settings/about phone/cynagenmod updates then choose the "all" option.

I think the M8 will also be here in a week or so. They are released on a monthly basis
[Galaxy S 4 i9505 Original Android Development] petrus764:
M builds have replaced rc/stable builds. M builds are released every 4 weeks now, but they plan on getting that down to 2 weeks.
[Galaxy S 4 i9505 Original Android Development] v00d007:
Ok, you're right when "snapshots" are supposed to be milestones. But why aren't they put into the milestones folder then?
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
Agree but I still prefer the "fun" of nightlies.... 9 out of 10 times they r relatively stable for me as I been using as my daily driver. Seems jus the odd one or two out of ten that have weird things like battery drain or annoying beep sound during call (remember that one?)... My guess is the recent issues were much to do with their "tinkering" from 4.4.2 to 4.4.3 to 4.4.4 in such short space of time...
[Galaxy S 4 i9505 Original Android Development] vedko:
I agree. Although right now I prefer the stability of the M releases, I was a frequent nighly flasher since Android 2.x. I guess I'm getting old ;)

Anyway, my reaction was triggered by 2 reasons:

1. although the topic of stable version vs. snapshots/M's vs. nightlies were discussed in the thread multiple times, people just don't read back or search before posting. Plus, there was a post about the commit to fix the battery drain issue was just a few posts above

2. I would assume one knows at least something about what "nighties" stand for - in that way you just cannot be surprised if something breaks from one day to another
[Galaxy S 4 i9505 Original Android Development] v00d007:
Yes, there was, but the playstore service wakelock wasn't really the solution (no difference). It must be something else of the android system that just doesn't want go to sleep at all...
[Galaxy S 4 i9505 Original Android Development] sronweb:
For the drain issue I would wipe system together with dalvik before flashing. At least has worked for me. Usually is not necessary anyway but maybe some nightly require a clean system to work properly
[Galaxy S 4 i9505 Original Android Development] sushidog:
I always wipe Dalvik+cache+system on clean flashing. Problem is most guys here prefer to dirty flashing on previous nightly.

My advise is wipe everything (except SD), install clean and recover apps from Titanium.

/// Samsung Galaxy S4 GT-I9505

/// Press "THANKS" if I helped you
[Galaxy S 4 i9505 Original Android Development] sanik90:
I got a problem in CM Snapshot M7, caller name does not appear when receiving call, same goes to text message, only number appear but my phonebook is full of contact complete with name and number, any thought?
[Galaxy S 4 i9505 Original Android Development] twcobra:
Did you restore with Titanium. You might have restored a system app by mistake. I have seen many goofy things by making that goof. I have learned to keep my backups as clean as possible.
[Galaxy S 4 i9505 Original Android Development] sanik90:
not at all, I restore the contact the traditional way, export to Storage before flashing, then import that file back after flash the new ROM
[Galaxy S 4 i9505 Original Android Development] maciejk-pl:
Hi guys, haven't been here a long time and thinking about getting back to CM. Is the grey photo problem when using HDR still present? That was the only issue I had about two months back and I had to switch to GPE. Thanks.
[Galaxy S 4 i9505 Original Android Development] v00d007:
It maybe isn't the best time to go back to cm right now cause after the upgrade to 4.44 code there lots of new bugs in it at the moment. Or you go back to the stable 4.42 builds like i did yesterday after i couldn't get over the massive battery drainage...
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
Seems to b a long list of changelogs for next nightly http://www.cmxlog.com/11/jflte
[Galaxy S 4 i9505 Original Android Development] Dr.No.pt:
Better check your apps or fresh install cause i have very good battery with 4.44. :)
[Galaxy S 4 i9505 Original Android Development] John_wba:
I've told him several times that the problem is his and not CM, he refuses to listen. I managed 6 hours screen on and 1 day 8 hours stand by... Hardly sounds like battery drain does it? Lol :p how long are you getting mate?
[Galaxy S 4 i9505 Original Android Development] tomurbanowicz:
Xposed framework

I use xposed and after update CM11 I have to reinstall framework. What have I do, to do that without reinstall framework? Ex. any script?
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
Agree.. Also I think the problem is a few of us have been dirty flashing as per CMs advice on their blog (says nightly not necessary to wipe anything when update nightly ) ,.. And some of us too lazy (I am guilty also) of doing a fresh factory reset and install. (anyhow my battery seems much improved since 629 nightly)... but my gut feeling is a fresh install for me is also inevitable soon. :)
[Galaxy S 4 i9505 Original Android Development] snakecharmer23:
Everyone needs to read this section of the OP.

Every single sentence is relevant.

In other words, don't post any issues in this thread if you're using a different kernel, unsupported GAPPS, or haven't wiped and re-installed the rom.

99% of this stuff needs to be taken out of the development section and put into a discussion thread.
[Galaxy S 4 i9505 Original Android Development] !crazy:
Actually nightlies are mostly stable, and there are at less few nightlies after M7 which seem to work better than Me release. So, no need to switch to M, just find nightly which works well for you. But people have problems with other stuff, like applications, gapps etc. and consider CM to be responsible for every single issue they get.

Also as someone mentioned, one should be particularly cautious when big code changes and merges happen. It is likely, or 100 % sure they will introduce new bugs. On the other side, it depends on usage if one is going to discover and notice these.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
I disagree. IMO I think that if people have modified kernels they should be able to share with others on how that kernel works with this CM, just like how people share how certain apps work or dont work here with CM, already. Also as an example, I had alot of problems with the original CM recommended GAPPs few months ago and my problem was solved when another user here suggested PAGAPPS which worked well before CM4.4.4 came out. And Yes I did do a factory reset wipe everything dalvik cache system all at that time. The whole point of this thread is to help test the robustness of CM rom and because we cannot use jira to report nightly and to share experience of issues. If you would like to start a new discussion thread as you suggested pls feel free to go ahead.
[Galaxy S 4 i9505 Original Android Development] v00d007:
Thanks for the bashing guys, but you're partly wrong. I had huge battery drain with the 0623 build right after installing, with no bunch of apps installed at all.

So i thought it's maybe a bad one, did a full wipe and gave 0628 the next try. Then i installed all my favorite apps and tried to configure the system like i want it.

Some bugs layed on this way, but with all help of this forum (thanks), i solved them. All but one, the well beloved almighty battery drain... :mad:

That's the way it was...
[Galaxy S 4 i9505 Original Android Development] 135Shadowsoul:
Hi,

yes, there are "Custom-Recovery-Scripts" for saving and restore XPOSED while updating

I am using the following skript:

#!/sbin/sh
#
# /system/addon.d/90-xposed.sh
# During an upgrade, if /system/bin/app_process.orig exists, this
# script backs up /system/bin/app_process, /system is formatted
# and reinstalled, the ROM bundled /system/bin/app_process is copied as
# /system/bin/app_process.orig, then /system/bin/app_process is restored
# (as would the Xposed Installer do)

. /tmp/backuptool.functions

APP_PROCESS=bin/app_process

case "$1" in
backup)
[ -e "$S/${APP_PROCESS}.orig" ] && backup_file "$S/${APP_PROCESS}"
;;
restore)
if [ -e "$C/$S/${APP_PROCESS}" ]; then
echo "Backuping new $S/${APP_PROCESS} as $S/${APP_PROCESS}.orig"
cp -p "$S/${APP_PROCESS}" "$S/${APP_PROCESS}.orig"
echo "Restoring Xposed $S/${APP_PROCESS}"
restore_file "$S/${APP_PROCESS}"
echo "If your system bootloops, you can either:"
echo " - Replace $S/${APP_PROCESS} with $S/${APP_PROCESS}.orig"
echo " - Remove $S/${APP_PROCESS} and reinstall your ROM"
fi
;;
pre-backup)
# Stub
;;
post-backup)
# Stub
;;
pre-restore)
# Stub
;;
post-restore)
# Stub
;;
esac

I am not 100% sure what exactly is saved and restored; Im using "GPSNotification" and "Smiley Replacer" Module

Try on you own risk!! for me it is working:

Just copy the code into a file, name it like other custom srkips ("XY-xposed.sh", with XY any number > last original recoveryskripts, the name "xposed" is not importat (i think), but to know what it does i would recommend it) in /system/addon.d and copy it into this folder.

On my device it is called "90-xposed.sh" (without the " )

i hope, this may help you
[Galaxy S 4 i9505 Original Android Development] Chahk:
Anyone else having issues with Xposed and the latest (7/1) nightly? Viber, TaskSync and a few other apps are crashing when I enable Xposed. Relevant log entries:

I/NLService( 1601): ****REMOVED: ID:666; Text: Unexpected error, please send a report...; Package: com.viber.voip
V/DashNotifier( 1656): Removed: com.viber.voip: 666
E/ACRA ( 3270): Viber fatal error : Unable to create application com.viber.voip.ViberApplication: java.lang.NullPointerException
E/ACRA ( 3270): java.lang.RuntimeException: Unable to create application com.viber.voip.ViberApplication: java.lang.NullPointerException
E/ACRA ( 3270): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4471)
E/ACRA ( 3270): at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
E/ACRA ( 3270): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
E/ACRA ( 3270): at android.app.ActivityThread.handleBindApplication(Native Method)
E/ACRA ( 3270): at android.app.ActivityThread.access$1500(ActivityThread.java:145)
E/ACRA ( 3270): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1266)
E/ACRA ( 3270): at android.os.Handler.dispatchMessage(Handler.java:102)
E/ACRA ( 3270): at android.os.Looper.loop(Looper.java:136)
E/ACRA ( 3270): at android.app.ActivityThread.main(ActivityThread.java:5141)
E/ACRA ( 3270): at java.lang.reflect.Method.invokeNative(Native Method)
E/ACRA ( 3270): at java.lang.reflect.Method.invoke(Method.java:515)
E/ACRA ( 3270): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
E/ACRA ( 3270): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:611)
E/ACRA ( 3270): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
E/ACRA ( 3270): at dalvik.system.NativeStart.main(Native Method)
E/ACRA ( 3270): Caused by: java.lang.NullPointerException
E/ACRA ( 3270): at org.acra.ConfigurationInspector.toString(ConfigurationInspector.java:129)
E/ACRA ( 3270): at org.acra.ErrorReporter.init(ErrorReporter.java:363)
E/ACRA ( 3270): at org.acra.ACRA.initAcra(ACRA.java:297)
E/ACRA ( 3270): at org.acra.ACRA.init(ACRA.java:238)
E/ACRA ( 3270): at com.viber.voip.ViberApplication.onCreate(ViberApplication.java:359)
E/ACRA ( 3270): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
E/ACRA ( 3270): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4468)
E/ACRA ( 3270): ... 14 more

Everything was working well on the 6/30 nightly. Also, the crashes stop if I disable Xposed.
[Galaxy S 4 i9505 Original Android Development] FrA1l3:
7/1 here have a lot of FCs in phone process, contacts, and adjusts.

Anymore?

I have all stock.
[Galaxy S 4 i9505 Original Android Development] mooyaart:
I haven't had any problems with 7/1 so far.

KT kernel, F2FS, ART
[Galaxy S 4 i9505 Original Android Development] FrA1l3:
Thank you mooyaart, I change to ART and now it works without problems.

Enviado desde mi GT-I9505 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
Same here... For now..
[Galaxy S 4 i9505 Original Android Development] mooyaart:
That's weird! First time I have heard ART fixing problems!

I just use it because for my setup it is faster and uses less battery.

Glad it worked out for you.
[Galaxy S 4 i9505 Original Android Development] Stransky:
On 1/7 ART CM kernal and Gapps and have not had any problems, no FCs or high battery drain etc.
[Galaxy S 4 i9505 Original Android Development] Diazz72:
Why is USB OTG not working whit CM11, if i install AOSP its working but if i install CM11 its not...i have try it with KT-SGS4 kernel and its not working, any ideas why?

http://usbhost.chainfire.eu/?search=386389
[Galaxy S 4 i9505 Original Android Development] mooyaart:
I haven't had any problems with USB OTG on CM11 and I also use KT kernel. I have used both FAT and NTFS USBs. What format is your USB?
[Galaxy S 4 i9505 Original Android Development] Diazz72:
Its not problem in USB Format, becose mouse is not working too...

EDIT: I got it working by goeing in DL. Mod...strange!!!
[Galaxy S 4 i9505 Original Android Development] Ritvars:
Is anyone else experiencing terrible battery life on CM11? 26th nightly was terrible. Installed an update to July 1st nightly and the battery drains fast when playing games or simply browsing internet/apps. With stock TW ROM I didn't experience that. I know, I know - this is a nightly but still, the drain shouldn't be like that. Also, checked Google for same problems and many people complain about this.
[Galaxy S 4 i9505 Original Android Development] tomurbanowicz:
Not working for me...
[Galaxy S 4 i9505 Original Android Development] sronweb:
Read some pages back. Apparently most of the issues have been solved with a clean installation.
[Galaxy S 4 i9505 Original Android Development] Cozmos23:
I just remember a m8 who was telling me that CM is not working because he dirty flashed CM over a TW Rom lol.

Yeh there are a few bugs but CM also gives u frequent updates to the newest Android Version and features. I guess before Samsung will release a 4.4.4 update CM will have a working L Version...
[Galaxy S 4 i9505 Original Android Development] stevesin:
is there anyway to get notifications on the lockscreen without using a 3rd party app? if not, anyone have any recommendations on which one?
[Galaxy S 4 i9505 Original Android Development] snakecharmer23:
It's great that custom kernels and gapps solve your problems and it can help others but it contributes nothing to the development of CM, which is what this thread is for.

If I was a developer for CM (which I'm not), I wouldn't be looking in this thread anymore because people are polluting it with stuff about 3rd party kernels and Gapps. Both of those things have nothing to do with the actual ROM.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
Well, by your definition we might as well not talk about what apps FC or crash or dont work with this ROM? . How will you know if a ROM has problems if you cant say how well it works with this app or that app or kernel or when the recommended GAPPs doesn't work for some people. Every phone is different even if same model, thats we we share on forums, and can have different issues. You may not have issues doesn't mean someone else doesn't. And no, a "factory reset" doesn't "always" solve the problem. Thats a simplistic view. We r all trying to help each other here. And share experience with this great free ROM and we are all testers here not just you. I am glad you say don't work for CM otherwise by your definition 99% of us here should be gone by your definition? And I disagree, I am sure CM would be interested to know why they recommend people NOT to factory reset each time they flash an update, and why they officially recommend "just dirty flash", but their users are now having problems. And by the way I am on CM default kernel. BTW the other guy said he did factory reset before and "still have battery drain". So he can't share that? What if is was the CM recommended GAPPS causing problems for this ROM or it was a ROM problem? , how will he know if he didn't share here? You saying he's not allowed to share?
[Galaxy S 4 i9505 Original Android Development] aleksik:
I just flashed the 7/1 nigthly and I have a problem with app installation. If I try to install an app from sd card the installation screen pops up just fine, but I can't click the 'install' button. However I can click 'cancel'.. And of course I have enabled installing apps from other than play store in the settings. I might do a clean install of this nigthly tomorrow as I have been dirty flashing since the 4.4.3 came out..
[Galaxy S 4 i9505 Original Android Development] cdmackay:
A long shot, but...

this happens if you have an app that has taken over the whole screen, e.g Screen Filter. When that happens, the APK installer won't run, as a security measure.

That's the only time I've seen this happen. there may be other reasons...
[Galaxy S 4 i9505 Original Android Development] aleksik:
I have never used any kind of screen filter so good try, but didn't help. :/

Edit. OMG, just deleted an app called Echo Lockscreen which I installed today. Would have never thought that it was causing my problem as it's not 'on' other than on locksreen.. Big Thanks to you! And nah, maybe I won't make a clean install of ROM tomorrow :D
[Galaxy S 4 i9505 Original Android Development] riksterinto:
GAPPS are a major part of Android. I don't think there are many people who don't install them with CM. GAPPS are not part off the base CM because CM wants to give people options about which apps they want. I'm pretty sure CM devs are interested in knowing about issues encountered with GAPPS on their ROM.

Custom Kernels are also used by a large number of CM users so if using one resolves an issue, then there is no reason it can't be mentioned here. Most everything is open source so CM devs could review the custom kernel to help identify and fix issues with their own. The only thing I would agree with is that issues related to a custom Kernel should not be discussed here.
[Galaxy S 4 i9505 Original Android Development] jcasares:
They are not part of CM because they can't bundle them.

I don't have it anymore after I uninstalled some apps that coincidentally were on one of the home screens where the flickering was most noticed and on the first page off the app drawer (three Cut The Rope games and Birzzle game). It's really weird.

I found a way by recreating it again as mentioned in Google Support Forums. Don't know if it was because of the multiple tries or because I made it another way. I ran the command rm -rf /data/misc/wifi through an elevated rights (su) terminal session and then rebooted.
[Galaxy S 4 i9505 Original Android Development] v00d007:
Yes you're right, man!

I've tried to discuss this matter here with losts of descriptions but either there are really some configurations where the drain isn't that big or most people here just controvert that... So

at least at the moment

it is a

real big issue

of the current cm builds... A clean installation

doesn't solve the problem

as i posted quite a few times here.....

Battery life is just

half as good

as with older 4.42 builds or with 4.42 TWz roms!

---------- Post added at 07:59 AM ---------- Previous post was at 07:55 AM ----------

Maybe this works for you...:rolleyes:

But here seem to be quite a lot of users who don't solve the problem with that! (if you don't mind)
[Galaxy S 4 i9505 Original Android Development] Darkside14:
I've never suffered with battery drain on my s4, never since I've installed CM11 back in february... And I've done some full wipes only with a major Android update (4.4.2->4.4.3), and all is fine for me, all stock with cm gapps
[Galaxy S 4 i9505 Original Android Development] remorema:
I have to say I still haven't tested later releases but with the 29th nightly I'm getting amazing battery life. In all the ROMs I've tried including the stock one, this is by far the best performance/battery balanced ROM. Games run fluid and battery lasts forever. Really really great job on this one. I have a ton of apps syncing and still haven't greenified nothing. Brightness always on auto and WiFi always on. All that said I can get about 5h screen on with mostly web and forums and some light gaming.

As someone asked before. Anyone knows a good solution to mimic L lock screen. I use hall monitor for sview and no lockscreen at the moment.
[Galaxy S 4 i9505 Original Android Development] Cozmos23:
With 0701 nightly my phone gets hot in the middle and Battery life isn't that good like it was a few nightlys before dunno why. BBS and Battery setting shows nothing suspicious.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
R u on Dalvik or ART?
[Galaxy S 4 i9505 Original Android Development] remorema:
Art
[Galaxy S 4 i9505 Original Android Development] v00d007:
What i found out what really is a pain for the battery is the developer-option "force gpu rendering in 2D apps". It takes at least 20% bat-life.
[Galaxy S 4 i9505 Original Android Development] riksterinto:
When you say clean install, are you wiping the internal and external SDs? I used to have issues with AOSP ROMs coming from TW but after cleaning both SD cards; the issues went away.
[Galaxy S 4 i9505 Original Android Development] SWTR:
really? I have it on too
[Galaxy S 4 i9505 Original Android Development] v00d007:
From SD card I never delete more than what's got anything to do with android/apps. They are easy to find by their name. From external SD never anything.

---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------

just try and see......
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Installed CM11 14 dec. 2013 and have flashed every nightly since then (never wiped in between).

I only have had to revert to previous nightly two times due to severe bugs in build.

I'm used to get a full day with 3-4 hours screen time and 10-15% battery left when I go to sleep. Is this normal or should I expect more ?

Thanks
[Galaxy S 4 i9505 Original Android Development] Darkside14:
My phone starts it's day at 6am fully charged, I use it maybe 2-3 hours per day, taking some photos for my work, and I use it with my car for music (2h for the trip), when I go to sleep at 10pm, I've got 60-70% remaining, depending of each nightlies, it sometimes goes down to ~45%, always on edge except when I need some speed, wifi active ~7h30 per days
[Galaxy S 4 i9505 Original Android Development] v00d007:
If you want 70% or more on top you gotta take a modified Samsung TWz Rom. See my comparison some pages ago.....