Related
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
Hi All,
Still sense rom with Jelly Bean not released right? Is it not possible at all? I know if it was possible devs would have made it.. but still.. many HTC handsets got JB update,.. why not any port to our phone..
I am on MiUi JB rom and certainly miss sense as its still on ICS..
Rah0ol said:
Hi All,
Still sense rom with Jelly Bean not released right? Is it not possible at all? I know if it was possible devs would have made it.. but still.. many HTC handsets got JB update,.. why not any port to our phone..
I am on MiUi JB rom and certainly miss sense as its still on ICS..
Click to expand...
Click to collapse
I'd suggest you do a snooping around in the Development Forums first, but because there are a lot of ROMs in which it was discussed, Ill just tell you here.
To put it simply, it is possible but quite difficult. It is possible to have Jellybean Sense running on our device but A LOT of kernel work has to be done. JellyBean kernels require something call Ion. Some devices support it natively (like the newer ones) while others like our device, does not support it natively, and as a result, there are some conflicts, the most common and widely known is probably the camera breaking. Some libs and modules need to be fixed/replaced in order for the Jellybean ROM to work.
But patience, if a dev has the time, maybe he/she will work on a Jellybean Sense kernel for us.
072665995 said:
I'd suggest you do a snooping around in the Development Forums first, but because there are a lot of ROMs in which it was discussed, Ill just tell you here.
To put it simply, it is possible but quite difficult. It is possible to have Jellybean Sense running on our device but A LOT of kernel work has to be done. JellyBean kernels require something call Ion. Some devices support it natively (like the newer ones) while others like our device, does not support it natively, and as a result, there are some conflicts, the most common and widely known is probably the camera breaking. Some libs and modules need to be fixed/replaced in order for the Jellybean ROM to work.
But patience, if a dev has the time, maybe he/she will work on a Jellybean Sense kernel for us.
Click to expand...
Click to collapse
Thanks a lot for the explanation. So the Kernel is the issue here for the JB sense ROM development. I will just have to wait for the kernel to be developed..
and yeah snooping around the Dev forum, I am a mad flasher.. I have flashed all the firmware that are currently released for HTC on the dev forum and have played around with all dude
Was patiently waiting for a JB sense.. Guess I have to wait more..
Thanks a lot for the detailed explaination..
Brilliant explanation by 072665995, but dont get your hopes up guys
The Epik Dude said:
Brilliant explanation by 072665995, but dont get your hopes up guys
Click to expand...
Click to collapse
Agreed, brilliant explanation.
Yeah seriously!! Sense is so awesome that release of new version of JellyBean just makes its so expected to have a sense version of it. Bad that we face an issue in achieving that..
When we will have available an android 4.4 rom ? Is someone working on this ?
SilentGTX said:
When we will have available an android 4.4 rom ? Is someone working on this ?
Click to expand...
Click to collapse
Hey, well we can get some pre-alpha 4.4 AOSP builds maybe, but these will definitely have bugs, i do believe adam has built a 4.4. omni rom but i don't know much about bugs/boot status etc.
We are still waiting for cyanogenmod to merge sources, however they have stated that they are in no rush to start dishing out 4.4 roms as they have only just sunken their teeth into 4.3 Roms, we will get them eventually, however any builds within the next few days will have little customization or lots of bugs, patience is all we have till then
I hope this answered your question, also, this needs to be in the Q&A section next time bro
Good evening.
penguin449 said:
Hey, well we can get some pre-alpha 4.4 AOSP builds maybe, but these will definitely have bugs, i do believe adam has built a 4.4. omni rom but i don't know much about bugs/boot status etc.
We are still waiting for cyanogenmod to merge sources, however they have stated that they are in no rush to start dishing out 4.4 roms as they have only just sunken their teeth into 4.3 Roms, we will get them eventually, however any builds within the next few days will have little customization or lots of bugs, patience is all we have till then
I hope this answered your question, also, this needs to be in the Q&A section next time bro
Good evening.
Click to expand...
Click to collapse
Yeah thank you very much , it was very helpful , sorry for the wrong section . I can't wait for Android 4.4 ROMs :fingers-crossed: Good evening .
SilentGTX said:
Yeah thank you very much , it was very helpful , sorry for the wrong section . I can't wait for Android 4.4 ROMs :fingers-crossed: Good evening .
Click to expand...
Click to collapse
Please understand that all the great things you've been hearing about android 4.4 wont apply to us for quite some time, what i mean by this is all the efficiency/ performance improvements will be somewhat mitigated buy bugs and firmware incompatibilities, these things take time for devs to work through, 4.3 still isnt mature enough on this device to call it stable.
I just don't want people to get overly excited by a 4.4 port, its improvements will come gradually.
JoinTheRealms said:
Please understand that all the great things you've been hearing about android 4.4 wont apply to us for quite some time, what i mean by this is all the efficiency/ performance improvements will be somewhat mitigated buy bugs and firmware incompatibilities, these things take time for devs to work through, 4.3 still isnt mature enough on this device to call it stable.
I just don't want people to get overly excited by a 4.4 port, its improvements will come gradually.
Click to expand...
Click to collapse
I understand , of course , but still I can't wait :victory:
Gonna join this group, too
4.4 sure is on its way for our device, BUT:
Google is removing more and more support for our device, as it already is pretty old. So we need to re-add everything.
Even if it's booting, we still need a lot of work in order to get the most important stuff working (like SurfaceFinger, Audio, and ofc also data/RIL)
So regarding 4.4, all I can say is: Have patience
BTW, Thread moved to Q&A section
JoinTheRealms said:
4.3 still isnt mature enough on this device to call it stable.
Click to expand...
Click to collapse
im using pa 3.99 rc2 wich is 4.3 and it is perfectly stable, has great performance and no big bugs, i use it as a daily driver and it is the most perfect rom i used on my p880 till date
~MaX~ said:
im using pa 3.99 rc2 wich is 4.3 and it is perfectly stable, has great performance and no big bugs, i use it as a daily driver and it is the most perfect rom i used on my p880 till date
Click to expand...
Click to collapse
Yes they are functionally stable to a user, but to call a rom stable (at least by Cyanogenmods standards) requires more than that.
JoinTheRealms said:
Yes they are functionally stable to a user, but to call a rom stable (at least by Cyanogenmods standards) requires more than that.
Click to expand...
Click to collapse
please define stable then
~MaX~ said:
please define stable then
Click to expand...
Click to collapse
Doesn't use dirty patch code to fix issues in source, usually done to get a release out quicker, between release candidates to stable this code is refined.
JoinTheRealms said:
Doesn't use dirty patch code to fix issues in source, usually done to get a release out quicker, between release candidates to stable this code is refined.
Click to expand...
Click to collapse
Well.... Thank you
That's Well explained
I hope you are working on 4.4 rom
laufersteppenwolf said:
Gonna join this group, too
4.4 sure is on its way for our device, BUT:
Google is removing more and more support for our device, as it already is pretty old. So we need to re-add everything.
Even if it's booting, we still need a lot of work in order to get the most important stuff working (like SurfaceFinger, Audio, and ofc also data/RIL)
So regarding 4.4, all I can say is: Have patience
BTW, Thread moved to Q&A section
Click to expand...
Click to collapse
i'm really excited to see you releasing the 4.4 rom Aosp or custom, anyway your work is cool
You guys really doing great work here so l know that stable 4.4 will come eventually
Sent from my HTC Explorer A310e using Tapatalk 2
JoinTheRealms said:
Doesn't use dirty patch code to fix issues in source, usually done to get a release out quicker, between release candidates to stable this code is refined.
Click to expand...
Click to collapse
Sometimes it's still necessary to do. This is the case with our EGL libs for example. The best would be getting an update from LG, but this is very unlikely to happen. I got 4.3 BSP partially working, updated all graphics-related libs to 4.3 from grouper, but it broke a few things. Porting the full BSP might not be even possible.
Regarding Omni 4.4, I gradually found probably all needed patches for it, will see when I get to computer.
Sent from my OmniROM-powered LG Optimus 4X HD
Hello everyone
This is the first time Im creating a thread in all my years here on XDA. So please bear with me
Im very happy and excited to see the recent boom of custom roms for our device, its going really well and at a break neck speed.
Much rapid then I can download and flash it too
However, the only thing bugging me the lack of custom kernels.
I understand that the pINKman kernel by slukk and unnamed kernel by luca are both fantabulous kernels , and are mighty contenders for your time.
Dont get me wrong, I fully and whole-heartedly appreciate the kernel-devs and the awesome work made by them
The furnace kernel by savoca seemed to be a good one too, but I noticed that the thread has been closed and my recent pm to him about some possible update has not yielded any results.
I dont possibly know where im going with this conversation (lol), but if you catch my drift, we'd certainly want to see the boom of custom kernels just as we did with custom roms
Sorry for such a lengthy post .
*bows out*
:cyclops:
EDIT- lol, sorry for creating a thread in the general section, I botched it
Should have created in the QA section
metalrules321 said:
However, the only thing bugging me the lack of custom kernels.
Click to expand...
Click to collapse
Well, as long as Motorola doesn't release the kernel sources for lollipop, there isn't much that can be done. I found today some commits for lollipop but nothing official (look at Motorola's github kernel under issues). It took Motorola quite a while to release the sources for kitkat, so we have to keep patient.
need some OC and OV feature
@doppelhelix
Whelp
Thanks for clearing that up for me man.
Yeah it kinda sucks , I mean with the recent influx of so many roms and only 2 kernels was an eye-sore xD
Anys ways
*fingers crossed*
@doppelhelix
But on a second thought
How come slukk is developing and updating kernels even though the sources have not been released ??
metalrules321 said:
@doppelhelix
But on a second thought
How come slukk is developing and updating kernels even though the sources have not been released ??
Click to expand...
Click to collapse
based on kitkat. Thats why they don't work on stock lollipop, only cm
Why has google still not uploaded Shamu Android 7.0 Nougat ota zip.:crying: Anyone here who got the ota update on shamu?
Check this thread (And no, it's not out yet)
http://forum.xda-developers.com/nexus-6/general/factory-images-uploaded-t3446112
I'm waiting too ?
axok12 said:
I'm waiting too ��
Click to expand...
Click to collapse
It's so hard to wait. Really getting on my nerves.
Still on DP5, no OTA yet. Im in Kosovo, Europe
Nexus device blues
Having a nexus 6 and now getting the OTA update as soon as release as previously expected.
we will see it in a couple of weeks.
Who needs the stock images when there are already custom roms on the market.
Much better flashable zip. No encryption and custom kernel
mikaole said:
Who needs the stock images when there are already custom roms on the market.
Much better flashable zip. No encryption and custom kernel
Click to expand...
Click to collapse
As long as Bootloader and Radio dont change from DP5 to Release. Custom roms are the best route. :laugh:
I am even on preview 1 bootloader and no problem at all. Runs super smooth and root is working. All my apps are fine. So take your time Google
mikaole said:
Who needs the stock images when there are already custom roms on the market.
Much better flashable zip. No encryption and custom kernel
Click to expand...
Click to collapse
Out of curiosity I see you list velocity nougat for nexus 6. I searched on XDA but couldn't find anything except for an HTC device. Mind if I ask where you got that rom? I'd like to scope it out, thank you in advance
Sent from my Nexus 6 using XDA-Developers mobile app
Velocity is from the psx def. He is not on xda. Just building for himself and I am a tester since day one 4 years ago. It's only available on a German forum. N is not official, so I can't. But if you Google my name with velocity you will find.
mikaole said:
Velocity is from the psx def. He is not on xda. Just building for himself and I am a tester since day one 4 years ago. It's only available on a German forum. N is not official, so I can't. But if you Google my name with velocity you will find.
Click to expand...
Click to collapse
I shall take a gander, thank you.
SynisterWolf said:
As long as Bootloader and Radio dont change from DP5 to Release. Custom roms are the best route. :laugh:
Click to expand...
Click to collapse
Not really a wise option. The roms right now are hacked together with bits and parts from other stuff and without an updated kernel many things are causing issues and you dont get all the new under the hood improvments.
zelendel said:
Not really a wise option. The roms right now are hacked together with bits and parts from other stuff and without an updated kernel many things are causing issues and you dont get all the new under the hood improvments.
Click to expand...
Click to collapse
We have kernel source for DP5. And as of right now the AOSP r1 source hasn't changed much from DP5 to r1. Or thats what the elite guys have mentioned.
Sent from my iPhone 6s+ using Tapatalk
SynisterWolf said:
We have kernel source for DP5. And as of right now the AOSP r1 source hasn't changed much from DP5 to r1. Or thats what the elite guys have mentioned.
Sent from my iPhone 6s+ using Tapatalk
Click to expand...
Click to collapse
Yeah I have the source and alot is still missing compared to the DP5. I have spoken with most teams and they are all of the same mind. Until it is fixed they wont build for the n6. Some are even gonna wait until late September or October before even attempting to build it. We are all over Google groups complaining about it. Most think it has to do with Qualcom and the new Vulcan stuff that qualcomm is refusing to support on some chips.
We can only wait and see. I personally am not touching a single rom that is built at the moment. Not a fan of hack together roms.
zelendel said:
Yeah I have the source and alot is still missing compared to the DP5. I have spoken with most teams and they are all of the same mind. Until it is fixed they wont build for the n6. Some are even gonna wait until late September or October before even attempting to build it. We are all over Google groups complaining about it. Most think it has to do with Qualcom and the new Vulcan stuff that qualcomm is refusing to support on some chips.
We can only wait and see. I personally am not touching a single rom that is built at the moment. Not a fan of hack together roms.
Click to expand...
Click to collapse
Yolo? ?
Sent from my iPhone 6s+ using Tapatalk
SynisterWolf said:
Yolo? ?
Sent from my iPhone 6s+ using Tapatalk
Click to expand...
Click to collapse
Not with a device I rely on. My device is a tool not a toy lol.
Plus I make my own roms and only use roms made by a very few others. To be honest only 2 teams do I trust their roms to flash to my device. I know all too well the risks involved in flashing roms.
Nexus 5x is live Come On GOOGLE!!!
Velocity was a ROM by Trident in the LG Ally days, woah they bring me back. Back to Android 2.2.2!