[Bug report] Music player stops playing music from sd after some time

ahmedelhofy

Senior Member
Apr 12, 2012
688
508
0
Shebin El-Koum
I am using the latest build of Gustavo's kernel. Since the 21/12 build of Gustavo's kernel I am having random Baseband issues (phone would not recognize the Baseband after restart, and About phone would show "Baseband: unknown"). Subsequent restarts usually help and once the Baseband is recognized, connectivity is stable.
Restart to recovery, and fix permissions .. That should fix your baseband issues
 

Lanchon

Senior Member
Jun 19, 2011
2,703
4,455
0
fix permissions is a rain dance. people report simple rebooting solves it.

i verified that gustavo's kernel is safe regarding trimming; as safe as my trim kernel. it doesn't mean it will work as it should, just that it shouldnt trigger brickbug.
 
  • Like
Reactions: Acid0057

telephonemann

New member
Dec 27, 2014
3
3
0
User experience Zeitferne kernel

I am using Zeitfernes kernel, based on Launchons kernel, since about 5 days now, and it works like a charm. No battery drain after reboot, phone does not get hot anymore, everything seems to be more fluid.
I am running cm 11 nightly from 12/18/2014 and 12/24/2014, both work very fine. Just HDSPA using seems to drain a lot of battery, and phone gets hot around the camera again. Music bug doesent appear anymore. In general the battery life doubled, though I didnt meassure the sot.
The phone is refusing to connect to any PC or Mac, but I had to change the USB port at the same time I flashed the fixed kernel, so I am pretty sure thats the reason and not the kernel, esspecially because it doesent work with any kernel.

Great job you guys, thought I finally had a reason to buy a new phone, but it seems S2 is back in the game!
 

zeitferne

Senior Member
Jul 15, 2014
153
684
0
Upper Austria
oberon00.github.io
are you doing something to the codebase that is not in mainline arm linux? if so you should report it to the arm list (or i can do it if you want)
The mainline ARM Linux exynos cpuidle driver (wow, that's a word) is completely different, I don't think that the changes apply there (although I haven't seen a call to local_irq_disable or equivalent).
 
  • Like
Reactions: pilgrim011

pilgrim011

Senior Member
May 3, 2008
1,639
456
0
Belgrade
www.tvojsajt.com
I made a small update to my patch, mostly interesting for kernel developers. See here: http://forum.xda-developers.com/showpost.php?p=57643086&postcount=829

/cc @Lanchon, @cybernetus, @Gustavo_s
Could you please explain to us non-developers in layman terms what's this patch for?
As one of the members said recently, the only negative thing so far is the high battery usage over 3g/hspa+/hsdpa (even on screen off it seems to constantly transfer some data according to bbs), but that probably isn't related to fpbugfix. I'm assuming its cm11 fault, or maybe some app misbehaving...
 
  • Like
Reactions: Acid0057

zeitferne

Senior Member
Jul 15, 2014
153
684
0
Upper Austria
oberon00.github.io
Could you please explain to us non-developers in layman terms what's this patch for?
Since the kernel worked well already, there will, as I already said, probably be no difference at all, with "probably" being the key word. The problem was that there is some code in the kernel that expects that it is never interrupted by any other code (e.g. code that executes when the baseband signals an incoming call or when you press a hardware button, or just when a timer fires), as that code's documentation says, but I did not ensure that this was the case. This means that if such a interrupt comes at the wrong moment (a very, very short one, which might be why it did not cause any problems) during the execution of this code (which only executes when the phone enters a deeper sleep state), the behavior of a kernel with the previous patch is unpredictable; it might just work anyway, not wake up anymore, cause the FPBug again, or whatever.
 

snow

Senior Member
Oct 14, 2010
204
305
103
26
www.mozilla.ro
Since the kernel worked well already, there will, as I already said, probably be no difference at all, with "probably" being the key word. The problem was that there is some code in the kernel that expects that it is never interrupted by any other code (e.g. code that executes when the baseband signals an incoming call or when you press a hardware button, or just when a timer fires), as that code's documentation says, but I did not ensure that this was the case. This means that if such a interrupt comes at the wrong moment (a very, very short one, which might be why it did not cause any problems) during the execution of this code (which only executes when the phone enters a deeper sleep state), the behavior of a kernel with the previous patch is unpredictable; it might just work anyway, not wake up anymore, cause the FPBug again, or whatever.
@GeeckoDev have you seen this? :D I hope this will be useful for you for fixing freeze thanks to master @zeitferne :victory: Exynos 4210 FTW! :cool:
 
  • Like
Reactions: GeeckoDev

Maroussia

Member
Dec 8, 2012
8
0
0
EDIT: I have added a flashable ZIP with this kernel (MD5: 55b591535854b66ef0de3245183eb33e).
EDIT2: Updated the ZIP to include driver modules, so that WiFi now works. New MD5: 4d9cd2b9021a4652f7d14ea5a101291d.
EDIT3: Fixed a potential bug. Since the kernel was running fine for (almost?) everyone, users don't need to update, but kernel developers should take a look at the change: https://gist.github.com/Oberon00/9f...xynos-call-pm-notifiers-w-irqs-disabled-patch. New MD5: 4852de8e7c3b77878290a72519b8004d

For a full patchset (includes Lanchon's required changes), see here: http://forum.xda-developers.com/showpost.php?p=57654708&postcount=833.
Does it work with the Samsung Galaxy note 1 n7000 ?
 

pilgrim011

Senior Member
May 3, 2008
1,639
456
0
Belgrade
www.tvojsajt.com
I made a small update to my patch, mostly interesting for kernel developers. See here: http://forum.xda-developers.com/showpost.php?p=57643086&postcount=829

/cc @Lanchon, @cybernetus, @Gustavo_s
I have flashed your newest kernel. It was running fine, but after I rebooted the phone, the mobile network was gone - something like when there is a problem with efs. I have waited few minutes, then rebooted to recovery and flashed Apolo (version with your previous patch) and after reboot the network was there.
I have to say, maybe this isn't connected with newest patch, but that is what happened. It could be that network was down for all in that particular moment, or it was a bug with modem or... Who knows...
 

notabenem

Senior Member
Jul 17, 2009
118
75
0
I have flashed your newest kernel. It was running fine, but after I rebooted the phone, the mobile network was gone - something like when there is a problem with efs. I have waited few minutes, then rebooted to recovery and flashed Apolo (version with your previous patch) and after reboot the network was there.
I have to say, maybe this isn't connected with newest patch, but that is what happened. It could be that network was down for all in that particular moment, or it was a bug with modem or... Who knows...
Had a similar problem. See this post: http://forum.xda-developers.com/showpost.php?p=57756636&postcount=860
As of this moment (running Gustavo's 23/12 build) I still think it applies to my phone (but I did not restart for a couple of days now). I suspected the TRIM code to cause this, but since you're using zeitferne's patched kernel which does not include the TRIM it must be something else. Either zeitferne's own patch, or something completely unrelated.
 

pilgrim011

Senior Member
May 3, 2008
1,639
456
0
Belgrade
www.tvojsajt.com
Had a similar problem. See this post: http://forum.xda-developers.com/showpost.php?p=57756636&postcount=860
As of this moment (running Gustavo's 23/12 build) I still think it applies to my phone (but I did not restart for a couple of days now). I suspected the TRIM code to cause this, but since you're using zeitferne's patched kernel which does not include the TRIM it must be something else. Either zeitferne's own patch, or something completely unrelated.
Yes, but your problem is with Gustavo_s kernel, and that kernel had similar problems for months before this patch even existed. Since Gustavo_s made a shift to Synapse and started to experiment, it's not rock stable like it was before...
On the other hand, I had this problems several times in cm11, so it could be totally unrelated to zei's patch...