yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] misha0209:
No problem m8, just that i had no idea that there was a button for it. now i do, thanks!

on the other hand now that i do, i played around with the combinations between the 2.

is it just me or does it work the same for everyone?

so 2g/3g selector set to 3g (actually it says 2g and 3g on the button).

now if you tap lte, it switches to lte. NICE :)

if you tap lte again, goes back to 2g3g. good.

now i set 2g.

tap lte, nothing happens :(

the main goal of using 2g (for me at least) is to save battery.

what i would really want, is an easy way of jumping between 2g and lte.

when you are on lte, the phone will stick to the fastest network, so 3g is implicitly covered, because if there is no lte, 3g is used. when you want to save battery, just jump to the slowest of the bunch. simple.

so, now, i am complaining as to why things were implemented like this.

i would not use the 2g3g selector at all, if LTE worked like this

lte on, you're on lte

lte off, you jump back to the last network used before lte button activation.

would this not make more sense?

but then again, maybe it is just my phone :)

anyhow, thanks again for letting me know the button exists :P
[Galaxy S 4 i9505 Original Android Development] !crazy:
You will not find nightly so easy which is so ****ed up as M10.

M10 is/was a no no, keep the finger away from it, 'release'.

It happened at the time when the CM 11 code (at least for this device.) reached its worst level, and didn't fix none of the major bugs which exploded with new code patches shortly after M9 release.

Everyone who uses CM on a Samsung device should definitely visit a place like this in order to inform him/her self about state and the condition of the current builds.

As other people said, you are best with wiping, and I would say formating everything. If you can, format also the internal sdcard.

If you want to continue using CM, I would recommend the nightly from 11.11, I still didn't try today's build, but if you have time, try for your self, and see how it feels for you ☺. M12 is probably not that bad too, so if you like the M letter so much, you'll probably be ok with M12 too.
[Galaxy S 4 i9505 Original Android Development] sancho_panzer:
Who the heck are you? Go learn some manners before vomiting your preconceptions to people. End of talk.

Tapatalk signature:

Device:

Samsung Galaxy S4 (GT-I9505)

ROM:

CyanogenMod 11/M9

Kernel:

Default CM11/M9 3.4.0

Recovery:

TWRP 2.7.1.0

Modem:

I9505XXUGNE8

Device:

Nexus 7 (Grouper)

ROM:

CyanogenMod 11/M9

Kernel:

Default CM11/M9 3.1.10

Recovery:

TWRP 2.7.1.0
[Galaxy S 4 i9505 Original Android Development] misha0209:
thanks for the thoughts :)

i'll ask next time i want to update for sure.

like i said, i got it wrong, my go to m build was 9.

i flashed m10 and m11 and after each one i did a full wipe, and restored my nandroid of m9 (am i to understand i am not safe, and should still do a full wipe like you said above?)

now, after the very scientific resolution to my problem, i'm sticking to m12 for a while :)

i use to be a fan of the nighlty branch.. would flash latest once every 2 days.

until that one time when i updated, and after 2 hours the screen of my S2 wen black, then a little android popped up saying kernel panic mode.

after i could not restore nandriod backup because CWM said it had no write rights on the kernel, i attempted to go into download mode, and flash the latest samsung firmware. odin got stuck on kernel, and after waiting it out for 2 hours, i unplugged. that was the last time the screen or the phone were ever on :(

so i decided to take it easy.

i thought that m builds were made with the most stable code from the last month of nighltys, or at least a renamed version of the most stable nightly of the month.
[Galaxy S 4 i9505 Original Android Development] giodeluigi:
Sorry, a little question the make things clearer:

Cyanogenmod11 M12...is a little bit confusing here.

What M stands for?

Thank you
[Galaxy S 4 i9505 Original Android Development] sancho_panzer:
http://androidcommunity.com/cyanogenmod-explains-what-m-releases-are-20140310/

Tapatalk signature:

Device:

Samsung Galaxy S4 (GT-I9505)

ROM:

CyanogenMod 11/M9

Kernel:

Default CM11/M9 3.4.0

Recovery:

TWRP 2.7.1.0

Modem:

I9505XXUGNE8

Device:

Nexus 7 (Grouper)

ROM:

CyanogenMod 11/M9

Kernel:

Default CM11/M9 3.1.10

Recovery:

TWRP 2.7.1.0
[Galaxy S 4 i9505 Original Android Development] giodeluigi:
? perfect, thank you!!
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
Just update to 1113 wow lot of delta files 30mb...

All smooth... great! I saw boot animation some fix related but only new resolutions... I wish they put the new CM logo as boot animation... Would be awesome!
[Galaxy S 4 i9505 Original Android Development] foxbatul:
1113, perfect. better than m12 . battery life restored on this build, on M12 was poor.

I'll stick with this build now( my humble opinion - from 0711 , all other builds had some issuess ). I did jump back from each nighlt ( even from M12 ) to 0711.
[Galaxy S 4 i9505 Original Android Development] misha0209:
thanks for the info, think i'll jump on to 11/13 myself (don't know just how bad it will be, dirty flashing a nightly on an m build).

in my short time with m12 i can confirm what you said with the battery life. it ate up a lot in my ~5 hours with it.

does anyone here use car stereo over bluetooth, and poweramp on cyanogenmod?

i have a peculiar thing happening with this combo since before m9. on older builds this was a no issue.
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
Guys stay with the nightlies... Forget about M releases.

Use cyandelta and you will be happy forever! ;)
[Galaxy S 4 i9505 Original Android Development] FernBch:
Basically the designations are:

Nightly: Experimental, things may be broken and contain bugs. Do Not file bug reports. You can post issues in the JIRA Nightlies Regression when things are borked in a newer build. Be sure to include a logcat and a detailed explanation of the issue.

M (Milestone) or Snapshot: the current state of the development process. May have bugs. Bug reports can be filed as above. They usually are anywhere from a week to as much as a month behind the current nightly as far as what has been merged from Gerrit.

RC or Release Candidate: Most things should be working. Bug reporting is accepted. Please include a logcat.

Stable: Just what it means. Everything should be working. Bug reports are accepted as above.
[Galaxy S 4 i9505 Original Android Development] mupet0000:
Is anyone having problems with mic volume? My mic is extremely low volume, especially noticeable when making whatsapp voice notes or using voice recorder. Playing back voice recordings at full volume are barely audible. This is not a problem when using another rom. I've tried using the Googymax kernel and increasing the mic gain to maximum, and even though it's louder, it's still quieter than stock or google edition rom. Any ideas?
[Galaxy S 4 i9505 Original Android Development] dmb219:
Noticed this with Google Now - little or no response at normal voice levels.
[Galaxy S 4 i9505 Original Android Development] morpheus302:
Same thing here. The difference is obvious between TW and CM mic sensitivity
[Galaxy S 4 i9505 Original Android Development] 78Staff:
FWIW, latest nightly fixed this for me, 11/13 that is.
[Galaxy S 4 i9505 Original Android Development] exynoss:
Which gapps you guys advise.

Is their any link between gapps and battery. Till now I using PA gapps
[Galaxy S 4 i9505 Original Android Development] tomurbanowicz:
horrible audio quality

It is big problem in audio drivers in CM/AOSP/etc. becouse of "open audio drivers". Quality of audio/mic is horrible - non only problem with level, but normalization too - big audio distortions with video recording in high levels of noise - like a concert. In TW everything is OK.

Here is my sample: http://prostozfona.blogspot.com/2014/11/stock-vs-aospcm11mokeespiritmahdi.html
[Galaxy S 4 i9505 Original Android Development] nds850:
IR still don't seem to be working in M12 :(
[Galaxy S 4 i9505 Original Android Development] feraay:
It seems to you but its wrong ...

Works perfect
[Galaxy S 4 i9505 Original Android Development] pjkiener:
Anybody know where screen record went? Can't find it in Display and Lights anymore.
[Galaxy S 4 i9505 Original Android Development] !crazy:
Yup, the issue is present on probably all 'newer' (from S3) Samsung devices.

I have ignored this issue before, and was thinking only about hardware, and maybe price (was getting devices for free or very cheap, and wanted to get 'best' value, but I could than just switch to iPhone), but this has changed. Running a CM or AOSP on Samsung is a no go for me any more (but will probably continue doing so with this device.). Not that I am angry on CM developers or similar, has nothing to do with them, only on Samsung.
[Galaxy S 4 i9505 Original Android Development] tomurbanowicz:
The problem it was in my Galaxy S2 too.
[Galaxy S 4 i9505 Original Android Development] ed_bracam:
Hello, I downloaded and Installed CM11 M12 for Galaxy S4 GT9505. It worked fine except Android Wear for my LG G Watch R. The result was the message "Connected, running sync loop" on the android wear connection notification and a very big battery drain of the watch (6% per hour, normally it's about 2%). I didn't find solution and I needed to switch for a Google edition rom (4.4.4) where my watch doesn't drain. How to solve this problem?
[Galaxy S 4 i9505 Original Android Development] Mystikal57:
same notification for me but with my sony smartwatch 3 !

Edit: we are not alone:

http://xdaforums.com/android-wear/help/running-sync-loop-t2809301/page2
[Galaxy S 4 i9505 Original Android Development] tasosf:
And my pebble says : "Connecting to Pebble" although it IS connected. Maybe it's related?
[Galaxy S 4 i9505 Original Android Development] misha0209:
anyone tried 14/11 nightly?

i see "UsbSettings: Fix UMS mode (android_packages_apps_Settings)" in changelog. is mass storage mode back?

i'd love to install to check, but i finally have a good thing going on here with 13/11.. don't want to loose that :)
[Galaxy S 4 i9505 Original Android Development] tasosf:
USB OTG works on my 13/11. It wasn't supposed to work?
[Galaxy S 4 i9505 Original Android Development] snakecharmer23:
Read the commit comments... they just tweaked it a little.

http://review.cyanogenmod.org/#/c/77001/
[Galaxy S 4 i9505 Original Android Development] !crazy:
I'm not surprised. I had S2 for a short time, and after having galaxy nexus, which worked in that regard, but it is Nexus, so a bit different story. Good thing was that one could unlock sim with a software hack, which was available in the market back then. I just customized it a bit and gave it to my father.
[Galaxy S 4 i9505 Original Android Development] Jacopo97:
Hi guys, I left cm11 for several months so I don't know well what to search in cyanogenmod's site (jflte?) And what's the best snapshot/nightly? Thanks in advance and excuse me for my bad english
[Galaxy S 4 i9505 Original Android Development] fdc77:
when i open my smart cover, the phone doesn't unlock automaticaly in recent nightly , is this function removed? or is a bug?
[Galaxy S 4 i9505 Original Android Development] exynoss:
Try 13/Nov nightly, it's rock stable.

and download it from https://download.cyanogenmod.org/?device=jflte
[Galaxy S 4 i9505 Original Android Development] Hyperfish:
13/11 nightly made my phone get really hot when playing video. :eek: How random.

Gone back to M12.
[Galaxy S 4 i9505 Original Android Development] carole6m:
Dirty flashed 11/13. Wifi and bluetooth seems to be working fine now. Disconnected and reconnected many times and it worked every time. :D
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
agree.
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
No Bluetooth still disables Wifi, if you wait long enough. Just switch both on and wait...

The new version of the CMFileManager crashes if you press the menu button on the bottom left of the device. I replaced it with an older version for now.
[Galaxy S 4 i9505 Original Android Development] misha0209:
usb otg? i'm sorry but i do not know what that is :(

edit: did a quick google search on OTG. no that is definitely not what i meant :)

i was talking about mass storage mode, when you connect to a pc.

in 13/11 all i see is media device (MTP) and camera (PTP).
[Galaxy S 4 i9505 Original Android Development] exynoss:
There is no maas storage mode from long time in cm. If you need maas storage then you need some mods or third party support
[Galaxy S 4 i9505 Original Android Development] nds850:
It worked fine for me before. I use Smart IR Remote. Anyone have any suggestions what could be wrong? Thanks.
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
Mass storage mode only works for the external SD for technical reasons. Internal can still be accessed via MTP / camera only!
[Galaxy S 4 i9505 Original Android Development] snakecharmer23:
I was able to duplicate this app crash. To clarify, it happens when pressing the hardware menu button, not the one within the app itself.

I submitted a bug report.

Disclaimer, I dirty flashed 11/13 nightly over a previous one.
[Galaxy S 4 i9505 Original Android Development] carole6m:
Used bluetooth and wifi and played pandora on the speaker for over half an hour yesterday and today with no issues. In previous builds it would cut off after a song and wifi would be greyed out until I reboot the phone. Right now I can disconnect and reconnect with no problems.
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
Which modem versions are you using? Maybe i can try the same
[Galaxy S 4 i9505 Original Android Development] carole6m:
I have the sprint L720 with the latest NG2 modem
[Galaxy S 4 i9505 Original Android Development] bernarbernuli:
Hello, you can flash by via recovery M12 having the installer version (build 11.0-InstallerXNPQ32P) of "CM Installer" installed ???

Some time ago you could do it without problems, but now, in the recovery shows me the following flash error:

Can´t install this package on top of incompatible data. Please try another package or run factory reset.

E: Error in /storage/sdcard1/cm-11-20141112-SNAPSHOT-M12-jlfte.zip

(status 7)

Installation aborted.

Is it possible that the CM team has a kind of lock on "updater-script" or something similar to prevent the jump from one installer version to nightly or snapshot"?

What do you think that might be? Has anyone tested lately flash a snapshot with installer version?

I have the latest version of Philz Touch Recovery, v6.58.7.
[Galaxy S 4 i9505 Original Android Development] feraay:
Wipe cache and dalvik cache
[Galaxy S 4 i9505 Original Android Development] bernarbernuli:
Believed comment was left, but it is done well.
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
[MENTION=2887670]canariohippie[/MENTION] you can edit out that check in the updater-script :good:

L

Gesendet von meinem One mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] bernarbernuli:
How to do that?

I ask again, does anyone lately gone from installer version to Snapshot by via recovery?
[Galaxy S 4 i9505 Original Android Development] PapaMag:
May have to come back over and check out the latest nightly, what I have now is pretty dang smooth
[Galaxy S 4 i9505 Original Android Development] lauterm:
I think error 7 means you need a newer recovery.
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
[MENTION=3929182]lauterm[/MENTION] no, that's wrong. It was written why the installation stopped. It didn't pass the cm restrictions for dirty flashing (which I don't know)

[MENTION=2887670]canariohippie[/MENTION] could you post the updater-script of the M12 please for me, then I'll edit it for you

L

Gesendet von meinem One mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] BurlaMatto:
or a compatible one :P
[Galaxy S 4 i9505 Original Android Development] sancho_panzer:
I'm still on M9, very stable and everything working fine, but I miss the adrenaline of flashing and make my device better. I've been following cmxlog.com but was waiting for the last stable Kitkat.

Guys, sorry to bother with this question, maybe I'm asking to much mind gymnastic. Do you remember/see any real benefits from M9 to M12? Do you think that it is worth?

Tapatalk signature:

Device:

Samsung Galaxy S4 (GT-I9505)

ROM:

CyanogenMod 11/M9

Kernel:

Default CM11/M9 3.4.0

Recovery:

TWRP 2.7.1.0

Modem:

I9505XXUGNE8

Device:

Nexus 7 (Grouper)

ROM:

CyanogenMod 11/M9

Kernel:

Default CM11/M9 3.1.10

Recovery:

TWRP 2.7.1.0
[Galaxy S 4 i9505 Original Android Development] jumpers:
got errors 7 with corrupted zips.

the best, is to download a proper zip from download.cyanogenmod.org, and checking signatures from the file before flashing.
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Why tell him to do something if it won't change anything?? In the updater-script of CyanogenMod is a check if this build can flashed ontop of the current installed build. And if it says it can't be upgraded you know the zip was fine. Redownloading won't change anything here.

L

Gesendet von meinem One mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] BurlaMatto:
md5 is checked if you use rom update feature :P, so there's no way you can start flashing a corrupted zip
[Galaxy S 4 i9505 Original Android Development] bernarbernuli:
yes, it is true, among other things, but it is not the case.

My recovery is Philz Touch v6.58.7. That's the latest version.

I have also tried alternative as TWRP recovery.

Thanks for your interest.

Down in the post, you have "updater-script"

Perhaps, as I said in previous post, it does the script have a safety mechanism to prevent the jump ?? In the lines of code "assert"?

I understand if you need to edit "update-script" can not jump Snapshot Installer to normal, right? Is this correct, no?

This method would not work for the novice user as this is somewhat more laborious. Many novice try to jump from installer to Snapshot not having Installer updates since August.

No, "Status 7" is not shown due to a corrupt file. If so the error code "Signature Verification Failed E" would be displayed.

However, I checked the md5sum, and it is correct.
[Galaxy S 4 i9505 Original Android Development] maquille:
Hi everyone

Don't know about you, but my home button (when viewing running applications, for example) is significantly less responsive than my old s2 and my s4 mini! Would you have a solution to remedy to this?

I tried the navigation bar but it does not suit me.

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] Spud37:
So i noticed something on both of my devices running M12 that if you have the setting the setting for the clock to be in the middle it will disappear sometimes, and it can be hard for it to reappear. It looks like whenever another notification comes up the clock disappears for it to kinda flash the first few words in the status bar and then just doesn't come back. Is that a known problem?
[Galaxy S 4 i9505 Original Android Development] cristianpark:
HDMI Output Working!!!

Hi guys

I have M12 on my i337m and I tested today HDMI Output with the cable I bought for my i747 previously. I don't know if there are work on there by CM guys or the hardware of the S4 is more CM friendly for this but the HDMI Output is working with CM11!!! I'm very happy because this is a great spec for me and being able of use it with CM is just great

Attached a picture of CM on my TV, test it disconnecting.connecting again and everything works just well, even playing music with screen off worked :laugh:. If you need further tests, just let me know
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
[MENTION=2887670]canariohippie[/MENTION]

Here's the edited file. With that one the update should work flawless ;)

L
[Galaxy S 4 i9505 Original Android Development] vedko:
One difference I remember is that the quick launch buttons (toggle WiFi, GPS etc) in the notification bar are "squeezed" to fit into screen, so that you don't have to scroll right and left.

There will be others I think, like "Pass widget" option - although I have no idea what it does.
[Galaxy S 4 i9505 Original Android Development] sancho_panzer:
Thanks a lot [MENTION=1020589]vedko[/MENTION] , what about battery life, wifi/Bluetooth, IR and stability?

Tapatalk signature:

Device:

Samsung Galaxy S4 (GT-I9505)

ROM:

CyanogenMod 11/M9

Kernel:

Default CM11/M9 3.4.0

Recovery:

TWRP 2.7.1.0

Modem:

I9505XXUGNE8

Device:

Nexus 7 (Grouper)

ROM:

CyanogenMod 11/M9

Kernel:

Default CM11/M9 3.1.10

Recovery:

TWRP 2.7.1.0
[Galaxy S 4 i9505 Original Android Development] O-T:
I hope that the upstream open issue in JIRA got more attention: Manual carrier search error /unable to select manual carrier. See https://jira.cyanogenmod.org/browse/CYAN-4902

JIRA 4902 get some added reports by i9505 and i9295 users that knows they have same issue. The rest of CM11-jflte camp and all CM11-jactivelte has the error too and stay silent. [MENTION=2385005]invisiblek[/MENTION] (isn't that also dev. of CM11 jflte?) has ticket assigned, still unresolved.

What I don't understand is how an issue with impact on every QualComm based phone functionality and phone bill can stay open for 3 months... Can't find comments about progress in the JIRA issue. Perhaps I'm not searching in best places.

I know the choice to join CM project is without any promises or agreement as compared to a commercial product. Only trying to indicate that solving the Manual carrier search error would be great for a lot of people.

Thanks
[Galaxy S 4 i9505 Original Android Development] erikasnoske:
Totally agree with you - those devs are lazy. Check what I have reported: https://jira.cyanogenmod.org/browse/NIGHTLIES-355 STILL NOTHING
[Galaxy S 4 i9505 Original Android Development] maltinbay:
hi all, i am total noob of custom roms, and wanna install my first one.

is this have serious bugs compared to touchwiz?

i am have to install kernels or modems?

is there any tricks or problem about installition?

thank you so so much.
[Galaxy S 4 i9505 Original Android Development] Cozmos23:
all bash bug security holes fixed.

Other fixes/improvements.

But I tried M12 and had a lot fcs on different apps but I'm on f2fs and art. Also used Gapps...

M11 on f2fs and art without gapps runs awesome
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
Guys anyone flash the last nightly?

Im on 1114... I wanna know if they fix c. File manager. Anyone know?
[Galaxy S 4 i9505 Original Android Development] mikecantreed:
M12 is running flawlessly over here. Perfect BT and wifi. I'd try a full wipe if I were you.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
for me, installed everything fine on 1118 nightly (via CyanDelta) w ART default Kernel. WiFi, Network, Bluetooth all ok. no RR no FC so far. Samsung IR universal remote (free) seems only thing not working for me (no big deal, as I don't use it much)
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
please, can you verify the file manager bug? Wen you use the menu key the file manager close... Thanks in advance :)
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
i tried tested for you. my file manager no FC on menu key or anywhere on file manager bro. All ok.

---------- Post added at 10:34 AM ---------- Previous post was at 10:27 AM ----------

why not just try it. make sure u do a FULL wipe before if its ur first time to avoid any possible issues. make sure u use latest CM nightly. no need any special kernel, default CM kernel is OK. (i use Alucard kernel every now and then though). i used to use TW but I feel CM is 10x better and smoother. CM has little or no bloatware.
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
Thanks for the fast reply. Ive already updated my delta files.

I wish to know if we will receive lollipop update, anyone?
[Galaxy S 4 i9505 Original Android Development] 78Staff:
http://www.cyanogenmod.org/blog
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
Thanks for the link... for sure will have CM 12 but now only unnoficial threads...

Lets wait for the official dev thread :)