yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Pfeffernuss:
If I leave the phone overnight, let's say for 8 hours or so, around 12% battery is gone. Deepsleep is at 95%. No apps consuming anything major, no screen on. And what's on top of the list? FD-this, FD-that, etc. So yes, the ONLY thing that's draining my battery at that time is FD-related and the alarm wakelocks I can't get rid of but those are normal because of the stuff running in the background.

It's a normal work day over here now and I couldn't let the phone lay dormant for longer than this. But yes, these are FD-related wakelocks galore.
[Galaxy S 4 i9505 Original Android Development] ionutzvio:
Tnx for your reply guys. I will stay with the nightly builds
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Would the fast dormancy stay disabled if I nandroid my setup, flash a samsung stock rom, disable it with the dialer code and then restore the nandroid?

L
[Galaxy S 4 i9505 Original Android Development] jmjviana:
This is happening in every update I do. I have to remove the Google account and add it again. Wipe the cache isn't working. Any ideas for a permanent fix?
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Guys are you getting a screen burn in?

The black status bar in cm10.x will burn in and make the area blue-ish (or another color). Had that with my S2 too.. Why is google choosing this? In fullscreen apps you'll always see the area with the burnt in status bar... Damn :/

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] Planet X:
It's not a matter of Google chose for it. It is a shortcoming ot lets say property of the OLED screen what Samsung has chosen for.You could also choose for a phone with LCD screen what does not burn in. OLED and Plasma does. And by the way Google has chosen for LG wth LCD screen.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Gingerbread on the Nexus S with amoled had a black status bar.. Just sayin..

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] Planet X:
I know I owned that one too. As all Samsung High End phones. But all the Nexus too. I never own a phone longer the 3 months by the way...
[Galaxy S 4 i9505 Original Android Development] Pfeffernuss:
Of course. Every AMOLED-based phone has burn-in, whatever the owners (I have no burn-in!!1!!111!) might say. All of them. Even after a relatively short time.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
That's a pity. A 'destroyed' 1080p display isn't that nice.. But damn it. I buy a new one every year lol. Google come on bring kitkat!!! Jelly bean gets boring..

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] Seferi:
What so you guys mean by screen burn in? Can you post a Screenshot?
[Galaxy S 4 i9505 Original Android Development] Planet X:
There has been a change today in the Android.mk.

Change-Id: Ic7337daeb61aa8eb862aa33c4533a0177db87aa1 which means to make su optional in cm10.x

Does this mean we have to change something like export .... in terminal before start building to have su installed in cm10.2?
[Galaxy S 4 i9505 Original Android Development] -Koze-:
classic issue of amoled screen is deteriorate unalike

example http://oi52.tinypic.com/149b76o.jpg
[Galaxy S 4 i9505 Original Android Development] Seferi:
Thanks for the pic. Does this happen in time? My device seems fine...
[Galaxy S 4 i9505 Original Android Development] donalgodon:
As I understand it, this optional su means that each build maintainer has the option to include it or not. I don't think it means that we have the option to choose whether or not to install it. Not even sure how that would work, given that CM uses zips and not something like Aroma, which allows user selectable options on installs.
[Galaxy S 4 i9505 Original Android Development] Planet X:
Thank you for your answer. As I usually build myself at home I have to do it on my own. That's why I asked. I guess there are more home brewers around here and may be somebody already knows if we have to do a export command or not to still have su in the rom.
[Galaxy S 4 i9505 Original Android Development] ksr007:
Sorry for noob, but how can i unlock sim network after installing CM10.2 ? :)
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
What's that?? It keeps my phone awake :/

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] MrJiM:
do u mean after pin? reboot 1 time then it dont hang.
[Galaxy S 4 i9505 Original Android Development] JacksoNxy:
Lockscreen doesn't wake on homebutton?! CWM 6.0.3.6 and yes I found the settings and activated that... Doesn't work...
[Galaxy S 4 i9505 Original Android Development] donalgodon:
Works for me. Must be something on your end. Maybe do a full wipe and reflash.
[Galaxy S 4 i9505 Original Android Development] JacksoNxy:
Hmm did it twice

---------- Post added at 11:22 PM ---------- Previous post was at 11:17 PM ----------

Sorry, so it does unlock the lockscreen but does not activate the sleeping display after locking?!
[Galaxy S 4 i9505 Original Android Development] tapiov:
What do you mean? There's a setting for the device to wake on home button and setting for different unlocking methods. Can you describe in more detail what are doing, what happens and what would you expect to happen?

I recently had this: http://forum.cyanogenmod.com/topic/79516-solved-nightly-20130926-lock-screen-not-locking/
[Galaxy S 4 i9505 Original Android Development] Steyux:
I have an issue, apollo seems not recognize my external sd: if I put a song into the internal sd apollo sees it, but if I put it into the external one apollo doesn't see it....

Does anyone else have this issue? It seems like cm doesn't to a media scanning of external sd. I've also tried with 2 different SDs to see if the problem was the sd but it isn't :(

Galaxy s4 i9505 cm 10.2 27/09/2013 nightly
[Galaxy S 4 i9505 Original Android Development] jcasares:
What I had after applying a nightly from some days ago is that I lost the setting and had to enable it again.

Maybe he is having that... but I confirm that it works.
[Galaxy S 4 i9505 Original Android Development] pitcher85:
.

Does the screen rotation lock quick toogle work for you in the 09/27 build immediately?

No matter which activity is displayed, I have to reopen the activity that the rotation feature works.

This holds for enabling as well as disabling the rotation lock.

In older builds a rotation lock toogle took place immediately :confused:

This is quite bad if you want to enable the rotation while being in one specific activity :-/

.
[Galaxy S 4 i9505 Original Android Development] OpenCollective:
Can you access the SD card from other apps on android? Have you tried inserting your SD card into your PC? Can you access it there?
[Galaxy S 4 i9505 Original Android Development] Steyux:
Yes I can access the SD card with any file manager (only CM original file manager doesn't see it) and my pc recognize it as well. I can also see it in "Storage" settings as you can see in the screenshot attached.
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
try rebooting

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Worked! Thanks. But strange bug..

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] jakemog:
Why is the camera getting ignored? :(
[Galaxy S 4 i9505 Original Android Development] donalgodon:
That's something I've wondered about myself.

Green lines in FFC

No HDR

No Focus in Scene Modes, etc.

I would have thought that, by now, with the GE sources, we'd be a lot further along in terms of the Camera functions.
[Galaxy S 4 i9505 Original Android Development] tapiov:
The thing is, although I keeping up positive thinking about CM Inc, I am worried that going forward OPPO is going to get much more love than other devices. That's where the money and fame will be coming, so other devices will be left with less development.
[Galaxy S 4 i9505 Original Android Development] jakemog:
I have noticed GE has low recordig fps in low light too, why would google do that when in can do 30 fps all the time :confused:

Camera has not been touched since the 1st build... its really making me want to go back to TW, even though i don't..
[Galaxy S 4 i9505 Original Android Development] jmjviana:
In games like this one: https://play.google.com/store/apps/details?id=dk.logisoft.aircontrolfull appears some graphic problems.

In this one in particular the line of the target of the planes makes some glitches.

Can someone test it out and give me some hints on how to solve this? This only happens in CM. In TW it doesn't.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Green lines on front cam with CM Gallery2.apk?

I guess it's a GoogleGallery.apk known issue on i9505 but not with cm one.
[Galaxy S 4 i9505 Original Android Development] rob151515:
I had a similar problem and Apollo wouldn't find my music until I created a new music root folder and moved all my music into it. From memory I think I originally had my music in /Music and then created and moved it all into /music. Weird but its working now. Might not be the same issue but thought I would mention just in case.
[Galaxy S 4 i9505 Original Android Development] BillGoss:
I'm on 0928. The orientation quick tile works as follows:

- locking the orientation works without needing to leave the current screen. However, if you rotate the screen it will first rotate the display followed by rotating it back to the original orientation. After that rotating the screen has no effect.

- unlocking the orientation requires you to leave the current screen, such as bringing up the recent app list, before the unlock takes effect.

I can't comment on earlier versions as I never tried this until I saw your post.

Update: cm 10.1.3 works properly. I tried cm 10.2 0926 and 0924 and both of these have the bug.

I've added this to the bug listhttp://xdaforums.com/showthread.php?p=44627324

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] donalgodon:
Yes, they are still there with CM app, at least for me, as are all the other bugs, such as non-functional focus in modes, HDR, etc.
[Galaxy S 4 i9505 Original Android Development] NZgeek:
The GE sources contain quite a few closed-source binary drivers, and the CM team will only use these drivers as an absolute last resort.

I would guess that it's all about trying to capture enough light to have something visible in each frame.

In low light, you essentially have two ways of making the image brighter: capturing the image for longer (i.e. reducing frames per second), or trying to amplify the available light (i.e. increasing the gain). The problem with increasing the gain is that it amplifies everything that causes the sensor to react, including background radiation. This shows up as image noise. Increasing gain will also decrease saturation and contrast.

Samsung have probably chosen to increase the gain, vs reducing the frame count like Google have chosen. The choice is effectively between a smoother video with lots of visual noise, or a more jerky video with better image quality.
[Galaxy S 4 i9505 Original Android Development] ixomon:
Simply turn off screen when attached to power source. To be found in the developer option.
[Galaxy S 4 i9505 Original Android Development] Pfeffernuss:
Hahaha and that will completely avoid getting burn-in? What a joke :good:
[Galaxy S 4 i9505 Original Android Development] upichie:
Honestly, I've only ever owned AMOLED Android devices—and one of those devices was used for over 3 years—and I have never witnessed even a hint of screen burn-in.

Your mileage may vary of course, but it doesn't feel like a rampant problem that every user experiences. And I've had plenty of 8+ hour screen-on time days.
[Galaxy S 4 i9505 Original Android Development] Pfeffernuss:
Emphasis is the key.

Same as people saying "my plasma is completely black", "my phone is 100% smooth" etc. All in the eye of the beholder, but all not necessarily true :angel:
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
Well the Galaxy S(1) had some trouble with screen burns. Multiple friends of mine had screen burns where the keyboard would burn into the screen.

But I haven't had that with the S2, S3 and S4. The thing that sucks with the screen of the S4 is the purple smearing or ghosting issue. When the Nexus 5 get's released I'm def. switching over to that one. It's kinda unacceptable that a 700 euro phone (now 500) has a screen with issues.
[Galaxy S 4 i9505 Original Android Development] upichie:
As a power user who clocks in 5+ hours of screen-on time a day, who shares his device with other people, who has owned an AMOLED device for over 3 actively used years, who is consciously aware of and has plenty of experience with screen burn-in, and who has the necessary tools (and eyesight) to test for it's existence, all I have to say is this:

People are doing it wrong. That is all. :p
[Galaxy S 4 i9505 Original Android Development] Pfeffernuss:
No, probably you have the single one phone with an Amoled screen without any burn-in in existence. Don't sell it. It's unique! :good:

Because of the different aging speeds of the subpixels you will always have a form of burn-in/aging after a while. Now that they made the blue subpixels (which decay the fastest) a lot bigger on the diamond-shaped Pentile display on the SGS4 the problem is somewhat less than before. But still, the subpixels decay at a different speed, after a while all amoleds will show some form of burn-in/aging. All of them. Yours as well. You can't see it? Great. Is it there? One hundred percent certain. Does it matter? Nope.
[Galaxy S 4 i9505 Original Android Development] upichie:
Technically you are correct, but if someone with 20/20 can't see it unassisted, I would consider it to not be there—or not be relevant. I do feel the picture posted before is due to user error. But of course, we all strive to not have that worry, regardless of the user.

Anyways, I appreciate the discussion. I'll get back on topic now. :)
[Galaxy S 4 i9505 Original Android Development] jmjviana:
I'm sorry, I gave you a link for a paid version. Can you test this one: https://play.google.com/store/apps/details?id=dk.logisoft.aircontrol and tell me if there are trajectory line glitches of the planes?

In the stock ROM wasn't happening with me.
[Galaxy S 4 i9505 Original Android Development] jcasares:
There are many things that end in a burn in. I had one with my S2.

It was my fault. Using it at 100% brightness all the time. Having it for 2 years with 2~3 hours of screen average every day.

I used a lot that phone, but the culprit seemed to be an app I couldn't track, that turned the screen on/off at night while I were sleeping (maybe NoLED).

In any case, now I use auto-brightness and try to monitor that no app malfunctions with the screen.

And you can see the burn in on a full white screen. It's quite visible for me but most people wouldn't care/notice. I showed to a friend that said he didn't see anything wrong. :p
[Galaxy S 4 i9505 Original Android Development] donalgodon:
No new build again today?
[Galaxy S 4 i9505 Original Android Development] jcasares:
You mean the trajectories that are shown to show where your plane is going? That's not a glitch...

But if you see something wrong with the lines, I don't. Here they work as expected.

I played this game in the S2 and see no difference to those times.
[Galaxy S 4 i9505 Original Android Development] jmjviana:
The lines appear behind the plane blinking. That's not normal. It only happens if I have the hardware acceleration enabled. With it disabled the game stays slow. With the hardware acceleration enabled in the stock ROM everything was fine.
[Galaxy S 4 i9505 Original Android Development] jcasares:
Ok, no, I don't get those lines behind the plane and I have Hardware acceleration enabled in the game.

Maybe some OS setting? I have it by default but there might be some settings in development and performance that could cause such issue.

I'm on 0928 build.
[Galaxy S 4 i9505 Original Android Development] jmjviana:
I've putted everything in default in performance and disabled development, rebooted the phone and it didn't worked. :(
[Galaxy S 4 i9505 Original Android Development] simondavies315:
Bug Report: When playing Worms 2: Armageddon on CyanogenMod 10.2 the screen goes black between player turns.
[Galaxy S 4 i9505 Original Android Development] kubicek123:
Quick Glance

Did anybody found any alternative for Quick glance from stock TW rom? (wave your hand over sensors shows time and information about missed messages, calls etc. for a short time)
[Galaxy S 4 i9505 Original Android Development] jmjviana:
Here it is a screenshot about what I was saying before.

Other games are very slow and buggy. Any ideas?
[Galaxy S 4 i9505 Original Android Development] donalgodon:
Seems that audio blobs are being merged into the next build. Anybody know what they actually fix? I confess that I sometimes find the Gerrit code reviews rather cryptic and it's hard to understand what they address.

Is there a plain language description available anywhere?
[Galaxy S 4 i9505 Original Android Development] jmjviana:
In brightness levels it's not doing the lowest level. 0lux - 0%. The phone can go darker when I'm at 0 lux and it doesn't.
[Galaxy S 4 i9505 Original Android Development] jmjviana:
In today's build both of the issues I said earlier are persisting.
[Galaxy S 4 i9505 Original Android Development] jcasares:
I don't have the back trails staying but I see some delay on them disappearing.

I don't remember if that happened in the GS2. Have to try it with other phones.

Which games?
[Galaxy S 4 i9505 Original Android Development] jmjviana:
This game is also too slow: https://play.google.com/store/apps/details?id=com.ricardoalves.quemquerserrico (it's in Portuguese, sorry)

It wasn't slow in the stock ROM. Having a S 4 slow is kind of a joke.

Does anyone know where I can find modems to flash over recovery for this phone? Anyone recommended?
[Galaxy S 4 i9505 Original Android Development] donalgodon:
All of the sudden, for some unknown reason, my screen stopped sleeping when charging.

Went to Settings - Applications - Development -. made sure that stay awake is unchecked and the screen will still not sleep.
[Galaxy S 4 i9505 Original Android Development] NZgeek:
I'm not sure of the reason why, but it's near impossible to flash a modem on the I9505 unless you're using Odin/Heimdal. Mobile Odin is said to work too, but flashing from recovery just silently fails.

Update: this thread is a good source for modems: http://xdaforums.com/showthread.php?t=2192025
[Galaxy S 4 i9505 Original Android Development] jcasares:
Ok, I can't help you with that one. Paid and in another language I don't manage. :p

I had trouble (being slow) with three games so far:

- https://play.google.com/store/apps/details?id=com.lattanzio.eljodete (it wasn't fast on S2 but is unbearable on S4)

- https://play.google.com/store/apps/details?id=com.rangames.jigsawmanads (was slow in an old version but new ones work quite fast).

- https://play.google.com/store/apps/details?id=ua.co.cts.sideup (slow on CM 10.x or is it Android 4.1+)

I blame the big resolution but could be CyanogenMod as well. As I don't care much about those I ended removing them.

As I can't stand Tocuhwiz I never used those games on the S4 with original ROM so I can't say if they work well on it. Maybe someone can test them?

Not possible as already said. Just use ODIN and the procedure detailed in the proposed thread (writing modem two times).
[Galaxy S 4 i9505 Original Android Development] jmjviana:
You have here the free version: https://play.google.com/store/apps/details?id=com.ricardoalves.quemquerserrico.lite

I'll test those you said to see if they're slow with me.
[Galaxy S 4 i9505 Original Android Development] jmjviana:
The first one was also very slow with me.

The others I think were OK.

I've also tested the air control in the S 3 and was working without the lines behind the planes.

I think it's a CM problem because I played the game in S 4 stock ROM.
[Galaxy S 4 i9505 Original Android Development] philipkroberts:
Should I go for the Stable or the Nightlies?

If I go for stable and there are bugs or whatnot and a further update is released can I download that OTA?

Thanks
[Galaxy S 4 i9505 Original Android Development] donalgodon:
To me, there's not a major difference between "stable" and the "nightlies" and I have bounced back and forth a few times between them. I just prefer the layout refinements in 10.2, so I'm on the nightlies and will probably stay there.

You must do a full wipe between the two, so changing isn't just a simple flash either way. You are still going to need to do a setup.
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
Though i know the solution, but where does the problem persist? im guessing its not with the recoveries since it has problems on every single one.
[Galaxy S 4 i9505 Original Android Development] BillGoss:
[MENTION=2385005]invisiblek[/MENTION] gave me a copy of a different updater binary and that worked. So that's one possible place of the problem.

I've also encountered problems with the official CWM from http://www.clockworkmod.com/rommanager just wiping the cache and system partitions - not even trying to flash a file. Remember it's the format statement that's causing grief. That would indicate that there's some problem with recovery itself.

I'm assuming that all the different recoveries have some common code at their heart. It may just not work on the S4 - who knows if it's due to something Samsung have done in the design of the S4

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] websinister:
I know that removing the line to format /system makes the nightlies install without errors from recovery. But what if there are files that were removed from the previous nightlies - those files will not be cleaned/removed since the format line was omitted from the update-script.

This is what I did to make nightlies flash without errors:

Original:

...snip...
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p16", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p16", "/system");
package_extract_dir("system", "/system");
...snip...

Modified:

...snip...
run_program("/tmp/backuptool.sh", "backup");
show_progress(0.500000, 0);
delete_recursive("/system");
package_extract_dir("system", "/system");
...snip...

I know it is easier to just delete a line rather than the path that I took - but this method makes me sure that I'm installing a cleaner CM.
[Galaxy S 4 i9505 Original Android Development] maxamus007:
I for the life of me cannot install this ROM :(

#1 I use Odin to install I9505XXUBMEA-PRE-ROOTED-ODEX-FULL

#2 Then i use Odin to install i9505-cwm-recovery-6.0.3.2(0611)

#3 Copy rom + gapps over to phone (internal sd card as i dont have an ext one yet)

#4 wipe cache

#5 wipe dalvik

#6 wipe data/factory rest

#7 install rom from sd card

#8 pick rom and install........this on two occasions has turned off the phone mid way through install.

#9 pick gapps and install.....this on two occasions has turned off the phone mid way through install.

I just cant get past this stage.

Everytime it happens i have to repeat the process from #1.

Any ideas?!
[Galaxy S 4 i9505 Original Android Development] Mohanned85:
Must try. What recovery will this work with
[Galaxy S 4 i9505 Original Android Development] thunderserpent:
About 40% of the time when I turn on my phone it hangs on the boot logo and when my phone is off and I plug in my charger it hangs on the battery loading logo 85% of the time.
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
try flashing another kernel
[Galaxy S 4 i9505 Original Android Development] thunderserpent:
I've tried chronic and KT kernels, they make no difference. They also seem to stuff up my OTG...