Database Develop

Streamfurious update-now fills memory

After running Streamfurious for a few hours today my internal memory is totally full, and Apps manager doesn't have a a "clear cache" option for this app.
I'm using CM 3.6.8.1, with apps to SD. This never happened before this update.
Is there a way to clear out the memory using the Terminal app?
Thanks.

Streamfurious memory issues
I have been happily running StreamFurious Pro on my G1 for several months, with almost no problems. However, in the past couple weeks Streamfurious has been very flaky. It just quits after a few minutes. If I try to restart it more than 2 or 3 times, it crashes. I keep getting low memory messages from the G1. When I review the applications, Streamfurious takes up more than 128 MB! The next closest is about 2.3 MB. Usually the cache is around 25MB. Clearing it does not seem to help at all.
If I don't hear anything or get an update, i looks like I will have to give up on Streamfurious, which is really too bad because it has been a very reliable workhorse up until this month. If this problem is resolved I will post the news.

I saw the same memory-filling behavior a few days ago. It was soon after receiving an update for the free version of StreamFurious. I think this update was a mistake by the dev, since it had the advanced features I assume came from the full pay version. When it ate all my internal memory, I deleted the app and then re-installed from the Market. It was fine after that, though not long after this, the dev posted another update that took away the pay features again. It's been fairly stable since, though maybe a bit more prone to dropping active streams.

I was using the pro version, but it recently stopped working correctly. Is there a way to install an older version?

highvista said:
I saw the same memory-filling behavior a few days ago. It was soon after receiving an update for the free version of StreamFurious. I think this update was a mistake by the dev, since it had the advanced features I assume came from the full pay version. When it ate all my internal memory, I deleted the app and then re-installed from the Market. It was fine after that, though not long after this, the dev posted another update that took away the pay features again. It's been fairly stable since, though maybe a bit more prone to dropping active streams.
Click to expand...
Click to collapse
Thanks highvista - uninstalling and reinstalling did help. Still, Streamfurious is nothing like it used to be. Now it is always dropping the stream. I am definitely looking for a replacement to Streamfurious. Anyone know a good one that I can use with custom URL's (one of my main stations is Radio Swiss Classic)http://www.radioswissclassic.ch/en/webradio

I used streamfurious a long time. Im having the same issues and reached the point of uninstalling it.
Someone on the market (under the streamfurious comments, of all things) suggested "Cherry Rplayer". Its free.
Ive only had Cherry Rplayer a day or so, but I can tell you from what I have seen so far it has none of the streamfurious issues.
Blade

Blade10,
Thanks for the recommendation for Cherry Rplayer. I will reserve final judgement until after several days of testing, but so far, so good. It appears to be vastly superior to Streamfurious. Not a single dropout. And it works perfectly with custom URLs and AAC, two of my most important requirements. Thanks again for jumping in and letting me know.

The author released a new version of streamfurious last night that supposedly reverts back to the old streaming engine. I haven't tried it yet to confirm.

5spot said:
The author released a new version of streamfurious last night that supposedly reverts back to the old streaming engine. I haven't tried it yet to confirm.
Click to expand...
Click to collapse
Seemed to solve the memory issues. Works great for me

But the old Streamfurious didn't support AAC, so why go back to that? Plus I'm still more than a little irked that they would put out such a piece of untested junk.

The Boot Loop of Death (BLOD)

Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....

Reserved for future use

My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.

I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done

wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.

I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.

I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.

I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)

The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.

While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.

I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.

I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.

cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.

I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.

DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.

MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?

DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.

I have this on stock 2.1u1 EPE54B

I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.

tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?

[Q] Where is RC1-7.0.0-11.02.18 CM7 for Milestone?

I see in the Dev forum that the first RC1 of Cyanogenmod 7 for Milestone is available, but when I go to download it here, it doesn't seem to be available. I guess it would be called update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip but that last one available was the 11.02.15 release. Does anyone know whether the RC1-7.0.0-11.02.18 has been withdrawn for some reason?
I've been testing each and every build with good success, so I'm really keen to try the new one. I would ask in the dev forum, but I'm relatively new at the XDA forum and am therefore not eligible to post in it.
SF

Well, I eventually found the correct download link at https://github.com/downloads/nadlabak/android/update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip
Thanks,
SF

How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.

FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
I would stick with cm6 for now. CM7 could use many improvements and as of now is very memory hungry (I was on the feb.10 release). CM7, however, has many bug fixes that are not implemented in cm6, for example, the wifi fix (wasn't working with some n routers before I think [depending on the security type or something] ) and it seems as though there is also the random freeze + random reboot fix (using another, older kernel) I would not switch to CM7, until many bugs are fixed. Also some games don't work.

FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
It's great. But video playing not working for me.

So I installed CM7 to try it out, and on RC1 my videos play fine (widescreen) using the included "Video" app. Well most of them do, one of them is displayed 4:3 for some reason?

I'm finding that it works quite well. Battery life is good, but there are a few bugs that need working out. CM6 is probably better if you need your phone to be 100% reliable, but I like to push the boundaries and play around.
Bugs or missing features so far:
- Button lights and keyboard backlight not working properly for me (and at least one other user here)
- Auto backlight brightness not working for me at all
- Volume button swapping/remapping not yet implemented, so that in lanscape mode left means louder (which is the wrong way round for me)
- Memory usage is a problem, so that Launcher pro keeps having to re-initialise
- Camera is VERY unreliable
- Getting random reboots and lockups, especially in Google Maps
Still, things are getting better with every release and I can always go back to CM6 if I want, since I made a Nandroid backup in OpenRecovery before I installed the CM7 update. I've just installed the RC2 update, so lets see how that goes...
SF

NeoFroyo!! Well testing

hey guys!
Well i was trawling the android forums and found this!
http://www.neopeek.com/viewtopic.php?t=7524
All thanks yo neopeek for the rom.
I decided to test it out on my kovsky. This coupled with I believe duckkly's kernels worked like a charm!! ill post the kernels up here too as I experimented with quite a few to see what worked best!
Battery life: 8 hours on full blast so i rekon around 11 on normal usage
Wifi: never ever ever dropped on me so far! thou it does seem to be weak in some places around my house where i usually should be getting more signals and strong at places where i get little signal :S.confusing
phone: well calls come in and stuff but sometimes ull see a black screen and cant see who's calling! :S
Bluetooth: paired with my mw600s just fine dont know about file transfer
market:works just fine a bit slow though..could be my internet speeds out here in pakistan.
Apart from that using whatsapp like a charm. facebook apps. gaaps everything works!! not a single sod to date been using it for around about 5 days or so.
Sorry for the spelling errors! big thanks goes out to neopeek and duckkly or whoever compiled those kernels !
PS: oh and the keys will freeze up as you hit around 20% battery. I simply reboot. Also terminal doesnt seem to be working. keeps crashing on me but i dont really ever use it in daily use so it seems to be pretty stable apart from these flaws. Also you'll need to reinstall quickpic from market
Also im on radio 1.16 i believe. 1.14 seemed to drop calls randomly.
please read all of neopeek's instructions before flashing ! happy flashing

can't confirm 20% battery being the point where keys stop working. for me 4 hours of uptime seems the be magic point...
i stopped restarting modules via script (how to has been explained many times in here) and simply restart. most of the time it happens when an app is running - now what good is it if you have a shortcut somewhere, but can't get there because back- and home-key isn't working?!
but yeah, neofroyo is a big step forwards. first time using android on x1 is fun!
for terminal to work you have to reinstall it just like quickpic.
i just hope we'll see some kernel-update soon. without it the whole thing is pointless.

lol truee..thanks for the terminal update. oh if u press the camera button it will take you back to your home screen. than i guess u could load the keyboard modules..annoying i never bother with it. try my combination of kernel it gives me decent battery lifee but yea its the kernel with all the problems. tried the new kernels but they dont seem to work properly

hm, which kernel-version is that?
might try if i know which it is. just had to step down from ygge-monster to ygge-turbo. monster made my touchscreen getting unprecise in left half.
thx for the update with cam-button - never bothered to press that, since camera doesn't work anyway.
yeah, new kernels suck for our device, especially since they're missing the specific battery-driver for x1. the only guy still working on x1-kernel has been silent for months, but i can see he's still at it (porting 2.6.35.7).

Just tried pressing cam-button.
Falls back to lockscreen, after unlock shows homescreen. But system is frozen and after some time reboots directly to android. But lots of stuff doesn't work, especially phone-stuff. So i have to reboot winmo anyway.
Sent from my X1i using Tapatalk

i think its the ducckly's keyboard not loaded as modules turbo verison. I believe it should be that because i remember the msm drivers werent really working properly on it
Sent from my Transformer TF101 using Tapatalk

Invisiblek's 4.4 12-30-13 Nightly Impression

I can't post this on the Milaq thread (where most of the invisiblek discussion is) so I thought I would post it here to give anyone else a heads up.
The Good:
It's a fairly stable kernel and all my apps run seemingly just fine. I mean I've only been running it about 5 hours but not a single FC. I did have a weird bootup glitch that locked it up right away after install but after that I loaded all the apps just fine. Super exciting to see it so far!
The Bad:
Screen pixelation/tearing from left to right, especailly on grey backgrounds. Something is up with the video driver/gpu voltage. Certain icons like the Settings sprocket will have a few pixels that will flash and other times you'll see lines all the way across the screen. It might be color specific. I was playing Quadropus Rampage and never noticed it but then went back to the home screen or typing an e-mail and it's very much there.
Pandora plays music fine. If you turn off the screen while playing, horrific things happen like ZZZZZZZZZZZZ and then hard lock. I didn't like that station anyway..
The "OK Google" voice command doesn't seem to work though voice typing does. I'm pretty sure this worked on the Milaq build of the same date.
It's a bit slow and CPU is stuck to 1188. There is a bit of a lag switching apps but I don't notice any core functions slow.
The Different:
The home button doesn't wake up the TP. Only the power button.
Can't say anything about battery life quite yet but I'll keep a gander on it. Battery hasn't been a super concern of mine because I plug it in ever night

The Different:
The typical 15 second reset switch mult-button key is more like 3 seconds now. I like this a lot better.

Positive:
--backup and restore work
--it is getting much better.
Negatives:
--Microphone does not work, so I could not use any vioce search or voice dialer/sound recorder.
--Free game "F.S. Xtreme" has black box issue.
--Youtube still has reboot issue.
--TV streams app "syncbak" has similar reboot issue.

My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.

Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.

Waiting on Flintmans as it is the only non data media rom. Not a big fan of all the repartitioning. For several reasons. Good to see choices still available. God bless the developers for all their time and effort. Wish I could do what they do.

goog888 said:
Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.
Click to expand...
Click to collapse
I flashed 3.4 rom (0103) over 3.0, and tried briefly.
--3.4 rom seems running OK, except it runs relatively slower at 1.1Ghz.
--camera is not working on both 3.0/3.4 rom.
--Free game "F.S. Xtreme" seems not compatible with 3.x kernel. It also cannot run on Samsung S3.

Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Turn off WiFi Optimization in settings.

EbolaCola said:
Turn off WiFi Optimization in settings.
Click to expand...
Click to collapse
Still does it. Did that soon as rom booted as per the Op.

Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Same here. Also double check that the setting took. I swear I unchecked it and it went back or didn't take the first time. Perhaps give it a toggle or two. I also noticed that if wifi turns off, it won't turn back on.

Anyone else having a problem with rebooting from within CM and it just goes to a blank screen?

Dirty flashed to the 1/5 nigthly. Reboot issues seems gone now, or just that a reflash has fixed mine specifically.

Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!

sokratz said:
Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!
Click to expand...
Click to collapse
Negative on the posting. I'm still seeing the bzzzz when the screen shuts off while playing music. Have disabled the mic (I think). Curious that nobody on that thread has reported that quite yet.

I'm very excited to see all of this development on our old TPs! I'm currently running Milaq's latest 3.0 kernel test build. It is running almost perfectly for me! I cannot wait for 3.4 to finish getting smoothed out. I've tried Invisiblek's builds out, and they currently seem a little laggy compared to Milaq's 3.0 test build. Great work all around though! Thanks to Invisiblek, Flintman, Milaq, JCSullins, Dorregary, and all of the others that I haven't mentioned who have contributed so much of their time and skill toward keeping our Touchpads relevant, even competitive with the current crop of tablets on the market!
Sent from my TouchPad using Tapatalk 4