yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Loop4zil:
Google Email App not copatiblw with latest Nightly?

I'm on the 7-16 nightly. I have had this issue with the last few nightlies. Is there something I'm doing (or not doing) to cause this issue? I'm using AquaMail in the mean time. No issues with Aqua.

[IMG="CM_11_Google_Email_client_app"]https://lh3.googleusercontent.com/-rYo-WMZrxh8/U8Zopc94s0I/AAAAAAAAMw8/eFLV4Ngxtzg/w311-h553-no/Screenshot_2014-07-16-07-57-21.png[/IMG]
[Verizon Samsung Galaxy S 4] FernBch:
Running the 7/16 build. The issue of having to toggle airplane mode to get LTE to reconnect has returned.
[Verizon Samsung Galaxy S 4] MustGoFast:
I've not seen this issue but I run the security fix which replaces that client with a hacked version.
[Verizon Samsung Galaxy S 4] papstar:
Is anyone getting constant screen flickering? Its been going on for about the last month.
[Verizon Samsung Galaxy S 4] jkc120:
Not on stock but I tried faux kernel for the fast charge and had flickering like crazy with that.
[Verizon Samsung Galaxy S 4] FernBch:
The only display issue I have seen recently (7/16 build) is an occasional system freeze lasting about 5 seconds using the stock kernel.
[Verizon Samsung Galaxy S 4] jkc120:
OT, but curious what others on Verizon are thinking for their next device? I'm waiting to see how the X+1 looks (provided they have a developer edition), though I think I'd miss cm11 and an RGB led. The S5 is out of the question having to be stuck with touchwiz for me and the m8 looks OK, but the camera and lack of RGB led would bother me. And despite more pixels, I think the G3 would be a step backwards in quality compared to the S4.
[Verizon Samsung Galaxy S 4] FernBch:
With 12 months before I can upgrade I'm not even thinking about a new device. Anything that limits me from running CM is out of the question. Unless I can run CM I will be sticking with my GS4.
[Verizon Samsung Galaxy S 4] jkc120:
I don't know why but I'm kind of itching to try a stock rooted experience but on a device without a fugly skin heh. Sense is OK, but I like that moto (and hopefully lenovo) is staying close to stock from a UI perspective.
[Verizon Samsung Galaxy S 4] jkc120:
The 7/20 zip is borked, only 111 MB so don't bother with it.
[Verizon Samsung Galaxy S 4] FernBch:
I wonder if it was caught and fixed. The download site now says 231.10mb.
[Verizon Samsung Galaxy S 4] papstar:
Screen flickering is getting out of control. Reboot fixes it for about a half hour. Tried multiple kernels, as well as development settings. Anyone have any ideas?:confused::confused:
[Verizon Samsung Galaxy S 4] FernBch:
I have noticed an issue with internet use (7/16 build).

I frequently have to restart the device to browse the web. Page loading will become extremely slow or not work at all. After a reboot all works again. Not sure if it's my browser (DolphinHD) or a wifi issue. I don't browse much off wifi but I think it does it on mobile data connection, too.

I have also seen messages in my logcat saying something an issue with google services. (Probably unrelated to the web issue).

Logcat is attached.

https://www.dropbox.com/s/2iho47okmpekhxn/Log_2014-07-20_16-42-14.txt
[Verizon Samsung Galaxy S 4] musicfreak190:
Use Google Launcher not CM stock..
[Verizon Samsung Galaxy S 4] wtherrell:
Just flashed CM 11. 2x factory reset /wipe. Verizon GS4 unlocked bootloader. Suddenly Titanium Backup can't read its backups directory on the ext SD card. Other apps such as office suite access their files on ext SD card just fine. File explorer reads them OK. I have searched Google & various forums but can't find an answer that works. Looking for some help on this. Had same problem on 10.2.1 I tried the sd card fix but doesn't help.

All works fine on TW roms like Hyperdrive but have been wanting to test drive CM

<br/>
[Verizon Samsung Galaxy S 4] papstar:
Did you change the default Titanium Backup save directory before you wiped?

---------- Post added at 09:32 PM ---------- Previous post was at 09:32 PM ----------

To whom are you referring?
[Verizon Samsung Galaxy S 4] FernBch:
You have to restore the previous Android ID. TiBu associates backup sets to an Android ID. Once you do that TiBu will see them again. In TiBu go to settings then your device and choose manage Android ID.
[Verizon Samsung Galaxy S 4] wtherrell:
No. Just same as always - - ext sd card. I did that eons ago. Titanium just shows big red x & says backup directory on ext not available.

---------- Post added at 06:11 AM ---------- Previous post was at 06:10 AM ----------

Thanks, I will give that a try.
[Verizon Samsung Galaxy S 4] FernBch:
That should do the trick for you. Each time you wipe and clean flash a custom ROM a new ID is generated for your device. I have had to do this a couple times myself.
[Verizon Samsung Galaxy S 4] wtherrell:
Thanks for the help, but Well, hmm. Didn't work. The titanium menu item to restore the ID has two choices. Create a new one, or restore from backup. Choosing restore results in showing the path to backup directory and the notification that the directory is not available. Still the red "x" by the backup directory listing on the 1st page of TiBu.

What next?
[Verizon Samsung Galaxy S 4] FernBch:
Not sure. I've never had to do more than restore the previous ID and detect the directory. It's always worked for me.
[Verizon Samsung Galaxy S 4] wtherrell:
I have sent description of problem to Titanium devs. Until this gets sorted out I am forced back to previous rom.

Could it be kernel that is in CM?
[Verizon Samsung Galaxy S 4] FernBch:
I guess anything is possible. I currently am and have been running CM11 since it's release with the stock kernel and have never had an issue with TiBu.
[Verizon Samsung Galaxy S 4] wtherrell:
And is your backup directory also on the ext SD card?
[Verizon Samsung Galaxy S 4] FernBch:
Yes. Always has been. When I first got TiBu it placed it on the internal storage and I wiped it once by mistake. After that it went on the SD card.
[Verizon Samsung Galaxy S 4] wtherrell:
Well, I just flashed Hyperdrive 17.1 with Ktoonz kernel and titanium worked perfectly. Missing something, probably obvious but just cannot put my finger on it.
[Verizon Samsung Galaxy S 4] Train88:
Chainfire's su update zip always fixes any problems I've had with TiBu
[Verizon Samsung Galaxy S 4] wtherrell:
I am using Chainfire's SuperSU latest 2.0.1. Is that what you mean? I installed it and updated binaries but Tibu problem persists. I searched for "Chainfire's su update zip " but results didn't show up anything.
[Verizon Samsung Galaxy S 4] jkc120:
7/25 link is dead. Was there a problem with it causing them to pull it? Saw some commits for the ffc to fix snapchat, and while I don't use it I know I've heard some folks in here talking about it. And back to the OT question I had before, this throttling nonsense on Verizon means I'm probably going to see if AT&T coverage has improved here. At least I can pick from phones that aren't locked down on AT&T :/
[Verizon Samsung Galaxy S 4] FernBch:
I just downloaded 7/25 succesfully.
[Verizon Samsung Galaxy S 4] jkc120:
Ah the short URL works but the direct download doesn't, thanks.
[Verizon Samsung Galaxy S 4] wessiide:
I guess given that I pull down over 100 gigs a month on 4g probably means I am about to get the **** throttled out of me.
[Verizon Samsung Galaxy S 4] TMYINC:
I pull around the same. I'm sure we are in the "5%" group lol.
[Verizon Samsung Galaxy S 4] jkc120:
Well, you have to be on a "busy" tower, but I'm sure magically they'll all be "busy" for those that qualify as of 10/1. :/
[Verizon Samsung Galaxy S 4] wtherrell:
Well, Titanium Backup works on Hyperdrive, AOKP, and Carbon roms but not on Cyanogenmod. So I am giving up on Cyanogenmod for my GS4.
[Verizon Samsung Galaxy S 4] FernBch:
Sorry to hear. I wish I could give you more help. TiBu works perfectly for me on CM11.
[Verizon Samsung Galaxy S 4] papstar:
Is no one having the screen flicker issue?
[Verizon Samsung Galaxy S 4] Train88:
I'm almost certain I've said it in this thread, bc I know I've said it in others... But flash Chainfire's su update zip. Google it.

Yea I have, just didn't pay it much attention till I saw your post lol

Team BlackOut... or Back Out

---------- Post added at 09:44 PM ---------- Previous post was at 09:40 PM ----------

Funny, the one on his website is 1.94

Team BlackOut... or Back Out
[Verizon Samsung Galaxy S 4] wtherrell:
I have Chainfire's Su 2.0.1 running with updated binaries. Doesn't work to fix the problem. I also found another file called Chainfire's Su update zip & flashed it. No change in the behavior of Tibu not able to access the ext sd card. Thanks for all the help, guys. But for now CM just is not working for me.
[Verizon Samsung Galaxy S 4] papstar:
Found a way to fix the flicker for the most part. It seems that the screen flicker is caused by auto brightness in low light situations. Try adjusting your 0 lux brightness to 8%. Helped for me.
[Verizon Samsung Galaxy S 4] FernBch:
Has anyone been experiencing random fc's? I'm on 7/27 and have had random fc's with the calendar, app drawer, Apex Launcher, and Dolphin Browser recently. Can't seem to reproduce any pattern. The affected app will freeze for a few seconds then force close.

I've always set mine there. Auto brightness seems like it has always been a little on the dim side for me. Maybe this is why I have never noticed the flicker.
[Verizon Samsung Galaxy S 4] jkc120:
As I mentioned before, I don't really have the screen flickering on the stock kernel. Although I did notice it a bit the other day when I went into the gallery app and it was sitting in the initial window.
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 7/31 this morning and promptly was stuck in a bootloop. Pulled the battery, restarted, updated 7 apps, and seems fine ever since. Only thing I noticed was I had to reset my wallpaper, it booted to the default.
[Verizon Samsung Galaxy S 4] swordmastr54:
Have you had low call volume mine seems so low I can't hear anything been that way for the past few days updates.
[Verizon Samsung Galaxy S 4] FernBch:
Not sure. I use a BT earpiece most of the time. I'll pay attention for the next few and report back.
[Verizon Samsung Galaxy S 4] FernBch:
I have noticed the compass in apps such as GPS Status & Toolbox is borked again.
[Verizon Samsung Galaxy S 4] jkc120:
Was never working for me :/ At least not that I noticed
[Verizon Samsung Galaxy S 4] FernBch:
For me it's been hit or miss. Sometimes works perfectly, sometimes orientation is off by 180°, sometimes (like now) doesn't work at all.
[Verizon Samsung Galaxy S 4] bsimpson1:
Oddly, the latest faux kernel had compass working flawlessly for me. I know it's definitely the kernel because I've since switched back to the default cm kernel and the compass is buggy again. The issue with the compass more specifically in my case has been that east and west are backwards.
[Verizon Samsung Galaxy S 4] jkc120:
Interesting! Although with faux I had such terrible flickering that I'd rather have a borked compass than constant screen flicker :/
[Verizon Samsung Galaxy S 4] jkc120:
Well I tried faux 018m just to see if the flickering was fixed and so far so good. I downloaded a compass app which seems to be correct. I wonder what he did to fix it and whether he'll share that info with CM?
[Verizon Samsung Galaxy S 4] papstar:
Couldn't get latest faux to boot on 08/03. Couldn't get past the boot screen.
[Verizon Samsung Galaxy S 4] jkc120:
Hmm I'm still on 7/31 and it worked OK on here.
[Verizon Samsung Galaxy S 4] papstar:
I'll try a older build. Also HATE the customizable ribbon size.

---------- Post added at 09:03 PM ---------- Previous post was at 08:50 PM ----------

And 08/01 doesn't with faux's kernel. Frustrating.
[Verizon Samsung Galaxy S 4] rajones19:
Never working for me, either, and I definitely would have noticed.
[Verizon Samsung Galaxy S 4] jkc120:
Just (dirty) flashed 8/3 over 7/31 with faux and booted fine. Not sure what's up with your particular case, but it seems to work ok here. It's going through the re-build of the apps, but it booted.
[Verizon Samsung Galaxy S 4] BaronLager:
M9!

http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m9-released
[Verizon Samsung Galaxy S 4] FernBch:
It incorporates changes from 6/31 thru 7/27. Anything introduced after that can only be found in a nightly.

Speaking of nightlies, I have flashed 8/3. Booted without issue and will be test driven today.
[Verizon Samsung Galaxy S 4] reinaldistic:
12/16 thinks I'm charging even when I'm not, 100% battery for a full 30 mins of screen time and the led notification light stayed green and on the whole time, actually charging it had no effect... I've yet to test Bluetooth, I'll test then report back and flash back to 12/12
[Verizon Samsung Galaxy S 4] brewner:
12/16 seems to have broken the camera.
[Verizon Samsung Galaxy S 4] Alarbus:
I couldn't get 12/16 to boot, so....
[Verizon Samsung Galaxy S 4] Chris123NT:
Oh jeeze lol :/

Steve strikes again

People with camera issues try this

system/lib/hw/camera.msm8960.so

rename it to vendor-camera.msm8960.so and reboot.
[Verizon Samsung Galaxy S 4] Dusty Rhodes:
Hey, well... I streamed music in my car from Google Play on my way to work this morning. Track info didn't show but the BT thing is fixed.
[Verizon Samsung Galaxy S 4] reinaldistic:
Bluetooth connected now, but the skipping was still there...
[Verizon Samsung Galaxy S 4] rexdog1888:
I had this problem but switching to the PA gapps solved it for me.
[Verizon Samsung Galaxy S 4] FernBch:
Thanks for the info. I'll give it a shot.
[Verizon Samsung Galaxy S 4] scarmon25:
There is two of them. One with capitol letters and one without??
[Verizon Samsung Galaxy S 4] ITGuy11:
Thanks, this worked for the camera.
[Verizon Samsung Galaxy S 4] Chris123NT:
Yeah rename the lowercase one, leave the capital alone.
[Verizon Samsung Galaxy S 4] DynastySS:
Anyone having SMS issues? I did a clean wipe and it won't let me send any.
[Verizon Samsung Galaxy S 4] scarmon25:
OK cool. Just wanted to make sure I did the right one.
[Verizon Samsung Galaxy S 4] isaacfinnegan:
Get a can of compressed air and spray around the audio grill (earpiece). The area can get dust and screw up the sensor. this has already happened to me a few times, and this method has corrected it both times.
[Verizon Samsung Galaxy S 4] drmark50:
I am too. I have had problems in earlier builds with hangouts and worked when I switched back to messenger. Didn't work on 12/16 build.
[Verizon Samsung Galaxy S 4] scarmon25:
Texting works fine for me on 12/16, although Google wallet won't open. I'm using dalvik too so not sure what's up with it.
[Verizon Samsung Galaxy S 4] kick069:
Google wallet is having issues today
[Verizon Samsung Galaxy S 4] abn.geek:
Dirty flash or full wipe? Which kernel?

I dirty flashed with ktoonz's latest 4.4 kernel and I'm seeing the same thing. Gonna try full wipe with stock kernel and see if it makes a difference.
[Verizon Samsung Galaxy S 4] brizey:
It's the kernel. KK had a feature cherry picked in a few days ago and it did the same thing. The feature must have been merged.
[Verizon Samsung Galaxy S 4] whiteout7942:
Camera doesn't work again after flashing the milestone release -__-
[Verizon Samsung Galaxy S 4] Cameron_S:
Did you dirty flash?
[Verizon Samsung Galaxy S 4] whiteout7942:
Nope. Did it clean for the milestone release. Vignette will work after I force close Camera (only for like 5 mins then it won't initialize camera) but when I open the stock Camera app it displays movement for about a second and then crashes. Same for Google Camera. Wiped cache and fixed permissions. Same results :(
[Verizon Samsung Galaxy S 4] vanberge:
Mine is working okay... I clean flashed m9.

What kernel? I am stock
[Verizon Samsung Galaxy S 4] whiteout7942:
Faux kernel latest

---------- Post added at 11:28 PM ---------- Previous post was at 10:47 PM ----------

Looks like I fixed it by running fix permissions from the Fauxclock app. Sorry for the false alarm against CM.
[Verizon Samsung Galaxy S 4] stranula:
I was running this for a couple of weeks without issue. Yesterday I got a notification that there was an update, so downloaded the update and flashed. Now my phone just shuts off with no errors, then will not restart. Pulling and replacing the battery allow the phone to start to boot, but quickly after SAMSUNG logo shows up, it turns off. When I try to get into recovery, the blue letters in the top left appear, but the phone crashes before booting. Anybody have any input on where to start trouble shooting this?

*UPDATE* it also immediately crashes when trying to go into download mode

*UPDATE 2* I figured out the problem, and it is completely unrelated to the ROM. Apparently Samsung phones have a known issue the the power button just one day gets stuck.
[Verizon Samsung Galaxy S 4] gunnermike:
Anyone having trouble with the in call dialer? Mine freezes up after a few minutes. I am only able to hang up using my bluetooth and i cant press buttons like the numbers or the mute. The rest of the phone continues to work fine and i dont get any force closes.
[Verizon Samsung Galaxy S 4] phonedawg:
Lock screen tile behaves inversely in M9

Lock screen tile behaves inversely in M9 - when the tile is switched on, there is no lock screen and when the tile is switched off, we encounter a lock screen. - Anyone else see this?
[Verizon Samsung Galaxy S 4] dspalphamu:
I am experiencing the same issue. I updated this morning to 8/04 build with 8/4 PA Gapps and the issue still exists.
[Verizon Samsung Galaxy S 4] gunnermike:
Looks like a proximity sensor issue. The thread says its because there is dirt behind the screen infront of the sensor. That is total BS. It worked fine on the last ROM. However the calibration, specifically the second method worked for me. I think its just an issue in how Samsung re-writes things for TW and how Google has it written for 4.4.4.

http://xdaforums.com/showthread.php?t=2569141
[Verizon Samsung Galaxy S 4] dspalphamu:
Did you test the calibration with *#0*# or just go ahead and manually change the calibration settings? I ask because it looks like the Samsung codes have to be enabled on Verizon s4
[Verizon Samsung Galaxy S 4] gunnermike:
Enabling them is easy, however that wont do you any good. That code doesn't work for JFLTE. I just did the method one in terminal emulator and it didn't work. Method 2 did though.
[Verizon Samsung Galaxy S 4] dspalphamu:
Thanks a lot for the help. Method 1 in terminal (auto calibration) worked for me. I have been dealing with this for a while and knew it couldn't be dirt on the sensor. Much appreciated.
[Verizon Samsung Galaxy S 4] Mitch8892:
Couldn't get data, LTE or 3g, on the 8/6 nightly from a clean flash. Tried adjusting APNs and network mode but nothing worked. Flashed 8/3 clean and data came right up.
[Verizon Samsung Galaxy S 4] invisiblek:
FYI everyone: tomorrow's nightly will likely break compatibility with all third party kernels. We completely revamped the kernel to base it off newer samsung (and caf) source. Also - we are no longer going to support variant recoveries. You'll need a jflte recovery. Here's a flashable zip of the lastest clockworkmod for jflte: http://www.invisiblek.org/recovery/jflte/jflte_recovery-cwm-6.0.5.0.zip
[Verizon Samsung Galaxy S 4] crossen0:
So TWRP will no longer work, is that what you mean?
[Verizon Samsung Galaxy S 4] FernBch:
No , he said they will no longer support third party recoveries. If you choose to use one, such as TWRP, it may very well work. BUT, if you have issues because of it they will not support it. Officially CM has only supported ClockworkMod. It has been this way from the beginning.
[Verizon Samsung Galaxy S 4] gonzlobo:
I hope you're right. If cm forces cwm, that would be a show stopper for some.
[Verizon Samsung Galaxy S 4] hlxanthus:
Hopefully [MENTION=912474]Dees_Troy[/MENTION] and team will incorporate the need changes for a unified recovery for twrp2

Also, it was not said you had to be on cwm, just a unified jflte recovery and provided a jflte cwm flashable. Hopefully we can get a unified recovery I can stomach to use . . I may not be a regular cyanogenmod user but every aosp ROM out there for the gs4 relies on cm kernel/device trees
[Verizon Samsung Galaxy S 4] bsimpson1:
Is anyone else noticing that WiFi with aes encryption suddenly works at decent speeds?

I'm so happy about this. I've been having to use tkip (and thus no 802.11n) to get above 4mbps but now it's back to 28 Mbps with wpa2-aes!
[Verizon Samsung Galaxy S 4] aphlatoon:
broken camera

Upgraded to the latest Snapshot build and the camera only works while storage is set to internal, as soon as I change it to sdcard, the camera crashes. Rebooted and still same issue, camera keeps crashing after 5 seconds. Tried nightly from 2 days ago, issue is still there.:confused:
[Verizon Samsung Galaxy S 4] lordgodgeneral:
I just updated to the latest snapshot and I can't even get the camera to open to set the storage location, just get the camera has stopped message.
[Verizon Samsung Galaxy S 4] aphlatoon:
Was it working in the previous snapshot? I might have to downgrade if it was.
[Verizon Samsung Galaxy S 4] Lw00d:
where are you guys getting your nightly from.??? the last file i see in cyanagenmod website is M9 8/4 for days old.
[Verizon Samsung Galaxy S 4] FernBch:
I get them in settings>about phone>cyanogenmod updates. I'm set to development channel.
[Verizon Samsung Galaxy S 4] Lw00d:
i just flashed m9, there is no google . i try to flash gapps, still no google. no google account, no google log in. only CM.

what is the deal??

UPDATE:: i figured it out. for some reason when i would download M9 to my pc. then transfer to my phone something would happen that will F up my ZIP. i download 2 times. both came out with same result .. then i downloaded through CMUpdates. it work.
[Verizon Samsung Galaxy S 4] HowardZ:
Yesterday and today's build will not flash.

TWRP error message says it is for jflte and my phone is jfltevzw
[Verizon Samsung Galaxy S 4] crookedview:
What recovery are you using?
[Verizon Samsung Galaxy S 4] HowardZ:
TWRP
[Verizon Samsung Galaxy S 4] rajones19:
Same here. It is as if the install script is unaware of the unified builds - assuming they are still unified?
[Verizon Samsung Galaxy S 4] hlxanthus:
Try the new recovery as it is clearly stated you MUST be on a unified recovery. Might take a bit for [MENTION=912474]Dees_Troy[/MENTION] to get a unified TWRP2 out that will work
[Verizon Samsung Galaxy S 4] HowardZ:
All my backups are with TWRP, which I do not think will work with other recoveries.

I will stop updating cyanogenmod until this mess created by cyanogenmod volunteer developers is cleared up.
[Verizon Samsung Galaxy S 4] hlxanthus:
I have mentioned dees troy several times and just sent him a pm in regards to this. I am sure twrp will be updated once they are aware of the issue and have the time to address it.
[Verizon Samsung Galaxy S 4] gonzlobo:
Yeah, me too & MD5s are good. Looking back, I do recall a dev message saying twcp is no longer supported.
[Verizon Samsung Galaxy S 4] rajones19:
Where is this clearly stated? I am not finding it. I follow this thread daily, and do not recall this. I did see mention a day or two ago that the next build would break compatibility with other kernels. Have had no problem flashing other unified builds (almost) daily since April.
[Verizon Samsung Galaxy S 4] AzureShadow:
Invisiblek makes this statement in post #3196. The exact same post that they announced third party kernal compatibility would be broken.
[Verizon Samsung Galaxy S 4] rajones19:
Thank you, found it. I had read the part about the kernel, obviously - but I had apparently quit reading at that point (also obviously). Duh.

---------- Post added at 11:06 AM ---------- Previous post was at 10:45 AM ----------

Confirmed, after the embarassment of completely missing the part about updating recovery - the current nightly flashes just fine under CWM 6.0.5.0. Now to see if the new kernel fixes the compass issue. Faux kernel has been fixing the compass for me on prior builds, but that apparently will no longer be an option.