yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Darkside14:
Made a factory reset, all LEDs and vibration back to normal, but still strange

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] hust1k:
is 20140405 nightly works with ART?
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
99.9% it doesn't.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Seferi:
I flashed the latest nightly on top of the last M build. When i click the camera it opens on video mode and i can take videos but when i try to switch to camera mode it force closes. Any solutions for that? Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] 0kti:
Full wipe

Send from my Galaxy S4 powered by CM11
[Galaxy S 4 i9505 Original Android Development] marouane80:
Video Recorder issue when stopped !:eek:
[Galaxy S 4 i9505 Original Android Development] exynoss:
Try full wipe.
[Galaxy S 4 i9505 Original Android Development] !crazy:
No issues neither when recording, nor when stopped.
[Galaxy S 4 i9505 Original Android Development] Seferi:
I did a titanium backup of my apps, did a full wipe, flashed the nightly and than downloaded my apps and restored only app data from titanium. Still having force close on camera.. :(
[Galaxy S 4 i9505 Original Android Development] zeus85:
Try formating system and data then reinstall

Gt-I9505_Cm11_Nightly
[Galaxy S 4 i9505 Original Android Development] !crazy:
Do a full wipe,and format, not only wipe. Don't restore anything from titanium. Install gapps linked on the CM page, not one with nexus camera.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
Just out CM11 M5 http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m5-release but says no Jlfte. They Suggest we stick to nightlys if we need and give their reasons.

Says; "..... D2lte and Jflte..

Normally, we wouldn’t comment on specific device families in release posts – under the basic pretense that if the devices aren’t ready, they simply shouldn’t go out. D2 and JF present an interesting issue for us. As we unified GSM and CDMA variants into ‘one build to rule them all’ we’ve been making necessary modifications over the past 2 months or so to address all the feedback we’ve received. However, now that all the variants are served by one build, it would lead to confusion to release a build under the ‘M’ banner that worked great on 90% of the supported variants, but not the remaining 10%. Users of the CDMA nightlies for these devices would likely agree that there are still some niggling issues. It is our plan to address these items prior to green-lighting an M build for these families......Understand that this decision stings. Our device maintainers have done an amazing job with planning, executing and handling all the complexity the unification process involves – and now we’ve held these devices from 2 M releases in a row. However we stand by the fact that release decisions should be based on the actual quality of the release; even if it means making an unpopular decision. If you are in desperate need of a D2/JF ‘flash’, then the nightly channel builds are available for that purpose. Else, trust that we make these decisions based on the responsibilities you place on this team. /tangent.."
[Galaxy S 4 i9505 Original Android Development] Seferi:
But I'll loose all my data. Is there a way to restore my app data?
[Galaxy S 4 i9505 Original Android Development] vedko:
Sure there is, one is mentioned in !crazy's post (Titanium). However, most probably it is your data that is causing the FC's, so wiping data and then restoring it is contradicting.

What sometimes worked for me was cleaning data only for the problematic app (in settings), you may try that first. If it doesn't, full wipe without any data restoration is the only way forward.
[Galaxy S 4 i9505 Original Android Development] NZgeek:
I think that there's a pretty good chance that the data restore is not at fault, especially if you've only restored data for user apps, not system apps.

I would suggest that you boot into recovery, do a system backup, wipe /system and /data, then flash the ROM without GApps. Boot, get things set up, then see if the camera still forces closes. If it does, there would appear to be a genuine issue with the camera.

If it works fine, the next step is to install your GApps package and wipe /data. When you go through the setup process, choose to skip logging into your Google account. Try the camera again, and see what happens. If it force closes then your GApps package is probably replacing the camera with something flaky. You'll probably need to find a different GApps package that didn't include a camera, or which uses a different camera.

If that's still fine, wipe just /data and set your phone up again, this time signing in and letting your apps restore. Don't restore any data yet. Try the camera again. It's highly unlikely, but a force close here would indicate that one of your apps is messing with the camera. You'd need to remove them one by one, checking the camera between each, to see which one is causing the problem.

The last step is to restore data using Titanium Backup. Only restore data for user apps, and system apps that are restored via XML (e.g. messaging, call los). If this finally causes the problem again, you'll need to start wiping data for individual apps until you fix the problem.

Once you've figured out what the source of the problem is, you should be able to work around it and get everything back to normal.
[Galaxy S 4 i9505 Original Android Development] zeus85:
Use titanium backup to uninstall camera apk and reinstall the latest nightly manually through your recovery this would eliminate the chance of the camera being replaced by your gapps

Gt-I9505_Cm11_Nightly
[Galaxy S 4 i9505 Original Android Development] Pomp92:
Hi guys, can anyone tell me where I can find a list of known problems of these nightlies? For example, the LTE/3G switch, the infrared port...

Thanks ;)
[Galaxy S 4 i9505 Original Android Development] vedko:
I don't think there's any such list. The nighties are more or less bug-free, definitely stable and fine for daily use.

There are of course small things, like ART being broken in the last few builds and for me the notification area flickering when you pull down the bar (but I haven't checked this in the last few days).

The 2 things you specifically asked about are definitely working.

And yes - you may want to read last few pages of this thread to check what others are reporting.

EDIT: Just checked the notification area flickering - it's still present, tested when running Waze (animation on the screen) and pulling down the bar... my personal feeling, however, is that I observe it less often than some months ago.
[Galaxy S 4 i9505 Original Android Development] FrA1l3:
Here everything works, even what you mention :good:
[Galaxy S 4 i9505 Original Android Development] sronweb:
Nightly is just a name. I know some roms called "stable" having much more problems... :)
[Galaxy S 4 i9505 Original Android Development] dngr:
sgh m919 ext sd encryption

Hey Guys

On latest cm11-nightly, enabled phone encryption, worked like a charm.

I'd like to also encrypt the external sd card, but cm11 does not provide this option. Any tricks to manage to encrypt it?

Thanks, dngr.
[Galaxy S 4 i9505 Original Android Development] xeph20:
Can't wait for the nightly of 8 april to release soon

It should fix the pedometer (for s Health)

Searched a lot for that fix
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Cyanogenmod network down so we might have to wait a bit for this one :confused:
[Galaxy S 4 i9505 Original Android Development] xeph20:
yeah,

I thought it would be something like that :(

I also noticed their main site didnt work

These 2 do work

http://download.cyanogenmod.org/?device=jflte&type=

http://www.cmxlog.com/11/jflte/#
[Galaxy S 4 i9505 Original Android Development] Mittaa:
BTW S Health is from Samsung? How did you get it to run on CM? And do you have a link for me?
[Galaxy S 4 i9505 Original Android Development] !crazy:
Probably because of heartbleed bug. I presume they are updating servers, changing keys or something. Although it doesn't have to be related, the coincidence is quite nice.

I'll just stop caring about security, and start looking for some pure useless fun... Oh, but then they'll do profiling and discover something we our self don't know about our self, and then... Yellowstone? Or who knows? :). Then I would be thinking, 'those security holes, observation and **** were not that bad at all...'

Is this off topic?
[Galaxy S 4 i9505 Original Android Development] !crazy:
Ok, it is not heartbleed, it is apparently because of the widespread routing outage of the primary datacenter. Info provided by mcampbellsmith, maintainer of the CM for i9305 S3.
[Galaxy S 4 i9505 Original Android Development] zeus85:
Anyone have a link to s health please I'd also like this installed

Gt-I9505_Cm11_Nightly
[Galaxy S 4 i9505 Original Android Development] xeph20:
Well atm it does not work.

But i noticed a fix is coming in the next nightly for the sensor.

So i just assumed it would work after the next nightly.

Well hoped is a better word.

And there are some posts on xda who provide s health and sensor APK diffrent versions.

Also samsungapps APK

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Original Android Development] misha0209:
hi there,

i installed an app to see the charging current of the phone, and it does not work on a nightly from 2 weeks ago.

can someone check check on newer nightly and tell me if it works?

i tried galaxy charging current and current widget.

both only show the theoretical value (nominal), not the actual.
[Galaxy S 4 i9505 Original Android Development] xeph20:
galaxy charging current works fine on my nightly (5th of april)

but i'm waiting for the next release D: they couldn't release yesterday because of connection problems and there is a fix i want to try :/

[Edit]

Omg the waiting is killing me ... i also waited for hours yesterday blah

Always when i have a buttload of free time, the things i need to do are not possible to do

And then when i don't have the time it all flings at my head
[Galaxy S 4 i9505 Original Android Development] xeph20:
Hi,

I tried this an the Test says on both sensors false

i copied the 2 xml files into etc/permissions and changed the permissions of the 2 files like you said

Do you know what the problem might be?

And if its fixed does S health work? because it always crashes on me

thx
[Galaxy S 4 i9505 Original Android Development] misha0209:
thanks for the input.

so you have numbers in all 3 fields: reference, maximum, and average? interested in the maximum, that one does not work for me..

also, haven't visited for some time. are there any new bugs that should stop me from flashing latest nightly?
[Galaxy S 4 i9505 Original Android Development] _Sofos_:
Made the changes and it shows true. Basically indeed it corrects step counting for many apps but not for S Health. It doesn't work and if it needs tw framework.. it will probably never work with Cm itself or Cm based Roms.

If the step counter sensor doesn't get fixed in the next nightlies I can make a flashable .zip btw.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
This fixes ART

http://review.cyanogenmod.org/#/c/62128/

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] xeph20:
only "now" and "average" shows a number but i think that always was the case on my phone

Also with stock + root

The only thing i do not like about CM is that S Health doesn't work

My job requires a lot of walking and it was helpfull in giving me an insight in how many kcal i could eat.

i tried NOOM but it doesn't count while the screen is off (atleast it didnt for me)

Does anyone know a better pedometer then S heath? that doesn't use a lot of battery?
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Walkroid open source ... link

Maybe not sexy but doing exactly what is needed ... counting steps.

Working fine screen off and have a tiny non bragging widget :D
[Galaxy S 4 i9505 Original Android Development] emanuele1986:
My friend updated his i9505 with the nightly of 04/09/14 from nightly of 03/22/14. Perhaps he used art and when he installed the new ROM the phone started but IT goes Stuck with a continuos message NFC process is blocked etc.. He had to reinstall the nightly of 03/22 becouse also with the 04/07 nightly he got the same problem.

So, are there problem with the latest nightly?

Other question. He left the baseband of 4.3, he have to install the last modem available?
[Galaxy S 4 i9505 Original Android Development] BustedFly:
Hey, could you please tell how high your battery drain overnight is (not in flight mode, No WLAN / GPS on)

Have in 8h 2% / h

Find the somewhat high.

BBS indicates no Waklocks.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
Jus wanna report installed 409 nightly (was fresh install). Everything works fine. Except it wiped out my APN (only thing I didn't back up) as the Vodafone Australia APN device settings from rom are incorrect. Ie no mobile data. Easy fixed by getting correct APN from Vodafone.com.au site. Also Restore from ex SD card by Titanium didn't work at first, but after flashing exSDCardFix all works OK and restored all 100+ apps and data no problems at all from exSD card. Everything works fine now.

But my Antutu score seems low..25k?. Is that normal? But device feels snappy compared to TW (which had 28k antutu)?
[Galaxy S 4 i9505 Original Android Development] NZgeek:
Part of the reason is because Samsung cheat at the performance test. They've added code to the kernel that keeps all 4 cores at max clock speed when certain benchmark software (e.g Antutu, Quadrant) is in use. You can probably get a similar effect by using the performance governor.

Another part of the reason is that benchmarks are utterly unreliable. Running the same benchmark several times in a row, on the same device with minimal apps installed and network turned off, can give you results that vary by up to a few percent. When you turn on the network connection and install a bunch of apps, any hope of meaningful data flies right out the window.
[Galaxy S 4 i9505 Original Android Development] 135Shadowsoul:
Problems with Update

Hi @ all,

i have got some problems with updating. im running CM11 nightly 20140407 and CMupdater is not able to find any new update; there is 1 from yesterday i could download (downloading works) but if i try to check for new updates, i get message that searching failed and i should test internetconnectivity and try later. well, i tryed some w-lans and tryed c.a. 3h now to get download. server down or my CMupdater crazy? Like i have said: downloading nightly from yesterday would work, but i decided to skip and falsh todays nightly

EDIT: does manually download (with computer) and manual install (recovery) use custom recovery scripts and save my changes? (none of them is responsible for this problem)
[Galaxy S 4 i9505 Original Android Development] HetsHumbucker:
Seems to be a server related problem. searching for updates doesnt work here either.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Had same problem and solved by wiping CyanDelta data and download full ZIP
[Galaxy S 4 i9505 Original Android Development] hamidoo:
After you do the fix, you should see both sensors true.

Not sure about S Health, bu I think it will not work as it needs Samsung's TouchWiz framework/interface.
[Galaxy S 4 i9505 Original Android Development] 135Shadowsoul:
CyanDelta = CM updater? if yes: wiped data+cache => still no connectivity (download with computer worked)
[Galaxy S 4 i9505 Original Android Development] Mittaa:
CyanDelta ...
[Galaxy S 4 i9505 Original Android Development] LiquidBee:
Yep, im having about 1.5-2%/h as well, even with Alucard's kernel. Im on 20140410-nightly.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
ART will be fixed in the next nightly.

http://review.cyanogenmod.org/#/c/62128/

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] kiwi_de:
Problems with charging

I'm running latest CM 11 (cm-11-20140410-NIGHTLY-jflte) and since 3 days I've got a problem with charging. Screen during charging won't turn off, even when phone is powered off. Always see the Battery charging logo. Cleared cache / dalvik but always the same. Phone seems to stuck.

Anyone else with this problem?

Modem is XXUFNC9
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Why is ART so important? Does it really boost performance and battery life in such a degree, that it's worth trying out?
[Galaxy S 4 i9505 Original Android Development] !crazy:
To such degree that it is worth trying out... Uau... Just try it, and see for yourself...

---------- Post added at 11:24 PM ---------- Previous post was at 11:20 PM ----------

If you haven't done formating your partitions for a while, that would bring the best performance improvement of that kind, but it doesn't last really long, unfortunately. Maybe we'll se f2fs soon in our kernels, that could fix the fragmentation, or whichever issue we have with ext4.
[Galaxy S 4 i9505 Original Android Development] sronweb:
No issue here. Just tested. I would test another rom for confirmation but look to be an hardware issue.....maybe. Doing a recovery back up first then you can restore quickly CM11.
[Galaxy S 4 i9505 Original Android Development] My Public:
I can confirm: ART is working again with cm-11-20140411-NIGHTLY-jflte.zip

:victory:
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Of course. Like I said. :)

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] kiwi_de:
I tried Omega 28 instead, no screen/stuck problem there. Must be something CM 11 specific.
[Galaxy S 4 i9505 Original Android Development] 135Shadowsoul:
Download and update with CMUpdater works again, dont know, why. Updated yesterday to nightly with download, put it into cmupdater folder and updated normaly and tody tryed 2h ago to update => no connectivity but 5 min ago i found the update for today, downloaded with cmupdater and flashed it => it works

i think its just an temporary problem not depending on the CM nightly version u are running; yesterday a friend has same problem with his I9100
[Galaxy S 4 i9505 Original Android Development] ZeroAE:
Is the latest update supposed to update CWM recovery from 6.0.4.4 to 6.0.4.8?

Cause it didn't

At first, when I tried to enter CWM the phone just restarted, but after trying again, I entered the old CWM, and it tells me again and again that the root is broken.

Is anyone else having this problem?
[Galaxy S 4 i9505 Original Android Development] 0kti:
No problems on TWRP 2.7.0.1
[Galaxy S 4 i9505 Original Android Development] geomax45:
ROMs and recoveries are not related. Flashing a ROM will not affect the recovery you have installed. You need to update your recovery independently.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
Agree. (I used PhilZ Touch to flash CM11 no problem at all.)
[Galaxy S 4 i9505 Original Android Development] ZeroAE:
Yeah, I thought that too, but I'm confused with this on the changelog:

http://review.cyanogenmod.org/#/c/62381/

If it's not about CWM, then what it's about?
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
I can Confirm art working here also. (CM11 411). Could b psychosomatic but definitely Feels snappier.
[Galaxy S 4 i9505 Original Android Development] rodrigoger:
Sorry,

But how can I make ART work with my CM11 last nightly version?

Everytime I change the option from Dalvik to ART, after reboot, it comes back to dalvik...

I have a lot of apps and xposed framework too.

Do I have to wipe data, dalvik and cache before? And then, can I recover my backups with Titanium?

Tks a lot!
[Galaxy S 4 i9505 Original Android Development] 0kti:
Xposed don't work with ART
[Galaxy S 4 i9505 Original Android Development] emanuele1986:
Someone can post the link for photsphere full working with cm11?
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
NEW THEME ENGINE is finally merged in cm11. Byebye old ics theme engine...

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] NZgeek:
On many phones (like the S4) the recovery is completely independent of the ROM. It's stored in a separate partition and has its own separate kernel, and doesn't get touched when you update or change your ROM.

Other phones (like the S1 and S2) don't have a separate recovery. It has to be built into the kernel, meaning that it will change depending on your ROM.

The change logs show the change for the S4 because the recovery is a standard portion of the build. It just doesn't get shipped as part of the S4 builds.
[Galaxy S 4 i9505 Original Android Development] stalvatero:
Hi all, i'm from Italy. With stock ROM i've H+ icon when connected to HSDPA. Now on i see DC... what it means?

Another question... is it possible to let Soft Keys backlight ligths only when i touch them, instead of let them light up also when the display is touched? (as for stock or GPE rom). If this is not possible, is there any way to decrease light voltage?

Thx a lot.
[Galaxy S 4 i9505 Original Android Development] aleksik:
DC means Dual Carrier which should be faster than the HSDPA. I have never had it, but that's what I've read. For the button backlights, every AOSP ROM I've tried has the same problem so I have had to disable them.

Edit. Just flashed the 11/4 nightly over Mahdi ROM and noticed that I also have the DC network icon now.. :eek: As I previously said, I have never had that icon before. Has something changed in CM lately, because I have been using other ROMs almost for 2 months?

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] !crazy:
This is not true. Last versions of xposed work with art, but they maybe cause problem like described above, when switching. One maybe needs to temporarily remove xposed, and after switch to install it again.

I don't say all modules work fine, but xposed, and some modules I use(d) (greenify and Android tuner) work flawlessly.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
R u on latest nightly? I am on 411 nightly. I just went to developer options >select runtime >select Art. Reboot. And wait for "android updating apps message" . I didn't need to wipe Dalvik or cache. All apps working well. Except my Google play was giving me strange message "Google play sound searching" and wouldn't connect to internet. But a hard reboot fixed that and Google play working fine. All apps fine now. And device definitely feels quicker..

Separately I found my Titanium backup works better and more stable with updated Chainfire's supersu.

---------- Post added at 09:40 AM ---------- Previous post was at 09:31 AM ----------

Same here. I was on KK 4.4.2 TW leaks before never had DC icon, and as soon as I updated to CM11 from 409 nightly I began getting the DC Dual Carrier icon. Could b coincidence in timeing dunno. But I feel DC is faster for sure. As it usually take me ages to download CM 11's 200mb+ nightly's but my last download of 411 nightly with DC was super fast.
[Galaxy S 4 i9505 Original Android Development] Ky0sHiR0:
How did You install xposed after switch to Art? When i install IT, it automatically after reboot switch to dalvik? Should i unistall before switch everything? (xposed , framework & greenify)?

Wysłane z mojego GT-I9505 przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] petrus764:
Xposed doesn't work on art regardless of what he claims.

http://xdaforums.com/apps/xposed/framework-xposed-rom-modding-modifying-t1574401
[Galaxy S 4 i9505 Original Android Development] Ky0sHiR0:
In this case...

BTW. Greenify can keep push notifications without xposed?

Wysłane z mojego GT-I9505 przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] ZeroAE:
Is anyone's Xposed apps not working with today's nightly?

The framework tells me it installed successfully, and I rebooted, but no change is showing.