FORUMS

Analysis & Opinion

Top Forum Discussions

[ROM] Evervolv | 3.2.0p1 [AOSP]

558 posts
Thanks Meter: 1,723
 
By preludedrew, Recognized Developer on 29th October 2012, 08:19 AM
Post Reply Subscribe to Thread Email Thread
17th February 2013, 06:25 AM |#661  
Mazda's Avatar
Recognized Developer
Flag Milton, Florida
Thanks Meter: 11,325
 
More
Arrow Wallpaper


ENJOY!!
 
 
17th February 2013, 01:00 PM |#662  
88exp88's Avatar
Senior Member
Thanks Meter: 273
 
More
Re: [ROM] Evervolv | 3.2.0p1 [AOSP]
Big change log today, some of it pertaining to us. Check it out.

Sent from my PC36100 using xda app-developers app
The Following User Says Thank You to 88exp88 For This Useful Post: [ View ]
18th February 2013, 09:27 PM |#663  
dieselford's Avatar
Senior Member
Flag Tampa, FL
Thanks Meter: 870
 
More
Re: [ROM] Evervolv | 3.2.0p1 [AOSP]
Quote:
Originally Posted by 88exp88

Big change log today, some of it pertaining to us. Check it out.

Sent from my PC36100 using xda app-developers app

Seems to have a lot going on in the past week. Anyone been running any recent builds? Curious if there is noticeable improvement or not

Sent from my PC36100 using Tapatalk 2
18th February 2013, 09:37 PM |#664  
NxNW's Avatar
Senior Member
Thanks Meter: 517
 
More
Re: [ROM] Evervolv | 3.2.0p1 [AOSP]
The most recent bunch had a lot of camera-related items.

I don't honestly believe the Evo is capable of "zero shutter lag", but "zsl burst mode" was mentioned in one of those commits (i commented on it weeks ago, then it was abandoned, then it re-appeared, and now it's been merged) and I'll be curious to know if it applies to us.

Of course if any of those other items fixes the phone FC issue, that would be a real game-changer...

Sent from my PC36100 using xda app-developers app
19th February 2013, 05:57 AM |#665  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by NxNW

I answered my own question: still FC's..

Sent from my PC36100 using xda app-developers app

Me too. I use the nightly 2013.02.14 version.
the phone often FC when end the call.
19th February 2013, 06:05 PM |#666  
Senior Member
Bryan, TX
Thanks Meter: 7
 
More
Working OK here so far. Camera still wigs out, but I'm used to that.
19th February 2013, 07:36 PM |#667  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by quicktimex

Me too. I use the nightly 2013.02.14 version.
the phone often FC when end the call.

The 2.14 build was too laggy for me but 2.18 works as daily driver. Also installed the Mazwoz GPS fix which stabilized the GPS
19th February 2013, 09:39 PM |#668  
NxNW's Avatar
Senior Member
Thanks Meter: 517
 
More
the one thing no one said in the last few posts was whether the *2/17 nightly* fixes the phone FC's when the far side hangs up first.

i did see a commit that specifically addressed phone audio but not phone crashing per se.

guess i'll have to flash it which i enjoy doing just haven't had the time
20th February 2013, 12:45 AM |#669  
Senior Member
Bryan, TX
Thanks Meter: 7
 
More
Quote:
Originally Posted by lijujg

The 2.14 build was too laggy for me but 2.18 works as daily driver. Also installed the Mazwoz GPS fix which stabilized the GPS

Is that GPS fix still needed with the recent builds?
20th February 2013, 07:54 PM |#670  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by Coldfirex

Is that GPS fix still needed with the recent builds?

i had flaky GPS performance without it. As I use Waze quite a lot, I reinstalled the fix and that resolved it.
20th February 2013, 08:13 PM |#671  
Member
Thanks Meter: 8
 
More
Quote:
Originally Posted by NxNW

I suppose the sound issues described above could explain why my alarm clock lights up but emits no sound *sometimes*.

I'm still on the Feb 3 nightly, but I just started having stock alarm clock problems too. Specifically, when the alarm goes off, the screen turns on but there is no sound or vibration. I turned all my volume levels up and tested it again, but it didn't help (and the lack of vibration seems to be an indication of a deeper problem anyways).

After some googling, I decided to force stop + clear data on the Clock app. I then added a new test alarm, and it worked!

The problem is that I'm sure it will get into that state again. Maybe I will upgrade to the latest nightly and hope for the best, but it sucks being 15 minutes late to work

If it happens again, I'll probably try a third-party alarm clock app, as I'd rather not have to clear data on the clock app every night just to be safe
The Following User Says Thank You to HunterZ0 For This Useful Post: [ View ]

Read More
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes