Related
Looks like the G2 (Desire-Z) will not be getting CM9 stable as I have been keeping an eye on this list since last week's launch:
http://get.cm/?type=stable
Does anyone in this dev thread know why? I know there are unofficial RCs and the nightlies, but I avoid them and only go for stable. I was hoping it would get ICS stable but it appears 7.2 Gingerbread will be this device's final stable ROM.
Any insight would be greatly appreciated!
sf_smith said:
Looks like the G2 (Desire-Z) will not be getting CM9 stable as I have been keeping an eye on this list since last week's launch:
http://get.cm/?type=stable
Does anyone in this dev thread know why? I know there are unofficial RCs and the nightlies, but I avoid them and only go for stable. I was hoping it would get ICS stable but it appears 7.2 Gingerbread will be this device's final stable ROM.
Any insight would be greatly appreciated!
Click to expand...
Click to collapse
We don't have the needed drivers/source code HTC backed out on us. Aside from that though Mimicry is VERY stable I'd recommend flashing it!
Many roms past GB are very stable now. From Sense 4.0, to ICS, to even JB nightlies are reportedly smooth.
I use this ICS as a daily driver and it's very stable (AOKP): http://forum.xda-developers.com/showthread.php?t=1642443
JB nightlies: http://forum.xda-developers.com/showthread.php?t=1605016 Weren't stable when I tried them, but I hear they're really good now. Might try later this week.
It all has to do with drivers being released or something from Qualcomm: http://forum.xda-developers.com/showthread.php?t=1822694
I don't know if it's true. The thread doesn't provide much information, maybe someone can clarify.
Are the drivers really released and being incorporated into roms? People are saying they are already being used in those JB nightlies.
As for not being out officially by CM... I don't even think they started working on it.
sf_smith said:
Looks like the G2 (Desire-Z) will not be getting CM9 stable as I have been keeping an eye on this list since last week's launch:
http://get.cm/?type=stable
Does anyone in this dev thread know why? I know there are unofficial RCs and the nightlies, but I avoid them and only go for stable. I was hoping it would get ICS stable but it appears 7.2 Gingerbread will be this device's final stable ROM.
Any insight would be greatly appreciated!
Click to expand...
Click to collapse
There are no official CM9 roms for the vision. The unofficial roms (Andromadus & the one by jerl92) are the closest thing, but they are only based on Cm9, not released by or associated with the actual Cyanogenmod team. The reason there even is a CM9 based rom is thanks to Andromadus.
That said, Mimicry will have a new version out this week based on the repo for CM9 stable. The non-device specific code anyway, the other branches are of course unofficial and not supplied by the CyanogenMod team.
Sent from my HTC Vision using xda premium
---------- Post added at 03:57 PM ---------- Previous post was at 03:54 PM ----------
.ili.music.ili. said:
Are the drivers really released and being incorporated into roms? People are saying they are already being used in those JB nightlies.
As for not being out officially by CM... I don't even think they started working on it.
Click to expand...
Click to collapse
Yes, the qualcomm drivers have always been incorporated into Andromadus roms as soon as they're available. Since the other roms are based on Andromadus (AOKP, jerl92's), they also incorporate the new drivers.
Sent from my HTC Vision using xda premium
eeeeey, and I thought that CM9 stable for Desire Z is already out, bad luck
I hate to be that guy, but while development related, I'm pretty sure this belongs in the Q&A or General Discussion section. Catch knowledge!
You guys are missing drivers to?? We're also missing them!! Dang HTC :banghead::banghead::banghead:
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
The word around the Cyanogenmod Google+ site is that its coming but that it will take some time given that the drivers need to basically be written from scratch. This is a list of devices that are being droppped from any further releases of CM past CM7. The vision is not included on the list so you could say there is a glimmer of hope but I guess you have to take it with a grain of salt.
https://plus.google.com/117962666888533781522/posts/MRnnvs3oFUF
DON_58 said:
The word around the Cyanogenmod Google+ site is that its coming but that it will take some time given that the drivers need to basically be written from scratch. This is a list of devices that are being droppped from any further releases of CM past CM7. The vision is not included on the list so you could say there is a glimmer of hope but I guess you have to take it with a grain of salt.
https://plus.google.com/117962666888533781522/posts/MRnnvs3oFUF
Click to expand...
Click to collapse
There was a post by one of the developers stating that it will be coming. Everyone just needs to be patient.
Sent from planet Vegeta.
DON_58 said:
The word around the Cyanogenmod Google+ site is that its coming but that it will take some time given that the drivers need to basically be written from scratch. This is a list of devices that are being droppped from any further releases of CM past CM7. The vision is not included on the list so you could say there is a glimmer of hope but I guess you have to take it with a grain of salt.
https://plus.google.com/117962666888533781522/posts/MRnnvs3oFUF
Click to expand...
Click to collapse
Only mentions of the DesireZ/G2 in that posting is in the comment section, they're probably talking bout semi-newer devices. I still think we have a better chance of getting it 'fully' working under the Andramadus team's effort (still cM9 but probably the best it's going to be for our devices). ie: if drivers are written from scratch, it most likely won't be done by the CM team, but will probably be incorporated into their project when done.
kbeezie said:
Only mentions of the DesireZ/G2 in that posting is in the comment section, they're probably talking bout semi-newer devices. I still think we have a better chance of getting it 'fully' working under the Andramadus team's effort (still cM9 but probably the best it's going to be for our devices). ie: if drivers are written from scratch, it most likely won't be done by the CM team, but will probably be incorporated into their project when done.
Click to expand...
Click to collapse
Thats the point. Its not listed among those which are being discontinued and most of those devices are over 2 years old. Don't get me wrong I'm not trying to take anything away from the Andramadus team. I'll probably end up giving mimicry a run soon. I'm just trying to point out that the door hasnt been officially shut yet on this device as far as an official cm9 build goes.
DON_58 said:
Thats the point. Its not listed among those which are being discontinued and most of those devices are over 2 years old. Don't get me wrong I'm not trying to take anything away from the Andramadus team. I'll probably end up giving mimicry a run soon. I'm just trying to point out that the door hasnt been officially shut yet on this device as far as an official cm9 build goes.
Click to expand...
Click to collapse
Though here's something to think of: There is only one, I repeat one HTC device that is officially supported by Cyanogenmod 9. IF newer HTC devices aren't getting it, I doubt even more that a 2+ year old device would.
kbeezie said:
Though here's something to think of: There is only one, I repeat one HTC device that is officially supported by Cyanogenmod 9. IF newer HTC devices aren't getting it, I doubt even more that a 2+ year old device would.
Click to expand...
Click to collapse
I doubt the One S/One X aren't going to get CM9 Actually, I could complain about CM turning into SamsungMod, but I don't really give a damn. Just look through the supported device list yourselves, folks...
Hello,
I have a question on what is needed by developers to make Lollipop ROMs for our S3.
I have been following the releases and know that the images for the Nexus devices are up and that OTAs have begun. Is that what developers need as a starting point?
As you can tell I'm fairly clueless about this so I appreciate any information because I like to follow along.
Thanks!
Devs need the actual sources to build, which have been released. Unfortunately they can't work with the factory images for Nexus devices.
If I remember correctly, it took 2 or 3 months to get a usable KitKat build from Slim. (the first ones to do it, I recall.) We'd be lucky to see it by the new year, in my opinion.
Thank you for the info.
So they take the Nexus sources and then build it for our devices and then figure out how to add drivers for our hardware, etc?
Thank you for the timeline. I'm hoping it will be sooner, but your estimate is more realistic
I saw this in the S3 international forum:
http://forum.xda-developers.com/galaxy-s3/orig-development/rom-namelessrom-t2939673
And
http://forum.xda-developers.com/galaxy-s3/development/wip-cyanogenmod-12-t2936990
Looks like they are hard at work on lollipop for their devices. I wonder if anyone is working on it for ours yet?
philhouse said:
I saw this in the S3 international forum:
http://forum.xda-developers.com/galaxy-s3/orig-development/rom-namelessrom-t2939673
And
http://forum.xda-developers.com/galaxy-s3/development/wip-cyanogenmod-12-t2936990
Looks like they are hard at work on lollipop for their devices. I wonder if anyone is working on it for ours yet?
Click to expand...
Click to collapse
Im wondering the same and if anybody has taken interest in building it for the d2lte variants like the att etc..
I haven't seen anything yet in the forums, but I'm still hopeful that someone will!
Found this today. Sweeeeet:
http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
philhouse said:
Found this today. Sweeeeet:
http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Click to expand...
Click to collapse
Yeah I been on the ROM since it was provided.
Request a CyanogenMod for Z2 here, on their official device request page! If we've got that threat enough with requests any CM dev might take notice of that and start building!
Link : https://forum.cyanogenmod.org/topic/129472-rquest-for-lenovo-zuk-z2/#comment-611014
I recently shifted from the great XDA beloved OnePlus One and I'm shocked by the lack of the development with Z2, the device is awesome, in terms of specs and it shoud deserve more XDA love!
CM ROMs available in Chinese forums
There are CM ROMs available in official Chinese forum (bbs.zuk.cn)
CM13: bbs.zuk.cn/z2/t135170/
Download: pan.baidu.com/s/1qYlKh5a Verification Code: kd5f
CM14: bbs.zuk.cn/z2/t176429/
Download: pan.baidu.com/s/1skYQSm5 Verification Code: e95q
Google Translate may help you understand what they say.
The Baidu NetDrive would require a code as provided above when you access the file.
The ROMs are unofficial versions but they work fine.
Four promotional software exist in the ROM.
/system/app/NewBrowser
/system/app/AppCenter
/system/app/Movie2345
/system/app/Weather2345
The removal of these injected apps is recommended before use.
WhatsApp Group
We have started a WhatsApp Group for all Z2 plus owners. If you are interested kindly WhatsApp me on 9999388558
Ateesh23 said:
We have started a WhatsApp Group for all Z2 plus owners. If you are interested kindly WhatsApp me on 9999388558
Click to expand...
Click to collapse
Can you post the invite link for that group here?
WhatsApp Group for Z2 plus
https://chat.whatsapp.com/CV0oFDugpsLBfxy4zLLhnF
Explorer said:
Request a CyanogenMod for Z2 here, on their official device request page! If we've got that threat enough with requests any CM dev might take notice of that and start building!
Link : https://forum.cyanogenmod.org/topic/129472-rquest-for-lenovo-zuk-z2/#comment-611014
I recently shifted from the great XDA beloved OnePlus One and I'm shocked by the lack of the development with Z2, the device is awesome, in terms of specs and it shoud deserve more XDA love!
Click to expand...
Click to collapse
I own a OnePlus One and i was thinking about buy it as well but for a familiar, not for me and It's clearly that this device is far away from the OPO development, and it surprised me because it's a great device.
Just curious, and sorry for the little off-topic: how is it in terms of performance, camera and screen compared to the OPO?
Do you know if there are any update about this? I'm thinking about buy it if we can get official CM14.1 builds in some near future.
Basically I'm interested in buying it only if there are a fully functional custom rom like CM, slim or omni.
mustang_ssc said:
I own a OnePlus One and i was thinking about buy it as well but for a familiar, not for me and It's clearly that this device is far away from the OPO development, and it surprised me because it's a great device.
Just curious, and sorry for the little off-topic: how is it in terms of performance, camera and screen compared to the OPO?
Do you know if there are any update about this? I'm thinking about buy it if we can get official CM14.1 builds in some near future.
Basically I'm interested in buying it only if there are a fully functional custom rom like CM, slim or omni.
Click to expand...
Click to collapse
I've also been keeping tabs on the device. Check www.zukfans.eu for an overview of available roms and a more active device forum.
antimatter.web said:
I've also been keeping tabs on the device. Check www.zukfans.eu for an overview of available roms and a more active device forum.
Click to expand...
Click to collapse
Yeah i saw that at least in that forum there is much more activity, but even with that the development is not as good as i would like to see. Maybe I'm quite exigent with this but i think this device has a really good potential since his source code was published some few months ago and i don't see big results for now.
For example, the only official builds from a recognized development group i saw was from Mokee. That doesn't need to mean the development is bad but also I'm seeing some people complaining about some minor issues in unofficial builds like CM13.
mustang_ssc said:
Yeah i saw that at least in that forum there is much more activity, but even with that the development is not as good as i would like to see. Maybe I'm quite exigent with this but i think this device has a really good potential since his source code was published some few months ago and i don't see big results for now.
For example, the only official builds from a recognized development group i saw was from Mokee. That doesn't need to mean the development is bad but also I'm seeing some people complaining about some minor issues in unofficial builds like CM13.
Click to expand...
Click to collapse
I see what you mean though don't agree with. If you talk of chinese cm13 then yes.
Just take the latest release from fedor and you'll be good. I am myself crafting a rom from the different guys release.
Right now hardcore devs (meaning doing that full time) are on cm14.1 port, which is already running but having some issues.
CM 13 is mostly stable, in the coming weeks you should have some even better releases coming out.
Had anybody noticed this? Maybe some dev willing to work with it? Below it is the link. Just search for can will do =)
http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
From what I can tell there is really no difference in the kernel sources. I can use a kernel built on CAN-L01-11 source when I run LOS, but my device is AL10, I would guess it works the other way around also. Maybe someone with more time can compare the original sources released for both and see if anything is different. If not, hopefully LOS 14 will come to life soon for our device.
I am in the middle of switching jobs (very time consuming as a foreign resident in China). Good news is I will be making more money and will be able to build a build machine in the next few months.
wangdaning said:
From what I can tell there is really no difference in the kernel sources. I can use a kernel built on CAN-L01-11 source when I run LOS, but my device is AL10, I would guess it works the other way around also. Maybe someone with more time can compare the original sources released for both and see if anything is different. If not, hopefully LOS 14 will come to life soon for our device.
I am in the middle of switching jobs (very time consuming as a foreign resident in China). Good news is I will be making more money and will be able to build a build machine in the next few months.
Click to expand...
Click to collapse
I really think that there is no difference too, as we already tested with @#Henkate builds. I just specified the models to be precise, but my device (caz-tl10) would probably be able to run a LOS (or derivative) ROM built for these models I mentioned. Maybe, the thing to be aware is the partition size for our models, but as system probably has the same size, it wouldn't be a major thing.
I really want to learn and to build, but I don't have enough storage for sources and will have to wait a bit. It would be really nice to have a LOS/AOSP build with updated software
Would be nice to see Slim on the Huawei, I bought the thing simply because of the size being close to the Nexus 5. Loved that thing, but has been given to my son (he is 2 and a half, so no wifi or calling, but it runs the games he wants).
Vinnom said:
I really think that there is no difference too, as we already tested with @#Henkate builds. I just specified the models to be precise, but my device (caz-tl10) would probably be able to run a LOS (or derivative) ROM built for these models I mentioned. Maybe, the thing to be aware is the partition size for our models, but as system probably has the same size, it wouldn't be a major thing.
I really want to learn and to build, but I don't have enough storage for sources and will have to wait a bit. It would be really nice to have a LOS/AOSP build with updated software
Click to expand...
Click to collapse
Well, there must be differences in the kernel source between CAZ-TL10 and CAN-L11/L01 since those models aren't mentioned at CAZ's source on huawei's website. For example, at the source code of EMUI 4.1, both L01 and L11 are mentioned, so they use the same kernel.
Last night I've updated the defconfig by looking at a commit from Moto G4 Play (harpia), at the defconfigs of Xiaomi Redmi Note 4 (mido), Moto G5 Plus (potter) and of course, the defconfig from CAZ-TL10. You can see the commit here. Other changes might be needed too, but I'll see about that later.
You can use Google Cloud Platform for building, as I'm doing now. You only need a credit card and 1$ (which they'll give back in 1 day or so).
wangdaning said:
Would be nice to see Slim on the Huawei, I bought the thing simply because of the size being close to the Nexus 5. Loved that thing, but has been given to my son (he is 2 and a half, so no wifi or calling, but it runs the games he wants).
Click to expand...
Click to collapse
Slim it's on my "to do list". If I'll manage to build los14.1, then I'll build Slim7, otherwise Slim6.
Last night I've started to build LOS14.1 and fixed some minor build errors which you can see on my github, but then I've ran into this build error after ~30 mins of building (usually it takes 1h 30m to finish a build, thanks to GCloud platform...). I've searched a bit and found a post where a dev has the same issue and is saying that hwcomposer isn't compatible with the kernel source and that must be because I'm still using MM source since Huawei didn't publish N source for L01/L11. There's a cm14.1 branch left by Grarak and there's a commit which contain something which appear in the build error. He might tried to build cm/los 14 and ran into the same build error, I don't know. But I'll try that commit today and I'll also do more research. I'd like to build it successfully today, but I'll see how it goes.
#Henkate said:
Well, there must be differences in the kernel source between CAZ-TL10 and CAN-L11/L01 since those models aren't mentioned at CAZ's source on huawei's website. For example, at the source code of EMUI 4.1, both L01 and L11 are mentioned, so they use the same kernel.
Last night I've updated the defconfig by looking at a commit from Moto G4 Play (harpia), at the defconfigs of Xiaomi Redmi Note 4 (mido), Moto G5 Plus (potter) and of course, the defconfig from CAZ-TL10. You can see the commit here. Other changes might be needed too, but I'll see about that later.
You can use Google Cloud Platform for building, as I'm doing now. You only need a credit card and 1$ (which they'll give back in 1 day or so).
Slim it's on my "to do list". If I'll manage to build los14.1, then I'll build Slim7, otherwise Slim6.
Last night I've started to build LOS14.1 and fixed some minor build errors which you can see on my github, but then I've ran into this build error after ~30 mins of building (usually it takes 1h 30m to finish a build, thanks to GCloud platform...). I've searched a bit and found a post where a dev has the same issue and is saying that hwcomposer isn't compatible with the kernel source and that must be because I'm still using MM source since Huawei didn't publish N source for L01/L11. There's a cm14.1 branch left by Grarak and there's a commit which contain something which appear in the build error. He might tried to build cm/los 14 and ran into the same build error, I don't know. But I'll try that commit today and I'll also do more research. I'd like to build it successfully today, but I'll see how it goes.
Click to expand...
Click to collapse
I really understand your point, but what makes me think about no differences is that the link I shared leads to Cannes AL10 and Cannes TL10, which seems to be international models, but inside the file "README_Version.txt" is written that "This kernel package is released for the phone software version--CAZ-B368,MLA-B351". This really made me think that they are compatible. Maybe the various Nova types are differs in radio/modem and storage, Idk. Really made me wonder.
Thanks for the tips for google cloud storage. First I'm trying to build at least the kernel, so I can understand a bit of the process =) At least the kernel tree I can handle with my limited storage xD
PS
Is good to know that you are making quick progress to LOS 14.1 =D
Vinnom said:
I really understand your point, but what makes me think about no differences is that the link I shared leads to Cannes AL10 and Cannes TL10, which seems to be international models, but inside the file "README_Version.txt" is written that "This kernel package is released for the phone software version--CAZ-B368,MLA-B351". This really made me think that they are compatible. Maybe the various Nova types are differs in radio/modem and storage, Idk. Really made me wonder.
Thanks for the tips for google cloud storage. First I'm trying to build at least the kernel, so I can understand a bit of the process =) At least the kernel tree I can handle with my limited storage xD
PS
Is good to know that you are making quick progress to LOS 14.1 =D
Click to expand...
Click to collapse
Umm, I haven't checked that readme. Maybe I'll try that kernel source someday.
If you'll use Google Cloud Platform, then you won't need to worry about your storage, as GCloud uses own storage, like a virtual one. When you'll sign up to GCloud, you'll see that you'll have to make an "instance" and you'll have to choose "PC specs" (CPU, ram, storage). You get 300$ free and the trial is available 1 year if I'm not wrong.
I have about 150-180$ left ( I can't remember properly) and that's kinda enough. Also, I can get another trial since I have a second credit/bank card . As a tip, make sure that you'll shutdown the instance everytime you stop using it, otherwise it'll take money after some time (e.g. if the instance has been on overnight or 1-2 days). That's how I ended up with less credits available, by forgetting to shutdown it.
Here's a great guide about how to build ROM from source. I've used it myself at begin. However, keep in mind that you'll need newer java version than the one which is mentioned there.
Regarding LOS14.1, after spending the whole day (today), I've finally built the kernel without any errors. It turned out that I had to use newer CAF source and the one left by @Grarak in "caf-n" branch was useful. Probably I would've had difficulties in finding which CAF source I should use or I would've been stuck if the one by Grarak wouldn't have been there.
Tomorrow, when I'll start building the ROM, the errors related to the kernel which I've encountered yesterday should be gone since I've built the kernel successfully.
I think the chances are pretty high that the ROM won't boot, not sure, but I'm quite excited .
The thread tittle is called "Cannes al10 & cannes tl10 emui 5.0 source code release" and we talk about... you know We've went off topic.
Thank you for working so hard on this device. Living in China as a non-Chinese it is really hard to get a credit card. I will be moving in about a week and have a much better job. Hope I can get a build device together and help you out. Again, thanks for all your work.
@Vinnom
Finally, Huawei has published the source code...
There says "CAN-L10, L11", but I don't think there's L10. Probably is just a typo as they did with "Andriod".
#Henkate said:
@Vinnom
Finally, Huawei has published the source code...
There says "CAN-L10, L11", but I don't think there's L10. Probably is just a typo as they did with "Andriod".
Click to expand...
Click to collapse
Maybe lol
Btw, do you know the differences between L10 and L11?
EDIT [OT]:
I didn't have the time to answer your in the OT thread yet, but later today I'll xD
Vinnom said:
Maybe lol
Btw, do you know the differences between L10 and L11?
EDIT [OT]:
I didn't have the time to answer your in the OT thread yet, but later today I'll xD
Click to expand...
Click to collapse
I don't know and I don't think there's CAN-L10, but I'm not sure though.
Do you know when we can expect a ROM based on Android O?
Can't say for sure. May never see an official release from Nextbit/Razer, but I'm sure custom rom devs will release it when it's ready.
davehasninjas said:
Can't say for sure. May never see an official release from Nextbit/Razer, but I'm sure custom rom devs will release it when it's ready.
Click to expand...
Click to collapse
Didn't Nextbit or Razer hire the devs from Paranoid Android? If they are working on the Robin ROM, I'm pretty sure it's safe to say we'll get Oreo. However Razer announced a gaming phone a while ago, so there is no way to tell.
Baconator724 said:
Didn't Nextbit or Razer hire the devs from Paranoid Android? If they are working on the Robin ROM, I'm pretty sure it's safe to say we'll get Oreo. However Razer announced a gaming phone a while ago, so there is no way to tell.
Click to expand...
Click to collapse
One of the Developer's for PA is also one of the 30 teams members of nextbit.
There are quite a few links like these which mention Lineage OS 15 (Oreo) supported devices and robin is one of them! I cant wait for the release!
http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/
protonsavy said:
There are quite a few links like these which mention Lineage OS 15 (Oreo) supported devices and robin is one of them! I cant wait for the release!
http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/
Click to expand...
Click to collapse
Except those are all fake. The LOS maintainers won't actually know if a device will support LOS 15 until they actually try porting it in the first place. As of now, they haven't tried for the Nextbit Robin yet, so we don't know if the Robin could actually get LOS 15 yet.
If you wanna keep tabs on what devices are currently being worked on, go to https://review.lineageos.org/#/q/statuspen and look for anything being commited to the lineageos-15.0 branch for android_device_nextbit_ether.
Software updates till February as they say on Twitter. Apart from nextbits cloud framework the OS is pretty much stock AOSP and it seems to me they're really good with releasing kernel source and providing updates almost every three months.
Robin, on N, is a mess. If it does eventually get O, it will be a while. We cannot upgrade it to O until we fix out the bugs we have on N first.
What are the bugs on N? I'm thinking about buying one. Is it worth it?
oh1blksheep said:
What are the bugs on N? I'm thinking about buying one. Is it worth it?
Click to expand...
Click to collapse
Camera, GPS, battery blah the list goes on. The kernels a mess because of bad sources. I wouldnt recommend it , it would be better getting a moto G device or similar at this stage.
DarkExistence said:
Camera, GPS, battery blah the list goes on. The kernels a mess because of bad sources. I wouldnt recommend it , it would be better getting a moto G device or similar at this stage.
Click to expand...
Click to collapse
I have two devices, and I don't have troubles with it.
HeaDekBatHblu said:
I have two devices, and I don't have troubles with it.
Click to expand...
Click to collapse
Doesn't make a difference, the code base is a mess. If your buying for a Dev device, dont. Even the top lineage Devs are struggling to make it as stable as it is (and it's not very stable, messy as hell!) As an every day device it's ok but there are better phones now a days in the price range, and support is basically dead for robin now.
DarkExistence said:
Doesn't make a difference, the code base is a mess. If your buying for a Dev device, dont. Even the top lineage Devs are struggling to make it as stable as it is (and it's not very stable, messy as hell!) As an every day device it's ok but there are better phones now a days in the price range, and support is basically dead for robin now.
Click to expand...
Click to collapse
Development is not dead at all. Have you seen Gerrit for many of the ROMs??? The CarbonROM Dev already has pushes to Gerrit for O. Lineage still gets device specific changes. ParanoidAndroid has a private kernel source for ether so their working on it behind the scenes. AICP and many other ROMs use the Lineage kernel, so there aren't many differences to those that use that kernel. O development is still ongoing, and this device is still great for the price. The ROMs at the moment, are very stable in my opinion.
xWolf13 said:
Development is not dead at all. Have you seen Gerrit for many of the ROMs??? The CarbonROM Dev already has pushes to Gerrit for O. Lineage still gets device specific changes. ParanoidAndroid has a private kernel source for ether so their working on it behind the scenes. AICP and many other ROMs use the Lineage kernel, so there aren't many differences to those that use that kernel. O development is still ongoing, and this device is still great for the price. The ROMs at the moment, are very stable in my opinion.
Click to expand...
Click to collapse
I know, I'm the AICP maintainer for ether lol... And discuss with the official lineage maintainers for ether daily ..
I meant official development, btw, meaning a lot of the bugs won't be fixed because we need official updates to be able to fix them.
O development for lineage ether hasn't even begun yet, N bugs need to be fixed before O begins, and that will take awhile.
DarkExistence said:
I know, I'm the AICP maintainer for ether lol... And discuss with the official lineage maintainers for ether daily ..
I meant official development, btw, meaning a lot of the bugs won't be fixed because we need official updates to be able to fix them.
O development for lineage ether hasn't even begun yet, N bugs need to be fixed before O begins, and that will take awhile.
Click to expand...
Click to collapse
My apologies if I seemed aggressive. Official development seems to be like any other manufacturer, however, as we all know, software support is ending soon. I've been following Gerrit and have noticed the ongoing development by our developers (including you). IIRC camera was borked on one of the nightlies, but was immediately fixed. IMO, we are now depending on development from our ether devs rather than official support since Nextbit have been ghosting for the past few months.
oh1blksheep said:
What are the bugs on N? I'm thinking about buying one. Is it worth it?
Click to expand...
Click to collapse
Keep in mind what DarkExistence said, and realize the Robin's closest equivalent is a Nexus 5. If you can get better & newer hardware for a little more money, do so. I got mine as an "emergency" replacement when I was short on funds a few months ago. I lucked into an eBay sale & discount code which brought the phone to about 100.00. I'm happy with it, but I wish Razer would have made good sources available & gave full permission for them to be hosted elsewhere. So the devs didn't get so frustrated with what should be a decent phone to run custom ROMs on.
Sent from my Robin using XDA Labs
So how us the Robin treating you. Did you root? ARE you using any ROMs
oh1blksheep said:
What are the bugs on N? I'm thinking about buying one. Is it worth it?
Click to expand...
Click to collapse
Yes, for $130 it's worth buying. The bugs on android N are not nearly as bad as what some claim them to be.
Here's as list of what I can recall:
1. Enhance colors distorts colors (so turn it off)
2. Screen static displays when unlocking phone for 1/10th of a second with some roms
3. You can hear The Speakers turn off after sound has stopped playing if You listen closely
4. Headphones with a mic sometimes cut out and play through internal Speakers although there is as work around for this
5. Audio fx does not work
Other than any of those there is not much i can personally complain about and I own 2 robins. About to get a moto g4 plus because it's time for something that has a larger XDA fourm and something that has been confirmed to get android O (wich nextbit has yet to announce a decision to besides "we have been discussing it").
If I were You and my budget was under $200 i'd get The robin.
If You can spend $225 get The g4 plus without a doubt. Hope this helps
oh1blksheep said:
So how us the Robin treating you. Did you root? ARE you using any ROMs
Click to expand...
Click to collapse
I like it, especially for the price. Currently using CarbonROM rooted with Magisk. Just realize you're getting a phone with zero support from the manufacturer, so don't spend more than you're willing to lose.
Sent from my Robin using XDA Labs
DarkExistence said:
I know, I'm the AICP maintainer for ether lol... And discuss with the official lineage maintainers for ether daily ..
I meant official development, btw, meaning a lot of the bugs won't be fixed because we need official updates to be able to fix them.
O development for lineage ether hasn't even begun yet, N bugs need to be fixed before O begins, and that will take awhile.
Click to expand...
Click to collapse
Well thank you for being the maintainer on Ether. I just ordered the phone. 129.00 for a phone with these specs. Couldn't pass it up. I'm sure you will eventually make AICP stable. Thank you for your honesty.