Related
So Im running JACxHEROSkiv1.6r2B and I have a 4gig class 6 sd card. I have the fat32 set up, ext3, and linux swap at 32.
I had a class 4 before, but hearing everyone rant and rave how fast hero runs with a class 6 I went out and bought one. However, hero still seems to be a little laggy and slow..... at least for me. I'll get the htc screen and the loading screen.. I even reverted back to superhero v2 and that was the fastest hero for me, no lag, no loading screens nothing.
But the newer hero's seem to be slow for some reason even with a class 6. Can anyone help, I absolutly love hero, just want it to be fast like how everyone says it is.
Thanks in advance...
hang your head in shame...
the speed of hero roms will vary depending on the phone itself, the way the phone is used, the settings on the phone, the way people use their phone, how they choose to set up their linux-swap size and what they set swappiness to, in short, different people get different results with hero roms, some find them fast, some find them tremendously slow, its most likely a mind over matter type deal... so finally we reach the point of all this.... stop with the why isn't my hero blazing fast threads and how do i make hero make hero faster threads. basically you have 2 options for optimizing your hero build, set it up exactly the way the first post of the thread tells you to, or you can pm the people with amazingly fast hero roms and ask them what they are doing...
wow i was a smart ass and still managed to give a half way decent answer
I did follow ALL directions, i've flashed tons of roms and experienced different things with different builds. Kind of wierd how superhero v2 seems to run faster then the new builds. Even with the echo at 60, some threads say set it to 10, etc. Followed all directions, and still have these results. When a thread says FAST, you kind of expect it. I mean gimme a break going from checking the market to your home screen you get a loading issue, c'mon. There has to be something to alter to fix it. I know im not the only person having slow issues with hero EVEN on a CLASS 6
there was a post i just read where some one set there linux-swap to 96mb and swappiness to 100 and said it ran really fast, that was the newest jacski hero rom version b i think. you could always try that, though whether or not it will suffer future slow downs remains to be seen. I haven't tried a hero rom recently (since 3.6.8.1 was released by cyanogen damn that was a while back) because of the slow downs i would get after a day or so i don't know much other than to try what others are saying works.
though with the way drizzy's new hero v1 is shaping up to look i might have to try it when he drops it. I remember trying jac's 1.4 hero, if you think the hero roms they have now have lag... but alas now i am reminiscing
I agree, his new hero rom is supposed to be the best to date, so we'll see, I just flashed over to cyans 4.0.4 since its fast. I also read about the 96mb and 100swap, but I want to see what happens in a few days with that.
cire253 said:
So Im running JACxHEROSkiv1.6r2B and I have a 4gig class 6 sd card. I have the fat32 set up, ext3, and linux swap at 32.
I had a class 4 before, but hearing everyone rant and rave how fast hero runs with a class 6 I went out and bought one. However, hero still seems to be a little laggy and slow..... at least for me. I'll get the htc screen and the loading screen.. I even reverted back to superhero v2 and that was the fastest hero for me, no lag, no loading screens nothing.
But the newer hero's seem to be slow for some reason even with a class 6. Can anyone help, I absolutly love hero, just want it to be fast like how everyone says it is.
Thanks in advance...
Click to expand...
Click to collapse
I had the same issue with my 32mb swap. I changed it to 96 and saw a HUGE increase in performance. No compcache. Just swap with 60 swappiness and I hardly ever see Loading or the HTC screen.
Here is a thread that discusses this issue:
http://forum.xda-developers.com/showthread.php?t=551643
It is among many, however almost everyone has their own opinion based on their own phone which is of course based on their own needs. The key is playing around with it and seeing what works best for you. Start with the swappiness and then try your swap partition size and see what works best for you.
Then there was a vague tweet from jac about a possible fix for bluetooth, and twisted zero is supposedly getting really close with the led's, also with the htc kernal that was made open.
It really wouldn't suprise to me to see in another month or so a hero rom that competes with stock cupcake, maybe i'm too optimistic though lol
david1171 said:
...maybe i'm too optimistic though lol
Click to expand...
Click to collapse
I think so too.
Binary100100 said:
I think so too.
Click to expand...
Click to collapse
well when you compare jac's 1.4 back when hero threads were getting thrashed left and right to what the hero rom's are now. there is a vast improvement. I remember when I couldn't use a hero rom for more than a few hours without having to go to a stable rom. now my friend has had a rom on his phone a few weeks and hasn't said anything to me about it running horribly so maybe one day...
david1171 said:
well when you compare jac's 1.4 back when hero threads were getting thrashed left and right to what the hero rom's are now. there is a vast improvement. I remember when I couldn't use a hero rom for more than a few hours without having to go to a stable rom. now my friend has had a rom on his phone a few weeks and hasn't said anything to me about it running horribly so maybe one day...
Click to expand...
Click to collapse
I agree that the Hero roms are stable enough for daily use provided that you make certain adjustments, but in regards to the LED and bluetooth I don't think they will be perfect for a long time. The LED will hopefully come soon since Twisted reported getting them to work. But I don't understand why we don't have fully working LED's like that was announce last week. Perhaps it was an accidental fix that couldn't be recreated? Perhaps it was a fluke? Who knows. What I do know is that the LED's still need work even after it was reported to have a fix. As for bluetooth... as far as I know and read it could only be initialized by manual command lines and not from the settings app. Even IF there is a fix... will it be full bluetooth (A2DP) or just enough to pair and use a headset?
The fact that the BT and LED's for Hero builds tend to work with MT3G and not the G1 tells me that it's hardware related and not so much in code or scripts. So if fixes to the LED and BT are developed and perfected then how will the MT3G work after flashed a ROM with these patches included? Will they conflict? Will we need different ROMs for different phones? I'm not trying to be negative or pessimistic but I'm just not seeing full fixes for these issues to be ready, available and implemented this week or next. Maybe in a month or two... but that's as far as my optimisism takes me. But I hope that I'm wrong.
Is anyone going to build a FroYo rom for the vogue?
If memory serves, Eclair was announced/released on phones for months before AOSP ever had a hold of it.
If it takes months again for Froyo to be released, I'll probably have moved on. However, if AOSP does get Froyo in a reasonable amount of time, I'll do enough to at least dabble in it and create something. No promises on functionality.
I'll be at Google I/O next week, and I have plenty of questions, one of which is how soon we'll see Froyo on AOSP and if it'll be brought up to speed at faster, more regular intervals.
Tell them Google people that they promised me a pony!
Shidell said:
If memory serves, Eclair was announced/released on phones for months before AOSP ever had a hold of it.
If it takes months again for Froyo to be released, I'll probably have moved on. However, if AOSP does get Froyo in a reasonable amount of time, I'll do enough to at least dabble in it and create something. No promises on functionality.
I'll be at Google I/O next week, and I have plenty of questions, one of which is how soon we'll see Froyo on AOSP and if it'll be brought up to speed at faster, more regular intervals.
Click to expand...
Click to collapse
Isn't there a rom out for the Droid or Nexus already?
This is supposed to have a 250% increase in speed, that would be sweet
berardi said:
This is supposed to have a 250% increase in speed, that would be sweet
Click to expand...
Click to collapse
I heard it was a 450% increase... and I know theres at least a few people running froyo on thier Nexus
as soon as we see a froyo dump we'll see if our libs/kernel will work with it. If not we'll have to wait until the aosp is updated to compile the drivers for froyo.
loserskater said:
I heard it was a 450% increase... and I know theres at least a few people running froyo on thier Nexus
Click to expand...
Click to collapse
sure there's a 450% inc on systems with a FPU built in, we don't have one so we'll only see a 200% or so if that
mrono said:
sure there's a 450% inc on systems with a FPU built in, we don't have one so we'll only see a 200% or so if that
Click to expand...
Click to collapse
Let's not pretend a 200 percent increase wouldn't be awesome.
TheKartus said:
Let's not pretend a 200 percent increase wouldn't be awesome.
Click to expand...
Click to collapse
This is so true!
fyi, our libs don't work natively on froyo. We'll have to wait for the aosp to be updated so we can make the required adjustments and compile them for it.
mssmison said:
fyi, our libs don't work natively on froyo. We'll have to wait for the aosp to be updated so we can make the required adjustments and compile them for it.
Click to expand...
Click to collapse
How long is that usually from SDK release? 2.2 looks really fun.
looks fun, runs slow on the vogue. Mind you this is only the sdk build (which is usually slower and more buggy in the begining).
Hopefully it won't take too long.
It probably wont fit on nand.
Also they say froyo 2.2 is lik 5x faster than eclair.
My guess as to why its faster is 2 things;
better coding
More of the mobile operating system is in the ram
(which is why it will be running faster)
Since all the newer devices have a crap load of rom and ram, this wont be a problem.
But for us vogue users who have limited rom and ram, this will mean we will run it off the sd card; which is ok......
Overall i do hope it runs than i anticipate.
intimidatorx31 said:
It probably wont fit on nand.
Also they say froyo 2.2 is lik 5x faster than eclair.
My guess as to why its faster is 2 things;
better coding
More of the mobile operating system is in the ram
(which is why it will be running faster)
Since all the newer devices have a crap load of rom and ram, this wont be a problem.
But for us vogue users who have limited rom and ram, this will mean we will run it off the sd card; which is ok......
Overall i do hope it runs than i anticipate.
Click to expand...
Click to collapse
Couldn't it be possible to reduce it's size? Removing applications and unnecessary gadgets?
It is reasonable to assume that we could fit a stock build of Froyo onto the Vogue's NAND memory--especially given that Froyo natively supports transitioning applications to the SD card. It remains to be seen what size a stock Froyo build will be (roughly).
Froyo is optimized, sure--but the majority of the speed increase is coming from the trace JIT compiler. (The browser will be faster rendering Javascript as well thanks to the V8 engine being migrated in from the Chrome browser.)
Shidell said:
It is reasonable to assume that we could fit a stock build of Froyo onto the Vogue's NAND memory--especially given that Froyo natively supports transitioning applications to the SD card. It remains to be seen what size a stock Froyo build will be (roughly).
Froyo is optimized, sure--but the majority of the speed increase is coming from the trace JIT compiler. (The browser will be faster rendering Javascript as well thanks to the V8 engine being migrated in from the Chrome browser.)
Click to expand...
Click to collapse
Trace JIT has quite a bit of RAM overhead - that's one of the reasons it was originally not in Android (check out the Android overview talk from 2008's Google I/O for details). And it really only tends to make CPU-heavy loops (games, artificial benchmarks) faster. On the other hand, Google claim to have optimized low-memory handling and the low memory killer/ejector (check out the Android 2.2 new features page).
However, I *highly* doubt it'll fit in NAND - that's the reason Google's cited for never bringing 2.2 to the G1 (in a fireside talk with Gizmodo).
At any rate, if Froyo isn't coming to the G1 family, we won't get 3D drivers (which need to be updated) for the Vogue either, so we're probably dead out of luck. It'll run, but without GL drivers the experience will probably not be great. Someone might be able to shim/dummy in the older ones (especially once AOSP is out) but I wouldn't get my hopes up too far.
Don't get me wrong, I'd love Froyo on the Vogue, but there are a lot of reasons it's a pipe dream.
The V8 improvements have already been backported to Eclair (The Eclair branch of Cyanogenmod has had V8 is a compile time selection for ages - it's disabled by default mostly due to an incompatibility with some JS used in the Epocrates app) so we might see those. The stable JIT might get backported onto the existing hacky / open-source Eclair one as well.
Mmm...Android FroYo...
1. yes froyo fits on nand no problem,
2. the 3d drivers work just fine that we're already using
3. the reason it was slow (when I mentioned it) was becuase of the un optimized apk's, and of course the new launcher 2. it runs much better with an alternative launcher. Though it's not really any faster than eclair at this point. More testing is required.
4. yes once aosp is out we'll get the libs updated and get full compatibility. (or as close as we can)
bri3d said:
Trace JIT has quite a bit of RAM overhead - that's one of the reasons it was originally not in Android (check out the Android overview talk from 2008's Google I/O for details). And it really only tends to make CPU-heavy loops (games, artificial benchmarks) faster. On the other hand, Google claim to have optimized low-memory handling and the low memory killer/ejector (check out the Android 2.2 new features page).
However, I *highly* doubt it'll fit in NAND - that's the reason Google's cited for never bringing 2.2 to the G1 (in a fireside talk with Gizmodo).
At any rate, if Froyo isn't coming to the G1 family, we won't get 3D drivers (which need to be updated) for the Vogue either, so we're probably dead out of luck. It'll run, but without GL drivers the experience will probably not be great. Someone might be able to shim/dummy in the older ones (especially once AOSP is out) but I wouldn't get my hopes up too far.
Don't get me wrong, I'd love Froyo on the Vogue, but there are a lot of reasons it's a pipe dream.
The V8 improvements have already been backported to Eclair (The Eclair branch of Cyanogenmod has had V8 is a compile time selection for ages - it's disabled by default mostly due to an incompatibility with some JS used in the Epocrates app) so we might see those. The stable JIT might get backported onto the existing hacky / open-source Eclair one as well.
Click to expand...
Click to collapse
Now I'm no expert and only spouting off what I had read somewhere else, FROYO will really not benefit the vogue or kaiser at all. Its the JIT that will help us on other builds correct me if I'm wrong but there is something else in froyo that makes the big difference. Froyo utilizes a part of the processor in the N1 that's not been used in older builds this is where the added speed comes from. Granted it would be nice if I'm wrong though. I'm sure some of you others are more in the know than I am.
Just want to see what everyone's take is with the battery life issues, etc
[highlight]Mod Edit: trolling and flaming are not allowed on XDA grounds. Consider this a friendly warning[/highlight]
If you guys seriously consider that either trolling or flaming, then your standards for such really are lackluster.
For the sake of the thread though, I went back to MCR r15. Runs amazing, and have much faster up and dl speeds. Paul said he will be releasing a ROM based on this soon anyway, so I can wait. FroYo was amazing though. Only real reason I went back was because of a wifi issue, LOL. Turns out it was just an IP address conflict. I reset the IP of my laptop and solved it, but only AFTER I'd reverted. Too lazy to go back again.
dictionary said:
If you guys seriously consider that either trolling or flaming, then your standards for such really are lackluster.
For the sake of the thread though, I went back to MCR r15. Runs amazing, and have much faster up and dl speeds. Paul said he will be releasing a ROM based on this soon anyway, so I can wait. FroYo was amazing though. Only real reason I went back was because of a wifi issue, LOL. Turns out it was just an IP address conflict. I reset the IP of my laptop and solved it, but only AFTER I'd reverted. Too lazy to go back again.
Click to expand...
Click to collapse
Why MCR R15 over CM 5.0.7.1?
hah2110 said:
Just want to see what everyone's take is with the battery life issues, etc
Click to expand...
Click to collapse
I have great battery life with FroYo, running stock FroYo kernel, and all... I do have a few small bugs that were clear signs to me it was unofficial to begin with, and am excited for the official release to see if it polishes out those few minor issues.
All in all, though, 99.9% of if works perfect. Super fast, great battery life, and so forth. Radio seems to be about the same as all the others, I get good 3G when I have it, good EDGE when I am on that. I still say I get better reception than my G1 did, but that is just me and my testing at my Dad's house (death hole for cell phone coverage) and my basement (it is where my "man dungeon" is located). Beyond that, I always get good coverage no matter the phone, so it has been a moot point to me... speed wise, I always edit my GPRS and HSDPA to 12 and 2.
hah2110 said:
Why MCR R15 over CM 5.0.7.1?
Click to expand...
Click to collapse
Why CM over MCR? Or Enom over CM? and so forth... personal preference is the likely answer. I like MCR since I have a pay account over there and can use his kitchens, thus making a ROM that is lighter. I like Enom because it is rock solid, fast, and great battery life (1.8.1 is best IMHO). I like CM because it is bleeding edge, fast, and while has its moments of instability, is still the gold standard for a full feature custom ROM, especially with all the extras pre-baked in. Desire has only 1 real option, Modaco.
And I like FroYo the most because it is new, super duper fast, good battery life, and I like frozen yogurt.
hah2110 said:
Why MCR R15 over CM 5.0.7.1?
Click to expand...
Click to collapse
MCR r15 for me runs soooo much smoother. I love CyanogenMod, as my sign indicates. LOL. After trying out r15 though I was hooked.
The poll options seem to indicate a dislike of Froyo. Even the positive options imply that by using it you are putting up with tons of bugs or something. Are people really having trouble with Froyo?
It's been working well for me. My battery life has been worse but I thought it was just because I had turned Latitude back on about the same time I upgraded to Froyo.
hexix said:
The poll options seem to indicate a dislike of Froyo. Even the positive options imply that by using it you are putting up with tons of bugs or something. Are people really having trouble with Froyo?
It's been working well for me. My battery life has been worse but I thought it was just because I had turned Latitude back on about the same time I upgraded to Froyo.
Click to expand...
Click to collapse
I LOVE FroYo but can't tolerate the battery consumption. Sorry if it came off bias
I love FroYo and I want to keep it but... I have some problems that I can't live with.
1. Reboot phone, resets widgets and some installed programs on SD
2. Double messaging notifications (stock messaging app conflict with other apps, even if I disable notifications)
3. Miss the tweaks and stuff from CM
Still using it but urging to switch back until custom roms are out.
Not only am I keeping Froyo, I'm being FORCED to use my TMobile Nexus(2.2) instead of my ATT Nexus(2.1) because Froyo makes 2.1 feel like a slow crappy beta.
I cannot even get voice plus data at the same time with my TMobile Nexus, yet I use it because, imo, Froyo is that much better.
Going back to my 2.1 Nexus feels like a pre launch beta device that I yell at because it's so damn laggy compared to Froyo, which is fast as a bullet.
Please Google give us 2.2 so I can go back to my freaking ATT Nexus!
wish I could have two nexus ones, LOL.
Overall I loved FroYo, and had I realized the IP conflict before switching back to MCR r15, I would still be on it.
Well, I just solved two of my problems, it's not so bad now. Going to stick with it
dictionary said:
wish I could have two nexus ones, LOL.
Click to expand...
Click to collapse
if I'd known the ATT version was going to follow so closely behind the Tmobile version, I would only have one as well. I just couldn't wait. I keep the Tmobile Nexus rather than sell it because if anything were to ever happen to my ATT Nexus, my GF will NEVER let me buy a third one. I've used up my smartphone quota for quite awhile
People get too caught up in the other ROMS when in all reality Froyo briings everything they need via a stock ROM but some folks would rather run Cyano or Modaco just to say they have have a custom ROM. In all reality if you install Froyo after a clean wipe the only real bug you will encounter is with some marketplace apps not showing up. A small price to pay considering they will eventually show up and life will be back to normal. The majority of ppl complaining about other bugs are folks who flashed froyo over a cyano or modaco etc.. rom and of course they are going to have problems as this update was obviously not tested with cyano or modaco as a base rom for obvious reasons. I'd say a good 90% plus of the problems some are experiencing are due to this and the rest of us are loving Froyo to death. I'm happy with it and anxiously awaiting the official release so I can reinstall those market apps that are missing as that's the only real bug I am encountering after a clean install of Froyo.
For everyday use I feel Froyo is definitely slower than CM5.0.7 with pershoot's latest kernel. I used CM's quick rooter with Froyo so I was also OC'd for a fair comparison. I'm still going to keep using Froyo because it's fun seeing optimizations and themes etc slowly tickle out for the new Android build.
bluehaze said:
People get too caught up in the other ROMS when in all reality Froyo briings everything they need via a stock ROM but some folks would rather run Cyano or Modaco just to say they have have a custom ROM. In all reality if you install Froyo after a clean wipe the only real bug you will encounter is with some marketplace apps not showing up. A small price to pay considering they will eventually show up and life will be back to normal. The majority of ppl complaining about other bugs are folks who flashed froyo over a cyano or modaco etc.. rom and of course they are going to have problems as this update was obviously not tested with cyano or modaco as a base rom for obvious reasons. I'd say a good 90% plus of the problems some are experiencing are due to this and the rest of us are loving Froyo to death. I'm happy with it and anxiously awaiting the official release so I can reinstall those market apps that are missing as that's the only real bug I am encountering after a clean install of Froyo.
Click to expand...
Click to collapse
I agree, to a degree, but there is no way most people are just caught up in the hype of a ROM. The assumption and assertion that custom ROMs are pointless is unjustified, and bias to your needs. I find the the enhancements custom ROMs bring can drastically alter my user experience in many ways. For example, MCR r15 runs circles around my stock ROM, in terms of speed, performance with games, battery life, etc. Prior to FroYo, these ROMs added the wifi/wired tethering, lower capacitive button fix (thanks kmobs), better battery life, smaller file sizes for installed system, homescreen rotation (which FroYo still doesn't do), trackball colors, and various other small tidbits. Now that FroYo is out (I wonder how much of what's in FroYo only came about due to the Dev community putting it out there, and Google taking notice.. hmm), I can only imagine what the Devs will cook up to enhance it even further.
Looking forward to the future Cyano ROMS based on Froyo no doubt but at this point in time Froyo brings everything I ever rooted for and gives me better battery life to boot. The dev community certainly had some influence in the features we see today in Froyo and for that I am thankful, don't mean to sound like i'm coming down on the devs. I just don't see much point in running anything other than Froyo right now but will consider it once I see what the devs can add to it.
bluehaze said:
...
I just don't see much point in running anything other than Froyo right now but will consider it once I see what the devs can add to it.
Click to expand...
Click to collapse
Well, if you want a good example - I want the option to have sd-ext partition (custom, pre-Froyo Apps2SD). Firstly because many apps I have currently don't support moving to SD - and I'm "overbooked" by at least 50MB that I have to offload to SD card to have some space left on the device, and also because I like the ability to mound SD card without loosing access to applications.
I also hate it that I don't have direct access to hidden system menus, and even for changing the browser user agent I need to write "about:debug".
Those things keep me with CM5.0.7.1 until better times.
I downloaded the leaked froyo firmware to my captivate hoping it would solve a lot of the issues of lag but it still lags a lot like it's a phone from 2006. I downloaded the Ryan ZA one click lag fix and it still lags. I wanted to put voodoo on it but I have froyo and I don't think it will allow me to do it...what the heck is the problem and why is there so much hacking I have to do to get it to run smooth. The HTC Aria runs blazingly fast and quick from what I read and this Super Phone Galaxy S runs slower than a Hero? If anybody has an answer I'd like to know or if someone can offer some suggestions on how to improve this. It's pretty annoying.
crossover37 said:
I downloaded the leaked froyo firmware to my captivate hoping it would solve a lot of the issues of lag but it still lags a lot like it's a phone from 2006. I downloaded the Ryan ZA one click lag fix and it still lags. I wanted to put voodoo on it but I have froyo and I don't think it will allow me to do it...what the heck is the problem and why is there so much hacking I have to do to get it to run smooth. The HTC Aria runs blazingly fast and quick from what I read and this Super Phone Galaxy S runs slower than a Hero? If anybody has an answer I'd like to know or if someone can offer some suggestions on how to improve this. It's pretty annoying.
Click to expand...
Click to collapse
Its called RFS... call up samsung and complain to them about it...
so many problems with this
a) wrong section, Q&A or general please
b) notice that word "leaked" in what you said? it means this isn't OFFICIAL, which means it likely ISN'T the final release, so it's bound to have at least some bugs.
c) ryanza lagfix is placebo and awful and doesn't work at all (on top of that, ext2 is a bad choice)
d) if you understood how/where the lag was coming from, you'd know why voodoo is "necessary" on 2.1
e) the aria is built EXTREMELY different from the captivate, it's like comparing the iphone to the nokia n8... yes they're both android, but they're built different which leads to complications
f) voodoo is not yet available for 2.2 because we don't have source code for 2.2 (again, if you knew how voodoo worked, you'd know why it wasn't instant)... we can hack it in with initramfs, and there are people working on it... but it isn't top priority
g) and shockingly a SMALLER piece of hardware with a SMALLER resolution made by a company known for making quality android phones runs smoother? shocker. honestly.
h) if you actually had any other real world interactions with other android phones, you'd know the lag is occasional but not unusual (hell I've seen just as bad or worse on the droid x before)
i) I suggest you read, read, read, search, read, read, and think before you make posts like the above (why on earth you thought this belongs in development is beyond me)
/rant
There are two kinds of lag. I/O lag is caused by the delays in accessing data stored on your phone in some partition. This is largely due to the use of RFS by Samsung, and the voodoo lag fix gets rid of most of that. Unfortunately there is no voodoo on Captivate leaked Froyo yet, as the source code has not yet been released by Samsung. The OCLF type fixes will help some by masking this lag when the amount of data being written and read is small. When a large amount of data is involved, these fixes will lag, as they still sit on top of RFS.
There is a second kind of lag due to memory shortage. This will hit you after the phone has been on for a while. This is similar to the paging seen on Windows, where the data has to be fetched from the hard disk. This type of lag is best fixed by installing a memory management application. The one I use is called Autokiller. Despite its name, it is not a task killer. What it does is make sure that a certain amount of RAM is always free. I use the strict profile, and my phone can go days without having to be rebooted.
troll. go get an aria then^^
save a galaxy s for a person who can truly appreciate it.
by accident I posted this in the development area, I didn't realize until after the fact, my bad.
So do you think I should put my phone back to 2.1 on my phone and apply voodoo? My phone lags quite a bit, it's bad.
I'll try out that app you suggested, thanks.
..............
crossover37 said:
by accident I posted this in the development area, I didn't realize until after the fact, my bad.
So do you think I should put my phone back to 2.1 on my phone and apply voodoo? My phone lags quite a bit, it's bad.
I'll try out that app you suggested, thanks.
Click to expand...
Click to collapse
Look at the z4mod post in this forum. It works on 2.2
http://forum.xda-developers.com/showthread.php?t=811902
Kaik541 said:
f) voodoo is not yet available for 2.2 because we don't have source code for 2.2 (again, if you knew how voodoo worked, you'd know why it wasn't instant)... we can hack it in with initramfs, and there are people working on it... but it isn't top priority
/rant
Click to expand...
Click to collapse
There is a pre-release version out for froyo but I doubt it will provide more benefits than issues at this point.
cliffgardner said:
There is a pre-release version out for froyo but I doubt it will provide more benefits than issues at this point.
Click to expand...
Click to collapse
the "pre-release" version you're talking about is for the i9000... and guess what, the i9000 has source code, we do not
I had the same issue when I installed the leaked 2.2.
I did a master reset, flashed back to stock, master reset again, flashed to 2.2 cognition. Now I don't know if the second master reset was necessary, but my phone is faster than ever. Very few problems, in fact... less problem than the 2.2 leak.
Just flash to cog 2.1.6/2.1.7. I have absolutely no lag at all. Though even at stock my phone wasnt crazy laggy like your claiming your phone is.
rajendra82 said:
There is a second kind of lag due to memory shortage. This will hit you after the phone has been on for a while. This is similar to the paging seen on Windows, where the data has to be fetched from the hard disk. This type of lag is best fixed by installing a memory management application. The one I use is called Autokiller. Despite its name, it is not a task killer. What it does is make sure that a certain amount of RAM is always free. I use the strict profile, and my phone can go days without having to be rebooted.
Click to expand...
Click to collapse
Free RAM is wasted RAM.
And task killers, etc. are a great way to rape your battery life.
MikeyMike01 said:
Free RAM is wasted RAM.
And task killers, etc. are a great way to rape your battery life.
Click to expand...
Click to collapse
Autokiller is NOT a task killer. It changes the memory management profile that defines when the apps are closed. This is a combination of the amount of free RAM and the type of app and the state it is in. I also disagree that free RAM is wasted RAM. If you are trying to open a webpage and the amount of RAM is low, the system has to decide to close something else to free the space you need. If the profile of what to close is inefficient, you will frequently run into low memory situations, when the system has to continue to close some apps to free up the memory, and you will see lag as the system works it out for you. What makes you think that the profile that Samsung chose to determine when to close an app is necessarily the best one?
Came across a funny older article on a fruit based website about the nook color when it first came out. After reading it i couldnt help but chuckle.
This was the best part of it,
But unlike forthcoming Android tablets like the Samsung Galaxy Tab, this device is going to be locked down and will only be able to run a limited number of B&N-approved apps such as Pandora and Lonely Planet.
Click to expand...
Click to collapse
lol
Its a good read for a laugh.
I know that my nook color countinues to amaze me with more and more functionality everyday.
Its amazing what xda devs can accomplish. Take something and make it do something it was never meant to do and do it better than its competition.
That article is an unfortunate example of what a lot of tech journalists are doing these days. Hastily research a new product, then clip together a bunch of other coverage and bang out an article. By demonstrating his technical incompetence, sure he's got egg on his face now after the fact, however he also represents a large (the majority) percentage of B&N's customer base. The average purchaser would says "rooting what now?".
Amazingly, the NC has proven wildly popular and B&N's top selling item EVER, so obviously even with the limitations the author describes it's trouncing the competition. For those of use who know about ADB and scripts/img files, hey it's even better. Bought one for myself, then for my Dad (50's, tech savvy still). I rooted it, installed xeam and some apps then wrapped it back up and bang, best Christmas present ever!)
I've had a book 3g and then the NC which i rooted. Bottom line it rocks!!!!
Sent from my NOOTED NC using XDA App
I cannot wait for a fully functional froyo rom for the internal memory that will make this a true tablet
Sent from my DROIDX using Tapatalk
sp1kez said:
I cannot wait for a fully functional froyo rom for the internal memory that will make this a true tablet
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Forgot Froyo. Gingerbread CM7. It's going to be B-E-A-UTIFUL
nicbennett said:
Forgot Froyo. Gingerbread CM7. It's going to be B-E-A-UTIFUL
Click to expand...
Click to collapse
Name 5 things that Gingerbread does better than Froyo....
Anywho, I too look forward to a tablet-friendly custom ROM.. I still really like the status bar on the bottom of the screen, but the stupid B&N shortcut thing gets on my nerves when I'm typing.
khaytsus said:
Name 5 things that Gingerbread does better than Froyo....
Anywho, I too look forward to a tablet-friendly custom ROM.. I still really like the status bar on the bottom of the screen, but the stupid B&N shortcut thing gets on my nerves when I'm typing.
Click to expand...
Click to collapse
You mean aside from the better Dalvik VM, better battery management, improved UI, improved hardware capabilities (improved camera handling, gyroscope, NFC), improved game API, improved audio API, new media (audio/video) support, and a new linux base kernel? I guess if you don't count those, you still have the new/updated core libraries, updated bluetooth stack, improved text selection, built-in VOIP, and of course, the better keyboard...
Seriously, i mean, really seriously, why would ANYONE have anything against getting the NEWEST OS? All our efforts should be on gingerbread, since it offers the most compared to Froyo. Its not like moving to GB has any shortcomings, so why NOT want it?
I just got my nook color last night - I've found BBuy that had it in stock about 50 miles and drove there - sure enough about 20 were on the shelve - forgot to mention I traveled actually from one state to another (about 50 miles) to get it right of the shelve ... so anyhow, I am happy with "locked" nook color has to offer - I am even more thrilled about rooting it soon and unlocking the full potential. NC here I come
Yeah, a lot of the reviews bemoaned its alleged "doesn't know what it is" status. I've rooted mine, OC'd it, isntalled dozens of apps and games. Yet I still use it primarily to read novels, and do some light web browsing. And for that, it's dead perfect.
In other words, even an unrooted NC is an outstanding gizmo. I mean that screen is just to die for.
I definitely love my Nook. People are always surprised when I tell them it was only $250. Froyo on teh emmc via dd ftw! It's much better than the stock OS.
rjsmith2007 said:
I definitely love my Nook. People are always surprised when I tell them it was only $250. Froyo on teh emmc via dd ftw! It's much better than the stock OS.
Click to expand...
Click to collapse
IN regards to emmc Froyo - what about the lag? I guess it may just be my SD card, but every Froyo build i have tried, has been painfully laggy - not slow, but things like gmail can take 1-2 minutes to actually show the mail. The app drawer animations are also oddly slow. Does emmc really make Froyo more usable for you?
Divine_Madcat said:
IN regards to emmc Froyo - what about the lag? I guess it may just be my SD card, but every Froyo build i have tried, has been painfully laggy - not slow, but things like gmail can take 1-2 minutes to actually show the mail. The app drawer animations are also oddly slow. Does emmc really make Froyo more usable for you?
Click to expand...
Click to collapse
Oh GOD yes. There is no lag on eMMC. Typing this comment to you on my Froyo'd NC right now
Divine_Madcat said:
You mean aside from the better Dalvik VM, better battery management, improved UI, improved hardware capabilities (improved camera handling, gyroscope, NFC), improved game API, improved audio API, new media (audio/video) support, and a new linux base kernel? I guess if you don't count those, you still have the new/updated core libraries, updated bluetooth stack, improved text selection, built-in VOIP, and of course, the better keyboard...
Seriously, i mean, really seriously, why would ANYONE have anything against getting the NEWEST OS? All our efforts should be on gingerbread, since it offers the most compared to Froyo. Its not like moving to GB has any shortcomings, so why NOT want it?
Click to expand...
Click to collapse
No, I agree that Gingerbread has small incremental improvements, but nothing that'd cause me to say screw Froyo, wait for Gingerbread. Especially if Gingerbread on the NC is well off.
khaytsus said:
No, I agree that Gingerbread has small incremental improvements, but nothing that'd cause me to say screw Froyo, wait for Gingerbread. Especially if Gingerbread on the NC is well off.
Click to expand...
Click to collapse
I guess what i am thinking - given that Gingerbread is already being worked on, and our Froyo build doesn't actually work that well, why not just move ALL the resources out there to GB, and the most recent right away. Why go incrementally?
Divine_Madcat said:
I guess what i am thinking - given that Gingerbread is already being worked on, and our Froyo build doesn't actually work that well, why not just move ALL the resources out there to GB, and the most recent right away. Why go incrementally?
Click to expand...
Click to collapse
I'd agree with that.. If the effort is the same for both, go with Gingerbread. However so far we have Nookie Froyo which is "mostly" there and I haven't heard of Gingerbread on the NC at all.
Just to add how amazing this gadget is I'm typing this comment using SlideIT and it has taken mea fraction of what it used to.
Sent from my rooted Nook Color
khaytsus said:
I'd agree with that.. If the effort is the same for both, go with Gingerbread. However so far we have Nookie Froyo which is "mostly" there and I haven't heard of Gingerbread on the NC at all.
Click to expand...
Click to collapse
WEll, there is a gingerbread branch that is being worked on here: https://github.com/fat-tire/android_device_bn_encore
And there is plenty of talk that CM7 is on its way (though, i admit that i still fall into the see it to believe it camp). http://forum.cyanogenmod.com/topic/11127-nook-color/page__st__40
But regardless, the froyo build really isn't that usable - its laggy, market is like sludge, etc. I really think that the devs working on it, should take the froyo lessons, and focus totally on GB. Let froyo be the sandbox for others to learn on, and let GB be the first real OS upgrade for the NC.