Database Develop

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

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!

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...

mtmjr90 said:
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...
Click to expand...
Click to collapse
First off, thanks for posting to the correct thread! 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.

Bexton said:
First off, thanks for posting to the correct thread! 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.
Click to expand...
Click to collapse
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.

mtmjr90 said:
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.
Click to expand...
Click to collapse
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

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).

mtmjr90 said:
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).
Click to expand...
Click to collapse
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.

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!

mothor said:
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!
Click to expand...
Click to collapse
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

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

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.

Is butter working in these builds?

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

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

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

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

seinjunkie said:
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
Click to expand...
Click to collapse
i am using the xdata flag everything seems to work in regards to that

With smartassV2 governor the rom is faster without any reboot or similar
Has someone try it?

ironjon said:
With smartassV2 governor the rom is faster without any reboot or similar
Has someone try it?
Click to expand...
Click to collapse
Where do you change the governor? Don't see evervolv toolbox under settings. On 7/27 nightly
Sent from my Nexus One

vimitake said:
Where do you change the governor? Don't see evervolv toolbox under settings. On 7/27 nightly
Sent from my Nexus One
Click to expand...
Click to collapse
I did it with setcpu
Enviado desde mi HTC Desire usando Tapatalk 2

downgrade from CM10.1 nightly to cm9 or 7?

Is there an "easy" or tried and true method to downgrading? CM10.1 is too laggy for my phone. Is 9 any faster or more stable? I was going to downgrade to 7 because I know it works and I don't have any experience with 9.
Thanks in advance.

RE: stable CM
HTCscout said:
Thanks in advance.
Click to expand...
Click to collapse
I don't want to come off as rude, but this belongs among Q&A threads, not Development. Having said that, 10.1 is a work in progress and yes 9 would be more stable. I recommend going back to stock Gingerbread and flashing up from there. There is a stickied thread at the top of this Dev forum with methods to go back to stock Gingerbread (I recommend KK4), or check my signature for links. Happy flashing!

CM10 is stable too, I had it on my phone for about a month with no single issue. Same file system, just flash and ready to go.
In my opinion, no need to downgrade to GB or ICS. I've tried many custom ROMs and JB based give best performance and smoothest UI.

Thread moved to Q and A as this is not a discussion that offers or is development.
Please post in accordance with XDA posting rules.

Thanks for the replies. I posted in the dev section by accident. Thanks for moving my post to the appropriate section. After reading through the threads about GB, ICS and JB I think I'll just stick with CM10.1 and optimize what I have.
Thanks again.
Naddict said:
Thread moved to Q and A as this is not a discussion that offers or is development.
Please post in accordance with XDA posting rules.
Click to expand...
Click to collapse

Try other JB ROMs too. There are many great and stable out there. I'm sure you'll find what you are looking for in less than a week. :victory:

[Q] CM 10.2

Hi All,
I remember that we will not be receiving next major version of Android by CM becoz of lack of NEON instructions. I only wonder, if we will still get CM 10.2 or our last version will be CM 10.1.
Can anybody with CM insider knowledge answer?
I can only see that there was not created CM10.2 branches in our P990 github related repositories, which is bad sign to me.
Edit: Answer is Yes, CM10.1 is last version.

CM 10.1 seems to be the latest official version of cyanogenmod. But just look at all the gifted developers in the development thread. I guess someone will get it working on our device .
I think even some time ago pengus or tonyp mentioned that they like the challenge ....:thumbup:
Sent from my LG-P990 using xda app-developers app

Yes, I have read tonyp's thread and there was mentioned that CM team officially won't support 10.2 for our phone. But I hope Pengus and Tonyp will make something But it's quite possible that it will be a little bit unstable and glitchy...

p.valenta said:
Hi All,
I remember that we will not be receiving next major version of Android by CM becoz of lack of NEON instructions. I only wonder, if we will still get CM 10.2 or our last version will be CM 10.1.
Can anybody with CM insider knowledge answer?
I can only see that there was not created CM10.2 branches in our P990 github related repositories, which is bad sign to me.
Edit: Answer is Yes, CM10.1 is last version.
Click to expand...
Click to collapse
nope it isn't if you watch the developer thread you see cm10.2 only camera doesn't work yet but further it is smooth and stable i am posting this cause you may didn't see it

winstonxl2 said:
nope it isn't if you watch the developer thread you see cm10.2 only camera doesn't work yet but further it is smooth and stable i am posting this cause you may didn't see it
Click to expand...
Click to collapse
Thanks, I know about it. But unfortunately it will not be official CM, only experimental.
It's great that there are still developers who want to keep our device up to date :fingers-crossed: , but looks like it's time to look around for next future device.

p.valenta said:
Thanks, I know about it. But unfortunately it will not be official CM, only experimental.
It's great that there are still developers who want to keep our device up to date :fingers-crossed: , but looks like it's time to look around for next future device.
Click to expand...
Click to collapse
it isn't really experimental only the camera doesn't work and all cm10.1 bugs are included but cm10.2 is smoother and hdmi is partly fixed

rom with camers,stable and fairly easy to install?

main purpose is to install XBMC KODI,its for my daughter,just wondering which one best fits these requirments?thanks.

Been using flintman's Evervolv 5.0.1 with 3.4 kernel (3/11 nightly) for about couple of weeks without any issues. Runs kodi 14.1, some flash, html5, etc fine. Don't expect camera to be as good as it was in webos. It works, but resolution isn't impressive; hasn't been since cm9.
Install is straight forward using touchpad toolbox. Read, Resize, flash. I remove anything I don't need with Rom Toolbox. That includes Google search and launcher, live wallpapers, face unlock, talk back, tts, etc. Doing so makes it a lot more stable for me.
Sent from my Touchpad using Tapatalk

I would say to install something a little more stable than a lollipop (5.0) build. The KitKat builds (4.4) are far more stable and complete so you won't have to do as much troubleshooting and reflashing all the time to fix stuff. I personally run the latest JC Sullins build from January and the performance is far better than what I've gotten from the lollipop builds so far.

patdufo said:
main purpose is to install XBMC KODI,its for my daughter,just wondering which one best fits these requirments?thanks.
Click to expand...
Click to collapse
Questions go in q&a forums. This is for development only.... As is posted at the top.

I thought this was the q&a forum.

gtallmadge said:
I thought this was the q&a forum.
Click to expand...
Click to collapse
This had originally been posted on the development section I believe. It has since been moved by a moderator to the correct location. The notice was to let the OP know for future reference.

(Unofficial) (Nightly) (Not Supported) CyanogenMod 13

I recently decided to do some personal builds of CM for the OnePlus 3. I have seen that the other threads are not updating their builds since they are the ones working on them. I am simply sharing the current builds from the CyanongenMod Repos. I did not do any of the development work and I will kill this thread the moment we get official nightly builds. I am not responsible for anything that may happen and I do not care what does and does not work. You are deciding to flash this ROM. Bugs can be reported to the CM devs but include a logcat or GTFO.
Link to build folder - https://www.androidfilehost.com/?w=files&flid=74080
Instructions:
1. Unlock Bootloader
2. Flash TWRP
3. Fastboot format userdata
4. Boot into TWRP
5. Flash ROM
6. Flash GAPPS
7. Reboot

Thanks for making another ROM for our OP 3

papi92 said:
I recently decided to do some personal builds of CM for the OnePlus 3. I have seen that the other threads are not updating their builds since they are the ones working on them. I am simply sharing the current builds from the CyanongenMod Repos. I did not do any of the development work and I will kill this thread the moment we get official nightly builds. I am not responsible for anything that may happen and I do not care what does and does not work. You are deciding to flash this ROM. Bugs can be reported to the CM devs but include a logcat or GTFO.
Link to build folder - coming soon (waiting on AFH approval)
Instructions:
1. Unlock Bootloader
2. Flash TWRP
3. Fastboot format userdata
4. Boot into TWRP
5. Flash ROM
6. Flash GAPPS
7. Reboot
Click to expand...
Click to collapse
Hehe thanks for this Started building them as well but don't really know how, so made a little guide for others like me Feel free to share your knowledge if you want

build is up

papi92 said:
build is up
Click to expand...
Click to collapse
Downloading...

_MartyMan_ said:
Downloading...
Click to expand...
Click to collapse
Thanks

Thanks for doing this dude. Going to download now. Can finally ditch OOS.
Sent from my ONEPLUS A3000 using Tapatalk

Wooohoo! Everything is working Good job!

_MartyMan_ said:
Wooohoo! Everything is working Good job!
Click to expand...
Click to collapse
Does VoLTE work? I haven't stuck in my T-Mobile SIM lol and i didn't do anything so no thanks to me. It's all @Grarak and @Romanbb

Not trolling but we dont need several twrp, cm, resurrection and so on rom threads here. I believe the mods starting closing these. Not discouraging you from building but several threads just confuse people.

Nah mods don't close it, maybe move it.
It's a nightly build from cm13, did u see a nightly build around? Nope.
Good work, fastest cm13 build around, good to have some nightlys around. Thanks

fix-this! said:
Not trolling but we dont need several twrp, cm, resurrection and so on rom threads here. I believe the mods starting closing these. Not discouraging you from building but several threads just confuse people.
Click to expand...
Click to collapse
These are nightlies. I'm more than happy to close once CM sends the OnePlus into Jenkins.

I really hope this thread doesnt get closed till we see official builds. I know some devs might be mad about this. But since you dont ask for any reward for compiling these builds its ok.

nadejo said:
I really hope this thread doesnt get closed till we see official builds. I know some devs might be mad about this. But since you dont ask for any reward for compiling these builds its ok.
Click to expand...
Click to collapse
Yeah not my work at all. Nor would I pretend it is. Way over my head

So anyone confirm VoLTE is working? I want to switch to T-Mobile once it does.

nadejo said:
I really hope this thread doesnt get closed till we see official builds. I know some devs might be mad about this. But since you dont ask for any reward for compiling these builds its ok.
Click to expand...
Click to collapse
Tbh i dont think alot of devs even have the device in hand yet. thats why im running stock rooted. no offense to the op, wasnt my intention. just been seeing alot of the same threads pop up and its confusing and uneeded. im sure these nightlies are appreciated.

Put up a second build. I saw some commits to snap and wanted to share.

Possible to link the source?
Not that I know where it is, but I'm to lazy to search all the time.
Only thing I noticed is the battery drain compared to stock, not a big one, maybe it need to settle a little.
1 hour SOT 21% on cm
1 hour SOT 14-16% on stock.
Lets see how it settle.
Edit:
Compared to others Roms who looks like they are on a older source, it's running like it should, compared to stock min. the same smoothness, maybe even better.
And I can't test lte because I only have a h+

secXces_debaki said:
Possible to link the source?
Not that I know where it is, but I'm to lazy to search all the time.
Only thing I noticed is the battery drain compared to stock, not a big one, maybe it need to settle a little.
1 hour SOT 21% on cm
1 hour SOT 14-16% on stock.
Lets see how it settle.
Edit:
Compared to others Roms who looks like they are on a older source, it's running like it should, compared to stock min. the same smoothness, maybe even better.
And I can't test lte because I only have a h+
Click to expand...
Click to collapse
The source is just github.com/cyanogenmod

papi92 said:
Does VoLTE work? I haven't stuck in my T-Mobile SIM lol and i didn't do anything so no thanks to me. It's all @Grarak and @Romanbb
Click to expand...
Click to collapse
Sorry I can' test that