yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] tee00max:
Man Im trying to get this phone set up so where I wont get any reboots or anything like that, doing another fresh load sitting here at work and im going to try your exact settings....I do know every device is different though.

---------- Post added at 02:52 PM ---------- Previous post was at 02:35 PM ----------

Guess my next thing is to see what zram is all about.
[Fascinate Android Development] jcurley:
I was getting that a lot with this ROM also. Now I have not been seeing it, but if it does keep happening I will go back to PW. So far, I have not had any issues with 10-27 kernel. I think the reboot thing, is the phone being bogged down on RAM. So I am trying to avoid that at all cost.

I have not had a reboot since I reset my VM heap to 48.
[Fascinate Android Development] MR H3LLMAN:
I've been having the same problem and have now used this rom on 2 seperate handsets. Absolutely love this rom but at this point its not worth it to me. Can't wait for the creases to be ironed out.
[Fascinate Android Development] weiserbyte:
Resurrection 1.0 Rom and Dock Battery Drain

Hello all,

I was wondering if anybody has come across a fix for the battery draining that occurs when these phones are docked past a full charge. Like many others, it appears that after the phone charges completely, it no longer recognizes the charge and begins to discharge. Do we know weft that is, and if there is a way to fix this bug?

Thank you,

Sean
[Fascinate Android Development] mkuehl06:
Known bug with just about all custom roms from what I've understood. No known fix as of now

Sent from my SCH-I500
[Fascinate Android Development] jcurley:
My battery is never lower than 96% when I pull it off the charger. I actually noticed with GB if I go down to 5%, then if I plug the phone in and reboot while charging, the phone will then read 60%. I have to pull the phone off and reboot again to get the correct battery level.

I am wondering if those of you that are waking up to a 50, 60, 70% battery, are you rebooting your phone while charging?

If you are at 30% before hand and are plugged in, maybe the phone is going to 100% but once you unplug it is reverting to correct battery level.

Hope this will help.
[Fascinate Android Development] droidstyle:
known bug for eh09 roms...aosp roms have the fix, atleast cm7.1 does.
[Fascinate Android Development] weiserbyte:
What you are describing with the 60% and 70% only occurs the phone is attached to a Dock with the desktop cradle running. If I have the phone connected to a regular charger without anything running then the phone charges to the standard 96-98%. I am aware this is a glitch in Roms EH09 and later, as I had no problems with any of the earlier roms. More than anything I wanted to know if anybody had ran into any fixes for this yet. :)
[Fascinate Android Development] laureanop:
No matter what my zram settings are,this phone still needs the memory optimizer. Grrrr! Damn you TW !

TSM Resurrection 1.0,TKSGB10-27 bleedingedge, lagfix, XIX,ec09 radio., 40heap,ondemand, bfq, oc 200-1200,Uv, zram96,honeycomb theme,mem opt
[Fascinate Android Development] jcurley:
Yep, figured that out yesterday. It sucks, but at least the akmo patches it.

tsm 1.0

tks 10/21

Memory optimizer optimal

XIX

lagfix enabled

Honeycomb

Heap 48
[Fascinate Android Development] DarthCivicus:
How do you do this?
[Fascinate Android Development] droidstyle:
dowload vm heap tool from market
[Fascinate Android Development] DarthCivicus:
Thank you, what causes the system to bog down like this? I changed the heap to 40 and installed a memory optimizer...anything else I can do? I also have the stable kernel from the 10/27 release.
[Fascinate Android Development] DarthCivicus:
What is AKMO? Where do you find z ram?
[Fascinate Android Development] droidstyle:
well its TW poor memory management that causes the bog because it does not properly free up ram to allow apps to run efficiently. no different than a pc, low memory causes bogging and freezing, unfortunately we cantu upgrade ram on these phones, so memory management needs to be efficient as possible. that's where memory optimizer steps in.

---------- Post added at 05:29 PM ---------- Previous post was at 05:27 PM ----------

auto killer memory optimizer from market

zram is a kernal feature, you need terminal emulator to enable. this has been covered multiple times in this thread. take the time and read a bit.
[Fascinate Android Development] laureanop:
It's autokiller memory optimizer. Use the optimum or aggressive presets. Without it the phone will eventually get bogged down.

TSM Resurrection 1.0,TKSGB10-27 bleedingedge, lagfix, XIX,ec09 radio., 40heap,ondemand, bfq, oc 200-1200,Uv, zram96,honeycomb theme,mem opt
[Fascinate Android Development] laureanop:
Now that I am certain that I need the memory manager I'm questioning the benefits of having zram enabled...

There things are undeniable:

- The need for the memory optimizer

- The lower heap size 36-48 range speeds up the phone.

- Beavis and Butthead still rule all

TSM Resurrection 1.0,TKSGB10-27 bleedingedge, lagfix, XIX,ec09 radio., 40heap,ondemand, bfq, oc 200-1200,Uv, zram96,honeycomb theme,mem opt
[Fascinate Android Development] droidstyle:
haha hell yes they do! finally mtv is worth watching again because its drastically gone down hill.
[Fascinate Android Development] vshand:
Can I say amko releases locked memory by killimg apps and recover leaked memory, zram add some virtual memory?
[Fascinate Android Development] sendan:
I really don't see how you "need" a memory optimizer. I use my phone quite a bit and exerperience zero system bog downs, zero locksups...nothing. The default memory manager works perfectly if you ask me, try a different kernel.

And although a low dalvik heap may "speed up" your phone, that's what is going to end up causing system lockups. There's a reason it was set to 80, although I have had very good stability with 64MB.
[Fascinate Android Development] laureanop:
It does the same thing that android low memory killer does, but more efficiently on TW roms.

Imoseyo has an extended explanation of what zram is over at" the other guys", but basically yes

TSM Resurrection 1.0,TKSGB10-27 bleedingedge, lagfix, XIX,ec09 radio., 40heap,ondemand, bfq, oc 200-1200,Uv, zram96,honeycomb theme,mem opt
[Fascinate Android Development] vshand:
If so, we need both amko and zram yo avoid reboot before a new kernal implememted memory optimizer. So far both lean kernal and 1027 can not stop memory leaking, if not use amko, rebooting can not be avoid.
[Fascinate Android Development] laureanop:
Zram is not necessary, we're still trying to quantify the benefits we get from it. The memory optimizer

is a must for ram performance and to avoid lock ups and re boots. A memory leak is something different

TSM Resurrection 1.0,TKSGB10-27 bleedingedge, lagfix, XIX,ec09 radio., 40heap,ondemand, bfq, oc 200-1200,Uv, zram96,honeycomb theme,mem opt
[Fascinate Android Development] vshand:
I checked before, amko can defragment, and recover leaked memory. Without these functions,killing apps can't release memory fully.
[Fascinate Android Development] sendan:
Have you even run this ROM completely stock before assuming memory optimizer is COMPLETELY necessary? because it's not, in fact it runs perfectly fine. I'm guessing the problem lies with one of your kernel settings, completely unnecessary tweaks like XIX, or low heap size.

Unless you give some solid DATA, please stop spewing how necessary it is. All I see here is a fix completely unrelated to the actual ROM.
[Fascinate Android Development] laureanop:
I ran imoseyo' s kernel with no lag fix last Saturday and TKSGB no lag fix on Sunday with and without memory optimizer. Performance as far as speed and snappiness was far inferior without lag fix than with. Since benchmarks don't seem to matters(which by the way lag fix scored way, way higher on the four that I ran) you gotta take my word for it.

On all the kernels , zram, lag fix combinations that I ran the phone would invariably become bogged down after 6-7 hours of use. The only thing that fixed this was the memory optimizer.

This has been the case with EVERY TW Rom I've used in this phone.

The heap size adjustments will vary with each phone and the type of apps you run, which was concluded at the very beginning of the heap size discussion.

Don't ask me not to express my educated opinion on these subjects. If you don't like it go ahead and disagree with it.

I never like the tone of your posts, so the only SOLID thing that I have to give you right now is my middle finger pointing at a perpendicular angle to the sky

TSM Resurrection 1.0,TKSGB10-27 bleedingedge, lagfix, XIX,ec09 radio., 40heap,ondemand, bfq, oc 200-1200,Uv, zram96,honeycomb theme,mem opt
[Fascinate Android Development] bestchoicedon:
Hehehe. By the way I tried the stock kernal and gee wiz kernal and at some point in the day I also end up with the bogged down non responsive phone. This probably wouldn't be such a topic of discussion if others weren't experiencing it too. Something is sneaking around in my phone and stealing my ram. Errrr
[Fascinate Android Development] sendan:
I asked you if you ever ran this ROM stock and all you tell me is you tried a bunch of other tweaks and you and had the same result...? Okay, that's good to know...I guess?

I'm saying your lock-up problem has NOTHING to do with this ROM, hence it doesn't belong in this forum.

And as for your uneducated opinion, all in all the only people it "helps" (lol) is the pack of casual users that follow you like sheep. (Probably because you spew it so much on these forums it's impossible to avoid)

xda-developers.com - What a joke.
[Fascinate Android Development] Dj-Dubster_TN:
L..O...L
[Fascinate Android Development] laureanop:
Ram, kernel, Rom, tweaks and their interactions with each other are part of how the rom we're running performs.

How about we have 6 million different threads so everything can be in its neat, correct place?. We're taking the "wrong thread thing" a little too far.

Lastly, you and your miracle Samsung phone don't have to read or try anything that I say.

TSM Resurrection 1.0,TKSGB10-27 bleedingedge, lagfix, XIX,ec09 radio., 40heap,ondemand, bfq, oc 200-1200,Uv, zram96,honeycomb theme,mem opt
[Fascinate Android Development] sendan:
My point doesn't have anything to do with "tidiness," it's to find the problem and fix it. Do some actual troubleshooting and figure out what is causing the problem, and post in THAT thread so it can be addressed and fixed. I've put this ROM on 3 fascinates (Sister's, and Mom's) and none of them have lockups, random reboots, or a bogged down system. I find it hard to believe you're THAT incompetent, but keep posting and we'll find out.
[Fascinate Android Development] bestchoicedon:
Have you used titanium backup on any of the phones you mentioned
[Fascinate Android Development] sendan:
Two out of the three phones have used Titanium Backup, why?
[Fascinate Android Development] bestchoicedon:
Just trying to figure out if restoring apparel might be causing the problem
[Fascinate Android Development] FDro:
I dont really want to get into this argument, but I am going to chime in something from personal experience. My phone runs better on the stock kernel than on the lean kernel or TKSGB kernel. Both "aftermarket" kernels end up giving me a bog down much faster than what I've experienced on the stock kernel...just an observation, having run both options with and without voodoo over several days.
[Fascinate Android Development] MattRussNC:
As much as hate to say this I have to agree with the better performance with stock. I am currently running tks 10/27 with voodoo and thinking of going back to rfs and leaving every thing as is. I have used pwgb with stock settings and kernel with amazing results and have no doubt this rom would be the same under the same conditions. I fully respect and appreciate the work put into the custom kernels and acknowledge the effort given to them. However the best I've seen with any so far its simply stable. Never has my particular phone performed better then with the stock kernel and settings with pwgb (again I'm sure out would be no different with this ROM). If not for bln I would and still may revert back to rfs. Heap size is the only tweak so far that i have seen to have any merit for my device. In my case all these extras have only fixed one issue by causing two others.

This is just my uneducated guess, I think all of the reboots are from either your gov, sch, uv, or oc, not so much the other tweaks. However the lags, freezes, and fcs are from memory optimizers, and the little tweaks here and there.

Not taking sides in a argument. Only thought to express my own experience so far.
[Fascinate Android Development] jcurley:
I don't take sides in these arguments either. These are opinions and you know what they are like. Remember, I am no developer, I just try to help report the bugs that I experience.

I have been also playing with different configurations on this rom and others. The akmo does a great job for my phone and my wifes (running pw). I ram stock kernel on both and they bogged down without any other mods.

My wifes Phone got so bad she freaked on me. I installed pwgb on hers before any other roms or kernels where out yet.

Since I added amko, she has not had an issue.

Now with that, when I constantly closed my own programs with a task kilter I did not have any problems, but that is just doing akmo's job, now I don't have to focus on that. I ran insoymen kernel and had reboots before the sd scan even finished if I tried to do anything with the phone.

This is my take on this phone. This does not mean I am right or wrong, this is just the set up that works for me. Since running a similar set up to learenop, my phone is stable. and this rom is great.

We are just trying to help those people that are getting the same issues that have had with this rom, since ninjst had not had the same issues. This goes back to certain kernel settings work for done and not others, we all have the same phone, but the can all function just a little different. That is why the rom was built with heap of 80, but done work with 40. Tsm released it to everyone so it worked for everyone. Not just a few.

Remember, (showing my geek side) the needs of the many out weigh the needs Of the few, or the one.
[Fascinate Android Development] laureanop:
@nitsuj 17 and other members. My apologies for carrying on with this argument in this thread. If anyone's interested I opened a thread in the general discussion section

TSM Resurrection 1.0,TKSGB10-27 bleedingedge, lagfix, XIX,ec09 radio., 48heap,ondemand, cfq, Uv, zram96,mem opt
[Fascinate Android Development] bobloblaw1:
Quick question. Do people on the stock version, for this rom have an issue where their touchscreen will stop responding until it is cycled on and off.

I can't remember if it did this prior to flashing leankernel. So I'm considering flashing back but am curious if it will be worth it.
[Fascinate Android Development] jcurley:
I do believe that is a bug in the Rom/tw gb. I think that is a regular bug.

tsm 1.0

tks 10/27 bleeding edge

Memory optimizer optimal

XIX

lagfix enabled

Honeycomb

Zram 64

Heap 48
[Fascinate Android Development] darkmage1991:
yep, i have that on both pwgb and tsm. it gets annoying at times. but it only really happens to me in certain apps, but im gonna add on to the discussion of mem optimizer, its not needed and same goes with the adrenaline shot. now if you never close your apps that you open then any phone will bog down so the best mem killer is easy, just close the apps when your done :)
[Fascinate Android Development] jcurley:
Only one problem with that. I do close every app I use. That does not prevent other apps that I have that restart every time I shut them down.

Google talk or voice. Gmail, maps, vlingo, facebook, my verizon, tikl touch to talk.

These apps will run without me ever touching them. Those apps alone are a lot of ram, then add what ever else wants to run in the back ground.

Maybe the akmo is best used depending on the apps you have on the phone. some people may not have this issue, since they do not have the same apps.

Again, every phone is different, what may work for me,.may not be needed for you and vise, versa.

tsm 1.0

tks 10/27 bleeding edge

Memory optimizer optimal

XIX

lagfix enabled

Honeycomb

Zram 64

Heap 48
[Fascinate Android Development] sendan:
It takes a mediocre understanding of how android actually works to comprehend this, but by not closing apps you're not using any (or very much) extra ram in most cases.

http://developer.android.com/guide/topics/fundamentals/activities.html

This is why I don't understand 3rd party task killers, it just messes everything up in most cases when a perfectly good system is already in place.
[Fascinate Android Development] bobloblaw1:
This is a wild theory but I think the touchscreen responsiveness issues may be tied to the accelerometer or more accurately when a program polls the accelerometer excessively. Try to install an app like screbl which relies on the accelerometer and screen freezes will get much more common.

Edit: I don't think it's the accelerometer anymore as other programs that use it don't seem to have the issue. Perhaps the problem is apps that were written for earlier versions of android and don't handle certain events as gingerbread expects.
[Fascinate Android Development] sendan:
When looking at a logcat is seems pretty clear it's incompatible touchscreen drivers.
[Fascinate Android Development] laureanop:
Do you mean the one implemented to make Bln work?

TSM Resurrection 1.0,TKSGB10-27 bleedingedge, lagfix, ,ec09 radio., 64heap,smartassv2,deadline, Uv, zram,, no Uv, no oc
[Fascinate Android Development] sendan:
Err, no I don't think so. I don't know what that is.

Djp has far more knowledge on the problem, but I don't think he has had any luck getting a different driver to work. Or he hasn't tried yet, not sure.

Sent from my Samsung Fascinate
[Fascinate Android Development] darkmage1991:
it isnt related to the accelerometer , the reason i say this is cause i most frequently get it when playing the scre4m game, and that game doesn't use the accelerometer at all.
[Fascinate Android Development] ibrubeer:
Just a question, but how would a person go about getting the "stock" ROM if they wanted it anyway?

TSM Resurrection 1.0, TKSGB10-27 bleedingedge, lagfix, XIX, ec09, 64heap, noop, ondemandx, 200-1000, Uv-50, mem opt, zram 44372.
[Fascinate Android Development] bobloblaw1:
I didn't nt think verizon released it so you aren't going to be able to get a verizon stock. You could get the pure USSC release but you will lose things like data and mms.

I'm pretty sure PWGB or Geewiz are about the closest you can get to stock gb and still have everything work.

As for the touchscreen freezes, certain apps make them much more common. Screebl is a big offender and won't last longer than a minute or so without a screen responsiveness issue.
[Fascinate Android Development] laureanop:
You can't really get 100 per stock ei 20 because is not a VZW Rom. To make it work for our phones it needs apn and other modifications. The closest to stock would be gee wiz

TSM Resurrection 1.0,TKSGB10-27 bleedingedge, lagfix, ,ec09 radio., 64heap,smartassv2,deadline, Uv, zram,, no Uv, no oc
[Fascinate Android Development] joebob2000:
With this version (compared to PWGB) the screen lock-ups have gone from needing to cycle the screen on/off to actually causing the phone to completely reboot (or maybe being a result of a pending FC-reboot taking place). :(
[Fascinate Android Development] laureanop:
Those of you having re boot issues: are you guys using the 4tab lock screen?

TSM Resurrection 1.0,TKSGB10-27 bleedingedge, lagfix, ,ec09 radio., 64heap,smartassv2,deadline, Uv, zram,, no Uv, no oc
[Fascinate Android Development] mising:
No, I am using the Pulldown one. I don't have my phone on me right now, so I cannot verify the actual name. The only time I get a freeze/re-boot is if I open a browser and try to scroll, zoom, or even just touch the screen before the page finishes loading. I can recreate it nearly any time. If I can remember, I will try and get a logcat when I get home.
[Fascinate Android Development] sfd0124:
I was getting the exact same lockup with web pages loading. It happened with lean kernal and tks kernal. I reflashed 2 days ago and am running the stock kernal. The freezing and rebooting while web browsing appears to have stopped.
[Fascinate Android Development] jcurley:
I am using 4 tab with no issues.

I get an occasional reboot, but I think it happens when I am not even using the phone. Today, got to work, turned off my 3G (service at work is horrible, so I do this to save battery) and boom, reboot.

Not sure why, maybe had something to do with me cycling off the 3G, but this is the first time it has done that just turning off the network.

So I am lost on that one.
[Fascinate Android Development] nitsuj17:
while i think the occasional hot boot (better/worse on some people unique set ups) will never be gone or killed completely...we are at least aiming to put heap size selection in the next version to make it easier for people to change the heap size on their own and experiment

would be in tsm parts when done with multiple selections (ie 32, 48, etc etc)
[Fascinate Android Development] sendan:
So after pushing a themed framework-res.apk I'm working on I lose access to anything that requires data. "An error has occurred during sign in. Please try again later"

Have you seen this issue before? :(

Sent from my Samsung Galaxy Tab 10.1
[Fascinate Android Development] nitsuj17:
what theme was it from and what version?
[Fascinate Android Development] sendan:
I just compiled it from the latest TSM res, all I did was some hex color edititing and changed a lot of pngs. I'm pretty sure I didn't screw anything up.

Sent from my Samsung Galaxy Tab 10.1
[Fascinate Android Development] nitsuj17:
and it killed data?...heh strange

what version of apktool are you using (not that is should matter)

did you replace the manifest from the original file..and meta folder?
[Fascinate Android Development] sendan:
Version 1.4.1

And ya I replaced both the manifest and meta folder....hrmmm....

Oh well, I'll try flashing it in a bit, maybe pushing it directly to system screwed **** up.

Sent from my Samsung Galaxy Tab 10.1
[Fascinate Android Development] grenade01:
Roms still running great on stock kernal for me as did the last version. Never a reboot, no lock ups or sluggishness. I did use Titanium to restore non critical apps. No screen unresponsiveness for me either. I froze many more of the apk's with titanium such as the car dock and DLNA pretty much everything I could because I hardly use any of those features. No problem with maps either. Glad I'm not having any of the problems you guys are because I love this rom!
[Fascinate Android Development] sendan:
I guess the problem was being caused from using ADB wireless. (damn I thought that was really cool)

Actually had to re-flash the ROM...it really screws something up, but everything works now.
[Fascinate Android Development] bestchoicedon:
When I use the search button on the phone to browse the web. No matter how many pages I go to as soon as I hit the back button it goes all the way back to the main search screen that opens when you I initially hit the search button on the bottom of the phone. All other Rome would back me out one page at a time. It leaves me with no way to go back a page at a time plus I have no idea if all the pages I open are actually closing out or just running in the back ground. I'm not a rev but could that contribute to the phone getting slower and slower over time. I am only running the kernal that is from pwgb as I flashed this rom from that one.
[Fascinate Android Development] laureanop:
I know what you're talking about. Very annoying

TSM Resurrection 1.0,TKSGB10-27 bleedingedge, lagfix, ,ec09 radio., 64heap,smartassv2,deadline, Uv, zram,, no Uv, no oc