Elegancia Music Player - HTC One X+

Hi,
I rooted yesterday and flashed Elagancia for my HTC One X Plus. I have noticed that the there are little glitches when the music player is playing, sort of like an occassional hesitation or dropped byte. It's not so bad that it is a big bother. The only reason I put music on the phone was to test the player. Still, has anyone had a similar problem?
Also, during installation, the instruction warned that if you don't have S-Off, you need to flash the kernal. Heck if I know if S was off. I just finished the newbie tutorial at http://forum.xda-developers.com/showthread.php?t=2213910, which is, by the way, the best I have ever seen. I didn't know how to backup, so I proceeded with the installation. The phone is running okay except that CoPilot won't start, and I have that glitch. I just mentioned S-Off just in case it could have something to do with the music player.
Ndmand

---

Ndmand said:
Hi,
I rooted yesterday and flashed Elagancia for my HTC One X Plus. I have noticed that the there are little glitches when the music player is playing, sort of like an occassional hesitation or dropped byte. It's not so bad that it is a big bother. The only reason I put music on the phone was to test the player. Still, has anyone had a similar problem?
Also, during installation, the instruction warned that if you don't have S-Off, you need to flash the kernal. Heck if I know if S was off. I just finished the newbie tutorial at http://forum.xda-developers.com/showthread.php?t=2213910, which is, by the way, the best I have ever seen. I didn't know how to backup, so I proceeded with the installation. The phone is running okay except that CoPilot won't start, and I have that glitch. I just mentioned S-Off just in case it could have something to do with the music player.
Ndmand
Click to expand...
Click to collapse
That issue has nothing to do with Elegancia, that's just the way the stock HTC Music player works. You might try Viper XL+ which lets you tweak the minfree settings to open up more ram for multitasking, as the phone gives a lot of it to sense. Viper also lets you adjust the minimum CPU frequency and the minimum frequency for when the screen is off, with the screen of the phone clocks to 51 mhz by default, and will dry to drop down that low without other activity. You could also root and try Set CPU or System Tuner to do the same thing without having to flash another ROM.
S-Off also has nothing to do with this, you correctly understand that S-Off just means you have to flash a kernel via USB when changing ROMs.

---

kylealanr said:
That issue has nothing to do with Elegancia, that's just the way the stock HTC Music player works. You might try Viper XL+ which lets you tweak the minfree settings to open up more ram for multitasking, as the phone gives a lot of it to sense. Viper also lets you adjust the minimum CPU frequency and the minimum frequency for when the screen is off, with the screen of the phone clocks to 51 mhz by default, and will dry to drop down that low without other activity. You could also root and try Set CPU or System Tuner to do the same thing without having to flash another ROM.
S-Off also has nothing to do with this, you correctly understand that S-Off just means you have to flash a kernel via USB when changing ROMs.
Click to expand...
Click to collapse
I believe what causes this audio stutter is indeed a low clock rate when the app does not have focus, especially when the screen is off. This happens in Elegancia, stock HTC Music, Winamp, Play Music, and more.
The only solution I've found is setting the processor to Performance (so that it never drops below the maximum clock), but that's a battery hog.
Also, the problem seems to have disappeared after installing ParanoidAndroid - perhaps that's because Sense isn't there to hog the processor.

---

Hero_Lief said:
I believe what causes this audio stutter is indeed a low clock rate when the app does not have focus, especially when the screen is off. This happens in Elegancia, stock HTC Music, Winamp, Play Music, and more.
The only solution I've found is setting the processor to Performance (so that it never drops below the maximum clock), but that's a battery hog.
Also, the problem seems to have disappeared after installing ParanoidAndroid - perhaps that's because Sense isn't there to hog the processor.
Click to expand...
Click to collapse
The only solution may be upping the minimum clock speed. I also want to say that using PowerAmp has fixed this for me, but I'm not sure why. PowerAmp also has the ability to use a wakelock to keep the CPU up and also to keep service from being unloaded when in idle. The latter might help specifically with the stock multitasking values on this generation of HTC Phones which don't allot very much RAM/CPU time to non-HTC processes. I haven't had to try these, but they might help depending on what specific usecase is causing your issues.
I believe it would also be possible to set a Tasker profile to up the minimum CPU values when audio is playing, but that's a little over my head. That would certainly give the best balance of battery life and performance though, as the CPU really shouldn't dip as low as it does when audio is playing. I have my suspicions that HTC tried to drop the clock speed as low as possible at all time because in my experience the Tegra 3 chipset runs hot under even moderate stress, and uses much more battery than other chipsets for simple tasks. The chip doesn't seem to me to use more battery than others under high stress though, so upping the clock only when intense activity (like multitasking with audio playing in the background) would seem like the best course of action. I might try to use my HOX+ for a few days with a higher minimum CPU speed to test my theory.
---------- Post added at 09:43 PM ---------- Previous post was at 09:38 PM ----------
For what it's worth, my Nexus 7 gets MUCH better battery life on CM 10.1 with Franco Kernel than it does on stock, there might be some optimizations or tweaks enabled that help, I'll look into it.
For those who don't know, the Nexus 7 has a slightly different Tegra 3 chipset clocked at 1.3 GHz as compared to the 1.7 GHz SOC in the HOX+. There are also some low level cost saving differences in the Nexus 7's CPU though as I understand, and those compromises make it less powerful, which in turn, could have heat/power drain implications.
Also this discussion might be moot in a month or so if the HOX+ is updated to 4.2 which could very well bring more optimizations from HTC and of course from a newer version of JB.
Does anyone know if the new HTC One suffers from any of these audio playback issues?