yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] zwliew:
PSA to all

Please understand that it is extremely difficult to debug issues without simple logs and reproduction cases. Since I don't commonly encounter the issues many other users do, having actual bug reports would be amazing and very helpful to debugging.

Here's the template for what I'd consider to be the ideal bug report:

Issue title

Affected build

Last known good (if not 100% sure of a specific build, just state a period in time. If it never worked fine, just state so)

Issue summary

Reproduction case (has to be AS SPECIFIC AS POSSIBLE)

Logcat and dmesg of the issue

Here's an example of an ideal bug report:

[B]Issue title:[/B]
Camera crashes

[B]Affected build:[/B]
cm-13.0-20160818-NIGHTLY-jfltexx

[B]Last known good:[/B]
20160814 [I]OR[/I] Since about 20160719[I] OR[/I] never worked

[B]Issue summary:[/B]
The camera crashes when I try to change resolutions

[B]Reproduction case:[/B]
1. Open Snap camera app
2. Switch to snapshot mode
3. Switch to 9.6 MP resolution
4. Camera freezes then crashes

[B]Logcat and dmesg:[/B]
[Attached logcat.txt]
[Attached dmesg.txt]

Furthermore,

bug reports for CM ideally shouldn't go on the XDA thread. If you want to lodge a bug report, you should head over to CM JIRA (https://jira.cyanogenmod.org) and create an issue report following the guidelines.

In conclusion,

I really appreciate the bug reports in this thread as it brings to my attention several issues I wouldn't have noticed otherwise. However, it would really speed up the bug fixing process if the above guidelines were followed when reporting bugs. Thanks a bunch :)
[Galaxy S 4 i9505 Original Android Development] jpxsat:
S View

Has anyonme tried an app called Hall Monitor? For me in the past it has done wonders, but in 6.0 it does not work.

It's code is open, maybe this could be integrated into the CM code? :confused:
[Galaxy S 4 i9505 Original Android Development] zwliew:
I'm aware of this issue; working on it.
[Galaxy S 4 i9505 Original Android Development] Epic.:
Hey guys, I'd appreciate any help I can get on my problem with CM roms. For ages now I have wanted to use CM nightlies and snapshots, and other CM based roms like ResurrectionRemix on my phone, however I always get constant random reboots frequently (every 2 or 3 minutes) which leaves me no choice but to go back to JDC AOSP/Opt. CM13 builds, which are great roms, however I want to try the latest snapshot of CM13 Official. However, once again, I flash the rom, flash GAPPS, everything works great, the rom initializes and during Setup straight away I'm hit with a couple of random reboots. I keep going and set up the phone, but yet again I get random reboots once using the phone. Can anyone help me out on my issue?

My phone is the GT-i9507 (identical to i9505, except it has an extra 4G baseband), which runs all the other jfltexx roms like JDC AOSP and JDC CM13 and other i9505 roms, however it seems I can never run CM roms straight from CM as I always get random reboots. Would providing log cats help?
[Galaxy S 4 i9505 Original Android Development] Mastroaldo70:
Guys, did cm-13.0-20160818-NIGHTLY-jfltexx.zip update on my Samsung - jfltexx s4 i9505 !!!

No longer comes into TWRP recovery, does not open rootexplore, says not rooted supersu .... help

cyanomod recovery ???
[Galaxy S 4 i9505 Original Android Development] Axl_Mas:
Hi [MENTION=5604178]zwliew[/MENTION] ,

In my case I saw that every time I use Wave or Maps for GPS driving one of the core (usually core 1) remains in full load also when I finish my trip, disable the GPS and close every applications.

Clean the memory and/or greenify all apps doesn't stop the full load of one core, the only one solution is to reboot the phone.

I tried to change the cpu governor to Ondemand but it is the same.

The 1 core full load issue after GPS using is the single bug I found in the rom, for the rest it works perfect.

I don't play games or other high demand apps, for standard phone use and internet browsing I have 100% stable performances and great battery.

Just my 2cents, many thanks for this great rom! :)

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

There are 2 nightly roms released on 18.08, I used all of them (now I am on the last one) and they works well on i9505.

Try to reflash TWRP with Odin and clean install the rom and gapps (I use opengapps pico)
[Galaxy S 4 i9505 Original Android Development] Nicolas...:
Hello ,

Can you say me what is the best rom :

-The official cyanogenmod 13 (snapshoot version)

-The Optimized CyanogenMod 13.0 builds Stable-2 by JDCTeam

Actually I use the second rom, but my phone is always burning.

Could you help me please ?

Nicolas...
[Galaxy S 4 i9505 Original Android Development] Mastroaldo70:
ok thanks .... I try to reinstall as you said

.......I had to cf-root install car, he told me that the root was gone !!!
[Galaxy S 4 i9505 Original Android Development] m4xi88:
does it work for gt-i9500?
[Galaxy S 4 i9505 Original Android Development] stylemessiah:
Wow, misinform much?

Ive used CM "Official" on several devices, and the JDC Optimised ROM (Stable 1 - they have a Stable 2 that some have issues with) has for me been waaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaay more stable than 4 months on CM13 official/nightlies

I have not had a single issue with JDC Stable 1 ROM

Ill take that over the fixed, (and then reintroduced a few builds later) bugfest and new bugfest that CM13 Official has become any day

You keep having to flash each day, ill keep using the "supposed" optimised ROM ive had on here for weeks

No pink screen, no touch loss....

No bs
[Galaxy S 4 i9505 Original Android Development] robertogl:
In the last two, three months the nightly has become so much better, mostly because of zwliew.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] stylemessiah:
Actually i think you'll find performance and stability arent mutually exclusive unlike official CM13, if you want to continue slanging untruths...

Cant say ive seen a report of a pink screen since ive been using it, so theres another lie....

When official CM13 gets as stable maybe ill give it another go, but its been disappointing so far. I havent had to flash anything since i flashed the Stable 1 ROM weeks ago....i do not miss the constant bug flashes of official CM13

Side made mention of retiring it, but only when N comes out, and is tweaked to run on our device, until then he's still working on M

Are you tired of misrepresenting yet?
[Galaxy S 4 i9505 Original Android Development] Mentu12:
Hello!

I got a little problem with cm13 snapshot. Phone cant go to deep sleep, its constantly active and drains battery very very quick. Because od that phone get warm. Does anyone got same problem? Thank you for answer and any tips how to solve mine situation.

Wysłane z mojego GT-I9505 przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] masterlo3:
errrr... maybe the official cm don't support your device. JDC CM13 is your best alternative
[Galaxy S 4 i9505 Original Android Development] Mastroaldo70:
cm-13.0-20160819-NIGHTLY-jfltexx.zip update on my Samsung - jfltexx s4 i9505.......

history repeats itself ..

New update, done, new root to do, not rooted device after update ....

BECAUSE ???
[Galaxy S 4 i9505 Original Android Development] Rhoban:
It could be kernel related, since pretty much all JDCTeam ROMs run Alucard kernel and those are the only ones that run well on your device, while everything else runs stock CM kernel.
[Galaxy S 4 i9505 Original Android Development] Heathered:
Let's go with another Snapshot release... :)
[Galaxy S 4 i9505 Original Android Development] rapid_rabbit:
Can anyone share if the new snapshot is stable for daily driver? I was thinking to put the previous one (coming from stock 5.0.1) but comments were negative.
[Galaxy S 4 i9505 Original Android Development] aksdroid:
Hello [MENTION=5604178]zwliew[/MENTION], would you care to share the changelog of new cm-13.0-20160820-SNAPSHOT release ?

---------- Post added at 03:54 PM ---------- Previous post was at 03:54 PM ----------

Hello [MENTION=5604178]zwliew[/MENTION], would you care to share the changelog of new cm-13.0-20160820-SNAPSHOT release ?
[Galaxy S 4 i9505 Original Android Development] fattest:
I tried flashing the stable build for jfltexx to my jfltecan (via twrp 3.0.2-0 for jfltexx), but the install hangs at "Patching system image unconditionally". From a quick search it's usually resolved by changing to a different recovery. Is the CM recovery that is released with the rom recommended over other recoveries? I ended up having to flash stock from Odin (which is what I was on previously) because the nandroid restore kept failing on /data (tried restoring /system and /cache only but that didn't work) and other roms were giving problems with the /system mount. Is there anything else I need to do before installing this rom (change file system, repartition)? THanks
[Galaxy S 4 i9505 Original Android Development] zwliew:
Testing CPU load fix

For those experiencing the issue with CPU cores and frequencies staying high even on idle, please try this boot image:

https://drive.google.com/file/d/0B9qb8cB5djMoLTN0ZnctMS1DZTg/view?usp=sharing

This is related to the isuses reported by [MENTION=7083959]cruplezone[/MENTION] and [MENTION=5400393]Axl_Mas[/MENTION] here:

http://xdaforums.com/showpost.php?p=68259400&postcount=2765

http://xdaforums.com/showpost.php?p=68221448&postcount=2724

I'm doing some preliminary tests, but as I've been relatively busy lately, I figured offloading some testing work to the users would be nice.

Note:

Please provide honest and objective feedback based on comparison between the stock CM 13 boot.img and this boot.img. I don't really want to merge incorrect fixes due to 'placebo'.

Thanks :p

P.S. Seems like there's been quite a bit of confusion on what exactly quantifies a 'snapshot release'; I'll upload a post soon explaining a bit on the difference between nightlies and snapshot releases. (@aksdroid)

P.P.S. The next nightly will allow you to access the 'developer options' of the Snap camera by tapping the 'Bright screen' option 7 times. I wouldn't exactly call it 'developer options' though - it's more like 'advanced options'. Fun stuff nonetheless :)
[Galaxy S 4 i9505 Original Android Development] evlo:
In general snapshot works great!

I have two questions and maybe they are related:

1.*icons - i played with themes and some theme had changed icons for foursquare, x-plore etc. I then found out, that now all dark text were made light so it was not really working great for me. Went back to default, but icons for apps did not revert. Is this standard for themes or should app icons return?

2. gapps - i installed latest gapps with the system, but i chose stock and enabled system partition resize. But now i'm missing default CM apps for phone, messages, or launcher as they had been replaced with gapps ones. Is this standard behavior?

Bonus question - if i reinstall and go with some basic gapps package how to i shrink system partition?

Also screen wake up on call is a bit slow, but i can live with that.
[Galaxy S 4 i9505 Original Android Development] evlo:
I tried updating previous CM13 nightly to today's one and after update i got message "Unfortunately Google Play Services Has Stopped", then when i installed gapps in twrp i get message that setup wizard crashed, repeatedly and i'm unable to see the launcher/desktop.

Are gapps not considered when developing CM or how to proceed if i want to update and keep google services?
[Galaxy S 4 i9505 Original Android Development] laupuy:
Thanks Zhao Wei Liew, it's done: https://review.cyanogenmod.org/#/c/128083

Turn on developer menu and you'll have access to this setting: http://dl-1.va.us.xda-developers.co....jpg?key=5yV2s1ggAKNu9_faB-hHlg&ts=1471763039 or here: View attachment 3848768

:good:
[Galaxy S 4 i9505 Original Android Development] wurstherpes:
Why can't connects SixAxis and a PS3 controller with CM13 ?
[Galaxy S 4 i9505 Original Android Development] Cysign:
First page says "Jira issue tracker - don't report bugs for nightly builds!"

So where to report bugs on the nightly?

I'm using CM13 since weeks and I'm updating as soon as there's a new version.

But since 20160814 or 20160815 there seems to be a really annoying bug:

When I get a phonecall I'm able to reactivate my screen only when the phonecall ended.

When I plaback a voice message the screen turns off suddenly and I need to completly restart my device to get the screen on, again.

I figured out that accidentaly this bug doesn't occur.

So how could I track this bug?
[Galaxy S 4 i9505 Original Android Development] echo_21:
I think it is clear. You must not report this bug in jira as you observed it in a nightly. Still wait for a snapshot or a stable. If the issue is still there report it in jira.

If you can't wait report the nightlies' issues elsewhere e.g. in xda

---------- Post added at 07:15 ---------- Previous post was at 07:04 ----------

How did you figure out? Just by memories?

There are well established good practices in troubleshooting bugs: first you have to install a predecessor Rom of 20160814 to see if the bug really does not happen again. Believe an old dog. Only come back with the results of this potentially surprising test.

---------- Post added at 07:23 ---------- Previous post was at 07:15 ----------

This sounds similar to me as if the proximity sensor is not calibrated correctly anymore. You can check this with the APP "Sensors test" from the play store.
[Galaxy S 4 i9505 Original Android Development] A838:
1. Make sure you tick icons in the Default theme and then reboot after applying.

2. This is standard behaviour. Read https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options to find out how to change the behaviour for individual apps. (To change GAPPS just flash straight after flashing a ROM, no need to clear data)

Bonus - I don't know, maybe enable partition resize when flashing? I have never tried resizing partitions, it's a little dodgy.

I have a question as well:silly:

Does power off alarm work? Is it meant to?
[Galaxy S 4 i9505 Original Android Development] nico933:
sorry if i ask this type of question but i'm on exam time so i haven't time to make some testes.... is camera bug(unable to connet to the camera/camera crash ecc..) solved in the last snapshot/nightly?
[Galaxy S 4 i9505 Original Android Development] Cysign:
Thanks echo_21! I figured out it's my LoveMei case. I removed my phone and retestet the proximity sensor (which was always NEAR in the case) and without it it works properly. There have to be reflections occured by the case...but I wonder why it has worked before. Might the sensor have been recalibrated during the updates?
[Galaxy S 4 i9505 Original Android Development] LinkinParkBoy:
I have too much baterry drain since i installed Snapshot version, both versions 17 and 20. Someone have the same problem? :eek:

I always do Clean install with all Wipes.
[Galaxy S 4 i9505 Original Android Development] Axl_Mas:
Hi [MENTION=5604178]zwliew[/MENTION] ,

I flashed the testing kernel, after numerous tests I can confirm that the CPU Load issue remains.

I've also tried to use other high CPU usage apps (like 3DMark and HD video playback with VLC) but once I've close them the phone correctly returned to idle status: the issue seems to be stricted linked to GPS usage.

How to reproduce the issue:

- activate GPS and use Waze or Maps (also at home for a short time)

- close the app (you can also freeze or uninstall it)

- deactivate the GPS

- Check the CPU usage with one CPU usage app: one core (usually Core 1) stay ad 80-100% warming the phone and draining the battery even if there is no app running. The only way to stop it is to reboot the phone.

Workaround:

Reboot the phone every time you've finished to use a GPS app.

I am on PF4 modem/bootloader but it happens also with older version

S4 version: i9505

I tried to change the CPU governor from Interactive to Ondemand but the issue remains this both of them.

This is the only one bug I still have with this fantastic rom, many thanks for it!!! :)
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
Since we're talking about GPS, does anyone have issues with it? On stock 5.0 I can get a fix from inside my house in 3-4 seconds, on CM13 the GPS can't seem to find me even if I'm outside. I've tried clearing AGPS data, rebooting the phone, flashing another build, try another GPS app but the outcome was always the same.
[Galaxy S 4 i9505 Original Android Development] Catscratch:
I'm on 0731 nightly and everything is working really good. GPS fix in some seconds. I also used fasterGPS app to configure gps for my country. Give it a try and go back. Newer nightlies seem to have other problems too.
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
Hm, the last nightly I tried was 0818. Maybe [MENTION=5604178]zwliew[/MENTION] has something to say about it? I can't flash CM13 right now and I need GPS working to play Pokémon GO :D
[Galaxy S 4 i9505 Original Android Development] Mastroaldo70:
Hi, I try to explain better.

ota update comes out every day.

every day I update.

when upgrading, my TWRP, is reset.

root seems to be no more. rootexplorer and supersu, says that there is no rooting.

each update done, I do cf-autoroot and install TWRP.

can only me?
[Galaxy S 4 i9505 Original Android Development] zwliew:
Don't install any other versions of root! CM provides its own root control.

Steps to enable root:

1. Go to settings

2. Go to about phone

3. Tap on 'build number' 7 times

4. A toast message should appear stating 'you have enabled developer options!'

5. Go back to settings

6. Go to the new option right above about phone - developer options

7. Tap on root access and set it to either 'Apps' or 'Apps and ADB', depending on whether you want root in ADB

8. ???

9. Profit!

10. Get rid of other root control systems

Steps to keep TWRP after an update:

1. Go to developer options

2. Uncheck 'Update Cyanogen recovery'
[Galaxy S 4 i9505 Original Android Development] Racoonator:
Hello,

Little question about root.

I don't use super su, just the root mechanism described by zwliew.

How I can grant to some app the root access manually? In general app send an authorization to ask the root, but how to do this if the application doesn't send anything?

Same, how I can see which app have the root access?

I need this mainly for one app (good for enterprise), it seems give this app the root access solves a bug.

Regards

Stéphane
[Galaxy S 4 i9505 Original Android Development] Flouque:
Settings -> Confidentiality (the shield icon, I don't know exactly the name in english) -> Data protection -> Click on the 3 dots and Advanced settings -> go to the far right panel and you've got all apps which either have or can have root access
[Galaxy S 4 i9505 Original Android Development] Catscratch:
That's a known problem. If you use a kernel with sTweaks support, increase the max CPU frequency. This will solve the heating problem until it is fixed in the rom itself.
[Galaxy S 4 i9505 Original Android Development] baddan:
LTE not works

I have a SGH-M919N and I installed the cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J3-jfltetmo.zip, the devices are the same thing, but my LTE not works.
[Galaxy S 4 i9505 Original Android Development] a103:
I could be wrong but check the APN and add the APN for your network of its not already added.
[Galaxy S 4 i9505 Original Android Development] baddan:
I checked, but LTE is still not working
[Galaxy S 4 i9505 Original Android Development] luptatorul:
The following is about the interactive governor (might be avalaible for the other governors as well)

Hello [MENTION=5604178]zwliew[/MENTION], there's a small problem. When there's only 1 core online, the frequency won't go below 1134 MHz. I hope this helps, I believe it is related to those "spicy" frequencies we experience.

I changed the hispeed_freq to 384 MHz and the boost frequencies (all 4 of them) to 810 MHz, using Kernel Adiutor. I don't know how right this is, but it's behaving much better now.

Edit: I did that because it looks like when there's only 1 core online, that core will stay at the hispeed_freq when doing nothing.
[Galaxy S 4 i9505 Original Android Development] maurocds:
used cm in january, came back to gpe

i just tried latest snapshot again, seems very good

-google camera no longer works with this??????????

-slow charging still present, i had this in january build and still there at least for me, takes like 6 hours to charge device, and yes, battery and charger are fine, it is this rom since it came out in december

no other bugs so far, will keep testing
[Galaxy S 4 i9505 Original Android Development] masterlo3:
Pink Screen!

wow! i've been reading about ''pink screen'' and thought maybe it's something to do with custom kernel or some unofficial version of CM. so today while i was charging device, on mobile data 3G and playing clash of kings, my screen went all pink for the first time in my life so i freaked out and pulled out my battery putting it back on everything's normal again... am on 20160821 official nightly which i've had no issues with so far. just sharing my experience. everything else works well for me.

In other news, Android N is rolling out! :D
[Galaxy S 4 i9505 Original Android Development] baddan:
https://drive.google.com/file/d/0BysezDOSN965dVQ4bGQ0MW05MGM/view?usp=sharing

I Have log
[Galaxy S 4 i9505 Original Android Development] xperiaatic:
I am just coming over from CM12.1 to CM13 and finding 2016-08-20 release surprisingly stable even over CM12.1. Good work!
[Galaxy S 4 i9505 Original Android Development] mirabilis:
I have the same problem... there any solution now? It happens for all voice messages, whatsapp, weixin even google duo... I am on the nightly from 8/17/2016 but that problem is old, was also with cyanogenmod 11...

Thanks for any help!
[Galaxy S 4 i9505 Original Android Development] totopesce:
I just did a clean flash or the snap rom and gapps, and still having the same problem, videos and music dont start and it doesnt produce any sound.

Dont know how to fix it
[Galaxy S 4 i9505 Original Android Development] WolffK98:
Have you already tried to update your baseband and modem? It seems like your baseband is way too old...
[Galaxy S 4 i9505 Original Android Development] Catscratch:
No. I mean increase. The CPU got too much stress with the GPS bug. Increasing speed to 1,89 (afaik) gives the CPU more room to operate.

You can gave a look in the optimized cm 13 thread. They discussed this problem in detail. Maybe. Have a look there.

The target frequency is:
[Galaxy S 4 i9505 Original Android Development] nico933:
Issue title:

Camera crashes

Affected build:

cm-13.0-20160818-NIGHTLY-jfltexx

Last known good:

20160814 OR Since about 20160822 and last nighthly

Issue summary:

The camera crashes when I use it and the last image become home background (wallpaper)

Reproduction case:

1. Open Snap camera app

2. take a photo

3. Camera freezes then crashes, last image become wallpaper, flash title disappear and camera dosen't work again untile reboot.

Logcat

see attachments

[MENTION=5604178]zwliew[/MENTION] i done my best , please let me know if my logcat it's ok or if i need to take another one with others setting (i'm not a big logcatter:D)
[Galaxy S 4 i9505 Original Android Development] :
Guys I am on I9505XXUHOB7. what is the latest baseband for me...? I would like to update it..
[Galaxy S 4 i9505 Original Android Development] jstath1972:
The baseband (Modem) is not related with the AOSP/CM roms and so you have to apply it by yourself. Here and here you can find information of how to change it and for the latest version.
[Galaxy S 4 i9505 Original Android Development] nickmax1:
so the latest seems to be a lollipop one (XXUHOF2 LATEST Lollipop )
[Galaxy S 4 i9505 Original Android Development] jstath1972:
Yes... ;)
[Galaxy S 4 i9505 Original Android Development] nickmax1:
last question then, is it the combined package i want (not the bootloader)

GSM_Modem_I9505XXUHOF2_and_LTE_Modem_I9505XXUHOF2

EDIT: new version found here (OL2)

http://xdaforums.com/showpost.php?p=64701938&postcount=5849