yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] maurocds:
1 WEEK WITH LATEST cm13 snap, and i will be coming back to gpe

- camera sucks, no hdr

- camera fails to open a lot, gives error many times or black screen

- no working google camera

- random overheating, cpu crazy at 100%, battery drain at random

- a lot of annoying system apps to delete

- mega slow charging (for me)

the camera issue was the worst

sure, it can be used as a daily driver, but the camera problem was too much, it fails to open like 40% of time
[Galaxy S 4 i9505 Original Android Development] Apad121:
I looked through the settings and because it was an early build of cm14 it didn't have the standard CyanogenMod settings. It didn't have live display I wasn't able to disable that annoying hello tint.

Thanks for the suggestion though :)
[Galaxy S 4 i9505 Original Android Development] nico933:
I have a problem with whazapp notifications, sometimes I don't receive any notification until I open the app, at this time all the messages arrive in the same time

I have greenify but I don't have ibernated whazapp, i don't use force doze o app link that and I put whazapp in the white list

Anyone have this problem?
[Galaxy S 4 i9505 Original Android Development] Black Manta:
Deleted
[Galaxy S 4 i9505 Original Android Development] Hemuli:
I have a cheap USB meter that sticks between the charger and the usb cable. For me the meter and apps (Galaxy charging current, Ampere) seem to show the same reading. For example while my meter shows 0.40 A, the app shows 430 mA. When the meter shows 0.43 A, the app shows 460 mA. This falls into the measuring accuracy i'm expecting out of my cheapo meter. Plugging the meter in the circuit seems to lower my charging current. This might (or might not) be due to additional ripple on the +5 V line caused by the meter.

Our device perhaps begins drawing current depending on what it sees on the USB data pins. Then it will gradually lower the current until it sees a clean voltage for protection reasons. The charging current never rises after plugging the cable in, which partly indicates that this is the way our device is currently working. The implementation might be different between stock and cm. I also know that for Galaxy S3 I9300 there are custom kernels that let you choose to disable the protection against ripple or voltage drop completely. I'm not certain how this has been implemented for our device though, as I haven't looked into the code or the chips on our charging circuit.

The charger I'm using came with my Lenovo tablet and is rated at 5 V, 1 A. With my S4 I only seem to get max. ~600 mA out of it. Sometimes I only get 400 mA or lower, which indeed means slow charging. To me it looks like the protection is working too aggressively. I haven't checked how clean a voltage my charger is providing with though. There might be a boogeyman riding on the DC.

I mostly charge overnight so this is not a major disadvantage for me. I really should have a long enough sleep at night so that my phone is able to charge fully. That isn't the case always though. :eek:
[Galaxy S 4 i9505 Original Android Development] zwliew:
[MENTION=5592554]Hemuli[/MENTION], [MENTION=4365919]Braccoz[/MENTION], [MENTION=5399879]echo_21[/MENTION] or anyone else,

If one of y'all is able to get on TW or GPE, could you check what the following files show when charging off AC?

/sys/class/power_supply/battery/current_now

/sys/class/power_supply/battery/current_avg

/sys/class/power_supply/sec-charger/current_now

/sys/class/power_supply/sec-charger/current_avg

/sys/class/power_supply/sec-charger/current_max

I'm currently looking to get the charging current reporting fixed. However, there is quite a bit of voodoo in the Samsung's battery drivers that will require more info from stock (TW or GPE) to fully understand. I have a preliminary fix ready, but I'll need further understanding of the charging drivers before merging the fix.

[MENTION=7083959]cruplezone[/MENTION],

Haven't really had time to work on it so far. But there's some testing going on.
[Galaxy S 4 i9505 Original Android Development] Braccoz:
[MENTION=5592554]Hemuli[/MENTION]:

yes the current reported is accurate up to 1460 mA, then it jumps to 1900 mA but really isn't 1900, it's about 1600, and it jumps higher only when screen is on, up to 1750.

[MENTION=5399879]echo_21[/MENTION]

charged the phone, i confirm my earlier findings. the check for cables/charger is stricter than in 4.3 TW and the max peak current drawn is down to 1.75 from 1.84 A, normal current while charging is also down from 1.68 to 1.55-1.60. all these values report 1900 mA in the app.

[MENTION=5604178]zwliew[/MENTION]

will see what i can do
[Galaxy S 4 i9505 Original Android Development] Nabeel_Nabs:
So I've been having issues with sending text messages and random battery draining on the latest snapshot, the previous one didn't have any issues... I can see others having had similar battery drain issues, are these fixed on the nightlies?
[Galaxy S 4 i9505 Original Android Development] Flouque:
No problem sending text nor battery drain (using Naptime though) on 03/09 nightly
[Galaxy S 4 i9505 Original Android Development] chris-l-a:
Noticed that with recent builds (say starting about 20160831) steep battery drain when the camera is used. Currently using build 20160905 and could only the camera once - subsequent attempts showed error accessing camera. Restarting the phone seems to have resolved the battery drain, but I suspect taking another picture with the camera will repeat the problem - steep drain and no camera after.
[Galaxy S 4 i9505 Original Android Development] TcG71:
I had the same camera issue (on all 4 devices I moved to CM13) but it's much better (not fixed completely) after removing (or renaming) the "Android" folder on internal SDCard. That was helpful even after a fresh installation with full wipe (incl. internal SD) right before installation.
[Galaxy S 4 i9505 Original Android Development] zwliew:
could you link me the previous snapshot (the one you were using)?

there weren't really any changes that could've affected that on 0831 though..
[Galaxy S 4 i9505 Original Android Development] Plonkyplonk:
Flashed cm-13.0-20160907-NIGHTLY-jfltexx.zip over a well working cm-13.0-20160905-NIGHTLY-jfltexx.zip (checked sha1sum: correct) alltogether with open_gapps-arm-6.0-nano-20160907.zip (checked the md5sum: correct).

Now "SetupWizard has stopped working" popup is jamming the UX (the popup is back again and again).

Just behind this popup is there another one: "process system isn't responding".

---------- Post added at 11:38 AM ---------- Previous post was at 11:24 AM ----------

I had to give back permissions to the SetupWizard. Launched adb shell, then launched:

pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE

The complete list of permissions is:

pm grant com.google.android.setupwizard android.permission.CALL_PHONE

pm grant com.google.android.setupwizard android.permission.GET_ACCOUNTS

pm grant com.google.android.setupwizard android.permission.PROCESS_OUTGOING_CALLS

pm grant com.google.android.setupwizard android.permission.READ_CONTACTS

pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE

pm grant com.google.android.setupwizard android.permission.WRITE_CONTACTS
[Galaxy S 4 i9505 Original Android Development] portaleus:
Sounds like an issue I had some month ago. Did you remove the CMSetupWizard?
[Galaxy S 4 i9505 Original Android Development] Joelko:
Calling

Calling does not work for me. :(

Maybe first call works, but after a while it does not work.

Is there no solution for this issue?
[Galaxy S 4 i9505 Original Android Development] Jimmyhao:
Call recording Apps

Hi =D Good day Everyone.

I have been trying for call recording apps like ACR to records call. But it seems not working in Cyanogenmod 13. Why? anybody can help me please?

It use to work in the samsung stock rom but not in cyanogenmod 13.

Any other alternative apps or ways can be use to record calls?

hope anyone will some info can help me out.

Thanks in advanced.
[Galaxy S 4 i9505 Original Android Development] moonsoo:
It's the Amazon instant video app.

You need a Amazon Prime account.

You could use a trial (no risk!) for one month to reproduce this issue if it is worth it.

Non of the videos is played in HD.

However it seems to be better than 480p.

I believe it has something to do with the device ID.

When I used device faker (I know xposed is not supported here but I saw this work around for netflix) it works when I make a clean reinstall of the app (wipe caches (dalvik, too).

But after a reboot it has to be re done.

Looks like a CM issue as the same behavior I saw with CM 11 with kitkat for Mi Pad.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
The issue is being caused by dirty flashing, not due to some issue in the build.

You also only have to grant setup wizard permissions to contacts, nothing else, in order to not get FC's from it.
[Galaxy S 4 i9505 Original Android Development] moonsoo:
Now I reinstalled and changed the display ID.

Wow it worked but after closing the app and restarting again 480P and no HD! ???
[Galaxy S 4 i9505 Original Android Development] xperiaatic:
Should NFC work with this ROM or not? NFC icon does not appear when it is turned on and phone does not recognize any NFC tags.
[Galaxy S 4 i9505 Original Android Development] abdelkader azhar:
Hi first thing big thanks to Mr developer

I first time install this ROM and the result was more than perfect

No heat up no FC

Everything work fine

But can some one help me pleas I can't update super SU it gives me installation failed. ( I already enabled root access in developer option to apps and ADB )

And thanks
[Galaxy S 4 i9505 Original Android Development] metlen:
Hi

Is there any chance to add to quick answers sms app functions that i read the messages? Without this you need to enter the application to indicate that it is read

Thx
[Galaxy S 4 i9505 Original Android Development] george stamatos:
Does anyone knows what is "fix Greece SPN" ?
[Galaxy S 4 i9505 Original Android Development] thafath:
See the changes here.

https://review.cyanogenmod.org/#/c/161593/1/selective-spn-conf.xml
[Galaxy S 4 i9505 Original Android Development] george stamatos:
And again, I m asking what spn is.
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
Honestly, is it that hard to use Google? I've just googled "spn android" and this was the first result (no kidding, literally the first): https://developer.android.com/reference/android/telephony/TelephonyManager.html
[Galaxy S 4 i9505 Original Android Development] kridster:
I just updated to current nightly (9/11) and still have that problem on this device as well as Nexus 4.

Using different camera, like Open Camera, seems to be the only way to avoid this. Anyone else?
[Galaxy S 4 i9505 Original Android Development] jeroendj2:
Google contact sync crash for me after installing latest nightly 9/11, installed right gapps.

Tried this:

Reflash multiple times

1.Disable Webview on android in apps manager its only 2mb !!

2.Then download Webview on android from Google playstore and reboot the phone and whola its fixed.

Both didn't work :(
[Galaxy S 4 i9505 Original Android Development] Nicolas C:
To Krister,

Moving to "open camera" aps does not solve the camera crash for me. I thought it was OK the first 5 or 6 photos then crashed again and again :(
[Galaxy S 4 i9505 Original Android Development] bullsei:
i had the same problem, starting the super su app i always needed to update the binaries. This didn't work in the normal mode and flashing with twrp resultet in a not starting device.

So i downloaded the super su zip. file (http://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703) and flashed it manually in twrp.

this worked for me
[Galaxy S 4 i9505 Original Android Development] abdelkader azhar:
Thanks mate
[Galaxy S 4 i9505 Original Android Development] saullo:
i9505XXUHOJ2

using nightly 20160907 in a i9505XXUHOJ2 and still having these two issues:

- Camera Crash;

- "Sim card removed" and phone asks me to reboot (occasionally - 2 times two days ago, 0 times yesterday and 10 times today)

:(
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
Why don't you update your modem/bootloader? It could be the cause of the second issue. Camera is half-broken, but I'm having a fairly stable experience with Open Camera (until [MENTION=5604178]zwliew[/MENTION] get enough time to fix it.).
[Galaxy S 4 i9505 Original Android Development] saullo:
Because i really didn't think in that possibility of updating bootloader could help me gh0st! Thank you!

I'll try and post If it solves
[Galaxy S 4 i9505 Original Android Development] Black Manta:
Even if updating your modem/bootloader don't fix your problems it can improve your connection and battery life.
[Galaxy S 4 i9505 Original Android Development] Mitsch79:
Just one question, what Do you need SuperSU for? Root is integrated into Cm and you can activate and deactivate it in the developer options. Actually, i don't use SuperSU anymore, since it doesn't offer any additional features and quite often bricks the phone.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
CM's root doesn't always work well. I've had problems with CM's root manager app in the past, while I had no problems with SuperSU.

SuperSU seems to brick the device when updating from the play store. That's why I update through recovery, or simply wait until I update my ROM and flash the new SuperSU in the process. Unless the ROM already has SuperSU integrated.

---------- Post added at 08:20 AM ---------- Previous post was at 08:16 AM ----------

Did NFC work before coming to this ROM?

The NFC antenna is located on the battery. If you've changed the battery recently then it might be fake, as those don't usually have NFC antennas.
[Galaxy S 4 i9505 Original Android Development] xperiaatic:
Thank's for the tip :good: i indeed had a 3rd party battery in use at that time.
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
My batter says Near Field Communication, but I've never tested NFC on stock and it doesn't work at all. Maybe I am missing something else?
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Of course Near Field Communication is written on your battery. Even if it is fake it has that writing on it, because fakes are supposed to resemble the real thing.
[Galaxy S 4 i9505 Original Android Development] Catscratch:
I got a third-party battery with nfc antenna and the Samsung original one. Nfc isn't working on both. So it seems to be a ROM/driver problem.
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
Well, this is how I got the phone. The battery is "new", according to the previous owner, it even has the store sticker on it. This means that I need to get a new one?
[Galaxy S 4 i9505 Original Android Development] Rhoban:
A friend also bought an S4 with a "new" battery, according to the seller. But it turned out the battery was fake. So don't take his word on it.

The battery might be new, but that doesn't mean it is genuine.

Anyway, the previous poster seems to have problems with original batteries to, so that's that.
[Galaxy S 4 i9505 Original Android Development] Mitsch79:
Has one of you gotten bluetooth to work? For me it's not working using latest snapshot or latest nightly (clean flash) . I'm using the phone with my car radio and it connects. But as soon as i start audio streaming bluetooth crashes and can't be turned on till next reboot. I'm on latest modem and bootloader (HPG1). With Imperium rom V15 bt works without any problems. Since CM13 has a stable release i was hoping they fixed bt. Obviuosly they didn't :(
[Galaxy S 4 i9505 Original Android Development] Catscratch:
Can you explain me how to do plz? I have another Samsung device with stock rom. There I hit share with Android beam and hold both devices together. But nothing happens.
[Galaxy S 4 i9505 Original Android Development] hrjj:
Bluetooth is working flawlessly. No problems at all since the new audio hal.
[Galaxy S 4 i9505 Original Android Development] Mitsch79:
Well, are you talking about bt audio only with bt headphones or about bt hands free in combination with a car radio that accesses the phone functions such as phone book, recent calls a.s.o along with the audio playback features? Cause the car audio combination is in fact not working here with cm any CM13 build, stable or nightly.
[Galaxy S 4 i9505 Original Android Development] hrjj:
Car audio i am talking about.
[Galaxy S 4 i9505 Original Android Development] A838:
Make sure your battery is legitimate (bought straight with your phone from a trusted retailer), and remove any intruding cases from devices. NFC is located on the back of phones, so hold devices back to back. Confirm that the other device's NFC works 100% as well.

[MENTION=5604178]zwliew[/MENTION] Don't want to demand anything, but could you let me know if there are any CM14 updates, or working on CM13/general life stuff for now? JDC's ROM isn't to my liking and I'm looking forward to a build with no red borders! Thanks for the amazing unpaid work you do! :)
[Galaxy S 4 i9505 Original Android Development] zwliew:
Generally I've been working on CM 14, but there hasn't been a build that's CyanogenMod-esque enough for me to be satisfied with releasing. There are also some bugs (i.e. camcorder) that need to be fixed, but progress is slow since school and exams have started. The previous bugs from CM 13 also need working on (that also appear in CM 14), unfortunately.

If you want to keep track of the progress, you can take a look at the merged section of the CM Gerrit (review.cyanogenmod.org)

I'd like to ask a question regarding the camera crashes - are the crashes present only in the Snap camera, or are they present in the AOSP-based camera as well? If the Snap camera is the cause of the problems, I'll revert to the AOSP camera while the bugs are fixed in Snap.
[Galaxy S 4 i9505 Original Android Development] side:
bug is everywhere mate...i also compiled aosp's camera and it still crashes...not that often but it is..

did u touch the wrapper recently ?or the device tree?

i also saw that framework/base has some cpp camera-related files.

question:Since we use 8960 platform and we know that our camera is a sony one,cant we build other 8960 driver?or any caf ?
[Galaxy S 4 i9505 Original Android Development] xperiaatic:
Replaced backup battery with original and NFC works for me again. S4 NFC seems to be little insensitive and reads tags best at bottom half of the phones back.

Bluetooth works also fine for me. I'm using the phone mainly for car audio, hands-free calling, Spotify and Waze.
[Galaxy S 4 i9505 Original Android Development] Black Manta:
Where do you have camera crashs? Because I still using Snap Camera and haven't seen a crash since month.

I only recognize that the camera isn't working anymore and the battery drain is very huge if I am still in camera application and close it via task manager. If I go out from the camera with back key there isn't such a problem.
[Galaxy S 4 i9505 Original Android Development] Red'Gen:
Hello, Folks !

Are we far from a stable first version ? Nor what is it left to be done ?

Thx, and GJ for all AntaresONe !
[Galaxy S 4 i9505 Original Android Development] abdelkader azhar:
I have no problem with camera in this build

I have been using it for a whole day and I recorded I video with 1080p for about 38 min without any crash
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
For me, the problem happens when I switch from camera to other apps then try to switch back to camera, either after closing (removing it from recents) or simply by selecting it from recents. Then it only works after a reboot.
[Galaxy S 4 i9505 Original Android Development] Mitsch79:
Today i removed my car radios Power cable cause i wanted to install the phantom power my antenna needs to work properly. Well, what to say... Bt works like a charm :) I did some phone calls while i was on the road and listened to streaming music. Everything works perfectly. So thx guys [emoji8]
[Galaxy S 4 i9505 Original Android Development] chris-l-a:
Tried this - take picture, switch to MMS, back to camera. First couple times got "Camera has stopped" but on third attempt camera opened and seems okay. Now to see if remaining charge falls off a cliff...
[Galaxy S 4 i9505 Original Android Development] Mitsch79:
I just tried taking several pictures then switched to another app, came back to snap camera (your talking about the playstore App, right? I own the paid version) using recent apps, took some pictures in a row using the continious shooting feature, switched to another app, switched to Youtube, opened recent apps and killed all apps incl. snap camera, launched snap camera again and took some pictures. Everything's perfectly fine. Any other test case to reproduce the issue?
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
I'm gonna try this next time Camera stops.

I use the camera that comes with CyanogenMod and Open Camera. Open Camera never stop working, but it is slow as hell to open and take pictures. Curiously enough, today I tried Snap Camera and it force closed once and worked fine after. I'll try to make it crash again (lol), then I can tell what I did in order to reproduce the error - for now, it seems to be almost stable.
[Galaxy S 4 i9505 Original Android Development] glarage:
Good one. I was able to reproduce the crash when i played with "recent" and switched from apps to apps, like you did...

The issue gone if i open "gallery" and after camera.

Complety stock, here, no gapps

The log: E at 22:24:54
[Galaxy S 4 i9505 Original Android Development] glarage:
Forgot something......
[Galaxy S 4 i9505 Original Android Development] TheRealStarkman:
Does anyone have the issue where you click on the microphone in the keyboard in the upper right and it does nothing.? Could be local problem after titanium restore.

Thanks
[Galaxy S 4 i9505 Original Android Development] Mitsch79:
No, the app from appstore has always been called snap camera for at least the last 5 years. The HDR part was added later. You can see this as well when you install the app. The Icon has the naming snap camera (and packages as well). That's why i asked. So it would be better to call the cm camera, well, cm camera as snap camera is a name that's already in use. [emoji6]

---------- Post added at 06:49 AM ---------- Previous post was at 06:40 AM ----------

Did the same procedure with stock camera and it's perfectly stable.
[Galaxy S 4 i9505 Original Android Development] 135Shadowsoul:
Hi every1,

soon it is time for me to upgrade my GT-I9505 from CM11 to CM13 (snapshots each). Just some final questions:

1. did any1 figured out any problems with one of the two CM13 snapshot builds? (GPS, IR, bluetooth, NFC and so on working properly?)

2. Post 1 said "choose arm, 6.0, nano", but is micro ok, too?

3. which partitions should be f2fs? or just "optional"? if required, can twrp do this? or how to f2fs those partitions?

maybe i will add more questions later. But if any1 can answer 1-3 would be great :)

thanks in advance :)
[Galaxy S 4 i9505 Original Android Development] Rhoban:
1) Bluetooth may be the only issue you will have. Bluetooth on Marshmallow ROMs is a bit unstable.

2) Doesn't matter which one you choose. You can download everything else from the play store anyway.

3) Changing to f2fs is optional. ROM will work without it.

If you really want to, convert /data, /cache and maybe internal to f2fs. And yes, you can use TWRP for this.
[Galaxy S 4 i9505 Original Android Development] 135Shadowsoul:
one more additinal question: im not used to TWRP (mostly used CWM). TWRP backup offered me an option to backup efs.

Now the Question: if i upgrade from CM11 M12 -> CM13 snapshot and want to restore backup cause i like CM11 more then CM13 (or any other reason), do i have backup efs, too? Or is this option just in case i nearly hardbrick my device?