[Q] Problem with music playback on CM7 Stable - Nook Color General

Before I ask my question, I just want to let everyone know that I have searched and searched and searched for the answer to this before posting. Please don't be a troll unless you have a link that helps me. There are thousands upon thousands of pages and unfortunately xda's search function leaves a lot to be desired.
Now, here is my setup:
emmc CM7
Kernel OC'd to 1.1 ghz
DSP equalizer enabled
MortPlayer Music
What I get is a fairly regular skip/pop whenever I play any song from my music collection (mp3/m4a, mostly). Sometimes it will go almost a whole song without skipping but very rarely. From my research I do know that this WAS an issue with CM7 pre-stable release, but now there seems to be no discussion about it. It's not listed in known issues as far as I can tell so I thought this issue was no longer, well, an issue.
Here's all the things I've tried to get the music to work.
1. I dropped the kernel down to 800 mhz, thinking it may be an issue of my Nook not handling the OC'd kernel. Same result.
2. Flashed back to CM7 stock kernel. Same result.
3. Changed music players (stock, Meridian, cubed). Same result.
4. Made sure the files were not corrupted by copying the files to my phone (EVO Shift) and playing them. They play perfectly on my phone.
5. Disabled DSP thinking perhaps I had the level set too high and it was peaking. Same result.
6. Moved music from external storage (sdcard) to internal storage (emmc/My Files/Music) thinking that my class 6 card wasn't being read properly. Seemed to fix it for the first song or two, then same result.
7. Flashed phiremod 4/13 version, which again, seemed to help at first, then I got the same result.
8. Added (then removed) Auto Killer Memory Optimizer thinking that perhaps memory was getting low while I was playing music. Removed it thinking that maybe it was constantly trying to kill the Music app. Same result with or without AKMO.
9. Disabled the keep home in memory option in CM Settings thinking it was straining the system. Same result.
10. Dropped performance settings in Launcher Pro thinking the same thing as #9. Same result.
11. Switched launchers. Cm Version ADW, ADW EX, LP, Launcher7, Zeam, the launcher I use makes absolutely no difference.
I'm sure I've tried a few other things that I can't think of, but that is about it. What bugs me about it is that even if I'm not doing anything else on it, i.e., I just let it set and play music, it still skips. Even if I'm not performing other tasks such as surfing the web or playing a game. The other strange thing is that youtube and even flash video in the browser work flawlessly, so I really don't understand what the problem could be. I do know that a while back when the video issues were being ironed out, DSP was broken, but I thought that was fixed by rc4. Flash would presumably take up WAY more resources than the music player, why don't I have any problems with it? Would it be a problem with the audio codecs for mp3/m4a?
I'm really stumped here guys. My hours of searching have proved fruitless, so hopefully someone will have the elusive link I'm looking for. Thanks in advance for any help I receive.

I have the same problem. Anyone found a solution for this?
Sent from my DROID2 using XDA App

Next nightly should mostly fix the problem.

Thank you dalingrin. I'll make sure to check it out. You and the other devs here are doing a great job. I'll be sure to donate the next time I get paid.
Sent from my PG06100 using Tapatalk

If you don't want to wait the DEV Kernel topic has a ALSA update as well as an experimental 4/13A kernel that together fix this problem. As well as give you quandrant scores close to 2500! =D

Sorry to ask this, but I've been poking around the forums here and over @ the CM site itself and I have not been able to find the thread with this kernel. Could some kind soul take pity on me and point me in the right direction?
Many thanks!

Yeah the 4/13a kernel was one of the things I tried but forgot to mention. Its a little better but the issue remains. I'll wait til the next nightly thanks for the input guys.
And you can find the 4/13a download in the test build folder linked in dalingrin's oc kernel thread.

tambourineman86 said:
Yeah the 4/13a kernel was one of the things I tried but forgot to mention. Its a little better but the issue remains. I'll wait til the next nightly thanks for the input guys.
And you can find the 4/13a download in the test build folder linked in dalingrin's oc kernel thread.
Click to expand...
Click to collapse
Then you did not install it with the ALSA update...
Kernel Thread
4/13A Test Kernel
Alsa Update - This fixes your issue, even with stock kernel. But works best with 4/13A for extra performance.

Yes I missed that. Thank you sooo much!
EDIT: That fixed it. Again thanks. I hate when I miss something small like that.
Sent from my NookColor using Tapatalk

Thanks for the fix! Just applied it and 4 songs in....the "snap, crackle, pop" is gone. Happy camper here. Also thanks to the OP for bringing this up in such a thorough way, surprised I had not heard of anyone else having this issue.

Dsp manager
I've noticed for a while now since Nightly 27ish, maybe prior, that my DSP manager doesnt work correctly. To modify the settings through my headset, I actually have to modify the Phone Speaker settings.
Is this a known issue, or am I missing something?
Not sure this is the correct thread, but any input would be helpful.

Hitting this again on CM-7.1.0-stable
First off, this is by far the best and most thorough description of the music playback problem that I keep running into, so kudos and thanks to the OP!
But sadly, I upgraded to CM-7.1.0 stable and this is still happening. I see the mention of installing dalingrin's update-alsa-041411.zip, but I can't find that anywhere.
I'm also surprised that this problem is still present in CM 7.1.0 stable. Does anyone know what the new solution for this problem is?

Related

[Q] Some questions about CM7

Hi all,
With CM7 i'm enjoying my Milestone like never before. But since it's my first custom ROM, i have some questions though.
1. When returning to the home screen, 9 out of 10 times it reloads and rebuilds completely. How can i avoid this?
2. If it's a memory issue and i want to keep it in memory, how can i accomplish this without the risk of losing other essential apps from memory, like SMS and phone?
3. I read something about priorities for apps, how does this work?
4. Sometimes my device reboots randomly. My CPU is set to 900. Can this be the cause? If so, what's the best CPU speed setting?
So far for now, but i guess i'll be back with some more ;-)
Thanks in advance,
Gerard
The Netherlands
I'm no expert so someone please correct me if i'm wrong and sorry for all spelling errors.
What version of CM7 are you running? If u'r running RC3 0.08-11.03.16 that homescreen Redraw (problem number 1) should be minor, something like 1 out of 10 times, atleast on my milestone. There is "Keep home in memory" setting in Cyanogenmod settings -> Performance, make sure it's enabled and for the problem number 2 enable "Keep SMS in memory". You shouldn't care much about app priorities cause CM7 memory management is taking care of that pretty well. Random reboot are DSI errors, they are minor in the newest CM7 version but there is no failsafe way to avoid them, if you don't want to chance the kernel, you can read about that in CM7 for milestone thread.
Thanks, i just can't find the "keep SMS in memory" option?
Then you probably won't have the newest version of CM7. You can find it here http://forum.xda-developers.com/showthread.php?t=941346 and flash it just like u flashed it at the first time. Just wipe cache and dalvik cache from open recovery and you will get to keep all your personal settings and files/apps.
That's the one i have and i already found it. But thanks again!
twixyz said:
Hi all,
With CM7 i'm enjoying my Milestone like never before. But since it's my first custom ROM, i have some questions though.
1. When returning to the home screen, 9 out of 10 times it reloads and rebuilds completely. How can i avoid this?
2. If it's a memory issue and i want to keep it in memory, how can i accomplish this without the risk of losing other essential apps from memory, like SMS and phone?
3. I read something about priorities for apps, how does this work?
4. Sometimes my device reboots randomly. My CPU is set to 900. Can this be the cause? If so, what's the best CPU speed setting?
So far for now, but i guess i'll be back with some more ;-)
Thanks in advance,
Gerard
The Netherlands
Click to expand...
Click to collapse
A few answers of my own:
1) The CPU speed is probably NOT the cause of your reboots, but if you want to be sure, try it for a week. 700 is safer, 550 is default.
2) If it is your CPU overclocking, you may be able to fix it by upping the voltage on your overclock. This will lead to a bit more heat and a bit more battery drain, but should fix the reboots if CPU related
3) I would look at the SUPERCHARGE your Milestone thread about memory management settings. Although Zepps's settings and scripts are meant for tweakers and are probably a tad aggressive if you don't know what you are doing, they did speed up my phone by 200%.
I would recommend installing AutoMemoryManager and using the mild settings if you want to do something less aggressive than the Supercharge scripts...
You will get some of the benefits of the supercharge and a very low risk of apps getting killed by the memory manager.
My 2 cents!
thanks caz.
I'm pretty sure the new minfree settings that I've been testing out are the best of both worlds... superfast and background friendly.
I hadnt had a chance to update the thread yet and post the new script.
But for those interested, this should really work great... 6, 8, 24, 26, 28, 30.
Thanks all, i'll look into those things. By reading that is, because i've got a lot to learn!
Hi all,
I'm still experimenting and impressed by this ROM. Just now I performed a fix permissions to prevent apps from fc. That modified the read & write permissions of all apps. I assumed it couldn't hurt to try, but now I'm wondering what it did exactly. There aren't any noticable changes. Can anyone fill me in?
Thanks,
Gerard
Do you think that is better than FroyoMod??
Lapiduss said:
Do you think that is better than FroyoMod??
Click to expand...
Click to collapse
I'm not sure what you mean, but this is my first custom ROM coming from stock Eclair on my first Android device.
So I have no idea which is the best, but I do know that I'm very impressed by CM7. It runs perfectly on my Milestone, so I feel no need whatsoever to try another.
Yup, for sure
twixyz said:
I'm not sure what you mean, but this is my first custom ROM coming from stock Eclair on my first Android device.
So I have no idea which is the best, but I do know that I'm very impressed by CM7. It runs perfectly on my Milestone, so I feel no need whatsoever to try another.
Click to expand...
Click to collapse
Can you tell me if the camera & video work well?
My 2 bigs problem with froyomod are the camera that often FC and freeze and the video that are stuttering so much..
I can move to CM7 only if I'm sure that this stuff work well!
Lapiduss said:
Can you tell me if the camera & video work well?
My 2 bigs problem with froyomod are the camera that often FC and freeze and the video that are stuttering so much..
I can move to CM7 only if I'm sure that this stuff work well!
Click to expand...
Click to collapse
I can only speak for myself, but I haven't had one single problem so far. Shooting pictures and videos works fluently on my device. I am also not aware of any possible known problems, but maybe others can confirm this.
ADW Launcher in CM7 RC4.1
Started new thread for a specific question, but i can't delete this post.

[CM7][BETA 1] CyanogenMod 7 With Tablet Tweaks Beta 1

Update 16/04/11
New build Up folks
changelog:
rebuilt kernel with upto 1.4ghz overclock ability, (thanks to pershoot and others on xda for the base code)
still has sleep bug, i am getting the updated kernel edits fixing this from ni soon
get setcpu 2.1.1a from xda devs then choose the SET SPEEDs device option (scroll all the way down the device list and its the bottom option)
performance on this build is absolutely insane - 3000+ quadrants 50+ in linpack.
link: http://mirror2.streakdroid.com/adam/NI/update.zip
Update 12/04/11
New build based directly off of up to date (as of today) cm7 Final Source
changes:
HDMI Partially working (sound seems to not transfer over)
New kernel build finally worked, cifs, tun, usb mounting built in
camera pics are not in crappy colors any more but the preview is rotated 90 degrees for some reason
performance seems better but that could be placebo.
link: http://mirror2.streakdroid.com/adam/cm7-adam.zip
Update 09/04/11
will be uploading a slightly edited zip shortly that adds MrGuys PixelQi toggle app and a few other minor edits
link is the same as for last nights update.
google apps zip linked below is also now fixed and works on adam
Update 08/04/11
Fixed browser and webkit related force closes. Removed google apps.. You will need to install these yourself
camera also working now.
flash 10.2 confirmed working also
New link: http://mirror2.streakdroid.com/adam/cm7-adam.zip
Latest google apps update fixed to work on adam are at http://mirror2.streakdroid.com/adam/gapps.zip
Again please report issues folks
-------
ok folks i thought id post up my CM7 build, this one is based off the work done over in this thread on xda, and works brilliantly on adam, but has a few issues which ive listed below
Things Not Working:
Stock Android Browser (removed from build and re
Camera
USB Storage mounting
download link: http://mirror2.streakdroid.com/cm7-adam.zip
please report other issues and general thoughts on the rom.
Downloading and flashing now! thanks allready!
it works? I tried to get it working the other day and couldn't. either way thank you very very much!!!
same here, great work!
Thanks, giving it a try now
Wow,
Installing as we speak.
I will get back on this...
Well it's running fine for now Great work
MArket is broken, but as you stated it's a beta, maybe you could team up with other adam developers (josh ) to make this one beast of a CM7
Greetz,
couldn't get it to work properly..
First bootloop, then when it booted everything FC'ed..
After another reboot and wipe I could't get past the touch android to begin screen..
Very strange..
I got it booted...
Can't get the market to work though. A good start but needs work before it'd be a daily driver for me. I'll probably go back to vegan soon.
this is sweet, going to try this tomorrow =)
hi thx for your input in our life with Adam
It booted for me after wiping data and cash
First it seemed to be bit glichy and slow with response...
the design with Honey comb like bar is very nice
but WiFi could not connect to my router and i try and try and try and try
and reboot and try
and change permissions on router and try
and no go for me
as for included aps Terminal emulation FC. on me
hym
Looking forward for next version
Now back on Beast
regards
Just installed to take a look. Nice to see cm7 on the Adam. Got wifi going unlike others, but most applications would fc.
Thanks for starting this project.
Sent from my Adam LCD 3G using XDA App
Thanks a lot DJ_Steve.
Installed it on my PQi Wifi Adam and here are updates so far. ( Wiped data )
1. Firefox FC but installing it from SD card again and its working fine now
2. Market FC. Tried the Market trick ( clearing data on service, fc market and reboot) but didn't work
3. Installed Titanium backup from SD card apk. Works fine
4. Used Ti Backup to restore some apps like thumb keyboard and they work fine
5. Installed Dolphin Browser HD but it starts in portrait mode and I cannot click accept button.
6. I got a prompt on first boot to install some apps like facebook, gmail etc but they all failed with a FC on market.
So far the ROM runs really fast and working great. I need dig the PQi toggle app and install. I like the HC look and the smoothness of the ROM.
Kudos .. and Thanks ..
Will post after more testing.
Have you talk with mad-murdock about the changes you made to make it work? It would be best to get this included with the official builds.
That said, god job on this. Similar issues to arvi007 so far. Firefox and Market FC. Terminal Emulator causes a reboot. Red LED on the side of the Adam is on all of the time.
I'll keep playing and see what else I can come up with.
Crud, not long after I said this I rebooted and it died. Had to NVFlash to get it back.
Not seen most of those issues here. But their is bugs. Ill see if I cant build from source at a point soon
Sent from my Dell Streak using Tapatalk
DJ_Steve said:
Not seen most of those issues here. But their is bugs. Ill see if I cant build from source at a point soon
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
Yeah, getting quite a few Force Closes.
Fruit Ninja THD for example closes due to Webkit problems, you said you removed the stock browser, so these probably go hand in hand.
Dolphin HD also crashes for an unknown reason.
Feel free to add in my Pixel Qi toggler app if you like, (MrGuy here)
www(dot)megaupload(dot)com/?d=EY1OGQGZ
Newbie filter
Yea webkit seems screwed up. going to try a stock cm7 build next to see if it works their them add the tablet tweaks back
Sent from my Dell Streak using Tapatalk
Great start, will definitely be following this, would be great to get a stable CM7 build on the Adam
Mostly Working
I have a PQ+Wifi adam and i got CM7 working using this build but when I did a shut down power off and try to power on again the device never boots. I have to debrick it. Otherwise besides the browser/Camera issues and a FC in gmail when opening a message with an attachment it was a great start towards a fully functional CM build
Edit:
Fixed the reboot problem by not using Clockwork Recovery. I wonder if this is related to the issue CW /CM has on the G2 were when you power it off it goes to recovery instead of completely turning off.
I somehow got the market working. However, Firefox does not work.
Being CM7 is there CIFS and TUN support? I really need something to let me access windows shares from my corporate network over VPN.
I should have tried it before I went back to Beast and got all comfy
Looking forward to using this, but will wait till the bugs get worked out. Enjoying Beast at the moment.

[Q] Built a custom AOSP ROM, sound + video does not work

Hi All,
I wanted to learn how to build an AOSP ROM for my Droid Incredible (original version), and I was finally able to get a working build today (i've been at it for more than a month on and off when I have time).
I downloaded gingerbread-release and used the CM overlay to get the vendor-specific stuff. The proprietary files were pulled from my working OMGB phone (which I understand borrows a lot from cyanogen; well-- the kernel at least).
My problem is that (1) I can't get any audio to play, (2) any time I try to play a video (like Youtube) I get a force close, and (3) the camera wont work.
I'm pretty sure (3) is a totally different problem, as I've seen lots of ROMs where the camera won't work.
Does anyone have any point that I could start on this? I've posted my logcat here: pastebin.com/GPqpD8N3
(sorry-- I'm not allowed to post links yet.)
I googled it but I'm having trouble finding anything pertinent.
Thanks in advance for any assistance you anyone can provide!!
EDIT: By the way, since this post I have changed my setup. All of my proprietary modules are from the CM nightly build now, instead of having modules from OMGB and and overlay from CM. I did this to make it more consistent in case I run in to any more problems.
Sorry -- additional detail that I meant to add in the post (but it won't let me re-edit for 5 minutes):
The bottom of the log shows me trying to play a song in the music player. From what I can tell, /system/bin/mediaserver is crashing and performing a stack dump; however I don't know why or how I can fix it.
It will not play any ringtones either, but the DTMF tones *do* sound when you press on the digits, and the phone/speakerphone work fine as well.
I just figured it out myself... in the logcat there is the line:
frameworks/base/media/libstagefright/omx/OMXMaster.cpp:90 err != OMX_ErrorNoMore
if you go to that file, in line 90:
CHECK_EQ(err, OMX_ErrorNoMore);
I just commented it out and sound works fine.
Now if I can get the camera working... any ideas?
Hmm I know the bugglas beast nightly's had the camera issue.
Sent from my ADR6300 using XDA App
Thanks, @Kiboe for the reply. I found the fix last night (right after I posted ) on xda-developers through Google Groups.
I implemented @dferreira's suggestion, and it compiled just fine. Now I have a working camera, but video still isn't working. (Also accelerometer isn't working, but I believe I have already found the answer for that).

[KANG] [CM 10.1] tilal6991's CM 10.1 Kangs [4.2.2] [XPERIA T]

So due to the recent nightlies having quite a few issues but me being unable to fix them officially, here's a final 10.1 build from myself. Honestly, you should be on a 4.3 based ROM though
Download link (feel free to mirror if Goo is slow):
26/09 - http://goo.im/devs/tilal6991/roms/mint/cm-10.1/cm-10.1-20130926-UNOFFICIAL-mint.zip
Thanks:
FXP/CM teams - as always
Reserved.
Good work
How did you find out that it is a toolchain issue? Is this problem escalated to someone who might have influence in tracking it down?
Maybe these "some reboots" left has the same cause - only happening more rarely, for example because of optimization level etc. You might confuse people with accusation of that type without a proof.
adiq_ambro said:
How did you find out that it is a toolchain issue? Is this problem escalated to someone who might have influence in tracking it down?
Maybe these "some reboots" left has the same cause - only happening more rarely, for example because of optimization level etc. You might confuse people with accusation of that type without a proof.
Click to expand...
Click to collapse
Note that I don't outrightly say that it IS a toolchain issue. It is what I suspect because I have set up the CM sources in exactly the same way as the buildserver. If the number of reboots is reduced on my build and the sources are exactly the same then it stands to reason that it is a difference in the way the system itself is set up.
I SUSPECT a toolchain issue because the reboots are kernel panics and they are difficult to create except with differences in the compiler itself.
I do agree that optimization level could be an issue but find it hard to believe since the optimization level is set in the source itself and as I say, my sources are the same as upstream.
is it 10.1.2 then?
l.capriotti said:
is it 10.1.2 then?
Click to expand...
Click to collapse
Past 10.1.2. It's equivelent to the current nightly build.
Smart move. And thanks!
For me it suffers from the "Can't play this video" bug.
I had CM 10.1.2 official stable before, that one plays video correctly.
Many thanks to tilal6991 for the time and effort he's spending in order all of us can have a great working version of CM10.1 on our Xperia T's.
I'm going to try this kang and see what happens with the random reboots!
l.capriotti said:
For me it suffers from the "Can't play this video" bug.
I had CM 10.1.2 official stable before, that one plays video correctly.
Click to expand...
Click to collapse
Oh? 10.1.2 works? That's interesting.
For a temporary workaround: install MX player and use it to play videos.
thanks tilal hope this well help in investigating and hopefully fixing the reboot problem so i can at last buy this phone
Thank you for your job tilal! I have tried again but I got three reboots in half an hour first when I wanted to enter to the settings menu, second át the theme chooser, third at starting camera app. There are the tipical reboots point in cm rom according to my experince.
daruma said:
Thank you for your job tilal! I have tried again but I got three reboots in half an hour first when I wanted to enter to the settings menu, second át the theme chooser, third at starting camera app. There are the tipical reboots point in cm rom according to my experince.
Click to expand...
Click to collapse
That's insane and totally contradictory to my experience :/ I use the settings app and the camera all the time and as I said once a week is typical for me. Theme chooser is an interesting one. I'll see if I can force reboots there.
tilal6991 said:
That's insane and totally contradictory to my experience :/ I use the settings app and the camera all the time and as I said once a week is typical for me. Theme chooser is an interesting one. I'll see if I can force reboots there.
Click to expand...
Click to collapse
To make this more insane.... The nightly is pretty stable for me actually. It reboots most of the time when playing music using a BT headset (Google Music / Apollo).
I am playing Ingress, so the phone is really on a lot of time (screen on about 1.5 hours non stop and connected to an external battery) and i get 2 max 4 reboots a week. With the exception when playing music, then i get reboots every few minutes
I have not seen any improvements with your kang (and also not with my own kang).
Verstuurd van mijn TF300T met Tapatalk
Have your kang running since last night and had at least five reboots since then. Often related to the camera (both from the lock screen and from the separate application). Another one while fiddling with Facebook, and one that I cannot exactly recall... I have been able to take a number of photographs without reboots
Can of course start collecting logs if that's helpful.
Thank Rob
Yeah logs might be useful although I'm sure I know what I'm going to see in them.
Mirror
Here is a mirror for anyone who may need it. It is on androidfilesharing.com
http://androidfilesharing.com/sharing1/data/public/71033b.php
Tilal6991, I have pm'd you log on info so if you choose, can log in, upload more ROMS/mods and keep track of your download stats on shared files.
Thanks
Hi
Iam flash you rom to my T ...
Only one restart if iam go to in theme settings.
Iam have more restart in original CM if iam use GPS and navigation, but if iam use your rom, GPS and navigation works fine without restart...
Thank you
Sorry for my bad english ...
Odesláno z mého Xperia T pomocí Tapatalk 2
So I have to say.. Nice rom, more stable than original one but... I still have tons of reboots yesterday.. I have been on tour yesterday and took around 300 photos, was hardly using my phone for 4 hours and I can clearly say.. Small chance of reboot when opening camera app, very small when taking a photo, had few reboots with some camera apps too but it's better then official later Nightlies or stable one... No reboots with any others applications yet, just with snapseed once ( reboots while trying to edit picture in official builds are common).. So ahm anyway it's way better, thank u for ur work sir
Sent from my Xperia T using Tapatalk 4 Beta

[Q] I9000 memory problems

Hello everyone! I've been following this website for a while and have been using HellyBean on my device.
I'm using the most recent version, 27/09 and I am sad with the RAM problems I'm having. Simple things like writing a SMS can be a nightmare at times because the keyboard goes away and it does not appear again! Using the AOSP browser it closes a lot and the wifi icon goes gray constantly.
I've tried to do a clean install twice but this happens every time. Has anyone been having these problems or is it only me? Anyone knows how I can fix it?
Thanks in advance!
After a reboot how many free RAM do you have? Have you installed apps like whatsapp, skype etc. they need huge mem ...especially the Gapps ...and our device only have 512MB RAM less reserved for the Kernel to be used by some drivers (video, capture, JPG) for DMA (Direct Memory Access)
What kernel uses HellyBean in Stock? Maybe try Sema-Kernel with BigMEM-Libs gives you up to 409MB RAM available for the Android System, but breaking the video recording in 720p, maybe it could help ...
timeforagame said:
Hello everyone! I've been following this website for a while and have been using HellyBean on my device.
I'm using the most recent version, 27/09 and I am sad with the RAM problems I'm having. Simple things like writing a SMS can be a nightmare at times because the keyboard goes away and it does not appear again! Using the AOSP browser it closes a lot and the wifi icon goes gray constantly.
I've tried to do a clean install twice but this happens every time. Has anyone been having these problems or is it only me? Anyone knows how I can fix it?
Thanks in advance!
Click to expand...
Click to collapse
freakymod2120 said:
After a reboot how many free RAM do you have? Have you installed apps like whatsapp, skype etc. they need huge mem ...especially the Gapps ...and our device only have 512MB RAM less reserved for the Kernel to be used by some drivers (video, capture, JPG) for DMA (Direct Memory Access)
What kernel uses HellyBean in Stock? Maybe try Sema-Kernel with BigMEM-Libs gives you up to 409MB RAM available for the Android System, but breaking the video recording in 720p, maybe it could help ...
Click to expand...
Click to collapse
After a reboot, the device reports 134 MB free. There are a lot of apps running and changing the RAM at the beginning but it stabilizes at around 130 MB and 120 MB. Here everything seems ok. I had some heavy apps, facebook, facebook messenger, skype (installed but not actually running, stopped using it) and firefox. Firefox was the only app I had trouble before but it is normal for it. Maybe Gapps but I find it strange to happen only now.
HellyBean uses the Devil Kernel by default. I used the option that gave me slightly more memory than default but still with access to the 720p recording. I changed to Semaphore Kernel to try and see if the same happened. Installed the slim version and it still happened. I now have the normal version because videos didn't work, I don't know why. I'll try the Devil Kernel again with the extreme memory option. I'll have no camera but let's see what happens. I'm not expecting miracles though. If it worked once with the normal amount of memory it should still work now...
EDIT: By the way, to clarify, facebook, facebook messenger and skype are not on my device anymore. firefox still is.
Experimenting now with the Devil Kernel with the Maximum RAM option (439 MB w/out camera)
Hmhh okay ,maybe you can test your origin HellyBean later ( without using facebook and so on ),and see what happened..
For Testing i i think the devil kernel with maximum RAM option is good, but i think you need the camera, so it is no option for daily use, or what do you think ...
As is said there are many apps which consumed much of ram and so android has to restart different apps often ...
Our device only has 512MB RAM...is it the latest helly bean version based on android 4.3 ???
But when you have tested hellybean with stock kernel AND Sema-Kernel and it still happened, could it be a bug in hellybean? Did you a clean installation ???
timeforagame said:
After a reboot, the device reports 134 MB free. There are a lot of apps running and changing the RAM at the beginning but it stabilizes at around 130 MB and 120 MB. Here everything seems ok. I had some heavy apps, facebook, facebook messenger, skype (installed but not actually running, stopped using it) and firefox. Firefox was the only app I had trouble before but it is normal for it. Maybe Gapps but I find it strange to happen only now.
HellyBean uses the Devil Kernel by default. I used the option that gave me slightly more memory than default but still with access to the 720p recording. I changed to Semaphore Kernel to try and see if the same happened. Installed the slim version and it still happened. I now have the normal version because videos didn't work, I don't know why. I'll try the Devil Kernel again with the extreme memory option. I'll have no camera but let's see what happens. I'm not expecting miracles though. If it worked once with the normal amount of memory it should still work now...
EDIT: By the way, to clarify, facebook, facebook messenger and skype are not on my device anymore. firefox still is.
Experimenting now with the Devil Kernel with the Maximum RAM option (439 MB w/out camera)
Click to expand...
Click to collapse
freakymod2120 said:
Hmhh okay ,maybe you can test your origin HellyBean later ( without using facebook and so on ),and see what happened..
For Testing i i think the devil kernel with maximum RAM option is good, but i think you need the camera, so it is no option for daily use, or what do you think ...
As is said there are many apps which consumed much of ram and so android has to restart different apps often ...
Our device only has 512MB RAM...is it the latest helly bean version based on android 4.3 ???
But when you have tested hellybean with stock kernel AND Sema-Kernel and it still happened, could it be a bug in hellybean? Did you a clean installation ???
Click to expand...
Click to collapse
Testing with Devil Kernel now with the maximum RAM option (439MB). It has no facebook, facebook messenger and the skype app is unninstalled now as well. So far so good! I've actually managed to use Firefox and write a message in a floating window with no problems at all. I've been going at it for a while now, testing Firefox, the AOSP browser, playing games, sending SMS, updating stuff, everything works fine. Except now for the camera. While I don't normally use it I don't like it disabled. Just for testing right now.
I found a screenshot I took, the phone reported only 17MB free and 379MB used. Calculator says it was only 103,6MB, unless something else escapes me, and facebook was restarting and poweramp and voodoo sound were battling to stay running since I was trying to listen to music. I thought it might be some kind of memory leak or something since it did somekind of soft-reboot (shows boot screen but doesn't ask for pin code) and everything was fine for a little while...
I don't think there are anymore heavy apps running on my phone. It's too bad the phone is considered almost ancient now but I'll have to deal with it for now. No money for a new one so cool as this one!
HellyBean is now based on 4.3 for most of it's compatible devices. It includes the GT-i9000 I use.
I first did a dirty flash on a new version. But that started the problems so I did a clean flash ( lots of wipes since I screwed up the kernel during install ) twice and it still happened even with a more recent version. Visiting the thread doesn't seem to show much regarding this problem. I can't post there yet or I would ask them first since it's the same ROM. They are only talking about SWAP and I don't use it. So it doesn't seem like a HellyBean bug. I thought also maybe it was a CM bug since HellyBean is based on it... But I would probably find more people in my situation if it was like that. I would like not to downgrade to the last version I had no problems with since I like a feature that came with the new version (deactivated because it could be that feature was a problematic one) but if this lasts I'll do that.
Thanks for your suggestions!
EDIT: It seems to be fixed! Don't ask me how... I didn't want to get the DevilKernel from the site since I already had it on the device but I had to install the last version again which I used to test the maximum RAM option I talked about. Since I had no problem I started decreasing the RAM amount until I got to the default option. And everything is working fine! I really don't get it why a dirty reflash fixed that a clean install did not. Sad because I couldn't figure out what was happening... But it's normal again... Lucky me, I guess? Anyway, thanks for your time trying to help me! I appreciate it!
No Problem therefore it is a forum !!! And it is great that i could help, or not in your case
It is strange, but the main thing is ,it works...however ...
Thanks for reporting!!!
timeforagame said:
Testing with Devil Kernel now with the maximum RAM option (439MB). It has no facebook, facebook messenger and the skype app is unninstalled now as well. So far so good! I've actually managed to use Firefox and write a message in a floating window with no problems at all. I've been going at it for a while now, testing Firefox, the AOSP browser, playing games, sending SMS, updating stuff, everything works fine. Except now for the camera. While I don't normally use it I don't like it disabled. Just for testing right now.
I found a screenshot I took, the phone reported only 17MB free and 379MB used. Calculator says it was only 103,6MB, unless something else escapes me, and facebook was restarting and poweramp and voodoo sound were battling to stay running since I was trying to listen to music. I thought it might be some kind of memory leak or something since it did somekind of soft-reboot (shows boot screen but doesn't ask for pin code) and everything was fine for a little while...
I don't think there are anymore heavy apps running on my phone. It's too bad the phone is considered almost ancient now but I'll have to deal with it for now. No money for a new one so cool as this one!
HellyBean is now based on 4.3 for most of it's compatible devices. It includes the GT-i9000 I use.
I first did a dirty flash on a new version. But that started the problems so I did a clean flash ( lots of wipes since I screwed up the kernel during install ) twice and it still happened even with a more recent version. Visiting the thread doesn't seem to show much regarding this problem. I can't post there yet or I would ask them first since it's the same ROM. They are only talking about SWAP and I don't use it. So it doesn't seem like a HellyBean bug. I thought also maybe it was a CM bug since HellyBean is based on it... But I would probably find more people in my situation if it was like that. I would like not to downgrade to the last version I had no problems with since I like a feature that came with the new version (deactivated because it could be that feature was a problematic one) but if this lasts I'll do that.
Thanks for your suggestions!
EDIT: It seems to be fixed! Don't ask me how... I didn't want to get the DevilKernel from the site since I already had it on the device but I had to install the last version again which I used to test the maximum RAM option I talked about. Since I had no problem I started decreasing the RAM amount until I got to the default option. And everything is working fine! I really don't get it why a dirty reflash fixed that a clean install did not. Sad because I couldn't figure out what was happening... But it's normal again... Lucky me, I guess? Anyway, thanks for your time trying to help me! I appreciate it!
Click to expand...
Click to collapse

Categories

Resources