Big change log today, some of it pertaining to us. Check it out.
Sent from my PC36100 using xda app-developers app
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.
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
i had flaky GPS performance without it. As I use Waze quite a lot, I reinstalled the fix and that resolved it.
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).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
I wonder if it could be triggered by the phone app force close issue?I think this is having the same issue as Mazwoz 4.2.1 Rom as they come from the same source, but the sounds is routing through the headset speaker, rather than through the speaker phone. Something is toggling it under certain situations. for me when I go from bluetooth in my car to sitting in my office I turn bluetooth off and it routes sound through the earpiece speaker, and then I have to use sound about and click the headset recognition toggle in an app called sound about, or run a music player and toggle it to fix it. Then it is good until the situation with bluetooth or sometimes after completing a phone call. Don't know what to capture when it's happening to help though.
Where is the copy of the 4.2.2 gapps at?
Sent from my PC36100 using xda app-developers app
Where is the copy of the 4.2.2 gapps at?
Sent from my PC36100 using xda app-developers app
There isn't one. The 12/12 version works fine.
Sent from my PC36100 using xda premium
Haven't posted here in awhile, and I've got 3 other devices to post for tonight so this is gonna be short and updated later.
Right now the current source we are working on is Jellybean (Android 4.2.x).
For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Current version: 3.2.0p1
Downloads:
Evervolv releases
Evervolv nightlies
Below is the "Not working" or items that are buggy list. I'm going to keep it short and simple for the time being and let ya'all figure bugs out, and I will update this.
Items that need attention: (Not working or buggy)
** Resetting for 3.2 release **
GPS?
Here's a couple links to keep in mind:
My twitter: @preludedrew
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
(The website has not been updated since our gingerbread builds... I know I know.)
IRC: #evervolv
[GPL Compliance]
Kernel Source: https://github.com/Evervolv/android_kernel_htc_qsd8k
Or maybe since the end of the world is near they said screw it why even bother
In all seriousness, Evervolv is available on multiple platforms. Some may take longer to get working than others. Grouper and Manta are the Nexus 7 and Nexus 10 devices, which already has the 4.2.x upgrade so of course those would be one of the first to get this ROM. In regards to our specific device, only the Evo LTE and Evo3D have had theirs released by @preludedrew. And of those two the LTE version was pulled due to connectivity issues.
To all who want to know when our device gets a release:
1.) Download Twitter or some variant
2.) Follow @preludedrew
3.) Patiently wait for him to say when it is available.
Any available release would be posted on his Twitter feed before here.
[01:07] <@preludedrew> CaptainThrowback, supersonic enabled on nightlies