[Q&A] Q&A Thread for Evervolv Jellybean builds

Bexton

Senior Member
Sep 26, 2011
643
1,128
0
50° 56' 33" 6° 57' 32"
To keep the development thread clean, this thread is meant to post any questions with regards to Evervolv's Jellybean builds for your Nexus One, such as "Has issue X been solved in build Y?", or "I have a problem X. Is anybody else experience the same?". The kind users on XDA will try to answer all your questions, or point you to the relevant location to solve/address your issue.

For general discussions about the Rom, please use this thread: http://forum.xda-developers.com/showthread.php?t=1795954

Please don't forget to include as much details as possible to any questions (build number + release date, steps to reproduce the issue etc.).

Before you post a question, you should

1.) Search this thread
2.) Search the development thread: http://forum.xda-developers.com/showthread.php?t=1762790

if you can find an answer for your question.

Before you post any questions with regards to a problem you're facing, you should

1.) Search this thread
2.) Search the development thread: http://forum.xda-developers.com/showthread.php?t=1762790
3.) Search the Evervolv Code review site: http://review.evervolv.com/#/q/branch:jellybean,n,z

to check if there's already a solution that is not mentioned in OP, or if the issue was filed and/or a fix is pipelined by the developers already.

Thanks for helping to keep everything clean! :)
 
Last edited:

Bexton

Senior Member
Sep 26, 2011
643
1,128
0
50° 56' 33" 6° 57' 32"
I hate to start off this thread with such a base question...but I just got a Nexus One and flashed this ROM. Wondering if anyone has a kernel suggestion to maximize smoothness...
First off, thanks for posting to the correct thread! :p ;) Now, to answer your question: Since this Rom is in a real early stage development phase, there're a few "hacks" implemented to get things running. Personally I didn't tried to flash another kernel, nor am I a kernel dev. However, to ensure functionality it might be the best choice to stay with the released kernels for the moment. I know that's not the answer you wanted, but just my 2 cents. ;)

Edit: Especially because you were asking for "smoothness".. The Evervolv team is working to the graphic related stuff "with priority". Many libs are broken or partitially incompatible. So I think another kernel won't change anything with regards to "smoothness". But we can expect updates on that soon.
 
Last edited:

mtmjr90

Senior Member
Aug 4, 2011
181
27
0
San Jose, CA
plus.google.com
First off, thanks for posting to the correct thread! :p ;) Now, to answer your question: Since this Rom is in a real early stage development phase, there're a few "hacks" implemented to get things running. Personally I didn't tried to flash another kernel, nor am I a kernel dev. However, to ensure functionality it might be the best choice to stay with the released kernels for the moment. I know that's not the answer you wanted, but just my 2 cents. ;)

Edit: Especially because you were asking for "smoothness".. The Evervolv team is working to the graphic related stuff "with priority". Many libs are broken or partitially incompatible. So I think another kernel won't change anything with regards to "smoothness". But we can expect updates on that soon.
Ah, thanks for the info. I got the N1 to play with and with a Galaxy Nexus as my primary device I can really feel the difference...which was of course expected;) I obviously haven't followed Evervolv's development in the past, just out of curiosity, how frequent are releases in general? I'm running AOKP on my GNex and they release approx every other week, so I'm hoping for something similar here.
 

Bexton

Senior Member
Sep 26, 2011
643
1,128
0
50° 56' 33" 6° 57' 32"
Ah, thanks for the info. I got the N1 to play with and with a Galaxy Nexus as my primary device I can really feel the difference...which was of course expected;) I obviously haven't followed Evervolv's development in the past, just out of curiosity, how frequent are releases in general? I'm running AOKP on my GNex and they release approx every other week, so I'm hoping for something similar here.
Probably the best answer to get, is by looking at the release history of the Evervolv TexasIce Cream Sandwich thread (post 2 & 3): http://forum.xda-developers.com/showthread.php?p=19785288#post19785288

But don't expect weekly updates. Updates come, as Texasice think that it's worth to bump to a new build.

I didn't followed any AOKP projects.. But I know that some devs publish new builds for "every" commit they push to their repos to keep users up to date with the latest stuff. However, Evervolv is a small team of 3 devs and Texasice, who works on N1 stuff, additionally works on other devices and other stuff as well. From what I can see, he's pushing new releases when "something big" was fixed, or was improved, but not for every tiny change.

However, they build nightlies, too. So if you want, you could update every morning. ;) But a better idea would be to follow the progress via their code review site and if you see any commit which you think you would like to have that, go ahead and grab the next nightly.

All Jellybean commits: http://review.evervolv.com/#/q/branch:jellybean,n,z
Jellybean commits that have been merged: http://review.evervolv.com/#/q/status:merged+branch:jellybean,n,z

Finally, you can find the source at GitHub and build yourself as often as you want. ;) https://github.com/Evervolv
 

mtmjr90

Senior Member
Aug 4, 2011
181
27
0
San Jose, CA
plus.google.com
Lots of questions coming from me today I'm afraid... I am curious what everyone is doing to solve the Insufficient Space error. I posted a general question in the Q&A forum but I don't know if there's any particularities resulting from being on JB rather than GB (CM7).
 

thrik

Senior Member
Jun 10, 2010
193
43
0
Lots of questions coming from me today I'm afraid... I am curious what everyone is doing to solve the Insufficient Space error. I posted a general question in the Q&A forum but I don't know if there's any particularities resulting from being on JB rather than GB (CM7).
There are no peculiarities to JB that I know of. All I had to do was enter a2sd install in Terminal (after getting SU there first). I assume you already had an sd-ext partition on your SD.
 
  • Like
Reactions: tuesdaydev

mothor

Member
Jul 27, 2012
9
1
0
Hey guys....loving the Jelly Bean experience so far!!
Real silly question here...but what do 0p1, 0p2, 0p3 mean on the nightlies. Is it just releases?
Also is there somewhere we can see what changes are made to each nightly release?

Thanks!
 

Bnorus

Member
Jun 1, 2010
26
6
0
22.3 N,114.2 E
Hey guys....loving the Jelly Bean experience so far!!
Real silly question here...but what do 0p1, 0p2, 0p3 mean on the nightlies. Is it just releases?
Also is there somewhere we can see what changes are made to each nightly release?

Thanks!
It is version 3.0.0
p stands for pre-alpha (see it as pre-release) and the build number :) The JB build is just beginning TexasIce will come up hopefully soon with an alpha build once all the merging is completed :p
 
Last edited:

seinjunkie

New member
Dec 2, 2011
2
1
0
bitshift.tumblr.com
I'm coming from ICS as my daily driver, but hesitant on JB just yet.

Is the included Apps2SD working with xdata like the ICS version? I know that was an experimental feature, but it always works better for me than the normal install did.

Thanks,
-sj
 

mtmjr90

Senior Member
Aug 4, 2011
181
27
0
San Jose, CA
plus.google.com
I'm having serious stability issues and I just want to confirm what causing them...namely is it the ROM or perhaps a hardware issue. I've had the ROM set up and running three times now and each time (once over night, twice just having it sit around for an hour or so) it just freezes up and when I battery pull to reboot, almost all of my apps and settings have been erased. I've used the built in a2sd to move apps and dalvik to sd-ext, dunno if that could be part of the problem... Anyone else have similar issues? I'm thinking if it's not the ROM, it could be corrupt storage or something.
 
This is more in response to your rant on the development thread than in relation to the ROM directly, but I was thinking it would possibly reduce the amount of posts about stuff not appropriate for the development thread if you could put a warning to come up when someone is writing a post for the thread asking if what they're writing is going to contribute to the development of the ROM and with links to this and the discussion thread suggesting them as more appropriate places to post. Dunno if that's possible, or if someone like you with lots of posts could suggest it as a solution to this problem that plagues so many threads?

Sent from my Nexus One using xda app-developers app
 
  • Like
Reactions: KoolPal
Another question which is more directly related to the ROM.
Is it possible for an option to be added to remap the soft keys? Such as remapping the search key to be a multitasking key as is in actual ICS phones?
I know I personally hardly ever use the search key but often use the multitasking features which would make it awesome to have that functionality!
Just a thought, thanks if you implement it!

Sent from my Nexus One using xda app-developers app
 

altruistic666

Senior Member
Jan 18, 2011
353
81
58
Brussels
Just wondering when TI will release next build. Am having trouble with notifications. I have pushed all the libs but still the video playing is broken. I really don't know what bexton has fixed but p1 with all fixes was just awesome. I know TI will incorporate all those stuffs so just waitimg eagerly for a p3.


Sent from my Nexus One using Tapatalk
 

vimitake

Senior Member
May 18, 2011
68
5
0
I don't know if it's a bug or not... sometimes screen display doesn't turn off but phone is asleep (I think). See the lockscreen but doesnt respond to touchscreen. Works fine once I wake up phone with power button. On latest nightly(7/27).

Sent from my Nexus One