First post so please be gentle.
OK, here goes. I have a HTC Desire GSM running the stable CyanogenMod 7.1 ROM and occasionally (20-30% of the time) when playback of a new track starts it will stutter - as if the track is stuck. This lasts a second or so before it sorts itself out. I am using the music player that ships with Cyanogen but I've also tried the stock (unmodified) 2.3 player and Google Music 4.0.1 (the leaked ICS version). All three have the same issue. There seems to be no obvious pattern to this - MP3 bitrate, etc. doesn't seem to matter.
I run as few background processes as possible and don't have much in the way of widgets installed.
Now, I'm new to CyanogenMod and have been running Oxygen for the last few months where this issue never occurred. However, prior to Oxygen I was running the 2.2 HTC Sense kernel (before I got into rooting and ROMs) and this release would also exhibit a similar issue (again at the start of some tracks, no pattern). The original 2.1 HTC Sense kernel the phone came with was fine.
My first thought was DSP - but disabling this makes no difference. I am also not short of memory - right now I have 175MB free.
I have a 16GB SanDisk microSD card but am not sure what class it is. As it worked OK with Oxygen I'm not sure it's the root of the problem but who knows.
I really, really like the CyanogenMod ROM and would prefer not to switch back to Oxygen so am after any suggestions of things I can try in an attempt to resolve this issue.
Any ideas? Would any of the CyanogenMod performance/advanced options have any bearing on this? I don't mess with CPU governors at the moment.
Try wiping Dalvik Cache
Tried that but still stuttering.
Related
Hi there!
As you might see, I'm new here, so please kick my ass kindly if this issue has already been discussed (even though I'm pretty sure it didn't, after spending a couple of hours reading tones of threads).
I was kind of disappointed when I unpacked my Desire a week ago, discovering how low the headphones volume was compared to my former iPhone 3G (R.I.P). Fortunately, the froyo update came out a couple of days after, I installed it, hoping it will solve this issue... Obviously, it didn't.
After being able to root my desire (thanks to the downgrading hack ), I started trying a bunch of roms, starting with the Psychosis-1.2 one, and happily discovered that the music was finally as loud as on my iPhone with this rom.
The issue here is that I still get the same low volume problem with other roms (so far, I tried OpenDesire and Pinky (this name should definitely be changed...).
I also tried the NexTSense rom and unsurprisingly, the volume was good on this one as well (unsurprisingly, as Psychosis is based on that rom...).
My question is quite simple: would you know which .apk/.so/.jar could I extract from NexTSense in order to get a decent volume on the rom I will finally hang out with?
Thanks.
No one?
Just tried out the LeeDroid rom, and the volume is also ok with this rom...
LeeDroid does nothing really fancy.
So either your problem is fixed in the new 2.09 official update (and all the custom roms based on that one, like pinky, nextsense, leedroid, modaco r7)
It will for sure NOT be as simple as extracting a single .apk. The volume (and even mp3 decoding and media playback) is not handled by the music player software at all.
So you'll have to look in firmwares, libraries or kernel being used and stuff like that. Not something you easily dive into and rip out if you're new to linux / android developing. It might also be something with the new radio that you probably installed to get the latest leedroid or others running.
For what it's worth, I never noticed (too) low volume on my desire, and tried a lot of ROMs (2.1 official based, 2.2 official based, AOSP, Cyanogen)... never noticed a difference in volume. You sure it isn't some placebo effect?
Yep, 100 percent sure its not a placebo effect, I compared for each Rom the volume on my desire with the one on my former iPhone, using the same song and headphones, and the volume was only at the same level with the Roms I mentioned.
Plus, It's not radio related, as I had this issue with stock sense on both radios, and as I tried all the Roms with the last one...
I'm pretty convinced it's library related, I'll do a comp of the ones dealing with audio and tell you what.
Sent from my HTC Desire using XDA App
I (still) love my Desire, unfortunately after two weeks of usage or so the screen starts annoying me! Any live wallpaper is unusable due choppy home screen scrolling and some menus like "All Apps" or "Customize" become very slow at the bottom. At first I thought it was problem of custom ROM, but this is happening even on stock ROM, so it's probably a HW problem (GPU maybe?).
Can someone help me?
Thanks.
HW problem? Don't think so. However, can be, but it's not likely.
I suggest to try a different kernel and if that not helps do a full wipe & reflash.
I see, that we use the same radio & kernel (except that I'm on LeeDroid) - but i never experienced that slowdowns.
Nah, coutts, CM, HTC, ziggy... All the same.
Try changing your governor
Sent from my HTC Desire using XDA App
Maybe a ram thing .... i use (i know not all think this is good but) a taskmanager with a auto close apps widget
with kind regards...Alex
Still the same and I have plenty of free RAM.
If your device can still play 3d intensive games without slow downs or errors then I doubt it's a hardware problem. So...Does it play games properly?
Recommend such game that is OK on your Desire, so we can compare.
Try nenamark (1.5 free in the market). I get 20.9 FPS with the stuff in my signature. So if you get more than 15 then I think it won't be a hardware problem.
Also I noticed the lag when something is installing. So can be the a2sd+ slowing down your phone.
It can't be due A2SD (read OP).
Btw, I got 18,6 FPS.
Hmm, then the gpu/cpu seems to be fine. Must be a software error.
But what SW? Every ROM and every kernel behave in the same way.
That's what I try to figure out. So if you do a full wipe & changing ROM - Lag remains.
Changing kernel - lag remains.
Seriously, I have no idea. Usually a full wipe & reflash helps (ROM+kernel).
Can't it be the radio?
Can't be, this problem started in virgin stock ROM (I have copyright on that ).
Have you tried aosp roms its probaly a HTC sense issue
Sent from my HTC Desire using XDA App
AOSP ROMs have the same issue.
maybe your NAND got corrupted in some way?
maybe after you install new ROM try not to restore your previous apps or system setting with neither titanium backup or mybackup, whichever you use.
however,i would assume you tried that already.
also you could try going back to stock ROM and or even HD rom which fits on NAND and try booting without SD card which maybe trying to read something and it cant.
so was your phone branded?
and when did you noticed this performance issue?
Unbraded. And I noticed it during using stock ROM.
Don't know if its just imagination but i think my desire has also gotten more laggy lately.
My phone has definitely slowed down LWPs are pretty much unusable & Sense always slows right down at the bottom of some menus, including the app drawer.
I noticed that the TW music player no longer allows 5.1 surround to play through bluetooth. Anyone know why?
Why have devs moved from SetCPU to Tegrak?
What is the deal with some ROMS only installing from internal storage even if it is not noted as needing to be on internal storage.
Why do some ROMS perform INSANE on one phone and perfectly fine on another? Not a user problem. These are roms I flashed for myself and they are great; then I flash them for others and there device goes bonkers even before they reinstall data. I pick a differnt ROM and we're good. that different rom may go bonkers on anohter device ect....
Is there a list of general android bugs that no manufacturer is able to fix or workaround?
How much work goes into updating APK's to work with new OS updates. for example; launcher pro is kinda buggy now, so is zeam. Bother were amazing before the later froyo and gb updates.
That's it for now, I know there is more but Im drawing a blank.
Hello all,
A long time ago I got bored of the stock ROM on my Desire HD and ended up rooting and installing CM7.2. That was a fantastic move as the phone was now faster, smoother and had more features than the stock ROM ever had. However, as Android has progressed onwards I've looked wistfully at 4+ phones and wished I had a slice of that goodness. So, over the past few months I've experimented with a couple of ICS and Jelly Bean ROMs (PACman, JellyTime, TrickDroid). However, despite these ROMs all being fully functional, performance was always often so frustratingly bad that I always ended up going back to CM7.2. The interesting thing is that individual applications generally tend to work very well. For example, a good portion of the time, web browsing on the stock browser on PACman is fantastic - smooth, fast, better than anything I'd experienced on the DHD. However, when loading and switching between apps (including sometimes when using the keyboard), going back to the homescreen etc, the performance would often be molasses slow. Reverting back to CM7.2, sadly, always feels like a breath of fresh air!
The only thing I noticed was that the device reported twice as much free RAM in CM7.2 as it did in the 4+ ROMs (between 200-300MB, compared to less than 150MB). Interestingly enough, in PACman when you go into the AOKP settings you can enable a RAM counter in the application switching interface. This always reported much less free RAM available than the the stock RAM counter that you can find in Settings->Apps->Running Apps (why is that?). But regardless of that, that counter was very frequently showing very little free RAM (a few MBs) when the phone was acting super slow. I tried messing around with memory management settings (enabling zRAM, enabling the shared kernel paging option etc), but to no noticeable effect. The only performance tweak I make to all the ROMs is to overclock the CPU to 1.5GHz...other than that, I just use the ROM.
Is this just an expected side effect of using 4+ ROMs on such an old phone? Or are people able to get super-smooth, never-frustrating, always-responsive performance with these ROMs by tweaking/changing stuff etc? Any thoughts?
Amr
I haven't experienced any problems using CodefireX. Did you make sure to fully wipe everything when you reinstalled the ROM?
Quarsar said:
I haven't experienced any problems using CodefireX. Did you make sure to fully wipe everything when you reinstalled the ROM?
Click to expand...
Click to collapse
Thanks for the CodefireX suggestion - I'm downloading it now. And yes, I always do a full wipe before installing a ROM.
Some users have reported auto rotation issues with just flashing the stable releases..currently there are two options I know of. One is to download a stock ROM than dirty flash a jb rom soon after..the directions I gave you for that one are probably out of sync. Than there's another option such as flashing codefire nightly than dirty flash the latest codefire stable release. I flashed nightly 20130219 than dirty flashed the latest stable release and auto rotation works for me. What surprised me the most is I came from a low end smartphone. That being a LG optimus one and even that had a cm10 ROM but I never messed with it so I'm not sure if it had the same problems as the ones I flash now on my I4G. Than again that LG only had 512 mb of memory
Sent from my Desire HD using xda premium
If you want more ram and you don't need many programs to be working in the background you can just set max backgr processes to 4 in dev options
Sent from my HTC Desire HD using Music Player
Hey guys how are you doing?
I don't know if this is supposed to be normal but my Nexus is becoming really slow. I've compared it with my father's Samsung Galaxy Gio (yes, that damn piece of brick) running a port of CM10 called Xperia Jelly Bean with an overclock to 1GHz (without messing with the low freqs) and my Nexus running CM11 was slower in terms of opening the SMS app, the contacts, the settings and so on.
I've tried everything, wiping every partition in the phone and installing many roms (CM12, fresh's AOSP Lollipop, CM11, Vanir, LiquidSmooth, CarbonRom, SlimRom, etc) and I even tried different kernels (DirtyV, Fancy and Franco for KK roms and BSmitty's kernel for L) but my perfomance goes from bad to even worse.
Most roms come with many apps I don't use like apollo, stock camera, stock messaging, aosp email app, lancher3 or trebuchet (I like google now but I tested not changing the launcher and it's about the same performance) and the default browser app, so I usually delete them with titanium backup.
I heard some weird sounds when I was with lollipop roms that worried me since I've never heard those sounds (looked like something tiny blowing up) so I am a little worried that those things caused some hardware to start malfunctioning or even stopped working. I am also having now troube with flashing a rom and it being stable. I usually wipe all the partitions, install ROM then Gapps (the most minimal ones) and then Kernel, wipe Cache again, reboot. Set everything (Gmail account and custom rom things like notification bar, locksreen, etc), reinstall the apps I need from google play, change to ART if needed/avaiable and go on. But sometime later the phone starts freezing and ends up turning off and when it turns on it stucks on the boot so I need to reinstall the rom.
What am I doing wrong? What can cause my device to behave like this? Is it a likely end of my device? I am worried and have little knowledge xd. Should I flash a stock rom? Which version is the more appropriate? What do you recommend for custom ROM, am I flashing them and applying everything alright?
EDIT: I forgot to mention that I did some benchmark tests and it does well as espected. Goes up to 20K with Lollipop, 15K with KitKat (1.5GHz) and 13-14K with KitKat (1.2GHz). I've tested it in FML 5.0.2 (last build) + Bsmitty kernel (about 2 weeks ago) and the KK ones I did yesterday with CM11 and fancy r60. The problem here is the menus that are freezing constantly and the basic apps that take too much time to load when compared to the time I bought it (I'm talking about Settings, Camera, Messaging, Dialer, Contacts, etc)
I feel the same way about my phone too! Btw, is installing new app on your phone slow? My phone takes about 15-20 secs to install an app.
I am by no means an expert, but the "weird sounds / stability of ROM flashing / constant freezing" that you're reporting, regardless of the ROMs that you're using, it sounds like your device may be on its last legs. How long have you had the device? Is it possible that some of your hardware components are failing?
In my own Gnex experience, I was using CM11 Snapshot ROMs for about a year. About 6 months after installing CM11, I started noticing massive slowdown and lagging. Similar to what you reported: slow launching of apps (even simple ones like the default SMS Messaging and Camera), freezing/crashing in Gmail and Chrome, very slow multitasking/tab/app switching, etc.
Google officially stopped supporting the Gnex at 4.3 so I would recommend that you try returning to the 4.3 Stock Nexus Image, and see if that improves your stability. I did that for my Gnex and installed the Xposed framework on top, and I've been happy with the results. I no longer use my Gnex as my daily phone so I can't speak to longer-term usage, but you may want to try this first before writing the device off entirely.
Well, after some time I finnaly put my phone working nicely again
I flashed and tried over and over again many combinations of rom, gapps and kernel until my phone worked nicely with something. I am with CM11 + PA Stock Gapps (with gapps-config.txt written of my own to avoid installing things I consider bloat) + Fancy Kernel (everything in their respective last versions).
Well, just an advice from me to anyone who starts having problems like me. If you are flashing much and testing many roms per day and your phone starts getting slow and not booting like it should boot (and having weird sounds) just stop for a while. Find a stable rom+kernel combination and let the phone work like that for some time. Then when you think you are ok, start flashing to your content again