• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Viper 4G 2.0.0 and beyond

I've been having a lot of randon little bugs and glitches. Stock kernel BTW. Only optional install was Google Now.

I performed the usual dalvik and cache partition wipes, I also fixed permissions. PRL and data profile updates before wiping anything, no dice.

I downloaded the full version of 2.0.2 and I dirty flashed it. Bad idea, I know better. LOL

I had a dead phone in 6 hours, and location for my weather was showing indiana all day. Random force closures, etc. I full wiped and reflashed, going to see how it behaves tomorrow.
 
So I know this should go in the kernel's forum, but the traffic there seems to be light. Hoping I might get some help here.

I'm s-off on viper4g 2.0.2 and flashed the Anthrax kernel. I wiped cache and dalvik before flashing. After flashing Facebook kept stopping on me. I tried clearing Facebook's cache/data and rebooting and that seemed to stop the FCs, but now Facebook calendar can't sync. Any ideas?

Oh, btw what exactly does fixing permissions do?:confused:

Thanks!
 
EarlyMon said:
Here's your best explanation for fixing permissions -

https://play.google.com/store/apps/details?id=com.stericson.permissionfix

Viperboy has posted a few patch files and hints to combat various fc and multitasking issues, don't know if you want to check for those.

There are a number of FB / Sense complaints that go away by removing and re-entering your FB credentials.
Click to expand...
Thanks for the info.

Tried signing out and back in to FB, but it still said sync is currently experiencing problems. Tried updating FB with the same results. Any other ideas? At least I'm not getting fcs, but annoying I can't get syncing to work.:(
 
Glad to see some people posting in here again. I just signed on to see what was going on, i.e. to see if everyone had abandoned ship and moved on to a different ROM. I still haven't upgraded to the new Viper4G just because of all the possible issues that I have been reading about on here.

Any idea when this stuff is supposed to be updated or what better ROMs are available right now (with the same or better customizability options)?
 
CriticalCritic said:
Glad to see some people posting in here again. I just signed on to see what was going on, i.e. to see if everyone had abandoned ship and moved on to a different ROM. I still haven't upgraded to the new Viper4G just because of all the possible issues that I have been reading about on here.

Any idea when this stuff is supposed to be updated or what better ROMs are available right now (with the same or better customizability options)?
Click to expand...

I'm still using it and loving it!
 
It's been a really good rom for me (tried fresh, then used mean for several months). I love all the customization options for this rom, just waiting for racun to be stable, my wife wants it, she s-on hboot 1.19.
 
The updates in general are done, but they are testing memory management adjustments. Each iteration takes several days to test.


People with different configurations report various results over time, such as lag creeping in to dialer for example. There is no single set of symptoms but they think it's in the memory management. And viperboy has shared various pieces for people to try, so it's not all a closed doors thing.

This is looking interesting from what I have read -

http://androidforums.com/evo-4g-lte...-svn-superlte-r145-8-5-12-xda-developers.html
 
SamuraiBigEd said:
When doing this do I allow it to overwrite the existing mail.api?
Click to expand...

O.o

Is that a swipo? Did you mean Mail.apk?

I froze mine by renaming it to Mail.apk.bak - because I hate doing nandroids when I don't have to rely on them.

Because of the name change, I had no overwrite conflict.

After all - I think I tested it all, but if I didn't, that way you can blow away the new one, rename Mail.apk.bak to just Mail.apk, clears both caches and reboot and Bob's your uncle. :)
 
EarlyMon said:
O.o

Is that a swipo? Did you mean Mail.apk?

I froze mine by renaming it to Mail.apk.bak - because I hate doing nandroids when I don't have to rely on them.

Because of the name change, I had no overwrite conflict.

After all - I think I tested it all, but if I didn't, that way you can blow away the new one, rename Mail.apk.bak to just Mail.apk, clears both caches and reboot and Bob's your uncle. :)
Click to expand...

Yep, fat-fingered the keyboard. Thanks!
 
Let's see if I can go 3 for 3 :)

EarlyMon at XDA said:
On multitasking -

http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/

I note that we're running the ICS defaults for vm.heapsize and growth limit, appropriate for a phone with 1 GB of ram.

But we have less than a gig, as I recall, the S4 is mapping ram for i/o ports and also for the gpu.

In any case, we're all used to seeing 680 MB of ram, far less than a 3vo.

So now, I've changed my /system/build.prop like so -


# For ICS project, default 32m/48m
# 128/64 originally below
dalvik.vm.heapsize=96m
dalvik.vm.heapgrowthlimit=40m


And I am seeing two things -

One, ram now reports as 770 MB.

Two, my phone is screaming fast.

This is all very preliminary. Try at your own risk, make a nandroid backup first.

I would like to hear from anyone with lag issues willing to try this.

I'll be trying everything I can think of to stress test and will report back. :)

PS - tip of the topper to Wes and his report about having to kill Chrome. When I think of browsers, I think about core leaks and garbage collection, that's what gave me the idea.

I figured we had less than 70% of 1 GB ram, so a sloppy approximation of that on 64 gave me 40, and that article said the next should be double or more, so 96 sounded fair enough to me. That's how I chose my numbers, if anyone cares.
Click to expand...

Viperboy commented that he was getting ready to post similarly and encourages people to try this.
 
You must log in or register to reply here.
Back
Top Bottom