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
Hey guys so I recently heard that the Sprint HTC One started receiving CyanogenMod 10.1 nightlies.
Sure enough I checked it out at the get cm site, and they're there!
I'm currently running the nightly from 5/14 and it's smooth/ stable enough for a daily driver rom (In My Opinion)
What I would like to know is where I could find some changelogs for the new builds/ who's behind this awesomeness.
I checked the CyanogenMod wiki, but the only information I could find was that it's being maintained by "kushdeck"
Can someone please find out more information about the dev/ changelogs between builds/ etc...
I checked the android development section and there aren't any posts relating to this.
Chrisal8 said:
Hey guys so I recently heard that the Sprint HTC One started receiving CyanogenMod 10.1 nightlies.
Sure enough I checked it out at the get cm site, and they're there!
I'm currently running the nightly from 5/14 and it's smooth/ stable enough for a daily driver rom (In My Opinion)
What I would like to know is where I could find some changelogs for the new builds/ who's behind this awesomeness.
I checked the CyanogenMod wiki, but the only information I could find was that it's being maintained by "kushdeck"
Can someone please find out more information about the dev/ changelogs between builds/ etc...
I checked the android development section and there aren't any posts relating to this.
Click to expand...
Click to collapse
10.1.cmxlog.com/?device=m7wls
Aldo101t said:
10.1.cmxlog.com/?device=m7wls
Click to expand...
Click to collapse
Thanks, couldn't find this lol.
Check original development..
deck is indeed the shiznit.
Sent from my HTCONE using XDA Premium HD app
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
Hi,
I'm about to get a Z1 in a few days so I stalked the forums already.
So I noticed something that confuses me.
I found the CM11 Thread by FreeXperiaProject and I also checked the original CyanogenMod Homepage.
So it seems like there are the official CM Nightlys and the FreeXperiaProject release of CM11.
Which of them is "the right one" ? Should I stick with the forums and use the FXP Version or the official one?
Is there a difference at all?
Hope you can enlighten me
.K' said:
Hi,
I'm about to get a Z1 in a few days so I stalked the forums already.
So I noticed something that confuses me.
I found the CM11 Thread by FreeXperiaProject and I also checked the original CyanogenMod Homepage.
So it seems like there are the official CM Nightlys and the FreeXperiaProject release of CM11.
Which of them is "the right one" ? Should I stick with the forums and use the FXP Version or the official one?
Is there a difference at all?
Hope you can enlighten me
Click to expand...
Click to collapse
http://download.cyanogenmod.org/?device=honami
Rekoil said:
http://download.cyanogenmod.org/?device=honami
Click to expand...
Click to collapse
wow .. that was ... not helpful at all.
As I said: I already found BOTH the FXP and Official CM11 releases/nightlys.
And call me stupid but I could not find any infos about differences in both versions on the CM Download page.
.K' said:
wow .. that was ... not helpful at all.
As I said: I already found BOTH the FXP and Official CM11 releases/nightlys.
And call me stupid but I could not find any infos about differences in both versions on the CM Download page.
Click to expand...
Click to collapse
Your question was, "Should I stick with the forums and use the FXP Version or the official one?", my response was a link to the official, I thought that was clear enough. There's most often no difference except that the common CyanogenMod code is generally newer in the official releases.
Official nightly builds is a good start, no?
http://www.androidpolice.com/2015/03/13/samsung-galaxy-tab-s-8-4-gets-official-cyanogenmod-nightly-builds/
Link to firmware: http://get.cm/get/nCM
zetajunkie said:
Official nightly builds is a good start, no?
http://www.androidpolice.com/2015/03/13/samsung-galaxy-tab-s-8-4-gets-official-cyanogenmod-nightly-builds/
Link to firmware: http://get.cm/get/nCM
Click to expand...
Click to collapse
Ah you beat me to it. I was just about to make a thread about this. The official thread can be found here: http://forum.xda-developers.com/gal...0-x-cyanogenmod-12-0-nightlies-tab-s-t3053977
Uhh t705 getting no love
Can someone please explain to the noobs out there what a nightly build is? And yes I do mean me thanks.
MohamedN said:
Uhh t705 getting no love
Click to expand...
Click to collapse
look here:
http://forum.xda-developers.com/gal...official-blck-cyanogenmod-12-sm-t705-t3053004
What about the 10.5?
Ccieslin said:
Can someone please explain to the noobs out there what a nightly build is? And yes I do mean me thanks.
Click to expand...
Click to collapse
Quoted from the android headlines.com article:
"Of course, if this is your first time trying CyanogenMod then you do need to be made aware that this is a ‘nightly’ download. This first and foremost means that you are going to see far more regular updates landing for the ROM once it is installed. Sometimes, literally, on a nightly basis (hence the name). It is also worth pointing out that this also means that it is considered an experimental build and not fully stable. That said, you are unlikely to experience anything too problematic. However, with these nightly builds it is at least wise to expect (and prepare) for some minor bugs. Not to mention, it would be wise to make sure all your important data is backed up."
http://www.androidheadlines.com/201...ailable-for-the-samsung-galaxy-tab-s-8-4.html