yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
if u havent already suggest do a full wipe?
[Galaxy S 4 i9505 Original Android Development] !crazy:
-------------------------------------
[Galaxy S 4 i9505 Original Android Development] !crazy:
If you want I can provide you with 0509, or 0608 (what I use. It has a newer code base than M9, but before new changes which brought issues were merged.).

Just say it and I'll upload it somewhere.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Thanks. It will be nice. Its better than M9 and anyway a temporary solution waiting for the BT fix on the new nightly.
[Galaxy S 4 i9505 Original Android Development] Chronosmiki:
I did full wipe, I think it's battery related, when I'm charging and 60% + It does not reboot.
[Galaxy S 4 i9505 Original Android Development] !crazy:
https://copy.com/VGT1WOZh3Yh3vEES

md5sum 0806:

6851d81441e8df0f84a81f5eeb25b6d5

https://mega.co.nz/#!p91DTRbD!jFpO6CifEN_d3cDM_t4cfoILzSpfk8BskBs_uCvzZpo

md5sum 0905: d08238c65b3b2962a75b2105d81c88f0
[Galaxy S 4 i9505 Original Android Development] aznkenshin:
I can't press Allow in Superuser Requests. It doesn't let me. Anyone know?
[Galaxy S 4 i9505 Original Android Development] Zedonite:
Are you using Screen Filter or something like that? (+ Same problem with installing APK's?)
[Galaxy S 4 i9505 Original Android Development] SamiTaiba:
Is anyone having problem with their speaker ? It's too loud that's good but the bass is so distorted
[Galaxy S 4 i9505 Original Android Development] aznkenshin:
You sir are awesome. I wish I could give you 100 thanks's.
[Galaxy S 4 i9505 Original Android Development] well0549:
Have had it with cyanogen

I used to install cyanogen to have possibillities others didn't have....

Lately it seems i get problems others don't have.....

Most im[portant are the Bluetooth issues and the data connection wich is problematic..... (have to switch it off and on again to get any data flowing)

Loved cyabnogen a long time but now i really hate the unrelieabillity...... Still on M9 and tried a lot of nightlies after that but nothing helped....

Going back to stock.......
[Galaxy S 4 i9505 Original Android Development] BEBU1:
Same here. Besides I got some Wifi issues with latest M-Build. Wifi doesn't connect when phone is in deep sleep so I need to wake up phone e.g. by pressing home button to connect my Wifi.
[Galaxy S 4 i9505 Original Android Development] sronweb:
I guess that the developers know the problems. But maybe there is a misunderstand generally where people expect to flash everyday a nightly that should work at 100%. There is no need to flash last nightly except if we like to test new features or new drivers or kernel and support the developing with logs or reporting the problems. If we like to stay safe we should stay with last working version (for my experience I would stay with M9 or 05 Sep 14 nightly) which seems to be ok. I have my backup and sometime I test the new release hoping to help also others.

There is nothing wrong if you like to stay with stock rom for a while...
[Galaxy S 4 i9505 Original Android Development] Spud37:
Okay quick question does an MHL HDMI adapter work for Cyanogenmod, I feel like i got one to work, however when i got a different cable i could not get it to work. Anyone know the answer, Thanks.
[Galaxy S 4 i9505 Original Android Development] well0549:
Have been waiting for two months now. ...

bad Photo quality, media stutter..... Ik have had it ..

cm used to be better than stock but now it is worse. ...
[Galaxy S 4 i9505 Original Android Development] sronweb:
Personally I still consider that CM is better than stock rom (faster, more customizable, less ram, no bloatware o useless apps, etc).

And think that CM will continue to support and update until is possible and not until Sammy wants (Sammy will stop to update in 18 months possibly). Is still possible to find the good CM version but we know that, due to some important updates, we suffer several problems with latest nightly but we don't need to install necessarily a recent nightly. Otherwise we can keep a good working M9 version from August which should be stable enough. I hope that recent issues on BT and wi-fi connection will be solved soon.

As camera I'm using Snap Camera which has more features and better quality then CM camera in my opinion.
[Galaxy S 4 i9505 Original Android Development] cristianpark:
In Cyanogenmod, they always advise about the propietary drivers and that HDMI Out will never work, I experienced something as you say with a SII T989 but can't repeat it with any of my other devices, I'll get my i337 soon and let you know if I see something new in that aspect after install CM
[Galaxy S 4 i9505 Original Android Development] stephendt0:
I upgraded to the latest nightly (19th September) from the M10 and all my issues were fixed. Quite stable at the moment, very happy with the build.
[Galaxy S 4 i9505 Original Android Development] GRREEN:
Does it includes BT and wifi? I was on M10 but reverted back to M9. Got trouble with BT, Signal and Wifi.
[Galaxy S 4 i9505 Original Android Development] 1weener:
Agreed. CM 0918, 19, and 21 have been very solid for me. I did have problems over the last week, but reflashing the same ROM again cleared up the problems every time... maybe it is the unified build causing problems for some, and some variants just work better? I am with ATT/i337.

---------- Post added 22nd September 2014 at 12:01 AM ---------- Previous post was 21st September 2014 at 11:59 PM ----------

Mine work fine.
[Galaxy S 4 i9505 Original Android Development] GRREEN:
That's good news. Just to be sure, what nightly you are referring to?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Every nightly has something new fixed... I always use latest, and accept that something can be not ok... It is a choice...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] GRREEN:
Yes I agree with that. A nightly is always something to look forward to. I always look forward for new stuff coming in every nightlies. But this time I'm much particular on the issues encountered on M10. I'm checking the nightly logs to hopefully stumble on something related to BT, Wifi, etc thingy. I'm itching to have M10 in my phone. :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] iabhi:
galaxy s4 at&t CM11

I have galaxy s4 at&t (SGH-I337) with stock 4.4.2 and build NB1. I'm trying to install CM11.

Tried to intsall cwm and twrp. Neither of them got installed. (Tried loki, motochopper etc)

Finally installed Safestrap recovery.

Flashed cm-11-20140916-SNAPSHOT-M10-jflte rom with Safestrap.

But on startup 'com.android.phone' stopped working popup coming continuously.

Now again reverted back to stock 4.4.2 firmware.

Any ideas/ help on how to install CM11?

Thankyou
[Galaxy S 4 i9505 Original Android Development] henrik.dk:
I am wondering whether I should switch to the cm11 from tw rom.

What I like from the tw rom are:

1. call recorder

2. alarm. I like the gentle wake up very much from sam's tw rom

3. locker. I still prefer simple swipe unlock with shortcuts.

4. camera. is cm camera generate photo of the same quality?
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
At least the camera question was asked and answered on and on here...
[Galaxy S 4 i9505 Original Android Development] lauterm:
You can't. You have to use safestrap, and it is only compatible with TW ROMs.
[Galaxy S 4 i9505 Original Android Development] pod0087:
I'm on the 22nd nightly from m10 and my Bluetooth isn't disabling by Wi-Fi anymore so it's working for me.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
why don't you just try it?

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

agree. i prefer nighlies
[Galaxy S 4 i9505 Original Android Development] sronweb:
BT connection with Vivofit

[MENTION=2385005]invisiblek[/MENTION]

Since 0910 nightly BT connection with Garmin vivofit is broken. Perhaps we miss the support to BLE (Bluetooth Low Energy) but I'm not sure what is the real reason.

Is there anything I can do to help to solve this problem (log, testing?). Today's nightly is still no good then I have to go back to 0909 or later to find a working version. Thanks
[Galaxy S 4 i9505 Original Android Development] well0549:
I know all this....

But there are some important features that i need from my phone....

1. Continuously switching radio drained my battery very fast. (Data connection LTE/3G switching all the time)

2. Serious media stutter in videos...

3. Less than optimal photo quality

4. Bluetooth connection problems

5. Switch airplane on and off to get a data connection...

I know they are trying and I have been a FAN of CM A LONG time...

I could always live with the issues but for now the issues (even in the claimed stable M9) are too much...

Have been on stock and some of the advantages are :

- battery life is WAY better !

- No media stutter

- And when i parked the car i could immediately park with the data connection (in the netherlands you can use your phone for that)

- No bluetooth problems....

So for now I am happy.....

For sure the disadvantages are :

- Cannot delete files from SD (No QuickPic anymore :(

- Load of Crapware on the phone

But at least it does what it should do.

Once there is a REALLY stable CM I will go back but I don't expect that anytime soon......

( I did not see any activity on the BT issue for two months ).
[Galaxy S 4 i9505 Original Android Development] bossarts:
Same problem here...
[Galaxy S 4 i9505 Original Android Development] mrja22:
Still having same BT disconnect issues on 0922.

Samsung Gear Live after a while stops getting alerts, even though phone shows device connected.

Occasional WiFi drop on BT toggle.
[Galaxy S 4 i9505 Original Android Development] geyce76:
Hi to all I noticed a strange thing.. When listening music on my bt headphones using appolo or Henry I got micro cuts in sound.... But when I listen with Google music or poweramp I do not get these micro cuts... Strange no? Any idea??

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] 1weener:
Good news! It looks like some BT issues resolved on the next nightly. Although I don't seem to use my BT with anything that doesn't work, and my wifi does stay on, I hope these BT commits help out you guys with BT issues. Sometimes small changes make big differences... I hope.

Have you guys seen the retirement savings commercial where a small domino hits against a slightly larger domino, and so on, until a huge 10 foot domino falls? It looks real, but won't work in reality... just sayin' :eek:
[Galaxy S 4 i9505 Original Android Development] ykdr-scott:
Perfect.. These are nightly builds guys. There is going to be bits broken.. They get sorted in new builds.

Accept it or move to a touchwiz based ROM. :thumbup::p
[Galaxy S 4 i9505 Original Android Development] mrja22:
Great to hear.

Don't get me wrong. Love the work that is being done here, and i understand how nightlies work.

That being said my post was more for other end users to get a heads up certain issues still exist. Hopefully it might save them a few hours of testing that I already tried out.
[Galaxy S 4 i9505 Original Android Development] morpheus302:
Is anyone else having low mic gain issues. Try recording audio with a TW then using a CM rom. The difference is obvious.
[Galaxy S 4 i9505 Original Android Development] GRREEN:
That's good news. I just curious, from M9 is it required to install M10 first before installing the latest nightlies? Before was easy for me as I install nightlies on weekly basis and snapshots when they come out.
[Galaxy S 4 i9505 Original Android Development] worktorest:
Got a question: Anyone experiencing random auto-shutdown of your phones? I'm on M10.

Don't know if it's my phone's hardware.
[Galaxy S 4 i9505 Original Android Development] pod0087:
No you just go straight to the nightly.. You can generally flash any newer ROM without wiping anything. It's only when going backwards that you will probably experience issues (say reverting from a bad nightly to a milestone)
[Galaxy S 4 i9505 Original Android Development] Rapalax:
Anyone here using an i337m ? I can't seem to connect to Fido since M8, and searching network operators errors out.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
I experienced random freeze (stuck in deep sleep) between M9 and M10, but haven't had that problem since M10.

But that's the nature of random ... hard to find the reason :eek:

At the moment my main problem is loosing 3G connection, but I just changed my service provider so properly nothing to do with CM11.
[Galaxy S 4 i9505 Original Android Development] 1weener:
No, no shutdowns here.

I suggest moving to the newest nightly. They seem quite good once again, and it looks like we'll get some BT fixes tomorrow!
[Galaxy S 4 i9505 Original Android Development] worktorest:
Yeah it's so random and happens about twice a day. And I'm referring to a complete shutdown of the phone. The screen turns blank out of the blue while I'm still using it, or while it's on standby. I will need to long-press the power button to turn the whole thing back on.

Not sure if it only occurred when I started using cm or also for other custom roms.
[Galaxy S 4 i9505 Original Android Development] Stransky:
Had this happening on nightlies prior to 22/9. Has not happened so far on this nightly, appeared to be a deep sleep issue as the notification light was flashing but the phone would not wake up. Had to hold power to shutdown and then re-boot.

Stransky
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
If you move some strings from one file to another then this simply fixes nothing!
[Galaxy S 4 i9505 Original Android Development] thafath:
I'm on chatr and it's working great here. What modem you have? Try ne1.
[Galaxy S 4 i9505 Original Android Development] ntnlzr:
you've to flash different modem, i was in the same trouble and i've fixed with this (i've old bootloader)

http://xdaforums.com/showpost.php?p=55475958&postcount=528
[Galaxy S 4 i9505 Original Android Development] Mittaa:
I'm on new bootloader and already have the newest modem available :good:

I noticed that (until now) all dropouts have happen after trying to send MMS with faulty MMS provider setup. Now my setup is correct, problem might have disappeared :victory:
[Galaxy S 4 i9505 Original Android Development] Rapalax:
I had ne1 but just went to ni1, both seem to have issues with Fido and connect only to Rogers. Can you search for network operators?
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
agree . for me, i am loving the last few nighlies. very stable. battery good. daily driver. camera fast. no reboots. no signal issues. w ART + default kernel. (sorry, I don't use BT much so that hasn't affected me at all)
[Galaxy S 4 i9505 Original Android Development] kubapl66:
What about IR blaster using Anymote IR app or any other app?

Galaxy S4 & Tapatalk

Edit:

Guys! I know how to make IR blaster working in apps: download ASmart Remote, check HTC Sense 6 OPTION reboot and it work :D
[Galaxy S 4 i9505 Original Android Development] sronweb:
Let's test today's nightly if BT is working! Is out!
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
In the public changelog i can't see anything that fixes something on Bluetooth...
[Galaxy S 4 i9505 Original Android Development] mrja22:
I can confirm that my BT issue still exist on 0923.

Connects to Gear Live fine, and usually works great for 10-15 minutes. Usually after the phone goes into deep sleep for a while BT stops working

Then notifications stop going through. Watch and phone still thing they are connected. Interestingly when in this error state, if I turn off BT then the watch shows disconnected instantly. It is almost like BT has gone into a sleep mode or low power mode - that is still active, but no data transmission.

Sometimes issue resolves itself, other times not.

Toogling BT fixes issue, then returns after 10-15.

I have not tested with BT audio.
[Galaxy S 4 i9505 Original Android Development] sronweb:
No good news for BT. Still no connection with the Vivofit.
[Galaxy S 4 i9505 Original Android Development] mrja22:
Interesting, when I turn off WiFi (not just when WiFi is disconnected), BT seems to work perfectly.
[Galaxy S 4 i9505 Original Android Development] IcePick74:
Agreed - still issues with my car without reboot or toggling BT

Back to Sept 06
[Galaxy S 4 i9505 Original Android Development] moffe:
Bluetooth works fine about 5 min then it stops working, then you need to turn it off and on and works again around 5 min.

:( *in the latest nightly 20140923*
[Galaxy S 4 i9505 Original Android Development] geyce76:
Is Sept 06 bt working??

Envoyé de mon GT-I9505 en utilisant Tapatalk

---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------

Up! Nobody has an idea?? Player issue or bt compatibility issue?

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] IcePick74:
yes no BT issues for me on Sept 6.

Battery life isnt great

and there is the phone UI thing that sometimes the lock screen appears on top of the dialler.

But I would rather have BT working in my car.
[Galaxy S 4 i9505 Original Android Development] 1weener:
IR Remote 2.0 working perfectly on 0922. Everything else is working perfectly too.

---------- Post added at 04:12 PM ---------- Previous post was at 04:08 PM ----------

Audio works. That is how I use it, and that part does work..
[Galaxy S 4 i9505 Original Android Development] ionutzvio:
Guys can u recommend a nightly newer then the M9 with better battery life and without the bad speaker sound and the blutooth issue. Tnx in advance. I tried m10 and the battery was oky but the sound was awful :((
[Galaxy S 4 i9505 Original Android Development] feraay:
Yesterdays^^

No problems here...
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
i don't have irblaster but ZappIR works (922 nightly) .
[Galaxy S 4 i9505 Original Android Development] yurividal:
Actually the app i use is SMART REMOTE.... but it does not seem to be working on CM since End of July
[Galaxy S 4 i9505 Original Android Development] munkyvirus:
I use Smart Remote, is yours fully upgraded to the latest version? Mine works fine.
[Galaxy S 4 i9505 Original Android Development] FrA1l3:
+1
[Galaxy S 4 i9505 Original Android Development] Dr.No.pt:
Nightly 22/09 and Sleep of Death still present. Always Cache+Dalvik clean before upgrade.

Should i full wipe or is it a known bug and awaiting resolution ?

Thank you. :D
[Galaxy S 4 i9505 Original Android Development] ntnlzr:
what do you mean with sleep of death?
[Galaxy S 4 i9505 Original Android Development] feraay:
If u use smart remote , you have to send Them an email again to reset your profile because of new drivers

S4 never had sleep oft death ^^

No one knows what are u talking about.

Do a full wipe and clean install its not a known bug^^ it never was
[Galaxy S 4 i9505 Original Android Development] Dr.No.pt:
Sleep of Death is when the screen doesn't wake up. You press power button or menu and it doesn't do anything.

You have to press 10 seconds to shut the phone down and restart it.

Received a phone call, phone ringing and screen is off. Nothing you do wake's it up beside shutting down and up again.

;)

Just want to mention that this "Sleep of Death" is random. It might happen when phone is idling ( screen off ) or when ringing ( again coming from screen off ) and it might happen within several hours apart
[Galaxy S 4 i9505 Original Android Development] feraay:
I know what sleep of death means ...

But with phone calls its not sod

Its just your nearing Sensor

Phone is still there but u have nearing Sensor error

Nothing to do with sleep of death something really different.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Thanks to describe SOD... Anyway never had a sod on S4 with CM...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] mooyaart:
I found hitting the home button 10 or so times would bring it out of sleep of death. Quicker than rebooting!
[Galaxy S 4 i9505 Original Android Development] feraay:
Thats not sleep of death

Sleep of death means

Phone cant get out of deep sleep

But you say phone call than its just the nearing Sensor doesnt allow to unlock screen because Sensor belive phone is still on your ear

Has nothing to do with sleep of death ....

Sleeping is missing^^

9505,never had sleep of death errors

.

But nearing Sensor is a Problem on lot of s4.

Sometimes a lil but of dust betwen Sensor and screen and phone goes crazy.

But definitly it has nothing to do with sleep of death becouse sleep of death means phone is in deep sleep and cant get back.

Düring a phone call device will never be in deep sleep its impossible.

I hope unterstand it

No one of u has a sleep of death.

Its a proximity sensor error.

Phone belive you are still talking on phone call.

Just try to blow dust out of proximity sensor

If u mean u have sleep of death

Than just do a full wipe and clean install because its not a known bug and it never was.

Option 1 . proximity sensor

Option 2. Bad flash just do a full wipe
[Galaxy S 4 i9505 Original Android Development] Dr.No.pt:
I don't know if it's the sensor or not. Mine has no dust.

The phone is on the table sleeping. A call comes in and it doesn't allow me to wake up the screen. I can press the power button to cancel the ringing but screen is always off. Only shutting it down and up again brings me back the screen.

I'll try to click the menu button several times. :eek:
[Galaxy S 4 i9505 Original Android Development] feraay:
This 2 options you have.

Try for your self but i belive your proximity sensor is broken or a lil bit dust between Sensor and Glas. You just talk about errors during calls that says all

But what i want to say since first post it is not a sleep of death because s 4 never had .
[Galaxy S 4 i9505 Original Android Development] moffe:
I got the issue when trying to hang up the call... screen stays black.

Not a SW issue... just used some compressed air in the earspeaker and also in the headphone jack hole. I also removed backcover and used the compressed air in all holes and cracks.

Now it works just fine!
[Galaxy S 4 i9505 Original Android Development] feraay:
Thats what i mean with blow proximity sensor

But no one belives me

Sleep of death^^

Check your proximity sensor

or do a full wipe
[Galaxy S 4 i9505 Original Android Development] yurividal:
This was the problem! I had an old version! It worked fine with July Nightlies. Updated the app to 2.0.4 and now it works fine! =D:laugh:
[Galaxy S 4 i9505 Original Android Development] Cusa:
Some of my apps are randomly closing when I open them. I'm using the latest nightly with stock kernel. Anybody else getting this?
[Galaxy S 4 i9505 Original Android Development] feraay:
Nope

Last nigthlies are stable AS hell.

No Problems Here

And i mean no
[Galaxy S 4 i9505 Original Android Development] smeroni68:
FYI: on jerkins build servers there was a kind of general compiling failure... I think for today no nightly will be available!

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] BEBU1:
Hi, guys. I'm on M10 build and it's very buggy for me. Wifi issues, very loud speaker etc. Is it safe to upgrade to latest nightly?
[Galaxy S 4 i9505 Original Android Development] a103:
Flash M9 if you want stability.
[Galaxy S 4 i9505 Original Android Development] !crazy:
You can also flash nightly from 6th of August, it has a bit newer code base than M9, but before most of issue have started. You can find link in one of my last few posts.

Also, don't just flash older nightlies (or M, doesn't matter.) over newer builds. You have to do a clean install (to wipe data, cache, system, but system anyway goes automatically.). Only way (and good and simple one.) to go backwards is to have a nandroid backup, which you can always restore. In that case one wipes everything, but than restores everything like it was at the time of making the nandroid.
[Galaxy S 4 i9505 Original Android Development] Mitsch79:
Bug confirmed here.